You must have Credits on your Balance to download this sample
Pages 20 (5020 words)
Frame Relay can be thought of as a lightweight descendant of X .25. Here, much of the sophisticated control functionality and facilities found in X .25   are sacrificed for the sake of high speed data transmission. Moreover, identification of the virtual channel now takes place at the lowest part of the data link layer instead of the network layer as in the case of X .25…
This is the reason why the Frame Relay interface does not include an underlying sublayer assigned with error and flow control tasks such as LAP-B in X.25. Subsequently, Frame Relay is suitable for existing private and public networks based on digital TDM transmission systems. This paper is divided into 4 chapters. This is an introductory chapter. Next chapter is dedicated to a review of the literature on the technology. Then comes the methodology part and finally the conclusion.
ISDN represents another ideal carrier for frame relay traffic able to support a number of frame mode bearer services (FMBS). This plurality of frame mode bearer services was considered necessary by the CCITT because Frame Relay may have to be supported over segments of analog technology, at least during the early stages of ISDN.
There are two types of Frame Relay connections: permanent virtual connections (PVCs) and switched virtual connections (SVCs). The establishment, maintenance, and release of PVCs are subject to local management operations. On the other hand, signalling is required to manage SVCs. Of course, dynamically allocated SVCs are much more attractive compared to PVCs which function much like dedicated private lines. At present, the Frame Relay implementations are only PVC-based. ...
Not exactly what you need?