Abstract:
The present invention relates to a method and network element for providing linkset-related SS7 network functions based on M3UA messages. In particular the present invention provides a method and a signaling gateway ( 108 ) for implementing screening based on M3UA messages by mapping M3UA connections to pseudo linksets ( 116 ) to which linkset-related rules can then be applied.

Description:
CROSS REFERENCE TO RELATED APPLICATIONS  
       [0001]     This application claims priority to the European application No. 04022108.7, filed Sep. 16, 2004 and which is incorporated by reference herein in its entirety.  
       FIELD OF INVENTION  
       [0002]     The present invention relates to a method and network element for providing linkset-related SS7 network functions based on M3UA messages. In particular the present invention provides a method and a signaling gateway for implementing screening based on M3UA messages.  
       SUMMARY OF THE INVENTION  
       [0003]     Modern communication networks normally transport two types of traffic or data. The first type is traffic which is sent or received by users or subscribers, with the user or subscriber frequently being billed for the transmission thereof. This traffic is also known as user traffic, user data or subscriber traffic. The second type is traffic originated by network management and frequently called management traffic.  
         [0004]     In the field of telecommunications, management traffic is also called signaling traffic. The term “signaling” here relates to the exchange of signaling messages between different network elements such as database servers, local switching centers, transit switching centers and user terminals. A widely known protocol for transmitting signaling information is Signaling System 7 (SS7), frequently also called Central Signaling System No. 7 (ZZS7) or Common Channel Signaling System 7 (CCS7).  
         [0005]     Signaling System 7 is standardized by the International Telecommunication Union (ITU) in standard series Q.7xx and meets all signaling requirements of modern telecommunication networks.  
         [0006]     Signaling System 7 here forms an independent network, in which SS7 messages are exchanged between the network elements via two-way channels called links. Signaling takes place out-of-band rather than in-band on channels reserved for user data (e.g. voice). Besides faster call setup times, this also permits a range of functions, for example Intelligent Network (IN) services, which can run in the signaling network without parallel user data connections having to be set up.  
         [0007]     The elements of an SS7 network are called signaling points, and are uniquely identified by a signaling point code (SPC). These point codes are transmitted between signaling points in the signaling messages and in each case designate the source and destination of a message. Each signaling point uses a routing table to select an appropriate signaling path for each message.  
         [0008]     Three types of signaling points are distinguished in SS7 networks: Service Switching Points (SSPs), Signaling Transfer Points (STPs) and Service Control Points (SCPs).  
         [0009]     SSPs are switching centers from which calls originate, at which calls end or which forward calls as transit switching centers (frequently as “tandems”). An SSP sends signaling messages to other SSPs to set up, manage and clear down (voice) circuits which are required for a call. An SSP can also interrogate centralized databases (SCPs) to determine how a call should be routed (in the case of toll-free calls, for example). An SCP sends a reply to the inquiring SSP, containing the routing number associated with the number dialed.  
         [0010]     Network traffic between signaling points can be routed via signaling transfer points (STPs). An STP forwards each incoming message on the basis of the routing information contained in the SS7 message to an outgoing signaling link. Since an STP acts as a central network node, it makes better use of the SS7 network, since it obviates the need for direct links between signaling points. An STP can execute “Global Title Translation”, a procedure by which the destination is determined from the number digits contained in the signaling message (e.g. the called toll-free number, the number of a calling card or the ID of a cell phone user MSIN).  
         [0011]     Signaling System 7 uses a protocol stack in which the hardware and software functions of the SS7 protocol are divided into functional abstractions, called levels. These levels can be mapped with certain restrictions to the Open Systems Interconnect (OSI) 7-layer model or the layer model of the International Standards Organization (ISO).  
         [0012]     The lower three levels are called the Message Transfer Part (MTP). MTP Level 1 defines the physical, electrical and functional attributes of the digital signaling link. MTP Level 2 ensures correct end-to-end transmission of a message via a signaling link. MTP Level 3 routes messages between signaling points of the SS7 network.  
         [0013]     Functions are provided in SS7 by so-called user parts. A frequently used user part is the ISDN User Part (ISUP), which defines the protocol used to occupy, manage and release lines that transport the user traffic between switching centers (e.g. between the caller and the called party). In some countries the less powerful Telephone User Part (TUP) is used instead of the ISUP.  
         [0014]     Another SS7 protocol, the Signaling Connection Control Part (SCCP), provides connection-free and connection-oriented network services and Global Title Translation (GTT) above MTP Level 3. The SCCP is used as a transportation level for TCAP-based services.  
         [0015]     The Transaction Capabilities Applications Part (TCAP) supports the exchange of non-voice-circuit-related data between applications in the SS7 network using the connection-free SCCP. Queries and responses exchanged between SSPs and SCPs are transported in TCAP messages. In mobile communication networks the TCAP transports messages of the Mobile Application Part (MAP) exchanged between mobile switching centers and databases to assist with user authentication, device identification and roaming by subscribers.  
         [0016]     In traditional telecommunication networks all user parts use MTP Level 3 to transport messages, MTP Level 3 for its part relying on Levels 2 and 1 to provide transportation and to implement link management.  
         [0017]     Current developments are aimed at replacing signaling based on exclusive and hence expensive lines by services based on the Internet Protocol (IP). However, if IP is used instead of MTP Level 1, the previously used MTP Level 2 also needs to be replaced. The Internet Engineering Task Force (IETF) hence specified in RFC 3332 the MTP3 User Adaptation Layer (M3UA) protocol based on the Stream Control Transmission Protocol (SCTP) and which replaces MTP Levels 2 and 3.  
         [0018]     The aim of the M3UA/SCTP/IP combination is to create the possibility, analogously with MTP Level 3 in traditional SS7 networks, of transporting messages of the user parts between SS7 signaling gateways (SG), media gateway controllers (MGC) or IP-based databases.  
         [0019]     One problem is that the M3UA protocol architecture does not support the linksets known from the traditional MTP Level 3. One result of this is that screening of Level 3 message signaling units (MSUs) is not possible. However, because the networks of many telecommunication providers are linked by means of a higher-level SS7 network, screening is increasingly required so that a network operator can prevent unauthorized use of his resources by other network operators. To this end incoming MTP Level 3 MSUs are largely examined in STPs and forwarded to their destination or rejected using screening rules. A known and frequently used screening standard is laid down in STP Generic Requirements, GR-82-CORE, Annex C from Telcordia Technologies (also called “Bellcore Screening”).  
         [0020]     One object of the present invention is hence to specify a method and a network element which permit the implementation of linkset-related SS7 network functions, in particular screening, based on M3UA messages.  
         [0021]     This object is achieved by a method for implementing linkset-related SS7 network functions based on messages according to M3UA, with the following steps: 
        in a setup phase, mapping M3UA connections to pseudo linksets, a pseudo linkset being defined as the set of M3UA connections between a signaling gateway and an application server and uniquely determined by a set of SS7 parameters and parameter values, the parameters and parameter values uniquely laying down the scope of the traffic processed by the application server;     in the setup phase, storing the data describing the pseudo linksets as linkset data in a database; and     in an operating phase, implementing the linkset-related SS7 network functions by determining an assigned pseudo linkset and applying the SS7 network functions to the messages of the M3UA connection determined using the database.        
 
         [0025]     The invention further relates to a signaling gateway with means for executing this method.  
         [0026]     Advantageous embodiments are specified in the dependent claims.  
         [0027]     One advantage of the invention is that, thanks to the invention, functions requiring the traditional SS7 linksets, for example screening at MTP level or M3UA level, can now also be implemented in SS7 networks based on M3UA.  
         [0028]     If in an existing, traditional SS7 network a TDM-based STP is replaced in the course of converting to SS7 over IP using M3UA by a signaling gateway, advantageously the existing database of the previously used screening rules can still be used, since the M3UA connections are mapped as linksets according to the invention.  
         [0029]     Preferred embodiments of the present invention are explained in greater detail below, in conjunction with a drawing. Terms relating to M3UA are here used in conformity with the meanings defined in RFC 3332, unless specified otherwise (see section 1.2 of RFC 3332). 
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0030]     The single FIGURE shows a network made up of a traditional telecommunication network, namely the TDM network and an IP-based telecommunication network. 
     
    
     DETAILED DESCRIPTION OF THE INVENTION  
       [0031]     The single FIGURE shows a network  100  made up of a traditional telecommunication network, namely the TDM network  102  and an IP-based telecommunication network  104 .  
         [0032]     At the interface between the networks  102  and  104  there is arranged an inventive signaling gateway  108  which in this example has the function of both a signaling transfer point and a signaling gateway (STP/SG). Connected to the signaling gateway  108  in the TDM network  102  by means of a signaling link  118  is, for example, a mobile switching center (MSC)  106 , which by means of signaling link  120  is connected to other network elements, such as a base station controller (BSC) (not shown). In the IP network  104  the signaling gateway  108  is connected by means of three M3UA connections  114 A-C to an application server (AS)  110 , in the present example a home location register (HLR), the application server  110  including by way of example three application server processes (ASP 1 , ASP 2 , ASP n )  112 A-C. Boxes  124 ,  126  and  128  show for MSC  106 , STP/SG  108  and AS  110  the protocol hierarchy used in each case for the message transmission. In particular box  126  shows the signaling gateway function of the STP/SG  108 , namely the conversion from MTP Level 1-3 to M3UA/SCTP/IP.  
         [0033]     To permit screening of messages from the IP network  104  sent via the M3UA signaling relation  122 B in the direction of the TDM network  102  and further switched there by means of traditional SS7 signaling relation  122 A, the M3UA connections  114 A-C are mapped to a pseudo linkset or IP linkset  116 . Whereas in the traditional SS7 a linkset is defined by the set of all SS7 links that connect a network element directly to a particular, immediately adjacent network element and a traditional linkset is thus uniquely defined by its own point code and the point code of the immediate neighbor (Adjacent Destination Point Code, ADPC), the pseudo linkset or IP linkset  116  is defined as a set of all M3UA connections  114 A-C between the signaling gateway  108  and the application server  110 .  
         [0034]     A pseudo linkset or IP linkset  116  is thus uniquely defined by the point code of the signaling gateway  108  and the routing key of the application server  110 . The routing key describes a set of SS7 parameters and parameter values which uniquely lay down the scope of the traffic processed by the application server  110 . The routing key can include in each case a range or an individual value of all or one of the following SS7 parameters: Service Information Octet (SIO), Destination Point Code (DPC), Origination Point Code (OPC), Circuit Identification Code (CIC). The routing key, i.e. the set of parameters and parameter values, is uniquely represented by a numerical value called a routing context.  
         [0035]     The pseudo linksets or IP linksets defined in this way—as with SS7 linksets—are stored in databases of the signaling gateway  108  and hence can be used exactly like SS7 linksets as an entry point for linkset-based functions such as screening. Advantageously for the network operator, the same linkset-related rules, e.g. screening rules, can be used after the switch to SS7 over IP with M3UA as previously in a pure TDM environment.  
         [0036]     For screening, starting from a linkset via which a message was received, parameters of the message determined by a sequence of so-called screening steps are examined (e.g. OPC, DPC, SIO, Affected Destination or Affected Point Code). On the basis of the parameters examined it is finally determined here whether the message in question should be forwarded in accordance with the routing rules or rejected as impermissible.  
         [0037]     The procedure for screening is as follows: first the IP linkset  116  on which the message to be screened was received is determined. In conventional SS7 linksets the linkset can be determined uniquely by checking on which SS7 link the message was received, since the assignment of a link to precisely one linkset is unique. However, with M3UA one application server process  112  may be responsible for several application servers (not shown). However, this means that a message sent by an ASP  112 A is sent via a first pseudo linkset if this ASP  112 A works in the context of a first application server and is sent via a second pseudo linkset if the same ASP  112 A works in the context of a second application server. However, in both cases the message reaches the STP/SG  108  via the same M3UA connection, so that no screening can be implemented on the basis of the M3UA connection, but only on the basis of the pseudo linksets defined here.  
         [0038]     Which application server—and hence which pseudo linkset—the message is assigned to can be determined from the parameter routing context (RC) by using the above definition for the pseudo linksets. If an ASP is only responsible for precisely one AS, this assignment can also be made without the RC parameter.  
         [0039]     For user part messages (e.g. ISUP or SCCP) the parameters to be screened can be read directly from the M3UA protocol data parameters of an M3UA data message. This relates to parameters such as Origination Point Code (OPC), Destination Point Code (DPC), Service Indicator (SI), Network Indicator (NI) or Signaling Link Selection (SLS). Other parameters, for example ISUP message type, can be determined from the user protocol data field of the M3UA message.  
         [0040]     SS7 management messages must first be identified as such. SS7 management messages cannot always be identified by the service indicator (SI), since the M3UA management messages do not contain this. To screen messages with SI=0 (MTP Management), the screening process can preferably determine by the M3UA message class that this is an SS7 management message. The message class for SS7 management messages is fixed as “2” for M3UA. Since in the case of M3UA connections point-to-point connections are involved, these SS7 signaling network management (SSNM) messages have neither a DPC nor an OPC. If these parameters are to be subjected to screening, it is not possible to read these out from the message. Instead DPC and OPC can preferably be derived from the attributes of the pseudo linkset on the basis of the data of the pseudo linkset stored in the database.  
         [0041]     Whereas for traditional SS7 messages screening based just on the so-called affected point codes (the point code or the network element affected by the message) is possible, since traditional SS7 messages each have a maximum of one affected point code, M3UA messages may relate to several affected point codes simultaneously. As an example, consider the message DUNA (Destination Unavailable) defined in RFC 3332, corresponding to a TFP message (Transfer Prohibited) or a TCP message (Transfer Cluster Prohibited) of MTP Level 3, and which can relate to 1 . . . n affected point codes:  
                                                                                                                          
 
         [0042]     If screening rules for affected point codes are defined, it cannot be ascertained for the M3UA message how to proceed with the message, because several rules could be applicable simultaneously for the same message, which in some cases also produce conflicting results. In order nevertheless to screen M3UA messages with several affected point codes, the messages can be broken down into individual messages with just one affected point code each. Alternatively the messages can also be broken down into messages which in each case include a group of affected point codes for which the same screening restrictions apply.  
         [0043]     Although the invention was described above with reference to the linkset-related function of “screening”, the invention is not restricted to this application. Instead, the invention can advantageously be used for all linkset-related network functions.