Introduction
-
Upload
maryam-bean -
Category
Documents
-
view
36 -
download
0
description
Transcript of Introduction
Uses of Computer Networks
• Business Applications
• Home Applications
• Mobile Users
• Social Issues
Home Network Applications
• Access to remote information
• Person-to-person communication
• Interactive entertainment
• Electronic commerce
Network Hardware
• Local Area Networks
• Metropolitan Area Networks
• Wide Area Networks
• Wireless Networks
• Home Networks
• Internetworks
Wireless Networks
Categories of wireless networks:
• System interconnection
• Wireless LANs
• Wireless WANs
Home Network Categories
• Computers (desktop PC, PDA, shared peripherals• Entertainment (TV, DVD, VCR, camera, stereo, MP3)• Telecomm (telephone, cell phone, intercom, fax)• Appliances (microwave, fridge, clock, furnace, airco)• Telemetry (utility meter, burglar alarm, babycam).
Network Software
• Protocol Hierarchies• Design Issues for the Layers• Interfaces and services• Connection-Oriented and Connectionless Services• Service Primitives• The Relationship of Services to Protocols
Design Issues for the Layers
• Addressing• Transfer rule• Error Control• Flow Control• Disassemble and reassemble• Multiplexing• Routing
Design Issues for the LayersAddressing
• Each layer needs a mechanism for identifying senders and receivers
• Sender: a process on a machine• Receiver: a process on another machine
Design Issues for the LayersError Control
• Physical lines are not perfect• Error-detecting or error-correcting codes• How the receiver tells the sender which messages have
been correctly received and which have not• Messages may be out of sequence• How the sender numbers the messages, how the receiver
deals with the messages arrive out of order
Design Issues for the LayersFlow control
• A fast sender may swamp a slow receiver with data• Method 1: some kind of feedback from the receiver to
announce it’s current situation• Method 2: limit the sender’s transmission rate
Design Issues for the LayersDisassemble & Reassemble
• Each layer could have different message size• Lower layer may disassemble upper layer’s message into
several smaller messages reassembled by receiving peer• Lower layer may gather several small messages into a
single large message to improve efficiency
Design Issues for the LayersMultiplexing
• The underlying layer may use the same connection for multiple, unrelated conversions
• The multiplexing and demultiplexing must be done transparently
Interfaces and services
• Entity: active elements in a layer, software entity or hardware entity
• Peers: entities in the same layer on different machines• Service provider and service user: the entities in layer n
implement a service used by layer n+1, layer n is called the services provider, layer n+1 is called service user
• SAPs: Service Access Points, the layer n SAPs are the places where layer n+1 can access the services offered
• IDU: Interface Data Unit, the information elements exchanged between neighboring layers via SAP
Interfaces and services(2)
• SDU: Service Data Unit, the information passed across the network to the peer entity and then up to layer n+1,it is filled into user data part of layer n PDUs
• PDU: Protocol Data Unit, the information exchanged between two peers
• ICI: Interface Control information, the control information in IDU
• PCI: Protocol Control Information, the control information in PDU
Service Primitives
• Requests: an entity wants the service to do some work
• Indication: an entity is to be informed about an event
• Response: an entity wants to respond to an event• Confirm: The response to an earlier request has
come back
Service Primitives (2)
服务用户
( N+1)
服务提供者
( N)
SYSTEM A
服务用户
( N+1)
服务提供者
( N)
SYSTEM B
RequestIndication
Response
Confirm
confirmed
RequestIndication
PDU
unconfirmed
Service Primitives (3)Example
1. CONNECT.request - request a connection to be established
2. CONNECT.indication - signal the called party
3. CONNECT.response - used by the callee to accept/reject calls
4. CONNECT.confirm – tell the caller whether the call was accepted
5. DATA.request – request that data be sent
6. DATA.indication – signal the arrival of data
7. DISCONNECT.request – request that a connection be released
8. DISCONNECT.indication – signal the peer about the request
Reference Models
• The OSI Reference Model
• The TCP/IP Reference Model
• A Comparison of OSI and TCP/IP
• A Critique of the OSI Model and Protocols
• A Critique of the TCP/IP Reference Model
*Comparing OSI and TCP/IP Models
Concepts central to the OSI model
• Services
• Interfaces
• Protocols
A Critique of the OSI Model and Protocols
Why OSI did not take over the world
• Bad timing
• Bad technology
• Bad implementations
• Bad politics
A Critique of the TCP/IP Reference Model
Problems:• Service, interface, and protocol not distinguished• Not a general model• Host-to-network “layer” not really a layer• No mention of physical and data link layers• Minor protocols deeply entrenched, hard to replace
Example Networks
• The Internet
• Connection-Oriented Networks: X.25, Frame Relay, and ATM
• Ethernet
• Wireless LANs: 802:11
The ARPANET
(a) Structure of the telephone system.(b) Baran’s proposed distributed switching system.
The ARPANET (3)
Growth of the ARPANET (a) December 1969. (b) July 1970.(c) March 1971. (d) April 1972. (e) September 1972.
Internet Usage
Traditional applications (1970 – 1990)
• News
• Remote login
• File transfer
Network Standardization
• Who’s Who in the Telecommunications World• Who’s Who in the International Standards World• Who’s Who in the Internet Standards World
ITU
• Main sectors• Radio communications• Telecommunications Standardization• Development
• Classes of Members• National governments• Recognized private operators• Regional telecommunications organizations• Telecommunication vendors and scientific
organizations• Other interested organizations