摘要:
A routing node (516) for translating and re-directing Signaling System 7 (SS7) messages associated with ported subscribers in a communications network. Re-direction or re-routing of signaling message packets is accomplished without the need for explicit local number portability (LNP) type triggers or queries, and such as the routing node of the present invention is considered to implement a triggerless LNP (TLNP) routing solution. Upon entering the routing node, SS7 ISDN User Part (ISUP) type signaling messages (N1) that require LNP translation service are encapsulated in an SS7 Signaling Connection Control Part (SCCP) message packet and internally routed within the switch to an LNP translation subsystem (518). The LNP translation subsystem (518) can be integrated within the routing node (516) or a portion of the LNP translation subsystem (518) can be located on an external database server platform. LNP translation involves the lookup of a called party (122) address in an LNP database, and the return of a Location Routing Number (LRN). The returned LNR, which is representative of the End Office (EO, 110 & 113) currently servicing the called party (113), is inserted into the original ISUP message (N1) and the resulting modified message (N2) is then routed from the switch.
摘要:
A routing node (516) for translating and re-directing Signaling System 7 (SS7) messages associated with ported subscribers in a communications network. Re-direction or re-routing of signaling message packets is accomplished without the need for explicit local number portability (LNP) type triggers or queries, and such as the routing node of the present invention is considered to implement a triggerless LNP (TLNP) routing solution. Upon entering the routing node, SS7 ISDN User Part (ISUP) type signaling messages (N1) that require LNP translation service are encapsulated in an SS7 Signaling Connection Control Part (SCCP) message packet and internally routed within the switch to an LNP translation subsystem (518). The LNP translation subsystem (518) can be integrated within the routing node (516) or a portion of the LNP translation subsystem (518) can be located on an external database server platform. LNP translation involves the lookup of a called party (122) address in an LNP database, and the return of a Location Routing Number (LRN). The returned LNR, which is representative of the End Office (EO, 110 & 113) currently servicing the called party (113), is inserted into the original ISUP message (N1) and the resulting modified message (N2) is then routed from the switch.