Basic Functionality

Siemens

Basic Functionality

Contents
1 2 3 4 5 6 7 8 9 9.1 9.2 What is Frame Relay? Reasons for Frame Relay Virtual Circuits in Frame Relay Frame Relay Frames Service Parameters Error Detection and Handling Congestion Management PVC Status Management Switched Virtual Circuits (SVCs) UNI signaling NNI Signaling 3 7 11 15 21 27 31 35 43 44 47

Siemens

Basic Functionality

Basic Functionality

Siemens

What is Frame Relay?

Frame Relay?

Fig. 1

TI2430EU01AL-01

Siemens

Basic Functionality

Definition Frame Relay is an extremely fast communications technology used globally in numerous communications networks. It is principally used for LAN, SNA and Internet connections as well as for voice applications. Information flow Fundamentally, in Frame Relay applications the information sent through a wide area network is divided into frames or packets. Each frame is given an address used by the network to find the path to the frame's destination. The frames are transmitted through the switches in the Frame Relay Network to reach their destination. Fast packet switching Frame Relay uses a simple, but fast, form of packet switching. In this way, it is particularly suitable for intelligent terminal equipment such as PCs, workstations and servers, which in turn communicate with each other by means of intelligent protocols like SNA or TCP/IP. In this way, error correction can be transposed to the terminal equipment. The Frame Relay switches themselves only perform error detection and discard faulty frames. The Frame Relay nodes should be connected to each other with lines with a high quality of service in order to keep down the error rate. Summary Viewed overall Frame Relay provides a high rate of data throughput and great operational reliability with low delay times, and is therefore particularly suitable for a wide variety of contemporary business applications.

Basic Functionality

Siemens

PVC PC CPE UNI Controller Router Bridge FRAD MUX Switch ISDN nailed-up connection or ISDN dial-up connection or direct connection (V.35, E1, RS232) Port PVC PVC SVC SVC

PBX

Video

Desktop & LAN Formats packets in frames

Network access Statistical multiplexing

Frame Relay Network

UNI CPE PVC SVC FRAD PBX

Fig. 2

User Network Interface Customer Premises Equipment Permanent Virtual Connection Switched Virtual Connection Frame Relay Access Device Private Branch Exchange

TI2430EU01AL-01

Siemen s

Basic Functionality

Basic Functionality

siemens

Reasons for Frame Relay

~ 1990 New trends in data networks Frame Relay

Fig. 3

TI2430EU01AL-01

Siemens

Basic Functionality

General Frame Relay met with great acceptance from the very beginning because the market exhibited a distinct demand for a fast data transmission technology with a high rate of throughput. The Frame Relay technology uses powerful end devices and digital networks with high grades of service that were already available relatively inexpensively at the time of the introduction of the technology. Consequently, Frame Relay was the right technology at the right time. At the end of the 1980s there were a number of new trends, which when viewed as a whole led to the increase in demand for fast data transmission across wide area networks. Transition from pure text applications to graphical applications Increase in the number of applications producing bursty traffic Intelligent terminal equipment (PCs, workstations, X-Windows terminals) with improved computing performance are already available at low cost More widespread implementation of LAN and client/server applications Broad availability of digital networks.

Greater demand for bandwidth Storage and retrieval of graphics for interactive applications is as common today as the swapping of entire pages of text was in the 1970s and 1980s. Users used to working from an early stage with graphical applications in local networks also of course expect similarly fast response times from wide area networks. As the bandwidth requirements for transfer of graphics are considerably greater than for text transfers, increased bandwidth and data throughput became urgently needed, particularly where fast response times were demanded. Dynamic bandwidth requirements Applications running via LAN typically require large amounts of bandwidth for very short periods. This type of traffic known as bursty traffic is particularly suitable for statistical multiplexing on common physical lines, and is also characteristic of Frame Relay.

Basic Functionality

Siemens

Transition from pure text applications to graphical applications Increase in the number of applications producing bursty traffic Intelligent terminal equipment (PCs, workstations, X-Windows terminals) with improved computing performance are already available at low cost More widespread implementation of LAN and client/server applications Broad availability of digital networks
Fig. 4

Kb

SDLC t (sec) T1 T2 T3 T4 T5 LAN Voice

Fig. 9

TI2430EU01AL-01

Siemens

Basic Functionality

Intelligent terminal equipment The performance of terminal equipment developed along with the changes in network requirements. Falling costs of computing performance led to widespread installation of powerful PCs, workstations and servers that in turn were interconnected by LAN. These new terminal devices also allowed complex data communication protocols to be processed. In other words, the resource-consuming processes for error detection and correction were able to be relocated from data communication networks to the terminal devices. This was a further development in the application of fast packetswitching methods such as Frame Relay. By relieving networks of their error handling processes, Frame Relay provides considerably greater data throughput rates than with conventional packet-switching methods such as X.25. Greater performance The increased use of local networks and the Internet protocol produced a greater demand for the interconnection of the LANs by wide area networks. Initially, attempts were made to intermesh LAN bridges and routers directly with each other with dedicated lines. This could be done provided the networks were small and simply designed. However, with increasing size and complexity of the networks, the disadvantages of this connection methods became evident, namely: Greater transmission costs Low level of operating reliability Limited network management options Restricted diagnostic options in the event of errors. It quickly became clear that the alternative approach of interconnecting LANs in a reliable, manageable wide area network offered distinct advantages: Less overhead than IP Frame relay switching is easy to implement IP switching is rarely available in public WANs IP routing produces delays and requires additional bandwidth. Digital transmission networks The conversion of the public telecommunications infrastructure from analog to digital lines meant greater availability of bandwidth and lower error rates. The error correction mechanisms used by X.25 and SNA (which are particularly suited to handling fault-susceptible analog line) were no longer necessary in wide area networks.

10

Basic Functionality

Siemens

Virtual Circuits in Frame Relay

Virtual Circuits

Fig. 5

TI2430EU01AL-01

11

Siemens

Basic Functionality

General The Frame Relay technology is based on the concept of virtual circuits (VCs). VCs which are usually bi-directional are software-defined paths between two ports and are used as substitutes for nailed-up connections in networks. In contrast to former applications in which only so-called Permanent Virtual Circuits (PVCs) were used, the concept of Switched Virtual Circuits (SVCs) is also used nowadays. Permanent Virtual Circuits (PVCs) PVCs are configured by the network operator by means of a network management system. The two connection end points and the service parameters for the connection must be defined for the configuration. If necessary, a network operator can modify existing PVCs. PVCs are permanently connected paths that are not immediately available when required or on a call-by-call basis. However, in the event of faults, paths can be automatically rerouted in the network; the connection end points remain the same. In this regard, a PVC behaves like a permanently configured point-to-point connection. PVCs are very popular because they represent an inexpensive alternative to nailedup connections. The provisioning of PVCs demands careful planning, knowledge of the traffic profile and the bandwidth utilization. Startup times are therefore needed before the service can be provided and the flexibility is somewhat restricted if only a brief connection duration is required. Switched Virtual Circuits (SVCs) Unlike PVCs, SVCs are available on a call-by-call basis. Analogously to a normal telephone call, an SVC is switched through the network using a signaling protocol. The calling party has to specify a destination address, similar to a telephone number. SVC switching through the network is considerably more complex than is the case for PVCs, but the procedure is transparent for the end user. Simultaneous handling of large numbers of call requests in the network Fast switching of calls with parallel allocation of necessary bandwidths Call monitoring, traffic statistics and billing Although SVCs were already specified on the introduction of Frame Relay, the option was not implemented and supported in the frame relay networks in their initial years. The situation has changed in the meantime and network operators now offer the service. Whereas PVCs use the possible statistical multiplex gains obtained by Frame Relay, SVCs offer dynamic connection options for saving costs and providing more flexibility.

12

Basic Functionality

Siemens

FR network PVC PVC PVC PVC PVC

FR end device supports PVCs

Frame Relay Switch

Fig. 6

FR network E.164 (ISDN/Telephone Numbering Plan) or X.121 (Data Numbering Plan) PVC PVC SVC SVC FR end device supports PVCs and SVCs Frame Relay Switch SVC

Fig. 7

TI2430EU01AL-01

13

Siemens

Basic Functionality

14

Basic Functionality

Siemens

Frame Relay Frames

Flag DLCI DLCI FC CR EA BC DE EA

Payload FCS Flag

Fig. 8

TI2430EU01AL-01

15

Siemens

Basic Functionality

General A Frame Relay frame consists of a header, an information field, and a checksum (frame check sequence) field and is enclosed by flags. Flags All Frame Relay frames must be separated from each other by one or more flags in order to be able to detect the start of a new frame. The flags are one byte long and are set to the binary value 01111110. Frame Relay header The standard Frame Relay header comprises a 10-bit DLCI address and six special function bits. The DLCI address field can be optionally extended. Data Link Connection Identifier (DLCI) In order to distinguish between the frames of different virtual circuits on a link, a connection identifier is needed in the frames themselves. The DLCI field in each Frame Relay header is used for this purpose. Different DLCI values must be specified for different connections for each interface. A DLCI must be provided for each data link connection, but it is only locally significant. DLCI 0 1-15 16-991 992-1007 1008-1022 1023 DLCI 0 1-15 16-1007 1008-1022 1023 Function (ITU-T and ANSI) ITU-T Q.933 Annex A and ANSI T1.617 Annex D Link Management Reserved User Data Link Connections Layer 2 Management for Frame Mode Bearer Service Reserved In Channel Layer 2 Management Function (LMI) Reserved for Call Control (in-channel) Reserved User Data Link Connections Reserved Local Management Interface

16

Basic Functionality

Siemens

FLAG

Frame Relay header

Information field

FCS

DLCI (most significant bits)

C/R

EA

DLCI (least significant bits)

FECN BECN

DE

EA

Fig. 9

DLCI=32 DLCI=16 R DLCI=17 DLCI=16

DLCI=32

DLCI=17

FR-network
DLCI=16 DLCI=21 FRAD R

Virtual circuit R B Router Bridge

Frame Relay network node

Fig. 10

FLAG

TI2430EU01AL-01

17

Siemens

Basic Functionality

Command /Response (C/R) The Frame Relay protocol does not use the C/R bit. It can be used by end users for command/response functionality. Discard Eligibility (DE) If this bit is set, the frame is first discarded on occurrence of congestion in the network. Backward Explicit Congestion Notification (BECN) If this bit is set by a network node, congestion is indicated in the backward direction to the transmitting user. Forward Explicit Congestion Notification (FECN) If this bit is set by a network node, congestion is indicated in the forward direction to the receiving user. Extended Address (EA) This bit is used to limit the address field. In the standard frame format, the EA bit is set to 0 in the first octet and to 1 in the second octet. DLCI/Control Indicator (D/C) The D/C bit indicates whether the remaining 6 bits in the octet are to be interpreted as the least significant DLCI bits (D/C = 0) or as DL-CORE (D/C = 1) control bits. Information field The length of the information field is variable. The field has an integral number of octets. The Frame Relay protocol itself does not interpret the field. The maximum length of the frame is limited. Frame Check Sequence (FCS) The FCS field has two octets. The frame check sequence includes the Frame Relay header and the information field. Transparency To prevent accidental occurrence of a flag or frame abort bit sequence, a zero (0) is inserted after 5 successive "1" bits during transmission. The zero is automatically filtered out by the receiver. Frame Abort A frame can be aborted by transferring at least 7 consecutive "1" bits. The receiver interprets this bit sequence as "frame abort" and ignores the frame currently received.

18

Basic Functionality

Siemens

DLCI (most significant bits)

C/R

EA=0

DLCI

FECN BECN

DE

EA=0

DLCI (least significant bits)

D/C

EA=1

DLCI (most significant bits)

C/R

EA=0

DLCI

FECN BECN

DE

EA=0

DLCI

EA=0

DLCI (least significant bits)

D/C

EA=1

Fig. 11

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

TI2430EU01AL-01

19

Siemens

Basic Functionality

20

Basic Functionality

Siemens

Service Parameters

Fig. 12

TI2430EU01AL-01

21

Siemens

Basic Functionality

Committed information rates and burstiness Bandwidth guarantees (committed information rates) can be given to users for their connections in Frame Relay networks. Moreover, users may be allowed to exceed the guaranteed bandwidth to a certain extent for example, if strongly bursty traffic occurs. Service parameters There are three configurable parameters for defining the guaranteed bandwidth and possible excess bandwidth. The parameters can be set for each Data Link Connection (DLC): CIR (Committed Information Rate) Bc (Committed Burst Size) Be (Excess Burst Size). Two further variables are derived from CIR, Bc and Be: EIR (Excess Information Rate) Tc (Committed Measurement Interval). These service parameters apply to incoming frames in a Frame Relay switch. Consequently, a check can be made for each incoming frame to determine if it complies with the traffic agreement or not. There are two additional service parameters: AR (Access Rate) N203 (Maximum Octet Length of the Frame Relay Information Field).

22

Basic Functionality

Siemens

CIR

Bc

Be

AR Tc EIR

N203

Fig. 13

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TI2430EU01AL-01

23

Siemens

Basic Functionality

Committed Information Rate (CIR) The CIR is the guaranteed data rate in a virtual circuit. The maximum value of the CIR can be the same as the rate available at the access channel (i.e., the access rate). However, the committed rate is usually much less. The CIR is generally set to the average required rate. Committed Burst Size (Bc) Bc is defined as the maximum quantity of data that the network can switch under normal conditions. These frames are not marked with the DE bit. Excess Burst Size (Be) Be is defined as the quantity of data additional to the committed burst size that the network can attempt to switch under normal conditions. The excess burst frames are either marked with the DE bit from the user or at the user interface. Committed Rate Measurement Interval (Tc) The system monitors the number of bits received in a data link connection and can therefore ensure that the CIR is not exceeded. Tc is the duration in which the bit stream is monitored in the DLC. If CIR>0: Tc = Bc (kb)/CIR (kb/s) or if CIR=0: Tc is administratively defined for a specified interval Excess Information Rate (EIR) The EIR is the non-guaranteed rate additional to the CIR that can be used in a virtual circuit. The availability of this rate depends mainly on the usage of the access channel by other virtual circuits. If no excess information rate (additional bandwidth) is currently available, the frames marked with the DE bit are discarded. The excess information rate is calculated as follows: EIR = Be/Tc Access Rate (AR) The access rate is the maximum data rate at which an end device can send or receive in the access channel. Maximum frame length (N203) The length of the Frame Relay information field (N203) is defined by the number of octets between the address field and the frame check sequence field. All networks should support a maximum frame length of at least 1600 bytes.

24

Basic Functionality

Siemens

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

25

Siemens

Basic Functionality

26

Basic Functionality

Siemens

Error Detection and Handling

Flag DLCI DLCI FC CR EA BC DE EA

Payload FCS Flag

Fig. 14

TI2430EU01AL-01

27

Siemens

Basic Functionality

Discarding frames There is a simple rule for keeping Frame Relay as uncomplicated as possible: If there is a problem with a frame, discard it There are two basic causes for discarding a frame: Invalid frame Congestion Invalid frame An invalid frame is a frame that a) is not correctly positioned between two flags b) has less than three octets between the address field and end flag c) does not consist of an integral quantity of octets before insertion of the zero (0) bit or after the zero bit has been filtered out d) indicates a checksum error e) only has a single octet in the frame header f) has a DLCI value that is not supported by the receiver g) has 7 or more consecutive bits set to 1 after insertion of the zero bit or after the zero bit has been filtered out (violation of the transparency or frame abort) h) has an information field that is too long. Invalid frames are discarded without notifying the sender. The end devices are responsible for the error correction. Congestion There are two causes of congestion in a network: Receiver congestion: A network node receives more frames than it can handle. Line congestion: A network node wants to send more frames in a transmission channel than the allocated bandwidth allows. In both cases the buffer areas in the network node are overloaded and frames need to be discarded until sufficient space becomes available in the receive or send buffers again. Since LAN traffic is extremely bursty, the probability of congestion occurring is relatively great. A superior congestion management function is particularly important to minimize the occurrence and effects of congestion. The end devices are again responsible for error correction in these cases.

28

Basic Functionality

Siemens

Invalid frame? CPE FR-Knoten PVC PVC PVC SVC SVC

Congestion ?

Fig. 15

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

TI2430EU01AL-01

29

Siemens

Basic Functionality

30

Basic Functionality

Siemens

Congestion Management

Fig. 16

TI2430EU01AL-01

31

Siemens

Basic Functionality

General The chief objective of Congestion Management is to maintain the specified grade of service (e.g., throughput, delay, frame loss) in the virtual circuits. Congestion Management contains functions for avoiding congestion (Congestion Avoidance). In other words, congestion should be prevented from ever occurring. There are also functions for recovering from existing congestion situations (Congestion Recovery) and for detecting congestion. The congestion functions have the following objectives: To minimize the number of frames discarded To keep the degradation in service quality during congestion to a minimum To be easy to implement and to produce only a minor amount of additional load To equally distribute the resources (memory, bandwidth, processing capacity) between the virtual circuits To prevent congestion from spreading to other network elements To optimize the utilization of the existing network resources To effectively function regardless of the direction the traffic is flowing. The effects of congestion on the service quality is defined by two points. If the traffic exceeds the point A (see diagrams), the delay increases overproportionally. The network element is in a so-called mild congestion state; the quality of the service decreases with increasing traffic volume. From point B the network begins to manage the congestion by discarding frames in order to prevent further degradation in service quality. The network element is in the severe congestion state. Points A and B can usually be defined for specific networks or network elements by setting threshold values. In this way the service quality can be manipulated.

32

Basic Functionality

Siemens

Network Throughput

No congestion within network Region 1

Mild congestion Region 2 B A

Severe congestion Region 3

Congestion Avoidance

Congestion Recovery

Offered load

Fig. 17

No congestion within network Delay Region 1

Mild congestion Region 2

Severe congestion Region 3

Congestion Avoidance
Fig. 3

Congestion Recovery

Offered load

TI2430EU01AL-01

33

Siemens

Basic Functionality

34

Basic Functionality

Siemens

PVC Status Management

Annex D

Annex A LMI

Fig. 18

TI2430EU01AL-01

35

Siemens

Basic Functionality

General

The procedures of the PVC Status Management at the user-to-network interface (UNI) and network-to-network interface (NNI) enable the following: Link integrity verification between the user and network or between networks Notification of the user or network node if a new PVC has been switched Detection by the user or network node that an existing PVC has been canceled Transmission of status information on existing PVCs to users or network nodes There are three slightly different standards for the PVC Status Management: ITU-T: Q.933 Annex A (uses DLCI 0; can be used at the UNI or NNI) ANSI: T1.617 Annex D (uses DLCI 0; can be used at the UNI or NNI) Industrial standard: LMI (uses DLCI 1023; can only be used at the UNI) The procedures for all three standards of the PVC Status Management are based on the replacement of the following message types between the user and network: Status enquiry Status Single PVC asynchronous status
Status enquiry and status messages

"Status Enquiry" and "Status" messages are synchronous handshaking messages for ensuring the connection between the two interfaces of the access channel. At the UNI, a Status Enquiry message is sent in the direction of the network from the user side. The network side replies with a Status message. At the interfaces between networks (NNI), a Status Enquiry message is sent from both sides and the two sides reply with a Status message (bi-directional procedures can also be optionally used at the UNI for example, when connecting a private FR network to a public FR network). Status Enquiry messages always have the same format. Status messages can have two different formats: A "Keep Alive" signal that verifies the connection at the access channel A "Full Status" signal that indicates the status of all virtual circuits in the access channel. The Status Enquiry signal indicates whether a "Keep Alive" or a "Full Status" signal is requested.

36

Basic Functionality

Siemens

Q.933 Annex A T1.617 Annex D LMI Network Status Port Frame Relay network

User

CPE UNI FR network node Status Enquiry

FR network access node or FR customer premises equipment

Fig. 19

Q.933 Annex A bidirectional T1.617 Annex D bidirectional

User+ Network Frame Relay network Port Status

User+ Network Frame Relay network Port

Status Enquiry NNI

FR network node

Status Enquiry Status

FR network node

Fig. 20

37

Siemens

Basic Functionality

Single PVC Asynchronous Status message

This message type is automatically sent without solicitation by the network side at the UNI and NNI whenever the status of a PVC changes (active to inactive or vice versa) or whenever a PVC is canceled. If the status of more than one PVC changes, the message is sent separately for each relevant PVC. Single PVC Asynchronous Status messages have no effect on Status Enquiry and Status messages. TIP: The use and implementation of this message type are optional in the case of the Annex A and Annex D protocols. Network nodes using the LMI protocol in the access channel at the UNI have to be set to "LMI Extended" in order to support Single PVC Asynchronous messages. This message type is known in the LMI protocol as an Update Status message.
System parameters

The accepted value ranges for the configurable parameters are shown in the tables below. The parameters themselves are explained later.
Counter Description Range Default

N391 N392 N393

Full Status Polling Counter Error Threshold Monitored Events Count

1-255 1-10 1-10

6 3 4

N392 must be less than or equal to N393 N391 is always assigned to the user side. N391 is assigned to the user and network sides if the bi-directional procedures are used.
Timer Description Range Default

T391 T392

Link Integrity Verification Polling Timer Polling Verification Timer

5-30 5-30

10 15

T392 should be longer than T391 T391 is always assigned to the user side. T391 is assigned to the user and network sides if the bi-directional procedures are used. T392 is always assigned to the network side. T392 is assigned to the user and network sides if the bi-directional procedures are used.

38

Basic Functionality

Siemens

Status Enquiry Message

Control Field Protocol Discriminator Call Reference Message Type Locking Shift * Identifier Length Report Type Identifier Length Current Sequence Nr. Last Received Seq. Nr.

03 Unnumbered Information Frame /P=0 08 Annex A (09 bei LMI) 00 75 Status Enquiry Nur bei Annex D untersttzt 51 Report (01 bei LMI) 01 00=Full Status/01=Link Integrity Verification 53 Sequence Numbers (03 bei LMI) 02 01-FF 01-FF

Status Message

Control Field Protocol Discriminator Call Reference Message Type Locking Shift * Identifier Length Report Type Identifier Length Current Sequence Nr. Last Received Seq. Nr.

03 Unnumbered Information Frame /P=0 08 Annex A (09 bei LMI) 00 7D Status Enquiry Nur bei Annex D untersttzt 51 Report (01 bei LMI) 01 01 Link Integrity Verification only 53 Sequence Numbers (03 bei LMI) 02 01-FF 01-FF

TI2430EU01AL-01

39

Siemens

Basic Functionality

Full Status Message

Control Field Protocol Discriminator Call Reference Message Type Locking Shift * Identifier Length Report Type Identifier Length Current Sequence Nr. Last Received Seq. Nr. Identifier Length DLCI (msb) DLCI (Isb) Status CIR (msb) CIR CIR (Isb)

03 Unnumbered Information Frame /P=0 08 Annex A (09 bei LMI) 00 7D Status Enquiry Nur bei Annex D untersttzt 51 Report (01 bei LMI) 01 00 Full Status (fr alle PVC) 53 Sequence Numbers (03 bei LMI) 02 01-FF 01-FF 57 PVC Status (7 bei LMI) 03-06 00XXXXXX Most 6 significant bits 1XXXX000 Least 4 significant bits 1000NDAR New/Delete/Active/RNR RNR (Receive Not Ready) und CIR Felder werden bei Annex A und Annex D nicht untersttzt

40

Basic Functionality

Siemens

Single PVC Asynchronous Status Message

Control Field Protocol Discriminator Call Reference Message Type Locking Shift Identifier Length * Report Type * Identifier Length DLCI (msb) DLCI (Isb) Status CIR (msb) CIR CIR (Isb)

03 Unnumbered Information Frame /P=0 08 Annex A (09 bei LMI) 00 7D Status Nur bei Annex D untersttzt 51 Report (7B Update Status bei LMI ext.) 01 * nur bei Annex A und Annex D 02 Single PVC Asynchronous Status 57 PVC Status (7 bei LMI ext.) 03-06 00XXXXXX Most 6 significant bits 1XXXX000 Least 4 significant bits 1000NDAR New/Delete/Active/RNR RNR (Receive Not Ready) und CIR Felder werden bei Annex A und Annex D nicht untersttzt

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

TI2430EU01AL-01

41

Siemens

Basic Functionality

42

Basic Functionality

Siemens

Switched Virtual Circuits (SVCs)

FRF.4/ X.36

CPE

FRF.10/ X.76

FRF.4/ X.36 FRF.4/ X.36 CPE CPE

Fig. 21

TI2430EU01AL-01

43

Siemens

Basic Functionality

9.1 UNI signaling

The calling party sends out a SETUP message to set up a new connection. This message basically contains the following information:
Called party address: specifies an address in a standardized numbering plan such as E.164 or X.121. Link Layer Core Parameter : specifies parameters including throughput, maximum frame size, burst size, etc. which are used by the network to allocate resources for the required connection. End-to-End Parameter: these parameters are optional and specify parameters which are only relevant for communication between the terminal equipment, such as window size and the end-to-end application protocol, for example. These parameters are transmitted transparently through the network. Additional Parameter: specifies additional parameters such as the calling party address, transit network selection, etc.

The SETUP message passes through the network to the called party. The routing is either predetermined by the static configuration of the network node, or the network nodes communicate with one another using a dynamic routing protocol to find possible routes. All nodes along the route taken by the call check whether they can provide enough resources to set up the required connection without impairing existing connections. Should there be any problems with this or the called party, the call is rejected by returning a RELEASE COMPLETE message. If the call is accepted by the called party, the latter returns a CONNECT message to the calling party. This message establishes the end-to-end connection and the DLCIs are also allocated step-by-step for this connection. Between the SETUP and CONNECT messages, other messages can be sent to show the progress of the call. A CALL PROCEEDING message shows that the recipient of the SETUP message has received the message and is processing it. A CONNECT ACKNOWLEDGE message can be returned as a confirmation of receipt of a CONNECT message. The calling party, the called party or a network element involved in the call can release the connection by sending out a DISCONNECT message. The other side responds with a RELEASE message. This message is confirmed step-by-step with a RELEASE COMPLETE message.

44

Basic Functionality

Siemens

Calling DTE ITU-T X.36 FRF.4 CPE UNI Null

SET UP

DCE

DCE ITU-T X.36 FRF.4 Frame Relay Netz

Called DTE

CPE UNI

Null Call Initiated

Call Initiated

ING OCED R P CALL

Null
SET UP

Outgoing Call Call Proceeding Present Incoming Call Proceeding

Null

Outgoing Call Proceeding

ECT CONN

Call G N Present I OCED R P L Incoming CAL CT E N Call N CO Proceeding

Active Active

Active

Active

Fig. 22

TI2430EU01AL-01

45

Siemens

Basic Functionality

Calling DTE ITU-T X.36 FRF.4 CPE UNI Active

DISC O NNE CT

DCE

DCE ITU-T X.36 FRF.4 Frame Relay Netz

Called DTE

CPE UNI

Active Active Active

Disconnect Request

ASE RELE

RELE A COM SE PLET E

Disconnect Request Disconnect Indication

DISC O

NNE CT

ASE RELE

Disconnect Indication Null

Null Null Null

RELE A COM SE PLET E

Fig. 23

46

Basic Functionality

Siemens

9.2 NNI Signaling

ITU T (X.76) Amendment 1

This ITU standard specifies the procedures for Frame Relay SVC signaling at the DCE-DCE interface of Frame Relay data networks. The protocol is similar to the X.36 protocol, but contains additional procedures for managing connections between several networks.
Frame Relay Forum Variant (FRF.10)

The Frame Relay Forum has defined a subset of the ITU-T X.76 specification for use at the NNI interface. The objective of this variant is to achieve the easiest possible implementation to allow early application in networks. This way, for example, the additional facilities of X.76 signaling, such as transit network identification, call identification, closed user group interlock code, reverse charging indication, etc. are not supported.

TI2430EU01AL-01

47

Siemens

Basic Functionality

ITU-T X.76 FRF.10 UNI CPE Calling User Calling STE Null Called STE Originating Network NNI Terminating Network UNI CPE Called User

SETU

Null Call Initiated Call Proceeding Sent

Call Present
CAL

NG CEDI L PRO

Call Proceeding Received

ECT CONN

Active Active

Fig. 24

48

Basic Functionality

Siemens

ITU-T X.76 FRF.10 UNI CPE Calling User Calling STE Active
REL EAS E

NNI Originating Network Terminating Network

UNI CPE Called User Called STE

Active Release indication

Release Request

LETE O MP C E AS RELE

Null Null

Fig. 25

TI2430EU01AL-01

49

Siemens

Basic Functionality

50