Interworking gateway and method
First Claim
1. An interworking gateway for interworking at least one Open Mobile Alliance (OMA) Instant Message and Presence Service (IMPS) domain and a Session Initiation Protocol (SIP) infrastructure comprising at least one SIP Instant Messaging and Presence Leveraging Extensions (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.
7 Assignments
0 Petitions
Accused Products
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.
85 Citations
21 Claims
-
1. An interworking gateway for interworking at least one Open Mobile Alliance (OMA) Instant Message and Presence Service (IMPS) domain and a Session Initiation Protocol (SIP) infrastructure comprising at least one SIP Instant Messaging and Presence Leveraging Extensions (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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A method for interworking at least one Open Mobile Alliance (OMA) Instant Message and Presence Service (IMPS) domain and a Session Initiation Protocol (SIP) infrastructure comprising at least one SIP Instant Messaging and Presence Leveraging Extensions (SIMPLE) domain, the method comprising the steps of:
-
receiving OMA IMPS transactions from users in an OMA IMPS domain over an OMA IMPS interface; receiving SIMPLE transactions from users in a SIMPLE domain over a SIMPLE interface; converting an interworking subset of said 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 SIMPLE domain; and converting an interworking subset of said 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 OMA IMPS domain. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18, 19, 20, 21)
-
Specification