WO2019214550A1 - Message transmission method, device and system, storage medium and electronic apparatus - Google Patents

Abstract

Provided are a message transmission method, device and system, and a storage medium and an electronic apparatus, wherein the method comprises: receiving a serial number, sent by a first device, of a lost message, wherein the serial number of the lost message is used for indicating the serial number of the lost message among messages sent to the first device by a second device; conducting a deduplication operation on the serial number of the lost message to obtain a set of serial numbers of lost messages; and sending the set of serial numbers of lost messages to the second device. By means of the present disclosure, the technical problem in the relevant art of the time it takes to process a lost message being too long is solved.

Description

Message transmission method and device, system, storage medium, electronic device Technical field

The present disclosure relates to the field of communications, and in particular, to a message transmission method and apparatus, system, storage medium, and electronic device.

Background technique

In network applications, multicast is widely used as an efficient transmission scheme for video transmission, message distribution, and file push. The mainstream multicast scheme is based on the connectionless UDP (User Data Protocol) protocol. The original data packet is encapsulated and distributed and transmitted in the network device in a multicast manner. Due to the unreliability of multicast transmission, packet loss or bit error is likely to occur when the network is abnormal, and error correction compensation must be performed to ensure reliable data transmission. In the field of video services such as IPTV (Internet Protocol Television) and video conferencing, the multicast transmission scheme in the related art is UDP multicast + FEC (Forward Error Correction): for media data, transmission In addition to transmitting the multicast original data, the terminal also performs FEC error correction coding on the media content, and sends the FEC error correction message. The receiving end can receive the original data packet and the FEC packet of the media content at the same time, for packet loss or error. The original data packet of the code, the receiving end uses the FEC error correction message to restore the original message, thereby greatly improving the quality of the media content transmission. Problems with the UDP multicast + FEC scheme: FEC redundant packets can only provide partial redundancy. When the packet loss rate of the original data packet exceeds the redundancy of the FEC, the FEC error correction packet cannot still perform data. Restore; if the FEC error correction data packet is lost, the receiving end will not be able to restore the original data packet.

In order to achieve more efficient and reliable multicast transmission, the IETF (The Internet Engineering Task Force) proposed a reliable multicast protocol NORM (NACK-based based on NACK (Negative Acknowledge) mechanism). Oriented Reliable Multicast Transport Protocol), the main idea is that, under normal circumstances, the sender encapsulates the transmission data based on the UDP+FEC protocol, and transmits it by multicast. The receiver receives the original data and the FEC error correction data, and according to the message. The sequence number is detected by packet loss. If there is no packet loss, FEC error correction, decoding, and service presentation are performed. If there is packet loss, the receiver sends a NACK (negative acknowledgement) message to the sender, thereby losing the multicast. The sequence number of the packet is sent to the sender. The sender sends a repair packet to the specified original data packet or the FEC error correction packet according to the packet loss packet number in the NACK request. When the receiver receives the repair packet, the receiver performs the repair packet. Data reorganization, in order to achieve reliable data transmission.

Compared with the UDP multicast + FEC error correction transmission scheme, the NORM reliable multicast transmission scheme introduces a packet loss retransmission and congestion control mechanism similar to TCP (Transport Control Protocol), which is far better than UDP in terms of transmission reliability. The multicast + FEC scheme makes NORM suitable for more transmission scenarios. Currently, NORM can be applied to business scenarios such as IPTV live broadcast, OTT (Over The Top) live broadcast, digital video broadcast (DVB) live broadcast, distributed message queue, file distribution, web red live broadcast, video conference, online game. , military command system, and so on. The well-known open source message queue ZeroMQ supports the use of NORM as a transport protocol. CableLabs' IPTV specification also defines NORM as a standard protocol for media transmission, and its market value is getting higher and higher.

There is also a problem with the reliable multicast transmission mechanism of NORM. As shown in FIG. 1, FIG. 1 is a schematic diagram of a NORM reliable multicast transmission mechanism in the related art of the present disclosure.

If the abnormal transmission or the jitter of the key transmission device occurs between the NORM sender and the receiver, a large number of receivers will detect the packet loss at the same time, and send a large number of NACKs with the same packet loss packet number to the sender to form a message storm. There is a processing performance bottleneck on the sender side. At the same time, the NORM protocol requires the sender to have a repair window with a certain delay of the NACK. That is, the sender needs to collect NACK packets from different receivers in a period of time, perform deduplication processing, and then combine the packet loss packets. , send repair message. In order to avoid sending duplicate repair packets as much as possible, the sender needs to set a relatively long time window to process NACK packets, which delays the time for repairing the packets. For the receiving end, the delay of packet packet repair is relatively large, which may lead to a decline in service quality. Typically, in a video service scenario, the video screen on the terminal is likely to be screened or frame skipped, which affects the viewing experience. As the number of receivers increases, this problem becomes more apparent. This feature of the NORM transmission mechanism limits the number of receiving ends that a NORM sender can support, and cannot support large-scale users such as IPTV/OTT.

In view of the above problems in the related art, no effective solution has been found yet.

Summary of the invention

Embodiments of the present disclosure provide a message transmission method and device, system, storage medium, and electronic device.

According to an embodiment of the present disclosure, a message transmission method is provided, including: receiving a sequence number of a lost message sent by a first device, where a sequence number of the lost message is used to indicate that the message is sent to the second device Deleting the sequence number of the packet in the packet of the first device; performing a deduplication operation on the sequence number of the lost packet to obtain a lost packet sequence number set; and sending the lost packet sequence number set to the second device.

According to another embodiment of the present disclosure, a message transmission apparatus is provided, including: a receiving module, configured to receive a sequence number of a lost message sent by a first device, where a sequence number of the lost message is used to indicate The sequence number of the lost message in the packet sent by the second device to the first device; the processing module is configured to perform a deduplication operation on the sequence number of the lost packet to obtain a lost message sequence number set; and the sending module is set to Sending the lost message sequence number set to the second device.

According to still another embodiment of the present disclosure, a message transmission system is provided, including one or more first devices, a second device, and a filtering device, wherein the first device is configured to receive the second device The original packet, and the packet loss detection packet is sent to the filtering device when the packet loss detection is performed on the original packet, and the filtering device includes: a receiving module, configured to receive The sequence number of the lost packet sent by the first device, where the sequence number of the lost packet is used to indicate the sequence number of the packet lost in the packet sent by the second device to the first device; The sequence of the lost message is subjected to a deduplication operation to obtain a lost message sequence number set; the sending module is configured to send the lost message sequence number set to the second device; and the second device is set to The first device sends the original message, and receives the lost message sequence number set.

According to still another embodiment of the present disclosure, there is also provided a storage medium having stored therein a computer program, wherein the computer program is configured to execute the steps of any one of the method embodiments described above at runtime.

According to still another embodiment of the present disclosure, there is also provided an electronic device comprising a memory and a processor, wherein the memory stores a computer program, the processor being configured to execute the computer program to perform any of the above The steps in the method embodiments.

Through the disclosure, the de-duplication operation is performed on the sequence number of the lost packet, and the number of the sequence number of the same lost packet is reduced and then sent to the second device to avoid forming a message storm on the second device, which solves the problem of processing loss in the related art. The technical problem that the packet time is too long reduces the filtering workload of the second device for the serial number of the lost packet, thereby improving the efficiency of the second device for sending the repair packet for the lost packet, and reducing the loss of the first device repair report. The delay of the text.

DRAWINGS

The drawings described herein are provided to provide a further understanding of the present disclosure, which is a part of the present disclosure, and the description of the present disclosure and the description thereof are not intended to limit the disclosure. In the drawing:

1 is a schematic diagram of a NORM reliable multicast transmission mechanism in the related art of the present disclosure;

2 is a flowchart of a message transmission method according to an embodiment of the present disclosure;

FIG. 3 is a structural block diagram of a message transmission apparatus according to an embodiment of the present disclosure; FIG.

4 is a structural block diagram of a message transmission system according to an embodiment of the present disclosure;

Figure 5 is a schematic diagram of reliable multicast communication in the embodiment;

6 is a working principle diagram of a system for reliable multicast communication according to the embodiment;

7 is a flowchart of a method for implementing reliable multicast communication according to this embodiment;

FIG. 8 is a block diagram showing the internal structure of a reliable multicast NACK filtering apparatus according to this embodiment; FIG.

9 is a system structural diagram of implementing reliable multicast message distribution in scenario one;

10 is a flow chart of implementing reliable multicast message distribution in scenario one;

11 is a structural diagram of a NORM-based OTT live broadcast service system in scenario 2 of the present embodiment;

12 is a flowchart of NORM-based OTT live content distribution in scenario 2 of the present embodiment;

13 is a structural diagram of a NORM-based IPTV live broadcast system in the third embodiment of the present invention;

14 is a flowchart of a NORM-based IPTV live broadcast service in the third scenario of the present implementation;

15 is a structural diagram of a multi-stage NORM filtering device system of the fourth embodiment of the present invention;

16 is a flow chart of message processing of a multi-level NORM filtering device in scenario 4 of the present embodiment.

detailed description

The present disclosure will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

It is to be understood that the terms "first", "second", and the like in the specification and claims of the present disclosure are used to distinguish similar objects, and are not necessarily used to describe a particular order or order.

Example 1

The network architecture that can be run by the embodiment of the present application includes: one or more first devices, and a second device, where the first device interacts with the second device, and the second device sends a service packet or original to the first device. After receiving the service packet or the original packet, the first device detects the lost packet in the transmission process or the lost packet that is not received, and initiates a feedback process to the second device.

In this embodiment, a message transmission method running on the network architecture is provided. FIG. 2 is a flowchart of a message transmission method according to an embodiment of the present disclosure. As shown in FIG. 2, the process includes the following steps:

Step S202: Receive a sequence number of the lost packet sent by the first device, where the sequence number of the lost packet is used to indicate the sequence number of the lost packet in the packet sent by the second device to the first device.

Step S204: Perform a deduplication operation on the sequence number of the lost message to obtain a lost message sequence number set.

Step S206: Send the lost message sequence number set to the second device.

Through the above steps, the de-duplication operation is performed on the sequence number of the lost packet, and the number of the sequence number of the same lost packet is reduced and then sent to the second device to avoid forming a message storm on the second device, which solves the problem of processing loss in the related art. The technical problem that the packet time is too long reduces the filtering workload of the second device for the serial number of the lost packet, thereby improving the efficiency of the second device for sending the repair packet for the lost packet, and reducing the loss of the first device repair report. The delay of the text.

Optionally, the execution body of the foregoing steps may be a server, a function module, or the like, and may be disposed between the communication link of the first device and the second device, or integrated on the second device, but is not limited thereto. The de-duplication operation can delete the sequence number of the duplicate lost message. The total number of the sequence number after the re-operation is less than the total number of the sequence number before the de-duplication operation. For example, before the de-duplication operation, the sequence number 1, the sequence number 2, and the sequence number 3 are respectively 5, 2, and 3 After de-duplication operation, the serial number 1, the serial number 2, and the serial number 3 may only exist 2, 1, and 2 respectively, and the total number is 5 less than the previous 10. In a special case, after the de-duplication operation, the serial number 1, No. 2, No. 3 may exist only 1, 1, 1 respectively, no matter how heavy, No. 1, No. 2, No. 3 have at least one.

In this embodiment, the lost message includes: a message that is not received by the first device within a predetermined time after the second device sends the message. Of course, it may also be a message that needs to be re-received in the case of decoding failure.

Optionally, the second device sends the repair packet to the first device according to the packet loss message indicated by the lost packet sequence number, where the sequence number of the repair packet is from one of the lost packet sequence numbers.

Optionally, after the sending of the lost packet sequence number to the second device, the method further includes: the second device sending the repair message to the first device, where the repair message is indicated by the sequence number in the lost message sequence set. Message. The second device sends the original packet to the first device, where the original packet includes a sequence number that is not repeated, and the first device detects the lost packet according to the sequence number of the original packet, and the sequence number of the packet loss packet sent by the first device. That is, the sequence number of the original packet of the packet loss detected by the first device.

Optionally, receiving the sequence number of the lost packet sent by the first device includes: receiving a NACK packet sent by the one or more first devices, where the NACK packet carries the sequence number of the lost packet.

Optionally, receiving the sequence number of the lost packet sent by the first device includes: receiving the NACK packet sent by the first device, where the NACK packet carries the sequence number of the lost packet. When the lost packet sequence number is sent to the second device, the lost packet sequence number in the lost packet sequence number may also be carried in the NACK packet of the NACK packet set.

Optionally, the NACK packet includes: a NACK packet based on a reliable multicast communication protocol NORM.

Optionally, the packet transmitted between the first device and the second device may be a multicast packet or a unicast packet, and the lost packet includes at least one of the following: a multicast packet and a unicast packet.

Optionally, the de-duplication operation is performed on the sequence number of the lost packet, and the lost message sequence number set is obtained, including the following two strategies:

In the sequence numbers of all the lost packets received in the predetermined time period, there will be duplicate sequence numbers for deduplication, and the non-repeated sequence numbers are reserved, and the lost message sequence number sets are obtained;

According to the historical packet loss sequence number list that has been sent within the predetermined time, in the sequence number of all the lost packets received, the sequence number of the lost packet not included in the history packet loss sequence number is selected, and the lost message sequence number set is obtained. .

Optionally, the sending the lost message sequence number set to the second device includes one of: sending the lost message sequence number set to the second device, and then receiving the ACK information fed back by the second device, where, ACK The information is used to indicate that the second device receives the lost message sequence number set; and sends the lost message sequence number set to the second device according to the preset retransmission times. If the third device can receive the lost message sequence number set, the second device can perform the deduplication operation after receiving the lost message sequence number set.

Optionally, receiving the sequence number of the lost packet sent by the first device includes: receiving a sequence number of the lost packet sent by the first device in the corresponding first region. A plurality of areas may be divided according to the location of the first device, and a filtering device is added to each area for filtering and deduplication, and each filtering device is responsible for receiving the sequence number of the lost message of the first device in the area. The lost message sequence number set may be carried in a NORM-based NACK message.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, portions of the technical solutions of the present disclosure that contribute substantially or to the prior art may be embodied in the form of a software product stored in a storage medium (eg, ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present disclosure.

Example 2

In the embodiment, a message transmission device and a system are provided to implement the foregoing embodiments and preferred embodiments, which are not described again. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 3 is a structural block diagram of a message transmission apparatus according to an embodiment of the present disclosure. As shown in FIG. 3, the apparatus includes:

The receiving module 30 is configured to receive the sequence number of the lost message sent by the first device, where the sequence number of the lost message is used to indicate the sequence number of the lost message in the message sent by the second device to the first device;

The processing module 32 is configured to perform a deduplication operation on the sequence number of the lost message to obtain a lost message sequence number set.

The sending module 34 is configured to send the lost message sequence number set to the second device.

Optionally, the receiving module includes: a receiving unit, configured to receive a NACK message sent by the one or more first devices, where the NACK message carries the sequence number of the lost message.

Optionally, the processing module includes one of the following: the first processing unit is configured to de-duplicate the repeated sequence numbers in the sequence numbers of all the lost messages received in the predetermined time period, to obtain the lost message sequence number set; The second processing unit is configured to select, according to the historical packet loss sequence number list that has been sent within the predetermined time, the sequence number of the lost packet that is not included in the historical packet loss sequence number in the sequence number of all the lost packets received. Get the lost message sequence number set.

FIG. 4 is a structural block diagram of a message transmission system according to an embodiment of the present disclosure. As shown in FIG. 4, the first device 40 includes a first device 40, a filtering device 42, and a second device 44.

The first device 40 is configured to receive the original packet sent by the second device, and send the sequence number of the lost packet to the filtering device when performing packet loss detection on the original packet to determine that there is a lost packet;

The second device 44 is configured to send the original message to the first device, and receive the lost message sequence number set;

The filtering device 42 includes: a receiving module 30, configured to receive a sequence number of the lost packet sent by the first device, where the sequence number of the lost packet is used to indicate that the packet is lost in the packet sent by the second device to the first device The processing module 32 is configured to perform a deduplication operation on the sequence number of the lost message to obtain a lost message sequence number set, and the sending module 34 is configured to send the lost message sequence number set to the second device.

Optionally, the second device further includes: a retransmission module, configured to resend the repair message to the first device, where the repair message is a message indicated by the sequence number in the lost message sequence number set.

Optionally, the first device further includes: an error correction module, configured to receive the repair message, and perform error correction and restoration processing on the data by using the repair message to obtain a complete original message.

Optionally, the retransmission module further includes: a first retransmission unit, configured to determine a message that is lost by each of the one or more first devices; and the repair message is the same as the lost message The message is sent to the corresponding first device; the second resending unit is configured to send the repair message to all the first devices. Only the packets lost by each first device are sent, and the target packets are not filtered again on the first device, which can reduce the workload of the first device. All the repaired packets are sent to all the first devices. The first device can select the modified packets as needed to reduce the workload of the second device, because the first device corresponding to each repair packet is not queried.

It should be noted that each of the above modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination. The forms are located in different processors.

Example 3

This embodiment is an optional embodiment of the present disclosure, and is used to describe the application in detail in conjunction with a specific scenario example:

FIG. 5 is a schematic diagram of reliable multicast communication according to the embodiment. As shown in FIG. 5, the delay and performance problems solved by adding a NACK filtering device between the transmitting end and the receiving end enable better application to a large number of users. Business scene. In this embodiment, by setting up a filtering device between the transmitting end and the receiving end, a plurality of areas can be divided according to the position of the receiving end, and a NACK message filtering device is added to each area, and each filtering device is responsible for receiving the terminal device in the area. The NACK packet is received by the receiving end. The receiving end receives the multicast data packet, and detects the packet loss according to the sequence number of the multicast data packet. If there is a packet loss, the device sends a NACK packet to the filtering device in the area, carrying the sequence number of the lost data packet. The filtering device collects the NACK packet of the terminal in the area, performs deduplication according to the carried sequence number in the NACK packet, obtains the packet sequence number of the packet loss at the receiving end of the local area, and sends a small number of NACK packets to the transmitting end. The sender collects a small number of NACK packets sent by filtering devices in different areas, and then retransmits the lost packets to all receiving ends.

This embodiment provides a reliable multicast communication system, as shown in FIG. 6. FIG. 6 is a working principle diagram of a system for reliable multicast communication according to the embodiment, including a sender, one or more filter nodes, and multiple Data device, multiple receivers.

Transmitter: The source of reliable multicast, which can be a message server, a file server, a video source station, a web server, a central control system, and so on. The sender needs to support the NORM protocol, and can create a NORM group session, which can encapsulate data such as messages, files, and real-time streams into original data such as IP/UDP/RTP and FEC error correction data. The transmitting end can generate a message sequence number for each original data and FEC error correction data, and sequentially send the message to the receiving end in a multicast manner. The sender supports receiving the NACK packet sent by the filtering node, and collects the NACK packet in the different area in a certain time window, and can decrement according to the sequence number of the packet loss packet in the NACK packet, and obtain the packet loss at the receiving end. The sequence number of the packet. Finally, the sender can resend the packet lost at the receiving end in the same NORM group session according to the sequence number list of the packet loss packet. Optionally, depending on the type of the sender, the transmission also supports the transmission of NORM_CMD (including but not limited to CC, EOT, SQUELCH, REPAIR_ADV, FLUSH, reference RFC 5740). The NORM protocol described in this embodiment is exemplified by RFC 5740. In actual applications, the NORM specification is updated. The apparatus, method and system proposed in this embodiment are also applicable to subsequent versions of the RFC NORM protocol. The use of this embodiment based on the new version of NORM is also within the scope of the rights protection.

Filtering device: used to collect and filter NACK requests from the receiving end. The filtering device receives the unicast or multicast NACK packet of all the receiving ends in the area in the area, and can use the time window aggregation filtering mode and the buffer forwarding mode to decrement the number of the lost packet in the NACK packet. The number of lost message sequences of all the receiving ends in the area, and the lost message sequence number can be sent to the sending end in a new NACK message. The filtering device may use a certain redundancy policy to send one or more NACK packets to the sending end, but each packet loss packet, for each received packet number of the received NACK packet. The serial number, the number of times the filtering device sends to the sending end is less than the number of times received. Optionally, the filtering device may perform the unicast to multicast or the multicast to unicast conversion, and then send the NACK packet to the sending end. The filtering device may be in the form of a software module on the data device, or may be a message proxy server, a file distribution server, a real-time stream relay server, a CDN node, a special module on the data device, an SDN controller + an SDN forwarding device, and the like. In the deployment, it can be a level 1 deployment: according to the geographical location, the receiving end of different geographical locations is divided into different areas, one for each area; or multiple levels of deployment, that is, according to the number of receiving ends, data equipment networking, in the network Both the center and the edge are deployed to form a cascade.

One of the redundancy policies, the NORM signaling is extended between the filtering device and the upper entity, and the NORM_INFO message can be specifically referred to, and an ACK message is returned for each NACK message sent by the filtering device, and the filtering device filters the After the NACK message is sent, the ACK of the NACK message is sent to the higher-level entity. After the ACK is acknowledged, the higher-level entity does not retransmit the NACK message containing the packet loss sequence number. Otherwise, the NACK message is retransmitted. N (configurable) times. In the second redundancy policy, the filtering device sets a certain number of retransmissions M (configurable). For the packet loss message number after filtering and deduplication, each sequence number appears in the NACK message sent by the filtering device to the upper entity. Times.

Data equipment: divided into two types, multicast replication devices, and multicast routing networks. The multicast replication device can be deployed in multiple stages. The multicast replication device connected to the sender is mainly used to send multicast packets sent by the sender, and is copied into multiple copies and sent to the lower-level multicast replication device until multicast is enabled. The message is sent to all receivers. A multicast routing network is a network of switches and routers that support unicast and multicast packets. In actual applications, multiple or even multiple levels of data can be deployed between the sending end, the filtering device, and the receiving end. device.

Receiver: Distributed in various areas of the network, supporting multicast packets that use the NORM protocol to receive raw data and FEC error correction data. When receiving the NORM multicast data packet from the sending end, the receiving end may detect whether there is a data packet loss according to the sequence number in the multicast data packet. If the data packet is lost, the receiving end may send a NACK report to the filtering node. And the NACK message includes a sequence number list of the packet loss packet; the receiving end can receive the retransmission repair message sent by the sender, and can use the repair message to perform data restoration. Optionally, the receiving end may further receive the NORM_CMD sent by the sending end (including but not limited to CC, EOT, SQUELCH, REPAIR_ADV, FLUSH, and reference RFC 5740) and perform response processing. The receiving end performs corresponding service presentation on three objects (messages, files, and real-time streams) that can be transmitted to the NORM, and the manner of service presentation includes not limited to message display, file downloading, audio and video playback, and the like. The form of the receiving end may be a message client, a file client, a proxy server, a network device, a computer, a mobile phone, and the like that support the NORM standard protocol.

This embodiment provides a method for implementing reliable multicast communication. FIG. 7 is a flowchart of a method for implementing reliable multicast communication according to the embodiment. As shown in FIG. 7, the method includes:

The sender initializes the multicast address and port configured for the NORM group session:

The sender creates a NORM group session, where the group session uses the multicast address and port defined in step 1;

Multiple receivers join the group communication session as follows:

The receiving end initializes the multicast address and port of the NORM group session, where the multicast address and port are the same as the multicast address and port of the group session created by the sender;

Optionally, the receiving end initializes the filtering device address information of the local area, and is configured to send a unicast NORM_NACK message to the filtering device.

The receiving end joins the NORM group session according to the multicast address and port configured in step 3, and starts to receive the NORM multicast data message NORM_DATA in the session, and the instruction NORM_CMD (including but not limited to CC, EOT, SQUELCH, REPAIR_ADV, FLUSH);

Optionally, the sending end may periodically send a NORM_CMD (FLUSH) command in the group session to notify all receiving ends to send a NACK message.

The NORM multicast packet sending process includes:

In the group session, the sending end uses the UDP to encapsulate the original data packet, and optionally, the sending end further performs FEC encoding on the data to be transmitted according to the redundancy policy, and generates NORM according to a certain order. The serial number of the data packet, and the NORM multicast data packet is sent according to the serial number. The type of the message is NORM_DATA. According to the definition of the NORM protocol, the data may be a data, a file, or a real-time stream. Each NORM data packet includes a corresponding serial number; When the NORM multicast data message is sent, the original data, and the FEC error correction data, may be in a NORM_DATA message or may be divided into different NORM_DATA messages.

The receiving end starts to receive the NORM multicast data packet, and the receiving end detects the packet loss according to the sequence number of the NORM multicast data packet. The multicast data packet sequence number is specifically defined by the NORM_DATA message format in RFC 5740;

The receiving end generates a NORM_NACK packet for the lost multicast data packet, and the NACK packet contains the sequence number of the lost multicast data packet, and the receiving end sends a NORM NACK packet to the filtering device in the local area, where the NACK packet can be The unicast mode (using the filtering device address initialized in step 4) may also be the multicast mode (using the NORM multicast session address initialized in the above step), and the sequence number of the packet loss message is placed in the payload of NORM_NACK. RFC 5740 NORM_NACK definition.

The filtering device NACK filtering, deduplication, conversion and forwarding processes include:

The filtering device receives the NACK packet of different receiving ends in the local area in the time window of length N; in this step, the characteristic of N is relatively small;

The filtering device performs deduplication according to the serial number list of the packet loss packets of the NACK packet sent by the different receiving end;

The filtering device forwards the de-asserted NACK packet to the sender in unicast or multicast mode. In this step, the NACK message sequence number list is a subset of the union of the sequence number lists in the NACK messages of all receiving ends in the local time window.

The process of sending the repair message by the sender includes:

The sender receives NACK packets of different filtering devices in a time window of length M;

The sending end performs deduplication according to the sequence number of the lost multicast data packet sent by the sending end in the NACK packet sent by the filtering device, and obtains a sequence number set of all the receiving packet loss packets in the entire system;

The sender sends the multicast data packet that is lost at the receiving end. The sequence number of the repair packet is the same as the sequence number of the lost multicast packet carried in the NACK packet. The format of the multicast data packet is the same as that of the corresponding sequence number. In the above group session, the repair message is retransmitted, and the retransmission message format is still NORM_DATA. For details, refer to RFC 5740.

The data repair process at the receiving end includes:

The receiving end determines, for each NORM_DATA repair message sent by the sending end, whether the serial number in the repairing message is a multicast data packet lost by the receiving end. If yes, the NORM_DATA repair message is used for data restoration; if not, the receiving end discards the NORM_DATA repair message;

The receiving end performs other processing on the restored complete NORM multicast data packet, and performs service presentation. The form of the service presentation includes but is not limited to, media playback, file downloading, and message distribution.

For the boundaryd data, the transmitting end, the filtering device, and the receiving end repeatedly perform steps 07 to 17 shown in FIG. 7 until the data transmission is completed;

For borderless data, such as real-time streaming, optionally, the receiving end can join the group session at any time, and the sending end can continuously send the NORM data packet without closing the session; for the bounded data, such as messages and files, Between the sender and the receiver, after the data is sent, it also includes a session closure process:

Optionally, for the bordered data, the sending end sends a NORM_CMD (EOT) command to notify all the receiving ends, and the transmission is completed;

The receiving end responds to the NORM_EOT command, waits for the transmission to complete, exits the group session, and returns NORM_ACK;

After all clients, such as the sender, return NORM_ACK, close the group session. So far, the flow of Fig. 7 ends.

The present embodiment provides a NORM NACK filtering device, and FIG. 8 is an internal structure diagram of a reliable multicast NACK filtering device according to the embodiment. As shown in FIG. 8, the NORM filtering device includes:

The sending module 101 sends the filtered and converted NACK message to the upper entity, and the format of the sent NACK message is filtered by the filtering module to obtain the same;

The conversion module 102, the optional module, is configured to perform unicast-to-multicast or multicast-to-unicast processing on the NACK packet after filtering and de-duxing;

The filtering module 103 performs filtering and de-duxing according to the sequence number of the packet loss packet of the NACK packet for the received multiple NACK packets;

The receiving module 104 is configured to receive a unicast or multicast NACK message from a subordinate entity;

With the solution of the present implementation scenario, a NACK filtering device is deployed in each area. When a large number of receiving ends detect packet loss, the NACK packet sent by the receiving end is filtered and de-duplicated by the NACK filtering device in one area. The different terminals are lost with the same data packet. Therefore, the NACK packet processed by the NACK filtering device in the area is greatly reduced. For the transmitting end, only a small number of NACK packets sent by the NACK filtering device in different areas are collected. The sender does not receive NACK packet storms, and the performance processing requirements of the sender are greatly reduced. The performance requirement of the NACK packet processing on the transmitting end is more the number of filtering devices directly related to the sending, and the increase in the number of the receiving end does not directly increase the performance requirement of the transmitting end. After adopting the system, device and method of the embodiment, In the same NORM session, the number of receivers can be greatly improved. Since the NACK filtering device only receives the NACK packet of the receiving end of the area, the number is controllable. Therefore, the NACK filtering device can collect the NACK packet by using a short time window, and the NACK random backoff duration of the receiving end can be small, and the transmitting end can be small. Similarly, because only a small number of NACK packets are received, there is no performance bottleneck, and a small time window can be used to collect NACK packets. Therefore, the sender can send repair messages faster, and the receiving end can receive NORM repair as soon as possible. The message, thereby reducing the delay at the receiving end.

This embodiment can be deployed into different application scenarios from the service scenario and the deployment location.

In the business scenario, NORM has three main categories, messages, files, and live streams. The message business scenarios mainly include: chat room, real-time message push, military command system, etc. (implementation scenario 1); file service scenarios include IPTV on-demand, OTT on-demand, OTT live broadcast, Internet content distribution, etc. (implementation scenario 2); real-time flow The business scenarios include IPTV live broadcast, DVB live broadcast, video conference, global eye monitoring, web red live broadcast, etc. (Scenario 3).

From the perspective of deployment, the location of the filtering device may be located at the network center where the transmitting end is located, or may be distributed with different receiving edges, or may be deployed in multiple layers. For example, filtering devices exist in the network center and the network edge. The NORM filtering device receives the NACK message of the receiving end, which may be a unicast mode or a multicast mode. For the multicast NACK packet sent by the receiving end, the NORM filtering device may be converted into a unicast mode after being deduplicated. Forward to the sender to support long-distance deployment scenarios. Implementation scenario 4 shows a level 2 filtering device and performs a NACK multicast to unicast conversion. The following is a detailed description:

Implementation scenario one

The message is distributed using NORM multicast. The message multicast message is not FEC-encoded. After receiving the NACK, the sender directly retransmits the original data packet. All receivers receive all the messages synchronously and display them.

9 is a system structure diagram of implementing reliable multicast message distribution in scenario 1, as shown in FIG. 9. In this implementation scenario, one message server is deployed as a NORM sender in the present disclosure; an intermediate server is set up as the present disclosure. The NACK filtering device proposed in the present invention; two message clients (1 and 2) are set up to be used as the NORM receiving end in the present disclosure, and the multicast address of the message is 221.1.1.1:8080; deployed in the area of the user network edge One multicast router acts as a multicast replication device.

FIG. 10 is a flowchart of implementing reliable multicast message distribution in scenario 1. As shown in FIG. 10, the message distribution process interacts as follows:

701. The message server creates a group session by using the multicast address norm://221.1.1.1:8080;

702. The message client 1 joins the group session with the multicast address norm://221.1.1.1:8080;

703. The message client 2 joins the group session with the multicast address norm://221.1.1.1:8080;

704. The message server encapsulates the message data with the NORM_DATA object, the type of the NORM_DATA is NORM_OBJECT_DATA, and sends 10 messages Message (1 to 10), and the message NORM sequence numbers are 1 to 10 respectively. In the sending process, Messages 4 to 5 cause messages due to network abnormalities. The client 1 loses the packet, and the message 5 to 6 causes the message client 2 to drop packets due to the network abnormality. The other serial number packets are normally sent and received, and the message client 1 and the message client 2 perform display processing for the normal packet.

705. The message client 1 detects the packet loss, and sends a NORM NACK message NACK1 to the intermediate server in a multicast manner, and the NACK1 includes the packet loss sequence numbers 4 and 5;

706. The message client 2 detects the packet loss, and sends a NORM NACK message NACK2 to the intermediate server in a multicast manner, and the NACK2 includes the packet loss sequence numbers 5 and 6;

707. After collecting the NACK1 and NACK2 in the 10ms time window, the intermediate server deduplicates the sequence number, takes the union, and obtains the sequence number, and obtains the message client 1 and the message client 2 packet collection. 4, 5, 6, and then the intermediate server sends NACK3 to the message server, the message payload in NACK3 contains the sequence number 4, 5, 6;

708. The message server receives the NACK3, obtains the message that the client 1 and 2 packet loss is 4, 5, 6, and then resends three original data messages Message4, Message5 and Message6;

709. The message client 1 receives Message4, Message5, and Message6, and uses the retransmitted Message4 and Messag5 to display, and discards the retransmitted Message6, and uses the first thick message of Message6 to display;

710. Message client 2 receives Message4, Message5, Message6, discards the retransmitted Message4, uses Message4 received the first time, and retransmits Message5 and Message6 for display;

711. After all Messages are sent and the presentation is completed, the message client 1 closes the NORM group session;

712. Wait until all Messages are sent and the presentation is complete, the message client 2 closes the NORM group session;

713. The message server closes the NORM group session.

Implementation scenario 2

Distributing one file to a set top box terminal in multiple regions illustrates how the present disclosure is implemented in a business application for file distribution.

11 is a structural diagram of a NORM-based OTT live broadcast service system in the second embodiment of the present invention. As shown in FIG. 11, an OTT service system is deployed. In this implementation scenario, one HLS content source station is deployed as a NORM sender in the present disclosure. Setting up a CDN node with the NACK filtering device function proposed in the present disclosure; setting up two set top box clients (1 and 2) with the NORM receiving end function in the present disclosure. A multicast router is deployed in the area at the edge of the user network as a multicast replication device. The HLS content source station needs to push a video file list File01~10.ts to all set-top box terminals for playback. For each video file 01~10.ts, the HLS content source station loop uses the following steps to know all video file transfers and playback is complete. In this implementation scenario, we describe the multicast distribution process of one of the files in detail, and assume that the first file 01.ts is encoded into 300 NORM multicast packets FilePack001-300, and the set-top box 1 and the intermediate data device are abnormal. The set top box 2 simultaneously generates NACK messages NACK1 and NACK2 for the lost FilePacks 011 to 020, and the list of lost packet numbers included in NACK1 and NACK2 is 11 to 20, which is illustrated.

12 is a flowchart of NORM-based OTT live content distribution in scenario 2 of the present embodiment. As shown in FIG. 12, the video file distribution process interacts as follows:

901. The HLS content source station creates a NORM group session, and the multicast address is norm://221.1.1.1:8080;

902. The set top box 1 joins the NORM group session with norm://221.1.1.1:8080;

903. The set top box 2 joins the NORM group session with norm://221.1.1.1:8080;

HLS content source station, CDN node and set-top box, repeat steps 804 to 7xx video files until all files File01~10.ts are played.

904. The HLS content source station encapsulates the video content 01.ts content with the NORM_DATA object, and encodes it into 300 NORM DATA packets File Pack (001-300), the NORM message serial number is 1 to 300, and the NORM_DATA type is NORM_OBJECT_FILE, other serial numbers. The packets are normally sent and received, and the set top box 1 and the set top box 2 are displayed for normal packets.

905. The set top box 1 detects a packet loss from FilePach011 to FilePack020, and sends a NACK message NACK1 to the CDN node in a multicast manner, and the NACK1 payload contains 10 packet loss numbers 11 to 20;

906. The set top box 2 detects a packet loss from FilePach011 to FilePack020, and sends a NACK message NACK1 to the CDN node in a multicast manner, and the NACK1 payload contains 10 packet loss numbers 11 to 20;

907. After collecting the NACK1 and NACK2 in the 10ms time window, the CDN node de-duplicates the sequence numbers, takes the union, and obtains the sequence number, and obtains the set-top box 1 and the set-top box 2 packet loss combination is 11-20, and then The intermediate server sends a NACK3 to the HLS content source station, and the message payload in the NACK3 includes 10 sequence numbers 11-20;

908. The HLS content source station receives the NACK3, and the packets of the set- top box 1 and 2 are 11 to 20, and then re-send 10 packets of the multicast repair message FilePack010-020, which are the repair packets of FilePack011-020, respectively. ;

909. When the set top box 1 receives the FilePacks 011 to 020, it starts data repair, and then converts to a video screen and continues to play File01.ts until the playback is completed.

910. When the set-top box 2 receives the FilePack011~020, it starts data repair, and then converts to a video screen and continues to play File01.ts until the playback is completed.

911. After all the Messages are sent and the display is completed, the set top box 1 closes the group session;

912. Wait until all Messages are sent and the presentation is complete, the set top box 2 closes the group session;

913. The HLS content source station closes the group session.

Implementation scenario three

The real-time flow object of NORM illustrates how the present disclosure can be implemented in a real-time stream service without borders.

FIG. 13 is a structural diagram of a NORM-based IPTV live broadcast system according to the third embodiment of the present invention, such as the IPTV live broadcast service system shown in FIG. 13. In this implementation scenario, a live broadcast encoder is deployed as the NORM sender in this embodiment. Setting up a CDN node with the NACK filtering device function proposed in the present disclosure; setting up two set top box clients (1 and 2) with the NORM receiving end function in the present disclosure. A multicast router is deployed in the area at the edge of the user network as a multicast replication device. The live broadcast encoder pushes the H.264 live stream to all set-top boxes. The live stream is encoded in H.264 mode and uses 8% FEC redundancy. The FEC error correction data is sent along with the original NORM data. The live encoder is unified. NORM_DATA encapsulates the original data encoding and FEC encoding, and the serial number is uniformly generated. The live broadcast source starts to create a NORM session at 07:00. The sequence number of the initial video multicast packet is 1. The set-top box 1 joins the NORM session at 07:05 to receive the multicast, starts watching the video, and receives the first multicast packet. The serial number is 30000. The set-top box 2 joins the NORM session at 07:10 to receive the multicast, starts watching the video, and receives the first multicast packet sequence number of 60000. The live broadcast encoder has lost 50 packets due to network reasons at 07:15. The packet loss packet number is from 90000 to 90050, and the corresponding multicast packet is Stream90000 to 90050. The set-top box 1 and the set-top box 2 are simultaneously at 07:15. NACK1 and NACK2 are generated simultaneously, and NACK1 and NACK2 both contain a list of lost packet numbers 90000-9050.

FIG. 14 is a flowchart of a NORM-based IPTV live broadcast service in the third scenario of the present embodiment. The interaction process of the IPTV live broadcast service system shown in FIG. 14 is as follows:

1101. The live broadcast encoder creates a group session with a multicast address norm://224.1.1.1:8080;

1102. Starting at 07:00:00, the live encoder generates a multicast live stream, and the live stream is encapsulated in a NORM_DATA format. The NORM object type is NORM_OJECT_STREAM, and the NORM_DATA contains original data and FEC encoded data, and is 100 multicast reports per second. The packet is transmitted at a speed. Each multicast packet generates a NORM_DATA sequence number. The packet with the sequence number x is Streamx.

1103. Starting at 07:05:00, the set-top box 1 joins the NORM group session with the multicast address norm://224.1.1.1:8080, and opens a buffer area to store the multicast live stream packets received within 5 seconds;

1104. The set top box 1 starts the multicast message sequence number 30000 to start receiving the multicast live stream, parses the NORM_DATA, obtains the original data and the FEC encoded data, and then performs FEC decoding, and the video playback starts.

1105. Starting at 07:10:00, the set-top box 2 joins the NORM group session with the multicast address norm://224.1.1.1:8080, and opens a buffer area to store the multicast live stream packets received within 5 seconds;

1106. The set top box 2 starts to receive the multicast broadcast stream number 60000, starts to receive the multicast live stream, parses the NORM_DATA, obtains the original data and the FEC encoded data, and then performs FEC decoding, and the video playback starts.

1107. 07:15:00, the set-top box 1 detects that the multicast live stream packet with the serial number of 90000~90050 in the buffer is not received, and sends a NACK packet NACK1 to the CDN node in multicast mode. The NACK1 payload is included in the payload. The package serial number ranges from 90000 to 90050;

1108. 07:15:00, the set-top box 2 detects that the multicast live stream packet with the sequence number 90000-90050 in the buffer area is not received, and sends a NACK message NACK2 to the CDN node in multicast mode, and the NACK2 payload includes the lost packet. Package serial number range 90000～90050

1109. After receiving the NACK1 and NACK2 in the 100ms time window, the CDN node de-duplicates the sequence number list, takes the union, and obtains the sequence number, and obtains the set-top box 1 and the set-top box 2 packet loss set is 90000~ 900500, then the CDN node sends a NACK3 to the live broadcast encoder, and the message payload in the NACK3 includes a sequence number ranging from 90000 to 90050;

1110. The live broadcast encoder receives the NACK3 in the time window of 100 ms, and obtains the packet of the set- top box 1 and 2 that is lost from 90000 to 90050, and then retransmits the multicast live stream packet with the serial number of 90000-90050, Stream90000-Stream90050 ;

1111. The set top box 1 receives Stream90000~Stream90050, fills in the corresponding data packet in the buffer, waits until the video recording of the set top box reaches Stream90000, then re-interprets the NORM_DATA, obtains the original data and the FEC encoded data, and then performs FEC decoding to continue the screen. Show.

1112. The set-top box 2 receives Stream90000~Stream90050, fills in the corresponding data packet in the buffer, waits until the video recording of the set-top box reaches Stream90000, then re-interprets the NORM_DATA, obtains the original data and the FEC encoded data, and then performs FEC decoding to continue the screen. Show.

1113. The set top box 1 closes the group session when the remote controller switches or closes the channel, and stops receiving the multicast live stream;

1114. The set top box 2 closes the group session when the remote controller switches or closes the channel, and stops receiving the multicast live stream;

In this implementation scenario, as long as the sum of the times occupied by the steps 1107, 1110, and 1111 is smaller than the length of the buffer of the set top box 1, the continuous play of the video can be realized, and the set top box 1 loses the video loss without sensing. Similarly, as long as the sum of the times occupied by steps 1108, 1110, and 1112 is less than the length of the buffer of the set top box 2, continuous playback of the video can be achieved, and the set top box 2 loses video loss without perception.

Implementation scenario four

In the multi-level architecture, file distribution is used as an example to illustrate how to deploy a multi-level NORM filtering device to support the number of receiving ends supported by a NORM sender. In order to prevent the spread of NORM NACK packets, the filtering device in the area in this implementation scenario The multicast NACK-to-unicast method is added to enable the multicast NACK packets sent by the receivers in different areas to be transmitted only in the local area, which avoids the performance impact of the multicast NACK packets on the receiving end, and further increases the utility of the present disclosure. Sex.

15 is a system structure diagram of a multi-level NORM filtering device in the fourth embodiment of the present invention. As shown in FIG. 15, in this implementation scenario, one message server is deployed as a NORM transmitting end in the present disclosure; and a level 2 NORM filtering device is set up. 2 edge filter units and 1 center filter unit. The area 1 contains a message client (1, 2, 3), and the area 2 contains a client (4, 5, 6) as a receiving end in the present disclosure. Each area includes a NORM filtering device, which is a filtering device 1 and a filtering device 2, respectively, and receives the multicast NACK message of the message client in the corresponding area, and the edge filtering devices 1 and 2 filter the de-duplicated NACK message. It is converted into unicast and sent to the central filtering device 3. The central filtering device sends a NACK message to the transmitting end in a unicast manner. At the same time, each zone also contains a multicast router as the multicast replication device described in this disclosure. In the meantime, in order to explain the two filtering modes of the filtering device proposed in the appended claims, the edge filtering devices 1 and 2 in the present embodiment adopt a time window aggregation filtering mode, and the central filtering device 3 adopts a cache forwarding filtering mode. In the cache, the list of lost packet numbers that have been sent NACK is empty.

In this implementation scenario, the message type service is used as the description. For the sake of space consideration, refer to the implementation scenario 1 for the steps of creating a message type NORM session and closing the session. Only the multi-level NORM filtering device and the NACK conversion are listed in this implementation scenario. Related steps. In this implementation scenario, the NORM multicast message is NORM_DATA, the transport object type is NORM_OBJECT_DATA, and there is no FEC encoding; the NACK packet is NORM_NACK. The NORM_DATA and NORM_NACK formats refer to RFC 5740.

16 is a message flow diagram of a multi-level NORM filtering device in the fourth embodiment of the present invention. As shown in FIG. 16, the message service implementation process of the multi-level NORM filtering device includes:

1201, the message server sends NORM multicast messages Message1~10 in sequence;

The three steps 1202~1204 are the working process of the client and the filtering device of the area 1;

1202, the message client 1, 2, 3 of the area 1 detects the sequence number 4, 5 packet loss, and sends a multicast NACK message 1 to the filtering device 1, respectively, including the sequence number loss packet number 4, 5;

1203, the filtering device 1 uses the time window aggregation filtering mode, that is, in the time window of 10 ms, receives three multicast NACK messages sent by the client 1, 2, 3, and filters according to the sequence number carried in the NACK message. Heavy, get the sequence number 4, 5 of the packet loss of the area 1 packet;

1204, the filtering device 1 sends a unicast NACK message NACK3 to the filtering device 3, the NACK message contains a sequence number list 4, 5;

The three steps 1205 to 1207 are the working process of the client and the filtering device of the area 2;

1205, the message client 4, 5, 6 of the area 2 detects the sequence number 5, 6 packet loss, and sends a multicast NACK message 2 to the filtering device 2, including the sequence number loss packet number 5, 6;

1206, the filtering device 2 uses the time window aggregation filtering mode, that is, in the 10 ms time window, the multicast NACK2 message sent by the client 4, 5, 6 is filtered according to the packet loss sequence number carried in the NACK message, Heavy, get the sequence number list 5,6 of packet loss in area 2;

1207, the filtering device 2 sends a unicast NACK message NACK4 to the filtering device 3, the NACK message contains a sequence number list 5, 6;

The two working processes of Zone 1 and Zone 2 are parallel and have no sequential relationship. Here, we assume that the NACK3 transmitted by the filtering device 1 reaches the filtering device 3 first than the NACK4 transmitted by the filtering device 2.

1208, the filtering device 3 adopts a buffer forwarding filtering mode, that is, after receiving the unicast NACK packet NACK3 sent by the filtering device 1, after determining that the NACK packet of the sequence number 4, 5 has not been sent from the buffer, the sending device sends a single message to the transmitting end immediately. Broadcasting NACK message NACK5, the NACK includes the packet loss sequence number list 4, 5, and the filtering device 3 stores the packet loss sequence number 4, 5 in the cache;

1209. The filtering device 3 adopts a buffer forwarding filtering mode. After receiving the unicast NACK packet NACK4 sent by the filtering device 2, it determines that the NACK packet of the packet loss sequence number 5 has not been sent from the buffer, and the NACK packet of the packet loss sequence number 6 is not sent. If the file has been sent, the unicast NACK message NACK6 is sent to the sender, and the NACK includes only the packet loss sequence number list 6; the filtering device 3 saves the packet loss sequence number 6 in the cache;

1210, after receiving the unicast NACK packet NACK5 sent by the filtering device 3, the transmitting end starts retransmitting the original multicast message Message4, 5;

1211, after receiving the unicast NACK packet NACK6 sent by the filtering device 3, the transmitting end starts retransmitting the original multicast message Message6;

1212, the client 1, 2, 3 receives the message 4, 5 retransmitted by the sender, then uses Message4, 5 to restore the data, and then displays the message.

1213, the client 4, 5, 6 receives the Message4, 5 retransmitted by the sender, then discards Message4, and uses Message5 to restore part of the data.

1214. When the client 1, 2, 3 receives the Message6 retransmitted by the sender, the message 6 is discarded.

1215, the client 4, 5, 6 receives the Message6 retransmitted by the sender, and uses Message6 to restore the remaining part of the data, and then displays the message.

Example 4

Embodiments of the present disclosure also provide a storage medium having stored therein a computer program, wherein the computer program is configured to execute the steps of any one of the method embodiments described above.

Optionally, in the embodiment, the above storage medium may be configured to store a computer program for performing the following steps:

S1. The sequence number of the lost packet sent by the first device is received, where the sequence number of the lost packet is used to indicate the sequence number of the lost message in the packet sent by the second device to the first device.

S2, performing a deduplication operation on the sequence number of the lost packet, to obtain a lost message sequence number set;

S3. Send the lost message sequence number set to the second device.

Optionally, in the embodiment, the foregoing storage medium may include, but is not limited to, a USB flash drive, a Read-Only Memory (ROM), and a Random Access Memory (RAM). A variety of media that can store computer programs, such as hard drives, disks, or optical disks.

Embodiments of the present disclosure also provide an electronic device including a memory and a processor having a computer program stored therein, the processor being configured to execute a computer program to perform the steps of any one of the method embodiments described above.

Optionally, the electronic device may further include a transmission device and an input and output device, wherein the transmission device is connected to the processor, and the input and output device is connected to the processor.

Optionally, in this embodiment, the foregoing processor may be configured to perform the following steps by using a computer program:

S1. The sequence number of the lost packet sent by the first device is received, where the sequence number of the lost packet is used to indicate the sequence number of the lost message in the packet sent by the second device to the first device.

S2, performing a deduplication operation on the sequence number of the lost packet, to obtain a lost message sequence number set;

S3. Send the lost message sequence number set to the second device.

For example, the specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

It will be apparent to those skilled in the art that the various modules or steps of the present disclosure described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. As such, the disclosure is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present disclosure, and is not intended to limit the disclosure, and various changes and modifications may be made to the present disclosure. Any modifications, equivalent substitutions, improvements, etc., made within the scope of the present disclosure are intended to be included within the scope of the present disclosure.

Industrial applicability

As described above, the packet transmission method, device, system, storage medium, and electronic device provided by the embodiments of the present invention have the following beneficial effects: reducing the sequence number of the same lost message by performing a deduplication operation on the sequence number of the lost message. The number is then sent to the second device to avoid the formation of a message storm on the second device, which solves the technical problem that the lost time of the lost message is too long in the related art, and reduces the screening operation of the second device for the serial number of the lost message. The amount of the second device is improved by sending the repair packet to the lost packet, and the delay of the first device for repairing the lost packet is reduced.

Claims (18)

1. A message transmission method includes:

   Receiving a sequence number of the lost packet sent by the first device, where the sequence number of the lost packet is used to indicate a sequence number of the lost packet in the packet sent by the second device to the first device;

   Performing a deduplication operation on the sequence number of the lost packet to obtain a lost message sequence number set;

   Sending the lost message sequence number set to the second device.
2. The method of claim 1, wherein after the sending the lost message sequence number set to the second device, the method further comprises:

   The second device sends a repair message to the first device, where the repair message is a message indicated by a sequence number in the lost message sequence number set.
3. The method of claim 1, wherein receiving the sequence number of the lost message sent by the first device comprises:

   Receiving a NACK message sent by the one or more of the first devices, where the NACK message carries the sequence number of the lost message.
4. The method of claim 3, wherein the NACK message comprises: a NACK message based on a reliable multicast communication protocol NORM.
5. The method according to claim 1, wherein the de-duplication operation is performed on the sequence number of the lost message to obtain a lost message sequence number set, including one of the following:

   In the sequence numbers of all the lost packets received in the predetermined time period, the repeated sequence numbers are deduplicated to obtain the lost message sequence number set;

   According to the historical packet loss sequence number list that has been sent within the predetermined time, in the sequence numbers of all the lost packets received, the serial number of the lost message that is not included in the historical packet loss sequence number list is selected. The lost message sequence number set.
6. The method of claim 1 wherein transmitting the lost message sequence number to the second device comprises one of:

   And sending the lost packet sequence number to the second device, and receiving the ACK information that is sent by the second device, where the ACK information is used to indicate that the second device receives the lost message sequence number set;

   Sending the lost message sequence number set to the second device according to the preset number of retransmissions.
7. The method of claim 1, wherein receiving the sequence number of the lost message sent by the first device comprises:

   And receiving a sequence number of the lost packet sent by all the first devices in the first area.
8. The method of claim 1 wherein transmitting the lost message sequence number set to the second device comprises one of:

   And sending the lost message sequence number set to the second device in one time;

   After the lost message sequence number set is split, it is distributed to the second device.
9. The method of claim 8 wherein said set of lost message sequence numbers is carried in a NORM-based NACK message.
10. A message transmission device comprising:

    The receiving module is configured to receive the sequence number of the lost packet sent by the first device, where the sequence number of the lost packet is used to indicate the sequence number of the lost packet in the packet sent by the second device to the first device;

    The processing module is configured to perform a deduplication operation on the sequence number of the lost packet to obtain a lost message sequence number set;

    The sending module is configured to send the lost message sequence number set to the second device.
11. The apparatus of claim 10, wherein the receiving module comprises:

    The receiving unit is configured to receive a NACK message sent by the one or more first devices, where the NACK message carries the sequence number of the lost message.
12. The apparatus of claim 10 wherein said processing module comprises one of:

    The first processing unit is configured to de-duplicate the repeated sequence numbers in the sequence numbers of all the lost packets received in the predetermined time period to obtain the lost message sequence number set;

    The second processing unit is configured to: according to the historical packet loss sequence number list that has been sent within the predetermined time, select, in the sequence numbers of all the lost packets that are received, the sequence number is not included in the history packet loss sequence number list. The sequence number of the packet is obtained by the sequence number of the lost message.
13. A message transmission system includes one or more first devices, second devices, and filtering devices, where

    The first device is configured to receive the original message sent by the second device, and send a sequence number of the lost message to the device when performing packet loss detection on the original packet to determine that there is a lost packet Filtering device;

    The filtering device includes: a receiving module, configured to receive a sequence number of the lost packet sent by the first device, where the sequence number of the lost packet is used to indicate the packet sent by the second device to the first device The sequence number of the lost message; the processing module is configured to perform deduplication operation on the sequence number of the lost message to obtain a lost message sequence number set; and the sending module is configured to send the lost message sequence number set to the second device;

    The second device is configured to send an original message to the first device, and receive the lost message sequence number set.
14. The system of claim 13 wherein said second device further comprises:

    The retransmission module is configured to resend the repair message to the first device, where the repair message is a message indicated by a sequence number in the lost message sequence number set.
15. The system of claim 14, the first device further comprising:

    The error correction module is configured to receive the repair message, and use the repair message to perform error correction and restoration processing on the data to obtain a complete original message.
16. The system of claim 14, the retransmission module further comprising:

    a first retransmission unit, configured to determine a packet that is lost by each of the one or more first devices, and send a packet with the same packet as the lost packet to the corresponding packet The first device;

    And a second retransmission unit, configured to send the repair message to all of the first devices.
17. A storage medium having stored therein a computer program, wherein the computer program is arranged to execute the method of any one of claims 1 to 9 at runtime.
18. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, the processor being arranged to execute the computer program to perform the method of any one of claims 1 to 9.

Images