MXPA00009920A - Bearer independent signaling protocol - Google Patents

Abstract

In a telecommunication network, an ATM Adaptation Layer (2) (AAL2) signaling protocol is employed independent of the signaling bearer service being used in transport signaling messages to and from various network entities, such as mobile switching centers, radio network controllers and cell base stations in, for example, a mobile telecommunications network. This is achieved by dividing the functionality of the AAL2 signaling protocol into a number of functional sublayers including an AAL2 Signaling Common Part (CAP), a Bearer Coordination Part (BCP) and a Bearer Adaptor Part (BAP), wherein the BAP adjusts incoming and outgoing messages so that they are compatible with the AAL2 signaling protocol or the underlying signaling bearer service respectively.

Description

"INDEPENDENT CARRIER INDICATION PROTOCOL" BACKGROUND The present invention relates to signaling protocols in telecommunications networks (e.g., mobile networks). More particularly, the present invention relates to a telecommunications network signaling protocol that is independent of the underlying bearer signaling service. Typically, network systems employ what is known in the art as a layered architecture. In a layered architecture, data and / or signaling messages are transferred between entities to peer at the same level of the layer architecture with the help of the services provided by the underlying layers. The messages exchanged between the entities peer at the same level of the layer architecture with the help of the services provided by the underlying layers. The messages exchanged between the peeping entities are generated, prepared in a format, transmitted, received and transported in accordance with the rules described in a protocol specification. The functionality that is provided by an underlying layer for the layer above it, as well as the formatting and coding of the information that is exchanged between the adjacent layers, are described in an interface specification. An interface specification usually describes each function that is provided by the underlying layer in terms of a corresponding service primitive, where each primitive is associated with a specific function or service provided by the underlying layer for the layer just above it. . The information exchanged between the layers is described in terms of parameters in a specific primitive. A simple layer architecture can, from the top to the bottom, include an application layer, a network layer, a data link layer and a physical layer. The function of the application layer is to generate, process and prepare in format the data and / or the signaling that is required to support a specific user application (e.g., cellular voice service). The function of the network layer is to manage the links and the end-to-end relationships between the different network entities, for example, the different mobile switching centers, radio network controllers and base station units in a network cell phone. The data link layer provides a means (i.e., links) for secure data transfer and signaling between adjacent nodes in the network. The physical layer provides services that are required to interconnect with the physical environment, such as coding, modulation, transmission and reception signals. It will be understood that the layered architecture described above may include a signaling layer, wherein the signaling layer actually forms part of the application layer or the network layer. The signaling layer, as the name suggests, generates and receives signaling messages, in accordance with a specific signaling protocol (e.g., Q.2931, PNNI, and B-ISUP). The signaling protocol provides the rules that regulate the generation and format of the signaling messages. The signaling messages, in turn, are used, for example, to establish, maintain and release connections between network entities. It will also be understood that a lower layer network service, such as a bearer signaling service, is required to carry the signaling messages from a sending entity to a receiving entity. Examples of bearer signaling services include the ATM Adaptation Layer service - User Network Interface (SAAL_UNI) and the Message Transfer Service Part 3 (MTP3). Typically, in a layered architecture, the bearer bearer service is associated with the functional layers below the bearer layer. Typically, different networks are employed different bearer signaling services. In addition, the signaling protocols are designed in such a way that they are compatible with a specific bearer signaling service. For example, the ITU UNI signaling protocol (Q.2931) is designed in such a way that it must be carried by the Signaling ATM Adaptation Layer - User Network Interface (SAAL_UNI) signaling bearer service. Likewise, the Private Network-Network Interface (PNNI) signaling protocol must be carried by the service to the signaling bearer SAAL_UNI. However, the Broadband - Integrated Services Digital Network (B-ISDN) User Part (B-ISUP) signaling protocol is designed in such a way that it must be carried by the bearer service of the Message Transfer Party. (MTP3) associated with the Seven Signaling System (SS7). As telecommunication networks continue to overlap, interconnect and share services with each other, using a signaling protocol that is incompatible with all, except a bearer service will become more problematic because it can restrict user access and coverage within certain networks. Therefore, it would be highly desirable to have a signaling protocol that can generate, process and receive signaling messages independent of the underlying bearer signaling service.

COMPENDIUM OF THE INVENTION An object of the present invention is to provide a more flexible signaling protocol architecture. An object of the present invention is to provide a telecommunications network signaling protocol that is capable of generating signaling messages independent of the service to the underlying signaling bearer that is being used to carry the signaling messages. An object of the present invention is to provide a signaling protocol that can be used in conjunction with different telecommunications applications, networks, network segments, and markets, without having to first modify the signaling protocol. Asynchronous Transfer Mode, Adaptation Layer 2 (AAL2) is a well-known mechanism that can be used to transfer the data and signaling information, as described in ITU-T Recommendation Number 1.363.2, "Specification of Adaptation Layer - of ATM B-ISDN ATM, Type 2", September 1997. It is to be expected that AAL2 will soon be used extensively together with different telecommunication applications, networks and markets.In general, the present invention involves an AAL2 signaling protocol that can now be used independently of the underlying bearer service used to establish, maintain and reverse the end-to-end connections AAL 2. This is achieved by dividing the functionality of the AAL2 signaling protocol into a number of functional sublayers: a Common Part of AAL2 signaling (ACP), a Bearer Coordination Part (BCP) and a Bearer Adapter Part (BAP), where_ BCP makes it possible to dynamically switch between different bearer signaling services.The functions carried out by each of these layers will be described in greater detail below In accordance with one aspect of the present invention, the objects above Identified and other objects are achieved by a method to generate signaling messages in accordance with a signaling protocol that is independent of a service to the underlying signaling protador. The method involves generating a signaling message independent of the underlying bearer signaling service to be used for - transport the message to a remote network node, then invoking a service primitive, where the signaling message is a parameter in the service primitive. The method then involves adapting the service primitive so that it is compatible with the subsequent bearer service. In accordance with another aspect of the present invention, the objects identified above and others are achieved by a method for receiving signaling messages in accordance with a signaling protocol independent of an underlying bearer signaling service. This method involves receiving an incoming message in a local network node, regardless of the bearer service underlying signal used to carry the incoming message from a remote network node, where the incoming message is a parameter in a rimitive of entrance service. The method also involves adapting the input service primitive from a format that is compatible with the underlying bearer service to a format that is compatible with the signaling protocol. In accordance with another aspect of the present invention, the objects identified above and others are achieved by an apparatus for generating signaling messages employing an AAL2 signaling protocol that is independent of an underlying bearer signaling service. The apparatus includes a means for generating a message independent of the service to the underlying signaling bearer to be used for transporting the message to a remote network node, and a means for invoking a service primitive, wherein the signaling message is a parameter in the service primitive. The apparatus also includes a means of adapting to the bearer to convert the service primitive from a format that is compatible with the AAL2 signaling protocol to a format that is compatible with the underlying bearer service. In accordance with another aspect of the present invention, objects previously identified and others are achieved by an apparatus for receiving signaling messages that employs an AAL2 signaling protocol that is independent of the service to the underlying signaling bearer. The apparatus includes a means for receiving a separate input message from the underlying bearer signal service, which is used to carry the incoming message from a remote network node to a local network node, where the incoming message is a parameter in an input service primitive. The apparatus also includes a means of adapting to the bearer to adjust the service primitive from a format that is compatible with the service to the underlying bearer to a format that is compatible with the AAL2 signaling protocol.

BRIEF DESCRIPTION OF THE DRAWINGS The objects and advantages of the invention will be understood by reading the following detailed description together with the drawings, in which: Figure 1 shows the layered architecture of the AAL2 signaling protocol of confraternity with a preferred embodiment of the present invention; Figure 2 illustrates the function of representing the primitive map of the Bearer Coordination Part in accordance with the preferred embodiment of the present invention; Figure 3 illustrates a SAAL_UNI adapter; and Figure 4 illustrates the MTP adapter.

DETAILED DESCRIPTION For a better understanding of the invention, the following detailed description refers to the accompanying drawings, wherein the preferred exemplary embodiments of the present invention are illustrated and - describe. In addition, the reference numbers used to identify the key elements of the invention in the drawings are consistent in their entirety. As stated above, the present invention involves an AAL2 signaling protocol that is capable of generating and receiving signaling messages independent of the bearer service underlying signaling. In accordance with a preferred embodiment of the present invention b, this is accomplished by dividing the signaling protocol AAL2 into 3 functional sublayers. Figure 1 shows the architecture at layer 100 for signaling protocol AAL2, in accordance with a preferred embodiment of the present invention, wherein the architecture at layer 100 includes the following three functional sublayers: a Common Part of AAL2 Signaling (ACP) 110, a Bearer Coordination Part (BCP) 120, and a Bearer Adapter Part (BAP) 130. Each of these three functional sublayers will now be described in greater detail. The upper functional sub-layer is the ACP 110.

ACP 110 is essentially responsible for constructing the AAL2 signaling messages, which are used to establish, maintain and release AAL2 connections. In a preferred embodiment, the signaling messages are initially passed to the bearer service of - - signaling through ACP 110. However, in order to transmit and / or receive the signaling messages, the following primitives must be provided via BCP 120 at the interface between ACP 110 and BCP 120: an APPLICATION. TRANSFER_PORTER, an INDICATION. TRANSFER_PORTER, an INDICATION. PAUSE_PORTER, an INDICATION.RESUMEN_PORTER, an INDICATION. CURRENT STATUS_PORTER, a SOLICI UD.INICI CION_PORTADOR, an INDICATION. INICIACION_PORTADOR, a REQUEST. DETENCION_PORTADOR, and an INDICATION. DETENCION_PORTADOR. A primitive APPLICATION. TRANSFER_PORTER, is used to pass the AAL2 signaling messages to the signaling bearer service. The parameters associated with the primitive REQUEST. TRANSFER_ CARRIER is the same signaling message and the AAL2 address of the adjacent AAL2 switch to which the signaling bearer service will transport the message. A primitive INDICATION. TRANSFER_PORTER, is used to supply AAL2 input messages to ACP 110. The parameters associated with a primitive INDICATION. TRANSFER_PORTER are the signaling message and the AAL2 address of the AAL2 switch that last processed the signaling message. A primitive INDICATION. PAUSE_PORTER, is used to inform ACP 110 that another AAL2 switch is not available. The parameter associated with a primitive INDICATION. PAUSE_PORTER is the AAL2 address associated with the AAL2 switch not available. A primitive INDICACIÓN.RESUMEN_PORTADOR, is used to inform ACP 110 that another AAL2 switch, previously known as being inaccessible, is now capable of receiving the signaling messages. The parameter here is the address AAL2 of the AAL2 switch previously unavailable. A primitive INDICATION. CURRENT STATE_PORTER, is used to announce that another AAL2 switch is partially inaccessible because for example, there is congestion of message traffic or the service to the bearer of signaling is unable to make contact with ACP. Again, the parameter is the AAL2 address of the affected AAL2 switch and a cause code. In general, the five primitives identified above are used when the signaling bearer is in service. The following primitives identified below are used to control the status of the bearer signaling service. Unlike the primitives described above, these are not parameters associated with the following primitives. The first is the primitive APPLICATION. INICIACION_PORTADOR, which requests that the service to the bearer of signaling change to the CONNECTED state. The second is the primitive INDICATION. INTTIACION_PORTADOR, which reveals that the service to the bearer of signaling is ready to transport the AAL2 messages. The third is the primitive REQUEST.DETENTION_PORTER, which requests that the bearer service be signaled to change to a DISCONNECTED state. The last one is the primitive INDICATION. DETENCION_PORTADOR that reveals that the service to the bearer of signaling is now out of service and is unable to transfer messages. Figure 2 illustrates the mapping function (ie, distribution) that is provided by the BCP 120. As shown, the BCP 120 maintains the variable state 205 named TYPE_PORTER. The variable state 205 identifies the bearer service (e.g., SAAL_UNI) that is used to carry the signaling messages. Upon receipt of a primitive 210 (eg, a primitive APPLICATION TRANSFER_PORTER) through its upper interface with ACP 110, BCP 120 moves the primitive 210 to a specific bearer primitive (eg, a REQUEST.TRANSFERENCE SAALJNI_ADAPER_220) by directing the message to the adapter. carrier service is appropriately signaled in BAP 130, in accordance with state variable 205. It should be noted that state variable 205 is established based on the information it receives from BCP 120 of the system administration. In addition, state variable 205 can be readjusted by administering the system at any time, thereby causing BCP 120 to begin redirecting signaling messages to a different bearer signaling service adapter without affecting the operation of the protocol. of signaling same. The main function of BAP 130 is to adapt or adjust a signaling message so that it becomes compatible with a proposed service of a number of services to the bearer of signaling. Accordingly, BAP 130 includes a number of adapters to the signaling bearer. In Figure 2, three exemplary bearer carrier adapters are illustrated: an MTP adapter 225, a SAAL_UNI adapter 230, and an IP adapter 235. However, it will be understood that additional adapters related to other underlying bearer signaling services may be provided. . Adapting a signaling message in a way that is compatible with the bearer service, the proposed signaling may involve moving the corresponding primitive, and may involve adding or deleting the parameter information depending on - of the message and / or the service to the specific signaling bearer. Figure 3 illustrates the SAAL_UNI 230 adapter in greater detail. More specifically, Figure 3 shows the different input and output primitives associated with the upper layer interface 305 between the adapter SAALJJNI 230 and BCP 120. Figure 3 also shows the different input and output primitives associated with the lower layer interface 315 between the SAAL_UNI 230 adapter and the bearer service SAAL_UNI 310. More importantly, Figure 3 illustrates how the SAAL_UNI 230 adapter processes the different input and output signaling messages. For example, the adapter SAAL_UNI 230 will prepare on a map a primitive REQUEST. TRANSFER SAAL_UNI_ADAPTADOR towards the primitive APPLICATION.AW_DATA. However, only the signaling message itself is transferred. The AAL2 address is discarded. It is discarded because SAAL_UNI is a link-level signaling bearer service based on connection, as will be appreciated by those skilled in the art. Consequently, there are only two AAL2 switches associated with the connection, that is, one at either end of the connection. In this way, a signaling message sent by a switch AAL2 can only be transported to the other switch AAL2 placed at a remote end of the connection. There are no other possible destinations. Therefore, there is no requirement to include an AAL2 address among the parameters associated with the primitive APPLICATION., so that the AAL2 address is discarded as shown. Similarly, the SAAL NI 230 adapter will prepare a map of a primitive INDICACION.ALL_DATO to a primitive INDICATION. SAAL_UNI_ADAPTADOR_TRANSFERENCIA. However, the parameter associated with the primitive REQUEST.ALL_DATA includes only the signaling message to be transferred. Because the AAL2 signaling protocol expects the primitive to include both the signaling message and the AAL2 address as parameters, the SAAL_UNI 230 adapter adds the AAL2 address, as shown in Figure 3. The AAL2 address is stored in a variable status REMOTE_EXTREME 320, after the connection to the bearer SAAL_UNI is first established. The primitives INITIATION, DETENTION, RELEASE and SETUP are prepared on a map using the SAAL_UNI 230 adapter as shown. It should be noted that no further processing is required, since there are no parameters associated with these primitives. It should also be noted that the SAAL_UNI 230 adapter never invokes an INDICATION. SAAL_UNI_ADAPTADOR_PAUSA, an INDICATION. SAAL_UNI_ADAPTADOR_RESUMEN, or an INDICATION. SALL_UNI_ADAPTADOR_ESTADO ACTUAL, since the bearer service SAAL_UNI does not provide any functions related to these primitives. Figure 4 shows the MTP adapter 225 in greater detail, as well as the different input and output primitives associated with the upper interface 410 between BCP 120 and the MTP adapter 225, and the input and output primitives associated with the lower interface 420 between the MTP 225 adapter and the MTP3 signaling bearer. Usually the MTP 225 adapter carries out the address transfer; the extension of the message as required to insert and remove the MTP3 routing labels; and the preparation of primitive maps. Unlike SAAL_UNI, MTP3 is a carrier that provides a packet transport service. Accordingly, the message packets are routed from one sending entity to one of the many possible receiving entities based on the address information contained in the message packet. As such, MTP3 does not require connection establishment. Consequently, MTP3 does not use the primitives INITIATION and DETENTION. However, this is not important as far as - l it is related to the signaling protocol AAL2, which continues invoking INITIATION. APPLICATION and DETENTION. REQUEST that the primitives are and continue to wait in response to the primitive INITIATION. INDICATION and DETENTION. INDICATION. To accommodate the AAL2 signaling protocol, and to ensure that the AAL2 signaling protocol is truly independent of the bearer, the MTP adapter 225, upon receiving an INITIATION primitive. APPLICATION or a DETENTION. REQUEST through its upper interface 410 returns to a primitive INITIATION. INDICATION or one of DETENTION. INDICATION respectively without actually forming on a map any primitive to or from its lower interface 420. Since MTP3 is a packet transport service, as stated above, it depends on the information of origin point and destination point so that it can properly route the messages to and from the proposed AAL2 nodes. In accordance with a preferred embodiment of the present invention, each MTP node in the SS7 network maintains its own unique point code (OPC) 430, where OPC 430 is used to identify the MTP node from which a signaling message originates. In addition, each MTP adapter, for example, the MTP 225 adapter, maintains an address transfer box 440. The address transfer box 440 - provides a list of each AAL2 address associated with the adjacent AAL2 node in the ALL2 network, along with the destination point code (DCP) associated with the MTP node corresponding to each of the adjacent AAL2 nodes. The MTP adapter 225 uses this information to process the message transfer primitives and flow control primitives as will be explained in more detail below. When the MTP adapter 225 receives a primitive REQUEST.MTP_TRANSFER_ADAPER from BCP 120, through its upper interface 410, it analyzes the address parameter to identify the address AAL2 of the adjacent switch AAL2 to which the output message is to be transferred. Since MTP3 depends on the DPCs instead of the AAL2 address, the MTP adapter 225 uses the address transfer box to identify the DPC that corresponds to the address AAL2 in the parameter. The MTP 225 adapter then replaces the AAL2 address in the corresponding DPC parameter as shown in Figure 4. In addition, the MTP 225 adapter sets its OPC, as shown in Figure 4, as required by the service to the MTP3 signaling bearer. In contrast, the OPC and DPC are removed from the parameter- for the input primitives of TRANSFER. INDICATION as shown.

- - The protocol used by the MTP3 bearer service requires two additional codes that are present as parameters of a TRANSFER primitive. REQUEST. These two additional codes are the Signal Link Selection (SLS) code and the Signaling Information Octet (SIO) code. The subject of these two additional codes will now be described in greater detail. The signaling bearer MTP3 supports more than one link between the adjacent signaling nodes in the network. Typically, the message traffic is equally distributed through the different links. By doing so, the message transfer capacity is increased and the service is more robust since alternative routes are available for message traffic when one or more links are inoperative. The appropriate coding of the SLS code helps the MTP3 layer to equally distribute the message traffic through the available links. However, sometimes messages must reach their destination in a specific sequence. To ensure that this occurs, messages must be transported along the same route between the signaling nodes. By setting the SLS code to the same value for each of a number of messages, the SLS code helps to ensure that messages are transported through the same route, in sequence, through the bearer service MTP3. As shown in Figure 4, the MTP adapter 225 sets the SLS to the parameter associated with the TRANSFER output primitives. REQUEST and remove them from the parameter associated with the input primitives TRANSFER. INDICATION This SIO code is used to identify the specific MTP3 user. In the present case, for example, the SIO code identifies the AAL2 signaling protocol as an MTP3 user. As shown in Figure 4, the MTP 225 adapter inserts the SIO code as a parameter in each output primitive TRANSFER. REQUEST, and remove the parameter of each TRANSFER input primitive. INDICATION. In addition to handling the primitive INITIATION, STOP, and TRANFERENCE, the MTP adapter must also handle certain input flow control primitives. These include MTP3_PAUS. INDICATION, MTP3_RESUMEN. INDICATION, and MTP3_STATE CURRENT. INDICATION. Upon receiving any of these three types of flow control primitive from the MTP3 bearer service, the MTP adapter 225 first determines whether the DPC parameter in the primitive is present in the address transfer box 440. If the DPC is present in the address transfer box 440, this indicates that the message was emanated from an adjacent AAL2 switch. The MTP adapter 225 then identifies the corresponding AAL2 address in the address transfer box 440 and inserts it as a parameter in the primitive, as required by the AAL2 protocol. In the case of a primitive MTP3_STATE CURRENT. INDICATION, a cause code provided by the MTP3 signaling bearer service is also specified as a parameter. However, if DPC has not been listed in the address transfer box 440, the MTP adapter 225 discards the message as received from the non-adjacent AAL2 switch, and is unusable by the AAL2 signaling protocol. Although a preferred embodiment of the present invention has been described with respect to bearer services, SAAL_UNI and MTP3 are indicated, it will be understood that other modalities that include adapters related to other services to the bearer of signaling are feasible. Other candidate bearer services include IP bearer services, TCP / IP and SAAL_NNI. The present invention has been described with reference to a preferred embodiment. However, it will be readily apparent to those skilled in the art that it is possible to encompass the invention in specific forms other than those described above without departing from the spirit of the invention. The preferred embodiment is illustrative and should not be considered restrictive in any way. The scope of the invention is provided by the appended claims rather than the foregoing description, and all variations and equivalents that fall within the scale of the claims are intended to be encompassed herein.

Claims (40)

1. CLAIMS: 1. In a telecommunications network, a method for generating signaling messages in accordance with a signaling protocol that is independent of the underlying bearer signaling service, the method comprises the steps of: generating a signaling message independent of the bearer signaling service underlying to be used to transport the message to a remote network node; invoke a service primitive, where the signaling message is a parameter in the service primitive; and adapting the service primitive so that it is compatible with the service to the underlying bearer. The method of claim 1, further comprising the step of: distributing the service primitive to one of a plurality of adapters to the bearer, wherein each of the plurality of adapters to the bearer corresponds to a bearer signaling service different. - 3. The method of claim 1, wherein the bearer bearer service is a bearer service SAAL_UNI. The method of claim 3, wherein the step of adapting the service primitive so that it is compatible with the underlying bearer signal service comprises the step of: removing an address parameter from the service primitive, where the address parameter is associated with the remote network node. The method of claim 3, wherein the step of adapting the service primitive so that it is compatible with the service to the underlying bearer comprises the steps of: preparing a map of a primitive of TRANSFER. REQUEST to a primitive of DATA. REQUEST; and send the DAT primitive. APPLICATION to the service of the signaling carrier SAAL_U I. 6. The method of claim 3, further comprising the steps of: invoking a primitive STOP. REQUEST; prepare a map of the primitive DETENTION. REQUEST to a primitive of LIBERATION. REQUEST; Y - send the primitive of LIBERATION. APPLICATION to the service of the signaling carrier SAAL_UNI. The method of claim 3 further comprising the steps of: invoking an INITIATION primitive. REQUEST; Prepare a map of the INITIATION primitive. REQUEST to a primitive to ESTABLISH. REQUEST; and send the primitive to ESTABLISH. APPLICATION to the service of the signaling carrier SAAL_UNI. The method of claim 1, wherein the signaling bearer service is a bearer service MTP3. The method of claim 8, wherein the step of adapting the service primitive so that it is compatible with the underlying bearer signal service comprises the step of: inserting an identification code into the service primitive, such as a parameter, where the identification code corresponds to an MTP node that is responsible for issuing a signaling message. The method of claim 8, wherein the step of adapting the service primitive so that it is compatible with the service to the underlying bearer comprises the steps of: identifying an address parameter in the service primitive, wherein the address parameter corresponds to a remote network node; using the address parameter to secure an identification code for an MTP node associated with the remote network node; and replace the address parameter with the identification code. The method of claim 8, wherein the step of adapting the service primitive so that it is compatible with the service to the underlying bearer comprises the step of: inserting a link selection code into the service primitive, as a parameter, wherein the link selection code identifies one of a plurality of links through which the message may be transported to the remote network node. The method of claim 8, wherein the step of adapting the service primitive to be compatible with the service of the underlying signaling bearer comprises the step of: inserting a signaling information code into the service primitive, as a parameter, wherein the signaling information code identifies the signaling protocol as an MTP user. 13. The method of claim 8, wherein the step of adapting the service primitive so that it is compatible with the service of the underlying bearer comprises the steps of: preparing a primitive of a map in a map; MTP_ADAPTADOR_TRANSFERENCIA. REQUEST in a primitive of MTP3_TRANSFERENCIA. REQUEST; and send the primitive of MTP3_TRANSFERENCE. REQUEST to the service of the MTP3 carrier. The method of claim 8, further comprising the steps of: invoking a STOP primitive. REQUEST; prepare a map of the primitive DETENTION. REQUEST to a primitive DETENTION. INDICATION; and send the primitive DETENTION. INDICATION back to the message generation medium. The method of claim 8, further comprising the steps of: invoking an INITIATION primitive. REQUEST; Prepare a map of the INITIATION primitive. APPLICATION to a primitive INITIATION. INDICATION; and send the primitive INITIATION. INDICATION back to the message generation medium. 16. In a telecommunications network, a method for receiving the signaling messages in accordance with a signaling protocol independent of the underlying bearer signaling service, the method comprises the steps of: receiving an input message in a local network node, independently of the underlying signaling bearer service used to carry the input message from a remote network node, wherein the input message is a parameter in an input service primitive; and adapting the input service primitive from a format that is compatible with the service to the underlying signaling bearer to a format that is compatible with the signaling protocol. The method of claim 16 further comprising the step of: distributing the service primitive from one of a plurality of bearer adapters to the signaling protocol, wherein each of a plurality of bearer adapters corresponds to a service of different signaling bearer. 18. The apparatus of claim 16, wherein the bearer service signaling is a bearer service SAAL UNI. 19. The method of claim 18, wherein the step of adapting the input service primitive from a format that is compatible with the service of the underlying bearer to a format that is compatible with the signaling protocol comprises the step of: an address in the service primitive; as a parameter, where the address is associated with the remote network node. The method of claim 18, wherein the step of adapting the input service primitive from a format that is compatible with the underlying bearer signal service to a format that is compatible with the signaling protocol comprises the steps of : to form on a map a primitive of DATA. INDICATION to a TRANSFER primitive. INDICATION; and send the TRANSFER primitive. INDICATION to the medium receiving the input message. The method of claim 18 further comprising the steps of: forming a map of a RELEASE primitive. INDICATION to a primitive DETENTION. INDICATION; - 3 form a map of a primitive of LIBERATION. CONFIRM a primitive DETENTION. INDICATION; and send the DETENTION. INDICATION to the medium receiving the input message. 22. The method of claim 18 further comprising the steps of: forming a map of a SET primitive. INDICATION to a primitive of INITIATION. INDICATION; form a map of a primitive of ESTABLISH. CONFIRM . a primitive of INITIATION. INDICATION; and send the primitive INITIATION. INDICATION to the medium receiving the input message. The method of claim 16, wherein the bearer bearer service is a bearer service MTP3. The method of claim 23, further comprising the step of: removing an identification code parameter from a second service primitive, wherein the identification code corresponds to an MTP node associated with the remote network node. - 25. The method of claim 24, further comprising the steps of: using the identification code to identify an address corresponding to the remote network node; and inserting the address corresponding to the remote network node to the service primitive, as a parameter, instead of the identification code parameter. 26. The method of claim 25, wherein the second service primitive is a primitive of PAUS. INDICATION. 27. The method of claim 25, wherein the second service primitive is a SUMMARY primitive. INDICATION. 28. The method of claim 25, wherein the second service primitive is a CURRENT STATUS primitive. INDICATION. The method of claim 23, wherein the step of adapting the service primitive from a format that is compatible with the underlying bearer service to a format that is compatible with the signaling protocol comprises the step of: removing a parameter of the identification code from the service primitive, where the identification code corresponds to the remote network node. - 30. The method of claim 23, wherein the step of adapting the service primitive from a format that is compatible with the service to the underlying bearer to a format that is compatible with the signaling protocol comprises the step of: removing a parameter of the identification code from the service primitive, where the identification code corresponds to the local network node. The method of claim 23, wherein the step of adapting the service primitive from a format that is compatible with the underlying bearer signal service to a format that is compatible with the signaling protocol, comprises the step of: removing a link selection code parameter from the service primitive, wherein the link selection code identifies a link through which the input message was transported from the remote network node. 32. The method of claim 23, wherein the step of adapting the service primitive from a format that is compatible with the service of the underlying bearer to a format that is compatible with the signaling protocol comprises the step of: removing a signaling information code parameter from the service primitive, where the - 3 The signaling information code identifies the signaling protocol as an MTP user. 33. In a telecommunications network, an apparatus for generating signaling messages employing an AAL2 signaling protocol that is independent of a service to the underlying signaling bearer, the apparatus comprises: a means for generating a message independent of the bearer service of underlying signal to be used to transport the message to a remote network node; means for invoking a service primitive, wherein the signaling message is a parameter in the service primitive; and a means of adapting to the bearer that converts the service primitive from a format that is compatible with the AAL2 signaling protocol to a format that is compatible with the underlying bearer signaling service. 34. The apparatus of claim 33 further comprising: a bearer service coordination means for distributing the service primitive containing the signaling message from the message generating means to one of the plurality of bearer adaptation means , wherein each of the plurality of means for adapting the carrier corresponds to a different signaling bearer service. 35. The apparatus of claim 33, wherein the signaling bearer service is a service of the bearer SAAL_UNI and the bearer adaptation means is a SAAL_UNI adapter. 36. The apparatus of claim 33, wherein the bearer signaling service which is an MTP3 bearer service and the bearer adaptation means is an MTP adapter. 37. In a telecommunications network, an apparatus for receiving signaling messages employing an AAL2 signaling protocol independent of an underlying bearer signaling service, the apparatus comprising: means for receiving an input message independent of the underlying bearer signaling service that is used to carry the input message from a remote network node to a local network node, where the input message is a parameter in an input service primitive; and a means of adapting to the bearer to adjust the service primitive from a format that is compatible with the service to the underlying bearer of signaling I to a format that is compatible with the signaling protocol with AAL2. - 3( 38. The apparatus of claim 37 further comprising: a bearer service coordination means for distributing the service primitive from one of a plurality of bearer adaptation means to an incoming message receiving means, wherein each of the plurality of means of adaptation to the bearer corresponds to a different bearer signaling service. 39. The apparatus of claim 37, wherein the signal bearer service is a bearer service SAAL__UNI and the bearer adaptation means is a SAAL NI adapter. 40. The apparatus of claim 37, wherein the signal bearer service is a bearer service MTP3 and the bearer adaptation means is an MTP adapter.