CN100407818C - A method for selecting session members when a PoC group initiates a session - Google Patents

Abstract

The present invention provides a method for selecting session members in PoC cluster sessions, which comprises the following steps: a, user data is set; b, a user originates a PoC cluster session; c, if the user has the authority of selecting session members, step d is executed; d, the session members are selected according to a predefined member list; e, a call success response is returned to the user. The present invention can satisfy user's requirements, provide convenience for users, enhance user experience, and solve the problem that the invitation of the members during a session can not be originated when the number of cluster people is larger than the defined maximum number of session people. The present invention is compatible with the existing scheme and meets all requirements of the existing scheme.

Description

A method for selecting session members when a PoC group initiates a session

technical field

The invention belongs to the field of cluster communication based on a cellular network, and in particular relates to a method for selecting session members when a PoC (Push-to-talk over Cellular, "Push-to-talk over Cellular") group initiates a session.

Background technique

PoC is the "push to talk" service based on the cellular network, also known as "Push to talk over wireless", which is a half-duplex voice service that allows users to communicate immediately through specific buttons.

PoC supports multi-party calls, and users can make multi-party calls through temporary groups, fixed groups, chat groups, etc.

The data of the PoC group is stored on the PoC XDMS (XML Document Management Server, XML document management server), and the user can send related requests through the terminal (XDMC, XMLDocument Management Client, XML document management client) for group management. It will be sent to PoC XDMS after being authenticated by AP (Aggregation Proxy) (determining whether the user has the corresponding management authority). Of course, if the user Portal provides related group management functions, the user can directly send related requests to PoCXDMS through the Portal for group management.

In the "OMA-TS-PoC_XDM-V1_0-20050317-C" specification standard of PoC version 1.0, an attribute is provided for groups: <invite-members>. When the <invite-members> attribute is set to:

①True: when the session of the group is initiated, other members of the group will be invited;

②False: When the session of this group is initiated, other members of the group will not be invited.

This attribute is operable for the user, that is, the user can set whether to invite their group members when initiating a group session according to their needs. Of course, for a fixed group, it is generally set to invite all members of the group when the session is initiated.

Secondly, there are two elements in the child node <rule> of the group rule <ruleset>: <conditions> and <actions>. Among them, <conditions> is used to indicate the user ID with the corresponding <actions> authority; and <actions> includes a boolean element <allow-initiate-conference>, which means the corresponding <conditions> when it is true Users identified in have permission to initiate group conversations.

The corresponding processing flow is shown in Figure 1: first check whether the user has <allow-initiate-conference> permission, if not, reject the user to initiate a call, if yes, continue to check whether the value of <invite-members> is true; when <invite-members> -members> When the value is true, all members of the group will be invited to join the session, if it is false, no user will be invited to join the session.

However, this solution has the following drawbacks:

(1) For the user, it is not only desired to invite or not invite all members of the group, but may request to invite some members to participate, and in this case, the existing technology cannot meet the needs of the user.

(2) In addition, the user may not only want to invite group members to participate in the session, but sometimes also wants to invite other people to participate in the session, and the user can only invite after initiating a fixed group session, the user's pre-invitation requirements Can't be satisfied.

(3) In order to reduce the system load and other reasons, the operator limits the maximum number of people in a session of a fixed group. The purpose of this limit is to prevent users from having too many participants per session. Therefore, the following attribute is added to the session: <max-participant-count> (the maximum number of participants in the session). Obviously, if in practice, the number of group members of the user is greater than the value of <max-participant-count>, serious problems will occur: when the user sets <invite-members> to true, since the number of group members is larger than the session If the maximum number of participants is not specified, the server will reject the request to initiate a session; that is, the user cannot initiate a fixed group session. This obviously degrades the user experience.

In the "OMA-ERELD_POC-V1_0-20050329-C" standard of the PoC version 1.0, a session type is also defined: an Ad-hoc session, that is, a temporary group session. It allows users to temporarily set up a list of invitees and invite them to a session. Obviously, users can flexibly set the list of invitees according to their needs, which is much more flexible than fixed groups in this regard.

However, this solution still has shortcomings, such as:

(1) However, the temporary group requires setting every time, obviously this is a cumbersome process for the user, and it is obviously not as convenient as the fixed group in this respect.

(2) Users cannot set any attributes related to fixed group members for temporary group members, such as whether they can invite other people to participate in the session, whether they can be anonymous, etc. In this regard, it is obviously not as powerful as the fixed group function.

Contents of the invention

The technical problem to be solved by the present invention is to overcome the deficiencies in the above-mentioned prior art, provide a method for selecting session members when a PoC group initiates a session, support users to flexibly invite members to participate in group sessions, and enable users to initiate group sessions During the session, it is convenient to invite some required members to join the session.

The present invention provides a method for selecting session members when a PoC group initiates a session, comprising the following steps:

a. Set user data;

b. Receive the PoC group session request initiated by the user;

c. If the user has permission to select session members, select session members according to a predefined list of members; otherwise

d. The PoC server checks that the user has the authority to initiate a group session and invites all members of the group to join the session, then invites all members of the group to join the session;

e. Return a call success response to the user.

Further, said step a further includes:

h1. Request to add a user with the permission to select session members, and set the permission;

h2. Request to set the judgment condition of whether to select according to the predefined member list when initiating a PoC group session; and

h3. Request to set a list of members to be selected when initiating a PoC group session.

Further, the step h1 further includes:

h11. Send an HTTP request on the PoC XML document management client, and add a user with the authority to select session members to the PoC group;

h12. The aggregation agent checks whether the user who sends the request has the corresponding authority, and if so, forwards the request to the PoC XML document management server;

After the h13.PoC XML document management server receives the request, it has the authority to select session members for adding user settings;

h14. After the processing of the PoC XML document management server is completed, a successful response is returned to the aggregation agent; and

h15. The aggregation agent forwards a successful response to the PoC XML document management client.

Further, the step h2 further includes:

h21. Send an HTTP request on the PoC XML document management client, and request to set the judging condition for selecting by a predefined member list when initiating a PoC group session;

h22. The aggregation agent checks whether the user who sends the request has the corresponding authority, and if so, forwards the request to the PoC XML document management server;

After the h23.PoC XML document management server receives the request, it is set to select by a predefined list of members when initiating a PoC group session;

h24. After the processing of the PoC XML document management server is completed, a successful response is returned to the aggregation agent; and

h25. The aggregation agent forwards a successful response to the PoC XML document management client.

Further, the step h3 further includes:

h31. The user with the authority to select session members sends an HTTP request on the PoC XML document management client, requesting to set the list of members to be selected for initiating a group session;

h32. The aggregation agent checks whether the user who sends the request has the corresponding authority, and if so, forwards the request to the PoC XML document management server;

After h33. the PoC XML document management server receives the request, it sets the list of members to be selected when initiating the group session;

h34. After the processing of the PoC XML document management server is completed, a successful response is returned to the aggregation agent; and

h35. The aggregation agent forwards a successful response to the PoC XML document management client.

Further, the step b further includes:

b1. The user initiates a PoC group session request to the PoC server, and the request includes a group uniform resource identifier;

b2. the PoC server sends a request to the PoC XML document management server to request data corresponding to the group uniform resource identifier according to the requested group uniform resource identifier; and

b3. The PoC XML document management server returns the data of the group according to the request.

Further, if the PoC server checks that the user does not have the right to select session members in the step c, then:

The PoC server checks that the user does not have the authority to initiate a group session, and then refuses the user to initiate a group session; and

If the PoC server checks that all members of the group are not invited to join the session, then no member is invited to join the session.

Further, after step b and before c, further steps are included:

f. Check whether there is the identification of the user and the added member list required to be selected.

Further, if there is no identification of the user and the added member list required to be invited, no member is invited to join the session.

Because the present invention realizes the method for selecting session members when a PoC group initiates a session, the call mechanism of the PoC group has been expanded to a large extent, and the flexibility is stronger, and at the same time, it is not necessary to perform data management based on the above-mentioned scheme at the server end. Complex, so the program is feasible. If this scheme is applied, the following beneficial effects will be brought about:

(1) Meet user needs, facilitate user use, and improve user experience: Due to the method of selecting sessions, users can invite the users they need to invite according to their needs; it is also very convenient to use, and has the advantages of fixed groups , It also has the advantages of temporary groups; it can largely meet the requirements of users in different situations and improve the user experience.

(2) Solved the problem that members cannot be invited when initiating a session because the number of people in the group is greater than the maximum number of sessions stipulated by the system. Because the user can add some members to the user list, and ensure that the number of them is not greater than the maximum number of conversations stipulated by the system, so that the user can initiate group conversations more conveniently.

(3) The present invention is compatible with existing solutions, and can realize all requirements of existing solutions. For example, when the PoC server checks that the user does not have the right to select session members, it will proceed according to the existing scheme; and when the PoC server checks that the PoC group session is not invited according to the predefined member list, it will continue Check to see if all members of the group are invited to join the session, and proceed with the existing scheme.

Description of drawings

Fig. 1 is the flowchart of the method for inviting members when an existing PoC group session is initiated;

Fig. 2 is a flow chart of data preparation in the present invention;

Fig. 3 is a flowchart of user call management in the present invention;

FIG. 4 is a flow chart for processing normal and abnormal situations in FIG. 3 .

Detailed ways

In the "OMA-TS-PoC_XDM-V1_0-20050317-C" specification standard of the PoC version 1.0, the basic structure of the PoC group is defined. In order to complete the functions described in the present invention, the following content is added to the structure of the PoC group:

(1) Add a sub-element under the group root element: <pre-invite-listset>. This sub-element is of the [COMMONPOL] type, including zero or more <pre-invite-list> nodes, and <pre-invite-list> nodes include <createlistuseridentity> and <userlist> nodes. The value of <createlistuseridentity> is used to identify the identity of the creator of the list; while <userlist> contains zero or more elements, each element is used to identify the identity of the invitee's <entry> sub-element or used to identify the reference The <external> element for the list of invitees.

(2) Add a sub-element under the group root element: <pre-inviteuser>. Its type is boolean: true or false. When it is true, it means that the members requested by the user will be invited when the session is initiated; and when false, it means that the members requested by the user will not be invited when the session is initiated.

(3) Add a new element <pre-invite> in the child element <actions> of the <rule> element, the type is Boolean, which is used to indicate which users have the right to invite members when this fixed group initiates a session. When its value is true, it means that it has this permission. At this time, the user can add the members he wants to invite in the child element <userlist> of the <pre-invite-list> element, and can flexibly initiate a session in a fixed group Invite the required members; and when its value is false, it indicates that there is no such permission. It should be noted that users with this permission will also have the permission to initiate fixed group conversations.

Please refer to shown in Fig. 2, the data preparation process of selecting session members when the present invention realizes that PoC group initiates session comprises the following steps:

Step 1: The group creator or other authorized user sends an HTTP request on the terminal (XDMC) to add a user with pre-invite authorization to a certain group. For example, it is requested that user A and user B have the pre-invite right to select session members.

Step 2: AP checks whether the user who sent the request has the corresponding authority, and if so, forwards the request to PoC XDMS.

Step 3: After PoC XDMS receives the corresponding request, it adds a <rule> node to the data of the specified group, and selects the sub-element <pre-invite> of <actions> to be true, and in the <identity of the <conditions> node >Increase the member ID required to be able to select session members in the sub-element. For example, if two members in the group (user A and user B) have this permission, the expression is as follows:

<cr:ruleset>

...

<cr:rule id="a10c">

<cr:condition>

<identity>UserA@XDMSServer.com</identity>

<identity>UserB@XDMSServer.com</identity>

</cr:condition>

<cr:actions>

<pre-invite>true</pre-invite>

</cr:actions>

</cr:rule>

<cr:ruleset>

Step 4: After the PoC XDMS processing is completed, return a success response to the AP.

Step 5: AP forwards the success response to the terminal (XDMC).

Step 6: The group creator or other authorized user sends an HTTP request on the terminal (XDMC), requesting to set the judgment condition of whether to select according to the predefined member list when initiating a PoC group session, that is, whether to set < pre-inviteuser> is true.

Step 7: AP checks whether the user who sent the request has the corresponding authority, and if so, forwards the request to PoC XDMS.

Step 8: After PoC XDMS receives the corresponding request, set the value of <pre-inviteuser> to true. At this time, no matter whether <invite-members> is true or not, all members of the group will not be automatically invited to join the session.

Step 9: After the PoC XDMS processing is completed, a success response is returned to the AP.

Step 10: AP forwards the success response to the terminal (XDMC).

Step 11: A user with the right to select session members (pre-invite) sends an HTTP request on the terminal (XDMC), requesting to set a list of members to be invited to initiate a fixed group session, for example: user B, user C, user D, User E, user F, user G, user H.

Step 12: AP checks whether the user who sent the request has the pre-invite authority, and if so, forwards the request to PoC XDMS.

Step 13: After PoC XDMS receives the corresponding request, it will add a new node <pre-invite-list> in <pre-invite-listset>, set <createlistuseridentity> as the requesting user identity, and it will be in <userlist> Add the list of members you want to invite. For example, if user A sends the request, and the list of members to be invited to initiate a fixed group session is user B, user C, user D, user E, user F, user G, and user H, the corresponding data is expressed as follows:

<pre-invite-listset>

...

<pre-invite-list>

<createlistuseridentity>UserA@XDMSServer.com</createlistuseridentity>

<userlist>

<entry>UserB@XDMSServer.com</entry>

<entry>UserC@XDMSServer.com</entry>

<entry>UserD@XDMSServer.com</entry>

<entry>UserE@XDMSServer.com</entry>

<entry>UserF@XDMSServer.com</entry>

<entry>UserG@XDMSServer.com</entry>

<entry>UserH@XDMSServer.com</entry>

</userlist>

</pre-invite-list>

<pre-invite-listset>

Step 14: After the PoC XDMS processing is completed, return a success response to the AP.

Step 15: AP forwards the success response to the terminal (XDMC).

Please refer to shown in Fig. 3, after data preparation is finished, the user call management process of the present invention comprises the following steps:

Step S1: The user initiates a PoC group session request to the PoC Server, and the request includes the group Uniform Resource Identifier (URI).

Step S2: The PoC Server will send a request to the PoC XDMS to request the data of the group URI according to the requested group URI.

Step S3: PoC XDMS will return the data of the corresponding group according to the request of PoC Server.

Step S4, Step S5, Step S6: PoC Server can check whether the user has the pre-invite authority according to the data of the group, whether the value of <pre-inviteuser> is true, whether there is a node <pre-invite-list> is the user's. If the above checks are all passed, go to step S7. The normal and abnormal processing procedures of step S4, step S5 and step S6 are shown in Figure 4 and its description in detail.

Step S7: The server invites members according to the list in <userlist>, and when a member returns a response of accepting the session, it means that the invitation is successful.

Step S8: The server returns a call success response to the user.

The process shown in Figure 4 is as follows:

Process (1): When a user initiates a group call, the PoC server will first check whether the user has <pre-invite> permission. If there is, it will continue to check the <pre-inviteuser> value and enter "process (2)". Otherwise, the original design process will be followed: first check whether the user has <allow-initiate-conference> permission, if not, reject the user to initiate a call, if yes, continue to check whether the value of <invite-members> is true; when <invite- members> If the value is true, all members of the group will be invited to join the session, if it is false, no member will be invited to join the session;

Process (2): The server continues to check whether the value of <pre-inviteuser> is true. When it is true, the server continues to check whether the node <pre-invite-list> is the user, and enters "process (3)". Otherwise, the server checks whether the value of <invite-members> is true: when the value of <invite-members> is true, all members of the group will be invited to join the session, and if it is false, no member will be invited to join the session;

Process (3): The server continues to check whether the node <pre-invite-list> is the user. If sometimes, the members listed in <userlist> will be invited; otherwise, the server will not invite any members to join the session.

Claims (9)

1. method of selecting session members when realizing PoC group initiation session may further comprise the steps:

A., user data is set;

B. receive the request of Client-initiated PoC cluster conversation;

If c. described user has the authority of selecting session members, then according to the predefined member selection session members of tabulating; Otherwise

The d.PoC server checks that described user has the authority of initiating cluster conversation and is that all members of invite group add session that then all members of invite group add session;

E. return the response of access success and give described user.

2. method according to claim 1 is characterized in that: described step a further comprises:

H1. the user with selection session members authority is added in request, and described authority is set;

H2. request is provided with the Rule of judgment of whether selecting by predefined member's tabulation when initiating the PoC cluster conversation; And

H3. request is provided with member's tabulation to be selected when initiating the PoC cluster conversation.

3. method according to claim 2 is characterized in that, described step h1 further comprises:

H11. on PoC XML document administrative client, send the HTTP request, PoC group is added user with selection session members authority;

H12. whether the Aggregation Proxy inspection user that sends described request possesses corresponding authority, if any then passing on described request to PoC XML document management server;

After h13.PoC XML document management server receives described request, the authority with selection session members is set to adding the user;

After h14.PoC XML document management servers process is finished, return success and respond described Aggregation Proxy; And

H15. described Aggregation Proxy is transmitted success response to described PoC XML document administrative client.

4. method according to claim 2 is characterized in that, described step h2 further comprises:

H21. send the HTTP request on PoC XML document administrative client, request is arranged on the Rule of judgment of selecting by predefined member's tabulation when initiating the PoC cluster conversation;

H22. whether the Aggregation Proxy inspection user that sends described request possesses corresponding authority, if any then passing on described request to PoC XML document management server;

After h23.PoC XML document management server receives described request, be arranged on when initiating the PoC cluster conversation and select by predefined member's tabulation;

After h24.PoC XML document management servers process is finished, return success and respond described Aggregation Proxy; And

H25. described Aggregation Proxy is transmitted success response to described PoC XML document administrative client.

5. method according to claim 2 is characterized in that, described step h3 further comprises:

H31. the user who has the authority of selecting session members sends the HTTP request on PoC XML document administrative client, request is provided with initiates cluster conversation member's tabulation to be selected;

H32. whether the Aggregation Proxy inspection user that sends described request possesses corresponding authority, if any then passing on described request to PoC XML document management server;

After h33.PoC XML document management server receives described request, member's tabulation to be selected when initiating cluster conversation is set;

After h34.PoC XML document management servers process is finished, return success and respond described Aggregation Proxy; And

H35. described Aggregation Proxy is transmitted success response to described PoC XML document administrative client.

6. method according to claim 1 is characterized in that, described step b further comprises:

B1. the user initiates the request of PoC cluster conversation and gives the PoC server, and described request has comprised group's unified resource identifier;

B2. described PoC server transmit a request to management server request of PoC XML document and the corresponding data of described group's unified resource identifier according to group's unified resource identifier of described request; And

B3.PoC XML document management server returns the data of described group according to described request.

7. method according to claim 1 is characterized in that, if the PoC server checks that described user does not have the authority of selecting session members among the described step c, then:

The PoC server checks that described user does not initiate the authority of cluster conversation, then refuses described user and initiates cluster conversation; And

The inspection of PoC server is not that all members of invite group add session, does not then invite any member to add session.

8. method according to claim 1 is characterized in that: after step b, before the c, also comprise step:

F. whether inspection has described user's the sign and the member who selects that requires of interpolation to tabulate.

9. method according to claim 8 is characterized in that, if do not have described user's the sign and the member who invites that requires of interpolation to tabulate, does not then invite any member to add session.

Images