A method, apparatus, electronic device and storage medium for meeting restoration

Abstract

The present application provides a conference restoration method, apparatus, electronic device, and storage medium. The method is applied to a node device in a Visual Networking (VN) network. The method includes: in a VN video conference, when it is necessary to activate a node device as an active node in the VN network, determining an activation type, where the activation type is determined according to the type of the node device to which the VN video conference belongs and the type of the node device, and the active node is the only node device in the VN network that provides VN services; and restoring the VN video conference on the node device according to a conference restoration policy corresponding to the activation type. This method can set different conference restoration policies for switching operations between different types of active nodes, enabling the node device to restore an interrupted VN video conference according to the characteristics of different types of switching operations. Compared with the method of generally restoring an interrupted VN video conference according to the same method, the conference restoration effect can be significantly improved.

Description

Technical Field

[0001] The present application relates to the technical field of data processing, and in particular, to a conference recovery method, apparatus, electronic device, and storage medium. Background Art

[0002] Currently, with the popularization and development of the video Internet of Things (VIoT) services across the country, the high-definition video interaction technology of the VIoT plays a crucial role in government departments and other industries. The VIoT adopts the world's most advanced VisionVera real-time high-definition video exchange technology to achieve real-time transmission of full-network high-definition videos that cannot be achieved by the current Internet.

[0003] The VIoT network consists of multiple node devices, and the node devices have various types. When a certain node device fails and cannot work, it is necessary to restore the interrupted services on the failed node on another new node device to take over the work of the failed node device. When switching between different types of node devices, the operations to be performed during service restoration are different. In the related art, a unified method is used to restore services. For example, a unified method is used to restore interrupted conference services, which severely restricts the service restoration effect. Therefore, how to improve the service restoration effect when node devices switch has become an urgent problem to be solved. Summary of the Invention

[0004] In view of the above problems, the present application provides a conference recovery method, apparatus, electronic device, and storage medium, which can better restore the VIoT video conference interrupted due to node device failures and improve the conference recovery effect.

[0005] The first aspect of the present application provides a conference recovery method, which is applied to a node device in a VIoT network. The method includes:

[0006] In a VIoT video conference, when it is necessary to activate the node device as an active node in the VIoT network, determine the activation type, where the activation type is determined according to the node type of the original active node of the VIoT video conference and the node type of the node device, and the active node is the only node device that provides VIoT services in the VIoT network;

[0007] Restore the VIoT video conference on the node device according to the conference recovery strategy corresponding to the activation type.

[0008] Optionally, the types of node devices in the VIoT network include a master node, a standby node, and a slave node; determining the activation type includes:

[0009] When the original active node is the primary node and the node device is the standby node, or the original active node is the standby node and the node device is the primary node, determine that the activation type is primary-standby switch;

[0010] When the original active node is the standby node and the node device is the slave node, or the original active node and the node device are different slave nodes, determine that the activation type is slave-slave switch;

[0011] When the original active node is the slave node and the node device is the primary node, or the original active node is the slave node and the node device is the standby node, determine that the activation type is slave-primary switch.

[0012] Optionally, according to the conference recovery policy corresponding to the activation type, restore the Visual Networking video conference on the node device, including:

[0013] Determine the delay waiting duration corresponding to the activation type;

[0014] When the delay waiting duration is reached, for the participating terminals that have joined the Visual Networking video conference, start the Visual Networking video conference.

[0015] Optionally, the restoring of the Visual Networking video conference on the node device according to the conference recovery policy corresponding to the activation type includes:

[0016] When all participating terminals have joined the Visual Networking video conference, start the Visual Networking video conference.

[0017] Optionally, determining the delay waiting duration corresponding to the activation type includes:

[0018] When the activation type is primary-standby switch, determine that the delay waiting duration is the first duration, and the first duration includes the joining duration of the participating terminals;

[0019] When the activation type is slave-slave switch, determine that the delay waiting duration is the second duration, and the second duration includes the network access duration and the joining duration of the participating terminals;

[0020] When the activation type is slave-primary switch, determine that the delay waiting duration is the third duration, and the third duration includes the detection duration, the network access duration of the participating terminals, and the joining duration, and the detection duration is used to detect whether the heartbeat connection between the primary node and the standby node is disconnected.

[0021] Optionally, a first type of heartbeat connection is established between each node device in the Visual Networking; the method further includes:

[0022] Detect whether the first type of heartbeat connection with the original active node of the Visual Networking video conference is disconnected;

[0023] When the first type of heartbeat connection is disconnected, it is determined that the node device needs to be activated as an active node in the Visual Networking.

[0024] Optionally, a second type of heartbeat connection is also maintained between the primary node and the standby node; before the delay waiting duration is reached, the method further includes:

[0025] If the activation type is primary-standby switch, wait for the participating terminal to join the Visual Networking video conference within the conference joining duration.

[0026] If the activation type is secondary-secondary switch, wait for the participating terminal to access the network within the network access duration, and within the conference joining duration, wait for the participating terminal that has successfully accessed the network to join the Visual Networking video conference.

[0027] If the activation type is secondary-primary switch, within the detection duration, detect whether the second type of heartbeat connection is disconnected. If the second type of heartbeat connection is disconnected, wait for the participating terminal to access the network within the network access duration, and within the conference joining duration, wait for the participating terminal that has successfully accessed the network to join the Visual Networking video conference.

[0028] A second aspect of the present application provides another conference recovery device, which is applied to a node device in the Visual Networking. The device includes:

[0029] A first determination module, configured to determine an activation type when it is necessary to activate the node device as an active node in the Visual Networking in a Visual Networking video conference. The activation type is determined according to the node type of the original active node in the Visual Networking video conference and the node type of the node device. The active node is the only node device that provides Visual Networking services in the Visual Networking.

[0030] A recovery module, configured to recover the Visual Networking video conference on the node device according to a conference recovery policy corresponding to the activation type.

[0031] Optionally, the types of node devices in the Visual Networking include a primary node, a standby node, and a secondary node; to determine the activation type, the first determination module includes:

[0032] A first determination sub-module, configured to determine that the activation type is primary-standby switch when the original active node is a primary node and the node device is a standby node, or when the original active node is a standby node and the node device is a primary node.

[0033] A second determination sub-module, configured to determine that the activation type is secondary-secondary switch when the original active node is a standby node and the node device is a secondary node, or when the original active node and the node device are different secondary nodes.

[0034] A third determination sub-module, configured to determine that the activation type is a slave-to-master switch when the original active node is a slave node and the node device is a master node, or when the original active node is a slave node and the node device is a standby node.

[0035] Optionally, the recovery module includes:

[0036] A fourth determination sub-module, configured to determine a delay waiting duration corresponding to the activation type;

[0037] A first activation sub-module, configured to activate the Visual Networking video conference for the participating terminals that have joined the Visual Networking video conference when the delay waiting duration is reached.

[0038] Optionally, the recovery module includes:

[0039] A second activation sub-module, configured to activate the Visual Networking video conference when all participating terminals have joined the Visual Networking video conference.

[0040] Optionally, the fourth determination sub-module includes:

[0041] A fifth determination sub-module, configured to determine that the delay waiting duration is a first duration when the activation type is a master-standby switch, and the first duration includes the joining duration of the participating terminals;

[0042] A sixth determination sub-module, configured to determine that the delay waiting duration is a second duration when the activation type is a slave-slave switch, and the second duration includes the network joining duration and the joining duration of the participating terminals;

[0043] A seventh determination sub-module, configured to determine that the delay waiting duration is a third duration when the activation type is a slave-to-master switch, and the third duration includes a detection duration, the network joining duration, and the joining duration of the participating terminals, where the detection duration is used to detect whether the heartbeat connection between the master node and the standby node is disconnected.

[0044] Optionally, a first type of heartbeat connection is established between each node device in the Visual Networking; the apparatus further includes:

[0045] A detection module, configured to detect whether the first type of heartbeat connection with the original active node of the Visual Networking video conference is disconnected;

[0046] A second determination module, configured to determine that the node device needs to be activated as an active node in the Visual Networking when the first type of heartbeat connection is disconnected.

[0047] Optionally, a second type of heartbeat connection is further maintained between the master node and the standby node; the apparatus further includes:

[0048] A first delay module, configured to, if the activation type is primary - standby switchover, wait for the participating terminal to join the Visual Networking video conference within the conference joining duration.

[0049] A second delay module, configured to, if the activation type is slave - slave switchover, wait for the participating terminal to access the network within the network access duration, and within the conference joining duration, wait for the participating terminal that has successfully accessed the network to join the Visual Networking video conference.

[0050] A third delay module, configured to, if the activation type is slave - primary switchover, detect whether the second - type heartbeat connection is disconnected within the detection duration. If the second - type heartbeat connection is disconnected, wait for the participating terminal to access the network within the network access duration, and within the conference joining duration, wait for the participating terminal that has successfully accessed the network to join the Visual Networking video conference.

[0051] A third aspect of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes, the steps of the conference recovery method described in the first aspect of the present application are implemented.

[0052] A fourth aspect of the present application provides a computer - readable storage medium, on which a computer program is stored. When the program is executed by a processor, the steps in the conference recovery method described in the first aspect of the present application are implemented.

[0053] Through the conference recovery method of the present application, in a Visual Networking video conference, when it is necessary to activate a node device as an active node in the Visual Networking, first determine the activation type, which is determined according to the type of the node device to which the Visual Networking video conference belongs and the type of the node device. The active node is the only node device in the Visual Networking that provides Visual Networking services. Then, according to the conference recovery strategy corresponding to the activation type, recover the Visual Networking video conference on the node device. This method sets corresponding conference recovery strategies for the switching operations between different types of active nodes in the Visual Networking, enabling the node device to recover the interrupted Visual Networking video conference according to the characteristics of different types of switching operations. Compared with the method in the related art that generally recovers the interrupted Visual Networking video conference according to the same method, the method of the present application can better recover the Visual Networking video conference interrupted due to node device failures and improve the conference recovery effect. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] To more clearly illustrate the technical solutions of the embodiments of the present application, the accompanying drawings required for the description of the embodiments of the present application will be briefly introduced below.

[0055] Figure 1 It is a schematic structural diagram of a Visual Networking shown in an embodiment of the present application;

[0056] Figure 2 is a flowchart of a conference recovery method shown in an embodiment of the present application;

[0057] Figure 3 is a schematic diagram of the process of a conference recovery method shown in an embodiment of the present application;

[0058] Figure 4 is a structural block diagram of a conference recovery device shown in an embodiment of the present application. Detailed implementation manners

[0059] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0060] Figure 1 is a schematic diagram of the structure of the Visual Networking (VN) network shown in an embodiment of the present application. In the present application, each geographical area (pre-divided) corresponds to a VN network, and the VN network corresponds to a VN server cluster. The specific structure of the VN server cluster can be as Figure 1 shown. In Figure 1 , the thick black solid line box represents a node device. Each node device is a server, and each node device includes a database, an operation and maintenance system, a storage system, a conference management system, a network management system, and an autonomous system inside.

[0061] Among them, the types of node devices include: a primary node, a standby node, and a slave node. In a VN server cluster, there is one primary node, one standby node, and multiple slave nodes. In Figure 1 , the primary node is server A1, which includes database A1, operation and maintenance system A1, storage system A1, conference management system A1, network management system A1, and autonomous system A1; the standby node is server A2, which includes database A2, operation and maintenance system A2, storage system A2, conference management system A2, network management system A2, and autonomous system A2; one slave node is server B, which includes database B, operation and maintenance system B, storage system B, conference management system B, network management system B, and autonomous system B.

[0062] In Figure 1 , multiple servers, switches, sub-control devices, and terminals constitute the entire VN network. The primary node and the standby node are both managed by the same integrated management server A ( Figure 1The dashed box in the middle represents the integrated management server), and the integrated management server A adopts a dual-machine hot standby mechanism (composed of two servers, the main and backup servers, and the two servers are autonomously connected to the same visual network server) to manage server A1 and server A2. The number of slave nodes of the visual network can be one or more, Figure 1 3 shows a case where there are three slave nodes, namely server B (managed by integrated management server B), server C (managed by integrated management server C), and server D (managed by integrated management server D).

[0063] Meeting management refers to the meeting management and scheduling system, which is responsible for the internal logic processing of meeting operations, such as speaker switching, meeting start / stop, dynamic addition and deletion of participants, etc. The program is divided into the meeting management front-end WEB management and the back-end scheduling program. The scheduling program is divided into two sub-programs, CMS and DMS. CMS is responsible for interacting with the WEB interface, and DMS is responsible for the underlying meeting and control logic.

[0064] Network management refers to the visual network OMC network management system, which is responsible for the registration, deregistration and real-time status monitoring of various visual network video terminals, switches, and routers, user authority management, terminal level, legality verification and other functions.

[0065] The autonomous system is used to control the core server of the video network through the video network protocol to perform conference business operations such as hosting and controlling meetings.

[0066] The databases on multiple servers (multiple node devices) are synchronized in real time to ensure data consistency of each node, making it convenient for conference managers to restore conference services through data saved in the database.

[0067] The storage system is used to store data during node operation.

[0068] The operation and maintenance system is used to maintain the normal operation of the entire node.

[0069] This application provides a conference recovery method, which is applied to Figure 1 Any node device in . Figure 2 1 is a flowchart of a conference recovery method shown in an embodiment of the present application. Figure 1 The conference recovery method of the present application may include the following steps:

[0070] Step S21: In a visual networking video conference, when a node device needs to be activated as an active node in the visual networking network, the activation type is determined. The activation type is determined based on the node type of the original active node of the visual networking video conference and the node type of the node device. The active node is the only node device in the visual networking network that provides visual networking services.

[0071] In this embodiment, each node device can be communicatively connected to other node devices, and each node device stores node configuration files of other node devices internally. The node configuration files record the types and roles of the affiliated node devices. The types of node devices can include master nodes, standby nodes, and slave nodes, and the roles of node devices can include active nodes and inactive nodes. Only one node device can be in an active state at the same time in the Vision Network, that is, only one node device can provide Vision Network services (such as Vision Network video conferencing services) externally at the same time in the Vision Network. This node device is the active node, and the remaining node devices are inactive nodes.

[0072] In step S21, a Vision Network video conference is in progress on the active node. If the active node suddenly fails, a new active node needs to be reactivated, and the Vision Network video conference interrupted on the old active node is resumed on the new active node. In this process, the old active node is the original active node of the Vision Network video conference. Among them, the activation type can be determined according to the types of the old active node and the new active node.

[0073] In this embodiment, it can be detected by the node device whether it needs to be activated as an active node, or it can be detected by other devices whether a node device needs to be activated as an active node. If so, the node device is notified to activate itself as an active node. In actual implementation, any method can be used to detect whether a node device needs to be activated as an active node in the Vision Network, and this embodiment does not limit this.

[0074] For the convenience of subsequent description of each embodiment, this application takes the node device itself detecting whether it needs to be activated as an active node as an example to illustrate the conference recovery method. In implementation, the network management in the node device can detect whether the node device needs to be activated as an active node.

[0075] In this embodiment, the activation order of each node device in the Vision Network is preset in advance. When a certain node device fails, other node devices are activated in the preset priority order. For example, Figure 1 the activation order can be set as: master node > standby node > slave node B > slave node C > slave node D. In this way, when the master node fails, the standby node can be activated; when the standby node fails, slave node A can be activated; when slave node A fails, slave node B can be activated, and so on.

[0076] According to the above activation order, if Figure 1 in the network shown, the active node is server A1, and if server A1 fails at a certain moment, then server A2 needs to be activated as the active node. If Figure 1The active node in the shown network is Server B. If Server B fails at a certain moment, then Server C needs to be activated as the active node.

[0077] In specific implementation, for a certain node device, when it detects that a certain other node device connected to itself fails, it can determine whether the node device is an active node by checking the node configuration file of the faulty node device. If the faulty node is an active node, it determines whether itself is the new active node (the node device that takes over the faulty active node) according to the pre-set activation order. If so, then it continues to determine the activation type.

[0078] Among them, the activation type can include three types: primary-backup switch, slave-slave switch, and slave-primary switch. The primary-backup switch means switching from the primary node to the backup node or from the backup node to the primary node. The slave-slave switch means switching from the backup node to the slave node or switching between different slave nodes. The slave-primary switch means switching from the slave node to the primary node or from the slave node to the backup node. The activation type will be specifically described later.

[0079] Step S22: Recover the Visual Networking video conference on the node device according to the conference recovery policy corresponding to the activation type.

[0080] In this embodiment, different conference recovery policies can be pre-set for different activation types, and according to the conference recovery policy, the Visual Networking video conference interrupted when the old active node fails is recovered on the newly activated active node.

[0081] In this embodiment, since the databases on each node device are synchronized in real time, therefore, the conference management of the node device as the new active node can directly read the conference data of the interrupted Visual Networking video conference from the database and recover the Visual Networking video conference.

[0082] Exemplarily, taking Figure 1 as an example, if the old active node is the primary node and the Visual Networking video conference (conference ID: XXXX) created by the primary node fails, then the next-level node of the old active node (i.e., the backup node), when learning that it needs to be activated as the active node, determines that the activation type is primary-backup switch, obtains the corresponding conference recovery policy, and then reads the conference data of the Visual Networking video conference to be recovered (conference ID: XXXX) from its own database according to the conference recovery policy and recovers the video conference on itself (the recovered conference ID is still XXXX).

[0083] In this embodiment, the above steps S21 - S22 can be executed by the conference management in the node device.

[0084] Through the conference restoration method of this application, in a Visual Networking video conference, when a node device needs to be activated as an active node in the Visual Networking, first determine the activation type, which is determined according to the node type of the original active node in the Visual Networking video conference and the node type of the node device. The active node is the only node device that provides Visual Networking services in the Visual Networking. Then, according to the conference restoration policy corresponding to the activation type, restore the Visual Networking video conference on the node device. This method sets corresponding conference restoration policies for the switching operations between different types of active nodes in the Visual Networking, enabling the node device to restore the interrupted Visual Networking video conference according to the characteristics of different types of switching operations. Compared with the method in the related art that generally restores the interrupted Visual Networking video conference according to the same method, the method of this application can better restore the Visual Networking video conference interrupted due to node device failures.

[0085] Combined with the above embodiments, in one implementation, this application also provides a method for determining the activation type, which may specifically include:

[0086] When the original active node is the master node and the node device is the standby node, or the original active node is the standby node and the node device is the master node, determine that the activation type is master-standby switching;

[0087] When the original active node is the standby node and the node device is the slave node, or the original active node and the node device are different slave nodes, determine that the activation type is slave-slave switching;

[0088] When the original active node is the slave node and the node device is the master node, or the original active node is the slave node and the node device is the standby node, determine that the activation type is slave-master switching.

[0089] Each step in this embodiment is executed by the conference management of the target node.

[0090] In this embodiment, the corresponding relationship between the activation type and the node type of the node device is stored in each node device, enabling the node device to quickly determine the activation type according to the corresponding relationship after obtaining the node type of the old active node. This corresponding relationship can be stored in the form of a table. For example, it can be as shown in Table 1 below:

[0091] Activation type Type of node device Primary / backup switchover Primary node > Backup node, Backup node > Primary node Backup-backup switchover Backup node > Slave node, Slave node > Slave node Slave-primary switchover Slave node > Primary node, Slave node > Backup node

[0092] Table 1

[0093] In Table 1, the node before the > sign represents the node type of the original active node (old active node), and the node after the > sign represents the node type of the node device as the new active node. Specifically, when switching from the primary node to the standby node, or from the standby node to the primary node, it corresponds to the activation type of the primary-standby switch. When switching from the standby node to the secondary node, or switching between two different secondary nodes, it corresponds to the activation type of the secondary-secondary switch. When switching from the secondary node to the primary node, or from the secondary node to the standby node, it corresponds to the activation type of the secondary-primary switch.

[0094] In this embodiment, a correspondence relationship is set between the activation type and the node type of the node device, so that after the node device obtains the node type of the original active node and its own node type, it can quickly determine the activation type according to the correspondence relationship, improving the efficiency of meeting recovery.

[0095] Combined with the above embodiments, in one implementation manner, the present application provides a meeting recovery strategy. On this basis, according to the meeting recovery strategy corresponding to the activation type, restoring the Visual Networking video conference on the node device may include the following steps:

[0096] Determine the delay waiting duration corresponding to the activation type;

[0097] When the delay waiting duration is reached, for the participating terminals that have joined the Visual Networking video conference, start the Visual Networking video conference.

[0098] Each step in this embodiment is executed by the meeting management in the node device.

[0099] In this embodiment, when the original old active node fails, each participating terminal in the interrupted Visual Networking video conference may exit the Visual Networking. Therefore, the node device needs to spend a certain amount of time waiting for each participating terminal to access the Visual Networking, and then wait for the successfully accessed participating terminals to join the Visual Networking video conference, and then start the Visual Networking video conference. After starting the Visual Networking video conference, the entire interrupted conference service is considered to be fully restored successfully.

[0100] However, the meeting management programs deployed in all node devices are the same set of programs, and the meeting management does not know which server the failed old active node is (only the network management knows). Therefore, in some scenarios, after the meeting management of the node device restores the meeting data of the Visual Networking video conference, it directly pulls the participating terminals into the Visual Networking video conference and starts the meeting, resulting in some participating terminals that have exited the Visual Networking being unable to join the Visual Networking video conference because they have not had time to access the network. Therefore, the recovery effect of the interrupted conference service is not ideal.

[0101] The method of this embodiment can well solve this problem. Under different activation types, the time required for the participating terminal to re-enter the Visual Networking after exiting it is different. Therefore, this embodiment sets different delay waiting durations for different activation types. During this delay waiting duration, the node device can wait for the participating terminal that has exited the Visual Networking to enter the network, and can wait for the participating terminal that has successfully entered the network to join the Visual Networking video conference. When the delay waiting duration ends, the Visual Networking video conference is started, thereby reducing the probability that the participating terminal cannot join the Visual Networking video conference due to not entering the network, and overall improving the recovery effect of the interrupted conference service.

[0102] In this embodiment, the participating terminal can either actively join the Visual Networking video conference (the participating terminal actively sends an invitation request to the node device and joins the conference after obtaining permission), or join the Visual Networking video conference in response to the conference invitation of the node device. When the node device sends a conference invitation to the participating terminal, it can send the conference invitation periodically, so as to ensure with the highest probability that the participating terminal can smoothly join the Visual Networking video conference. This application does not specifically limit the way for the participating terminal to join the Visual Networking video conference.

[0103] Among them, the delay waiting duration corresponding to different activation types can be set according to actual needs, and this embodiment does not specifically limit this.

[0104] In this embodiment, different delay waiting durations are set for different activation types, which can reduce the probability that the participating terminal cannot join the Visual Networking video conference due to not yet entering the network, and overall improve the recovery effect of the interrupted conference service.

[0105] Combined with the above embodiments, in one implementation, this application also provides another conference recovery strategy. On this basis, according to the conference recovery strategy corresponding to the activation type, the Visual Networking video conference is restored on the node device, which can specifically include the following steps:

[0106] When all participating terminals have joined the Visual Networking video conference, start the Visual Networking video conference.

[0107] In this embodiment, after the original active node fails, the participating terminals may exit the Visual Networking. After a participating terminal exits the Visual Networking, it will automatically send an access request to the autonomous system, and the autonomous system will complete the access operation. When a certain participating terminal successfully accesses the network, the autonomous system will send a network access success notification to the conference management. At this time, the conference management waits for the participating terminal that has successfully accessed the network to join the Visual Networking video conference. If the joining is successful, the conference management will receive the joining success notification sent by this participating terminal. When receiving the joining success notifications sent by all the participating terminals, it is determined that all the participating terminals have joined the Visual Networking video conference. If the participating terminals do not exit the Visual Networking after the original active node fails, then the conference management can directly wait for the participating terminals to join the Visual Networking video conference, and when receiving the joining success notifications sent by all the participating terminals, determine that all the participating terminals have joined the Visual Networking video conference.

[0108] In this embodiment, in order to prevent the Visual Networking video conference from not being able to start when the joining success notification of a certain participating terminal is not received, a preset duration can also be set. If within the preset duration, the conference management receives the joining success notifications sent by all the participating terminals, then the conference management can start the Visual Networking video conference at the moment when the last participating terminal joins the Visual Networking video conference, without waiting until the preset duration ends. If at the end of the preset duration, the conference management has not received the joining success notification sent by a certain participating terminal, then the conference management can directly start the Visual Networking video conference without waiting for those participating terminals that have not joined the conference, ensuring the normal progress of the Visual Networking video conference.

[0109] In this embodiment, the Visual Networking video conference can be started when all the participating terminals have joined the Visual Networking video conference, realizing the start of the Visual Networking video conference according to the dynamic joining situation of each participating terminal, and improving the flexibility of conference recovery.

[0110] In specific implementation, different conference recovery strategies can be arbitrarily set for different activation types. For example, the first conference recovery strategy can be set for the activation type of primary-backup switchover, and the second conference recovery strategy can be set for the slave-slave switchover and slave-primary switchover. The first conference recovery strategy can also be directly set for all the activation types, which can be specifically set according to actual needs, and this application does not limit this.

[0111] Combined with the above embodiments, in one implementation manner, this application also provides a method for determining the delay waiting duration corresponding to the activation type, which can specifically include:

[0112] When the activation type is primary-backup switchover, determine that the delay waiting duration is the first duration, and the first duration includes the access duration of the participating terminal;

[0113] When the activation type is slave-to-slave switch, determine that the delay waiting duration is the second duration, and the second duration includes the network access duration and the meeting entry duration of the participating terminal;

[0114] When the activation type is slave-to-master switch, determine that the delay waiting duration is the third duration, and the third duration includes the detection duration, the network access duration of the participating terminal, and the meeting entry duration. The detection duration is used to detect whether the heartbeat connection between the primary node and the standby node is disconnected.

[0115] Each step in this embodiment is executed by the meeting management of the target node.

[0116] In this embodiment, under different activation types, the duration required for each participating terminal to rejoin the Visual Networking video conference after exiting the Visual Networking is different. Specifically, the first duration is less than the second duration, and the second duration is less than the third duration.

[0117] When the activation type is primary-standby switch, since a dual hot standby mechanism is configured between the primary node and the standby node, and the autonomous systems on the two node devices are connected to the same integrated management server, each participating terminal does not need to exit the Visual Networking and can quickly join the Visual Networking video conference on the standby node. Therefore, the first duration needs to include the meeting entry duration of the participating terminal.

[0118] When the activation type is slave-to-slave switch, the participating terminal will have a process of exiting and then re-entering the network. The participating terminal needs to wait until the network access is successful before joining the Visual Networking video conference. Therefore, the second duration needs to include the network access duration and the meeting entry duration of the participating terminal.

[0119] When the activation type is slave-to-master switch, since a dual hot standby mechanism is adopted between the primary node and the standby node, the autonomous system of the standby node will have a process of detecting whether it is out of step (whether the heartbeat connection between the autonomous systems of the primary and standby nodes is disconnected). After this process ends, the participating terminal will be loaded to access the network, and the participating terminal can join the Visual Networking video conference after the network access is successful. Therefore, the third duration needs to include the detection duration, the network access duration of the participating terminal, and the meeting entry duration.

[0120] In this embodiment, different delay waiting durations are set for each activation type according to the different durations required when the participating terminal exits the Visual Networking and then rejoins the Visual Networking video conference, which can reduce the probability that the participating terminal cannot join the Visual Networking video conference due to not being networked yet, and overall improve the recovery effect of the interrupted conference service.

[0121] Combined with the above embodiments, in one implementation, a first type of heartbeat connection is established between each node device in the Visual Networking; on this basis, the meeting recovery method of this application can further include:

[0122] Detect whether the first type of heartbeat connection with the original active node of the Visual Networking video conference is disconnected;

[0123] When the first type of heartbeat connection is disconnected, it is determined that the node device needs to be activated as an active node in the Vision Network.

[0124] In this embodiment, a first type of heartbeat connection is established between the network managers of each node device in the Vision Network.

[0125] In specific implementation, for a certain node device X, when it is detected that the first type of heartbeat connection with the network manager of another node device Y is disconnected, it can be determined that the node device Y has a fault. Then, the node device X can determine whether the node device Y is an active node by viewing the node configuration file of the faulty node device Y. If the node device Y is an active node, the node device X determines whether it is a new active node (the node device that replaces the faulty active node device Y) according to the preset activation order. If so, then obtain the type of the node device Y according to the node configuration file of the node device Y, obtain the type of the node device X according to the node configuration file of the node device X, and determine the activation type according to the type of the node device Y, the type of the node device X, and the corresponding relationship between the activation type and the type of the node device.

[0126] In specific implementation, it can be detected by the network manager of the node device whether the first type of heartbeat connection with the old active node is disconnected. If it is disconnected, it is determined that the old active node has a fault and needs to be switched to a new active node. At this time, the network manager reads the node configuration file of the old active node to determine the role of the old active node, and at the same time determines the role of the new active node according to its own node configuration file, and then writes the role of the old active node and the role of the new active node into the shared file. The shared file is sent to the meeting manager of the node device, and the meeting manager of the node device determines the activation type according to the shared file and the corresponding relationship.

[0127] In this embodiment, by establishing a first type of heartbeat connection between the network managers of each node device, the subordinate node device can quickly detect whether a fault occurs according to the first type of heartbeat connection with the active node, which can improve the fault detection efficiency and thus improve the meeting recovery efficiency.

[0128] Combined with the above embodiments, in one implementation manner, a second type of heartbeat connection is also maintained between the network managers of the master node and the standby node, and the second type of heartbeat connection is different from the first type of heartbeat connection. On this basis, when the delay waiting duration is not reached, the method of the present application may further include:

[0129] If the activation type is master-standby switch, wait for the participating terminal to join the Vision Network video conference within the meeting duration;

[0130] If the activation type is slave-slave switch, wait for the participating terminal to access the network within the network access duration, and within the meeting duration, wait for the participating terminal that has successfully accessed the network to join the Vision Network video conference;

[0131] If the activation type is switching from the master, during the detection duration, it is detected whether the second type of heartbeat connection is disconnected. If the second type of heartbeat connection is disconnected, during the network access duration, it waits for the participating terminal to access the network, and during the meeting entry duration, it waits for the participating terminal that has successfully accessed the network to join the Visual Networking video conference.

[0132] In this embodiment, since a dual - machine hot - standby mechanism is adopted between the primary node and the standby node, a second type of heartbeat connection (dual - machine hot - standby heartbeat connection) different from the first type of heartbeat connection (network management heartbeat connection) is established between the primary node and the standby node.

[0133] For the primary - standby switch, since the primary node (such as Figure 1 server A1 in Figure 1 and the standby node (such as

[0134] Figure 1 server A2 in

[0134] are configured with a dual - machine hot - standby mechanism, and the autonomous systems on the two servers are connected to the same Visual Networking server (comprehensive management server A), the participating terminal can be quickly switched to the standby node. During this switching period, the participating terminal does not exit the Visual Networking, and the speed is the fastest, about 2 seconds. Therefore, for the primary - standby switch, the corresponding delay waiting duration can be set to 2 seconds. During the delay waiting duration, it waits for the participating terminal in the interrupted Visual Networking conference to join the Visual Networking video conference. When the delay waiting duration ends, the Visual Networking video conference is started. For the slave - slave switch, the terminal will have a process of exiting the Visual Networking and then accessing the Visual Networking again. Therefore, the terminal needs to wait until it accesses the Visual Networking before it can join the Visual Networking video conference, and the speed is slower, about 30 seconds. Therefore, for the slave - slave switch, the corresponding delay waiting duration can be set to 30 seconds, and then the delay waiting duration is divided into a network access duration and a meeting entry duration. First, during the network access duration, it waits for the participating terminal to access the network, and then during the meeting entry duration, it waits for the participating terminal that has successfully accessed the network to join the Visual Networking video conference. When the delay waiting duration ends, the Visual Networking video conference is started. For the slave - master switch, since it involves the dual - machine hot - standby mechanism between the primary node and the standby node, there is also a process of detecting whether the second type of heartbeat connection between the primary and the standby is disconnected. After this process ends, the terminal network access is loaded. Therefore, the slave - master switch takes the longest time, about 70 seconds. Therefore, for the slave - master switch, the corresponding delay waiting duration can be set to 70 seconds, and then the delay waiting duration is divided into a detection duration, a network access duration, and a meeting entry duration. First, during the detection duration, it is detected whether the second type of heartbeat connection is disconnected. If it is disconnected, then during the network access duration, it waits for the participating terminal to access the network, and then during the meeting entry duration, it waits for the participating terminal that has successfully accessed the network to join the Visual Networking video conference. When the delay waiting duration ends, the Visual Networking video conference is started.Regardless of the activation type, when the participating terminal joins the Visual Networking video conference, it can either actively send a conference entry request to the node device and join the Visual Networking conference, or wait for the node device to send a conference invitation and join the Visual Networking conference. For primary-to-secondary and secondary-to-secondary switches, since the participating terminal will have a process of disconnecting from the network and then reconnecting to the network, the node device does not know when the participating terminal will successfully reconnect to the network. Therefore, if the method of the node device sending a conference invitation is adopted, the node device can send a conference invitation at regular time intervals to ensure that the participating terminal can smoothly join the Visual Networking video conference with the highest probability. In this embodiment, according to the different durations required when the participating terminal exits the Visual Networking and then rejoins the Visual Networking video conference, different delay waiting durations are set for each activation type, which can reduce the probability that the participating terminal cannot join the Visual Networking video conference due to not being connected to the network yet, and overall improve the recovery effect of the interrupted conference service.

[0135] Figure 3 It is a schematic diagram of the process of a conference recovery method shown in an embodiment of the present application. The following will combine Figure 3 to describe the conference recovery method of the present application in detail.

[0136] In Figure 3 when the network management in the node device detects that the first type of heartbeat connection with the network management of the old active node is disconnected (for example, the disconnection of the heartbeat will occur when the old active node fails), it is determined that the old active node has failed and the active node needs to be switched (that is, a new active node needs to be activated).

[0137] The network management in the node device reads the node configuration file of the old active node to obtain the role of the old active node, and then according to its own node configuration file, obtains the role of the new active node (node device), and then writes the roles of the old and new active nodes into the network management role switching file (shared file).

[0138] The network management in the node device sends the network management role switching file to the conference management in the node device.

[0139] The conference management in the node device reads the network management role switching file and determines the activation type according to the roles of the old and new active nodes therein.

[0140] The conference management in the node device determines the delay waiting duration according to the activation type (2s for primary-backup switch, 30s for secondary-secondary switch, and 70s for secondary-primary switch).

[0141] During the delay waiting duration, the conference management in the node device waits for each participating terminal to connect to the network, and after the connection ends, waits for the successfully connected participating terminals to join the Visual Networking video conference and starts the Visual Networking video conference, thus completing the recovery of the interrupted Visual Networking service.

[0142] In this application, multiple node devices can be composed of multiple servers distributed in different regions. Among them, the primary node and the standby node form a dual-active hot standby with two servers, and multiple slave nodes (A / B / C / …) are added to form multi-point anti-destruction. At the same time, only one of the multiple node devices is an active node. When a certain active node is destroyed, the network management in the new active node will activate the new active node in the order of hot standby priority (for example: primary > standby > C > B > A > …). The meeting management in the new active node will determine the activation type according to the shared file sent by the network management and resume the meeting on the new active node. The databases on multiple servers are synchronized in real time to ensure data consistency among all nodes, facilitating the meeting management to restore the meeting service based on the data saved in the database. In this application, different delay waiting durations are set for different activation types, which can reduce the probability that the participating terminals cannot join the Visual Networking video conference due to not being connected to the network yet, and overall improve the restoration effect of the interrupted meeting service.

[0143] It should be noted that for the method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the embodiments of the present invention are not limited by the described action sequences, because according to the embodiments of the present invention, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily essential for the embodiments of the present invention.

[0144] Based on the same inventive concept, this application provides a meeting restoration device 400, which is applied to a target node in the Visual Networking. Figure 4 It is a structural block diagram of a meeting restoration device shown in an embodiment of this application. Refer to Figure 4 , the meeting restoration device 400 of this application may include:

[0145] A first determination module 401, configured to determine an activation type when it is necessary to activate the node device as an active node in the Visual Networking video conference. The activation type is determined according to the node type of the original active node in the Visual Networking video conference and the node type of the node device. The active node is the only node device that provides Visual Networking services in the Visual Networking.

[0146] A restoration module 402, configured to restore the Visual Networking video conference on the node device according to the meeting restoration policy corresponding to the activation type.

[0147] Optionally, the types of node devices in the Visual Networking include a primary node, a standby node, and a slave node; to determine the activation type, the first determination module 401 includes:

[0148] The first determination sub-module is used to determine that the activation type is master-backup switching when the original active node is the master node and the node device is the backup node, or when the original active node is the backup node and the node device is the master node;

[0149] The second determination sub-module is used to determine that the activation type is slave-slave switching when the original active node is the backup node and the node device is the slave node, or when the original active node and the node device are different slave nodes;

[0150] The third determination sub-module is used to determine that the activation type is slave-master switching when the original active node is the slave node and the node device is the master node, or when the original active node is the slave node and the node device is the backup node.

[0151] Optionally, the recovery module 402 includes:

[0152] The fourth determination sub-module is used to determine the delay waiting duration corresponding to the activation type;

[0153] The first activation sub-module is used to activate the Visual Networking video conference for the participating terminals that have joined the Visual Networking video conference when the delay waiting duration is reached.

[0154] Optionally, the recovery module 402 includes:

[0155] The second activation sub-module is used to activate the Visual Networking video conference when all participating terminals have joined the Visual Networking video conference.

[0156] Optionally, the fourth determination sub-module includes:

[0157] The fifth determination sub-module is used to determine that the delay waiting duration is the first duration when the activation type is master-backup switching, and the first duration includes the joining duration of the participating terminals;

[0158] The sixth determination sub-module is used to determine that the delay waiting duration is the second duration when the activation type is slave-slave switching, and the second duration includes the network access duration and the joining duration of the participating terminals;

[0159] The seventh determination sub-module is used to determine that the delay waiting duration is the third duration when the activation type is slave-master switching, and the third duration includes the detection duration, the network access duration of the participating terminals, and the joining duration, and the detection duration is used to detect whether the heartbeat connection between the master node and the backup node is disconnected.

[0160] Optionally, a first type of heartbeat connection is established between each node device in the Visual Networking; the apparatus 400 further includes:

[0161] A detection module, configured to detect whether a first type of heartbeat connection between the original activity node of the Visual Networking video conference and the node device is disconnected;

[0162] A second determination module, configured to determine that the node device needs to be activated as an activity node in the Visual Networking when the first type of heartbeat connection is disconnected.

[0163] Optionally, a second type of heartbeat connection is also maintained between the primary node and the standby node; the apparatus 400 further includes:

[0164] A first delay module, configured to, if the activation type is primary-standby switchover, wait for the participating terminal to join the Visual Networking video conference within the conference joining duration;

[0165] A second delay module, configured to, if the activation type is standby-standby switchover, wait for the participating terminal to access the network within the network access duration, and within the conference joining duration, wait for the participating terminal that has successfully accessed the network to join the Visual Networking video conference;

[0166] A third delay module, configured to, if the activation type is standby-primary switchover, detect within the detection duration whether the second type of heartbeat connection is disconnected, and if the second type of heartbeat connection is disconnected, wait for the participating terminal to access the network within the network access duration, and within the conference joining duration, wait for the participating terminal that has successfully accessed the network to join the Visual Networking video conference. Based on the same inventive concept, the present application provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the steps in the conference recovery method in any of the above embodiments of the present application are implemented.

[0167] For the apparatus embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for the relevant parts, reference may be made to the partial description of the method embodiment.

[0168] Each embodiment in this specification is described in a progressive manner, and the key point of each embodiment is to illustrate the differences from other embodiments. For the same or similar parts among the embodiments, reference may be made to each other.

[0169] Those skilled in the art should understand that the embodiments of the present invention can be provided as a method, an apparatus, or a computer program product. Therefore, the embodiments of the present invention can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the embodiments of the present invention can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memories, CD-ROMs, optical memories, etc.) containing computer-usable program codes.

[0170] Embodiments of the present invention are described with reference to the flowcharts and / or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, and the combination of 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 the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing terminal devices generate a device for implementing the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 or a device for implementing the functions specified in multiple blocks.

[0171] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including an instruction device, and the instruction device implements the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 or the functions specified in multiple blocks.

[0172] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device, such that a series of operation steps are executed on the computer or other programmable terminal device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable terminal device provide steps for implementing the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 or the functions specified in multiple blocks.

[0173] Finally, it should also be noted that in this document, relational terms such as first and second are only used 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 term "comprising", "including", or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or elements inherent to such process, method, article, or terminal device. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of additional identical elements in the process, method, article, or terminal device including the element.

[0174] The above has introduced in detail a conference recovery method, device, electronic device and storage medium provided by the present invention. Specific examples are used in this article to elaborate on the principle and implementation manner of the present invention. The description of the above embodiments is only used to help understand the method and its core idea of the present invention; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to the present invention.

Claims

1. A conference recovery method, characterized in that, it is applied to a node device in a Visual Networking (VN) network, and the method includes: In a VN video conference, when the node device needs to be activated as an active node in the VN network, determining an activation type, where the activation type is determined according to the node type of the original active node in the VN video conference and the node type of the node device, and the active node is the only node device providing VN services in the VN network; Recovering the VN video conference on the node device according to a conference recovery policy corresponding to the activation type; Recovering the VN video conference on the node device according to a conference recovery policy corresponding to the activation type includes: Determining a delay waiting duration corresponding to the activation type; When the delay waiting duration is reached, for the participating terminals that have joined the VN video conference, starting the VN video conference, where different delay waiting durations are set for each activation type according to the different durations required when the participating terminal exits the VN and then joins the VN video conference.

2. The method according to claim 1, characterized in that, the types of node devices in the VN network include a primary node, a standby node, and a slave node; Determining the activation type includes: When the original active node is a primary node and the node device is a standby node, or when the original active node is a standby node and the node device is a primary node, determining the activation type as primary-standby switch; When the original active node is a standby node and the node device is a slave node, or when the original active node and the node device are different slave nodes, determining the activation type as slave-slave switch; When the original active node is a slave node and the node device is a primary node, or when the original active node is a slave node and the node device is a standby node, determining the activation type as slave-primary switch.

3. The method according to any one of claims 1-2, characterized in that, recovering the VN video conference on the node device according to a conference recovery policy corresponding to the activation type includes: When all participating terminals have joined the VN video conference, starting the VN video conference.

4. The method according to claim 1, characterized in that, determining a delay waiting duration corresponding to the activation type includes: When the activation type is primary-standby switch, determining the delay waiting duration as a first duration, and the first duration includes the joining duration of the participating terminal; When the activation type is slave-slave switch, determining the delay waiting duration as a second duration, and the second duration includes the network access duration and the joining duration of the participating terminal; When the activation type is slave-primary switch, determining the delay waiting duration as a third duration, and the third duration includes a detection duration, the network access duration, and the joining duration of the participating terminal, and the detection duration is used to detect whether the heartbeat connection between the primary node and the standby node is disconnected.

5. The method according to claim 1, characterized in that, a first type of heartbeat connection is established between each node device in the VN network; the method further includes: Detect whether the first type of heartbeat connection with the original active node of the Visual Networking video conference is disconnected; When the first type of heartbeat connection is disconnected, determine that the node device needs to be activated as an active node in the Visual Networking.

6. The method according to claim 4, wherein, A second type of heartbeat connection is also maintained between the master node and the standby node; before the delay waiting duration is reached, the method further includes: If the activation type is master-standby switchover, wait for the participating terminal to join the Visual Networking video conference within the conference joining duration; If the activation type is slave-slave switchover, wait for the participating terminal to access the network within the network access duration, and within the conference joining duration, wait for the participating terminal that has successfully accessed the network to join the Visual Networking video conference; If the activation type is slave-master switchover, within the detection duration, detect whether the second type of heartbeat connection is disconnected. If the second type of heartbeat connection is disconnected, wait for the participating terminal to access the network within the network access duration, and within the conference joining duration, wait for the participating terminal that has successfully accessed the network to join the Visual Networking video conference.

7. A conference recovery device, wherein, Applied to a node device in the Visual Networking, the device includes: A first determination module, configured to determine an activation type when the node device needs to be activated as an active node in the Visual Networking during a Visual Networking video conference. The activation type is determined according to the node type of the original active node of the Visual Networking video conference and the node type of the node device. The active node is the only node device that provides Visual Networking services in the Visual Networking; A recovery module, configured to recover the Visual Networking video conference on the node device according to a conference recovery policy corresponding to the activation type; The recovery module includes: A fourth determination sub-module, configured to determine a delay waiting duration corresponding to the activation type; A first start sub-module, configured to, when the delay waiting duration is reached, start the Visual Networking video conference for the participating terminals that have joined the Visual Networking video conference. Among them, different delay waiting durations are set for each activation type according to the different durations required for the participating terminal to exit the Visual Networking and then join the Visual Networking video conference.

8. A computer-readable storage medium, on which a computer program is stored, wherein, When the program is executed by a processor, it implements the steps in the conference recovery method according to any one of claims 1-6.

9. An electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein, When the processor executes, it implements the steps in the conference recovery method according to any one of claims 1-6.

Images