Method and device for sending negative acknowledgement message in conference, equipment and medium
By flexibly adjusting the sending strategy of negative acknowledge messages based on network status and packet type, the problem of single sending NACK messages in the prior art affecting the quality of real-time video conferences is solved, and the success rate and fluency of packet retransmission of the conference are improved.
Patent Information
- Application Number
- CN202411094114.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-09
- Publication Date
- 2024-11-26
AI Technical Summary
The method of sending NACK messages in the prior art may affect the quality of real-time video conferencing, making it difficult to effectively solve the problem of network packet loss.
By determining the reference factors that affect the sending of negative acknowledge messages, such as network status parameters and packet types, flexibly adjusting the transmission frequency and interval of negative acknowledge messages, ensuring accurate retransmission of data packets and improving the quality of real-time video conferencing.
By adjusting the sending strategy of negative confirmation messages based on specific reference factors, the quality of real-time video conferencing is improved, the smooth playback of audio and video is ensured, and the negative impact of network latency and packet loss rate on meeting quality is reduced.
Smart Images

Figure CN119031090A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of online conferences, and in particular, to a method, apparatus, device and medium for sending a negative confirmation message in a conference. Background Art
[0002] The Negative Acknowledgement (NACK) mechanism is a network protocol used for real-time communications to detect and correct packet loss during transmission. When the receiver detects that a packet is lost, it sends a NACK message to the sender, requesting that the lost packet be resent. In Web Real-Time Communications (WebRTC), the NACK mechanism can be implemented through the Real-Time Transport Control Protocol (RTCP). RTCP is a protocol for transmitting control information, which works with the Real-Time Transport Protocol (RTP) to transmit audio, video, and data streams in real-time communications. The RTCP channel can be used to transmit control information, including NACK messages, between the sender and the receiver.
[0003] The NACK mechanism is an important part of WebRTC, which is used to deal with network packet loss and improve communication quality and stability. By using the NACK mechanism, the integrity and accuracy of data in real-time communication can be improved, thereby providing a better user experience.
[0004] In the existing solutions, when there is packet loss, a NACK message is usually sent to request retransmission. However, this single NACK message sending method may affect the quality of the real-time video conference.
[0005] Therefore, how to provide a method for sending a negative confirmation message to improve the quality of a real-time video conference becomes a problem that needs to be solved. Summary of the invention
[0006] An embodiment of the present application aims to provide a method, apparatus, device and medium for sending a negative confirmation message in a conference. The technical solution of the embodiment of the present application can improve the quality of a real-time video conference.
[0007] In the first aspect, an embodiment of the present application provides a method for sending a negative confirmation message in a conference, which is applied to a data packet receiving end, and the method includes: determining reference factors that affect the sending of the negative confirmation message, and the reference factors include network status parameters, the type of data packet, or predicted data packet loss; sending a negative confirmation message according to the reference factors, and the negative confirmation message includes the sequence number of the lost data packet, and the negative confirmation message is used to instruct the sending end device to retransmit the lost data packet.
[0008] The embodiment of the present application sends a negative confirmation message based on the reference factors that affect the sending of the negative confirmation message, thereby solving the problem that the single method of sending a NACK message in the prior art may affect the quality of the real-time video conference. The embodiment of the present application can flexibly determine the sending of the negative confirmation message based on specific reference factors, thereby improving the quality of the real-time video conference.
[0009] In one embodiment, the reference factor includes the network status parameter, and the network status parameter includes round-trip delay or packet loss rate; wherein, when the network status parameter includes round-trip delay, sending a negative confirmation message based on the reference factor includes: when the round-trip delay is greater than a delay threshold, reducing the sending frequency of negative confirmation messages; or, when the network status parameter includes packet loss rate, sending a negative confirmation message based on the reference factor includes: when the packet loss rate is higher than a packet loss rate threshold, increasing the sending frequency of negative confirmation messages or shortening the sending interval of negative confirmation messages.
[0010] In one embodiment, the reference factor includes the type of data packet, and the types of data include key frame data packets, incremental frame data packets, newly lost data packets or requested retransmission data packets; sending negative confirmation messages according to the reference factors include: when the type of the data packet is a key frame data packet, increasing the sending frequency of negative confirmation messages or shortening the sending interval of negative confirmation messages; or, when the type of the data packet is an incremental frame data packet, maintaining or reducing the sending frequency of negative confirmation messages; or, when the type of the data packet is a newly lost data packet, reducing the sending frequency of negative confirmation messages or increasing the sending interval of negative confirmation messages; or, when the type of the data packet is a requested retransmission data packet, increasing the sending frequency of negative confirmation messages or shortening the sending interval of negative confirmation messages.
[0011] In one embodiment, increasing the sending frequency of negative confirmation messages or shortening the sending interval of negative confirmation messages includes: sending negative confirmation messages with a period less than one round-trip delay, wherein the negative confirmation message is also used to instruct the sending end device to increase the frequency of sending retransmitted data packets.
[0012] In one embodiment, the reference factor includes a predicted packet loss situation; sending a negative confirmation message based on the reference factor includes: when the predicted packet loss probability meets a retransmission condition, sending the negative confirmation message, the negative confirmation message including the sequence number of the predicted lost packet.
[0013] In one embodiment, the sequence number of the predicted lost data packet includes a sequence number subsequent to the sequence number of the latest received datagram.
[0014] In the second aspect, an embodiment of the present application provides a device for sending a negative confirmation message in a conference, which is applied to a data packet receiving end, and the device includes: a determination unit, used to determine reference factors affecting the sending of the negative confirmation message, the reference factors include network status parameters, the type of data packet or predicted data packet loss; a sending unit, used to send a negative confirmation message according to the reference factors, the negative confirmation message includes the sequence number of the lost data packet, and the negative confirmation message is used to instruct the sending end device to retransmit the lost data packet.
[0015] In one embodiment, the reference factor includes the network status parameter, and the network status parameter includes a round-trip delay or a packet loss rate; wherein, when the network status parameter includes a round-trip delay, the sending unit is specifically used to reduce the sending frequency of negative confirmation messages when the round-trip delay is greater than a delay threshold; or, when the network status parameter includes a packet loss rate, the sending unit is specifically used to increase the sending frequency of negative confirmation messages or shorten the sending interval of negative confirmation messages when the packet loss rate is higher than a packet loss rate threshold.
[0016] In one embodiment, the reference factor includes the type of data packet, and the types of data include key frame data packet, incremental frame data packet, newly lost data packet or requested retransmission data packet; the sending unit is specifically used to increase the sending frequency of negative confirmation messages or shorten the sending interval of negative confirmation messages when the type of the data packet is a key frame data packet; or, when the type of the data packet is an incremental frame data packet, maintain or reduce the sending frequency of negative confirmation messages; or, when the type of the data packet is a newly lost data packet, reduce the sending frequency of negative confirmation messages or increase the sending interval of negative confirmation messages; or, when the type of the data packet is a requested retransmission data packet, increase the sending frequency of negative confirmation messages or shorten the sending interval of negative confirmation messages.
[0017] In one embodiment, the sending unit is specifically used to send a negative confirmation message with a period less than one round-trip delay, wherein the negative confirmation message is also used to instruct the sending end device to increase the frequency of sending retransmission data packets.
[0018] In one embodiment, the reference factor includes a predicted packet loss situation; the sending unit is specifically configured to send the negative confirmation message when the predicted packet loss probability meets a retransmission condition, the negative confirmation message including a sequence number of a predicted lost packet.
[0019] In one embodiment, the sequence number of the predicted lost data packet includes a sequence number subsequent to the sequence number of the latest received datagram.
[0020] In a third aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, and when the program is executed by a processor, the method described in the first aspect and any one of the embodiments of the first aspect can be implemented.
[0021] In a fourth aspect, an embodiment of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the method described in the first aspect and any one of the embodiments of the first aspect can be implemented.
[0022] In a fifth aspect, an embodiment of the present application provides a computer program product, wherein the computer program product includes a computer program, wherein when the computer program is executed by a processor, it can implement the method described in the first aspect and any one of the embodiments of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] In order to more clearly illustrate the technical solution of an embodiment of the present application, the drawings required for use in an embodiment of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.
[0024] Figure 1 A schematic diagram of a real-time communication system provided for one embodiment of the present application;
[0025] Figure 2 A flow chart of a method for sending a negative confirmation message in a conference provided by one embodiment of the present application;
[0026] Figure 3 A schematic diagram of a device for sending a negative confirmation message in a conference provided by one embodiment of the present application;
[0027] Figure 4 A schematic diagram of an electronic device is provided for one embodiment of the present application. DETAILED DESCRIPTION
[0028] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.
[0029] The NACK mechanism works as follows:
[0030] After receiving the data packet, the receiver will check the sequence number to determine whether there is any lost data packet. The sequence number is a continuous value used to identify the order of data packets. If the receiver finds that the sequence number of a data packet is not continuous, it means that a data packet is lost.
[0031] If a packet is lost, the receiver will send a NACK message to the sender, indicating that the lost packet needs to be resent. The NACK message contains the sequence number information of the lost packet, so that the sender can know exactly which packets need to be resent.
[0032] After receiving the NACK message, the sender will resend the lost data packet according to the receiver's request.
[0033] After receiving the resent data packets, the receiver will insert them into the correct order to restore the lost data. In this way, smooth audio and video playback can be guaranteed even under poor network conditions.
[0034] In existing solutions, in order to ensure data continuity and video fluency as much as possible, the receiving end usually uses efficient NACK messages to request retransmission when packet loss occurs. However, this single NACK message sending method may affect the quality of real-time communication.
[0035] Therefore, how to provide a method for sending a negative confirmation message to solve the problem of sending a single NACK message in the prior art has become a problem that needs to be solved.
[0036] In view of the above problems, the present application provides a method for sending a negative confirmation message in a conference, which can solve the communication quality problem caused by simply and efficiently sending NACK messages to request retransmission in the prior art.
[0037] In the following, for the sake of ease of understanding and explanation, as an example but not a limitation, the execution process and actions of the method for sending a negative confirmation message in a conference of the present application in a real-time communication system are explained.
[0038] The following is combined with Figure 1 The overall structure of a real-time communication system provided by an embodiment of the present application is exemplified.
[0039] like Figure 1As shown, one embodiment of the present application provides a real-time communication system including: multiple clients and a media server.
[0040] In the embodiment of the present application, the media server can be used to receive the uplink media stream sent by the client and can also be used to send the downlink media stream to the client. Among them, the body server can be an MCU server in the multipoint conferencing unit (MCU) architecture, or it can be an SFU in the selective forwarding unit (SFU) architecture, and the real-time example of the present application is not limited to this.
[0041] In the embodiments of the present application, the client may also be referred to as a user terminal or user equipment or terminal equipment. In the real-time embodiments of the present application, the terminal equipment may be installed with a browser, and real-time communication may be performed through the browser, or an APP or applet may be installed, and real-time communication may be performed through the APP or applet. In the present application, the terminal equipment may include a smart phone, a tablet computer (personal digital assistant, PDA), a computer, a game console, a wearable device, a tablet computer (portable android device, PAD), etc., and the embodiments of the present application are not limited thereto.
[0042] It should be understood that Figure 1 In the communication system scenario shown in , only two clients are illustrated, but the embodiments of the present application are not limited to this. In an actual real-time communication scenario, the number of clients may include any number and may be determined according to the actual number of participating terminals.
[0043] It should also be understood that, for uplink transmission, the data packet sender hereinafter may be a client, and the corresponding receiving end may be a media server; for downlink transmission, the data packet sender hereinafter may be a media server, and the corresponding receiving end may be a client.
[0044] The following is combined with Figure 2 A method for sending a negative confirmation message in a conference provided by an embodiment of the present application is exemplarily described.
[0045] like Figure 2 The method shown is applied to Figure 1 In the real-time communication system shown, Figure 2 The methods shown include:
[0046] 210. Determine reference factors that affect sending a negative confirmation message, where the reference factors include network status parameters, data packet types, or predicted data packet loss conditions.
[0047] It should be understood that network status parameters may include round-trip time (RTT) or packet loss rate. Among them, RTT refers to the time from the sender sending data to the sender receiving the confirmation message from the receiver. RTT delay is usually determined by three parts: the propagation time of the link, the processing time of the end system, and the cache and queuing time of intermediate network nodes such as routers. Under normal circumstances, the transmission time and application processing time of the message are relatively fixed. In the case of network congestion, the RTT delay will fluctuate. An increase in RTT usually indicates high network latency or congestion. The packet loss rate refers to the ratio of the number of lost data packets to the total number of data packets sent. An increase in the packet loss rate indicates that the network condition is poor.
[0048] The types of data packets may include key frame data packets, incremental frame data packets (also called difference frame data packets), newly lost data packets, or requested retransmission data packets. Among them, the newly lost data packets are data packets that have been found to be lost but have not been requested to be retransmitted through a NACK message, and the requested retransmission data packets include data packets that have been requested to be retransmitted through an NCAC message.
[0049] The predicted packet loss situation may refer to the loss probability of the unreceived packet predicted by the receiver, or may refer to the situation of whether the unreceived packet predicted by the receiver is lost.
[0050] It should be understood that in the real-time example of the present application, how to send a negative confirmation message can be determined based on any one of the reference factors, or how to send a negative confirmation message can be determined based on multiple factors.
[0051] 220. Send a negative confirmation message according to the reference factor, wherein the negative confirmation message includes a sequence number of the lost data packet, and the negative confirmation message is used to instruct the sending end device to retransmit the lost data packet.
[0052] The embodiment of the present application sends a negative confirmation message based on the reference factors that affect the sending of the negative confirmation message, thereby solving the problem that the single method of sending a NACK message in the prior art may affect the quality of the real-time video conference. The embodiment of the present application can flexibly determine the sending of the negative confirmation message based on specific reference factors, thereby improving the quality of the real-time video conference.
[0053] It should be understood that the method of sending a negative confirmation message in the embodiment of the present application is different depending on the reference factors. The following will illustrate the method of sending a negative confirmation message in the real-time example of the present application with examples for the cases where the reference factors are the above-mentioned factors.
[0054] Case 1: the reference factor includes the network status parameter, and the network status parameter includes round-trip delay or packet loss rate;
[0055] Wherein, the network status parameter includes a round trip delay, and sending a negative confirmation message according to the reference factor includes:
[0056] When the round trip delay is greater than the delay threshold, the sending frequency of negative confirmation messages is reduced.
[0057] Specifically, if bandwidth permits, the existing solution should ensure that retransmissions can be made up as much as possible, using bandwidth redundancy as compensation. However, too many NACKs are also a burden on the source and link, and the sender may not respond to too many requests. Generally speaking, in WEBRTC, after receiving a NACK request and having sent the RTP of the relevant sequence number, it will not respond to the NACK retransmission request of the relevant sequence number that has been sent within at least one RTT. In addition, if the bandwidth is too small, too many retransmitted historical packets will affect the transmission of newly generated packets later, causing the video to become increasingly stuck.
[0058] In the embodiment of the present application, the NACK sending frequency can be reduced when the RTT is high to avoid excessive retransmission requests. For example, in the embodiment of the present application, the NACK sending period can be no less than RTT / 2 and no more than one RTT. Since the sending frequency is low, the delay will increase; if the sending frequency is too high, the source will not respond. Considering that the NACK data sent by the data receiving end received by the data generating end may also be lost, the NACK sending period can be set to RTT / 2 in the embodiment of the present application, but the embodiment of the present application is not limited to this.
[0059] Alternatively, when the network status parameter includes a packet loss rate, sending a negative confirmation message according to the reference factor includes:
[0060] When the packet loss rate is higher than the packet loss rate threshold, the sending frequency of the negative confirmation message is increased or the sending interval of the negative confirmation message is shortened.
[0061] When the packet loss rate is high, the embodiments of the present application can increase the NACK sending frequency or shorten the NACK sending interval. In this way, even if the NACK message sent by the receiving device is lost, since the embodiments of the present application increase the sending frequency or shorten the sending interval, this can improve the effectiveness of NACK transmission and facilitate the sending device to retransmit the lost data packets.
[0062] Further, as another embodiment, increasing the sending frequency of negative confirmation messages or shortening the sending interval of negative confirmation messages includes:
[0063] A negative confirmation message is sent with a period less than one round trip delay, wherein the negative confirmation message is also used to instruct the sending end device to increase the frequency of sending retransmission data packets.
[0064] Specifically, the receiving device sends a NACK message at a period less than one RTT to increase the probability of successful reception of the NACK. Further, as another embodiment, the NACK message sent by the receiving device can also be used to instruct the sending device to increase the frequency of sending retransmission data packets. For example, the sending device can send lost data packets at an interval less than one RTT, or the sending device can send two copies of the data packet each time. The sending device increases the frequency of sending retransmission data packets or sends multiple lost retransmission data packets at one time to increase the retransmission success rate of the retransmission data packets.
[0065] Case 2: the reference factor includes the type of data packet, and the type of data packet includes a key frame data packet, an incremental frame data packet, a newly lost data packet, or a data packet for which retransmission has been requested;
[0066] The sending of a negative confirmation message according to the reference factor comprises:
[0067] When the type of the data packet is a key frame data packet, increasing the sending frequency of the negative confirmation message or shortening the sending interval of the negative confirmation message;
[0068] Alternatively, when the type of the data packet is an incremental frame data packet, maintaining or reducing the sending frequency of negative confirmation messages;
[0069] Alternatively, when the type of the data packet is a newly lost data packet, reducing the sending frequency of the negative confirmation message or increasing the sending interval of the negative confirmation message;
[0070] Alternatively, when the type of the data packet is a data packet for which retransmission has been requested, the frequency of sending negative confirmation messages is increased or the interval of sending negative confirmation messages is shortened.
[0071] In video coding and decoding technology, video frames are divided into key frames and incremental frames. Key frames play a key role in coding and decoding. If the key frame and incremental frame data packets are requested to be retransmitted indiscriminately according to the same weight, even if the RTP of the subsequent incremental frame arrives, all the incremental frames that refer to it cannot be decoded due to the incomplete key frame. Therefore, in order to increase the decoding success rate, in the embodiment of the present application, the frequency of NACK retransmission of key frame data packets is increased or the sending time interval is shortened; the sending frequency of NACK of incremental frame data packets is maintained or reduced.
[0072] Optionally, when the type of data packet is a newly lost data packet, there may be a reception delay. The embodiment of the present application can reduce the waste of resources by reducing the sending frequency of the corresponding NACK message or increasing the sending interval.
[0073] Optionally, when the type of the data packet is a data packet for which retransmission has been requested, since retransmission has been requested but has not been received, considering the timeliness of real-time video conferencing, the data packet needs to be received in a fixed time window to ensure the validity and continuity of the video. Therefore, the embodiment of the present application increases the sending frequency of NACK messages or shortens the sending interval of NCAC messages in order to achieve the retransmission of lost data in the shortest possible time. The specific method of increasing the sending frequency of NACK messages or shortening the sending interval of NCAC messages can be referred to the description above and will not be repeated here.
[0074] Case 3, the reference factor includes predicted packet loss;
[0075] The sending of a negative confirmation message according to the reference factor comprises:
[0076] When the predicted probability of data packet loss meets the retransmission condition, the negative confirmation message is sent, and the negative confirmation message includes the sequence number of the data packet predicted to be lost.
[0077] Optionally, as another embodiment, the sequence number of the predicted lost data packet includes a sequence number subsequent to the sequence number of the latest datagram received.
[0078] The existing packet loss confirmation mechanism in WEBRTC is that when the RTP data packet is received for the first time, the sequence number (Sequence Number) of the current data packet is recorded as the last sequence number (lastSeq). After each packet is received, the new packet sequence number is compared with the above last sequence number. If the sequence number of the new packet is > lastSeq+1, the system considers that the middle packet is lost. The sequence number in the interval [lastSeq+1, Seq] is placed in the queue of lost requests, and lastSeq is updated at the same time. If a packet in the interval [lastSeq+1, Seq] is received later, the system will delete the sequence number of the packet from the queue of requests. However, after receiving a new packet in this way, the receiving end can only find out whether there is packet loss by comparing the sequence number of the new packet with lastSeq. It is impossible to find out packet loss in time or too early. That is, the existing technology needs to wait until the next valid packet to realize whether there is packet loss. For real-time video conferencing, this will reduce real-time performance and increase latency. In response to this situation, the embodiment of the present application can predict whether there is packet loss. If the predicted probability of packet loss is high, retransmission can be requested in advance. In this way, timeliness can be improved and delay can be reduced.
[0079] Optionally, as another embodiment, the embodiment of the present application can predict whether there is packet loss in a variety of ways. For example, when the RTT delay increases, the receiving device of the present application can request NACK and send a certain number of sequence numbers after lastSeq to the sending device to realize early request for retransmission.
[0080] Optionally, in an embodiment of the present application, the receiving end device may use a reverse detection protocol. For example, the receiving end sends a data packet (for example, sends a reference signal). By receiving the response of the sending end, the receiving end can determine the RTT time. By continuously detecting the receiving end device, the RTT situation can be determined, and then when the RTT delay increases, the receiving end device can send a NACK message in advance. Correspondingly, after receiving the NACK, the sending end device determines whether the corresponding data packet has been sent before. If it has been sent before, it can be retransmitted. If the corresponding data packet has not been produced or sent after receiving the NACK, this situation corresponds to an inaccurate prediction of the receiving end device, or the prediction of packet loss is too advanced. The sending end device can directly discard the NACK message without processing.
[0081] Please refer to Figure 3 , Figure 3 A block diagram showing the composition of an apparatus for sending a negative confirmation message in a conference provided by an embodiment of the present application is shown. Figure 3 The device 300 shown can be applied to a data packet receiving end, or the device 300 is a data packet receiving end. It should be understood that the device 300 corresponds to the data packet receiving end in the above-mentioned method embodiment, and can execute the various steps performed by the data packet receiving end involved in the above-mentioned method embodiment. The specific functions of the device 300 can be found in the description above. To avoid repetition, the detailed description is appropriately omitted here.
[0082] Figure 3 The device 300 shown includes at least one software function module that can be stored in a memory or fixed in the device in the form of software or firmware. Figure 3 The device 300 shown includes: a determination unit 310, used to determine reference factors that affect the sending of a negative confirmation message, the reference factors including network status parameters, the type of data packet or predicted data packet loss; a sending unit 320, used to send a negative confirmation message according to the reference factors, the negative confirmation message including the sequence number of the lost data packet, and the negative confirmation message is used to instruct the sending end device to retransmit the lost data packet.
[0083] In one embodiment, the reference factor includes the network status parameter, and the network status parameter includes a round-trip delay or a packet loss rate; wherein, when the network status parameter includes a round-trip delay, the sending unit is specifically used to reduce the sending frequency of negative confirmation messages when the round-trip delay is greater than a delay threshold; or, when the network status parameter includes a packet loss rate, the sending unit is specifically used to increase the sending frequency of negative confirmation messages or shorten the sending interval of negative confirmation messages when the packet loss rate is higher than a packet loss rate threshold.
[0084] In one embodiment, the reference factor includes the type of data packet, and the types of data include key frame data packet, incremental frame data packet, newly lost data packet or requested retransmission data packet; the sending unit is specifically used to increase the sending frequency of negative confirmation messages or shorten the sending interval of negative confirmation messages when the type of the data packet is a key frame data packet; or, when the type of the data packet is an incremental frame data packet, maintain or reduce the sending frequency of negative confirmation messages; or, when the type of the data packet is a newly lost data packet, reduce the sending frequency of negative confirmation messages or increase the sending interval of negative confirmation messages; or, when the type of the data packet is a requested retransmission data packet, increase the sending frequency of negative confirmation messages or shorten the sending interval of negative confirmation messages.
[0085] In one embodiment, the sending unit is specifically used to send a negative confirmation message with a period less than one round-trip delay, wherein the negative confirmation message is also used to instruct the sending end device to increase the frequency of sending retransmission data packets.
[0086] In one embodiment, the reference factor includes a predicted packet loss situation; the sending unit is specifically configured to send the negative confirmation message when the predicted packet loss probability meets a retransmission condition, the negative confirmation message including a sequence number of a predicted lost packet.
[0087] In one embodiment, the sequence number of the predicted lost data packet includes a sequence number subsequent to the sequence number of the latest received datagram.
[0088] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the device described above can refer to the corresponding process in the aforementioned method, and will not be described in detail here.
[0089] like Figure 4As shown, an embodiment of the present application provides an electronic device 400, which includes: a memory 410, a processor 420, and a computer program stored in the memory 410 and executable on the processor 420, wherein the processor 420 reads the program from the memory 410 through a bus 430 and executes the program to implement the method performed by the data packet receiving end in any of the above embodiments. Optionally, Figure 4 The device shown may also include a transceiver, which may be used to send and / or receive data streams. Figure 4 The device shown may also include a collector, which may be used to collect audio / video data. The optional electronic device 400 may also include other input devices or other hardware devices, etc., but the embodiments of the present application are not limited thereto.
[0090] Processor 420 can process digital signals and can include various computing structures, such as complex instruction set computer structure, reduced instruction set computer structure, or a structure that implements a combination of multiple instruction sets. In some examples, processor 420 can be a microprocessor.
[0091] The memory 410 may be used to store instructions executed by the processor 420 or data related to the execution of instructions. These instructions and / or data may include codes for implementing some or all functions of one or more modules described in the embodiments of the present application. The processor 420 of the disclosed embodiment may be used to execute instructions in the memory 410 to implement the method shown above to be executed by the control end or the client. The memory 410 includes a dynamic random access memory, a static random access memory, a flash memory, an optical memory, or other memory known to those skilled in the art.
[0092] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, can implement the method performed by a data packet receiving end in any of the above methods provided in the above embodiments.
[0093] An embodiment of the present application further provides a computer program product, which includes a computer program, wherein when the computer program is executed by a processor, it can implement the method performed by the data packet receiving end in any of the above methods provided in the above embodiments.
[0094] It should be noted that the processor in the embodiment of the present invention (eg, Figure 4The processor in the embodiment of the present invention may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above method embodiment may be completed by an integrated logic circuit of hardware in the processor or an instruction in software form. The above processor may be a general processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The methods, steps and logic block diagrams disclosed in the embodiments of the present invention may be implemented or executed. The general processor may be a microprocessor or the processor may be any conventional processor, etc. The software module may be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
[0095] It can be understood that the memory in the embodiment of the present invention (for example, Figure 4The memory in the memory may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the nonvolatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0096] The application programs involved in the embodiments of the present application include any application installed on the requesting end, including but not limited to browsers, email, instant messaging services, word processing, keyboard virtualization, widgets, encryption, digital rights management, voice recognition, voice replication, positioning (such as functions provided by the global positioning system), music playback, etc.
[0097] It should be understood that the transceiver unit or transceiver in the embodiment of the present invention may also be referred to as a communication unit.
[0098] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instruction is loaded and executed on a computer, the process or function according to the embodiment of the present invention is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instruction can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instruction can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).
[0099] The terms "component", "module", "system", etc. used in this specification are used to represent computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program and / or a computer. By way of illustration, both applications running on a computing device and a computing device can be components. One or more components may reside in a process and / or an execution thread, and a component may be located on a computer and / or distributed between two or more computers. In addition, these components may be executed from various computer-readable media having various data structures stored thereon. Components may, for example, communicate through local and / or remote processes according to signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system and / or a network, such as the Internet interacting with other systems through signals).
[0100] It should be understood that "one embodiment" or "an embodiment" mentioned throughout the specification means that specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present invention. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in various embodiments of the present invention, the size of the sequence number of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.
[0101] In addition, the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.
[0102] It should be understood that in the embodiment of the present invention, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.
[0103] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.
[0104] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0105] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or can be electrical, mechanical or other forms of connection.
[0106] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of the present invention.
[0107] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0108] In short, the above is only a preferred embodiment of the technical solution of the present invention, and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims
1. A method for sending a negative confirmation message in a conference, characterized in that: Applied to a data packet receiving end, the method comprises: Determining reference factors affecting sending a negative confirmation message, the reference factors comprising network status parameters, types of data packets, or predicted data packet loss conditions; A negative confirmation message is sent according to the reference factor, the negative confirmation message includes the sequence number of the lost data packet, and the negative confirmation message is used to instruct the sending end device to retransmit the lost data packet.
2. The method according to claim 1, characterized in that The reference factors include the network status parameters, and the network status parameters include round-trip delay or packet loss rate; Wherein, the network status parameter includes a round trip delay, and sending a negative confirmation message according to the reference factor includes: When the round-trip delay is greater than the delay threshold, reducing the frequency of sending negative confirmation messages; Alternatively, when the network status parameter includes a packet loss rate, sending a negative confirmation message according to the reference factor includes: When the packet loss rate is higher than the packet loss rate threshold, the sending frequency of the negative confirmation message is increased or the sending interval of the negative confirmation message is shortened.
3. The method according to claim 1, characterized in that The reference factors include the type of data packets, and the types of data packets include key frame data packets, incremental frame data packets, newly lost data packets, or data packets for which retransmission has been requested; The sending of a negative confirmation message according to the reference factor comprises: When the type of the data packet is a key frame data packet, increasing the sending frequency of the negative confirmation message or shortening the sending interval of the negative confirmation message; or, When the type of the data packet is an incremental frame data packet, maintaining or reducing the sending frequency of negative confirmation messages; or, When the type of the data packet is a newly lost data packet, reducing the sending frequency of the negative confirmation message or increasing the sending interval of the negative confirmation message; or, When the type of the data packet is a retransmission requested data packet, the sending frequency of the negative confirmation message is increased or the sending interval of the negative confirmation message is shortened.
4. The method according to claim 2 or 3, characterized in that: Increasing the sending frequency of negative confirmation messages or shortening the sending interval of negative confirmation messages includes: A negative confirmation message is sent with a period less than one round trip delay, wherein the negative confirmation message is also used to instruct the sending end device to increase the frequency of sending retransmission data packets.
5. The method according to claim 1, characterized in that The reference factors include predicted packet loss conditions; The sending of a negative confirmation message according to the reference factor comprises: When the predicted probability of data packet loss meets the retransmission condition, the negative confirmation message is sent, and the negative confirmation message includes the sequence number of the data packet predicted to be lost.
6. The method according to claim 5, characterized in that The sequence numbers of the data packets predicted to be lost include sequence numbers subsequent to the sequence number of the latest datagram received.
7. A device for sending a negative confirmation message in a conference, characterized in that: Applied to a data packet receiving end, the device comprises: A determination unit, configured to determine reference factors affecting the sending of a negative confirmation message, wherein the reference factors include network status parameters, types of data packets, or predicted data packet loss conditions; A sending unit is used to send a negative confirmation message according to the reference factor, wherein the negative confirmation message includes a sequence number of a lost data packet, and the negative confirmation message is used to instruct a sending end device to retransmit the lost data packet.
8. An electronic device, characterized in that: The method comprises a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the computer program executes the method according to any one of claims 1 to 6 when being run by the processor.
9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program executes the method according to any one of claims 1 to 6 when executed by a processor.
10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.
