Enterprise mobility

• US 8,045,568 B2
• Filed: 09/29/2006
• Issued: 10/25/2011
• Est. Priority Date: 09/29/2006
• Status: Active Grant

• Current Assignee: Genband US LLC (Ribbon Communications, Inc.)
• Original Assignee: Genband US LLC (Ribbon Communications, Inc.)
• Inventors: Constantinof, Cristian, Sylvain, Dany
• Primary Examiner(s): Phillips; Hassan
• Assistant Examiner(s): EBRAHIM, ANEZ C
• Application Number:
  US11/536,921
• Publication Number:
  US 20080144637A1
• Time in Patent Office: 1,852 Days
• Field of Search: 370/352, 370/401, 370/256, 370/390, 370/328, 370/338, 709/202, 709/227, 705/40
• US Class Current: 370/401
• CPC Class Codes: H04L 2101/385 Uniform resource identifier for session initiation protocol [SIP URI]
• CPC Class Codes: H04L 61/106 across networks, e.g. mapping telephone numbers to data network addresses
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1043 Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
• CPC Class Codes: H04L 65/1056 Multi-site
• CPC Class Codes: H04W 36/0022 for transferring data sessions between adjacent core network technologies
• CPC Class Codes: H04W 36/00226 wherein the core network technologies comprise IP multimedia system [IMS], e.g. single radio voice call continuity [SRVCC]

Abstract

The present invention provides a service node, which extends the services of a carrier'"'"'s multimedia subsystem (MS), such as an IP multimedia subsystem (IMS), to enterprise networks in an efficient and effective manner. As such, MS subscribers gain access to enterprise services in addition to the carrier'"'"'s services provided via the carrier'"'"'s circuit switched subsystems (CS) and packet subsystems (PS). The service node acts as a liaison between enterprise application servers and the MS, such that the enterprise application servers appear as MS application servers to the MS. The service node provides user identifier and protocol translation between enterprise and MS user identifiers and protocols, respectively. As such, enterprise application servers can access the MS as well as be accessed by the MS to support user mobility, with continuity of services, between the enterprise and carrier networks.

Claims

1. A method comprising:

receiving a first carrier session message from a multimedia subsystem associated with a carrier network and comprising a carrier user identifier identifying a user associated with a communication session;

identifying an enterprise user identifier corresponding to the carrier user identifier for the first carrier session message, wherein the enterprise user identifier is different from the carrier user identifier and at least one of the enterprise user identifier and the carrier user identifier includes a session initiation protocol (SIP) identifier;

creating a first enterprise session message corresponding to the first carrier session message and comprising the enterprise user identifier; and

forwarding the first enterprise session message into an enterprise network, wherein the first enterprise session message is an initial message transmitted into the enterprise network associated with the first carrier session message.

2. The method claim 1 wherein the first enterprise session message is forwarded toward an enterprise application server to invoke an originating enterprise application service provided by the enterprise application server for the communication session on behalf of the user establishing the session.

3. The method of claim 2 further comprising:

receiving from the enterprise application server a second enterprise session message associated with the communication session and comprising the enterprise user identifier, the second enterprise session message responsive to providing the enterprise application service to the first enterprise session message;

identifying the carrier user identifier corresponding to the enterprise user identifier for the second enterprise session message;

creating a second carrier session message corresponding to the second enterprise session message and comprising the carrier user identifier; and

forwarding the second carrier session message into the multimedia subsystem.

4. The method of claim 1 further comprising:

receiving from the enterprise network a second enterprise session message associated with the communication session and comprising the enterprise user identifier;

identifying the carrier user identifier corresponding to the enterprise user identifier for the second enterprise session message;

creating a second carrier session message corresponding to the second enterprise session message and comprising the carrier user identifier; and

forwarding the second carrier session message into the multimedia subsystem.

5. The method of claim 1 wherein the enterprise user identifier is used to identify the terminal within the enterprise network, and the carrier user identifier is used to identify the terminal within the carrier network.

6. The method of claim 1 wherein the enterprise user identifier is not a valid user identifier in the carrier network.

7. The method of claim 1 wherein control of the communication session is provided by the multimedia subsystem.

8. The method of claim 1 wherein the multimedia subsystem is an Internet Protocol Multimedia Subsystem of the carrier network.

9. The method of claim 1 further comprising effecting establishment of at least a portion of a bearer path for the communication session outside of the enterprise network and via a circuit-switched subsystem of the carrier network.

10. The method of claim 1 further comprising:

receiving from the multimedia subsystem a first registration message comprising the carrier user identifier for the user;

identifying the enterprise user identifier corresponding to the carrier user identifier for the first registration message;

creating a second registration message corresponding to the first registration message and comprising the enterprise user identifier; and

forwarding the second registration message into the enterprise network to register the user with the enterprise network.

11. The method of claim 1 wherein the first carrier session message and the first enterprise session message are session control messages facilitating at least one of the group consisting of establishment of the communication session and controlling the communication session once the communication session is established.

12. A system comprising:

at least one communication interface; and

a control system associated with the at least one communication interface and configured to;

receive a first carrier session message from a multimedia subsystem associated with a carrier network and comprising a carrier user identifier identifying a user associated with a communication session;

identify an enterprise user identifier corresponding to the carrier user identifier for the first carrier session message, wherein the enterprise user identifier is different from the carrier user identifier and at least one of the enterprise user identifier and the carrier user identifier includes a session initiation protocol (SIP) identifier;

create a first enterprise session message corresponding to the first carrier session message and comprising the enterprise user identifier; and

forward the first enterprise session message into an enterprise network, wherein the first enterprise session message is an initial message transmitted into the enterprise network associated with the first carrier session message.

13. The system claim 12 wherein the first enterprise session message is forwarded toward an enterprise application server to invoke an originating enterprise application service provided by the enterprise application server for the communication session on behalf of the user establishing the session.

14. The system of claim 13 wherein the control system is further configured to:

receive from the enterprise application server a second enterprise session message associated with the communication session and comprising the enterprise user identifier, the second enterprise session message responsive to providing the enterprise application service to the first enterprise session message;

identify the carrier user identifier corresponding to the enterprise user identifier for the second enterprise session message;

create a second carrier session message corresponding to the second enterprise session message and comprising the carrier user identifier; and

forward the second carrier session message into the multimedia subsystem.

15. The system of claim 12 wherein the control system is further configured to:

receive from the enterprise network a second enterprise session message associated with the communication session and comprising the enterprise user identifier;

identify the carrier network address corresponding to the enterprise user identifier for the second enterprise session message;

create a second carrier session message corresponding to the second enterprise session message and comprising the carrier user identifier; and

forward the second carrier session message into the multimedia subsystem.

16. The system of claim 12 wherein the enterprise user identifier is used to identify the terminal within the enterprise network, and the carrier user identifier is used to identify the terminal within the carrier network.

17. The system of claim 12 wherein the enterprise user identifier is not a valid user identifier in the carrier network.

18. The system of claim 12 wherein control of the communication session is provided by the multimedia subsystem.

19. The system of claim 12 wherein the multimedia subsystem is an Internet Protocol Multimedia Subsystem of the carrier network.

20. The system of claim 12 wherein the control system is further configured to effect establishment of at least a portion of a bearer path for the communication session outside of the enterprise network and via a circuit-switched subsystem of the carrier network.

21. The system of claim 12 wherein the control system is further configured to:

receive from the multimedia subsystem a first registration message comprising the carrier user identifier for the user;

identify the enterprise user identifier corresponding to the carrier user identifier for the first registration message;

create a second registration message corresponding to the first registration message and comprising the enterprise user identifier; and

forward the second registration message into the enterprise network to register the user with the enterprise network.