A video conference communication method, device and computer readable storage medium

Abstract

The embodiment of the present invention provides a video conference communication method, device and computer storage medium, which detect messages through a SIP server to determine the state of an MCU protocol stack and perform corresponding policy processing. At the same time, the MCU restores the corresponding SIP session information according to the request message of the SIP server. In some implementation processes, it is ensured that the terminal participating in the conference is not hung up and the conference control function is normal, and the terminal user cannot perceive the occurrence of an MCU failure, thereby improving the reliability of the video conference and enhancing the user experience.

Description

Technical Field

[0001] The embodiments of the present invention relate to, but are not limited to, the field of multimedia video conferencing, and specifically, to, but are not limited to, a video conferencing communication method, apparatus, and computer-readable storage medium. Background Art

[0002] The MCU (Multipoint Control Unit), a key component of a video conferencing system, interacts with multiple endpoints to maintain audio and video connectivity. To provide reliable video conferencing services, the MCU incorporates mechanisms to ensure system reliability. For example, if a key module within the MCU fails, stops processing messages, or freezes, the monitoring process will automatically restart the module and restore functionality in the shortest possible time.

[0003] However, restarting modules cannot solve all problems. For example, after the SIP (Session Initiation Protocol) protocol stack module is restarted, it can only ensure the normal operation of subsequent functions, such as new terminal calls, but existing calls cannot be maintained. Because key information such as session information has been lost, such as the call state machine and transaction layer data, the restarted SIP protocol stack cannot normally respond to subsequent SIP messages, such as UPDATE session keepalive messages and INFO VCU requests. Abnormal UPDATE responses can cause the SIP server network element to hang up the call, and abnormal INFO VCU requests can cause image decoding failures.

[0004] In related technologies, for scenarios with high security requirements, the system is generally configured with two independent MCUs, which serve as the primary and backup devices. When the primary device fails, the entire MCU device will be brought down. This has obvious disadvantages:

[0005] 1. When using the master-slave MCU solution, any abnormality in a module may cause the entire device to switch, affecting the stability of the entire system;

[0006] 2. The active-standby solution requires two sets of physical equipment, which increases costs. In addition, the solution is relatively complex and requires a backup MCU to restore the entire business system from the database.

[0007] To summarize, when a failure occurs in certain key MCU modules, the terminals already connected to the conference will be disconnected. After the monitoring process reconnects the module, it will be unable to maintain the calls that had been established before the failure. When a master-slave MCU solution is adopted, as long as an abnormality occurs in any MCU module, the stability of the entire video conferencing system will be affected. Summary of the Invention

[0008] The embodiments of the present invention provide a video conferencing communication method and apparatus, which primarily address the technical problem of insufficient monitoring process mechanisms in MCU devices. This problem arises when the MCU fails and restarts the protocol stack process, making it unable to respond normally to messages such as hang-up and call keep-alive from the SIP server.

[0009] To solve the above technical problems, an embodiment of the present invention provides a video conferencing communication method, including:

[0010] After the MCU is restarted, the SIP server receives the session keep-alive message sent by the terminal and sends the session keep-alive message to the MCU. The session keep-alive message is sent by the terminal according to the keep-alive period;

[0011] The SIP server receives the first SIP session response message sent by the MCU, and sends a session keep-alive message response message to the terminal.

[0012] An embodiment of the present invention further provides a video conference communication method, including:

[0013] The MCU monitoring process detects a SIP session abnormality and restarts it;

[0014] The MCU receives a session keep-alive message sent by the SIP server, where the session keep-alive message is sent by the terminal to the SIP server according to a keep-alive period;

[0015] The MCU sends the first SIP session response message to the SIP server and reports the session keep-alive message abnormality event to the application server;

[0016] After receiving a successful response from the terminal indicating that the conference status is normal according to the service query, the MCU constructs and saves SIP session information corresponding to the terminal.

[0017] An embodiment of the present invention further provides a video conferencing communication device, comprising:

[0018] A first receiving module is used to receive a session keep-alive message sent by the terminal and a first SIP session response message sent by the MCU;

[0019] The first sending module is configured to send the session keep-alive message to the MCU and send a session keep-alive message response message to the terminal.

[0020] An embodiment of the present invention further provides a video conferencing communication device, comprising:

[0021] The monitoring module is used to detect SIP session anomalies and restart the MCU;

[0022] The second receiving module is used to receive the session keep-alive message sent by the SIP server and the successful response of the receiving terminal according to the service query that the conference status is normal;

[0023] A second sending module is used to send the first SIP session response message to the SIP server and report the session keep-alive message abnormal event to the application server;

[0024] The processing module is used to construct and save the SIP session information corresponding to the terminal.

[0025] An embodiment of the present invention further provides a computer storage medium, wherein the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of the video conference communication method described above.

[0026] The beneficial effects of the present invention are:

[0027] According to the video conferencing communication method, apparatus, and computer storage medium provided by embodiments of the present invention, after an MCU restarts, a SIP server receives a session keep-alive message sent by a terminal and sends the session keep-alive message to the MCU. The session keep-alive message is sent by the terminal according to a keep-alive period. The SIP server receives a first SIP session response message sent by the MCU and sends a session keep-alive message response message to the terminal. In certain implementations, after an MCU fails and restarts, a SIP session message corresponding to the terminal is constructed based on the session keep-alive information, thereby preventing the connected terminal from being disconnected and ensuring the normal progress of subsequent sessions.

[0028] Other features and corresponding beneficial effects of the present invention are described in the latter part of the specification, and it should be understood that at least some of the beneficial effects become obvious from the description in the specification of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 This is a schematic diagram of the general process of video conference communication;

[0030] Figure 2 This is a schematic diagram of the basic process of restarting the MCU protocol stack module when a fault occurs in a video conference according to the first embodiment of the present invention;

[0031] Figure 3 This is a schematic diagram of the restart process when a fault occurs in the MCU protocol stack module in a video conference according to the second embodiment of the present invention;

[0032] Figure 4 This is a schematic diagram of the interactive process of restarting the MCU protocol stack module when a fault occurs in a video conference according to the second embodiment of the present invention;

[0033] Figure 5This is a schematic diagram of a service request I frame process after the MCU protocol stack is restarted in a video conference according to the third embodiment of the present invention;

[0034] Figure 6 This is a schematic diagram of the I-frame interaction process for a service request after the MCU protocol stack is restarted in a video conference according to the third embodiment of the present invention. DETAILED DESCRIPTION

[0035] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the following is a further detailed description of the embodiments of the present invention through specific implementation methods in conjunction with the accompanying drawings. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0036] Example 1:

[0037] In order to address the deficiencies of the monitoring process mechanism in the MCU device and maintain the connection of terminals that have already joined the conference without being disconnected and the conference control function being normal, an embodiment of the present invention provides a video conferencing communication method. The method uses a SIP server to detect messages to determine the status of the MCU protocol stack and perform corresponding policy processing. At the same time, the MCU restores the corresponding SIP session information based on the request message of the SIP server, thereby maintaining the connection of terminals that have already joined the conference without being disconnected and the conference control function being normal.

[0038] See Figure 1 , the terminal calls the MCU through the SIP server. After the SIP session connection is established, the media code stream is sent between the terminal and the MCU, and the terminal will succeed.

[0039] In order to detect whether the SIP session still exists, the terminal and the SIP server, and the SIP server and the MCU will periodically send session keep-alive messages. If no session keep-alive message response message is received, the SIP server and the terminal will hang up the SIP call. It should be noted that in the embodiment of the present invention, the session keep-alive message is an UPDATE message, and correspondingly, the session keep-alive message response message is an UPDATE 200OK response message. Figure 1 ,When the MCU’s SIP protocol stack fails, the MCU cannot respond to the UPDATE keep-alive message, and the request times out, the SIP server will send a 408 request timeout message to the terminal and execute the ,hangup operation.

[0040] When the monitoring process detects that the SIP protocol stack of the MCU has failed, it will immediately restart the SIP protocol stack. However, the restarted SIP protocol stack has lost the key information of the SIP session and cannot respond to subsequent SIP messages normally. In this regard, the embodiment of the present invention improves on the existing mechanism and proposes a video conferencing communication method to ensure that the terminal is not hung up when the MCU fails. For the specific process, see Figure 2 .

[0041] S201: After the MCU is restarted, the SIP server receives a session keep-alive message sent by a terminal, and sends the session keep-alive message to the MCU.

[0042] In this embodiment of the present invention, after a successful terminal connection, session keepalive messages are periodically sent between the terminal and the SIP server, and between the SIP server and the MCU, to verify the continued existence of the SIP session. In other words, the prerequisite for the terminal to periodically send session keepalive messages is to ensure that the terminal connection is successful. The specific process of the terminal connection is as follows: the terminal sends an INVITE message to the SIP server. The SIP server receives the INVITE message and forwards it to the MCU. The MCU sends a 200OK response message to the SIP server. The SIP server receives the 200OK response message and forwards it to the terminal. The terminal sends an ACK message to the SIP server. The SIP server receives the ACK message and sends it to the MCU. At this point, media streams can be sent between the terminal and the MCU, and the terminal connection is successful.

[0043] In this embodiment of the present invention, session keepalive messages are sent periodically, i.e., periodically. This period is called the keepalive period. It should be noted that session keepalive messages are UPDATE messages. The UPDATE messages received by the MCU from the SIP server carry key session information such as the Request-Line, From, To, and Call-ID fields. The following examples further illustrate this information:

[0044] UPDATE sip:+863213328433@mmconf100.ucs.com.cn SIP / 2.0

[0045] It should be noted that this information includes the request type, request address (Request-URI) and SIP version number.

[0046] Via:SIP / 2.0 / UDP 192.166.6.226:15123; branch=z9hG4bK20939826222

[0047] It should be noted that this information contains the SIP version number, transmission type UDP, call address and branch random code.

[0048] From:<sip:26770010@ucs.com.cn> ;tag=8508.116826223

[0049] To:<tel:+<8610001>;tag=651375074.133.100.0.0.1182650445

[0050] It should be noted that the From and To session messages represent the sender and the recipient of the request message. Since there are username tags in these two messages, they are enclosed in angle brackets. The tag contained in the From information is a random code.

[0051] Call-ID:2111976454j133.100.26330660@192.166.5.49

[0052] It should be noted that the Call-ID is a globally unique value and is the same for each call.

[0053] CSeq:100UPDATE

[0054] It should be noted that the CSeq message is also known as the command queue. For each new request sent, the value is automatically incremented by 1.

[0055] Contact:<sip:26770010@192.166.6.226:15123;transport=UDP>

[0056] Session-Expires:120;refresher=uac

[0057] According to the protocol specification, the From, To, and Call-ID within the same session must be exactly the same, and the URI of the Request-Line must also be exactly the same. Except for the request type, the IP address in the contact is replaced with the MCU local listening IP and port number.

[0058] In the embodiment of the present invention, when the MCU fails and before the MCU restarts, the SIP protocol stack crashes and cannot process messages normally. At this time, the monitoring process has not detected the failure of the MCU and has not immediately restarted the SIP protocol stack. The MCU does not respond to the UPDATE message, and the SIP server does not receive the response message from the MCU. At this time, due to the timeout of the UPDATE request message, the SIP server protocol stack does not receive the MCU response. The SIP server then determines that it may be a network problem or the MCU has failed at this time. To maintain the current SIP session without hanging up, an UPDATE response message is sent to the terminal. It should be understood that in the embodiment of the present invention, the UPDATE response message can specifically be an UPDATE 200OK response message.

[0059] In the embodiment of the present invention, UPDATE messages are sent periodically to ensure the normality and reliability of the SIP session. After the MCU is restarted, when the keep-alive period is reached, the terminal sends an UPDATE message to the SIP server, and the SIP server forwards the UPDATE message to the MCU.

[0060] S202: The SIP server receives the first SIP session response message sent by the MCU, and sends a session keep-alive message response message to the terminal.

[0061] The MCU's monitoring process detects an abnormality in the MCU's SIP protocol stack process and restarts the SIP protocol stack. However, since the SIP protocol stack has been restarted, there is no SIP session information corresponding to the terminal in the SIP protocol stack. According to the protocol specification, the corresponding first SIP session response message is sent to the SIP server. At the same time as sending the first SIP session response message, the session keep-alive message abnormality event is reported to the application server.

[0062] Specifically, the SIP protocol stack restarts, and there is no transaction layer key data corresponding to the terminal in the SIP protocol stack. According to the protocol specification, it will respond with a 481 message, indicating that the SIP transaction layer data does not exist. While sending the 481 response message, the SIP protocol stack reports the UPDATE exception event to the application. It should be noted that the UPDATE exception event carries identification information such as the terminal number and conference number.

[0063] It should be noted that if the MCU still responds with a timeout and the SIP server does not receive a response message from the MCU, the SIP server will believe that the MCU or the network has failed and has not recovered, and will send a request timeout message to the terminal. The terminal will perform an abnormal hang-up process, specifically a 408 message.

[0064] In an embodiment of the present invention, the SIP protocol stack reports an UPDATE exception event to the application. The UPDATE exception event carries identification information such as the terminal number and conference number. It should be noted that the conference number is the user number in the Request-Line, and the terminal number is the user number in the From header field. The service inquires whether the conference status of the corresponding terminal is normal. If normal, after receiving a successful response, the SIP protocol stack constructs the SIP session information of the corresponding terminal and saves it in the SIP protocol stack transaction layer of the MCU. It should be noted that the SIP protocol stack has already constructed the SIP session information. Therefore, when the MCU receives a session keep-alive message in the next keep-alive cycle, it can respond to the session keep-alive message normally and then send a 200OK response message to the SIP server. The SIP server can then confirm that the MCU has restored the SIP session information and the conference on the MCU side is normal, and forward the 200OK response message to the terminal.

[0065] It should be noted that if the SIP call status is abnormal and the SIP protocol stack does not have the SIP session information corresponding to the terminal, it will send the corresponding first SIP session response message to the SIP server according to the protocol specification. The SIP server will forward the first SIP session response message to the terminal, and the terminal will hang up. Specifically, if the SIP protocol stack does not have transaction layer data, it will send a 481 response message to the SIP server. If the SIP server fails to keep alive twice, it will determine that the terminal's SIP call is abnormal and forward the 481 response message to the terminal, allowing the terminal to hang up the call.

[0066] In the embodiment of the present invention, when the terminal receives the 408 request timeout message or 481 message sent by the SIP server, it can hang up. For details, please refer to Figure 1 The terminal sends a BYE request message to the SIP server, indicating that it wants to release the call. The SIP server forwards the BYE request message to the MCU. The MCU responds with a timeout, and the SIP server sends a 408 Request Timeout message to the terminal. The terminal then hangs up the SIP call and releases the SIP session.

[0067] The video conferencing communication method provided by the embodiment of the present invention determines the status of the MCU protocol stack through message detection by the SIP server and performs corresponding policy processing. At the same time, the MCU restores the corresponding SIP session information according to the request message of the SIP server, thereby ensuring that the terminal participating in the meeting is not hung up and the conference control function is normal. The terminal user is unaware of the occurrence of the MCU failure, thereby improving the reliability of the video conferencing and enhancing the user experience.

[0068] Example 2:

[0069] For ease of understanding, this embodiment provides further examples based on the video conferencing communication method shown in the above embodiment.

[0070] See Figure 3 As shown, Figure 3 The specific process of the video conferencing communication method according to the embodiment of the present invention is as follows:

[0071] S301: The SIP server receives a session keep-alive message sent by a terminal in a first keep-alive period, and sends the session keep-alive message to an MCU.

[0072] In the embodiment of the present invention, after the terminal successfully connects, in order to detect whether the SIP session still exists, the terminal and the SIP server, and the SIP server and the MCU will periodically send session keep-alive messages. The session keep-alive messages are sent periodically. It should be noted that the session keep-alive messages are UPDATE messages. The UPDATE messages sent by the SIP server received by the MCU protocol stack will carry key session information such as Request-Line, From, To, and Call-ID.

[0073] S302: When the SIP server does not receive a response message from the MCU, it sends a session keep-alive response message to the terminal.

[0074] In this embodiment of the present invention, an MCU fails, causing the SIP protocol stack to freeze and be unable to process messages normally. At this point, the monitoring process has not yet detected the MCU failure and has not immediately restarted the SIP protocol stack. The MCU does not respond to the UPDATE request message, and the SIP server does not receive a response message from the MCU. In this case, the SIP server protocol stack does not receive a response from the MCU due to a timeout of the UPDATE request message. The SIP server determines that this may be due to network issues or an MCU failure. To maintain the current SIP session, the SIP server does not terminate the session and sends an UPDATE response message to the terminal. The UPDATE response message may specifically be an UPDATE 200 OK response message.

[0075] S303: The SIP server receives a session keep-alive message sent by the terminal in the second keep-alive period, and sends the session keep-alive message to the MCU;

[0076] In the embodiment of the present invention, the UPDATE session keep-alive message is sent periodically in order to ensure the normality and reliability of the SIP session.

[0077] S304: The SIP server receives the first SIP session response message sent by the MCU and sends a session keep-alive message response message to the terminal;

[0078] In the embodiment of the present invention, before the second keep-alive period arrives, the monitoring process of the MCU detects that the SIP protocol stack process of the MCU is abnormal and restarts the SIP protocol stack. However, because the SIP protocol stack has been restarted, the SIP protocol stack does not contain SIP session information corresponding to the terminal. Therefore, according to the protocol specification, the corresponding first SIP session response message is sent to the SIP server. At the same time as sending the first SIP session response message, the session keep-alive message abnormality event is reported to the application server.

[0079] Specifically, the SIP protocol stack restarts, and there is no transaction layer key data corresponding to the terminal in the SIP protocol stack. According to the protocol specification, it will respond with a 481 message, indicating that the SIP transaction layer data does not exist. While sending the 481 response message, the SIP protocol stack reports the UPDATE exception event to the application. It should be noted that the UPDATE exception event carries identification information such as the terminal number and conference number.

[0080] It should be noted that if the MCU still responds to timeout in the second keep-alive period, the SIP server will consider that the MCU or the network has failed and has not recovered, and will send a 408 request timeout message to the terminal, and the terminal will perform abnormal hang-up processing.

[0081] S305. The SIP server receives a session keep-alive message sent by the terminal in the third keep-alive period, and sends the session keep-alive message to the MCU.

[0082] S306: The SIP server receives the session keep-alive message response message sent by the MCU, and sends the session keep-alive message response message to the terminal.

[0083] In an embodiment of the present invention, the SIP protocol stack reports an UPDATE exception event to the application. The UPDATE exception event carries identification information such as the terminal number and conference number. It should be noted that the conference number is the user number in the Request-Line, and the terminal number is the user number in the From header field. The service inquires whether the conference status of the corresponding terminal is normal. If normal, after receiving a successful response, the SIP protocol stack constructs the SIP session information of the corresponding terminal and saves it in the SIP protocol stack transaction layer of the MCU. It should be noted that the SIP protocol stack has already constructed the SIP session information. Therefore, when the MCU receives a session keep-alive message in the next keep-alive cycle, it can respond to the session keep-alive message normally and then send a 200OK response message to the SIP server. The SIP server can then confirm that the MCU has restored the SIP session information and the conference on the MCU side is normal, and forward the 200OK response message to the terminal.

[0084] It should be noted that if the SIP call status is abnormal and the SIP protocol stack does not have the SIP session information corresponding to the terminal, it will send the corresponding first SIP session response message to the SIP server according to the protocol specification. The SIP server will forward the first SIP session response message to the terminal, and the terminal will hang up. Specifically, if the SIP protocol stack does not have transaction layer data, it will send a 481 response message to the SIP server. If the SIP server fails to keep alive twice, it will determine that the terminal's SIP call is abnormal and forward the 481 response message to the terminal, allowing the terminal to hang up the call.

[0085] In the embodiment of the present invention, when the terminal receives the 408 request timeout message or 481 message sent by the SIP server, it can hang up. For details, please refer to Figure 1 The terminal sends a BYE request message to the SIP server, indicating that it wants to release the call. The SIP server forwards the BYE request message to the MCU. The MCU responds with a timeout, and the SIP server sends a 408 Request Timeout message to the terminal. The terminal then hangs up the SIP call and releases the SIP session.

[0086] In the embodiment of the present invention, after the terminal successfully joins the conference, the MCU protocol stack module fails and crashes, and the monitoring process restarts the MCU protocol stack. This involves the interaction between the terminal, the SIP server, and the MCU. For a more intuitive and specific process, see Figure 4 .

[0087] The video conference communication method provided by the embodiment of the present invention receives the session keep-alive information sent by the terminal in the first keep-alive period through the SIP server, and sends the session keep-alive information to the MCU. If the MCU fails and does not respond to the session keep-alive information, the SIP server does not receive the response message of the MCU. The SIP server determines that the MCU may have failed at this time, maintains the current SIP session, does not hang up, and sends a session keep-alive information response message to the terminal; the SIP server receives the session keep-alive information sent by the terminal in the second keep-alive period, and sends the session keep-alive information to the MCU. At this time, the monitoring process of the MCU has detected the abnormality of the SIP protocol stack process and restarted the SIP protocol stack. The MCU sends a first SIP session response message to the SIP server. The SIP server receives the first SIP session response message sent by the MCU, and can confirm that the MCU If a restart occurs and the current SIP protocol stack has been restored, the current session is still maintained without hanging up, and a session keep-alive information response message is sent to the terminal; the SIP server receives the session keep-alive information sent by the terminal in the third keep-alive period, and sends the session keep-alive information to the MCU. The MCU sends a session keep-alive information response message to the SIP server. At this time, the SIP server can confirm that the conference on the MCU side is normal and forward the third session keep-alive information 200OK response message to the terminal; the SIP server performs message detection to determine the status of the MCU protocol stack and performs corresponding policy processing. At the same time, the MCU restores the corresponding SIP session information according to the request message of the SIP server, thereby ensuring that the terminal in the meeting is not hung up and the conference control function is normal. The terminal user cannot perceive the occurrence of the MCU failure, thereby improving the reliability of the video conference and enhancing the user experience.

[0088] Example 3:

[0089] It should be understood that image transmission is also involved in video conferencing. An abnormal response to the UPDATE session keep-alive information will cause the SIP server network element to hang up the call. An abnormal INFO request will cause image decoding failure. Therefore, based on the above embodiment, the present invention proposes a video conferencing communication method, which is applied when the MCU fails and the protocol stack is restarted, and the service requests an I frame. For the specific process, please refer to Figure 5 .

[0090] S501: A SIP server receives a session keep-alive message sent by a terminal in a first keep-alive period, and sends the session keep-alive message to an MCU.

[0091] In the embodiment of the present invention, after the terminal successfully logs in, in order to detect whether the SIP session still exists, UPDATE session keep-alive messages are periodically sent between the terminal and the SIP server, and between the SIP server and the MCU. This has been described in detail in the above embodiment and will not be repeated here.

[0092] S502: When the SIP server does not receive a response message from the MCU, it sends a session keep-alive message response message to the terminal.

[0093] In this embodiment of the present invention, if an MCU fails, the SIP protocol stack freezes and cannot process messages normally. At this time, the monitoring process has not yet detected the MCU failure and has not immediately restarted the SIP protocol stack. The MCU does not respond to the UPDATE request message, and the SIP server does not receive the MCU's response message. In this case, the SIP server protocol stack times out the UPDATE request message and does not receive the MCU's response message. The SIP server determines that this may be due to network issues or MCU failure. To maintain the current SIP session, the SIP server does not terminate the session and sends an UPDATE response message to the terminal. The UPDATE response message may specifically be an UPDATE 200OK response message.

[0094] S503: The monitoring process of the MCU detects that the SIP protocol stack process is abnormal and restarts the SIP protocol stack.

[0095] S504: The MCU fails to send an INFO request message to the SIP server.

[0096] In this embodiment of the present invention, the SIP protocol stack is restarted, and an MCU decoding error occurs. At this point, the MCU sends an I-frame request to the terminal in the form of an INFO request. Because the SIP protocol stack has been restarted, it lacks the SIP session information corresponding to the terminal and is unable to send the INFO request, resulting in a failure.

[0097] It should be noted that I frame (I Frame) is also called intra picture. I frame is usually the first frame of each GOP (a video compression technology used by MPEG). After being moderately compressed, it can be used as a reference point for random access and can be regarded as an image.

[0098] S505: The SIP server receives a session keep-alive message sent by the terminal in the second keep-alive period, and sends the session keep-alive message to the MCU.

[0099] In the embodiment of the present invention, the INFO request is sent between the first keep-alive period and the second keep-alive period.

[0100] S506: The SIP server receives the first SIP session response message sent by the MCU, and sends a session keep-alive message response message to the terminal.

[0101] In the embodiment of the present invention, the monitoring process of the MCU detects that the SIP protocol stack process of the MCU is abnormal and restarts the SIP protocol stack. However, since the SIP protocol stack has been restarted, there is no SIP session information corresponding to the terminal in the SIP protocol stack. According to the protocol specification, the corresponding first SIP session response message is sent to the SIP server. When the SIP server receives the first SIP session response message sent by the MCU, it can be confirmed that the MCU has been restarted and the current SIP protocol stack has been restored. The current session is still maintained without hanging up, and a session keep-alive message response message is sent to the terminal.

[0102] It should be understood that the first SIP session response message is a 481 response message, and the session keep-alive response message is a 200 OK response message.

[0103] S507: The SIP server receives the INFO request message sent by the MCU, and forwards the INFO request message to the terminal.

[0104] It should be understood that the MCU protocol stack has restored the SIP session based on the UPDATE message sent during the second keepalive period. At this point, the MCU can send the INFO request normally. Since the previous I-frame request failed and the MCU image decoding has not been restored, the MCU sends another I-frame request to the terminal.

[0105] S508. After receiving the INFO request message, the terminal sends an INFO response message to the SIP server and notifies the encoder to encode an I frame.

[0106] In the embodiment of the present invention, the INFO response message is a 200OK message.

[0107] S509: The SIP server forwards the INFO response message to the MCU.

[0108] In the embodiment of the present invention, after the MCU receives the INFO response message, it indicates that the MCU image decoding is normal, and thus the I frame request process is terminated.

[0109] In the embodiment of the present invention, when the MCU fails and the monitoring process restarts the MCU protocol stack, the process of service request I frame involves the interaction between the terminal, SIP server and MCU. For a more intuitive and specific process, see Figure 6 .

[0110] In a video conferencing communication method provided by an embodiment of the present invention, after an MCU fails and restarts, the restarted protocol stack does not have the SIP session information of the corresponding terminal, and an INFO request fails to be sent before the second keepalive period arrives. The SIP server receives a session keepalive message sent by the terminal in the second keepalive period and sends the session keepalive message to the MCU. The MCU sends a first SIP session response message to the SIP server. After receiving the first SIP session response message sent by the MCU, the SIP server confirms that the MCU has restarted and the current SIP protocol stack has been restored. The current session is maintained without hanging up, and a session keepalive message response message is sent to the terminal. The MCU resumes the SIP dialogue based on the session keepalive message, and the MCU can then normally send an INFO request message. The SIP server performs message detection to determine the status of the MCU protocol stack and performs corresponding policy processing. The MCU resumes the corresponding SIP session information based on the request message from the SIP server, thereby ensuring that the terminal participating in the conference is not hung up and the conference control function is normal. The terminal user is unaware of the MCU failure, thereby improving the reliability of the video conferencing and enhancing the user experience.

[0111] Example 4:

[0112] An embodiment of the present invention further provides a video conferencing communication device for implementing at least one step in the method of the above embodiment.

[0113] The video conferencing communication device according to the embodiment of the present invention includes a first receiving module and a first sending module.

[0114] The first receiving module is used to receive a session keep-alive message sent by the terminal and a first SIP session response message sent by the MCU;

[0115] The first sending module is configured to send a session keep-alive message to the MCU and send a session keep-alive message response message to the terminal.

[0116] The video conferencing communication device of the embodiment of the present invention further includes a monitoring module, a second receiving module, a second sending module and a processing module;

[0117] The monitoring module is used to detect SIP session anomalies and restart the MCU;

[0118] The second receiving module is used to receive the session keep-alive message sent by the SIP server and the successful response of the receiving terminal according to the service query that the conference status is normal;

[0119] The second sending module is used to send the first SIP session response message to the SIP server and report the abnormal event of the session keep-alive message to the application server;

[0120] The processing module is used to construct and save the SIP session information corresponding to the terminal.

[0121] The video conferencing communication device provided by the embodiment of the present invention includes a first receiving module, a first sending module, a monitoring module, a second receiving module, a second sending module and a processing module, which implements at least one step of the method in the first to third embodiments above, ensuring that the terminal participating in the conference is not hung up and the conference control function is normal, and the terminal user is unaware of the occurrence of the MCU failure, thereby improving the reliability of the video conferencing and enhancing the user experience.

[0122] Embodiment 5:

[0123] The present embodiment also provides a computer-readable storage medium, which includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules or other data). Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable read only memory), flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer.

[0124] The computer-readable storage medium in this embodiment can be used to store one or more computer programs, and the one or more computer programs stored therein can be executed by a processor to implement at least one step of the video conferencing communication method in the above-mentioned embodiment 1 and embodiment 3.

[0125] The above content is a further detailed description of the embodiments of the present invention in conjunction with specific implementation methods, and the specific implementation of the present invention cannot be considered to be limited to these descriptions. For those skilled in the art of the present invention, without departing from the concept of the present invention, several simple deductions or substitutions can be made, which should be considered to fall within the scope of protection of the present invention.

Claims

1. A video conference communication method, include: After the MCU is restarted, the SIP server receives a session keep-alive message sent by the terminal, and sends the session keep-alive message to the MCU, where the session keep-alive message is sent by the terminal according to a keep-alive period; The SIP server receives the first SIP session response message sent by the MCU, and sends a session keep-alive message response message to the terminal; Wherein, the method further comprises: The MCU sends the first SIP session response message to the SIP server, and reports the abnormal event of the session keep-alive message to the application server; after the MCU receives the successful response from the terminal that the conference status is normal according to the service query, the SIP session information corresponding to the terminal is constructed and saved; The SIP server receives a session keep-alive message sent by the terminal in the next keep-alive period, and sends the session keep-alive message to the MCU; the SIP server receives a session keep-alive message response message sent by the MCU, and sends the session keep-alive message response message to the terminal.

2. The video conference communication method according to claim 1, It is characterized in that After the MCU is restarted, before the SIP server receives the session keep-alive message sent by the terminal, the following steps are performed: The SIP server receives a session keep-alive message sent by the terminal, and sends the session keep-alive message to the MCU; The SIP server does not receive a response message from the MCU, and sends a session keep-alive message response message to the terminal.

3. The video conference communication method according to claim 1, It is characterized in that The SIP server receives the session keep-alive message sent by the terminal, and sends the session keep-alive message to the MCU, and then further includes: The SIP server does not receive a response message from the MCU, and sends a request timeout message to the terminal.

4. The video conference communication method according to claim 1, It is characterized in that After the SIP server receives the first SIP session response message sent by the MCU and sends a session keep-alive message response message to the terminal, the following further includes: The SIP server receives a session keep-alive message sent by the terminal, and sends the session keep-alive message to the MCU; The SIP server receives the first SIP session response message sent by the MCU, and sends the first SIP session response message to the terminal.

5. The video conference communication method according to claim 1, It is characterized in that After the MCU is restarted, the following steps are also included: The MCU fails to send an INFO request message to the SIP server.

6. The video conference communication method according to claim 5, It is characterized in that After the SIP server receives the first SIP session response message sent by the MCU and sends a session keep-alive message response message to the terminal, the following steps are included: The SIP server receives the INFO request message sent by the MCU, and forwards the INFO request message to the terminal; The SIP server receives the INFO response message sent by the terminal and forwards it to the MCU.

7. A video conference communication method, include: The MCU monitoring process detects an abnormal SIP session and restarts it; The MCU receives a session keep-alive message sent by the SIP server, where the session keep-alive message is sent by the terminal to the SIP server according to a keep-alive period; The MCU sends the first SIP session response message to the SIP server, and reports the abnormal event of the session keep-alive message to the application server; After the MCU receives a successful response from the terminal that the conference status is normal according to the service query, the MCU constructs and saves the SIP session information corresponding to the terminal; The MCU receives the session keep-alive message in the next keep-alive period, and sends the session keep-alive message response message to the SIP server; The SIP server sends the session keep-alive message response message to the terminal.

8. The video conference communication method according to claim 7, It is characterized in that After the MCU monitoring process detects that the SIP session is abnormal and restarts, the following steps are performed: The MCU fails to send an INFO request message to the SIP server.

9. The video conference communication method according to claim 8, It is characterized in that After the SIP server receives the first SIP session response message sent by the MCU and sends a session keep-alive message response message to the terminal, the following steps are included: The MCU sends an INFO request message to the SIP server; The MCU receives an INFO response message sent by the SIP server, where the INFO response message is a response message sent by the SIP server after receiving the INFO request message received by the terminal.

10. A video conference communication device, used to execute the method according to claim 1, wherein the device include: A first receiving module, used for receiving a session keep-alive message sent by a terminal and receiving a first SIP session response message sent by an MCU; The first sending module is used to send the session keep-alive message to the MCU and send a session keep-alive message response message to the terminal.

11. A video conference communication device, used to execute the method according to claim 7, wherein the device include: Monitoring module, used to detect SIP session abnormalities and restart the MCU; The second receiving module is used to receive the session keep-alive message sent by the SIP server and the successful response of the receiving terminal according to the business query that the conference status is normal; A second sending module is used to send the first SIP session response message to the SIP server, and report the abnormal event of the session keep-alive message to the application server; The processing module is used to construct and save the SIP session information corresponding to the terminal.

12. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores one or more computer programs, and the one or more computer programs can be executed by one or more processors to implement the steps of the video conference communication method as described in any one of claims 1-6 or 7-9.

Images