WO2009092242A1

WO2009092242A1 - A method for implementing sub-conference, a method, an apparatus and a terminal device for implementing private conference

Info

Publication number: WO2009092242A1
Application number: PCT/CN2008/073580
Authority: WO
Inventors: Cheng Huang; Guojun Xu; Lunjian Mu; Jue Wang; Yonggang Bian; Gang Liang; Yongjing Zhang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-12-27
Filing date: 2008-12-18
Publication date: 2009-07-30
Also published as: CN101471806A

Abstract

A method for implementing sub-conference, a method, an apparatus and a terminal device for implementing private conference are provided. The invention belongs to the communication technique field. The method for implementing sub-conference includes that: acquiring the state information of the main conference, determining the participating state of each participant in the sub-conference according to the state information of the main conference acquired, sending the session content of the sub-conference or the session content of the main conference and the session content of the sub-conference to each participant in the sub-conference according to the participating state of each participant in the sub-conference. The method perfects the existing scheme for implementing sub-conference. Another method for implementing sub-conference includes that: receiving the request for creating sub-conference, using the conference control focus of the main conference as the control focus of the sub-conference to create the sub-conference. The method provides a new technical scheme for implementing sub-conference.

Description

Sub-conference implementation method, private conference implementation method, device and terminal device

Technical field

The present invention relates to the field of network communication technologies, and specifically relates to a method for implementing a conference, a device for implementing a conference, a method for implementing a private conference, a device for implementing a private conference, and a terminal device. Background of the invention

The IP Multimedia Subsystem (IMS) uses the Session Initiated Protocol (SIP) to implement call and signaling control functions. The conference users who participate in the multimedia conference and the multimedia conference server implement the session function of the multimedia conference through SIP and other protocols cooperated with the SIP.

In the multimedia conference, the application scenario in which the main conference and the sub-conference can coexist can occur. For example, the participant user wants to perform a Sidebar or Sub-Conference with the designated user at the same time as the current conference. A private conference is called a sub-conference. The current conference is called a primary conference. The designated user can be a participant in the main conference or a participant in the non-main conference.

During the sub-conference, the original main conference participant in the sub-conference can receive the conversation content of the main conference. In order to protect the privacy of the sub-conference, the participants who do not join the sub-conference in the main conference are generally not allowed to obtain the conversation content of the sub-conference.

Currently, the technical solution for implementing a sub-conference is as follows: The conference server receives a sub-conference creation request of a participant in the main conference, and the conference server allocates resources, creates a sub-conference instance, and returns a sub-conference identifier. Sub-meeting session media type negotiation, sub-conference user invitation, and other sub-conference activation actions are also performed. The conference server selects two Conference Focuss, which are relatively independent of resource allocation, in the management of the conference instance to implement the main conference, the sub-conference creation, and the conference session control respectively, that is, the main conference instance corresponds to the Main Conference Focus in the conference server. (Primary Conference Control Center), the sub-conference instance corresponds to the Sidebar Focus in the conference server. The Main Conference Focus interacts with the main conference participant through the main conference session, and the Sidebar Focus interacts with the sub-session conference user through the sub-conference session. The primary conference session and the conference session are two separate conference sessions.

When the sub-meeting is activated, the conference server invites the main conference control center to join the sub-conference, so that after receiving the main conference session content transmitted by the Main Conference Focus, the Sidebar Focus mixes the main conference session content and the sub-conference session content, and The conference participant user sends the content of the conversation after the remix, so that the sub-conference participant can receive both the main conference session content and the sub-conference session content.

In the process of implementing the present invention, the inventor finds that: although the above technical solution implements a sub-meeting, since the main conference session content can only be received by the main conference participant user, only all the participating users in the sub-conference are simultaneously The main conference session is allowed to output to the sub-conference when the main conference participates in the user; otherwise, Sidebar Focus cannot distribute the session content. That is to say, when a non-main conference participant participates in a sub-conference, the output of the main conference session content to the sub-conference cannot be realized, or when the Sidebar Focus has received the main conference session input (that is, the current sub-conference participants) At the same time, the new non-main conference participants can not accept the sub-conference. Moreover, the above technical solution does not consider the control problem of the main sub-conference session after the sub-conference is completed. For example, when the participating user in the sub-conference is also the main conference participant, the main conference session content cannot be implemented to the participant user. Output control. In addition, the technical solution does not consider how the participant user continues to receive the sub-conference session after switching from the sub-conference to the main conference, and the release of the sub-conference session before the termination of the main conference.

On the other hand, since the main and sub-conference control centers in the existing sub-conference implementation technical solutions are independent of each other, The terminal device used by the participating users of the sub-conference must establish and maintain separate conference sessions with the primary and secondary conference control centers. In practical applications, not all terminal devices have parallel session capabilities, which may result in some participating users not being able to participate in the primary conference at the same time. Summary of the invention

The embodiments of the present invention provide a sub-conference implementation method, a private conference implementation method, an apparatus, and a terminal device, which improve the existing sub-meeting implementation mechanism and improve the flexibility of implementing the sub-conference.

A method for implementing a sub-conference provided by an embodiment of the present invention includes:

Obtain primary conference status information;

Determining, according to the obtained main conference status information, a participation status of each participating user in the sub-conference;

The sub-conference session content is sent to each sub-conference participant according to the participation status of each participating user in the sub-conference, or the main conference session content and the sub-conference session content are sent.

The embodiment of the present invention further provides another seed conference implementation method, including:

After the conference server receives the sub-conference creation request, the conference control center of the main conference performs the operation of establishing the sub-conference as the sub-conference control center to establish the sub-conference.

The embodiment of the invention further provides a method for implementing a private conference, including:

The private conference session sent by the receiving user occupies the conference session channel request;

The conference control center forwards the content of the private conference session sent by the participant user received from the conference session channel according to the received private conference session user identifier carried in the request.

Embodiments of the present invention also provide another method for implementing a private conference, including:

Receiving a private conference session request sent by the participant user; the request carries the participant user information of the participating private conference; the conference control center establishes and participates with the existing conference session with the participating user participating in the private conference. Private conference session channel between participating users of private conferences;

The conference control center receives and sends the private conference session content by using the private conference session channel.

An embodiment of the present invention further provides a sub-conference implementation apparatus, including:

An obtaining module, configured to obtain primary conference status information;

Determining a status module, configured to determine, according to the main conference status information acquired by the acquiring module, a participation status of each participating user in the sub-conference;

The first control module sends the sub-conference session content to the sub-conference participants according to the participation status of each participating user in the sub-conference, or sends the main conference session content and the sub-conference session content.

The embodiment of the present invention further provides another seed conference implementation apparatus, including:

Receiving a creation request module, and receiving a sub-conference creation request;

And a second creating module, configured to use the conference control center of the primary conference as the sub-conference control center to establish a sub-conference according to the sub-conference creation request.

The embodiment of the invention further provides a terminal device, including:

a session establishment module, establishing a conference session with the conference control center;

a second interaction module, configured to use a conference session between the conference control center and the conference user to interact with the conference control center; and the second interaction module controls the conference session to be used when the conference user participates in the conference Main conference session, in the conference The second interaction module controls the conference session to be used as a conference session when the user participates in the conference.

An embodiment of the present invention further provides a private conference implementation apparatus, including:

a fourth receiving requesting module, configured to receive a conference session channel request by the private conference session sent by the participant user, and a sixth control module, configured to forward the participant user according to the received private conference session user identifier carried in the request The content of the private meeting session sent.

The embodiment of the present invention further provides another private conference implementation apparatus, including:

The fifth receiving request module is configured to receive a private conference session request sent by the participant user, where the request carries the information of the participant user participating in the private conference;

Establishing a session channel module, configured to establish a private conference session channel between the participating users participating in the private conference by using the existing conference session with the participating users participating in the private conference;

The seventh control module sends the content of the private conference session received from the private conference session channel through the private conference session channel.

According to the description of the foregoing technical solution, the main conference and the sub-meeting are associated by using the main conference state information, so that when the session content is sent to the participating users in the sub-conference, the control content of the session content can be realized, thereby avoiding The non-main conference participant can not join the sub-conference, the sub-conference can not send the session content when there is a non-main conference participant, and the existing sub-conference implementation mechanism is improved; the main conference and the sub-conference are reused by the main conference. The conference control center avoids the process of setting up the independent sub-conference control center, and can also enable the participating users to participate in the main conference and the sub-conference at the same time when the terminal device used by the participating user does not have the parallel conversation capability; The technical solution provided by the embodiments of the present invention improves the flexibility of implementing a sub-meeting. BRIEF DESCRIPTION OF THE DRAWINGS

1 is a schematic diagram of an implementation manner of a sub-conference according to Embodiment 1 of the present invention;

2 is a flowchart of creating a sub-conference according to Embodiment 1 of the present invention;

3 is a flowchart of receiving a main conference session by a sub-conference participant in the first embodiment of the present invention;

4 is a flowchart of receiving a sub-conference session by a primary conference participant user according to Embodiment 1 of the present invention;

5 is a flowchart of a conference in which a participant who participates in a primary and a secondary conference exits the main conference and releases the conference before the termination of the main conference according to the first embodiment of the present invention;

6 is a schematic diagram of an implementation manner of a sub-conference according to Embodiment 2 of the present invention;

7 is a flowchart of creating a sub-conference according to Embodiment 2 of the present invention;

FIG. 8 is a flowchart of a primary and sub-conference session sending control according to Embodiment 2 of the present invention; FIG.

9 is a flowchart of receiving control of a primary and a secondary conference session according to Embodiment 2 of the present invention;

10 is a flowchart of a conference in which a participant who participates in a primary and a secondary conference simultaneously withdraws from the primary conference and releases the conference before the termination of the primary conference according to the second embodiment of the present invention;

11 is a schematic flowchart 1 of a method for implementing a private conference according to an embodiment of the present invention;

12 is a second schematic flowchart of a private conference implementation manner according to an embodiment of the present invention;

13 is a first schematic diagram of a sub-meeting implementation apparatus according to an embodiment of the present invention;

FIG. 14 is a second schematic diagram of a sub-conference implementation apparatus according to an embodiment of the present invention. Mode for carrying out the invention

The present invention can implement a sub-conference by two different embodiments, one embodiment of implementing a sub-conference is: creating an independent sub-conference control center, and utilizing the basis of a main conference session and a sub-conference session that are mutually parallel The main conference and the sub-meeting are associated with the main conference status information, so as to perform the distribution control of the main conference session content in the sub-conference, and the sub-conference with the termination of the main conference, and the like; another implementation of the sub-conference For example: Reusing the main conference control center, using the main conference session to simultaneously provide the sub-conference function for the sub-conference participants of the main conference participant, or using the main conference session as the sub-conference participant of the main conference participant user. The participating users who participate in the sub-conference only provide the sub-conference function; that is, the main main conference control center is used to simultaneously control the main conference session and the sub-conference session.

The embodiments of the above two implementation sub-conferences are respectively described below.

Embodiment 1: On the basis of utilizing the main conference session and the sub-conference session which are mutually parallel, the association of the main conference and the sub-meetage is realized through the pre-acquired main conference state information; thus, in the subsequent sub-conference implementation process, The main conference and the sub-meeting are related to each other, and therefore, the sub-conference session control can be conveniently implemented.

In the first embodiment, the sub-conference control center needs to obtain the main conference status information. The sub-conference control center can obtain the status information of the main conference by means of subscription. Of course, the main conference control center can also actively transmit the main conference status information to the sub-conference control center periodically or irregularly, where the irregular transmission is as the main conference. Transmission when status information changes. The main conference status information may include: a list of main conference participants. The main conference status information may further include one or two items of the main conference session media type, the main conference control policy, and the like, including the main conference participant user list. The main conference status information may contain: The content of the current main conference status information. The content of the main conference status information can be determined according to the actual application. The foregoing primary conference control policy may include: one or more of information such as whether the primary conference is locked, that is, whether the primary conference allows the new user to participate, and the duration of the speech of a participating user. The content of the main conference control policy can also be: The content of the existing master conference control strategy. Moreover, the content of the main conference control strategy can be determined according to the actual application. Sub-Conference The Control Center can subscribe to the main conference status information during the sub-conference process, or subscribe to the main conference status information after the sub-conference is successfully created. The embodiment of the present invention does not limit the specific content included in the main conference state information and the main conference control policy, nor the specific implementation manner of the sub-conference control center acquiring the main conference state information, and the timing of subscribing to the main conference state information.

For the sub-conference control center, the main conference status information can be used to determine the participation status of each participating user in the sub-conference, that is, the main conference status information can be used to determine whether the participating users in the sub-conference are participating in the sub-conference. Also participated in the main meeting. That is to say, the use of the main conference status information can help the sub-conference control center to determine whether the participating users in the sub-conference participate in the sub-meeting or participate in the main sub-conference.

The sub-conference in the first embodiment may be a sub-meeting established according to the conference control policy. The process of establishing a sub-conference according to the conference control policy may be: The conference server receives the sub-conference creation request sent by the main conference participant user. The primary conference participant user can submit the conference conference creation request to the conference server through the conference resource access mechanism supported by the conference server; for example, the primary conference participant user submits the conference conference creation request to the conference server through the conference access portal (entry). For another example, the primary conference participant submits the child conference creation request to the conference server through the Remote Assistance application of the secondary conference application parameter settings. The embodiment of the present invention does not limit the specific implementation process of the primary conference participant user to send the conference conference creation request.

The sub-conference creation request may carry a primary conference identifier, a sub-conference topic information, a sub-conference participant user list information, a sub-conference session media type, and a sub-conference control policy. The sub-conference control policy may include: whether the sub-conference receives the main conference session content, whether the sub-conference allows non-main conference participants to participate in the sub-conference, and the like. The information carried in the above sub-conference creation request can also pass Multiple messages are transmitted to the conference server. The embodiment of the present invention does not limit the specific content of the information carried in the sub-conference creation request, the specific content of the sub-conference control policy, and the transmission manner of each of the foregoing information.

After receiving the sub-conference creation request, the conference server obtains the conference control policy, where the conference control policy is different from the foregoing sub-conference control policy, where the conference control policy is used to determine whether to allow the sub-conference to be created. The conference control policy may be a primary conference control policy. For example, the conference server obtains the primary conference control policy from the Main Conference Focus. Of course, the conference server may also obtain a conference control policy for determining whether to allow the sub-meetage to be created from other network devices.

After the conference server determines that the sub-conference is allowed to be created by using the conference control policy (such as the main conference control policy), the sub-conference subsequent operation is performed to create the sub-conference. The creation operation here may include: allocating resources required for implementing the sub-conference function, notifying the main conference participation user sub-conference creation of the sub-conference creation request, and the like. The resources required to implement the sub-conference function may include: creating a Sidebar Focus corresponding to the sub-conference instance, and a sidebar Focus establishing a media transmission channel for the sub-conference of the sub-conference participants. The creation operation here can adopt various existing sub-conference creation operations, and the embodiment of the present invention does not limit the processing procedures specifically included in the creation operation.

After the sub-conference is successfully established through the above operations, the sub-conference session and the main conference session are two parallel conference sessions, that is, the main conference instance corresponds to the Main Conference Focus, the sub-conference instance corresponds to the Sidebar Focus, and the Main Conference Focus passes the main conference session and the main conference. The conference participant interacts with the content of the main conference session, and the Sidebar Focus interacts with the child conference session user through the sub-conference session. The main conference participant who interacts with the Main Conference Focus can participate in: the participant who participates in the main conference only; or the participants who participate in the main conference and participate in the main conference and sub-conference at the same time. user. The sub-master conference participants who interact with the Sidebar Focus sub-conference session can be: participants who only participate in the sub-conference; or: participants who only participate in the sub-conference, and participants who participate in the main conference and sub-conference at the same time Will be the user.

In the first embodiment, the content of the main conference session sent by the main conference participant can pass the Main Conference Focus,

The Sidebar Focus is transmitted to the sub-conferences of the sub-conferences and the sub-conferences of the main conference participants. The main conference conversations sent by the sub-conference participants of the sub-conferences are also available through Sidebar Focus, Main Conference. Focus is transferred to the main conference participant in the main conference.

When a sub-conference participant in a sub-conference is also required to receive the main conference session content, Sidebar Focus can invite Main Conference Focus to join the sub-conference. The Sidebar Focus invites the Main Conference Focus to join the sub-conference when it receives the primary conference session request from the sub-conference participants of the primary conference participant user for the first time. Of course, Sidebar Focus can also invite Main Conference Focus to join the sub-conference in other situations. For example, when the sub-conference control policy includes allowing the sub-conference to receive the main conference session content, Sidebar Focus invites the Main Conference Focus force after the sub-conference is successfully created. Into the sub-conference.

After the Main Conference Focus session, Main Conference Focus can send the mixed main conference session content to Sidebar Focus, but does not receive the sub-conference session content, that is, Main Conference Focus as a virtual only send (Send only) The participating users participate in the sub-conference, that is, the Main Conference Focus to Sidebar Focus's main conference session channel (ie media transmission channel) can be a one-way channel.

After receiving the content of the main conference session, the Sidebar Focus is responsible for controlling the distribution of the main conference session content in the sub-conference, so as to ensure that only the participating users having the receiving authority can receive the main conference session content in the sub-conference. The Sidebar Focus can send the main conference session content to the sub-conference participants of the main conference participant user according to the main conference participation user list information in the main conference status information, and the Sidebar Focus can also participate in the conference according to the main conference participant user. List information, receiving a main conference session request to a sub-conference The sub-conference participants of the main conference participants will send the main conference session content. The Sidebar Focus can also receive the main conference session request from the main conference and stop receiving the main conference session request. The sub-conference participants send the main conference session content. The Sidebar Focus can also send the main conference session content to the sub-conference participants of the main conference participant user in the sub-conference according to the main conference participation user list information, the reception main conference session request, and the stop receiving the main conference session request.

The receiving the main conference session request in the embodiment of the present invention may carry the main conference identifier, so as to indicate that the sub-conference participant user who is the main conference participant user in the sub-conference needs to receive the main conference session content. The situation in which the Sidebar Focus sends the content of the main conference session to the sub-conference participants of the conference user in the sub-conference may include the following exemplary methods:

Example 1. If Sidebar Focus determines, according to the sub-conference control policy, that the sub-conference participants who are the main conference participants in the sub-conference are allowed to receive the main conference session content, Sidebar Focus can directly obtain the main content obtained from the Main Conference Focus. The conference participant user list information determines the sub-conference participant users who are the main conference participant users in the sub-conference, and sends the received main conference session content to all the sub-conferences at the same time as the main conference participant user. Conference participants.

Example 2: When Sidebar Focus determines, according to the sub-conference control policy, that the sub-conference participant who is the main conference participant user receives the main conference session content in the prohibited sub-conference, if Sidebar Focus receives the sub-conference participant, the user sends After receiving the main conference session request, Sidebar Focus can determine the sub-conference participant who needs to receive the main conference session according to the receiving main conference session request. If Sidebar Focus determines that the sub-conference participant who needs to receive the main conference session content is also the main conference participant based on the main conference participant user list information obtained from the Main Conference Focus, the Bay IJSidebar Focus can receive the determined need. The sub-conference participant of the main conference session sends the content of the main conference session. Otherwise, the Sidebar Focus does not send the content of the main conference session to the sub-conference participant who needs to receive the content of the main conference session. The participant who needs to receive the content of the main conference session may be the participant who sends the conference request to receive the conference session, or the participant who needs to receive the conference session indicated in the conference session request. That is to say, when a sub-conference participant in a sub-conference is required to receive the content of the main conference session, the user can send and receive the main conference session request; or the other sub-conference participants can send and receive on behalf of the user. The primary conference session request, and the received primary conference session request carries the specified at least one sub-conference participant user, and the designated sub-conference participant user may include: a child in the sub-conference that is simultaneously the main conference participant user Conference participants.

Example 3: When Sidebar Focus determines, according to the sub-conference control policy, that the sub-conference participant who is the main conference participant user in the sub-conference is allowed to receive the content of the main conference session, if the Sidebar Focus receives the sub-conference participant, the user sends After receiving the main conference session request, Sidebar Focus can determine the sub-conference participants who need to stop receiving the main conference session according to the stop receiving the main conference session request; Sidebar Focus no longer needs to stop receiving the conference session content. The participating user sends the content of the main conference session, and the Sidebar Focus collects the user conference list information obtained from the Main Conference Focus, and the other conferences other than the participant users who need to stop receiving the content of the main conference session. The sub-conference participants of the participating users send the content of the main conference session. The sub-conference participant who needs to stop receiving the main conference session may be a sub-conference participant who sends a request to stop receiving the main conference session, or may stop receiving the sub-conference indicated in the main conference session request and need to stop receiving the main conference session. Conference participants. That is to say, when a sub-conference participant in a sub-conference is required to stop receiving the main conference session content, the user may send a request to stop receiving the main conference session; or the other sub-conference participants may The sending and receiving of the main conference session request is stopped, and the receiving of the main conference session request carries the specified at least one sub-conference participant user, and the designated sub-conference participant user may include: The sub-conference participates in the user. After receiving the request to stop receiving the main conference session, the Sidebar Focus can determine whether the sub-conference participant who needs to stop receiving the content of the main conference session is the main conference participant user, and judges that the sub-conference participant user is at the same time After the conference is attended to the user, the content of the main conference session is stopped from being sent to the participant. Of course, Sidebar Focus can also not perform the judging process, that is, regardless of whether the sub-conference participant receives the main conference session content before, the main conference session content is not sent to the sub-conference participant; Sidebar Focus directly according to the main conference The user list information is sent to the sub-conference participants of the sub-conference participants who are also the main conference participants, except for the sub-conference participants who need to stop receiving the main conference session. That is to say, the content of the main conference session not sent to the sub-conference participant user includes two aspects: First, in the case that the sub-conference participant receives the content of the main conference session, the sending to the participant user is stopped. The content of the main conference session, and the second is that the conference user does not receive the content of the main conference session, and the content of the main conference session is still not sent to the conference user.

After receiving the request to stop receiving the main conference session, the Sidebar Focus can make the following judgments: All the sub-conference participants who receive the content of the main conference session in the sub-conference stop receiving the content of the main conference session, if it is determined that all the sub-conferences are determined The sub-conference participants who receive the main conference session stop receiving the main conference session content, then Sidebar Focus sends a request to the Main Conference Focus to request the Main Conference Focus to exit the sub-conference. After receiving the request, the Main Conference Focus releases the Main. The main conference session between Conference Focus and Sidebar Focus.

In the first embodiment, the sub-conference user who is the main conference participant in the sub-conference can select to switch back to the main conference as needed. At the same time, the sub-conference participants of the main conference participants can send a handover request to the Sidebar Focus to switch back to the main conference. After the sub-conference participant of the main conference participant user switches back to the main conference, the conference participant user can still request to receive the sub-conference session content. At this time, the sub-conference session content needs to be transmitted from Sidebar Focus. Go to the Main Conference Focus and transfer from the Main Conference Focus to the main conference participant. To create a sub-conference session from Sidebar Focus to Main Conference Focus, Main Conference Focus can invite Sidebar Focus to the main conference. The embodiment of the present invention can update the one-way main conference session channel from Main Conference Focus to Sidebar Focus to a two-way conference session channel, or re-establish a single/bidirectional sub-conference session channel from Sidebar Focus to Main Conference Focus, such as re-establishment. One-way sub-conference session channel from Sidebar Focus to Main Conference Focus.

After Sidebar Focus joins the main conference, Sidebar Focus can send the remixed sub-conference session content to Main Conference Focus, and Sidebar Focus can receive the main conference session content or not. After receiving the content of the sub-conference session, the Main Conference Focus is responsible for controlling the distribution of the sub-conference session content in the main conference participant to ensure that only the main conference participant having the receiving authority can receive the sub-conference session content in the main conference. The primary conference participant with the receiving permission may include: a primary conference participant who switches back to the primary conference, and a primary conference participant who does not perform the handover but requests to receive the conference session content.

The Main Conference Focus can send the sub-conference session content to the main conference participant user who needs to receive the sub-conference session content in the main conference according to the acquired sub-conference status information (such as the sub-conference participation user list information), such as switching back to the main conference. The main conference participant user sends the sub-conference session content. The Main Conference Focus can send the sub-conference session content to the main conference participant who switches back to the main conference according to the sub-conference participation user list information and the receiving sub-conference session request, and the Main Conference Focus can also receive the user list information according to the sub-conference. The sub-conference session request, the stop receiving the sub-conference session request, and the sub-conference session content are sent to the main conference participant user who switches back to the main conference. The specific example of the case where the above-mentioned Main Conference Focus sends the content of the sub-conference session to the main conference participant user who switches back to the main conference is the same as the above-mentioned Sidebar Focus-to-sub-conference. The sub-conference participants of the conference user are similar to the content of the main conference session. The differences include: The sub-conference identifier is carried in the sub-conference session request, and the sub-conference identifier is also carried in the request to stop receiving the sub-conference session. The specific example of sending the content of the sub-conference session to the main conference participant who switched back to the main conference will not be described in detail here.

The main conference participant can request to leave the main conference. After receiving the main conference request from the main conference participant, the main conference focus releases the main conference session with the main conference participant user. The release of the main conference session includes: releasing the main conference session channel. The Main Conference Focus can also send the main conference session content to the participant after receiving the main conference request from the conference participant. Moreover, Main Conference Focus can also notify Sidebar Focus of the information that the main conference participant exits the main conference after receiving the exit main conference request of the main conference participant, that is, Main Conference Focus sends the main conference status information change to Sidebar Focus. Notice. In this way, in the case that the primary conference participant receives the conference session in the conference, the Sidebar Focus can only send the conference conference content to the conference user according to the notification.

In addition, after receiving the main conference request of the main conference participant, the Main Conference Focus may determine whether all the main conference participants have logged out of the main conference. If all the main conference participants quit the main conference, The Main Conference Focus can request termination of the sub-conference, such as sending sub-conference termination indication information to Sidebar Focus, and after receiving the sub-conference termination indication information, Sidebar Focus releases the sub-conference session with each sub-conference participant user. The conference session between Main Conference Focus and Sidebar Focus also needs to be released. After each conference session is released, Main Conference Focus terminates the main conference.

Sub-conference participants can request to exit the sub-conference. After receiving the exit sub-conference request of the sub-conference participant, the Sidebar Focus no longer sends the sub-conference session content to the sub-conference participant, releases the sub-conference session with the sub-conference participant, and releases the sub-conference session. Includes: Releases the sub-conference session channel.

As can be seen from the description of the first embodiment, on the conference instance management layer of the conference server, the primary conference and the secondary conference are respectively controlled by two conference control centers whose resource allocation is relatively independent, that is, the primary conference session and the conference session. For two separate conference sessions. The participating users use the main conference session when participating in the main conference, and use the sub-meeting session when participating in the conference, that is, the participant needs to have the SIP parallel session capability. In the life cycle of the main conference instance, the technical solution provided in the first embodiment can perform primary and secondary conference association control on the primary conference and the conference. The primary conference association control may include: controlling the creation of the conference using the primary conference control policy; When there is a non-main conference participant user, the distribution of the main conference session content in the sub-conference is controlled; in the sub-conference, the sub-conference participant user who is the main conference participant user returns to the main conference, and controls the main conference participation. Continue to receive the content of the sub-conference session; when the participant who participates in the main sub-meeting exits the main conference, control the content of the main conference session is not distributed to the conference user; before the termination of the main conference, the end control of all the sub-conferences under the main conference Wait. Thus, the first embodiment improves the existing sub-meeting implementation mechanism.

The implementation of the first embodiment of the sub-conference will be described in detail below with reference to the accompanying drawings.

1 is a schematic diagram of an implementation sub-meeting of the first embodiment.

In Fig. 1, the participating users of the terminal 1, the terminal 2, and the terminal 3 are performing the main conference, and the participating users of the terminal 4 do not participate in the main conference, but participate in the conference.

Any participant in the participant user 1, the participant user 2, and the participant user 3 can create a sub-meeting through the terminal request. The conference server can determine whether to allow the sub-conference to be created according to the main conference control policy. After the sub-conference is created and successfully created, the participating users 1, the participating users 2, and the participating users 3 use the terminal to conduct the main conference through the main conference session, the participating users 1, the participating users 3, and the participating users. 4 Using the terminal, the sub-conference is performed through the sub-conference session. Sidebar Focus for the sub-conference instance Need to obtain the main conference status information, S idebar Focus can control the sub-conference session associated with the main conference according to the main conference status information.

2 is a flowchart of a sub-conference creation according to an embodiment of the present invention.

In FIG. 2, UE1, UE2, UE3, and UE4 respectively represent terminal devices used by participating users. The UE1, the UE2, and the UE3 are the terminal devices used by the first primary conference participant, that is, the conference users using the UE1, UE2, and UE3 participate in the multi-party multimedia conference under the host conference Conference Main Conference Focus, and use UE1, UE2. The conference sessions between the participants of UE3 and Main Conference Focus are Dialog1, Dialog2, and Dialog3 respectively _{. The} users who use UE4 are non-main conference participants, and the participants of UE4 and UE1 and UE3 participate. Users join the sub-conferences together. For the sake of brevity, in the following description, the information transmitted by the participating users through the terminal device is briefly described as transmitting information to UE1, UE2, UE3, and UE4.

Step 1. During the main conference, UE1 sends a sub-session creation request to the conference server. The sub-conference creation request can be submitted to the conference server through the conference resource access mechanism supported by the conference server. For example, the sub-conference creation request is submitted to the conference server through a conference access or a remote assistant that assists the conference application parameter setting. The sub-conference creation request carries a main conference identifier, a sub-conference topic, a sub-conference participant user list, a sub-conference session media type, a sub-conference control policy, and the like. The sub-conference control policy, such as whether the sub-conference participant is allowed to receive the main conference session content, whether to allow non-main conference participants to participate in the sub-conference, and the like.

Step 2. After receiving the sub-conference creation request, the conference server requests the main conference control policy from the Main Conference Focus. Step 3. The Main Conference Focus returns the main conference control policy to the conference server. If the primary conference is a predefined conference, the primary conference control policy may be recorded in the definition document of the predefined conference; if the primary conference is a temporary conference, the primary conference control policy may be a default control policy set by the operator.

Step 4: The conference server determines whether to accept the sub-conference creation request according to the main conference control policy. If the sub-conference creation request is accepted, the conference server performs the subsequent operations of creating the sub-conference, such as creating a resource allocation such as Sidebar Focus corresponding to the sub-conference instance. Operation, then go to step 5; If the sub-conference creation request is not accepted, the sub-conference creation process ends, and the conference server can return to UE1 the response information for stopping the creation of the sub-conference.

Step 5: After the conference is successfully created, the conference server returns the response information of the successful sub-conference creation to UE1.

Step 6. The conference server sends a sub-conference creation success notification to the Main Conference Focus.

Step 7. After receiving the sub-conference creation success notification, the Main Conference Focus returns a response message to the conference server. Step 8. Sidebar Focus sends a main conference status information subscription request to Main Conference Focus.

Step 9. After receiving the main conference status information subscription request, Main Conference Focus returns a response message to Sidebar Focus.

Step 10. Main Conference Focus sends an initial notification to Sidebar Focus.

Step 11. The Sidebar Focus obtains the main conference status information such as the main conference participant list from the initial notification received. Step 12: After receiving the response information that the sub-conference is successfully created, the UE1 sends a sub-meeting activation request to the Sidebar Focus. Step 13. The Sidebar Focus returns a response message to the UE1 after receiving the sub-meeting activation request.

Step 14. After receiving the response information, the UE1 returns an acknowledgement message to the Sidebar Focus, and successfully establishes a sub-conference session Dialog1 ' between the UE1 and the Sidebar Focus.

Step 15: The Sidebar Focus sends an invitation to the UE3 to join the sub-conference request according to the sub-conference participant user list, to invite the UE3 to join the sub-conference.

Step 16. After receiving the request, the UE3 returns a response message to the Sidebar Focus. Step 17, after receiving the response information, the Sidebar Focus returns an acknowledgement message to the UE3, and successfully establishes a sub-conference session Dialog3' between the UE3 and the Sidebar Focus.

Step 18: The Sidebar Focus sends an invitation to the UE4 to join the sub-conference request according to the sub-conference participant user list, to invite the UE4 to join the sub-conference.

Step 19. After receiving the request, the UE4 returns a response message to the Sidebar Focus.

Step 20: After receiving the response information, the Sidebar Focus returns an acknowledgement message to the UE4, and successfully establishes a sub-conference session Dialog4 between the UE4 and the Sidebar Focus.

It should be noted that, in the foregoing description of the process in FIG. 2, the step numbers do not represent the sequence of operations performed. For example, step 5 and step 6 may be performed simultaneously, or may be reversed in sequence; for example, step 18 may be performed first. Go to step 20, and then perform steps 15 through 17 and so on.

FIG. 3 is a flowchart of a main conference session content and a sub-conference session content transmission control according to an embodiment of the present invention.

In Figure 3, the main conference participants still want to receive the main conference session after they choose to participate in the sub-conference. S idebar Focus invites the Main Conference Focus to the sub-conference, and the Main Conference Focus only sends the remixed master to the Sidebar Focus. The content of the conference session, Main Conference Focus does not receive the content of the sub-conference session, that is, the Main Conference Focus participates in the sub-conference as a virtual conference user who does not receive the video. After receiving the content of the main conference session, S idebar Focus controls the content of the main conference session to be distributed in the sub-conference to ensure that the sub-conference participants in the sub-conference can receive the content of the main conference session. In addition, when the sub-conference participant who is the main conference participant user returns to the main conference in the sub-conference, the conference user can choose to continue to receive the sub-conference session content.

UE1, UE2, and UE3 in Figure 3 are the main conference participants participating in the multi-party multimedia conference hosted by the Main Conference Focus. During the main conference, UE1 and UE3 participate in the sub-conference with UE4. For other primary conference participants in the primary conference, such as UE2, UE1 and UE3 are still in the primary conference. Moreover, UE1 and UE3 may choose whether to continue to receive the content of the main conference when participating in the sub-conference. UE4 is a sub-conference participating user who only participates in the sub-conference, and UE4 has no right to receive the main conference session content. The main conference sessions between UE1, UE2, UE3 and Main Conference Focus are Dialog1, Dialog2, and Dialog3. The sub-conference sessions between UE1, UE3, UE4 and Sidebar Focus are Dialogl ', Dialog3', and Dialog4, respectively. Assume that the sub-conference creation policy default setting information includes: It is prohibited to receive the main conference session content in the sub-conference of the sub-conference user who is the main conference participant user.

Step 1. During the process of the sub-conference, UE1 wants to receive the content of the main conference session, and UE1 sends a request to receive the main conference session to Sidebar Focus in the conference server. The Request URI in the receiving main conference session request is the sub-conference identifier, the "See-To" header field value is the primary conference identifier, the "method" parameter value is "INVITE", and the "a" attribute value is "recvonly". The content included in a specific receiving main conference session request may be in the following form:

REFER s ip : sub_conference@example. com SIP/2. 0

Via : SIP/2. 0/UDP agenta. example, com; branch=z9hG4bK2293940223

To : <s ip: sub conf erence@. example. com>

From : <s ip : userl@example. com>; tag=193402342

CaU- ID : 898234234@agenta. example, com

CSeq : 93809823 REFER

Max-Forwards: 70

Refer-To: main_conference@example. com; method= INVITE; a=recvonly Contact: sip: userl@example. com

Content-Length : 0

Step 2: After receiving the request to receive the primary conference session sent by the UE1, the Sidebar Focus determines the UE1 as the conference participant user according to the primary conference participant list information obtained by subscribing to the conference conference status information, and returns the response information to the UE1. .

Step 3. The Sidebar Focus sends an invitation to the Main Conference Focus to join the sub-conference request to request the Main Conference Focus to participate in the sub-meeting as the virtual participant of the Sendonly. For example, the direction attribute sent in the MIME SDP message body as the session media negotiation in the invite primary conference session sent by the Sidebar Focus to the sub-conference request is set to "a=recvonly".

Step 4. After receiving the invitation main conference session to join the sub-conference request, Main Conference Focus returns the response information to Sidebar Focus. The response information returned by Main Conference Focus may include a description of the media parameters of the main conference session.

Step 5. After receiving the response message, Sidebar Focus returns a confirmation message to Main Conference Focus. The one-way media transmission channel from Main Conference Focus to Sidebar Focus was successfully established. After that, Sidebar Focus can control the distribution of the main conference session content in the sub-conference according to the subscribed main conference participant list, so as to ensure that the sub-conference participants of the main conference participant can receive the main conference. The content of the session, and the non-main conference participants in the sub-conference cannot receive the content of the main conference session, and can only receive the content of the sub-conference session.

Step 6. UE2 uses Dialog2 to send the main conference session content to Main Conference Focus.

Step 7. After receiving the content of the main conference session, the Main Conference Focus returns the received response information to the UE2. Step 8. The Main Conference Focus sends the received main conference session content to UE1 through Dialog1. It should be noted here that UE1 can be implemented through the control of the terminal side: the main conference session content sent from the Main Conference Focus received from Dialog1 is not played, and the conference session content sent from Sidebar Focus received from Dialogl ' Playback processing.

Step 9. After receiving the content of the main conference session, UE1 returns a response message to Main Conference Focus.

Step 10: Main Conference Focus sends the received main conference session content to UE3 through Dialog3. Similarly, it should be noted here that: UE3 can be implemented through the control of the terminal side: the main conference session content sent from the Main Conference Focus received from Dialog3 is not played, and the conference sent from Sidebar Focus received from Dialog3' The session content is played and processed.

Step 11. After receiving the content of the main conference session, the UE3 returns a response message to the Main Conference Focus.

Step 12. Main Conference Focus uses its one-way media transmission channel with Sidebar Focus to the Sidebar.

Focus sends the received main conference session content.

Step 13. After receiving the content of the main conference session, Sidebar Focus returns a response message to Main Conference Focus. Step 14. UE4 sends the sub-conference session content to Sidebar Focus through Dialog4.

Step 15. Sidebar Focus sends a response message to UE4 via Dialog4.

Step 16. UE1 sends the sub-conference session content to Sidebar Focus through Dialogl'.

Step 17. Sidebar Focus sends a response message to UE1 via Dialogl '.

Step 18: Sidebar Focus mixes the content of the main sub-conference session received in steps 12, 14 and 16 and sends the content of the main sub-conference session to the UE3 through Dialog3'.

Step 19: After receiving the content of the main sub-conference session, UE3 returns a response message to Sidebar Focus. Step 20: The Sidebar Focus sends the content of the main sub-conference session after the mixing to the UE1 through Dialog1.

Step 21: After receiving the content of the main sub-conference session, UE1 returns a response message to Sidebar Focus.

Step 22. Sidebar Focus sends the sub-conference session content to UE4 through Dialog4.

Step 23: After receiving the content of the sub-conference session, the UE4 returns a response message to the Sidebar Focus.

In addition, if UE1 wants to stop receiving the main conference session, UE1 can also send a stop to receive the main conference session request through Diall' to Sidebar Focus, and the Request URI in the request can be set as the sub-conference identifier, where: "Refer-To" header field The value is the primary conference ID to be invited, and the "method" parameter value is "BYE". The Sidebar Focus determines, according to the received stop receiving primary conference session request, that UE1 and UE3 do not need to receive the primary conference session, and then send a SIP BYE message to the Main Conference Focus to request the Main Conference Focus to exit the conference. After receiving the SIP BYE message, Main Conference Focus returns the SIP 200 OK response message to Sidebar Focus, releasing the main conference session between Main Conference Focus and Sidebar Focus, such as releasing the Media Conference Focus to Sidebar Focus media transmission channel.

It should be noted that, in the foregoing description of the process for FIG. 3, the step numbers do not represent the sequence of operations performed. For example, step 8, step 10, and step 12 may be performed simultaneously, or may be reversed in sequence; for example, step 14 Step 16 may be performed simultaneously, or may be performed simultaneously with step 6, and step 18, step 20, step 22 may be performed simultaneously, and the like.

FIG. 4 is a flow chart of the main conference session content and the sub-conference session content transmission control after the conference user switches back to the main conference according to the embodiment of the present invention.

In Figure 4, step 24, using the participant user of UE1 to switch back to the main conference from the sub-meeting, but still wants to continue receiving the content of the sub-conference session, UE1 sends a receiving sub-conference session request to the Main Conference Focus in the conference server through Dialog1.

Step 25. The Main Conference Focus returns a response message to the UE1.

Step 26. The Main Conference Focus sends an invitation sub-conference session to the Sidebar Focus to join the main conference request to request Sidebar Focus to participate in the main conference.

Step 27. After receiving the request, Sidebar Focus returns a response message to Main Conference Focus.

Step 28: After receiving the response message, Main Conference Focus sends a confirmation message to Sidebar Focus, thereby successfully establishing a sub-conference session of Sidebar Focus to Main Conference Focus, such as establishing a media transmission channel of Sidebar Focus to Main Conference Focus, so that Sidebar Focus can send sub-conference session content to the Main Conference Focus. The successfully established media transmission channel can be implemented in two ways: One is to update the existing Main Conference Focus to Sidebar Focus's one-way media transmission channel, so that the one-way media transmission channel becomes a two-way media transmission channel; One is to renegotiate a one-way or two-way media transmission channel that is only applicable to sub-conference session content transmission.

Step 29. UE4 sends the sub-conference session content to Sidebar Focus through Dialog4.

Step 30: After receiving the content of the sub-conference session, the Sidebar Focus returns a response message to the UE4.

Step 31: Sidebar Focus forwards the received sub-conference session content to Main Conference Focus. Step 32: Main Conference Focus returns response information to Sidebar Focus.

Step 33: The UE2 sends the content of the main conference session to the Main Conference Focus through Dialog2.

Step 34: The Main Conference Focus sends a response message to the UE2.

Step 35: The UE1 sends the main conference session content to the Main Conference Focus through Dialog1.

Step 36: The Main Conference Focus sends a response message to the UE1. Step 37: The Main Conference Focus forwards the received main conference session content to the Sidebar Focus. Step 38: After receiving the main conference session content sent by the Main Conference Focus, the Sidebar Focus returns the response information to the Main Conference Focus.

Step 39: The Main Conference Focus mixes the received main conference session content and the sub-conference session content through Dialog1 and sends it to UE1.

Step 40: After receiving the content of the main sub-conference session after the mixing, UE1 returns a response message to Main Conference Focus.

Step 41: The Main Conference Focus sends the received main conference session content to UE2 through Dialog2.

Step 42: After receiving the content of the main conference session, UE2 returns a response message to Main Conference Focus.

Step 43: Sidebar Focus sends the received main conference session content and the sub-conference session content to UE1 through Dialogl '. It should be noted here that UE1 can be implemented through the control of the terminal side: the main sub-conference session sent from the Sidebar Focus received from Dialog1 is not played, and the main sub-conference session sent from the Main Conference Focus received from Dialog1 The content (ie, the content of the main sub-conference session received in step 41) is played.

Step 44: After receiving the content of the main sub-conference session after the mixing, the UE1 sends a response message to the Sidebar Focus.

Step 45: Sidebar Focus sends the content of the mixed main sub-conference session to UE3 through Dialog3'.

Step 46: After receiving the content of the main sub-conference session after the mixing, the UE3 sends a response message to the Sidebar Focus.

In addition, when the UE1 does not wish to receive the content of the sub-conference session, the UE1 may send a request to the Main Conference Focus to stop receiving the sub-conference call to terminate the receiving of the sub-conference session. After confirming that all the main conference participants have stopped receiving the sub-conference session content, Main Conference Focus can release the Sidebar Focus to the Main Conference Focus sub-conference session, such as the one-way media transmission channel that releases Sidebar Focus to Main Conference Focus.

It should be noted that, in the foregoing description of the process in FIG. 4, the step numbers do not represent the sequence of operations performed. For example, step 29, step 33, and step 35 in FIG. 4 may be performed simultaneously, or may be reversed in sequence; For example, step 39, step 41, step 43, step 45 can be performed simultaneously.

FIG. 5 is a flowchart of an exit main conference and a main sub-meeting termination according to an embodiment of the present invention.

In FIG. 5, UE1, UE2, UE3 and Main Conference Focus implement a main conference session through Dialog1, Dialog2, and Dialog3, and UE1, UE3, UE4, and Sidebar Focus implement a sub-conference session through Dialogl ', Dialog3, and Dialog4. Moreover, Main Conference Focus participates as a virtual conference user in a sub-conference under the auspices of Sidebar Focus.

Step 1. UE3 sends a request to the Main Conference Focus to exit the main conference through Dialog3.

Step 2. The Main Conference Focus returns a response message to the UE3. Main Conference Focus releases Dialog3 between UE3 and Main Conference Focus, and UE3 successfully exits the main conference.

Step 3. Main Conference Focus sends a notification of the main conference participant change to Sidebar Focus to inform Sidebar Focus that UE3 has exited the main conference.

Step 4. After receiving the notification of the user change of the main conference, Sidebar Focus returns the response information to Main Conference Focus.

Step 5. UE2 sends the main conference session content to Main Conference Focus through Dialog2.

Step 6. The Main Conference Focus returns a response message to the UE2.

Step 7. Main Conference Focus forwards the received main conference session content to UE1 through Dialog1. Step 8. UE1 returns a response message to the Main Conference Focus.

Step 9. UE4 sends the sub-conference session content to Sidebar Focus through Dialog4.

Step 10. The Sidebar Focus returns a response message to the UE4.

Step 11. Main Conference Focus forwards the main conference session content to Sidebar Focus using the media transfer channel with Sidebar Focus.

Step 12. Sidebar Focus sends a response message to Main Conference Focus.

Step 13. Since the UE3 has exited the main conference, the Sidebar Focus receives the content of the main conference session, but only transmits the sub-conference session content to the UE3 through Dialog3'.

Step 14. After receiving the content of the sub-conference session, UE3 returns a response message to Sidebar Focus.

Step 15. After receiving the content of the main conference session, the Sidebar Focus passes the user list information according to the main conference.

Dialogl 'sends the content of the main sub-conference session after mixing to UE1.

Step 16. After receiving the content of the main sub-conference session after the mixing, the UE1 returns a response message to the Sidebar Focus.

Step 17. Since UE4 only participates in the sub-conference session, although Sidebar Focus receives the content of the main conference session, it only transmits the sub-conference session content to UE4 through Dialog4.

Step 18: After receiving the content of the sub-conference session, UE4 returns a response message to Sidebar Focus.

Step 19. UE2 sends a request to the Main Conference Focus to exit the main conference.

Step 20: After receiving the request to exit the main conference, the Main Conference Focus sends a response message to the UE2, and the conference server releases the media transmission channel Dialog2 between the UE2 and the Main Conference Focus, and the UE2 successfully exits the main conference session.

Step 21: UE1 sends an exit main conference request to Main Conference Focus through Dialog1.

Step 22: Because UE1 is the last primary conference participant in the primary conference, the exit primary conference request sent by UE1 triggers the process of terminating the primary conference. Before terminating the main conference, all sub-conferences under the main conference must be terminated. Therefore, the Main Conference Focus sends a sub-conference termination to the Sidebar Focus.

Step 23: Sidebar Focus sends an exit sub-conference request to UE1 through Dialog1' to instruct UE1 to exit the sub-conference. Step 24: After receiving the request to exit the sub-conference, UE1 returns a response message to Sidebar Focus.

Step 25. The Sidebar Focus sends an exit sub-conference request to the UE3 through Dialog3' to instruct the UE3 to exit the sub-conference. Step 26: After receiving the request to exit the sub-conference, the UE3 returns a response message to the Sidebar Focus.

Step 27: The Sidebar Focus sends an exit sub-meeting request to the UE4 through the Dialog4 to instruct the UE4 to exit the sub-conference. Step 28: After receiving the request to exit the sub-conference, the UE4 returns a response message to the Sidebar Focus.

Step 29. The Sidebar Focus sends a sub-meeting termination response to the Main Conference Focus.

Step 30: The Main Conference Focus returns the main conference termination response information to the UE1. The main sub-conference instance is all terminated. It should be noted that, in the foregoing description of the process in FIG. 5, the step numbers do not represent the sequence of operations performed. For example, step 7, step 9, and step 11 in FIG. 5 may be performed simultaneously, or may be reversed in sequence; For example, Step 13, Step 15, and Step 17 may be performed simultaneously, or may be reversed in sequence; and, Step 23, Step 25, and Step 27 may be performed simultaneously, or may be reversed in sequence, and the like.

Embodiment 2: Reusing the conference control center of the main conference.

The conference control center of the existing main conference realizes the main conference for the participants who participate only in the main conference, the sub-meeting for the participants who participate only in the sub-conference, and the main conference and the sub-conference for the participants who participate in the main sub-conference. , that is, using the meeting of the main meeting The control center controls the main conference session and the sub-meeting session at the same time. At the SIP session level, the main conference and the sub-conference reuse the conference session.

In the second embodiment, the sub-conference may have a sub-conference identifier, but the sub-conference identifier is an alias of the main conference identifier. Subconference IDs such as Sub-conference URIs. After the main conference participant participates in the sub-conference, the conference session between the conference user and the conference control center of the main conference (referred to as the conference control center in the following description) can be used as the main conference session or as a child. Meeting session.

The sub-conference creation process in the second embodiment may be: The conference server receives the sub-conference creation request sent by the main conference participant user. The primary conference participant can submit the sub-conference creation request to the conference server through the conference resource access mechanism supported by the conference server. For example, the conference participant user submits the conference conference creation request to the conference server through the conference access portal, for example, The main conference participant user submits the sub-conference creation request to the conference server through the remote assistant of the auxiliary conference application parameter setting. The implementation of the present invention does not limit the specific implementation process of the primary conference participant user to send the conference conference creation request.

The sub-conference creation request may carry the main conference identifier, the sub-conference topic information, the sub-conference participation user list information, and the sub-conference session media type. The sub-conference creation policy may also optionally carry a sub-conference control policy. Of course, the sub-conference control policy may also be preset in the conference server. The sub-conference control policy may include: whether to allow the participating users who participate in the main conference sub-conference to receive the main conference session content, whether to allow the non-main conference participant to participate in the sub-conference, and the like. The information carried in the above sub-conference creation request can also be transmitted to the conference server through multiple messages. The embodiment of the present invention does not limit the specific content of the carried information in the sub-conference creation request, the specific content of the sub-conference control policy, and the transmission manner of each of the foregoing information.

After receiving the sub-conference creation request, the conference server can directly perform the sub-conference creation operation or determine whether to perform the sub-conference creation operation according to the conference control policy. The conference control policy is different from the foregoing conference control policy. The conference control policy is used to determine whether to allow sub-conferences to be created. The conference control policy may be a primary conference control policy. In the case of adopting the conference control policy, the conference server first obtains the conference control policy. For example, the conference server obtains the primary conference control policy from the conference focus center. Of course, the conference server may also obtain the conference server from other network devices. Determine whether to allow the creation of a conference control policy for a sub-conference. After the conference server determines that the sub-conference is allowed to be created by using the conference control policy, the sub-conference is established by reusing the conference control center, that is, the conference conference corresponding to the sub-conference instance is not required to be created, and the main conference session channel and the sub-conference session channel can be reused. Some conference session channels (that is, the main conference session channel and the sub-meeting session channel share the same conference session channel), and the main conference session channel and the sub-conference session channel may also be independent conference session channels. In the case where the main sub-conference session media type is the same The main conference session channel and the sub-conference session channel may be reused in a conference session channel or in a separate conference session channel. In the case that the media types of the primary and secondary conference sessions are different, the primary conference session channel and the conference session are configured. Channels need to be independent of each other's conference session channels.

After a sub-conference is successfully created, the sub-conference session is only a logical session for the participating users who participate in the main and sub-conferences. The sub-conference session and the main conference session are not two parallel sessions, but are reused. The session, that is, the main conference instance corresponding to the Conference Focus ^ sub-conference instance also corresponds to the Conference Focus. Conference Focus interacts with the main conference participants and sub-conference participants through the reused conference session.

The Conference Focus can interact with the main conference session user and the main conference session content through the main conference session, and the Conference Focus can perform the sub-conference session content and/or the sub-conference conference user through the sub-conference session and/or The interaction of the main meeting session content. That is to say, the Conference Focus uses the conference session with each participating user to interact with the participating users participating in the main conference and the sub-conference, and the conference session is used as the main conference session when the participant user participates in the main conference. Used as a sub-conference session when participating users participate in a sub-conference. When a conference session is used as the primary conference session, it does not mean that the conference user can receive only the content of the conference session through the primary conference session. In the actual application, the participant can receive the content of the conference session through the conference session, or receive the conference session. Go to the sub-conference session content, or receive the main conference session content and sub-conference session content. Similarly, when a conference session is used as a sub-conference session, it does not mean that the participant user can only receive the sub-conference session content, and the participant user can receive the sub-conference session content through the sub-conference session, or receive the main conference session content, Or receive the main conference session content and the sub-conference session content.

In the case that Conference Focus uses the re-used conference session to interact with the main conference participant user and the sub-conference participant user for the main conference session content and the sub-conference session content, the control signaling may be used to distinguish the conference user from sending. Main meeting session content, sub-conference session content, and more. For example, when the participant needs to send the content of the main conference session, the conference session request carrying the primary conference identifier may be sent to notify the conference focus: the conference session content sent by the conference user is the content of the conference session. The participating user then sends the main conference session content to the Conference Focus. When the participant needs to send the content of the main conference session, the conference user may also add a primary conference identifier different from the conference conference identifier in the content of the main conference session that is sent, and the conference focus may first resolve the conference identifier information in the content of the conference session. And determining, according to the parsed conference identification information, whether the content of the received conference session is the content of the main conference session or the content of the conference session. In the case that Conference Focus interacts with the main conference participant user and the conference participant user through the independent main conference session channel and the sub-meeting session channel, Conference Focus can identify the channel through which the conference session content is transmitted. Determine whether the content of the conference session sent by the participating user is the content of the main conference session or the content of the sub-conference session. Therefore, regardless of whether the conference session channel is reused or the independent conference session channel is adopted, Conference Focus can realize the participation of the participants who participate in only the main conference, the participants who only participate in the conference, and the participants in the conference. Accurate reception of the content of the session sent by the user.

After identifying the content of the received conference session, Conference Focus can send the conference session content to the sub-conference participant or the main conference participant through the shared conference session channel; or through the independent main conference session channel and sub-conference session. The channel sends the conference session content to the sub-conference participant or the main conference participant.

Conference Focus can send the identified main conference session content to the participating users who need to receive the content of the main conference session; the participants who need to receive the content of the main conference session can include: participants participating in the main conference, and participating in the conference. A sub-conference participant who is required to receive the content of the main conference session and is approved. The Conference Focus can send the identified sub-conference session content to the participating users who need to receive the sub-conference session content. The participating users who need to receive the sub-conference session content can include: participating users participating in the sub-conference, and participating in the main conference and A primary conference participant who is required to receive the content of the subconference session and is approved. For example, in a sub-conference, a sub-conference participant who is a participant in the main conference requesting to receive the content of the main conference session, and the Conference Focus can determine the conference participant after the user is determined to participate in the conference. After the session content is mixed, it is sent to the sub-conference participant. The conference session content received by Conference Focus here can be the main conference session content and/or the sub-conference session content.

At the same time, the participating users participating in the main conference sub-conference can choose whether to receive the main conference session content and the sub-conference session content, and the participating users who participate in the main conference and the sub-conference can also choose to exit the main conference or exit the sub-conference, Conference Focus. The content of the conference session matching the selection of the participating user can be sent to the participating user, so that the participating user can selectively receive the content of the conference session, thereby realizing the control of the participating user to receive the content of the conference session.

Although the above embodiment 1 can also implement the control of transmitting and receiving the content of the conference session, the technical means adopted by the two are different. For example, in the first embodiment, Sidebar Focus needs to subscribe to the main conference status information to associate the main sub-meeting. Therefore, the sub-conference is controlled in association with the main conference. In the second embodiment, the Conference Focus can perform the association control on the main sub-conference through the separate processing operation, so that the cooperation of the Sidebar Focus is not required, that is, the implementation does not need to be performed. For example, in the first embodiment, if the participating users who participate in the main sub-conference need to receive the main conference session content, Sidebar Focus needs to invite the Main Conference Focus to the sub-conference, at Sidebar Focus and Main Conference Focus. The main conference session channel is established between the two. In the second embodiment, the conference focus can completely send the mixed main conference session content to the participating users who participate in the main conference and the sub-conference, so that Sidebar Focus is not needed. Cooperate, that is, there is no need to perform an invitation, establish a main conference session channel, and the like. For another example, in the first embodiment, if the participating user who participates in the main sub-conference needs to switch back to the main conference and receive the sub-conference session content in the main conference, the Main Conference Focus needs to invite the Sidebar Focus to enter the conference. A sub-conference session channel is established between the Sidebar Focus and the Main Conference Focus, or a two-way conference session channel is used between the two, and in the second embodiment, because Conference Focus can completely process the corresponding conference session content to the participating users, , there is no need to perform the invitation, establish a sub-conference session channel, and so on. The switching in the second embodiment can be used to control whether the participant who participates in the primary conference also sends the content of the primary conference session or the content of the conference session. In addition, in the first embodiment, the participant who participates in the primary conference needs to quit. At the main conference, Main Conference Focus needs to decide whether to notify Sidebar Focus to terminate the sub-meeting according to the participation of the main conference participants. In the second embodiment, Conference Focus can control the termination of the main sub-conference by its own operation. No need for Sidebar Focus, no need to perform notifications and other operations. The many differences between the second embodiment and the first embodiment are generated by the implementation of the conference control center that reuses the main conference, that is, the conference session of the main conference is reused. The following describes the conference session content sending control, receiving control, exiting the conference, terminating the conference, and the like in the second embodiment.

Conference Focus can know the participation status of each participating user in the main sub-conference, that is, Conference Focus can know whether the participating users in the main sub-conference only participated in the main meeting, only participated in the sub-conference, or participated in the same. The main meeting and the sub-conference. The Conference Focus can know the participation status of each participating user in the main sub-conference according to the main conference participant user list information and the sub-conference participation user list information.

Conference Focus can determine whether to send the main conference session content to the sub-conference participants who participate in the main conference at the same time according to the sub-conference control policy. The sub-conference control policy can be set to: Allow the main conference session content and the sub-conference session content to be sent to the participating users participating in the main sub-conference, that is, by default, the Conference Focus sends the main conference session content to the participating users who simultaneously participate in the main sub-conference. And the sub-conference session content; at this time, the participating users who participate in the main sub-conference at the same time can control to receive only the required conference session content by sending stop receiving the main conference session request or stopping receiving the sub-conference session request. The request to stop receiving the primary conference session may carry the primary conference identifier, and optionally carry at least one of the specified conference user information; the request to stop receiving the conference session may carry the conference identifier, and may optionally carry at least one of the specified conference identifiers. A participant user information.

After the participant who participates in the main sub-conference stops receiving the content of the main conference session, it can also continue to receive the content of the main conference session by sending a reception main conference session request to the Conference Focus. After receiving the content of the sub-conference session, the participating users who participate in the main sub-conference can also continue to receive the sub-conference session by sending a receiving sub-conference session request to the Conference Focus.

The sub-conference control policy can also be set as follows: It is forbidden to send the main conference session content to the participating users who participate in the main sub-conference at the same time, that is, by default, the Conference Focus only sends the sub-conference session content to the participating users who participate in the main sub-conference at the same time. At this time, the participating users who participate in the primary sub-conference can control the content of the primary sub-conference session by sending and receiving the primary conference session request. That is, Conference Focus can only send sub-conferences to all participating users in the sub-conference according to the sub-conference participation user list information. The content of the content, Conference Focus can also send the main sub-conference session content to the sub-conference participants of the main conference participant user according to the main sub-conference participation user list information and the receiving main conference session request.

In the second embodiment, the participating user who can receive the content of the main sub-conference session can control whether to receive only the sub-conference session content or only the main conference session content by stopping receiving the main conference session request, stopping receiving the sub-conference session request. In the case that the participating users participating in the primary and secondary conferences can only receive the content of the primary conference session, the participating users can receive the primary conference session content by sending a reception sub-conference session request to the Conference Focus. In the case that the participating users participating in the primary sub-conference can only receive the content of the sub-conference session, the participating user can receive the main conference session content by sending a reception main conference session request to the Conference Focus. That is to say, the Conference Focus can send the corresponding conference session content to the participating users according to the main sub-meeting participation user list information, receiving the main conference session request, receiving the sub-conference session request, stopping receiving the main conference session request, and stopping receiving the sub-conference session request. .

In the second embodiment, the receiving the primary conference session request may carry the specified at least one sub-conference participation user information, or may not carry the specified at least one sub-conference participation user information. If the user information of the specified sub-conference is not carried, the participant who sends the request to receive the main conference session needs to receive the content of the main conference session. In the case of carrying the specified sub-conference participation user information, it may indicate that the designated sub-conference participating user needs to receive the main conference session content. That is to say, when a sub-conference participant in a sub-conference is required to receive the main conference session content, the user may send and receive the main conference session request; or other conference users may send and receive the main conference. Session request.

In the second embodiment, the request to stop receiving the primary conference session may carry the specified sub-conference participation user information, or may not carry the specified at least one sub-conference participation user information. If the user information of the specified sub-conference is not carried, the participant who sends the request to stop receiving the main conference session needs to stop receiving the content of the main conference session. If the specified sub-conference participation user information is carried, it may indicate that the designated sub-conference participation user needs to stop receiving the main conference session content. That is to say, when a sub-conference participant in a sub-conference is required to stop receiving the main conference session content, the user may automatically send a request to stop receiving the main conference session; or may be sent by other participating users. Stop receiving the main meeting session request.

In the second embodiment, the receiving the sub-conference session request may carry the specified at least one main conference participant user information, or may not carry the specified at least one main conference participant user information. If the user information of the specified primary conference is not carried, the participant who sends the request to stop receiving the conference session needs to stop receiving the conference session content. If the specified primary conference participant user information is carried, it indicates that the designated primary conference participant user needs to stop receiving the conference conference session content. That is to say, when the primary conference participant needs to stop receiving the content of the conference conference session, the user may send a request to stop receiving the conference conference session; or the other conference user may send a request to stop receiving the conference conference session.

The specific example method for the Conference Focus in the second embodiment to send the corresponding conference session content to the corresponding participant user is similar to the specific exemplary manner described in the first embodiment, and will not be described in detail herein.

In the second embodiment, the sub-conference user who is the main conference participant in the sub-conference can select to switch to the main conference or switch to the sub-conference as needed. The handover here is different from the handover in the first embodiment. The switching indicates that the participating user who is participating in the primary sub-meeting informs Conference Focus: whether the content of the session sent by the participating user is the content of the primary conference session or the content of the conference session, and the handover can be performed by sending a conference session request carrying the conference identifier. The conference identifier in the conference session request may be the primary conference identifier or the conference conference identifier. The primary conference identifier indicates that the content of the conference session that the participant user subsequently sends to the Conference Focus is the content of the conference session. The conference conference identifier indicates that the content of the conference session that the participant user subsequently sends to the Conference Focus is the content of the conference conference session. For example, in a sub-conference, the child who is the main conference participant The conference participant user can send a conference call handover request (that is, a conference conference session request carrying the conference conference identifier) to the conference focus to notify the conference focus that the content of the conference session subsequently sent by the conference user is the content of the conference conference session. For example, in the sub-conference, the sub-conference user who is the main conference participant user can send a conference call request to the conference conference (that is, a conference conference session request carrying the main conference identifier) to notify Conference Focus: The content of the conference session sent by the participating users is the content of the conference session.

Participants in the main meeting can request to leave the main meeting. For example, the participating user in the main conference can send an exit main conference request with the main conference identifier to the conference focus to indicate that the conference user requests to withdraw from the main conference. After receiving the main conference request from the main conference participant, the Conference Focus is in the case that the main conference session channel and the sub-meeting session channel are shared conference session channels, and the participant user needs to receive the sub-conference session content, the conference Focus can not release the session with the conference session between the participating users requesting to leave the main conference. At this time, the conference session is only used as a sub-conference session (that is, Conference Focus releases the logical main conference session); When the session channel and the sub-conference session channel are shared conference session channels, and the participant user does not need to receive the content of the sub-conference session, the conference focus can release the conference session channel between the participant and the participant who requests to exit the main conference. Operation; in the case that the main conference session channel and the sub-meeting session channel are mutually independent conference session channels, Conference Focus can release the main conference session channel between the participant and the participant who requests to exit the main conference, again, at this time The conference session is only used as a sub-conference session. After the Conference Focus receives the request to exit the main conference, the Conference Focus can update the main conference participant list and no longer send the main conference session content to the conference user; if the conference user is still a sub-conference participant, the conference Focus can continue to send sub-conference session content to the participating users.

Conference Focus can also determine whether all the main conference participants have logged out of the main conference after receiving the request to exit the main conference. If all the main conference participants quit the main conference, Conference Focus can be terminated first. The operation of the sub-meeting, and then the operation of terminating the main meeting. When the main conference session channel and the sub-meeting session channel are two mutually independent conference session channels, the operation of terminating the sub-conference may include: the Conference Focus releases the sub-conference session channel between the sub-conference participants.

The participating users in the sub-conference can request to exit the sub-conference. For example, the participating users in the sub-conference can send an exit sub-conference request with the sub-conference identifier to the conference focus to indicate that the participating user requests to exit the sub-conference. After receiving the exit sub-conference request, Conference Focus may not release the conference if the main conference session channel and the sub-conference session channel are shared conference session channels, and the participant user needs to receive the main conference session content. The operation of the session channel. In the case that the main conference session channel and the sub-meeting session channel are shared conference session channels, and the participant user does not need to receive the content of the main conference session, Conference Focus can perform the operation of releasing the conference session channel. In the case where the main conference session channel and the sub-meeting session channel are mutually independent conference session channels, Conference Focus can perform the operation of releasing the sub-conference session channel between the conference and the participating user. After the Conference Focus receives the exit sub-conference request, the sub-conference participation user list can be updated, and the sub-conference session content is no longer sent to the participating user. If the participating user is still the primary conference participant, Conference Focus can continue to send the primary conference session content to the participating user.

In addition, it should be noted that the foregoing exiting the main conference request and the exiting sub-conference request may also carry the specified at least one participant user information, so that the designated conference user needs to withdraw from the main conference or the conference.

The second embodiment of the sub-meeting will be described in detail below with reference to the accompanying drawings.

6 is a schematic diagram of an implementation sub-meeting of the second embodiment. In FIG. 6, each participating user using the terminal 1, the terminal 2, and the terminal 3 is performing a main conference, and the participating user using the terminal 4 does not participate in the main conference, but participates in the sub-conference. Any participant in the conference user 1, participant user 2, and conference participant 3 can create a sub-meeting through the terminal request. The conference server can determine whether to allow the sub-conference to be created according to the main conference control policy. After the sub-conference is created and successfully created, the participating users 1, the participating users 2, and the participating users 3 use the terminal to continue the main conference through the main conference session, and the participating users 1, the participating users 3, and the participating users 4 Sub-conferences are made through a sub-conference session using a terminal. The primary conference session and the conference session are the reused conference sessions. That is, the same conference session is used as the primary conference session when the participant user participates in the primary conference, and is used as the conference conference session when the conference user participates in the conference. The main conference media transmission channel can be shared as a sub-conference media transmission channel, or the main conference media transmission channel can be independent of the sub-conference media transmission channel. Since the primary conference and the secondary conference reuse the same session, the primary conference and the conference are related to each other, and the conference conference of the primary conference can control the conference session associated with the primary conference for the conference.

FIG. 7 is a flowchart of a sub-conference creation of the second embodiment.

In FIG. 7, UE1, UE2, UE3, and UE4 respectively represent terminals used by the participating users, where: the participating users using UE1, UE2, and UE3 are the primary conference participants, that is, the participants of UE1, UE2, and UE3 are used. The user participates in the multi-party multimedia conference hosted by the Main Conference Focus in the conference server. The media transmission channels between the participants using UE1, UE2, and UE3 and the Main Conference Focus are Dialog1, Dialog2, and Dialog3 respectively _. The user is a non-main conference participant user. The participant user using UE4 participates in the multi-party multimedia sub-conference under the Host Conference Focus host in the conference server together with the participant users using UE1 and UE3.

It should be specially noted that the Main Conference Focus in FIG. 7, 8, 9, and 10 is the Conference Focus described in the above second embodiment. In addition, for the sake of brevity, in the following description of the drawings, participation will be made. The user sends a message to the UE1, UE2, UE3, and UE4 by using the terminal device to send a brief description.

In FIG. 7, step 1: During the main conference, UE1 sends a sub-conference creation request to the conference server. The sub-conference creation request can be submitted to the conference server through the conference resource access mechanism supported by the conference server. For example, the sub-conference creation request is submitted to the conference server through a conference access or a remote assistant that assists the conference application parameter setting. The sub-conference creation request may carry a main conference identifier, a sub-conference topic, a sub-conference participant user list, a sub-conference session media type, a sub-conference control policy, and the like. The sub-conference control policy, such as whether to allow the sub-conference participants to receive the main conference session content, whether to allow non-main conference participants to participate in the sub-conference, and the like.

Step 4: The conference server determines whether to accept the sub-conference creation request according to the main conference control policy. If the sub-conference creation request is accepted, the conference server uses the existing conference session between the conference participant user and the conference server to implement the conference conference session. Therefore, the resource deployment of the conference server for the sub-conference is actually an adjustment to the existing primary conference instance. The conference server also needs to assign the sub-conference identifier to the sub-meeting, to step 5; if the conference server does not accept the sub-conference creation request, the sub-conference creation process ends, and the conference server can return the response information of the sub-conference to the UE1.

Step 6. The conference server sends a sub-session creation success notification to the Main Conference Focus. Step 7. After receiving the sub-conference creation success notification, the Main Conference Focus returns a response message to the conference server. Step 8: After receiving the response information that the sub-conference is successfully created, the UE1 sends a sub-meeting activation request to the Main Conference Focus.

Step 9. After receiving the sub-meeting activation request, the Main Conference Focus returns a response message to the UE1.

Step 10: After receiving the response information, UE1 returns an acknowledgement message to Main Conference Focus, so that the sub-conference session Dialog1 ' is successfully established on the existing main conference session Dialog1 between UE1 and Main Conference Focus. In other words, the existing conference session between UE1 and Main Conference Focus can be used as the main conference session and as a sub-conference session.

Step 11. The Main Conference Focus sends an invitation to the UE3 to join the sub-conference request according to the sub-conference participation user list information.

Step 12: After receiving the request, UE3 returns a response message to Main Conference Focus.

Step 13: After receiving the response information, the Main Conference Focus returns an acknowledgement message to the UE3, so that the sub-conference session Dialog3' is successfully established on the existing main conference session Dialog3 between the UE3 and the Main Conference Focus.

Step 14. The Main Conference Focus sends an invitation to the UE4 to join the sub-conference request according to the sub-conference participation user list. Step 15. After receiving the request, the UE4 returns a response message to the Main Conference Focus.

Step 16. After receiving the response message, the Main Conference Focus returns a confirmation message to the UE4, thereby successfully establishing.

Sub-conference session Dialog4 between UE4 and Main Conference Focus.

In the above process of creating a sub-conference, two different media transmission channel establishment methods can be used.

In the first mode, the primary conference session and the conference session share the same media transmission channel, and the primary conference media transmission channel is the conference media transmission channel. That is, the main conference session channel is shared as a sub-conference session channel.

Manner 2: A new media transmission channel is separately established for the sub-conference in the main conference session. The main conference media transmission channel and the sub-meeting media transmission channel are independent of each other, that is, the main conference session channel and the sub-conference session channel are independent of each other.

When the main conference session media type and the sub-meeting session media type are the same, the sub-meeting media transmission channel may be established by using any one of the foregoing manners 1 and 2. When the primary conference session media type and the sub-meeting session media type are different, the second conference media transmission channel needs to be established.

When mode 1 is used to establish a sub-conference media transmission channel, signaling may be used to control the transmission of the conference session content, such as Main.

The Conference Focus controls the content of the main conference session and the reception of the content of the conference session by signaling, and the conference user controls the transmission of the content of the conference session and the content of the conference session by signaling. The control of the content of the main conference session and the reception of the content of the sub-conference session by signaling may be implemented by the conference user sending a SIP re_INVITE request to the Main Conference Focus, where the Request URI in the SIP re-INVITE request is the primary conference identifier or sub- Conference identifier, to indicate whether the content of the session that the Main Conference Focus needs to receive is the main conference session content or the sub-conference session content; the session media type description can be carried in the MIME SDP message body of the SIP re-INVITE request; the Main Conference Focus can be received according to the start Or the difference of the stop reception will be set to a= _aC ti _V e〃 or _a =in _aC ti _Ve with the activation attribute in the m line of the corresponding conference media transmission channel description.

When mode 2 is used to establish a sub-meeting media transmission channel, since the participating users use separate media transmission channels in different conferences, Main Conference Focus can correctly distinguish the participants from the media transmission channel. The content of the conference session is the content of the main conference session or the content of the conference session.

It should be noted that, in the foregoing description of the process in FIG. 7, the step numbers do not represent the sequence of operations performed. For example, steps 5 and 6 in FIG. 7 may be performed simultaneously, or may be reversed in sequence; for example, steps 11. Step 14 can be performed at the same time. It can also be reversed in order.

The following describes in detail the implementation process of the main conference session content and the reception and transmission control of the sub-conference session content in the case where the main conference session, the sub-conference session is a reuse conference session, and the same media transmission channel is shared.

FIG. 8 is a flowchart of a main conference session and a sub-conference session transmission control in the second embodiment.

The participant users who use UE1, UE2, and UE3 in FIG. 8 are the main conference participants who initially participate in the multi-party multimedia conference hosted by the Main Conference Focus. In the main conference, the users who use UE1 and UE3 are used again. The participating users of UE4 perform sub-conferences. For other participating users in the main conference, such as the participating users using UE2, the participating users using UE1 and UE3 are still in the main conference. The participating users using UE4 are only sub-conference participants, and the participating users using UE4 are not authorized to receive the main conference session content. The main conference sessions between the participating users using UE1, UE2, and UE3 and the Main Conference Focus are Dialog1, Dialog2, and Dialog3, respectively, and the sub-conference sessions between the participating users of UE1, UE3, and UE4 and the Main Conference Focus are used. They are Dialogl ', Dialog3', Dialog4.

In FIG. 8, step 1, UE1 sends a sub-conference session switching request to the Main Conference Focus, requesting to temporarily use the media transmission channel of the main conference session Dialog1 between UE1 and Main Conference Focus as the media transmission channel of the sub-conference session Dialog1'. That is, the media transmission channel between UE1 and Main Conference Focus is temporarily dedicated to the sub-conference. In the sub-conference session switching request sent by UE1, the Request URI may be set to the sub-conference identifier "sub- conference@example.com", and the "Replace" header field may carry the current session identifier Dialog1, the parameter "conference-only" Indicates the main conference identifier main_ conference@example.com that occupies the media transmission channel before the handover. The primary subsession session switching request may be in the form of: re- INVITE sip:sub- conference@example.com SIP/2.0

Via: SIP/2.0/TCP server.example.com;branch=z9hG4bK776sgdkse

To:sip:main— conference@example.com; tag=7743

From: sip:user1 ©example. com;tag=6472

Call-ID: a84b4c76e66710

CSeq: 1 UPDATE

Max-Forwards: 70

Date: Sun, 21 May 2006 13:02:03 GMT

Contact: <sip:user1 ©example. com>

Replaces: a84b4c76e66710;to-tag=7743;from-tag=6472;

Conference-oly=main_conference@example.com

Content-Type: application/sdp

Content-Length: [length] v=0

o=user1 2890844526 2890844526 IN IP4 user1 .example.com

s=...

c=IN IP4 user1 .example.com

m=audio 3456 RTP I AVP 96 970

t=0 0

Step 2: After receiving the sub-conference session handover request sent by the UE1, the Main Conference Focus returns the response information of the handover success to the UE1. Step 3: The UE1 sends the conference session content to the Main Conference Focus through Dialog1, and the content of the conference session is the content of the conference session.

Step 4: After receiving the content of the sub-conference session sent by the UE1, the Main Conference Focus returns a response message to the UE1. Since the media transmission channel is temporarily used as the sub-conference media transmission channel, the Main Conference Focus can clearly know that the session content it receives is the sub-conference session content.

Step 5. The Main Conference Focus sends the sub-conference session content to UE3 through Dialog3' according to the sub-conference participation user list information.

Step 6. After receiving the content of the sub-conference session, UE3 returns a response message to Main Conference Focus.

Step 7. Main Conference Focus sends the sub-conference content to UE4 via Dialog4 according to the sub-conference participation user list information.

Step 8. After receiving the content of the sub-conference session, UE4 returns a response message to Main Conference Focus.

Step 9. After the UE1 speaks in the sub-meeting, it is desirable to return to the main conference session state, and the UE1 sends a main conference session handover request to the Main Conference Focus to request media transmission of the sub-conference session Dialog1 ' between the UE1 and the Main Conference Focus. The channel is reused as the media transport channel for the main conference session Dialog1.

Step 10: After receiving the primary conference session handover request sent by the UE1, the Main Conference Focus returns the response information of the successful handover to the UE1.

Step 11. UE1 sends the content of the conference session to the Main Conference Focus through Dialog1, and the content of the conference session is the content of the main conference session.

Step 12: After receiving the content of the main conference session sent by the UE1, the Main Conference Focus returns a response message to the UE1. Since the media transmission channel between UE1 and Main Conference Focus is occupied by the main conference at this time, Main Conference Focus can clearly know that the content of the conference session it receives is the content of the main conference session.

Step 13. Main Conference Focus sends the main conference session content to UE2 through Dialog2 according to the main conference participant list.

Step 14. After receiving the content of the main conference session, UE2 returns a response message to Main Conference Focus.

Step 15. The Main Conference Focus sends the main conference session content to the UE3 through the Dialog3 according to the main conference participant list.

Step 16. After receiving the content of the main conference session, the UE3 returns a response message to the Main Conference Focus.

It should be noted that, in the foregoing description of the process in FIG. 8, the step numbers do not represent the sequence of operations performed. For example, steps 5 and 7 in FIG. 8 may be performed simultaneously, or may be reversed in sequence; for example, steps 13. Step 15 can be performed simultaneously or in reverse order.

FIG. 9 is a flowchart of a main conference session and a sub-conference session reception control in the second embodiment.

In Figure 9, step 1, UE2 sends the main conference session content to Main Conference Focus through the media transmission channel of Dialog2.

Step 2: After receiving the content of the main conference session sent by the UE2, the Main Conference Focus returns a response message to the UE2. Step 3: UE4 sends the sub-conference session content to the Main Conference Focus through the media transmission channel of Dialog4. Step 4: After receiving the content of the sub-conference session sent by the UE4, the Main Conference Focus returns a response message to the UE4. Step 5: Main Conference Focus according to the main conference participation user list information, sub-conference participation user list information, After Dialog1 sends the content of the main conference session and the content of the conference session after the sub-conference session content is mixed to UE1.

Step 6. After receiving the content of the conference session after the mixing, the UE1 returns a response message to the Main Conference Focus.

Step 7. The Main Conference Focus sends the main conference session content to the UE2 according to the main conference participant user list information, the sub-conference participation user list information, and the Dialog2. It should be noted that, for convenience of description, only four participating users using UE1, UE2, UE3, and UE4 are used in FIG. 9, and the participating users using UE1, UE2, and UE3 are the main conference participants. In fact, in actual applications, there are other main conference participants. Therefore, the main conference session content sent by the Main Conference Focus to the UE2 in step 7 is not the main conference sent by the UE2 received by the Main Conference Focus in step 2. Conversational content. If there are only three participating users using UE1, UE2, and UE3 in the main conference, step 7 can be omitted.

Step 8. After receiving the content of the main conference session, UE2 returns a response message to Main Conference Focus.

Step 9. The Main Conference Focus sends the main conference session content and the conference session content of the sub-conference session content to the UE3 according to the main conference participation user list information, the sub-conference participation user list information, and the Dialog3' (ie, through Dialog3). .

Step 10: After receiving the content of the mixed session, UE3 returns a response message to Main Conference Focus.

Step 11. The Main Conference Focus sends the sub-conference session content to the UE4 according to the main conference participation user list information, the sub-conference participation user list information, and the Dialog4.

Step 12: After receiving the content of the sub-conference session, UE4 returns a response message to Main Conference Focus.

Step 13, UE1 needs to temporarily stop receiving the content of the main conference session, UE1 sends a request to stop receiving the main conference session to the Main Conference Focus, and the request to stop receiving the main conference session may be a SIP UPDATE request, and the Request URI value in the SIP UPDATE request may be set as the main The conference identifier "main_conference@example.com", the activation attribute in the message body SDP media description m line can be set to a=i _naC ti _ve . The stop receiving the main conference session request may be in the following form:

UPDATE sip:main— conference@example.com SIP/2.0

Via: SIP/2.0/TCP server.example.com;branch=z9hG4bK776sgdkse

To:sip:main— conference@example.com; tag =7743

From: sip:user1 ©example. com;tag=6472

Call-ID: a84b4c76e66710

CSeq: 1 UPDATE

Max-Forwards: 70

Date: Sun, 21 May 2006 13:02:03 GMT

Contact: <sip:user1 ©example. com>

Content-Type: application/sdp

Content-Length: [length] v=0

o=- 2987933615 2987933616 IN IP6 5555::aaa:bbb:ccc:ddd

s=- c=IN IP6 5555::aaa:bbb:ccc:ddd

t=0 0

m=audio 3456 RTP/AVP 97

b=AS: 25.4

a=inactive

a=rtpmap:97 AMR

Step 14: After receiving the request to stop receiving the main conference session, the Main Conference Focus returns a response message to the UE1. The Main Conference Focus determines that the UE1 needs to suspend receiving the content of the main conference session according to the request to stop receiving the main conference session, that is, the Main Conference Focus determines that the content of the main conference session is not required to be transmitted to the UE1 during the transmission of the content of the subsequent conference session.

Step 15. UE2 sends the main conference session content to Main Conference Focus through Dialog2.

Step 16. After receiving the content of the main conference session sent by the UE2, the Main Conference Focus returns a response message to the UE2. Step 17. UE4 sends the content of the sub-conference session to the Main Conference Focus through Dialog4.

Step 18: After receiving the content of the sub-conference session sent by the UE4, the Main Conference Focus returns a response message to the UE4. Step 19. The Main Conference Focus sends the received sub-conference content to UE1 via Dialogl ' (ie via Dialogl).

Step 20: After receiving the content of the sub-conference session, UE1 returns a response message to Main Conference Focus.

Step 21: Main Conference Focus sends the received main conference session content to UE2 through Dialog2. It should be noted that, for convenience of description, only four participating users using UE1, UE2, UE3, and UE4 are used in FIG. 9, and the participating users using UE1, UE2, and UE3 are the main conference participants. In fact, in actual applications, there are other main conference participants. Therefore, in step 21, the main conference session sent by the Main Conference Focus to the UE2 is not the main conference sent by the UE2 received by the Main Conference Focus in step 15. Conversational content. If there are only three participating users using UE1, UE2, and UE3 in the main conference, step 21 can be omitted.

Step 22: After receiving the content of the main conference session, UE2 returns a response message to Main Conference Focus.

Step 23: The Main Conference Focus sends the main conference session content and the conference session content of the sub-conference session content to the UE3 according to the main conference participation user list information, the sub-conference participation user list information, and the Dialog3' (ie, through Dialog3). .

Step 24: After receiving the content of the conference session after the mixing, the UE3 returns a response message to the Main Conference Focus.

Step 25: The Main Conference Focus sends the sub-conference session content to the UE4 according to the main conference participation user list information, the sub-conference participation user list information, and the Dialog4.

Step 26: After receiving the content of the sub-conference session, the UE4 returns a response message to the Main Conference Focus.

The foregoing description of FIG. 9 is described by taking the example that the UE1 pauses to receive the content of the main conference session. The UE1 may also request that the content of the conference session is not received temporarily. The implementation process is basically the same as the description of the foregoing process, and is not detailed here. Description.

It should be noted that, in the foregoing description of the process in FIG. 9, the step numbers do not represent the sequence of operations performed. For example, step 5, step 7, step 9, and step 11 in FIG. 9 may be performed simultaneously, or may be sequentially performed. For example, Step 19, Step 21, Step 23, and Step 25 may be performed simultaneously, or may be reversed in order.

Figure 10 is a flow chart of the exit main conference and the main sub-meeting termination of the second embodiment.

In FIG. 10, step 1: UE3 sends an exit main conference request to Main Conference Focus.

Step 2. The Main Conference Focus returns a response message to the UE3. The conference server releases the main conference session Dialog3 between UE3 and Main Conference Focus. At this time, the conference session between UE3 and Main Conference Focus is only used as a conference session, and UE3 successfully exits the conference.

Step 3. UE2 sends the main conference session content to Main Conference Focus through Dialog2.

Step 4. The Main Conference Focus returns a response message to the UE2.

Step 5: UE4 sends the sub-conference session content to the Main Conference Focus through Dialog4. Step 6. The Main Conference Focus returns a response message to the UE4.

Step 7. After the Main Conference Focus mixes the received main conference session content and the sub-conference session content, it sends it to UE1 through Dialogl ' (ie, via Dialogl).

Step 8. UE1 returns a response message to Main Conference Focus.

Step 9. Main Conference Focus sends the content of the main conference session to UE2 through Dialog2.

Step 10. UE2 returns a response message to Main Conference Focus.

Step 11. Since the UE3 has exited the main conference, the Main Conference Focus receives the content of the main conference session, but only transmits the content of the conference session to the UE3 through Dialog3'.

Step 12: After receiving the content of the sub-conference session, UE3 returns a response message to Main Conference Focus.

Step 13: Since UE4 only participates in the sub-conference session, the Main Conference Focus receives the content of the main conference session, but transmits the received sub-conference session content to UE4 only through Dialog4.

Step 14: After receiving the content of the sub-conference session, UE4 returns a response message to Main Conference Focus.

Step 15. UE2 sends an exit main conference request to Main Conference Focus through Dialog2.

Step 16: After receiving the request to exit the main conference, the Main Conference Focus sends a response message to the UE2, and the conference server releases the session Dialog2 between the UE2 and the Main Conference Focus, and the UE2 successfully exits the main conference.

Step 17. UE1 sends a request to the Main Conference Focus to exit the main conference via Dialogl ' (ie via Dialogl).

Step 18: Because the participant user using UE1 is the last participant in the primary conference, the exit primary conference request sent by UE1 will trigger the conference server to terminate the primary conference session. Before terminating the main conference session, all sub-conferences under the main conference must be terminated first. Therefore, the Main Conference Focus sends an exit sub-meeting request to the UE3 to instruct the UE3 to exit the sub-conference.

Step 19: After receiving the request to exit the sub-meeting, the UE3 returns a response message to the Main Conference Focus, and the conference server releases the session Dialog3' between the UE3 and the Main Conference Focus, and the UE3 successfully exits the sub-conference.

Step 20: The Main Conference Focus sends an exit sub-meeting request to the UE1 to instruct the UE1 to exit the sub-conference.

Step 21: After receiving the request to exit the sub-meeting, UE1 returns a response message to Main Conference Focus, and the conference server releases the session Dialog1 ' between UE1 and Main Conference Focus, and UE1 successfully exits the sub-conference.

Step 22: The Main Conference Focus sends an exit sub-meeting request to the UE4 to instruct the UE4 to exit the sub-conference.

Step 23: After receiving the request to exit the sub-meeting, the UE4 returns a response message to the Main Conference Focus, and the conference server releases the session Dialog4 between the UE4 and the Main Conference Focus, and the UE4 successfully exits the sub-conference. At this point, the sub-conference participants all exit the sub-conference.

The conference server can successfully terminate the primary child conference instance.

It should be noted that, in the foregoing description of the process in FIG. 10, the step numbers do not represent the sequence of operations performed. For example, step 7, step 9, and step 11 in FIG. 10 may be performed simultaneously, or may be reversed in sequence; For example, step 18, step 20, and step 22 may be performed simultaneously, or may be reversed in order.

The method for implementing the private conference session provided by the embodiment of the present invention is described below.

The content of the private conference session can be transmitted between the participating users. Private meetings can also be called "private chats." A private conference is a private conference between certain specific participants during the current conference (such as the main conference, sub-conference). In the process of implementing a private conference, there is no need to establish a conference control center, or you need to assign a new conference identifier to a private conference. In addition, privacy Meetings have confidential requirements and are attached to ongoing meetings, such as private meetings attached to the main meeting. The participants in the private conference can be the participants of the conference, or the participants of the conference. They can also include the conference participants and the conference participants.

The differences between private and sub-conferences include: Sub-conferences can allow non-primary conference participants to join, but private conferences are usually limited to ad hoc conferences between participating users.

The embodiments of the present invention provide the following two ways to implement a private conference:

The first step is to use the private conference session to occupy the conference session channel request to determine the conference user who needs to receive the private conference session content, and then, after receiving the private conference session content, the conference to determine the content of the private conference session needs to be received. The user sends the private conference session content.

In the first mode, the conference user can determine the content of the private conference session according to the conference session channel request of the private conference session. Therefore, the conference user can no longer carry the privacy when the conference session content is sent. Participant user information of the conference session content. The conference control center may determine the content of the conference session sent by the conference user as the content of the private conference session, when the conference user sends the foregoing request to the conference user requesting to switch to the primary conference or the conference.

The method 1 uses the existing conference session channel to implement the transmission of the private conference session content. After the conference user sends the request, the private conference session temporarily occupies the existing conference session channel between the conference user and the conference control center.

The private conference session in the first mode can take the private session indication, the private conference session user ID, and the private conference session user identifier. The private session indication is used to indicate that a private conference session needs to occupy the conference session channel.

The specific implementation process of the mode 1 may be as follows: Before sending the content of the private conference session, the conference user first sends a private conference session to the conference control center to occupy the existing conference session channel request. The conference control center may be the primary conference control center or the conference control center described in the first embodiment, or may be the reused conference control center described in the second embodiment. After receiving the request, the conference control center can clearly know that the content of the conference session sent by the participant who sent the request is the content of the private conference session according to the private session indication in the request and the user ID of the private conference session. The conference control center can clearly know according to the user ID of the receiving private conference session carried in the request: The participant who needs to receive the content of the private conference session. The information of the participating users in the private conference session can be information of one participant or multiple participants. That is, private conference session content can be transferred between two participating users, or between three or more participating users. After receiving the content of the conference session sent by the conference user who sent the request, the conference control center sends the content of the private conference session to the participant who needs to receive the private conference session. The private conference session content sent by the participant user may not carry the participant user information that needs to receive the content of the private conference session. Certainly, the embodiment of the present invention does not exclude the possibility that the private conference session content carries the participant user information that needs to receive the private conference session content, but even if the private conference session content carries the conference that needs to receive the private conference session content, User information, the conference control center may also forward the content of the private conference session according to the participant information carried in the request.

In the first method, the participant who performs the private conference can use the technical solution described in the first embodiment or the second embodiment to implement the content of the main conference session or the sub-conference session. For example, the participant user The conference control center sends the sending to the sub-conference session switching request or the main conference session switching request described in the second embodiment, and then the participating user sends the main session meeting content or the sub-conference session content to the conference control center. The specific implementation process will not be described in detail herein.

Method 2: Use an existing conference session to establish a new conference session channel for the private conference, and utilize the newly established conference session channel. Realize the transmission of private conference session content.

In the case where the private conference session media type is the same as or different from the existing conference session media type, the private conference can be implemented in the second mode.

The private conference session channel can be established by the conference control center after the conference user sends a message to the conference control center for the first time to notify the conference control center that a private conference is required. The session of the private conference session can be set up as follows: When the conference user needs to perform a private conference, the conference user can send a private conference session request to the conference control center. The private conference session request indicates that a private conference needs to be performed. Participate in the information of the participating users in the private meeting, so that the conference control center can clearly know which participating users need to conduct private meetings, that is, need to establish a private meeting session channel and private meeting session content between the meeting control center and which participating users. Which participating users need to transfer between them. The conference control center establishes private conference session channels between the participating users and the participating users who need to conduct private meetings. The number of participants who need to conduct a private conference session here can be two or more.

After the private session session is successfully established, the conference session channel corresponding to the private conference is the conference session channel dedicated to the private conference session. Therefore, the conference user who needs to send the private conference session content can not send the private conference session content. A private conference session occupies an existing conference session channel request. The conference control center can determine whether the content of the received conference session is the content of the private conference session through the transmission channel of the conference session content it receives. After the conference control center judges that the content of the received conference is the content of the private conference session, the conference control center sends the private conference session content to other participants in the private conference. The other participating users here are the participating users other than the participating users who send the content of the meeting session in the private meeting.

Participants can request to quit a private meeting session. After the participant user requests to quit the private conference session, the conference control center can release the private conference session channel with the conference user.

FIG. 11 is a schematic flowchart of a method for implementing a private conference by adopting mode 1.

In FIG. 11, each participating user of UE1, UE2, UE3, and UE4 is a participating user participating in a multi-party multimedia conference hosted by Conference Focus, and between the participating users of UE1, UE2, UE3, and UE4 and Conference Focus. The conference sessions are Dialog1, Dialog2, Dialog3, and Dialog4, respectively, and the conference users using UE1 request private conferences with the conference users using UE3 and UE4. In the following process, the participating user sends a message to UE1 by using UE1 to send a message.

Step 1. The UE 1 sends a private chat session switching request to the Conference Focus for the private conference with the UE3 and the UE4. The private conference session request, that is, the private conference session described in the foregoing embodiment occupies the existing conference session channel request, is requested. The conference session Dialog1 channel between UE1 and Conference Focus is temporarily used as a "private chat" session channel. The request also indicates that the content of the session sent by UE1 is private chat session content (ie, private conference session content), and the private chat session content can only be forwarded to UE3 and UE4. The Request URI in the private chat session switch request can be set to the conference ID " conference@example. com" of the existing conference to indicate the conference session instance to which the Conference Focus belongs. The content type ( Content-Type ) carried by the message body of the chat session request can be set to: "application/resource_list+xml", (ie, the list of participating users who receive the "private chat" session content), such as UE3, UE4 „ Step 2: After receiving the private chat session handover request sent by the UE1, the Conference Focus returns a response message to the UE1.

Step 3. UE1 sends a private chat session content to Conference Focus through Dialogl.

Step 4: After receiving the private chat session content sent by the UE1, the Conference Focus returns a response message to the UE1.

Step 5. Conference Focus sends the received private chat session content to UE3 through Dialog3.

Step 6. After receiving the private chat session content, the UE3 returns a response message to the Conference Focus. Step 7. The Conference Focus sends the received private chat session content to the UE4 through the Dialog4.

Step 8. After receiving the private chat session content, the UE4 returns a response message to the Conference Focus.

Step 9. UE2 sends the content of the conference session to the Conference Focus through Dialog2 (that is, the content of the session of the current conference to which the private chat conference belongs).

Step 10: After receiving the content of the conference session sent by the UE2, the Conference Focus returns a response message to the UE2.

Step 11. UE3 sends the content of the conference session to the Conference Focus through Dialog3 (that is, the content of the session of the current conference to which the private chat conference belongs).

Step 12: After receiving the content of the conference session sent by the UE3, the Conference Focus returns a response message to the UE3.

Step 13. Conference Focus mixes the session content of the current conference to which the private chat conference it receives belongs, and sends the content of the conference session after mixing to UE1 through Dialog1.

Step 14. After receiving the content of the conference session, the UE1 returns a response message to the Conference Focus.

Step 15. Conference Focus sends the content of the conference session after mixing to UE2 through Dialog2.

Step 16. After receiving the content of the conference session, the UE2 returns a response message to the Conference Focus.

Step 17. Conference Focus sends the content of the conference session after mixing to UE3 through Dialog3.

Step 18: After receiving the content of the conference session, the UE3 returns a response message to the Conference Focus.

Step 19. Conference Focus sends the content of the conference session after mixing to UE4 through Dialog4.

Step 20: After receiving the content of the conference session, the UE4 returns a response message to the Conference Focus.

It should be noted that, in the foregoing description of the process in FIG. 11, the step numbers do not represent the sequence of operations performed. For example, step 5 and step 7 in FIG. 11 may be performed simultaneously, or may be reversed in sequence; for example, steps 13. Step 15, Step 17, and Step 19 may be performed simultaneously or in reverse order.

FIG. 12 is a schematic flowchart of implementing private conference by adopting mode 2.

The conference users who use the UE1, UE2, UE3, and UE4 in FIG. 12 are the conference users participating in the multi-party multimedia conference hosted by the Conference Focus, and use the conference sessions between the conference users of the UE1, UE2, UE3, and UE4 and the Conference Focus. The Dialog1, Dialog2, Dialog3, and Dialog4 are respectively used by the participating users of UE1 to make private meetings with the participating users using UE3 and UE4.

Step 1. The UE 1 sends a private chat session invitation (ie, the private conference session request described in the foregoing mode 2) to the Conference Focus to perform a private conference with the UE3 and the UE4 to request the conference focus to be established between the UE and the UE4. Private chat "Media transmission channel for session content transmission. The Request URI in the private session invitation can be set to the existing conference ID " conference@example. com" to indicate the conference session instance to which the private chat belongs. The message body of the private chat session invitation can carry two parts of content, one is the negotiation description of the "private chat" session media type whose content type is "appl icat ion/sdp", and the content type is "appl icat ion/resource- l ists+xml " (ie a list of participating users who receive "private chat" session content), such as UE3, UE4

Step 2. The Conference Focus receives the private chat session invitation sent by the UE1, and returns a response message to the UE1.

Step 3. The Conference Focus receives the confirmation information sent by the UE1.

Step 4: The Conference Focus sends a private chat session invitation to the UE3 to establish a conference session channel between the Conference Focus and the UE3 for transmitting the private chat session content, that is, the private chat session channel.

Step 5: The UE3 receives the private chat session invitation, and returns a response message to the Conference Focus. Step 6. The Conference Focus sends an acknowledgement message to the UE3.

Step 7. The Conference Focus sends a private chat session invitation to the UE4 to establish a conference session channel between the Conference Focus and the UE4 for transmitting the content of the private chat session.

Step 8. The UE4 receives the private chat session invitation and returns a response message to the Conference Focus.

Step 9. The Conference Focus sends an acknowledgement message to the UE4.

So far, in response to the private conference session request of UE1, the Conference Focus establishes a conference session channel dedicated to the private chat session between UE1 and UE3, UE4, that is, a private chat session channel.

Step 10: The UE1 sends the private chat session content to the Conference Focus through the private chat session channel.

Step 11. After receiving the private chat session content sent by the UE1, the Conference Focus returns a response message to the UE1.

Step 12. Conference Focus sends the private chat session content to UE3 through the private chat session channel.

Step 13. After receiving the private chat session content, the UE3 returns a response message to the Conference Focus.

Step 14. Conference Focus sends the private chat session content to UE4 through the private chat session channel.

Step 15. After receiving the private chat session content, the UE4 returns a response message to the Conference Focus.

Step 16. The UE2 sends the conference session content to the Conference Focus through the conference session channel to which the private chat conference belongs (the conference content is the conversation content of the current conference to which the private chat conference belongs).

Step 17: After receiving the content of the conference session sent by the UE2, the Conference Focus returns a response message to the UE2.

Step 18: The Conference Focus sends the received conference session content to the UE1.

Step 19: After receiving the content of the conference session, the UE1 returns a response message to the Conference Focus.

Step 20: The Conference Focus sends the received conference session content to the UE3.

Step 21: After receiving the content of the conference session, the UE3 returns a response message to the Conference Focus.

Step 22. The Conference Focus sends the received conference session content to the UE4.

Step 23: After receiving the content of the conference session, the UE4 returns a response message to the Conference Focus.

It should be noted that, in the foregoing description of the process for FIG. 12, the step numbers do not represent the sequence of operations performed. For example, step 4 and step 7 in FIG. 12 may be performed simultaneously or in reverse; for example, steps 12, Step 14 may be performed simultaneously, or may be reversed in sequence; further, Step 18, Step 20, Step 22 may be performed simultaneously, or may be reversed in order.

It can be seen from the description of the foregoing technical solution that, in the first embodiment, by using the main conference state information, the main conference and the sub-meeting can be associated, so that the sub-conference can be controlled by the main conference, and the associated control operation is performed. It can be: The sending and receiving control of the session content, for example, when the session content is sent to the participating users in the sub-conference, the session content can be sent and controlled, and the non-main meeting participant can not be added to the sub-conference or the sub-conference. There is a problem that the session content cannot be sent when there is a non-main conference participant user, so that the participating users with different rights can receive different session contents; the associated control operations can also be: the influence of the end of the main conference on the sub-conference, etc. The existing sub-conference implementation mechanism is improved. The main conference control strategy is considered in the sub-conference creation process, and the participant user is considered to receive the sub-conference session content during the process of switching back to the main conference. Existing sub-meeting implementation mechanisms. In the second embodiment, by reusing the main conference session for the main conference and the sub conference, the process of setting up the independent sub-conference control center is avoided, and the conference user can also participate in the main conference without the parallel conversation capability. And the sub-conference; in addition, since the main conference and the sub-conference reuse the main conference control center, the association control of the main conference and the sub-conference can be conveniently implemented; thus, the second embodiment provides a new technical solution for the sub-conference implementation; finally, the implementation of the present invention The two technical solutions provided by the method improve the flexibility of implementing sub-meeting. The sub-meeting implementation apparatus corresponding to the first embodiment will be described below with reference to the accompanying drawings.

FIG. 13 is a schematic diagram of an apparatus for implementing a conference according to an embodiment of the present invention. The apparatus may be configured in a conference server. The apparatus includes: an acquisition module, a determination status module, a first control module, a first creation module, a second reception request module, a third control module, a first termination module, and a first release module. The first control module includes: a first storage module, a second control module, and a first receiving request module.

The first creating module may obtain the primary conference control policy after receiving the sub-conference creation request sent by the primary conference participant user. The first creation module can obtain the main conference control policy from the Main Conference Focus, and can also obtain the conference control policy for determining whether to allow the sub-conference to be created from other network devices. The sub-conference creation request may carry a primary conference identifier, sub-conference topic information, sub-conference participant user list information, a sub-conference session media type, and a sub-conference control policy. After the first creation module determines that the sub-conference is allowed to be created by using the main conference control policy, the sub-conference subsequent creation operation is performed to create the sub-meeting. The content of the creation operation is as described in the above method embodiment. After the first creation module successfully establishes the sub-meeting, the sub-conference session and the main conference session are two parallel conference sessions, that is, the main conference instance corresponds to the Main Conference Focus, and the sub-conference instance corresponds to the Sidebar Focus „ the first creation module creates the sub-conference. During the process, the acquisition module can be notified to subscribe to the main conference status information.

The acquisition module is set in the conference server. After the sub-conference control center is successfully established, it belongs to the sub-conference control center. The get module gets the main conference status information. The main conference status information can be used to determine the participation status of each participating user in the sub-conference. The obtaining module can obtain the main conference status information by using a subscription manner, and the obtaining module can also obtain the main conference status information from the information actively sent by the main conference control center. The specific content of the main conference status information and the specific implementation process of obtaining the main conference status information are as described in the foregoing method embodiments.

The determination status module is set in the conference server. After the sub-conference control center is successfully established, it belongs to the sub-conference control center side. The determining status module determines the participation status of each participating user in the sub-conference according to the main conference status information acquired by the obtaining module. That is, the determination status module can use the main conference status information to determine whether the participating users in the sub-conference participate in the main conference while participating in the sub-conference.

The first control module is disposed in the conference server, and belongs to the sub-conference control center side after the sub-conference control center is successfully established. The first control module sends the sub-conference session content to the sub-conference participants according to the participation status of each participating user in the sub-conference, or sends the main conference session content and the sub-conference session content.

The process of sending the content of the conference session by the first control module can be implemented as follows:

The first storage module stores the participation status and the sub-conference control policy of each participating user in the sub-conference. The sub-conference control policy here may be: Allow or prohibit the sending of the main conference session content to the sub-conference participants who are simultaneously participating in the main conference.

The sub-conference control policy stored in the first storage module is: when the main conference session content is prohibited from being sent to the participating users of the sub-conferences participating in the main conference, the second control module sends the sub-conference session content to each sub-conference participant user. . The sub-conference control policy stored in the first storage module is: when the main conference session content is allowed to be sent to the participating users of the sub-conferences participating in the main conference, the second control module sends the main conference session content to each sub-conference participant user. And sub-conference session content.

The sub-conference control policy stored in the first storage module is: when the content of the main conference session is prohibited from being sent to the sub-conference participant who is simultaneously participating in the main conference, the first receiving request module receives the reception sent by the sub-conference participant user. After the primary conference session request, the second control module may determine, according to the request for receiving the primary conference session, the conference participant user who needs to receive the primary conference session. If the second control module determines that the sub-conference participant user who needs to receive the main conference session content is the main conference participant user according to the main conference participant user list information stored in the first storage module, the second control module may determine The child who needs to receive the main conference session The conference participant user sends the content of the main conference session and the content of the conference session. Otherwise, the second control module does not send the content of the conference session to the conference participant who needs to receive the content of the conference session. The content of the participant who needs to receive the content of the main conference session and the content of the main conference session is specifically included in the method embodiment.

The first receiving request module may further receive the stop receiving the main conference session request. At this time, the second control module does not send the main conference session content to the participating users who need to stop receiving the content of the main conference session. Here, the content of the participant who needs to stop receiving the content of the main conference session, the content specifically included in the stop receiving the main conference session request, and whether the user is judged after receiving the request to stop receiving the main conference session, etc. Description in .

The second receiving request module is set in the conference server, and belongs to the main conference control center side after the main conference control center is successfully established. The second receiving request module receives the receiving sub-conference session request sent by the main conference participant user, stops receiving the sub-conference session request, and exits the main conference request. The content specifically received by receiving the sub-conference session request, stopping receiving the sub-conference session request, and exiting the main conference request is as described in the above method implementation.

The third control module is set in the conference server, and belongs to the main conference control center side after the main conference control center is successfully established. The third control module acquires sub-conference status information. The third control module determines, according to the acquired sub-conference status information, whether the main conference participant user who sends and receives the sub-conference session request is a sub-conference participant user, and if the sub-conference user is also a sub-conference user, the third control module sends a request. The main conference participant user sends the main conference session content and the sub-conference session content; if the main conference participant user who sends the request is not the sub-conference participant user, the third control module does not send the request to the main conference participant user. Send the content of the sub-conference session. After the second receiving request module receives the request to stop receiving the sub-conference session, the third control module may not directly send the sub-conference session content to the participating user who sends the request, and the third module may also determine, according to the obtained sub-conference status information. The third control module stops sending the sub-conference session content to the participant user if the primary conference participant user who is the recipient of the sub-conference session request is the sub-conference participant. Specifically, it is as described in the above method embodiment.

The first termination module is set in the conference server, and belongs to the main conference control center side after the primary conference control center is successfully established. After receiving the request to exit the main conference, the first termination module determines whether the primary conference needs to be terminated. After determining that the primary conference needs to be terminated, the first termination module sends a sub conference termination indication to the first release module to indicate the first release. The module terminates the subsession. The first termination module also needs to terminate the main conference after the termination of the sub conference, that is, the first termination module terminates the main conference after receiving the response information returned by the first release module.

The first release module is disposed in the conference server, and belongs to the sub conference control center side after the sub conference control center is successfully established. After receiving the sub-conference termination indication sent by the first termination module, the first release module releases the sub-conference session between the sub-conference control center and each sub-conference participant user, and returns a response to the first termination module.

The specific implementation process of the first termination module and the first release module terminating the primary sub-conference is as described in the foregoing method embodiments. The sub-meeting implementation device corresponding to the second embodiment will be described below with reference to the accompanying drawings.

FIG. 14 is another apparatus for implementing a seed conference according to an embodiment of the present invention, and the apparatus may be disposed in a conference server. The apparatus includes: a receiving creation request module, a second creating module, a first interaction module, a judging module, a second terminating module, and a second releasing module. The first interaction module includes: a second storage module and a fourth control module. The fourth control module includes: a third receiving request module and a fifth control module.

The receiving creation request module receives the sub-conference creation request. The sub-conference creation request may carry the main conference identifier, the sub-conference topic information, the sub-conference participation user list information, and the sub-conference session media type. The sub-conference control policy may also optionally carry a sub-conference control policy. Of course, the sub-conference control policy may also be preset in the conference server. Sub-conference control strategy The content included in the body, other transmission modes in which the information is carried in the sub-conference creation request, and the like are as described in the foregoing method embodiments. After receiving the sub-conference creation request, the second creation module may directly perform the sub-conference creation operation, or may decide whether to perform the sub-conference creation operation according to the conference control policy. The conference control policy here is used to determine whether to allow the creation of a sub-meeting, and may be a main conference control strategy. The second creation module may obtain the main conference control policy from the conference control center, or obtain a conference control policy for determining whether to allow the sub-conference to be created from other network devices. After the second creation module determines that the sub-conference is allowed to be created by using the conference control policy, the sub-conference is established by reusing the conference control center, that is, the Conference Focus „the main conference session channel and the sub-conference session channel corresponding to the independent sub-conference instance do not need to be created. The main conference session channel and the sub-conference session channel can also be mutually independent conference session channels. The specific implementation process of creating a sub-meeting is as described in the foregoing method implementation manner.

The first interaction module can be set in the conference server. The first interaction module utilizes the conference session between the conference control center and each participating user to interact with the participating users participating in the main conference and the conference. The first interaction module can control the conference session to be used as the primary conference session when the participant user participates in the primary conference, and is used as the conference conference session when the participant user participates in the conference.

The first interaction module may distinguish the content of the main conference session, the content of the conference session, and the like sent by the participant user according to the notification of the judgment module. The judging module is set in the conference server. After the main conference control center is successfully established, it belongs to the main conference control center. The judging module can determine whether the content of the main conference session or the content of the sub-conference session is sent by the participating user by determining the control signaling sent by the participating user. The judging module can also determine whether the content of the main conference session or the content of the sub-conference session is sent by the participating user by determining the conference identifier carried in the content of the conference session sent by the participant user. After receiving the notification of the judging module, the first interaction module may send the main conference session content, or send the sub-conference session content, or send the main conference session content and the sub-conference session content to the participating user according to the status of the participating user. The specific implementation process of the judging module distinguishing the content of the conference session and the first interaction module to implement the session content interaction can be as follows:

When the conference user sends a conference session request to notify the conference control center that the content of the conference session sent by the conference control center is the content of the conference conference session or the conference conference session, the determination module determines that the conference user sends the conference conference session request. After the conference identifier is determined to be the primary conference identifier, the first interaction module is notified: the content of the conference session sent by the participant user is the content of the conference session; the judgment module determines that the conference identifier is the conference conference identifier. The first interaction module is notified: the content of the conference session sent by the participating user is the content of the conference session. When the conference user informs the conference control center by carrying the conference identifier in the conference session content, the judging module judges the conference identifier carried in the session content sent by the conference user, and after determining that the conference identifier is the main conference identifier, The first interaction module is notified: the content of the conference session sent by the participant user is the content of the conference session; the judging module notifies the first interaction module after determining that the conference identifier is the sub-conference identifier: the conference session sent by the participant user The content is the content of the sub-conference session.

The second storage module in the first interaction module stores the participation status of the participating users in the primary and secondary conferences, and the sub-conference control policy. The sub-conference control policy may be: Allow or prohibit the sub-conferences that participate in the main conference at the same time. The participating users send the content of the main conference session. The participation status of the participating users is as described in the above method implementation.

The fourth control module in the first interaction module sends the sub-conference session content to the sub-conference participants, or sends the main conference session content and the sub-conference session content according to the information stored in the second storage module and the notification of the determination module. The fourth control module may send the conference session content to the sub-conference participant user or the main conference participant user through the shared conference session channel; the fourth control module may also send the conference participant channel to the participant user participating in the main conference through the independent main conference session channel. The main conference session content, and the sub-conference session content is sent to the participating users participating in the sub-conference through a separate sub-conference session channel. Participating users participating in the main meeting and sub-conference at the same time To receive the main conference session content and the sub-conference session content, the fourth control module may mix the received main conference session content and the sub-conference session content, and then participate in the conference that needs to receive the main conference session content and the sub-conference session content. User sent.

At the same time, the participating users participating in the main conference sub-conference can choose whether to receive the main conference session content and the sub-conference session content, and the participating users who participate in the main conference and the sub-conference can also choose to exit the main conference or exit the sub-conference. The fourth control module may send the conference session content that matches the selection of the participant user to the participant user, so that the conference user can selectively receive the conference session content.

The third receiving request module in the fourth control module is configured to receive multiple requests sent by the primary conference participant user and the child conference participant user. The fifth control module in the fourth module may send the content of the conference session matched with the participant user selection according to the information stored by the second storage module and the request received by the third receiving request module, and the following examples are exemplified. The specific implementation process of the fifth control module sending the content of the conference session:

The first receiving request module receives the receiving primary conference session request sent by the sub-conference participant, and the receiving primary conference session request carries the primary conference identifier, or carries the primary conference identifier and at least one designated conference. User Info.

The fifth control module may be configured according to the participation status of each participating user in the main conference stored by the second storage module, when the main conference session request carries the primary conference identifier and does not carry the specified at least one participant user information. Information (such as the main conference participant user list information). Determine whether the sub-conference participant who sent the request is the main conference participant user. If the user is the main conference participant, the sub-conference to which the main conference session request is received is sent. The participant user sends the content of the main conference session; if the user is not the primary conference participant, the primary conference session content is not sent to the conference participant who sends the conference request.

The fifth control module may be configured according to the participation status information of each participating user in the main conference stored by the second storage module, when the main conference session request carries the primary conference identifier and the specified at least one participant user information. (For example, the main conference participant user list information) Determine whether the specified conference participant user is the main conference participant user. If the conference participant is the main conference participant, the main conference session content is sent to the designated conference participant; If the user is not the main conference participant, the content of the main conference session is not sent to the designated participant. It should be noted that, if there are multiple designated users, if one of the designated users is the main conference participant and the other conference users are not the main conference participants, then the user is assigned to the conference. The participating users send the main conference session content without sending the main conference session content to the designated other participating users.

Example 2: The third receiving request module receives the request to stop receiving the main conference session sent by the sub-conference participant, and the request to stop receiving the main conference session carries the main conference identifier, or carries at least one of the main conference identifier and the designated one. Participate in user information.

When the request to stop receiving the main conference session carries the primary conference identifier and does not carry the specified at least one participant user information, the fifth control module may directly determine that the conference user who sends the request to stop receiving the primary conference session is not sent. The content of the main conference session, the fifth control module may also judge the participating users according to the participation status information of each participating user in the main conference stored by the second storage module (such as the main conference participant user list information), and then perform the judgment. Determine the operation. Specifically, it is described in the above method embodiment.

The fifth control module may directly determine that the content of the main conference session is not sent to the designated participant user, in the case that the request to stop receiving the primary conference session carries the primary conference identifier and the specified at least one participant user information; The control module may also determine the participating users according to the participation status information of each participating user in the main conference stored by the second storage module (such as the main conference participant user list information), and then perform the determining operation. Specifically, it is as described in the above method embodiment.

The third receiving request module receives the receiving sub-conference session request sent by the main conference participant user, where the receiving main conference session request carries the sub-conference identifier, or carries the sub-conference identifier and the specified at least one participant. User Info. When the receiving sub-conference session request carries the sub-conference identifier and does not carry the specified at least one participant user information, the fifth control module may be configured according to the participation status of each participating user in the sub-conference stored by the second storage module. The information (such as the sub-conference participation user list information) determines whether the main conference participant user who sent the request is the sub-conference participant user. If the sub-conference is also the participant user, the main conference is sent to the receiving sub-conference session request. The participant user sends the sub-conference session content; if it is not the sub-conference participant user, the sub-conference session content is not sent to the main conference participant user who sends the receiving sub-conference session request.

In the case that the receiving sub-conference session request carries the sub-conference identifier and the specified at least one participant user information, the fifth control module may obtain the participation status information of each participating user in the sub-conference stored by the second storage module. (For example, the sub-conference participation user list information) determines whether the specified conference participant user is a sub-conference participant user. If the sub-conference is also a participant, the sub-conference session content is sent to the designated conference user; If the user is not a sub-conference participant, the sub-conference session content is not sent to the designated participant. It should be noted that if there are multiple designated users, if one of the specified users is a sub-conference participant and the other participant is not a sub-conference user, then the user is The participating users send the content of the sub-conference session without sending the sub-conference session content to the specified other participating users.

The fourth receiving request module receives the stop receiving sub-conference session request sent by the main conference participant user, and the stop receiving sub-conference session request carries the sub-conference identifier, or carries at least one of the sub-conference identifier and the specified one. Participate in user information.

When the request to stop receiving the sub-conference session carries the primary conference identifier and does not carry the specified at least one participant user information, the fifth control module may directly determine that the conference user that sends the request to stop receiving the conference session is not sent. The content of the sub-conference session, the fifth control module may also judge the participating users according to the participation status information of each participating user in the sub-conference stored in the second storage module (such as the sub-conference participation user list information), and then perform the Determine the operation. Specifically, it is described in the above method embodiment.

The fifth control module may directly determine that the sub-conference session content is not sent to the designated participant user, if the sub-conference identifier is carried in the request to stop receiving the sub-conference session, and the specified at least one participant user information is included; The control module may also determine the participating users according to the participation status information of each participating user in the sub-conference stored in the second storage module (such as the sub-conference participation user list information), and then perform the determining operation. Specifically, it is as described in the above method embodiment.

For example, the third receiving request module receives the exiting primary conference request sent by the primary conference participant user, and the exit primary conference request carries the primary conference identifier. The fifth control module does not send the content of the main conference session to the participating users who send the request to exit the main conference according to the primary conference identifier carried in the request. The fifth control module may further update the information stored in the second storage module according to the request to exit the main conference, for example, update the participation status of the participating users in the main conference (including the main conference participant list information). The fifth control module may determine, according to the specific situation of the main sub-conference session channel and the specific situation of the conference user receiving the conference session, whether to release the conference session between the conference user and the conference control center that sends the request to exit the main conference, and according to the judgment As a result, a corresponding release operation is performed, as described in the above method embodiment.

For example, the third receiving request module receives the exit sub-conference request sent by the sub-conference participant, and the exit sub-conference request carries the sub-conference identifier. The fifth control module does not send the sub-conference session content to the participating users who send the request to exit the sub-meeting according to the sub-conference identifier carried in the request. The fifth control module may further update the information stored in the second storage module according to the exit sub-meeting request, for example, update the participation status of the participating users in the sub-conference (including the sub-conference participation user list information). The fifth control module may determine, according to the specific situation of the main sub-conference session channel and the specific situation of the conference user receiving the conference session, whether to release the conference session between the conference user and the conference control center that sends the request to exit the sub-conference, and according to the judgment As a result, a corresponding release operation is performed, as described in the above method embodiment. After the specific implementation process of the judgment module distinguishing the conference session content and the first interaction module implementing the session content interaction is briefly introduced in an exemplary manner, the second termination module and the second release module are described below.

The second termination module is set in the conference server, and belongs to the conference control center side after the conference control center of the main conference is successfully established. After determining that the main conference needs to be terminated, the second termination module notifies the second release module, and terminates the main conference after the second release module releases the conference statements. The second termination module may determine whether the main conference needs to be terminated after the third receiving request module receives the request to exit the main conference, such as determining whether there is a main conference participant user in the main conference, as described in the foregoing method implementation manner.

The second release module is disposed in the conference server, and belongs to the conference control center side after the conference control center of the main conference is successfully established. After receiving the notification of the second termination module, the second release module separately sends an exit sub-meeting request to each sub-conference participant user, and releases the conference session between the conference control center and the main sub-conference participant user. After the second release module successfully releases the conference session, the second termination module is notified.

The terminal device provided by the embodiment of the present invention will be described below.

The terminal device provided by the embodiment of the present invention includes a session establishing module and a second interaction module. The second interaction module may include: any one or any of the first transmission control module, the second transmission control module, and the reception control module.

The session establishment module establishes a conference session with the conference control center. For example, when a user needs to participate in a main conference, the session establishment module in the terminal device establishes a conference session between the user and the conference control center by interacting with the information between the conference server. For another example, when the user requests to participate in the sub-conference without participating in the main conference, the session establishing module in the terminal device establishes a conference session between the user and the conference control center by performing information interaction with the conference server.

The second interaction module uses the conference session between the conference control center and the conference user established by the session establishment module to interact with the conference control center to exchange the conference content. The second interaction module can control the state of the conference session. For example, when the conference user participates in the conference, the second interaction module controls the conference session to be used as the primary conference session, and, for example, when the participant user participates in the conference, The second interaction module controls the conference session to be used as a sub-conference session.

The foregoing operations of the second interaction module can be implemented: In the case that the terminal device does not have the parallel session capability, the participating users using the terminal device can participate in the main conference and the sub conference at the same time.

The terminal device can send the main conference session content and the sub-conference session content to the conference control center in the following two manners.

Manner 1: The first sending control module sends a sending conference session request carrying the conference identifier to the conference control center, and then sends the conference session content corresponding to the conference identifier to the conference control center. For example, the first sending control module transmits a conference session request to the conference control center, where the request carries the primary conference identifier, and the first sending control module sends the response information returned by the conference control center to the conference control center after the terminal device receives the response information returned by the conference control center. Main meeting session content. The process of sending the content of the sub-conference session by the first sending control module is similar to the above process, and will not be described here.

Manner 2: The second sending control module sends the conference session content carrying the conference identifier to the conference control center. For example, the second sending control module sends the main conference session content carrying the primary conference identifier to the conference control center, or the second sending control module sends the conference conference content carrying the conference conference identifier to the conference control center.

The receiving control module can send various requests to the conference control center to enable the terminal device to receive the conference session content it needs. For example, the receiving control module may send any one or more of the following requests to the conference control center: receiving a primary conference session request, receiving a conference session request, stopping receiving a primary conference session request, stopping receiving a conference session request, and exiting The main meeting requests, exits the sub-conference request. Each of the foregoing requests may carry a conference identifier, and may also carry a conference identifier and at least one designated conference user. Specifically, it is as described in the above method embodiment. The two private conference implementing apparatuses provided by the embodiments of the present invention are described below.

One of the private meeting implementation devices includes a fourth receiving request module and a sixth control module, and the private meeting implementing device can be set in the conference server.

The fourth receiving request module receives the private conference session sent by the participating user and occupies the conference session channel request. Private conference session The conference session channel request can carry a private session indication, send a private conference session user ID, and receive a private conference session user ID. The private session indication is used to indicate that a conference session channel needs to occupy a private conference session. After receiving the above request, the private conference session temporarily occupies the existing conference session channel between the conference user and the conference control center.

The sixth control module can determine, according to the information carried in the session session channel request of the private conference session, the participant who needs to send the content of the private conference session, and the participant who needs to receive the content of the private conference session. The sixth control module may determine the content of the conference session that is subsequently sent by the participant user who sends the private conference session user identifier as the private conference session content, until the participant user who has sent the private conference session user identifier switches to the primary conference or the conference. In this embodiment, the content of the private conference session sent by the participant user may not carry the participant user information for receiving the content of the private conference session, which is specifically described in the foregoing method implementation manner.

Another private conference implementation apparatus includes a fifth receiving request module, a setup session channel module, and a seventh control module. The private conference implementation device can be set in the conference server. The private conference implementation device uses the existing conference session to establish a new conference session channel for the private conference, and uses the newly established conference session channel to implement the transmission of the private conference session content.

The fifth receiving request module receives the private meeting session request sent by the participating user. A private conference session request indicates that a private conference is required, and the request can carry the information of the participant who participates in the private conference.

The establishment of the session channel module can clearly know which participating users need to conduct a private conference according to the private conference session request, that is, a private conference session channel needs to be established between the conference control center and which participating users. Establish a session channel module to establish a private conference session channel between the conference control center and each participating user who needs to conduct a private conference.

The seventh control module can determine, by the transmission channel of the conference session content received by the conference control center, whether the content of the conference session received by the conference control center is a private conference session content, and the seventh control module determines that the content of the conference session received is After the content of the private conference session, the private conference session content is sent to other participants in the private conference. The other participating users here are the participating users in the private meeting except the participating users who send the content of the meeting session.

While the invention has been described by the embodiments of the invention, it will be understood that

Claims

Rights request

A method for implementing a sub-conference, comprising:

Obtain primary conference status information;

2. The method of claim 1, wherein the process of creating the sub-meeting comprises:

Obtain a primary conference control policy, and determine whether to allow a sub-conference to be created according to the primary conference control policy;

After determining that the sub-conference is allowed to be created, a sub-conference control center is created, and the sub-conference control center requests to subscribe to the main conference status information.

The method according to claim 1, wherein the sending the content of the sub-conference session or the content of the main conference session to each sub-conference participant according to the participation status of each participating user in the sub-conference And sub-conference sessions include:

Sending the content of the sub-conference session or the content of the main conference session and the content of the sub-conference session to each sub-conference participant according to the participation status of the participating users in the sub-conference and the sub-conference control policy;

The sub-conference control policy includes: enabling/disabling the sending of the main conference session content to the sub-conference participant users who are simultaneously participating in the main conference.

The method according to claim 1, wherein the determining, according to the acquired main conference state information, the participation status of each participating user in the sub-conference, according to the participating users in the sub-conference The method of sending the sub-conference session content to the sub-conference participants, or sending the main conference session content and the sub-conference session content includes:

Receiving a request for receiving a main conference session sent by a sub-conference participant user;

Determining, according to the main conference status information, that the sub-conference participant user who sent the request is the main conference participant user, and sending the main conference session content and the sub-conference session content to the sub-conference participant user that sends the receiving the main conference session request;

And / or include:

Receiving a primary conference session request sent by the sub-conference participant user, where the receiving primary conference session request carries at least one designated conference participant user;

And determining, according to the main conference status information, that the designated sub-conference participant user is the main conference participant user, and sending the main conference session content and the sub-conference session content to the designated sub-conference participant user.

The method of claim 4, wherein the method further comprises:

After receiving the primary conference session request sent by the sub-conference participant user, the one-way main conference session channel of the primary conference control center to the sub-conference control center is established to receive the content of the main conference session sent by the main conference control center.

The method of claim 1, wherein the method further comprises:

The sub-conference control center receives the request to stop receiving the main conference session sent by the sub-conference participant user;

The sub-conference control center does not send the main conference session content to the sub-conference participant who sends the request;

And/or the method further includes:

The sub-conference control center receives the request to stop receiving the main conference session sent by the sub-conference participant user, and the stop receiving the main conference session request carries the designated at least one sub-conference participant user;

The sub-conference control center does not send the main conference session content to the designated sub-conference participant.

The method of claim 6, wherein the method further comprises:

After the sub-conference control center determines that the sub-conference participants stop receiving the main conference session, the sub-conference control center requests the main conference control center to exit the sub-conference, and releases the main conference session channel between the main conference control center and the sub-conference control center.

8. The method of claim 1, wherein the method further comprises:

The main conference control center receives the receiving sub-conference session request sent by the main conference participant user;

The main conference control center determines, according to the obtained sub-conference status information, that the main conference participant user who sends the request is the sub-conference participant user, and the main conference control center sends the main conference session content and the sub-conference session to the main conference participant user who sends the request. content.

9. The method of claim 8, wherein: the method further comprises:

After receiving the sub-conference session request sent by the main conference participant, the main conference control center establishes a one-way sub-conference session channel from the sub-conference control center to the main conference control center;

Alternatively, after receiving the receiving sub-conference session request sent by the main conference participant user, the main conference control center requests to update the existing one-way main conference session channel with the sub-conference control center to establish the sub-conference control center to the main conference control. Central sub-conference session channel.

The method of claim 8, wherein the method further comprises:

The main conference control center receives the request to stop receiving the sub-conference session sent by the main conference participant user;

The primary conference control center does not send the conference conference content to the primary conference participant user who sends the request to stop receiving the conference conference session.

The method of claim 1, wherein the method further comprises:

The main conference control center receives the request for exiting the main conference sent by the user participating in the main conference;

The main conference control center releases the main conference session with the main conference participant user, and sends a notification of the main conference state information change to the conference control center;

After the sub-conference control center determines that the participant user who exits the main conference is the sub-conference participant user, the sub-conference control center does not send the main conference session content to the sub-conference participant user. .

The method of claim 1, wherein the method further comprises:

Before the main conference is terminated, the main conference control center sends a sub-conference termination instruction to the sub-conference control center;

The sub-conference control center releases the sub-conference session with each sub-conference participant and returns a response to the main conference control center; the main conference control center terminates the main conference after receiving the response.

13. A method for implementing a sub-conference, comprising:

14. The method of claim 13 wherein:

The conference control center interacts with the participating users participating in the main conference and the sub-conference through a conference session with each participating user;

The conference session is used as the primary conference session when the participant user participates in the primary conference, and serves as the conference conference session when the participant user participates in the conference.

15. The method of claim 14 wherein:

The sub-conference session shares a media transmission channel with the main conference session; or The sub-conference session is independent of the media transmission channel of the main conference session.

The method according to claim 14, wherein the conference control center interacts with the participating users of the participating conferences and the conference participants by the conference session with each conference user, and includes:

The conference control center sends the sub-conference session content to each sub-conference participant according to the participation status of the participating users in the main sub-conference, and the sub-conference control policy, or sends the main conference session content and the sub-conference session content;

The conference control center receives the sending conference session request that is sent by the participant user and carries the conference identifier;

The conference control center determines that the conference identifier is a primary conference identifier, and the conference control center sends the session content sent by the conference user that sends the request to the conference user that needs to receive the content of the main conference session; or, the conference control center determines The conference identifier is a sub-conference identifier, and the conference control center sends the session content sent by the conference user that sends the request to the conference user who needs to receive the content of the conference conference session.

The conference control center receives the session content sent by the participant user and carries the conference identifier;

The session control center determines that the conference identifier is a primary conference identifier, and the conference control center sends the session content to a conference user that needs to receive the content of the primary conference session; or, the session control center determines that the conference identifier is a conference conference identifier. The conference control center sends the session content to the participating users who need to receive the content of the sub-conference session.

The conference control center receives the receiving primary conference session request sent by the sub-conference participant user;

The conference control center determines, according to the main conference status information, that the sub-conference participant user who sent the request is the main conference participant user, and the conference control center sends the main conference session content and the sub-conference session to the sub-conference participant user that sends the request. Content; and / or include:

The conference control center receives the receiving primary conference session request sent by the sub-conference participant user, and the receiving the primary conference session request carries the designated at least one sub-conference participant user;

The conference control center determines, according to the main conference status information, that the designated sub-conference participant user is the main conference participant user, and the conference control center sends the main conference session content and the sub-conference session content to the designated sub-conference participant user.

The conference control center receives the request to stop receiving the main conference session sent by the sub-conference participant user;

The conference control center does not send the content of the main conference session to the sub-conference participant who sends the request;

And / or include:

The conference control center receives the request to stop receiving the main conference session sent by the sub-conference participant user, and the request to stop receiving the main conference session carries the main conference identifier and the designated at least one sub-conference participant user;

The conference control center does not send the content of the main conference session to the sub-conference participants specified in the request.

The conference control center receives the receiving sub-conference session request sent by the main conference participant user;

The conference control center determines, according to the sub-conference status information, that the primary conference participant user who sends the request is a child conference participant user, and the conference control center sends the primary conference session content and the conference conference session to the primary conference participant user that sends the request. Content; and / or include:

The conference control center receives the receiving sub-conference session request sent by the main conference participant user, and the receiving sub-conference session request carries the designated at least one main conference participant user;

The conference control center determines, according to the sub-conference status information, that the designated main conference participant user is a sub-conference participant user, and the conference control center sends the main conference session content and the sub-conference session content to the designated main conference participant user.

The method according to claim 14, wherein the conference control center interacts with the participating users of the participating conferences and the conference participants by the conference session with the conference users, and includes:

The conference control center receives the stop receiving sub-conference session request sent by the main conference participant user;

The conference control center does not send the content of the sub-conference session to the main conference participant who sends the request;

And / or include:

The conference control center receives the stop receiving sub-conference session request sent by the main conference participant user, and the stop receiving sub-conference session request carries the designated at least one main conference participant user;

The conference control center does not send the sub-conference session content to the primary conference participant user specified in the request.

The method of claim 14, wherein the method further comprises:

The conference control center receives the request for exiting the main conference sent by the user of the main conference;

The conference control center updates the main conference status information, and does not send the main conference session content to the conference user who sends the request to exit the main conference;

And/or the method further includes:

The conference control center receives the exit sub-conference request sent by the sub-conference participant user;

The conference control center updates the sub-conference status information, and does not send the sub-conference session content to the participating users who send the exit sub-meeting request.

The method of claim 14, wherein the method further comprises:

Before terminating the main conference, the conference control center sends an exit sub-conference request to the sub-conference participant to release the conference session with the main sub-conference participant;

The conference control center terminates the main conference.

25. A private conference implementation method, characterized in that:

The method of claim 25, wherein the method specifically includes:

The conference control center determines, according to the received private session session, the private session indication carried in the conference session channel request, the private conference session user identifier, and the private conference session user identifier, the participant who needs to send the private conference session content, and needs to receive Participant users of private conference session content; After the conference control center determines that the content of the conference session received from the conference session channel is the private conference session content, the conference control center sends the conference content to the conference user who needs to receive the private conference session content. The content of the conference session.

27. A method for implementing a private conference, characterized in that:

The method of claim 27, wherein the method for receiving and transmitting the private conference session content comprises: the conference control center receiving the conference session content sent by the conference user;

After the conference control center determines that the transmission channel of the content of the conference session is a private conference session channel, it determines other participating users who participate in the private conference except for the conference user who sends the content of the conference session;

The conference control center transmits the conference session content by using a private conference session channel with the other participating users.

29. A sub-conference implementation apparatus, comprising:

30. The device of claim 29, wherein the device further comprises:

The first creating module obtains the primary conference control policy, and determines whether to allow the sub-conference to be created according to the primary conference control policy, and determines that the sub-conference control center is created after the sub-conference is allowed to be created;

And during the process of creating a sub-conference, the acquisition module requests to subscribe to the main conference status information.

The device of claim 29, wherein the first control module comprises:

The first storage module is configured to store the participation status of the participating users in the sub-conference, and the sub-conference control policy. The sub-conference control policy includes: enabling or disabling the sending of the main conference to the sub-conference participants participating in the main conference. Conversational content;

The second control module is configured to send the sub-conference session content to the sub-conference participant users according to the information stored by the first storage module, or send the main conference session content and the sub-conference session content.

The device of claim 31, wherein the first control module further comprises:

The first receiving request module is configured to receive a primary conference session request sent by the sub-conference participant user, and/or stop receiving the primary conference session request; the request carries the primary conference identifier, or carries the primary conference identifier and the designated At least one sub-conference to participate in the user;

The second control module sends the sub-conference session content or the main conference session content and the sub-conference session content according to the information stored by the first storage module and the request received by the first receiving request module to each sub-conference participant.

33. The device of claim 29, wherein the device further comprises:

a second receiving requesting module, configured to receive a receiving sub-conference session request sent by a main conference participant user, and/or to stop receiving a sub-conference request, where the request carries a sub-conference identifier;

a third control module, configured to determine, according to the acquired sub-conference status information, a main conference participation for sending and receiving a sub-conference session request If the user is a sub-conference participant user, the main conference session content and the sub-conference session content are sent to the main conference participant user who sent the request, and/or, and the stop receiving sub-conference session request received according to the second receiving request module is not used. The content of the sub-conference session is sent to the main conference participant who sends the request to stop receiving the sub-conference session.

34. The device of claim 29, wherein the device further comprises:

a first termination module, configured to send a sub-conference termination indication to the sub-conference control center before the termination of the main conference;

The first release module releases the sub-conference session between the sub-conference control center and each sub-conference participating user according to the sub-conference termination indication sent by the first termination module, and returns a response to the first termination module, where the first termination module receives Terminate the main conference after the response.

35. A sub-conference implementation apparatus, wherein the apparatus comprises:

36. The device of claim 35, wherein the device further comprises:

a first interaction module, configured to use the conference session between the conference control center and each participating user to interact with the participating user in the main conference and the conference;

The conference session is used as a primary conference session when the participant user participates in the primary conference, and is used as a conference conference session when the conference user participates in the conference.

37. The device of claim 36, wherein the first interaction module comprises:

The second storage module is configured to store the participation status and the sub-conference control policy of each participating user in the primary sub-conference; the sub-conference control policy includes: enabling or disabling the sending of the main conference session to the sub-conference participating users participating in the main conference simultaneously Content

And a fourth control module, configured to send, according to the information stored in the second storage module, the content of the sub-conference session or the content of the main conference session and the content of the sub-conference session to each sub-conference participant.

38. The device of claim 36 or 37, wherein the device further comprises:

The judging module is configured to determine the conference identifier carried in the sending conference session request sent by the participant user, and notify the conference component content sent by the participant of the first interaction module as the main conference session content or the sub-conference session according to the judgment result. Or the content of the conference session carried in the session content sent by the participant user, and the content of the conference session sent by the participant of the first interaction module is notified as the content of the conference session or the content of the conference session. .

39. The device of claim 37, wherein the fourth control module comprises:

a third receiving requesting module, configured to receive a receiving primary conference session request sent by a sub-conference participant user, where the receiving primary conference session request carries a primary conference identifier;

And a fifth control module, configured to determine, according to the information stored by the second storage module, the sub-conference participant user that sends the request to be the main conference participant user, and send the main message to the sub-conference participant user that sends the receiving the main conference session request Conference session content and sub-conference session content;

Wohe / or

The third receiving requesting module is configured to receive a receiving primary conference session request sent by the sub-conference participant user, where the receiving the primary conference session request carries the primary conference identifier and the designated at least one sub-conference participant user;

a fifth control module, configured to determine, according to the information stored by the second storage module, that the designated sub-conference participant user is the main conference participant user, and send the main conference session content and the sub-station to the designated sub-conference participant user Conference session content; And/or

a third receiving requesting module, configured to receive a request to stop receiving the main conference session sent by the sub-conference participant user, where the stop receiving the main conference session request carries the main conference identifier;

a fifth control module, configured to not send the content of the main conference session to the sub-conference participant who sends the request to stop receiving the main conference session;

Wohe / or

a third receiving requesting module, configured to receive a request to stop receiving the main conference session sent by the sub-conference participant user, where the request to stop receiving the main conference session carries the main conference identifier and the designated at least one sub-conference participant user;

a fifth control module, configured to stop sending the content of the main conference session to the sub-conference participant specified in the stop receiving the main conference session request;

Wohe / or

The third receiving request module is configured to receive a receiving sub-conference session request sent by the main conference participant user, where the receiving sub-conference request carries the sub-conference identifier;

a fifth control module, configured to determine, according to the information stored by the second storage module, that the primary conference participant user who sends the receiving sub-conference session request is a sub-conference participant user, and sends the request to receive the sub-conference session request The conference participant user sends the content of the main conference session and the content of the sub-conference session;

Wohe / or

The third receiving request module is configured to receive a receiving sub-conference session request sent by the main conference participant user, where the receiving sub-conference request carries the sub-conference identifier and the designated at least one main conference participant user;

a fifth control module, configured to determine, according to the information stored by the second storage module, that the designated primary conference participant user is a child conference participant user, and send the main conference session content and the child to the designated primary conference participant user Conference session content;

Wohe / or

The third receiving request module is configured to receive a stop receiving sub-conference session request sent by the main conference participant user, where the stop receiving sub-conference session request carries the sub-conference identifier;

a fifth control module, configured to not send the content of the sub-conference session to the main conference participant who sends the request to stop receiving the sub-conference session;

Wohe / or

The third receiving request module is configured to receive a stop receiving sub-conference session request sent by the main conference participant user, where the stop receiving sub-conference session request carries the sub-conference identifier and the designated at least one main conference participant user;

a fifth control module, configured to not send the content of the sub-conference session to the designated main conference participant user;

Wohe / or

a third receiving request module, configured to receive an exit primary conference request sent by a primary conference participant user;

a fifth control module, configured to send the content of the main conference session to the primary conference participant who sends the request to withdraw from the primary conference; and/or

a third receiving request module, configured to receive an exit sub-conference request sent by the sub-conference participant user;

The fifth control module is configured to not send the sub-conference session content to the sub-conference participant user that sends the exit sub-conference request.

40. The device according to claim 36 or 37 or 38 or 39, wherein the device further comprises: a second termination module, configured to notify the conference control center of the main conference before terminating the main conference, and Terminate the main conference after the conference session is released;

a second release module, configured to send an exit sub-conference request to the sub-conference participant according to the notification of the second termination module, and release the conference A conference session between the control center and the participating users of the main sub-conference.

41. A terminal device, comprising:

a second interaction module, configured to use a conference session between the conference control center and the conference user to interact with the conference control center; and the second interaction module controls the conference session to be used when the conference user participates in the conference The primary conference session, when the participant user participates in the conference, the second interaction module controls the conference session to be used as a conference session.

The terminal device according to claim 41, wherein the second interaction module comprises any one or more of the following modules:

a first sending control module, configured to send, to the conference control center, a sending conference session request that carries the conference identifier, and then send the conference session content corresponding to the conference identifier;

a second sending control module, configured to send, to the conference control center, the content of the conference session carrying the conference identifier;

The receiving control module is configured to send any one or more of the following requests to the conference control center: receiving a primary conference session request, receiving a conference session request, stopping receiving a primary conference session request, stopping receiving a conference session request, and exiting The main conference request, the exit sub-conference request; the request carries the conference identifier, or carries the conference identifier and the designated at least one participant user.

43. A private conference implementation apparatus, comprising:

44. A private conference implementation apparatus, comprising: