System and method for controlling and managing sessions between endpoints in a communications system

• US 20040133683A1
• Filed: 12/31/2002
• Published: 07/08/2004
• Est. Priority Date: 12/31/2002
• Status: Active Grant

• Current Assignee: Motorola Solutions, Inc.
• Original Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Inventors: Keller, Matthew, Mathis, James E., Lillie, Ross J., Newberg, Donald G.
• Granted Patent: US 7,366,780 B2
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 61/4535 using an address exchange platform which sets up a session between two nodes, e.g. rendezvous servers, session initiation protocols [SIP] registrars or H.323 gatekeepers
• CPC Class Codes: H04L 61/5069 for group communication, multicast communication or broadcast communication
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/65 Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04L 65/756 adapting media to device capabilities
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: Y02E 60/32 Hydrogen storage
• CPC Class Codes: Y02E 60/36 Hydrogen production from non-carbon containing sources, e.g. by water electrolysis

Abstract

In a communications system having a plurality of endpoints (240,242,246) each including a logical entity and its physical counterpart, a system for controlling and managing session between at least two endpoints. The system including a registration manager (202), an application layer router (204), a session controller (206), a group database manager (208), and at least one group entity (210).

Claims

1. In a communications system having a plurality of endpoints each comprising a logical entity and its physical counterpart, a system for controlling and managing sessions between at least two of the endpoints, comprising:

a registration manager for maintaining an association between each logical entity in the communications system and its physical counterpart to enable application layer routing to each said logical entity;

an application layer router for directing control and information messages to a target logical entity as a function of the associations maintained by the registration manager;

a session controller for determining the state of a requested session between at least two endpoints as a function of communication system resources and resources of said at least two endpoints, and for determining a set of corresponding session parameters upon acceptance of said requested session;

a group database manager communicatively coupled to said application layer router for maintaining a group list including at least one group, and for each group included on said group list maintaining an association between said group and at least one affiliated endpoint; and

at least one group entity correlating to each group in the group list maintained by said group database manager to which each said group entity is communicatively coupled, each said group entity being communicatively coupled to said registration manager and to said session controller and named and addressable at the application layer for receiving messages directed from said application layer router, each said group entity further configured for receiving a first message via application layer routing requesting a group directed session between an initiating endpoint and said group entity'"'"'s correlating group, communicating said requested group directed session to said session controller, communicating to said initiating endpoint via application layer routing the state of said requested group directed session and for an accepted group directed session a set of corresponding session parameters, and communicating to each other endpoint affiliated with said correlating group the accepted group directed session and the set of corresponding session parameters.

2. The system of claim 1 further comprising a group entity manager communicatively coupled to said application layer router and to each said group entity for creating, maintaining and destroying each said group entity.

3. The system of claim 2, wherein said group entity manager is further configured for directing messages requesting a group directed session with a target group to the group entity that correlates to that target group.

4. The system of claim 1 further comprising a parameter resolver communicatively coupled to said session controller and to said group database manager for establishing at least one set of potential session parameters usable in a session between at least two endpoints and usable by the session controller to determine a set of corresponding session parameters for an accepted session between said at least two endpoints.

5. The system of claim 1 further comprising at least one individual proxy communicatively coupled to said registration manager and to said session controller for intercepting a first message directed from said application layer router requesting an individual directed session between an initiating endpoint and at least one target endpoint, communicating said requested individual directed session to said session controller, communicating to said initiating endpoint via application layer routing the state of said requested individual directed session and for an accepted individual directed session a set of corresponding session parameters, and communicating to said at least one target endpoint the accepted individual directed session and the set of corresponding session parameters.

6. The system of claim 5 further comprising an individual proxy manager communicatively coupled to said application layer router and to each said individual proxy for creating, maintaining and destroying each said individual proxy and for directing messages requesting a session with a target endpoint to the individual proxy servicing said session.

7. The system of claim 1 further comprising a multicast address manager communicatively coupled to said communications system for managing a pool of multicast addresses and for allocating a dedicated multicast address in response to a request for said dedicated multicast address.

8. The system of claim 7, wherein said multicast address manager is communicatively coupled to said session controller for allocating a dedicated multicast address in response to a request from said session controller for said dedicated multicast address.

9. The system of claim 7, wherein said multicast address manager is communicatively coupled to said group database manager for allocating a dedicated multicast address in response to a request from said group database manager for said dedicated multicast address.

10. The system of claim 1, wherein the corresponding session parameters include information for directing at least one endpoint affiliated with the group to a service specific entity.

11. In a communications system having a plurality of endpoints each comprising a logical entity and its physical counterpart and each including a Session Initiation Protocol (SIP) protocol User Agent Client (UAC) and a SIP User Agent Server (UAS), a system for controlling and managing sessions between at least two of the endpoints, comprising:

a registration manager for maintaining an association between each logical entity in the communications system and its physical counterpart to enable application layer routing to each said logical entity via the SIP protocol;

a SIP proxy for directing control and information messages to a target logical entity as a function of the associations maintained by the registration manager;

a session controller for determining the state of a requested session between at least two endpoints as a function of communication system resources and resources of said at least two endpoints, and for determining a set of corresponding session parameters upon acceptance of said requested session;

a group database manager communicatively coupled to said SIP proxy for maintaining a group list including at least one group, and for each group included on said group list maintaining an association between said group and at least one affiliated endpoint; and

at least one group entity correlating to each group in the group list maintained by said group database manager to which each said group entity is communicatively coupled, each said group entity communicatively coupled to said registration manager and said to session controller and including a SIP UAS for receiving messages directed from said SIP proxy, and further configured for receiving a first message from an initiating endpoint'"'"'s SIP UAC requesting a group directed session between said initiating endpoint and said group entity'"'"'s correlating group, communicating said requested group directed session to said session controller, communicating to said initiating endpoint'"'"'s SIP UAC the state of said requested group directed session and for an accepted group directed session a set of corresponding session parameters, and communicating to each other endpoint affiliated with said correlating group the accepted group directed session and the set of corresponding session parameters.

12. The system of claim 11 further comprising a group entity manager communicatively coupled to said SIP proxy and to each said group entity for creating, maintaining and destroying each said group entity.

13. The system of claim 11 further comprising a parameter resolver communicatively coupled to said session controller for establishing at least one set of potential session parameters usable in a session between at least two endpoints and usable by the session controller to determine a set of corresponding session parameters for an accepted session between said at least two endpoints.

14. The system of claim 11 further comprising at least one individual proxy communicatively coupled to said registration manager and to said session controller, each said individual proxy including a SIP UAS for intercepting messages directed from said SIP proxy, and further configured for receiving a first message from an initiating endpoint'"'"'s UAC requesting an individual directed session between said initiating endpoint and at least one target endpoint, communicating said requested individual directed session to said session controller, communicating to said initiating endpoint'"'"'s UAC the state of said requested individual directed session and for an accepted individual directed session a set of corresponding session parameters, and communicating to the UAS of said at least one target endpoint the accepted individual directed session and the set of corresponding session parameters.

15. The system of claim 14 further comprising an individual proxy manager communicatively coupled to said application layer router and to each said individual proxy for creating, maintaining and destroying each said individual proxy.

16. In a communications system having a plurality of endpoints each comprising a logical entity and its physical counterpart, a system for controlling and managing sessions between at least two of the endpoints, comprising:

a session controller for determining the state of a requested session between at least two endpoints as a function of communication system resources and resources of said at least two endpoints, and for determining a set of corresponding session parameters upon acceptance of said requested session;

a group database manager for maintaining a group list including at least one group, and for each group included on said group list maintaining an association between said group and at least one affiliated endpoint; and

at least one group entity correlating to each group in the group list maintained by said group database manager to which each said group entity is communicatively coupled, each said group entity being communicatively coupled to said session controller and configured for receiving a first message, using a transactional protocol, requesting a group directed session between an initiating endpoint and said group entity'"'"'s correlating group, communicating said requested group directed session to said session controller, communicating to said initiating endpoint, using the transactional protocol, the state of said requested group directed session and for an accepted group directed session a set of corresponding session parameters, and communicating to each other endpoint affiliated with said correlating group the accepted group directed session and the set of corresponding session parameters.

17. The system of claim 16 further including:

a registration manager communicatively coupled to each said group entity for maintaining an association between each logical entity in the communications system and its physical counterpart to enable messages to be sent using said transactional protocol to each said logical entity in the communications system; and

an application layer router for directing control and information messages to a target logical entity using said transactional protocol, said messages being directed as a function of the associations maintained by the registration manager.

18. The system of claim 16 further comprising a group entity manager communicatively coupled to each said group entity for creating, maintaining and destroying each said group entity and for directing messages requesting a group directed session with a target group to the group entity that correlates to that target group.

19. The system of claim 16 further comprising a parameter resolver communicatively coupled to said session controller for establishing at least one set of potential session parameters usable in a session between at least two endpoints and usable by the session controller to determine a set of corresponding session parameters for an accepted session between said at least two endpoints.

20. The system of claim 16 further comprising at least one individual proxy communicatively coupled to said session controller and configured for receiving a first message, using a transactional protocol, requesting an individual directed session between an initiating endpoint and at least one target endpoint, communicating said requested individual directed session to said session controller, communicating to said initiating endpoint, using the transactional protocol, the state of said requested individual directed session and for an accepted individual directed session a set of corresponding session parameters, and communicating to said at least one target endpoint the accepted individual directed session and the set of corresponding session parameters.

21. The system of claim 20 further comprising an individual proxy manager communicatively coupled to each said individual proxy for creating, maintaining and destroying each said individual proxy and for directing messages requesting a session with a target endpoint to the individual proxy servicing said target endpoint.

22. The system of claim 16, wherein said transactional protocol is a Session Initiation Protocol (SIP) protocol.

23. In a communications system having a plurality of endpoints each comprising a logical entity and its physical counterpart, a system for controlling and managing sessions between at least two of the endpoints, comprising:

a session controller for determining the state of a requested session between at least two endpoints as a function of communication system resources and resources of said at least two endpoints, and for determining a set of corresponding session parameters upon acceptance of said requested session;

a group database manager for maintaining a group list including at least one group, and for each group included on said group list maintaining an association between said group and at least one affiliated endpoint; and

at least one group entity correlating to each group in the group list maintained by said group database manager to which each said group entity is communicatively coupled, each said group entity being communicatively coupled to said session controller and configured for receiving a first message, using a Session Initiation Protocol (SIP), requesting a group directed session between an initiating endpoint and said group entity'"'"'s correlating group, communicating said requested group directed session to said session controller, communicating to said initiating endpoint, using SIP, the state of said requested group directed session and for an accepted group directed session a set of corresponding session parameters, and communicating to each other endpoint affiliated with said correlating group the accepted group directed session and the set of corresponding session parameters.

24. A device for use in a communications network having a plurality of endpoints, comprising:

a receiver for receiving information over the network;

a transmitter for transmitting information over the network; and

a processor communicatively coupled to said receiver and transmitter for performing the functions of;

receiving a first message via application layer routing requesting a group directed session between an initiating endpoint and a group having at least one other affiliated endpoint;

obtaining a determination of the state of said requested group directed session;

communicating to said initiating endpoint via application layer routing the state of said requested group directed session and for an accepted group directed session a set of corresponding session parameters; and

communicating to each endpoint affiliated with said group the accepted group directed session and the set of corresponding session parameters,

wherein said device is named and addressable at the application layer.

25. A device for use in a communications network having a plurality of endpoints, comprising:

a receiver for receiving information over the network;

a transmitter for transmitting information over the network; and

a processor communicatively coupled to said receiver and transmitter for performing the functions of;

receiving a first message using a transactional protocol requesting a group directed session between an initiating endpoint and a group having at least one other affiliated endpoint;

obtaining a determination of the state of said requested group directed session;

communicating to said initiating endpoint using said transactional protocol the state of said requested group directed session and for an accepted group directed session a set of corresponding session parameters; and

communicating to each endpoint affiliated with said group the accepted group directed session and the set of corresponding session parameters.

26. A device for use in a communications network having a plurality of endpoints, comprising:

a receiver for receiving information over the network;

a transmitter for transmitting information over the network; and

a Session Initiation Protocol (SIP) User Agent Server communicatively coupled to said receiver and transmitter for performing the functions of;

receiving a first message from a SIP User Agent Client (UAC) in an initiating endpoint requesting a group directed session between said initiating endpoint and a group having at least one other affiliated endpoint;

obtaining a determination of the state of said requested group directed session;

communicating to said initiating endpoint'"'"'s SIP UAC the state of said requested group directed session and for an accepted group directed session a set of corresponding session parameters; and

communicating to each endpoint affiliated with said group the accepted group directed session and the set of corresponding session parameters.

28. The method of claim 26, wherein:

said first message includes a request for a session between said first endpoint and a group to which said at least one other endpoint is affiliated;

said first endpoint is unable to affiliate with said group; and

said group affiliation is performed on behalf of said first endpoint for facilitating said session between said first endpoint and said at least one other endpoint.

29. The method of claim 28, wherein said communications system includes a group entity and said group entity performs said group affiliation on behalf of said first endpoint.

27. In a communications system having at least one service entity and a plurality of endpoints each comprising a logical entity and a terminal, a method for facilitating a session between at least two of the endpoints, comprising the steps of:

receiving a first message having information that includes a request for a session between a first endpoint comprising a non-dispatch terminal and at least one other endpoint;

detecting that said first endpoint comprises a non-dispatch terminal as a function of said first endpoint being unable to perform at least one function; and

causing said at least one function to be performed on behalf of said first endpoint by at least one said service entity for facilitating said session between said first endpoint and said at least one other endpoint.

30. The method of claim 27, wherein:

said first endpoint is unable to generate a floor control request in order to source media during said session; and

said floor control request is performed on behalf of said first endpoint for facilitating said session between said first endpoint and said at least one other endpoint.

31. The method of claim 30, further comprising generating signaling to said first endpoint for causing said first endpoint to direct its media to a first service entity included in said communications system for causing said first service entity to generate said floor control request on behalf of said first endpoint.

32. The method of claim 31, further comprising causing information to be sent to said first endpoint for notifying said first endpoint that it cannot source media because another endpoint has the floor.

33. The method claim 32, wherein said information includes audio information.

34. The method of claim 33, wherein said audio information is a tone.

35. The method of claim 32, wherein said information is sent as a function of said first endpoint attempting to source its media during said session.

36. The method of claim 30, wherein said communications system includes a media manager service entity and a floor control service entity and said media manager service entity generates floor control requests to said floor control service entity on behalf of said first endpoint.

37. The method of claim 27, wherein:

said first endpoint is unable to exchange media via Internet Protocol (IP) multi-cast; and

said media exchange via IP multi-cast is performed on behalf of said first endpoint for facilitating said session between said first endpoint and said at least one other endpoint.

38. The method of claim 37 further comprising generating signaling to said first endpoint for causing said first endpoint to direct its media to a first service entity included in said communications system for causing said first service entity to perform said media exchange via IP multi-cast on behalf of said first endpoint.

39. The method of claim 37, wherein said first endpoint is configured for exchanging media via IP unicast, said method further comprising:

receiving unicast media from said first endpoint;

causing said unicast media to be transmitted to said at least one other endpoint in said-session via IP multicast; and

causing any multicast media transmitted by said at least one other endpoint in said session to be transmitted to said first endpoint via IP unicast.

40. The method of claim 37, wherein said communications system includes a media manager service entity for causing said media exchange via IP multicast to be performed on behalf of said first endpoint.