Title of Invention

A METHOD OF UPDATING ROUTING TABLES STORED AT A MULTIPLICITY OF SIGNALLING END POINTS

Abstract

A method of updating routing tables stores at a multiplicity of Signalling End Points of an SS7 over IP signaling network following the introduction of a new Signalling End Point into the network, the method comprising sending a message from the new Signalling End Point to an existing Signalling End Point, the message identifying an IP address and SS7 address(es) of the new Signalling End Point, updating the routing table(s) stored at said existing signaling End Point with the new address information, forwarding said message from said existing Signalling End Point to other Signalling. End Points identified in the routing table(s) at said existing Signalling End Point, and updating the routing tables at said other Signalling End Points upon receipt of said messages.

Full Text

FORM 2 THE PATENTS ACT, 1970 (39 of 1970) & The Patents Rules, 2003 COMPLETE SPECIFICATION (See section 10, rule 13) “IP BASED SIGNALLING NETWORKS” TELEFONAKTIEBOLAGET LM ERICSSON (publ) of S-164 83 Stockholm, SWEDEN. The following specification particularly describes the invention and the manner in which it is to be performed. WO 2005/004411 2 PCT/EP2003/050233 IP Based Signalling Networks Field of the Invention 5 The present invention relates to IP based signalling networks and more particularly to IP based signalling networks designed to transport SS7 signalling. Background to the Invention 10 Modern telecommunication networks make use of a set of signalling protocols known collectively as SS7 to set up and control calls. SS7 messages are exchanged between so-called Signalling End Points which may be, for example, local exchanges of a Public Switched Telephone Network (PSTN), Mobile Switching Centres (MSCs) of a GSM network, or Radio Network Controllers of a UMTS (3G) Radio Access Network. SEPs 15 are identified by unique Signalling Point Codes (PC) which act as addresses within the SS7 network. Other network nodes may also be allocated unique PCs to allow SS7 signals to be routed to these nodes. Setting up or changing a traditional SS7 based signalling network is a laborious task 20 involving the dimensioning and defining of links, link-sets, routes, route-sets, routing data, etc. This needs to be done in every node, which is part of the network. To avoid a full-mesh, which would be very expensive from both an administrative and transmission network point of view, traditional SS7 signalling networks have been built according to a hierarchical network structure. This structure is illustrated in Figure 1. Every 25 Signalling End Point (SEP) has usually been connected to a pair of Signalling Transfer Points (STPs). This solution has allowed the SEPs to have only limited knowledge about other SEPs and their location in the network. The STPs have been the points in the network where the network structure has been known, which has allowed the STPs to do the routing of signalling messages between SEPs. 30 Within an SS7 network routing can be based on a destination PC (and optionally a subsystem number (SSN)). When a destination PC/SSN is provided for a signal, each participating node (e.g., switches, STPs, SCPs, etc.) within the serving network must have data identifying the specified destination PC/SSN. Therefore, whenever a signal is WO 2005/004411 3 PCT/EP2003/050233 received with a particular destination PC/SSN, each transferring node within the serving network knows exactly where to send the signal. Signals can also be routed using global title (GT) numbers. When the node originating 5 a signal does not know the destination PC associated with a particular destination node, a global title number has to be used for routing purposes. That global title number is translated into an "intermediate" PC which identifies the next known step. Translation is a two step process involving a first translation from the global title number to a global title routing case (GTRC) using a GT table, and a second translation from a GTRC to a 10 PC using a GTRC table. Each transfer node connecting the originating node with the destination node performs a similar global title number translation to identify the next step. Each node knows only to forward a received signal with a particular global title number toward a certain network or direction. Of course, at some point on the journey of the signal, a correct destination PC has to be provided so that the signal can reach its 15 final destination. Thus, all of the STPs within a given network must include up-to-date information (i.e. GT and GTRC tables) correlating global title numbers with specific PC information. In some implementations, the GT and GTRC tables may be merged into a single "routing" table. 20 The standardisation organisation Internet Engineering Task Force (IETF) has formed a working group known as Signal Transport (SIGTRAN) to formulate and implement the specifications necessary for transporting SS7 signalling over an IP network. SIGTRAN based signalling networks are expected to be introduced commercially over the next few years. IP based signalling has a number of advantages including increased network 25 capacity and reduced infrastructure and maintenance costs. The structure of a SIGTRAN based signalling network resembles on the logical level a full mesh (although the physical network may be of another structure, e.g. an SDH ring). This structure is illustrated in Figure 2. There is no equivalent of the SS7 STP 30 node and instead every SEP communicates on the logical level directly with every other SEP. The reason STPs are not needed is because routing is done at the IP level, thus allowing the physical and the logical networks to be different. (Some vendors may choose to include IP/STP nodes in SIGTRAN network, the STP nodes performing routing based upon SS7 addresses.) WO 2005/004411 4 PCT/EP2003/050233 One drawback of the SIGTRAN network, especially if the network consists of many nodes, is the fact that every SEP needs to have an SCCP GT/GTRC routing table(s) and a further IP address table mapping destination PCs to IP addresses (although again these 5 tables may be merged into a single table or demerged into additional linked tables). Thus, a SEP needs to know the IP address (or addresses as an STP may "posses" multiple IP addresses to provide a degree of redundancy) of nearly every other SEP in the network. Maintaining these address tables, especially in situations when the network is growing rapidly (as will be the case in the years immediately following the 10 first introduction of SIGTRAN), will be very expensive for the operator. Changing the IP address(es) of a SEP manually would also be difficult or even impossible in practice due to the major reconfiguration of the rest of the signalling network that this would require. 15 Even with today's SS7 networks, operators would like to reduce operating costs which are high due to the need to maintain the large global title and PC routing tables. If network management costs were to increase further with the introduction of SIGTRAN networks, many operators may not find SIGTRAN to be a feasible alternative. 20 The following are concerned with distributing routing information in the data plane: WO 200207331; The 'Hello protocol' described in the OSPF protocol (e.g. RFC 1247 July 1991); The ATM Forum P-NNI spec, para 5.6. Summary of the Invention 25 According to a first aspect of the present invention there is provided a method of updating routing tables stored at a multiplicity of Signalling End Points of an SS7 over IP signalling network following the introduction of a new Signalling End Point into the network, the method comprising: 30 sending a message from the new Signalling End Point to an existing Signalling End Point, the message identifying an IP address and SS7 address(es) of the new Signalling End Point; updating the routing table(s) stored at said existing Signalling End Point with the new address information; WO 2005/004411 5 PCT/EP2003/050233 forwarding said message from said existing Signalling End Point to other Signalling End Points identified in the routing table(s) at said existing Signalling End Point; and updating the routing tables at said other Signalling End Points upon receipt of 5 said messages. Embodiments of the present invention allow new Signalling End Points to be implemented in a "plug and play" format. That is to say that it is not necessary to either program a new Signalling End Point with address information for all existing network 10 nodes, or to manually update the routing tables of those other Signalling End Points with address information of the new Signalling End Point. The "automatic" nature of the present can also be expected to make the SIGTRAN network more reliable as faults made by human staff may be avoided. 15 Said multiplicity of Signalling End Points need not comprise all of the Signalling End Points of an SS7 over IP signalling network. Upon the introduction of a new Signalling End Point, those Signalling End Points which are not one of said multiplicity may have their routing tables updated by some other means, e.g. manually. The routing table(s) of the new Signalling End Point may also be updated manually for those Signalling End 20 Points. Preferably, upon receipt of said message at a Signalling End Point, that Signalling End Point sends a response message to the new Signalling End Point containing the IP and SS7 addresses of the responding Signalling End Point. The new Signalling End Point 25 populates its routing table(s) using the contents of the response messages. Preferably, said SS7 addresses of the new Signalling End Point are SS7 Signalling point codes and Global Titles. Signalling End Points comprise Signalling Connection and Control Part (SCCP) Global Title Translation tables and Destination Signalling point 30 code tables. Preferably, said new Signalling End Point is preconfigured with IP and SS7 address information for itself and for said existing Signalling End Point. WO 2005/004411 6 PCT/EP2003/050233 The message sent from the new Signalling End Point to an existing Signalling End Point may contain multiple IP addresses for the new Signalling End Point, e.g. a primary address and one or more secondary addresses. 5 According to a second aspect of the present invention there is provided a method of updating routing tables stored at a multiplicity of Signalling End Points of an SS7 over IP signalling network to reflect the deletion of a Signalling End Point from the network, the method comprising: sending a message from the Signalling End Point to be deleted to other 10 Signalling End Points identified in the routing table(s) of that said Signalling End Point; and updating the routing tables at said other Signalling End Points upon receipt of said message. 15 According to a third aspect of the present invention there is provided a method of updating routing tables stored at a multiplicity of Signalling End Points of an SS7 over IP signalling network to reflect changes in address data at a given Signalling End Point, the method comprising: sending a message from said given Signalling End Point to other Signalling End 20 Points identified in the routing table of said given Signalling End Point, notifying the other Signalling End Points that the entry for given Signalling End Point is to be deleted from routing tables of the other Signalling End Points; in response to receipt of said message at each other Signalling End Point, deleting data for said given Signalling End Point from the routing table(s); and 25 carrying out the method of the first aspect of the present invention, said messages asociated with that method containing the new address data. According to a fourth aspect of the present invention there is provided a signalling end point for use in an SS7 over IP signalling network, the signalling end point 30 a memory for storing one or more routing tables mapping IP addresses to SS7 address data for other signalling end points of the signalling network; processing and transmission means for sending a message to an existing Signalling End Point when the first mentioned signalling end point is introduced into WO 2005/004411 7 PCT/EP2003/050233 the signalling network, wherein the exisiting signalling end point can forward the message to other signalling end points known to it; and input and processing means for receiving response messages from other signalling end points, each containing an IP address and SS7 address data for the 5 responding signalling end point, and for adding this information to the routing table(s) stored in said memory. Brief Description of the Drawings 10 Figure 1 illustrates schematically the architecture of a conventional SS7 signalling network; Figure 2 illustrates schematically the architecture of a SIGTRAN signalling network; and Figure 3 illustrates signalling associated with the introduction of a new signalling end 15 point into the SIGTRAN network of Figure 2. Detailed Description of Certain Embodiments In order to implement a "Plug & Play" SIGTRAN network, a mechanism is needed 20 which allows nodes, for example signalling end points (SEPs), to automatically configure their routing tables and establish links (=SCTP Associations) to other nodes. This can be achieved by creating a virtual network, which would be used for administrative purposes. In such a virtual network every node in the network is aware of all other nodes in the network, i.e. every node knows about the IP address(es), 25 Signalling point code and Global Title(s) of all other nodes. When a new node is attached to the network, the operator enters that node's own IP address(es), Signalling point code and Global Title(s) in the node's routing tables. Additionally, the operator sets up the IP address of one other (adjacent) node in the network. This allows the new node to send its address information to the adjacent node, which then distributes the 30 address information for the new node to all other nodes in the network and which are identified in the routing tables of that adjacent node. When a node in the network receives information about a new node in the network, it updates its own routing tables with the address information and sends it's own address information to the new node WO 2005/004411 8 PCT/EP2003/050233 using the received IP address. The signalling associated with this procedure is illustrated in Figure 3. If a node is to be removed (permanently or temporarily) from the SIGTRAN network, 5 the node sends a detach message to all nodes in the network. In case the signalling point code or the IP address(es) of a node needs to be changed, the node is removed and introduced again with the new information. If a new Global Title needs to be introduced, this Global Title is sent to all the nodes in the network by the node in which the new Global Title is introduced. 10 When SIGTRAN networks are first introduced into the "field", it is inevitable that there will be a large number of legacy (TDM or ATM based) SS7 nodes. The communication with these nodes will be handled via Signalling Gateways (or interworking functions). If a Signalling Gateway is part of a virtual network as described above, it needs to 15 attach all signalling point codes and Global Titles of the legacy nodes to the virtual network. The unique IP addresses of the Signalling Gateway will however indicate implicitly to the other nodes in the network that the Signalling Gateway has introduced several signalling point codes, thus allowing the other nodes to establish only one SCTP association each to the Signalling Gateway. In the case of Signalling Gateways, a 20 Gateway acts as a "proxy" for attached Signalling End Points, sending attach and detach messages to other Signalling End Points (or their Signalling Gateways) on their behalf. When a new application is introduced into a node, the basic SS7 infrastructure is already in place, which allows the application to specify which of the nodes in the 25 network it wants to communicate with. This allows the node where the application is introduced to automatically establish an SCTP association to every node to which the application needs to communicate with. In a practical implementation, it may be that automatic configuration only happens for 30 nodes belonging to a given national network. Links between networks can still be administered manually, as the number of connections between networks is likely to be limited to a relatively small number. WO 2005/004411 9 PCT/EP2003/050233 The inventive concept described here can be implemented in only a subset of all of the nodes in a given network. Other nodes, not implementing the inventive concept, can be updated manually. Even where only say 50% of the nodes in a given network implement the invention, there would still be significant savings. 5 It will be-appreciated by the person of skill in the art that various modifications may be made to the above described embodiments without departing from the scope of the present invention. For example, a new Signalling End Point may be configured with the address information of a secondary or back-up existing Signalling End Point to which 10 the update message is sent if the primary Signalling End Point cannot be reached. In another modification, a new Signalling End Point may start a timer following the sending of an update message. If responses from other Signalling End Points are not received prior to expiry of the timer, the message may be resent, e.g. to the same or another existing Signalling End Point. In yet another modification, a Signalling End 15 Point may "refresh" the network by resending an update message either automatically (e.g. once per day) or upon receiving an appropriate command. In the event that a SIGTRAN network comprises IP/STP nodes, an update message for a new Signalling End Point may be sent to an existing STP rather than to an existing 20 Signalling End Point. The STP may have to modify the message before passing it on to other Signalling End Points or STPs, e.g. to specify the STP as a destination point for messages destined for the new Signalling End Point. Signalling End Points may be arranged to store routing tables in a variety of formats. 25 Routing tables may be provided to map destination Point Codes to IP addresses and/or Global Titles to Global Title Routing Cases and Global Title Routing Cases to Point Codes. In the SIGTRAN implementation known as SUA, signalling Point Codes are not used. In this case, the routing table may map Global Titles directly to IP addresses. Other routing table configurations are also envisaged. 30 WO 2005/004411 10 PCT/EP2003/050233 Claims: 1. A method of updating routing tables stored at a multiplicity of Signalling End Points of an SS7 over an IP signalling network following the introduction of a new 5 Signalling End Point into the network, the method comprising: sending a message from the new Signalling End Point to an existing Signalling End Point, the message identifying an IP address and SS7 address(es) of the new Signalling End Point; updating the routing table(s) stored at said existing Signalling End Point with the 10 new address information; forwarding said message from said existing Signalling End Point to other Signalling End Points identified in the routing table(s) at said existing Signalling End Point; and updating the routing tables at said other Signalling End Points upon receipt of 15 said messages. 2. A method according to claim 1, wherein said multiplicity of Signalling End Points does not comprise all of the Signalling End Points of an SS7 over IP signalling network. 20 3. A method according to claim 1 or 2, wherein upon receipt of said message at a Signalling End Point, that Signalling End Point sends a response message to the new Signalling End Point containing the IP and SS7 addresses of the responding Signalling End Point, and the new Signalling End Point populates its routing table(s) using the 25 contents of the response messages. 4. A method according to any one of the preceding claims, wherein said SS7 addresses of the new Signalling End Point are SS7 Signalling point codes and Global Titles and optionally Sub-System Numbers. 30 5. A method according to claim 4, wherein said Signalling End Points comprise Signalling Connection and Control Part (SCCP) Global Title Translation tables and Destination Signalling point code tables. WO 2005/004411 11 PCT/EP2003/050233 6. A method according to claim 5, wherein said new Signalling End Point is preconfigured with IP and SS7 address information for itself and for said existing Signalling End Point. 5. 7. A method of updating routing tables stored at a multiplicity of Signalling End Points of an SS7 over IP signalling network to reflect the deletion of a Signalling End Point from the network, the method comprising: sending a message from the Signalling End Point to be deleted to other Signalling End Points identified in the routing table(s) of that said Signalling End Point, 10 and updating the routing tables at said other Signalling End Points upon receipt of said message. 8. A method of updating routing tables stored at a multiplicity of Signalling End 15 Points of an SS7 over IP signalling network to reflect changes in address data at a given Signalling End Point, the method comprising: sending a message from said given Signalling End Point to other Signalling End Points identified in the routing table of said given Signalling End Point, notifying the other Signalling End Points that the entry for given Signalling End Point is to be deleted 20 from routing tables of the other Signalling End Points; in response to receipt of said message at each other Signalling End Point, deleting data for said given Signalling End Point from the routing table(s); and carrying out the method of the first aspect of the present invention, said messages asociated with that method containing the new address data. 25 9. A signalling end point for use in an SS7 over IP signalling network, the signalling end point comprising: a memory for storing one or more routing tables mapping IP addresses to SS7 address data for other signalling end points of the signalling-network; 30 processing and transmission means for sending a message to an existing Signalling End Point when the first mentioned signalling end point is introduced into the signalling network, wherein the exisiting signalling end point can forward the message to other signalling end points known to it; and 12 Input and processing means for receiving response messages from other signaling end points, each containing an IP address and SS7 address data for the responding signaling end point, and for adding this information to the routing table(s) stored in said memory. 10. A system of updating routing tables stored at a multiplicity of Signalling End Points of an SS7 over an IP signalling network following the introduction of a new Signalling End Point into the network, said system comprising: a) a message generator unit providing a message from the new Signaling End Point to an existing Signalling End Point, the message identifier identifying an IP address and SS7 address(es) of the new Signalling End Point. b) means for updating the routing table(s) stroed at said existing Signalling End Point with the new address information; c) identifier unit identify in the routing table(s) at existing Signalling End Point which forwards the said message to other Signalling End point from the said existing Signalling End Point 11. A system according to claim 10, wherein the Signalling End Point sends a response message to the new Signalling End Point containing the IP and SS7 addresses of the responding Signalling End point upon the receipt of said message at a Signalling End Point, and the new Signalling End Point populates its routing table(s) using the contents of the response message. 12. A system according to claim 11, wherein said SS7 addresses of the new Signalling End Point are SS7 Signalling point codes and Global Titles and optionally Sub-System Numbers. 13. A system according to claim 10, wherein said Signalling End Points comprise Signalling Connection and Control Part (SCCP) Global Title Translation Tables and Desctination Signalling Point Code tables. 13 14. A system according to claim 12, wherein IP is preconfigured by said new Signalling End Point and SS& address information for itself and for said existing Signalling End Point. 15. A system of updating routing tables stored at a multiplicity of Signalling End Points of an SS7 over IP signaling network according to claim 10, to reflect the deletion of a Signalling End Point from the network, the system comprising: message generator unit provides a message from the Signalling End Point to be deleted to other Signalling End Points identified in the routing table(s) of that said Signalling End Point; and means for updating the routing tables at said other Signalling End Points upon receipt of said message. 16. A method and system of updating routing tables substantially as herein described with reference to accompanying drawings. 17. A signaling end point for use in an SS7 over IP signaling network, the signaling end point substantially as herein described with reference to accompanying drawings. MAHUA GHOSH OF K & S PARTNERS AGENT FOR THE APPLICANTS Dated this 12th day of January, 2006. 14 ABSTRACT A method of updating routing tables stores at a multiplicity of Signalling End Points of an SS7 over IP signaling network following the introduction of a new Signalling End Point into the network, the method comprising sending a message from the new Signalling End Point to an existing Signalling End Point, the message identifying an IP address and SS7 address(es) of the new Signalling End Point, updating the routing table(s) stored at said existing signaling End Point with the new address information, forwarding said message from said existing Signalling End Point to other Signalling. End Points identified in the routing table(s) at said existing Signalling End Point, and updating the routing tables at said other Signalling End Points upon receipt of said messages.

Documents:

54-mumnp-2006-abstract(06-05-2008).doc

54-mumnp-2006-abstract(06-05-2008).pdf

54-mumnp-2006-abstract.doc

54-mumnp-2006-abstract.pdf

54-mumnp-2006-cancelled pages(06-05-2008).pdf

54-mumnp-2006-claims(granted)-(06-05-2008).doc

54-mumnp-2006-claims(granted)-(06-05-2008).pdf

54-mumnp-2006-claims.doc

54-mumnp-2006-claims.pdf

54-mumnp-2006-correspondence(06-05-2008).pdf

54-mumnp-2006-correspondence(ipo)-(09-05-2007).pdf

54-mumnp-2006-correspondence-received-ver-120106.pdf

54-mumnp-2006-correspondence-received-ver-190506.pdf

54-mumnp-2006-correspondence-received.pdf

54-mumnp-2006-description (complete).pdf

54-mumnp-2006-drawing(06-05-2008).pdf

54-mumnp-2006-drawings.pdf

54-mumnp-2006-form 1(06-05-2008).pdf

54-mumnp-2006-form 1(19-05-2006).pdf

54-mumnp-2006-form 18(22-05-2006).pdf

54-mumnp-2006-form 2(granted)-(06-05-2008).doc

54-mumnp-2006-form 2(granted)-(06-05-2008).pdf

54-mumnp-2006-form 26(06-05-2008).pdf

54-mumnp-2006-form 26(19-05-2006).pdf

54-mumnp-2006-form 3(06-05-2008).pdf

54-mumnp-2006-form 3(16-01-2006).pdf

54-mumnp-2006-form 5(06-05-2008).pdf

54-mumnp-2006-form 5(16-01-2006).pdf

54-mumnp-2006-form-1.pdf

54-mumnp-2006-form-18.pdf

54-mumnp-2006-form-2.doc

54-mumnp-2006-form-2.pdf

54-mumnp-2006-form-26.pdf

54-mumnp-2006-form-3.pdf

54-mumnp-2006-form-5.pdf

54-mumnp-2006-form-pct-ipea-409(16-01-2006).pdf

54-mumnp-2006-form-pct-ipea-416.pdf

54-mumnp-2006-form-pct-isa-210(16-01-2006).pdf

54-mumnp-2006-pct-search report.pdf

54-mumnp-2006-petition under rule 138(07-05-2008).pdf

abstract1.jpg