System and method for enabling use of a single user identifier across incompatible networks for UCC functionality

• US 10,091,025 B2
• Filed: 04/04/2016
• Issued: 10/02/2018
• Est. Priority Date: 03/31/2016
• Status: Active Grant

• Current Assignee: Damaka, Inc.
• Original Assignee: Damaka, Inc.
• Inventors: Chaturvedi, Sivakumar, Gundabathula, Satish, Lohita, Rashmi
• Primary Examiner(s): Nguyen, Thu Ha T
• Application Number:
  US15/090,394
• Publication Number:
  US 20170288904A1
• Time in Patent Office: 911 Days
• Field of Search: 709227, 709228, 709229
• CPC Class Codes: H04L 12/184 with heterogeneous receivers, e.g. layered multicast
• CPC Class Codes: H04L 12/4625 Single bridge functionality, e.g. connection of two networks over a single bridge
• CPC Class Codes: H04L 51/56 Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
• CPC Class Codes: H04L 65/103 in the network
• CPC Class Codes: H04L 65/1053 IP private branch exchange [PBX] functionality entities or arrangements circuit switched PBXs H04M3/00
• CPC Class Codes: H04L 65/1073 Registration or de-registration
• CPC Class Codes: H04L 65/1094 Inter-user-equipment sessions transfer or sharing

Abstract

A method and system for supporting a cross-domain communication session between communication platforms using a bridge server are provided. In one example, the method includes registering the bridge server with multiple platforms using a user identifier. A request is received from one of the platforms to establish a communication session with a user corresponding to the user identifier. A communication leg is created for each of the platforms. The leg from which the request was received is an incoming leg and the other legs are outgoing legs. The request is sent over the outgoing legs. An acceptance is received from one of the outgoing legs. A cancel message is sent over the outgoing legs from which the acceptance was not received. The acceptance is sent over the incoming leg. The incoming leg and the outgoing leg from which the acceptance was received are bridged to establish the session.

Claims

1. A method for supporting a cross-domain communication session between communication platforms using a bridge server, the method comprising:

registering, by a bridge server, with a plurality of communication platforms using a user identifier, wherein at least two of the communication platforms are in incompatible domains and cannot communicate directly with one another, and wherein the user identifier is registered with each of the communication platforms via one or more clients that are in communication with the communication platforms;

receiving, by the bridge server, a request to establish a communication session with a user corresponding to the user identifier, the request being received from one of the communication platforms;

creating, by the bridge server, a separate communication leg for each of the communication platforms, wherein the communication leg created for the communication platform from which the request was received is designated as an incoming leg and any other of the communication legs are designated as outgoing legs;

sending, by the bridge server, the request to establish the communication session over the outgoing legs;

receiving, by the bridge server, a communication acceptance from one of the outgoing legs;

sending, by the bridge server, a cancel message over any of the outgoing legs from which the communication acceptance was not received;

sending, by the bridge server, the communication acceptance over the incoming leg; and

bridging, by the bridge server, the incoming leg and the outgoing leg from which the communication acceptance was received to establish the communication session, wherein bridging the incoming leg and the outgoing leg to establish the communication session includes creating a bridged media path through which communications sent over the incoming leg and the outgoing leg by the communication platforms during the communication session are first received by the bridge server before transmitting the communications to the communication platforms, and wherein the bridge server is configured to convert information received over the bridged media path between different media formats if the media format used by the incoming leg is different than the media format used by one of the outgoing legs.

2. The method of claim 1 further comprising:

receiving, from one of the incoming leg and the outgoing leg from which the communication acceptance was received, a communication session termination request;

sending the communication session termination request over the incoming leg or the outgoing leg from which the communication session termination request was not received; and

destroying all of the communication legs.

3. The method of claim 1, wherein the bridge server is coupled to a media server that forms part of a cross-domain system with the bridge server, wherein the media server handles media legs for the communication session.

4. The method of claim 3, wherein the cross-domain system includes a cross-domain database having a plurality of information specific to the communication platforms.

5. The method of claim 4, wherein the plurality of information includes an IP address, a port number, and a plurality of functionality identifiers, the plurality of functionality identifiers indicating whether each of the communication platforms supports certain Unified Communications and Collaboration (UCC) functions.

6. The method of claim 5 further comprising managing the communication session by the bridge server, wherein the bridge server uses the plurality of information contained in the cross-domain database to enable communications between the communication platforms that are in incompatible domains and cannot communicate directly with one another.

7. The method of claim 1 wherein the bridge server bridges the incoming leg and the outgoing leg both when the communication platforms corresponding to the incoming leg and outgoing leg are in incompatible domains and cannot communicate directly with one another and when the communication platforms corresponding to the incoming leg and outgoing leg are in compatible domains and can communicate directly with one another.

8. The method of claim 1 further comprising:

receiving, by the bridge server, a second request to establish a second communication session with the user corresponding to the user identifier, the second request being received from one of the communication platforms;

creating, by the bridge server, a separate second communication leg for each of the communication platforms, wherein the second communication leg created for the communication platform from which the second request was received is designated as a second incoming leg and any other of the second communication legs are designated as second outgoing legs;

sending, by the bridge server, the second request to establish the communication session over the second outgoing legs;

receiving, by the bridge server, a cancel message from the second incoming leg;

sending, by the bridge server, the cancel message over the second outgoing legs; and

destroying, by the bridge server, the second communication legs.

9. A method for supporting a cross-domain communication session between communication platforms using a bridge server, the method comprising:

registering, by a bridge server, with a plurality of communication platforms using a user identifier, wherein at least two of the communication platforms are in incompatible domains and cannot communicate directly with one another, and wherein the user identifier is registered with each of the communication platforms via one or more clients that are in communication with the communication platforms;

receiving, by the bridge server, a request to establish a communication session with the user corresponding to the user identifier, the request being received from one of the communication platforms;

creating, by the bridge server, a separate communication leg for each of the communication platforms, wherein the communication leg created for the communication platform from which the request was received is designated as an incoming leg and any other of the communication legs are designated as outgoing legs;

sending, by the bridge server, the request to establish the communication session over the outgoing legs;

receiving, by the bridge server, a cancel message from the incoming leg;

sending, by the bridge server, a cancel message over the outgoing legs; and

destroying, by the bridge server, all of the communication legs,

wherein the bridge server is configured to;

bridge the incoming leg and the outgoing leg to establish the communication session to create a bridged media path through which communications sent over the incoming leg and the outgoing leg by the communication platforms during the communication session are first received by the bridge server before transmitting the communications to the communication platforms, and

convert information received over the bridge media path between different media formats if the media format used by the incoming leg is different than the media format used by one of the outgoing legs.

10. The method of claim 9, wherein the bridge server is coupled to a media server that forms part of a cross-domain system with the bridge server, wherein the media server handles media legs for any communication sessions managed by the bridge server.

11. The method of claim 10, wherein the cross-domain system includes a cross-domain database having a plurality of information specific to the communication platforms.

12. The method of claim 11, wherein the plurality of information includes an IP address, a port number, and a plurality of functionality identifiers, the plurality of functionality identifiers indicating whether each of the communication platforms supports certain Unified Communications and Collaboration (UCC) functions.

13. The method of claim 12 wherein the bridge server uses the plurality of information contained in the cross-domain database to enable communications between any of the communication platforms that are in incompatible domains and cannot communicate directly with one another.

14. A system for supporting a cross-domain communication session between communication platforms using a bridge server, the system comprising:

a processor; and

a memory coupled to the processor, the memory containing computer executable instructions for;

providing a bridge server;

registering, by the bridge server, with a plurality of communication platforms using a user identifier, wherein at least two of the communication platforms are in incompatible domains and cannot communicate directly with one another, and wherein the user identifier is registered with each of the communication platforms via one or more clients that are in communication with the communication platforms;

receiving, by the bridge server, a request to establish a communication session with a user corresponding to the user identifier, the request being received from one of the communication platforms;

creating, by the bridge server, a separate communication leg for each of the communication platforms, wherein the communication leg created for the communication platform from which the request was received is designated as an incoming leg and any other of the communication legs are designated as outgoing legs;

sending, by the bridge server, the request to establish the communication session over the outgoing legs;

receiving, by the bridge server, a communication acceptance from one of the outgoing legs;

sending, by the bridge server, a cancel message over any of the outgoing legs from which the communication acceptance was not received;

sending, by the bridge server, the communication acceptance over the incoming leg; and

bridging, by the bridge server, the incoming leg and the outgoing leg from which the communication acceptance was received to establish the communication session,

wherein bridging the incoming leg and the outgoing leg to establish the communication session includes creating a bridged media path through which communications sent over the incoming leg and the outgoing leg by the communication platforms during the communication session are first received by the bridge server before transmitting the communications to the communication platforms, and

wherein the bridge server is configured to convert information received over the bridged media path between different media formats if the media format used by the incoming leg is different than the media format used by one of the outgoing legs.

15. The system of claim 14 further comprising instructions for:

receiving, from one of the incoming leg and the outgoing leg from which the communication acceptance was received, a communication session termination request;

sending the communication session termination request over the incoming leg or the outgoing leg from which the communication session termination request was not received; and

destroying all of the communication legs.

16. The system of claim 14, wherein the bridge server is coupled to a media server that forms part of a cross-domain system with the bridge server, wherein the media server handles media legs for the communication session.

17. The system of claim 16, wherein the cross-domain system includes a cross-domain database having a plurality of information specific to the communication platforms.

18. The system of claim 17, wherein the plurality of information includes an IP address, a port number, and a plurality of functionality identifiers, the plurality of functionality identifiers indicating whether each of the communication platforms supports certain Unified Communications and Collaboration (UCC) functions.

19. The system of claim 18 further comprising instructions for managing the communication session by the bridge server, wherein the bridge server uses the plurality of information contained in the cross-domain database to enable communications between the communication platforms that are in incompatible domains and cannot communicate directly with one another.

20. The system of claim 14, wherein the bridge server bridges the incoming leg and the outgoing leg both when the communication platforms corresponding to the incoming leg and outgoing leg are in incompatible domains and cannot communicate directly with one another and when the communication platforms corresponding to the incoming leg and outgoing leg are in compatible domains and can communicate directly with one another.

21. The system of claim 14 further comprising instructions for:

receiving, by the bridge server, a second request to establish a second communication session with the user corresponding to the user identifier, the second request being received from one of the communication platforms;

creating, by the bridge server, a separate second communication leg for each of the communication platforms, wherein the second communication leg created for the communication platform from which the second request was received is designated as a second incoming leg and any other of the second communication legs are designated as second outgoing legs;

sending, by the bridge server, the second request to establish the communication session over the second outgoing legs;

receiving, by the bridge server, a cancel message from the second incoming leg;

sending, by the bridge server, the cancel message over the second outgoing legs; and

destroying, by the bridge server, the second communication legs.

22. A system for supporting a cross-domain communication session between communication platforms using a bridge server, the system comprising:

a processor; and

a memory coupled to the processor, the memory containing computer executable instructions for;

providing a bridge server;

registering, by the bridge server, with a plurality of communication platforms using a user identifier, wherein at least two of the communication platforms are in incompatible domains and cannot communicate directly with one another, and wherein the user identifier is registered with each of the communication platforms via one or more clients that are in communication with the communication platforms;

receiving, by the bridge server, a request to establish a communication session with the user corresponding to the user identifier, the request being received from one of the communication platforms;

creating, by the bridge server, a separate communication leg for each of the communication platforms, wherein the communication leg created for the communication platform from which the request was received is designated as an incoming leg and any other of the communication legs are designated as outgoing legs;

sending, by the bridge server, the request to establish the communication session over the outgoing legs;

receiving, by the bridge server, a cancel message from the incoming leg;

sending, by the bridge server, the cancel message over the outgoing legs; and

destroying, by the bridge server, all of the communication legs,

wherein the bridge server is configured to;

bridge the incoming leg and the outgoing leg to establish the communication session to create a bridged media path through which communications sent over the incoming leg and the outgoing leg by the communication platforms during the communication session are first received by the bridge server before transmitting the communications to the communication platforms, and

convert information received over the bridged media path between different media formats if the media format used by the incoming leg is different than the media format used by one of the outgoing legs.

23. The system of claim 22, wherein the bridge server is coupled to a media server that forms part of a cross-domain system with the bridge server, wherein the media server handles media legs for any communication sessions managed by the bridge server.

24. The system of claim 23, wherein the cross-domain system includes a cross-domain database having a plurality of information specific to the communication platforms.

25. The system of claim 24, wherein the plurality of information includes an IP address, a port number, and a plurality of functionality identifiers, the plurality of functionality identifiers indicating whether each of the communication platforms supports certain Unified Communications and Collaboration (UCC) functions.

26. The system of claim 25 wherein the bridge server uses the plurality of information contained in the cross-domain database to enable communications between any of the communication platforms that are in incompatible domains and cannot communicate directly with one another.

27. A system for supporting a cross-domain communication session between communication platforms, the system comprising:

a bridge server registered with at least two communication platforms using a user identifier, wherein the at least two communication platforms are in separate and incompatible domains and wherein the user identifier is recognized by all of the at least two communication platforms; and

a cross-domain database having a plurality of information specific to the at least two communication platforms and the user identifier,

wherein the bridge server is configured to receive communications requests from the at least two communication platforms, to manage communication sessions between the at least two communication platforms using the plurality of information specific to the at least two communication platforms, to create a bridged media path through which communications for the communication session between the at least two communication platforms are first received by the bridge server before transmitting the communications to the communication platforms, and to convert information received over the bridge media path between different media formats if the media format used by one of the at least two communication platforms is different than the media format used by another one of the at least two communication platforms.

28. The system of claim 27 further comprising a media server interfaced with the bridge server.

29. The system of claim 27, wherein the plurality of information includes an IP address, a port number, and a plurality of functionality identifiers, the plurality of functionality identifiers indicating whether each of the communication platforms supports certain Unified Communications and Collaboration (UCC) functions.

30. The system of claim 27, wherein one of the at least two communication platforms is compatible with another one of the at least two communication platforms.