System and method for executing originating services in a terminating network for IMS and non-IMS applications

Abstract

A system, server and method of executing originating services in a terminating IP Multimedia Subsystem (IMS) network in which a triggered application may or may not support IMS.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an independently managed and controlled wireless carrier network, and an independently managed corporate enterprise network;

FIG. 2 is a diagram of a conventional enterprise network gateway server connected to a wireless carrier network;

FIG. 3 is a diagram of a gateway server system accordingly to one preferred embodiment of the present invention;

FIG. 4A is a diagram of an enterprise data and voice network operably connected using the gateway server system using pure enterprise call control according to one preferred embodiment;

FIG. 4B is a diagram of an enterprise data and voice network operably connected using the gateway server system using split call control according to one preferred embodiment;

FIG. 5 depicts a network architecture according to another preferred embodiment using VoIP systems;

FIG. 6 is a call flow diagram for call origination according to one embodiment of the present invention;

FIG. 7 is a call flow diagram for effecting call delivery using VoIP system according to another preferred embodiment of the present invention;

FIG. 8 is a call flow diagram for effecting mobile termination using VoIP according to another preferred embodiment of the present invention;

FIG. 9 is a diagram of a network architecture for a Legacy (TDM) network according to another preferred embodiment of the present invention;

FIG. 10 is a diagram of a next generation IMS architecture that is backwards compatible with legacy cellular networks based on existing cellular protocols;

FIG. 11 is a diagram of a conventional legacy network architecture that does not support IM;

FIG. 12 depicts a Packet Engine according to another preferred embodiment of the present invention allowing a call server to detect DTMF digit events on the call path;

FIG. 13 depicts one embodiment of the Packet Engine consisting of a user space;

FIG. 14 depicts a Linux kernel module of the Packet Engine;

FIG. 15 depicts the current IMS standard definition;;

FIG. 16 depicts one exemplary embodiment of the invention for IMS service;

FIG. 17 and FIG. 18 depict a gateway server carrier (GS-C) configured as an IMS standard-compliant SIP, and associated algorithm; and

FIG. 19 depicts an algorithm for receiving incoming calls on various lines that are to be directed to a subscribers mobile phone.

Claims

1. A system configured to execute originating services in a terminating IP Multimedia Subsystem (IMS) network in which a triggered application may or may not support IMS, comprising; a) a carrier or cellular gateway server (GS-C) configured to operate as an IMS-compliant SIP application server (SIP-AS) communicating with a terminating network gateway server (GS-E) located in an enterprise via a direct signaling connection, the GS-C configured to prepare the GS-E for an upcoming communication;b) the GS-C configured to operate as an IMS-compliant SIP application server (SIP-AS) responding to a serving CSCF (S-CSCF) and configured to route the session to a destination in the terminating IMS network;c) the GS-E configured to receive the session in the terminating IMS network and act as an IMS-compliant interrogating CSCF (I-CSCF); andd) the GS-E configured to act as an IMS-compliant S-CSCF, wherein the I-CSCF is configured to route the session for handling.

2. The system as specified in claim 1 wherein the GS-C is configured to act as an IMS-compliant SIP-AS and communicate with the GS-E, the GS-E configured to act as a complex comprising an IMS-compliant P-CSCF, I-CSCF, S-CSCF and/or SIP-AS, the GS-C configured to communicate with the GS-E, through a standard IMS interface rather than via a direct signaling connection to prepare the GS-E for an upcoming communication.

3. The system as specified in claim 1 whereby the GS-E is configured to act as an S-CSCF front-end (FE) to a non-IMS application such as a legacy, hybrid and/or IP PBX, additionally comprising the steps of: a) the FE configured to convert IMS messaging into a corresponding SIP-AS service-invocation message and operate with a non-IMS application; andb) the FE configured to convert a terminating services request into an originating services request prior to communication with a terminating service such that the terminating service is able to invoke services as if it were an originating node.

4. The system as specified in claim 3 wherein the GS-E is configured to act as an S-CSCF FE to a non-IMS application and enable a non-IMS application to perform terminating services once the originating services have been executed.

5. The system as specified in claim 3 wherein the GS-E is configured to act as an S-CSCF front-end to an IMS-compliant application, whereby the FE is configured to convert the terminating services request to an originating services request prior to communicating with the IMS-compliant application.

6. The system as specified in claim 3 wherein the system is configured such that following a successful execution of the originating services of an IMS-compliant application, the IMS-compliant application can return control to the FE to invoke another service request back to the IMS-compliant application to perform terminating services.

7. A carrier gateway server (GS-C) configured to execute originating services in a terminating IP Multimedia Subsystem (IMS) network in which a triggered application may or may not support IMS, comprising; a) the GS-C configured to operate as an IMS-compliant SIP application server (SIP-AS) communicating with a terminating network gateway server (GS-E) supporting a legacy, hybrid and/or IP PBX and located in an enterprise via a direct signaling connection, the GS-C configured to prepare the GS-E for an upcoming communication; andb) the GS-C configured to operate as an IMS-compliant SIP application server (SIP-AS) responding to the serving CSCF (S-CSCF) and configured to route the session to a destination in the terminating IMS network.

8. An enterprise gateway server (GS-E) configured to execute originating services in a terminating IP Multimedia Subsystem (IMS) network in which a triggered application may or may not support IMS, comprising; a) the GS-E configured to receive the session in the terminating IMS network and act as an IMS-compliant interrogating CSCF (I-CSCF); andb) the GS-E configured to act as an IMS-compliant S-CSCF, wherein the I-CSCF is configured to route the session for handling.

9. A method for executing originating services in a terminating IP Multimedia Subsystem (IMS) network in which a triggered application may or may not support IMS, comprising the steps of; a) a carrier gateway server (GS-C) acting as an IMS-compliant SIP application server (SIP-AS) communicating with a terminating network gateway server (GS-E) that is supporting a legacy, hybrid and/or IP PBX and located in an enterprise via a direct signaling connection to prepare the GS-E for an upcoming communication;b) the GS-C acting as an IMS-compliant SIP application server (SIP-AS) responding to the serving CSCF (S-CSCF) which routes the session to the destination in the terminating IMS network;c) the GS-E receiving the session in the terminating IMS network acting as an IMS-compliant interrogating CSCF (I-CSCP); andd) the GS-E acting as an IMS-compliant S-CSCF, to which the I-CSCF routes the session for handling.

10. The method as specified in claim 9 wherein the GS-C acts as an IMS-compliant SIP-AS and communicates with the GS-E acting as a complex comprising an IMS-compliant 1-CSCF, S-CSCF and SIP-AS, through a standard IMS interface rather than via a direct signaling connection to prepare the GS-E for an upcoming communication.

11. The method as specified in claim 9 whereby the GS-E acts as an S-CSCF front-end (FE) to a non-IMS application such as a legacy, hybrid and/or IP PBX, additionally comprising the steps of: a) the front end converting the IMS messaging into a corresponding SIP-AS service-invocation message of the non-IMS application; andb) the front end converting a terminating services request into an originating services request prior to communicating with a terminating service such that the terminating service is able to invoke services as if it were an originating node.

12. The method as specified in claim 11 wherein the GS-E acts as an S-CSCF FE to a non-IMS application and enables the non-IMS application to perform terminating services once the originating services have been executed.

13. The method as specified in claim 11 wherein the GS-E acts as an S-CSCF front-end to an IMS-compliant application, whereby the FE converts the terminating services request to an originating services request prior to communicating with the IMS compliant application.

14. The method as specified in claim 11 wherein following a successful execution of the originating services of an IMS-compliant application, the IMS-compliant application returns control to the FE to invoke another service request back to the IMS-compliant application to perform terminating services.