SYSTEM AND METHOD FOR ROUTING COMMUNICATIONS TO MOBILE STATIONS

• US 20080002710A1
• Filed: 06/29/2006
• Published: 01/03/2008
• Est. Priority Date: 06/29/2006
• Status: Abandoned Application

• Current Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Original Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Inventors: Lau, Jason W., Wilson, Timothy J., Upp, Steven D., Idnani, Ajaykumar R.
• Application Number:
  US11/427,550
• Publication Number:
  US 20080002710A1
• Time in Patent Office: Days
• US Class Current: 370/395.2
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1083 In-session procedures
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]

Abstract

A Session Initiation Protocol (SIP)-compliant proxy (106) receives a first INVITE message destined for a mobile station (102). The first INVITE message is associated with an initial Internet Protocol (IP) contact address for the mobile station (102). Subsequently, it is determined whether an IP address update for the mobile station (102) may have occurred and a new IP contact address is obtained for the mobile station (102). A second INVITE message is sent to the mobile station (102) at the new contact address so as to continue a session initiation.

Claims

1. A method of transmitting information in a network comprising:

at a Session Initiation Protocol (SIP)-compliant proxy;

receiving a first INVITE message destined for a mobile station, the first INVITE message being associated with an initial Internet Protocol (IP) contact address for the mobile station;

subsequently determining whether an IP address update for the mobile station has occurred and obtaining a new IP contact address for the mobile station; and

sending a second INVITE message to the mobile station at the new contact address so as to continue a session initiation.

2. The method of claim 1 wherein determining whether an IP address update has occurred comprises receiving a retry attempt of the first INVITE message.

3. The method of claim 1 wherein determining whether an IP address update has occurred comprises receiving an update message from a SIP-compliant registrar indicating that the address update has occurred.

4. The method of claim 1 wherein determining whether an IP address update has occurred comprises determining that a predetermined period of time has elapsed.

5. The method of claim 4 wherein sending the second INVITE message comprises sending the second INVITE message from the SIP-compliant proxy to the mobile station with the new contact address upon expiration of the predetermined period of time.

6. A method of transmitting information in a network comprising:

at a mobile station;

operating at and receiving communications at a first Internet Protocol (IP) address;

acquiring a second IP address, the second IP address being a new operating address of the mobile station;

registering the second IP address at a Session Initiation Protocol (SIP)-compliant registrar and subsequently receiving an INVITE message;

subsequent to registering the second IP address, initializing an IP stack at the mobile station to use the second IP address; and

preventing an occurrence of a race condition at the mobile station because of the mobile station operating at the second IP address.

7. The method of claim 6 wherein receiving an INVITE message comprises receiving an INVITE message associated with the first IP address, and wherein preventing an occurrence of a race condition comprises sending a redirect message to a SIP-compliant proxy, the message indicating that the mobile station has moved to the second IP address.

8. The method of claim 7, wherein the INVITE message comprises a first INVITE message and wherein the method further comprises successfully receiving a second INVITE message associated with the second IP address.

9. The method of claim 6 further comprising successfully receiving a retry attempt of the INVITE message, the INVITE message being associated with the second IP address.

10. The method of claim 6, wherein receiving an INVITE message comprises receiving an INVITE message that has been delayed until the IP stack at the mobile station has been initialized to use the second IP address.

11. A Session Initiation Protocol (SIP)-compliant proxy comprising:

a receiver having an input that receives a first INVITE message destined for a mobile station, the first INVITE message having an initial Internet Protocol (IP) contact address;

a transmitter having an output; and

a controller coupled to the receiver and the transmitter, the controller being programmed to determine whether an address update has occurred and to responsively obtain a new IP contact address for the mobile station, the controller being further programmed to responsively send a second INVITE message to the mobile station at the output of the transmitter, the second INVITE message associated with the new IP contact address so as to continue a session initiation.

12. The SIP-compliant proxy of claim 11 wherein the controller determines that an address update has occurred based upon reception of a retry attempt of the first INVITE message at the input of the receiver.

13. The SIP-compliant proxy of claim 11 wherein the controller determines that an address update has occurred based upon the reception of an update message from a SIP-compliant registrar at the input of the receiver.

14. The SIP-compliant proxy of claim 11 further comprising a timer that operably couples to the controller and wherein the controller is further programmed to determine that an address update has occurred based upon expiration of a predetermined time period at the timer.

15. The SIP-compliant proxy of claim 11 wherein the controller obtains the new IP contact address from a registration database.

16. A mobile station that is configured to operate at and receive communications at a first Internet Protocol (IP) address, acquire a second IP address, the second IP address being a new operating address of the mobile station, register the second IP address at a Session Initiation Protocol (SIP)-compliant registrar and subsequently receive an INVITE message, subsequent to registering the second IP address, initialize a stack at the mobile station to use the second IP address, and prevent an occurrence of a race condition at the mobile station because of the mobile station operating at the second IP address.

17. The mobile station of claim 16, wherein the mobile station is configured to receive an INVITE message by receiving an INVITE message associated with the first IP address, and wherein the mobile station prevents an occurrence of a race condition by sending a redirect message to a SIP-compliant proxy, the message indicating that the mobile station has moved to the second IP address.

18. The mobile station of claim 17, wherein the INVITE message comprises a first INVITE message and wherein the mobile station is further configured to successfully receive a second INVITE message associated with the second IP address.

19. The mobile station of claim 16, wherein the mobile station further is configured to successfully receive a retry attempt of the INVITE message, the INVITE message being associated with the second IP address.

20. The mobile station of claim 16, wherein the mobile station is configured to receive an INVITE message by receiving an INVITE message that has been delayed until the IP stack at the mobile station has been initialized to use the second IP address.