CN100407818C

CN100407818C - Method for selecting session members in PoC cluster session

Info

Publication number: CN100407818C
Application number: CN2006100339815A
Authority: CN
Inventors: 李绪健
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2006-02-23
Filing date: 2006-02-23
Publication date: 2008-07-30
Anticipated expiration: 2026-02-23
Also published as: CN1863341A

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

Select the method for session members when realizing PoC group initiation session

Technical field

The invention belongs to trunking communication field, select the method for session members when relating in particular to a kind of realization PoC (Push-to-talk over Cellular, " Push to talk over Cellular ") group initiation session based on cellular network.

Background technology

PoC promptly based on " press-and-talk " business of cellular network, also is " Push to talk over Cellular ", is the half-duplex voice business that a kind of user of permission communicates by letter immediately by specific keys.

PoC supports MPTY, and the user can be by interim group, fixedly mode such as group, chat group is carried out MPTY.

The data of PoC group are to be kept at PoC XDMS (XML Document ManagementServer, the XML document management server), the user can pass through terminal (XDMC, XMLDocument Management Client, the XML document administrative client) sends association requests and carry out management and group, this request will be by sending to PoC XDMS after AP (Aggregation Proxy, the Aggregation Proxy) authentication (determining whether this user has corresponding administration authority).Certainly, if user Portal provides the function of relevant management and group, the user just can directly send association requests by Portal and carry out management and group to PoCXDMS.

In " OMA-TS-PoC_XDM-V1_0-20050317-C " of PoC 1.0 versions codes and standards, provide attribute a:＜invite-members〉to group.As＜invite-members〉this attribute is set to:

1. True: then can other members of invite group when the session of this group is initiated;

2. Flase: then can other members of invite group when the session of this group is initiated.

This attribute is exercisable to the user, and promptly the user can be provided with as required and whether invite its group member when initiating cluster conversation.Certainly for fixing group, all members of invite group in the time of generally can being arranged on session and initiating.

Secondly at group rules＜ruleset〉child node＜rule there are two element:＜conditions the inside and＜actions.Wherein＜conditions be used to indicate have corresponding＜actions the user ID of authority;＜actions〉then comprised a kind of element＜allow-initiate-conference of Boolean type, when it then represents corresponding＜conditions during for true〉in specified user have the authority of initiating cluster conversation.

Corresponding handling process is as shown in Figure 1: check that earlier the user has or not＜allow-initiate-conference〉authority, as do not have then that refusing user's makes a call, if any then continuing inspection＜invite-members〉whether value be true; As＜invite-members〉value is then can all members of invite group add session during for true, then can not invite Any user to add session as for false the time.

But this scheme exists following defective:

(1), is not only to wish to invite or all members of invite group not, and may requires to invite the part member to participate in, and that like this prior art is to satisfy user's demand for the user.

(2) in addition, the user also may not only just hope invite group member participant session, the user also wish to invite other staff's participant session sometimes, and the user can only just invite behind the group of stability group session initiating, and then user's demand of inviting in advance can't be met.

(3) operator is in order to reduce reason such as system loading, and the fixing maximum number of session of group is limited.The purpose of this restriction is to prevent that the user from having too much participation number in every session.Therefore this attribute:＜max-participant-count below in session, having added〉(the maximum participation number of session).Obviously, if in the middle of reality, user's group member number is greater than＜max-participant-count〉during value, then serious problem can appear: user general＜invite-members〉when being set to true, because the group member number is greater than the maximum participation number of session, then server can be refused the request of initiation session; Be that the user can't initiate the group of stability group session.This has obviously reduced user experience.

In " OMA-ERELD_POC-V1_0-20050329-C " of PoC1.0 version codes and standards, also defined a kind of conversation type: Ad-hoc session, just interim cluster conversation.It supports the user that some invitee's tabulations are set provisionally, and invites them to participate in session.Obviously the user can be provided with invitee's tabulation as required neatly, in this than fixedly group is much flexible.

Yet this scheme still has deficiency, for example:

(1) however interim group require all to be provided with at every turn, obviously this is to loaded down with trivial details process of user Lai Shuoshi, in this respect obviously not fixedly group come conveniently.

(2) user can not be provided with the attribute that any group of stability group membership is correlated with to temporary group member, as whether can invite other people participant session, whether can be anonymous or the like, obvious fixing group management function powerful not in this respect.

Summary of the invention

The technical problem to be solved in the present invention is to overcome the deficiency that above-mentioned prior art exists, when being provided, a kind of PoC of realization group initiation session selects the method for session members, support user flexibility ground to invite the member to participate in cluster conversation, make the user when initiating cluster conversation, can invite some needed members to add session easily.

Select the method for session members when the invention provides a kind of PoC of realization 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.

Further, 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.

Further, 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.

Further, 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.

Further, 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.

Further, 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.

Further, 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.

Further, 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.

Further, if do not have described user's the sign and the member who invites that requires of interpolation to tabulate, then do not invite any member to add session.

Because the present invention selects the method for session members to make the call mechanism of PoC group obtain expansion to a great extent when realizing PoC group initiation session, flexibility is stronger, and carry out based on the data management of such scheme and uncomplicated at server end simultaneously, so scheme has feasibility.If application this programme will bring following useful effect:

(1) meet consumers' demand, be user-friendly to, improve user experience: owing to adopt the method for selecting session, so the user can invite the user of its required invitation as required; Also very convenient in the use, both have the advantage of fixing group concurrently, also had an advantage of interim group; Can satisfy the instructions for use of user under different situations to a great extent, improve user's experience.

(2) solved because group's number can not be invited the member during greater than the maximum number of the session of system defined when initiation session problem.Because the user can add some members in user list, and guarantee that its number is not more than the maximum number of session of system's defined, makes the user can initiate cluster conversation more easily.

(3) the compatible existing scheme of the present invention can realize all requirements of existing scheme.For example, the PoC server is checked when described user does not have the authority of selecting session members, will be handled according to existing scheme; And the inspection of PoC server is not to invite by predefined member's tabulation when initiating the PoC cluster conversation, can continue then to check whether all members of invite group add session, and handle according to existing scheme.

Description of drawings

Fig. 1 has the flow chart of inviting member's method when initiating the PoC cluster conversation now;

Fig. 2 is that data are prepared flow chart among the present invention;

Fig. 3 is a customer call management flow chart among the present invention;

Fig. 4 is at flow chart normal among Fig. 3 and that abnormal conditions are handled.

Embodiment

In " OMA-TS-PoC_XDM-V1_0-20050317-C " of PoC1.0 version codes and standards, defined the basic structure of PoC group.For finishing function of the present invention, on the structure of PoC group, increased following content:

(1) under group's root element, increases daughter element a:＜pre-invite-listset 〉.This daughter element is [COMMONPOL] type, has comprised zero or a plurality of＜pre-invite-list〉node, and＜pre-invite-list〉node comprises＜createlistuseridentity〉and＜userlist〉node.＜createlistuseridentity〉value is used to identify this list creating person's identity;＜userlist〉then comprised zero or a plurality of element, each element be used to identify invitee's identity＜entry daughter element or be used to identify invitee's tabulation of quoting＜external element.

(2) under group's root element, increase daughter element a:＜pre-inviteuser 〉.Its type is Boolean type: true or false.When being true, being illustrated in when session is initiated and inviting the user to require the member who invites; And when false, then be illustrated in when session is initiated and can not invite the user to require the member who invites.

(3) at＜rule〉daughter element＜actions of element〉increase a kind of new element＜pre-invite 〉, type is a Boolean type, is used to indicate which user and has in this fixing authority of invitation member during group's initiation session.When showing during for true, its value has this authority, at this moment the user can be at＜pre-invite-list〉daughter element＜userlist of element in add its member that will invite, also just can when fixing group's initiation session, invite needed member neatly; Then showing when its value is false does not have this authority.Need to prove that the user who has this authority can have the authority of initiating the group of stability group session simultaneously.

Please refer to shown in Figure 2ly, select the data of session members to prepare flow process when the present invention realizes PoC group initiation session and may further comprise the steps:

Step 1: group creator or other have the user of authority to go up transmission HTTP request in terminal (XDMC), certain group are added the user with pre-invite authority.For example the authority pre-invite that user A, user B possess the selection session members is given in request.

Step 2:AP checks whether send this requesting users possesses corresponding authority, if any transfer request then to PoC XDMS.

After step 3:PoC XDMS receives respective request, just the data to designated group increase by one＜rule〉node, and selection＜actions〉daughter element＜pre-invite be true, and at＜conditions node＜identity increase the desired member's sign that can select session members in the daughter element.For example two members in the group (user A and user B) setting is had this authority, is expressed 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>

After step 4:PoC XDMS finishes dealing with, return success and respond AP.

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

Step 6: group creator or other have the user of authority to go up the HTTP request that sends in terminal (XDMC), whether whether request is provided with when initiating the PoC cluster conversation Rule of judgment that will select by predefined member's tabulation, promptly be provided with＜pre-inviteuser〉be true.

Step 7:AP checks whether send this requesting users possesses corresponding authority, if any transfer request then to PoC XDMS.

After step 8:PoC XDMS receives respective request, setting＜pre-inviteuser〉value is true.This moment no matter＜invite-members whether be true, can be by all member's participant sessions of automatic invite group.

After step 9:PoC XDMS finishes dealing with, return success and respond AP.

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

Step 11: the user with authority (pre-invite) of selecting session members goes up the HTTP request that sends in terminal (XDMC), request is provided with initiates member's tabulation that the group of stability group session will be invited, for example: user B, user C, user D, user E, user F, user G, user H.

Step 12:AP checks and to send the authority whether this requesting users possesses pre-invite, if any transfer request then to PoC XDMS.

After step 13:PoC XDMS receives respective request, will be at＜pre-invite-listset〉in add a new node＜pre-invite-list, setting＜createlistuseridentity〉for sending requesting users sign, will be at＜userlist〉in add institute and require the member of invitation to tabulate.For example, the request of sending is user A, and member's tabulation that initiation group of stability group session will be invited is user B, user C, user D, user E, user F, user G, user H, and then corresponding data representation is as follows:

<pre-invite-listset>

......

<pre-invite-list>

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

<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>

After step 14:PoC XDMS finishes dealing with, return success and respond AP.

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

Please refer to shown in Figure 3ly, after data were ready, customer call management process of the present invention may further comprise the steps:

Step S1: the user initiates the request of PoC cluster conversation and gives PoC Server, and this request has comprised group's unified resource identifier (URI).

Step S2:PoC Server can transmit a request to the data that the URI of group is got in PoC XDMS request according to the URI of group of this request.

Step S3:PoC XDMS will return the data of relevant groups according to the request of PoC Server.

Step S4, step S5, step S6:PoC Server according to the data of this group just can check this user whether possess the pre-invite authority,＜pre-inviteuser whether value be true, whether node＜pre-invite-list is arranged be this user.As above-mentioned inspection all by then entering step S7.Normal and the exception handling procedure of step S4, step S5, step S6 is in detail as Fig. 4 and explanation thereof.

Step S7: server basis＜userlist〉in tabulation invite the member, return as the member and then can illustrate after the response that accepts session and invite successfully.

Step S8: server returns access success and responds to the user.

Flow process shown in Figure 4 is as follows:

Flow process (1): when the user initiated group call, the PoC server can check at first whether the user has＜pre-invite〉authority.If any then continuing inspection＜pre-inviteuser〉value, enter " flow process (2) ".Otherwise can be by original design cycle: check that earlier the user has or not＜allow-initiate-conference〉authority, as do not have then that refusing user's makes a call, if any then continuing inspection＜invite-members〉whether value be true; As＜invite-members〉value is then can all members of invite group add session during for true, then can not invite any member to add session as for false the time;

Flow process (2): server continues inspection＜pre-inviteuser〉whether be worth true.When being true, server continues to check whether node＜pre-invite-list is arranged〉be this user, enter " flow process (3) ".Otherwise, server inspection＜invite-members〉whether value be true: as＜invite-members〉value is then can all members of invite group add session during for true, then can not invite any member to add session as for false the time;

Flow process (3): server continues to check whether node＜pre-invite-list is arranged〉be this user.As then inviting sometimes＜userlist〉in each listed member; Otherwise server does not invite any member to add session.

Claims

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;

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:

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

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

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

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

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:

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

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.