Fig. 7A company's data network should be designedso as to permit both existing <strong>and</strong> future applicationsto use the same physical networkBox 1St<strong>and</strong>ardisation of <strong>Frame</strong> <strong>Relay</strong><strong>Frame</strong> <strong>Relay</strong> as a communications st<strong>and</strong>ard wasfirst proposed by CCITT in the late 80's <strong>and</strong> thenpresented in Recommendation 1.122. At that time,the US st<strong>and</strong>ardisation body ANSI had also beganto take an interest in this field, but the resultof both bodies' work was rather long in coming.Northern Telecom, DEC, CISCO, <strong>and</strong> Stratacomthere<strong>for</strong>e took the matter in their own h<strong>and</strong>s, submittingat the end of 1990 a proposal <strong>for</strong> a st<strong>and</strong>ardbased on the existing - but still incomplete -proposals drawn up by CCITT <strong>and</strong> ANSI. This proposalalso contained a "Local Management Interface",LMI, which describes the exchange of in<strong>for</strong>mationon link status between the DTEs <strong>and</strong>the network. To complete the work <strong>and</strong> <strong>for</strong>ce thepace of st<strong>and</strong>ardisation, <strong>Frame</strong> <strong>Relay</strong> Forum wasestablished in January, 1991.<strong>More</strong> than 70 companies including Ericsson arenow members of <strong>Frame</strong> <strong>Relay</strong> Forum, which doesnot do any st<strong>and</strong>ardisation work of its own but submitsproposals to existing st<strong>and</strong>ardisation bodiessuch as CCITT, ANSI <strong>and</strong> ETSI. The <strong>for</strong>mation of<strong>Frame</strong> <strong>Relay</strong> Forum speeded up the st<strong>and</strong>ardisationwork, <strong>and</strong> the CCITT <strong>and</strong> ANSI st<strong>and</strong>ardshave now reached an appreciable degree of development,including the specification of LMI functionality.CCITT's recommendations include I.223 (whichdescribes the service), Q.922 (describing theframe) <strong>and</strong> 0.933 (signalling). ANSI's versions ofthese st<strong>and</strong>ards, which are basically equivalent tothose specified by CCITT, are called T1.606 (theservice), T1.618 (frame) <strong>and</strong> T1.617 (signalling).(PVC) <strong>and</strong> Virtual Connections (VC). ThePermanent Virtual Connection is a networkpath which is predefined by the networkoperator. The procedure <strong>for</strong> setting up aVirtual Connection includes indication ofthe address by means of a Network TerminalNumber, which is unique to each setof equipment connected. No network operatoris involved in this set-up procedure,which results in the establishment of a networkpath that remains connected until thesender or receiver orders its release.The X.25 protocol is based on the store<strong>and</strong>-<strong>for</strong>wardprinciple. Packets enteringthe network are stored in a buffer <strong>and</strong>passed on in the order of their arrival. Thetransfer over each individual link is monitoredseparately, <strong>and</strong> an error results in initiationof retransmission on the link. In thisway, correct data transfer is possible evenin networks with heavily disturbed connections.There is one disadvantage, however;the protocol h<strong>and</strong>ling requires muchprocessing power, which causes delay<strong>and</strong> limits the available transfer speed. Today,a typical X.25 network cannot efficientlyutilise link speeds above 64 kbit/s.But the development towards higher transmissionspeed is evident in the X.25 networks,too, <strong>and</strong> follows the developmentof microprocessor capacity.Due to their limited transmission speed,X.25 networks have not been consideredeffective enough <strong>for</strong> the interconnection ofLANs in a wide-area environment. Pointto-pointconnections have been preferredwhen high transmission speed has beenthe prime requirement. Although point-topointconfigurations provide the requiredtransmission speed, they are not usuallycost-effective. The reason <strong>for</strong> this is thatLAN interconnect applications generatedata in the <strong>for</strong>m of bursts; that is, they utilisethe available capacity <strong>for</strong> very short periodsonly. In fact, the connections are passivemost of the time, resulting in a low degreeof utilisation.Network solutions of today <strong>and</strong>tomorrowThe new <strong>and</strong> the traditional, centraliseddatacom environments usually coexist ina company's organisation. Today, manycompanies there<strong>for</strong>e have a datacom environmentmade up of separate infrastructures.A uni<strong>for</strong>m communications environmentmust be able to meet the needs ofboth LAN-to-LAN connections <strong>and</strong> of thelarge number of terminals connected tohost computers, Fig. 7.<strong>Frame</strong> <strong>Relay</strong> - a newalternative in datacommunicationsThe purpose of introducing <strong>Frame</strong> <strong>Relay</strong>is to meet the new requirements, <strong>and</strong> mainlythose resulting from the development ofLAN-to-LAN communications. The st<strong>and</strong>arddefines a simplified packet switchingservice which meets the need <strong>for</strong> a simpleFig. 8The <strong>Frame</strong> <strong>Relay</strong> st<strong>and</strong>ard specifies an interfacebetween a user <strong>and</strong> a <strong>Frame</strong> <strong>Relay</strong> networkERICSSON REVIEW No. 1-2, 1992
Fig. 9A typical <strong>Frame</strong> <strong>Relay</strong> network with DTEs, networknodes <strong>and</strong> public <strong>Frame</strong> <strong>Relay</strong> servicesFig. 10<strong>Frame</strong> <strong>Relay</strong> networks use permanent virtualconnections, which means that a physical connectioncan provide several logical channels <strong>for</strong>simultaneous usedata transmission protocol focusing onhigh speed <strong>and</strong> requiring a minimum oferror-correcting <strong>and</strong> flow-controlling functions.The st<strong>and</strong>ard, which is described in bothCCITT <strong>and</strong> ANSI recommendations, definessignal <strong>and</strong> data transmission at linklevel, OSI level 2, in the interface betweenuser equipment <strong>and</strong> network, Fig. 8. (Cf.X.25, which comprises the first three OSIlevels <strong>and</strong> uses a frame at level 2 <strong>for</strong> thetransmission of a packet at level 3.) Thest<strong>and</strong>ardisation work is briefly described inBox 1.How <strong>Frame</strong> <strong>Relay</strong> worksA <strong>Frame</strong> <strong>Relay</strong> network is made up of networknodes <strong>and</strong> user equipment, DTE.s(Date Terminal Equipment) connected tothe network. The DTE, e.g., a personalcomputer, a gateway, a router or a hostcomputer, is provided with the interfacedefined <strong>for</strong> <strong>Frame</strong> <strong>Relay</strong>, Fig. 9.The sending DTE transmits frames to thenetwork. Each of these frames contains anidentification code (<strong>Data</strong> Link ConnectionIdentifier, DLCI). All network nodes alongthe path to the final destination contain in<strong>for</strong>mationindicating the outgoing channelto which a frame with a specific identificationcode is to be sent. The path betweenthe sending <strong>and</strong> receiving DTEs has beenpredefined by the network operator. Thistype of connection - a Permanent VirtualConnection - is so far the only one definedin the st<strong>and</strong>ard. Virtual connections are notincluded in today's <strong>Frame</strong> <strong>Relay</strong> function,but future versions of the protocol are expectedto allow such connections too.The network node routes to the right destinationsthe frames sent from a DTE. Thenetwork node reads the identification codeof the incoming frame <strong>and</strong> sends the frame(without changing it) on the outgoing channelindicated in the node's routing table.This outgoing channel can either be a connectionto another network node (in whichcase the procedure described above is repeated)or a connection directly to the terminatingDTE. However, the way theframes are h<strong>and</strong>led internally in the networkis not defined in the st<strong>and</strong>ard.As in X.25 switching, the use of severalidentification codes permits several parallelsessions in different directions to coexiston one physical connection, Fig. 10.In this way, a DTE can communicate simultaneouslywith different destinationsover the same physical connection to thenetwork. This is necessary if the DTE is acommunications port in an LAN, but it is alsoan attractive solution in cases where theDTE is a personal computer or workstationthat uses several simultaneously activewindows.H<strong>and</strong>ling is simple because the protocoldoes not include any error-correctingmechanism. Speeds of several Mbit/s canbe used without requiring unreasonableprocessing capacity <strong>for</strong> link h<strong>and</strong>ling.Today's version of the st<strong>and</strong>ard stipulatesa maximum link transmission speed ofERICSSON REVIEW No. 1-2, 1992