Method and conference controller for cluster-based conferencing

• US 20070109979A1
• Filed: 11/17/2005
• Published: 05/17/2007
• Est. Priority Date: 11/17/2005
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Glitho, Roch, Dssouli, Rachida, Fu, Chunyan
• Application Number:
  US11/280,206
• Publication Number:
  US 20070109979A1
• Time in Patent Office: Days
• US Class Current: 370/261
• CPC Class Codes: H04L 12/1813 for computer conferences, e.g. chat rooms instant messaging H04L51/04; protocols for multimedia communication H04L65/1101; arrangements for multi-party communication H04L65/403; telephonic conference arrangements H04M3/56; television conference systems H04N7/15
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/4038 with floor control
• CPC Class Codes: H04W 72/30 Resource management for broadcast services
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks

Abstract

A method and conference controller for cluster-based conferencing between ad-hoc network terminals supporting cluster-based conferences and legacy network terminals not equipped with such capabilities. The controller implements a Super User Agent (SUA) having a conference identity, a cluster member list including identities of legacy network'"'"'s terminals members of a cluster of terminals of the legacy network participating to the conference, and a cluster neighbour list that identifies terminals from an ad-hoc network that act as a super member of a cluster of terminals of the ad-hoc network. Responsive to receipt of a first message for establishing the conference between an ad-hoc network terminal and a legacy network terminal, the SUA sends a second message to establish a connection between the conference controller and one of the legacy network terminal and the ad-hoc network terminal, stores information relative to the conference, and notifies the terminals that the connection for use by the conference is established.

Claims

1. A method for multi-party conferencing between terminals of an ad-hoc network and terminals of a legacy network, the method comprising the steps of:

a. receiving at a conference controller of the legacy network a first message for an establishment of a conference between a terminal in the ad-hoc network and a terminal in the legacy network;

b. responsive to a receipt of the first message, sending from the conference controller a second message to establish a first connection between the conference controller and one of the terminal in the legacy network and the terminal in the ad-hoc network;

c. updating a Super User Agent (SUA) of the conference controller with information relative to the conference, the SUA being for use in establishing cluster-based conferences, and comprising;

a conference identity that identifies the conference;

a cluster member list including identities of terminals of the legacy network that are members of a cluster of terminals of the legacy network which participate to the conference; and

a cluster neighbour list that identifies at least one terminal from the ad-hoc network that acts as a super member of a cluster of at least one terminal of the ad-hoc network, the at least one terminal from the ad-hoc network also participating to the same conference; and

d. notifying at least one of the terminal in the ad-hoc network and the terminal in the legacy network that the first connection for use by the conference is established.

2. The method claimed in claim 1, further comprising the step of:

e. receiving at the conference controller a third message related to the establishment of a second connection for use by the conference, the second connection being between the conference controller and the other one of the terminal in the ad-hoc network and the terminal in the legacy network.

3. The method claimed in claim 1, wherein the first message is a Session Initiation Protocol (SIP) REFER message sent from the terminal in the ad-hoc network and the second message is a SIP INVITE message sent to the terminal in the legacy network.

4. The method claimed in claim 1, wherein the first message is a Session Initiation Protocol (SIP) INVITE message sent from the terminal in the ad-hoc network and the second message is a SIP INVITE message sent to the terminal in the legacy network.

5. The method claimed in claim 1, wherein the first message is a Session Initiation Protocol (SIP) REFER message sent from the terminal in the legacy network and the second message is a SIP INVITE message sent to the terminal in the ad-hoc network.

6. The method claimed in claim 1, wherein the first message is a Session Initiation Protocol (SIP) REFER message sent from the terminal in the legacy network and the second message is a SIP REFER message sent to the terminal in the ad-hoc network.

7. The method claimed in claim 1, wherein the first message comprises clustering information associated with a cluster of terminals to which a sender of the first message belongs.

8. The method claimed in claim 1, wherein the second message comprises clustering information associated with the cluster of terminals of the legacy network.

9. The method claimed in claim 1, wherein step d. comprises sending a Session Initiation Protocol (SIP) NOTIFY message from the conference controller to notify one of the terminal in the ad-hoc network and the terminal in the legacy network that the first connection for use by the conference is established.

10. A conference controller of a legacy network, comprising:

a super user agent for use in establishing cluster-based conferences, the super user agent comprising;

a conference identity that identifies a given conference;

a cluster member list including identities of any terminals of the legacy network that are members of a cluster of terminals of the legacy network which participate to the given conference; and

a cluster neighbour list that identifies at least one terminal from an ad-hoc network that acts as a super member of a cluster of at least one terminal of the ad-hoc network, the at least one terminal from the ad-hoc network also participating to the given conference;

the super user agent, responsive to a receipt of a first message for an establishment of the given conference between a terminal in the ad-hoc network and a terminal in the legacy network, sending a second message to establish a first connection between the conference controller and one of the terminal in the legacy network and the terminal in the ad-hoc network, storing information relative to the given conference, and notifying at least one of the terminal in the ad-hoc network and the terminal in the legacy network that the first connection for use by the given conference is established.

11. The conference controller claimed in claim 10, wherein the super user agent of the conference controller receives a third message related to the establishment of a second connection for use by the conference, the second connection being between the conference controller and the other one of the terminal in the ad-hoc network and the terminal in the legacy network.

12. The conference controller claimed in claim 10, wherein the first message is a Session Initiation Protocol (SIP) REFER message sent from the terminal in the ad-hoc network and the second message is a SIP INVITE message sent to the terminal in the legacy network.

13. The conference controller claimed in claim 10, wherein the first message is a Session Initiation Protocol (SIP) INVITE message sent from the terminal in the ad-hoc network and the second message is a SIP INVITE message sent to the terminal in the legacy network.

14. The conference controller claimed in claim 10, wherein the first message is a Session Initiation Protocol (SIP) REFER message sent from the terminal in the legacy network and the second message is a SIP INVITE message sent to the terminal in the ad-hoc network.

15. The conference controller claimed in claim 10, wherein the first message is a Session Initiation Protocol (SIP) REFER message sent from the terminal in the legacy network and the second message is a SIP REFER message sent to the terminal in the ad-hoc network.

16. The conference controller claimed in claim 10, wherein the first message comprises clustering information associated with a cluster of terminals to which a sender of the first message belongs.

17. The conference controller claimed in claim 10, wherein the second message comprises clustering information associated with the cluster of terminals of the legacy network.

18. The conference controller claimed in claim 10, wherein step d. comprises sending a Session Initiation Protocol (SIP) NOTIFY message from the conference controller to notify one of the terminal in the ad-hoc network and the terminal in the legacy network that the first connection for use by the conference is established.

19. The conference controller claimed in claim 10, wherein the information relative to the given conference includes the conference identity and the cluster neighbour list.