Interworking gateway and method

• US 20050213537A1
• Filed: 02/28/2005
• Published: 09/29/2005
• Est. Priority Date: 02/27/2004
• Status: Active Grant

• Current Assignee: Synchronica PLC (Myriad Group AG)
• Original Assignee: Nokia Corporation
• Inventors: Regnier, Jean, Thorkelsson, Haraldur, Ingimundarson, Jon Ingi, Vachon, Gaetan
• Granted Patent: US 7,526,563 B2
• Time in Patent Office: Days
• US Class Current: 370/329
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/085 specially adapted for interworking of IP-based networks with other networks

Abstract

An interworking gateway for interworking an OMA IMPS domain and a SIMPLE domain comprises an OMA IMPS interface for communication with the OMA IMPS domain, a SIMPLE interface for communication with the SIMPLE domain and an interworking function linking the interfaces and comprising a transaction mapping module for converting an interworking subset of OMA IMPS transactions received by the OMA IMPS interface to corresponding SIMPLE transactions and relaying the corresponding SIMPLE transactions to the SIMPLE interface for transfer to the SIMPLE domain and for mapping an interworking subset of SIMPLE transactions received by the SIMPLE interface to corresponding OMA IMPS transactions and relaying the corresponding OMA IMPS transactions to the OMA IMPS interface for transfer to the OMA IMPS domain.

Claims

1. An interworking gateway for interworking at least one OMA IMPS domain and a SIP infrastructure comprising at least one SIMPLE domain, the gateway comprising:

an OMA IMPS interface for communication with the at least one OMA IMPS domain;

a SIMPLE interface for communication with the SIP infrastructure; and

an interworking function linking said interfaces and comprising a transaction mapping module for converting an interworking subset of OMA IMPS transactions received by said OMA IMPS interface to corresponding SIMPLE transactions and relaying said corresponding SIMPLE transactions to said SIMPLE interface for transfer to the SIP infrastructure, and for mapping an interworking subset of SIMPLE transactions received by said SIMPLE interface to corresponding OMA IMPS transactions and relaying said corresponding OMA IMPS transactions to said OMA IMPS interface for transfer to the at least one OMA IMPS domain.

2. The interworking gateway of claim 1, wherein the OMA IMPS interface communicates with each OMA IMPS domain using OMA IMPS SSP.

3. The interworking gateway of claim 1, wherein the SIMPLE interface communicates with the SIP infrastructure using MSRP, CPCP and SIP.

4. The interworking gateway of claim 2, wherein the OMA IMPS interface comprises a protocol stack comprising an OMA IMPS SSP layer, a HTTP layer and a TCP/IP layer.

5. The interworking gateway of claim 2, wherein said SIMPLE interface comprises a protocol stack comprising a SIP layer, a HTTP layer, a TCP/IP layer and a UDP/IP layer.

6. The interworking gateway of claim 1, wherein each OMA IMPS domain comprises at least one OMA IMPS client and each SIMPLE domain comprises at least one SIP client, the OMA IMPS client exchanging instant messages with the SIP client via an OMA IMPS server and a SIP proxy, and wherein said OMA IMPS interface is in communication with said OMA IMPS server and said SIMPLE interface is in communication with said SIP proxy.

7. The interworking gateway of claim 1, wherein said OMA IMPS interface further comprises a routing table comprising an identifier of said at least OMA IMPS client coupled with an identifier of an OMA IMPS server servicing said at least one OMA IMPS client and wherein said OMA IMPS interface routes received OMA IMPS transactions comprising a particular destination address to an OMA IMPS server which services an OMA IMPS client designated by said destination address.

8. The interworking gateway of claim 7, wherein said received OMA IMPS transactions comprise corresponding OMA IMPS transactions received from said mapping module and OMA IMPS transactions received at said OMA IMPS interface from an OMA IMPS server.

9. The interworking gateway of claim 7, wherein each of said corresponding OMA IMPS transactions comprises a destination OMA IMPS client address and said OMA IMPS client identifier is an OMA IMPS client address.

10. The interworking gateway of claim 1, wherein said transaction mapping module converts OMA IMPS domain addresses to SIMPLE domain addresses and SIMPLE domain addresses to OMA IMPS domain addresses.

11. A method for interworking at least one OMA IMPS domain and a SIP infrastructure comprising at least one SIMPLE domain, the method comprising the steps of:

providing an OMA IMPS interface for communication with the at least one OMA IMPS domain;

providing a SIMPLE interface for communication with the SIP infrastructure;

converting an interworking subset of OMA IMPS transactions received by said OMA IMPS interface to corresponding SIMPLE transactions and relaying said corresponding SIMPLE transactions to said SIMPLE interface for transfer to the SIP infrastructure; and

converting an interworking subset of SIMPLE transactions received by said SIMPLE interface to corresponding OMA IMPS transactions and relaying said corresponding OMA IMPS transactions to said OMA IMPS interface for transfer to the at least one OMA IMPS domain.

12. The method of claim 11, wherein the OMA IMPS interface communicates with each OMA IMPS domain using OMA IMPS SSP.

13. The method of claim 11, wherein the SIMPLE interface communicates with the SIP infrastructure using MSRP, CPCP and SIP.

14. The method of claim 12, wherein the OMA IMPS interface comprises a protocol stack comprising an OMA IMPS SSP layer, a HTTP layer and a TCP/IP layer.

15. The method of claim 13, wherein said SIMPLE interface comprises a protocol stack comprising a SIP layer, a HTTP layer, a TCP/IP layer and a UDP/IP layer.

16. The method of claim 11, wherein each OMA IMPS domain comprises at least one OMA IMPS client and the SIMPLE domain comprises at least one SIP client, the OMA IMPS client exchanging instant messages with the SIP client via an OMA IMPS server and a SIP proxy, and wherein said OMA IMPS interface is in communication with said OMA IMPS server and said SIMPLE interface is in communication with said SIP proxy.

17. The method of claim 11, wherein said OMA IMPS interface further comprises a routing table comprising an identifier of said at least OMA IMPS client coupled with an identifier of an OMA IMPS server servicing said at least one OMA IMPS client and wherein said OMA IMPS interface routes OMA IMPS transactions comprising an OMA IMPS destination address to an OMA IMPS server which services an OMA IMPS client designated by said OMA IMPS destination address.

18. The method of claim 17, wherein said received OMA IMPS transactions comprise corresponding OMA IMPS transactions received from said mapping module and OMA IMPS transactions received at said OMA IMPS interface from an OMA IMPS server.

19. The method of claim 17, wherein a particular one of said corresponding OMA IMPS transactions is destined for a destination OMA IMPS client, and wherein said OMA IMPS interface routes said particular transaction to an OMA IMPS server which services said destination OMA IMPS client.

20. The method of claim 17, wherein each of said corresponding OMA IMPS transactions comprises a destination OMA IMPS client address and said OMA IMPS client identifier is an OMA IMPS client address.

21. The method of claim 11, wherein said transaction mapping module converts OMA IMPS domain addresses to SIMPLE domain addresses and SIMPLE domain addresses to OMA IMPS domain addresses.