Centralized Controller for Distributed Handling of Telecommunications Features

• US 20080084840A1
• Filed: 10/05/2006
• Published: 04/10/2008
• Est. Priority Date: 10/05/2006
• Status: Active Grant

• Current Assignee: Arlington Technologies, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Avaya Incorporated
• Inventors: Baker, Albert J., Zenner, Hal B., Sangermano, John Joseph
• Granted Patent: US 7,656,836 B2
• Time in Patent Office: Days
• US Class Current: 370/329
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/4053 without floor control
• CPC Class Codes: H04L 65/75 Media network packet handling
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1091 Interfacing with client-server systems or between P2P systems
• CPC Class Codes: H04L 67/1093 Some peer nodes performing special functions
• CPC Class Codes: H04M 3/42272 whereby the subscriber registers to the terminals for personalised service provision

Abstract

A method is disclosed that enables an improvement in the scalability of a centralized server by reallocating to the client endpoints some, but not all, of the feature functionality of the server. Each logical user in the system is represented by his own private domain of endpoint entities, from which an endpoint is selected to serve as a super peer to represent the user to the centralized server. Furthermore, a designated endpoint is selected, also from the private domain of devices, to handle some of the telecommunications features that the server otherwise would have handled. Each endpoint in the private domain is permitted to have limited direct access to the server, typically for the purposes of registering and subscribing to features, in addition to and in contrast with the indirect access through the super peer. During the subscribing process, the server redirects a subscribing endpoint to the designated endpoint that is handling the feature.

Claims

1. A method comprising:

receiving, at a data-processing system, a first message from a first client endpoint that is a member of a user domain, wherein said first client endpoint attempts to subscribe to a first telecommunications feature via said first message;

determining which one of (i) a designated client endpoint that is a member of said user domain and (ii) said data-processing system is to handle said first telecommunications feature; and

when said first telecommunications feature is to be handled by said designated client endpoint, transmitting a second message to at least one member client endpoint in said user domain, wherein said second message is transmitted after receiving said first message;

wherein all of the client endpoints in said user domain are associated with a first user.

2. The method of claim 1 wherein said first client endpoint is one of said at least one member client endpoint.

3. The method of claim 1 wherein said designated client endpoint is one of said at least one member client endpoint, and wherein said second message indicates that an endpoint in said user domain other than said designated client endpoint is subscribing to said first telecommunications feature.

4. The method of claim 3 further comprising initiating a session to said designated client endpoint that instructs said designated client endpoint to handle said first telecommunications feature.

5. The method of claim 3 wherein said second message indicates that said first client endpoint specifically is subscribing to said first telecommunications feature.

6. The method of claim 3 wherein said first telecommunications feature is related to the monitoring of device presence.

7. The method of claim 1 further comprising:

receiving, at said data-processing system, a third message from a second client endpoint that is also a member of said user domain, wherein said second client endpoint attempts to subscribe to a second telecommunications feature via said third message;

determining which one of (i) said designated client endpoint that is a member of said user domain and (ii) said data-processing system is to handle said second telecommunications feature; and

when said second telecommunications feature is to be handled by said data-processing system, transmitting a fourth message to said first client endpoint that indicates that said first client endpoint has been subscribed to said first telecommunications feature.

8. The method of claim 1 wherein the determination of where said first telecommunications feature is to be handled is based on a first capability of said first client endpoint.

9. A method comprising:

receiving, at a data-processing system, a first message from a first client endpoint that is a member of a private domain that is defined by a first attribute, wherein said first client endpoint attempts to subscribe to a first telecommunications feature via said first message;

determining, based on at least one rule that is related to said first attribute, which one of (i) a designated client endpoint that is a member of said private domain and (ii) said data-processing system is to handle said first telecommunications feature; and

when said first telecommunications feature is to be handled by said designated client endpoint, transmitting a second message to at least one member client endpoint in said private domain, wherein said second message is transmitted after receiving said first message.

10. The method of claim 9 wherein said first attribute is physical proximity of multiple client endpoints to each other.

11. The method of claim 10 wherein said at least one rule comprises a rule that is related to bandwidth allocation within a communication channel.

12. The method of claim 10 wherein said at least one rule comprises a rule that is related to the location of said first client endpoint.

13. The method of claim 9 wherein said first client endpoint is one of said at least one member client endpoint.

14. The method of claim 9 wherein said designated client endpoint is one of said at least one member client endpoint, and wherein said second message indicates that an endpoint in said private domain other than said designated client endpoint is subscribing to said first telecommunications feature.

15. The method of claim 14 further comprising initiating a session to said designated client endpoint that instructs said designated client endpoint to handle said first telecommunications feature.

16. The method of claim 14 wherein said second message indicates that said first client endpoint specifically is subscribing to said first telecommunications feature.

17. The method of claim 9 further comprising:

receiving, at said data-processing system, a third message from a second client endpoint that is also a member of said private domain, wherein said second client endpoint attempts to subscribe to a second telecommunications feature via said third message;

determining, based on at least one rule that is related to said first attribute, which one of (i) said designated client endpoint that is a member of said private domain and (ii) said data-processing system is to handle said second telecommunications feature; and

when said second telecommunications feature is to be handled by said data-processing system, transmitting a fourth message to said first client endpoint that indicates that said first client endpoint has been subscribed to said first telecommunications feature.

18. The method of claim 9 wherein the determination of where said first telecommunications feature is to be handled is based on a first capability of said first client endpoint.

19. A method comprising:

receiving, at a data-processing system, a first message from a first client endpoint that is a member of a private domain, wherein said first client endpoint attempts to subscribe to a first telecommunications feature via said first message;

determining which one of (i) a designated client endpoint that is a member of said private domain and (ii) said data-processing system is to handle said first telecommunications feature; and

when said first telecommunications feature is to be handled by said designated client endpoint, initiating a call to said designated client endpoint that instructs said designated client endpoint to handle said first telecommunications feature.

20. The method of claim 19 wherein when said first telecommunications feature is to be handled by said designated client endpoint, transmitting a second message to at least one member client endpoint in said private domain, wherein said second message is transmitted after receiving said first message.

21. The method of claim 20 wherein all of the client endpoints in said private domain are associated with a first user.

22. The method of claim 20 wherein said first client endpoint is one of said at least one member client endpoint.

23. The method of claim 20 further comprising:

receiving, at said data-processing system, a third message from a second client endpoint that is also a member of said private domain, wherein said second client endpoint attempts to subscribe to a second telecommunications feature via said third message;

determining, based on at least one rule that is related to said first attribute, which one of (i) said designated client endpoint that is a member of said private domain and (ii) said data-processing system is to handle said second telecommunications feature; and

when said second telecommunications feature is to be handled by said data-processing system, transmitting a fourth message to said first client endpoint that indicates that said first client endpoint has been subscribed to said first telecommunications feature.

24. The method of claim 19 wherein the determination of where said first telecommunications feature is to be handled is also based on at least one rule that is related to an attribute of said private domain.