CN1968120B - Method and system for group information management - Google Patents
Method and system for group information management Download PDFInfo
- Publication number
- CN1968120B CN1968120B CN200610072648A CN200610072648A CN1968120B CN 1968120 B CN1968120 B CN 1968120B CN 200610072648 A CN200610072648 A CN 200610072648A CN 200610072648 A CN200610072648 A CN 200610072648A CN 1968120 B CN1968120 B CN 1968120B
- Authority
- CN
- China
- Prior art keywords
- group
- xdms
- request message
- portal server
- message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Abstract
The invention relates to a method for managing group information, wherein it comprises that: interacting user terminal with Portable Server, therefore, Portable Server can build manage request message, defined by SOAP protocol; Portable Server sends manage request message to XDMS, which will manages the group information. The invention also provides relative system. With said invention, Portable Server can use manage information to manage the group information in XDMS, and Portable Server can provide group management for user terminal, and since the invention uses PC as user terminal, the group information of XDMS can be managed simply.
Description
Technical field
The present invention relates to a kind of communication technology, relate in particular to a kind of method and system of group information management.
Background technology
At 3GPP (3rd Generation Partnership Project, 3rd Generation Partnership Project) standard and OMA (Open Mobile Alliance, Open Mobile Alliance) in the standard, miscellaneous service engine (PoC, Presence, IM etc.) needs the group information unification of visit to be placed on the XDMS (XML (extend markup language) document management server), manages with the XML document form.The user can edit on mobile phone terminal, group information management.
As shown in Figure 1, in existing technical scheme, mobile phone terminal is mutual with XDMS by XCAP agreement (XML configuration access agreement), group information management.Like this, the user can be at the group information on the management XDMS on the mobile phone terminal.
Yet, because the content more complicated of group information, as, group information generally includes group name, the URI of group (unified resource sign), the term of validity etc., need import a large amount of letters during editor group, but mobile phone key is few, inputting word information is very inconvenient, and the user uses professional experience relatively poor.
Summary of the invention
The method and system that the purpose of this invention is to provide a kind of group information management can be by group information among Portal Server (portal server) the management XDMS.
The invention discloses a kind of method of group information management, 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 SOAP (Simple Object Access Protocol) protocol definition;
Portal Server will manage request message and issue XDMS (xml document management server);
XDMS manages group information according to the management request message.
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 revises group member attribute request message.
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 revises the group member attribute.
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 name 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.
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.
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.
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.
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.
Described interpolation simple group group membership specifically comprises:
User terminal send to add the group member request message by Portal Server to XDMS, interpolation group member request message comprise 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.
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.
The invention also discloses a kind of system of group information management, comprising:
User terminal is used for carrying out alternately with portal server Portal Server, so that the formation management request message that Portal Server structure sends to xml document management server XDMS;
Portal Server is used for obtaining to manage request message alternately 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.
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 according to user terminal;
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.
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.
According to the present invention,, make Portal Server by the group information among this administrative messag management XDMS by between Web Server (Portal Server) and XDMS, adopting the administrative messag of SOAP (Simple Object Access Protocol) protocol definition.Portal Server provides group management function to user terminal simultaneously.Owing to used Portal Server, can adopt PC as user terminal, thereby make things convenient for the group information among the user management XDMS.
Description of drawings
Fig. 1 shows the schematic diagram of the group information management system of prior art;
Fig. 2 shows the schematic diagram of the group information management system of the embodiment of the invention;
Fig. 3 shows the flow chart of the establishment group of the embodiment of the invention;
Fig. 4 shows the flow chart of browsing group list of the embodiment of the invention;
Fig. 5 shows the flow chart of the deletion group of the embodiment of the invention;
Fig. 6 shows the interpolation simple group group membership's of the embodiment of the invention flow chart;
Fig. 7 shows the flow chart of browsing group member of the embodiment of the invention;
Fig. 8 shows the flow chart of the deletion group member of the embodiment of the invention;
Fig. 9 shows the flow chart of checking/revise group attribute of the embodiment of the invention;
Figure 10 shows the flow chart of the modification group member attribute of the embodiment of the invention.
Embodiment
Understand and realization the present invention the existing embodiments of the invention of describing in conjunction with the accompanying drawings for the ease of persons skilled in the art.
As shown in Figure 2, the invention provides a kind of system of group information management, comprising: user terminal is used for carrying out alternately with Portal Server, so that Portal Server structure management request message; PortalServer is used for carrying out mutual with user terminal and structure management request message, and will manages request message and issue XDMS, the definition of described management request message employing soap protocol; XDMS is used for according to the management request message group information being managed.
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.
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.
Basic thought of the present invention is that the various administrative messags that adopt soap protocol to define between Web Server (Portal Server) and XDMS make Portal Server by the group information among this administrative messag management XDMS.Portal Server provides group management function to user terminal simultaneously.Described administrative messag comprises creates group's request message, browse the group list request message, deletion group request message, add simple group group membership request message, browse the group member request message, deletion group member request message, check/revise the group attribute request message, revise group member attribute request message, create group's response message, browse the group list response message, deletion group response message, add simple group group membership response message, browse the group member response message, deletion group member response message, check/revise the group attribute response message, revise group member property response message etc.Particularly, user terminal such as PC is connected to Internet, sign in to Portal Server then, user terminal and Portal Server carry out alternately, make Portal Server obtain management information, the administrative messag that Portal Server defines by the employing soap protocol according to the management information that obtains obtains or is provided with the group information among the XDMS.In order to realize obtaining or be provided with the group information among the XDMS, can be achieved as follows flow process: create group, browse group list, deletion group, add the simple group group membership, browse group member, the deletion group member, check/revises group attribute, modification group member attribute by above-mentioned administrative messag.Each flow process is described respectively with reference to the accompanying drawings.
1, creates group
As shown in Figure 3, the process of creating group is described below.
Step 301, user terminal selecting management and group menu, the establishment group page of request visit Portal Server.
Step 302, Portal Server send to user terminal and create group's page.
Step 303, user fill in group's essential information of creating on group's page, send the establishment group request that has group's essential information to Portal Server then.
Step 304, Portal Server send the group's request (CreateGroupRequest) of creating to XDMS, and described establishment group request message comprises user ID, group identification and group's term of validity;
The message body example of creating group's request is as follows:
<CreateGroupRequest>
<publicID>mary@abc.com</publicID>
<groupTitle>friends</groupTitle>
<duration>365</duration>
</CreateGroupRequest>
Above-mentioned message body shows: a friends by name is created in request, and the term of validity is 365 days a group.
Step 305, XDMS create the group information document according to creating group's request, according to group name distribution group URI and the URL of group (unified resource location), and group's term of validity and creation-time are set.
Step 306, XDMS return to Portal Server and create group's response (CreateGroupResponse) message, so that return to Potal Server and to create the result of group, described establishment group response message comprises the URL of group, the URI of group and creates the result of group.
The message body example of creating group's 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>
Above-mentioned message body shows: create group's success, the URI of group is friends@group.abc.com, and the URL of group is http://group.abc.com/service/group/user/mary@abc.com/friends.xm l.
Step 307, Portal Server send to user terminal and create group's response message, so that show the establishment result of group to the user.
2, browse group list
As shown in Figure 4, the process of browsing group list is described below.
Step 401, user terminal send to Portal Server and browse group list message, and the described group list message of browsing comprises user ID.
Step 402, Portal Server send to XDMS and browse group list request (QueryGroupRequest) message.
The message body example of browsing the group list request is as follows:
<QueryGroupRequest>
<publicID>mary@abc.com</publicID>
</QueryGroupRequest>
Above-mentioned message body shows: browse the group information that user ID is mary@abc.com.
Step 403, XDMS inquire about all group information documents that this user creates according to the user ID of browsing in the group list request.
Step 404, XDMS are according to the group information structure response message that inquires, browse group list response (QueryGroupResponse) message to Portal Server transmission, so that return the group list that inquires, the described group list response message of browsing comprises and browses result of group and group list that described group list comprises the URL of group, group name and the URI of group.
The message body example of browsing the 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>
Above-mentioned message body shows: browse success, the group information that obtains is, the URL of group is http://group.abc.com/service/group/user/mary@abc.com/friends.xm l, and group name is friends, and the URI of group is mary_friends@group.abc.com.
Step 405, Portal Server send to user terminal and browse group list message, so that user terminal is showed user's group list.
3, deletion group
The process of deletion group is described below as shown in Figure 5.
Step 501, user terminal are selected a group from group list, send deletion group request message to Portal Server then, and described deletion group request message comprises user ID and the URL of group.
Step 502, Portal Server send deletion group to user terminal and confirm request message, so that require user terminal to confirm whether will delete this group.
Step 503, user terminal send deletion group to Portal Server and confirm response message, confirm to delete this group with the expression user.
Step 504, Portal Server send deletion group request (DeleteGroupRequest) message to XDMS.
The body example of deletion 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>
Above-mentioned message body shows: request deletion user ID is that the URL of group of mary@abc.com is a group.abc.com/service/group/user/mary@abc.com/friends.xm l group.
Group's structure that step 505, XDMS represent according to the URL of the group deletion URL of group in the deletion group request message.
After group's structure that step 506, the XDMS deletion URL of group represents, return deletion group response (DeleteGroupResponse) message to Portal Server, described deletion group response message comprises deletion group response results.
The message body example of deletion group response message is as follows:
<DeleteGroupResponse>
<retValue>0</retValue>
</DeleteGroupResponse>
Above-mentioned message body shows: delete successfully.
Step 507, Portal Server send the response of deletion group to user terminal, so that to the user terminal prompting deletion result of group.
4, add single group member
As shown in Figure 6, the process of adding single group member is described below.
Step 601, user terminal are selected a group from group list, send to Portal Server then and add the group member request message.
Step 602, Portal Server send to user terminal and add member's page message, so that user terminal is filled in group member information according to adding member's page.
Step 603, user terminal are imported group member information according to adding member's page, and send interpolation group member request message to Portal Server, and described interpolation group member request message comprises user ID, the URL of group and group member information.
Step 604, Portal Server send to XDMS and add group member request (AddGroupMemberRequest) message.
The message body example of adding group member 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>
Last example shows: in user ID is that the user's of mary@abc.com the URL of group is that to add member: URI in the group of http://group.abc.com/service/group/user/mary@abc.com/friends.xm l be zhangsan@abc.com, name is called zhangsan, and out of Memory is best friend.
Step 605, XDMS add the member that group member is represented in group's structure that the URL of group represents.
Step 606, XDMS return to Portal Server and add group member response (AddGroupMemberResponse) message, described interpolation group member response message comprises interpolation group member result, and described interpolation group member result comprises success and failure.
The message body example of adding the group member response is as follows:
<AddGroupMemberResponse>
<retValue>0</retValue>
</AddGroupMemberResponse>
Above-mentioned message body shows: add the group member success.
Step 607, Portal Server send to user terminal and add the group member response message.
If once add a plurality of members, then Portal Server sends to XDMS and adds group member request (addGroupMembersRequest) message in batches, and described batch adds the group member request message and comprises a plurality of group member information.Described batch interpolation group member request message example 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>。
XDMS adds the member that group member is represented successively in group's structure that the URL of each group represents.Then, XDMS returns to Portal Server and adds the group member response message in batches, and described batch adds the group member response message and comprises that batch adds the group member result, and described batch adds the group member result and comprises success and failure.
5, browse group member
As shown in Figure 7, the process of browsing group member is described below.
Step 701, user terminal are selected a group from group list, send to Portal Server then and browse the group member request message, describedly browse the group member request and comprise: user ID, the URL. of group
The message body example of browsing the group member request 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, XDMS are according to user ID and the URL of the group retrieval group message file browsed in the group member request.
Step 704, XDMS take out information about firms from the group information file, the structure response message, send to PortalServer and to browse group member response (QueryGroupMemberResponse) message, the described group member response message of browsing comprises: group member and browse sign as a result.Described group member comprises member address, member's sign and member's information description.Describedly browse as a result that sign comprises success and failure.
The message body example of browsing the group member response 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, Portal Server send to user terminal and browse the group member response message.
6, deletion group member
The process of deletion group member is described below as shown in Figure 8.
Step 801, the user terminal member that selection will be deleted from the group member tabulation send the request of deletion group member to PortalServer then, and the request of described deletion group member comprises user ID, the URL of group and waits to delete group member URI tabulation.
Step 802, Portal Server send deletion group member acknowledge message to user terminal.
Step 803, if user terminal is confirmed this group member of deletion, then send the deletion group member and confirm response message to Portal Server, execution in step 804, otherwise, ending said process.
Step 804, Portal Server send deletion group member request (DeleteGroupMembersRequest) message to XDMS.
The message body example of group member 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>。
Last example expression: the URL of group of deletion user mary@abc.com is zhangsan@abc.com in the group of http://group.abc.com/service/group/user/mary@abc.com/friends.xm l and two members of lili@abc.com.
Group member to be deleted in the group of step 805, XDMS deletion group identification correspondence identifies pairing information about firms.
Step 806, XDMS return deletion group member response (DeleteGroupMembersResponse) message to Portal Server.Deletion group member response message comprises deletion sign as a result, and described deletion sign as a result comprises success and failure.
The message body example of deletion group member response is as follows:
<DeleteGroupMembersResponse>
<retValue>0</retValue>
</DeleteGroupMembersResponse>。
Step 807, Portal Server send deletion group member response message to user terminal.7, check, revise group attribute
As shown in Figure 9, the process of checking, revise group attribute is described below.
Step 901, user terminal are selected a group from group list, send to Portal Server then and check the group attribute request message, and the described group attribute request message of checking comprises user ID and the URL of group.
Step 902, Portal Server send to XDMS and check group attribute request (QueryGroupAttributeRequest) message.
The message body example of checking the group attribute request 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, XDMS are according to user ID and the URL of the group retrieval group message file checked in the group attribute request message.
Step 904, XDMS take out group attribute from the group information file, the structure response message, check group attribute response (QueryGroupAttributeResponse) message to the PortalServer transmission, so that return the group attribute that inquires, describedly check that the group attribute response message comprises and check group attribute result, the URI of group, group name, group's term of validity and creation-time etc. to Portal Server.
The message body example of checking the group attribute 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, Portal Server send to user terminal and check the group attribute response.
The modification group attribute page of step 906, user terminal requests visit Portal Server.
Step 907, Portal Server send to user terminal and revise the group attribute page, so that user terminal is filled in group information according to revising the group attribute page.
After step 908, user terminal are filled in group attribute to be revised, send the request of modification group attribute to Portal Server, described modification group attribute request message comprises user ID, the URL of group, group name and group's term of validity.
Step 909, Portal Server send to XDMS and revise group attribute request (ModifyGroupAttributeRequest) message.
The message body example of revising the group attribute request 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, XDMS revise group attribute according to revising the group attribute request.
Step 911, XDMS return to Portal Server and revise group attribute response (ModifyGroupAttributeResponse) message, described modification group attribute response message comprises revises the group attribute sign, and described modification group attribute sign comprises success and failure.
The message body example of revising the group attribute response is as follows:
<ModifyGroupAttibuteResponse>
<retValue>0</retValue>
</ModifyGroupAttibuteResponse>。
Step 912, Portal Server send to user terminal and revise the group attribute response.
8, check, revise the group member attribute
As shown in figure 10, the process of checking, revise the group member attribute is described below.
Step 1001, user terminal are selected a member from the group member tabulation, then send to Portal Server and check group member attribute request message.The described group member attribute request message of checking comprises user ID, the URL of group, member's sign.
Step 1002, Portal Server send to XDMS and check group member attribute request (QueryGroupMemberAttributeRequest) message.
The message body example of checking the group member attribute request 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, XDMS therefrom obtain group member group attribute information according to user ID, the URL of group retrieval group message file.
Step 1004, XDMS are according to group member attribute information structure response message, check group member property response (QueryGroupMemberAttributeResponse) message to Portal Server transmission, the described group member property response message of checking comprises group member attribute result and the group member information of checking.
The message body example of checking the group member property response is as follows:
<QueryGroupMemberAttributeResponse>
<retValue>0</retValue>
<groupMemberInfo>
<uri>zhangsan@abc.com</uri>
<name>zhangsan</name>
<info>best?friend</info>
</groupMemberInfo>
</QueryGroupMemberAttributeResponse>。
Above-mentioned example shows, checks that group member attribute result is successfully, returns a group member information.
Step 1005, Portal Server send to user terminal and check group member property response message.
Step 1006, user terminal send to Portal Server and revise the group member attribute request.
Step 1007, Portal Server send to user terminal and revise the group member attribute page.
Step 1008, user terminal are filled in member property to be revised according to revising the group member attribute page, have the modification group member attribute request of revising content to Portal Server transmission then, described modification group member attribute request comprises user ID, the URL of group, member's sign, member Name etc.
Step 1009, Portal Server send to XDMS and revise group member attribute request (ModifyGroupMemberAttributeRequest) message.
The message examples of revising the group member attribute request 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, XDMS revise the group member attribute according to revising the group member attribute request.
Step 1011, XDMS return to Portal Server and revise group member property response (ModifyGroupMemberAttributeResponse) message.Described modification group member property response message comprises revises group member attribute result, and described modification group member attribute result comprises member and failure.
The message body example of revising the group member attribute is as follows:
<ModifyGroupMemberAttibuteResponse>
<retValue>0</retValue>
</ModifyGroupMemberAttibuteResponse>
Above-mentioned way of example shows is revised the success of group member attribute.
Step 1012, Portal Server send to user terminal and revise the group member response.
According to the present invention,, make Portal Server by the group information among this administrative messag management XDMS by between Web Server (Portal Server) and XDMS, adopting the administrative messag of soap protocol definition.Portal Server provides group management function to user terminal simultaneously.Owing to used Portal Server, can adopt PC as user terminal, thereby make things convenient for the group information among the management XDMS.
Though described the present invention by embodiment, those of ordinary skills know, without departing from the spirit and substance in the present invention, just can make the present invention that many distortion and variation are arranged, and scope of the present invention is limited to the appended claims.
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.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610072648A CN1968120B (en) | 2006-04-07 | 2006-04-07 | Method and system for group information management |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610072648A CN1968120B (en) | 2006-04-07 | 2006-04-07 | Method and system for group information management |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1968120A CN1968120A (en) | 2007-05-23 |
| CN1968120B true CN1968120B (en) | 2010-05-12 |
Family
ID=38076689
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200610072648A Expired - Fee Related CN1968120B (en) | 2006-04-07 | 2006-04-07 | Method and system for group information management |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1968120B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101163117B (en) * | 2007-11-30 | 2010-04-14 | 腾讯科技（深圳）有限公司 | Packet management method, packet resource sharing method and instant communication equipment |
| CN102196367B (en) * | 2010-03-05 | 2014-11-05 | 华为技术有限公司 | PPT service processing method, and device and system thereof |
| CN102541964A (en) * | 2010-12-31 | 2012-07-04 | 中国移动通信集团浙江有限公司 | User information management method and system applicable to electronic book reading |
| CN108712320B (en) * | 2018-04-23 | 2021-02-05 | 天津字节跳动科技有限公司 | Message pushing method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2003003779A1 (en) * | 2001-06-29 | 2003-01-09 | Motorola Inc | Group application for group formation and management |
| CN1438581A (en) * | 2002-02-11 | 2003-08-27 | 游本华 | Group exchanging application platform and using method |
| CN1617507A (en) * | 2003-11-12 | 2005-05-18 | 鸿富锦精密工业（深圳）有限公司 | Managing system and method for user authority |
| WO2005120112A1 (en) * | 2004-05-26 | 2005-12-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Servers and methods for controlling group management |
-
2006
- 2006-04-07 CN CN200610072648A patent/CN1968120B/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2003003779A1 (en) * | 2001-06-29 | 2003-01-09 | Motorola Inc | Group application for group formation and management |
| CN1438581A (en) * | 2002-02-11 | 2003-08-27 | 游本华 | Group exchanging application platform and using method |
| CN1617507A (en) * | 2003-11-12 | 2005-05-18 | 鸿富锦精密工业（深圳）有限公司 | Managing system and method for user authority |
| WO2005120112A1 (en) * | 2004-05-26 | 2005-12-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Servers and methods for controlling group management |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1968120A (en) | 2007-05-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1703701B (en) | Apparatus for managing a collection of portlets in a portal server | |
| TW525393B (en) | System and method for collaborative multi-device web browsing | |
| CN102171690B (en) | System and method for implementing personalization and mapping in a network-based address book | |
| CN101277472B (en) | Method, equipment and system of synchronization of blog contents | |
| CN101557409B (en) | Method and device for syncretic management of address book information | |
| JP5601843B2 (en) | Community widget providing method and apparatus | |
| CN101651685A (en) | Methods and systems for mapping subscription filters to advertisement applications | |
| CN103119911A (en) | System and method for synchronizing the profile of a user in social networks and the user's personal contact card (PCC) | |
| CN102576361A (en) | System and method for aggregating multiple contact information sources in a network-based address book system | |
| CN101682648A (en) | Managing entity data in case of multiple entity identities | |
| CN102056106A (en) | Method and system for updating address lists in real time | |
| CN1968120B (en) | Method and system for group information management | |
| US9237206B2 (en) | Method and apparatus for updating personal information in communication system | |
| US20080189357A1 (en) | Community journaling using mobile devices | |
| CN102469042A (en) | Method and system for transmitting and obtaining output messages of chats and conversations | |
| CN101778122A (en) | Method, device and system for implementing message service | |
| CN101778056A (en) | Processing method and system for meeting history record fusing message business and | |
| US20130091287A1 (en) | System for contact subscription invitations in a cross-domain converged address book system | |
| KR20160001750A (en) | Management system for mobile name card web-based and its method | |
| CN101179550B (en) | Personal homepage implementing method and system | |
| CN101202953B (en) | Method and system of shortcut reversion | |
| CN104509028B (en) | The method and device of personal information is updated in a communications system | |
| CN102469041A (en) | Method and system of starting chat session and obtaining conversation list | |
| KR20010092982A (en) | Video electronic-mail service method, and system for the same | |
| CN101388861A (en) | Management system for mutual assistance behavior between terminals, and method thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100512 Termination date: 20130407 |