Conference management method and device, communication equipment, chip and storage medium

Abstract

The embodiment of the invention provides a conference management method, and relates to the technical field of wireless communication, and the method comprises the steps that in response to joining request information sent by network equipment, a first terminal sends subscription information to the network equipment, and the subscription information is used for obtaining terminal information in a current conference; first feedback information sent by the network equipment is received, the first feedback information comprises terminal information in the current conference, and the terminal information comprises an identifier and a state of a terminal; based on the first feedback information, a first request is sent to the network device, the first request comprises the identification and the operation type of the terminal, and the first request is used for adding the terminal to the current conference and / or removing the terminal from the current conference. According to the method provided by the invention, the function of managing the conference by the conference participant can be realized, the function of the conference participant is enhanced, and the conference participant can also manage other participants in the current conference.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to the field of wireless communication technologies, and in particular, to a conference management method and apparatus, a communication device, a chip, and a storage medium. Background Art

[0002] VoLTE (Voice over LTE, Long-Term Evolution Voice Bearer) / VoNR (Voice over New Radio, New Radio Bearer for Voice) is an IP-based data transmission technology. Both voice calls and data services are carried on the 4G / 5G network, allowing users to access the Internet while making calls, and at the same time providing shorter call connection waiting times, higher quality, and more natural voice and video call effects. In scenarios such as multi-party calls or conference calls, the conference initiator can initiate a conference call and has the function of managing conference participants, while conference participants do not yet have the function of managing the conference. Summary of the Invention

[0003] The present disclosure provides a conference management method and apparatus, a communication device, a chip, and a storage medium, realizing the function of managing a conference by conference participants.

[0004] In a first aspect embodiment of the present disclosure, a conference management method is proposed. The method includes: in response to join request information sent by a network device, a first terminal sends subscription information to the network device, and the subscription information is used to obtain terminal information in the current conference; receiving first feedback information sent by the network device, the first feedback information includes terminal information in the current conference, and the terminal information includes the identifier and status of the terminal; based on the first feedback information, sending a first request to the network device, the first request includes the identifier of the terminal and the operation type, and the first request is used to add and / or remove a terminal from the current conference.

[0005] In some embodiments of the present disclosure, sending a first request to the network device based on the first feedback information includes: based on the first feedback information, determining the number of terminals in the first state in the current conference; in the case where the number of terminals is less than the terminal number threshold, sending a first request to the network device, the first request includes the identifier of a second terminal and the operation type, and the operation type of the second terminal is the first type.

[0006] In some embodiments of the present disclosure, sending a first request to the network device based on the first feedback information includes: based on the first feedback information, determining at least one third terminal in the first state in the current conference; sending a first request to the network device, the first request includes the identifier of the third terminal and the operation type, and the operation type of the third terminal is the second type.

[0007] In some embodiments of the present disclosure, the method further includes: receiving at least one of the following sent by a network device: the identifier and status of a terminal in a first state; the identifier and status of a terminal in a second state; the identifier and status of a terminal added to the current meeting by a fourth terminal; the identifier and status of a terminal removed from the current meeting by a fourth terminal.

[0008] An embodiment of the second aspect of the present disclosure provides a conference management method, the method including: after a network device sends a join request message to a first terminal, receiving a subscription message sent by the first terminal, the subscription message being used to obtain terminal information in the current conference; sending a first feedback message to the first terminal, the first feedback message including terminal information in the current conference, the terminal information including the identifier and status of a terminal; receiving a first request sent by the first terminal, the first request including the identifier and operation type of a terminal, the first request being used to add and / or remove a terminal to / from the current conference.

[0009] In some embodiments of the present disclosure, the method further includes at least one of the following: based on the first request, sending a join request message to a second terminal, the first request including the identifier and operation type of the second terminal, and the operation type of the second terminal being a first type; based on the first request, sending a hang-up request message to a third terminal, the first request including the identifier and operation type of the third terminal, and the operation type of the third terminal being a second type.

[0010] In some embodiments of the present disclosure, the method further includes at least one of the following: in response to a response message sent by the second terminal, sending the identifier and status of the second terminal to the first terminal, the status of the second terminal being a first state; in response to a response message sent by the third terminal, sending the identifier and status of the third terminal to the first terminal, the status of the third terminal being a second state.

[0011] In some embodiments of the present disclosure, the method further includes: receiving a second request sent by a fourth terminal, the second request being used to add and / or remove a terminal to / from the current conference; sending the identifier and status of the terminal added to the current conference by the fourth terminal, or the identifier and status of the terminal removed from the current conference by the fourth terminal, to the fourth terminal and the first terminal.

[0012] In some embodiments of the present disclosure, the method further includes: receiving a create conference request sent by a fourth terminal, the create conference request including the identifier and operation type of at least one terminal; receiving a subscription message sent by the fourth terminal, the subscription message being used to obtain terminal information in the current conference; based on the create conference request, sending a join request message to at least one terminal; in response to a response message sent by at least one terminal, sending the terminal information in the current conference to the fourth terminal, the terminal information including the identifier and status of a terminal.

[0013] In the above embodiments, after the network device adds the first terminal to the current meeting, it may, based on the subscription information sent by the first terminal, feedback the terminal information in the current meeting to the first terminal, so as to implement the function of managing the meeting by the first terminal.

[0014] An embodiment of the third aspect of the present disclosure provides a meeting management device, including: a sending module, configured to send subscription information to a network device in response to a join request message sent by the network device, where the subscription information is used to obtain terminal information in the current meeting; a receiving module, configured to receive first feedback information sent by the network device, where the first feedback information includes terminal information in the current meeting, and the terminal information includes the identifier and status of the terminal; the sending module is further configured to send a first request to the network device, where the first request includes the identifier and operation type of the terminal, and the first request is used to add and / or remove a terminal from the current meeting.

[0015] An embodiment of the fourth aspect of the present disclosure provides a meeting management device, including: a sending module, configured to, after sending a join request message to a first terminal, receive subscription information sent by the first terminal, where the subscription information is used to obtain terminal information in the current meeting; send first feedback information to the first terminal, where the first feedback information includes terminal information in the current meeting, and the terminal information includes the identifier and status of the terminal; a receiving module, configured to receive a first request sent by the first terminal, where the first request includes the identifier and operation type of the terminal, and the first request is used to add and / or remove a terminal from the current meeting.

[0016] An embodiment of the fifth aspect of the present disclosure provides a communication device, including: a processor and a memory for storing a computer program that can run on the processor, where, when the processor is used to run the computer program, it executes the method according to any one of the first aspect or the second aspect of the present disclosure.

[0017] An embodiment of the sixth aspect of the present disclosure provides a non-transitory computer-readable storage medium storing computer instructions, where the computer instructions are used to cause a computer to execute the method according to any one of the first aspect or the second aspect of the present disclosure.

[0018] An embodiment of the seventh aspect of the present disclosure provides a chip, including at least one processor and a communication interface; the communication interface is configured to receive a signal input to the chip or a signal output from the chip, and the processor communicates with the communication interface and implements the method according to any one of the first aspect or the second aspect of the present disclosure through a logic circuit or by executing code instructions.

[0019] In summary, the method proposed in the present disclosure can implement the function of managing a meeting by the meeting participants, where the meeting participants other than the meeting initiator can add meeting participants to the meeting or remove other meeting participants from the meeting, enhancing the functions of the meeting participants and enabling the meeting participants to also manage other participants in the meeting.

[0020] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and do not limit the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The drawings herein are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with the present disclosure, and are used together with the specification to explain the principles of the present disclosure, and do not constitute an undue limitation on the present disclosure.

[0022] Figure 1A Schematic diagram for the establishment process of a general conference call;

[0023] Figure 1B Schematic diagram of the signaling flow for a general conference call;

[0024] Figure 1C Schematic diagram for the establishment process of a one - key conference call;

[0025] Figure 1D Schematic diagram of the signaling flow for a one - key conference call;

[0026] Figure 1E Schematic diagram for adding a user by the conference initiator;

[0027] Figure 1F Schematic diagram of the signaling flow for adding a user by the conference initiator;

[0028] Figure 1G Schematic diagram for the conference initiator to hang up a participant;

[0029] Figure 1H Schematic diagram of the signaling flow for the conference initiator to hang up a participant;

[0030] Figure 2 Schematic diagram of the architecture of a communication system;

[0031] Figure 3 Interaction schematic diagram of the conference management method proposed in the embodiments of the present disclosure;

[0032] Figure 4 Schematic flow diagram of the conference management method of the first terminal proposed in the embodiments of the present disclosure;

[0033] Figure 5 Schematic flow diagram of the conference management method of the network device proposed in the embodiments of the present disclosure;

[0034] Figure 6A Schematic diagram for a participant to add a user to the conference;

[0035] Figure 6B Schematic diagram for a participant to hang up other participants;

[0036] Figure 6C Schematic diagram of a subscriber message sent by a participant after joining a conference in a regular conference call;

[0037] Figure 6D Flow chart of a subscriber message sent by a participant in a regular conference call to the conference center after joining the conference;

[0038] Figure 6E Schematic diagram of a subscriber message sent by a participant after joining a conference in a one - key conference call;

[0039] Figure 6F Flow chart of a subscriber message sent by a participant in a one - key conference call to the conference center after joining the conference;

[0040] Figure 6G Signaling flow chart for a conference participant to add a user to a conference;

[0041] Figure 6H Signaling flow chart for a conference participant to hang up other participants;

[0042] Figure 7 Schematic diagram of the structure of a conference management device proposed in an embodiment of the present disclosure;

[0043] Figure 8 Schematic diagram of the structure of a conference management device proposed in an embodiment of the present disclosure;

[0044] Figure 9 Schematic diagram of a communication device for implementing the above - mentioned conference management method according to an exemplary embodiment;

[0045] Figure 10 Schematic diagram of the structure of a chip 1000 for implementing the above - mentioned conference management method according to an exemplary embodiment. Detailed implementation manners

[0046] The embodiments of the present disclosure will be described in detail below. The examples of the embodiments are shown in the accompanying drawings, where the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions from beginning to end. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to explain the present disclosure, and should not be construed as limiting the present disclosure.

[0047] In VoLTE (Voice over LTE, voice calls based on the LTE network) / VONR (Voice over New Radio, voice calls based on the new generation network) technology, conference calls are also known as multi-party calls or three-party calls. The characteristic of its application scenario is that when there are more than 2 users, multiple users can talk to each other, and each user can hear the speech content of other users in the conference call. In the framework of the IMS (IP Multimedia Subsystem) conference call system, according to different roles and divisions of labor, it can be divided into three types of devices:

[0048] Conference initiator: The terminal device that initiates the conference call, which has the function of managing the conference, including adding users and removing users.

[0049] Conference participant: The terminal device other than the conference initiator in the conference call.

[0050] Conference center: The network device that connects the conference initiator and each conference participant on the network side.

[0051] The conference call service in VoLTE technology is established based on the IMS (IP Multimedia Subsystem) system, and its establishment process uses the SIP (Session Initiation Protocol) messages of the IMS system. The main SIP messages related to conference calls are:

[0052] INVITE: The session initiation process in SIP-based communication, which is used to create a conference call or a single-call phone call.

[0053] re-INVITE: It is used to modify the phone-related attributes.

[0054] SUBSCRIBE: It is used to subscribe to the status of all conference members including the initiator and participants in the conference. After successful subscription, when the status of a conference member changes, the network-side conference center sends a NOTIFY message to notify the conference members of the status change.

[0055] NOTIFY: It is used to notify the status of conference members, and the relevant information is in the XML message body carried by NOTIFY.

[0056] XML: Extensible Markup Language, extensible markup language.

[0057] REFER: It is used to operate on a single user in the conference, such as adding or hanging up a user, etc.

[0058] BYE: Hang up the phone.

[0059] According to the different ways of establishing a conference call, it can be divided into a three-way session and an ad-hoc conference.

[0060] The process of establishing a three-way session is as Figure 1A shown in the schematic diagram of the process of establishing a three-way session: User A is on a call with User B, User A is on a call with User C, User A merges User B and C, and a conference call is established among User A, B, and C. Among them, User A is the conference initiator, and User B and C are conference participants. The signaling process is as Figure 1B shown in the schematic diagram. Process description: 1. The prerequisite for establishing a three-way session is the existence of two point-to-point single-channel calls AB and AC; 2. User A sends an INVITE message to the conference center to request the establishment of a connection with the conference center; 3. The connection between User A and the conference center is successfully established; 4. User A sends a SUBSCRIBE message to the conference center to subscribe to the conference status, and the conference center sends a NOTIFY message to User A when a participant enters or leaves the conference; 5. User A sends a REFER message to the conference center to request adding User B to the conference; 6. After User B joins the conference, the network releases the original point-to-point call between AB; 7. User A sends a REFER message to the conference center to request adding User C to the conference; 8. After User C joins the conference, the network releases the original point-to-point call between AC; 9. A three-way session is established among User A, B, and C, where User A is the conference initiator and User B and C are conference participants.

[0061] The process of establishing an ad-hoc conference is as Figure 1C shown in the schematic diagram of the process of establishing an ad-hoc conference: User A checks the numbers of User B and C on the interface and initiates an ad-hoc conference call. After receiving the incoming call, User B and C answer, and an ad-hoc conference call is established among User A, B, and C. User A is the conference initiator, and User B and C are conference participants. The signaling process is as Figure 1DAs shown in the figure. Process description: 1. Before the establishment of a one-key conference call, there is no point-to-point call. User A sends an INVITE message to the conference center to request a connection with the conference center, and the numbers of Users B and C are carried in the XML message body of the INVITE; 2. User A sends a SUBSCRIBE message to the conference center to subscribe to the conference status. Subsequently, when a participant enters or leaves the conference, the conference center sends a NOTIFY message to notify User A; 3. After User A successfully establishes a connection with the conference center, the conference center pages User B and User C according to the numbers carried in the XML message body of the INVITE; 4. After Users B and C answer the call, the conference center will send a NOTIFY message to User A, and the status information that Users B and C have entered the conference is carried in the XML message body of the NOTIFY. 5. Users A, B, and C have established a one-key multi-party conference call, where User A is the conference initiator, and Users B and C are conference participants.

[0062] Currently, there are two specific ways for the conference initiator to manage the conference as follows:

[0063] As Figure 1E shown in the schematic diagram of the conference initiator adding users. After the establishment of an ordinary conference call or a one-key conference call, the conference initiator can add users to the conference by means of one-key invitation. For example: Users A, B, and C have established a conference call, where User A is the conference initiator, and Users B and C are conference participants. User A checks the number of User D on the interface and initiates a one-key invitation operation. After User D receives the call and answers it, User D joins the conference. The signaling process is as Figure 1F shown in the figure. Process description: 1. The conference initiator A sends a REFER message to the conference center, and the number of User D and the operation method (join or hang up) INVITE are carried in the Refer-To header field of the REFER message. Here is a join request; 2. The conference center pages User D according to the number of User D in the Refer-To header field of the REFER message; 3. After User D answers the call, the conference center will send a NOTIFY message to the conference initiator User A, and the status information that User D has entered the conference is carried in the XML message body of the NOTIFY.

[0064] As Figure 1G shown in the schematic diagram of the conference initiator hanging up a participant. After the establishment of an ordinary conference call or a one-key conference call, the conference initiator hangs up a certain participant separately. For example: Users A, B, and C have established a conference call, where User A is the conference initiator, and Users B and C are conference participants. User A selects to hang up User C on the conference management interface, and User C disconnects from the conference. The signaling process is as Figure 1HAs shown in the figure. Process description: 1. The meeting initiator A selects to hang up user C and sends a REFER message to the conference center. The Refer-To header field of the REFER message carries the number of user C and the operation method BYE; this is a hang-up request. 2. The conference center hangs up user C according to the number of user C in the Refer-To header field of the REFER message. 3. After user C is hung up, the conference center sends a NOTIFY message to the meeting initiator A, and the XML message body of the NOTIFY carries the status information that user C has been disconnected.

[0065] The present disclosure proposes a method for a meeting participant to manage a meeting, enabling the participants in the meeting to also achieve the same functions as the meeting initiator, adding participants to the meeting, and hanging up other participants in the meeting except themselves.

[0066] This method is executed by a communication system, such as Figure 2 As shown in the figure, the communication system includes a terminal 201 and a network device 202. The terminal includes a first terminal, a second terminal, and a third terminal. In some embodiments, the communication system further includes a fifth terminal.

[0067] In an embodiment of the present disclosure, the communication device can be, for example, a terminal, a network device, or a chip, and there is no limitation thereto. The meeting management method proposed by the present disclosure can be executed by a terminal, or by a chip or a processor of the terminal.

[0068] The following method of the embodiment of the present disclosure can be applied to a communication system. The communication system can include a terminal and a network device. The network device can include at least one of an access network device and a core network device. The communication system can include all or part of the above-mentioned main bodies, or can include other main bodies. The number and form of each main body are arbitrary. The connection relationship between the main bodies is illustrative. The main bodies can be not connected or connected. Their connection can be in any way, either directly connected or indirectly connected, either wired connected or wireless connected.

[0069] In some embodiments, the terminal includes, for example, at least one of a mobile phone, a wearable device, an Internet of Things device, a vehicle with communication function, a smart vehicle, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, and a wireless terminal in smart home, but is not limited thereto.

[0070] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include at least one of an evolved NodeB (eNB) in a 5G communication system, a next-generation evolved NodeB (ng-eNB), a next-generation NodeB (gNB), a NodeB (NB), a home NodeB (HNB), a home evolved NodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an Open RAN, a Cloud RAN, a base station in other communication systems, and an access node in a WiFi system, but is not limited thereto.

[0071] In some embodiments, the technical solution of the present disclosure is applicable to the Open RAN architecture. At this time, the interfaces between or within the access network devices involved in the embodiments of the present disclosure may become the internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0072] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). Among them, the CU may also be referred to as a control unit. The use of the CU-DU structure can split the protocol layer of the access network device. The functions of some protocol layers are centrally controlled by the CU, and the functions of the remaining part or all protocol layers are distributed in the DU. The CU centrally controls the DU, but it is not limited to this.

[0073] In some embodiments, the core network device may be a single device including one or more network elements, or may be multiple devices or a group of devices, each including all or part of one or more network elements. The network elements may be virtual or physical. The core network includes, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0074] It can be understood that the communication system described in the embodiments of the present disclosure is to more clearly illustrate the technical solutions of the embodiments of the present disclosure, and does not constitute a limitation on the technical solutions proposed in the embodiments of the present disclosure. Those of ordinary skill in the art know that with the evolution of the system architecture and the emergence of new service scenarios, the technical solutions proposed in the embodiments of the present disclosure are equally applicable to similar technical problems.

[0075] Embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), 6th generation mobile communication system (6G), Future Radio Access (FRA), New Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine to Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), systems using other communication methods, next-generation systems extended based on them, etc. In addition, multiple systems can be combined (for example, a combination of LTE or LTE-A and 5G, etc.) and applied. The resource allocation method proposed in the present disclosure can be executed by a terminal, or by a chip or a processor of the terminal.

[0076] The conference management method proposed in this application will be introduced in detail below with reference to the accompanying drawings.

[0077] Figure 3 An interaction schematic diagram of a conference management method proposed in an embodiment of the present disclosure. As Figure 3 shown, the method includes the following steps:

[0078] Step 301, the fourth terminal sends a conference creation request to the network device.

[0079] In some embodiments, the conference creation request includes the identifiers of at least one terminal and the operation type.

[0080] In some embodiments, the fourth terminal is the conference initiator of the current conference. In other words, the fourth terminal sends a conference creation request to the network device to create the current conference.

[0081] In some embodiments, the conference creation request includes multiple terminals invited to join the conference, and the operation type is the first type, where the first type is join or add.

[0082] In some embodiments, the fourth terminal can create the current conference in the way of an ordinary conference call establishment process, as Figure 1A , Figure 1B shown, or it can be a one-key conference call establishment process, as Figure 1C , Figure 1D shown.

[0083] Exemplarily, the conference initiator sends an INVITE message to the conference center to request the establishment of a connection with the conference center, and the conference center sends a feedback to the conference initiator to notify the successful establishment of the connection.

[0084] Step 302, the fourth terminal sends subscription information to the network device.

[0085] In some embodiments, the subscription information is used to obtain the terminal information in the current conference.

[0086] In some embodiments, the fourth terminal sends subscription information to the network device to obtain information about other terminals joining or leaving the conference subsequently.

[0087] Exemplarily, the conference initiator sends a SUBSCRIBE message to the conference center to subscribe to the conference status.

[0088] Step 303, the network device sends join request information to at least one terminal based on the conference creation request.

[0089] In some embodiments, the conference creation request includes the identifiers of at least one terminal, for example, the identifiers of the first terminal and the third terminal.

[0090] In some embodiments, the network device sends join request information to the first terminal based on the conference creation request.

[0091] In some embodiments, based on a conference creation request, the network device sends join request information to a third terminal.

[0092] In some embodiments, the conference creation request includes the identifier of the first terminal and an operation type. If the operation type is the first type, i.e., join or add, the network device sends join request information to the first terminal so that the first terminal can join the current conference.

[0093] Exemplarily, during the establishment of an ordinary conference call, user A, the conference initiator, sends a REFER message to the conference center to request adding user B to the conference, and the conference center sends a re-INVITE message to user B.

[0094] Exemplarily, during the establishment of a one-key conference call, user A, the conference initiator, sends an INVITE request to the conference center to establish a conference call. The numbers of user B and user C are carried in the request, and the conference center paging user B and user C.

[0095] Step 304, at least one terminal sends response information to the network device.

[0096] In some embodiments, at least one terminal sends response information based on the join request information to join the current conference.

[0097] Exemplarily, during the establishment of an ordinary conference call, user B and user C respectively send responses to the re-INVITE message to the conference center to join the current conference.

[0098] Exemplarily, during the establishment of a one-key conference call, after receiving the paging initiated by the conference center, user B and user C join the current conference.

[0099] Step 305, the network device sends fifth feedback information to a fourth terminal.

[0100] In some embodiments, the fifth feedback information includes terminal information in the current conference, and the terminal information includes the identifier and status of the terminal.

[0101] In some embodiments, in the current conference, only the fourth terminal has the function of managing the conference, that is, the network device needs to send the terminal information of the current conference to the fifth terminal.

[0102] Exemplarily, in an ordinary conference call, after user B and user C join the current conference, the conference center sends a NOTIFY message to user A, the conference initiator, to notify user A.

[0103] For example, in a one-key conference call, after user A establishes a connection with the conference center, if a participant joins or leaves the conference subsequently, the conference center will send a NOTIFY message to user A to notify user A. After user B and user C answer the call, the conference center will send a NOTIFY message to user A, and the status information that user B and user C have entered the conference will be carried in the xml message body of the NOTIFY. User A has established a multi-party conference call with user B and user C. User A is the conference initiator, and user B and user C are the conference participants.

[0104] Step 306, in response to the join request information sent by the network device, the first terminal sends subscription information to the network device.

[0105] In some embodiments, the subscription information is used to obtain the terminal information in the current conference.

[0106] In some embodiments, the first terminal is the terminal invited by the fourth terminal to join the current conference, which can be understood as a conference participant in the current conference.

[0107] In some embodiments, in response to the join request information sent by the network device, the first terminal joins the current conference and determines whether to send subscription information to the network device.

[0108] In some embodiments, the first terminal may or may not send subscription information to the network device. When the first terminal needs to have the function of managing the conference, it sends subscription information to the network device. If it does not need to have the function of managing the conference, it does not send subscription information to the network device. The present disclosure does not limit this.

[0109] In some embodiments, the first terminal may be one or more. For example, one first terminal sends subscription information to the network device to manage the current conference, or multiple first terminals all send subscription information to the network device, and then each first terminal can manage the current conference.

[0110] For example, a participant who expects to manage the conference first needs to obtain the information (including numbers and status) of all users (including the conference initiator and participants) in the conference. The participant who expects to manage the conference sends a SUBSCRIBE message to the conference center when joining the conference to subscribe to the status of other users in the conference. When other users join or leave the conference, the participant who expects to manage the conference can receive a NOTIFY message from the conference center and obtain the information of other users.

[0111] For example, as Figure 6C shown in the schematic diagram and Figure 6DIn the shown flowchart, after Party B of the meeting participants joins the meeting (Party B learns that it has been added to the meeting according to the "isfocus" parameter carried in the Contact header field of the re-INVITE message), it sends a SUBSCRIBE message to the meeting center to subscribe to the information of all users in the meeting.

[0112] Step 307, the network device sends first feedback information to the first terminal.

[0113] In some embodiments, the first feedback information includes terminal information in the current meeting, and the terminal information includes the identifier and status of the terminal.

[0114] In some embodiments, the network device sends first feedback information to the first terminal based on the subscription information sent by the first terminal to inform the first terminal of the terminal information in the current meeting.

[0115] In some embodiments, the identifier of the terminal may be the number corresponding to the terminal, and the status of the terminal may be the first status or the second status of the terminal currently. The first status may be the joined status, and the second status may be the left status. Exemplarily, the first status is that the terminal has entered the meeting or is online, and the second status is that the call has been hung up.

[0116] Exemplarily, the meeting center sends a NOTIFY message to Party B of the meeting participants to inform Party B of the numbers and statuses of the terminals in the current meeting, such as the numbers of the terminals that have joined the current meeting.

[0117] Step 308, the first terminal sends a first request to the network device based on the first feedback information.

[0118] In some embodiments, the first request includes the identifier of the terminal and the operation type, and the first request is used to add and / or remove terminals in the current meeting.

[0119] In some embodiments, the first terminal may send a first request to the network device based on the first feedback information. The first request is used to add a terminal to the current meeting; or the first request is used to remove a terminal from the current meeting. It can be understood that the identifier of the terminal in the first request may be the identifier of one terminal or the identifiers of multiple terminals, and the present disclosure does not limit this.

[0120] In some embodiments, the first terminal may send different first requests to the network device, including a first request to add a terminal to the current meeting and a first request to remove a terminal. The two first requests may be sent simultaneously or separately. Among them, the identifiers of the terminals in the first requests are different, and the operation types are also different; the identifier of the terminal corresponding to the same operation type may be one or multiple, and the present disclosure does not limit this.

[0121] In some embodiments, different first terminals may respectively send a first request to a network device based on first feedback information. The identifier and operation type of the terminal in the first request may be the same or different, and the present disclosure places no restrictions thereon.

[0122] The following takes the case where the first request includes the identifier of one terminal as an example for illustration. It can be understood that the identifier of the terminal in the first request may be one or more, the number of first requests may be one or more, and the first terminals sending the first requests may be one or more.

[0123] In some embodiments, the first request includes the identifier and operation type of a second terminal or the identifier and operation type of a third terminal. The first request is used to add the second terminal to the current meeting or remove the third terminal from the current meeting. It can be understood that adding a terminal means adding a meeting participant to the current meeting, and removing a terminal from the current meeting means hanging up other participants except oneself in the current meeting.

[0124] In some embodiments, based on the first feedback information, the first terminal can obtain the identifiers of the terminals that have joined the current meeting to manage the current meeting. The purpose for the first terminal to obtain the first feedback information is as follows: when adding a terminal, to avoid duplicate addition; when removing a terminal, to remove the corresponding terminal according to the identifier and status of the terminal; and to determine whether to add a terminal to the current meeting to ensure that the number of terminals in the meeting does not exceed the terminal number threshold.

[0125] In some embodiments, the first terminal can manage the current meeting. For example, it can add a terminal to the current meeting or remove a terminal from the current meeting.

[0126] Solution 1: Add a terminal to the current meeting.

[0127] In some embodiments, based on the first feedback information, the first terminal determines the number of terminals in the first state in the current meeting; when the number of terminals is less than the terminal number threshold, the first terminal sends a first request to the network device. The first request includes the identifier and operation type of a second terminal, and the operation type of the second terminal is the first type.

[0128] In some embodiments, based on the identifiers of the terminals in the current meeting sent by the network device, the first terminal determines the number of terminals in the first state. When the number of terminals is less than the terminal number threshold, it indicates that the number of terminals in the current meeting has not reached the upper limit value, and a terminal can be added to the meeting. Then, the first terminal sends a first request to the network device to add the second terminal to the current meeting.

[0129] In some embodiments, the operation types are divided into a first type and a second type. The first type is join or add, and the second type is remove or hang up. Exemplarily, the first type is INVITE, and the second type is BYE.

[0130] In some embodiments, when the fourth terminal adds a terminal to the current conference, it also needs to determine the number of terminals in the first state in the current conference according to the feedback information sent by the network device. When the number of terminals is less than the terminal number threshold, a terminal is added to the current conference.

[0131] Exemplarily, as Figure 6G shown in the flowchart, conference participant B sends a REFER message to the conference center. Among them, the Refer-To header field of the REFER message carries the number of user D and the operation method INVITE.

[0132] Solution two: Remove the terminal in the current conference.

[0133] In some embodiments, the first terminal determines at least one third terminal in the first state in the current conference based on the first feedback information; sends a first request to the network device, and the first request includes the identifier of the third terminal and the operation type, and the operation type of the third terminal is the second type.

[0134] In some embodiments, the first terminal determines the third terminal in the joined state in the current conference according to the first feedback information sent by the network device, and the third terminal can be one or more.

[0135] In some embodiments, the first terminal sends a first request to the network device according to the identifier of at least one third terminal. The first request may include the identifiers of one or more third terminals and the operation type, and the operation type is to remove the conference, so as to remove one or more third terminals from the current conference.

[0136] Exemplarily, as Figure 6H shown in the flowchart, conference participant B selects to hang up user C and sends a REFER message to the conference center. Among them, the Refer-To header field of the REFER message carries the number of user C and the operation method BYE.

[0137] In some embodiments, solution one and solution two can be executed simultaneously or separately, and the present disclosure does not limit this.

[0138] Step 309, the network device sends join request information to the second terminal based on the first request.

[0139] In some embodiments, the first request includes the identifier of the second terminal and the operation type, and the operation type of the second terminal is the first type.

[0140] In some embodiments, the network device sends a join request message to the corresponding second terminal based on the first request sent by the first terminal, so as to add the second terminal to the current conference.

[0141] Exemplarily, as Figure 6G shown in the flowchart, the conference center pages user D according to the number of user D in the Refer-To header field of the REFER message. After user D answers the call, user D is added to the current conference.

[0142] In some embodiments, step 309 is optional, that is, when the operation type in the first request is the first type, step 309 is executed; when the operation type in the first request is the second type, step 309 is not executed.

[0143] Step 310, the network device sends second feedback information to the first terminal.

[0144] In some embodiments, the network device sends second feedback information to the first terminal in response to the response information sent by the second terminal.

[0145] In some embodiments, the network device sends second feedback information to the first terminal. The second feedback information includes terminal information in the current conference. The terminal information includes the identifier and status of the second terminal, and the status of the second terminal is the first status.

[0146] In some embodiments, the network device determines the terminal information in the current conference based on the response of the second terminal, and sends the terminal information to the first terminal to inform the first terminal that the second terminal has been added to the current conference.

[0147] In some embodiments, based on the response of the second terminal, the network device also sends second feedback information to the fourth terminal to inform the fourth terminal that the second terminal has been added to the current conference.

[0148] Exemplarily, as Figure 6G shown in the flowchart, after user D answers the call, the conference center sends a NOTIFY message to conference participant B, and carries the status information that user D has entered the conference in the xml message body of the NOTIFY.

[0149] In some embodiments, step 310 is optional, that is, when the operation type in the first request is the first type, step 310 is executed; when the operation type in the first request is the second type, step 310 is not executed.

[0150] Step 311, the network device sends a hang-up request message to the third terminal based on the first request.

[0151] In some embodiments, the first request includes the identifier of the third terminal and the operation type, and the operation type of the third terminal is the second type.

[0152] In some embodiments, based on the request from the first terminal to remove the third terminal, the network device sends a hang-up request message to the corresponding third terminal.

[0153] In some embodiments, the network device may send a hang-up request message to one or more third terminals to remove one or more third terminals from the current conference.

[0154] Exemplarily, as Figure 6H shown in the flowchart, the conference center hangs up user C according to the number of user C in the Refer-To header field of the REFER message.

[0155] In some embodiments, step 311 is optional. That is, when the operation type in the first request is the second type, step 311 is executed; when the operation type in the first request is the first type, step 311 is not executed.

[0156] Step 312, the network device sends third feedback information to the first terminal.

[0157] In some embodiments, in response to the response information sent by the third terminal, the network device sends third feedback information to the first terminal.

[0158] In some embodiments, the network device sends third feedback information to the first terminal. The third feedback information includes terminal information in the current conference. The terminal information includes the identifier and status of the third terminal, and the status of the third terminal is the second status.

[0159] In some embodiments, after receiving the response from the third terminal based on the hang-up request message, the network device sends third feedback information to the first terminal to inform the first terminal that the third terminal has been removed. Among them, the third feedback information includes the identifier of the third terminal and the status of the third terminal, and the status of the third terminal is the leave status.

[0160] Exemplarily, as Figure 6H shown in the schematic diagram, after user C is hung up, the conference center sends a NOTIFY message to conference participant B, and carries the status information that user C has disconnected in the xml message body of the NOTIFY.

[0161] In some embodiments, the network device also sends third feedback information to the fourth terminal to inform the fourth terminal that the third terminal has been removed from the current conference.

[0162] In some embodiments, step 312 is optional. That is, when the operation type in the first request is the second type, step 312 is executed; when the operation type in the first request is the first type, step 312 is not executed.

[0163] Step 313, the fourth terminal sends a second request to the network device.

[0164] In some embodiments, the second request is used to add a fifth terminal to the current meeting or remove the fifth terminal from the current meeting.

[0165] Solution 1: Add the fifth terminal to the current meeting.

[0166] In some embodiments, the fourth terminal may determine whether the number of terminals in the current meeting exceeds the terminal number threshold based on the second feedback information or the third feedback information. When it does not exceed, the fourth terminal sends a second request to the network device to add the fifth terminal to the current meeting.

[0167] Exemplarily, the meeting initiator A sends a REFER message to the conference center. The Refer-To header field of the REFER message carries the number of user E and the operation method INVITE.

[0168] In some embodiments, the network device sends a join request message to the fifth terminal based on the second request. After receiving the response message of the fifth terminal, the fifth terminal is added to the current meeting.

[0169] Solution 2: Remove the fifth terminal from the current meeting.

[0170] In some embodiments, the fourth terminal may determine the fifth terminal in the first state in the current meeting based on the second feedback information or the third feedback information, and send a second request to the network device. The second request includes the identifier of at least one fifth terminal and the operation type, and the operation type is the second type.

[0171] Exemplarily, the meeting initiator A sends a REFER message to the conference center. The Refer-To header field of the REFER message carries the number of user H and the operation method BYE.

[0172] In some embodiments, the network device sends a hang-up request message to the fifth terminal based on the second request. After receiving the response message of the fifth terminal, the fifth terminal is removed from the current meeting.

[0173] Step 314, the network device sends fourth feedback information to the first terminal and the fourth terminal.

[0174] In some embodiments, the fourth feedback information includes terminal information in the current meeting, and the terminal information includes the identifier and status of the fifth terminal.

[0175] Solution 1:

[0176] In some embodiments, after the network device receives the response from the fifth terminal based on the join request information, it sends fourth feedback information to the first terminal and the fourth terminal to inform the first terminal and the fourth terminal that the fifth terminal has been added to the current meeting.

[0177] Solution 2:

[0178] In some embodiments, after the network device receives the response from the fifth terminal based on the hangup request information, it sends fourth feedback information to the first terminal and the fourth terminal to inform the first terminal and the fourth terminal that the fifth terminal has been removed from the current meeting.

[0179] In some embodiments, steps 313 and 314 are optional.

[0180] In the above embodiments, the meeting participant, i.e., the first terminal, can manage the terminals in the current meeting, including adding terminals to the current meeting or removing terminals from the current meeting, thereby realizing the function of the meeting participant managing the meeting.

[0181] Figure 4 It is a schematic flowchart of the meeting management method proposed by the embodiments of the present disclosure. Based on Figure 3 the embodiments shown, this method is executed by the first terminal, and the method includes the following steps:

[0182] Step 401, in response to the join request information sent by the network device, send subscription information to the network device.

[0183] In some embodiments, the subscription information is used to obtain the terminal information in the current meeting.

[0184] In some embodiments, the optional implementation manner of step 401 can refer to Figure 3 the optional implementation manner of step 306 in , and details are not described herein again.

[0185] Step 402, receive the first feedback information sent by the network device.

[0186] In some embodiments, the first feedback information includes the terminal information in the current meeting, and the terminal information includes the identifier and status of the terminal.

[0187] In some embodiments, the optional implementation manner of step 402 can refer to Figure 3 the optional implementation manner of step 307 in , and details are not described herein again.

[0188] Step 403, based on the first feedback information, send a first request to the network device.

[0189] In some embodiments, the first request includes the identifier of the terminal and the type of operation, and the first request is used to add and / or remove terminals from the current conference.

[0190] In some embodiments, for the optional implementation of step 403, reference may be made to Figure 3 the optional implementation of step 308 in [reference], which will not be elaborated here.

[0191] In the above embodiments, the first terminal may, in response to the join request from the network device, apply to manage the current conference, send subscription information to the network device, and based on the feedback from the network device, send a first request to the network device to manage the terminals in the current conference, including adding terminals and removing terminals.

[0192] Figure 5 It is a schematic flowchart of the conference management method proposed in the embodiments of the present disclosure. Based on Figure 3 the embodiments shown, this method is executed by the network device. As Figure 5 shown, it includes the following steps.

[0193] Step 501: After sending a join request message to the first terminal, receive the subscription information sent by the first terminal.

[0194] In some embodiments, the subscription information is used to obtain the terminal information in the current conference.

[0195] In some embodiments, for the optional implementation of step 501, reference may be made to Figure 3 the optional implementation of step 306 in [reference], which will not be elaborated here.

[0196] Step 502: Send a first feedback message to the first terminal.

[0197] In some embodiments, the first feedback message includes the terminal information in the current conference, and the terminal information includes the identifier and status of the terminal.

[0198] In some embodiments, for the optional implementation of step 502, reference may be made to Figure 3 the optional implementation of step 307 in [reference], which will not be elaborated here.

[0199] Step 503: Receive the first request sent by the first terminal.

[0200] In some embodiments, the first request includes the identifier of the terminal and the type of operation, and the first request is used to add and / or remove terminals from the current conference.

[0201] In some embodiments, for the optional implementation of step 503, reference may be made to Figure 3 the optional implementation of step 308 in [reference], which will not be elaborated here.

[0202] In the above embodiments, the network device may, based on the subscription request of the first terminal, feed back the terminal information in the current conference to the first terminal, so that the first terminal can manage the terminals in the current conference, including adding terminals and removing terminals. It realizes that a conference participant other than the conference initiator can add a conference participant to the conference or remove other conference participants in the conference, enhancing the functions of the conference participants and enabling the conference participants to also manage other participants in the conference.

[0203] The following are the specific implementation manners of the method for a participant to manage a conference:

[0204] Figure 6A Schematic diagram for a participant to add a user to a conference, which specifically includes the following steps: (1) The conference participant user B sends a REFER message to the conference center with the number of user D, requesting to add D to the conference; (2) The conference center pages user D, and after user D answers, user D joins the conference.

[0205] Figure 6B Schematic diagram for a participant to hang up other participants, which specifically includes the following steps: (1) The conference participant user B sends a REFER message to the conference center with the number of user C, requesting to hang up user C; (2) The conference center sends a BYE message to user C to hang up user C.

[0206] According to the above two management methods, the method for a participant to manage a conference is specifically divided into the following steps:

[0207] Step 1: Obtain the status of all users

[0208] A participant who expects to manage a conference first needs to obtain the information (including numbers and status) of all users (including the conference initiator and participants) in the conference. The participant who expects to manage the conference sends a SUBSCRIBE message to the conference center when joining the conference to subscribe to the status of other users in the conference. When other users join or leave the conference, the participant who expects to manage the conference can receive a NOTIFY message from the conference center to obtain the information of other users.

[0209] According to the different ways of establishing a conference call, in a normal conference call and a one-key conference call, after a participant who expects to manage the conference joins the conference, they need to add and send a SUBSCRIBE subscription message, as Figure 6C and Figure 6E shown.

[0210] 1. A participant manages a conference in a normal conference call:

[0211] Figure 6C Schematic diagram for a participant to send a subscription message after joining a conference in a normal conference call, inFigure 1A On the basis of [the original], step 5a is added. After Party B joins the meeting, it sends a SUBSCRIBE message to the conference center to subscribe to the information of all users in the meeting. Figure 6D It is a schematic diagram of the process for an ordinary conference call participant to send a subscription message to the conference center after joining the meeting. On the basis of Figure 1B [the original], the following steps are added:

[0212] (1) After Party B, a meeting participant, joins the meeting (Party B learns that it has been added to the meeting according to the "isfocus" parameter carried in the Contact header field of the re-INVITE message), it sends a SUBSCRIBE message to the meeting initiator to subscribe to the information of all users in the meeting.

[0213] Supplementary note: The process for Party B to send a SUBSCRIBE message to the conference center is independent of the process for the meeting initiator, Party A, to send a SUBSCRIBE message to the conference center and they do not affect each other.

[0214] (2) After Party C joins the meeting, the conference center sends a NOTIFY message to Party B to notify the information of all users in the meeting.

[0215] Supplementary note: The purpose for Party B to obtain the information of all users in the meeting is as follows: When adding participants, it can avoid adding the same user repeatedly and control the number of added users not to exceed the maximum number of users allowed in the meeting; when hanging up a participant, it can hang up the corresponding participant according to the user's number and status.

[0216] 2. Participants in the one-key conference call manage the meeting:

[0217] Figure 6E It is a schematic diagram of the process for a participant in the one-key conference call to send a subscription message after joining the meeting. On the basis of Figure 1C [the original], it is added that after Party B joins the meeting, it sends a SUBSCRIBE message to the conference center to subscribe to the information of all users in the meeting.

[0218] Figure 6F It is a schematic diagram of the process for a participant in the one-key conference call to send a subscription message to the conference center after joining the meeting. The added process on the basis of Figure 1D [the original] is as follows:

[0219] (1) After Party B, a meeting participant, joins the meeting (Party B learns that it has been added to the meeting according to the "isfocus" parameter carried in the Contact header field of the re-INVITE message), it sends a SUBSCRIBE message to the meeting initiator to subscribe to the information of all users in the meeting.

[0220] (2) After Participant C joins the meeting, the conference center sends a NOTIFY message to Participant B to notify the information of all users in the meeting.

[0221] Step 2: Manage the meeting

[0222] Scenario 1: A meeting participant adds a user to the meeting

[0223] The application scenario where a meeting participant adds a user to the meeting is as Figure 6A shown, and the signaling process is as Figure 6G shown:

[0224] 1. Meeting Participant B sends a REFER message to the conference center. The Refer-To header field of the REFER message carries the number of User D and the operation method INVITE.

[0225] 2. The conference center pages User D according to the number of User D in the Refer-To header field of the REFER message;

[0226] 3. After User D answers the call, the conference center sends a NOTIFY message to Meeting Participant B, and the status information that User D has entered the meeting is carried in the xml message body of the NOTIFY.

[0227] Scenario 2: A meeting participant hangs up other participants

[0228] The application scenario where a meeting participant hangs up a participant in the meeting is as Figure 6B shown, and the signaling process is as Figure 6H shown:

[0229] 1. Meeting Participant B selects to hang up User C and sends a REFER message to the conference center. The Refer-To header field of the REFER message carries the number of User C and the operation method BYE;

[0230] 2. The conference center hangs up User C according to the number of User C in the Refer-To header field of the REFER message;

[0231] 3. After User C is hung up, the conference center sends a NOTIFY message to Meeting Participant B, and the status information that User C has been disconnected is carried in the xml message body of the NOTIFY.

[0232] In summary, the above method for a participant to manage a meeting enhances the functions of the meeting participants, enabling the meeting participants to also manage other participants in the meeting.

[0233] Figure 7 It is a schematic structural diagram of a meeting management device 700 according to an embodiment of the present disclosure. As Figure 7 shown, the device includes:

[0234] A sending module 710, configured to send a subscription message to a network device in response to a join request message sent by the network device, where the subscription message is used to obtain terminal information in the current conference.

[0235] A receiving module 720, configured to receive a first feedback message sent by the network device, where the first feedback message includes terminal information in the current conference, and the terminal information includes an identifier and a status of a terminal.

[0236] The sending module is further configured to send a first request to the network device, where the first request includes an identifier of a terminal and an operation type, and the first request is used to add and / or remove a terminal from the current conference.

[0237] In some embodiments, the sending module is further configured to determine, based on the first feedback message, a number of terminals in a first state in the current conference; and in a case where the number of terminals is less than a terminal number threshold, send a first request to the network device, where the first request includes an identifier of a second terminal and an operation type, and the operation type of the second terminal is a first type.

[0238] In some embodiments, the sending module is further configured to determine, based on the first feedback message, at least one third terminal in a first state in the current conference; and send a first request to the network device, where the first request includes an identifier of the third terminal and an operation type, and the operation type of the third terminal is a second type.

[0239] In some embodiments, the receiving module is further configured to receive at least one of the following sent by the network device: an identifier and a status of a terminal in a first state; an identifier and a status of a terminal in a second state; an identifier and a status of a terminal added to the current conference by a fourth terminal; and an identifier and a status of a terminal removed from the current conference by the fourth terminal.

[0240] Figure 8 The figure is a schematic structural diagram of a conference management apparatus 800 according to an embodiment of the present disclosure. As Figure 8 shown, the apparatus includes:

[0241] A sending module 810, configured to receive a subscription message sent by a first terminal after sending a join request message to the first terminal, where the subscription message is used to obtain terminal information in the current conference; and send a first feedback message to the first terminal, where the first feedback message includes terminal information in the current conference, and the terminal information includes an identifier and a status of a terminal.

[0242] A receiving module 820, configured to receive a first request sent by the first terminal, where the first request includes an identifier of a terminal and an operation type, and the first request is used to add and / or remove a terminal from the current conference.

[0243] In some embodiments, the sending module is further configured to send join request information to a second terminal based on a first request, where the first request includes the identifier and operation type of the second terminal, and the operation type of the second terminal is a first type; and send hang-up request information to a third terminal based on the first request, where the first request includes the identifier and operation type of the third terminal, and the operation type of the third terminal is a second type.

[0244] In some embodiments, the receiving module is further configured to, in response to response information sent by the second terminal, send the identifier and status of the second terminal to the first terminal, where the status of the second terminal is a first status; and in response to response information sent by the third terminal, send the identifier and status of the third terminal to the first terminal, where the status of the third terminal is a second status.

[0245] In some embodiments, the receiving module is further configured to receive a second request sent by a fourth terminal, where the second request is used to add and / or remove terminals from the current meeting; and the sending module is further configured to send the identifier and status of the terminals added to the current meeting by the fourth terminal, or the identifier and status of the terminals removed from the current meeting by the fourth terminal, to the fourth terminal and the first terminal.

[0246] In some embodiments, the receiving module is further configured to receive a create meeting request sent by the fourth terminal, where the create meeting request includes the identifiers and operation types of at least one terminal; receive subscription information sent by the fourth terminal, where the subscription information is used to obtain terminal information in the current meeting; and the sending module is further configured to send join request information to at least one terminal based on the create meeting request; and in response to response information sent by at least one terminal, send terminal information in the current meeting to the fourth terminal, where the terminal information includes the identifier and status of the terminal.

[0247] In summary, the conference management device proposed in the present disclosure can implement the function of managing a conference by conference participants, where conference participants other than the conference initiator can add conference participants to the conference or remove other conference participants from the conference, enhancing the functions of conference participants and enabling conference participants to also manage other participants in the conference.

[0248] Regarding the conference management device in the above embodiments, the specific manners in which each module performs operations have been described in detail in the embodiments related to the method, and will not be elaborated herein.

[0249] Figure 9 It is a schematic structural diagram of a communication device 900 for implementing the above conference management method shown according to an exemplary embodiment.

[0250] Refer to Figure 9, the communication device 900 may include one or more of the following components: a processing component 902, a memory 904, a power component 906, an input / output (I / O) interface 908, a sensor component 910, and a communication component 912.

[0251] The processing component 902 generally controls the overall operation of the communication device 900, such as operations associated with display, telephone calls, data communications, battery management, and recording operations. The processing component 902 may include one or more processors 920 to execute instructions to complete all or part of the steps of the above-described methods. In addition, the processing component 902 may include one or more modules to facilitate the interaction between the processing component 902 and other components. For example, the processing component 902 may include a balancing module to facilitate the interaction between the power component 906 and the processing component 902.

[0252] The memory 904 is configured to store various types of data to support the operation of the communication device 900. Examples of such data include instructions for any application or method operating on the communication device 900, contact data, phone book data, messages, pictures, videos, and the like. The memory 904 may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, a magnetic disk, or an optical disk.

[0253] The power component 906 provides power to various components of the communication device 900. The power component 906 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the communication device 900.

[0254] The I / O interface 908 provides an interface between the processing component 902 and a peripheral interface module, which may be a keyboard, a click wheel, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.

[0255] The sensor assembly 910 includes one or more sensors for providing a status assessment of various aspects of the communication device 900. For example, the sensor assembly 910 can detect the on / off state of the communication device 900, the relative positioning of components, such as components for the display and keypad of the communication device 900. The sensor assembly 910 can also detect a change in the position of the communication device 900 or a component of the communication device 900, the presence or absence of user contact with the communication device 900, the orientation or acceleration / deceleration of the communication device 900, and a change in the temperature of the communication device 900. The sensor assembly 910 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 910 can also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 910 can also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0256] The communication component 912 is configured to facilitate communication between the communication device 900 and other devices in a wired or wireless manner. The communication device 900 can access a wireless network based on communication standards, such as WiFi, 2G or 3G, 4G LTE, 5G NR (New Radio), or a combination thereof. In an exemplary embodiment, the communication component 912 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 912 further includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0257] In an exemplary embodiment, the communication device 900 can be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components for performing the above methods.

[0258] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions, such as a memory 904 including instructions, is also provided. The above instructions can be executed by a processor 920 of the communication device 900 to complete the above methods. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device, etc.

[0259] The present disclosure also provides a computer-readable storage medium, on which computer program instructions are stored. When the program instructions are executed by a processor, the steps of the meeting management method provided by the present disclosure are implemented.

[0260] An embodiment of the present disclosure also proposes a computer program product, including a computer program, which implements the meeting management method described in the foregoing embodiments of the present disclosure when executed by a processor.

[0261] Figure 10 is a schematic structural diagram of a chip 1000 for implementing the above-mentioned meeting management method shown according to an exemplary embodiment. Refer to Figure 10 , the chip 1000 includes at least one communication interface 1001 and a processor 1002. The communication interface 1001 is used to receive signals input to the chip 1000 or signals output from the chip 1000. The processor 1002 communicates with the communication interface 1001 and implements the meeting management method described in the foregoing embodiments of the present disclosure through logic circuits or by executing code instructions.

[0262] In addition, the word "exemplary" is used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as "exemplary" is not necessarily to be understood as being advantageous compared to other aspects or designs. Instead, the use of the word exemplary is intended to present concepts in a concrete manner. As used herein, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clear from the context, "X applies A or B" is intended to mean any permutation in a natural inclusive arrangement. That is, if X applies A; X applies B; or X applies both A and B, then "X applies A or B" is satisfied in any of the foregoing instances. Additionally, unless otherwise specified or clear from the context referring to the singular form, the articles "a" and "an" as used in this application and the appended claims are generally understood to mean "one or more".

[0263] Similarly, although the present disclosure has been shown and described with respect to one or more implementations, equivalent variations and modifications will occur to those skilled in the art upon reading and understanding this specification and the drawings. The present disclosure includes all such modifications and variations and is limited only by the scope of the claims. Specifically with respect to the various functions performed by the components described above (e.g., elements, resources, etc.), unless otherwise indicated, the terms used to describe such components are intended to correspond to any component (functionally equivalent) that performs the specific function of the described component, even if not structurally equivalent to the disclosed structure. Additionally, although a particular feature of the present disclosure may have been disclosed with respect to only one of several implementations, such a feature may be combined with one or more other features of other implementations as may be desired and advantageous for any given or particular application. Further, with respect to the use of "comprising," "having," "including," "contains," or variations thereof in the detailed description or claims, such terms are intended to be inclusive in a manner similar to the term "including."

[0264] Other embodiments of the present disclosure will be readily apparent to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include known or customary techniques in the art that are not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are pointed out by the following claims.

[0265] It should be understood that the present disclosure is not limited to the exact structures described above and shown in the drawings, and various modifications and changes may be made without departing from its scope. The scope of the present disclosure is limited only by the appended claims.

[0266] It should be noted that the terms "first," "second," etc. in the specification and claims of the present disclosure and in the above drawings are used to distinguish similar objects and not necessarily to describe a particular order or sequence. It should be understood that the data so used may be interchanged where appropriate so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. On the contrary, they are merely examples of apparatuses and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0267] In the description of this specification, the descriptions referring to terms such as "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples", or "some examples" etc. mean that the specific features, structures, materials, or characteristics described in connection with the embodiments or examples are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0268] Any process or method description represented in a flowchart or described otherwise herein may be understood to represent a module, segment, or portion of code including one or more executable instructions for implementing a specific logical function or process, and the scope of the preferred embodiments of the present disclosure includes additional implementations, where the functions may be executed in a manner not shown or discussed, including in a substantially simultaneous manner according to the functions involved or in a reverse order, which should be understood by those skilled in the art to which the embodiments of the present disclosure pertain.

[0269] The logic and / or steps represented in a flowchart or described otherwise herein, for example, may be considered as a sequenced list of executable instructions for implementing a logical function and may be specifically implemented in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, a system including a processing module, or other systems that can fetch instructions from and execute instructions of the instruction execution system, apparatus, or device. For the purposes of this specification, a "computer-readable medium" may be any device that can contain, store, communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium include the following: an electrical connection portion having one or more wirings (control method), a portable computer diskette (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium may even be paper or other suitable medium on which a program can be printed, because the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpretation, or otherwise processing as appropriate, and then stored in a computer memory.

[0270] It should be understood that each part of the embodiments of the present disclosure can be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, any one or a combination of the following techniques well known in the art can be used: discrete logic circuits having logic gate circuits for implementing logical functions on data signals, application specific integrated circuits having appropriate combinational logic gate circuits, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), etc.

[0271] Those of ordinary skill in the art can understand that all or part of the steps carried by the methods of the above embodiments can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiments.

[0272] In addition, in each of the embodiments of the present disclosure, each functional unit can be integrated into a processing module, or each unit can exist physically alone, or two or more units can be integrated into one module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. When the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. The above-mentioned storage medium can be a read-only memory, a magnetic disk, an optical disk, etc.

[0273] Although the embodiments of the present disclosure have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limitations on the present disclosure. Those of ordinary skill in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present disclosure.

Claims

1. A conference management method, characterized in that: The method comprises: In response to the joining request information sent by the network device, the first terminal sends subscription information to the network device, where the subscription information is used to obtain terminal information in the current conference; receiving first feedback information sent by the network device, where the first feedback information includes terminal information in the current conference, where the terminal information includes an identifier and a state of the terminal; Based on the first feedback information, a first request is sent to the network device, where the first request includes an identifier of a terminal and an operation type, and the first request is used to add a terminal to the current conference and / or remove a terminal.

2. The method according to claim 1, characterized in that The sending a first request to the network device based on the first feedback information includes: Based on the first feedback information, determining the number of terminals in the current conference that are in the first state; When the number of terminals is less than the terminal number threshold, the first request is sent to the network device, where the first request includes an identifier and an operation type of the second terminal, and the operation type of the second terminal is the first type.

3. The method according to claim 1, characterized in that The sending a first request to the network device based on the first feedback information includes: Based on the first feedback information, determining at least one third terminal in the current conference that is in the first state; The first request is sent to the network device, where the first request includes an identifier and an operation type of the third terminal, and the operation type of the third terminal is the second type.

4. The method according to claim 2 or 3, characterized in that: The method further comprises: Receiving at least one of the following sent by the network device: an identifier and a state of the terminal in the first state; The identification and state of the terminal in the second state; an identifier and a status of a fourth terminal added to the terminals in the current conference; The fourth terminal is an identifier and a status of a terminal removed from the current conference.

5. A conference management method, characterized in that: The method comprises: After sending a joining request message to the first terminal, the network device receives subscription information sent by the first terminal, where the subscription information is used to obtain terminal information in the current conference; Sending first feedback information to the first terminal, where the first feedback information includes terminal information in the current conference, where the terminal information includes an identifier and a state of the terminal; A first request sent by the first terminal is received, where the first request includes an identifier of a terminal and an operation type, and the first request is used to add a terminal to the current conference and / or remove a terminal.

6. The method according to claim 5, characterized in that The method further comprises at least one of the following: Based on the first request, sending the joining request information to the second terminal, where the first request includes an identifier and an operation type of the second terminal, and the operation type of the second terminal is the first type; Based on the first request, a hang-up request message is sent to a third terminal, wherein the first request includes an identifier and an operation type of the third terminal, and the operation type of the third terminal is the second type.

7. The method according to claim 6, characterized in that The method further comprises at least one of the following: In response to the response information sent by the second terminal, sending the identifier and state of the second terminal to the first terminal, where the state of the second terminal is a first state; In response to the response information sent by the third terminal, an identifier and a state of the third terminal are sent to the first terminal, and the state of the third terminal is a second state.

8. The method according to claim 5, characterized in that The method further comprises: receiving a second request sent by a fourth terminal, where the second request is used to add a terminal to the current conference and / or remove a terminal; Sending to the fourth terminal and the first terminal an identifier and a status of a terminal added by the fourth terminal to the current conference, or an identifier and a status of a terminal removed by the fourth terminal from the current conference.

9. The method according to claim 5, characterized in that The method further comprises: receiving a request for creating a conference sent by a fourth terminal, wherein the request for creating a conference includes an identifier and an operation type of at least one terminal; receiving subscription information sent by the fourth terminal, where the subscription information is used to obtain terminal information in the current conference; Based on the request to create a conference, sending the joining request information to the at least one terminal; In response to the response information sent by the at least one terminal, the terminal information in the current conference is sent to the fourth terminal, where the terminal information includes an identifier and a state of the terminal.

10. A conference management device, comprising: A sending module, configured to send subscription information to the network device in response to the joining request information sent by the network device, wherein the subscription information is used to obtain the terminal information in the current conference; A receiving module, configured to receive first feedback information sent by the network device, wherein the first feedback information includes terminal information in the current conference, and the terminal information includes an identifier and a state of the terminal; The sending module is further used to send a first request to the network device, where the first request includes an identifier of a terminal and an operation type, and the first request is used to add a terminal to the current conference and / or remove a terminal.

11. A conference management device, comprising: A sending module, configured to receive subscription information sent by the first terminal after sending a joining request message to the first terminal, wherein the subscription information is used to obtain information of terminals in the current conference; Sending first feedback information to the first terminal, where the first feedback information includes terminal information in the current conference, where the terminal information includes an identifier and a state of the terminal; The receiving module is configured to receive a first request sent by the first terminal, wherein the first request includes an identifier of a terminal and an operation type, and the first request is used to add a terminal to the current conference and / or remove a terminal.

12. A communication device, characterized in that: include: A processor and a memory for storing a computer program that can be run on the processor, wherein the processor, when being used to run the computer program, executes the method of any one of claims 1-4 or 5-9.

13. A non-transitory computer-readable storage medium storing computer instructions, characterized in that: The computer instructions are used to cause the computer to execute the method according to any one of claims 1-4 or 5-9.

14. A chip, characterized in that: It includes at least one processor and a communication interface; the communication interface is used to receive a signal input to the chip or a signal output from the chip, and the processor communicates with the communication interface and implements the method as described in any one of claims 1-4 or 5-9 through a logic circuit or executing code instructions.

Images