CSE 5300: Advanced Computer NetworksCourse infoCourse GoalsWireless networksOther wireless networksCourse TopicsCourse mechanicsGradingPart 0: Networking ReviewWhat’s a network: “nuts and bolts” viewWhat’s a protocol?Slide 12A closer look at network structure:The network edge:Network edge: connection-oriented serviceNetwork edge: connectionless serviceThe Network CoreNetwork Core: Circuit SwitchingNetwork Core: Packet SwitchingAccess networks and physical mediaExample access net: home networkWe have seen “pieces” of networkInternet protocol stackLayering: logical communicationLayering: physical communicationInternet structure: network of networksSlide 27Slide 28Slide 291-1CSE 5300: Advanced Computer Networks Bing WangComputer Science & Engineering DepartmentFall 20081-2Course infoInstructor: Bing Wang, [email protected]Office: ITEB 367Lecture: 3:30-4:45pm, TuTh, E2 322Office hours: by appointment1-3Course GoalsWireless networks, basics & advanced topicsa second course: i.e., assumes a first coursedifference & synergy between wired & wireless networks foundational material: longer lifemix of theory and practice1-4Wireless networksWireless LAN, ad-hoc network, wireless mesh, sensor network Internet1-5Other wireless networksCellular networksUnderwater sensor networksVehicular ad-hoc worksDelay/disruption tolerant networksPocket switching networksTurtle networksZebra networksDiesel networks1-6Course Topicsphysical layer basicsMACroutingnetwork simulation, performance analysis network measurement/managementmobilitysecuritycommon themes: randomization, indirection, virtualization, scalability, optimization1-7Course mechanicsclass www site: www.engr.uconn.edu/~bing/cse5300textbook: nonepapers, all posted on www siteprereq: previous course in networkingsome knowledge of probability, optimization theory, algorithmsworkload:3 paper critics2 written homeworks1 programming assignment (on using ns-2)1 semester-long project1-8GradingPaper critics (10%)3 papersHomework (30%)Semester-long project (60%) Goal: hand-on experiences through a well-defined research problemTeam of 2 students Topic (your background, preference)•Fill in background surveyProposal (due 5th class)Midterm report/presentation (14th class)Final report/presentation (last class)1-9Part 0: Networking Review Goals: review key topics from intro networks courseequalize backgroundsidentify remedial work ease into courseOverview:overviewerror controlflow controlcongestion controlroutingLANsaddressingsynthesis:“a day in the life”control timescales1-10What’s a network: “nuts and bolts” viewnetwork edge: millions of end-system devices: pc’s workstations, serversPDA’s, phones, toastersrunning network appsnetwork core: routers, switches forwarding datapackets: packet switchingcalls: circuit switchingcommunication linksfiber, copper, radio, …local netcompanynetregional netrouterworkstationservermobileWeb-enabled toaster+weather forecasterhttp://dancing-man.com/robin/toasty/1-11What’s a protocol?a human protocol and a computer network protocol:HiHiGot thetime?2:00TCP connection req.TCP connectionreply.Get http://www.cse.uconn.edu/index.html<file>time1-12What’s a protocol?human protocols:“what’s the time?”“I have a question”introductions… specific msgs sent… specific actions taken when msgs received, or other eventsnetwork protocols:machines rather than humansall communication activity in Internet governed by protocolsprotocols define format, order of msgs sent and received among network entities, and actions taken on msg transmission, receipt1-13A closer look at network structure:network edge: applications and hostsnetwork core: routersnetwork of networksaccess networks, physical media: communication links1-14The network edge:end systems (hosts):run application programse.g., WWW, emailat “edge of network”client/server modelclient host requests, receives service from servere.g., WWW client (browser)/ server; email client/serverpeer-peer model: host interaction symmetrice.g.: Gnutella, KaZaA1-15Network edge: connection-oriented serviceGoal: data transfer between end systemshandshaking: setup (prepare for) data transfer ahead of timeHello, hello back human protocolset up “state” in two communicating hostsTCP - Transmission Control Protocol Internet’s connection-oriented serviceTCP service [RFC 793]reliable, in-order byte-stream data transferloss: acknowledgements and retransmissionsflow control: sender won’t overwhelm receivercongestion control: senders “slow down sending rate” when network congested1-16Network edge: connectionless serviceGoal: data transfer between end systemssame as before!UDP - User Datagram Protocol [RFC 768]: Internet’s connectionless serviceunreliable data transferno flow controlno congestion controlApp’s using TCP: HTTP (WWW), BitTorrent (file transfer), Telnet (remote login), SMTP (email)App’s using UDP:streaming media, teleconferencing, Internet telephony1-17The Network Coremesh of interconnected routersfundamental question: how is data transferred through net?circuit switching: dedicated circuit per call: telephone netpacket-switching: data sent thru net in discrete “chunks”1-18Network Core: Circuit SwitchingEnd-end resources reserved for “call”link bandwidth, switch capacitydedicated resources: no sharingcircuit-like (guaranteed) performancecall setup required1-19Network Core: Packet Switchingeach end-end data stream divided into packetsuser A, B packets share network resources each packet uses full link bandwidth resources used as needed, resource contention: aggregate resource demand can exceed amount availablecongestion: packets queue, wait for link usestore and forward: packets move one hop at a timetransmit over linkwait turn at next linkBandwidth division into “pieces”Dedicated allocationResource reservation1-20Access networks and physical mediaQ: How to connect end systems to edge router?residential access netsinstitutional access networks (school, company)mobile access networksKeep in mind: bandwidth (bits per second) of access network?shared or
View Full Document