Servers and Methods for Controlling Group Management

• US 20070220005A1
• Filed: 05/26/2004
• Published: 09/20/2007
• Est. Priority Date: 05/26/2004
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Castro Castro, Fabian, Sanchez Herrero, Juan, Walker, John
• Application Number:
  US11/569,371
• Publication Number:
  US 20070220005A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04W 4/08 User group management
• CPC Class Codes: H04W 4/10 Push-to-Talk [PTT] or Push-On-Call services
• CPC Class Codes: H04W 76/45 for Push-to-Talk [PTT] or Push-to-Talk over cellular [PoC] services
• CPC Class Codes: H04W 8/186 Processing of subscriber group data
• CPC Class Codes: H04W 8/20 Transfer of user or subscriber data
• CPC Class Codes: H04W 84/08 Trunked mobile radio systems
• CPC Class Codes: H04W 88/18 Service support devices; Network management devices

Abstract

The present invention addresses the management of user groups, user contact lists, and user access lists in a telecom-communication system whereby a user access to a group and list management server for creating, deleting or modifying a group, contact list and access list in terms of group policies and members. User groups, user contact lists, and user access lists are operated without any validation other than being syntactically correct, and without taking into consideration the users access capabilities, the users privacy, and even the user existence. In particular, the telecommunication system may comprise a number of networks operated by different network operators where the users hold subscriptions. The present invention offers a new interface between a group management server and a subscriber server of a network operator where the users hold their subscriptions, so that user policies in the subscriber server govern operations on groups, contact lists and access lists.

Claims

1. A group server suitable for managing groups, contact lists or access lists of users, each user being a subscriber of a network operator, the group server comprising:

(a) a first protocol front-end for communication with the user and suitable for managing at least one element selected from;

user groups, user contact lists and user access lists;

(b) a second protocol front-end suitable for communication with a subscriber server of the network operator for the purpose of correlating group profiles in the group server with user profiles in the subscriber server; and

(c) a group evaluator module for checking whether the user, depending on group and user profiles, is allowed to, or barred from, creating, deleting, modifying, or being a member of at least one element selected from;

a user group, a user access list and a user contact list.

2. The group server of claim 1 wherein the second protocol front-end comprises a protocol handler module for dealing with a protocol suitable for supporting group-related operations applying to at least one element selected from:

a user group, a user access list and a user contact list, and for at least one user.

3. The group server of claim 1 wherein the second protocol front-end comprises a message parser module for dealing with group related operations, and a support function module for controlling local operations.

4. The group server of claim 1 wherein each group profile comprises:

a group identifier;

a group owner;

a number of data for each user member in the group that includes a user identifier and user policies; and

group specific information that includes policies for the group.

5. The group server of claim 1 wherein each group profile is applicable to at least one element selected from:

a user group, a user access list and a user contact list.

6. A subscriber server holding subscriber data for a subscriber of a network operator, and suitable for providing the subscriber data to a network entity wherein the subscriber is a user, the subscriber server comprising:

(a) a first protocol front-end for communication with the network entity; and

characterized by including;

(b) a second protocol front-end suitable for communication with a group server of user groups, user contact lists or user access lists, and for the purpose of correlating user profiles in the subscriber server with group profiles in the group server; and

(c) a user evaluator module for checking whether the user, depending on group and user profiles, is allowed to, or barred from, creating, deleting, modifying, or being a member of at least one element selected from;

a user group, a user access list and a user contact list.

7. The subscriber server of claim 6 wherein the second protocol front-end comprises a protocol handler module for dealing with a protocol suitable for supporting group-related operations applying to at least one element selected from:

a user group, a user access list and a user contact list, and for at least one user.

8. The subscriber server of claim 6 wherein the second protocol front-end comprises a message parser module for dealing with group related operations, and a support function module for controlling local operations.

9. The subscriber server of claim 6 wherein each user profile further comprises:

a user identifier;

user data under network operator premises;

generic group data that include policies applicable to all groups for the user; and

specific group data that includes policies and group identifier for each group.

10. The subscriber server of claim 9 wherein each user profile further comprises:

subscription data under network operator premises; and

common policies applicable to all groups for this user subscription.

11. A method of controlling in a group server the management of user groups, user contact lists or user access lists for a user, the groups, contact lists and access lists including a number of users, each user being subscriber of a network operator, the method including the steps of:

(a) receiving from the user an operation request intended to operate on at least one element selected from;

a user group, a user access list and a user contact list, the operation being selected from;

creating, deleting, and modifying the at least one selected element;

(b) correlating a group profile corresponding to the at least one selected element in the group server with at least one user profile obtainable from a subscriber server of the network operator; and

(c) checking whether the user, depending on group and user profiles, is allowed to, or barred from, creating, deleting, modifying, or being a member of the at least one selected element.

12. The method of claim 11 wherein the step b) of correlating a group profile with at least one user profile includes a step of submitting towards the subscriber server an operation request selected from a group of operations intended to respectively:

create or delete a group or list for the user;

include or withdraw a user in a group or list; and

update policies for at least one group or list.

13. The method of claim 12 wherein the step b) of correlating a group profile with at least one user profile includes a step of receiving from the subscriber server information obtainable from a user profile and usable in the step c) of checking whether the user is allowed to, or barred from, carrying out the requested operation.

14. The method of claim 11 further comprising a step of informing the subscriber server about the result of any operation carried out on a user by the group server in connection with a group or list.

15. The method of claim 11 further comprising a step of providing user identifiers under network operator premises upon a user'"'"'s retrieval operation request received from the subscriber server.

16. A method of controlling from a subscriber server the management in a group server of user groups, user contact lists and user access lists for a user, the user being a subscriber of a network operator, the method comprising:

(a) holding subscriber data for the user in the subscriber server of the network operator;

(b) correlating at least one user profile in the subscriber server with a group profile obtainable from the groupserver; and

(c) checking whether the user, depending on group and user profiles, is allowed to, or barred from, creating, deleting, modifying, or being a member of at least one element selected from;

a user group, a user access list and a user contact list.

17. The method of claim 16 wherein the step b) of correlating at least one user profile with a group profile includes a step of receiving from the group server an operation request selected from a group of operations intended to respectively:

create or delete a group or list for the user;

include or withdraw a user in a group or list; and

update policies for at least one group or list.

18. The method of claim 17 wherein the step b) of correlating at least one user profile with a group profile includes a step of submitting towards the group server information obtainable from the user, through network entities and via network protocols, for updating the user profile.

19. The method of claim 16 further comprising a step of submitting towards the group server a member updating operation request for updating status of members in a group or list according to users network status.

20. The method of claim 16 further comprising a step of submitting towards the group server a members retrieval operation request for retrieving members of a group or list identified by a common identifier.