CN111447393B - Conference maintenance method, conference maintenance device and readable storage medium - Google Patents

Conference maintenance method, conference maintenance device and readable storage medium Download PDF

Info

Publication number
CN111447393B
CN111447393B CN202010144598.7A CN202010144598A CN111447393B CN 111447393 B CN111447393 B CN 111447393B CN 202010144598 A CN202010144598 A CN 202010144598A CN 111447393 B CN111447393 B CN 111447393B
Authority
CN
China
Prior art keywords
terminal equipment
target
terminal device
abnormal
conference
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202010144598.7A
Other languages
Chinese (zh)
Other versions
CN111447393A (en
Inventor
贺传森
王晓燕
亓娜
王艳辉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Visionvera Information Technology Co Ltd
Original Assignee
Visionvera Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Visionvera Information Technology Co Ltd filed Critical Visionvera Information Technology Co Ltd
Priority to CN202010144598.7A priority Critical patent/CN111447393B/en
Publication of CN111447393A publication Critical patent/CN111447393A/en
Application granted granted Critical
Publication of CN111447393B publication Critical patent/CN111447393B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00Television systems
    • H04N7/14Systems for two-way working
    • H04N7/15Conference systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/442Monitoring of processes or resources, e.g. detecting the failure of a recording device, monitoring the downstream bandwidth, the number of times a movie has been viewed, the storage space available from the internal hard disk
    • H04N21/4425Monitoring of client processing errors or hardware failure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/643Communication protocols
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Abstract

The embodiment of the invention provides a conference maintenance method, a conference maintenance device and a readable storage medium. The conference maintenance method of the invention comprises the following steps: obtaining abnormal information of a first abnormal terminal device in a target conference, determining a first target terminal device corresponding to the first abnormal terminal device, wherein the first abnormal terminal device and the first target terminal device correspond to the same sub-control server, judging whether the first target terminal device is in a normal state, if the first target terminal device is in the normal state, replacing the first abnormal terminal device by the first target terminal device, controlling the first target terminal device to join the target conference, and controlling the first target terminal device to establish a data link. Therefore, when the abnormal terminal equipment exists, the normal terminal equipment corresponding to the abnormal terminal equipment can be used for replacing the abnormal terminal equipment to be added into the conference, so that the normal operation of the conference is ensured.

Description

Conference maintenance method, conference maintenance device and readable storage medium
Technical Field
The present invention relates to the field of communications, and in particular, to a conference maintenance method, apparatus, and readable storage medium.
Background
The video networking is an important milestone for network development, is a higher-level form of the Internet, is a real-time network, can realize real-time transmission of full-network high-definition videos which cannot be realized by the Internet at present, and pushes numerous Internet applications to high-definition videos.
Currently, a user can perform a video networking conference through a plurality of terminal devices from at least one sub-control device, however, when the terminal devices are abnormal (such as the terminal devices are off the network, do not receive data packets, have serious packet loss and the like), the conference is interrupted, and a technician is required to check the problem of the conference interruption and then restart the conference, so that the conference quality and conference efficiency are affected.
Disclosure of Invention
The embodiment of the invention provides a conference maintenance method, a conference maintenance device and a readable storage medium, which are used for solving the problem that conference interruption is caused when terminal equipment is abnormal in a conference, so that conference quality and conference efficiency are affected.
In a first aspect of the embodiment of the present invention, a conference maintenance method is provided, which is executed in a master control server, and includes:
acquiring abnormal information of a first abnormal terminal device in a target conference;
determining a first target terminal device corresponding to the first abnormal terminal device, wherein the first abnormal terminal device and the first target terminal device correspond to the same sub-control server;
Judging whether the first target terminal equipment is in a normal state or not;
and if the first target terminal equipment is in a normal state, replacing the first abnormal terminal equipment by the first target terminal equipment, controlling the first target terminal equipment to join the target conference, and controlling the first target terminal equipment to establish a data link.
In a second aspect of the embodiment of the present invention, there is provided a conference maintenance device, provided at a main control server, including:
the acquisition module is used for acquiring the abnormal information of the first abnormal terminal equipment in the target conference;
the determining module is used for determining first target terminal equipment corresponding to the first abnormal terminal equipment, wherein the first abnormal terminal equipment and the first target terminal equipment correspond to the same sub-control server;
the judging module is used for judging whether the first target terminal equipment is in a normal state or not;
and the replacing module is used for replacing the first abnormal terminal equipment by the first target terminal equipment if the first target terminal equipment is in a normal state, controlling the first target terminal equipment to join the target conference and controlling the first target terminal equipment to establish a data link.
In a third aspect of the embodiments of the present invention, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the conference maintenance method described above.
In a fourth aspect of the present invention, there is provided a conference maintenance device comprising a processor, a memory and a computer program stored on the memory and executable on the processor, the computer program implementing the steps of the conference maintenance method described above when executed by the processor.
Aiming at the prior art, the invention has the following advantages:
according to the conference maintenance method provided by the embodiment of the invention, the first target terminal equipment corresponding to the first abnormal terminal equipment is determined by acquiring the abnormal information of the first abnormal terminal equipment in the target conference, wherein the first abnormal terminal equipment and the first target terminal equipment correspond to the same sub-control server, whether the first target terminal equipment is in a normal state is judged, if the first target terminal equipment is in the normal state, the first target terminal equipment is adopted to replace the first abnormal terminal equipment, the first target terminal equipment is controlled to join the target conference, and the first target terminal equipment is controlled to establish a data link. Therefore, when the abnormal terminal equipment exists, the normal terminal equipment corresponding to the abnormal terminal equipment can be used for replacing the abnormal terminal equipment to be added into the conference, so that the normal operation of the conference is ensured.
The foregoing description is only an overview of the present invention, and is intended to be implemented in accordance with the teachings of the present invention in order that the same may be more clearly understood and to make the same and other objects, features and advantages of the present invention more readily apparent.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to designate like parts throughout the figures. In the drawings:
fig. 1 is a system architecture diagram of a conference maintenance method according to an embodiment of the present invention;
fig. 2 is a flowchart of steps of a conference maintenance method according to an embodiment of the present invention;
fig. 3 is a signaling flow chart of a conference maintenance method according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a conference maintenance device according to an embodiment of the present invention;
FIG. 5 is a networking schematic of the present invention for a video networking;
FIG. 6 is a schematic diagram of a hardware architecture of a node server according to the present invention;
Fig. 7 is a schematic diagram of a hardware architecture of an access switch according to the present invention;
fig. 8 is a schematic hardware structure of an ethernet corotating gateway according to the present invention.
Detailed Description
In order that the above-recited objects, features and advantages of the present invention will become more readily apparent, a more particular description of the invention will be rendered by reference to the appended drawings and appended detailed description.
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
Referring to fig. 1, fig. 1 is a system architecture diagram of a conference maintenance method according to an embodiment of the present invention. The system takes a conference management client (the conference management client is a conference management system) as an example, and comprises a master control server, a sub control server 1, a sub control server 2, a sub control server 3, a terminal device 1, a terminal device 2, a terminal device 3, a terminal device 4 and a terminal device 5. The sub-control servers corresponding to the terminal equipment 1 and the terminal equipment 2 are sub-control servers 1, the sub-control servers corresponding to the terminal equipment 3 and the terminal equipment 4 are sub-control servers 2, and the sub-control servers corresponding to the terminal equipment 5 are sub-control servers 3. Terminal device 1 is a master terminal device, terminal device 2 is a slave terminal device corresponding to terminal device 1, terminal device 3 is a master terminal device, and terminal device 4 is a slave terminal device corresponding to terminal device 3. It should be noted that whether to set the slave terminal device for the terminal device and the number of the set slave terminal devices may be determined according to actual meeting requirements.
Based on fig. 1, if the terminal device 1 and the terminal device 3 are terminal devices in the same conference, if the conference is in progress, for example, if the terminal device 1 is abnormal, the network is disconnected, or the like, resulting in a break in the conference, the master server may control the terminal device 2 to join the conference, instead of the terminal device 1, to continue the conference. Or when the terminal equipment 1 participates in the conference, if the terminal equipment 1 is abnormal and the terminal equipment 2 enters the normal state again at the moment, the terminal equipment 2 can be adopted to replace the terminal equipment 1 to continue the conference, so that the normal conference can be ensured when the terminal equipment is abnormal.
Based on fig. 1, an embodiment of the present invention provides a data maintenance method. Referring to fig. 2, fig. 2 is a flowchart illustrating steps of a conference maintenance method according to an embodiment of the present invention, where the method may be executed by a master server, and the method of the embodiment includes the following steps:
step 201, obtaining abnormal information of a first abnormal terminal device in a target conference.
For example, referring to fig. 1, in the target conference, when a terminal device 1 of a participant in the target conference is abnormal (for example, an audio/video data packet received by the terminal device 1 is severely lost, or the terminal device 1 does not receive an audio/video data packet), the terminal device 1 sends abnormal information to a sub-control server 1, the sub-control server sends the abnormal information to a main control server, that is, the main control server obtains the abnormal information of the terminal device 1, and the terminal device 1 is the first abnormal terminal device. Or, if the network between the terminal device 1 and the sub-control server 1 is abnormal or the terminal device 1 fails, and the sub-control server 1 cannot receive the heartbeat message of the terminal device 1 in a preset time period, the sub-control server 1 can determine that the terminal device 1 is abnormal, and the sub-control server 1 can send the abnormal information of the terminal device 1 to the main control server. The anomaly information includes, for example, information such as a meeting identifier of the target meeting, a cause of the anomaly (e.g., a logout for the terminal device 1, and a heartbeat message of the terminal device 1 is not received by the sub-control server 1 within a preset period of time), and the like.
Step 202, determining a first target terminal device corresponding to the first abnormal terminal device, wherein the first abnormal terminal device and the first target terminal device correspond to the same sub-control server.
It should be noted that, the master control server may store a terminal device corresponding to the terminal device. For example, the master control server stores slave terminal equipment corresponding to the terminal equipment 1 as terminal equipment 2, and master terminal equipment corresponding to the terminal equipment 2 as terminal equipment 1; the slave terminal device corresponding to the terminal device 3 is the terminal device 4, and the master terminal device corresponding to the terminal device 4 is the terminal device 3. That is, the master server stores the correspondence between the master terminal device and the slave terminal device, so that in the case that the first abnormal terminal device has a corresponding terminal device, the master server can determine the first target terminal device corresponding to the first abnormal terminal device according to the correspondence between the master terminal device and the slave terminal device. For example, in the case where the first abnormal terminal device is the terminal device 1, the terminal device 2 is the first target terminal device.
Step 203, judging whether the first target terminal equipment is in a normal state.
And 204, if the first target terminal equipment is in a normal state, replacing the first abnormal terminal equipment by the first target terminal equipment, controlling the first target terminal equipment to join the target conference, and controlling the first target terminal equipment to establish a data link.
It should be noted that if the first abnormal terminal device is the speaking party, the first target terminal device is controlled to establish a data link with other participant terminal devices except the first target terminal device in the target conference; and if the first abnormal terminal equipment is not the speaking party, controlling the first target terminal equipment to establish a data link with the speaking terminal equipment in the target conference. For example, if the terminal device 1 is the speaking party and the terminal device 2 is used to replace the terminal device 1, the master control server controls the first target terminal device to establish a data link with other terminal devices, and after the data link is established successfully, the master control server obtains the audio and video data of the terminal device 2 and distributes the audio and video data to other reference terminal devices in the target conference. If the terminal device 1 is not the speaking party, the control terminal device 1 establishes a data link with the speaking terminal device in the target conference, and after the data link is established successfully, the main control server acquires the audio and video data of the speaking terminal device and sends the audio and video data to the terminal device 2. Thereby ensuring normal meeting.
According to the method provided by the embodiment, the first target terminal equipment corresponding to the first abnormal terminal equipment is determined by acquiring the abnormal information of the first abnormal terminal equipment in the target conference, wherein the first abnormal terminal equipment and the first target terminal equipment correspond to the same sub-control server, whether the first target terminal equipment is in a normal state is judged, if the first target terminal equipment is in the normal state, the first target terminal equipment is adopted to replace the first abnormal terminal equipment, the first target terminal equipment is controlled to join the target conference, and the first target terminal equipment is controlled to establish a data link. Therefore, when the abnormal terminal equipment exists, the normal terminal equipment corresponding to the abnormal terminal equipment can be used for replacing the abnormal terminal equipment to be added into the conference, so that the normal operation of the conference is ensured.
Referring to fig. 3, fig. 3 is a signaling flow chart of a conference maintenance method according to an embodiment of the present invention, where the method includes the following steps:
step 301, a master control server receives a master-slave setting instruction sent by a session management client, wherein the master-slave setting instruction comprises a master terminal device identifier and a slave terminal device identifier.
It should be noted that, the session client may be connected to the master server through a transmission control protocol (TCP, transmission Control Protocol) socket communication, and then the session client may send a master-slave setting instruction to the master server.
Step 302, the master control server responds to the master-slave setting instruction, sets the terminal equipment corresponding to the master terminal equipment identifier in the registration file as master terminal equipment, sets the terminal equipment corresponding to the slave terminal equipment identifier in the registration file as slave terminal equipment, and establishes a master-slave corresponding relationship between the master terminal equipment and the slave terminal equipment to obtain a target registration file.
For step 301 and step 302, after the session management client is connected to the master control server through tcp socket communication, the master control server may receive a master-slave setting instruction sent by the session management client, where the master-slave setting instruction may be used for the master control server to set a master-slave correspondence relationship between terminal devices in the target session. For example, referring to fig. 1, if the master-slave setting instruction includes an identifier 1 of the terminal device 1 and an identifier 2 of the terminal device 2, the identifier 1 is a master terminal device identifier, and the identifier 2 is a slave terminal device identifier. The master control server sets the terminal device 1 in the registration file as a master terminal device, sets the terminal device 2 as a slave terminal device, and establishes a master-slave correspondence between the terminal device 1 and the terminal device 2, that is, the slave terminal device of the terminal device 1 is the terminal device 2, and the master terminal device of the terminal device 2 is the terminal device 1, so as to obtain the target registration file.
After step 302 is performed, that is, the master server has successfully set the master-slave correspondence between the terminal devices, a target registration file is obtained, and step 304 may be performed. I.e. step 304 is performed without waiting for step 303 to complete.
Step 303, the master control server determines a target sub control server corresponding to the master terminal device and the slave terminal device according to the corresponding relation between the terminal device and the sub control server in the target registration file, so as to send a first notification message to the master terminal device and a second notification message to the slave terminal device through the target sub control server.
The first notification message is used for notifying that the device corresponding to the master terminal device is the slave terminal device, and the second notification message is used for notifying that the device corresponding to the slave terminal device is the master terminal device.
Correspondingly, after receiving the first notification message, the master terminal device records that the device corresponding to the master terminal device is the slave terminal device. After receiving the second notification message, the slave terminal equipment records the equipment corresponding to the slave terminal equipment as the master terminal equipment. After the master terminal equipment records that the corresponding equipment is the slave terminal equipment, if the master terminal equipment initiates the video telephone service or issues services such as live broadcast service and the like, if the terminal equipment fails, the master terminal equipment can be switched to the slave terminal equipment to continue the services. Similarly, after the slave terminal device records the corresponding device as the master terminal device, the slave terminal device may also switch to the master terminal device when performing the video telephone service or issuing the live broadcast service.
Step 304, the master control server sends a successful setting result to the session client.
Accordingly, the session client receives the successful setting result sent by the master server, that is, the session client may determine, according to the successful setting result, that the master server has set, for example, the terminal device 1 as a master terminal device and the terminal device 2 as a slave terminal device. If the master-slave setting instruction in step 302 further includes the identifier 3 of the terminal device 3 and the identifier 4 of the terminal device 4, where the identifier 3 is a master terminal device identifier and the identifier 4 is a slave terminal device identifier, the master control server will also set the terminal device 3 as a master terminal device, and the terminal device 4 is a slave terminal device identifier, and establishes a master-slave correspondence relationship between the terminal device 3 and the terminal device 4.
Step 305, the master control server receives a meeting starting instruction sent by the meeting management client, wherein the meeting starting instruction comprises a meeting identifier of the target meeting and information of all terminal devices in the target meeting.
After receiving the successful setting result, the session management client can send a session starting instruction to the main control server, and correspondingly, the main control server receives the session starting instruction sent by the session management client.
The information of all the terminal devices can include information such as identification of the terminal device, type of the terminal device, conference video decoding mode and the like. The instruction to start the conference may further include a first conference identifier and a second conference identifier of the target conference, where the first conference identifier is used to identify a conference in one of the master servers, the second conference identifier is a global conference identifier, and the second conference identifier is a unique conference identifier in the video network.
And 306, if the second abnormal terminal equipment exists in all the terminal equipment, judging whether second target terminal equipment corresponding to the second abnormal terminal equipment exists or not by the main control server according to the target registration file.
After receiving the instruction to start the conference, the master control server may determine whether there are abnormal terminal devices in all the terminal devices (determine whether there are abnormal terminal devices that are not connected to the network or are unregistered or disabled, etc. in all the terminal devices). Because the target sub-control server can determine the network access state of all the terminal devices, for example, the sub-control server determines that a certain terminal device is not accessed to the network, the terminal device is determined to be an abnormal terminal device (namely, a second abnormal terminal device), the sub-control server reports the abnormal terminal device to the main control server, and the main control server can determine that the second abnormal terminal device exists. If the master control server determines that the second abnormal terminal device corresponds to the second target terminal device according to the target registration file, whether the second target terminal device is normal or not can be judged. If there is a second target terminal device and the second target terminal device is in a normal state, step 307 is performed. If there is no second target terminal device corresponding to the second abnormal terminal device or the second target terminal device is in an abnormal state, step 309 is performed.
If the second abnormal terminal device does not exist in all the terminal devices, the main control server sends a meeting notification to the sub control server, and the sub control server sends a meeting notification to the terminal device corresponding to the sub control server, for example, as shown in fig. 1, if all the terminal devices include the terminal device 1 and the terminal device 3, the main control server sends a meeting notification to the sub control server 1 and the sub control server 2. The sub-control server 1 sends a conference joining notification to the terminal device 1 to notify the terminal device 1 of joining in the target conference; the sub-control server 2 transmits a conference notification to the terminal device 3 to notify the terminal device 3 of joining to the target conference.
Step 307, the master control server replaces the second abnormal terminal device with the second target terminal device, controls the second target terminal device to join the target conference, and controls the second target terminal device to establish a data link.
For example, if all the terminal devices in step 305 include terminal device 1 and terminal device 3, where terminal device 1 is the second abnormal terminal device and terminal device 2 is normal, then terminal device 2 is used to replace terminal device 1 to join the target conference, host the server and establish a data link with terminal device 2. If the terminal device 1 is an speaking terminal, the terminal device 2 (the terminal device 2 is a second target terminal) is adopted as the speaking terminal, and the audio/video data of the terminal device 2 is sent to other terminal devices except the terminal device 2 in the target conference.
In step 308, the master control server sends a first conference notification message to the conference management client, where the first conference notification message is used to instruct the second target terminal device to successfully participate in the target conference.
It should be noted that, the first conference notification message may include a first conference identifier, a second conference identifier, an identifier of the second target terminal device, and a state of the second target terminal device, where the state of the second target terminal is in the conference.
Step 309, the master control server sends a second conference notification message to the conference client, where the second conference notification message is used to notify the conference client of an abnormal reason of the second abnormal terminal device.
The second conference notification message may include the first conference identifier, the second conference identifier, the identifier of the second target terminal device, and the state of the second abnormal terminal device, where the state of the second abnormal terminal device is, for example, a state of not being connected to the network, not being registered, or being disabled.
It should be noted that, during the conference, if the second target terminal device (for example, the terminal device 2) is abnormal, for example, the sub-control server does not receive the heartbeat message of the terminal device 2 within a specified period of time, the sub-control server may send the abnormal information of the terminal device 2 to the main control server, and correspondingly, the main control server receives the abnormal information of the terminal device 2 sent by the sub-control server. Or, in the conference, the serious packet loss problem occurs in the data packet received by the terminal device 2, the terminal device 2 sends the abnormal information (the abnormal information is packet loss serious) to the sub-control server 1, and correspondingly, the sub-control server receives the abnormal information sent by the terminal device 2 (that is, the sub-control server receives the abnormal information sent by the first abnormal terminal device, and the terminal device 2 is the first abnormal terminal device), and then sends the received abnormal information to the main control server. Therefore, in combination with the above analysis, the sub-control server 1 may send the abnormality information of the terminal device 2 to the main control server, that is, the main control server may obtain the abnormality information of the terminal device 2, that is, perform step 310.
Step 310, the main control server obtains the abnormal information of the first abnormal terminal device in the target conference.
Step 311, the master control server determines a first target terminal device corresponding to the first abnormal terminal device.
For example, referring to fig. 1, if the information of the terminal device 1 is included in the instruction to start the conference in step 305, but the terminal device 1 is the second abnormal terminal device, in this case, and it is determined that the terminal device 2 is normal, the terminal device 2 is joined to the target conference. If an abnormality occurs in the terminal device 2 during the conference, the main control server determines that the main terminal device corresponding to the first abnormal terminal device (terminal device 2) is the first target terminal device (terminal device 1). If the terminal device 1 is in a normal state at this time, the main control server may replace the terminal device 2 with the terminal device 1.
Or, for example, if the information of the terminal device 1 is included in the instruction to start the conference in step 305 and the terminal device 1 is not the second abnormal terminal device, in this case, the terminal device 1 joins the target conference, and if an abnormality occurs in the terminal device 1 during the conference (i.e., the terminal device 1 is the first abnormal terminal device) and the corresponding slave terminal device (terminal device 2) of the terminal device 1 is normal, step 313 may be performed, that is, the terminal device 2 is replaced with the terminal device 2, and the terminal device 2 is controlled to join the target conference and establish a data link with the terminal device 2.
Step 312, determining whether the first target terminal device is in a normal state.
If the first target terminal equipment is in a normal state, the first target terminal equipment is adopted to replace the first abnormal terminal equipment, the first target terminal equipment is controlled to join in the target conference, and a data link is established with the first target terminal equipment.
The method comprises the following steps of adopting a first target terminal device to replace a first abnormal terminal device and controlling the first target terminal device to join a target conference:
step 313, the master control server sends a meeting instruction to the target sub control server.
After receiving the meeting instruction, the target sub-control server sends the meeting instruction to the first target terminal equipment, and the first target terminal equipment responds to the meeting instruction and joins the target meeting. It should be noted that, after the first target terminal device joins the target conference, the target sub-control server may receive the conference joining result sent by the first target terminal device, and then execute step 314.
And step 314, the target sub-control server sends the conference result to the main control server, so that the main control server controls the first target terminal to establish a data link according to the conference result.
Note that if the information of the terminal device 5 is included in the instruction to start the conference in step 305, but the terminal device 5 is not the second abnormal terminal device, in this case, the terminal device 5 is added to the target conference. If the terminal device 5 is abnormal during the conference (i.e. the terminal device 5 is the first abnormal device), the master control server may obtain the abnormal information of the terminal device 5 in step 310, and the master control server may obtain the abnormal information of the terminal device 5 by receiving the abnormal information of the terminal device 5 sent by the sub control server. Since the terminal device 5 does not have a corresponding slave terminal device, the master control server may report the abnormality information of the terminal device 5 to the session client under the condition that the terminal device 5 is abnormal. The anomaly information of the terminal device 5 may include a first conference identifier, a second conference identifier, an identifier of the terminal device 5, and a specific anomaly cause of the terminal device 5 (for example, a serious packet loss phenomenon occurs in a data packet received by the terminal device 5, or the terminal device 5 does not receive the data packet, etc.).
If the information of the terminal device 1 is included in the instruction to start the conference in step 305 and the terminal device 1 is not the second abnormal terminal device, the terminal device 1 joins the target conference in this case. If an abnormality occurs in the terminal device 1 during the conference (i.e., the terminal device 1 is a first abnormal terminal device), and the slave terminal device (terminal device 2) corresponding to the terminal device 1 is abnormal, the master server may report the abnormality information of the terminal device 1 to the conference client, where the abnormality information may include a first conference identifier, a second conference identifier, an identifier of the terminal device 1, a specific abnormality cause of the terminal device 1, and the replacement information is null.
If an abnormality occurs in the terminal device 1 during the conference, and the slave terminal device (terminal device 2) corresponding to the terminal device 1 is normal, the terminal device 2 is adopted to replace the terminal device 1, the master server may report abnormality information of the terminal device 1 to the conference client, where the abnormality information may include a first conference identifier, a second conference identifier, an identifier of the terminal device 1, a specific abnormality cause of the terminal device 1, and replacement information, and the replacement information includes, for example, identifier information of the replaced terminal device and information of the replaced terminal device (for example, information of the terminal device 2).
If during the conference, the terminal device 1 is abnormal, and the slave terminal device (terminal device 2) corresponding to the terminal device 1 is normal, and after a period of time has elapsed after the terminal device 1 is replaced by the terminal device 2, the terminal device 2 is abnormal, and at this time, the abnormality information sent by the master control server to the conference client may include a first conference identifier, a second conference identifier, an identifier of the terminal device 2, a specific abnormality reason of the terminal device 2, an identifier of the terminal device 1, a specific abnormality reason of the terminal device 1, and replacement information of the terminal device 1 is null.
After the main control server sends the abnormal information of the terminal equipment to the meeting management client, the user can find the problem in time conveniently, so that the problem can be solved quickly, and the meeting is guaranteed to be carried out smoothly to a certain extent.
Receiving a notification message sent by the main control server, wherein the notification message comprises identification information of first target terminal equipment corresponding to the first abnormal terminal equipment;
and responding to the notification message, sending a meeting entering instruction to the first target terminal equipment so as to enable the first target terminal equipment to be added into the target meeting.
Referring to fig. 4, fig. 4 is a schematic structural diagram of a conference maintenance device according to an embodiment of the present invention, where the device 400 is disposed on a master server, and includes:
an acquiring module 410, configured to acquire anomaly information of a first anomaly terminal device in a target conference;
a first determining module 420, configured to determine a first target terminal device corresponding to the first abnormal terminal device, where the first abnormal terminal device and the first target terminal device correspond to the same sub-control server;
a first judging module 430, configured to judge whether the first target terminal device is in a normal state;
and a replacing module 440, configured to replace the first abnormal terminal device with the first target terminal device if the first target terminal device is in a normal state, and control the first target terminal device to join the target conference, and control the first target terminal device to establish a data link.
The conference maintenance device provided by the embodiment determines a first target terminal device corresponding to a first abnormal terminal device by acquiring the abnormal information of the first abnormal terminal device in the target conference, wherein the first abnormal terminal device and the first target terminal device correspond to the same sub-control server, judges whether the first target terminal device is in a normal state, and if the first target terminal device is in the normal state, adopts the first target terminal device to replace the first abnormal terminal device, controls the first target terminal device to join the target conference, and controls the first target terminal device to establish a data link. Therefore, when the abnormal terminal equipment exists, the normal terminal equipment corresponding to the abnormal terminal equipment can be used for replacing the abnormal terminal equipment to be added into the conference, so that the normal operation of the conference is ensured.
Optionally, the method further comprises:
the first receiving module is used for receiving a master-slave setting instruction sent by the session management client, wherein the master-slave setting instruction comprises a master terminal equipment identifier and a slave terminal equipment identifier;
the setting module is used for responding to the master-slave setting instruction, setting terminal equipment corresponding to the master terminal equipment identifier in the registration file as master terminal equipment, setting terminal equipment corresponding to the slave terminal equipment identifier in the registration file as slave terminal equipment, and establishing a corresponding relation between the master terminal equipment and the slave terminal equipment so as to obtain a target registration file.
Optionally, the method further comprises:
and the second determining module is used for determining a target sub-control server corresponding to the master terminal device and the slave terminal device according to the corresponding relation between the terminal device and the sub-control server in the target registration file, so as to send a first notification message to the master terminal device and send a second notification message to the slave terminal device through the target sub-control server, wherein the first notification message is used for notifying that the device corresponding to the master terminal device is the slave terminal device, and the second notification message is used for notifying that the device corresponding to the slave terminal device is the master terminal device.
Optionally, the method further comprises:
the second receiving module is used for receiving a meeting starting instruction sent by the meeting management client, wherein the meeting starting instruction comprises a meeting identifier of the target meeting and information of all terminal devices in the target meeting;
the second judging module is used for judging whether second target terminal equipment corresponding to the second abnormal terminal equipment exists or not according to the target registration file if the second abnormal terminal equipment exists in all the terminal equipment;
the replacing module 440 is further configured to, if the second target terminal device exists and the second target terminal device is in a normal state, replace the second abnormal terminal device with the second target terminal device, control the second target terminal device to join the target conference, and control the second target terminal device to establish a data link;
The sending module is used for sending a first meeting notification message to the meeting management client, wherein the first meeting notification message is used for indicating that the second target terminal equipment successfully participates in the target meeting.
Optionally, the sending module is further configured to send a second meeting notification message to the meeting management client if there is no second target terminal device corresponding to the second abnormal terminal device or the second target terminal device is in an abnormal state, where the second meeting notification message is used to notify the meeting management client of an abnormality cause of the second abnormal terminal device.
Optionally, the sending module is further configured to send, if there is no first target terminal device corresponding to the first abnormal terminal device, or the first target terminal device is in an abnormal state, abnormal information of the first abnormal terminal device to the session client.
In addition, the embodiment of the invention also provides a conference maintenance device, which comprises a processor, a memory and a computer program stored in the memory and capable of running on the processor, wherein the computer program realizes the processes of the conference maintenance method embodiment of the embodiment when being executed by the processor, and can achieve the same technical effects, and the repetition is avoided, so that the description is omitted.
The embodiment of the invention also provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the processes of the above-mentioned conference maintenance method embodiment, and can achieve the same technical effects, so that repetition is avoided, and no further description is provided herein. The computer readable storage medium may be a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, an optical disk, or the like.
The embodiment of the invention also provides a computer program which can be stored on a cloud or local storage medium. Which when executed by a computer or processor is adapted to carry out the respective steps of the conference maintenance method of an embodiment of the invention and to carry out the respective modules in the conference maintenance device according to an embodiment of the invention.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described by differences from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other.
As will be readily appreciated by those skilled in the art: any combination of the above embodiments is possible, and thus is an embodiment of the present invention, but the present specification is not limited by the text.
The conference maintenance methods provided herein are not inherently related to any particular computer, virtual system, or other apparatus. Various general-purpose systems may also be used with the teachings herein. The required structure for a system constructed with aspects of the present invention will be apparent from the description above. In addition, the present invention is not directed to any particular programming language. It will be appreciated that the teachings of the present invention described herein may be implemented in a variety of programming languages, and the above description of specific languages is provided for disclosure of enablement and best mode of the present invention.
In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be construed as reflecting the intention that: i.e., the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the apparatus of the embodiments may be adaptively changed and disposed in one or more apparatuses different from the embodiments. The modules or units or components of the embodiments may be combined into one module or unit or component and, furthermore, they may be divided into a plurality of sub-modules or sub-units or sub-components. Any combination of all features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or units of any method or apparatus so disclosed, may be used in combination, except insofar as at least some of such features and/or processes or units are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings), may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features but not others included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the claims, any of the claimed embodiments may be used in any combination.
Various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that some or all of the functions of some or all of the components in the conference maintenance method according to embodiments of the present invention may be implemented in practice using a microprocessor or Digital Signal Processor (DSP). The present invention can also be implemented as an apparatus or device program (e.g., a computer program and a computer program product) for performing a portion or all of the methods described herein. Such a program embodying the present invention may be stored on a computer readable medium, or may have the form of one or more signals. Such signals may be downloaded from an internet website, provided on a carrier signal, or provided in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, third, etc. do not denote any order. These words may be interpreted as names.
For a better understanding of embodiments of the present invention, the following description of the video networking is presented to one skilled in the art:
the partial techniques applied by the video networking are as follows:
network technology (Network Technology)
The network technology innovation of the internet of vision improves on the traditional Ethernet (Ethernet) to face the potentially huge video traffic on the network. Unlike pure network Packet Switching (Packet Switching) or network circuit Switching (Circuit Switching), the technology of video networking employs Packet Switching to meet Streaming requirements. The video networking technology has the flexibility, simplicity and low price of packet switching, and simultaneously has the quality and the safety guarantee of circuit switching, thereby realizing the seamless connection of the whole network switching type virtual circuit and the data format.
Exchange technology (Switching Technology)
The video network adopts the two advantages of the asynchronization and the packet switching of the Ethernet, eliminates the Ethernet defect on the premise of full compatibility, has full-network end-to-end seamless connection, and is directly connected with the user terminal to directly bear the IP data packet. The user data does not need any format conversion in the whole network. The video networking is a higher-level form of Ethernet, is a real-time exchange platform, can realize real-time transmission of full-network large-scale high-definition video which cannot be realized by the current Internet, and pushes numerous network video applications to high definition and unification.
Server technology (Server Technology)
The server technology on the video networking and unified video platform is different from the server in the traditional sense, the streaming media transmission is based on connection-oriented basis, the data processing capability is irrelevant to the flow and the communication time, and a single network layer can contain signaling and data transmission. For voice and video services, the complexity of video networking and unified video platform streaming media processing is much simpler than that of data processing, and the efficiency is greatly improved by more than hundred times than that of a traditional server.
Accumulator technology (Storage Technology)
The ultra-high-speed storage technology of the unified video platform adopts the most advanced real-time operating system for adapting to the ultra-large capacity and ultra-large flow media content, the program information in the server instruction is mapped to a specific hard disk space, the media content does not pass through the server any more, the media content is instantly and directly delivered to a user terminal, and the waiting time of the user is generally less than 0.2 seconds. The optimized sector distribution greatly reduces the mechanical motion of magnetic head seek of the hard disk, the resource consumption only accounts for 20% of the IP Internet of the same grade, but the concurrent flow which is 3 times greater than that of the traditional hard disk array is generated, and the comprehensive efficiency is improved by more than 10 times.
Network security technology (Network Security Technology)
The structural design of the video networking thoroughly structurally solves the network security problem puzzling the Internet by means of independent permission of each service, complete isolation of equipment and user data and the like, generally does not need antivirus programs or firewalls, eliminates attacks of hackers and viruses, and provides a structural carefree security network for users.
Service innovation technology (Service Innovation Technology)
The unified video platform fuses services with transmissions, whether a single user, private network users or a network aggregate, but automatically connects at a time. The user terminal, the set top box or the PC is directly connected to the unified video platform, so that various multimedia video services are obtained. The unified video platform adopts a menu type table allocation mode to replace the traditional complex application programming, and can realize complex application by using very few codes, thereby realizing 'infinite' new business innovation.
Networking of the video networking is as follows:
the video networking is a centrally controlled network structure, which may be of the tree network, star network, ring network, etc., but on the basis of this there is a need for a centralized control node in the network to control the whole network.
As shown in fig. 5, the view network is divided into an access network and a metropolitan area network.
The devices of the access network part can be mainly divided into 3 classes: node server, access switch, terminal (including various set-top boxes, code boards, memories, etc.). The node server is connected with an access switch, which can be connected with a plurality of terminals and can be connected with an Ethernet.
The node server is a node with a centralized control function in the access network, and can control the access switch and the terminal. The node server may be directly connected to the access switch or may be directly connected to the terminal.
Similarly, devices of the metropolitan area network portion can also be classified into 3 categories: metropolitan area server, node switch, node server. The metro server is connected to a node switch, which may be connected to a plurality of node servers.
The node server is the node server of the access network part, namely the node server belongs to the access network part and also belongs to the metropolitan area network part.
The metropolitan area server is a node with centralized control function in the metropolitan area network, and can control a node switch and a node server. The metropolitan area server may be directly connected to the node switch or directly connected to the node server.
Thus, the whole video network is a hierarchical centralized control network structure, and the network controlled by the node server and the metropolitan area server can be in various structures such as tree, star, ring and the like.
The access network part can be vividly called as a unified video platform (part in a dotted circle), and a plurality of unified video platforms can form a video network; each unified video platform can be interconnected and intercommunicated through metropolitan area and wide area video networking.
View networking device classification
1.1 devices in the visual network according to the embodiment of the present invention may be mainly classified into 3 types: a server, a switch (including an ethernet gateway), a terminal (including various set-top boxes, a code board, a memory, etc.). The view networking can be divided into metropolitan area networks (or national networks, global networks, etc.) and access networks as a whole.
1.2 devices in the access network part can be mainly classified into 3 classes: node server, access switch (including Ethernet gateway), terminal (including various set-top boxes, code board, memory, etc.).
The specific hardware structure of each access network device is as follows:
the node server:
as shown in fig. 6, the device mainly comprises a network interface module 601, a switching engine module 602, a CPU module 603 and a disk array module 604;
Wherein, the packets coming in from the network interface module 601, the cpu module 603 and the disk array module 604 all enter the switching engine module 602; the switching engine module 602 performs an operation of looking up an address table 605 on an incoming packet, thereby obtaining packet guiding information; and stores the packet into a queue of a corresponding packet buffer 606 according to the packet's guiding information; discarding if the queue of packet buffer 606 is nearly full; the switch engine module 602 polls all packet buffer queues for forwarding if the following conditions are met: 1) The port sending buffer is not full; 2) The queue packet counter is greater than zero. The disk array module 604 mainly controls the hard disk, including initializing, reading and writing operations on the hard disk; the CPU module 603 is mainly responsible for protocol processing with access switches and terminals (not shown), configuration of an address table 605 (including a downstream protocol packet address table, an upstream protocol packet address table, and a data packet address table), and configuration of the disk array module 604.
Access switch:
as shown in fig. 7, mainly includes a network interface module (a downstream network interface module 701, an upstream network interface module 702), a switching engine module 703, and a CPU module 704;
wherein, the packet (uplink data) coming in from the downlink network interface module 701 enters the packet detection module 705; the packet detection module 705 detects whether the Destination Address (DA), source Address (SA), packet type, and packet length of the packet meet the requirements, if so, allocates a corresponding stream identifier (stream-id), and enters the switching engine module 703, otherwise, discards the packet; the packet (downlink data) coming in from the uplink network interface module 702 enters the switching engine module 703; the data packet coming in by the CPU module 704 enters the switching engine module 703; the switching engine module 703 performs an operation of looking up an address table 706 on an incoming packet, thereby obtaining packet guiding information; if a packet entering the switching engine module 703 is destined for the downstream network interface to the upstream network interface, the packet is stored in the queue of the corresponding packet buffer 707 in conjunction with a stream-id; discarding if the queue of the packet buffer 707 is nearly full; if the packet entering the switching engine module 703 is not sent from the downlink network interface to the uplink network interface, storing the data packet in the queue of the corresponding packet buffer 707 according to the packet guiding information; if the queue of the packet buffer 707 is nearly full, it is discarded.
The switching engine module 703 polls all packet buffer queues, in two cases in the embodiment of the present invention:
if the queue is sent from the downlink network interface to the uplink network interface, the following conditions are satisfied for forwarding: 1) The port sending buffer is not full; 2) The queue packet counter is greater than zero; 3) Obtaining a token generated by a code rate control module;
if the queue is not addressed by the downstream network interface to the upstream network interface, the following condition is satisfied for forwarding: 1) The port sending buffer is not full; 2) The queue packet counter is greater than zero.
The rate control module 707 is configured by the CPU module 704 to generate tokens for all packet buffer queues from the downstream network interface to the upstream network interface at programmable intervals to control the rate of upstream forwarding.
The CPU module 704 is mainly responsible for protocol processing with the node server, configuration of the address table 706, and configuration of the rate control module 707.
Ethernet corotation gateway:
as shown in fig. 8, the network interface module (downlink network interface module 801, uplink network interface module 802), switching engine module 803, CPU module 804, packet detection module 805, rate control module 808, address table 806, packet buffer 807, MAC adding module 809, and MAC deleting module 810 are mainly included.
Wherein, the data packet coming in from the downlink network interface module 801 enters the packet detection module 805; the packet detection module 805 detects whether the ethernet MAC DA, ethernet MAC SA, ethernet length or frame type, video network destination address DA, video network source address SA, video network packet type and packet length of the data packet meet the requirements, and if so, allocates a corresponding stream identifier (stream-id); then, the MAC DA, MAC SA, length or frame type (2 byte) are subtracted by the MAC delete module 810 and enter the corresponding receive buffer, otherwise discarded;
the downlink network interface module 801 detects the sending buffer of the port, if there is a packet, acquires the ethernet MAC DA of the corresponding terminal according to the destination address DA of the packet's internet of view, adds the ethernet MAC DA of the terminal, the MAC SA of the ethernet co-ordination gateway, and the ethernet length or frame type, and sends.
The function of the other modules in the ethernet corotation gateway is similar to that of the access switch.
And (3) a terminal:
the system mainly comprises a network interface module, a service processing module and a CPU module; for example, the set top box mainly comprises a network interface module, a video/audio encoding/decoding engine module and a CPU module; the coding board mainly comprises a network interface module, a video and audio coding engine module and a CPU module; the memory mainly comprises a network interface module, a CPU module and a disk array module.
1.3 devices of the metropolitan area network part can be mainly classified into 2 classes: node server, node switch, metropolitan area server. The node switch mainly comprises a network interface module, a switching engine module and a CPU module; the metropolitan area server mainly comprises a network interface module, a switching engine module and a CPU module.
2. View networking data packet definition
2.1 Access network packet definition
The data packet of the access network mainly comprises the following parts: destination Address (DA), source Address (SA), reserved bytes, payload (PDU), CRC.
As shown in the following table, the data packet of the access network mainly includes the following parts:
DA SA Reserved Payload CRC
wherein:
the Destination Address (DA) is composed of 8 bytes (byte), the first byte represents the type of data packet (such as various protocol packets, multicast data packets, unicast data packets, etc.), 256 possibilities are at most provided, the second byte to the sixth byte are metropolitan area network addresses, and the seventh and eighth bytes are access network addresses;
the Source Address (SA) is also composed of 8 bytes (bytes), defined identically to the Destination Address (DA);
the reserved bytes consist of 2 bytes;
the payload portion has different lengths according to the types of the different datagrams, and is 64 bytes if it is various protocol packets, and 32+1024=1056 bytes if it is a unicast packet, and is of course not limited to the above 2 types;
The CRC consists of 4 bytes and its calculation method follows the standard ethernet CRC algorithm.
2.2 metropolitan area network packet definition
The topology of the metropolitan area network is a pattern, there may be 2 or even more than 2 connections between two devices, i.e. there may be more than 2 connections between node switches and node servers, node switches and node switches, node switches and node servers. However, the metropolitan area network address of the metropolitan area network device is unique, and in order to accurately describe the connection relationship between metropolitan area network devices, parameters are introduced in the embodiment of the present invention: a tag to uniquely describe a metropolitan area network device.
The definition of label in this specification is similar to that of MPLS (Multi-Protocol Label Switch, multiprotocol label switching), and assuming that there are two connections between device a and device B, there are 2 labels for packets from device a to device B and 2 labels for packets from device B to device a. The label is split into label and label out, and assuming that the label (in label) of the packet entering the device a is 0x0000, the label (out label) of the packet when leaving the device a may become 0x0001. The network access process of the metropolitan area network is a network access process under centralized control, that is, the address allocation and label allocation of the metropolitan area network are all led by the metropolitan area server, the node switch and the node server are all passively executed, which is different from the label allocation of the MPLS, which is the result of mutual negotiation between the switch and the server.
As shown in the following table, the data packet of the metropolitan area network mainly includes the following parts:
DA SA Reserved tag Payload CRC
I.e. Destination Address (DA), source Address (SA), reserved bytes (Reserved), labels, payload (PDU), CRC. Wherein the format of the tag may be defined with reference to the following: the tag is 32 bits, with the high 16bit reservation, with only the low 16bit, and its position is between the reserved bytes and payload of the packet.

Claims (10)

1. A conference maintenance method, which is executed in a master control server, comprising:
acquiring abnormal information of a first abnormal terminal device in a target conference;
determining a first target terminal device corresponding to the first abnormal terminal device according to a preset corresponding relation between the master terminal device and the slave terminal device, wherein the first abnormal terminal device and the first target terminal device correspond to the same sub-control server; the sub-control server is used for sending the abnormal information of the first abnormal terminal equipment to the main control server;
judging whether the first target terminal equipment is in a normal state or not;
and if the first target terminal equipment is in a normal state, replacing the first abnormal terminal equipment by the first target terminal equipment, controlling the first target terminal equipment to join the target conference, and controlling the first target terminal equipment to establish a data link.
2. The method according to claim 1, further comprising, before the acquiring the abnormality information of the first abnormal terminal device in the target conference:
receiving a master-slave setting instruction sent by a session management client, wherein the master-slave setting instruction comprises a master terminal equipment identifier and a slave terminal equipment identifier;
and responding to the master-slave setting instruction, setting terminal equipment corresponding to the master terminal equipment identifier in a registration file as master terminal equipment, setting terminal equipment corresponding to the slave terminal equipment identifier in the registration file as slave terminal equipment, and establishing a corresponding relation between the master terminal equipment and the slave terminal equipment to obtain a target registration file.
3. The method of claim 2, further comprising, after receiving the master-slave setup instruction sent by the session client:
according to the corresponding relation between the terminal equipment and the sub-control server in the target registration file, determining a target sub-control server corresponding to a master terminal equipment and a slave terminal equipment, and sending a first notification message to the master terminal equipment and a second notification message to the slave terminal equipment through the target sub-control server, wherein the first notification message is used for notifying that equipment corresponding to the master terminal equipment is the slave terminal equipment, and the second notification message is used for notifying that equipment corresponding to the slave terminal equipment is the master terminal equipment.
4. A method according to claim 2 or 3, further comprising, after said establishing a correspondence between said master terminal device and said slave terminal device to obtain a target registration file:
receiving a meeting starting instruction sent by the meeting management client, wherein the meeting starting instruction comprises a meeting identifier of the target meeting and information of all terminal devices in the target meeting;
if the second abnormal terminal equipment exists in all the terminal equipment, judging whether second target terminal equipment corresponding to the second abnormal terminal equipment exists or not according to the target registration file;
if the second target terminal equipment exists and is in a normal state, replacing the second abnormal terminal equipment by the second target terminal equipment, controlling the second target terminal equipment to join the target conference, and controlling the second target terminal equipment to establish a data link;
and sending a first conference entrance notification message to the conference management client, wherein the first conference entrance notification message is used for indicating that the second target terminal equipment successfully participates in the target conference.
5. The method as recited in claim 4, further comprising:
and if the second target terminal equipment corresponding to the second abnormal terminal equipment does not exist or the second target terminal equipment is in an abnormal state, sending a second meeting notification message to the meeting management client, wherein the second meeting notification message is used for notifying the meeting management client of the abnormal reason of the second abnormal terminal equipment.
6. A method according to claim 2 or 3, further comprising:
and if the first target terminal equipment corresponding to the first abnormal terminal equipment does not exist, or the first target terminal equipment is in an abnormal state, sending the abnormal information of the first abnormal terminal equipment to the session management client.
7. The utility model provides a meeting maintenance device which characterized in that sets up in the master control server, includes:
the acquisition module is used for acquiring the abnormal information of the first abnormal terminal equipment in the target conference;
the first determining module is used for determining first target terminal equipment corresponding to the first abnormal terminal equipment according to the preset corresponding relation between the master terminal equipment and the slave terminal equipment, wherein the first abnormal terminal equipment and the first target terminal equipment correspond to the same sub-control server, and the sub-control server is used for sending the abnormal information of the first abnormal terminal equipment to the master control server;
The first judging module is used for judging whether the first target terminal equipment is in a normal state or not;
and the replacing module is used for replacing the first abnormal terminal equipment by the first target terminal equipment if the first target terminal equipment is in a normal state, controlling the first target terminal equipment to join the target conference and controlling the first target terminal equipment to establish a data link.
8. The apparatus as recited in claim 7, further comprising:
the receiving module is used for receiving a master-slave setting instruction sent by the management client, wherein the master-slave setting instruction comprises a master terminal equipment identifier and a slave terminal equipment identifier;
the setting module is used for responding to the master-slave setting instruction, setting terminal equipment corresponding to the master terminal equipment identifier in the registration file as master terminal equipment, setting terminal equipment corresponding to the slave terminal equipment identifier in the registration file as slave terminal equipment, and establishing a corresponding relation between the master terminal equipment and the slave terminal equipment so as to obtain a target registration file.
9. A computer readable storage medium, characterized in that the computer readable storage medium stores thereon a computer program, which when executed by a processor implements the conference maintenance method according to any one of claims 1 to 6.
10. A conference maintenance device comprising a processor, a memory and a computer program stored on the memory and executable on the processor, which when executed by the processor carries out the steps of the conference maintenance method as claimed in any one of claims 1 to 6.
CN202010144598.7A 2020-03-04 2020-03-04 Conference maintenance method, conference maintenance device and readable storage medium Active CN111447393B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010144598.7A CN111447393B (en) 2020-03-04 2020-03-04 Conference maintenance method, conference maintenance device and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010144598.7A CN111447393B (en) 2020-03-04 2020-03-04 Conference maintenance method, conference maintenance device and readable storage medium

Publications (2)

Publication Number Publication Date
CN111447393A CN111447393A (en) 2020-07-24
CN111447393B true CN111447393B (en) 2023-08-18

Family

ID=71653131

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010144598.7A Active CN111447393B (en) 2020-03-04 2020-03-04 Conference maintenance method, conference maintenance device and readable storage medium

Country Status (1)

Country Link
CN (1) CN111447393B (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112017082B (en) * 2020-07-28 2023-12-05 安徽鸿程光电有限公司 Data processing method, device, electronic equipment and storage medium
CN112003978A (en) * 2020-08-21 2020-11-27 惠州Tcl云创科技有限公司 Conference management interface display method and device, storage medium and terminal equipment
CN115102930A (en) * 2022-06-28 2022-09-23 海南乾唐视联信息技术有限公司 Conference map generation method and device, electronic equipment and readable storage medium
CN115442557B (en) * 2022-08-10 2023-07-07 北京华建云鼎科技股份公司 Data processing system for verifying terminal

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0481060A (en) * 1990-07-20 1992-03-13 Sharp Corp Communication conference control system
CN101150439A (en) * 2007-09-25 2008-03-26 华为技术有限公司 A method, system and device for realizing master/slave switching
CN106209399A (en) * 2015-04-30 2016-12-07 华为技术有限公司 Conference terminal preordering method, Conference server and conference terminal switched system
KR102325758B1 (en) * 2017-10-31 2021-11-11 삼성에스디에스 주식회사 Conference system and method for switching connection terminal thereof

Also Published As

Publication number Publication date
CN111447393A (en) 2020-07-24

Similar Documents

Publication Publication Date Title
CN111447393B (en) Conference maintenance method, conference maintenance device and readable storage medium
CN109462753B (en) System and method for testing multiple video conferences
CN110620896B (en) Conference establishing method, system and device
CN108574818B (en) Information display method and device and server
CN109246486B (en) Method and device for framing
CN109561072B (en) Link detection method and system
CN110545395B (en) Video networking conference switching method and device
CN111327868B (en) Method, terminal, server, equipment and medium for setting conference speaking party roles
CN109347844B (en) Method and device for accessing equipment to Internet
CN111224889A (en) Data transmission method and device
CN110417792B (en) Communication method, system, gateway device and storage medium
CN110336710B (en) Terminal testing method, system and device and storage medium
CN109889516B (en) Method and device for establishing session channel
CN111510341A (en) Network testing method and device for video network
CN110690989A (en) Service data transmission method, device and computer readable storage medium
CN110099307B (en) Node connection method, video network and computer readable storage medium
CN111835717B (en) Method and device for acquiring monitoring code stream and readable storage medium
CN111526323B (en) Panoramic video processing method and device
CN110474956B (en) Method and device for sealing number of video networking equipment, electronic equipment and readable storage medium
CN110493311B (en) Service processing method and device
CN111131840B (en) Method and device for switching network of video service system
CN110808896B (en) Data transmission method and device, electronic equipment and storage medium
CN110636110B (en) Monitoring data flow adjusting method and device
CN110445701B (en) Business object processing method and device and storage medium
CN109819200B (en) Method and device for checking posts of participating terminals

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant