1 / 56

CSC 600 Internetworking with TCP/IP

This presentation discusses the protocol architecture and connection management in TCP/IP over ATM networks, including similarities between ATM and packet switching, ATM flow control, and reduced overhead. The presentation also covers the logical planes, control plane, user plane, and ATM hardware.

Download Presentation

CSC 600 Internetworking with TCP/IP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. CSC 600InternetworkingwithTCP/IP Unit 9: TCP/IP over ATM (ch. 18) Dr. Cheer-Sun Yang Spring 2001

  2. Most of the slides were taken from William Stalling’s Book. William StallingsData and Computer Communications Chapter 11 Asynchronous Transfer Mode and Frame Relay

  3. Protocol Architecture • Similarities between ATM and packet switching • Transfer of data in discrete chunks • Multiple logical connections over single physical interface • In ATM flow on each logical connection is in fixed sized packets called cells • Minimal error and flow control • Reduced overhead • Data rates (physical layer) 25.6Mbps to 622.08Mbps

  4. Protocol Architecture

  5. Protocol Architecture

  6. Reference Model Planes • User plane • Provides for user information transfer • Control plane • Call and connection control • Management plane • Plane management • whole system functions • Layer management • Resources and parameters in protocol entities

  7. Control Plane • Between subscriber and network • Separate logical channel used • Similar to common channel signaling for circuit switching services • Data link layer • LAPD (Q.921) • Reliable data link control • Error and flow control • Between user (TE) and network (NT) • Used for exchange of Q.933 control signal messages

  8. User Plane • End to end functionality • Transfer of info between ends • LAPF (Link Access Procedure for Frame Mode Bearer Services) Q.922 • Frame delimiting, alignment and transparency • Frame mux and demux using addressing field • Ensure frame is integral number of octets (zero bit insertion/extraction) • Ensure frame is neither too long nor short • Detection of transmission errors • Congestion control functions

  9. ATM Hardware

  10. Large ATM Networks

  11. The Logical View of an ATM Network

  12. The Logical View of an ATM Network • The goal of ATM is an end-to-end communication system. • ATM hides the details of physical hardware. • ATM hardware provides attached computers with the appearance of a single, physical network.

  13. ATM Logical Connections • Virtual channel connections (VCC) • Analogous to virtual circuit in X.25 • Basic unit of switching • Between two end users • Full duplex • Fixed size cells • Data, user-network exchange (control) and network-network exchange (network management and routing) • Virtual path connection (VPC) • Bundle of VCC with same end points

  14. ATM Connections • ATM provides connection-oriented interface to attached hosts using two paradigms: • Permanent Virtual Circuits • Switched Virtual Circuits

  15. ATM Connections • ATM assigns each circuit a virtual circuit identifier (VCI).

  16. ATM Connection Relationships

  17. Advantages of Virtual Paths • Simplified network architecture • Increased network performance and reliability • Reduced processing • Short connection setup time • Enhanced network services

  18. Call Establishment Using VPs

  19. Virtual Channel Connection Uses • Between end users • End to end user data • Control signals • VPC provides overall capacity • VCC organization done by users • Between end user and network • Control signaling • Between network entities • Network traffic management • Routing

  20. VP/VC Characteristics • Quality of service • Switched and semi-permanent channel connections • Call sequence integrity • Traffic parameter negotiation and usage monitoring • VPC only • Virtual channel identifier restriction within VPC

  21. Control Signaling - VCC • Done on separate connection • Semi-permanent VCC • Meta-signaling channel • Used as permanent control signal channel • User to network signaling virtual channel • For control signaling • Used to set up VCCs to carry user data • User to user signaling virtual channel • Within pre-established VPC • Used by two end users without network intervention to establish and release user to user VCC

  22. Control Signaling - VPC • Semi-permanent • Customer controlled • Network controlled

  23. ATM Cells • Fixed size • 5 octet header • 48 octet information field • Small cells reduce queuing delay for high priority cells • Small cells can be switched more efficiently • Easier to implement switching of small cells in hardware

  24. ATM Cell Format

  25. Header Format • Generic flow control • Only at user to network interface • Controls flow only at this point • Virtual path identifier • Virtual channel identifier • Payload type • e.g. user info or network management • Cell loss priority • Header error control

  26. Transmission of ATM Cells • 622.08Mbps • 155.52Mbps • 51.84Mbps • 25.6Mbps • Cell Based physical layer • SDH based physical layer

  27. Cell Based Physical Layer • No framing imposed • Continuous stream of 53 octet cells • Cell delineation based on header error control field

  28. ATM Adaptation Layer • Support for information transfer protocol not based on ATM • PCM (voice) • Assemble bits into cells • Re-assemble into constant flow • IP • Map IP packets onto ATM cells • Fragment IP packets • Use LAPF over ATM to retain all IP infrastructure

  29. Adaptation Layer Services • Handle transmission errors • Segmentation and re-assembly • Handle lost and incorrectly inserted cells • Flow control and timing

  30. Supported Application types • Circuit emulation • VBR voice and video • General data service • IP over ATM • Multiprotocol encapsulation over ATM (MPOA) • IPX, AppleTalk, DECNET) • LAN emulation

  31. AAL Protocols • Convergence sublayer (CS) • Support for specific applications • AAL user attaches at SAP • Segmentation and re-assembly sublayer (SAR) • Packages and unpacks info received from CS into cells • Four types • Type 1 • Type 2 • Type 3/4 • Type 5

  32. AAL Protocols

  33. AAL Type 1 • CBR source • SAR packs and unpacks bits • Block accompanied by sequence number

  34. AAL Type 2 • VBR • Analog applications

  35. AAL Type 3/4 • Connectionless or connected • Message mode or stream mode

  36. AAL Type 5 • Streamlined transport for connection oriented higher layer protocols

  37. CPCS PDUs

  38. Example AAL 5 Transmission

  39. Segmentation and Reassembly PDU

  40. Datagram Encapsulation and IP MTU Size • IP uses AAL5 to transfer datagrams across an ATM network. • Before data can be sent, a virtual circuit (PVS or SVC) must be in place and both ends must agree to use AAL5 on the circuit.

  41. Datagram Encapsulation and IP MTU Size • To transfer a datagram, the sender passes it to AAL5 along with the VPI/VCI identifying the circuit. • AAL5 generates a trailer, divides the datagram into cells, and transfers the cells across the network. • At the receiving end, AAL5 reassembles the cells, checks the CRC to verify that no bits were lost or corrupted, extracts the datagram, and passes it to IP.

  42. Datagram Encapsulation and IP MTU Size • When TCP/IP sends data across an ATM network, it transfers an entire datagram using ATM Adaptation Layer5. Although AAL5 can accept and transfer packets that contain up to 64K octets, IP must fragment any datagram larger than 9180 octets before passing it to AAL5 according to TCP/IP standard.

  43. Packet Type and Multiplexing • The two computers at the end of a virtual circuit agree a priori that the circuit will be used for a specific protocol (e.g., the circuit will only be used to send IP datagram). • The two computers at the ends of a VC agree a priori that some octets of the data area will be reserved for use as a type field.

  44. IP Address Binding • IP address binding in a non-broadcast multiple access (NBMA) environment can be difficult.

  45. Difficulties RE IP Address Binding • ATM physical address is larger than an IP address • ATM hardware does not support broadcast; ARP cannot be used to resolve address mapping.

More Related