Methods and systems for automatically provisioning address translation information in a mobile services node address translation database

• US 20030227899A1
• Filed: 06/11/2002
• Published: 12/11/2003
• Est. Priority Date: 06/11/2002
• Status: Active Grant

• Current Assignee: Tekelec
• Original Assignee: Tekelec
• Inventors: McCann, Thomas Matthew
• Granted Patent: US 6,993,038 B2
• Time in Patent Office: Days
• US Class Current: 370/349
• CPC Class Codes: H04Q 2213/13097 Numbering, addressing
• CPC Class Codes: H04Q 2213/13098 Mobile subscriber
• CPC Class Codes: H04Q 2213/13102 Common translator
• CPC Class Codes: H04Q 2213/13103 Memory
• CPC Class Codes: H04Q 2213/13141 Hunting for free outlet, circuit or channel
• CPC Class Codes: H04Q 2213/13176 Common channel signaling, CCS7
• CPC Class Codes: H04Q 2213/13345 Intelligent networks, SCP
• CPC Class Codes: H04Q 3/0025 Provisions for signalling
• CPC Class Codes: H04W 4/18 Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
• CPC Class Codes: H04W 40/248 Connectivity information update
• CPC Class Codes: H04W 40/28 for reactive routing
• CPC Class Codes: H04W 8/12 between location registers or mobility servers
• CPC Class Codes: H04W 8/18 Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
• CPC Class Codes: H04W 8/26 Network addressing or numbering for mobility support
• CPC Class Codes: H04W 92/24 between backbone network devices

Abstract

An auto-provisioning routing node including a mobile services node network address translation database and an auto-provisioning function for automatically provisioning the database is disclosed. The auto-provisioning routing node receives signaling messages that require network address translation services. The auto-provisioning routing node routes messages for which no translations exist to a default mobile services node and adds entries for the corresponding IMSIs in its mobile services node network address translation database. The default mobile services node determines whether it has records for these messages. If the default mobile services node does not have records for these messages, the default mobile services node routes the messages to a second mobile services node via the routing node. The routing node updates entries for IMSIs in the mobile services node network address translation database based on the information inserted by the default mobile services node. This process may continue by mobile services nodes routing to subsequent nodes, with the routing node continuing to update its database, until the mobile services node containing the IMSI is found.

Claims

1. A method for automatically provisioning a mobile services node address translation database, the method comprising:

(a) receiving a signaling message including first and second identifiers located in first and second portions of the signaling message;

(b) determining whether the first identifier matches the second identifier; and

(c) in response to determining that the first identifier does not match the second identifier, updating an entry corresponding to the second identifier in a mobile services node address translation database to include the first identifier as a mobile services node entity address.

2. The method of claim 1 wherein receiving signaling message including first and second identifiers located in first and second portions of the message includes receiving a MAP UpdateLocation message including an entity address of an HLR located in an SCCP portion of the MAP UpdateLocation message and an international mobile subscriber identifier located in a MAP portion of the MAP UpdateLocation message.

3. The method of claim 2 wherein receiving a MAP Update Location message includes receiving the MAP UpdateLocation message from an HLR that did not contain a record corresponding to the signaling message.

4. The method of claim 1 wherein receiving a signaling message including first and second identifiers located in first and second portions of the signaling message includes receiving a MAP UpdateLocation message including matching IMSIs in the MAP and SCCP portions of the signaling message, and wherein the method further comprises in response to determining the presence of matching IMSIs in the signaling message, performing a lookup in the mobile services node address translation database using one of the IMSIs.

5. The method of claim 4 comprising in response to failing to locate an entry corresponding to the IMSI in the mobile services node address translation database, inserting a record in the database corresponding to the IMSI and adding an entity address corresponding to a default mobile services node to the record.

6. The method of claim 4 comprising in response to locating a record in the mobile services node address translation database, extracting an entity address from the record and routing the UdateLocation message to the mobile services node corresponding to the entity address.

7. The method of claim 1 comprising routing the signaling message to a mobile services node corresponding to the first identifier.

8. The method of claim 7 wherein routing the signaling message to a mobile services node includes routing a signaling message to an HLR.

9. A method for automatically provisioning a mobile services node address translation database with records matching mobile subscriber identifiers to mobile services node network addresses, the method comprising:

(a) receiving signaling messages at a routing node, each signaling message having an IMSI;

(b) adding entries corresponding to the IMSIs to a mobile service node address translation database located in the routing node;

(c) adding an entity address of a default mobile service node to each entry;

(d) routing the signaling messages to the default mobile services node;

(e) at the default mobile services node, for each signaling message, accessing a mobile subscriber database and determining whether a record corresponding to the IMSI exists;

(f) in response to failing to locate a record corresponding to the IMSI, inserting an entity address in the message corresponding to a second mobile services node and routing the signaling message to the second mobile services node via the routing node; and

(g) at the routing node, receiving the signaling message for which a record corresponding to the IMSI did not exist at the default mobile services node and updating an entry corresponding to the IMSI in the mobile services address translation database to include the entity address inserted by the default mobile services node.

10. The method of claim 9 wherein receiving signaling messages includes receiving a MAP UpdateLocation messages.

11. The method of claim 9 wherein routing signaling messages to the default mobile services node includes routing the signaling message to a default home location register.

12. The method of claim 9 wherein adding entries to the mobile services node address translation database includes adding entries to an IMSI b-tree in the mobile services node address translation database.

13. The method of claim 9 wherein routing the signaling message to a second mobile services node includes inserting the entity address for the second mobile services node in a global title address field of the signaling message.

14. The method of claim 13 comprising, at the routing node, global title translating the entity address into a network address for the second mobile services node.

15. The method of claim 9 comprising using the updated entry in the mobile services node address translation message to translate IMSIs in subsequently-received signaling messages.

16. An auto-provisioning routing node comprising:

(a) a first communications module for sending and receiving signaling messages over external signaling links;

(b) a mobile services node address translation database for storing mappings between mobile subscriber identifiers in the signaling messages and network addresses of destination mobile services nodes for the signaling messages; and

(c) an auto-provisioning function operatively associated with the mobile services node address translation database for comparing first and second identifiers in the signaling messages, and, in response to determining that the first and second identifiers in the signaling messages do not match, updating records in the mobile services node address translation database to include the first identifiers as mobile services node network addresses corresponding to the second identifiers.

17. The auto-provisioning routing node of claim 16 wherein the communications module comprises an SS7 link interface module.

18. The auto-provisioning routing node of claim 16 wherein the communications module comprises a data communications module for communicating SS7 messages over an IP network.

19. The auto-provisioning routing node of claim 16 wherein the mobile services node network address translation database stores IMSI-to mobile-services-node address translations.

20. The auto-provisioning routing node of claim 19 wherein the IMSI-to mobile-services-node address translations comprise IMSI-to-HLR address translations.

21. The auto-provisioning routing node of claim 16 wherein the signaling messages include MAP UpdateLocation messages and wherein the auto-provisioning function is adapted to compare IMSI values stored in the MAP portion of the UpdateLocation messages with global title addresses stored in the SCCP portions of the signaling messages.

22. The auto-provisioning routing node of claim 21 wherein the auto-provisioning function is adapted to search the mobile services node network address translation database in response to determining that the MAP IMSI matches the global title address.

23. The auto-provisioning routing node of claim 22 wherein, in response to failing to locate an entry in the mobile services node address translation database, the auto-provisioning function is adapted to add a record to the mobile services node address translation database and insert a default mobile services node routing node address in the record.

24. The auto-provisioning routing node of claim 16 comprising a routing function operatively associated with the auto-provisioning function for routing messages to mobile services nodes corresponding to mobile services node network addresses extracted from the mobile services node address translation database.

25. A system for automatically provisioning a mobile services node address translation database, the system comprising:

(a) a routing node including a mobile services address translation database and an auto-provisioning function for automatically provisioning translations from IMSIs to mobile services node addresses in the mobile services node address translation database based on signaling messages received by the routing node; and

(b) n mobile services nodes operatively associated with the routing node, n being an integer of at least two, wherein the n mobile services nodes are adapted to successively route signaling messages to each other through the routing node in response to failing to locate subscriber records corresponding to the received signaling messages.

26. The system of claim 25 wherein the routing node comprises a signal transfer point.

27. The system of claim 25 wherein the routing node comprises an SS7/IP gateway.

28. The system of claim 25 wherein the mobile services nodes comprise home location registers.

29. The system of claim 25 wherein the auto-provisioning function is adapted to automatically provision IMSI-to-HLR translations in the mobile services node address translation database based on the signaling messages.