WO2007068208A1

WO2007068208A1 - A method for realizing service based on group

Info

Publication number: WO2007068208A1
Application number: PCT/CN2006/003401
Authority: WO
Inventors: Jinzhou Ye
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2005-12-16
Filing date: 2006-12-13
Publication date: 2007-06-21
Also published as: CN100442698C; CN1983944A

Abstract

The present invention comprises a method and system for realizing service based on group, with multimedia communication method, the user in the group can authorize the use authority of appointed service to the other user as third side. In the present invention, a group user establishes or modifies the consignment relation in network unit that saves group subscription information, so that the group user consigns it’s group service to other users. The consignment relation comprises two using method, the first method, after the consignment relation becomes effective or be canceled, notifying the network unit that provides correlative group service modifies the actual user list of the group service; the second method, the network unit that provides correlative group service acquires directly the actual user list that is effective currently from the network unit that saves group subscription information at the time of needing, replacing the consigning user by the consigned user therein. The network unit that provides the service can perform process according to the presetting strategy, if the consigning user is using service that is affected by the consignment relation when the consignment relation is becoming effective.

Description

Group-based business implementation method

This application claims the priority of the Chinese patent application filed on Dec. 16, 2005, the Chinese Patent Office, Application No. 200510111610.X, entitled "Group-based Business Implementation Method," In this application.

Technical field

The present invention relates to a multimedia communication method, and more particularly to a group-based service implementation method and system.

Background technique

In the third generation of mobile communication (The Third Generation, "3G"), there is also a system similar to the Next Generation Network ("NGN"), which is the Internet Protocol Multimedia Core Network Subsystem ( IP Multimedia Subsystem, the tube is called "IMS".

IMS is the original circuit domain of the Wideband Code Division Multiple Access (WCDMA) network based on the 3rd Generation Partnership Project (3GPP) R5/R6 standard. A relatively independent IP multimedia subsystem superimposed on the basis of the packet domain is a target network in which the 3G mobile network implements packet voice and packet data to provide unified multimedia services and applications. The IMS adopts the IP packet domain as the carrier channel for its control signaling and media transmission, and uses the Session Initiation Protocol (SES) as the call control signaling to implement service management, session control and bearer access. The three are separated. As a result, IP-based voice and multimedia services, open service interfaces, and flexible business development capabilities are available.

The IMS network provides IP multimedia value-added services for IMS users through various application servers (Application Servers, called "AS"). Here, the AS includes three types: SIPAS, Open Services Architecture AS (OSAAS), and IP Multimedia Service Switching Function ('ΊΜ-SSF').

In the IMS architecture, multiple enabled logical function network elements, such as instant messengers, are introduced.

(Instant Messenger, tube called "IM ,,), rendering techniques (Presence Technology), scalable language text has been marked ί ^{^:} When the device management service (Extensible Mark-up Language Document Management Server, referred to as" XDMS ") and so on, based on These enable logical function network elements can build a multi-service application architecture. Presentation technology is applied on the one hand to the messenger service of point-to-point instant messaging services such as yahoo, MSN and AOL on the Internet; on the other hand, it is applied to IM services or "push-to-talk" in mobile data services, (Push To Talk, the term "TTT") is a combination of services, which are mainly used for mobile terminals supporting ΙΜ or ΡΤΤ services.

Currently, the Open Mobile Alliance ("Open" Alliance) defines the Extensible Mark-up Language Document Management (XDM) group function under various application services. 3GPP also introduces The corresponding architecture and definition, especially in conferences, push-to-talk over cellular (PoC), chat, IM, games, etc., group functions are widely used. At the same time, these enabled logic function network elements are also The expansion of multiple services offers the possibility.

In the prior art, only the group user's own information is included in the related server of the group service, and the group service can only be routed to the terminal where the group user is located. Therefore, when the group user cannot handle the service by itself, the service can only be abandoned.

Summary of the invention

In view of this, the main purpose of embodiments of the present invention is to provide a group-based service implementation method, such that a user in a group can grant a right to use a designated service to other users of a third party.

Another object of the present invention is to provide a group-based service implementation system, which implements change and authorization of group usage rights, and enriches service provisioning and support capabilities under the IMS network system.

One embodiment of the group-based service implementation method provided by the present invention includes the following steps:

A. Establish or modify a delegation relationship in the group subscription information in the first network element, where the entrusted relationship includes the entrusted user and the entrusted user;

B. The second network element obtains the entrusted relationship;

C. When the second network element processes the services of the group, the service is routed to the trusted user according to the delegation relationship.

An embodiment of the group-based service implementation system provided by the present invention includes: a first network element storing group subscription information and a second network element processing group service, where

The first network element includes:

a setting unit, configured to establish or modify a delegation relationship in the group subscription information, the delegation relationship Including the trusted user and the delegated user;

a sending unit, configured to send the delegation relationship to the second network element according to the request of the second network element;

The second network element includes:

a requesting unit, configured to request the delegation relationship from the first network element;

The service processing unit is configured to process the group service, and when processing the group service with the delegation relationship, route the service to the delegated user according to the delegation relationship.

By implementing the entrusting relationship, the group user can conveniently select other users of the third party to proxy any service in the group, thereby enriching the user experience and perfecting the IMS user service function. DRAWINGS

1 is a schematic diagram of a delegation relationship of a group user in the present invention;

2 is a schematic diagram of changes in group user group rights before and after delegation in the present invention;

3 is a flowchart of group user authentication according to a first embodiment of the present invention;

4 is a delegation flow chart according to a first embodiment of the present invention;

FIG. 5 is a flowchart of a group service process after a delegation relationship is formed according to the first embodiment of the present invention; FIG.

6 is a flowchart of a group service processing after a delegation and a delegation relationship are formed according to a second embodiment of the present invention;

Figure 7 is a flow chart showing the group service processing after the cancellation of the delegation and the cancellation of the delegation relationship according to the third embodiment of the present invention;

8 is a flowchart of a group service process after a dynamic delegation and a delegation relationship are formed according to a fourth embodiment of the present invention;

Figure 9 is a schematic block diagram of a first embodiment of the system of the present invention;

Figure 10 is a schematic block diagram of a second embodiment of the system of the present invention;

Figure 11 is a schematic block diagram of a third embodiment of the system of the present invention;

Figure 12 is a schematic block diagram of a fourth embodiment of the system of the present invention.

detailed description

The invention establishes or modifies a delegation relationship in a network element in which group subscription information is stored, so as to delegate the group user's own group service to other users. In this way, at the network element that provides the relevant group service When the business of the group is managed, the service can be routed to the delegated user according to the delegation relationship. The network element that provides the related group service can obtain the delegation relationship in a plurality of manners, and the network element that stores the group subscription information can notify the network element that provides the related group service after the delegation relationship is valid or canceled, and provide the related group. The network element of the service modifies the actual user list of the group service, and performs service routing according to the user list. The network element that provides the related group service can also directly obtain the network element that saves the group subscription information when needed. The currently active actual user list, in which the delegated user replaces the trusted user, and performs service routing according to the user list.

The invention will be further described in detail below with reference to the accompanying drawings.

In the present invention, the right to use the group service is entrusted by the user to other users of the third party, and then the other users of the third party replace the user to complete the business in the group, which is essentially the ownership of the group business user rights. Separated from the right to use.

As shown in FIG. 1, the group user 1 delegates the right to use the group service to the user A, and then the user A replaces the user 1 to complete the service in the group.

2 is a schematic diagram of user rights before and after the formation of the delegation relationship: Before the delegation relationship is formed, the user 1 has ownership and usage rights of the group, and after the delegation relationship is formed, the user 1 transfers the usage rights of the group to the user. A, but still retain its group ownership.

The establishment of the delegation relationship depends first on the owner of the group authority. Therefore, there is no need to perform any XDM (XML Document Management) access processing on the delegate, and the modification and maintenance of the group. The authority is still owned by the principal; secondly, it is assumed that the principal and the trustee are mutually trusting. Based on this dependency, a reliable delegation relationship can be formed.

After the delegation relationship is formed, the XDMS modifies the corresponding user list stored therein, and the AS (Application Server) obtains the modified group service user list from the XDMS, and authorizes the group according to the list. Group of business users.

There are two ways for this AS to obtain user list changes: one is to obtain directly, that is, when

When the AS initiates the service, it obtains the current list from the XDMS, and the modification of the list will be reflected in the current list before the list is obtained. The other is to use the rendering technology, that is, the AS subscribes to the XDMS user list change, once the XDMS modifies the user. The list sends a modification message to the AS to notify the modified content. In addition, there may be two cases when commissioning a business: One is static, that is, the user does not use the group service related to the delegation while the user performs the commissioned operation; the other is dynamic, that is, the user is using Group business related to delegation. The static mode is mostly used for meetings, etc. The dynamic mode is mostly used for games, chats, and the like.

In order to improve the security of the delegation, the group users must first

The XDMS performs authentication. After the authentication succeeds, the group service usage rights can be modified. The group user authentication process of the first embodiment of the present invention is as shown in FIG.

In step 301, the user 1 issues an authentication request to the proxy server.

In step 302, the proxy server responds to the request of the user 1 and presents the authentication input window to the user 1.

In step 303, the user 1 inputs authentication information such as his/her name and password. Through authentication, the security of entrusted authorization can be improved and the interests of users can be guaranteed.

In step 304, the user authentication information is passed to the XDMS, and the XDMS determines whether the user is legitimate according to the group user list.

In step 305, the XDMS returns the authentication success information by verifying the user authentication information. In step 306, the authentication success information is delivered to the user 1 by the proxy server to complete the user authentication.

The delegation process of the first embodiment of the present invention is as shown in FIG.

In step 401, the user 1 issues a delegation service request to the XDMS.

In step 402, the XDMS responds to the user 1 requesting a service request and requests the user 1 to enter a specific trusted content.

In step 403, the user 1 inputs the content of the delegation, and the XDMS modifies the user list of its memory according to the content. For example, user 1 hands over the business usage rights of the work group in which it is located to user A. The XDMS deletes the user 1 in the usage permission list in the work group, and replaces it by the user A to form a new group service usage permission list; or the XDMS expands the user 1 to the user 1 to indicate the user A. Through such a single input operation, the group user can conveniently select other users of the third party to proxy any service in the group, thereby enriching the user experience and perfecting the IMS user service function.

In step 404, the XDMS sends a message to User 1 that the delegation was successful. T N2006/003401 a 6—

In step 405, after the group service usage permission list is modified, the XDMS sends a delegation notification to the client user A, informing the user that the service authority of the work group of the user 1 is trusted.

In step 406, the XDMS also sends a delegation notification to other users of the work group in which the user 1 is located, informing the other users of the group that the user A is the group service of the user 1. After any commissioned service is successfully set up, the relevant users will be notified, including the trusted user, the delegated user and other users of the group. Therefore, the IMS user can know the related group service use member change information in time, and can be more autonomous. Determine the use of the business and improve the business functions of the IMS user.

After the delegation relationship is formed, the response process of other group users initiating the group service is as shown in FIG. 5. In step 501, other users of the group initiate a group service.

In step 502, the AS receives the service initiation request, and then applies to the XDMS to apply for the current user list of the group service usage rights.

In step 503, the XDMS returns a modified current user list.

In step 504, AS # resides in the list of existing users, and initiates an invitation to other users in the group in the list.

In step 505, the AS also initiates a service invitation to User A. Because user 1 has been used by the user

A replaces or user 1 has already pointed to user A, so when the AS initiates a service invitation according to the list, the location of the original user 1 is queried, and a service invitation is initiated to user A.

In step 506, user A responds to the group service ^:. Can be received, rejected.

In step 507, other users of the group also respond to the invitation of the group service, and may also accept or reject.

According to the delegation process of the first embodiment, the process in which the user 1 performs the delegation cancellation is similar, and only the user 1 needs to fill in the cancelled delegation contents. When the delegate cancellation is accepted by the XDMS, modify its user list: delete user A and revert to user 1. When the other users in the group initiate the service, the AS requests the XDMS to obtain the restored user list. Therefore, the user A's usage rights for the group service are invalid, and the delegation is successfully cancelled.

In the second embodiment of the present invention, the method for obtaining the entrusted user list is the subscription mode, and the group service processing method after the delegation and the delegation relationship are formed is as shown in FIG. 6.

In step 601, the AS requests the XDMS to subscribe to the workgroup user list change in advance. In step 602, the XDMS confirms the AS subscription and returns to the current workgroup user list.

In step 603, the user 1 issues a delegation service request to the XDMS.

In step 604, the XDMS responds to the user 1 requesting the service request and requests the user 1 to enter the specific delegation content.

In step 605, the user 1 inputs the content of the delegation, and the XDMS modifies the user list of its memory according to the content. For example, user 1 hands over the business usage rights of the work group in which it is located to user A. The XDMS deletes the user 1 in the usage permission list in the work group, and replaces it by the user A to form a new group service usage permission list; or the XDMS expands the user 1 to the user 1 to indicate the user A. Through such a simple input operation, the group user can conveniently select other users of the third party to proxy any service in the group, thereby enriching the user body and perfecting the IMS user service function.

In step 606, the XDMS sends a message to the user 1 that the delegation was successful.

In step 607, the XDMS sends a modification notification to the AS to modify the content that the AS has subscribed to, and informs the AS to modify the content: User A replaces user 1.

In step 608, the XDMS sends a message to the user 1 that the delegation was successful.

In step 609, after the group service usage permission list is modified, the XDMS sends a delegation notification to the client user A, informing the user A that the service authority of the work group of the user 1 is trusted.

In step 610, other users of the group initiate group services.

In step 611, the AS compares other users of the group in the list according to the received existing user list.

- Initiate an invitation.

In step 612, the AS also initiates a service invitation to User A. Since user 1 has been replaced by user A or user 1 has already pointed to user A, when the AS initiates a service invitation according to the list, the location of the original user 1 is queried, and a service invitation is initiated to user A.

In step 613, User A responds to the invitation to the group service. Can be received, rejected.

In step 614, other users of the group also respond to the invitation of the group service, and may also accept or reject.

According to the third embodiment of the present invention, after the cancellation of the commission and the cancellation of the commissioning relationship according to the second embodiment The group business processing flow is shown in Figure 7.

In step 701, the user 1 initiates a commissioned service cancellation request to the XDMS.

In step 702, the XDMS responds to the delegating service cancellation request.

In step 703, the user 1 fills in the cancelled delegation content and cancels the work group authorization for the user A. Based on the content, the XDMS modifies the work service group user list stored therein. User A is removed from the list and restored to user 1.

In step 704, a delegation cancellation success message is sent to the user 1.

In step 705, the XDMS sends a request cancellation notice to the AS that subscribes to the change of the work service group list, and the AS modifies the group list according to the notification, and also deletes the user A and restores it to the user 1.

In step 706, as with the delegation process, the XDMS also sends a notification to User A informing that the granted user 1 service usage rights of the granted user 1 are cancelled.

In step 707, the XDMS also sends a notification of the delegation cancellation to other users of the group. In step 708, after the delegation relationship between the user 1 and the user A is canceled, other users of the work group initiate the work group service.

In step 709, the AS responds to the service initiated application and sends a service invitation to other users of the group.

In step 710, the AS no longer sends a service invitation to the user A, but sends a service invitation to the user 1 according to the current user list.

In step 711, other users of the group respond to the business invitation.

In step 712, User 1 responds to the business invitation.

The group service processing flow after the formation of the dynamic delegation and the delegation relationship according to the fourth embodiment of the present invention is as shown in FIG.

In step 801, user 1 is in the business of the work group.

In step 802, other users of the group are also performing the service.

Steps 803 through 809 are the same as steps 603 through 609.

In step 810, since the user 1 is in the service, the AS separately sends an invitation to the service to the user A according to the modified user list.

In step 811, user A responds to the business invitation, which may also be accepted or rejected. 003401

-9 one

Absolutely. The entrusted operation that the user can perform while using the group service has no influence on the service that the user is using, and the entrusted user can join or not join, which makes the user experience more humanized and diversified. In the case that the user 1 delegates the user A during the service, the AS may be different according to the preset policy, and may directly add the user A to the service after modifying the user list; The entrusted service does not respond, maintains the status of the service, and does not change the personnel; or the AS can join the service after the AS obtains the permission of the service initiator, and if not, ignores the entrusted service. deal with.

The entrusting method according to the fifth embodiment of the present invention is the same as that of the second embodiment, and the only difference is that, in the request content of the user 1 of the present embodiment, in addition to the client being the user A and the commissioning service being the work group business, there is a request. The effective period, for example, December 1, 2005, 12: 00 - 22: 00, December 2 - 4, 09: 00 - 12: 00. The effective period of the entrusted service can be preset, and the user can use the entrusted business function more flexibly, arrange the time independently, and enrich the user experience, and strengthen the serviceability of the entrusted service.

Then, the XDMS only modifies the user list at the start time of the effective time, validates the delegation relationship, and sends a notification of the user list modification to the AS, and replaces the user 1 with the user A. When the effective period ends, the XDMS modifies the user list again, restores user A to user 1, and also notifies the AS of the modification. Specifically, at 12:00 on December 1, 2005, at 12:00 on December 2nd - 4th, and at 4:00 every day, replace User 1 with User A, on December 1, 2005 at 22: 00, December 2nd - 4th, every day at 12: 00, the user A is restored to the user 1 to realize the function of automatically enabling the commission relationship only during special time periods.

Referring to Figure 9 for a schematic block diagram of a first embodiment of the system of the present invention:

In this embodiment, the method includes: a first network element 91 storing group subscription information and a second network element 92 processing group service. The first network element may be an XDMS (Extensible Markup Language Document Management Server); the second network element may be an AS (Application Server).

A setting unit 911 and a transmitting unit 912 are included in the first network element; a request unit 921 and a service processing unit 922 are included in the second network element.

The setting unit 911 is configured to establish or modify a delegation relationship in the group subscription information, where the delegation relationship includes a trusted user and a delegated user. The modification of the entrusted relationship is completed by the entrusted user. Therefore, in order to ensure the security of the user's subscription data, the authentication unit may also be set in the first network element. 913, to authenticate the trusted user requesting to establish or modify the delegation relationship. The sending unit 912 is configured to send the delegation relationship to the second network element according to the request of the second network element. The requesting unit 921 in the second network element is configured to request the delegation relationship from the first network element; the service processing unit 922 is configured to process the group service, and when processing the group service having the delegation relationship, according to the delegation relationship Route the business to the delegated user.

The requesting unit 921 may request the first network element to request the user list of the group when the second network element processes the service based on the group; after receiving the request, the first network element is sent by the sending unit 912 to the second network. The meta returns a list of users of the group, and the delegation relationship is included in the user list. Thus, the business processing unit 922 can route the traffic to the delegated user based on the delegation relationship.

In addition, a local group user list storage unit may be set in the second network element to store the local group user list. The first network element may actively send the stored group user list to the second network element after the startup, and the second network element stores the list in the local group user list storage unit after receiving the list; After the second network element starts, the first network element requests the group user list from the first network element, and the first network element sends the stored group user list to the second network element according to the request, and the second network element stores the list in the second network element. local. When processing a service based on the group, the second network element only needs to route the service according to the information in the list.

In this regard, reference is made to the block diagram of the second embodiment of the system of the present invention shown in FIG. 10:

A local group user list is stored in the local group user list storage unit 923. After the second network element is started, the request unit 921 subscribes the change event of the group user to the first network element. The first network element according to the subscription, after the delegation relationship in the setting unit 911 is valid or cancelled, the sending unit 912 notifies the second network element of the entrusted relationship that is valid or cancelled. The second network element modifies the information in the local group user list storage unit 923 according to the entrusted relationship of the valid or canceled, and when the service processing unit 922 processes the service of the group, according to the entrusting relationship in the local group user list The service is routed to the delegated user.

Referring to Figure 11 for a block diagram of a third embodiment of the system of the present invention:

Different from the second embodiment of the system of the present invention shown in FIG. 10, an effective controller 914 is further disposed in the first network element, and is respectively connected to the setting unit 911 and the sending unit 912, and is configured to control the delegation relationship. Effective time. When entering the effective time period, the notification sending unit 912 notifies the second network element of the effective delegation relationship; when entering the invalid time period, the notification sending unit 912 will cancel the 003401

- 11 - The entrusted relationship informs the second network element.

The second network element modifies the information in the local group user list storage unit 923 according to the notification. If the delegation relationship takes effect, the service processing unit routes the group's service to the delegated user according to the delegation relationship. If the second network element receives the notification from the first network element caused by the delegation, if the trusted user is using the service affected by the delegation, the service processing unit may process in any of the following manners:

(1) Inviting the entrusted user to join the current business;

(2) the second network element joins the second user to the current service when receiving the request of the trusted user to join the current service;

(3) Maintain the current business status.

Of course, the specific method can be selected according to actual needs.

If the trusted user retrieves the message, the service processing unit routes the service of the group to the trusted user.

Referring to Figure 12, a block diagram of a fourth embodiment of the system of the present invention is shown:

Different from the first embodiment of the system of the present invention shown in FIG. 10, a notification unit 924 is further disposed in the second network element, for notifying the trusted user and/or the same group after the delegation relationship is validated or cancelled. Other users within the group. In this way, the user experience can be further personalized and diversified. The notification process for the user can be referred to the description in the previous method of the present invention, and will not be described here. As can be seen from the above description, the present invention establishes or modifies a delegation relationship by a group user in a network element in which group subscription information is stored, to delegate its own group service to other users. The network element that provides the related group service may be notified to modify the actual user list of the group service after the commissioning relationship is valid or canceled, and the network element that provides the related group service may also use the network that holds the group subscription information when needed. The element directly obtains the currently valid actual user list, in which the delegated user replaces the trusted user. Through the delegation relationship, the group user can conveniently select other users of the third party to proxy any service in the group, thereby enriching the user experience and perfecting the MS user service function.

If the entrusted user is using the service affected by the entrusted relationship when the entrusted relationship is in effect, the network element providing the service can be processed according to the preset policy, for example, inviting the entrusted user to join the current service, and receiving the entrusted user to join the current The business request is added to the current business, or just the record is not further processed, and so on. Because users can use group services while The entrusted operation performed does not affect the service that the user is using, and the entrusted user may or may not join, so that the user body is more humanized and diversified.

When setting the delegation relationship, the effective time period can be set at the same time, which increases the flexibility of the group user setting, so that the user can use the commissioned business function more flexibly, and the user experience is more abundant.

When the entrusted relationship is in effect or canceled, the relevant users can be notified, including the entrusted users and other users of the group, so that the IMS users can timely understand the change information of the related group service members, and can decide more autonomously. The use of services has improved the business functions of IMS users.

While the invention has been illustrated and described with reference to the preferred embodiments embodiments The spirit and scope of the invention.

Claims

Rights request

A group-based service implementation method, comprising the steps of:

B. The second network element obtains the entrusted relationship;

2. The group-based service implementation method according to claim 1, wherein the step B comprises:

When the second network element processes the service based on the group, requesting the user list of the group from the first network element;

The first network element returns a user list of the group to the second network element, and the delegation relationship is included in the user list.

The group-based service implementation method according to claim 1, wherein before the step A, the method further includes: the second network element subscribing to the first network element a change event of the group user;

The step B includes:

After the established or modified enrollment relationship takes effect, the first network element notifies the entrusted relationship to the second network element;

The second network element modifies the local group user list according to the delegation relationship.

4. The group-based service implementation method according to claim 3, wherein the step C comprises:

The second network element routes the service to the delegated user according to the local group user list.

The method for implementing a group-based service according to claim 3, wherein the method further comprises:

After canceling the entrusted relationship in the first network element, the first network element sends a notification to the second network element that subscribes to the change event of the group user;

The second network element cancels the delegation relationship in the local group user list according to the notification.

6. The group-based service implementation method according to claim 3, wherein the delegation relationship takes effect according to a time period;

When entering the effective time period, the first network element notifies the second network element to replace the trusted user in the group by the trusted user, and the second network element modifies the local group user list; When entering an invalid time period, the first network element notifies the second network element to restore the delegated user to a trusted user in the group, and the second network element modifies a local group user list .

The group-based service implementation method according to claim 3, wherein, when the second network element receives a notification from the first network element caused by the delegation, The trusted user is using the business affected by the delegation, then

The second network element invites the entrusted user to join the current service; or

The second network element joins the second user to the current service when receiving the request of the trusted user to join the current service; or

The second network element maintains the current status of the service.

The group-based service implementation method according to any one of claims 1 to 3, further comprising the steps of: before the establishing or modifying the delegation relationship:

The first network element authenticates a trusted user requesting to establish or modify a delegation relationship.

The group-based service implementation method according to any one of claims 1 to 7, wherein

The first network element is an extensible markup language document management server;

The second network element is an application server.

The group-based service implementation method according to any one of claims 1 to 7, wherein the method further comprises:

When the entrusted relationship is valid or cancelled, the entrusted user and/or other users in the same group are notified.

A group-based service implementation system, comprising: a first network element storing group subscription information and a second network element processing group service, wherein

The first network element includes:

a setting unit, configured to establish or modify a delegation relationship in the group subscription information, where the delegation relationship includes a trusted user and a delegated user; a sending unit, configured to send the delegation relationship to the second network element according to the request of the second network element;

The second network element includes:

The group-based service implementation system according to claim 11, wherein the requesting unit requests the first network element when the second network element processes a service based on the group a list of users for the group;

After the first network element receives the request, the sending unit returns a user list of the group to the second network element, where the entrusting relationship is included in the user list;

The service processing unit routes the service to the delegated user according to the delegation relationship.

The group-based service implementation system according to claim 11, wherein the second network element further comprises: a local group user list storage unit, configured to store a local group user list;

The requesting unit subscribes the change event of the group user to the first network element in advance;

After the entrusting relationship in the setting unit is valid or canceled, the sending unit notifies the second network element of the entrusting relationship that is valid or cancelled; the second network element modifies the entrusting relationship according to the effective or canceled Describe the information in the local group user list storage unit;

When the service processing unit processes the services of the group, the service is routed to the delegated user according to the delegation relationship in the local group user list.

The group-based service implementation system of claim 13, wherein the first network element further comprises:

The effective controller is respectively connected to the setting unit and the sending unit, and is configured to control an effective time of the delegation relationship. When entering the effective time period, the sending unit is notified to notify the second effective relationship. The network element, when entering the invalid time period, notifies the sending unit to notify the second network element of the cancelled delegation relationship.

The group-based service implementation system according to any one of claims 11 to 14, wherein the first network element further comprises: An authentication unit is configured to authenticate a trusted user requesting to establish or modify a delegation relationship.

The group-based service implementation system according to any one of claims 11 to 14, wherein the second network element further comprises:

The notification unit is configured to notify the delegated user and/or other users in the same group after the delegation relationship is valid or cancelled.

The group-based service realization system according to any one of claims 11 to 14, characterized in that

The second network element is an application server.