Conference reservation method, apparatus, device, storage medium, and program product

Abstract

Embodiments of the present application provide a conference reservation method, device, equipment, storage medium and program product, and relate to the field of digital employees. The method comprises: obtaining a conference reservation request; determining a target conference management subsystem matching a conference level from a first conference management subsystem and a second conference management subsystem; in the case that the target conference management subsystem is the first conference management subsystem, the first conference management subsystem determines at least one first participating terminal and at least one second participating terminal in a plurality of participating terminals; the first conference management subsystem creates a target conference of the first conference level; and the first conference management subsystem performs conference group call of the target conference for the at least one first participating terminal based on a first MCU cluster, and performs conference group call of the target conference for the at least one second participating terminal based on a second MCU cluster. The method of the present application solves the problem that the prior art cannot realize conference hierarchical management, thereby failing to guarantee the conference resource demand of important users.

Description

Technical Field

[0001] This application relates to the field of digital employees, and more particularly to a meeting scheduling method, apparatus, device, storage medium, and program product. Background Technology

[0002] Video conferencing is a meeting format that can overcome geographical limitations and enable face-to-face communication among multiple parties. For large enterprises with multiple office locations, they typically establish one or more complete video conferencing systems within the enterprise to meet the needs of internal and external communication across regions. The video conferencing architecture of large enterprises usually consists of a centrally deployed meeting management system, a distributed MCU, and video terminals, relying on IP network interconnection for meeting scheduling.

[0003] Existing video conferencing scheduling methods do not differentiate between participants and / or meeting levels, resulting in all participants or meetings of different levels sharing the full video conferencing resource capacity equally. This leads to a situation where, during peak business periods, the resource needs of important users or important meetings cannot be guaranteed. Deploying multiple video conferencing systems to address this issue presents the problem of not being able to uniformly schedule and manage meetings across these systems. Summary of the Invention

[0004] This application provides a meeting reservation method, apparatus, device, storage medium, and product to solve the problem that existing meeting systems cannot achieve meeting tiering, resulting in the inability to guarantee the meeting needs of important users.

[0005] Firstly, this application provides a meeting reservation method applied to a meeting reservation system, the meeting reservation system comprising: a first meeting management subsystem and a second meeting management subsystem, including:

[0006] Obtain a meeting reservation request, which includes: meeting level and multiple participating terminals;

[0007] A target meeting management subsystem matching the meeting level is determined from the first meeting management subsystem and the second meeting management subsystem, wherein the meeting level corresponding to the first meeting management subsystem is higher than the meeting level corresponding to the second meeting management subsystem;

[0008] When the target meeting management subsystem is the first meeting management subsystem, the first meeting management subsystem determines at least one first meeting terminal and at least one second meeting terminal among a plurality of meeting terminals. The terminal level of the first meeting terminal corresponds to the first meeting management subsystem, and the terminal level of the second meeting terminal corresponds to the second meeting management subsystem.

[0009] The first conference management subsystem creates a target conference at a first conference level; and makes a conference group call for the target conference to at least one first participating terminal based on a first MCU cluster, and makes a conference group call for the target conference to at least one second participating terminal based on a second MCU cluster, wherein the first MCU cluster is the MCU cluster corresponding to the first conference management subsystem, and the second MCU cluster is the MCU cluster corresponding to the second conference management subsystem.

[0010] Secondly, this application provides a meeting reservation system, including:

[0011] The acquisition module is used to acquire meeting reservation requests, which include: meeting level and multiple participating terminals;

[0012] The determining module is used to determine a target meeting management subsystem that matches the meeting level from the first meeting management subsystem and the second meeting management subsystem, wherein the meeting level corresponding to the first meeting management subsystem is higher than the meeting level corresponding to the second meeting management subsystem;

[0013] The first meeting management subsystem is used to determine at least one first meeting terminal and at least one second meeting terminal among a plurality of meeting terminals when the target meeting management subsystem is the first meeting management subsystem. The terminal level of the first meeting terminal corresponds to the first meeting management subsystem, and the terminal level of the second meeting terminal corresponds to the second meeting management subsystem.

[0014] The first conference management subsystem is also used to create a target conference of a first conference level; and to make a conference group call for the target conference to at least one first participating terminal based on a first MCU cluster, and to make a conference group call for the target conference to at least one second participating terminal based on a second MCU cluster, wherein the first MCU cluster is the MCU cluster corresponding to the first conference management subsystem, and the second MCU cluster is the MCU cluster corresponding to the second conference management subsystem.

[0015] Optionally, the first meeting management subsystem is further configured to determine the address information and level information of each participating terminal from the meeting reservation system based on the multiple participating terminals;

[0016] The first meeting management subsystem is further configured to determine at least one first participating terminal and at least one second participating terminal among the multiple participating terminals based on the level information of the multiple participating terminals, wherein the first participating terminal corresponds to the first level and the second participating terminal corresponds to the second level.

[0017] Optionally, the first meeting management subsystem is further configured to determine the corresponding first resource reserve and the second resource reserve of the second meeting management system, and to determine the first resource quantity and the second resource quantity based on the meeting information, at least one first participating terminal and at least one second participating terminal. The first resource quantity is used to indicate the resource quantity required for at least one first terminal to access the meeting, and the second resource quantity is used to indicate the resource quantity required for at least one second terminal to access the meeting.

[0018] The first meeting management subsystem is also used to create a target meeting of the first meeting level when the first resource surplus and the second resource surplus respectively meet the first resource quantity and the second resource quantity.

[0019] Optionally, the first meeting management subsystem is further configured to determine whether the total amount of resources of the first resource reserve and the second resource reserve meets the first resource quantity when the first resource reserve does not meet the first resource quantity.

[0020] If the conditions are met, the first resource reserve and the second resource reserve are used to create a first sub-meeting corresponding to at least one of the first participating terminals;

[0021] If the first sub-meeting is successfully created, determine the current second resource reserve. If the current second resource reserve meets the second resource quantity, create a second sub-meeting corresponding to at least one second participating terminal.

[0022] Optionally, the first conference management subsystem is further configured to determine the cascading information between the first MCU cluster and the second MCU cluster, and send the cascading information to the first MCU cluster and the second MCU cluster, so that the first MCU cluster and the second MCU cluster establish conference communication based on the cascading information.

[0023] Optionally, the system may also include: a second meeting management subsystem;

[0024] The second meeting management subsystem is used to create a target meeting of a second meeting level when the target meeting management subsystem is the second meeting management subsystem, and to make a meeting group call for the target meeting to multiple participating terminals based on the second MCU cluster. The second meeting level is lower than the first meeting level.

[0025] Optionally, the second meeting management subsystem is also used to manage meeting reservation requests of the first meeting management subsystem in the event that the first meeting management subsystem is abnormal or unusable.

[0026] Thirdly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0027] The memory stores computer-executed instructions;

[0028] The processor executes computer execution instructions stored in the memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0029] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0030] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect and / or the second aspect and / or the second aspect.

[0031] The meeting reservation method provided in this application is applied to a meeting reservation system. It involves obtaining a meeting reservation request, which includes a meeting level and multiple participating terminals; determining a target meeting management subsystem matching the meeting level from a first meeting management subsystem and a second meeting management subsystem, wherein the meeting level corresponding to the first meeting management subsystem is higher than that corresponding to the second meeting management subsystem; when the target meeting management subsystem is the first meeting management subsystem, the first meeting management subsystem determines at least one first participating terminal and at least one second participating terminal from the multiple participating terminals, wherein the terminal level of the first participating terminal corresponds to the first meeting management subsystem, and the terminal level of the second participating terminal corresponds to the second meeting management subsystem; the first meeting management subsystem creates a target meeting at the first meeting level; and performs a meeting group call for the target meeting to at least one first participating terminal based on a first MCU cluster, and performs a meeting group call for the target meeting to at least one second participating terminal based on a second MCU cluster, wherein the first MCU cluster is the MCU cluster corresponding to the first meeting management subsystem, and the second MCU cluster is the MCU cluster corresponding to the second meeting management subsystem. The meeting reservation system integrates the first and second meeting management subsystems. Based on different meeting levels and participant terminal levels, corresponding target meeting management subsystems are used to manage meetings and participant terminals. This unified meeting reservation system manages meetings at different levels and allows for the reservation of key video conferencing resources through different subsystems. Attached Figure Description

[0032] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0033] Figure 1 Flowchart of the meeting reservation method provided in the embodiments of this application Figure 1 ;

[0034] Figure 2 Flowchart of the meeting reservation method provided in the embodiments of this application Figure 2 ;

[0035] Figure 3 A schematic diagram of the structure of the meeting reservation system provided in the embodiments of this application;

[0036] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0037] The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation

[0038] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0039] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of the relevant data all comply with the relevant laws, regulations, and standards of the relevant countries and regions, have taken necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation access points for users to choose to authorize or refuse.

[0040] Furthermore, the technical solution involved in this application, which involves big data analysis of user information (including but not limited to personal biometrics, identity data, consumption data, asset data, electronic terminal operation data, etc.) and the use of artificial intelligence technology for automated decision-making, and makes decisions that have a significant impact on personal rights based on the results of automated decision-making, provides users with corresponding operation entry points for users to choose to agree to or reject the results of automated decision-making; if the user chooses to reject, the process will proceed to the expert decision-making process.

[0041] It should be noted that the meeting reservation method, apparatus, equipment, storage medium and product provided in this application can be used in the field of digital employees, or in any other field. The application field of the meeting reservation method, apparatus, equipment, storage medium and product in this application is not limited.

[0042] The terms "first," "second," "third," "fourth," etc. (if present) in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented, for example, in orders other than those illustrated or described herein.

[0043] In this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0044] First, let me explain the terms used in this application:

[0045] Multi-Point Control Unit (MCU): The MCU is an important component of a video conferencing system. When a video conference is held at more than two locations, the MCU must aggregate, distribute, and switch the signals from multiple locations and control the conference. The MCU synchronously separates the information streams from each video conferencing terminal, extracts various information such as audio, video, data, and signaling, and sends the common information from each terminal to the corresponding information processing module to complete the processing.

[0046] Video conferencing terminal: Deployed on the user side of a video conferencing system, providing various interfaces to connect with audio and video input and output devices, enabling the sending and receiving of audio and video information.

[0047] Video conferencing is a form of meeting that can break geographical limitations and enable multiple parties to communicate face-to-face. For large enterprises with multiple office locations, they usually establish one or more complete video conferencing systems within the enterprise to meet the internal and external communication needs across regions.

[0048] Existing large-scale enterprise video conferencing architectures typically consist of a centrally deployed meeting management system, distributed MCUs, and video terminals, relying on IP network interconnection for meeting scheduling. The aforementioned centrally deployed meeting management system does not differentiate between participants and / or meeting levels, resulting in all participants or meetings of different levels sharing the entire video conferencing resource capacity equally. This leads to situations where, during peak business hours, the meeting resource needs of important users or important meetings cannot be guaranteed.

[0049] If the above problems are addressed by deploying multiple video conferencing systems, then the inability to uniformly schedule and manage meetings across these systems will arise.

[0050] The meeting reservation system provided in this application aims to solve the aforementioned technical problems of existing technologies. By integrating a first meeting management subsystem and a second meeting management subsystem, the system manages meetings and participating terminals according to different meeting levels and participant terminal levels using corresponding target meeting management subsystems. Simultaneously, when the resources of the first meeting management subsystem are insufficient, resources from the second meeting management subsystem are utilized. This achieves unified meeting reservation system management for meetings of different levels, and the reservation of key video conference resources through different subsystems improves the problem of resource contention during peak business periods, preventing important meetings from being held smoothly.

[0051] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0052] Figure 1 Flowchart of the meeting reservation method provided in the embodiments of this application Figure 1 .like Figure 1 As shown in the figure, the meeting reservation method illustrated in this embodiment is applied to a meeting reservation system and includes:

[0053] S101. Obtain a meeting reservation request.

[0054] The meeting reservation request includes: meeting level and multiple participating terminals.

[0055] Understandably, the meeting reservation system can provide a visual interface for users to operate. Users can input meeting reservation requests through the visual interface. Input information may include, for example, the meeting name, meeting time, meeting duration, meeting level, and participant video terminal identifiers. Specific meeting settings can be determined based on actual use. This solution will not elaborate on the input settings.

[0056] Specifically, the meeting level can be determined based on factors such as the attendees' positions, the importance of the meeting, and the size of the meeting.

[0057] S102. Determine the target meeting management subsystem that matches the meeting level from the first meeting management subsystem and the second meeting management subsystem; if the target meeting management subsystem is the first meeting management subsystem, execute steps S103-S105; if the target meeting management subsystem is the second meeting management subsystem, execute steps S106-S107.

[0058] The meeting level corresponding to the first meeting management subsystem is higher than that corresponding to the second meeting management subsystem. The target meeting system can be determined based on the obtained meeting level.

[0059] Understandably, the first meeting management subsystem can be a higher-level management system, with corresponding priority meeting resources set for high-level meetings; correspondingly, the second meeting management subsystem can be a low-capacity management system, used to handle smaller-scale, lower-level meetings.

[0060] S103, The first meeting management subsystem identifies at least one first participating terminal and at least one second participating terminal among multiple participating terminals.

[0061] The terminal level of the first participating terminal corresponds to the first meeting management subsystem, and the terminal level of the second participating terminal corresponds to the second meeting management subsystem. In other words, the terminal level of the first participating terminal is higher than that of the second participating terminal.

[0062] Understandably, if the target meeting management subsystem is identified as the first meeting management subsystem, the first management subsystem can receive meeting reservation requests from the meeting reservation system and analyze them to identify multiple participating terminals. Since the meeting level corresponding to the first meeting management subsystem is higher, the participating terminals in the target meeting can include both the first participating terminal and the second participating terminal.

[0063] Specifically, based on multiple participating terminals, the first meeting management subsystem can determine the terminal level according to the pre-stored information of the terminals, thereby identifying at least one first participating terminal and at least one second participating terminal among the multiple participating terminals, and allocating meeting resources of different clusters according to different types of terminals, so as to realize the hierarchical classification and retention of important resources in the meeting.

[0064] S104, First Meeting Management Subsystem, creates target meetings at the first meeting level.

[0065] The first meeting management subsystem, after determining the corresponding participating terminal, allocates resources for the meeting based on the meeting reservation request, creates a target meeting of the first meeting level, and completes the meeting reservation process for the target meeting of the first meeting level.

[0066] S105. The first conference management subsystem makes a conference group call to at least one first participating terminal based on the first MCU cluster, and makes a conference group call to at least one second participating terminal based on the second MCU cluster.

[0067] The first MCU cluster corresponds to the first conference management subsystem, and the second MCU cluster corresponds to the second conference management subsystem. Group calling refers to the ability of the conference system to simultaneously initiate calls to multiple participating terminals, allowing them to join the same conference.

[0068] Understandably, the first meeting management subsystem can send meeting group call requests to each participating terminal through the first MCU cluster based on the acquired information. The meeting request can carry relevant attribute information of the target meeting, such as the meeting name, meeting ID, and start time, so that users of the first participating terminals know which meeting they want to join and its basic information.

[0069] Optionally, after receiving the group call request, the first participating terminal can parse and verify the request. If the verification is successful, it can configure its own audio and video codecs, network interfaces and other related modules according to the conference parameters indicated in the request, and then send a confirmation response message to the first MCU cluster to complete the operation of joining the conference.

[0070] Correspondingly, the process of making a target conference call for at least one second participating terminal based on the second MCU cluster is similar to that of making a target conference call for at least one first participating terminal based on the first MCU cluster, and will not be described again here.

[0071] In one possible implementation, the first conference management subsystem determines the cascading information between the first MCU cluster and the second MCU cluster, and sends the cascading information to the first MCU cluster and the second MCU cluster, so that the first MCU cluster and the second MCU cluster establish conference communication based on the cascading information.

[0072] When there are multiple MCU clusters, such as the first MCU cluster and the second MCU cluster, in order to enable the two clusters to work together and allow the participating terminals managed by different clusters to participate in the same conference for communication, the first conference management subsystem needs to issue cascading information.

[0073] Understandably, the corresponding cascading information can be determined through the network configuration, communication protocols, and resource settings of each cluster. This cascading information may include, for example, the selected interconnection IP address and corresponding subnet mask, the determined communication protocol, relevant resource allocation and load balancing strategies, port allocation information, etc. The first conference management subsystem can transmit the IP address and network port of the second MCU cluster to the first MCU cluster, and the first MCU cluster can initiate a media channel interconnection request to realize the cascading of the first MCU cluster and the second MCU cluster.

[0074] Specifically, the first conference management subsystem can send cascading information to the first and second MCU clusters through a specific network communication mechanism, such as Simple Network Management Protocol (SNMP) or a custom configuration interface based on HTTP. After receiving the cascading information, the first and second MCU clusters can parse and verify it to ensure its integrity and legitimacy. Then, according to the requirements in the cascading information, they configure their own network interfaces, including setting corresponding IP addresses, subnet masks, ports, and other parameters to match the corresponding interfaces of the respective MCU clusters, thereby establishing conference communication between the first and second MCU clusters.

[0075] S106. If the target meeting management subsystem is the second meeting management subsystem, the second meeting management subsystem creates a target meeting at the second meeting level.

[0076] The second meeting level refers to a lower-level meeting, which is created through the corresponding second meeting management subsystem based on the meeting reservation request.

[0077] Understandably, the target meetings of the second-level meeting can be considered as meetings with simpler tasks and lower resource requirements, and the corresponding terminal levels of the participating terminals are also lower.

[0078] S107. The second conference management subsystem makes group calls to multiple participating terminals for the target conference based on the second MCU cluster. The second conference level is lower than the first conference level.

[0079] In this case, multiple participating terminals were secondary participating terminals. Because the secondary meeting management subsystem has a lower level, it can only process target meetings at the secondary meeting level, and correspondingly, it can only make group calls to secondary participating terminals, and cannot make group calls to primary participating terminals across terminal and meeting levels.

[0080] Understandably, the content of the group call for the target conference by the second MCU cluster to multiple participating terminals is similar to the steps in step S105 above, and will not be repeated here.

[0081] The meeting reservation method provided in this embodiment obtains a meeting reservation request; determines a target meeting management subsystem matching the meeting level from the first meeting management subsystem and the second meeting management subsystem; when the target meeting management subsystem is the first meeting management subsystem, the first meeting management subsystem determines at least one first participating terminal and at least one second participating terminal from multiple participating terminals; the first meeting management subsystem creates a target meeting at the first meeting level; and performs a meeting group call for the target meeting to at least one first participating terminal based on the first MCU cluster, and performs a meeting group call for the target meeting to at least one second participating terminal based on the second MCU cluster. The meeting reservation system sends meeting reservation requests to the corresponding target meeting management subsystems according to different meeting levels and participating terminal levels to manage the meeting and participating terminals, realizing unified meeting reservation system management of different levels of meetings, and reserving key video conferencing resources through different subsystems.

[0082] Figure 2 Flowchart of the meeting reservation method provided in the embodiments of this application Figure 2 .like Figure 2 As shown, this embodiment is... Figure 1 Based on the embodiments, the process of the first meeting management subsystem determining the terminal level and creating a target meeting of the first meeting level is described in detail. The meeting reservation method shown in this embodiment includes:

[0083] S201. Based on multiple participating terminals, determine the address information and level information of each participating terminal from the meeting reservation system.

[0084] The meeting reservation system can pre-enter the address information of each terminal and set the corresponding level information. When the first meeting management subsystem receives the meeting reservation request, it analyzes and determines multiple participating terminals, and can determine the corresponding terminal identifier or other label information that can analyze terminal information. Based on this, the meeting reservation system determines the corresponding terminal address and level information.

[0085] Understandably, the terminal address here refers to the terminal's IP address. For example, the first meeting management subsystem can query the relevant records storing the network address field of the participating terminals from the meeting reservation system to obtain a list of IP addresses corresponding to each participating terminal.

[0086] S202. Based on the level information of multiple participating terminals, determine at least one first participating terminal and at least one second participating terminal among the multiple participating terminals.

[0087] The terminal classifications differ for different levels.

[0088] Understandably, terminal level information can be stored in the system's configuration table or related rule table. The level information for each participating terminal can be determined by querying the table or field associated with its level. Specifically, for example, a meeting reservation system might have a "Participating Terminal-Level Association Table" to record the correspondence between each participating terminal's identifier (such as terminal number) and the corresponding personnel level information. By executing the appropriate query, the level information of a specific participating terminal can be obtained, thus clarifying the hierarchical status of the participants represented by each terminal in the meeting. This facilitates subsequent permission configuration and resource allocation.

[0089] S203. Determine the first resource reserve of the first meeting management subsystem and the second resource reserve of the second meeting management subsystem.

[0090] Among them, resource reserve is used to represent the amount of idle resources that are not currently being used in the system or cluster. In the conference management system, resource reserve can represent the remaining resources that the conference management subsystem can use to support the conference. Resources may include hardware resources (such as the processing power of the MCU, the number of ports, etc.) and software resources (such as the number of software licenses, data storage capacity, etc.).

[0091] Understandably, both the first and second meeting management subsystems have their own resource reserves. Regarding the methods for obtaining resource reserves, for example, monitoring tools can be used to collect the system resource usage in real time and calculate the amount of resources currently used based on the monitoring data. Subsequently, based on the system design and expected load, the total amount of system resources is determined. The resource reserves are obtained by subtracting the amount of resources currently used from the total amount of resources.

[0092] Optionally, since resource reserves are not fixed and will constantly change as meetings progress, new meetings are created, and old meetings end, dynamic monitoring of resource reserves is possible to adjust meeting schedules promptly. For example, this can be done by setting up scheduled tasks or utilizing the system's event-driven mechanism to recalculate resource reserves at regular intervals.

[0093] S204. Based on the meeting information, at least one first participating terminal and at least one second participating terminal, determine the first resource quantity and the second resource quantity.

[0094] Different levels of terminals have different requirements for meeting resources.

[0095] Understandably, the first participating terminal corresponds to relatively high-level participants who typically have higher requirements for meeting quality and functionality. For example, the first participating terminal often needs to support high-definition or even ultra-high-definition video quality (such as 4K resolution video) to ensure clear display of presentation content and observation of details such as other participants' expressions. Conversely, the second participating terminal corresponds to relatively low-level participants whose functional requirements are relatively basic. Most only need to meet basic standard-definition video calls and simple text communication functions, with relatively lower requirements for video quality and the richness of interactive functions. Therefore, based on the different meeting needs of the two types of terminals, corresponding resource requirements are determined.

[0096] S205. If the first resource reserve and the second resource reserve satisfy the first resource quantity and the second resource quantity respectively, create a target meeting of the first meeting level.

[0097] The relationship between resource quantity and resource reserve can be evaluated from both hardware and software perspectives. On the hardware side, it can be determined by analyzing MCU processing power and port availability; on the software side, it can be determined through data storage capacity or the number of software licenses.

[0098] Specifically, taking MCU processing capacity as an example, if the MCU processing capacity in the first resource margin is sufficient to cover the needs of the first resource quantity, for example, if the MCU processing capacity margin can still handle 60 high-definition video streams, while the first resource quantity only needs to handle 30 high-definition video streams, it means that the conditions are met in this respect.

[0099] Understandably, when both the first and second resource reserves meet the first and second resource requirements, it means that the resource foundation for creating a target meeting of the first meeting level is available, and the meeting can be created. A meeting reservation request is then made, setting the corresponding parameters and information. The first and second meeting management subsystems then reserve and allocate underlying hardware and network resources according to their respective first and second resource requirements. For example, based on the determined resource availability, a corresponding number of MCU ports and sufficient network bandwidth are allocated to the first participating terminal, while corresponding resource arrangements are made for the second participating terminal to ensure a stable supply of various resources during the meeting.

[0100] S206. If the first resource reserve does not meet the first resource quantity, determine whether the total amount of resources in the first resource reserve and the second resource reserve meets the first resource quantity; if yes, proceed to steps S207-S208; if no, proceed to step S209.

[0101] First, determine the remaining resource capacity of the first and second resource reserves. Then, sum up the corresponding resources in the first and second resource reserves to obtain the total resource capacity. For example, the MCU associated with the first conference management subsystem currently has 30 video streams that it can process, and the MCU associated with the second conference management subsystem currently has 20 video streams that it can process. Add the remaining processing capacity of the MCUs of the first and second conference management subsystems together, i.e., 30 streams (first resource reserve) plus 20 streams (second resource reserve), equals a total processing capacity of 50 video streams. Then, compare the total resource capacity obtained by summing up with the first resource capacity determined for the first participating terminal to determine whether it meets the requirements.

[0102] Understandably, in a multi-meeting management subsystem environment, such as when the first and second meeting management subsystems operate simultaneously, resource reserves can be planned and managed in a coordinated manner. For example, resource reserves can be allocated reasonably based on factors such as meeting priority and scale.

[0103] Specifically, if an important high-level meeting requires more resources, and the first meeting management subsystem has sufficient resources while the second meeting management subsystem has limited resources, then it is advisable to allocate some resources from the first meeting management subsystem to the second meeting management subsystem to meet the needs of the high-level meeting.

[0104] S207. Use the first and second resource reserves to create a first sub-meeting corresponding to at least one first participating terminal.

[0105] If the total amount of resources in the first resource reserve and the second resource reserve meets the first resource amount, then the first resource reserve and the second resource reserve are used to create a first sub-meeting corresponding to at least one first participating terminal.

[0106] Understandably, given the higher terminal level of the first participating terminal, its meeting needs will be prioritized. To ensure smooth resource allocation, a coordination mechanism can be established. The first and second meeting management subsystems can communicate and interact to confirm that both parties agree on the resource allocation plan and agree on details such as the timing and sequence of operations. For example, through the inter-system messaging interface, a message containing the resource allocation plan can be sent, the second meeting management subsystem can confirm resource reservation, and prepare for the actual resource allocation operation.

[0107] Based on the prioritized allocation of meeting resources, a first sub-meeting can be established corresponding to the first participating terminal to ensure the meeting needs of higher-level terminals.

[0108] S208. If the first sub-meeting is successfully created, determine the current second resource reserve. If the current second resource reserve meets the second resource quantity, create a second sub-meeting corresponding to at least one second participating terminal.

[0109] During the creation of the first sub-meeting, the value of the second resource reserve changes because the first resource reserve and part of the second resource reserve are used to meet the first resource quantity requirement. In order to accurately determine whether the second sub-meeting can be created, it is necessary to redetermine the specific situation of the current second resource reserve. Based on the resources after the call is completed, the updated resource reserve is determined, and the judgment is made based on the new resource reserve. Only when the current second resource reserve of each resource meets the corresponding second resource quantity requirement can the resource conditions for creating the second sub-meeting be met, and then the creation work can be carried out.

[0110] In one possible implementation, if the current second resource reserve is insufficient to meet the second resource quantity, the first meeting management subsystem can send a reminder to the customer that the second sub-meeting reservation has failed. The user can choose to prioritize the meeting based on the first sub-meeting or choose to end the current meeting reservation process and re-reserve.

[0111] S209. Generate resource prompt information.

[0112] If the total amount of resources in the first and second resource reserves is insufficient to meet the first resource requirement, it can be determined that the creation of the target meeting at the current first meeting level has failed. At this time, a corresponding resource shortage prompt can be generated so that the user can re-enter the meeting reservation process based on the current prompt information.

[0113] In one possible implementation, if the first meeting management subsystem malfunctions or becomes unusable, the second meeting subsystem is invoked to manage the meeting reservation requests from the first meeting management subsystem.

[0114] Among them, the meeting reservation system can be monitored, and an anomaly protection mechanism can be activated if the first meeting management subsystem is abnormal or unusable.

[0115] Understandably, in the event of an anomaly or unavailability of the first meeting management subsystem, permission transfer can be performed to enable the second meeting management subsystem to legally manage meeting reservation requests originally belonging to the first subsystem. For example, in the system's permission management module, the permission to process meeting reservation requests from the first subsystem can be transferred from the permission group corresponding to the first subsystem to the permission group corresponding to the second subsystem, while ensuring that the second subsystem has permission to access database tables, configuration files, and other resources related to these meeting reservation requests.

[0116] Meanwhile, to enable the second meeting management subsystem to effectively manage meeting booking requests, it can access relevant data already existing in the first meeting management subsystem, achieving data synchronization. This data can include, for example, submitted but unprocessed meeting booking requests, past meeting booking records, and information on attendees and meeting room resources related to the meeting booking. Specifically, this can be achieved through a database backup and recovery mechanism, restoring relevant database backup files from the first meeting management subsystem to a database environment accessible to the second meeting management subsystem; or by using data migration tools, migrating data from the storage location of the first meeting management subsystem to the corresponding storage area of ​​the second meeting management subsystem according to a predetermined data format and mapping relationship, ensuring that the second meeting management subsystem has complete and accurate information to process meeting booking requests.

[0117] The meeting reservation method provided in this embodiment determines the resource requirements of various participating terminals during the meeting creation process in the first meeting management subsystem and makes a judgment based on the existing meeting availability to ensure the normal convening of the meeting. By calling two resource clusters, meeting resources are prioritized for the first participating terminal, ensuring key video conferencing resources and improving the problem of important meetings being unable to be held smoothly due to resource contention during peak business periods. At the same time, an exception mechanism is set up so that if the first meeting management subsystem is abnormal or unavailable, the second meeting management subsystem can be called to effectively manage the meeting reservation request, ensuring the normal operation of meeting reservation services and the smooth progress of meeting organization and management.

[0118] Figure 3 A schematic diagram of the meeting reservation system provided in this application. Figure 3 As shown, the meeting reservation system 300 provided in this embodiment includes:

[0119] The acquisition module 301 is used to acquire a meeting reservation request, which includes: meeting level and multiple participating terminals 302;

[0120] The determination module is used to determine the target meeting management subsystem that matches the meeting level from the first meeting management subsystem 303 and the second meeting management subsystem 304, wherein the meeting level corresponding to the first meeting management subsystem 303 is higher than the meeting level corresponding to the second meeting management subsystem 304;

[0121] The first meeting management subsystem 303 is used to determine at least one first meeting terminal and at least one second meeting terminal among multiple meeting terminals when the target meeting management subsystem is the first meeting management subsystem 303. The terminal level of the first meeting terminal corresponds to the first meeting management subsystem 303, and the terminal level of the second meeting terminal corresponds to the second meeting management subsystem 304.

[0122] The first conference management subsystem 303 is also used to create a target conference at the first conference level; and to make a conference group call for the target conference to at least one first participating terminal based on the first MCU cluster, and to make a conference group call for the target conference to at least one second participating terminal based on the second MCU cluster. The first MCU cluster is the MCU cluster corresponding to the first conference management subsystem 303, and the second MCU cluster is the MCU cluster corresponding to the second conference management subsystem 304.

[0123] Optionally, the first meeting management subsystem 303 is also used to determine the address information and level information of each participating terminal from the meeting reservation system based on multiple participating terminals;

[0124] The first meeting management subsystem 303 is also used to determine at least one first participating terminal and at least one second participating terminal among the multiple participating terminals based on the level information of multiple participating terminals, wherein the first participating terminal corresponds to the first level and the second participating terminal corresponds to the second level.

[0125] Optionally, the first meeting management subsystem 303 is also used to determine the corresponding first resource reserve and the second resource reserve of the second meeting management system, and to determine the first resource quantity and the second resource quantity based on meeting information, at least one first participating terminal and at least one second participating terminal. The first resource quantity is used to indicate the resource quantity required for at least one first terminal to access the meeting, and the second resource quantity is used to indicate the resource quantity required for at least one second terminal to access the meeting.

[0126] The first meeting management subsystem 303 is also used to create a target meeting of the first meeting level when the first resource reserve and the second resource reserve respectively meet the first resource quantity and the second resource quantity.

[0127] Optionally, the first meeting management subsystem 303 is also used to determine whether the total amount of resources in the first resource reserve and the second resource reserve meets the first resource quantity when the first resource reserve does not meet the first resource quantity.

[0128] If the conditions are met, the first and second resource reserves are used to create a first sub-meeting corresponding to at least one first participating terminal.

[0129] If the first sub-meeting is successfully created, determine the current second resource reserve. If the current second resource reserve meets the second resource requirement, create a second sub-meeting corresponding to at least one second participating terminal.

[0130] Optionally, the first conference management subsystem 303 is also used to determine the cascading information between the first MCU cluster and the second MCU cluster, and send the cascading information to the first MCU cluster and the second MCU cluster, so that the first MCU cluster and the second MCU cluster establish conference communication based on the cascading information.

[0131] Optionally, the system may also include: a second meeting management subsystem 304;

[0132] The second meeting management subsystem 304 is used to create a target meeting of the second meeting level when the target meeting management subsystem is the second meeting management subsystem 304, and to make meeting group calls for multiple participating terminals of the target meeting based on the second MCU cluster. The second meeting level is lower than the first meeting level.

[0133] Optionally, the second meeting management subsystem 304 is also used to manage meeting reservation requests of the first meeting management subsystem 303 in the event that the first meeting management subsystem 303 is abnormal or unusable.

[0134] The meeting reservation system provided in this embodiment can execute the methods provided in the above method embodiments. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0135] Figure 4 This is a schematic diagram of the structure of an electronic device provided in this application. Figure 4 As shown, the electronic device 400 provided in this embodiment includes at least one processor 401 and a memory 402.

[0136] Optionally, the device 400 also includes a communication component 403. The processor 401, memory 402, and communication component 403 are connected via a bus 404.

[0137] In a specific implementation, at least one processor 401 executes computer execution instructions stored in memory 402, causing at least one processor 401 to perform the above-described method.

[0138] The specific implementation process of processor 401 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0139] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0140] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0141] It should be understood that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical functional division, and there may be other division methods in actual implementation. For example, multiple units, modules, or components may be combined, or integrated into another system, or some features may be ignored or not executed.

[0142] Furthermore, unless otherwise specified, the functional units / modules in the various embodiments of this application can be integrated into one unit / module, or each unit / module can exist physically separately, or two or more units / modules can be integrated together. The integrated units / modules described above can be implemented in hardware or in the form of software program modules.

[0143] When integrated units / modules are implemented in hardware, the hardware can be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC, etc. Unless otherwise specified, the storage unit can be any suitable magnetic or magneto-optical storage medium, such as Resistive Random Access Memory (RRAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Enhanced Dynamic Random Access Memory (EDRAM), High-Bandwidth Memory (HBM), Hybrid Memory Cube (HMC), etc.

[0144] If the integrated unit / module is implemented as a software program module and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0145] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0146] Other embodiments of this application will readily occur 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 this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0147] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A meeting reservation method, characterized in that, The method is applied to a meeting reservation system, which includes a first meeting management subsystem and a second meeting management subsystem, and includes: Obtain a meeting reservation request, which includes: meeting level and multiple participating terminals; A target meeting management subsystem matching the meeting level is determined from the first meeting management subsystem and the second meeting management subsystem, wherein the meeting level corresponding to the first meeting management subsystem is higher than the meeting level corresponding to the second meeting management subsystem; When the target meeting management subsystem is the first meeting management subsystem, the first meeting management subsystem determines at least one first meeting terminal and at least one second meeting terminal among a plurality of meeting terminals. The terminal level of the first meeting terminal corresponds to the first meeting management subsystem, and the terminal level of the second meeting terminal corresponds to the second meeting management subsystem. The first conference management subsystem creates a target conference at a first conference level; and makes a conference group call for the target conference to at least one first participating terminal based on a first MCU cluster, and makes a conference group call for the target conference to at least one second participating terminal based on a second MCU cluster, wherein the first MCU cluster is the MCU cluster corresponding to the first conference management subsystem, and the second MCU cluster is the MCU cluster corresponding to the second conference management subsystem; The first conference management subsystem determines the cascading information between the first MCU cluster and the second MCU cluster, and sends the cascading information to the first MCU cluster and the second MCU cluster, so that the first MCU cluster and the second MCU cluster establish conference communication based on the cascading information; The meeting reservation request also includes: meeting information, the first meeting management subsystem, and the creation of a target meeting at the first meeting level, including: The first meeting management subsystem determines the corresponding first resource reserve and the second resource reserve of the second meeting management subsystem, and determines the first resource quantity and the second resource quantity based on the meeting information, at least one first participating terminal and at least one second participating terminal. The first resource quantity is used to indicate the resource quantity required for at least one first participating terminal to access the meeting, and the second resource quantity is used to indicate the resource quantity required for at least one second participating terminal to access the meeting. If the first resource reserve and the second resource reserve respectively satisfy the first resource quantity and the second resource quantity, create a target meeting of the first meeting level; If the first resource reserve does not meet the first resource quantity, the first meeting management subsystem determines whether the total amount of resources of the first resource reserve and the second resource reserve meets the first resource quantity. If the conditions are met, the first resource reserve and the second resource reserve are used to create a first sub-meeting corresponding to at least one of the first participating terminals; If the first sub-meeting is successfully created, determine the current second resource reserve. If the current second resource reserve meets the second resource quantity, create a second sub-meeting corresponding to at least one second participating terminal.

2. The method according to claim 1, characterized in that, The first meeting management subsystem identifies at least one first participating terminal and at least one second participating terminal among multiple participating terminals, including: The first meeting management subsystem determines the address and level information of each participating terminal from the meeting reservation system based on multiple participating terminals. Based on the level information of the multiple participating terminals, at least one first participating terminal and at least one second participating terminal are determined among the multiple participating terminals, wherein the first participating terminal corresponds to the first level and the second participating terminal corresponds to the second level.

3. The method according to claim 1, characterized in that, The method further includes: When the target meeting management subsystem is the second meeting management subsystem, the second meeting management subsystem creates a target meeting of the second meeting level and makes a meeting group call for the target meeting to multiple participating terminals based on the second MCU cluster. The second meeting level is lower than the first meeting level.

4. The method according to claim 1, characterized in that, The method further includes: If the first meeting management subsystem malfunctions or becomes unusable, the second meeting management subsystem is invoked to manage the meeting reservation requests from the first meeting management subsystem.

5. A meeting reservation system, characterized in that, The system includes: The acquisition module is used to acquire meeting reservation requests, which include: meeting level and multiple participating terminals; The determining module is used to determine a target meeting management subsystem that matches the meeting level from the first meeting management subsystem and the second meeting management subsystem, wherein the meeting level corresponding to the first meeting management subsystem is higher than the meeting level corresponding to the second meeting management subsystem; The first meeting management subsystem is used to determine at least one first meeting terminal and at least one second meeting terminal among a plurality of meeting terminals when the target meeting management subsystem is the first meeting management subsystem. The terminal level of the first meeting terminal corresponds to the first meeting management subsystem, and the terminal level of the second meeting terminal corresponds to the second meeting management subsystem. The first conference management subsystem is also used to create a target conference of the first conference level; and to make a conference group call for the target conference to the at least one first participating terminal based on the first MCU cluster, and to make a conference group call for the target conference to the at least one second participating terminal based on the second MCU cluster, wherein the first MCU cluster is the MCU cluster corresponding to the first conference management subsystem, and the second MCU cluster is the MCU cluster corresponding to the second conference management subsystem; The first conference management subsystem is further configured to determine the cascading information between the first MCU cluster and the second MCU cluster, and send the cascading information to the first MCU cluster and the second MCU cluster, so that the first MCU cluster and the second MCU cluster establish conference communication based on the cascading information; The meeting reservation request also includes: meeting information; the first meeting management subsystem, when creating a target meeting of the first meeting level, specifically determines the corresponding first resource reserve and the second resource reserve of the second meeting management subsystem, and determines the first resource quantity and the second resource quantity based on the meeting information, at least one first participating terminal and at least one second participating terminal. The first resource quantity is used to indicate the resource quantity required for at least one first participating terminal to access the meeting, and the second resource quantity is used to indicate the resource quantity required for at least one second participating terminal to access the meeting. If the first resource reserve and the second resource reserve respectively meet the first resource quantity and the second resource quantity, a target meeting of the first meeting level is created. If the first resource reserve does not meet the first resource quantity, it is determined whether the total resource quantity of the first resource reserve and the second resource reserve meets the first resource quantity. If it does, the first resource reserve and the second resource reserve are invoked to create a first sub-meeting corresponding to at least one first participating terminal. If the first sub-meeting is successfully created, the current second resource reserve is determined. If the current second resource reserve meets the second resource quantity, a second sub-meeting corresponding to at least one second participating terminal is created.

6. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 4.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 4.

8. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 4.

Images