Systems, methods, and computer readable media for using a signaling message routing node to provide backup subscriber information management service

Description

TECHNICAL FIELD

The subject matter described herein relates to methods and systems for increasing a network's reliability and robustness. More particularly, the subject matter described herein relates to systems, methods, and computer readable media for using a signaling message routing node to provide backup subscriber information management service.

BACKGROUND

In conventional telecommunications networks that support mobile subscribers, one or more network entities maintain what is referred to as subscriber information, which may include the identity of the subscriber, the services that are available to the subscriber, and the current location of the mobile subscriber. In conventional telecommunications networks, certain network entities are responsible for maintaining subscriber information and for making that information available when needed. For example, global system for mobile communications (GSM) networks include a home location register, or HLR, which maintains information about subscribers to a mobile network. In Internet protocol media subsystems (IMS) networks, some of the same or similar functions are performed by a home subscriber server, or HSS. For simplicity, a network entity responsible for maintaining subscriber information is hereinafter generically referred to an HLR/HSS.

Access to subscriber information is vital to the operation of a mobile telecommunications network. Other network elements, such as mobile switching centers (MSCs) and call session control functions (CSCFs) communicate mobile subscriber status information to the HLR/HSS nodes using various signaling protocols, including GSM/IS-41 mobile application part (MAP), Diameter, and others. Example subscriber information management messages include MAP and Diameter UpdateLocation messages, Diameter user data request (UDR) messages, Diameter profile update, Diameter location information request (LIR) messages, Diameter server assignment request (SAR) messages, and MAP signal routing information (SRI) messages. These messages carry, among other things, information that identifies the current serving MSC or CSCF. The HLR/HSS is also configured to provide mobile subscriber information to a requesting MSC or CSCF.

There are disadvantages associated with conventional telecommunications networks that support mobile subscribers. In conventional networks, mobile subscribers are assigned or homed to a single subscriber information management node, such as an HLR or HSS. If the HLR/HSS nodes in a mobile communications network become unreachable, isolated, or otherwise unavailable, major service disruptions are possible and likely. What is needed, therefore, is a system and method for minimizing the negative impact of loss of access to subscriber information management information, such as may occur as a result of HLR/HSS network element isolation events in a mobile telecommunications network.

One conventional approach to overcome the disadvantages stated above has been to create an entity, called a gateway location register, or GLR, that copies mobility management messages, caches all of the information contained within the mobility management messages, and responds on behalf of the HLR/HSS when possible, in order to reduce the workload on the HLR/HSS. This conventional approach suffers the disadvantage that the GLR always responds on behalf of the HLR/HSS, even if the HLR/HSS is operational. What is needed is a system or method which provides backup service, responding only when the HLR/HSS is not operational.

Another conventional approach to overcome the disadvantages stated above has been to distribute the function of an HLR/HSS across a bank of nodes, where each individual HLR/HSS services a particular subset of subscribers, and to place a distribution function between the bank of nodes, where the each subscriber is routed to that subscriber's HLR/HSS. This conventional approach suffers the disadvantage that failure of a particular HLR/HSS causes a loss of service to whichever subscribers had been assigned to that HLR/HSS. Rather than protect against loss of service, this approach limits loss of service to a subset of subscribers rather than having all subscribers lose service. However, if the distribution function fails, all subscribers lose service anyway. What is needed is a system or method which can supplement this conventional approach by providing backup service for both any individual HLR/HSS that may fail, and also provide backup service in case the distribution function fails as well.

Another conventional approach to overcome the disadvantages stated above involves load sharing across multiple HLR/HSS nodes, where messages are distributed across the nodes to reduce the load on any individual node. This conventional approach suffers the disadvantage that each node must contain a full copy of the subscriber information database. This gives rise to overhead required to keep all databases in synchronization with each other. This approach suffers the additional disadvantage that a corrupted entry in one node's database is quickly replicated across all nodes' databases, rendering them all susceptible to the same kind of database corruption. What is needed is a system or method which stores information independently from the HLR/HSS nodes and is thus isolated from corruption of any one of the HLR/HSS nodes.

Accordingly, in light of these disadvantages, there exists a need for systems, methods, and computer readable media for using a signaling message routing node to provide backup subscriber information management service.

SUMMARY

Methods, systems, and computer readable media for using a signaling message routing node to provide a backup subscriber information management service are disclosed. According to one method, a signaling message routing node obtains information associated with a subscriber. The signaling message routing node receives a first subscriber information management message including a message destination and being associated with the subscriber. The signaling message routing node determines whether the message destination is operable to process the first subscriber information management message. In response to determining that the message destination node is operable to process the first subscriber information management message, the signaling message routing node routes the first subscriber information message to the message destination. In response to determining that the message destination is not operable to process the first subscriber information management message, the signaling message routing node responds to the first subscriber information management message on behalf of the message.

The subject matter described herein for using a signaling message routing node to provide backup subscriber information management service and may be implemented in software in combination with hardware and/or firmware. For example, the subject matter described herein can be implemented in software executed by a processor. As such, the terms “function” or “module” as used herein refer to software in combination with hardware and/or firmware for implementing the feature being described. In one exemplary implementation, the subject matter described herein may be implemented using a computer readable medium having stored thereon computer executable instructions that when executed by the processor of a computer control the computer to perform steps. Exemplary computer readable media suitable for implementing the subject matter described herein include non-transitory computer-readable media, such as disk memory devices, chip memory devices, programmable logic devices, and application specific integrated circuits. In addition, a computer readable medium that implements the subject matter described herein may be located on a single device or computing platform or may be distributed across multiple devices or computing platforms.

BRIEF DESCRIPTION OF THE DRAWINGS

Preferred embodiments of the subject matter described herein will now be explained with reference to the accompanying drawings, wherein like reference numerals represent like parts, of which:

FIG. 2 is a flow chart illustrating an exemplary process for using a signaling message routing node to provide backup subscriber information management service according to an embodiment of the subject matter described herein;

FIG. 3 is a flow chart illustrating an exemplary process for obtaining subscriber information by a signaling message routing node according to an embodiment of the subject matter described herein;

FIG. 6 is a block diagram illustrating a system for using a signaling message routing node to provide backup subscriber information management service according to yet another embodiment described herein;

FIGS. 7 and 8 are message flow diagrams illustrating providing backup subscriber information management service for a first set of Diameter transactions according to an embodiment of the subject matter described herein;

FIGS. 9 and 10 are message flow diagrams illustrating the providing of backup subscriber information management service for a second set of Diameter transactions according to an embodiment of the subject matter described herein; and

FIG. 11 is a block diagram illustrating a signaling message routing node for providing backup subscriber information management service according to an embodiment of the subject matter described herein.

DETAILED DESCRIPTION

In accordance with the subject matter disclosed herein, systems, methods, and computer readable media are provided for using a signaling message routing node to provide backup subscriber information management service. In one embodiment, a signaling message routing node is configured to provide home location register/home subscriber server backup. In this embodiment, if the HLR/HSS element in a mobile communications network becomes unreachable, unavailable, or isolated, queries that would normally be routed to and received by the HLR/HSS are redirected by the router to a subscriber information management module. The subscriber information management module receives, processes, and responds to the HLR/HSS query on behalf of the intended HLR/HSS element. The signaling message routing node may also be configured to provide an auto-provisioned subscriber location cache. Reference will now be made in detail to exemplary embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.

FIG. 1 is a block diagram illustrating a system for using a signaling message routing node to provide backup subscriber information management service according to an embodiment of the subject matter described herein. In the embodiment illustrated in FIG. 1, a signaling message routing node is used to provide home location register/home subscriber server backup. System 100 includes a signaling message routing node 102 including a subscriber information management module 103. As will be set forth in detail below, subscriber information management module 103 may obtain information associated with a subscriber through interception of subscriber information management messages and caching of subscriber information from those messages at a subscriber information cache 108, which may be integrated with or separate from signaling message routing node 102. In the illustrated example, subscriber information management module 103 may receive a subscriber information management message 104 having a message destination and being associated with a subscriber. The message destination may be HLR/HSS 106 or other node that stores subscriber information. Signaling message routing node 102 determines whether HLR/HSS 106 is operable to process subscriber information management message 104. If HLR/HSS 106 is operable to process subscriber information management message 104, signaling message routing node 102 routes subscriber information management message 104 to HLR/HSS 106. If HLR/HSS 106 is not operable to process subscriber information management message 104, signaling message routing node 102 responds to subscriber information management message 104 on behalf of HLR/HSS 106. The dashed arrows in FIG. 1 represent the message path when HLR/HSS 106 is not operable to process subscriber information management message 104, and the solid arrows represent the case where message destination106 is operable to process subscriber information management message 104.

In the embodiment illustrated in FIG. 1, signaling message routing node 102 is a signal transfer point (STP), but in alternative embodiments, signaling message routing node 102 may be a signaling gateway (SG), an edge router, a session initiation protocol (SIP) signaling router (SSR), a Diameter signaling router (DSR), an Internet protocol (IP) router, an IP multimedia subsystem (IMS) router, or other entity for routing signaling messages.

Similarly, subscriber information cache 108 can be any suitable node for storing subscriber information. As set forth above, subscriber information cache 108 can be an internal database to signaling message routing node 102. Alternatively, subscriber information cache 108 can be an STP, a signaling gateway, a signaling router, a DSR, an IP router, an IMS router, a server, a service control point, or other suitable node separate from with storage capacity.

Subscriber information management message 104 may be mobile application part (MAP) protocol message, a Diameter protocol message, or other type of subscriber information management message. For example, subscriber information management message 104 may be a request to update a subscriber's location information, such as an UpdateLoc message, a request for location information, such as LOC_REQ, a request for routing information for a particular subscriber, such as SRI and SRI_SM, or a registration message. Subscriber information management message 104 may alternatively be a Diameter server assignment request (SAR) message, a Diameter location information request (LIR) message, a Diameter profile update request (PUR) message, a Diameter update location request (ULR), a Diameter user data request (UDR) message, or any other Diameter message received on the Cx, Sh, S6a, S6b, or Sp interface.

The information associated with a subscriber that is obtained by signaling message routing node 102 may be information identifying the subscriber or identifying a network node that is currently serving the subscriber. Information identifying the subscriber may include an international mobile subscriber identity (IMSI) of the subscriber, a mobile station integrated services digital network (MSISDN) number of the subscriber, or other information identifying the subscriber. Information identifying a network node that is currently serving the subscriber may include the address of the node, such as a point code of the node, an IP address of the node, a name, a uniform resource identifier (URI), a uniform resource locator (URL), a Diameter node identifier, or other information identifying the node. Examples of nodes that serve subscribers include mobile switching centers (MSCs), such as visiting MSC (VMSC) 110, which, in the embodiment illustrated in FIG. 1 is serving mobile subscriber 112, and MSC 114. Other nodes may include mobile switching center servers (MSCSs), short message service centers (SMSCs), such as SMSC 116, call session control functions (CSCFs), etc.

The information obtained by routing node 102 and stored in subscriber information cache 108 may be all or a subset of the information normally stored in HLR/HSS 106. For example, basic HLR/HSS functionality may be approximated by storing only the subscriber identity and the identity of the node currently serving that subscriber. Additional information may be stored as well, such as the subscriber's profile, which may indicate the type of subscriber (subscription or pre-paid, local/national/international calling plan, etc.) as well as services that the subscriber has access to (calls, text messages, media streaming, Internet access, etc.) To save space, however, subscriber information cache 108 may store one or only a few basic service profiles that would take effect in the event that HLR/HSS 106 becomes inoperable. In this manner, network subscribers and their visitors would be allowed basic access, such as incoming and outgoing calls, limited text messaging, etc., even in an emergency situation. Alternatively, subscriber information cache 108 may provide only one profile for all subscribers in the event of failure of the HLR/HSS 106. Although not described explicitly with respect to FIG. 1, other functions typically performed by HLR/HSS nodes may also be provided by subscriber information cache 108 and/or routing node 102.

Providing backup subscriber information management service may include providing backup presence service, status updates, registration, and prepaid service. In alternative embodiments, telecommunications system 100 may include or consist of any wireless protocol, including WiMax and WiFi. In alternative embodiments, system 100 could provide backup service for other nodes or other subscriber information management nodes—not just for HLR/HSS nodes. In alternative embodiments, system 100 may include or consist of other network types, such as IMS, or other packet networks, wireline networks, etc.

FIG. 2 is a flow chart illustrating an exemplary process for using a signaling message routing node to provide backup subscriber information management service. This process is described with reference to FIGS. 1 and 2.

In step 200, information associated with a subscriber is obtained by a signaling message routing node. For example, signaling message routing node 102 may obtain information associated with a subscriber by intercepting subscriber information management messages and caching subscriber information from those messages in subscriber information cache 108. An exemplary process for obtaining subscriber information will be described in detail with respect to FIG. 3.

In step 202, a subscriber information management message having a message destination and being associated with a subscriber is received at the signaling message routing node. In the example illustrated in FIG. 1, routing node 102 receives an UpdateLocation message 104, which is being sent from visited MSC (VMSC) 110 to HLR/HSS 106, to inform HLR/HSS 106 of the location of mobile subscriber 112. UpdateLocation message 104 includes the identity of mobile subscriber 112.

In step 204, it is determined whether the message destination is operable to process the subscriber information management message. In one embodiment, either routing node 102 or subscriber information cache 108 may use a physical level protocol, a link level protocol, a network level protocol, an application level protocol, a high-availability protocol, or other suitable protocol to determine whether HLR/HSS 106 is operable to process UpdateLocation message 104. For example, network management messages such as subsystem status test (SST), subsystem prohibited (SSP), and subsystem restricted (SSR) may be used. Other mechanisms for determining the health of message destination 106 include link and linkset monitoring, ping, ICMP, and high availability (HA) protocols. For LTE, the SCTP level handshake can detect failure of the host node and/or failure of an application on the host node. A routing node may detect the failure of HLR/HSS 106 via SS7, SCTP, Diameter, and SIGTRAN protocol handshakes. Alternatively, either routing node 102 or subscriber information management cache 108 may receive notification from an entity other than HLR/HSS 106 that HLR/HSS 106 is not operational to process subscriber information management message 104. For example, this notification may be issued from a network operator or network controller, such as when the network operator detects that HLR/HSS 106 is down or disables HLR/HSS 106 for maintenance, etc.

In step 206, if the message destination is operable to process the subscriber information management message, the process moves to step 208, in which the subscriber information management message is routed to the message destination. In the embodiment illustrated in FIG. 1, routing node 102 may forward subscriber information management message 104 to HLR/HSS 106. However, if the message destination is not operable to process the subscriber information management message, the process moves to step 210, in which an entity that is different from the message destination node responds to the subscriber information management message on behalf of the message destination node. In the embodiment illustrated in FIG. 1, either cache 108 or routing node 102 may respond to subscriber information management message 104 responding to the message originator with an answer to subscriber information management message that would be expected from HLR/HSS 106. For example, if the message is a Diameter update location request message, the response may be an update location answer message indicating that the update location transaction is allowed. Routing node 102 may also update the information stored within cache 108 to accord to the contents of subscriber information management message 104. For example, if the subscriber information management message contains new location or status information concerning the subscriber, this information may be stored in cache 108.

In the case where subscriber information management message 104 is a request for location information, responding on behalf of HLR/HSS 106 may include providing the requested subscriber information to the message originator. For example, subscriber information management message 104 may be a request for subscriber location information, such as a send routing information (SRI) message, a send routing information for short messages (SRI_SM) message, a location request (LOC_REQ) message, etc. This type of message is hereinafter referred to generically as a subscriber information request. In this scenario, if HLR/HSS 106 is operable, message 104 is forwarded to HLR/HSS 106. If HLR/HSS 106 is not operable, cache 108 or routing node 102 may respond to message 104 with the latest location information for the subscriber that was stored within cache 108. If subscriber information management message 104 is a registration request, routing node 102 or cache 108 may respond with a registration response containing updated subscriber registration information.

Thus, responding to subscriber information management message 104 may include responding to a request for location update with an answer message indicating that the location update is allowed or responding to a request for profile information by providing user profile information to the requesting entity. In the latter example, profile information may include information about what services a subscriber does and does not have access to, the type of subscriber, etc.

FIG. 3 is a flow chart illustrating an exemplary process for obtaining subscriber information at a routing node, providing further detail for step 200 in FIG. 2. In FIG. 2, it is assumed that routing node has received the message and identified the message as being of the type that carries subscriber information. For example, signaling message routing node 102 may determine whether a received message is a MAP or Diameter message that is of a type that includes subscriber information. Exemplary MAP messages that include subscriber information include location update and registration notification messages. Exemplary Diameter messages that include subscriber information include server assignment request (SAR) messages, profile update request (PUR) messages, and update location request (ULR) messages. Such a determination may be performed by routing node 102 decoding the message to determine the message type and determining whether the message type is one of the aforementioned message types that contain subscriber information.

Referring to FIG. 3, in step 300, a subscriber information management message information associated with a subscriber is received at a signaling message routing node. For example, message 104 may be received by routing node 102. Message 104 may be addressed to HLR/HSS 106. In step 302, at least some of the subscriber information is stored in a subscriber information cache. For example, routing node 102 may cache the subscriber information in subscriber information cache 108.

In step 304, it is determined whether the message destination is operable to process the subscriber information management message. If so, the process moves to step 306, in which the subscriber information management message is routed to the message destination, and the process ends. If, in step 304, it is determined that the message destination node is not operable to process the subscriber information management message, the process moves to step 308, where the subscriber information management message is responded to on behalf of the message destination node. For example, routing node 102 may respond on behalf of HLR/HSS 106 in response to receiving a subscriber information management message that contains subscriber information by sending the corresponding answer or acknowledge message to the message originator.

FIG. 4 is a block diagram illustrating a system for using a signaling message routing node to provide backup subscriber information management service including routing of short message service (SMS) messages according to another embodiment described herein. In the embodiment illustrated in FIG. 4, SMSC 116 sends a send routing information for short messages (SRI_SM) message 400 to HLR/HSS 106. Routing node 102 intercepts SRI_SM message 400 and detects that HLR/HSS 106 is out of service. In response to detecting that HLR/HSS 106 is out of service, Routing node 102 forwards SRI_SM message 400 to cache node 108, which responds to SRI_SM message 400 with a send routing information for short messages acknowledgment (SRI_SM Ack) message 402. Routing node 102 receives SRI_SM Ack message 402 and forwards it to the requesting entity, SMSC 116.

FIG. 5 is a block diagram illustrating a system for using a signaling message routing node to provide backup subscriber information management service including routing of voice calls according to yet another embodiment described herein. In the embodiment illustrated in FIG. 5, MSC 114 sends a send routing information (SRI) message 500 to HLR/HSS 106. Routing node 102 intercepts SRI message 500 and detects that HLR/HSS 106 is out of service. In response to detecting that HLR/HSS 106 is out of service, routing node 102 forwards SRI message 500 to subscriber information cache 108. Subscriber information cache 108 issues a provide roaming number (PRN) message 502 to VMSC 110. VMSC 110 responds by sending to subscriber information cache 108 a PRN acknowledge (PRN Ack) message 504 that contains the mobile station routing number (MSRN) for the subscriber. Subscriber information cache 108 retrieves the MSRN information from PRN Ack message 504 and sends that information in an SRI acknowledge (SRI Ack) message 506 to routing node 102. Routing node 102 forwards SRI Ack message 506 to MSC 114. Thus, in FIG. 5, subscriber information cache 108, in addition to caching subscriber location information and responding on behalf of HLR/HSS 106, performs the provide roaming number function of HLR/HSS 106.

FIG. 6 is a block diagram illustrating the system of FIG. 5 where VMSC 110 exports location information (or other subscriber information) 600, for the purpose of offload or backup. The location information or other subscriber information may be that obtained from routing node 102 and/or cache 108. Thus, routing node 102 and/or cache 108 facilitate the distribution of subscriber information among network nodes, even when the HLR/HSS is down.

In the examples above, backup subscriber information management service is provided for various types of mobile application part (MAP) messages. In addition, the subject matter described herein may be used to provide backup subscriber information management service for various types of Diameter transactions. FIGS. 7 and 8 are message flow diagrams illustrating providing subscriber information backup service for Diameter messages exchanged over a Cx interface according to an embodiment of the subject matter described herein. Referring to FIG. 7, signaling message routing node 102 comprises a Diameter signaling router with subscriber information management module 103. Routing node 102 may communicate with home subscriber server 700 via a Cx interface. In the illustrated example, routing node 102 receives a Diameter server assignment request (SAR) message from another node, such as a serving call session control function (S-CSCF). In IMS networks, all calls to a mobile subscriber are directed through S-CSCF assigned to the subscriber. The S-CSCF assigned to the subscriber stores the binding between the subscriber IMS public identifier (IMPU), IMS private identifier (IMPI), and the S-CSCF identifier. The SAR message may contain this binding, and is sent to the HSS where the binding may be stored. In the illustrated example, the SAR message is intercepted by routing node 102. Subscriber information management module 103 caches the binding between the subscriber identifiers and the S-CSCF. Routing node 102 then routes the SAR message to HLR/HSS 106.

In FIG. 8, HLR/HSS 106 is assumed to be down. Accordingly, when routing node 102 receives a Diameter location information request (LIR) message specifying the same subscriber identifier cached in the signaling message flow in FIG. 8, routing node 102 identifies HLR/HSS 106 as the serving HLR/HSS, and determines whether HLR/HSS 106 is available. In this example, because HSS 106 is not available, routing node 102 accesses the subscriber information cache to obtain the S-CSCF assignment data. Routing node 102 then responds on behalf of HLR/HSS 106 to the originator of the LIR message with a corresponding LIA message that includes the S-CSCF assignment data for the subscriber.

FIGS. 9 and 10 illustrating the providing of backup subscriber information management service for Diameter transactions that occur on the IMS Sh interface according to an embodiment of the subject matter described herein. Referring to FIG. 9, routing node 102 receives a Diameter profile update request (PUR) message containing subscriber data and the IMS public and private identifiers for the subscriber. Routing node 102 intercepts the PUR message, caches the subscriber data in the corresponding subscriber identifier, and routes the PUR message to serving HLR/HSS 106.

Referring to FIG. 10, in line 1, DSR receives a user data request specifying the same subscriber identifiers for PUR message illustrated in FIG. 9. Accordingly, routing node 102 identifies HLR/HSS 106 as a serving HSS and determines that serving HLR/HSS 106 is not available. Routing node 102 accesses the subscriber information cached to obtain the subscriber data and responds to the UDR originator with a corresponding UDA message that includes the data for the subscriber.

FIG. 11 is a block diagram illustrating an exemplary routing node for providing backup subscriber information management service according to an embodiment of the subject matter described herein. Referring to FIG. 11, routing node 102 may be an STP, a signaling gateway, an edge router, a SIP signaling router, a Diameter signaling router, an IP router, or an IMS router. Routing node 102 includes subscriber information management module 103 that performs the steps described herein for providing backup subscriber information management service. Routing node 102 may also include a communications interface 1100 that exchanges messages with an HLR or HSS to determine availability or unavailability. Communication interface 1100 may also intercept the subscriber information management messages from other nodes and either route or respond to those messages depending on whether the HLR or HSS is available. Accordingly, routing node 102 may include a routing module 1102 that performs signaling message routing. If routing node 102 is a DSR, routing module 1102 may include Diameter routing information where messages are routed based on Diameter layer information, including any combination of originating host, destination host, originating realm, and destination realm. If routing node 102 operates in an SS7 network, routing module 1102 may route based on any combination of SS7 routing parameters, including destination point code, originating point code, destination IP address, and originating IP address. Because some messages in SS7 networks are sent route on global title, routing node 102 may include a global title translation (GTT) module 1104 that performs global title translation for signaling messages to translate the global title address into a point code and subsystem number that can be routed using routing module 1102.

It will be understood that various details of the subject matter described herein may be changed without departing from the scope of the subject matter described herein. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation.

Claims

1. A method for using a signaling message routing node to provide backup subscriber information management service, the method comprising: obtaining, by a Diameter signaling router (DSR), information associated with a subscriber;receiving, at the DSR, a first subscriber information management message including a message destination and being associated with the subscriber;determining, at the DSR, whether the message destination is available to process the first subscriber information management message;in response to determining that the message destination is available to process the first subscriber information management message, routing, at the DSR, the first subscriber information message to the message destination; andin response to determining that the message destination is not available to process the first subscriber information management message, responding, at the DSR, to the first subscriber information management message on behalf of the message destination using the information obtained at the DSR.
2. The method of claim 1 wherein obtaining the information associated with the subscriber comprises: receiving, at the signaling message routing node, a second subscriber information management message containing the information associated with the subscriber;extracting the information associated with the subscriber from the second subscriber information management message; andstoring the extracted information associated with the subscriber at the signaling message routing node or at a node that is separate from the DSR and the message destination.
3. The method of claim 2 wherein the first and second subscriber information management messages each comprise one of: a mobile application part (MAP) protocol message; anda Diameter protocol message.
4. The method of claim 2 wherein the second subscriber information management message comprises a request to update location information for the subscriber.
5. The method of claim 4 wherein the request to update location information for the subscriber comprises one of: an update location (UpdateLoc) message;a registration message; anda Diameter update location request (ULR).
6. The method of claim 1 wherein the information associated with the subscriber comprises information identifying the subscriber.
7. The method of claim 6 wherein the information identifying the subscriber comprises at least one of: an international mobile subscriber identity (IMSI); anda mobile station integrated services digital network (MSISDN) number.
8. The method of claim 1 wherein the information associated with the subscriber comprises information identifying the network node that currently serves the subscriber.
9. The method of claim 8 wherein the information identifying the network node that currently serves the subscriber comprises at least one of: a point code of the network node;an Internet protocol address of the network node; anda Diameter identity of the network node.
10. The method of claim 8 wherein the network node that currently serves the subscriber comprises at least one of: a mobile switching center (MSC);a mobile switching center server (MSCS);a short message service center (SMSC); anda serving call session control function (S-CSCF).
11. The method of claim 1 wherein the message destination comprises at least one of: a home location register (HLR); anda home subscriber server (HSS).
12. The method of claim 1 wherein determining whether the message destination is available to process the first subscriber information management message comprises at least one of: using at least one of a physical level protocol, a link level protocol, a network level protocol, an application level protocol, and a high availability protocol to determine whether the message destination node is available to process the first subscriber information management message; andreceiving notification from an entity other than the signaling message routing node indicating that the message destination is or is not available to process the subscriber information management message.
13. The method of claim 1 wherein the first subscriber information management message comprises a request for location information for the subscriber.
14. The method of claim 13 wherein the request for location information comprises one of: a send routing information (SRI) message;a send routing information for short message (SRI_SM) message;a location request (LOC_REQ) message; anda Diameter location information request.
15. The method of claim 13 wherein responding to the first subscriber information management message on behalf of the message destination comprises providing the location information for the subscriber.
16. The method of claim 1 wherein responding to the first subscriber information management message on behalf of the message destination node comprises at least one of: responding to a request for location update with an answer indicating that the location update is allowed; andresponding to a request for profile information by providing user profile information to the requesting entity.
17. The method of claim 1 wherein the first subscriber information management message comprises a Diameter message sent over a Cx, S6a, S6b, or Sp interface.
18. A system for using a signaling message routing node to provide backup mobility management service, the system comprising: a Diameter signaling router (DSR), the DSR including: a communications module located within the DSR for receiving a first mobility management message having a message destination and being associated with a subscriber; anda subscriber information management module located within the DSR for obtaining information associated with the subscriber, for determining whether the message destination is available to process the first subscriber information management message, for, in response to determining that the message destination is available to process the first subscriber information management message, routing the first subscriber information management message to the message destination, and, in response to determining that the message destination is not available to process the first subscriber information management message, responding to the first subscriber information management message on behalf of the message destination using the information obtained at the DSR.
19. The system of claim 18 wherein obtaining the information associated with the subscriber comprises: receiving, at the DSR, a second subscriber information management message containing the information associated with the subscriber;extracting the information associated with the subscriber from the second subscriber information management message; andstoring the extracted information associated with the subscriber at the signaling message routing node or at a node that is separate from the DSR and the message destination.
20. The system of claim 19 wherein the first and second subscriber information management messages each comprise one of: a mobile application part (MAP) protocol message; anda Diameter protocol message.
21. The system of claim 18 wherein the information associated with the subscriber comprises information identifying the subscriber.
22. The system of claim 21 wherein the information identifying the subscriber comprises at least one of: an international mobile subscriber identity (IMSI) of the subscriber; anda mobile station integrated services digital network (MSISDN) number of the subscriber.
23. The system of claim 22 wherein the network node that currently serves the subscriber comprises at least one of: a mobile switching center (MSC);a mobile switching center server (MSCS);a short message service center (SMSC); anda serving call session control function (S-CSCF).
24. The system of claim 19 wherein the information associated with the subscriber comprises information identifying the network node that currently serves the subscriber.
25. The system of claim 24 wherein the information identifying the network node that currently serves the subscriber comprises at least one of: a point code of the network node;an Internet protocol address of the network node; anda Diameter identity of the network node.
26. The system of claim 18 wherein the message destination comprises at least one of: a home location register (HLR); anda home subscriber server (HSS).
27. The system of claim 18 wherein determining whether the message destination is available to process the first subscriber information management message comprises at least one of: using at least one of a physical level protocol, a link level protocol, a network level protocol, an application level protocol, and a high availability protocol to determine whether the message destination is available to process the first subscriber information management message; andreceiving notification from an entity other than the signaling message routing node indicating that the message destination is or is not available to process the first subscriber information management message.
28. The system of claim 18 wherein the first subscriber information management message comprises a request for location information for the subscriber.
29. The system of claim 28 wherein the request for location information comprises one of: a send routing information (SRI) message;a send routing information for short message (SRI_SM) message;a location request (LOC_REQ) message; anda Diameter location information request (LIR) message.
30. The system of claim 28 wherein responding to the first subscriber information management message on behalf of the message destination comprises providing the location information for the subscriber.
31. The system of claim 18 wherein the first subscriber information management message comprises a request to update location information for the subscriber.
32. The system of claim 31 wherein the request to update location information for the subscriber comprises one of: an update location (UpdateLoc) message;a registration message; anda Diameter update location request.
33. The system of claim 18 wherein responding to the first subscriber information management message on behalf of the message destination comprises at least one of: responding to a request for location update with an answer indicating that the location update is allowed; andresponding to a request for profile information by providing user profile information to the requesting entity.
34. The system of claim 18 wherein the first subscriber information management message comprises a Diameter message sent over a Cx, S6a, S6b, or Sp interface.
35. A non-transitory computer readable medium having stored thereon executable instructions that when executed by a processor of a computer to instruct the computer to perform steps comprising: obtaining, by a Diameter signaling router (DSR), information associated with a subscriber;receiving, at the DSR, a first subscriber information management message including a message destination and being associated with the subscriber;determining, at the DSR, whether the message destination is available to process the first subscriber information management message;in response to determining that the message destination is available to process the first subscriber information management message, routing, at the DSR, the first subscriber information message to the message destination; andin response to determining that the message destination is not available to process the first subscriber information management message, responding, at the DSR, to the first subscriber information management message on behalf of the message destination using the information obtained at the DSR.

PRIORITY CLAIM

This application claims the benefit of U.S. Provisional Patent Application Ser. No. 61/308,280, filed Feb. 25, 2010; the disclosure of which is incorporated herein by reference in its entirety.

US Referenced Citations (237)

Number	Name	Date	Kind
4310727	Lawser	Jan 1982	A
4754479	Bicknell et al.	Jun 1988	A
5089954	Rago	Feb 1992	A
5237604	Ryan	Aug 1993	A
5247571	Kay et al.	Sep 1993	A
5251248	Tokunaga et al.	Oct 1993	A
5400390	Salin	Mar 1995	A
5420916	Sekiguchi	May 1995	A
5422941	Hasenauer et al.	Jun 1995	A
5423068	Hecker	Jun 1995	A
5430719	Weisser, Jr.	Jul 1995	A
5442683	Hoogeveen	Aug 1995	A
5455855	Hokari	Oct 1995	A
5457736	Cain et al.	Oct 1995	A
5475732	Pester, III	Dec 1995	A
5481603	Gutierrez et al.	Jan 1996	A
5502726	Fischer	Mar 1996	A
5504804	Widmark et al.	Apr 1996	A
5526400	Nguyen	Jun 1996	A
5579372	Äström	Nov 1996	A
5590398	Matthews	Dec 1996	A
5594942	Antic et al.	Jan 1997	A
5623532	Houde et al.	Apr 1997	A
5689548	Maupin et al.	Nov 1997	A
5706286	Reiman et al.	Jan 1998	A
5711002	Foti	Jan 1998	A
5812639	Bartholomew et al.	Sep 1998	A
5819178	Cropper	Oct 1998	A
5822694	Coombes et al.	Oct 1998	A
5832382	Alperovich	Nov 1998	A
5841854	Schumacher et al.	Nov 1998	A
5852660	Lindquist et al.	Dec 1998	A
5854982	Chambers et al.	Dec 1998	A
5862481	Kulkarni et al.	Jan 1999	A
5867788	Joensuu	Feb 1999	A
5878347	Joensuu et al.	Mar 1999	A
5878348	Foti	Mar 1999	A
5889849	Ban et al.	Mar 1999	A
5890063	Mills	Mar 1999	A
5953662	Lindquist et al.	Sep 1999	A
5953663	Maupin et al.	Sep 1999	A
5983217	Khosravi-Sichannie et al.	Nov 1999	A
6006098	Rathnasabapathy et al.	Dec 1999	A
6011803	Bicknell et al.	Jan 2000	A
6014557	Morton et al.	Jan 2000	A
6018657	Kennedy, III et al.	Jan 2000	A
6038456	Colby et al.	Mar 2000	A
6049714	Patel	Apr 2000	A
6094578	Purcell et al.	Jul 2000	A
6097960	Rathnasabapathy et al.	Aug 2000	A
6115463	Coulombe et al.	Sep 2000	A
H1895	Hoffpauir et al.	Oct 2000	H
6128377	Sonnenberg	Oct 2000	A
6134441	Äström et al.	Oct 2000	A
6134447	Havinis et al.	Oct 2000	A
6137806	Martinez	Oct 2000	A
6138007	Bharatia	Oct 2000	A
6138016	Kulkarni et al.	Oct 2000	A
6138017	Price et al.	Oct 2000	A
6138023	Agarwal et al.	Oct 2000	A
6144857	Price et al.	Nov 2000	A
6148204	Urs et al.	Nov 2000	A
6175743	Alperovich et al.	Jan 2001	B1
6178181	Glitho	Jan 2001	B1
6192242	Rollender	Feb 2001	B1
6205210	Rainey et al.	Mar 2001	B1
6208870	Lorello et al.	Mar 2001	B1
6226517	Britt et al.	May 2001	B1
6236365	LeBlanc et al.	May 2001	B1
6263212	Ross et al.	Jul 2001	B1
6292669	Meuronen et al.	Sep 2001	B1
6298232	Marin et al.	Oct 2001	B1
6308075	Irten et al.	Oct 2001	B1
6324279	Kalmanek et al.	Nov 2001	B1
6327350	Spangler et al.	Dec 2001	B1
6338140	Owens et al.	Jan 2002	B1
6356529	Zarom	Mar 2002	B1
6363431	Hammer et al.	Mar 2002	B1
6377674	Chong et al.	Apr 2002	B1
6377807	Iparrea et al.	Apr 2002	B1
6411632	Lindgren et al.	Jun 2002	B2
6421674	Yoakum et al.	Jul 2002	B1
6424832	Britt et al.	Jul 2002	B1
6434127	Ha	Aug 2002	B1
6453174	Cunningham et al.	Sep 2002	B1
6463055	Lupien et al.	Oct 2002	B1
6493551	Wang et al.	Dec 2002	B1
6505046	Baker	Jan 2003	B1
6512926	Henry-Labordere	Jan 2003	B1
6515997	Feltner et al.	Feb 2003	B1
6519242	Emery et al.	Feb 2003	B1
6519468	Donovan et al.	Feb 2003	B1
6529524	Liao et al.	Mar 2003	B1
6535746	Yu et al.	Mar 2003	B1
6560216	McNiff et al.	May 2003	B1
6560456	Lohtia et al.	May 2003	B1
6574481	Rathnasabapathy et al.	Jun 2003	B1
6577723	Mooney	Jun 2003	B1
6594258	Larson et al.	Jul 2003	B1
6611516	Pirkola et al.	Aug 2003	B1
6615037	Bharatia et al.	Sep 2003	B1
6625461	Bertacchi	Sep 2003	B1
6643511	Rune et al.	Nov 2003	B1
6662017	McCann et al.	Dec 2003	B2
6683881	Mijares et al.	Jan 2004	B1
6684073	Joss et al.	Jan 2004	B1
6697620	Lamb et al.	Feb 2004	B1
6731926	Link, II et al.	May 2004	B1
6738636	Lielbriedis	May 2004	B2
6745041	Allison et al.	Jun 2004	B2
6795701	Baker et al.	Sep 2004	B1
6801781	Provost et al.	Oct 2004	B1
6819932	Allison et al.	Nov 2004	B2
6826397	Vasa	Nov 2004	B1
6836477	West, Jr. et al.	Dec 2004	B1
6850768	Foll	Feb 2005	B2
6865191	Bengtsson et al.	Mar 2005	B1
6885872	McCann et al.	Apr 2005	B2
6912389	Bright et al.	Jun 2005	B2
6917612	Foti et al.	Jul 2005	B2
6950441	Kaczmarczyk et al.	Sep 2005	B1
6993038	McCann	Jan 2006	B2
7035239	McCann et al.	Apr 2006	B2
7039037	Wang et al.	May 2006	B2
7043002	Delaney et al.	May 2006	B2
7079524	Bantukul et al.	Jul 2006	B2
7079853	Rathnasabapathy et al.	Jul 2006	B2
7092505	Allison et al.	Aug 2006	B2
7113795	Somani et al.	Sep 2006	B2
7113800	Linkola	Sep 2006	B2
7145875	Allison et al.	Dec 2006	B2
7177398	Meer et al.	Feb 2007	B2
7177399	Dawson et al.	Feb 2007	B2
7181194	McCann et al.	Feb 2007	B2
7190959	Palmer et al.	Mar 2007	B2
7221929	Lee et al.	May 2007	B2
7221952	Cho et al.	May 2007	B2
7257401	Dizdarevic et al.	Aug 2007	B1
7274683	Segal	Sep 2007	B2
7286839	McCann et al.	Oct 2007	B2
7292592	Rune	Nov 2007	B2
7366945	Wang et al.	Apr 2008	B2
7397773	Qu et al.	Jul 2008	B2
7453876	Hua et al.	Nov 2008	B2
7551608	Roy	Jun 2009	B1
7583646	Hua et al.	Sep 2009	B2
7627331	Winterbottom et al.	Dec 2009	B2
7668543	Muller	Feb 2010	B2
7729485	Koskinen et al.	Jun 2010	B2
7746864	Asawa et al.	Jun 2010	B1
7801116	Westman	Sep 2010	B2
7844745	Darbyshire et al.	Nov 2010	B1
7848767	McCann et al.	Dec 2010	B2
7889716	Tejani et al.	Feb 2011	B2
7894353	Li et al.	Feb 2011	B2
7916857	Palmer et al.	Mar 2011	B2
7962120	Cai et al.	Jun 2011	B2
8041349	Fukui et al.	Oct 2011	B2
8175236	Pandey et al.	May 2012	B2
8194634	Delker et al.	Jun 2012	B2
8195161	Bumiller	Jun 2012	B2
8208461	Mitchell	Jun 2012	B2
8380209	Sylvain	Feb 2013	B1
8391833	Agarwal	Mar 2013	B2
20010006897	Kang et al.	Jul 2001	A1
20010029182	McCann et al.	Oct 2001	A1
20010030957	McCann et al.	Oct 2001	A1
20010040957	McCann et al.	Nov 2001	A1
20010046856	McCann	Nov 2001	A1
20020132636	Stockhusen	Sep 2002	A1
20020147845	Sanchez-Herrero et al.	Oct 2002	A1
20020173320	Aitken et al.	Nov 2002	A1
20020176382	Madour et al.	Nov 2002	A1
20030003930	Allison et al.	Jan 2003	A1
20030007482	Khello et al.	Jan 2003	A1
20030016684	Prasad et al.	Jan 2003	A1
20030026289	Mukherjee et al.	Feb 2003	A1
20030054844	Anvekar et al.	Mar 2003	A1
20030061234	Ali et al.	Mar 2003	A1
20030065788	Salomaki	Apr 2003	A1
20030081754	Esparza et al.	May 2003	A1
20030109271	Lewis et al.	Jun 2003	A1
20030157938	Haase et al.	Aug 2003	A1
20030193967	Fenton et al.	Oct 2003	A1
20030227899	McCann	Dec 2003	A1
20040076126	Qu et al.	Apr 2004	A1
20040081206	Allison et al.	Apr 2004	A1
20040082332	McCann et al.	Apr 2004	A1
20040087300	Lewis	May 2004	A1
20040125925	Marsot	Jul 2004	A1
20040132451	Butehorn et al.	Jul 2004	A1
20040142707	Midkiff et al.	Jul 2004	A1
20040198351	Knotts	Oct 2004	A1
20040202187	Kelly et al.	Oct 2004	A1
20040203914	Kall et al.	Oct 2004	A1
20040219935	McCann et al.	Nov 2004	A1
20040246965	Westman et al.	Dec 2004	A1
20040264674	Delaney et al.	Dec 2004	A1
20050003838	McCann et al.	Jan 2005	A1
20050111641	Koskinen et al.	May 2005	A1
20050119017	Lovell, Jr. et al.	Jun 2005	A1
20050238048	Delaney et al.	Oct 2005	A1
20060034256	Addagatla et al.	Feb 2006	A1
20060067338	Hua et al.	Mar 2006	A1
20060098621	Plata et al.	May 2006	A1
20060136557	Schaedler et al.	Jun 2006	A1
20060281492	Jiang	Dec 2006	A1
20070061397	Gregorat et al.	Mar 2007	A1
20070066326	Agarwal et al.	Mar 2007	A1
20070104184	Ku et al.	May 2007	A1
20070133574	Tejani et al.	Jun 2007	A1
20070209061	Dekeyzer et al.	Sep 2007	A1
20070254681	Horvath et al.	Nov 2007	A1
20070258575	Douglas et al.	Nov 2007	A1
20070288655	Price et al.	Dec 2007	A1
20070297419	Askerup et al.	Dec 2007	A1
20080039104	Gu et al.	Feb 2008	A1
20080176538	Terrill et al.	Jul 2008	A1
20080233931	Shim	Sep 2008	A1
20080248820	Lohtia	Oct 2008	A1
20090003388	Florkey et al.	Jan 2009	A1
20090129372	Pandey et al.	May 2009	A1
20090227276	Agarwal et al.	Sep 2009	A1
20090232011	Li et al.	Sep 2009	A1
20100113016	Gayde et al.	May 2010	A1
20100217858	Przybysz et al.	Aug 2010	A1
20100250662	Agarwal et al.	Sep 2010	A1
20100278041	Shi	Nov 2010	A1
20100299451	Yigang et al.	Nov 2010	A1
20110067085	Brouard et al.	Mar 2011	A1
20110222532	Noldus	Sep 2011	A1
20120034900	Agarwal	Feb 2012	A1
20120163297	Agarwal et al.	Jun 2012	A1
20120202550	Marsico	Aug 2012	A1
20120224524	Marsico	Sep 2012	A1
20120287844	Ophir et al.	Nov 2012	A1
20130157620	Marsico	Jun 2013	A1

Foreign Referenced Citations (38)

Number	Date	Country
ZL200680051295.9	Mar 2013	CN
0 512 962	Nov 1992	EP
0 788 283	Aug 1997	EP
0 936 825	Aug 1999	EP
0 944 276	Sep 1999	EP
1 558 004	Jul 2005	EP
1 742 452	Jan 2007	EP
1 950 942	Jul 2008	EP
10-2004-0107271	Dec 2004	KR
WO 9512292	May 1995	WO
WO 9611557	Apr 1996	WO
WO 9733441	Sep 1997	WO
WO 9856195	Dec 1998	WO
WO 9911087	Mar 1999	WO
WO 9957926	Nov 1999	WO
WO 0016583	Mar 2000	WO
WO 0147297	Jun 2001	WO
WO 0148981	Jul 2001	WO
WO 0154444	Jul 2001	WO
WO 02060192	Aug 2002	WO
WO 03005664	Jan 2003	WO
WO 03021982	Mar 2003	WO
WO 03105382	Dec 2003	WO
WO 2004006534	Jan 2004	WO
WO 2004008786	Jan 2004	WO
WO 2004075507	Sep 2004	WO
WO 2004102345	Nov 2004	WO
WO 2005002311	Jan 2005	WO
WO 2005013538	Feb 2005	WO
WO 2006072473	Jul 2006	WO
WO 2007045991	Apr 2007	WO
WO 2007064943	Jun 2007	WO
WO 2007092205	Aug 2007	WO
WO 2007146257	Dec 2007	WO
WO 2008157213	Dec 2008	WO
WO 2009023573	Feb 2009	WO
WO 2010111561	Sep 2010	WO
WO 2012088497	Jun 2012	WO

Non-Patent Literature Citations (99)

Entry
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2011/026307 (Nov. 15, 2011).
Communication under Rule 71(3) EPC for European Application No. 06 844 747.3 (Jul. 19, 2011).
Chinese Official Action for Chinese Patent Application No. 200680051295.9 (Dec. 24, 2010).
Notification of Transmittal of the Initernational Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2010/028762 (Oct. 27, 2010).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/291,502 (Oct. 5, 2010).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 10/405,859 (Aug. 5, 2010).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/706,837 (May 27, 2010).
Communication Pursuant to Article 94(3) EPC for European Application No. 06844747.3 (May 11, 2010).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 10/405,859 (Mar. 9, 2010).
Final Official Action for U.S. Appl. No. 11/291,502 (Feb. 4, 2010).
“Diameter (Protocol),” Wikipedia, pp. 1-8 (Document last modified on Jan. 16, 2010).
Final Official Action for U.S. Appl. No. 11/706,837 (Dec. 15, 2009).
Interview Summary for U.S. Appl. No. 11/706,837 (Oct. 26, 2009).
Official Action for U.S. Appl. No. 10/405,859 (Aug. 3, 2009).
Communication pursuant to Article 94(3) EPC for European application No. 06844747.3 (Jul. 28, 2009).
Official Action for U.S. Appl. No. 11/706,837 (May 13, 2009).
Official Action for U.S. Appl. No. 11/291,502 (May 13, 2009).
Supplementary European Search Report for European Application No. 06844747.3 (Apr. 24, 2009).
Final Official Action for U.S. Appl. No. 10/405,859 (Jan. 6, 2009).
3GPP, “Digital Cellular Telecommunications System (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling Flows and Message Contents,” ETSI TS 129 228 V8.4.0 (Jan. 2009).
Notification Concerning Transmittal of International Preliminary Report on Patentability for International Application No. PCT/US2006/046108 (Oct. 2, 2008).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2006/046108 (Sep. 9, 2008).
Interview Summary for U.S. Appl. No. 10/405,859 (Aug. 20, 2008).
Official Action for U.S. Appl. No. 11/706,837 (Jul. 29, 2008).
Communication of European publication number and information on the application of Article 67(3) EPC for Application No. 06844747.3 (Jul. 23, 2008).
Official Action for U.S. Appl. No. 10/405,859 (Mar. 17, 2008).
Restriction Requirement for U.S. Appl. No. 10/405,859 (Feb. 6, 2008).
“IP Multimedia Subsystem,” printout from wikipedia.org, Wikimedia Foundation, Inc. (May 29, 2007).
Supplementary European Search Report for European application No. 04 756 094.1 (Mar. 29, 2007).
“HP OpenCall Home Subscriber Server Software—Data Sheet”, 4AA0-3360ENW Rev. 2, Hewlett-Packard Development Company, L.P. (Jul. 2006).
Camarillo et al., “The Session Initiation Protocol (SIP) P-User-Database Private-Header (P-Header),” Network Working Group, RFC 4457, pp. 1-8 (Apr. 2006).
Liu et al., “Introduction to Diameter,” IBM, pp. 1-12 (Jan. 24, 2006).
“Cisco IP Transfer Point as the Signaling Gateway for the Cisco BTS 10200 Softswitch,” Cisco Systems, Inc., pp. 1-10 (Summer 2004).
“Cisco IP Transfer Point as the Signaling Gateway for the Cisco PGW 2200 Softswitch,” Cisco Systems, Inc., pp. 1-11 (Summer 2004).
“Next-Generation Signaling Transports Cisco IP Transfer Point,” Cisco Systems, Inc., pp. 1-27 (Summer 2004).
International Search Report in PCT Application No. 03/32626 (Mar. 5, 2004).
“A Study in Mobile Messageing: The Evolution of Messaging in Mobile Networks, and How to Efficiently and Effectively Manage the Growing Messaging Traffic,” White Paper, Cisco Systems, Inc., pp. 1-6 (Spring 2004).
Walker, “The IP Revolution in Mobile Messaging,” Packet, Cisco Systems Users Magazine, vol. 16, No. 1, pp. Cover; 73-74; and 89 (First Quarter 2004).
“Cisco ITP Multilayer Routing (MLR) SMS MO Routing Requirements,” Cisco Systems, Inc., p. 1 (Copyright 2004).
“Cisco Signaling Gateway Manager Release 3.2 For Cisco IP Transfer Point,” Cisco Systems, Inc., pp. 1-9 (Copyright 1992-2004).
“Solutions for Mobile Network Operators,” Cisco Systems, Inc., pp. 1-8 (Copyright 1992-2004).
Moodie, “Agilent acceSS7: White Paper,” Agilent Technologies, pp. 1-14 (Apr. 1, 2003).
“Cisco IP Transfer Point,” Cisco Systems, Inc., pp. 1-10 (Copyright 1992-2003).
“Cisco IP Transfer Point Multilayer Short Message Service Routing Solution,” Cisco Systems, Inc., pp. 1-6 (Copyright 1992-2003).
“Cisco ITP MAP Gateway for Public WLAN Slm Authentication and Authorization,” Cisco Systems, Inc., pp. 1-13 (Copyright 1992-2003).
Barry, “A Signal for Savings,” Packet, Cisco Systems Users Magazine, vol. 14, No. 4, pp. Cover; 19-21; and 81 (Fourth Quarter 2002).
“Agilent Technologies and Cisco Systems SS7 Over IP White Paper,” Cisco Systems, Inc. and Agilent and Technologies, pp. 1-6 (Copyright 2002—Printed in the UK Feb. 1, 2002).
“Cisco IP Transfer Point: MTP3 User Adaptation (M3UA) and SCCP User Adaptation (SUA) Signaling Gateway,” Cisco Systems, Inc., pp. 1-14 (Copyright 2002).
“Cisco SS7 Port Adapter for the Cisco 7500 Versatile Interface Processor and 7200 VXR Routers Provide High-Density SS7 Agrregation,” Cisco Systems, Inc., pp. 1-5 (Copyright 1992-2002).
“Next-Generation SS7 Networks with the Cisco IP Transfer Point,” Cisco Systems, Inc., pp. 1-14 (Copyright 1992-2002).
The attached email dated Oct. 20, 2001 and PowerPoint presentation dated Oct. 24, 2001 disclose an MSISDN-based auto-provisioning solution proposed by a customer of the assignee of the presend application.
“Agilent acceSS7 Business intelligence,” Agilent Technologies, pp. 1-6 (Copyright 2001—Printed in the UK Nov. 30, 2001).
“Cisco IP Transfer Point (ITP) Network Management Product Presentation,” Cisco Systems, Inc., pp. 1-20 (Copyright 2001).
“Networkers,” Cisco Systems, Inc., pp. 1-60 (Copyright 2001).
“Cisco SS7 Signaling Offload,” Cisco Systems, Inc., pp. 1-33 (Copyright 1992-2001).
Rockhold, “Or,” Wireless Review, p. 22, 23, 26, 28, 30, 32, (Aug. 15, 2000).
Bertrand, “Jambala Mobility Gateway-Convergence and Inter-System Roaming,” Ericsson Review, p. 89-93 (1999).
“Topsail Beach—SS7 Over IP−” Cisco Systems, Inc., pp. 1-16 (Copyright 1999).
ETSI, “Digital Cellular Telecommunications Systems (Phase 2+); Support of Mobile Number Portability (MNP); Technical Realisation; Stage 2,” Global System for Mobile Communications, p. 1-71, (1998).
Smith, “Number Portability Pileup,” Telephony, p. 22, 24, 26 (Jan. 6, 1997).
Jain et al., “Phone Number Portability for PCS Systems with ATM Backbones Using Distributed Dynamic Hashing,” IEEE, vol. 15 (No. 1), p. 96-105, (Jan. 1997).
Heinmiller, “Generic Requrements for SCP Application and GTT Function for Number Portability,” Illinois Number Portability Workshop, p. 1-50, (Sep. 4, 1996).
International Telecommunication Union, “Series Q: Switching and Signalling: Specifications of Signalling Systems No. 7—Signalling Connection Control Part,” p. 11-16, (Jul. 1996).
Rice, “SS7 Networks in a PCS World,” Telephony, pp. 138, 140 142, 144, 146, (Jun. 24, 1996).
TEKELEC, “Eagle STP Planning Guide”, Eagle Network Switching Division, (No. 3), p. i-vii, 1-64, A1-A2, B1-2, (May 1996).
Anonymous, “Generic Switching and Signaling Requirements for Number Portability,” AT&T Network Systems, No. 1, p. 1-75, (Feb. 2, 1996).
ETSI, Digital Cellular Telecommunications System (Phase 2+); Mobile Application Part (MAP) Specification, Global System for Mobile Communications, pp. 112-114 (1996).
Jain, et al., “A Hashing Scheme for Phone Number Portability in PCS Systems with ATM Backbones,” Bell Communications Research, p. 593-597, (1996).
Bishop, “Freeing the Network for Competition,” Telecommunications, p. 75-80, (Apr. 1995).
Anonymous, “Zeichengabesysteme-Eine neue Generation für ISDN und intelligente Netze,” Zeichengabesystem, Medien-Institut Bremen, p. iz-xi; 170-176, (Feb. 17, 1995).
Giordano et al., “PCS Number Portability,” IEEE, p. 1146-1150, (Sep. 1994).
Bellcore, “Signaling Transfer Point (STP) Generic Requirements,” Bell Communications Research, No. 1, p. ii-xxii, 4-84-J14, (Jun. 1994).
Telcordia Technologies, “CCS Network interface Specifications (CCSNIS) Supporting SCCP and TCAP,” Bell Communications Research, p. ii-xii, 1-1-C-22, (Mar. 1994).
Buckles, “Very High Capacity Signaling Transfer Point for Intelligent Network Servcies,” DSC Communications Corporation, p. 1308-1311, (1988).
“Diameter Overview,” referenced from www.ulticom.com/html/products/signalware-diameter-reference-guide.asp (Publication date unknown).
“Chapter 1: Overview,” SS7 Port Adapter Installation and Configuration, pp. 1-1-1-8 (Publication Date Unknown).
“Configuring ITP Basic Functionality,” IP Transfer Point, Cisco IOS Release 12.2(4)MB12, pp. 31-50 (Publication Date Unknown).
“Configuring ITP Optional Features,” IP Transfer Point, Cisco IOS Release 12.294)MB12, pp. 65-136 (Publication Date Unknown).
“Configuring M3UA and SUA SS7 Over IP Signaling Gateways,” IP Transfer Point, Cisco IOS Release 12.2(4)MB13, pp. 51-66 (Publication Date Unknown).
“Configuring M3UA and SUA SS7 Over IP Signaling Gateways,” IP Transfer Point, Cisco IOS Release 12.2(4)MB10, pp. 49-62 (Publication Date Unknown).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2011/067130 (Jun. 7, 2012).
Commonly-assigned, co-pending U.S. Appl. No. 13/336,132 for “Methods, Systems, and Computer Readable Media for Modifying a Diameter Signaling Message Directed to a Charging Function Node,” (Unpublished, filed Dec. 23, 2011).
Commonly-assigned, co-pending International Application No. PCT/US11/67130 for “Methods, Systems, and Computer Readable Media for Modifying a Diameter Signaling Message Directed to a Charging Function Node,” (Unpublished, filed Dec. 23, 2011).
U.S. Appl. No. 61/576,213 for “LTE HSS with HLR Proxy Mode for Mobility” (Unpublished, filed Dec. 15, 2011).
Korhonen et al., “Clarifications on the Routing of Diameter Requests Based on the Username and the Realm,” RFC 5729, pp. 1-12 (Dec. 2009).
Korhonen et al., “Diameter User-Name and Realm Based Request Routing Clarifications,” draft-ietf-dime-nai-routing-04.txt, pp. 1-13 (Oct. 6, 2009).
“3rd Generation Partnership Project; Technical Specifications Group Service and System Aspects; Telecommunication management; Charging management; Diameter charging applications (Release 7),” 3GPP TS 32.299, V7.7.0, pp. 1-120 (Sep. 2007).
Non-Final Office Action for U.S. Appl. No. 12/732,178 (Nov. 6, 2012).
Final Office Action for U.S. Appl. No. 12/732,178 (Jun. 17, 2013).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/336,132 (May 20, 2013).
First Examination Report for Indian Application No. 3231/CHENP/2008 (Jan. 2, 2013).
Non-Final Office Action for U.S. Appl. No. 13/336,132 (Dec. 18, 2012).
Commonly-assigned, co-pending U.S. Appl. No. 13/714,360 for “Methods, Systems, and Computer Readable Media for Seamless Roaming Between Diameter and Non-Diameter Networks,” (Unpublished, filed Dec. 13, 2012).
U.S. Appl. No. 61/291,961 for “A GTP Relay for Direct Internet Access from the Roaming Mobile Network and Other Services,” (Unpublished, filed Jan. 4, 2010).
Calhoun et al., “Diameter Base Protcol,” Network Working Group, RFC 3588 (Sep. 2003).
Communication of European publication No. and information on the application of Article 67(3) EPC for European Application No. 11852129.3 (Oct. 2, 2013).
Second Examination Report for Indian Application No. 3231/CHENP/2008 (Aug. 6, 2013).
Applicant-Initiated Interview Summary for U.S. Appl. No. 12/732,178 (Sep. 26, 2013).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/336,132 (Sep. 23, 2013).

Related Publications (1)

	Number	Date	Country
	20110211527 A1	Sep 2011	US

Provisional Applications (1)

	Number	Date	Country
	61308280	Feb 2010	US

Systems, methods, and computer readable media for using a signaling message routing node to provide backup subscriber information management service

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

US Classifications

Field of Search

US

International Classifications

Abstract