1. K. Salah 1 Module 3.0: ATM & Frame Relay

2. K. Salah 2 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

3. K. Salah 3 Protocol Architecture

4. K. Salah 4 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

5. K. Salah 5 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

6. K. Salah 6 ATM Connection Relationships

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

8. K. Salah 8 Call Establishment Using VPs

9. K. Salah 9 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

10. K. Salah 10 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

11. K. Salah 11 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

12. K. Salah 12 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

13. K. Salah 13 ATM Cell Format What is different between UNI and NNI AND WHY?

14. K. Salah 14 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

15. K. Salah 15 Generic Flow Control (GFC) Control traffic flow at user to network interface (UNI) to alleviate short term overload Two sets of procedures – Uncontrolled transmission – Controlled transmission Every connection either subject to flow control or not Subject to flow control Flow control is from subscriber to network – Controlled by network side

16. K. Salah 16 Header Error Control 8 bit error control field Calculated on remaining 32 bits of header Allows some error correction

17. K. Salah 17 HEC Operation at Receiver

18. K. Salah 18 Effect of Error in Cell Header

19. K. Salah 19 Transmission of ATM Cells 622.08Mbps (OC-12) 155.52Mbps (OC-3) 51.84Mbps (OC-1) Cell Based physical layer SDH based physical layer

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

21. K. Salah 21 Cell Delineation State Diagram

22. K. Salah 22 SDH Based Physical Layer Imposes structure on ATM stream e.g. for 155.52Mbps Use STM-1 (STS-3) frame Can carry ATM and STM payloads Specific connections can be circuit switched using SDH channel SDH multiplexing techniques can combine several ATM streams

23. K. Salah 23 STM-1 Payload for SDH-Based ATM Cell Transmission

24. K. Salah 24 ATM Service Categories Real time – Constant bit rate (CBR) – Real time variable bit rate (rt-VBR) Non-real time – Non-real time variable bit rate (nrt-VBR) – Available bit rate (ABR) – Unspecified bit rate (UBR)

25. K. Salah 25 Real Time Services Amount of delay Variation of delay (jitter)

26. K. Salah 26 CBR Fixed data rate continuously available Tight upper bound on delay Uncompressed audio and video – Video conferencing – Interactive audio – A/V distribution and retrieval

27. K. Salah 27 rt-VBR Time sensitive application – Tightly constrained delay and delay variation rt-VBR applications transmit at a rate that varies with time e.g. compressed video – Produces varying sized image frames – Original (uncompressed) frame rate constant – So compressed data rate varies Can statistically multiplex connections

28. K. Salah 28 nrt-VBR May be able to characterize expected traffic flow Improve QoS in loss and delay End system specifies: – Peak cell rate – Sustainable or average rate – Measure of how bursty traffic is e.g. Airline reservations, banking transactions

29. K. Salah 29 UBR May be additional capacity over and above that used by CBR and VBR traffic – Not all resources dedicated – Bursty nature of VBR For application that can tolerate some cell loss or variable delays – e.g. TCP based traffic Cells forwarded on FIFO basis Best efforts service

30. K. Salah 30 ABR Application specifies peak cell rate (PCR) and minimum cell rate (MCR) Resources allocated to give at least MCR Spare capacity shared among all ARB sources e.g. LAN interconnection

31. K. Salah 31 ATM Bit Rate Services

32. K. Salah 32 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

33. K. Salah 33 Adaptation Layer Services Handle transmission errors Segmentation and re-assembly Handle lost and misinserted cells Flow control and timing

34. K. Salah 34 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

35. K. Salah 35 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

36. K. Salah 36 AAL Protocols

37. K. Salah 37 Segmentation and Reassembly PDU

38. K. Salah 38 AAL Type 1 CBR source SAR packs and unpacks bits Block accompanied by sequence number

39. K. Salah 39 AAL Type 2 VBR Analog applications

40. K. Salah 40 AAL Type 3/4 Connectionless or connected Message mode or stream mode

41. K. Salah 41 AAL Type 5 Streamlined transport for connection oriented higher layer protocols

42. K. Salah 42 ITU Classifications is based on whether a timing relationship must be maintained between source and destination whether the application requires a constant bit rate whether the transfer is connection oriented or connectionless.

43. K. Salah 43 Summary of major differences AAL Type 1 supports constant bit rate (CBR), synchronous, connection oriented traffic. Examples include T1 (DS1), E1, and x64 kbit/s emulation. AAL Type 2 supports time-dependent Variable Bit Rate (VBR-RT) of connection-oriented, synchronous traffic. Examples include Voice over ATM. AAL2 is also widely used in wireless applications due to the capability of multiplexing voice packets from different users on a single ATM connection. AAL Type 3/4 supports VBR, data traffic, connection-oriented, asynchronous traffic (e.g. X.25 data) or connectionless packet data (e.g. SMDS traffic) with an additional 4-byte header in the information payload of the cell. Examples include Frame Relay and X.25. AAL Type 5 is similar to AAL 3/4 with a simplified information header scheme. This AAL assumes that the data is sequential from the end user. Examples of services that use AAL 5 are classic IP over ATM, Ethernet Over ATM, SMDS, and LAN Emulation (LANE). AAL 5 is a widely used ATM adaptation layer protocol. This protocol was intended to provide a streamlined transport facility for higher-layer protocols that are connection oriented.

44. K. Salah 44 AAL 5 was introduced to: reduce protocol processing overhead. reduce transmission overhead. ensure adaptability to existing transport protocols. The AAL 5 was designed to accommodate the same variable bit rate, connection-oriented asynchronous traffic or connectionless packet data supported by AAL 3/4, but without the segment tracking and error correction requirements.

45. K. Salah 45 Frame Relay Designed to be more efficient than X.25 Developed before ATM FR had larger installed base than ATM ATM now of more interest on high speed networks

46. K. Salah 46 Frame Relay Background  X.25 Call control packets, in band signaling Multiplexing of virtual circuits at layer 3 Layer 2 and 3 include flow and error control Considerable overhead Not appropriate for modern digital systems with high reliability

47. K. Salah 47 Frame Relay - Differences Call control carried in separate logical connection Multiplexing and switching at layer 2 – Eliminates one layer of processing No hop by hop error or flow control End to end flow and error control (if used) are done by higher layer Single user data frame sent from source to destination and ACK (from higher layer) sent back

48. K. Salah 48 Advantages and Disadvantages Lost link by link error and flow control – Increased reliability makes this less of a problem Streamlined communications process – Lower delay – Higher throughput ITU-T recommend frame relay above 2Mbps

49. K. Salah 49 Protocol Architecture

50. K. Salah 50 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

51. K. Salah 51 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

52. K. Salah 52 User Data Transfer One frame type – User data – No control frame No inband signaling No sequence numbers – No flow nor error control

53. K. Salah 53 What Is Congestion? Congestion occurs when the number of packets being transmitted through the network approaches the packet handling capacity of the network Congestion control aims to keep number of packets below level at which performance falls off dramatically Data network is a network of queues Generally 80% utilization is critical Finite queues mean data may be lost

54. K. Salah 54 Queues at a Node

55. K. Salah 55 Effects of Congestion Packets arriving are stored at input buffers Routing decision made Packet moves to output buffer Packets queued for output transmitted as fast as possible – Statistical time division multiplexing If packets arrive too fast to be routed, or to be output, buffers will fill Can discard packets Can use flow control – Can propagate congestion through network

56. K. Salah 56 Interaction of Queues

57. K. Salah 57 Ideal Performance

58. K. Salah 58 Practical Performance Ideal assumes infinite buffers and no overhead Buffers are finite Overheads occur in exchanging congestion control messages

59. K. Salah 59 Effects of Congestion - No Control

60. K. Salah 60 Congestion Control in Packet Switched Networks Send control packet to some or all source nodes – Requires additional traffic during congestion Rely on routing information – May react too quickly End to end probe packets – Adds to overhead Add congestion info to packets as they cross nodes – Either backwards or forwards

61. K. Salah 61 Mechanisms for Congestion Control

62. K. Salah 62 Backpressure If node becomes congested it can slow down or halt flow of packets from other nodes May mean that other nodes have to apply control on incoming packet rates Propagates back to source Can restrict to logical connections generating most traffic Used in connection oriented that allow hop by hop congestion control (e.g. X.25) Not used in ATM nor frame relay Only recently developed for IP

63. K. Salah 63 Choke Packet Control packet – Generated at congested node – Sent to source node – e.g. ICMP source quench From router or destination Source cuts back until no more source quench message Sent for every discarded packet, or anticipated Rather crude mechanism FR equivalent to XON-XOFF Flow Control

64. K. Salah 64 Implicit Congestion Signaling Transmission delay may increase with congestion Packet may be discarded Source can detect these as implicit indications of congestion Useful on connectionless (datagram) networks – e.g. IP based (TCP includes congestion and flow control) Used in frame relay LAPF

65. K. Salah 65 Explicit Congestion Signaling Network alerts end systems of increasing congestion End systems take steps to reduce offered load Backwards – Congestion avoidance in opposite direction to packet required Forwards – Congestion avoidance in same direction as packet required

66. K. Salah 66 Categories of Explicit Signaling Binary – A bit set in a packet indicates congestion Credit based – Indicates how many packets source may send – Common for end to end flow control Rate based – Supply explicit data rate limit – e.g. ATM

67. K. Salah 67 Traffic Management Fairness Quality of service – May want different treatment for different connections Reservations – e.g. ATM – Traffic contract between user and network

68. K. Salah 68 ATM Traffic Management High speed, small cell size, limited overhead bits Requirements – Majority of traffic not amenable to flow control – Feedback slow due to reduced transmission time compared with propagation delay – Wide range of application demands – Different traffic patterns – Different network services – High speed switching and transmission increases volatility

69. K. Salah 69 Latency/Speed Effects ATM 150Mbps ~2.8x10 -6 seconds to insert single cell Time to traverse network depends on propagation delay, switching delay Assume propagation at two-thirds speed of light If source and destination on opposite sides of USA, propagation time ~ 48x10 -3 seconds Given implicit congestion control, by the time dropped cell notification has reached source, 7.2x10 6 bits have been transmitted So, this is not a good strategy for ATM

70. K. Salah 70 Cell Delay Variation For ATM voice/video, data is a stream of cells Delay across network must be short Rate of delivery must be constant There will always be some variation in transit Delay cell delivery to application so that constant bit rate can be maintained to application

71. K. Salah 71 Network Contribution to Cell Delay Variation Packet switched networks – Queuing delays – Routing decision time Frame relay – As above but to lesser extent ATM – Less than frame relay – ATM protocol designed to minimize processing overheads at switches – ATM switches have very high throughput – Only noticeable delay is from congestion – Must not accept load that causes congestion

72. K. Salah 72 Cell Delay Variation At The UNI Application produces data at fixed rate Processing at three layers of ATM causes delay – Interleaving cells from different connections – Operation and maintenance cell interleaving – If using synchronous digital hierarchy frames, these are inserted at physical layer – Can not predict these delays

73. K. Salah 73 Traffic Management and Congestion Control Techniques Resource management using virtual paths Connection admission control Usage parameter control Selective cell discard Traffic shaping

74. K. Salah 74 Resource Management Using Virtual Paths Separate traffic flow according to service characteristics User to user application User to network application Network to network application Concern with: – Cell loss ratio – Cell transfer delay – Cell delay variation

75. K. Salah 75 Allocating VCCs within VPC All VCCs within VPC should experience similar network performance Options for allocation: – Aggregate peak demand – Statistical multiplexing

76. K. Salah 76 Connection Admission Control First line of defense User specifies traffic characteristics for new connection (VCC or VPC) by selecting a QoS Network accepts connection only if it can meet the demand Traffic contract – Peak cell rate – Cell delay variation – Sustainable cell rate – Burst tolerance

77. K. Salah 77 Usage Parameter Control Monitor connection to ensure traffic conforms to contract Protection of network resources from overload by one connection Done on VCC and VPC Peak cell rate and cell delay variation Sustainable cell rate and burst tolerance Discard cells that do not conform to traffic contract Called traffic policing

78. K. Salah 78 Traffic Shaping Smooth out traffic flow and reduce cell clumping Token bucket

79. K. Salah 79 Token Bucket

80. K. Salah 80 ATM-ABR Traffic Management Some applications (Web, file transfer) do not have well defined traffic characteristics Best efforts – Allow these applications to share unused capacity If congestion builds, cells are dropped Closed loop control – ABR connections share available capacity – Share varies between minimum cell rate (MCR) and peak cell rate (PCR) – ARB flow limited to available capacity by feedback Buffers absorb excess traffic during feedback delay – Low cell loss

81. K. Salah 81 Feedback Mechanisms Transmission rate characteristics: – Allowed cell rate – Minimum cell rate – Peak cell rate – Initial cell rate Start with ACR=ICR Adjust ACR based on feedback from network – Resource management cells Congestion indication bit No increase bit Explicit cell rate field

82. K. Salah 82 ABR and RM Cells ABR: available bit rate: “elastic service” if sender’s path “underloaded”: – Sender should use available bandwidth if sender’s path congested: – Sender throttled to minimum guaranteed rate RM (resource management) cells: Sent by sender, interleaved with data cells Bits in RM cell set by switches (“network-assisted”) – NI bit: no increase in rate (mild congestion) – CI bit: congestion indication RM cells returned to sender by receiver, with bits intact

83. K. Salah 83 Rate Control Feedback EFCI (Explicit forward congestion indication) marking ER (Explicit rate) marking CI (Congestion Indication) NI (No Increase) Two-byte ER (explicit rate) field in RM cell – Congested switch may lower ER value in cell – Sender’ send rate thus minimum supportable rate on path EFCI bit in data cells: set to 1 in congested switch – If data cell preceding RM cell has EFCI set, sender sets CI bit in returned RM cell

84. K. Salah 84 Cell Flow

85. K. Salah 85 ABR Cell Rate Feedback Rules if CI == 1 – Reduce ACR to a value >= MCR else if NI == 0 – Increase ACR to a value <= PCR if ACR > ER – set ACR = max(ER, MCR) ACR = Allowed Cell Rate MCR = Minimum Cell Rate PCR = Peak Cell Rate ER = Explicit Rate