WO2019149053A1

WO2019149053A1 - Data transmission method based on fusion transmission system

Info

Publication number: WO2019149053A1
Application number: PCT/CN2019/071616
Authority: WO
Inventors: 南凯; 王冬冬; 姜红旗; 张军强; 邢观斌; 邱翔东; 李群
Original assignee: 国广融合（北京）传媒科技发展有限公司
Priority date: 2018-01-31
Filing date: 2019-01-14
Publication date: 2019-08-08
Also published as: CN110099086A; CN110099086B

Abstract

The present application provides a data transmission method based on a fusion transmission system. The method comprises: obtaining a file to be sent; encapsulating said file in at least one fusion transmission block to form a fusion transmission stream and sending said fusion transmission stream to a terminal side; receiving a fusion transmission block retransmission request from the terminal side; and obtaining fusion transmission blocks needing to be retransmitted in the fusion transmission block retransmission request, encapsulating the fusion transmission blocks into a fusion transmission block retransmission response, and sending said fusion transmission block retransmission response to the terminal side.

Description

Data transmission method based on fusion transmission system

The present application claims priority to Chinese Patent Application No. 201101094159.2, entitled "A Data Transmission Method Based on Fusion Transmission System", filed on January 31, 2018, the entire contents of which are incorporated by reference. In this application.

Technical field

The present application relates to the field of digital multimedia broadcasting technologies, and in particular, to a data transmission method based on a converged transmission system.

Background technique

At present, in order to cope with the rapid growth of the demand for information services, the traditional broadcast network or the traditional two-way communication network alone cannot realize the optimal transmission of mobile information services. The traditional broadcast network adopts the large-area network connection mode, with large coverage and high-unidirectional broadcast efficiency, which is beneficial to the broadcast and push of public service content, but does not have an uplink return channel, and cannot achieve on-demand or broadband access, which is not conducive to personality. Transfer of content.

The existing mobile communication network adopts the cell-based cellular networking mode, has small coverage, high-efficiency two-way communication, and is beneficial for the transmission of personalized content, but the efficiency of broadcasting and pushing is low, which is not conducive to the broadcasting and pushing of public service content.

Under this circumstance, the broadcasting and communication industry is developing a new generation of broadcasting and communication technologies to improve the transmission rate and spectrum utilization of their respective systems. On the other hand, it is actively exploring new network architectures for the convergence of broadcasting and mobile communications. The access technology is to make full use of the advantages of the broadcast network and the mobile communication network for carrying different services, to allocate network resources and spectrum resources in a targeted manner, to select an optimal transmission mode, and to improve the overall wireless spectrum utilization rate of the network and the system.

Summary of the invention

In view of this, the embodiments of the present application provide a data transmission method and apparatus, a computing device, and a storage medium based on a converged transmission system, to solve the technical defects existing in the prior art.

The embodiment of the present application discloses a data transmission method based on a converged transmission system, which is applied to the convergence server side, and includes:

Get the file to be sent;

Encapsulating the file in the at least one fused transport block to form a fused transport stream to be sent to the terminal side, where each fused transport block carries a block sequence number;

Receiving a fused transport block retransmission request from the terminal side, where the fused transport block retransmission request includes a fused transport stream identifier and a fused transport block block sequence number list requesting retransmission, or includes a fused transport stream identifier and a file sequence number;

Obtaining a fused transport block that needs to be retransmitted in the fused transport block retransmission request, and encapsulating the fused transport block into a fused transport block retransmission response to be sent to the terminal side.

On the other hand, the embodiment of the present application further provides a data transmission method based on the fused transport block system, which is applied to the terminal side, and includes:

Receiving a converged transport stream;

Parsing and converging all the converged transport blocks in the converged transport stream, where each converged transport block carries a block sequence number;

When it is determined that the fused transport block in the fused transport stream is lost, sending a fused transport block retransmission request to the server side;

Receiving a fused transport block retransmission response carrying the fused transport stream identifier, the number of fused transport blocks requesting retransmission, and the fused transport block data requesting retransmission;

Determining, according to the fused transport stream identifier carried in the retransmission response of the fused transport block, the number of fused transport blocks requesting retransmission, and the fused transport block data requesting retransmission, determining that the fused transport block in the fused transport stream is buffered .

In another aspect, the embodiment of the present application further provides a computing device, including a memory, a processor, and a computer program stored on the memory and operable on the processor, where the processor implements the following steps:

Get the file to be sent;

Receiving a converged transport stream;

Determining, according to the fused transport stream identifier carried in the retransmission response of the fused transport block, the number of fused transport blocks requesting retransmission, and the fused transport block data requesting retransmission, determining that the fused transport transport block in the cached transport transport stream is complete.

In another aspect, the embodiment of the present application further provides a computer readable storage medium, where the computer readable storage medium stores a computer program, when the computer program is executed by a processor, implementing the The steps in the data transmission method of the converged transmission system or the steps in the data transmission method based on the converged transmission system applied to the terminal side.

The present invention provides a data transmission method, a computing device, and a storage medium based on a converged transmission system, where the method includes: acquiring a file to be sent; and encapsulating the file in at least one fused transport block to form a fused transport stream Sending to the terminal side, where each fused transport block carries a block sequence number; receiving a fused transport block retransmission request from the terminal side, the fused transport block retransmission request including the fused transport stream identifier and the fused transmission requesting retransmission a block sequence number list, or including a fused transport stream identifier and a file sequence number; acquiring a fused transport block that needs to be retransmitted in the fused transport block retransmission request, and encapsulating the fused transport block into a fused transport block retransmission response to be sent to The terminal side can adopt the above method to process the data and generate a unified format of the converged transport stream, which can be transmitted to the converged terminal through broadcast network broadcast and satellite, and the converged terminal can receive the satellite at the same time. Broadcast network and signals from mobile communication networks, and when broadcasting on satellites, etc. The received data error or loss occurs, the convergence terminal can retransmit lost or erroneous data in a mobile communication network via a bidirectional link, in order to ensure the reliability of data reception.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is an embodiment of the present invention, and those skilled in the art can obtain other drawings according to the provided drawings without any creative work.

1 is a schematic structural diagram of a fusion transmission system according to an embodiment of the present application;

2 is a schematic structural diagram of a protocol stack based on a converged transmission system for a server side according to an embodiment of the present application;

3 is a schematic structural diagram of a protocol stack based on a converged transmission system for a terminal side according to an embodiment of the present application;

4 is a schematic structural diagram of a converged transport stream according to an embodiment of the present application;

FIG. 5 is a schematic structural diagram of a fused transport block according to an embodiment of the present application;

6 is a schematic structural diagram of a file description header according to an embodiment of the present application;

7 is a schematic diagram of a mapping process of each fused transport stream in a next-generation broadcast television wireless NGB-W/S channel according to an embodiment of the present application;

8 is a schematic diagram of a mapping process and a TS packet structure of each fused transport stream in a DVB-S channel of a digital satellite broadcasting system according to an embodiment of the present application;

9 is a flowchart of a data transmission method based on a converged transmission system according to an embodiment of the present application;

10 is a flowchart of a data transmission method based on a converged transmission system according to an embodiment of the present application;

11 is a schematic structural view of a segment header of an embodiment of the present application;

FIG. 12 is a schematic structural diagram of a converged transport block package according to an embodiment of the present application;

FIG. 13 is a schematic structural diagram of a converged transport block package according to an embodiment of the present application;

14 is a schematic structural diagram of a converged transport block package according to an embodiment of the present application;

15 is a schematic structural diagram of a converged transport block package according to an embodiment of the present application;

16 is a schematic diagram of a terminal side requesting retransmission to a server side by sending a UDP retransmission request according to an embodiment of the present application;

17 is a schematic diagram of a terminal side requesting retransmission by sending an HTTP retransmission request to a server side according to an embodiment of the present application;

18 is a flowchart of a data transmission method based on a converged transmission system according to an embodiment of the present application;

19 is a flowchart of a data transmission method based on a converged transmission system according to an embodiment of the present application;

20 is a flowchart of a data transmission method based on a converged transmission system according to an embodiment of the present application;

21 is a flowchart of a data transmission method based on a converged transmission system according to an embodiment of the present application;

22 is a schematic structural diagram of a data transmission apparatus based on a converged transmission system according to an embodiment of the present application;

FIG. 23 is a schematic structural diagram of a data transmission apparatus based on a converged transmission system according to an embodiment of the present application.

Detailed ways

Numerous specific details are set forth in the description below in order to provide a thorough understanding of the application. However, the present application can be implemented in many other ways than those described herein, and those skilled in the art can make similar promotion without departing from the scope of the present application, and thus the present application is not limited by the specific embodiments disclosed below.

In the present application, "first", "second", "third", and the like are used only for distinguishing from each other, and not for indicating the degree of importance and order, and the premise of mutual existence.

In the present application, a data transmission method and apparatus, a computing device, and a storage medium based on a converged transmission system are provided, which are described in detail in the following embodiments.

First, the terminology involved in this application will be explained below.

Service - A series of programs or data that can be broadcast live under the control of a broadcaster.

Mobile satellite multimedia - multimedia services provided to mobile terminals via satellite communication networks, such as audio and video, on-demand and data push services.

Satellite broadcast network - A network that provides audio and video broadcasting and other information services based on geosynchronous orbit satellites.

Mobile communication network - A network that provides mobile communications and two-way data transmission based on terrestrial base stations, including 2G/bidirectional/xG.

Network convergence transmission—The same service uses both the satellite broadcast network and the mobile communication network to transmit to improve the service coverage and service reliability.

Transport Stream (MPEG2-TS, also known as TS) - A communication protocol for sound effects, images and data used to encapsulate a composite stream of audio and video media data.

Converged transport block - A fixed-length packet structure used to carry upper-layer service data.

Converged transport stream - A composite information stream consisting of consecutive converged transport blocks that can transport multiple services.

Physical pipe - A physical layer channel that occupies certain channel resources and can be independently encoded and modulated.

Uniform resource identifier - A string used to identify the name of an Internet resource that allows the user to interact with any (including local and Internet) resources through a specific protocol.

Before introducing the technical solution of the present application, the architecture of the converged transmission system according to the present application will be first described.

See Figure 1 for the architecture of the converged transmission system 10. In the converged transmission system 10, the output data of various service platforms 101 (such as audio and video broadcasting services, data push services, etc.) is first submitted to the converged gateway 103. After the converged gateway 103 processes various service data, it generates a converged transport stream in a unified format. The converged transport stream can be transmitted to the terminal 110 in two ways: one is submitted to the satellite broadcast headend device 105, sent to all terminals 110 via the satellite broadcast network 106 via the broadcast channel 108; the other is to save the data to an internet server or It is submitted to a cache server on the Content Delivery Network (CDN) 104 and provides a Uniform Resource Identifier (URI). The terminal 110 can actively access the fused transport stream via the network channel 109 through the mobile communication network 107. data.

The satellite broadcast network 106 utilizes geosynchronous orbit satellites to provide multimedia information services including audio, video, data, etc. for signal coverage areas (which may include one or more countries and regions). The satellite broadcasting network 106 has the advantages of wide coverage area, stable signal transmission in an open area, and high-speed movement of a support terminal, and is particularly suitable for providing an information service for an in-vehicle terminal.

The basic principle of the converged transmission system 10 is as follows: The terminal 110 simultaneously receives signals from the satellite broadcast network 106 and from the mobile communication network 107. In general, the terminal 110 preferentially receives service data from the satellite broadcast network 106, but when on the satellite broadcast network 106 When the received data is erroneous or lost, the terminal 110 will retransmit the lost or erroneous service data through the bidirectional link of the mobile communication network 107 to ensure the reliability of the service data reception.

The Big File Push (BFP) protocol is mainly used to implement reliable transmission of large files based on the network convergence transmission system, and can be used to transfer files from several Mbytes to a dozen Gbytes. The BFP protocol supports a variety of file-based non-real-time services, such as high-quality audio and video on demand, map push and more.

The Live Stream Transport Protocol (LSTP) protocol is mainly used to encapsulate a file stream of one or more live broadcast services into a converged transport stream.

The protocol stack based on the LSTP protocol can be set on both the server side and the terminal side, as shown in FIG. 2 and FIG. In a converged transmission system, the protocol stack includes three layers: a service application layer, a converged transport layer, and a physical transport layer.

In a network convergence transmission system, services are no longer implemented by relying on a single network transmission service, such as a transmission service provided by a satellite broadcast network alone or an Internet transmission service provided by an interconnection communication network alone, but The converged transmission function provided by the above two networks is implemented. The above converged transmission function is implemented by a new protocol layer, the converged transport layer.

The converged transport layer shields the business from the details of the underlying network transport. On the server side, the service source only needs to submit the data to the converged transport layer, and the converged transport layer is responsible for transmitting the service data in the satellite broadcast network, and providing the service data with access paths on the interconnected communication network; on the terminal side, the converged transmission The layer is responsible for receiving and checking the service data received on the satellite broadcast network, and starting the retransmission on the interconnection communication network as needed, and integrating the retransmitted service data with the service data received by the satellite broadcast network, and providing the upper layer service processing. .

In an actual network, the types of services that need to be transmitted are diverse, and the quality of service (QoS) requirements of various services are also different. For example, audio and video live broadcast services require data reliability of the program, and the reliability of the data needs to be fully guaranteed. In order to support different service types, the converged transport layer is further divided into two sub-layers: a converged transport stream sub-layer and a service-specific transport protocol sub-layer.

The functions of each sublayer are as follows:

1) Converged Transport Stream (CTS) sublayer

The Converged Transport Stream sublayer provides a unified format, Converged Transport Block (CTB), to encapsulate data for various upper layer services. The fused transport block is a data block having a fixed size and is consecutively numbered in the order of generation, which is referred to as a block number of the fused transport block.

The converged transport stream sublayer supports the transmission of the converged transport block over the satellite broadcast network. In order to adapt to different satellite broadcast links, the fused transport block needs to be adapted for transmission, and the fused transport block is encapsulated into different satellite broadcast link transport packets.

The fused transport stream sublayer supports retransmission of the fused transport block over the Internet, including retransmission of a single CTB, and also includes retransmission of multiple CTBs. The block numbers of the plurality of CTBs that are retransmitted in the retransmission of the plurality of CTBs may be continuous or discrete.

2) Service Specific Transport Protocol (SSTP) sublayer

The service specific transport protocol sublayer is a service adaptation layer introduced to guarantee the quality of service (QoS) of different services. The service specific transport protocol sublayer includes a variety of transport protocols, each for a type of service to meet the real-time and reliability requirements of such services. Currently, the main transport protocols include:

A. Live Streaming Protocol (LSTP) suitable for real-time live broadcast services; and

B. Large File Push Protocol (BFP) for non-real-time large file services.

The functions of these transport protocols include how to process the data submitted by the business. In addition, these transport protocols include specific retransmission capabilities and other service adaptation capabilities to meet business needs.

See Figure 4 for the structure of the fused transport stream and Figure 5 for the structure of the fused transport block.

The fused transport stream is a composite information stream consisting of consecutively numbered fixed-length data blocks, the Converged Transport Block (CTB), which can be used to carry various types of upper-layer service data, as shown in Figure 4.

Generally, there are multiple converged transport streams transmitted in parallel in a converged transmission system, and each converged transport stream is transmitted on a certain physical channel or logical channel. In the case where the modulation coding scheme of the underlying channel is determined, a fusion is performed. The transmission rate of the transport stream is constant. In order to distinguish different converged transport streams, the system assigns each converged transport stream a 12-bit identifier called the Converged Transport Stream Identifier (CTS-ID).

A converged transport block is the basic unit for transmitting service information. For a converged transport stream, the size of its converged transport block is fixed, mainly determined by the physical channel protocol occupied by the converged transport stream. For example, when the NGB-W/S channel is used, the size of the fused transport block is fixed to 2118 bytes.

The fused transport block is composed of a block header, a block payload and a check field, wherein the block header size is fixed to 5 bytes, and the structure is as shown in FIG. 5.

Wherein, the block header further includes the following bits:

Block number - 32-bit number, used to cyclically number the fused transport block in the same fused transport stream. The block number starts from 0. When the maximum value is 2 ³² -1, it is numbered from 0.

The service type, 3-bit, is used to indicate the type of service data encapsulated in the converged transport block, as shown in Table 1. When the service type is empty, the data in the fused transport block is filled with random data.

Table 1

值 value		描述description
11	文件流传输业务 File streaming service
22	大文件推送业务Large file push service
33	控制消息业务Control message service
77	空业务Empty business
其他other	待定To be determined

Check indicator - 1 bit. A value of 1 indicates that there is a check field at the end of the fused transport block. Cyclic Redundancy Check (CRC32). If the value is 0, there is no check field.

Check field (CRC32) - 32-bit bit, which is a check field. It exists when the check indication is 1. This field checks the block header and block payload all bytes of the file transfer block.

In an embodiment of the present application, the protocol stack on the server side is set as shown in FIG. 2, and includes:

The business application layer includes file units for storing files to be sent.

In order to stream or push a file, you need to add the file to a business. At least one file has been added to each business. Files added to a business are stored in file units corresponding to the service.

In a converged transmission system, each service corresponds to a converged transport stream. Therefore, in the process of adding a file to a service, it is equivalent to specifying a converged transport stream for the file.

The converged transport layer includes a service specific transport protocol sublayer and a converged transport stream sublayer.

The service specific transport protocol sublayer includes at least one physical unit for preprocessing the file to be transmitted to generate the original data. A data channel for transmitting a file to be sent is formed between the physical unit and the file unit, and the entity unit receives the file to be sent through the data channel, and then preprocesses the file to be sent. It should be noted that each physical unit corresponds to at least one file unit.

The service-specific transport protocol sub-layer can support multiple protocols. In this embodiment, the live streaming protocol, that is, the LSTP protocol, is used as an example to support the live broadcast service. Correspondingly, the physical unit is an LSTP physical unit.

During the live broadcast service, the entity unit may add a corresponding File Description Header (FDH) to the file to be sent, and the entity unit divides the file to be sent added with the file description header into multiple file segments. The file to be sent without the file description header is the original data.

In a specific embodiment, the entity unit adds a file description header (FDH) to the header of each file, and each file description header includes basic information and a plurality of extended information, and the specific structure of the file description header is as shown in the figure. 6 is shown.

The fused transport stream sublayer is configured to encapsulate the original data into a fused transport block, and the fused transport stream formed by the fused transport block is sent to the terminal side via the physical transport layer.

Specifically, the physical transport layer includes: a satellite broadcast channel and an internet channel.

In more detail, a data channel for transmitting a fused transport block is formed between the fused transport stream sublayer and the satellite broadcast channel, and a data channel for transmitting the fused transport block is formed between the fused transport stream sublayer and the Internet channel.

The satellite broadcast channel will be described in detail below. The satellite broadcast channel includes: a next-generation broadcast television wireless NGB-W/S channel or a digital satellite broadcast system DVB-S channel;

The fused transport stream sublayer encapsulates the fused transport block into broadcast data suitable for the NGB-W/S channel or the DVB-S channel and transmits it to the NGB-W/S channel or the DVB-S channel via the data channel.

In the NGB-W/S channel, one or several fused transport streams can be combined and transmitted on one physical pipeline, and each fused transport stream occupies a fixed period on a continuous scheduling period on the physical pipeline, and the mapping process is as shown in FIG. 7. Shown.

Each of the fused transport blocks CTB of the fused transport stream is mapped one by one into a link data packet, and the link data packet is further encapsulated by the link layer into a service load packet, and is handed to the physical layer for coding and modulation. .

In the DVB-S channel, the broadcast link uses the MPEG2-TS transport stream as the input form of the service, and does not divide the physical channel into several independent physical pipes. Therefore, a converged transport stream can be mapped directly to the entire physical channel or to a custom logical channel.

Each fused transport block in the fused transport stream will be mapped into an integer number of TS packets (188 bytes), and its mapping process and TS packet structure are as shown in FIG. As can be seen from FIG. 8, each TS packet includes a header (4 bytes) and a payload (184 bytes), and the header includes: a sync byte (8 bits), a transmission error indication (1 bit), and a payload unit start indication ( 1 bit), transmission priority (1 bit), program identification (13 bit), CTB start indication (1 bit), CTB end indication (1 bit), reservation (2 bit), and TS packet loop count (4 bits).

The Internet channel is described in detail below. The Internet channel includes: a User Datagram Protocol UDP channel and a Hypertext Transfer Protocol HTTP channel.

In addition, a message channel for transmitting a retransmission request is formed between the Internet channel and the fused transport stream sublayer; the fused transport stream sublayer receives the retransmission request via the message channel, and passes the retransmission response encapsulated with the fused transport block via the data The channel is sent to the internet channel.

Specifically, the fused transport stream sublayer receives the UDP retransmission request sent by the UDP channel via the message channel, and sends the UDP retransmission response encapsulated with the fused transport block to the UDP channel via the data channel; or the fused transport stream sublayer passes the message channel Receiving an HTTP retransmission request sent by the HTTP channel, and transmitting an HTTP retransmission response encapsulated with the fused transport block to the HTTP channel via the data channel.

It should be noted that in the Internet channel, the UDP channel and the HTTP channel are coexisting, and which channel is specifically used is determined by the terminal side when transmitting the retransmission request. When the data volume of the fused transport block requesting retransmission is less than the threshold, the fused transport stream sublayer of the terminal side receives the UDP retransmission request and sends the UDP retransmission response through the UDP channel; when the data volume of the fused transport block requesting retransmission is greater than At the threshold, the fused transport stream sublayer on the terminal side receives the HTTP retransmission request and sends an HTTP retransmission response through the HTTP channel.

As shown in FIG. 3, the protocol stack for the terminal side includes: a service application layer, a converged transport layer, and a physical transport layer.

The business application layer includes file units for receiving raw data of a file to be processed.

The service specific transmission protocol sublayer includes at least one physical unit for parsing the fused transport block to generate original data; each physical unit and the file unit form a data channel with original data for transmitting a file to be transmitted, each entity A data channel for transmitting the fused transport block is formed between the unit and the fused transport stream sublayer.

The service-specific transport protocol sub-layer can support multiple protocols. This embodiment uses the LSTP protocol as an example.

In the live broadcast service, the entity unit parses the transport block to generate the original data, including:

The fused transport block is decapsulated to obtain a file description header and a file segment, and then file recovery is performed on the file segment according to the file description header, that is, the original data is parsed and generated.

In addition, a data channel for transmitting the fused transport block is formed between the fused transport stream sublayer and the physical unit for receiving data via the satellite broadcast channel and transmitting a retransmission request and receiving retransmission data from the server side via the Internet channel.

A data channel for transmitting the fused transport block is formed between the physical transport layer and the fused transport stream sublayer. Specifically, the physical transport layer includes: a satellite broadcast channel and an internet channel.

A data channel for transmitting the fused transport block is formed between the satellite broadcast channel and the fused transport stream sublayer. Specifically, the satellite broadcast channel includes: an NGB-W/S channel or a DVB-S channel, and the fused transport stream sublayer decapsulates the broadcast data of the NGB-W/S channel or the DVB-S channel into a fused transport block And transmitting the fused transport block to the physical unit via the data channel.

Regarding the NGB-W/S channel and the DVB-S channel, the foregoing has been described in detail, and will not be further described herein.

A data channel for transmitting the fused transport block is formed between the Internet channel and the fused transport stream sublayer, and a message channel for transmitting a retransmission request is formed between the Internet channel and the fused transport stream sublayer. The fused transport stream sublayer sends a retransmission request via the message channel, and receives, via the data channel, a retransmission response encapsulated by the Internet channel and encapsulated with the fused transport block.

More specifically, the Internet channel includes: a User Datagram Protocol UDP channel and a Hypertext Transfer Protocol HTTP channel;

The fused transport stream sublayer sends a UDP retransmission request to the UDP channel via the message channel, and receives a UDP retransmission response encapsulated with the fused transport block sent by the UDP channel via the data channel;

The fused transport stream sublayer receives an HTTP retransmission request to the HTTP channel via the message channel, and receives an HTTP retransmission response encapsulated with the fused transport block sent by the HTTP channel via the data channel.

It should be noted that in the Internet channel, the UDP channel and the HTTP channel are coexisting, and which channel is specifically used is determined by the terminal side when transmitting the retransmission request. When the data volume of the fused transport block requesting retransmission is less than the threshold, the fused transport stream sublayer of the terminal side sends a UDP retransmission request and receives a UDP retransmission response through the UDP channel; when the data volume of the fused transport block requesting retransmission is greater than At the threshold, the fused transport stream sublayer on the terminal side transmits an HTTP retransmission request and receives an HTTP retransmission response through the HTTP channel.

Specifically, the fused transport stream sublayer on the terminal side determines whether the data volume of the retransmitted data is smaller than a packet threshold of a UDP retransmission response, and if yes, sends a UDP retransmission request and receives a UDP retransmission response by using the UDP channel; Then, the HTTP channel is used to send an HTTP retransmission request and receive an HTTP retransmission response.

It can be seen that, on the terminal side, the received fused transport block is checked, and the fused transport block is lost. In the process of retransmission, the terminal side initiates a retransmission process, and the terminal side also actively decides the retransmission channel selection. For the server side, in response to the retransmission request sent by the terminal side, the retransmission response is transmitted through the same Internet channel as the retransmission channel on the terminal side.

The physical transport layer of the present application uses a dual link of a satellite broadcast channel and an Internet channel, and uses a satellite broadcast channel to transmit data when transmitting data; when retransmitting data, an Internet channel is used to retransmit lost or erroneous data, thereby Guarantee the reliability of data reception.

The above is a detailed description of the architecture of the protocol stack disclosed in the present application. The protocol stack provides support for the operation of the converged transmission system.

In the present application, a data transmission method, apparatus, computing device, and computer readable storage medium based on a converged transmission system are provided, which are described in detail in the following embodiments. Similar to the description of the protocol stack, a data transmission method based on the converged transmission system of the present embodiment also describes the terminal side and the server side, respectively.

Referring to FIG. 9, an embodiment of the present application provides a data transmission method based on a converged transmission system, which is applied to a server side, and includes steps 901 to 904.

Step 901: Acquire a file to be sent.

In the embodiment of the present application, the file to be sent may be a file stream in an acquired upper layer service entity, and then the file stream is segmented to form at least one file to be sent, and the file to be sent is sent. That is, the data to be transmitted may include audio data, video data, image data, or text data.

The file to be sent may be an independently playable media file formed by dividing a file stream of an audio and video program by time or size, and the audio and video program is a service.

For example, the service is a, and the service includes file streams a1 and a2, wherein the file stream a1 is divided into files such as a11, a12, and a13 according to the time duration, and the file stream a2 is divided into a21 and a22 according to the file size. And a23 and other documents.

In the embodiment of the present application, the number of file streams in each service, and the manner and number of divisions of each file stream into files are not limited, and may be selected according to actual needs.

Step 902: Encapsulate the file in at least one fused transport block to form a fused transport stream, and send the fused transport stream to the terminal side, where each fused transport block carries a block sequence number.

In the embodiment of the present application, after the file is encapsulated in at least one Converged Transport Block (CTB), service index information of all the converged transport blocks under the same service may be generated, and used to record files and The correspondence of the transport blocks is fused, wherein each fused transport block carries a block sequence number and all block sequence numbers are consecutive.

The service index information includes a plurality of index rows, each index row represents index information of a file, and the index information of each file includes a fused transport stream identifier, a service stream number, a file sequence number in the file stream, and a file stream. The information of all the fused transport blocks corresponding to the information, where the information includes the block number of the first fused transport block corresponding to the file stream and the number of fused transport blocks generated after the file stream is encapsulated.

For example, the index information of a file has the following format:

CTS_ID: ISS_ID: FileSeq: BlockSeqBegin: BlockCount

The CTS_ID and the ISS_ID respectively indicate the fused transport stream identifier and the service stream number, which together constitute the service identifier; FileSeq is the file sequence number in the file stream; BlockSeqBegin is the block number of the first fused transport block corresponding to the file. ;BlockCount is the number of fused transport blocks generated after the file is encapsulated.

In the embodiment of the present application, the fused transport block includes a block header and a block payload, and the block header includes a block sequence number and a service type, and the file is encapsulated in the block payload.

In this embodiment, the fused transport stream may be sent to the terminal side through a satellite broadcast channel; the satellite broadcast channel includes an NGB-W/S channel or a DVB-S channel;

In the NGB-W/S channel, one or several fused transport streams may be combined and transmitted on one physical pipeline, and each fused transport stream occupies a fixed period on a continuous scheduling period on the physical pipeline, and the mapping process is as follows. As shown in FIG. 7, each fused transport block CTB of the fused transport stream is mapped one by one into a link data packet, and the link data packet is further encapsulated by the link layer into a service load packet, and is handed over to The physical layer performs code modulation;

On the DVB-S channel, the broadcast link uses the Transport Stream (MPEG2-TS) transport stream as the input form of the service, and does not divide the physical channel into several independent physical pipes, as shown in FIG. Therefore, a converged transport stream can be directly mapped to the entire physical channel or a custom logical channel;

Each fused transport block in the fused transport stream is mapped into an integer number of Transport Stream (TS) packets, and the mapping process and TS packet structure are as shown in FIG. 8.

The TS packet is 188 bytes long and consists of a header and a payload. The header length is 4 bytes, including the following bits:

Sync byte, including 8-bit bits, used for synchronization of the TS stream, the value is always 0x47;

Transmission error indication, including 1 bit, indicating whether the TS packet is in error during transmission, 0 means no error, 1 means error, default value is 0;

Payload unit start indication, including 1 bit, the value is always 0;

Transmission priority, including 1 bit, the value is always 0;

The program identifier, including the 13-bit bit, indicates the program or service to which the TS packet belongs, and the value ranges from 0x0000 to 0x1FFF, that is, the valid bit is 13 bits, and the PID value is 0x1FFF for the empty packet. In this standard, when the TS packet is used, When the CTB packet is carried, the highest bit of the program identifier is fixed to 0, and the last 12 bits correspond to the identifier (CTS_ID) of the fused transport stream to which the CTB belongs;

The CTB start indication includes a 1-bit bit. When the transmitted TS packet is the first TS packet of a fused transport block, the position is 1, otherwise, the bit is 0;

CTB end indication, including 1 bit, when the transmitted TS packet is the last TS packet of a fused transport block, the position is 1, otherwise, the bit is 0;

The TS packet loop count, including 4 bit bits, is independently loop counted for the TS packets output by each PID.

Further, referring to FIG. 10, the step of encapsulating the file in at least one fused transport block may be implemented by step 1001 to step 1003.

Step 1001: Add a file description header for each of the files.

In the embodiment of the present application, the file description header includes: a service identifier, a file sequence number, a file length, and a file play duration, and may also include a Live Stream Transport Protocol (LSTP), a file description header length, and an extended information indication. , file compression instructions and reserved fields, etc.

The service identifier is used to indicate the service to which the file belongs; the file serial number is used to indicate the number of the file in the entire file stream; and the file length is used to indicate the file when the file is not compressed. The original length, after compressing the file in a compressed manner, the file length is used to indicate the length of the compressed file, in bytes; the file playing duration is used to indicate the actual playing time of the file. In milliseconds.

Step 1002: Segment the file to which the file description header is added into at least one file segment according to the size of the fused transport block, where each file segment carries a segment header, and the file description header is included in the file. One of the file segments.

In the embodiment of the present application, the file added with the file description header is divided into a plurality of file segments according to the size of the fused transport block, where the file segment includes a segment header and a segment payload. Referring to FIG. 11, the segment header includes a file segment. The number, the total number of file segments, and the file serial number may also include the segment payload type, the segment payload length, and the service stream number.

The file description header is segmented into the segment payload of one of the file segments of the file, and the present application preferably divides the file description header into the segment payload of the first file segment of the file.

Step 1003: Encapsulate the file segment in a converged transport block.

In the embodiment of the present application, if the last file segment of the file is encapsulated in the fused transport block and the fused transport block has a remaining space, it is detected whether there is a file to be sent next;

If there is a next file to be sent and if the size of the first file segment of the next file to be sent is equal to or smaller than the remaining space, the first file segment is encapsulated in the remaining space. When the service type in the block header of the converged transport block is equal to 1;

If there is a file to be sent but the size of the first file segment of the next file to be sent is larger than the remaining space, the remaining space is filled, and the service in the block header of the fused transport block is Type is equal to 1;

If the file to be sent is not encapsulated in the fused transport block, the entire fused transport block is padded, and the service type in the block header of the fused transport block is set to the null service 7.

Referring to FIG. 12, an example is described in which each file segment in a file A is encapsulated in a fused transport block. First, FDH is added to file A, and then the file A is segmented into a start according to the size of the fused transport block. a plurality of file segments to be sent, a segment, three intermediate segments, and an end segment, the FDH being included in the start segment, and then placing the start segment into the fused transport block k, and then sequentially The intermediate segment is placed in the fused transport block k+1, the fused transport block k+2, the fused transport block k+3, and finally the end segment is placed in the fused transport block k+4; as shown in Fig. 12, the fused transport block k The end segment of the +4 bearer has not yet filled the space of the fused transport block k+4. The following uses the file B to be transmitted as an example to describe the remaining space usage of the fused transport block k+4.

Referring to FIG. 13 to FIG. 14, if the first file segment of the file B, that is, the size of the start segment is equal to or smaller than the remaining space, the start segment of the file B is encapsulated in the fused transport block k+ 4 in the remaining space, and at this time the service type in the block header of the fused transport block is equal to 1;

If the starting segment size of the file B is larger than the remaining space, the remaining space is padded, and the service type in the block header of the fused transport block is equal to 1;

If there is no next file to be sent, the remaining space is also filled, and the service type in the block header of the fused transport block is equal to 1.

Referring to FIG. 15, if the file to be transmitted is not encapsulated in the fused transport block, the entire fused transport block is padded, and the service type in the block header of the fused transport block is set to the null service 7.

Step 903: Receive a fused transport block retransmission request from the terminal side, where the fused transport block retransmission request includes a fused transport stream identifier and a fused transport block block sequence number list requesting retransmission, or includes a fused transport stream identifier and a file sequence number.

In the embodiment of the present application, if the server side receives the fused transport block retransmission request from the terminal side to request to retransmit several missing fused transport blocks, the fused transport block retransmission request includes the fused transport stream identifier and the request retransmission. The fused transport block block sequence number list may further include a retransmission request number and a total number of fused transport blocks requesting retransmission;

The fused transport stream identifier (CTS_ID) may be an integer type, in the range of 0 to 4095, indicating the fused transport stream identifier that initiates the retransmission;

The retransmission request number (REQ_SEQ) may be an integer type, ranging from 0 to 255, indicating that the Service Specific Transport Protocol (SSTP) entity chronologically transmits the fused transport block retransmission request (CTS_CTB_REQ message). The number of the cycle performed;

The total number of the fused transport blocks (CTS_REQ_COUNT) to be retransmitted may be an integer type, in the range of 1 to 1000, indicating the total number of fused transport blocks requesting retransmission;

The fused transport block block sequence number list (CTS_REQ_LIST) for requesting retransmission may be a string type indicating the sequence number of the fused transport block that needs to be retransmitted, and is composed of a plurality of binary groups <CTB_BEGIN: CTB_NUM>, each of the two groups Representing a group of fused transport blocks consecutively numbered, where SEQ_BEGIN indicates the starting sequence number, SEQ_NUM indicates the number of CTBs in the CTB group, and multiple binary groups are separated by semicolons. The overall format is as follows:

SEQ_BEGIN1: SEQ_NUM1; SEQ_BEGIN2: SEQ_NUM2; SEQ_BEGIN3: SEQ_NUM3;

For example, when CTB_REQ_LIST is a string of 1001:1; 1050:4; 1066:2, the CTB indicating that retransmission is required includes seven CTBs of sequence numbers 1001, 1050, 1051, 1052, 1053, 1066, and 1067.

If the server side receives the fused transport block retransmission request from the terminal side, and requests the retransmission of the fused transport block of the lost entire file, the fused transport block retransmission request includes the fused transport stream identifier and the file sequence number, and may also include the fused transmission. Block request number, service stream number, file acquisition mode, file relative position;

The fused transport stream identifier (CTS_ID) may be an integer type, and the value ranges from 0 to 4095, indicating the fused transport stream identifier.

The fused transport block request number (REQ_SEQ) may be an integer type, ranging from 0 to 255, indicating a circulating number of the fused transport block retransmission request (CTS_CTB_REQ2 message) sent by the LSTP entity in chronological order;

The service flow number (ISS_ID) may be an integer type, ranging from 0 to 255, indicating the number within the service flow, and the service identifier of the fused transport stream constitutes a service identifier.

The file acquisition mode (GET_MODE) can be an integer type, in the range of 0 to 1, indicating the file acquisition mode. When the value of the file acquisition mode is 0, it is the normal mode; when the value of the file acquisition mode is 1, it is Relative mode.

The file serial number or the relative position of the file (FILE_SEQ) may be an integer type, ranging from 0 to (2 ²⁰ -1). When the value of the file acquisition mode is 0, it represents the file number of the retransmission; The value of the acquisition mode is 1 and represents the relative position of the retransmission file and the latest package file. The service index information generated by the server side records the file encapsulated as a converged transport block in the file stream of the service, assuming the latest packaged file. The serial number is S0. If S0 is greater than or equal to the file serial number or the relative position of the file, the serial number of the actual retransmission file is (S0-FILE_SEQ); if S0 is smaller than the file serial number or the relative position of the file, the actual retransmission file serial number Is (S0+2 ²⁰ -FILE_SEQ).

Step 904: Acquire a fused transport block that needs to be retransmitted in the fused transport block retransmission request, and encapsulate the fused transport block into a fused transport block retransmission response and send it to the terminal side.

Further, when the fused transport block retransmission request includes the fused transport stream identifier and the fused transport block block sequence number list that is requested to be retransmitted, acquiring the fused transport block that needs to be retransmitted in the fused transport block retransmission request includes:

Determining, according to the correspondence between the fused transport stream identifier in the fused transport packet retransmission request and the fused transport stream identifier in the service index information, determining that the fused transport block requested to be retransmitted in the fused transport block retransmission request belongs to Converged transport stream;

Comparing the fused transport block block sequence number list that is requested to be retransmitted with the information of all the fused transport blocks corresponding to the file stream in the service index information, and determining that the fused transport block requesting retransmission in the fused transport block retransmission request corresponds to File segment

Re-encapsulating the file segment to form a fused transport block that needs to be retransmitted in the fused transport block retransmission request.

In the embodiment of the present application, the parameter fused transport stream identifier carried in the retransmission request of the fused transport block is firstly found, and the corresponding fused transport stream is found from the service index information of the server side, and then the block sequence number of the fused transport block retransmitted according to the request is obtained. The file segment number and the file sequence number in the header segment of the file segment to be encapsulated in each converged transport block, and the file segment corresponding to the fused transport block requesting retransmission is determined, and the file segment is obtained by the upper layer service entity on the server side. A file segment corresponds to a fused transport block. Therefore, the file segment number of a file corresponds to the block sequence number of the fused transport block. Finally, the determined file segment is re-encapsulated in the corresponding fused transport block that needs to be retransmitted, and the encapsulation is fused. The transport block retransmission response is sent to the terminal side.

Optionally, when the fused transport block retransmission request includes the fused transport stream identifier and the file sequence number, acquiring the fused transport block that needs to be retransmitted in the fused transport block retransmission request includes:

Comparing the file sequence number to which the fused transport block requesting the retransmission belongs and the file sequence number of the file stream in the service index information, and determining a file to which the fused transport block requested to be retransmitted in the fused transport block retransmission request belongs;

The file is encapsulated according to the size of the fused transport block that is requested to be retransmitted into a file segment to form a fused transport block that needs to be retransmitted in the fused transport block retransmission request.

In the embodiment of the present application, the fused transport stream identifier carried in the retransmission request of the fused transport block is first found, and the corresponding fused transport stream is found from the service index information of the server side, and then the file to which the fused transport block is retransmitted according to the request belongs. Sequence number, determining the file corresponding to the fused transport block requesting retransmission, and then finding the determined file from the upper layer service entity, dividing the file into file segments according to the size of the fused transport block requested to be retransmitted, and finally dividing the file The file segment is encapsulated in the corresponding fused transport block that needs to be retransmitted, and the encapsulation is sent to the terminal side as a fused transport block retransmission response.

In this embodiment, the fused transport block retransmission request and the fused transport block retransmission request may be received through an Internet channel.

The Internet channel includes a User Datagram Protocol UDP channel and a Hypertext Transfer Protocol HTTP channel;

When the amount of data requested by the terminal side to be retransmitted is less than a threshold, the server side receives the fused transport block retransmission request and sends the fused transport block retransmission request through a UDP channel;

When the amount of data requested by the terminal side to be retransmitted is greater than a threshold, the server side receives the fused transport block retransmission request and sends the fused transport block retransmission request through an HTTP channel.

The amount of data is the amount of data of the fused transport block that is requested to be retransmitted. When the amount of CTB data requested by the terminal side to be retransmitted is less than a threshold, for example, a UDP packet threshold, the UDP protocol is used; when the amount of CTB data requested for retransmission exceeds When a UDP packet threshold is used, the HTTP protocol is used. You can set the threshold of the UDP packet to not exceed the maximum length of a UDP packet, that is, 64 Kbytes (Byte).

Referring to FIG. 16 and FIG. 17, FIG. 16 is a schematic diagram of a terminal side sending a UDP retransmission request to a server requesting retransmission, and FIG. 17 is a schematic diagram of the terminal side transmitting an HTTP retransmission request to the server requesting retransmission.

The data transmission method based on the converged transmission system provided by the embodiment of the present application can implement processing on the data to generate a converged transport stream in a unified format, and the converged transport stream can be transmitted to the broadcast network and the Internet through satellites and the like. With the converged terminal, the converged terminal can simultaneously receive the broadcast network from the satellite and the signal from the mobile communication network, and when the data received on the broadcast link such as the satellite is erroneous or lost, the converged terminal can transmit the bidirectional link through the mobile communication network. Retransmit lost or erroneous data to ensure the reliability of data reception.

Referring to FIG. 18, an embodiment of the present application provides a data transmission method based on a converged transmission system, which is applied to a terminal side, and includes steps 1801 to 1805.

Step 1801: Receive a converged transport stream.

In the embodiment of the present application, the fused transport stream sent by the server side may be received by using a satellite broadcast channel, where the fused transport stream is formed by a fused transport block.

Wherein, the satellite broadcast channel comprises an NGB-W/S channel or a DVB-S channel.

Step 1802: Parse all the converged transport blocks in the converged transport stream and cache them, where each converged transport block carries a block sequence number.

In this embodiment, the file segments encapsulated in all the converged transport blocks in the converged transport stream are parsed and cached, where each file segment carries a segment header, and the segment header includes a file segment number and a total number of file segments. And the file serial number, the segment header may further include a segment payload type, a segment payload length, and a service stream number.

Step 1803: When it is determined that the fused transport block in the fused transport stream is lost, send a fused transport block retransmission request to the server side.

Further, referring to FIG. 19, when it is determined that the fused transport block in the fused transport stream is lost, sending the fused transport block retransmission request to the server side includes steps 1901 to 1905.

Step 1901: Receive a file retransmission request of an upper layer service entity of the terminal side, where the file retransmission request includes a fused transport stream identifier and a file sequence number.

In the embodiment of the present application, after receiving the fused transport stream, the terminal side may confirm, by using various error checking methods, that the fused transport block in the received fused transport stream is lost or faulty, and the application does not perform the error check mode. limited.

In the embodiment of the present application, the file retransmission request (LSTP_FILE_GET message) further includes a service flow number, a file request number, and a file acquisition mode.

The service flow number (ISS_ID) may be an integer type, in the range of 0 to 255, indicating the number in the service flow, and the service identifier is formed by the fused transport stream identifier;

The file request number (GET_SEQ) may be an integer type, ranging from 0 to 255, the number of the file request, and the file retransmission request sent by the same service is cyclically counted;

The file acquisition mode (GET_MODE) can be an integer type, in the range of 0 to 1, indicating the file acquisition mode. When the value of the file acquisition mode is 0, it is the normal mode; when the value of the file acquisition mode is 1, it is Relative mode

Step 1902: Determine, according to the merged transport stream identifier and the file serial number, the content of the cache, and determine all segment headers and corresponding block sequence numbers.

In the embodiment of the present application, for example, the fused transport stream identifier is C, the file sequence number is C1, and the file segments C11, C13, and C15 in the cached C1 are determined, where the segment header of each of the file segments is The file segment number, the total number of file segments, the file serial number, and the block number of the corresponding fused transport block are shown in Table 2.

Table 2

Step 1903: Determine the lost fused transport block according to the segment header and the corresponding block sequence number.

In the embodiment of the present application, the file segment lost in the file may be determined according to the file segment number and the total number of file segments in the cached segment header, and then the file segment number in the segment header of the lost file segment is merged with the corresponding file segment. The block number of the transport block determines the lost fused transport block;

For example, according to Table 2, it can be determined that the file segment number of the

file segment number

2 and 4 in the file C1 is lost, and the block number of the fused transport block corresponding to the file segment with the

file segment number

2 and 4 is 4, 6, so it can be determined. The fused transport block with block numbers 4 and 6 is lost.

Step 1904: Generate a fused transport block retransmission request according to the lost fused transport block.

Step 1905: Send a fused transport block retransmission request to the server side.

The embodiment of the present application can actively request the retransmission of the missing converged transport block according to the file retransmission request of the upper layer service entity of the receiving terminal, without performing detection on the terminal side, and saving the receiving time of the converged transport block on the terminal side.

Optionally, referring to FIG. 20, when it is determined that the fused transport block in the fused transport stream is lost, sending the fused transport block retransmission request to the server side includes steps 2001 to 2006.

Step 2001: When performing file recovery on all the converged transport blocks of the cache, the file recovery duration monitoring request of the upper layer service entity of the terminal is monitored and the file recovery time is monitored, wherein the file recovery duration monitoring request includes a file sending interval.

In the embodiment of the present application, the receiving timer can be used to monitor the file recovery duration, and the file recovery duration monitoring request may further include a fused transport stream identifier, a service stream number, and an automatic repeat-request (ARQ). Switch, file sending interval, file timeout adjustment value and the next file number to be received;

The fused transport stream identifier (CTS_ID) may be an integer type, ranging from 0 to 4095, and the fused transport stream identifier is specified;

The service flow number (ISS_ID) may be an integer type, ranging from 0 to 255, specifying a service flow number, and the fused transport stream identifier constitutes a service identifier;

The ARQ switch (ARQ_SWITCH) can be of an integer type, and takes values of 0 and 1, where 1 represents automatic file retransmission, and 0 represents automatic file retransmission.

The file sending interval (FILE_INTERVAL) can be an integer type, ranging from 0 to 64000, and the file interval is sent in ms.

The file timeout adjustment value (TIME_ADJUST) may be an integer type, the value range is 0 to 64000, the timeout adjustment value is in ms, and the reception timeout timing time for the next file is the sum of FILE_INTERVAL and TIME_ADJUST.

The sequence number of the next file to be received (NEXT_FILE_SEQ) may be an integer type, and the value ranges from 0 to (2 ²⁰ -1), indicating the sequence number of the next file to be received.

Step 2002: If the file recovery time length is greater than the file sending interval duration, triggering a file retransmission request sent by the terminal side upper layer service entity, where the file retransmission request includes a fused transport stream identifier and a file sequence number.

In the embodiment of the present application, if the file recovery time length is greater than the file sending interval duration, the file retransmission request sent by the terminal side upper layer service entity is triggered, for example, the file recovery time is 3 ms, and the file sending interval is If the duration is 2 ms, then the terminal-side upper-layer service entity is actively triggered, and the upper-layer service entity actively sends a file retransmission request, and the parameters carried in the file retransmission request are referred to the foregoing embodiment.

Step 2003: Determine, according to the merged transport stream identifier and the file serial number detection cache content, all segment headers and corresponding block sequence numbers.

Step 2004: Determine the lost fused transport block according to the segment header and the corresponding block sequence number.

In the embodiment of the present application, the method for determining the lost fused transport block is described in the foregoing embodiment.

Step 2005: Generate a fused transport block retransmission request according to the lost fused transport block.

Step 2006: Send a fused transport block retransmission request to the server side.

In the embodiment of the present application, when the file is restored, the recovery time of the file is monitored in real time, the loss of the converged transport block is determined by monitoring the file recovery time, the file retransmission function is automatically triggered, the file is automatically automated, and the file can be automatically opened as needed. And the file recovery time monitoring device is closed and easy to use.

Optionally, referring to FIG. 21, when it is determined that the fused transport block in the fused transport stream is lost, sending the fused transport block retransmission request to the server side includes steps 2101 to 2105.

Step 2101: When performing file recovery on all the converged transport blocks of the cache, the file recovery duration monitoring request of the upper-layer service entity of the terminal is monitored and the file recovery duration is monitored, wherein the file recovery duration monitoring request includes a file sending interval.

Step 2102: If the file recovery time reaches the file sending interval duration, and receives a file retransmission request sent by the terminal side upper layer service entity, where the file retransmission request includes the fused transport stream identifier and the file serial number, The monitoring of the file recovery duration is stopped, and the cached content is determined according to the fused transport stream identifier and the file sequence number, and all segment headers and corresponding block sequence numbers are determined.

Step 2103: Determine the lost fused transport block according to the segment header and the corresponding block sequence number.

Step 2104: Generate a fused transport block retransmission request according to the file retransmission request and the lost fused transport block.

Step 2105: Send a fused transport block retransmission request to the server side.

In the embodiment of the present application, before the file recovery time reaches the file sending interval duration, if the terminal-side upper-layer service entity detects the missing file, the file retransmission request may be actively sent to implement the file deletion request. Passed, strong autonomy and good use.

Further, if the unfused transport block is determined to be lost according to the segment header and the corresponding block sequence number, the upper layer service entity of the terminal side is triggered to send a cancel file retransmission request, where the cancel file retransmission request includes The transport stream identifier and the file acquisition number are merged, and the cancel file retransmission request may further include a number in the service stream;

The fused transport stream identifier (CTS_ID) may be an integer type, in a range of 0 to 4095, and specifies a fused transport stream identifier.

The service flow number (ISS_ID) may be an integer type, ranging from 0 to 255, specifying a service flow number, and the fused transport stream identifier constitutes a service identifier.

The file acquisition number (GET_SEQ) may be an integer type, ranging from 0 to 255, indicating the number of the file request to be canceled.

In the embodiment of the present application, after determining that the fused transport block in the fused transport stream is lost, after transmitting the fused transport block retransmission request to the server side, if the terminal side receives the cancel file retransmission request, determining that there is no loss or error fusion. Transmitting a block to send a canceled transport block request to the server side; the canceling the transport block request includes a fused transport stream identifier and a fused transport block retransmission request number;

The fused transport stream identifier (CTS_ID) may be an integer type, ranging from 0 to 4095, to initiate a retransmitted fused transport stream identifier.

The fused transport block retransmission request number (REQ_SEQ) may be an integer type, ranging from 0 to 255, and the SSTP entity chronologically numbers the issued CTS_CTB_REQ message.

Step 1804: Receive a fused transport block retransmission response carrying the fused transport stream identifier, the number of fused transport blocks requesting retransmission, and the fused transport block data requesting retransmission.

In this embodiment, the fused transport block retransmission request and the fused transport block retransmission request may be sent through an Internet channel.

When the amount of data requested by the terminal side to be retransmitted is less than a threshold, the terminal side sends the fused transport block retransmission request and receives the fused transport block retransmission request through a UDP channel;

When the amount of data requested by the terminal side to be retransmitted is greater than a threshold, the terminal side receives the fused transport block retransmission request and receives the fused transport block retransmission request through an HTTP channel.

Step 1805: Determine, according to the fused transport stream identifier carried in the retransmission response of the fused transport block, the number of fused transport blocks requesting retransmission, and the fused transport block data that is requested to be retransmitted, to determine that the complete fused transport stream is cached. Converged transport blocks.

In the embodiment of the present application, determining, according to the fused transport stream identifier carried in the retransmission response of the fused transport block, the number of fused transport blocks requesting retransmission, and the fused transport block data requested to be retransmitted, determining the cached transport stream in the cache And parsing the file description header in the fused transport block; then performing file recovery according to the file description header and the segment header, and sending the file to an upper layer service entity on the terminal side;

The file description header includes: a service identifier, a file serial number, a file length, and a file playback duration.

In the embodiment of the present application, the foregoing method can be used to process data, and generate a unified format of the converged transport stream, which can be transmitted to the converged terminal through a broadcast network broadcast such as satellite and the Internet, and the converged terminal can receive the same at the same time. From broadcast networks such as satellites and signals from mobile communication networks, and when data received on broadcast links such as satellites are erroneous or lost, the converged terminal can retransmit lost or erroneous data over the bidirectional link of the mobile communication network. To ensure the reliability of data reception.

Referring to FIG. 22, an embodiment of the present application discloses a data transmission apparatus based on a converged transmission system, which is applied to a server side, and the apparatus includes:

The obtaining module 2201 is configured to obtain a file to be sent.

Specifically, the obtaining module 2201 is configured to obtain a file stream in the service, and divide the file stream into at least one file to be sent.

The file encapsulating module 2202 is configured to encapsulate the file in the at least one fused transport block to form a fused transport stream, where the fused transport block carries a block sequence number.

Further, the file encapsulating module 2202 includes:

A file description header adds a submodule for adding a file description header for each of the files;

a file splitting submodule, configured to divide the file to which the file description header is added into at least one file segment according to a size of the fused transport block, where each file segment carries a segment header, and the file description header is included in One of the file segments of the file;

a file segment encapsulation submodule, configured to encapsulate the file segment in a converged transport block;

The file description header includes: a service identifier, a file serial number, a file length, and a file playing duration, and the segment header includes a file segment number, a total number of file segments, and a file serial number.

Specifically, the file segment encapsulation submodule includes:

a remaining space judging submodule, configured to detect whether there is a next file to be sent if the last file segment of the file is encapsulated in the fused transport block and the fused transport block has a remaining space;

a remaining file encapsulation submodule, configured to: if the next file to be sent exists and if the size of the first file segment of the next file to be sent is equal to or smaller than the remaining space, the first file segment is encapsulated In the remaining space;

Filling a sub-module, if there is a file to be sent but the size of the first file segment of the next file to be sent is larger than the remaining space, or there is no next file to be sent, then the remaining Space is filled.

The receiving retransmission request module 2203 is configured to receive a fused transport block retransmission request from the terminal side, where the fused transport block retransmission request includes a fused transport stream identifier and a fused transport block block sequence number list requesting retransmission, or includes a fused transmission Stream ID and file serial number.

The retransmission response module 2204 is configured to obtain the fused transport block that needs to be retransmitted in the fused transport block retransmission request, and encapsulates the fused transport block into a fused transport block retransmission response and sends the retransmission response to the terminal side.

Further, when the fused transport block retransmission request includes a fused transport stream identifier and a fused transport block block sequence number list that requests retransmission, the generate retransmission response module 2204 includes:

a fused transport stream determining submodule, configured to determine, according to the correspondence between the fused transport stream identifier in the fused transport block retransmission request and the fused transport stream identifier in the service index information, to determine the fused transport block retransmission request a fused transport stream to which the fused transport block requesting retransmission belongs;

a file segment determining submodule, configured to compare the fused transport block block sequence number list requesting retransmission with information of all fused transport blocks corresponding to the file stream in the service index information, to determine the fused transport block retransmission request a file segment corresponding to the fused transport block requesting retransmission;

a file segment encapsulating retransmission submodule, configured to re-encapsulate the file segment to form a fused transport block that needs to be retransmitted in the fused transport block retransmission request;

When the fused transport block retransmission request includes the fused transport stream identifier and the file sequence number, the generating the retransmission response module 2204 includes:

a determining submodule, configured to determine, according to the correspondence between the fused transport stream identifier in the fused transport block retransmission request and the fused transport stream identifier in the service index information, to request retransmission in the fused transport block retransmission request a converged transport stream to which the converged transport block belongs;

a file determining submodule, configured to compare a file sequence number to which the fused transport block requesting retransmission belongs and a file sequence number of the file stream in the service index information, to determine a fusion requesting retransmission in the fused transport block retransmission request The file to which the transport block belongs;

The file encapsulation retransmission sub-module is configured to divide the fused transport block size that is requested to be retransmitted into a file segment for encapsulation, and form a fused transport block that needs to be retransmitted in the retransmission request of the fused transport block.

Further, the device further includes:

a service index information generating module, configured to generate service index information of all the converged transport blocks under the same service,

The service index information includes a fused transport stream identifier, a file sequence number in the file stream, and information of all fused transport blocks corresponding to the file stream, where the information includes a block sequence number of the first fused transport block corresponding to the file stream, and The number of fused transport blocks generated after file stream encapsulation.

Optionally, the device sends the fused transport stream to the terminal side through a satellite broadcast channel;

Receiving the fused transport block retransmission request and transmitting the fused transport block retransmission response over an internet channel.

Optionally, the satellite broadcast channel comprises an NGB-W/S channel or a DVB-S channel.

Optionally, the Internet channel includes a User Datagram Protocol UDP channel and a Hypertext Transfer Protocol (HTTP) channel;

The data transmission device based on the converged transmission system disclosed in the embodiment of the present application can implement data processing to generate a converged transport stream in a unified format, and the converged transport stream can be transmitted to the converged terminal through a broadcast network broadcast such as satellite and the Internet. The converged terminal can simultaneously receive signals from a broadcast network such as a satellite and from a mobile communication network, and when data received on a broadcast link such as a satellite is erroneous or lost, the converged terminal can retransmit the bidirectional link through the mobile communication network. Lost or erroneous data to ensure the reliability of data reception.

Referring to FIG. 23, the embodiment of the present application discloses a data transmission device based on a fusion transmission system, which is applied to a terminal side, and the device includes:

The fused transport stream receiving module 2301 is configured to receive the fused transport stream.

The fused transport block parsing module 2302 is configured to parse and cache all the fused transport blocks in the fused transport stream, where each fused transport block carries a block sequence number to the cache module.

Specifically, the fused transport block parsing module 2302 is configured to parse the file segments encapsulated in all the fused transport blocks in the fused transport stream and cache the file segments into the cache module, where each file segment carries a segment header. The segment header includes a file segment number, a total number of file segments, and a file serial number.

The transmit retransmission request module 2303 is configured to send a fused transport block retransmission request to the server side when the fused transport block in the fused transport stream is lost.

Further, the sending retransmission request module 2303 includes:

a file retransmission request receiving submodule, configured to receive a file retransmission request of an upper layer service entity of the terminal side, where the file retransmission request includes a converged transport stream identifier and a file serial number;

a cache detection sub-module, configured to detect, according to the merged transport stream identifier and the file serial number, a cached content, and determine a sequence header and a corresponding block sequence number;

a file determining submodule, configured to determine a lost converged transport block according to the segment header and the corresponding block sequence number;

a first retransmission request generating submodule, configured to generate a fused transport block retransmission request according to the lost fused transport block;

The first sending submodule is configured to send a fused transport block retransmission request to the server side.

Optionally, the sending retransmission request module 2303 further includes:

The first monitoring sub-module is configured to receive a file recovery duration monitoring request of the upper-layer service entity of the terminal and monitor the file recovery duration, where the file recovery time monitoring request includes File sending interval;

The file retransmission request triggering submodule is configured to trigger a file retransmission request sent by the terminal side upper layer service entity if the file recovery time length is greater than the file sending interval duration, where the file retransmission request includes the fused transport stream Identification and file serial number;

a cache content determining submodule, configured to determine, according to the merged transport stream identifier and the file serial number, the cached content, and determine a total number of segments and corresponding block numbers;

a file segment determining submodule, configured to determine a lost merged transport block according to the segment header and the corresponding block sequence number;

a second retransmission request generating submodule, configured to generate a fused transport block retransmission request according to the lost fused transport block;

The second sending submodule is configured to send the fused transport block retransmission request to the server side.

The receiving retransmission response module 2304 is configured to receive a fused transport block retransmission response carrying the fused transport stream identifier, the number of fused transport blocks requesting retransmission, and the fused transport block data requesting retransmission;

The fused transport block complete module 2305 is configured to determine, according to the fused transport stream identifier carried in the retransmission response of the fused transport block, the number of fused transport blocks requesting retransmission, and the fused transport block data requested to be retransmitted, to determine that the complete cache is cached. A converged transport block in a converged transport stream.

Optionally, the sending retransmission request module 2303 further includes:

The second monitoring sub-module is configured to: when receiving file recovery of all the converged transport blocks of the cache, receive a file recovery duration monitoring request of the upper-layer service entity of the terminal side, and monitor the file recovery duration, where the file recovery duration monitoring request includes File sending interval;

The file retransmission request automatic receiving submodule is configured to: before the file recovery time reaches the file sending interval duration, receive a file retransmission request sent by the terminal side upper layer service entity, where the file retransmission request includes fusion Transmitting the flow identifier and the file serial number, stopping monitoring the recovery time of the file, and detecting the cached content according to the merged transport stream identifier and the file serial number, and determining all segment headers and corresponding block serial numbers;

a fused transport block missing submodule, configured to determine a lost fused transport block according to the segment header and the corresponding block sequence number;

a third retransmission request generating submodule, configured to generate a fused transport block retransmission request according to the lost fused transport block;

The third sending submodule is configured to send the fused transport block retransmission request to the server side.

Optionally, the device further includes:

a canceling a file retransmission requesting module, configured to determine, according to the segment header and the corresponding block sequence number, that the unfused transport block is lost, triggering an upper layer service entity of the terminal side to send a cancel file retransmission request, where the canceling The file retransmission request includes a converged transport stream identifier and a file acquisition number.

Optionally, the device further includes:

The block retransmission request module is configured to send a cancel converged transport block request to the server side, where the unfused transport block request includes a fused transport stream identifier and a fused transport block retransmission request number.

Optionally, the device further includes:

a file description header parsing module, configured to parse a file description header in the converged transport block;

a file recovery module, configured to perform file recovery according to the file description header and the segment header, and send the file to an upper layer service entity of the terminal side;

Optionally, the apparatus receives the fused transport block sent by the server side by using a satellite broadcast channel;

Transmitting the fused transport block retransmission request and receiving the fused transport block retransmission response over an internet channel.

Optionally, the Internet channel includes a User Datagram Protocol UDP channel and a Hypertext Transfer Protocol HTTP channel;

The above is a schematic diagram of a data transmission apparatus based on a converged transport block system of the present embodiment. It should be noted that the technical solution of the data transmission device based on the fused transport block system belongs to the same concept as the technical solution of the data transmission method based on the fused transport block system, and the technical solution of the data transmission device based on the fused transport block system is not For details of the detailed description, reference may be made to the description of the technical solution of the data transmission method based on the fused transport block system described above.

An embodiment of the present application further provides a computing device, including a memory, a processor, and a computer program stored on the memory and operable on the processor, the processor implementing the program to implement the following steps:

Get the file to be sent;

The embodiment of the present application further provides a computing device, including a memory, a processor, and a computer program stored on the memory and operable on the processor, where the processor implements the following steps:

Receiving a converged transport stream;

It should be noted that the computing device may be a computing device such as a desktop computer, a notebook, a palmtop computer, or a mobile terminal.

The processor may be a central processing unit (CPU), or may be other general-purpose processors, a digital signal processor (DSP), an application specific integrated circuit (ASIC), and an off-the-shelf device. Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like, which is a control center of the terminal, and connects various parts of the entire terminal using various interfaces and lines.

The memory mainly includes a storage program area and a storage data area, wherein the storage program area can store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.); and the storage data area can be stored according to Data created by the use of the mobile phone (such as audio data, phone book, etc.). In addition, the memory may include a high-speed random access memory, and may also include non-volatile memory such as a hard disk, a memory, a plug-in hard disk, a smart memory card (SMC), and a Secure Digital (SD) card. , Flash Card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.

An embodiment of the present application further provides a computer readable storage medium storing a computer program, when the computer program is executed by a processor, implementing the fusion transmission system based on the application side as described above The steps in the data transfer method.

An embodiment of the present application further provides a computer readable storage medium storing a computer program, when the computer program is executed by a processor, implementing the fusion transmission system based on the application to the terminal side The steps in the data transfer method.

The above is a schematic illustration of a computer readable storage medium of the present embodiment. It should be noted that the technical solution of the storage medium belongs to the same concept as the technical solution of the data transmission method based on the fused transport block system, and the details of the technical solution of the storage medium are not described in detail. A description of the technical solution of the system's data transmission method.

The computer instructions include computer program code, which may be in the form of source code, an object code, an executable, or some intermediate form. The computer readable medium may include any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM). , random access memory (RAM, Random Access Memory), electrical carrier signals, telecommunications signals, and software distribution media. It should be noted that the content contained in the computer readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in a jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, computer readable media Does not include electrical carrier signals and telecommunication signals.

It should be noted that, for the foregoing method embodiments, for the sake of brevity, they are all described as a series of action combinations, but those skilled in the art should understand that the present application is not limited by the described action sequence. Because certain steps may be performed in other sequences or concurrently in accordance with the present application. In the following, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

In the above embodiments, the descriptions of the various embodiments are all focused, and the parts that are not detailed in a certain embodiment can be referred to the related descriptions of other embodiments.

The preferred embodiments of the present application disclosed above are only intended to assist in the description of the present application. The various embodiments are not described in detail, and the invention is not limited to the specific embodiments. Obviously, many modifications and variations are possible in light of the teachings herein. The present invention has been selected and described in detail to explain the principles of the invention and the application of the invention. This application is only limited by the scope of the claims and the full scope and equivalents thereof.

Claims

A data transmission method based on a converged transmission system is applied to a server side, and is characterized in that it comprises:

Get the file to be sent;

Encapsulating the file in the at least one fused transport block to form a fused transport stream to be sent to the terminal side, where each fused transport block carries a block sequence number;

Receiving a fused transport block retransmission request from the terminal side, where the fused transport block retransmission request includes a fused transport stream identifier and a fused transport block block sequence number list requesting retransmission, or includes a fused transport stream identifier and a file sequence number;

Obtaining a fused transport block that needs to be retransmitted in the fused transport block retransmission request, and encapsulating the fused transport block into a fused transport block retransmission response to be sent to the terminal side.
The method according to claim 1, wherein the obtaining the file to be sent comprises:

Obtaining a file stream in the service, and dividing the file stream into at least one file to be sent.
The method according to claim 2, further comprising: after the file is encapsulated in the at least one fused transport block, further comprising:

Generate service index information of all converged transport blocks under the same service.

The service index information includes a fused transport stream identifier, a file sequence number in the file stream, and information of all fused transport blocks corresponding to the file stream, where the information includes a block sequence number of the first fused transport block corresponding to the file stream, and The number of fused transport blocks generated after file stream encapsulation.
The method of claim 3, wherein the encapsulating the file in the at least one fused transport block comprises:

Add a file description header for each of the files;

Splitting the file with the file description header into at least one file segment according to the size of the fused transport block, wherein each file segment carries a segment header, and the file description header is included in one of the files of the file In the paragraph;

Encapsulating the file segment in a converged transport block;

The file description header includes: a service identifier, a file serial number, a file length, and a file playing duration, and the segment header includes a file segment number, a total number of file segments, and a file serial number.
The method of claim 4 wherein:

When the fused transport block retransmission request includes the fused transport stream identifier and the fused transport block block sequence number list that is requested to be retransmitted, obtaining the fused transport block that needs to be retransmitted in the fused transport block retransmission request includes:

Determining, according to the correspondence between the fused transport stream identifier in the fused transport packet retransmission request and the fused transport stream identifier in the service index information, determining that the fused transport block requested to be retransmitted in the fused transport block retransmission request belongs to Converged transport stream;

Comparing the fused transport block block sequence number list that is requested to be retransmitted with the information of all the fused transport blocks corresponding to the file stream in the service index information, and determining that the fused transport block requesting retransmission in the fused transport block retransmission request corresponds to File segment

Re-encapsulating the file segment to form a fused transport block that needs to be retransmitted in the fused transport block retransmission request;

When the fused transport block retransmission request includes the fused transport stream identifier and the file sequence number, the fused transport block that needs to be retransmitted in the fused transport block retransmission request includes:

Determining, according to the correspondence between the fused transport stream identifier in the fused transport packet retransmission request and the fused transport stream identifier in the service index information, determining that the fused transport block requested to be retransmitted in the fused transport block retransmission request belongs to Converged transport stream;

Comparing the file sequence number to which the fused transport block requesting the retransmission belongs and the file sequence number of the file stream in the service index information, and determining a file to which the fused transport block requested to be retransmitted in the fused transport block retransmission request belongs;

The file is encapsulated according to the size of the fused transport block that is requested to be retransmitted into a file segment to form a fused transport block that needs to be retransmitted in the fused transport block retransmission request.
The method according to claim 4, wherein the encapsulating the file segment in the fused transport block comprises:

If the last file segment of the file is encapsulated in the fused transport block and the fused transport block has a remaining space, detecting whether there is a file to be sent next;

If the next file to be sent exists and if the size of the first file segment of the next file to be sent is equal to or smaller than the remaining space, the first file segment is encapsulated in the remaining space;

If there is a next file to be sent but the size of the first file segment of the next file to be sent is larger than the remaining space, the first file segment is encapsulated in the remaining space; The remaining space is filled.
The method of claim 1 wherein

Transmitting the fused transport stream to the terminal side through a satellite broadcast channel;

Receiving the fused transport block retransmission request and transmitting the fused transport block retransmission response over an internet channel.
The method of claim 7 wherein said satellite broadcast channel comprises a next generation broadcast television wireless NGB-W/S channel or a digital satellite broadcast system DVB-S channel.
The method according to claim 7, wherein said Internet channel comprises a User Datagram Protocol UDP channel and a Hypertext Transfer Protocol HTTP channel;

When the amount of data requested by the terminal side to be retransmitted is less than a threshold, the server side receives the fused transport block retransmission request and sends the fused transport block retransmission request through a UDP channel;

When the amount of data requested by the terminal side to be retransmitted is greater than a threshold, the server side receives the fused transport block retransmission request and sends the fused transport block retransmission request through an HTTP channel.
A data transmission method based on a fused transport block system is applied to a terminal side, and is characterized in that it comprises:

Receiving a converged transport stream;

Parsing and converging all the converged transport blocks in the converged transport stream, where each converged transport block carries a block sequence number;

When it is determined that the fused transport block in the fused transport stream is lost, sending a fused transport block retransmission request to the server side;

Receiving a fused transport block retransmission response carrying the fused transport stream identifier, the number of fused transport blocks requesting retransmission, and the fused transport block data requesting retransmission;

Determining, according to the fused transport stream identifier carried in the retransmission response of the fused transport block, the number of fused transport blocks requesting retransmission, and the fused transport block data requesting retransmission, determining that the fused transport block in the fused transport stream is buffered .
The method of claim 10, wherein parsing all of the fused transport blocks in the fused transport stream and caching comprises:

A file segment encapsulated in all the converged transport blocks in the converged transport stream is parsed and cached, wherein each file segment carries a segment header, and the segment header includes a file segment number, a total number of file segments, and a file serial number.
The method according to claim 11, wherein when determining that the fused transport block in the fused transport stream is lost, transmitting the fused transport block retransmission request to the server side comprises:

Receiving a file retransmission request of an upper layer service entity of the terminal side, where the file retransmission request includes a converged transport stream identifier and a file serial number;

Determining, according to the merged transport stream identifier and the file serial number, the content of the cache, and determining a total number of the segment header and the corresponding block;

Determining a lost fused transport block according to the segment header and the corresponding block sequence number;

Generating a fused transport block retransmission request according to the lost fused transport block;

A fused transport block retransmission request is sent to the server side.
The method according to claim 11, wherein when determining that the fused transport block in the fused transport stream is lost, transmitting the fused transport block retransmission request to the server side comprises:

When the file is restored, the file recovery time monitoring request of the upper layer service entity of the terminal is monitored and the file recovery time is monitored, where the file recovery time monitoring request includes a file sending interval;

And if the file recovery time length is greater than the file sending interval duration, triggering a file retransmission request sent by the terminal side upper layer service entity, where the file retransmission request includes a fused transport stream identifier and a file serial number;

Determining, according to the fused transport stream identifier and the file serial number, the contents of the cache, and determining the total number of the segment header and the corresponding block;

Determining a lost fused transport block according to the segment header and the corresponding block sequence number;

Generating a fused transport block retransmission request according to the lost fused transport block;

A fused transport block retransmission request is sent to the server side.
The method according to claim 11, wherein when determining that the fused transport block in the fused transport stream is lost, transmitting the fused transport block retransmission request to the server side comprises:

When the file is restored, the file recovery time monitoring request of the upper layer service entity of the terminal is monitored and the file recovery time is monitored, where the file recovery time monitoring request includes a file sending interval;

Receiving a file retransmission request sent by the upper layer service entity of the terminal side before the file recovery time reaches the file sending interval duration, where the file retransmission request includes the fused transport stream identifier and the file serial number, Performing monitoring of the file recovery duration and determining the cached content according to the merged transport stream identifier and the file sequence number, and determining all segment headers and corresponding block sequence numbers;

Determining a lost fused transport block according to the segment header and the corresponding block sequence number;

Generating a fused transport block retransmission request according to the lost fused transport block;

A fused transport block retransmission request is sent to the server side.
The method according to any one of claims 12-14, wherein after determining the all the segment headers and the corresponding block numbers according to the content of the merged transport stream identifier and the file serial number detection cache, the method further includes:

Determining, by the segment header and the corresponding block sequence number, that the unfused transport block is lost, triggering the upper layer service entity of the terminal side to send a cancel file retransmission request, where the cancel file retransmission request includes the fused transport stream identifier And file get number.
The method according to claim 15, wherein after determining that the fused transport block in the fused transport stream is lost, after transmitting the fused transport block retransmission request to the server side, the method further includes:

Sending a cancel fused transport block request to the server side; the cancel fused transport block request includes a fused transport stream identifier and a fused transport block retransmission request number.
The method according to claim 11, wherein the cache is determined according to the fused transport stream identifier carried in the retransmission response of the fused transport block, the number of fused transport blocks requesting retransmission, and the fused transport block data requested to be retransmitted. After the complete fused transport block in the fused transport stream, the method further includes:

Parsing a file description header in the converged transport block;

Performing file recovery according to the file description header and the segment header, and sending the file to an upper layer upper layer service entity;

The file description header includes: a service identifier, a file serial number, a file length, and a file playback duration.
The method of claim 10 wherein:

Receiving, by the satellite broadcast channel, the fused transport block sent by the server side;

Transmitting the fused transport block retransmission request and receiving the fused transport block retransmission response over an internet channel.
The method of claim 18 wherein said satellite broadcast channel comprises a next generation broadcast television wireless NGB-W/S channel or a digital satellite broadcast system DVB-S channel.
The method of claim 18 wherein said internet channel comprises a User Datagram Protocol UDP channel and a Hypertext Transfer Protocol HTTP channel;

When the amount of data requested by the terminal side to be retransmitted is less than a threshold, the terminal side sends the fused transport block retransmission request and receives the fused transport block retransmission request through a UDP channel;

When the amount of data requested by the terminal side to be retransmitted is greater than a threshold, the terminal side receives the fused transport block retransmission request and receives the fused transport block retransmission request through an HTTP channel.
A computing device comprising a memory, a processor, and a computer program stored on the memory and operable on the processor, wherein the processor performs the following steps when executing the program:

Get the file to be sent;

Encapsulating the file in the at least one fused transport block to form a fused transport stream to be sent to the terminal side, where each fused transport block carries a block sequence number;

Receiving a fused transport block retransmission request from the terminal side, where the fused transport block retransmission request includes a fused transport stream identifier and a fused transport block block sequence number list requesting retransmission, or includes a fused transport stream identifier and a file sequence number;

Obtaining a fused transport block that needs to be retransmitted in the fused transport block retransmission request, and encapsulating the fused transport block into a fused transport block retransmission response to be sent to the terminal side.
A computing device comprising a memory, a processor, and a computer program stored on the memory and operable on the processor, wherein the processor performs the following steps when executing the program:

Receiving a converged transport stream;

Parsing and converging all the converged transport blocks in the converged transport stream, where each converged transport block carries a block sequence number;

When it is determined that the fused transport block in the fused transport stream is lost, sending a fused transport block retransmission request to the server side;

Receiving a fused transport block retransmission response carrying the fused transport stream identifier, the number of fused transport blocks requesting retransmission, and the fused transport block data requesting retransmission;

Determining, according to the fused transport stream identifier carried in the retransmission response of the fused transport block, the number of fused transport blocks requesting retransmission, and the fused transport block data requesting retransmission, determining that the fused transport transport block in the cached transport transport stream is complete.
A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program, the computer program being executed by a processor to implement the fusion transmission system according to any one of claims 1-9 The steps in the data transmission method or the steps in the data transmission method based on the fusion transmission system according to any one of claims 10-20.