程序代做CS代考 Layered Architecture and Network Protocols – cscodehelp代写

Layered Architecture and Network Protocols
EE450: Introduction to Computer Networks Professor A. E450, USC, Zahid 1

Protocols
Human Protocols:
 what’s the time?
 I have a question
 Introductions
… specific msgs sent
… specific actions taken when msgs received, or other events
Network Protocols:
 Machines rather than humans
 All communication activity in Internet governed by protocols
Protocols define format, order of msgs sent and received among network entities, and
actions taken on msg transmission, receipt
EE450, USC, Zahid 2

Human vs. Network Protocols
Hi
Hi
Got the time?
2:00
TCP connection request
TCP connection reply
time
Get http://www.usc.com/grades.html
EE450, USC, Zahid
3

Key Elements of a Protocol
 Syntax
 Data formats, compression, encryption, etc..
 Signal levels  Semantics
 Control information such as flow & congestion  Error detection and control mechanisms
 Timing
 Speed matching
 Sequencing  Fairness
EE450, USC, Zahid 4

OSI Reference Model
EE450, USC, Zahid 5

Data Transfer in OSI
EE450, USC, Zahid 6

The Internet and TCP/IP
EE450, USC, Zahid 7

Internet Protocol Stack
 Application: supporting network applications
 FTP, SMTP, HTTP
 Transport: process-process data
transfer
 TCP, UDP
 Network: routing of datagrams from source to destination
application
transport
network
link
physical
 IP, routing protocols
 Link: data transfer between neighboring networkelements
 PPP, Ethernet
 Physical: bits “on the wire”
Developed by the US Defence Advanced Research Project Agency (DARPA) for its packet switched network (ARPANET)
EE450, USC, Zahid 8

TCP/IP Model
EE450, USC, Zahid 9

Message Transmission using TCP/IP
EE450, USC, Zahid 10

TCP/IP vs. OSI Models
EE450, USC, Zahid 11

Encapsulation
Hl

Ht
Ht
M
source
application
transport
network
link
physical
message segment Ht
M
M
packet frame
M
link
physical
network
link
Switch
destination
Hn Ht Ht
Router
M
M
application
transport
network
link physical
M
Ht
Hn Ht Ht
EE450, USC, Zahid 16
physical
Hn
Ht
M
M
M M

Addressing in TCP/IP
EE450, USC, Zahid 13

TCP/IP Layers and Addresses
EE450, USC, Zahid 14

Link Layer (MAC) Addresses
Most local area networks use a 48-bit (6 Bytes) physical address written as 12 hexadecimal digits, with every 2 Bytes separated by a hyphen for example
“07-01-02-01-2C-4B”
a node with MAC address 10 sends a frame to a node with MAC address 87. The two nodes are connected by a link. At the data link level this frame contains MAC addresses in the header. These are the only addresses needed. The header contains other information needed @ this level. The trailer contains extra bits needed for error detection
EE450, USC, Zahid 15

Internetwork Communications
An Internet address (in IPv4) is 32 bits in length written as four decimal numbers, with each number representing 1 Byte. The numbers are separated by a dot. For example 128.125.75.9
A node with an IP address A and MAC address 10, located on one LAN, to a node with an IP address P and MAC address 95, located on another LAN. Because the two devices are located on different networks, we cannot use MAC addresses only; the MAC addresses only have local significance. What we need here are universal addresses that can pass through the LAN boundaries. The IP address has
this characteristic.
EE450, USC, Zahid 16

Port Addresses
EE450, USC, Zahid
17
A port address is a 16-bit address represented by one decimal number for example 750
Data coming from the upper layers have port addresses j and k (j is the address of the sending process, and k is the address of the receiving process). Data are split into two Packets, each retaining the port addresses (j and k). Then in the network layer, IP addresses (A and P) are added to each packet.

Layered Architecture and Networks
• Each host needs a unique global address referred to as the IP address
• Each application on a multitasking computer needs a unique address, referred to as the Port number, within the computer
EE450, USC, Zahid 18

Leave a Reply

Your email address will not be published. Required fields are marked *