ece544: communication networks-ii, spring 2006
DESCRIPTION
ECE544: Communication Networks-II, Spring 2006. D. Raychaudhuri Lecture I. Includes teaching materials from L. Peterson & L. Govidan. Today’s Lecture. Administrative matters Course Overview topics covered design & prototyping projects Introduction to networking - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/1.jpg)
ECE544: Communication Networks-II, Spring 2006
D. Raychaudhuri
Lecture I
Includes teaching materials from L. Peterson & L. Govidan
![Page 2: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/2.jpg)
Today’s Lecture
• Administrative matters• Course Overview
– topics covered– design & prototyping projects
• Introduction to networking• Elements of top-down design
![Page 3: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/3.jpg)
Class Structure
• Friday 4:45-7:30pm*• Lecture format
– Slides, Board, …– Interactive
• Two 80 min sessions– with a 10 min break in between
*location will move to WINLAB Modular Conf Room
![Page 4: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/4.jpg)
Contact Information• Instructor: Prof. D. Raychaudhuri
– Email: [email protected]– Office Hours: by appt, WINLAB Tech Center or Core
501
• TA (for project): Zhibin Wu– Email: [email protected]– Office hours: tbd
• Class Resources (eff 1/23)– Web page: http://www.winlab.rutgers.edu/comnet2– Mailing list: [email protected]
![Page 5: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/5.jpg)
Course Readings• Textbook (required, to be used for
~60% material)– Peterson & Davie, “Computer Networks: A
Systems Approach”, Morgan Kaufman, 3rd ed
• Research papers in networking– to be distributed either online or in class– collection of classical and topical
research• ~10 papers and standards documents• required reading to supplement text book
overview
![Page 6: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/6.jpg)
Course Grading• Class participation & homework: 10%
– Brief in-class presentations– Assigned homework from textbook
• Midterm (25%) and Final (40%)– Open book, 1 page of notes permitted;
includes both descriptive and numerical problems
• Design & Prototyping Assignments: 25%– network architecture paper 10%– software project & report 15%
• No makeup exams, no extra credit work
![Page 7: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/7.jpg)
Student Commitments• Keep up with your reading
– read applicable text book chapter and distributed papers/RFC’s before and after each class
• Sharpen your programming skills– study C/C++ & Unix programming as
needed and work on simple programming exercises early in the semester
• Work independently– no “collaboration” of any sort
• Turn in assignments on time• Make sure assignments are gradable
– follow project and program submission rules
![Page 8: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/8.jpg)
Prerequisites
• Curricular prerequisites– Computer Networks I or equivalent– General communications and
computer architecture/OS background
• Skills– C/C++ programming
• significant programming project
– use of design and analysis tools
![Page 9: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/9.jpg)
Course Topics• Introduction• Network Principles• Shared Media/MAC• Pkt switching
(ATM)• IP Basics• IP Advanced• Mobility Protocols-- mid-term
• Network security• Transport layer• Higher-layer
protocols• Hardware issues• Case studies and
research topics– www, VOIP– semantic routing– optical IP network– ad-hoc mobile net
![Page 10: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/10.jpg)
Projects• Network
architecture paper- select a network
- top-down design- requirements- specifications- performance analysis
• In-class presentations- supplementary topics
- ~20 min talk
• Warm-up Projects- C/C++ programming exercises
- Unix sockets, etc.
- simple link protocols • Network software project
- new network prototype
- software platform provided- student teams will write spec & protocol software - system integration & demo
![Page 11: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/11.jpg)
What is the problem?
![Page 12: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/12.jpg)
Application Considerations
• Application input to network– traffic data rate– traffic pattern (bursty or constant bit rate)– traffic target (multipoint or single
destination, mobile or fixed)
• Network service delivered to application– delay sensitivity– loss sensitivity
![Page 13: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/13.jpg)
Chapter 1, Figure 7
A Multimedia Application
![Page 14: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/14.jpg)
Reliable File Transfer
• Loss sensitive• Not delay sensitive relative to
round trip times• Point-to-point or multipoint• Bursty
![Page 15: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/15.jpg)
Remote Login
• Loss sensitive• Delay sensitive
– subject to interactive constraints– can tolerate up to several hundreds of
milliseconds
• Bursty• Point to point
![Page 16: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/16.jpg)
Network Audio
• Relatively low bandwidth– Digitized samples, packetized
• Delay variance sensitive• Loss tolerant• Possibly multipoint, long duration
sessions– natural limit to number of
simultaneous senders
![Page 17: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/17.jpg)
Network Video
• High bandwidth• Compressed video, bursty• Loss tolerance function of compression• Delay tolerance a function of
interactivity• Possibly multipoint• Larger number of simultaneous
sources
![Page 18: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/18.jpg)
Web
• Transactional traffic– short requests, possibly large
responses
• Loss (bug?) tolerant• Delay sensitive
– human interactivity
• Point-to-point (multipoint is asynchronous)
![Page 19: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/19.jpg)
What is….
• Structure• Metrics• Failure modes• Functions
![Page 20: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/20.jpg)
Network Structure
Backbones
Regionals
Campus LANs
![Page 21: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/21.jpg)
Network Metrics
• Bandwidth– transmission capacity
• Delay– queueing delay– propagation delay (limited by c)
• Delay-Bandwidth product– important for control algorithms
![Page 22: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/22.jpg)
Bandwidth versus Latency• Relative importance
– 1-byte: 1ms vs 100ms dominates 1Mbps vs 100Mbps
– 25MB: 1Mbps vs 100Mbps dominates 1ms vs 100ms
• Infinite bandwidth– RTT dominates
• Throughput = TransferSize / TransferTime• TransferTime = RTT + 1/Bandwidth x TransferSize
– 1-MB file to 1-Gbps link as 1-KB packet to 1-Mbps link
![Page 23: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/23.jpg)
Delay x Bandwidth Product
• Amount of data “in flight” or “in the pipe”
• Example: 100ms x 45Mbps = 560KB
Bandwidth
Delay
![Page 24: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/24.jpg)
Chapter 1, Figure 9
10,000
5000
2000
1000
500
200
100
50
20
10
5
2
1
10010RTT (ms)
1-MB object, 1.5-Mbps link
1-MB object, 10-Mbps link
2-KB object, 1.5-Mbps link
2-KB object, 10-Mbps link
1-byte object, 1.5-Mbps link
1-byte object, 10-Mbps link
Per
ceiv
ed la
tenc
y (m
s)
![Page 25: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/25.jpg)
Network Failures
• Packet loss– queue overflows– line noise
• Node or link failures• Routing transients or failures
![Page 26: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/26.jpg)
Statistical Multiplexing Gain
1 Mbps link; users require 0.1 Mbps when transmitting; users active only 10% of the time.
• Circuit switching: can support 10 users• Packet switching: with 35 users,
probability that >=10 are transmitting at the same time = 0.0004.
![Page 27: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/27.jpg)
Back in the old days..
Time
bw
![Page 28: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/28.jpg)
Then came TDM..
mux demux
![Page 29: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/29.jpg)
Logical network view
![Page 30: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/30.jpg)
Packet switching (Internet)
![Page 31: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/31.jpg)
Packet Switching
Interleave packets from different sources
• Efficient: resources used on demand– statistical multiplexing
• General– multiple types of applications
• Accommodates bursty traffic
![Page 32: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/32.jpg)
Characteristics of Packet Switching
• Store and forward– packets are self contained units– can use alternate paths - reordering
• Contention– congestion– delay
![Page 33: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/33.jpg)
Protocols
• On top of a packet switched network, need
• Set of rules governing communication between network elements (applications, hosts, routers)
• Protocols define:– format and order of messages– actions taken on receipt of a message
![Page 34: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/34.jpg)
Protocols (contd.)
• Building blocks of a network architecture• Each protocol object has two different
interfaces– service interface: operations on this protocol– peer-to-peer interface: messages exchanged
with peer
• Term “protocol” is overloaded– specification of peer-to-peer interface– module that implements this interface
![Page 35: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/35.jpg)
Layering
Host Host
Application
Transport
Network
Link
User A User BTeleconferencing
Layering: technique to simplify complex systems
Peers
![Page 36: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/36.jpg)
Layering Characteristics
• Each layer relies on services from layer below and exports services to layer above
• Interface defines interaction• Hides implementation - layers can
change without disturbing other layers (black box)
![Page 37: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/37.jpg)
ISO Architecture
Application
Presentation
Session
Transport
End host
One or more nodeswithin the network
Network
Data link
Physical
Network
Data link
Physical
Network
Data link
Physical
Application
Presentation
Session
Transport
End host
Network
Data link
Physical
![Page 38: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/38.jpg)
Internet Architecture• Defined by Internet Engineering Task Force
(IETF)• Hourglass Design• Application vs Application Protocol (FTP, HTTP)
…
FTP HTTP NV TFTP
TCP UDP
IP
NET1 NET2 NETn
![Page 39: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/39.jpg)
Layering General Issues
• Reliability• Flow control• Fragmentation• Multiplexing• Connection setup (handshaking)• Addressing/naming (locating
peers)
![Page 40: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/40.jpg)
Example: Transport layer
• First end-to-end layer• End-to-end state• May provide reliability, flow and
congestion control
![Page 41: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/41.jpg)
Example: Network Layer
• Point-to-point communication• Network and host addressing• Routing
![Page 42: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/42.jpg)
Inter-Process Communication
• Turn host-to-host connectivity into process-to-process communication.
• Fill gap between what applications expect and what the underlying technology provides. Host Host
Application
Host
Application
Host Host
Channel
![Page 43: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/43.jpg)
IPC Abstractions
• Request/Reply– distributed file
systems– digital libraries
(web)
• Stream-Based– video: sequence of
frames• 1/4 NTSC = 352x240 pixels• (352 x 240 x
24)/8=247.5KB• 30 fps = 7500KBps =
60Mbps
– video applications• on-demand video• video conferencing
![Page 44: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/44.jpg)
Host 1
Protocol
Host 2
Protocol
High-level
object
High-levelobject
Service
interface
Peer-to-peer
interface
Interfaces
![Page 45: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/45.jpg)
Chapter 1, Figure 21
IP
TCP
send(IP, message) deliver(TCP, message)
Interfaces (contd.)
![Page 46: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/46.jpg)
Chapter 1, Figure 22
send()deliver()
Topmost protocol
Application process
Interfaces (contd.)
![Page 47: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/47.jpg)
47
Protocol Machinery• Protocol Graph
– most peer-to-peer communication is indirect– peer-to-peer is direct only at hardware level
Fileapplication
Digitallibrary
application
Videoapplication
RRP MSP
HHP
Host 1
Fileapplication
Digitallibrary
application
Videoapplication
RRP MSP
HHP
Host 2
![Page 48: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/48.jpg)
48
Machinery (cont)• Multiplexing and Demultiplexing (demux
key)• Encapsulation (header/body)
RRP DataHHP
Applicationprogram
Applicationprogram
Host 1 Host 2
Data
RRP
RRP Data
HHP
Data
RRP
RRP Data
HHP
![Page 49: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/49.jpg)
Network Architecture• Identify basic service requirements
– transport service(s)– bit-rates to be supported– network API– # of users– terminal type (fixed, portable, etc.)
• Outline network topology– access network type (wired/wireless,
span, etc.)– core network if any (node locations, span,
etc.)
![Page 50: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/50.jpg)
Example 1: Broadband Wireless Access
• Draw a general conceptual network diagram to start...
Internet
Broadband WirelessAccess Network
Mobile CommDevices
Fixed PC/WS
Mobile PDA/PIASemi-mobileLaptop, etc.
Switched TelecomNetwork telco-BWA
gateway
IP-BWAgateway
Multiserviceinterface withvoice/data ,
QoS support,and mobility
support
Metro-areawireless access
network(~Km)
~0.1-10 Mbos
![Page 51: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/51.jpg)
Example 2: Infostations• Mobile user passes through Infostations in sec during which ~MB files are downloaded
from (or uploaded to) network– Requires fast synchronization and service setup– Motivates 2-tier architecture with ~10m service zone (for high-speed data transfer) and ~50m access control zone (for sync,
authentication, ..)
Transit time ~sec
Infostationsaccess pointData cache
~100 MB/sFast transfer
Low-speed control channel(for synch & service setup)
ServiceZone
Access ControlZone
Total transit time ~10sec
![Page 52: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/52.jpg)
Requirements (contd.)• List additional service and network
features– QoS, video/audio, etc.– special routing (mcast, broadcast,..)– mobility– availability– reliability– security/authentication
• Rough system capacity (Mbps) and cost estimates ($/MB or $/user/mo)
![Page 53: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/53.jpg)
Requirements Analysis • Summary table listing key
requirements
# of users
Terminal type
Reliability
Security features
Bit rate
Topology
QoS features
Availability
Transport services
Cost
CBR, VBR-rt,..
0.1-10 Mbps
~1000’s per access network
portable/mobile, fixed wireless
hierarchical, access/core
selectable BW, stream support
99.9%
99.99%
mobile authentication, on-air encryption
$0.1/MB or $50/mo/user
![Page 54: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/54.jpg)
Network Components• Key hardware components of a
network– NIC ~10, 100, 155, 622, 1000 Mbps– shared media channels (Ethernet,
HFC, wireless, satellite, ..) ~Mbps– point-to-point links (DSL, CAT-5,
microwave, fiber,..)– switches (Ethernet, ATM, MPLS/IP) ~
Gbps -Tbps– routers (IP) ~Mbps - Gbps
![Page 55: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/55.jpg)
High-Level Design• Select network topology based on
geographic, capacity, reliability, etc.• Partition into access network, core
network, etc. as required• Assign network hardware components to
each subnetwork based on service and QoS requirements
• Define service API and protocol stacks• Analyze network performance & cost
and iterate until requirements are met
![Page 56: ECE544: Communication Networks-II, Spring 2006](https://reader036.vdocuments.mx/reader036/viewer/2022062517/56813a21550346895da1ff38/html5/thumbnails/56.jpg)
56
Today’s Homework• Peterson & Davie, Chap 1 (3rd ed)
-1.1-1.3-1.15-1.17-1.23-1.28