SS7 point code sharing at MTP level 3

Abstract

The invention relates to message handling in SS7 communications networks. An inventive network arrangement comprises at least two SS7 network elements having a common first and individual second signaling point codes. A third network element also has the common signaling point code. At least one SS7 link set is provided between the at least two SS7 network elements. SS7 link sets between the at least two SS7 network elements and the third network element terminate at the individual second point codes, whereas SS7 links between the at least two SS7 network elements and other SS7 network elements having signaling point codes different from the common signaling point code terminate at the common point code in each of the at least two SS7 network elements. The at least two SS7 network elements comprise: means for forwarding all MTP user part messages received for the common signaling point code to the third network element either directly or via another one of the at least two SS7 network elements; means for treating all incoming MTP network management messages such that the first, second, and third network element appear to be one unique network element having the common signaling point code; and means for suppressing or modifying outgoing MTP network management messages that relate to operative conditions of any other of the at least two SS7 network elements or of the third SS7 network element such that the first, second, and third network element appear to be one unique network element having the common signaling point code.

Description

The present invention relates to an optimized method, apparatus and network arrangement for handling signaling messages in a communications network. More particularly, the present invention relates to an optimized method, apparatus and network arrangement for point code sharing at MTP level 3 and transparently introducing network elements in a SS7 network.

Modern communications networks generally carry two types of traffic or data. The first is the traffic which is transmitted by or delivered to a user or subscriber, and which is usually paid for by the user. That type of traffic is widely known as user traffic or subscriber traffic. The second is the traffic caused by network management applications in sending and receiving management data from network elements, known as management traffic.

In telecommunications, the management traffic is also known as signaling traffic. The term “signaling” refers to the exchange of signaling messages between various network elements such as database servers, local exchanges, transit exchanges and user terminals. A well known protocol for transferring such signaling messages is the Signaling System 7 (SS7), also referred to as Common Channel Signaling System 7 (CCS7).

The Signaling System 7 as specified by the International Telecommunication Union (ITU) in the Q.700-series Recommendations provides for all signaling tasks in today's telecommunications networks. More specifically, SS7 provides for example for:

• • basic call setup, management, and tear down;
  • enhanced call features such as call forwarding, calling party name/number display, and three-way calling;
  • accounting and billing;
  • database operations for services such as authentication, roaming, toll-free and special tariff services, and number portability;
  • network management for the SS7 network and its connections; and
  • non-call related signaling, allowing for services such as short message service (SMS), ISDN Supplementary Services and user-to-user signaling (UUS).

The Signaling System 7 forms an independent network in which SS7 messages are exchanged between network elements over bi-directional channels called signaling links. Signaling occurs out-of-band on dedicated channels rather than in-band on channels reserved for user traffic such as voice. Compared to in-band signaling, out-of-band signaling provides:

• • faster call setup times;
  • more efficient use of voice circuits; and
  • support for Intelligent Network (IN) services which require signaling to network elements without voice trunks (e.g., database systems).

The elements of a SS7 network are known as signaling points, each uniquely identified by a signaling point code. Point codes are carried in signaling messages exchanged between signaling points to identify the source and destination of each message. Each signaling point uses a routing table to select the appropriate signaling path for each message.

There are essentially three kinds of signaling points in a SS7 network: Service Switching Points (SSPs), Signaling Transfer Points (STPs), and Service Control Points (SCPs).

SSPs are switches that originate, terminate, or tandem calls. An SSP sends signaling messages to other SSPs to setup, manage, and release voice circuits required to complete a call. An SSP may also send a query message to a centralized database (an SCP) to determine how to route a call (e.g., a toll-free call). An SCP sends a response to the originating SSP containing the routing number(s) associated with the dialed number.

Network traffic between signaling points may be routed via signaling transfer points (STPs). An STP routes each incoming message to an outgoing signaling link based on routing information contained in the SS7 message. Because it acts as a network hub, an STP provides improved utilization of the SS7 network by eliminating the need for direct links between signaling points. An STP may perform global title translation, a procedure by which the destination signaling point is determined from digits present in the signaling message (e.g., the dialed 800 number, calling card number, or mobile subscriber identification number).

Signaling in a SS7 network may occur in either of two configurations: associated signaling wherein the signaling points are direct neighbors and communicate directly via SS7 links; or quasi-associated signaling wherein signaling between two nodes occurs via one or more STP.

Associated signaling allows for a maximum of 16 signaling links between the neighboring network elements. This limit may be overcome by providing a pair of signaling transfer points in the path between those network elements, thereby choosing quasi-associated signaling instead. Each STP may support 16 signaling links, thereby allowing a maximum of 32 signaling links between said network elements. Having two signaling transfer points further allows multiple routes between the network elements and therefore the introduction of a pair of signaling transfer points provides resiliency against single STP failures.

An exemplary network setup involving a local exchange (LE) 102 and two direct neighbors 104, 106 is schematically shown in FIG. 1. It shall be noted that FIG. 1 shows the signaling aspects only. Associated signaling occurs via a first link set 120 comprising two signaling links 120A, 120B between local exchange 102 and first neighbor 104 and also via a second link set 122 comprising two signaling links 122A, 122B between local exchange 102 and second neighbor 106. Note that all signaling points comprise unique signaling point codes, which is “A” for local exchange 102, “X1” for first neighbor 104, and “X2” for second neighbor 106. First and second neighbors 104, 106 may also be local exchanges. In some situations all three local exchanges 102, 104, 106 may be placed in different operator's networks as indicated by dashed curves 112, 114, and 116.

If allowed by an operator of network section 112, LE 102 may act as STP for signaling from LE 104 to LE 106 and vice versa; the signaling between LE 104 and LE 106 would then be quasi-associated.

For either of the network operators there may arise the need to introduce an additional network element in the path towards the local exchange owned by that operator. For example, operator of network section 112 may choose to introduce an additional network element (not shown) in the signaling paths between LE 102 and LE 104 and/or LE 106. Traditionally, such additional network element would be assigned a signaling point code and fundamentally act as STP for messages between LE 102 and LE 104 and/or LE 106. To avoid single points of failure, a pair of signaling transfer points each having a unique signaling point code may typically be deployed.

Especially in multi-operator environments such as depicted in FIG. 1 it may not always be possible to reach an agreement on the introduction of new signaling points and their point codes. One reason thereof is that signaling point codes are a limited resource in a SS7 network, and it may very well be that an operator already has as many signaling points in his network as he has signaling point codes available. Another, even more challenging problem is that routing tables in various network elements, including network elements of other operators, need to be changed upon introduction of new signaling (transfer) points.

It is therefore an object of the present invention to provide a novel method for handling messages in network element of a communications network. It is a further object of the invention to provide an improved signaling transfer point. It is yet another object of the present invention to provide a network arrangement having transparent SS7 network elements.

In accordance with the foregoing objectives, there is provided by the invention a method for handling messages in a first SS7 network element of a communications network, comprising:

• • providing a first and a second signaling point code in the first SS7 network element, wherein the first signaling point code is also a signaling point code of at least one second SS7 network element and a third SS7 network element;
  • providing at least one SS7 link set to the second SS7 network element;
  • terminating said SS7 link set to the second SS7 network element at the first or second point code;
  • terminating SS7 a link set to the third SS7 network element at the second point code;

terminating SS7 links to other SS7 network elements having signaling point codes different from the first signaling point code at the first point code;

• • forwarding all MTP user part messages received for the first signaling point code to the third network element either directly or via the second network element;
  • treating all incoming MTP network management messages such that the first, second, and third network element appear to be one unique network element having the first signaling point code; and
  • suppressing or modifying outgoing MTP network management messages that relate to operative conditions of the second or third network element such that the first, second, and third network element appear to be one unique network element having the first signaling point code.

In accordance with the invention, there is also provided a network arrangement in a SS7 communications network, comprising:

• • at least two SS7 network elements having a common first and individual second signaling point codes;
  • a third network element also having the common signaling point code;
  • at least one SS7 link set between the at least two SS7 network elements;
  • at least one SS7 link set between each of the at least two SS7 network elements and the third SS7 network element, said SS7 link sets terminating at the individual second point codes;
  • at least one SS7 link between each of the at least two SS7 network elements and other SS7 network elements having signaling point codes different from the common signaling point code, said SS7 links terminating at the common point code in each of the at least two SS7 network elements;
  • wherein the at least two SS7 network elements comprise:
    • means for forwarding all MTP user part messages received for the common signaling point code to the third network element either directly or via another one of the at least two SS7 network elements;
    • means for treating all incoming MTP network management messages such that the first, second, and third network element appear to be one unique network element having the common signaling point code; and
    • means for suppressing or modifying outgoing MTP network management messages that relate to operative conditions of any other of the at least two SS7 network element or of the third SS7 network element such that the first, second, and third network element appear to be one unique network element having the common signaling point code.

The invention also relates to a Signaling Transfer Point (STP) of a SS7 network, comprising:

• • a first and a second signaling point code, wherein the first signaling point code is also a signaling point code of at least one second SS7 network element and a third SS7 network element;
  • at least one SS7 link set to the second SS7 network element, said SS7 link set terminating at the first or second point code;
  • at least one SS7 link set to the third SS7 network element, said SS7 link set terminating at the second point code;
  • at least one SS7 link to other SS7 network elements having signaling point codes different from the first signaling point code, said SS7 link terminating at the first point code;
  • means for forwarding all MTP user part messages received for the first signaling point code to the third network element either directly or via the second network element;
  • means for treating all incoming MTP network management messages such that the first, second, and third network element appear to be one unique network element having the first signaling pointrcode; and
  • means for suppressing or modifying outgoing MTP network management messages that relate to operative conditions of the second or third network element such that the first, second, and third network element appear to be one unique network element having the first signaling point code.

One advantage of the invention is that it allows to transparently introduce a redundant configuration of network elements, preferably signaling transfer points, “in front of” a third network element by presenting the redundant configuration of two or more network elements and the third network elements to other network elements as one unique signaling point. This, in turn, is achieved by the invention by allowing the redundant configuration of network elements and the third network element to “share” the signaling point code originally assigned to the third network element.

Transparently introducing a redundant configuration of network elements in accordance with the invention does advantageously not require a change of the routing information of any network element with the exception of the third network element. This network element however will be under the full control of a network operator introducing such redundant configuration of network elements. Changes in the routing tables of this network element will therefore not require the cooperation of other operators.

In the following, the invention will be described in more detail in the form of advantageous embodiments which are better understood in accordance with the enclosed drawings.

FIG. 1 shows an exemplary network arrangement involving a local exchange having two direct neighbors.

FIG. 2 shows the network arrangement of FIG. 1 wherein a set of signaling transfer points has been introduced in the paths between the local exchange and its neighbors in accordance with the invention.

FIG. 3 shows a message sequence of a changeover procedure in case of a link failure involving one of the signaling transfer points introduced in accordance with the invention.

FIG. 1, as explained in detail above, schematically shows a typical network setup involving a local exchange (LE) 102 and two direct neighbors 104, 106, wherein said three nodes may be placed in three different network sections 112, 114 and 116 owned by different operators.

Operator of network section 112 may wish to introduce a new network element or, to avoid a single point of failure, preferably a redundant configuration of network elements in network section 112 wherein signaling links 120A/B, 122A/B from other operator's network sections 114 and 116 terminate at said redundant configuration of network elements. As this new network element or redundant configuration of network elements as placed at the network boundary it may also be referred to as border network element(s) BNE or BE.

Potential scenarios, where the introduction of border elements may be of advantage, include, but are not limited to, the following:

• • Several operators (operators of networks 112, 114, 116) are sharing the same logical SS7 network, having only associated signaling links 120A/B and 122A/B between their network elements and one operator (operator of network 112) whishes to migrate to an STP based SS7 network.
  • Screening purposes, e.g. inspecting any received signaling message in full depth to block certain messages such as call setups or ISUP supplementary services or SCCP messages, or to monitor messages and their contents such as sender and content of SMS messages. The operator introducing such screening element may wish it to be “invisible” or transparent for other operator's network elements.
  • One operator wishes to replace a TDM based SS7 network by IP based transport. Some aspects of such replacement procedure are covered in ETSI EG 202 360 “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Architectural scenarios and applicability for different SIGTRAN adaptation layers; SIGTRAN scenarios”. However, in practical configurations it may be impossible to find one SS7 over IP signaling protocol supported by all network elements. Some network elements such as call servers performing call control may only support the IETF protocol M3UA (RFC 3332 or ETSI TS 102 142), whereas other network elements such as media gateway and/or signaling gateway elements mediating between TDM and IP network only support IETF protocol M2UA (RFC 3331 or ETSI TS 102 141). Introducing an STP that supports all applicable protocols may resolve this issue. Again the operator may wish to introduce such STP transparently.

Turning now to FIG. 2, there is shown one preferred embodiment of a network arrangement in accordance with the present invention. As with FIG. 1, FIG. 2 only depicts the signaling aspects; no reference is made to bearer or data channels. In the path between local exchange 102 (hereinafter also referred to as third SS7 network element) and its neighbors 104, 106 (hereinafter also referred to as other SS7 network elements) there is now provided a pair of signaling transfer points 150, 160 (also referred to as first and second SS7 network element). Having a pair of network elements 150, 160 is a minimum configuration for a redundant configuration of network elements. It is understood that more than two such SS7 network elements may be combined into a redundant configuration of network elements. As seen from either of the network elements 150, 160, each other network element 160, 150 in the redundant configuration is a “second” network element and there may exist several such “second” network elements in a redundant configuration.

In detail, LE 104 is connected via link set 120 to each of the first and second STP 150, 160. Link set 120 comprises a first signaling link 120A and a second signaling link 120B. First link 120A terminates at first STP 150 and second link 120B terminates at second STP 160. Likewise, LE 106 is connected via link set 122 to each of the first and second STP 150, 160. Link set 122 comprises a first signaling link 122A and a second signaling link 122B. First link 122A terminates at first STP 150 and second link 122B terminates at second STP 160. Link sets 120, 122 may of course comprise more than two links in other embodiments, wherein more than one link may be connected to either or both STPs 150, 160 allowing a further degree of redundancy.

LE 102 is connected to first STP 150 via link set 180 and to second STP 160 via link set 182. Link sets 180, 182 each comprise at least one signaling link. Between first and second STP 150, 160 there is provided at least one signaling link set 170 comprising at least one link, or multiple signaling link sets each comprising at least one signaling link (not shown).

According to the invention, network arrangement 190 comprising first and second STP 150, 160 and LE 102 is represented to other network elements 104, 106 by a single signaling point code A, also referred to as common or shared signaling point code. To this end, both first and second STP 150, 160 have a first and a second signaling point code, sometimes also referred to as primary and secondary point code. The first point code 152 in STP 150 is chosen to be the shared signaling point code A. Similarly, the first point code 162 in STP 160 is also chosen to be the shared signaling point code A. The second point code 154 in STP 150 is chosen to be a unique signaling point code A1, and the second point code 164 in STP 160 is chosen to be a unique signaling point code A2. Reference is made to international application WO03/032653 published on Apr. 17, 2003 which discloses a method for providing multiple signaling point codes in a SS7 signaling point.

Links 120A/B, 122A/B from other SS7 network elements 104, 106 will be terminated at the first signaling point codes 152, 162, which is the common signaling point code A. This allows connecting one link set 120, 122 to two SS7 network elements 150, 160 simultaneously which would not be possible if SS7 network elements 150, 160 had different point codes (in SS7, all links in a given link set may only terminate at one signaling point code). It further allows maintaining the routing information in other SS7 network elements 104, 106 since the links 120A/B, 122A/B (as seen from the other network elements) still terminate at a signaling point having the signaling point code A, i.e. the other SS7 network elements 104, 106 operate as if they were directly connected to LE 102. In SS7 network elements 150, 160, messages handled are such as if network arrangement 190 were in fact one unique element having the signaling point code A.

The third SS7 network element, LE 102, is connected to the respective second, or individual, point codes 154, 164 in SS7 network elements 150, 160. In detail, a first link set 180 between LE 102 and first STP 150 terminates at second point code 154 of first STP 150, and a second link set 182 between LE 102 and second STP 150 terminates at second point code 164 of first STP 160. Routing information in LE 102 has to be modified such that LE 102 may now reach LEs 104, 106 by means of a route set comprising link sets 180 and 182 via either STP 150, 160. Since these changes apply to a first operator's network 112 only, this operator is free to apply such changes without having to reach agreement with other network's 114, 116 operators.

When terminating links 120A/B, 122A/B at physically different entities having a shared signaling point code A, such point code sharing is effected at MTP Level 3 in accordance with the invention. When sharing the point code at MTP Level 3, user part messages such as ISUP messages will be passed on unmodified by the redundant configuration of SS7 network elements 150, 160 using any route available to a message's destination. For example, an ISUP message received from LE 104 for signaling point code A on link 120A at first STP 150 may be passed on directly via link set 180 to LE 102 or via link set 170 to second STP 160 and from there via link set 182 to LE 102 where the ISUP processing takes place. It is readily apparent that the redundancy of network arrangement 190 allows for continued operation under any single failure condition of any links or signaling element with the exception of LE 102. Failure of first STP 150 for example shall lead to rerouting of affected traffic to second STP 160.

MTP network management messages will be handled such that no indication is given to other network elements 104, 106 that the network configuration 190 is, in fact, not a single node but three or more nodes 150, 160, 102.

MTP network management messages include, but are not limited to the following:

• • Change Over Order (COO) and Change Over Acknowledgement (COA);
  • Emergency Change Over Order (ECO) and Emergency Change Over Acknowledgement (ECA);
  • Extended Change Over Order (XCO) and Extended Change Over Acknowledgement (XCA);
  • Change Back Declaration (CBD) and Change Back Acknowledgement (CBA);
  • Inhibiting Messages (LIN/LIA/LUN/LUA/LID/LFU);
  • Inhibiting Test Messages (LLT, LRT); and
  • Signaling Link Test Message (SLTM) and Signaling Link Test Acknowledgement (SLTA).

In one embodiment, the signaling link code SLC contained in certain MTP network management messages may be used to facilitate MTP message handling. The SLC of MTP network management messages received from other network elements 104, 106 is determined by the receiving STP 150, 160. If a message relates to a link terminating at the receiving STP 150, 160, then this STP 150, 160 will process the message and respond if required by SS7 procedures. If a message relates to a link not terminating at the receiving STP 150, 160, then this STP 150, 160 will not process the message but forward it to the other STP 160, 150 unless the message was received from this other STP 160, 150, in which case the message will be discarded and no notifications or responses will be sent. The step of forwarding a message relating to a link not terminating locally requires modifications in the MTP message handling function in a STP 150, 160 as any “off the shelf” STP would simply discard any such message.

Of course, if more than two STPs 150, 160 form the redundant configuration of network elements, additional provisions may be implemented to ensure that a message traverses all such network elements exactly once before it is discarded.

FIG. 3 shows an exemplary application of this preferred principle. For the sake of simplicity, LE 102 and LE 106 and their terminating links are omitted from FIG. 3. In FIG. 3, LE 104 is connected via link 120A to first (shared) signaling point code 152 of first STP 150 and via link 120B to first (shared) signaling point code 162 of second STP 160. Link or link set 170 is connected to the second (individual) signaling point codes 154, 164 of STPs 150, 160. Both links 120A/B are of the same link set 120, as explained above.

In FIG. 3, second link 120B having the SLC=1 is assumed to have come out of service. LE 104 will, upon detecting the failure of second link 120B of link set 120, send a changeover order (COO) to the adjacent signaling point code of that link set 120, which is the shared signaling point code A (step 1). The COO will have an origination point code (OPC) equal to the signaling point code of LE 104 (OPC=X1), a destination point code equal to the signaling point code of the signaling point adjacent at that link set 120, which is the shared signaling point code A (DPC=A), and reference the failed link 120B (SLC=1). First STP 150 receives this message (step 2) and determines the SLC of the COO, which is SLC=1. Since link 120B having SLC=1 does not terminate at first STP 150, and the COO was not received from second STP 160 via link set 170, first STP 150 forwards the COO to second STP 160 (step 3). In more detail, the COO is first forwarded internally from the common signaling point code 152 to the individual signaling point code 154 before it is sent to individual signaling point code 164 of second STP 160.

In step 4, the COO is received at second STP 160. In more detail, the COO is received by the individual signaling point code 164 of second STP 160 and forwarded internally to the common signaling point code 162 as determined from the DPC=A of the COO. Second STP 160 determines the SLC of the COO, which is SLC=1. Since link 120B having SLC=1 does terminate at second STP 160, second STP processes the message. In response to a COO a changeover acknowledgement message (COA) is required. Such COA is generated by second STP 160 and returned to LE 104 on any available link of the same link set the COO was received on (steps 5-7).

In the example of FIG. 3 where there is only one (disturbed) link 120B between STP 160 and LE 104, the COA is created by the common signaling point code 162 of second STP 160 and forwarded internally to the individual signaling point code 164 for further transfer to first STP 150. The COA will have an origination point code (OPC) equal to the shared signaling point code A (OPC=A), a destination point code equal to the signaling point code of the signaling point adjacent to link set 120, which is the signaling point code of LE1 (DPC=X1), and reference the failed link (SLC=1). The OPC in the COA must not be the second STP's second point code 164 as this point code is not known at LE 104.

The COA is then received at first STP 150. In more detail, the COA is received by the individual signaling point code 154 of second STP 150 and forwarded internally to the common signaling point code 152. Then the COA is forwarded to LE 104 in step 7. In general, messages not relating to the common signaling point code A are not handled in accordance with the principles laid out above but forwarded in accordance with their DPC.

It shall be noted that the regular behavior of first STP 150 upon receiving a COO for a link 120B not terminating at first STP 150 would be to discard this message. This behavior is suppressed and replaced by the procedure as laid out above. Any COO message(s) that would normally be created by second STP 160 upon detecting the link failure may either be suppressed or sent in a similar fashion as described with reference to the COA.

If there is more than one link 120B between STP 160 and LE 104 (not shown), the COA (having the same parameters OPC=X1, DPC=A, SLC=1) may alternatively be sent directly to LE 104 from the common signaling point code 162 of second STP 160.

With respect to signaling link test messages and their acknowledgements (SLTM/SLTA), STP 150, 160 may implement the behavior as laid out in the SS7 standards: any SLTM received on the same link it references by means of SLC will be answered by a SLTA, and any SLTM received on a different link than that referenced by means of SLC will be discarded.

If in the example of FIG. 3 all links of link set 170 to the second STP 160 are out of service, i.e. the COO cannot be forwarded from first STP 150 to second STP 160, first STP 150 may immediately respond to the incoming COO with a corresponding emergency changeover acknowledgement message (ECA).

Turning back to FIG. 2, there may occur an operative condition where either of the STPs 150, 160 is no longer able to communicate with the other STP and LE 102. For example, second STP 160 may no longer be able to reach first STP 150 due to a failure of all links in link set 170, and LE 102 due to a failure of all links in link set 182. The connections to LE 104, 106 however may still be in service. Generally, second STP 160 would send corresponding TFP messages to LE 104 and LE 106. This however would reveal that the network arrangement 190 consists of multiple network elements 102, 150, 160, which is undesirable. Therefore, such TFP messages will be suppressed, and the links 120B, 122B to all other network elements 104, 106 will be taken out of service instead. As soon as LE 102 becomes reachable again, second STP 160 reactivates these links 120B, 122B.

After such isolation of second STP 160, and in other situations where only one of the STPs 150, 160 looses its connection with other network elements 104, 106, this STP would perform a MTP restart procedure as soon as the first link towards the other network elements 104, 106 becomes available again. The other network elements 104, 106 however will not perform a MTP restart as some links towards the common signaling point code A are still active via the other STP. The other network elements 104, 106 will most likely perform the change back procedure (ITU-T, Q.704, chapter 6) instead of the MTP restart procedure (ITU-T, Q.704, chapter 9). To overcome potential problems resulting from this situation, the following may be provided:

• • The restarting STP 160 will preferably send a Traffic Restart Allowed message (TRA) to LE 104, 106. Although this message may alternatively be suppressed, sending such message is preferred to also cover situations in which all STPs 150, 160 had lost connection to LEs 104, 106 and a “real” restart of arrangement 190 representing signaling point code A is expected. The restarting STP 160 will not wait for a TRA to be returned. The TRA supervision timer (T18 respectively T21) is not started. As the LEs 104, 106 may only perform change back, the restarting STP 160 immediately has to be able to handle user traffic.
  • If a LE 104, 106 sends a TRA (either because it is restarting or in response to an unexpected TRA), such TRA may be received at any of the two STPs, including a STP not expecting a TRA at that time. While it would be possible to respond to such unexpected TRA with another TRA in accordance with ITU-T Q.704, such responses may lead to a sequence of unexpected TRA messages. To avoid such a situation, it is preferred to discard unexpected TRA messages in the STPs and suppress the appropriate response.

The invention is applicable to all transport protocols available in SS7. More particularly, the present invention does not require links 120A/B, 122A/B and the links in link sets 170, 180, 182 to be TDM based SS7 links. Instead, the signaling transfer points 150, 160 may be employed to provide for interworking between different signaling protocols such as TDM and IP based SS7 protocols. The following is an example in connection with FIG. 2: Link set 120 from LE 104 to redundant configuration of network elements 150, 160 may comprise a conventional TDM link 120A and a link 120B that is handled by a signaling gateway (not shown) which effects TDM-IP interworking between MTP Level 2 and M2UA/SCTP/IP according RFC 3331. Link set 170 between the STPs 150, 160 may comprise IP based links using M2PA/SCTP and/or M3UA/SCTP and/or conventional MTP. Link sets 180, 182 may also use any of the signaling protocols M2PA/SCTP and/or M3UA/SCTP and/or conventional MTP. Where necessary, each individual link may be according to a different signaling protocol.

While link set 170 has been shown to terminate in both STPs 150, 160 at the individual point codes 154, 164, other embodiments may include links and/or link sets connecting the individual point code 154 of first STP 150 to the common point code 162 of second STP 160 and individual point code 164 of second STP 160 to the common point code 152 of first STP 150. The setup of STPs 150, 160, and such link sets, may be such that messages to be transferred from first STP 150 to second STP 160 are received at first point code 152 and forwarded to second point code 154 in first STP 150, and are then forwarded to first point code 162 in second STP 160. Similarly, messages to be transferred from second STP 160 to first STP 150 are received at first point code 162 and forwarded to second point code 164 in first STP 160 and are then forwarded to first point code 152 in first STP 150.

While the redundant configuration 150, 160 has been described with reference to FIG. 2 as being transparently introduced in front of one signaling point 102 having a signaling point code SPC=A, the same redundant configuration 150, 160 may also be used to represent more than one point code (not shown) to the other network elements 104, 106. To represent a second point code SPC=B (not shown), a second logical MTP network can be created in both STPs 150, 160. A signaling transfer point supporting up to 32 logical MTP networks is known as hiS 700, manufactured by Siemens. In this second logical network, the setup is similar to the setup described herein with reference to signaling point code SPC=A.

It shall be noted that local exchanges 102, 104, 106 may each comprise multiple point codes and/or MTP networks (not shown) as required by a specific application. It will be readily apparent from the detailed description how the inventive principle may be applied in such configurations.

Claims

1-17. (canceled)

18. A method for handling messages in a first SS7 network element of a communications network, comprising: providing a first and a second signaling point code in the first SS7 network element, wherein the first signaling point code is also a signaling point code of at least one second SS7 network element and a third SS7 network element; providing at least one SS7 link set to the second SS7 network element; terminating the SS7 link set to the second SS7 network element at the first or second point code; terminating SS7 a link set to the third SS7 network element at the second point code; terminating SS7 links to other SS7 network elements having signaling point codes different from the first signaling point code at the first point code; forwarding all MTP user part messages received for the first signaling point code to the third network element either directly or via the second network element; treating all incoming MTP network management messages such that the first, second, and third network element appear to be one unique network element having the first signaling point code; and suppressing or modifying outgoing MTP network management messages relating to operative conditions of the second or third network element such that the first, second, and third network element appear to be one unique network element having the first signaling point code.

19. The method according to claim 18, wherein the steps of treating, suppressing or modifying MTP network management messages comprise: determining the SLC of a received MTP network management message; if the SLC relates to a signaling link not terminating at the first network element, forwarding message to the second network element if the message was not received from the second network element, or alternatively discarding the message if the message was received from the second network element; if the SLC relates to a signaling link terminating at the first network element, processing the message in accordance with standard SS7 procedures and returning any applicable responses.

20. The method according to claim 19, further comprising the step of sending a changeover acknowledgement message or emergency changeover acknowledgement message in response to any incoming changeover order messages if all links of the link set to the second network element are out of service.

21. The method according to claim 19, further comprising the steps of: suppressing the sending of transfer prohibited messages to other network elements; and taking out of service any signaling links to said other network elements if all links in link sets to the second and third network elements are out of service.

22. The method according to claim 18, wherein either or all signaling links terminating at the first network element are traditional TDM links and/or ATM links and/or M2UA links and/or M2PA links and/or M3UA links.

23. A network arrangement in a SS7 communications network, comprising: at least two SS7 network elements having a common first and individual second signaling point codes; a third network element also having the common signaling point code; at least one SS7 link set between the at least two SS7 network elements; at least one SS7 link set between each of the at least two SS7 network elements and the third SS7 network element, the SS7 link sets terminating at the individual second point codes; at least one SS7 link between each of the at least two SS7 network elements and other SS7 network elements having signaling point codes different from the common signaling point code, said SS7 links terminating at the common point code in each of the at least two SS7 network elements, wherein the at least two SS7 network elements comprise: a device for forwarding all MTP user part messages received for the common signaling point code to the third network element either directly or via another one of the at least two SS7 network elements; a device for treating all incoming MTP network management messages such that the first, second, and third network element appear to be one unique network element having the common signaling point code; and a device for suppressing or modifying outgoing MTP network management messages that relate to operative conditions of any other of the at least two SS7 network elements or of the third SS7 network element such that the first, second, and third network element appear to be one unique network element having the common signaling point code.

24. The network arrangement according to claim 23, wherein the at least one SS7 link set between the at least two SS7 network elements connects the individual second point codes.

25. The network arrangement according to claim 23, further comprising a plurality of SS7 link sets between the at least two SS7 network elements, said SS7 link sets arranged such that the individual second point code of each of the SS7 network elements is connected to the common first point code of at least one other of the SS7 network elements.

26. The network arrangement according to claim 23, wherein the treating, suppressing or modifying device comprise a device for: determining the SLC of a received MTP network management message; if the SLC relates to a signaling link not terminating at one of the at least two SS7 network elements, forwarding the message to another one of the at least two SS7 network elements if the message was not received from another one of the at least two SS7 network elements or has not traversed all other of the at least two SS7 network elements, or alternatively discarding the message if the message was received from another one of the at least two SS7 network elements after traversing all other of the at least two SS7 network elements; if the SLC relates to a signaling link terminating at one of the at least two SS7 network elements, processing the message at this SS7 network element in accordance with standard SS7 procedures and returning any applicable responses.

27. The network arrangement according to claim 26, wherein the at least two SS7 network elements further comprise a device for sending a changeover acknowledgement message or emergency changeover acknowledgement message in response to any incoming changeover order messages if all links to all other of the at least two SS7 network elements are out of service.

28. A network arrangement according to any of claim 26, wherein each of the at least two SS7 network elements further comprises a device for suppressing the sending of transfer prohibited messages to other network elements and taking out of service any signaling links to said other network elements if all links between said one of the at least two SS7 network elements and all other of the at least two SS7 network elements and all links between said one of the at least two SS7 network elements and the third network element are out of service.

29. The network arrangement according to any of claim 23, wherein either or all signaling links comprise traditional TDM links and/or ATM links and/or M2UA links and/or M2PA links and/or M3UA links.

30. A signaling transfer point of a SS7 network, comprising: a first and a second signaling point code, wherein the first signaling point code is also a signaling point code of at least one second SS7 network element and a third SS7 network element; at least one SS7 link set to the second SS7 network element, the SS7 link set terminating at the first or second point code; at least one SS7 link set to the third SS7 network element, the SS7 link set terminating at the second point code (154); at least one SS7 link to other SS7 network elements having signaling point codes different from the first signaling point code, said SS7 link terminating at the first point code; a device for forwarding all MTP user part messages received for the first signaling point code to the third network element either directly or via the second network element; a device for treating all incoming MTP network management messages such that the signaling transfer point, the second, and third network element appear to be one unique network element having the first signaling point code; and a device for suppressing or modifying outgoing MTP network management messages that relate to operative conditions of the second or third network element such that the signaling transfer point, the second, and third network element appear to be one unique network element having the first signaling point code.

31. The signaling transfer point according to claim 30, wherein the treating, suppressing or modifying device comprise a device for: determining the SLC of a received MTP network management message; if the SLC relates to a signaling link not terminating at the signaling transfer point, forwarding message to the second network element if the message was not received from the second network element, or alternatively discarding the message if the message was received from the second network element; else if the SLC relates to a signaling link terminating at the signaling transfer point, processing the message in accordance with standard SS7 procedures and returning any applicable responses.

32. The signaling transfer point according to claim 31, further comprising a device for sending a changeover acknowledgement message or emergency changeover acknowledgement message in response to any incoming changeover order messages if all links to the second network element are out of service.

33. The signaling transfer point according to any of claims 31, further comprising a device for suppressing the sending of transfer prohibited messages to other network elements and taking out of service any signaling links to the other network elements; if all links in link sets to the second and third network elements are out of service.

34. The signaling transfer point according to claim 30, further comprising a device for connecting to SS7 links comprising traditional TDM links and/or ATM links and/or M2UA links and/or M2PA links and/or M3UA links.