HUB BASED CLEARING HOUSE FOR INTEROPERABILITY OF DISTINCT UNIFIED COMMUNICATIONS SYSTEMS

• US 20160006683A1
• Filed: 07/06/2015
• Published: 01/07/2016
• Est. Priority Date: 03/31/2011
• Status: Active Grant

• Current Assignee: Nextplane, Inc.
• Original Assignee: Nextplane, Inc.
• Inventors: Pujare, Sanjay M., Bellan, Saravanan, Restelli, Silvia, Raina, Yogesh, Shahidi, Farzin Khatib
• Granted Patent: US 9,992,152 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• 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 61/2575 using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
• CPC Class Codes: H04L 61/2589 over a relay server, e.g. traversal using relay for network address translation [TURN]
• CPC Class Codes: H04L 63/104 Grouping of entities
• CPC Class Codes: H04L 65/103 in the network
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion

Abstract

A hub-based clearing house for interoperability of distinct unified communication systems is disclosed. According to one embodiment, a system comprises a database that stores configuration information for the system; an administrator module that maintains the configuration information; a federation server that is connected to a first unified communications system and a second unified communications system. The federation server comprises a first translator that translates a first formatted message received from the first unified communications system into a common language formatted message, a second translator that translates the common language formatted message into a second formatted message, and a routing engine that routes the second formatted message to the second unified communications system.

Claims

1. A system, comprising:

a federation server that is connected to a first domain and a second domain, the federation server comprising,

a translator that translates a first formatted message received from the first domain into a second formatted message, and

a routing engine that routes the second formatted message to the second domain, wherein the federation server allows the first domain that runs a first type of unified communications application to appear as running a second type of unified communications application, wherein the second domain runs the second type of unified communications application.

2. The system of claim 1, wherein the translator translates the first formatted message into a common language formatted message and translates the common language formatted message into the second formatted message.

3. The system of claim 2, wherein the common language formatted message contains at least one field in the first formatted message.

4. The system of claim 2, wherein the common language formatted message contains at least one field in the second formatted message.

5. The system of claim 2, wherein the format of the common language formatted message is generic Session Initiation Protocol (SIP).

6. The system of claim 1, further comprising a database that stores configuration information for the system.

7. The system of claim 6, further comprising an administrator module that maintains the configuration information.

8. The system of claim 7, wherein the administrator module sets enforcement policies for determining whether messages received by the federation server are acceptable.

9. The system of claim 8, wherein the federation server further comprises a policy enforcement engine that applies the enforcement policies to the first formatted message.

10. The system of claim 1, further comprising load balancers that manage and direct communications traffic to the federation server to make efficient use of available system resources.

11. The system of claim 1, further comprising a relay server that relays real-time media communications traffic between the first domain and the second domain.

12. The system of claim 1, further comprising a transcoder that transcodes real-time media communications traffic between the first domain and the second domain.

13. The system of claim 1, further comprising a file sharing server that relays file transfer data between the first domain and the second domain using dissimilar file transfer protocols.

14. The system of claim 1, wherein the federation server is connected to the first domain through a first connector and is connected to the second domain through one of the first connector and through a second connector.

15. The system of claim 14, wherein each of the first connector and the second connector is configured to connect to multiple unified communications (UC) systems.

16. The system of claim 7, wherein only the administration module has direct access to the database.

17. The system of claim 6, wherein the database is a relational database.

18. The system of claim 1, wherein the federation server allows the first domain that runs a first type of unified communications application to appear as running a second type of unified communications application that federates with the second domain based on a published service (SRV) record.

19. A method, comprising:

connecting a first domain and a second domain through a federation server;

receiving into the federation server a first formatted message from the first domain;

translating the first formatted message into a second formatted message; and

routing the second formatted message from the federation server to the second domain, wherein the federation server allows the first domain that runs a first type of unified communications application to appear as running a second type of unified communications application, wherein the second domain runs the second type of unified communications application.

20. The method of claim 19, further comprising translating the first formatted message into a common language formatted message and translating the common language formatted message into the second formatted message.

21. The method of claim 20, wherein the common language formatted message contains at least one field in the first formatted message.

22. The method of claim 20, wherein the common language formatted message contains at least one field in the second formatted message.

23. The method of claim 20, wherein the format of the common language formatted message is generic Session Initiation Protocol (SIP).

24. The method of claim 19, further comprising setting enforcement policies for determining whether messages received by the federation server are acceptable.

25. The method of claim 24, further comprising applying the enforcement policies to the first formatted message.

26. The method of claim 19, wherein the federation server allows the first domain that runs a first type of unified communications application to appear as running a second type of unified communications application that federates with the second domain based on publishing a service (SRV) record.

27. The method of claim 26, wherein publishing the SRV record directs the first formatted message to the federation server.