Conference control method and device, electronic equipment and storage medium

Abstract

The invention provides a conference control method and device, electronic equipment and a storage medium. The conference control method comprises the following steps: a first server receives a conference instruction which is sent by a terminal and carries a conference identifier of a target conference, and judges whether the target conference is a conference in a first autonomous domain to which the first server belongs according to an autonomous domain identifier contained in the conference identifier; wherein when the target conference creates an appointment, the autonomous domain identifier of the autonomous domain to which the target conference belongs is added to the conference identifier of the target conference; and if the target meeting is not the meeting in the first autonomous domain, determining a second autonomous domain corresponding to the target meeting, and sending the meeting instruction to a second server in the second autonomous domain, so that the second server controls the target meeting according to the meeting instruction. According to the embodiment of the invention, the cross-autonomous-domain conference is realized.

Description

Technical Field

[0001] The present invention relates to the field of network technology, and in particular to a conference control method, device, electronic equipment and storage medium. Background Art

[0002] With the rapid development of audio, video, and network technologies, video conferencing is becoming increasingly widespread and has become a core technical tool for maintaining efficient operations for all users. For easier management, a network can be divided into multiple autonomous domains (ADs). These are independent, and video conferences can be created within each domain.

[0003] Currently, video conference information is stored on the server of the autonomous domain to which the host terminal belongs. When the server of that autonomous domain receives a conference request from a terminal in that autonomous domain, it queries the server of that autonomous domain for the corresponding conference information to determine whether to allow the terminal to join the video conference. However, terminals in other autonomous domains cannot join the video conference, making cross-autonomous domain video conferencing impossible. Summary of the Invention

[0004] In view of the above problems, embodiments of the present invention are proposed to provide a conference control method, device, electronic device, and storage medium that overcome the above problems or at least partially solve the above problems.

[0005] In a first aspect, an embodiment of the present invention discloses a conference control method, applied to a first server, the method comprising:

[0006] A meeting instruction sent by a receiving terminal and carrying a conference identifier of a target conference is determined, based on an autonomous domain identifier included in the conference identifier, to determine whether the target conference is a conference within the first autonomous domain to which the first server belongs; wherein, when creating a reservation for the target conference, the autonomous domain identifier of the autonomous domain to which the target conference belongs is added to the conference identifier of the target conference;

[0007] If the target conference is not a conference within the first autonomous domain, a second autonomous domain corresponding to the target conference is determined, and the conference instruction is sent to a second server within the second autonomous domain, so that the second server controls the target conference according to the conference instruction.

[0008] Optionally, judging whether the target conference is a conference within the first autonomous domain to which the first server belongs based on the autonomous domain identifier included in the conference identifier includes:

[0009] Obtaining the autonomous domain identifier contained in the conference identifier and the autonomous domain identifier of the first autonomous domain, and comparing the autonomous domain identifier contained in the conference identifier with the autonomous domain identifier of the first autonomous domain;

[0010] If they are the same, it is determined that the target conference is a conference within the first autonomous domain; if they are different, it is determined that the target conference is not a conference within the first autonomous domain.

[0011] Optionally, determining the second autonomous domain corresponding to the target conference includes: obtaining the autonomous domain identifier contained in the conference identifier, and determining that the autonomous domain corresponding to the autonomous domain identifier contained in the conference identifier is the second autonomous domain corresponding to the target conference.

[0012] Optionally, the method further includes: receiving a control result of the target conference returned by the second server, and returning the control result to the terminal.

[0013] In a second aspect, an embodiment of the present invention discloses a conference control method, which is applied to a second server, and the method includes:

[0014] receiving a meeting instruction sent by a first server within the first autonomous domain, the instruction carrying a meeting identifier of a target meeting;

[0015] controlling the target meeting according to the meeting instruction;

[0016] In which, the meeting instruction is sent by the terminal to the first server, and the first server determines whether the target meeting is a meeting within the first autonomous domain to which the first server belongs based on the autonomous domain identifier contained in the meeting identifier. If the target meeting is not a meeting within the first autonomous domain, the second autonomous domain corresponding to the target meeting is determined and sent to the second server within the second autonomous domain; in which, when creating an appointment for the target meeting, the autonomous domain identifier of the autonomous domain to which the target meeting belongs is added to the meeting identifier of the target meeting.

[0017] Optionally, controlling the target conference according to the conference instruction includes:

[0018] Querying the meeting information corresponding to the target meeting;

[0019] If the meeting information exists and it is determined according to the meeting information that the target meeting is not in progress, starting the target meeting;

[0020] If the conference information exists and it is determined according to the conference information that the target conference is in progress, the terminal is pulled into the target conference;

[0021] If the meeting information does not exist, it is determined that the target meeting does not exist.

[0022] In a third aspect, an embodiment of the present invention discloses a conference control device, applied to a first server, comprising:

[0023] A judgment module, configured to receive a meeting instruction sent by a terminal and carrying a conference identifier of a target conference, and to judge, based on an autonomous domain identifier included in the conference identifier, whether the target conference is a conference within the first autonomous domain to which the first server belongs; wherein, when creating an appointment for the target conference, the autonomous domain identifier of the autonomous domain to which the target conference belongs is added to the conference identifier of the target conference;

[0024] The sending module is used to determine the second autonomous domain corresponding to the target meeting if the target meeting is not a meeting within the first autonomous domain, and send the meeting instruction to the second server within the second autonomous domain, so that the second server controls the target meeting according to the meeting instruction.

[0025] Optionally, the judgment module is specifically configured to:

[0026] Obtaining the autonomous domain identifier contained in the conference identifier and the autonomous domain identifier of the first autonomous domain, and comparing the autonomous domain identifier contained in the conference identifier with the autonomous domain identifier of the first autonomous domain;

[0027] If they are the same, it is determined that the target conference is a conference within the first autonomous domain; if they are different, it is determined that the target conference is not a conference within the first autonomous domain.

[0028] Optionally, the sending module is specifically configured to obtain the autonomous domain identifier included in the conference identifier, and determine that the autonomous domain corresponding to the autonomous domain identifier included in the conference identifier is the second autonomous domain corresponding to the target conference.

[0029] Optionally, the device further includes: a transceiver module, configured to receive a control result of the target conference returned by the second server, and return the control result to the terminal.

[0030] In a fourth aspect, an embodiment of the present invention discloses a conference control device, which is applied to a second server, and the device includes:

[0031] A receiving module, configured to receive a meeting instruction sent by a first server within a first autonomous domain, the instruction carrying a meeting identifier of a target meeting;

[0032] A control module, configured to control the target conference according to the conference instruction;

[0033] In which, the meeting instruction is sent by the terminal to the first server, and the first server determines whether the target meeting is a meeting within the first autonomous domain to which the first server belongs based on the autonomous domain identifier contained in the meeting identifier. If the target meeting is not a meeting within the first autonomous domain, the second autonomous domain corresponding to the target meeting is determined and sent to the second server within the second autonomous domain; in which, when creating an appointment for the target meeting, the autonomous domain identifier of the autonomous domain to which the target meeting belongs is added to the meeting identifier of the target meeting.

[0034] Optionally, the control module is specifically configured to:

[0035] Querying the meeting information corresponding to the target meeting;

[0036] If the meeting information exists and it is determined according to the meeting information that the target meeting is not in progress, starting the target meeting;

[0037] If the conference information exists and it is determined according to the conference information that the target conference is in progress, the terminal is pulled into the target conference;

[0038] If the meeting information does not exist, it is determined that the target meeting does not exist.

[0039] In a fifth aspect, an embodiment of the present invention discloses an electronic device, which includes a processor and a computer-readable storage medium, on which a computer program is stored; when the computer program is executed by the processor, the processor executes the conference control method as described in any one of the above items.

[0040] In a sixth aspect, an embodiment of the present invention discloses a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the processor executes the conference control method as described in any one of the above items.

[0041] In an embodiment of the present invention, when creating an appointment for a target conference, the autonomous domain identifier of the autonomous domain to which the target conference belongs is added to the conference identifier of the target conference. After receiving the meeting instruction sent by the terminal carrying the conference identifier of the target conference, the first server can determine whether the target conference is a meeting within the first autonomous domain to which it belongs based on the autonomous domain identifier contained in the conference identifier. After determining that the target conference is not a meeting within the first autonomous domain to which it belongs, it can determine the second autonomous domain corresponding to the target conference and send a meeting instruction to the second server in the second autonomous domain. The second server in the second autonomous domain controls the target conference according to the meeting instruction, thereby realizing a meeting across autonomous domains.

[0042] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are specifically listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments of the present invention. Obviously, the drawings described below are only some drawings of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0044] Figure 1 This is a flowchart of the steps of a conference control method according to an embodiment of the present invention;

[0045] Figure 2 is a flowchart of another conference control method according to an embodiment of the present invention;

[0046] Figure 3 This is a flowchart of the steps of another conference control method according to an embodiment of the present invention;

[0047] Figure 4 is a schematic diagram of a conference control process according to an embodiment of the present invention;

[0048] Figure 5 This is a structural block diagram of a conference control device according to an embodiment of the present invention;

[0049] Figure 6 is a structural block diagram of another conference control device according to an embodiment of the present invention;

[0050] Figure 7 is a structural block diagram of an electronic device according to an embodiment of the present invention;

[0051] Figure 8 It is a structural block diagram of a computer-readable storage medium according to an embodiment of the present invention. DETAILED DESCRIPTION

[0052] To make the objectives, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts shall fall within the scope of protection of the present invention.

[0053] In the embodiment of the present invention, for ease of management, a network can be divided into multiple autonomous domains, which are independent of each other. Each autonomous domain has its own conference-related devices, which may include remote controls, terminals, servers, and other devices.

[0054] The remote control is operated by the user to issue corresponding control commands to the terminal. For example, the user can enter the meeting ID (such as room number) and password and trigger the meeting button to issue a meeting command to the terminal.

[0055] The terminal is configured to respond to control commands issued by the remote control, generate corresponding instructions, and send the instructions to the server within its own autonomous domain. For example, in response to a conference call issued by the remote control, the terminal generates a conference call instruction containing the conference ID and password, and sends the conference call instruction to the server within the terminal's own autonomous domain.

[0056] The server, specifically a conference management and scheduling system, is responsible for conference control and management, enabling a series of conference control operations such as starting and stopping meetings, switching speakers, rotating screens, and dynamically adding and removing participants. The conference management and scheduling system consists of two parts: the conference management webpage (front-end page) and the conference management and scheduling (back-end program). The conference management webpage is used to display the status of current meetings, user management, and appointment management. The conference management and scheduling system is responsible for conference control and management, enabling a series of conference control operations such as starting and stopping meetings, switching speakers, rotating screens, and dynamically adding and removing participants.

[0057] The following describes in detail the conference control method in the embodiment of the present invention. The conference control method in the embodiment of the present invention can be applied in a visual network or the Internet.

[0058] In the embodiment of the present invention, the first autonomous domain and the second autonomous domain are used as examples for description. The server in the first autonomous domain is referred to as the first server, and the server in the second autonomous domain is referred to as the second server.

[0059] Reference Figure 1 , shows a step flow chart of a conference control method according to an embodiment of the present invention. Figure 1 The conference control method shown can be applied to the first server.

[0060] like Figure 1 As shown, the conference control method may include the following steps:

[0061] Step 101: A first server receives a conference start instruction sent by a terminal and carrying a conference identifier of a target conference, and determines, based on an autonomous domain identifier included in the conference identifier, whether the target conference is a conference within a first autonomous domain to which the first server belongs.

[0062] When creating an appointment for any meeting, the host terminal makes the appointment and enters the meeting identifier (such as room number) and password of the meeting through the remote control corresponding to the host terminal. The meeting information of the meeting is stored in the database of the server within the autonomous domain to which the host terminal belongs. The meeting information at this time includes information such as the meeting identifier (such as room number) and password, and may also include information indicating that the meeting has not yet started, etc., and then waits for the meeting to start.

[0063] When a terminal within the first autonomous domain requests a meeting for a scheduled target meeting, the user enters information such as the meeting ID (such as the room number) and password through the remote control corresponding to the terminal and triggers the meeting button, thereby issuing a meeting command to the terminal within the first autonomous domain. The terminal responds to the meeting command issued by the remote control, generates a meeting instruction carrying the above-mentioned meeting ID and password and other information, and sends the meeting instruction to the first server within the first autonomous domain.

[0064] In an optional implementation, in order to facilitate the determination of the autonomous domain to which the target meeting belongs, the autonomous domain identifier of the autonomous domain to which the host terminal belongs can be added to the conference identifier of the target meeting when creating an appointment for the target meeting. That is, the autonomous domain identifier of the autonomous domain to which the target meeting belongs. Based on the autonomous domain identifier, it can be uniquely determined which autonomous domain the target meeting belongs to.

[0065] Accordingly, when a terminal within the first autonomous domain requests a meeting for a scheduled target conference, the meeting identifier of the target conference input by the user through the remote control corresponding to the terminal also carries the autonomous domain identifier of the autonomous domain to which the target conference belongs. Therefore, the meeting instruction carries the meeting identifier of the target conference and, therefore, the autonomous domain identifier of the autonomous domain to which the target conference belongs.

[0066] The first server receives a meeting instruction sent by the terminal that carries the meeting identifier of the target meeting and can determine whether the target meeting is a meeting within the first autonomous domain to which the first server belongs based on the autonomous domain identifier included in the meeting identifier.

[0067] Step 102: If the first server determines that the target meeting is not a meeting within the first autonomous domain, it determines the second autonomous domain corresponding to the target meeting and sends the meeting instruction to the second server in the second autonomous domain, so that the second server controls the target meeting according to the meeting instruction.

[0068] If the first server determines that the target meeting is not a meeting within the first autonomous domain, the first server cannot query the meeting information of the target meeting (because the meeting information of the target meeting is stored in the server within the autonomous domain to which the target meeting belongs). Therefore, the first server can determine the second autonomous domain corresponding to the target meeting (the second autonomous domain is the autonomous domain to which the target meeting belongs).

[0069] A communication channel may be established between the first server and the second server, and the first server may send the meeting instruction to the second server in the second autonomous domain through the communication channel.

[0070] Reference Figure 2 , shows a step flow chart of another conference control method according to an embodiment of the present invention. Figure 2 The conference control method shown can be applied to the second server.

[0071] like Figure 2 As shown, the conference control method may include the following steps:

[0072] Step 201: The second server receives a conference instruction carrying a conference identifier of a target conference, which is sent by the first server in the first autonomous domain.

[0073] In which, the meeting instruction is sent by the terminal to the first server, and the first server determines whether the target meeting is a meeting within the first autonomous domain to which the first server belongs based on the autonomous domain identifier contained in the meeting identifier. If the target meeting is not a meeting within the first autonomous domain, the second autonomous domain corresponding to the target meeting is determined and sent to the second server within the second autonomous domain; in which, when creating an appointment for the target meeting, the autonomous domain identifier of the autonomous domain to which the target meeting belongs is added to the meeting identifier of the target meeting.

[0074] Step 202: The second server controls the target conference according to the conference instruction.

[0075] After receiving the conference instruction, the second server can control the target conference according to the conference instruction. The specific process of the second server controlling the target conference according to the conference instruction will be described in detail in subsequent embodiments.

[0076] In an embodiment of the present invention, when creating an appointment for a target conference, the autonomous domain identifier of the autonomous domain to which the target conference belongs is added to the conference identifier of the target conference. After receiving the meeting instruction sent by the terminal carrying the conference identifier of the target conference, the first server can determine whether the target conference is a meeting within the first autonomous domain to which it belongs based on the autonomous domain identifier contained in the conference identifier. After determining that the target conference is not a meeting within the first autonomous domain to which it belongs, it can determine the second autonomous domain corresponding to the target conference and send a meeting instruction to the second server in the second autonomous domain. The second server in the second autonomous domain controls the target conference according to the meeting instruction, thereby realizing a meeting across autonomous domains.

[0077] Reference Figure 3 , shows a step flow chart of another conference control method according to an embodiment of the present invention.

[0078] like Figure 3 As shown, the conference control method may include the following steps:

[0079] In step 301, a first server receives a meeting start instruction from a terminal containing a conference identifier of a target conference. Based on the autonomous domain identifier contained in the conference identifier, the first server determines whether the target conference is within the first autonomous domain to which the first server belongs. If so, the server proceeds to step 302; if not, the server proceeds to step 304.

[0080] Wherein, when creating a reservation for the target conference, the autonomous domain identifier of the autonomous domain to which the target conference belongs is added to the conference identifier of the target conference.

[0081] Exemplarily, the process of determining whether the target conference is a conference within the first autonomous domain to which the first server belongs, based on the autonomous domain identifier contained in the conference identifier, may include: obtaining the autonomous domain identifier contained in the conference identifier and the autonomous domain identifier of the first autonomous domain, and comparing the autonomous domain identifier contained in the conference identifier with the autonomous domain identifier of the first autonomous domain; if they are the same, determining that the target conference is a conference within the first autonomous domain; if they are different, determining that the target conference is not a conference within the first autonomous domain. In this method, the autonomous domain to which the conference belongs can be determined by adding the autonomous domain identifier, and the processing method is simple and efficient.

[0082] Step 302: If the first server determines that the target conference is a conference within the first autonomous domain, the first server controls the target conference according to the conference instruction.

[0083] Exemplarily, the process of the first server controlling the target meeting according to the meeting instruction may include: querying the meeting information corresponding to the target meeting; if the meeting information exists and it is determined according to the meeting information that the target meeting is in an unheld state, then starting the target meeting; if the meeting information exists and it is determined according to the meeting information that the target meeting is in a held state, then pulling the terminal into the target meeting; if the meeting information does not exist, determining that the target meeting does not exist.

[0084] If the target meeting is a meeting within the first autonomous domain, the meeting information of the target meeting is stored in the database of the first server within the first autonomous domain, so the first server can query the meeting information corresponding to the target meeting requested by the meeting instruction from its own database. Specifically, when storing the meeting information, the meeting identifier and the meeting information can be stored correspondingly. The first server can extract the meeting identifier of the target meeting from the meeting instruction and query the meeting information corresponding to the target meeting based on the meeting identifier of the target meeting.

[0085] If the meeting information corresponding to the target meeting exists and the target meeting has not yet been held, the meeting information corresponding to the target meeting includes non-meeting identification information. According to the non-meeting identification information, it can be determined that the target meeting is in a non-meeting state. Therefore, if the first server finds that the meeting information exists and determines that the target meeting is in a non-meeting state according to the meeting information, it starts the target meeting. Specifically, the first server executes the meeting process, pulls up the corresponding venue corresponding to the first server, and starts the target meeting. After starting the target meeting, the first server can also modify the non-meeting identification information in the meeting information corresponding to the target meeting to meeting identification information.

[0086] If meeting information corresponding to the target meeting exists and the target meeting has already started, the meeting information corresponding to the target meeting includes started identification information. Based on the started identification information, it can be determined that the target meeting is in a started state. Therefore, if the first server finds that the meeting information exists and determines that the target meeting is in a started state based on the meeting information, the terminal is pulled into the target meeting. Specifically, the first server executes a dynamic meeting joining process to pull the terminal into the target meeting.

[0087] If the first server finds that the meeting information corresponding to the target meeting does not exist, it determines that the target meeting does not exist.

[0088] Step 303: The first server obtains a control result of the target conference and returns the control result to the terminal.

[0089] If the first server executes the process of opening the target conference, the control result for the target conference is a meeting success message; if the first server executes the process of pulling the terminal into the target conference, the control result for the target conference is a meeting entry success message; if the first server determines that the target conference does not exist, the control result for the target conference is an error message. The first server returns the control result to the terminal.

[0090] Step 304: If the first server determines that the target meeting is not a meeting within the first autonomous domain, it determines the second autonomous domain corresponding to the target meeting and sends the meeting instruction to the second server in the second autonomous domain.

[0091] In an optional embodiment, as described above, the conference identifier includes the autonomous domain identifier of the autonomous domain to which the target conference belongs. Exemplarily, the process of determining the second autonomous domain corresponding to the target conference may include: obtaining the autonomous domain identifier contained in the conference identifier, and determining that the autonomous domain corresponding to the autonomous domain identifier contained in the conference identifier is the second autonomous domain corresponding to the target conference. In this way, the autonomous domain to which the conference belongs can be determined by adding the autonomous domain identifier, and the processing method is simple and efficient.

[0092] Step 305: The second server receives the conference start instruction sent by the first server and carries the conference identifier of the target conference, and controls the target conference according to the conference start instruction.

[0093] Exemplarily, the process of the second server controlling the target meeting according to the meeting instruction may include: querying the meeting information corresponding to the target meeting; if the meeting information exists and it is determined according to the meeting information that the target meeting is in an unheld state, then starting the target meeting; if the meeting information exists and it is determined according to the meeting information that the target meeting is in a held state, then pulling the terminal into the target meeting; if the meeting information does not exist, determining that the target meeting does not exist.

[0094] If the target meeting is a meeting within the second autonomous domain, the meeting information of the target meeting is stored in the database of the second server within the second autonomous domain, so the second server can query the meeting information corresponding to the target meeting requested by the meeting instruction from its own database. Specifically, when storing the meeting information, the meeting identifier and the meeting information can be stored correspondingly, and the second server can extract the meeting identifier of the target meeting from the meeting instruction and query the meeting information corresponding to the target meeting based on the meeting identifier of the target meeting.

[0095] If the meeting information corresponding to the target meeting exists and the target meeting has not yet been held, the meeting information corresponding to the target meeting includes non-meeting identification information. According to the non-meeting identification information, it can be determined that the target meeting is in a non-meeting state. Therefore, if the second server finds that the meeting information exists and determines that the target meeting is in a non-meeting state according to the meeting information, it starts the target meeting. Specifically, the second server executes the meeting process, pulls up the corresponding venue corresponding to the second server and the venue corresponding to the first server, and starts the target meeting. After starting the target meeting, the second server can also modify the non-meeting identification information in the meeting information corresponding to the target meeting to the meeting identification information.

[0096] If meeting information corresponding to the target meeting exists and the target meeting has already started, the meeting information corresponding to the target meeting includes started identification information. Based on the started identification information, it can be determined that the target meeting is in a started state. Therefore, if the second server finds that the meeting information exists and determines that the target meeting is in a started state based on the meeting information, it pulls the terminal into the target meeting. Specifically, the second server executes a dynamic meeting joining process to pull the terminal into the target meeting.

[0097] If the second server finds that the meeting information corresponding to the target meeting does not exist, it determines that the target meeting does not exist.

[0098] Step 306: The second server obtains the control result of the target conference and returns the control result to the first server.

[0099] If the second server executes the process of opening the target conference, the control result for the target conference is a message indicating a successful meeting. If the second server executes the process of adding the terminal to the target conference, the control result for the target conference is a message indicating a successful meeting. If the second server determines that the target conference does not exist, the control result for the target conference is an error message. The second server returns the control result to the first server.

[0100] Step 307: The first server receives the control result of the target conference returned by the second server, and returns the control result to the terminal.

[0101] Reference Figure 4 , which shows a schematic diagram of a conference control process according to an embodiment of the present invention. Figure 4 The main conference manager corresponds to the second server mentioned above, the branch conference manager corresponds to the first server mentioned above, terminal A is a terminal in the autonomous domain to which the main conference manager belongs, and terminal B is a terminal in the autonomous domain to which the branch conference manager belongs.

[0102] like Figure 4 As shown, if terminal A sends a conference instruction to the main conference manager, the conference instruction carries a room number (such as 100-360-0-123 in 4) and a password (such as 123456 in 4), and the room number contains the autonomous domain identifier of the autonomous domain to which the main conference manager belongs (such as 100-360-0 in 4); after the main conference manager receives the conference instruction, it compares the autonomous domain identifier carried in the conference instruction (such as 100-360-0 in 4) with the autonomous domain identifier of the autonomous domain to which the main conference manager belongs (such as 100-360-0 in 4). -0) is compared and it is determined that the target conference requested by the meeting instruction is a conference within the autonomous domain to which the main conference manager belongs. Therefore, the main conference manager traverses the conference information list stored in itself; if there is meeting information corresponding to the target conference and it is determined that the target conference is in an unheld state based on the meeting information, the meeting process is executed to start the target conference; if there is meeting information corresponding to the target conference and it is determined that the target conference is in a held state based on the meeting information, the dynamic meeting joining process is executed to pull the terminal into the target conference.

[0103] like Figure 4 As shown, if terminal B sends a meeting instruction to the branch manager, the meeting instruction carries a room number (such as 100-360-0-123 in 4) and a password (such as 123456 in 4), and the room number contains the autonomous domain identifier of the autonomous domain to which the main conference manager belongs (such as 100-360-0 in 4); after receiving the meeting instruction, the branch manager compares the autonomous domain identifier carried in the meeting instruction (such as 100-360-0 in 4) with the autonomous domain identifier of the autonomous domain to which the branch manager belongs (such as 100-360-2 in 4) to determine whether the meeting instruction is requested. The target conference requested is not a conference within the autonomous domain to which the branch manager belongs, so the branch manager sends a meeting instruction to the main conference manager; the main conference manager traverses the conference information list stored in itself; if the meeting information corresponding to the target conference exists and it is determined based on the meeting information that the target conference is in an unheld state, the meeting process is executed to start the target conference; if the meeting information corresponding to the target conference exists and it is determined based on the meeting information that the target conference is in a held state, the dynamic meeting joining process is executed to pull the terminal into the target conference; the main conference manager can return the control result to the branch manager.

[0104] Reference Figure 5 , shows a structural block diagram of a conference control device according to an embodiment of the present invention. Figure 5 The conference control device shown is applied to the first server.

[0105] like Figure 5 As shown, the conference control device may include the following modules:

[0106] The judgment module 501 is configured to receive a meeting instruction sent by a terminal and carrying a conference identifier of a target conference, and to judge whether the target conference is a conference within the first autonomous domain to which the first server belongs based on the autonomous domain identifier contained in the conference identifier; wherein, when creating a reservation for the target conference, the autonomous domain identifier of the autonomous domain to which the target conference belongs is added to the conference identifier of the target conference;

[0107] The sending module 502 is used to determine the second autonomous domain corresponding to the target meeting if the target meeting is not a meeting within the first autonomous domain, and send the meeting instruction to the second server within the second autonomous domain, so that the second server controls the target meeting according to the meeting instruction.

[0108] Optionally, the judgment module 501 is specifically configured to:

[0109] Obtaining the autonomous domain identifier contained in the conference identifier and the autonomous domain identifier of the first autonomous domain, and comparing the autonomous domain identifier contained in the conference identifier with the autonomous domain identifier of the first autonomous domain;

[0110] If they are the same, it is determined that the target conference is a conference within the first autonomous domain; if they are different, it is determined that the target conference is not a conference within the first autonomous domain.

[0111] Optionally, the sending module 502 is specifically configured to obtain the autonomous domain identifier included in the conference identifier, and determine that the autonomous domain corresponding to the autonomous domain identifier included in the conference identifier is the second autonomous domain corresponding to the target conference.

[0112] Optionally, the device further includes: a transceiver module, configured to receive a control result of the target conference returned by the second server, and return the control result to the terminal.

[0113] Reference Figure 6 , shows a structural block diagram of another conference control device according to an embodiment of the present invention. Figure 5 The conference control device shown is applied to the second server.

[0114] like Figure 6 As shown, the conference control device may include the following modules:

[0115] The receiving module 601 is configured to receive a conference start instruction sent by a first server in a first autonomous domain and carrying a conference identifier of a target conference;

[0116] The control module 602 is configured to control the target conference according to the conference instruction.

[0117] In which, the meeting instruction is sent by the terminal to the first server, and the first server determines whether the target meeting is a meeting within the first autonomous domain to which the first server belongs based on the autonomous domain identifier contained in the meeting identifier. If the target meeting is not a meeting within the first autonomous domain, the second autonomous domain corresponding to the target meeting is determined and sent to the second server within the second autonomous domain; in which, when creating an appointment for the target meeting, the autonomous domain identifier of the autonomous domain to which the target meeting belongs is added to the meeting identifier of the target meeting.

[0118] Optionally, the control module 602 is specifically configured to:

[0119] Querying the meeting information corresponding to the target meeting;

[0120] If the meeting information exists and it is determined according to the meeting information that the target meeting is not in progress, starting the target meeting;

[0121] If the conference information exists and it is determined according to the conference information that the target conference is in progress, the terminal is pulled into the target conference;

[0122] If the meeting information does not exist, it is determined that the target meeting does not exist.

[0123] In an embodiment of the present invention, when creating an appointment for a target conference, the autonomous domain identifier of the autonomous domain to which the target conference belongs is added to the conference identifier of the target conference. After receiving the meeting instruction sent by the terminal carrying the conference identifier of the target conference, the first server can determine whether the target conference is a meeting within the first autonomous domain to which it belongs based on the autonomous domain identifier contained in the conference identifier. After determining that the target conference is not a meeting within the first autonomous domain to which it belongs, it can determine the second autonomous domain corresponding to the target conference and send a meeting instruction to the second server in the second autonomous domain. The second server in the second autonomous domain controls the target conference according to the meeting instruction, thereby realizing a meeting across autonomous domains.

[0124] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0125] In an embodiment of the present invention, an electronic device is further provided. The electronic device may include a processor and a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program; when the computer program is executed by the processor, the processor executes the conference control method of any of the above embodiments.

[0126] Reference Figure 7 , shows a structural block diagram of an electronic device according to an embodiment of the present invention. Figure 7 As shown, the electronic device 11 includes a processor 111 and a computer-readable storage medium 112 , on which a computer program 1121 is stored.

[0127] The processor 111 is used to execute the computer program 1121 stored on the computer-readable storage medium 112. When executing the computer program 1121, the processor 111 implements the conference control method of any of the above embodiments and can achieve the same technical effect. To avoid repetition, it will not be described here.

[0128] The processor 111 mentioned above may include but is not limited to: a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0129] The computer-readable storage medium 112 mentioned above may include, but is not limited to, read-only memory (ROM), random access memory (RAM), compact disc read-only memory (CD-ROM), electronic erasable programmable read-only memory (EEPROM), hard disk, floppy disk, flash memory, and the like.

[0130] In an embodiment of the present invention, a computer-readable storage medium is also provided, on which a computer program is stored. The computer program can be executed by a processor of an electronic device. When the computer program is executed by the processor, the processor executes the conference control method described in any of the above embodiments.

[0131] Reference Figure 8 , shows a structural block diagram of a computer-readable storage medium according to an embodiment of the present invention. Figure 8As shown, a computer program 211 is stored on the computer-readable storage medium 21. When the computer program 211 is executed by the processor, the processor executes the conference control method described in any of the above embodiments and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0132] It should be noted that all actions of acquiring signals, information or data in the present invention are performed in compliance with the corresponding local data protection laws and policies and with authorization from the corresponding device owner.

[0133] The various embodiments in this specification are interrelated and are described in a progressive manner. Each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments can be referenced to each other.

[0134] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, apparatus, or computer program products. Thus, embodiments of the present invention may take the form of a fully hardware embodiment, a fully software embodiment, or an embodiment combining software and hardware. Furthermore, embodiments of the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0135] The embodiments of the present invention are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the process in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0136] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0137] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The steps for the function specified in one or more boxes.

[0138] Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they are aware of the basic creative concepts. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present invention.

[0139] Finally, it should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or terminal device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or terminal device that includes the element.

[0140] The above is a detailed introduction to the conference control method, device, electronic device and storage medium provided by the present invention. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core ideas. At the same time, for those skilled in the art, according to the ideas of the present invention, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as limiting the present invention.

Claims

1. A conference control method, characterized in that: Applied to the first server, the method includes: A meeting instruction sent by a receiving terminal and carrying a conference identifier of a target conference is determined, based on an autonomous domain identifier included in the conference identifier, to determine whether the target conference is a conference within the first autonomous domain to which the first server belongs; wherein, when creating a reservation for the target conference, the autonomous domain identifier of the autonomous domain to which the target conference belongs is added to the conference identifier of the target conference; If the target conference is not a conference within the first autonomous domain, a second autonomous domain corresponding to the target conference is determined, and the conference instruction is sent to a second server within the second autonomous domain, so that the second server controls the target conference according to the conference instruction.

2. The method according to claim 1, characterized in that The determining, based on the autonomous domain identifier included in the conference identifier, whether the target conference is a conference within the first autonomous domain to which the first server belongs includes: Obtaining the autonomous domain identifier contained in the conference identifier and the autonomous domain identifier of the first autonomous domain, and comparing the autonomous domain identifier contained in the conference identifier with the autonomous domain identifier of the first autonomous domain; If they are the same, it is determined that the target conference is a conference within the first autonomous domain; if they are different, it is determined that the target conference is not a conference within the first autonomous domain.

3. The method according to claim 1, characterized in that The determining the second autonomous domain corresponding to the target conference includes: The autonomous domain identifier included in the conference identifier is obtained, and it is determined that the autonomous domain corresponding to the autonomous domain identifier included in the conference identifier is the second autonomous domain corresponding to the target conference.

4. The method according to claim 1, wherein The method further comprises: Receive the control result of the target conference returned by the second server, and return the control result to the terminal.

5. A conference control method, characterized in that: Applied to the second server, the method includes: receiving a meeting instruction sent by a first server within the first autonomous domain, the instruction carrying a meeting identifier of a target meeting; controlling the target meeting according to the meeting instruction; In which, the meeting instruction is sent by the terminal to the first server, and the first server determines whether the target meeting is a meeting within the first autonomous domain to which the first server belongs based on the autonomous domain identifier contained in the meeting identifier. If the target meeting is not a meeting within the first autonomous domain, the second autonomous domain corresponding to the target meeting is determined and sent to the second server within the second autonomous domain; in which, when creating an appointment for the target meeting, the autonomous domain identifier of the autonomous domain to which the target meeting belongs is added to the meeting identifier of the target meeting.

6. The method according to claim 5, characterized in that The controlling the target conference according to the conference instruction includes: Querying the meeting information corresponding to the target meeting; If the meeting information exists and it is determined according to the meeting information that the target meeting is not in progress, starting the target meeting; If the conference information exists and it is determined according to the conference information that the target conference is in progress, the terminal is pulled into the target conference; If the meeting information does not exist, it is determined that the target meeting does not exist.

7. A conference control device, characterized in that: Applied to a first server, the device includes: A judgment module, configured to receive a meeting instruction sent by a terminal and carrying a conference identifier of a target conference, and to judge, based on an autonomous domain identifier included in the conference identifier, whether the target conference is a conference within the first autonomous domain to which the first server belongs; wherein, when creating an appointment for the target conference, the autonomous domain identifier of the autonomous domain to which the target conference belongs is added to the conference identifier of the target conference; The sending module is used to determine the second autonomous domain corresponding to the target meeting if the target meeting is not a meeting within the first autonomous domain, and send the meeting instruction to the second server within the second autonomous domain, so that the second server controls the target meeting according to the meeting instruction.

8. A conference control device, characterized in that: Applied to the second server, the device includes: A receiving module, configured to receive a meeting instruction sent by a first server within a first autonomous domain, the instruction carrying a meeting identifier of a target meeting; A control module, configured to control the target conference according to the conference instruction; In which, the meeting instruction is sent by the terminal to the first server, and the first server determines whether the target meeting is a meeting within the first autonomous domain to which the first server belongs based on the autonomous domain identifier contained in the meeting identifier. If the target meeting is not a meeting within the first autonomous domain, the second autonomous domain corresponding to the target meeting is determined and sent to the second server within the second autonomous domain; in which, when creating an appointment for the target meeting, the autonomous domain identifier of the autonomous domain to which the target meeting belongs is added to the meeting identifier of the target meeting.

9. An electronic device, characterized in that: The electronic device includes a processor and a computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium; when the computer program is executed by the processor, the processor executes the conference control method according to any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processor executes the conference control method according to any one of claims 1 to 6.

Images