WO2009021413A1

WO2009021413A1 - Method and system for joining a group

Info

Publication number: WO2009021413A1
Application number: PCT/CN2008/070588
Authority: WO
Inventors: Jianfeng Lu; Xuena Sun; Wei Li
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-08-15
Filing date: 2008-03-26
Publication date: 2009-02-19
Also published as: CN101369985A

Abstract

A method for inviting to join a group in communication field, particularly relates to a method for joining a group is provided, which mostly includes steps: receiving a request for inviting a member to join a group send by a group management terminal; sending an invite message to the invited new member; receiving response message returned by the invited new member according to the invite message; modifying the status of the new member according to the response message; returning the invite result message to the group management terminal. A method for joining a group actively and a group system also are provided. It realizes the management terminal invites new member to join a group and new member joins a group actively. It can combine to produce more service, rich in experience of member by the function.

Description

Method and system for joining groups

Technical field

The present invention relates to the field of communications, and in particular, to a method and system for joining an XDMS group. Background technique

XML, The Extensible Markup Language (XDMS, XML document management server) is based on the 3GPP IMS (IP Multimedia Subsystem) system architecture and is responsible for managing XML documents (including member personal information documents, group documents, resources). List documents and other resources).

Groups processed in XDMS can be divided into two types according to their life cycle:

1. Short-term group: For example, a group temporarily set up for a conference will die after the conference ends. Such groups will not record the status of members in the document.

2. Long-term group: For example, a classmate created for a class, the group is long-lived, and any status of the member will be updated to the document in time.

The process of managing a terminal to invite members to join and actively joining a group in such a group is not defined in the specification, and there is such a requirement in the business implementation. Summary of the invention

Embodiments of the present invention provide a method and system for joining an XDMS group, implementing an XDMS for members to join, and updating member information in real time.

In order to implement the member joining the XDMS group, the embodiment of the present invention provides a method for inviting to join the group, including the steps of:

Receiving a request sent by the group management terminal to invite a new member to join the group;

Send an invitation message to the invited new member;

Receiving a response message returned by the invited new member according to the invitation message;

Modifying a state of the new member according to the response message; Returning an invitation result message to the group management terminal.

An embodiment of the present invention further provides a method for actively joining a group, which mainly includes the steps of: receiving a request sent by an application member to join a group;

Sending a request to join the group to the group management terminal;

Receiving a response message returned by the group management terminal;

Modifying a status of the application member according to the response message;

The application result message is sent to the application member.

An embodiment of the present invention further provides a system for inviting to join a group, including:

Adding a group requesting module, configured to receive a request sent by the group management terminal to invite a new member to join the group;

An invitation sending module, configured to send an invitation message to the invited new member;

a response sending module, configured to receive a response message returned by the invited new member according to the invitation message; a state modifying module, configured to modify a state of the new member according to the response message; and return an invitation result to the group management terminal Message.

The embodiment of the invention further provides a system for actively joining a group, including:

a request receiving module, configured to receive a request sent by an application member to join a group; and a request sending module, configured to send a request to join the group to the group management terminal;

a response receiving module, configured to receive a response message returned by the group management terminal;

a status modification module, configured to modify a status of the application member according to the response message; and an application result sending module, configured to send a request result message to the application member.

An embodiment of the present invention further provides a group system, including:

a group management terminal, configured to send a request to invite a new member to join the group;

And a group server, configured to invite the new member to join the group or accept the new member to join the group according to the request or the returned response message sent by the group management terminal.

The embodiment of the present invention provides a method for implementing the "management terminal invites members to join the group" and "members actively request to join the group", the group is a long-term existence, any state of the member All of the embodiments of the present invention need to be updated in time to meet the needs. At the same time, with this function, more services can be combined to meet more needs of users. DRAWINGS

1 is a flow chart of a method for inviting members to join a group according to a first embodiment of the present invention; FIG. 2 is a flowchart of a method for a member to actively request to join a group according to a second embodiment of the present invention; Embodiment a group system structure diagram;

4 is a structural diagram of another population group system according to a fourth embodiment of the present invention.

detailed description

In order to make the objects, technical solutions and advantages of the present invention more comprehensible, the embodiments of the present invention will be described in further detail with reference to the accompanying drawings.

The first embodiment of the present invention provides a method for the management terminal to invite members to join the group. In this embodiment, the group server is an XDMS. As shown in FIG. 1, the method includes the following steps:

In step 119, when the group management terminal needs a new member to join the XDMS group, the XDMS sends a request to invite the new member to join the group, such as a Put request of the Xcap protocol, where the request carries the basic information of the invited member. .

The groups mentioned in the embodiments of the present invention generally refer to public groups.

In this step, the group management terminal may invite a new member to join at a time, or may invite multiple new members to join at the same time, and the invitation request also carries basic information of the invited multiple new members.

In step 1200, after receiving the invitation request sent by the group management terminal, the XDMS sends 202 success response signaling to the group management terminal, indicating that the request is being processed.

In this step, the XDMS may join the invited new member when processing the invitation request sent by the group management terminal, but identify the member in the invited state, and the informal member.

In step 103, the XDMS sends an invite message to the invited new member, and the message may be a SIP protocol message, where the message includes group information and management terminal information. At the same time, the message indicates by a special identifier that this is a group invitation message. The special identifier may be an identifier that is customized for a certain field in the invitation message. For example, the SIP signaling message has a "Content-Type" field, and the field may be used to indicate that the message is a group invitation message.

In step 104, after the invited new member receives the invitation message, it sends back 200 response signaling to 0^^, indicating that the invitation message has been received.

In step 1 05, the new member is invited to send a request to the XDMS, such as the Xcap protocol Put request, to indicate whether or not they agree to join the XDMS group.

In step 1 06, the XDMS sends a 200 response to the invited new member, indicating that the message has been received. In step 107, the XDMS modifies the member status in the document as the invited new member wishes. In this step, if the new member is invited to join the group, the new member status is modified to the official group member status.

The status of the members in this step includes: invited status, active joining status, formal group member status, and non-group member status. The server can make its own rules: whether to delete the members that do not agree to join, or to mark the various states mentioned above.

In step 1 08, the XDMS sends the SIP protocol message to the group management terminal by sending a S IP protocol message, the message includes the group information and the invited new member information, and indicates by the special identifier that this is a group invitation confirmation.

In this step, the special identifier may be an identifier customized in a field of the invitation message. For example, the S IP signaling message has a "Cont en t-Type" field, and the field may be used to indicate that the message is an invite message.

In addition, in this step, the invitation result is sent to the group administrator through the S ip/Me s sage message to be a new session, and the previous group management terminal sends a request to the XDMS to invite the new member to join the invitation request, and the group does not matter. Group administrators receive SIP messages from many members. Therefore, in this step, it is necessary to include the group information and the invitee information in the S I P/Mes sage message. Here, the information of the invitee may be information for a specific application. For example, if the group is for the alumni, the information of the invitee may be the common information required to generally join the alumni record.

In step 119, the group management terminal returns a 200 response indicating that the result of the invitation has been received. In addition, in this embodiment, in order to streamline the process, step 104, step 105, and step 106 may also be organized into one step: the invited new member returns 200 or 403 according to his or her will, 200 indicates consent to join, and 403 indicates Do not agree to join. It can be seen from the above process that the group management terminal sends a request for inviting a new member to join the XDMS through the group management terminal, so that the new member joins the XDMS group.

The following is the group management terminal s ip: ownerQexample. com invite member s ip: bobQexample. com force into the group s ip: f ootba 11 team_groupQexample. com signaling example:

TABLE 1. 1 The group management terminal initiates a request for the group join to the XDMS service (Xcap/Put)

PUT

Http:〃xcap.example.com/services/public-group/users/sip:owner@example.com/footballteam.xml/ /public-group/list%5b @uri=%22sip:footballteam— group@example.com %22%5d/entry%5b@uri=%22sip:bob@example.com%22%5d

HTTP/1.1

X-3GPP-Intended-Identity: "sip:owner@example.com"Content-type: application/xcap-el+xml

Content-Length: (...)

<display-name>Bob</display-name>

<info>Defend</info>

</entry>

HTTP/1.1 202 Accepted

Etag: "ereere"

... Content-Length: 0

TABLE 1. 2 XDMS sends an invitation message to the invited new member (S i p/Mes s age )

Note: This signaling indicates that this is by setting Con tent-Type to mes sage/group- i nv i te Group invitation request

TABLE 1.3 is invited to send a new Xcap/Put request to tell XDMS whether or not to agree to join the group.

PUT

Http: / /xcap . ex amp 1 e com/ services /public-g roup/user s / sip: owner @ example . com/f ootb allteam xml/— /pub lie - group/ list %: b@uri = % 22sip:

Bob @example . com%22%5d ^status HTTP/1.1

X - 3GPP - Intended - Ider it ity : " sip : bob@examp le . com"

Content -type: applic: at ion/xcap-att+xml

Content -Length: -..

"active"

HTTP/1.1 200 OK

Et ag: "ereere "

Content-Length: 0

Note: Invited new members can send "active" to indicate consent, and send ' 're ject ' ' to reject

TABLE 1.4 XDMS will invite the result to the group management terminal through the Sip/Message message.

MESSAGE sip: owner @example . com SIP/2 .0

Via: SIP/2.0 /TCP group . example . com; branch=z 9h G4bK776sgdkbb

User-Agent: XDM-serv/OMAl .0

Max- F o wards: 70

From: sip: group . example . com; t ag=98— 86

To: sip: owner @ example . com

Call-ID: asd89asd77cc@l .2.3.4

CSeq: 1 MESSAGE

Content -Type: message/group— invite- notify

Content - Length: -..

<group-invite-not if y>

<group-uri>sip: f ootballteam_gr oup@example . com</group-uri>

<group— invitee > sip: bob @ example com</ grou p-invitee>

<group-ident if ier>/public-grou o/user/ sip owner @ example . com/f ootbal It earn . x ml </ group - i dent i

</group-invite-not if y> Note: This signaling indicates that this is a group invitation confirmation by setting the Content-Type to message/group-invi te_not if y.

The second embodiment of the present invention provides a method for a new member to actively request to join a group. In this embodiment, the group server is an XDMS. As shown in FIG. 2, the method mainly includes the following steps:

In step 201, a new member to join the group sends a request to the XDMS to join the group. (Xcap/Put) , the request carries information about the new member.

In step 202, the XDMS returns 202 a successful response indicating that the request is being processed.

In step 203, the XDMS sends a request for the new member to join the group (S ip/Mes sage) to the group management terminal, where the request includes the group information and the new member information, and the special identifier indicates that the application is an application group. Group request.

Here, the group information and the new member information may be information for a specific application. For example, if the group is for alumni, the group information and the new member information may be common information required for a general alumni to join the alumni.

In step 204, the group management terminal returns a 200 response, indicating that the Mes sage request has been received, and mutating the member status of the new member in the document.

The status of the members in this step includes: invited status, active joining status, formal group member status, and non-group member status. When a member actively applies to join a group, XDMS can change the member to the active join state.

In step 205, the group management terminal sends an Xcap/Put request to tell the XDMS whether to agree to join the group.

In step 206, the XDMS returns a 200 response indicating that the message has been received.

In step 207, the XDMS modifies the member status in the group document according to the request sent by the group management terminal. In this step, if the group management terminal requests to agree to apply for a new member to join the group, the new member status is set to the official group member status.

In step 208, the XDMS informs the applicant through the S i p/Mes sage message that the message contains the group information and the management terminal information, and indicates by the special identifier that this is a confirmation that the group application is added.

In step 209, the new member terminal returns a result that the 200 response identifier has received the invitation.

In addition, in this embodiment, in order to streamline the process, step 204, step 205, and step 206 may also be implemented as a step: The group management terminal returns 200 or 403, 200 indicates that the joining is agreed, and 403 indicates that the joining is not agreed.

Here is the member s ip: bobQexample. com Sip: footballteam_groupS) Example signaling of example.com, where the group management terminal is sip: ownerQexample.com.

TABLE2.2.1 New member sends a request to XDMS to join the group (Xcap/Put)

PUT

Http: / /xcap . example . com/ services /public-gr /users/sip: owner @ example . com/: — ootba _lteam . xml/~ - /public-group/ list%5b@uri = %22 sip:

Ob@example . com%22%5d HTTP/1.1

X-3 GPP—Intended— Identity : " sip : bob@examplt . com "

Content -type: applicat ion/xcap-el+xml

Content -Length: (...)

< entry uri=" sip: bob @ example . com" >

< /ent ry >

HTTP/1.1 202 Accepted

Et ag: "ereere "

Content-Length: 0

TABLE2.2.2 XDMS sends a request for a new member to join the group to the group management terminal

MESSAGE sip: owner @example . com SIP/2.0

Via: SIP/2.0/TCP group . example . com; branch=z 9hG4bK776sg dkse

User-Agent: XDM-serv/OMAl .0

Max- F o wards: 70

From: sip: group . example . com; t ag= 9583

To: sip: owner @ example . com

Call-ID: asd88asd77a@l .2.3.4

CSeq: 1 MESSAGE

Content -Type: mess age /group- oin

Content -Length: -..

<group- oin>

<group-proposer>sip: bob @ example . com</group-propost

<group-uri>sip: f ootballt eam_group@ example . com</gr -uri>

<group-ident if ier>xcap . example . com/ services /publi ^-group/user / sip: owner @exar nple . com/f o otballteam . xml</group-ident if ier>

</group- oin> Note: This signaling indicates that this is a group join request by setting the Content-Type to message/group-join.

TABLE2.2.3 The group management terminal sends an Xcap/Put request to tell whether to agree to the new member joining the group. PUT

Http : / /xcap . example . com/ services /public-g oup/user s / sip: owner @ example . com/f ootb allteam xml/— /public-group/ list%5b@uri = %22 sip:

Bob @example . com%22%5d /@ status HTTP/1.1

Content -type: applicat ion/xcap-att+xml

Content -Length: -..

"active"

HTTP/1.1 200 OK

Et ag: "ereere "

Content-Length: 0

Note: The group management terminal can send "active" to indicate consent, and send ' 'reject' to indicate rejection.

TABLE2.2.4 XDMS will inform the applicant through the Sip/Message message

MESSAGE sip: bob@example . com SIP/2.0

Via: SIP/2.0/TCP group . example . com; branch

User-Agent: XDM-serv/OMAl .0

From: sip: group . example . com; t ag=98786

To: sip: bob @ example . com

Call-ID: asd89asd77cc@l .2.3.4

CSeq: 1 MESSAGE

Content -Type: mess age /group- oin-notify

Content -Length: -..

<group- oin-not if y>

<group-uri>sip: f ootballt eam_group@ example . com</group-uri>

<group-owner>sip: owner @ example . com</group-owner>

<group-ident if ier> /public-group/user/ sip: owner @ example . com/f ootballt earn . xml</group-ident i f ier>

</group-j oin-not if y>

Note: This signaling indicates that this is a group invitation confirmation by setting the Content-Type to message/group_join_not if y

A third embodiment of the present invention provides a group system. As shown in FIG. 3, the method includes: a group management terminal 301, configured to add a group release permission for a new member; Mainly includes: When the group management terminal 301 needs a new member to join, it can send a request to the group server 302, indicating that the right to join the group is released to the invited new member, so that the group server 302 can invite the new one. Members join the group; or, when new members actively request to join In the case of the group, when the group management terminal 301 receives the permission request sent by the group server 302, it sends a message to the group server 302 whether to approve the new member to join the group. The group server 302 is configured to invite the member to join the group or accept the request of the new member to join the group according to the permission of the new member released by the group management terminal 301 to join the group; and also to store the group information, when the new member joins After the group is modified, the status of the new member is the official group member status. In addition, the group server 302 is also responsible for modifying the status of the group members and the new members, for example, changing the member status of the new member who does not agree to join the group or the new member who is not agreed to join the group by the group management terminal 301. Group member status, or deleted according to group server rules.

In addition, in this embodiment, the group management terminal 301 may further include a first invitation module 3011, configured to send, to the invitation receiving module 3021, a request for inviting a new member to join the group, where the request carries the information of the invited member; The group server 302 may further include an invitation receiving module 3021, configured to receive a request sent by the first invitation module 3011 to invite a new member to join the group. And the second invitation module 3022 is configured to send an invitation message to the invited new member, where the message includes the information of the group and the information of the group management terminal, and the special identifier indicates that the message is an invitation message to join the group.

A fourth embodiment of the present invention provides another population group system, as shown in FIG. Compared with the system provided by the third embodiment, the system includes a group server 302 and a group management terminal 301, and the difference is that: in this embodiment, the group server 302 includes a request receiving module 3023 and a permission request module. 3024. The request receiving module 3023 is configured to receive a request for a new member to join the group, where the request carries the information of the applying member. The permission requesting module 3024 is configured to send, to the group management terminal 301, the permission of the new member to join the group. The request includes the group information and the new member information that is applied to join the group, and indicates by the special identifier that the application is a group joining request, and receives a message sent by the group management terminal 301 whether to agree to the new member joining the group. . The group management terminal 301 includes a rights release module 3012 for sending a message to the rights request module 3024 whether to approve the new member to join the group.

In summary, in the embodiment of the present invention, the group management terminal sends an invitation request to the group server, and the group server interacts with the invited new member to determine whether the new member agrees to join the group. The group server modifies the group information according to the wishes of the new member, and realizes that the management terminal invites the new member to join the group; the group server receives the application of the new member, and according to the application and the group management terminal interaction, according to the received group Whether the group management terminal allows new members to join the information, modifies the group, and implements the active invitation of the new member to join the group. With this implementation process, you can combine more business and enrich the experience of members.

A person skilled in the art can understand that all or part of the steps of implementing the foregoing embodiments can be completed by a program instructing related hardware, and the program can be stored in a computer readable storage medium, the storage. Media, such as: R0M/RAM, disk, CD, etc.

The above is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or within the technical scope disclosed by the present invention. Alternatives are intended to be covered by the scope of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

Rights request

A method for inviting a group to join a group, comprising the steps of:

Send an invitation message to the invited new member;

Modifying a state of the new member according to the response message;

Returning an invitation result message to the group management terminal.

The method according to claim 1, wherein the receiving the newly invited member according to the response message returned by the invitation message further includes:

Modify the status of the new member to the invited status.

The method according to claim 1, wherein the response message is that the invited new member agrees to join the group, and the state of the new member is modified to be a formal group member state.

The method according to claim 1, wherein the response message is that the invited new member does not agree to join the group, and the state of the new member is modified to be a non-group member state; or according to the server. The rule deletes the invited new member.

The method according to claim 1, wherein the receiving the group management terminal sends a request to invite a new member to join the group, and the request carries information of the invited new member.

The method according to claim 5, wherein, in the sending an invitation message to the invited new member, the invitation message includes the information of the group and the information of the group management terminal, and The message is indicated by a special identifier as a group invitation message.

The method according to claim 1, wherein the returning the invitation result message to the group management terminal, the invitation result message includes the information of the group and the invited new member Information.

The method according to claim 1, wherein the request for inviting a new member to join the group is a Put request of the Xcap protocol, and the invitation message and the invitation result message are SIP protocol messages.

9. A method for actively joining a group, the method comprising the steps of: receiving a request sent by an application member to join a group;

Sending a request to join the group to the group management terminal;

Receiving a response message returned by the group management terminal;

Modifying a status of the application member according to the response message;

The application result message is sent to the application member.

The method according to claim 9, wherein the step of: receiving the response message returned by the group management terminal, further comprising: modifying the status of the application member to be an active join status.

The method according to claim 9, wherein the response message returned by the group management terminal is a message that agrees that the application member joins the group, and the status of the application member is modified to be a formal group member status. .

The method according to claim 9, wherein the response message returned by the group management terminal is a message disagreeing that the application member joins the group, and modifying the status of the application member to be a non-group member. Status; or delete the application member according to server rules.

The method according to claim 9, wherein the request for joining the group sent to the group management terminal includes the information of the group and the information of the application member, and is indicated by a special identifier. The request is for an application to join a group request.

The method according to claim 9, wherein the application result message includes information of the group and information of the group management terminal, and indicates, by using a special identifier, that the application result message is the A confirmation message for the request to join the group.

The method according to claim 9, wherein the request and response message of the application joining the group is a Put request of the Xcap protocol, and the request for joining the group is a SIP protocol request.

16. A system for inviting to join a group, the method comprising:

Adding a group requesting module, configured to receive a request sent by the group management terminal to invite a new member to join the group; An invitation sending module, configured to send an invitation message to the invited new member;

a response sending module, configured to receive a response message returned by the invited new member according to the invitation message;

a state modifying module, configured to modify a state of the new member according to the response message; and a result message returning module, configured to return an invitation result message to the group management terminal.

The system for inviting a group to join the group according to claim 16, further comprising: an invited state modifying module, configured to receive, in response to the invitation message, a response that the invited new member returns according to the invitation message Before the message, modify the status of the new member to be invited.

The system for inviting a group to join the group according to claim 16, wherein the state modifying module further comprises: a first state modifying submodule, configured to: the response message is that the invited new member agrees to join Group, then modify the status of the new member to the official group member status.

The system for inviting a group to join the group according to claim 16, wherein the state modifying module further comprises: a second state modifying submodule, wherein the response message is that the invited new member does not agree When joining a group, the state of the new member is modified to be a non-group member state; or the invited new member is deleted according to a server rule.

20. A system for actively joining a group, the method comprising:

The system of actively joining a group according to claim 20, further comprising: an active joining state modifying module, configured to modify the application member before the response receiving module receives the response message returned by the group management terminal The status is active join status.

The system of actively joining a group according to claim 20, wherein the state modifying module further comprises: The first state modification submodule, the response message returned by the group management terminal is a message that agrees that the application member joins the group, and the state of the application member is modified to be a formal group member state.

The system of actively joining a group according to claim 20, wherein the state modifying module further comprises:

a second state modification submodule, wherein the response message returned by the group management terminal is a message disagreeing that the application member joins the group, and modifying the status of the application member to be a non-group member state; or according to a server rule The application member is deleted.

24. A group system, comprising:

a group management terminal, configured to send a request for inviting a new member to join the group, or return a response message according to the received request to join the group;

And a group server, configured to invite the new member to join the group or accept the request of the new member to join the group according to the request or the returned response message sent by the group management terminal.

The system according to claim 24, wherein the group management terminal further comprises:

The first invitation module is configured to send a request for inviting the new member to join the group, where the request carries information about the new member.

The system according to claim 24, wherein the group server further comprises:

An invitation receiving module, configured to receive a request sent by the first invitation module to invite the new member to join the group;

a second invitation module, configured to send an invitation message to the new member, where the message includes information about the group and information of the group management terminal, and indicates, by using a special identifier, that the message is added to the group Group of invitation messages.

The system according to claim 24, wherein the group server further comprises: a request receiving module, configured to receive a request sent by the new member to join a group, where the request carries information about the new member;

a permission requesting module, configured to send, to the group management terminal, a permission request of the new member to join the group, where the request includes information about the group and information of the new member, and the special identifier is used Indicates that the request is an application to join the group, and receives a message sent by the group management terminal whether to agree to the new member joining the group.

The system according to claim 27, wherein the group management terminal further comprises:

And a privilege release module, configured to send, according to the privilege request of the group, the new member sent by the privilege requesting module, to the privilege requesting module, whether to agree to the new member joining the group.