CN1968120B - A method and system for managing group information - Google Patents

Abstract

The invention discloses a method for managing group information, comprising: user terminal interacts with Portal Server, so that Portal Server constructs a management request message, and the management request message is defined by SOAP protocol; Portal Server sends the management request message to XDMS; XDMS manages group information according to the management request message. The invention also provides a system for managing group information. According to the present invention, by using the management message defined by the SOAP protocol between the Web Server (Portal Server) and the XDMS, the Portal Server manages the group information in the XDMS through the management message. At the same time, PortalServer provides group management functions to user terminals. Due to the use of Portal Server, PCs can be used as user terminals, which facilitates the management of group information in XDMS.

Description

A method and system for managing group information

technical field

The present invention relates to a communication technology, in particular to a method and system for managing group information.

Background technique

In the 3GPP (3rd Generation Partnership Project, third-generation mobile communication standardization partner project) specification and OMA (Open Mobile Alliance, Open Mobile Alliance) standard, various service engines (PoC, Presence, IM, etc.) need to access group information It is uniformly placed on XDMS (XML (Extensible Markup Language) Document Management Server) and managed in XML document format. Users can edit and manage group information on the mobile terminal.

As shown in FIG. 1 , in the existing technical solution, the mobile terminal interacts with the XDMS through the XCAP protocol (XML Configuration Access Protocol) to manage group information. In this way, the user can manage the group information on the XDMS on the mobile terminal.

However, due to the complex content of group information, for example, group information usually includes group name, group URI (Uniform Resource Identifier), validity period, etc., a large number of letters need to be input when editing a group, but there are few keys on the mobile phone, and it is difficult to input text. The information is very inconvenient, and the user experience of using the service is poor.

Contents of the invention

The purpose of the present invention is to provide a method and system for managing group information, which can manage group information in XDMS through Portal Server (portal server).

The invention discloses a method for managing group information, including:

User terminal interacts with Portal Server (portal server), so that Portal Server constructs management request message, and described management request message adopts SOAP (Simple Object Access Protocol) protocol definition;

Portal Server sends the management request message to XDMS (Extensible Markup Language Document Management Server);

The XDMS manages group information according to the management request message.

The management request message includes creating a group request message, browsing a group list request message, deleting a group request message, adding a single group member request message, browsing a group member request message, deleting a group member request message, viewing/ Modify group attribute request message and modify group member attribute request message.

The management includes creating groups, browsing group lists, deleting groups, adding single group members, browsing group members, deleting group members, viewing/modifying group attributes and modifying group member attributes.

The creation of groups specifically includes:

The user terminal sends a group creation request to XDMS through the Portal Server, and the group creation request includes user identification, group name and group validity period;

XDMS creates a group according to the group creation request, allocates the group URL and group URI according to the group name, and sets the validity period and creation time of the group.

The described group creation also includes:

XDMS returns to Portal Server and creates group response message, and described creation group response message includes group URL, group URI and creates group result;

The Portal Server sends a group creation response message to the user terminal.

The browsing group list specifically includes:

The user terminal sends a browsing group list request message to the XDMS through the Portal Server, and the browsing group list request message includes a user identification;

XDMS queries all group information created by the user according to the user identifier in the browse group list request message;

The XDMS sends a browsing group list response message to the user terminal through the Portal Server, and the browsing group list response message includes browsing group list results and a group list, and the group list includes a group URL, a group ID and Group URIs.

The deletion group specifically includes:

User terminal sends delete group request message to XDMS by Portal Server, and described delete group request message includes user identification and group URL;

XDMS deletes the group structure indicated by the group URL.

The deletion of the group also includes: XDMS sends a deletion group response message to the user terminal through the Portal Server, and the deletion group response message includes a deletion group response result.

The adding of a single group member specifically includes:

The user terminal sends an add group member request message to the XDMS through the Portal Server, and the added group member request message includes user identification, group URL and group member information;

XDMS adds the members indicated by the group member information to the group structure indicated by the group URL.

The deletion of group members specifically includes:

The user terminal sends a deletion group member request to XDMS through the Portal Server, and the deletion group member request includes a user ID, a group ID and a group member ID to be deleted;

The XDMS deletes the member information corresponding to the member identifier of the group to be deleted in the group corresponding to the group identifier.

The invention also discloses a system for managing group information, including:

The user terminal is used to interact with the portal server Portal Server, so that the Portal Server constructs the formation management request message sent to the Extensible Markup Language Document Management Server XDMS;

Portal Server, used to interact with the user terminal to obtain a management request message, and send the management request message to XDMS, the management request message is defined by the SOAP protocol;

The XDMS is configured to manage group information according to the management request message.

The Portal Server specifically includes:

The receiving module is used to receive the management request of the user terminal, and receive the response message of XDMS;

A message construction module, configured to construct a management request message according to a management request of the user terminal;

The sending module is configured to send the management request message constructed by the message construction module to the XDMS, and send the response message received by the receiving module to the user terminal.

The XDMS specifically includes:

Receiving module, for receiving the management request message of Portal Server;

A management module, configured to manage the group information according to the management request message received by the receiving module, and construct a response message according to the management result;

The sending module is used to send the response message constructed by the management module to the Portal Server.

According to the present invention, by adopting the management message defined by the SOAP (Simple Object Access Protocol) protocol between the Web Server (Portal Server) and the XDMS, the Portal Server is made to manage the group information in the XDMS through the management message. At the same time, Portal Server provides group management functions to user terminals. Due to the use of Portal Server, PCs can be used as user terminals, which facilitates users to manage group information in XDMS.

Description of drawings

FIG. 1 shows a schematic diagram of a management group information system in the prior art;

FIG. 2 shows a schematic diagram of a management group information system according to an embodiment of the present invention;

Fig. 3 shows the flowchart of creating a group according to an embodiment of the present invention;

FIG. 4 shows a flow chart of browsing a group list according to an embodiment of the present invention;

FIG. 5 shows a flow chart of deleting a group according to an embodiment of the present invention;

Fig. 6 shows the flowchart of adding a single group member according to an embodiment of the present invention;

FIG. 7 shows a flowchart of browsing group members according to an embodiment of the present invention;

FIG. 8 shows a flowchart of deleting group members according to an embodiment of the present invention;

FIG. 9 shows a flow chart of viewing/modifying group attributes according to an embodiment of the present invention;

Fig. 10 shows a flow chart of modifying attributes of group members according to an embodiment of the present invention.

Detailed ways

In order to make it easier for those skilled in the art to understand and realize the present invention, the embodiments of the present invention are described in conjunction with the accompanying drawings.

As shown in Figure 2, the present invention provides a kind of system of management group information, comprises: user terminal, is used for interacting with Portal Server, so that Portal Server constructs management request message; PortalServer, is used for interacting with user terminal and Constructing a management request message, and sending the management request message to XDMS, the management request message is defined by the SOAP protocol; XDMS is used to manage group information according to the management request message.

Described Portal Server specifically comprises: receiving module, is used for receiving the management request of user terminal, and receives the response message of XDMS; Message construction module, is used for constructing management request message according to the management request that receiving module receives; Sending module, is used for Send the management request message constructed by the message constructing module to the XDMS, and send the response message received by the receiving module to the user terminal.

Described XDMS specifically comprises: receiving module, is used to receive the management request message of Portal Server; Management module, is used for group information is managed according to the management request message that receiving module receives, and constructs response message according to management result; Sending module , used to send the response message constructed by the management module to the Portal Server.

The basic thought of the present invention is, adopts various management message defined by SOAP agreement between Web Server (Portal Server) and XDMS, makes Portal Server manage the group information in XDMS by this management message. At the same time, Portal Server provides group management functions to user terminals. The management messages include creating a group request message, browsing a group list request message, deleting a group request message, adding a single group member request message, browsing a group member request message, deleting a group member request message, viewing/modifying Group attribute request message, modify group member attribute request message, create group response message, browse group list response message, delete group response message, add single group member response message, browse group member response message, delete group Group member response message, view/modify group attribute response message, modify group member attribute response message, etc. Specifically, a user terminal such as a PC is connected to the Internet, and then logs in to the Portal Server. The user terminal interacts with the Portal Server, so that the Portal Server obtains management information. According to the obtained management information, the Portal Server uses the management message defined by the SOAP protocol Get or set group information in XDMS. In order to obtain or set group information in XDMS, the following processes can be realized through the above-mentioned management message: create group, browse group list, delete group, add single group member, browse group member, delete group member , View/modify group attributes, modify group member attributes. Each flow will be described below with reference to the accompanying drawings.

1. Create a group

As shown in Figure 3, the process of creating a group is described below.

Step 301, the user terminal selects the group management menu, and requests to visit the group creation page of the Portal Server.

Step 302, the Portal Server sends the page for creating a group to the user terminal.

Step 303, the user fills in the group basic information on the group creation page, and then sends a group creation request with the group basic information to the Portal Server.

Step 304, Portal Server sends to XDMS and creates group request (CreateGroupRequest), and described creation group request message includes user identification, group identification and group validity period;

An example message body for a group creation request is as follows:

<CreateGroupRequest>

<publicID>mary@abc.com</publicID>

<groupTitle>friends</groupTitle>

<duration>365</duration>

</CreateGroupRequest>

The above message body shows: request to create a group named friends, valid for 365 days.

Step 305, XDMS creates a group information document according to the group creation request, allocates a group URI and a group URL (Uniform Resource Locator) according to the group name, and sets the validity period and creation time of the group.

In step 306, the XDMS returns a create group response (CreateGroupResponse) message to the Portal Server, so as to return the group creation result to the Portal Server. The group creation response message includes a group URL, a group URI and a group creation result.

An example message body for creating a group response is as follows:

<CreateGroupResponse>

<retValue>0</retValue>

<groupURI>friends@group.abc.com</groupURI>

<groupURL>http://group.abc.com/service/group/user/mary@abc.com/friends.

xml</groupURL>

</CreateGroupResponse>

The above message body shows: the group is successfully created, the group URI is friends@group.abc.com, and the group URL is http://group.abc.com/service/group/user/mary@abc.com/ friends. xml.

In step 307, the Portal Server sends a group creation response message to the user terminal, so as to display the group creation result to the user.

2. Browse the group list

As shown in FIG. 4, the process of browsing the group list is described below.

Step 401, the user terminal sends a browse group list message to the Portal Server, and the browse group list message includes a user identifier.

In step 402, the Portal Server sends a query group request (QueryGroupRequest) message to the XDMS.

An example message body for a request to browse the group list is as follows:

<QueryGroupRequest>

<publicID>mary@abc.com</publicID>

</QueryGroupRequest>

The above message body shows: browsing group information whose user ID is mary@abc.com.

Step 403, the XDMS queries all group information files created by the user according to the user identifier in the request for browsing the group list.

Step 404, XDMS constructs a response message according to the group information inquired, and sends a browsing group list response (QueryGroupResponse) message to Portal Server, so that the group list inquired is returned, and the browsing group list response message includes browsing group A group result and a group list, the group list includes a group URL, a group name and a group URI.

An example of the message body of the browse group list response is as follows:

<QueryGroupResponse>

<retValue>0</retValue>

<groupList>

<groupInfo>

<url>http://group.abc.com/service/group/user/mary@abc.com/friends.xml</url>

<title>friends</title>

<uri>mary_friends@group.abc.com</uri>

</groupInfo>

</groupList>

</QueryGroupResponse>

The above message body shows: the browsing is successful, the obtained group information is, the group URL is http://group.abc.com/service/group/user/mary@abc.com/friends.xml, the group name For friends, the group URI is mary_friends@group.abc.com.

Step 405, the Portal Server sends a browse group list message to the user terminal, so that the user terminal displays the user's group list.

3. Delete group

As shown in FIG. 5, the process of deleting a group is described below.

Step 501, the user terminal selects a group from the group list, and then sends a delete group request message to the Portal Server, and the delete group request message includes a user ID and a group URL.

Step 502, the Portal Server sends a delete group confirmation request message to the user terminal, so as to ask the user terminal to confirm whether to delete the group.

Step 503, the user terminal sends a delete group confirmation response message to the Portal Server to indicate that the user confirms to delete the group.

Step 504, Portal Server sends a delete group request (DeleteGroupRequest) message to XDMS.

An example body of a delete group request is as follows:

<DeleteGroupRequest>

<publicID>mary@abc.com</publicID>

<groupUrl>http://group.abc.com/service/group/user/mary@abc.corn/friends.x

ml</groupUrl>

</DeleteGroupRequest>

The above message body shows that the group URL requesting to delete the group whose user ID is mary@abc.com is group.abc.com/service/group/user/mary@abc.com/friends.xml group.

Step 505, XDMS deletes the group structure indicated by the group URL according to the group URL in the delete group request message.

Step 506: After deleting the group structure indicated by the group URL, the XDMS returns a delete group response (DeleteGroupResponse) message to the Portal Server, and the delete group response message includes the delete group response result.

An example message body of the delete group response message is as follows:

<DeleteGroupResponse>

<retValue>0</retValue>

</DeleteGroupResponse>

The above message body shows: the deletion is successful.

Step 507, the Portal Server sends a delete group response to the user terminal, so as to prompt the user terminal to delete the group result.

4. Add a single group member

As shown in Figure 6, the process of adding a single group member is described below.

Step 601, the user terminal selects a group from the group list, and then sends a request message for adding a group member to the Portal Server.

Step 602, the Portal Server sends an add member page message to the user terminal, so that the user terminal fills in the group member information according to the add member page.

Step 603, the user terminal inputs group member information according to the page for adding members, and sends a request message for adding a group member to the Portal Server, and the request message for adding a group member includes a user ID, a group URL and group member information.

Step 604, the Portal Server sends an add group member request (AddGroupMemberRequest) message to the XDMS.

An example message body for adding group members is as follows:

<AddGroupMemberRequest>

<publicID>mary@abc.com</publicID>

<groupUrl>http://group.abc.com/service/group/user/mary@abc.com/friends.x

ml</groupUrl>

<memberInfo>

<uri>zhangsan@abc.com</uri>

<name>zhangsan</name>

<info>best friend</info>

</memberInfo>

</AddGroupMemberRequest>

The above example shows: in the group whose user ID is mary@abc.com the group URL is http://group.abc.com/service/group/user/mary@abc.com/friends.xml Add member: URI is zhangsan@abc.com, name is zhangsan, other information is best friend.

Step 605, XDMS adds the member indicated by the group member to the group structure indicated by the group URL.

Step 606: The XDMS returns an add group member response (AddGroupMemberResponse) message to the Portal Server, the add group member response message includes the result of adding the group member, and the result of adding the group member includes success and failure.

An example message body of the response to add group members is as follows:

<AddGroupMemberResponse>

<retValue>0</retValue>

</AddGroupMemberResponse>

The above message body shows that adding group members is successful.

Step 607, the Portal Server sends a response message of adding group members to the user terminal.

If multiple members are added at one time, the Portal Server sends a batch add group member request (addGroupMembersRequest) message to the XDMS, and the batch add group member request message includes multiple group member information. An example of the request message for adding group members in batches is as follows:

<AddGroupMembersRequest>

<publicID>mary@abc.com</publicID>

<groupUrl>http://group.abc.com/service/group/user/mary@abc.com/friends.x

ml</groupUrl>

<memberURIList>

<URI>zhangsan@abc.com</URI>

<URI>lili@abc.com</URI>

</memberURIList>

</AddGroupMembersRequest>.

The XDMS sequentially adds members represented by group members to the group structure represented by each group URL. Next, the XDMS returns a response message of adding group members in batches to the Portal Server, the response message of adding group members in batches includes the results of adding group members in batches, and the result of adding group members in batches includes success and failure.

5. Browse group members

As shown in FIG. 7, the process of browsing group members is described below.

Step 701, the user terminal selects a group from the group list, and then sends a browsing group member request message to the Portal Server, and the browsing group member request includes: user ID, group URL.

Step 702, Portal Server sends a browsing group member request (QueryGroupMemberRequest) message to XDMS.

An example message body for a request to browse group members is as follows:

<QueryGroupRequest>

<publicID>mary@abc.com</publicID>

<groupUrl>http://group.abc.com/service/group/user/mary@abc.com/friends.x

ml</groupUrl>

</QueryGroupRequest>.

Step 703, the XDMS retrieves the group information file according to the user ID and the group URL in the request for browsing group members.

Step 704, XDMS retrieves member information from the group information file, constructs a response message, and sends a querygroup member response (QueryGroupMemberResponse) message to PortalServer. The group member browsing response message includes: group member and browsing result flag. The group members include member addresses, member identifiers and information descriptions of members. The browsing result flags include success and failure.

An example message body for browsing group member responses is as follows:

<QueryGroupMemberResponse>

<retValue>0</retValue>

<groupMembers>

<groupMemberInfo>

<uri>zhangsan@abc.com</uri>

<name>zhangsan</name>

<info>best friend</info>

</groupMemberInfo>

<groupMemberInfo>

<uri>lili@abc.com</uri>

<name>lili</name>

<info></info>

</groupMemberInfo>

</groupMembers>

</QueryGroupMemberResponse>.

Step 705, the Portal Server sends a browsing group member response message to the user terminal.

6. Delete group members

As shown in FIG. 8, the process of deleting a group member is described below.

Step 801, the user terminal selects the member to be deleted from the group member list, and then sends a request for deleting a group member to PortalServer, and the request for deleting a group member includes a user ID, a group URL and a URI list of group members to be deleted .

Step 802, the Portal Server sends a confirmation message for deleting group members to the user terminal.

Step 803, if the user terminal confirms to delete the group member, then send a deletion group member confirmation response message to the Portal Server, and execute step 804, otherwise, end the process.

Step 804, Portal Server sends a delete group member request (DeleteGroupMembersRequest) message to XDMS.

An example message body for a group membership request is as follows:

<DeleteGroupMembersRequest>

<publicID>mary@abc.com</publicID>

<groupUrl>http://group.abc.com/service/group/user/mary@abc.com/friends.x

ml</groupUrl>

<memberURIList>

<URI>zhangsan@abc.com</URI>

<URI>lili@abc.com</URI>

</memberURIList>

</DeleteGroupMembersRequest>.

The above example means: delete zhangsan@abc in the group whose URL is http://group.abc.com/service/group/user/mary@abc.com/friends.xml of user mary@abc.com. com and two members of lili@abc.com.

Step 805, the XDMS deletes the member information corresponding to the member identifier of the group to be deleted in the group corresponding to the group identifier.

In step 806, the XDMS returns a delete group member response (DeleteGroupMembersResponse) message to the Portal Server. The delete group member response message includes a delete result flag, and the delete result flag includes success and failure.

An example of the message body of the delete group member response is as follows:

<DeleteGroupMembersResponse>

<retValue>0</retValue>

</DeleteGroupMembersResponse>.

Step 807, the Portal Server sends a delete group member response message to the user terminal. 7. View and modify group properties

As shown in Figure 9, the process of viewing and modifying group attributes is described below.

Step 901, the user terminal selects a group from the group list, and then sends a request message for viewing group attributes to the Portal Server, and the request message for viewing group attributes includes a user ID and a group URL.

Step 902, the Portal Server sends a query group attribute request (QueryGroupAttributeRequest) message to the XDMS.

An example message body of a request to view group attributes is as follows:

<QueryGroupAttributeRequest>

<publicID>mary@abc.com</publicID>

<groupUrl>http://group.abc.com/service/group/user/mary@abc.corn/friends.x

ml</groupUrl>

</QueryGroupAttributeRequest>.

Step 903, the XDMS retrieves the group information file according to the user ID and the group URL in the request message for viewing group attributes.

Step 904, XDMS takes out the group attribute from the group information file, constructs a response message, and sends a query group attribute response (QueryGroupAttributeResponse) message to the PortalServer, so that the group attribute that is inquired is returned to the Portal Server. The attribute response message includes querying group attribute results, group URI, group name, group validity period and creation time, etc.

An example of the message body of the group property response is as follows:

<QueryGroupAttributeResponse>

<retValue>0</retValue>

<groupUri>mary_friends@group.abc.com</groupUri>

<groupTitle>friends</groupTitle>

<duration>365</duration>

<timestamp>20050108153000</timestamp>

</QueryGroupAttributeResponse>.

Step 905, the Portal Server sends a query group attribute response to the user terminal.

Step 906, the user terminal requests to visit the modification group attribute page of the Portal Server.

Step 907, the Portal Server sends the modifying group attribute page to the user terminal, so that the user terminal fills in the group information according to the modifying group attribute page.

Step 908: After the user terminal fills in the group attributes to be modified, it sends a group attribute modification request to the Portal Server. The group attribute modification request message includes the user ID, group URL, group name and group validity period.

Step 909, the Portal Server sends a modify group attribute request (ModifyGroupAttributeRequest) message to the XDMS.

An example message body of a request to modify group attributes is as follows:

<ModifyGroupAttributeResponse>

<publicID>mary@abc.com</publicID>

<groupUrl>http://group.abc.com/service/group/user/mary@abc.com/friends.x

ml</groupUrl>

<groupTitle>friends</groupTitle>

<duration>730</duration>

</ModifyGroupAttributeResponse>.

Step 910, the XDMS modifies the group attribute according to the group attribute modification request.

Step 911, the XDMS returns a modify group attribute response (ModifyGroupAttributeResponse) message to the Portal Server, the modify group attribute response message includes a modify group attribute flag, and the modify group attribute flag includes success and failure.

An example of the message body of the group attribute modification response is as follows:

<ModifyGroupAttributeResponse>

<retValue>0</retValue>

</ModifyGroupAttributeResponse>.

Step 912, the Portal Server sends a modification group attribute response to the user terminal.

8. View and modify group member attributes

As shown in FIG. 10 , the process of viewing and modifying group member attributes is described below.

Step 1001, the user terminal selects a member from the group member list, and then sends a request message to the Portal Server to view the attributes of the group member. The request message for viewing group member attributes includes a user ID, a group URL, and a member ID.

Step 1002, the Portal Server sends a query group member attribute request (QueryGroupMemberAttributeRequest) message to the XDMS.

An example message body of a request to view group member attributes is as follows:

<QueryGroupMemberAttributeRequest>

<publicID>mary@abc.com</publicID>

<groupUrl>http://group.abc.com/service/group/user/mary@abc.com/friends.x

ml</groupUrl>

<memberID>zhangsan@abc.com</memberID>

</QueryGroupMemberAttributeRequest>.

Step 1003, the XDMS retrieves the group information file according to the user ID and the group URL, and obtains group member attribute information from it.

Step 1004, XDMS constructs a response message according to the group member attribute information, and sends a query group member attribute response (QueryGroupMemberAttributeResponse) message to Portal Server, and the group member attribute response message includes checking group member attribute results and group member information .

An example message body of the response to view group member attributes is as follows:

<QueryGroupMemberAttributeResponse>

<retValue>0</retValue>

<groupMemberInfo>

<uri>zhangsan@abc.com</uri>

<name>zhangsan</name>

<info>best friend</info>

</groupMemberInfo>

</QueryGroupMemberAttributeResponse>.

The above example shows that the result of viewing group member attributes is successful, and a group member information is returned.

In step 1005, the Portal Server sends a response message for viewing group member attributes to the user terminal.

Step 1006, the user terminal sends a request for modifying group member attributes to the Portal Server.

Step 1007, the Portal Server sends a page for modifying group member attributes to the user terminal.

Step 1008, the user terminal fills in the member attribute to be modified according to the modification group member attribute page, and then sends a modification group member attribute request with modification content to Portal Server, and the modification group member attribute request includes user identification, group Group URL, member ID, member name, etc.

Step 1009, the Portal Server sends a modify group member attribute request (ModifyGroupMemberAttributeRequest) message to the XDMS.

An example message for a request to modify group member attributes is as follows:

<ModifyGroupMemberAttributeResponse>

<publicID>mary@abc.com</publicID>

<groupUrl>http://group.abc.com/service/group/user/mary@abc.com/friends.x

ml</groupUrl>

<memberID>zhangsan@abc.com</memberID>

<name>zhangsan</name>

<info>old friend</info>

</ModifyGroupMemberAttributeResponse>.

Step 1010, the XDMS modifies the attributes of the group members according to the request for modifying the attributes of the group members.

Step 1011, XDMS returns a modify group member attribute response (ModifyGroupMemberAttributeResponse) message to the Portal Server. The modifying group member attribute response message includes a group member attribute modifying result, and the group member attribute modifying result includes membership and failure.

An example message body for modifying group member attributes is as follows:

<ModifyGroupMemberAttributeResponse>

<retValue>0</retValue>

</ModifyGroupMemberAttributeResponse>

The above example shows that the modification of group member attributes is successful.

Step 1012, the Portal Server sends a modification group member response to the user terminal.

According to the present invention, by adopting the management message defined by the SOAP protocol between the Web Server (Portal Server) and the XDMS, the Portal Server manages the group information in the XDMS through the management message. At the same time, Portal Server provides group management functions to user terminals. Due to the use of Portal Server, PCs can be used as user terminals, which facilitates the management of group information in XDMS.

Although the present invention has been described by the embodiments, those of ordinary skill in the art know that, without departing from the spirit and essence of the present invention, the present invention can have many modifications and changes, and the scope of the present invention is defined by the appended rights Requirements to limit.

Claims (13)

1. the method for a group information management is characterized in that, comprising:

User terminal and portal server Portal Server are mutual, so that Portal Server structure management request message, described management request message is to adopt the definition of Simple Object Access Protocol soap protocol;

Portal Server will manage request message and issue xml document management server XDMS;

XDMS manages group information according to the management request message.

2. the method for group information management according to claim 1, it is characterized in that described management request message comprises to be created group's request message, browse the group list request message, deletes group's request message, adds simple group group membership request message, browses the group member request message, deletes the group member request message, checks/revise the group attribute request message and revise group member attribute request message.

3. the method for group information management according to claim 1 and 2, it is characterized in that described management comprises to be created group, browse group list, deletes group, adds the simple group group membership, browses group member, deletes group member, checks/revise group attribute and revise the group member attribute.

4. the method for group information management according to claim 3 is characterized in that, described establishment group specifically comprises:

User terminal send to be created group's request by Portal Server to XDMS, and described establishments group asks to comprise user ID, group identification and group's term of validity;

XDMS creates group according to creating group's request, according to group name distribution group URL and the URI of group, and group's term of validity and creation-time is set.

5. the method for group information management according to claim 4 is characterized in that, described establishment group also comprises:

XDMS returns to Portal Server and creates group's response message, and described establishment group response message comprises the URL of group, the URI of group and creates the result of group;

Portal Server sends to user terminal and creates group's response message.

6. the method for group information management according to claim 3 is characterized in that, the described group list of browsing specifically comprises:

User terminal sends to XDMS by Portal Server and browses the group list request message, and the described group list request message of browsing comprises user ID;

XDMS inquires about all group informations that this user creates according to the described user ID of browsing in the group list request message;

XDMS sends to user terminal by Portal Server and browses the group list response message, and the described group list response message of browsing comprises and browse group list result and group list that described group list comprises the URL of group, group identification and the URI of group.

7. the method for group information management according to claim 3 is characterized in that, described deletion group specifically comprises:

User terminal sends deletion group request message by Portal Server to XDMS, and described deletion group request message comprises user ID and the URL of group;

Group's structure that the XDMS deletion URL of group represents.

8. the method for group information management according to claim 7, it is characterized in that, described deletion group also comprises: XDMS sends deletion group response message by Portal Server to user terminal, and described deletion group response message comprises deletion group response results.

9. the method for group information management according to claim 3 is characterized in that, described interpolation simple group group membership specifically comprises:

User terminal sends to XDMS by Portal Server and adds the group member request message, and described interpolation group member request message comprises user ID, the URL of group and group member information;

XDMS adds the member of group member information representation in group's structure that the URL of group represents.

10. the method for group information management according to claim 3 is characterized in that, described deletion group member specifically comprises:

User terminal sends the request of deletion group member by Portal Server to XDMS, and the request of described deletion group member comprises user ID, group identification and waits to delete the group member sign;

Group member to be deleted in the group of XDMS deletion group identification correspondence identifies pairing information about firms.

11. the system of a group information management is characterized in that, comprising:

User terminal is used for carrying out alternately with portal server Portal Server, so that the management request message that Portal Server structure sends to xml document management server XDMS;

Portal Server is used for carrying out interactive configurations management request message with user terminal, and will manages request message and issue XDMS, and described management request message is to adopt the soap protocol definition;

XDMS is used for according to the management request message group information being managed.

12. the system of group information management according to claim 11 is characterized in that, described Portal Server specifically comprises:

Receiver module is used to receive the management request of user terminal, and receives the response message of XDMS;

The message constructing module is used for the management request structure management request message that receives according to receiver module;

Sending module is used for the management request message of described message constructing module structure is sent to XDMS, and the response message that described receiver module receives is issued user terminal.

13. the system according to claim 11 or 12 described group information managements is characterized in that, described XDMS specifically comprises:

Receiver module is used to receive the management request message of Portal Server;

Administration module is used for according to the management request message that receiver module receives group information being managed, and according to managing tectonic response message as a result;

Sending module is used for the response message of administration module structure is sent to Portal Server.

Images