CN1889722A - PoC group session realizing method and apparatus - Google Patents
PoC group session realizing method and apparatus Download PDFInfo
- Publication number
- CN1889722A CN1889722A CN 200610103265 CN200610103265A CN1889722A CN 1889722 A CN1889722 A CN 1889722A CN 200610103265 CN200610103265 CN 200610103265 CN 200610103265 A CN200610103265 A CN 200610103265A CN 1889722 A CN1889722 A CN 1889722A
- Authority
- CN
- China
- Prior art keywords
- group
- user
- server
- authority
- poc
- 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.)
- Granted
Links
Images
Landscapes
- Telephonic Communication Services (AREA)
Abstract
A method for realizing session of PoC group includes using identification of the second group to request server side to combine the second group by user in the first group, checking right of user issued with combination request and adding all users in the second group to the first group by server side according to said identification of the second group if user has the right to do so or otherwise refusing to carry out combination.
Description
Technical field
The present invention relates to the communications field, particularly relate to a kind of implementation method and device of PoC cluster conversation.
Background technology
PoC (Push-to-talk over Cellular) also is Push to talk over Cellular promptly based on " press-and-talk " business of cellular network, 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 various sessions of PoC all are based upon on the Session initiation Protocol SIP/IP territory.As both sides or when needing to communicate in many ways, at first all must set up a SIP session.
SIP is the control protocol of an application layer, can be used for setting up, revises and stop Multimedia session (perhaps meeting).It allows to use internet side point (user agent) to seek the participant and allow to set up a sharable conversation description.SIP provides the INVITE method to set up a session, referring to shown in Figure 1, has illustrated that the SIP session is from being established to the whole process of end.And this flow process is also followed in all sessions of PoC.
Among the figure, at first the request between the terminal UE of user A and user B all needs server: the proxy by the middle-agent with response.
When the INVITE request arrived the UE of user B, the UE of user B can ring purine, simultaneously this state (180) is sent it back the UE of user A.When user B uses UE to accept session request, can send 200 responses to the UE of user A; And received for 200 whens response as the UE of user A, show that session sets up (Session Established).
When a reef knot bundle session of session, send BYE and ask at last to the other side; And when the other side receives this request, show that then session finishes.
At present, PoC server (PoC Server) is supported cluster conversation, below two flow processs (annotating: select from " Open Mobile Alliance OMA-AD_PoC-V1_0-20050805-C ") PoC Server performed function in cluster conversation has been described.
Referring to shown in Figure 2, be start flow (originating procedures);
Referring to shown in Figure 3, be termination process (termination procedures).
As can be seen, POC Server can execution control function (controllingfunction) and participation function (participating function) from above-mentioned two flow charts.Controlling function carries out the concentrated manipulation function of session; And participating function just is responsible for participant's role, is undertaking the session manipulation function of part, provide between user and the controlling function alternately.In the PoC cluster conversation, the POC Server at management and group person place is a management server, and it carries out controlling role, and other PoC Server is a member server, and it carries out participating role.
But, prior art do not support to set up a plurality of (" a plurality of " are meant " two or more ", below if no special instructions, all represent this implication) cluster conversation carries out that integral body merges and separating treatment.
For example: when a cluster conversation A is set up in Xiao Ming, Xiao Wang and little east, a cluster conversation B also set up in little sea, Xiao Li and little literary composition, working as Xiao Ming so this moment wants to allow little sea, Xiao Li and little literary composition participate in the cluster conversation A at its place together, though can be by sending the invite request message in cluster conversation A, invite little sea, Xiao Li and little literary composition, to allow little sea, Xiao Li and little literary composition participate in cluster conversation A, following two shortcomings are arranged but still:
The first, must one by one send the invite request message to little sea, Xiao Li and little literary composition, also must allow little sea, Xiao Li and little literary composition return the 200OK response one by one, obviously this is a loaded down with trivial details process, particularly when group's number is more;
The second, the cluster conversation B of little sea, Xiao Li and little literary composition still exists.And cluster conversation A all participated in current little sea, Xiao Li and little literary composition, and obviously the existence of cluster conversation B is insignificant; And if when little sea, Xiao Li and little literary composition finish this cluster conversation, need the process of an end session, obviously be very inefficient.
The shortcoming of two cluster conversation merging aspects has been described above.Aspect the separation after merging, there is shortcoming too.
For example: after cluster conversation A participated in Dang Xiaohai, Xiao Li and little literary composition, they wanted again to withdraw from after after a while, when carrying out three of them cluster conversation again, following two shortcomings were arranged obviously:
The first, little sea, Xiao Li and little literary composition must send bye message to cluster conversation A one by one, and to withdraw from cluster conversation A, this obviously also is the process of a poor efficiency;
The second, after Dang Xiaohai, Xiao Li and little literary composition withdraw from cluster conversation A, its original cluster conversation B may be through with by them before, also may be because the overtime serviced device of conference mute is through with, they just must initiate three of them cluster conversation again so, so also are the loaded down with trivial details and processes of poor efficiency.
Summary of the invention
The invention provides a kind of implementation method and device of PoC cluster conversation, do not support a plurality of groups that set up are carried out the whole problem that merges in order to solve prior art.
Further, solve the problem that prior art does not support a plurality of groups that merged are carried out overall separation.
The inventive method comprises the following steps:
User in A, first group merges second group with the sign of second group to the server side request;
B, server side inspection initiate to merge the authority of requesting users, if having corresponding authority, then change step C over to; Otherwise refusal merges;
C, server side add all users in second group in first group to the sign of described second group.
Before the wherein said steps A, in the tabulation of the PoC of server side group rules, increase new element,, when merging request, check the authority of initiating to merge the request user in order to receive at server side with the Permission Levels whether the expression user has authority and user.Before the described steps A, the keeper of merged group sends authorization request message to server side, so that corresponding user obtains the specified power rank.
Further, described step B comprises following substep:
B1, server side inspection are initiated to merge requesting users and whether are had authority, if having authority, then change step B2 over to; Otherwise refusal merges; User's highest weight limit rank compares in the Permission Levels that B2, server side will initiate to merge requesting users and second group, as if greater than, then directly change step C over to; If equal, then obtain having other user's of highest weight limit level permission in second group through consultation after, change step C again over to; If less than, then refusal merges.
Further, comprise among the described step C: the management server of second group obtains the data of second group according to the sign of second group, and by response message the data of second group are sent to the management server of first group, and the member server of the management server of first group and second group is set up session.Also comprise among the described step C: delete the session between the member server of the management server of second group and second group, and the management server of second group is deleted the Session Resources of second group.
In sum, also comprise the following steps: that the user in D, the group after merging separates second group with the sign of second group to the server side request after the described step C; The user's of detach request authority is initiated in E, server side inspection, if having corresponding authority, then changes step F over to; Otherwise refusal separates; F, server side will separate the group of all users in second group after merging with the sign of described second group.
Further, described step e comprises that whether the user of following substep: E1, server side inspection initiation detach request has authority, if having authority, then changes step e 2 over to; Otherwise refusal separates; The highest weight limit rank that E2, server side will be initiated user in user's the Permission Levels of detach request and second group compares, if greater than, then directly change step F over to; If equal, then obtain having other user's of highest weight limit level permission in second group through consultation after, change step F again over to; If less than, then refusal separates.
Further, comprise in the described step F: if when merging in group, the management server of second group has been deleted the Session Resources of second group, then after the management server of second group is received detach request message, redistributes the Session Resources of second group.
Further, comprise in the described step F: the management server of first group obtains the data of second group according to the sign of second group, and by detach request message the data of second group are sent to the management server of second group, and the member server of the management server of second group and second group is set up session.Delete the session between the member server of the management server of first group and second group, and the management server of first group will be deleted the group of all users in second group after merging.
PoC cluster server of the present invention comprises:
The first scope check unit is used for checking whether initiate to merge requesting users has corresponding authority;
Merge cells is used for judging when initiation merging requesting users has corresponding authority in the described first scope check unit, and the user in the group of this user's desire merging is added in the group at this user place.
Further, also comprise in the described server:
The second scope check unit is used to check whether the user who initiates detach request has corresponding authority;
Separative element is used for judging when the user who initiates detach request has corresponding authority in the described second scope check unit, separates the group of user after merging in the group that will this user's desire separates.
Beneficial effect of the present invention is as follows:
In the inventive method, the user in first group merges second group with the sign of second group to the server side request; Server side with the sign of described second group, adds all users in second group in first group to after reviewing and validate and initiate merging requesting users and have corresponding authority.
Further, user in the group after the merging with the sign of second group when the server side request separates second group, server side is reviewed and validate after the user who initiates detach request has corresponding authority, with the sign of described second group, will separate the group of all users in second group after merging.
In order to support the inventive method, the present invention also provides a kind of PoC cluster server.
By the enforcement of the inventive method, first, can make two or more PoC group merge into a PoC group, realize concentrating cluster conversation, satisfy and carry out the user's request of centralized call; The second, can in concentrating cluster conversation, isolate a certain PoC group, realize packet sessions, satisfy the demand and carry out the user's request of packet call.Because the inventive method makes the call mechanism of PoC group obtain expansion to a great extent, flexibility is stronger, and scheme has feasibility.If user experience will effectively be met consumers' demand, be user-friendly to, improve to application the inventive method.
Description of drawings
Fig. 1 is for having the SIP session now from being established to the signaling process of end;
Fig. 2 is the start flow of existing PoC cluster conversation;
Fig. 3 is the termination process of existing PoC cluster conversation;
Fig. 4 is a case step flow chart of the present invention;
Fig. 5 increases the signaling process figure of authority for the user for the present invention;
Fig. 6 merges signaling process figure in the example;
Fig. 7 is that the management server of first group and the member server of second group are set up the signaling process figure of session;
Fig. 8 separates signaling process figure in the example;
Fig. 9 is the signaling process figure of the member server end session of the management server of first group and second group;
Figure 10 is the structural representation of PoC cluster server of the present invention.
Embodiment
In order to support that a plurality of groups that set up are carried out integral body to be merged, further a plurality of groups that merged are carried out overall separation in order to support, the invention provides a kind of implementation method of PoC cluster conversation, referring to shown in Figure 4, comprise following key step:
S0, user authority management.
This step is to enter the preceding preparation process of flow process.
In OMA standard " OMA-TS-PoC_XDM-V1_0-20050428-C " standard, the basic structure of PoC group data has been described.For realizing the present invention, need in the tabulation of the PoC of server side group rules, increase a kind of new element: allow-conference-dynamically.Illustrate with this element whether the user has and carry out that the PoC cluster conversation merges and the authority of separating.
Described allow-conference-dynamically type is the int type, and when it is to represent to possess the PoC cluster conversation more than 1 or 1 during value to merge and the authority of separating, but its value represents that its Permission Levels are low more when low more.
Referring to shown in Figure 5, the XDMC transmission XCAP solicited message of the keeper of merged group by terminal has been described, add the process of allow-conference-dynamically authority for other user:
Step 1: the keeper of merged group goes up in terminal (XDMC) and sends the HTTP request, certain group is added the user with allow-conference-dynamically authority.
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 general＜actions〉daughter element＜allow-conference-dynamically the analog value that is set to ask, and at＜conditions node＜identity increase the user ID that requires to have this authority in the daughter element.
After step 4:PoC XDMS finishes dealing with, return success and respond AP.
Step 5:AP transmits success response to terminal (XDMC).
For example: the keeper of merged group sends message request for the first time user A, user B is changed to the user with this authority, and its rank is 1; For the second time send message request user C is changed to the user with this authority, its rank is 2.Then this regular XML that preserves on the PoC XDMS is expressed as:
<ruleset>
……
<rule?id＝”a10c”>
<condition>
<identity>UserA@XDMSServer.com</identity>
<identity>UserB@XDMSServer.com</identity>
</condition>
<actions><allow-conference-dynamically>1</allow-conference-dynamically>
</actions>
</rule>
<rule?id＝”allc”>
<condition>
<identity>UserC@XDMSServer.com</identity>
</condition>
<actions><allow-conference-dynamically>2</allow-conference-dynamically>
</actions>
</rule>
</ruleset>
User in S1, first group merges second group with the sign of second group to the server side request.
Second group is designated the URI that is assigned to when setting up second group.
S2, server side inspection initiate to merge the authority of requesting users, if having corresponding authority, then change step S3 over to; Otherwise refusal merges.
Server side checks in two steps whether initiate to merge requesting users has corresponding authority.
The first step: the server side inspection is initiated to merge requesting users and whether is had authority, if having authority, then changes for second step over to; Otherwise refusal merges;
Second step: user's highest weight limits rank to compare in the Permission Levels that server side will initiate to merge requesting users and second group, as if greater than, then directly change step S3 over to; If equal, then obtain having other user's of highest weight limit level permission in second group through consultation after, change step S3 again over to; If less than, then refusal merges.
S3, server side add all users in second group in first group to the sign of described second group.
The management server of second group obtains the data of second group according to the sign of second group, and the data of second group are sent to the management server of first group by response message, so that the management server of first group adds all users in second group in first group to; And the member server of the management server of first group and second group is set up session, the cluster conversation after merging with support; Afterwards, delete the session between the member server of the management server of second group and second group, and the management server of second group is deleted the Session Resources of second group.
User in the group after S4, the merging separates second group with the sign of second group to the server side request.
Second group is designated the URI that is assigned to when setting up second group.When merging second group, the URI of second group is kept by the management server of first group, and writes down the corresponding relation of user in this URI and second group.
The user's of detach request authority is initiated in S5, server side inspection, if having corresponding authority, then changes step S6 over to; Otherwise refusal separates.
Server side checks in two steps whether the user who initiates detach request has corresponding authority.
The first step: whether the user that detach request is initiated in the server side inspection has authority, if having authority, then changes for second step over to; Otherwise refusal separates;
Second step: server side will be initiated the highest weight of user in user's Permission Levels and second group of detach request and be limit rank to compare, as if greater than, then directly change step S6 over to; If equal, then obtain having other user's of highest weight limit level permission in second group through consultation after, change step S6 again over to; If less than, then refusal separates.
S6, server side will separate the group of all users in second group after merging with the sign of described second group.
If when merging in group, the management server of second group has been deleted the Session Resources of second group, then after the management server of second group is received detach request message, redistributes the Session Resources of second group.
The management server of first group obtains the data of second group according to the sign of second group, and by detach request message the data of second group are sent to the management server of second group, so that the management service of second group is added the user of second group in second group to; And the member server of the management server of second group and second group sets up session, to support second cluster conversation; Afterwards, delete the session between the member server of the management server of first group and second group, and the management server of first group will be deleted the group of all users in second group after merging.
Below specifically describe the inventive method by an example.
The scene of this example is: user A initiates a PoC cluster conversation 1, and the participant is user B, user C; User D has initiated a cluster conversation 2, and the participant is user E, user F.In the group of user D institute initiation session the user with allow-conference-dynamically authority being set is user A, and its rank is M=1.User A wants to allow user D, user E, user F participate in cluster conversation 1 now, just allows cluster conversation 2 merge in the cluster conversation 1.Referring to shown in Figure 6, comprise following concrete steps:
Step 1: user A sends refer and invites in cluster conversation 1, and the URI that request is added is the URI of user D, user E, user F place group.
Step 9:PoC server2 (controlling) will check whether user A has the authority that merges cluster conversation 2.
PoC server2 (controlling) checks at first whether initiate to merge requesting users A has the allow-conference-dynamically authority, if not then refusal; If have, then obtain its Permission Levels value M (setting the Permission Levels value M=1 of user A according to scene).Further, whether PoC server2 (controlling) checks will have the user of allow-conference-dynamically authority among the user of merged cluster conversation 2, if do not have, then agree to merge.If have, then obtain other value of highest authority level N among these users, and M and N are compared, if M＞N then directly agrees to merge; If M=N, then, agree merging by having in user A and the cluster conversation 2 after other user of highest authority level holds consultation and obtain allowing; If M＜N, then refusal merges.
Setting as can be known according to this routine scene, PoC server2 (controlling) will ask by this refer.
Step 13:PoC server1 (controlling) will add the user of cluster conversation 2 in the meeting-place of cluster conversation 1 according to the information in the 200OK response.Simultaneously also set up session with the member server PoC server B (participating) at the user place of cluster conversation 2.
In the above-mentioned steps 13, PoC server1 (controlling) and the user's of cluster conversation 2 PoCserver B (participating) set up the process of session, referring to shown in Figure 7, further comprise the following steps:
Z1 to Z3:PoC server1 (controlling) sends the invite request to PoC serverB (participating), to set up session.
Z4 to Z5:PoC serverB (participating) will finish the session with PoC server2 (controlling) after receiving invite message; And PoC server2 (controlling) also will delete the operation in cluster conversation 2 meeting-place.
Z6 to Z7:PoC server2 (controlling) returns 200OK and responds PoC serverB (participating), and it is successful to confirm that PoC serverB (participating) finishes with the request of PoC server2 (controlling) session.
Z8 to Z10:PoC server B (participating) returns 200OK and responds PoC server1 (controlling), and it is successful to confirm that PoC server1 (controlling) sets up with the request of PoC serverB (participating) session.
So far the process prescription of He Binging finishes.
If user A isolates cluster conversation 2 again after the merging of finishing cluster conversation 2 and cluster conversation 1,, comprise following concrete steps then referring to shown in Figure 8:
Step 19: user A sends the request of refer removing members in cluster conversation 1, and the URI of request deletion is the URI of user D, user E, user F place group.
Step 20 is to step 23: the refer request that user A is sent is sent to PoC server1 (controlling), and PoC server1 (controlling) finds that this is the refer request of an isolates group session.
Step 24:PoC server1 (controlling) will check whether user A has the authority of isolates group session.This step is similar with step 9.
Setting as can be known according to this routine scene, PoC server1 (controlling) will ask by this refer.
Step 25 is to the corresponding relation of step 27:PoC server1 (controlling) according to user in the URI of cluster conversation 2 of record and the cluster conversation 2, user's data in the cluster conversation 2 is carried in the detach request, and send to SIP/IP Core1, by SIP/IP Core1 request is sent to SIP/IP Core2; SIP/IP Core2 then continues request is dealt on the PoC server2 (controlling), is handled by PoC server2 (controlling).The meeting-place that PoC server2 (controlling) request of receiving will be created cluster conversation 2.
Step 28 sends 200OK to step 30:PoC server2 (controlling) and responds to PoCserver1 (controlling).
Step 31 is to step 36: since before PoC server1 (controlling) set up session with PoC server2 (controlling), so after session separated, both needed end session.So PoCserver1 (controlling) will send the bye request to PoC server2 (controlling), with end session.At last, PoC server2 (controlling) returns 200OK and responds PoC server1 (controlling).
Step 37:PoC server1 (controlling) deletes the user of former cluster conversation 2 in the meeting-place of cluster conversation 1, simultaneously also with the user's of cluster conversation 2 PoC server B (participating) end session.
Step 38 is returned the 200OK response to step 42:PoC server1 (controlling) to user A, and expression is operated successfully.
In the above-mentioned steps 37, the process of the user's of PoC server1 (controlling) and cluster conversation 2 PoCserver B (participating) end session referring to shown in Figure 9, further comprises the following steps:
T1 to T3:PoC server1 (controlling) sends the bye request to PoC serverB (participating), with end session.
T4 to T5:PoC server B (participating) needs the session of foundation and PoC server2 (controlling) after receiving bye message; And the user data of the cluster conversation 2 that PoC server2 (controlling) also will send by detach request according to PoCserver1 (controlling) adds cluster conversation 2 users' operation.
T6 to T7:PoC server2 (controlling) returns 200OK and responds PoC server B (participating).
T8 to T10:PoC server B (participating) returns 200OK and responds PoC server1 (controlling).
So far separating process is described.
In order to support said method, the present invention also provides a kind of PoC cluster server, and referring to shown in Figure 10, it comprises interconnective first scope check unit and the merge cells; Further, described PoC cluster server also can comprise interconnective second scope check unit and the separative element.
The described first scope check unit is used for checking whether initiate to merge requesting users has corresponding authority.Described user's authority is before this user initiates to merge request, by the keeper of merged group and authorizing alternately of server side.Described inspection was divided into for two steps, checked at first whether have authority, if there is not authority, then directly refusal merges if initiating to merge requesting users.If authority is arranged, then further this user's Permission Levels and the highest weight limit rank of the user in its desire merging group are compared, if greater than, judge that then initiating the merging requesting users has corresponding authority; After equaling, then obtain its desire through consultation to merge the permission that has other user of highest weight limit level in group, judge that again initiation merges requesting users and has corresponding authority; If less than, then refusal merges.
Described merge cells is used for judging when initiation merging requesting users has corresponding authority in the described first scope check unit, and the user in the group of this user's desire merging is added in the group at this user place.
The described second scope check unit is used to check whether the user who initiates detach request has corresponding authority.Its checking process is similar to the first scope check unit.
Described separative element is used for judging when the user who initiates detach request has corresponding authority in the described second scope check unit, separates the group of user after merging in the group that will this user's desire separates.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (13)
1, a kind of implementation method of PoC cluster conversation is characterized in that, comprises the following steps:
User in A, first group merges second group with the sign of second group to the server side request;
B, server side inspection initiate to merge the authority of requesting users, if having corresponding authority, then change step C over to; Otherwise refusal merges;
C, server side add all users in second group in first group to the sign of described second group.
2, the method for claim 1, it is characterized in that, before the described steps A, in the tabulation of the PoC of server side group rules, increase new element, the Permission Levels that whether have authority and user with the expression user, when merging request, check the authority of initiating to merge the request user in order to receive at server side.
3, method as claimed in claim 2 is characterized in that, before the described steps A, the keeper of merged group sends authorization request message to server side, so that corresponding user obtains the specified power rank.
4, method as claimed in claim 3 is characterized in that, described step B comprises following substep:
B1, server side inspection are initiated to merge requesting users and whether are had authority, if having authority, then change step B2 over to; Otherwise refusal merges;
User's highest weight limit rank compares in the Permission Levels that B2, server side will initiate to merge requesting users and second group, as if greater than, then directly change step C over to; If equal, then obtain having other user's of highest weight limit level permission in second group through consultation after, change step C again over to; If less than, then refusal merges.
5, method as claimed in claim 4, it is characterized in that, comprise among the described step C: the management server of second group obtains the data of second group according to the sign of second group, and by response message the data of second group are sent to the management server of first group, and the member server of the management server of first group and second group is set up session.
6, method as claimed in claim 5, it is characterized in that, also comprise among the described step C: delete the session between the member server of the management server of second group and second group, and the management server of second group is deleted the Session Resources of second group.
7, as each described method of claim 2 to 6, it is characterized in that, also comprise the following steps: after the described step C
User in the group after D, the merging separates second group with the sign of second group to the server side request;
The user's of detach request authority is initiated in E, server side inspection, if having corresponding authority, then changes step F over to; Otherwise refusal separates;
F, server side will separate the group of all users in second group after merging with the sign of described second group.
8, method as claimed in claim 7 is characterized in that, described step e comprises following substep:
Whether the user that detach request is initiated in E1, server side inspection has authority, if having authority, then changes step e 2 over to; Otherwise refusal separates;
The highest weight limit rank that E2, server side will be initiated user in user's the Permission Levels of detach request and second group compares, if greater than, then directly change step F over to; If equal, then obtain having other user's of highest weight limit level permission in second group through consultation after, change step F again over to; If less than, then refusal separates.
9, method as claimed in claim 7, it is characterized in that, comprise in the described step F: if when merging in group, the management server of second group has been deleted the Session Resources of second group, then after the management server of second group is received detach request message, redistribute the Session Resources of second group.
10, method as claimed in claim 7, it is characterized in that, comprise in the described step F: the management server of first group obtains the data of second group according to the sign of second group, and by detach request message the data of second group are sent to the management server of second group, and the member server of the management server of second group and second group is set up session.
11, method as claimed in claim 10, it is characterized in that, delete the session between the member server of the management server of first group and second group, and the management server of first group will be deleted the group of all users in second group after merging.
12, a kind of PoC cluster server is characterized in that, comprising:
The first scope check unit is used for checking whether initiate to merge requesting users has corresponding authority;
Merge cells is used for judging when initiation merging requesting users has corresponding authority in the described first scope check unit, and the user in the group of this user's desire merging is added in the group at this user place.
13, server as claimed in claim 12 is characterized in that, also comprises in the described server:
The second scope check unit is used to check whether the user who initiates detach request has corresponding authority;
Separative element is used for judging when the user who initiates detach request has corresponding authority in the described second scope check unit, separates the group of user after merging in the group that will this user's desire separates.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB200610103265XA CN100411461C (en) | 2006-07-20 | 2006-07-20 | PoC group session realizing method and apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB200610103265XA CN100411461C (en) | 2006-07-20 | 2006-07-20 | PoC group session realizing method and apparatus |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1889722A true CN1889722A (en) | 2007-01-03 |
| CN100411461C CN100411461C (en) | 2008-08-13 |
Family
ID=37578981
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB200610103265XA Expired - Fee Related CN100411461C (en) | 2006-07-20 | 2006-07-20 | PoC group session realizing method and apparatus |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100411461C (en) |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101378366B (en) * | 2007-08-31 | 2011-04-20 | 华为技术有限公司 | Method and apparatus for adding user into group conversation |
| CN102457811A (en) * | 2010-10-18 | 2012-05-16 | 中国移动通信集团北京有限公司 | Method, system and device for PoC (Push-to-talk over Cellular) group communication |
| CN103281237A (en) * | 2013-06-14 | 2013-09-04 | 北京小米科技有限责任公司 | Group processing method and device |
| WO2016155015A1 (en) * | 2015-04-03 | 2016-10-06 | 华为技术有限公司 | Multi-group regrouping method and device |
| WO2016161591A1 (en) * | 2015-04-09 | 2016-10-13 | 华为技术有限公司 | Method and device of establishing multi-group call |
| CN106254220A (en) * | 2016-08-16 | 2016-12-21 | 北京小米移动软件有限公司 | The management method of instant messaging group and device |
| CN106254084A (en) * | 2016-03-07 | 2016-12-21 | 上海驴徒电子商务有限公司 | Group chat paradigmatic system |
| CN106453066A (en) * | 2016-12-09 | 2017-02-22 | 腾讯科技（深圳）有限公司 | Group session processing method and system, terminal and server |
| CN106487533A (en) * | 2015-08-27 | 2017-03-08 | 九玉（北京）科技有限公司 | A kind of method and device set up circle of friends and communicated based on circle of friends |
| CN106506560A (en) * | 2016-12-29 | 2017-03-15 | 广州华多网络科技有限公司 | A kind of right management method, and device |
| WO2018201306A1 (en) * | 2017-05-02 | 2018-11-08 | 华为技术有限公司 | Group connection method and related equipment |
| WO2019079971A1 (en) * | 2017-10-24 | 2019-05-02 | 深圳市云中飞网络科技有限公司 | Method for group communication, and apparatus, computer storage medium, and computer device |
| CN110198489A (en) * | 2019-05-17 | 2019-09-03 | 网宿科技股份有限公司 | A kind of multigroup group audio-video-interactive method and system |
| CN110233742A (en) * | 2018-03-06 | 2019-09-13 | 阿里巴巴集团控股有限公司 | A kind of group's method for building up, system, terminal and server |
| CN111277637A (en) * | 2020-01-14 | 2020-06-12 | 腾讯科技（深圳）有限公司 | Method, device, terminal and storage medium for merging session groups |
| US10893237B2 (en) | 2019-05-17 | 2021-01-12 | Wangsu Science & Technology Co., Ltd. | Method and system for multi-group audio-video interaction |
| CN113497715A (en) * | 2020-03-18 | 2021-10-12 | 恩希软件株式会社 | Chat service providing method and device |
| WO2022142504A1 (en) * | 2020-12-29 | 2022-07-07 | 上海掌门科技有限公司 | Meeting group merging method and device |
| WO2023035834A1 (en) * | 2021-09-10 | 2023-03-16 | 华为技术有限公司 | Wi-fi direct communication method and apparatus |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100370737C (en) * | 2003-11-12 | 2008-02-20 | 鸿富锦精密工业（深圳）有限公司 | Managing system and method for user authority |
| CN100527733C (en) * | 2003-12-31 | 2009-08-12 | 华为技术有限公司 | SIP system and method for implementing SIP group call |
| KR100840365B1 (en) * | 2004-07-30 | 2008-06-20 | 삼성전자주식회사 | Method for merging session of Multiple Push To Talk over Cellular session and system thereof |
| KR100678142B1 (en) * | 2004-08-31 | 2007-02-02 | 삼성전자주식회사 | Mobile communication system using push to talk scheme supplying for location based service and method therefor |
-
2006
- 2006-07-20 CN CNB200610103265XA patent/CN100411461C/en not_active Expired - Fee Related
Cited By (40)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101378366B (en) * | 2007-08-31 | 2011-04-20 | 华为技术有限公司 | Method and apparatus for adding user into group conversation |
| CN102457811A (en) * | 2010-10-18 | 2012-05-16 | 中国移动通信集团北京有限公司 | Method, system and device for PoC (Push-to-talk over Cellular) group communication |
| CN103281237A (en) * | 2013-06-14 | 2013-09-04 | 北京小米科技有限责任公司 | Group processing method and device |
| US10952036B2 (en) | 2015-04-03 | 2021-03-16 | Huawei Technologies Co., Ltd. | Method for regrouping multiple groups and device |
| CN112040425A (en) * | 2015-04-03 | 2020-12-04 | 华为技术有限公司 | Multi-group recombination method and equipment |
| US10470003B2 (en) | 2015-04-03 | 2019-11-05 | Huawei Technologies Co., Ltd. | Method for regrouping multiple groups and device |
| CN106576384B (en) * | 2015-04-03 | 2020-07-28 | 华为技术有限公司 | Multi-group recombination method and equipment |
| CN112040425B (en) * | 2015-04-03 | 2024-04-09 | 华为技术有限公司 | Multi-group reorganization method and device |
| JP2018512000A (en) * | 2015-04-03 | 2018-04-26 | ホアウェイ・テクノロジーズ・カンパニー・リミテッド | Method and device for reorganizing multiple groups |
| EP3267762A4 (en) * | 2015-04-03 | 2018-01-17 | Huawei Technologies Co. Ltd. | Multi-group regrouping method and device |
| WO2016155015A1 (en) * | 2015-04-03 | 2016-10-06 | 华为技术有限公司 | Multi-group regrouping method and device |
| CN106576384A (en) * | 2015-04-03 | 2017-04-19 | 华为技术有限公司 | Multi-group regrouping method and device |
| US10743148B2 (en) | 2015-04-09 | 2020-08-11 | Huawei Technologies Co., Ltd. | Multi-group call setup method and device |
| US10425775B2 (en) | 2015-04-09 | 2019-09-24 | Huawei Technologies Co., Ltd. | Multi-group call setup method and device |
| CN106465453A (en) * | 2015-04-09 | 2017-02-22 | 华为技术有限公司 | Method and device of establishing multi-group call |
| RU2678464C1 (en) * | 2015-04-09 | 2019-01-29 | Хуавей Текнолоджиз Ко., Лтд. | Method and device for setup of multiple call |
| CN111050424B (en) * | 2015-04-09 | 2023-09-29 | 华为技术有限公司 | Multi-group call establishment method and equipment |
| CN111050424A (en) * | 2015-04-09 | 2020-04-21 | 华为技术有限公司 | Multi-group call establishment method and device |
| CN106465453B (en) * | 2015-04-09 | 2019-11-29 | 华为技术有限公司 | More group call method for building up and equipment |
| WO2016161591A1 (en) * | 2015-04-09 | 2016-10-13 | 华为技术有限公司 | Method and device of establishing multi-group call |
| CN106487533A (en) * | 2015-08-27 | 2017-03-08 | 九玉（北京）科技有限公司 | A kind of method and device set up circle of friends and communicated based on circle of friends |
| CN106254084A (en) * | 2016-03-07 | 2016-12-21 | 上海驴徒电子商务有限公司 | Group chat paradigmatic system |
| CN106254220A (en) * | 2016-08-16 | 2016-12-21 | 北京小米移动软件有限公司 | The management method of instant messaging group and device |
| CN106254220B (en) * | 2016-08-16 | 2019-06-04 | 北京小米移动软件有限公司 | The management method and device of instant messaging group |
| CN106453066A (en) * | 2016-12-09 | 2017-02-22 | 腾讯科技（深圳）有限公司 | Group session processing method and system, terminal and server |
| CN106453066B (en) * | 2016-12-09 | 2020-03-17 | 腾讯科技（深圳）有限公司 | Group session processing method, terminal, server and system |
| CN106506560A (en) * | 2016-12-29 | 2017-03-15 | 广州华多网络科技有限公司 | A kind of right management method, and device |
| CN106506560B (en) * | 2016-12-29 | 2019-10-29 | 广州华多网络科技有限公司 | A kind of right management method and device |
| WO2018201306A1 (en) * | 2017-05-02 | 2018-11-08 | 华为技术有限公司 | Group connection method and related equipment |
| WO2019079971A1 (en) * | 2017-10-24 | 2019-05-02 | 深圳市云中飞网络科技有限公司 | Method for group communication, and apparatus, computer storage medium, and computer device |
| CN110233742B (en) * | 2018-03-06 | 2022-04-01 | 阿里巴巴集团控股有限公司 | Group establishing method, system, terminal and server |
| CN110233742A (en) * | 2018-03-06 | 2019-09-13 | 阿里巴巴集团控股有限公司 | A kind of group's method for building up, system, terminal and server |
| US10893237B2 (en) | 2019-05-17 | 2021-01-12 | Wangsu Science & Technology Co., Ltd. | Method and system for multi-group audio-video interaction |
| CN110198489A (en) * | 2019-05-17 | 2019-09-03 | 网宿科技股份有限公司 | A kind of multigroup group audio-video-interactive method and system |
| CN111277637A (en) * | 2020-01-14 | 2020-06-12 | 腾讯科技（深圳）有限公司 | Method, device, terminal and storage medium for merging session groups |
| CN113497715A (en) * | 2020-03-18 | 2021-10-12 | 恩希软件株式会社 | Chat service providing method and device |
| US11570013B2 (en) | 2020-03-18 | 2023-01-31 | Ncsoft Corporation | Method and apparatus for providing chat service |
| CN113497715B (en) * | 2020-03-18 | 2023-09-19 | 恩希软件株式会社 | Chat service providing method and device |
| WO2022142504A1 (en) * | 2020-12-29 | 2022-07-07 | 上海掌门科技有限公司 | Meeting group merging method and device |
| WO2023035834A1 (en) * | 2021-09-10 | 2023-03-16 | 华为技术有限公司 | Wi-fi direct communication method and apparatus |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100411461C (en) | 2008-08-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1889722A (en) | PoC group session realizing method and apparatus | |
| CN1290354C (en) | Interconnecting and interflowing method for digital cluster system and common telephone system | |
| CN1658689A (en) | A cellular push-to-talk system | |
| CN101043252A (en) | Method and system for transmitting MBMS mechanism based IMS service | |
| US20120077536A1 (en) | Collaborative group communication method involving a context aware call jockey | |
| CN101047534A (en) | Method, device and system for customer active joining conference | |
| CN1893692A (en) | Method and apparatus for invited user in conversation obtaining group information | |
| CN1889609A (en) | Telephone conference realizing method | |
| CN100344095C (en) | Charge metering association and charge managing method for concentrated speech business | |
| CN1794675A (en) | Method of establishing instant data transmission channel to realize instant message transmission | |
| CN1852490A (en) | Method and system for group calling business | |
| EP2789124A1 (en) | Collaborative group communication method involving a context aware call jockey | |
| CN1794835A (en) | Method and system of controlling right of speak | |
| CN101047529A (en) | Media session data sending control method, control relation consultation method and control system | |
| CN1665324A (en) | Method for constructing press-and-speak communication linkage and press-and-speak customer unit and communication device thereof | |
| CN101043431A (en) | Method and system for shortening built-up time of multi-party communication service | |
| CN1856137A (en) | Method and system for determining centrally controlled server | |
| CN101057477A (en) | Method for dividing session of push to talk over cellular session and system thereof | |
| CN1848980A (en) | Method for determining voice right distributing mode and group communication system | |
| CN1581744A (en) | Method for providing multiple QOS for MBMS business | |
| CN1859636A (en) | System and method for realizing communication system intercommunication | |
| CN1801968A (en) | Method and system for realizing real-time speaking in cluster system | |
| CN1794833A (en) | Method and device of processing PoC speak request | |
| EP2299628B1 (en) | Method and system for managing the user floor and push to talk over cellular server | |
| CN1867108A (en) | POC service group member state informing process and apparatus |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20080813 Termination date: 20160720 |