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. This is due to both the complexity of the required signalling  and it s unavailability on the local loop. However, PVCs provide a good immediate solution because LAN-to-LAN interconnectivity is the main Frame Relay application. But the need for products supporting SVCs is growing and a lot of work is being done in this area.
Work on the definition of the Frame Relay interface has been carried out by several organizations during the past years. CCITT has produced a series of standards covering the support of Frame Relay over ISDN, the provision of several Frame Mode Bearer Services (FMBS) and the