Scribd
Upload
38 views44 pages

CH 02 - Dcc10e

The document discusses protocol architectures, the TCP/IP protocol stack, traditional internet applications like FTP, HTTP, and SMTP, multimedia applications and technologies, and sockets programming. It describes the layers of a simple protocol architecture and the TCP/IP architecture including the physical layer, network access layer, internet layer, transport layer, and application layer. It also covers TCP, UDP, and IP addressing as well as common internet applications and sockets.

Uploaded by

Mr. Shuaimi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
38 views44 pages

CH 02 - Dcc10e

The document discusses protocol architectures, the TCP/IP protocol stack, traditional internet applications like FTP, HTTP, and SMTP, multimedia applications and technologies, and sockets programming. It describes the layers of a simple protocol architecture and the TCP/IP architecture including the physical layer, network access layer, internet layer, transport layer, and application layer. It also covers TCP, UDP, and IP addressing as well as common internet applications and sockets.

Uploaded by

Mr. Shuaimi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 44

EDW 204

Data Communication and


Networking

CHAPTER 2
Protocol Architecture, TCP/IP, and
Internet-Based Applications
Topic
 A Simple Protocol Architecture
 The TCP/IP Protocol Architecture
 Traditional Internet-Based Applications
To destroy communication completely, there
must be no rules in common between
transmitter and receiver—neither of alphabet
nor of syntax.

—On Human Communication,


Colin Cherry
The Need for a Protocol
Architecture
Functions of Protocol
Architecture
 Breaks logic into subtask modules which
are implemented separately
 Modules are arranged in a vertical stack
• Each layer in the stack performs a
subset of functions
• Relies on next lower layer for primitive
functions
• Provides services to the next higher layer
• Changes in one layer should not require
changes in other layers
Key Features of a Protocol
A protocol is a set of rules or conventions
that allow peer layers to communicate
The key features of a protocol are:
A Simple Protocol Architecture
Communication Layers
TCP/IP Protocol Architecture
Physical Layer
 Covers the physical interface between
computer and network
 Concerned with issues like:
 Characteristics of transmission medium
 Nature of the signals
 Data rates
Network Access/Data Link Layer
 Covers the exchange of data between an
end system and the network that it is
attached to
 Concerned with:
 Access to and routing data across a network
for two end systems attached to the same
network
Internet Layer
Host-to-Host (Transport) Layer
Application Layer
 Contains the logic needed to support the
various user applications
 A separate module is needed for each
different type of application that is peculiar
to that application
TCP/IP Address Requirements
Two levels of addressing are needed:
Transmission Control Protocol
(TCP)
 TCP is the transport layer protocol for most
applications
 TCP provides a reliable connection for transfer
of data between applications
 A TCP segment is the basic protocol unit
 TCP tracks segments between entities for
duration of each connection
User Datagram Protocol
(UDP)
 Alternative to TCP
 Does not guarantee delivery, preservation of
sequence, or protection against duplication
 Enables a procedure to send messages to other
procedures with a minimum of protocol
mechanism
 Adds port addressing capability to IP
 Used with Simple Network Management Protocol
(SNMP)
 Includes a checksum to verify that no error occurs
in the data
Service Primitives and
Parameters
Table 2.1
Service Primitive Types
Traditional Internet-Based
Applications
 Three common applications that have been
standardized to operate on top of TCP are:
Table 2.2
Multimedia Terminology
Media Types
Table 2.3

Domains of Multimedia Systems


and Example Applications
Multimedia Applications
Multimedia Technologies
 Some technologies that are relevant to the
support of multimedia applications are:
Sockets Programming
 Concept was developed in the 1980s in the
UNIX environment as the Berkeley Sockets
Interface
 De facto standard application programming
interface (API)
 Basis for Window Sockets (WinSock)
 Enables communication between a client and
server process
 May be connection oriented or
connectionless
The Socket
 Formed by the concatenation of a port value and an IP
address
 Unique throughout the Internet
 Used to define an API
 Generic communication interface for writing programs that use
TCP or UDP
 Stream sockets
 All blocks of data sent between a pair of sockets are guaranteed
for delivery and arrive in the order that they were sent
 Datagram sockets
 Delivery is not guaranteed, nor is order necessarily preserved
 Raw sockets
 Allow direct access to lower-layer protocols
Table
2.4

Core
Socket
Functions

(Table can be found


on page 54 in
textbook)
(Figure 2.13 can be
found on page 57 in
textbook)
(Figure 2.14 can be
found on page 58 in
textbook)
Summary
 The need for a protocol
architecture  Traditional internet-
 Simple protocol based applications
architecture
 TCP/IP protocol  Multimedia
architecture  Media types
 TCP/IP layers  Multimedia applications
 Operation of TCP and IP
 TCP and UDP  Multimedia technologies
 IP and IPv6  Sockets programming
 Protocol interfaces
 Standardization within a
 The socket
protocol architecture  Sockets interface calls
 Standards and protocol
layers
 Service primitives and
parameters

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy