Method, Apparatus and Network for Multi-Domain Conference Management

• US 20160088111A1
• Filed: 08/31/2015
• Published: 03/24/2016
• Est. Priority Date: 09/18/2014
• Status: Active Grant

• Current Assignee: TATA Communications Limited (Tata Sons Pvt Ltd.)
• Original Assignee: TATA Communications Limited (Tata Sons Pvt Ltd.)
• Inventors: Wilson, Lee Joseph, Nocchi, Joseph W.
• Granted Patent: US 10,341,452 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 12/1822 Conducting the conference, e.g. admission, detection, selection or grouping of participants, correlating users to one or more conference sessions, prioritising transmission
• CPC Class Codes: H04L 12/1827 Network arrangements for conference optimisation or adaptation
• 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/403 Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15
• CPC Class Codes: H04L 67/1087 using cross-functional networking aspects
• CPC Class Codes: H04L 67/566 Grouping or aggregating service requests, e.g. for unified processing

Abstract

A conference management system, network, and method for enabling the management of teleconference resources across multiple telecommunications networks that serve multiple conference domains. A disclosed multi-domain conference manager (MDCM) subscribes to a network management platform and for one or more sets of entities. Each set defines a particular combination of i) communications service provider(s) (CSP) and ii) enterprise, in which the combination defines a particular scope of management. When a conference-related event occurs, such as a particular conference involving video endpoints being set up with a unified communications (UC) network, the MDCM can notify a CSP network that is within a same scope of management as the UC network, to report on related events as they occur. The MDCM can then coordinate the connection of resources associated with the multiple domains via a cascaded link between bridging resources that serve the different domains.

Claims

1. A conference management system in a first telecommunications network comprising:

a receiver that is configured to receive a second message from a second data-processing system specifying that a first conference is starting, wherein the first conference involves a predetermined set of entities identified in a first message transmitted to the second data-processing system;

a transmitter that is configured to transmit;

(i) the first message to the second data-processing system, wherein the first message specifies a subscription to events that involve the predetermined set of entities,

(ii) upon receiving the second message, a third message to a third data-processing system in a second telecommunications network, wherein the third message specifies to the third data-processing system to monitor for activities related to the first conference, and wherein the first and second telecommunications networks are managed by different service providers; and

a processor that is configured to coordinate, based on a fourth message being received from the third data-processing system subsequent to the transmitting of the third message and that specifies the first conference, the establishing of a communications link between a first bridging device in the first telecommunications network and a second bridging device in the second telecommunications network, wherein the first and second bridging devices are being used by the first conference.

2. The conference management system of claim 1, wherein the processor is further configured to determine a second conference identification (ID) in response to the receiving of the second message, wherein the first conference is identified by a first conference ID in the second message, and wherein the second conference ID serves to identify the first conference to the third data-processing system.

3. The conference management system of claim 1 wherein the transmitter is further configured to transmit a fifth message to a session manager, wherein the fifth message specifies that the communications link is to be established for the first conference.

4. The conference management system of claim 1, wherein the receiver is further configured to receive a fifth message from the second data-processing system, wherein the fifth message specifies that the first conference is ending;

wherein the processor is further configured to coordinate the dropping of the communications link between the first bridging device and the second bridging device, in response to the receiving of the fifth message; and

wherein the transmitter is further configured to transmit;

(i) a sixth message to a session manager, wherein the sixth message specifies that the communications link is to be dropped for the first conference, and

(ii) a seventh message to the third data-processing system, wherein the seventh message specifies to stop monitoring for activities related to the first conference.

5. The conference management system of claim 1 wherein the receiver is further configured to receive a fifth message from the third data-processing system, wherein the fifth message specifies that a participant endpoint has dropped from the first conference;

wherein the processor is further configured to coordinate the dropping of the communications link between the first bridging device and the second bridging device, in response to the participant endpoint being the last endpoint to have been using the second bridging device for the first conference; and

wherein the transmitter is further configured to transmit a sixth message to a session manager, specifying the first conference.

6. A first telecommunications network comprising:

a conference management system that is configured to;

(i) transmit, to a second data-processing system, a first message that specifies a subscription to events that involve a predetermined set of entities,

(ii) receive a second message from the second data-processing system specifying that a first conference is starting, wherein the first conference involves the set of entities identified in the first message,

(iii) transmit, upon receiving the second message, a third message to a third data-processing system in a second telecommunications network, wherein the third message specifies to the third data-processing system to monitor for activities related to the first conference, and wherein the first and second telecommunications networks are managed by different service providers, and

(iv) establish, upon receiving a fourth message from the third data-processing system wherein the fourth message specifies the first conference, a communications link between a first bridging device in the first telecommunications network and a second bridging device in the second telecommunications network, wherein the first and second bridging devices are being used by the first conference, and wherein the receiving of the fourth message is subsequent to the transmitting of the third message; and

a network management platform that is configured to;

(i) receive the first message from the conference management system,

(ii) receive, from the first bridging device, an indication that a communication session with a first endpoint has started, and

(iii) transmit the second message to the conference management system, in response to the receiving of (a) the first message and (b) the indication that the communication session has started.

7. The first telecommunications network of claim 6, further comprising a multipoint control unit, wherein the multipoint control unit is configured to provide the functionality of the first bridging device.

8. The first telecommunications network of claim 6, further comprising a session manager that is configured to add the communications link in response to receiving, from the conference management system, a message that specifies the first conference.

9. A method comprising:

transmitting, by a conference management system in a first telecommunications network to a second data-processing system, a first message that specifies a subscription to events that involve a predetermined set of entities;

receiving, by the conference management system, a second message from the second data-processing system specifying that a first conference is starting, wherein the first conference involves the set of entities identified in the first message;

upon receiving the second message, transmitting by the conference management system a third message to a third data-processing system in a second telecommunications network, wherein the third message specifies to the third data-processing system to monitor for activities related to the first conference, and wherein the first and second telecommunications networks are managed by different service providers; and

upon receiving a fourth message from the third data-processing system wherein the fourth message specifies the first conference, establishing by the conference management system a communications link between a first bridging device in the first telecommunications network and a second bridging device in the second telecommunications network, wherein the first and second bridging devices are being used by the first conference, and wherein the receiving of the fourth message is subsequent to the transmitting of the third message.

10. The method of claim 9, wherein the set of entities comprises an enterprise and a communications service provider, wherein the communications service provider manages the second telecommunications network.

11. The method of claim 9, further comprising determining a second conference identification (ID) in response to the receiving of the second message, wherein the first conference is identified by a first conference ID in the second message, and wherein the second conference ID serves to identify the first conference to the third data-processing system.

12. The method of claim 9 further comprising:

receiving, by the second data-processing system, the first message from the conference management system;

receiving, by the second data-processing system from the first bridging device, an indication that a communication session with a first endpoint has started; and

transmitting, by the second data-processing system, the second message to the conference management system, in response to the receiving of (i) the first message and (ii) the indication that the communication session has started.

13. The method of claim 9 wherein the establishing of the communications link comprises transmitting, by the conference management system, a fifth message to a session manager, wherein the fifth message specifies the first conference.

14. The method of claim 9 further comprising:

upon receiving the second message, transmitting by the conference management system a fifth message to a fourth data-processing system in a third telecommunications network, wherein the fifth message specifies to the fourth data-processing system to monitor for activities related to the first conference, and wherein the first and third telecommunications networks are managed by different service providers; and

upon receiving a sixth message from the fourth data-processing system wherein the sixth message specifies the first conference, establishing by the conference management system a communications link between the first bridging device and a third bridging device in the third telecommunications network, wherein the third bridging device is also being used by the first conference, and wherein the receiving of the sixth message is subsequent to the transmitting of the fifth message.

15. The method of claim 14 wherein the first, second, and third telecommunications networks are managed by different service providers.

16. The method of claim 9 further comprising:

receiving, by the conference management system, a fifth message from the second data-processing system, wherein the fifth message specifies that the first conference is ending; and

dropping by the conference management system, the communications link between the first bridging device and the second bridging device, in response to the receiving of the fifth message.

17. The method of claim 16 wherein the dropping of the communications link comprises:

transmitting, by the conference management system, a sixth message to a session manager, specifying the first conference; and

transmitting, by the conference management system, a seventh message to the third data-processing system, specifying to stop monitoring for activities related to the first conference.

18. The method of claim 9 further comprising:

receiving, by the conference management system, a fifth message from the third data-processing system, wherein the fifth message specifies that a participant endpoint has dropped from the first conference; and

dropping, by the conference management system, the communications link between the first bridging device and the second bridging device, in response to the participant endpoint being the last endpoint to have been using the second bridging device for the first conference.

19. The method of claim 18 wherein the dropping of the communications link comprises transmitting, by the conference management system, a sixth message to a session manager, specifying the first conference.

20. The method of claim 18 further comprising waiting for a predetermined time interval before the dropping of the communications link.