System and method to provide interoperability between session initiation protocol and other messaging services

• US 20040199649A1
• Filed: 03/31/2003
• Published: 10/07/2004
• Est. Priority Date: 03/31/2003
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Rooke, Michael, Tarnanen, Teemu
• Application Number:
  US10/405,049
• Publication Number:
  US 20040199649A1
• Time in Patent Office: Days
• US Class Current: 709/230
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/59 Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A system and method is provided that allows alternative messaging routes when Session Initiation Protocol (SIP) message delivery fails. Automatic retry mechanisms are put into place to automatically retry transmission of a failed SIP message. In one embodiment, a mobile terminal having received a failed SIP delivery message, automatically instantiates a Short Message Service (SMS) message delivery. In another embodiment, a Short Message Service Center (SMSC)/SIP proxy instantiates message retry mechanisms based on a previously configured schedule. A legacy SMS device may also initiate an SMS message to the SMSC/SIP proxy, whereby the SMSC/SIP proxy initiates either SMS or SIP retry mechanisms.

Claims

1. A method for retrying a failed message delivery attempt, comprising:

transmitting a message of a first protocol type along a first transmission path;

receiving an indication of a failed delivery of the message;

converting the message of a first protocol type to a message of a second protocol type; and

transmitting the message of the second protocol type along a second transmission path.

2. The method according to claim 1, wherein transmitting the message of the first protocol type comprises:

resolving addresses of relay network elements along the first transmission path; and

maintaining a record of the resolved addresses.

3. The method according to claim 2, wherein the indication of the failed message delivery uses the record of resolved addresses to traverse the first transmission path.

4. The method according to claim 2, wherein converting the message of the first protocol type comprises:

transferring a portion of the resolved addresses from the message of the first protocol type to a header of the second protocol type; and

transferring a message content from the message of the first protocol type to a message content of the second protocol type.

5. The method according to claim 1, wherein transmission attempts of the message of the second protocol type occur until delivery is successful.

6. The method according to claim 1, wherein transmission attempts of the message of the second protocol type occur until a predetermined number of retries has occurred.

7. The method according to claim 1, wherein the first protocol type includes Session Initiation Protocol (SIP).

8. The method according to claim 1, wherein the second protocol type includes a protocol consistent with Short Messaging Service (SMS).

9. A messaging system, comprising:

a first terminal coupled to transmit a message in a first format;

a plurality of network elements coupled to relay the message; and

a second terminal coupled to receive the message, wherein a failed attempt to receive the message causes a retransmission of the message in a second format.

10. The messaging system according to claim 9, wherein the first terminal comprises:

a Session Initiation Protocol (SIP) stack as a primary means of communicating messages in the first format; and

a Short Messaging Service (SMS) stack as a secondary means of communicating messages in the second format.

11. The messaging system according to claim 10, wherein receipt of the failed message attempt in the first format causes the first terminal to retransmit the message in the second format.

12. The messaging system according to claim 9, wherein at least one of the plurality of network elements comprises:

a Session Initiation Protocol (SIP) stack as a primary means of communicating messages in the first format; and

a Short Messaging Stack (SMS) as a secondary means of communicating messages in the second format.

13. The messaging system according to claim 12, wherein receipt of the failed message attempt in the first format causes one of the at least one network elements to retransmit the message in the second format.

14. A mobile terminal wirelessly coupled to a network which includes a network element capable of relaying messages, the mobile terminal comprising:

a memory capable of storing at least one of a protocol module and a legacy module;

a processor coupled to the memory and configured by the protocol module to enable a message exchange of a first protocol type with the network element; and

a transceiver configured to facilitate the message exchange with the network element, wherein the processor is configured by the legacy module to exchange messages of a second protocol type in response to a failure of exchanges of messages of the first protocol type.

15. The mobile terminal according to claim 14, wherein usage of the protocol module and the legacy module is selected by the processor in response to messages received from the network element.

16. A computer-readable medium having instructions stored thereon which are executable by a mobile terminal for generating messages by performing steps comprising:

transmitting a message of a first protocol type along a first transmission path;

receiving an indication of a failed delivery of the message;

converting the first protocol type to a second protocol type; and

transmitting the second protocol type message along a second transmission path.

17. A server within a network used to facilitate an exchange of messages, comprising:

means for receiving messages of a first protocol type;

means for transmitting the messages to a network element;

means for receiving a receipt failure notification from the network element;

means for converting the first protocol type to a second protocol type in response to the receipt of failure notification; and

means for transmitting messages of the second protocol type to the network element.

18. The server according to claim 17, wherein the means for receiving messages of the first protocol type supports an ALL-IP core protocol compatible within a Third Generation (3G) network.

19. The server according to claim 18, wherein the first protocol type includes Session Initiation Protocol (SIP).

20. The server according to claim 19, wherein the messages of the first protocol type includes a retry policy.

21. The server according to claim 20, wherein the retry policy comprises fields to define at least one of:

a number of retries to perform upon failure;

an amount of time allowed between retries; and

a retry mechanism.

22. The server according to claim 21, wherein the retry mechanism operates in accordance with a Short Messaging Service (SMS).

23. The server according to claim 17, wherein the means for receiving messages of the first protocol type supports a Short Messaging Service (SMS).

24. The server according to claim 23, wherein the messages of the first protocol type includes a retry policy.

25. The server according to claim 24, wherein the retry policy comprises fields to define at least one of:

a number of retries to perform upon failure;

an amount of time allowed between retries; and

a retry mechanism.

26. The server according to claim 25, wherein the retry mechanism operates in accordance with a Session Initiation Protocol (SIP).

27. A computer-readable medium having instructions stored thereon which are executable by a network server for facilitating messaging by performing steps comprising:

receiving messages of a first protocol type;

transmitting the messages to a network element;

receiving a receipt failure notification from the network element; and

converting the first protocol type to a second protocol type in response to the receipt failure notification; and

transmitting messages of the second protocol type to the network element.