WO2007019789A1 - A method for ending multi-party communication session and a server for implementing the method - Google Patents

Abstract

A method for ending multi-party communication session and a server for implementing the method, wherein the method includes during the multi-party communication session, after determining the condition of triggering ending of the multi-party communication session is met, and when the server determines that the predetermined condition of ending the man-machine interaction PoC session is met, ending the current PoC session, and releasing the participants’ session resources. The method and server of the present invention avoids the unreasonable state of the multi-party communication session that no human participates, and ends the multi-party communication session properly, as well as effectively prevents wasting of the session resource of multi-party communication system.

Description

 End multi-party communication method and server for implementing the method

 The present invention relates to multi-party communication techniques, and more particularly to a method of ending a multi-party communication session and a server implementing the method. Background of the invention

 A multi-party communication system based on the SIP protocol, such as a PoC (Push to Talk over Cellular) system and a multi-party conference system, and the corresponding multi-party communication session includes a PoC session, a conference session, and the like. . This is a brief introduction to the PoC session. In the PoC system, the PoC server is the main processing unit of the PoC service, and mainly includes: a PoC session processing module, a media distribution module, a conversation right control processing module, and an adaptation module of the user plane. A conversion module or the like of a different encoding protocol, wherein the PoC session processing module may be composed of a PoC session establishing module for establishing a PoC session, a PoC session ending module for ending the PoC session, and a PoC session control module for controlling the PoC session. Currently, in the PoC session related specification, when there is only one participant or no participant in the PoC session, the PoC server controls the end of the current session. Here, the PoC user terminal is a mobile terminal that supports the PoC service, and the like, the normal person participates in the PoC session through the PoC user terminal, and when the participant of the PoC session is the PoC user terminal, the participant is considered to be a non-machine; the PoC device terminal To a voice recording device or an intelligent computer system supporting a PoC service, when a participant of a PoC session is a PoC device terminal, the participant is considered to be a machine.

In a PoC session, in the case where the participant has both the person and the machine participating in the session at the same time, After the participants in the session exit the PoC session and the number of remaining participants is greater than one and both are machines, according to the existing PoC session related specifications, at this time, if no other PoC session termination conditions are set, the PoC server will not Proactively end the current PoC session. It can be seen that the prior art PoC system may be in the case where multiple participants participating in the PoC session are machines. From the perspective of PoC services provided for human users, this kind of PoC session without human participation is an unreasonable session state, and at the same time, because the session resources cannot be released, the resources of the PoC system are also wasted. The machine refers to a non-human participant.

 For example, four people A, B, C, and D have joined the PoC session and are in a normal conversation state. For some reason, C and D respectively switch the session to the voice recording device. At this time, the participants are two people: And B, two machines: C and D; A and B both quit the PoC session after the end of the PoC session, but the two voice recording devices C and D as the session participants did not get the information to exit the PoC session. Previously, it did not voluntarily quit the PoC session. This PoC session only preserves the session state of the machine, which is a session state that has no practical meaning for human users. At this time, the resources of the PoC session are not released, and the resources of the C and D are not released, resulting in waste of PoC system resources.

 For example, one of the four people A, B, C and D uses the user terminal, while the other three use the recording device. At this time, the PoC session is also in an unreasonable state, and the session can be set at this time. condition. Summary of the invention

 In view of this, it is a primary object of the present invention to provide a method of terminating a multiparty communication session that avoids unreasonable session state in a multiparty communication session while conserving multiparty communication session system resources.

Another object of the present invention is to provide two servers for implementing the above method for ending a multiparty communication session, which can reasonably end a multiparty communication session while properly controlling multiple parties. The session resource of the communication session system.

 To achieve the above object, the technical solution of the present invention is specifically implemented as follows: A method for ending a multiparty communication session, in a multiparty communication session, the method includes the following steps:

 When the server determines that the multi-party communication session end condition of the preset human-computer interaction is satisfied, the current multi-party communication session is ended, and the session resources of each participant in the current multi-party communication session are released.

 The method also includes:

 When the server determines that the multi-party communication session end condition of the preset human-computer interaction is not satisfied, the multi-party communication session is continued, and after waiting for the triggering end PoC session processing condition to be satisfied, the server re-determines whether the content is satisfied. The multi-party communication session end condition of the preset human-computer interaction.

 In the establishment of the multi-party communication session and/or the multi-party communication session, the server records the participant type of each participant, and the server determines whether the preset multi-party communication session end condition of the human-computer interaction is satisfied is: If so, the multi-party communication session end condition is satisfied; otherwise, the multi-party communication session end condition is not satisfied.

 In establishing a multi-party communication session and/or a multi-party communication session, the server records the participant type of each participant; the method for the server to determine whether the multi-party communication session termination condition of the preset human-computer interaction is satisfied is:

 a server determines whether the number of participants in the current multi-party communication session is less than or equal to one, and if so, satisfies the multi-party communication session end condition; otherwise, proceeds to step b;

b. The server determines, according to the type of participant of the record, whether the participant is If it is a machine, if yes, the multi-party communication session end condition is satisfied; otherwise, the multi-party communication session end condition is not satisfied.

 In establishing a multi-party communication session and/or a multi-party communication session, the server records the participant type of each participant, and records the number of each participant according to the participant type, and the server determines whether the preset human-computer interaction is satisfied. The method for ending the multiparty communication session is:

 Determining, by the server, whether the current number of non-machine participants is less than or equal to a server preset end number according to the number of non-machine participants of the record, and if yes, satisfying the multi-party communication session end condition; The multiparty communication session end condition is described.

 Before the ending the current multiparty communication session, the method further includes:

 Determining, by the server, whether the machine participant in the current multi-party communication session has an intelligent machine, and if yes, proceeding to continue the multi-party communication session, and after waiting for the triggering to end the PoC session processing condition, the server re-determines whether the server satisfies The preset multi-party communication session end condition of the human-machine interaction; otherwise, the session resources of each participant in the current multi-party communication session are released and then ended.

 The preset end number is one, or zero.

 The multiparty communication session end condition can be used in conjunction with an end condition of an existing multiparty communication session.

 The method for the server to record the participant type of each participant is: the server determines the value of the type identifier carried in the message sent by the participant to itself, and if the value indicates that the participant type is a machine type, the server records the server The participant type of the participant is a machine; if the value indicates that the participant type is a non-machine type, the server records that the participant's participant type is non-machine.

The method for the server to record the participant type of the participant is: the server determines the participation of the participant that does not carry the type identifier according to the type of the participant specified by the operator's policy or default value. The type of party. The message sent by the participant to the server is carried by the Session Initiation Protocol SIP message. The method further includes: setting an end condition of the current multiparty communication session;

 Before the server ends the current multi-party communication session, the method further includes: the server determining whether the current multi-party communication session end additional condition is met, and if not, continuing the multi-party communication session, waiting for the trigger to be satisfied After the processing condition of the PoC session is ended, the server re-determines whether the multi-party communication session end condition of the preset human-computer interaction is satisfied; if yes, the session resources of each participant in the current multi-party communication session are released, and the process ends.

 The method for setting the current multi-party communication session end attachment condition is: the participant, or the server administrator, or the operator is preset in the server.

 The method for setting an end condition of the current multiparty communication session is: the participating direction server sends a current multiparty communication session end attachment condition.

 The current multiparty communication session end extension is: a waiting time set by the non-machine participant to join or return to the multiparty communication session, or a timed end multiparty communication session, or a participant exiting the session.

 The method for the participating direction server to send the current multi-party communication session end condition is: the participant carries the current multi-party communication session end condition in the message that the user sends the setting information to the server, and sends the message to the server.

 The message for sending the setting information to the server is a SIP message.

 The SIP message is: a PUBLISH message, or an INVITE message, or a Re-INVITE message, or an UPDATE message, or a SUBSCRIBE message, or a REGISTER message.

 Each of the participants is in a multi-party communication session, and the method further includes:

 If the non-machine participant switches itself to the machine, or the machine participant is switched to a non-machine, the party to which the switch is switched will notify the server of its own participant type.

The method further includes: determining that the multi-party communication session processing condition that satisfies the trigger end; The triggering end multiparty communication session processing condition is: the participant having the multiparty communication session set by the operator in the server exits the current multiparty communication session, or the timing trigger ends the multiparty communication session processing, or the type of the participant changes. .

 The multi-party communication session is a push button of a cellular system, that is, a PoC session, or a multi-party conference session.

 A server includes a session establishing module, a session ending module, and a session control module, the server further comprising: a participant type detecting module for identifying a participant type of the multiparty communication session participant and a participant for storing the participant type Type storage module;

 The session establishing module is configured to establish a multi-party communication session, identify a participant type, send the identified participant type to the participant type storage module, and notify the session control module of the session establishment result information;

 The participant type storage module is configured to record the participant type of each participant;

 a session control module, configured to control a multiparty communication session, and notify the session end module to end the current multiparty communication session when the multiparty communication session end condition is met;

 a session end module, configured to: after receiving the notification of ending the multiparty communication session from the session control module, ending the current multiparty communication session and releasing the session resources of the participant; the participant type detection module, configured to receive the session from the session The detection request of the control module acquires the recorded participant type information from the participant type storage module, and determines the type of the participant according to the participant type information, and returns the determined participant type information to the session control module.

 The server further includes: a condition determining module for determining whether the server exists and satisfies the current multi-party communication session ending condition;

The session control module determines, after the current multi-party communication session end condition is met, if the information that the current multi-party communication session attachment condition is satisfied from the condition determination module is received, notifying the session end module to end the current multi-party communication session and releasing the participation Party conversation Resources; otherwise, continue the current multiparty communication session;

 The condition judging module is configured to send, to the session control module, information that ends the current multi-party communication session additional condition when the current condition exists and meets the current multi-party communication session end condition; or determines that the current multi-party communication session is not satisfied. When the condition is attached, information that the current multi-party communication session attachment condition is not satisfied is sent to the session control module.

 The multiparty communication session end condition is: the number of participants in the current multiparty communication session is less than or equal to one, or the participants in the current multiparty communication session are machines.

 The multi-party communication session is a PoC session of the cellular system, and the server is a PoC server;

 Alternatively, the multi-party communication session is a multi-party conference session, and the server is a conference server.

 A server includes a session establishment module, a session termination module, and a session control module, and the server further includes: a participant quantity recording module for recording the number of each participant type;

 The session establishing module is configured to establish a multi-party communication session, identify a participant type, send the identified participant type to the participant type storage module, and notify the session control module of the session establishment result information;

 The participant quantity recording module is configured to receive a participant type from the session establishment module and record the number of the participant in the participant type type;

 The session control module queries the information of the number of participants in the participant type record module, determines that the end of the multi-party communication session is satisfied, and notifies the session end module to end the current multi-party communication session;

The session end module is configured to, after receiving the notification of ending the multi-party communication session from the session control module, end the current multi-party communication session and release the session resources of the participant. The server further includes: a condition determining module configured to determine whether the server exists and satisfies an additional condition of the current multiparty communication session end;

 The session control module determines, after the current multi-party communication session end condition is met, if the information that the current multi-party communication session attachment condition is satisfied from the condition determination module is received, notifying the session end module to end the current multi-party communication session and releasing the participation Party session resources; otherwise, continue the current multiparty communication session;

 The condition judging module is configured to send, to the session control module, information that ends the current multi-party communication session additional condition when the current condition exists and meets the current multi-party communication session end condition; or determines that the current multi-party communication session is not satisfied. When the condition is attached, the multi-party communication session end condition that the end of the current multi-party communication session additional condition is not satisfied is sent to the session control module: the number of non-machine participants in the current multi-party communication session is less than or equal to the preset end number.

 The multi-party communication session is a key of a cellular system, that is, a PoC session, and the server is a PoC server;

 Or the multi-party communication session is a multi-party conference session, and the server is a conference server.

 It can be seen from the foregoing technical solution that, in the multi-party communication session, after determining that the multi-party communication session processing condition that satisfies the preset human-machine interaction is satisfied, the server determines whether the multi-party communication session end condition of the preset human-machine interaction is satisfied, and if yes, ends the current multi-party communication session, and Release the session resources of the participant; otherwise continue the current multiparty communication session and wait for the trigger to end the multiparty communication session processing condition. The multiparty communication session of the present invention includes a PoC session, a conference session, and the like.

The method for determining, by the server of the present invention, whether the multi-party communication session end condition of the preset human-computer interaction is met may be: distinguishing the type of the participant in the multi-party communication session according to the type identifier of the participant participating in the multi-party communication session, and recording the participant type In the server. such, When the participant type detecting module preset in the server detects that the participants in the multiparty communication session are all machines according to the participant type recorded in the server, the server determines that the multiparty communication session end condition is satisfied.

 The method for determining, by the server of the present invention, whether the multi-party communication session end condition of the preset human-computer interaction is satisfied may be: when the number of the multi-party communication session participants is greater than one, when the preset participant type detection module in the server is recorded on the server according to the The participant type detects that only one of the participants in the multiparty communication session is a non-machine participant, and the server determines that the multiparty communication session end condition is satisfied.

 The method for determining whether the server meets the termination condition of the multi-party communication session of the preset human-computer interaction may also be: Suppose that when the server records the participant type of the multi-party communication session participant, the non-machine whose participant type is non-machine is also recorded. The number of participants, and the number of presets. The server determines whether the current number of non-machine participants is less than or equal to the server preset end number according to the number of participants in the recorded non-machine type, and if so, determines that the multi-party communication session end condition is satisfied. The server of the multi-party communication session of the present invention includes

PoC server, Conference server, etc.

 The method of the present invention for ending a multiparty communication session when only a machine participant exists in a multiparty communication session may be used alone or in combination with a method of ending a multiparty communication session such as a session release policy.

 The method and server of the invention avoid the unreasonable multi-party communication session state without human participation, reasonably end the multi-party communication session, and effectively avoid waste of resources of the multi-party communication system. BRIEF DESCRIPTION OF THE DRAWINGS

Figure la is a schematic diagram of a composition of a PoC server in the PoC session system of the present invention; Figure lb is a schematic diagram of another composition of a PoC server in the PoC session system of the present invention; 2 is a flow chart of an embodiment of ending a PoC session in the PoC session system of the present invention; FIG. 3 is a flow chart of another embodiment of terminating a PoC session in the PoC session system of the present invention. Mode for carrying out the invention

 The core idea of the present invention is: in a multi-party communication session, determining that the server determines whether the multi-party communication session end condition of the preset human-machine interaction is satisfied after the triggering of the multi-party communication session processing condition is ended, and if yes, ending the current multi-party communication session, And releasing the session resources of the participant; otherwise, continuing the current multi-party communication session and waiting for the trigger to end the multi-party communication session processing condition. The server of the multiparty communication session of the present invention includes a PoC server, a Conference server, and the like.

 The present invention ensures a reasonable termination of the multiparty communication session while saving resources of the multiparty communication session system.

 In order to make the objects, technical solutions and advantages of the present invention more clear, the present invention will be further described in detail below with reference to the accompanying drawings, the PoC server in the PoC session and the PoC session system, and the preferred embodiment.

 Figure la is a schematic diagram of a PoC server in the PoC session system of the present invention. As shown in Figure la, in order to implement the method of the present invention, the PoC server includes a PoC session establishing module for establishing a PoC session and a PoC session for ending the PoC session. The PoC session end module and the PoC session control module for controlling the PoC session further include: a participant type detection module for identifying a participant type of the PoC session participant and a participant type storage for storing the participant type. Module

The PoC session establishing module is configured to receive a PoC session request, record the participant type of each participant, control the establishment of the PoC session, identify the participant type, and transmit the identified participant type to the participant type storage module, and Notifying the PoC session control module of the session establishment result information; Participant type storage module, used to record the type of participants of each participant after identification;

The PoC session control module is configured to notify the PoC session end module to end the current PoC session after determining that the number of participants existing in the current PoC session is less than or equal to one according to the group information stored by the PoC session. Or receiving information from the participant type returned by the participant type detecting module, determining that the participant in the current PoC session is a machine, and notifying the PoC session ending module to end the current PoC session;

a PoC session end module, configured to: after receiving the notification of the end PoC session from the PoC session control module, end the current PoC session and release the session resources of the participant; the participant type detection module, configured to receive the control from the PoC session The module's detection request acquires the recorded participant type information from the participant type storage module, determines the type of the participant, and determines the participant type according to the participant type information, and returns the determined participant type information to the PoC. Session control module.

 In addition, the PoC server may further include: a condition determining module configured to determine whether the PoC server exists and satisfies an additional condition of the current PoC session end;

 After the PoC session control module determines that the number of participants in the current PoC session is less than or equal to one, or determines that the participants in the current PoC session are all machines, the notification condition determination module performs a judgment operation and receives the PoC session processing module. After the current PoC session end conditional information from the condition judging module is satisfied, the PoC session end module is notified to end the current PoC session and release the session resources of the participant; or the PoC session processing module receives the current condition from the condition judging module. After the PoC session ends the information that the condition is not satisfied, the current PoC session is continued.

a condition judging module, configured to: when the current PoC session end condition is satisfied, is sent to the PoC session control module, and the current PoC session end condition is satisfied, or the current PoC session end condition is not satisfied, Sending information to the PoC session control module that the current PoC session attachment condition is not satisfied. In addition, in order to implement the method of the present invention, the PoC server may also be as shown in FIG. 1b, and FIG. 1b is another schematic diagram of the composition of the PoC server in the PoC session system of the present invention: in addition to including for establishing and identifying the participant type. a PoC session establishing module, a PoC session ending module for ending a PoC session, and a PoC session control module for controlling a PoC session, further comprising: a participant number recording module for recording the number of each participant type;

 The PoC session establishing module is configured to receive a PoC session request, establish a PoC session, and identify a participant type, or receive a type notification message in the PoC session to identify a participant type, and transmit the identified participant type to the participant. The party type recording module notifies the PoC session control module session establishment result information;

 a participant quantity recording module for receiving a participant type from the PoC session establishment module and recording the number of participants of the participant type type;

 The PoC session control module queries the information of the number of participants in the participant type record module, and determines that the number of non-machine participants in the participant in the current PoC session is less than or equal to the preset number of ends, and the notification PoC session end module ends. Current PoC session;

 The PoC session end module is configured to, after receiving the notification of the end PoC session from the PoC session control module, end the current PoC session and release the session resources of the participant.

 It should be noted that the PoC server component modules shown in Figures la and lb are only modules related to the present invention, and other existing modules of the PoC server are not shown in Figures la and lb.

Corresponding to the PoC server, when the server is a conference server, the conference server includes a conference session establishment module, a conference session control module, and a conference session control module, and includes a participant type detection module and a participant type storage module. Still further includes: a condition determination module. The functions of each module in the Conference server are the same as those of the corresponding modules in the PoC, except for the names. The Conference server also has two forms of diagrams la and lb, which will not be described in detail here. Before describing the method of ending the PoC session of the present invention, the process of establishing a PoC session is briefly described as follows:

 In order to establish a PoC session, a participant sends a session request message to the PoC server as a session initiation direction, such as a session establishment request (INVITE). The INVITE request includes related information of the participant, and is invited to join other participants of the PoC session. Information, etc., if the invited party can join the session normally, the acknowledgment message, such as a 200 OK response message, is sent to the participant who initiated the current PoC session through the PoC server. The PoC server stores the information of all parties participating in the PoC session locally, and manages and controls the established PoC session. The specific implementation process of establishing a PoC session can be found in the related PoC session related specifications, and will not be repeated here.

 It should be emphasized that the participant carries a type identifier indicating the machine in the Session Initiation Protocol (SIP) message, and the PoC server determines whether the invited party is a machine or not, according to the value of the type identifier of the machine, if the machine is represented. The value of the type identifier is true, that is, TURE, that is, indicating that the participant type is machine type, then the invited party is determined to be a machine; if the value of the type identifier of the machine is false, that is, FALSE, indicating that the participant type is For non-machine types, it is determined that the invited party is a non-machine. When the invited party is a machine, the machine carries a type identifier for indicating that it is a machine in a SIP message, such as a 200 OK response message, and the type identifier may be stored in an existing Contact field of the 200 OK response message, such as If the automata or PoC Box field in the Contact field is TRUE, it means that the sender of the SIP message is a machine. It should be noted here that there may be more than one type of identifier indicating whether the participant is a machine participant, such as recorder for recorder, Automata for auto answering machine, PoC Box for PoC service recording device, etc.

After receiving the 200 OK response message, the PoC server determines that the invited participant is a machine according to the value of the type identifier indicating the machine carried in the 200 OK response message, that is, TRUE, and the invited participant is Participant type with other users of the machine The information is correspondingly stored in the PoC server. When the session initiator is a machine, for example, the machine is scheduled to initiate an INVITE request to the PoC server at a certain time. At this time, the INVITE request carries a type identifier indicating that it is a machine. The type identifier can be stored in the existing Contact field of the INVITE request. After receiving the INVITE request, the PoC server determines the session initiator according to the value of the type identifier indicating the machine carried in the INVITE request, that is, TRUE. Is a machine, and stores the participant type of the session initiator with other user information of the machine in the PoC server; when the session initiator or the invited party is non-machine, the PoC server receives the INVITE request or the 200 OK response After the message, according to the INVITE request or the 200 OK response message carrying the identifier indicating the type of the participant, the value of the identifier is false, that is, false, and the session initiator or the invited party is determined to be non-machine, and the session initiator or the invited party is invited to participate. The participant type of the party is stored in the PoC server corresponding to the other user information of the non-machine.

For example, a non-machine participant initiates a PoC session and invites a machine to join the session. The implementation process includes: the non-machine participation direction PoC server initiates an INVITE request, because the initiator of the originating PoC session is non-machine, so the INVITE request can be The value of the carried type identifier is false, which means that the session participant is non-machine; after receiving the INVITE message, the PoC server controlling the session authenticates the session initiator, and according to the type identifier carried in the INVITE request The value determines that the participant type of the participant is non-machine, and records the participant type of the session initiator and the related information of the session initiator in the PoC server. According to the PoC session establishment procedure specified by the PoC session related specification, the INVITE request is sent to the invitee through the PoC server for controlling and managing the session; as the machine of the invitee, after receiving the INVITE request message, the returned 200 OK response message The contact field carries the type identifier of the value of the ture. After receiving the 200 OK response message of the PoC device terminal, the PoC server determines that the participant type of the participant is a machine according to the value of the type identifier carried in the 200 OK response message. And locally with the be The relevant information of the inviter correspondingly records the type of the party of the invited party.

 So far, when establishing a PoC session, the present invention records the participant types of the participating parties participating in the PoC session in the PoC server.

 It should be noted that, if the message that the participant requests to establish a POC session does not carry the type identifier indicating the machine, the POC server may determine whether the participant is a machine according to the type of the participant specified by the operator's policy or default value. Not machine.

 2 is a flowchart of an embodiment of ending a PoC session in the PoC session system of the present invention. It is assumed that the PoC server determines whether to end the current session according to the number of session participants and the type of the participant, and the PoC server is configured to identify The participant type detecting module of the participant type of the PoC session participant, the participants in the PoC session have established a PoC session and are in the PoC session. The ending the PoC session in the present invention specifically includes the following steps: Step 200 ~ Step 201: When the current PoC session is in progress, the PoC server determines whether the triggering end PoC session processing condition is met. If not, the process returns to step 200; otherwise, the process proceeds to step 202.

 The setting of the processing condition for triggering the PoC session may be set by the operator in the PoC server, and may be changed by the participant of the PoC session, for example, the participant withdraws from the current PoC session, or the type of the participant changes, such as switching from the machine to the non-party. The machine switches from non-machine to machine, etc.; it also triggers the PoC session processing flow and so on.

 Step 202: The PoC server determines whether the number of participants existing in the current PoC session is less than or equal to one, and if yes, proceeds to step 204; otherwise, proceeds to step 203.

The PoC server has a PoC session processing function, so the PoC server can determine whether the number of participants existing in the current PoC session is less than or equal to one according to the group information of the participating parties that have been stored in the PoC server. If there is no user or only one user in the group information, the PoC server determines that the number of participants in the current PoC session is less than or equal to one; if there is more than one user in the group information, the PoC server determines the current The number of participants in a PoC session is greater than one. For details, refer to the PoC session related specifications, which are not repeated here.

 In this step, if there is only one bit left in the PoC session participant, the PoC server will proceed to step 204 whether the party is a non-machine or a machine; or if no party exists. If there are more than one remaining PoC session participants, the PoC server proceeds to step 203 for further determination.

 Step 203: The PoC server determines whether the participants of the PoC session are all machines, and if yes, proceeds to step 204; otherwise, returns to step 200.

 The participant type detecting module in the PoC server judges the participants in the current PoC session according to the information recorded locally. If the participant type in the information of each participant shows that the participant is a machine type, the PoC server determines At this point, the participants of the PoC session are all machines; otherwise, it is determined that the participants of the PoC session are not all machines at this time, and the PoC session is continued.

 It should be noted here that the execution of step 202 and step 203 may be performed in no particular order. Step 204: The PoC server ends the current PoC session and releases the session resources of each participant. .

 The PoC server sends an end session message to each participant, such as a BYE message, ending the current PoC session and releasing the session resources of each participant.

 It should be noted that if a non-machine participant switches itself to a machine in a PoC session, or a machine participant is switched to a non-machine, the party to which the switch is switched will pass the type notification message of the participant type. For example, a SIP message, such as an INVITE message, a 200 OK response message, etc., may be used to notify the PoC server. For the specific implementation, refer to the existing related specifications, and details are not repeated herein.

In addition, it should be noted that, if the participant or the PoC server administrator or the operator is allowed to configure the current PoC session end additional bar on the PoC server before establishing the PoC session, Before the PoC server sends the end session message to each participant, the method further includes: Step 2031: The PoC server determines whether the current PoC session end attachment condition is preset. If not, the process proceeds to step 204; otherwise, Step 2032.

 Step 2032: The PoC server determines whether the preset current PoC session end condition is met. If not, the process returns to step 200. If yes, the process proceeds to step 204.

 In addition to configuring the current PoC session end attachment condition in the PoC server before establishing the PoC session, in the current PoC session, the participant may carry the current PoC session end attachment condition to the existing user for sending the setup information to the PoC server. The message is sent to the PoC server. Here, the message used by the user to send the setting information to the PoC server may be a SIP message, such as: a PUBLISH message, or an INVITE message, or a Re-INVITE message, or an UPDATE message, or a SUBSCRIBE message, or a REGISTER message.

 The current PoC session end preconditions preset in the PoC server include: the length of the waiting time for the participant to join or return the PoC session, the end of the PoC session, the end of the PoC session by a participant, and the end of the PoC session. For example, a non-machine participant presets the waiting time for joining or returning to a PoC session. That is, when the PoC server determines to end the current PoC session, the PoC server needs to wait for a set length of time. If the non-machine participant joins or returns the current PoC session, the PoC server determines that the preset current PoC session end condition is not satisfied; if the non-machine participant has not joined or returned the current PoC session within the set time length, The PoC server determines that the preset current PoC session end attachment condition is satisfied. In addition, the implementation of the condition for ending the PoC session and ending the PoC session by a participant to exit the session is similar to the above method, and will not be described in detail herein.

 It is easy to see from the above method for ending the PoC session of the present invention that the method of the present invention distinguishes the types of machines and non-machines participating in the PoC session by the type identification of the machines participating in the PoC session, and records the participant type of the participant in the PoC server. in. Exist in multiple participants

In the case of a PoC session, when the participant type detection module preset in the PoC server is based on When the participant type of each participant in the PoC server detects that the participants are all machines, the PoC server sends a message to the participants to end the PoC session, and ends the current PoC session and releases the session resources of each participant. The method avoids the unreasonable PoC session state in which no one participates, and reasonably ends the PoC session, and effectively avoids the waste of the session resources of the PoC system.

 In the flowchart shown in Fig. 2, the entry step 202 in steps 200 to 201 is changed to the step 203, so that the object of the present invention can be achieved as another method for ending the PoC session of the present invention.

 3 is a flow chart of another embodiment of ending a PoC session in a winter invented PoC session system. In a PoC session, it is assumed that when the PoC server records the participant type of the PoC session participant, the participant type is also recorded as non-machine. The number of non-machine participants, and the number of preset ends. After the PoC server determines that the processing condition of the triggering end PoC session is satisfied, the method includes the following two steps:: determining whether the current number of non-machine participants is less than or equal to the preset number of endings of the PoC server, and if yes, proceeding to step 301; otherwise, continuing After the current PoC session and waiting for the trigger to end the PoC session processing condition is satisfied, returning to step 300;

 Step 301: The PoC server ends the current PoC session, and releases the session resources of the participant.

 The preset number of terminations may be determined by an operator, an initiator of a PoC session, an administrator, or an Authenticated User authorized by an administrator, for example, the number of terminations is preset to one.

After the PoC server determines that the number of non-machine participants in the current PoC session is less than or equal to the preset number of ends, before the step 301, the method may further include: the PoC server further determining whether the machine participant in the current PoC session is It is a smart machine, such as a smart computer, and if so, returns to step 300, otherwise, proceeds to step 301. Here, a smart machine refers to a machine that can interact with non-machine participants such as a smart computer, a content server, and the like.

 The PoC server determines whether the machine participant in the current PoC session is an intelligent machine, and can be judged by the further additional function identification of the machine participant in the session. For example, a function identifier for indicating the function of the machine participant can be recorded in the PoC session, so that whether the machine participant is a smart machine or a non-intelligent machine, such as a machine participant corresponding to the function identification display, can be determined by the function identifier of the machine participant. In the case of a smart machine, the PoC server determines that the machine participant is an intelligent machine; the function identifier indicates that the corresponding machine participant is a non-intelligent machine, and the PoC server determines that the machine participant is a non-intelligent machine.

 At this time, if the participant or the PoC server administrator or the operator is allowed to configure the current PoC session end attachment condition on the PoC server before the PoC session is established, the PoC server determines whether the PoC server sends the end session message to each participant before the PoC server establishes the PoC server. The preset PoC session end is preset, if not preset, the process proceeds to step 301; otherwise, the PoC server further determines whether the preset current PoC session end condition is satisfied, and if not, returns to step 300; Then, the process proceeds to step 301.

 The foregoing embodiment is a specific embodiment of the three types of ending PoC sessions of the present invention. The process proceeds to step 204 or step 301 to indicate that the PoC session end condition is currently met; otherwise, the PoC session end condition is not met currently.

It should be noted that, in the present invention, when only the machine participant exists in the PoC session, or the number of the participant type is non-machine is less than or equal to the preset number of the PoC server, the method of ending the PoC session may be separately used as the ending PoC. The conditions of the session can also be used together as a condition for ending the PoC session, and can also be used in combination with the ending method of the existing PoC session as a reason for ending the PoC session. The method for ending the existing PoC session includes: a method of ending a PoC session when the PoC administrator issues an instruction to end the PoC session, a method of ending the PoC session when the last participant in the PoC session leaves, and when the PoC session initiator leaves Method for ending a PoC session, a method for ending a PoC session when a specified PoC participant leaves, a method for ending a PoC session when the number of participants is less than a certain value, and a method for ending a PoC session when an initiator of a session leaves a session A method of ending a PoC session when a preset time arrives or a method of ending a PoC session when there is no participant speaking within a preset time.

 The method for combining the PoC session end method may be to set multiple PoC session methods for one PoC session. As long as the reason for ending a PoC session is satisfied, the PoC session ends.

 The above is only the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modifications, equivalents, improvements, etc., which are made within the spirit and principles of the present invention, should be included. It is within the scope of the invention.

Claims

Claim A method of ending a multiparty communication session, characterized in that in a multiparty communication session, the method comprises the steps of:  When the server determines that the multi-party communication session end condition of the preset human-computer interaction is satisfied, the current multi-party communication session is ended, and the session resources of each participant in the current multi-party communication session are released.  2. The method of claim 1, wherein the method further comprises: continuing the multiparty communication session when the server determines that the multiparty communication session end condition of the preset human-computer interaction is not satisfied, After waiting to satisfy the triggering end PoC session processing condition, the server re-determines whether the multi-party communication session end condition of the preset human-machine interaction is satisfied.  The method according to claim 1, wherein in establishing a multiparty communication session and/or in a multiparty communication session, the server records a participant type of each participant, and the server determines whether the preset person is satisfied. The method of ending the multi-party communication session of the machine interaction is...  The server determines, according to the type of participant of the record, whether each of the participants is a machine, and if so, satisfies the multi-party communication session end condition; otherwise, the multi-party communication session end condition is not satisfied.  4. The method according to claim 1, wherein, in establishing a multiparty communication session and/or in a multiparty communication session, the server records a participant type of each participant; the server determines whether the preset is satisfied. The method for ending the multi-party communication session of human-computer interaction is: a. the server determines whether the number of participants existing in the current multi-party communication session is less than or equal to one, and if yes, satisfies the multi-party communication session end condition; otherwise, enters Step b;  b. The server determines, according to the type of participant of the record, whether the participants are all machines, and if so, satisfies the multi-party communication session end condition; otherwise, the multi-party communication session end condition is not satisfied.  The method according to claim 1, wherein in establishing a multi-party communication session and/or in a multi-party communication session, the server records the participant type of each participant, and records each participant according to the participant type. The number of the server, the method for determining whether the multi-party communication session end condition of the preset human-computer interaction is satisfied is:  Determining, by the server, whether the current number of non-machine participants is less than or equal to a server preset end number according to the number of non-machine participants of the record, and if yes, satisfying the multi-party communication session end condition; The multiparty communication session end condition is described.  The method according to claim 5, wherein before the ending the current multi-party communication session, the method further comprises:  Determining, by the server, whether the machine participant in the current multi-party communication session has an intelligent machine, and if so, the financial entry continues to the multi-party communication session, and after waiting for the triggering to end the PoC session processing condition, the server re-determines whether the server satisfies The preset multi-party communication session end condition of the human-machine interaction; otherwise, the session resources of each participant in the current multi-party communication session are released and then ended.  The method according to claim 5, wherein the preset end number is one, or zero.  8. The method of claim 1, wherein the multiparty communication session end condition can be used in conjunction with an end condition of an existing multiparty communication session. The method according to claim 3, 4 or 5, wherein the method for the server to record the participant type of each participant is: the server determines the type identifier carried in the message sent by the participant to itself Value, if the value indicates that the participant type is machine class Type, the server records the participant type of the participant as a machine; if the value indicates that the participant type is a non-machine type, the server records that the participant's participant type is non-machine.  The method according to claim 3, 4 or 5, wherein the method for the server to record the participant type of the participant is: the server pairs the participant that does not carry the type identifier, and the operator The type of the party specified by the policy or default value determines the type of the party. '  The method according to claim 9, wherein the message sent by the participant to the server is carried by a Session Initiation Protocol SIP message.  12. The method according to claim 3, 4 or 5, characterized in that the method further comprises: setting an end condition of the current multiparty communication session;  Before the server ends the current multi-party communication session, the method further includes: the server determining whether the current multi-party communication session end additional condition is met, and if not, continuing the multi-party communication session, waiting for the trigger to be satisfied After the processing condition of the PoC session is ended, the server re-determines whether the multi-party communication session end condition of the preset human-computer interaction is satisfied; if yes, the session resources of each participant in the current multi-party communication session are released, and the process ends.  The method according to claim 12, wherein the setting of the current multi-party communication session end attachment condition is: the participant, or the server administrator, or the operator is previously set in the server.  The method according to claim 12, wherein the setting of the current multi-party communication session end condition is: the participating direction server sends a current multi-party communication session end condition. 15. The method according to claim 13, wherein the current multiparty communication session end addition condition is: a waiting time length of joining or returning a multiparty communication session set by a non-machine participant, or ending a multiparty communication session at a time, Or a participant exits the session. The method according to claim 14, wherein the method for the participation direction server to send the current multiparty communication session end condition is: the participant carries the current multiparty communication session end condition to be carried by the user for sending to the server. Set the message to the message and send it to the server.  The method according to claim 16, wherein the message for sending the setting information to the server is a SIP message.  The method according to claim 17, wherein the SIP message is: a PUBLISH message, or an INVITE message, or a Re-INVITE message, or an UPDATE message, or a SUBSCRIBE message, or a REGISTER message.  The method according to claim 3, 4 or 5, wherein the participants are in a multi-party communication session, the method further comprising:  If the non-machine participant switches itself to the machine, or the machine participant is switched to a non-machine, the party to which the switch is switched will notify the server of its own participant type.  The method according to claim 1, wherein the method further comprises: determining that the multi-party communication session processing condition that satisfies the trigger end is determined;  The triggering end multiparty communication session processing condition is: the participant having the multiparty communication session set by the operator in the server exits the current multiparty communication session, or the timing trigger ends the multiparty communication session processing, or the type of the participant changes. .  21. The method according to claim 1, wherein the multi-party communication session is a cellular system, a PoC session, or a multi-party conference session.  The server according to claim 1, wherein the multi-party communication session is a push button of a cellular system, that is, a PoC session, and the server is a PoC server; or the multi-party communication session is a multi-party conference conference session. The server is a conference server. 23. A server, including a session establishment module, a session termination module, and session control a module, the server further comprising: a participant type detection module for identifying a participant type of the multiparty communication session participant and a participant type storage module for storing the participant type;  The session establishing module is configured to establish a multi-party communication session, identify a participant type, send the identified participant type to the participant type storage module, and notify the session control module of the session establishment result information;  The participant type storage module is configured to record the participant type of each participant;  a session control module, configured to control a multiparty communication session, and notify the session end module to end the current multiparty communication session when the multiparty communication session end condition is met;  a session end module, configured to: after receiving the notification of ending the multiparty communication session from the session control module, ending the current multiparty communication session and releasing the session resources of the participant; the participant type detection module, configured to receive the session from the session The detection request of the control module acquires the recorded participant type information from the participant type storage module, and determines the type of the participant according to the participant type information, and returns the determined participant type information to the session control module.  The server according to claim 23, wherein the server further comprises: a condition determining module for determining whether the server exists and satisfies the current multi-party communication session ending condition;  The session control module determines, after the current multi-party communication session end condition is met, if the information that the current multi-party communication session attachment condition is satisfied from the condition determination module is received, notifying the session end module to end the current multi-party communication session and releasing the participation Party session resources; otherwise, continue the current multiparty communication session; The condition judging module is configured to send, to the session control module, information that ends the current multi-party communication session additional condition when the current condition exists and meets the current multi-party communication session end condition; or determines that the current multi-party communication session is not satisfied. Additional conditions Sending a message to the session control module that ends the current multiparty communication session with an unsatisfactory condition.  The server according to claim 23 or 24, wherein the multi-party communication session end condition is: the number of participants in the current multi-party communication session is less than or equal to one, or the participants in the current multi-party communication session are machines .  The server according to claim 23, wherein the multi-party communication session is a push button of a cellular system, that is, a PoC session, and the server is a PoC server; or the multi-party communication session is a multi-party conference conference session, The server is a conference server.  27. A server, comprising a session establishing module, a session ending module, and a session control module, wherein the server further comprises: a participant number recording module for recording the number of each participant type;  The session establishing module is configured to establish a multi-party communication session, identify a participant type, send the identified participant type to the participant type storage module, and notify the session control module of the session establishment result information;  The participant quantity recording module is configured to receive a participant type from the session establishment module and record the number of the participant in the participant type type;  The session control module queries the information of the number of participants in the participant type record module, determines that the end of the multi-party communication session is satisfied, and notifies the session end module to end the current multi-party communication session;  The session end module is configured to, after receiving the notification of ending the multiparty communication session from the session control module, end the current multiparty communication session and release the session resources of the participant. The server according to claim 27, wherein the server further comprises: a condition determining module for determining whether the server exists and satisfies the current multi-party communication session end adding condition; After the session control module determines that the current multi-party communication session end condition is met, if the information that the current multi-party communication session attachment condition is satisfied from the condition determination module is received, the session bundle module is notified to end the current multi-party communication session and release the participation. Party session resources; otherwise, continue the current multiparty communication session;  The condition judging module is configured to send, to the session control module, information that ends the current multi-party communication session additional condition when the current condition exists and meets the current multi-party communication session end condition; or determines that the current multi-party communication session is not satisfied. When the condition is attached, the station control module sends a station that terminates the current multiparty communication session with an unsatisfactory condition.  The server according to claim 27 or 28, wherein the multi-party communication session end condition is: the number of non-machine participants in the current multi-party communication session is less than or equal to the preset end number.  The server according to claim 27, wherein the multi-party communication session is a key of a cellular system, that is, a PoC session, and the server is a PoC server; or the multi-party communication session is a multi-party conference conference session, The server is a conference server.