WO2022012210A1 - 数据的封装方法、装置、系统及计算机可读存储介质 - Google Patents

数据的封装方法、装置、系统及计算机可读存储介质 Download PDF

Info

Publication number
WO2022012210A1
WO2022012210A1 PCT/CN2021/098392 CN2021098392W WO2022012210A1 WO 2022012210 A1 WO2022012210 A1 WO 2022012210A1 CN 2021098392 W CN2021098392 W CN 2021098392W WO 2022012210 A1 WO2022012210 A1 WO 2022012210A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
encapsulation
format
transmitted
service
Prior art date
Application number
PCT/CN2021/098392
Other languages
English (en)
French (fr)
Inventor
尹华镜
朱钧
翦林鹏
王元鹏
Original Assignee
深圳思凯微电子有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳思凯微电子有限公司 filed Critical 深圳思凯微电子有限公司
Publication of WO2022012210A1 publication Critical patent/WO2022012210A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/06—Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]

Definitions

  • the present application relates to the technical field of digital information transmission, in particular to a digital broadcasting system supporting data information transmission in multiple formats, and in particular to a data encapsulation method, device, system and computer-readable storage medium.
  • the data encapsulation method of the digital broadcasting system mainly encapsulates all the data to be transmitted according to the data encapsulation method defined by its own system, and cannot encapsulate the data to be transmitted in a corresponding way according to the data characteristics of the data to be transmitted, resulting in broadband loss. . It can be seen from this that the data encapsulation method of the current digital broadcasting system cannot classify and encapsulate the data to be transmitted, and the bandwidth loss is large.
  • the main purpose of the present application is to provide a data encapsulation method, device, system and computer-readable storage medium, aiming to solve the problem that the data encapsulation method of the current digital broadcasting system cannot classify and encapsulate the data to be transmitted, and the technology with large bandwidth loss problem.
  • the present application provides a data encapsulation method, the data encapsulation method comprising the following steps:
  • Receive the data to be transmitted classify the data according to the data identifier and the transmission requirement in the data to be transmitted, and determine the data type corresponding to the data to be transmitted;
  • a corresponding data encapsulation rule is determined according to the data encapsulation format, and the data encapsulation package is encapsulated according to the data encapsulation rule.
  • the step of determining a corresponding data encapsulation rule according to the data encapsulation format, and encapsulating the data encapsulation package by using the data encapsulation rule includes:
  • the data encapsulation format is a message packet encapsulation format, then determine that the data encapsulation packet is a message encapsulation packet, and determine that the data encapsulation rule is a message packet encapsulation rule;
  • the message encapsulation packet is encapsulated into a second message sub-channel.
  • the step of determining a corresponding data encapsulation rule according to the data encapsulation format, and encapsulating the data encapsulation package by using the data encapsulation rule includes:
  • the data encapsulation format is a business flow encapsulation format, then determine that the data encapsulation package is a business encapsulation package, and determine that the data encapsulation rule is a business flow encapsulation rule;
  • the second channel length remaining in the second service sub-channel after the first service encapsulation package is encapsulated is detected, and the service encapsulation package is segmented and encapsulated into the first service encapsulation package. a traffic sub-channel and the second traffic sub-channel.
  • the step of determining the encapsulation format code corresponding to the data to be transmitted according to the data type, and determining the corresponding data encapsulation format according to the encapsulation format code includes:
  • the step of converting the to-be-transmitted data into a corresponding data encapsulation package according to the data encapsulation format includes:
  • the data encapsulation format is a message packet encapsulation format
  • the to-be-transmitted data is converted into a message encapsulation packet
  • the to-be-transmitted data is converted into a service encapsulation package.
  • the receiving data to be transmitted is classified according to the data identifier and the transmission requirement in the data to be transmitted, and the step of determining the data type corresponding to the data to be transmitted includes:
  • Receive the data to be transmitted obtain the data identifier and data parameter transmission type in the data to be transmitted, classify the data to be transmitted in combination with the data identifier and the data parameter transmission type, and determine the data to be transmitted The data type corresponding to the data.
  • the method before the step of receiving the data to be transmitted, classifying the data to be transmitted according to a data identifier and a transmission requirement, and determining the data type corresponding to the data to be transmitted, the method further includes:
  • the input data format is sent to the upper-layer application, so that the upper-layer application can convert the data format of the data to be sent into the input data format to obtain the to-be-transmitted data.
  • the present application also provides a data encapsulation device, and the data encapsulation device includes:
  • the receiving module is used to receive the data to be transmitted
  • a classification module configured to classify according to the data identification and transmission requirements in the data to be transmitted, and determine the data type corresponding to the data to be transmitted;
  • a determining module configured to determine the encapsulation format code corresponding to the data to be transmitted according to the data type, and determine the corresponding data encapsulation format according to the encapsulation format code;
  • a conversion module for converting the data to be transmitted into a corresponding data package according to the data package format
  • the determining module is further configured to determine a corresponding data encapsulation rule according to the data encapsulation format
  • An encapsulation module configured to encapsulate the data to be transmitted according to the data encapsulation rule.
  • the present application also provides a data encapsulation system
  • the data encapsulation system includes a memory, a processor, and a data encapsulation program stored on the memory and running on the processor, When the data encapsulation procedure is completed by the processor, the steps of the data encapsulation method as described above are implemented.
  • the present application also provides a computer-readable storage medium on which a data encapsulation program is stored, and the data encapsulation program is completed by a processor to realize the above-mentioned The steps of the encapsulation method of the data.
  • the present application realizes that by receiving the data to be transmitted, classifying the data according to the data identification and transmission requirements in the data to be transmitted, determining the data type corresponding to the data to be transmitted, determining the encapsulation format code corresponding to the data to be transmitted according to the data type, and determining according to the encapsulation format encoding
  • the corresponding data encapsulation format, and according to the data encapsulation format, the data to be transmitted is converted into a corresponding data encapsulation package, the corresponding data encapsulation rule is determined according to the data encapsulation format, and the data encapsulation package is encapsulated by the data encapsulation rule.
  • the data to be transmitted needs to be classified according to the data identification and transmission requirements, and then the encapsulation format code corresponding to the to-be-transmitted data is determined, and the corresponding data encapsulation format is determined according to the encapsulation format code, and then according to The data encapsulation format determines the corresponding data encapsulation rules, and encapsulates the data encapsulation package through the data encapsulation rules, which realizes the design of the data to be transmitted according to the characteristics and transmission requirements of the data to be transmitted, thus realizing the different classification of the data to be transmitted. Data encapsulation is performed through different data encapsulation rules, thereby reducing bandwidth consumption.
  • FIG. 1 is a schematic flowchart of a first embodiment of a method for encapsulating data of the present application
  • FIG. 2 is a schematic diagram of an encapsulation format of a message encapsulation package according to the first embodiment of the data analysis method of the present application;
  • FIG. 3 is a schematic diagram of a service flow encapsulation format of a service encapsulation package according to the first embodiment of the data analysis method of the present application;
  • FIG. 4 is a schematic diagram of the service package encapsulation format of the service package package of the first embodiment of the data analysis method of the present application;
  • FIG. 5 is a schematic diagram of a message packet encapsulation rule according to the first embodiment of the data analysis method of the present application
  • FIG. 6 is a schematic diagram of a service flow encapsulation rule according to the first embodiment of the data analysis method of the present application.
  • FIG. 7 is a schematic diagram of a service package encapsulation rule according to the first embodiment of the data analysis method of the present application.
  • FIG. 8 is a schematic diagram of the input data format of the system configuration information of the first embodiment of the data analysis method of the present application.
  • FIG. 9 is a schematic diagram of the input data format of the message data in the first embodiment of the data analysis method of the present application.
  • FIG. 10 is a schematic diagram of the input data format of the business data of the first embodiment of the data analysis method of the present application.
  • 11 is a schematic diagram of the process of mapping the service payload to the interleaving block according to the second embodiment of the data analysis method of the present application;
  • FIG. 12 is a preferred structural schematic diagram of the packaging device of the data of the present application.
  • FIG. 13 is a schematic structural diagram of a hardware operating environment involved in the solution of the embodiment of the present application.
  • FIG. 1 is a schematic flowchart of the first embodiment of the data encapsulation method of the application
  • FIG. 2 is the message encapsulation of the first embodiment of the data encapsulation method of the application.
  • FIG. 3 is a schematic diagram of the service flow encapsulation format of the service encapsulation package of the first embodiment of the encapsulation method of the application data
  • FIG. 1 is a schematic flowchart of the first embodiment of the data encapsulation method of the application
  • FIG. 2 is the message encapsulation of the first embodiment of the data encapsulation method of the application.
  • FIG. 3 is a schematic diagram of the service flow encapsulation format of the service encapsulation package of the first embodiment of the encapsulation method of the application data
  • FIG. 4 is a schematic diagram of the service package encapsulation format of the service encapsulation package of the first embodiment of the encapsulation method of the application data
  • 5 is a schematic diagram of the message packet encapsulation rules of the first embodiment of the encapsulation method of the application data
  • FIG. 6 is a schematic diagram of the service flow encapsulation rules of the first embodiment of the encapsulation method of the application data
  • FIG. 7 is the encapsulation method of the application data.
  • FIG. 8 is a schematic diagram of the input data format of the system configuration information of the first embodiment of the encapsulation method of the application data
  • FIG. 9 is the input of the message data of the first embodiment of the encapsulation method of the application data Schematic diagram of data format;
  • FIG. 10 is a schematic diagram of the input data format of service data of the first embodiment of the encapsulation method of the application data;
  • FIG. 10 is a schematic diagram of the input data format of service data of the first embodiment of the encapsulation method of the application data;
  • Embodiments of the present application provide embodiments of data encapsulation methods. It should be noted that, although a logical sequence is shown in the flowchart, under certain data, the shown or described steps.
  • Data encapsulation methods include:
  • Step S10 Receive the data to be transmitted, classify according to the data identifier in the data to be transmitted and the transmission requirement, and determine the data type corresponding to the data to be transmitted.
  • the digital broadcasting system receives the data to be transmitted sent by the upper-layer application, then obtains the data identifier in the data to be transmitted, determines the service type of the data to be transmitted according to the mapping relationship between the data identifier and the service type, and obtains the data transmission mode corresponding to the data to be transmitted, Then, the data to be transmitted is classified according to the service type and the data transmission mode, and the data type corresponding to the to-be-transmitted data is determined.
  • the upper-layer application includes but is not limited to a new digital broadcasting system, in this embodiment, it particularly refers to a symbiotic FM data broadcasting (CD-Radio) system, and other digital broadcasting systems.
  • Service types include but are not limited to system configuration information, message data and service data.
  • the system configuration information includes, but is not limited to, physical layer transmitter function control parameters, message data transmission control parameters, and service data transmission control parameters.
  • the message data includes system message data and user message data.
  • the system message data comes from the system configuration information and is used to transmit control information at the physical layer.
  • the user message data is a function of the upper-layer application and is used to transmit brief data and determined content data.
  • the business data includes business flow data and business package data.
  • Data transmission methods include but are not limited to message packet transmission methods, service stream transmission methods, and service packet transmission methods.
  • Data types include, but are not limited to, physical layer configuration parameters, system information, user messages, service flows, and service packets.
  • step S10 includes:
  • Step a Receive the data to be transmitted, and obtain the data identifier and data parameter transmission type in the data to be transmitted, classify the data to be transmitted in combination with the data identifier and the data parameter transmission type, and determine the data to be transmitted. Describe the data type corresponding to the data to be transmitted.
  • the digital broadcasting system receives the data to be transmitted sent by the upper-layer application, then obtains the data identifier of the link layer interface in the data to be transmitted, determines the service type corresponding to the data to be transmitted according to the preset data mapping table in the digital broadcasting system, and then Obtain the data parameter transmission type in the data to be transmitted, classify the service type and the data parameter transmission type, and determine the data type corresponding to the data to be transmitted.
  • the link layer interface is a part of the data format in the data to be transmitted.
  • the preset data mapping table is pre-set in the digital broadcasting system according to requirements, which is not limited in this embodiment.
  • Data parameter transmission types include, but are not limited to, system information packet transmission, user message packet transmission, service flow transmission, and service packet transmission, where both system information packet transmission and user message packet transmission belong to message packet transmission.
  • Message packet transmission is applied to the transmission of various types of message data. Both service stream transmission and service packet transmission are applied to the transmission process of service data.
  • Service stream transmission is used in scenarios where there is no integrity check of the data to be transmitted during the data transmission process.
  • Service packet transmission has a certain structure, and can perform integrity detection on the received data to be transmitted. It is mainly used in scenarios where the data to be transmitted is sensitive to data missing and accuracy during the data transmission process.
  • the data format of the data to be transmitted is data identifier + data length or data number + data transmission control parameter field or upper layer application control parameter field + data transmission system parameter field or data content field.
  • the mapping relationship between data identifiers and service types in the preset data mapping table is that data identifier 0x00 corresponds to system configuration information, data identifier 0x01 corresponds to message data, and data identifier 0x02 corresponds to service data.
  • the digital broadcasting system receives The data identifier in the data to be transmitted is 0x01, the data parameter transmission type obtained in the data to be transmitted is user message packet transmission, and the digital broadcasting system determines that the data type of the received data to be transmitted is user message.
  • Step S20 determining the encapsulation format code corresponding to the data to be transmitted according to the data type, determining the corresponding data encapsulation format according to the encapsulation format encoding, and converting the to-be-transmitted data into a corresponding data encapsulation format according to the data encapsulation format.
  • Data encapsulation package determining the encapsulation format code corresponding to the data to be transmitted according to the data type, determining the corresponding data encapsulation format according to the encapsulation format encoding, and converting the to-be-transmitted data into a corresponding data encapsulation format according to the data encapsulation format.
  • the digital broadcasting system determines the data type corresponding to the data to be transmitted, it determines the encapsulation format code corresponding to the data to be transmitted according to the mapping relationship between the data type and the encapsulation format code in the digital broadcasting system, and then according to the encapsulation format code and the data encapsulation format, the digital broadcasting system
  • the mapping relationship determines the data encapsulation format corresponding to the data to be transmitted, and then converts the to-be-transmitted data into a data encapsulation package corresponding to the data encapsulation format.
  • mapping relationship between the data type and the encapsulation format code in the digital broadcasting system and the mapping relationship between the encapsulation format encoding and the data encapsulation format in the digital broadcasting system are pre-set in the digital broadcasting system, which are not limited in this embodiment.
  • step S20 includes:
  • Step b obtaining a format coding mapping table, and determining the corresponding encapsulation format coding of the data to be transmitted in the format coding mapping table according to the data type;
  • Step c obtaining an encapsulation format mapping table, and determining a data encapsulation format corresponding to the data to be transmitted according to the encapsulation format mapping table and the encapsulation format code.
  • the digital broadcasting system obtains the format encoding mapping table in the digital broadcasting system, determines the encapsulation format encoding corresponding to the data to be transmitted according to the mapping relationship between the data type and the encapsulation format encoding in the format encoding mapping table, and then obtains the encoding in the digital broadcasting system.
  • the encapsulation format mapping table according to the mapping relationship between the encapsulation format code and the data encapsulation format in the encapsulation format mapping table, to determine the data encapsulation format corresponding to the data to be transmitted.
  • the format encoding mapping table and the encapsulation format mapping table are preset in the digital broadcasting system according to your requirements, which are not limited in this embodiment.
  • the mapping relationship between the data type and the encapsulation format encoding in the format encoding mapping table is that the system information corresponds to encapsulation format encoding 1, the user message corresponds to encapsulation format encoding 2, the service stream corresponds to encapsulation format encoding 3, and the service package corresponds to Encapsulation format code 4.
  • the encapsulation format code 1 corresponds to the system message packet encapsulation format
  • the encapsulation format code 2 corresponds to the user message packet encapsulation format
  • the encapsulation format code 3 corresponds to the service stream encapsulation format and encapsulation format.
  • Format code 4 corresponds to the service package encapsulation format. If the data type of the data to be transmitted acquired by the digital broadcasting system is a user message, it is determined that the encapsulation format code of the data to be transmitted is 2, and the data encapsulation format is the user message packet encapsulation format.
  • Step d if the data encapsulation format is a message packet encapsulation format, then the to-be-transmitted data is converted into a message encapsulation packet;
  • Step e if the data encapsulation format is a service flow encapsulation format or a service package encapsulation format, the to-be-transmitted data is converted into a service encapsulation package.
  • the to-be-transmitted data is converted into a message encapsulation packet corresponding to the data encapsulation format.
  • the digital broadcasting system detects that the data encapsulation format of the acquired data to be transmitted is a service flow encapsulation format or a service package encapsulation format, the to-be-transmitted data is converted into a service encapsulation package corresponding to the data encapsulation format.
  • the message package encapsulation format includes a system message package format and a user message package format
  • the corresponding message package includes a system message package and a user message package.
  • FIG. 2 is the encapsulation format of the message encapsulation package of the present application.
  • the data encapsulation format of the message encapsulation packet is packet header + message data payload
  • the packet header includes encapsulation format code, message data code, start identifier, end identifier and payload length, wherein the byte length of the encapsulation format code is 2 bytes,
  • the byte length of the message data encoding is 6 bytes
  • the byte length of the start identifier is 1 byte
  • the byte length of the end identifier is 1 byte
  • the byte length of the payload length is 6 bytes
  • the byte length of the message data is 6 bytes.
  • the byte length of the payload is not limited. If the maximum byte length of the payload length of a single complete data to be transmitted is limited to M bytes, the maximum byte length of the message encapsulation package converted into the corresponding data encapsulation format is M+2 bytes. Due to the different spectrum modes of the message encapsulation packets, the capacity of the message channel for transmitting the message encapsulation packet is also different.
  • the message channel includes multiple FEC (Forward Error Correction, forward error correction code), that is, a message channel includes multiple message sub-channels with coding.
  • FIG. 3 is a service flow encapsulation format of the service encapsulation package of the application.
  • the service flow encapsulation format of the service encapsulation package is header + payload segment.
  • the header includes binary code, reserved bits, and payload length.
  • the byte length of binary code is 2 bytes, and the byte length of reserved bits is 6 bytes.
  • the byte length of the payload length is 8 bytes, and the byte length of the payload segment is not limited.
  • FIG. 4 is a service package encapsulation format of the service encapsulation package of the application.
  • the service package encapsulation format of the service encapsulation package is header + payload segment.
  • the header includes binary code, count code, start flag, end flag, and payload length.
  • the byte length of the binary code is 2 bytes, and the count code is 2 bytes long.
  • the length of the bytes is 4 bytes, the length of the bytes of the start identifier is 1 byte, the length of the bytes of the end identifier is 1 byte, the length of the bytes of the payload length is 8 bytes, and the length of the bytes of the payload segment is 8 bytes. Section length is not limited.
  • the service package is transmitted through multiple coded service sub-channels.
  • Step S30 Determine a corresponding data encapsulation rule according to the data encapsulation format, and encapsulate the data encapsulation package according to the data encapsulation rule.
  • the digital broadcasting system determines the data encapsulation rules corresponding to the data to be transmitted according to the mapping relationship between the data encapsulation format and the data encapsulation rules in the digital broadcasting system, and then encapsulates the data encapsulation packets corresponding to the data to be transmitted through the data encapsulation rules.
  • the mapping relationship between the data encapsulation format and the data encapsulation rule is preset in the digital broadcasting system, which is not limited in this embodiment.
  • step S30 includes:
  • Step f if the data encapsulation format is a message package encapsulation format, then determine that the data encapsulation package is a message encapsulation package, and determine that the data encapsulation rule is a message package encapsulation rule;
  • Step g obtaining the remaining capacity of the message channel, and detecting whether the remaining capacity is greater than or equal to the first byte length of the message encapsulation package;
  • Step h if it is detected that the remaining capacity is greater than or equal to the length of the first byte, detecting whether there is a first remaining capacity in the first message sub-channel;
  • Step i if it is detected that the first remaining capacity does not exist, the message encapsulation packet is encapsulated into a second message sub-channel.
  • Fig. 5 is the message packet encapsulation rule of the application, if the digital broadcasting system detects that the data encapsulation format is the message packet encapsulation format, the data encapsulation packet is determined to be the message encapsulation packet, and the data encapsulation rule is determined to be the message packet. Encapsulation rule, the digital broadcasting system obtains the remaining capacity of the message channel, and detects whether the remaining capacity is greater than or equal to the length of the first byte of the message encapsulation package.
  • the first message is detected Whether the subchannel has the first remaining capacity, if it is detected that the remaining capacity is less than the first byte length, the message encapsulation packet is encapsulated into other message channels whose remaining capacity is greater than or equal to the first byte length.
  • the message encapsulation packet is encapsulated into the second message sub-channel; if it is detected that the first remaining capacity exists, the first remaining capacity is The byte length is split into a first information encapsulation packet equal to the first remaining capacity, and the first message encapsulation packet is encapsulated into the first message sub-channel, and the remaining second message encapsulation packet is encapsulated into the second message subchannel.
  • the remaining capacity of the message channel is 10 bytes
  • the capacity of the first message sub-channel is 2 bytes
  • the capacity of the second message sub-channel is 8 bytes
  • the byte length of the message encapsulation package is 9 bytes
  • the digital broadcasting system first splits the message encapsulation packet into a 2-byte first information encapsulation packet and encapsulates it into the first message sub-channel, and then encapsulates the remaining 7-byte second message encapsulation packet into the second message. subchannel.
  • Step j if the data encapsulation format is a business flow encapsulation format, then determine that the data encapsulation package is a business encapsulation package, and determine that the data encapsulation rule is a business flow encapsulation rule;
  • Step k obtaining the first channel length of the first service sub-channel, and detecting whether the second byte length of the service encapsulation package is less than the first channel length;
  • Step 1 if it is detected that the length of the second byte is less than the length of the first channel, then detect whether there is a first service encapsulation package;
  • step m if it is detected that the first service encapsulation package exists, the remaining second channel length of the second service sub-channel after the first service encapsulation package is encapsulated is detected, and the service encapsulation package is segmented and encapsulated into all the sub-channels. the first service sub-channel and the second service sub-channel.
  • FIG. 6 is the service flow encapsulation rule of the application. If the digital broadcasting system detects that the data encapsulation format is the service flow encapsulation format, the data encapsulation package is determined as the service encapsulation package, and the data encapsulation rule is determined as the service flow.
  • the digital broadcasting system obtains the first channel length of the first service sub-channel, and detects whether the second byte length of the service encapsulation package is less than the first channel length, if it is detected that the second byte length is less than the first channel length, Then it is detected whether there is a first service encapsulation package, and if it is detected that there is a first service encapsulation package, the second channel length remaining in the second service sub-channel after the first service encapsulation package is encapsulated is detected, and the service encapsulation package is split into A second service encapsulation package that is equal to the length of the second channel, encapsulates the second service encapsulation package into the second service sub-channel, and then encapsulates the remaining third service encapsulation package of the service encapsulation package into the first service encapsulation package. traffic sub-channel. If it is detected that the first service encapsulation package does not exist, the service encapsulation package is directly encapsulated into the first service encapsul
  • a service flow package can encapsulate multiple service packages.
  • Fig. 7 is the application business package encapsulation rule, if the digital broadcasting system detects that the data encapsulation format is a business package encapsulation format, then determine that the data encapsulation package is a business package, and determine that the data encapsulation rule is a business package.
  • the digital broadcasting system obtains the first channel length of the first service sub-channel, and detects whether the second byte length of the service encapsulation package is less than the first channel length, if it is detected that the second byte length is less than the first channel length, Then it is detected whether there is a first service encapsulation package, and if it is detected that there is a first service encapsulation package, the second channel length remaining in the second service sub-channel after the first service encapsulation package is encapsulated is detected, and the service encapsulation package is split into A second service encapsulation package that is equal to the length of the second channel, encapsulates the second service encapsulation package into the second service sub-channel, and then encapsulates the remaining third service encapsulation package of the service encapsulation package into the first service encapsulation package. traffic sub-channel. If it is detected that the first service encapsulation package does not exist, the service encapsulation package is directly encapsulated into the service
  • the size of the service package encapsulation is limited to the length of the service sub-channel.
  • a service package encapsulation can only encapsulate one service package.
  • the encapsulation method of the data also includes:
  • Step n after detecting that the upper-layer application sends a data transmission instruction, send the input data format to the upper-layer application, so that the upper-layer application can convert the data format of the data to be sent into the input data format, and obtain the to-be-sent data format. transfer data.
  • the digital broadcasting system After the digital broadcasting system detects that the upper-layer application sends a data transmission instruction, it sends the input data format to the upper-layer application. After the upper-layer application receives the input data format, it converts the data format of the data to be sent into the input data format, and obtains the data format to be transmitted. data, and send the data to be transmitted to the digital broadcasting system.
  • FIG. 8 is the input data format of the system configuration information of the application, and the input data format of the system configuration information is data identification + data length + upper layer application control parameter field + data transmission system parameter field.
  • the byte length of the data identification is 1 byte, and 0x00 represents the system configuration information.
  • the byte length of the data length is 1 byte, which indicates the content length of the system configuration information, excluding the data identification and data length.
  • the upper-layer application control parameter field includes system startup time, timing function indication, spectrum mode and frame length.
  • the byte length of the system startup time is 4 bytes, 0 means immediate start, other values indicate the start time of the physical frame signal, and when the timing function is turned on, it also corresponds to the initial time when the timing is turned on.
  • the length of the byte indicated by the timing function is 1 byte, indicating whether the system enables the timing function and sends a timing message.
  • the byte length of the spectrum mode is 1 byte, and there are 8 spectrum modes in the symbiotic FM data broadcasting system.
  • the byte length of the frame length is 1 byte, and the value indicates the number of subframes included in a physical frame.
  • the data transmission system parameter field includes the number of services, the number of LDPC (Low Density Check Code) blocks, the coding rate, the interleaving depth, the mapping method, the data encapsulation format, the spreading factor, and the authorization sequence.
  • the byte length of the number of services is 1 byte, which indicates the number of services carried in the physical signal frame.
  • the byte length of the service number is 1 byte, indicating the identification and arrangement number of the service.
  • the byte length of the number of LDPC blocks is 1 byte, which indicates the number of FEC coding blocks for services in the physical frame.
  • the byte length of the coding rate is 1 byte, indicating the corresponding number in the FEC coding rate.
  • the byte length of the interleaving depth is 1 byte, indicating the interleaving depth of the service.
  • the byte length of the mapping mode is 1 byte, which indicates the constellation mapping mode of the service.
  • the byte length of the data encapsulation format is 1 byte, 1 represents the service flow, and 2 represents the service packet.
  • the byte length of the spreading factor is 1 byte, which indicates the spreading parameter when the service needs spreading.
  • the byte length of the authorization sequence is 1 byte, and is used to initialize the initial PN (Pseudo-Noise Code, PN code) value of the physical layer scrambling code.
  • FIG. 9 is the input data format of the message data of the application, and the input data format of the message data is data identification+message number+message data transmission control parameter field+message data content field.
  • the type corresponding to the message code (decimal notation) and the message code is that message code 0 corresponds to control messages, message code 1 corresponds to timing messages, message code 2 corresponds to emergency messages, message code 3 corresponds to service description messages, and message code 4 corresponds to RTK ( Real-time Kinematic, real-time dynamic) messages, and message codes 5 to 63 correspond to other user messages.
  • the byte length of the data identification is 1 byte
  • 0x01 represents the message data.
  • the byte length of the message number is 1 byte, and the value ranges from 1 to 63.
  • the message data transmission control parameter field includes the message timestamp, the number of repeated broadcasts and the broadcast interval.
  • the byte length of the message timestamp is 1 byte, which indicates the sending time information of the message.
  • the byte length of the number of repeated broadcasts is 1 byte, which means that the message will be broadcast after repeated broadcasts for many times. 0 means no retransmission, 255 means infinite retransmission, and other values represent the actual number of retransmissions.
  • the byte length of the advertisement interval is 1 byte, indicating. Take the physical frame as the unit, 0 means that every physical frame is broadcast, and other values indicate how many physical frames to broadcast again.
  • the message data content field includes message data length and message data payload.
  • the byte length of the message data length is 1 byte, which indicates the length of the message data payload, the unit is byte, and the value ranges from 1 to 60.
  • the byte length of the message data payload is not limited, it indicates the content of the message data payload, which corresponds to a complete message data defined by the user.
  • FIG. 10 is the input data format of the application service data, and the input data format of the service data is data identification + service number + service data transmission control parameter field + service data content field.
  • the byte length of the data identification is 1 byte, and 0x02 represents service data.
  • the byte length of the service number is 1 byte, which indicates the sequence number of the service.
  • the sequence of the service on the physical layer and the sequence of the modulation parameters corresponding to the service data in the system control information message are given by this number, which is used as the priority. a number.
  • the service data transmission control parameter field includes the service timestamp, and the byte length is 4 bytes, which indicates the sending time information of the service (0 means immediate and sequential sending).
  • the service data content field includes service length and service payload, wherein the byte length of the service length is 2 bytes, indicating the length of the service payload, and the unit is bytes.
  • the byte length of the service payload is not limited, it indicates the content of the service payload, which corresponds to a service data packet of the user.
  • the data to be transmitted is received, the data is classified according to the data identifier and the transmission requirement in the data to be transmitted, the data type corresponding to the data to be transmitted is determined, the encapsulation format code corresponding to the data to be transmitted is determined according to the data type, and the encapsulation format code is determined according to the encapsulation format code.
  • the corresponding data encapsulation format, and according to the data encapsulation format, the data to be transmitted is converted into a corresponding data encapsulation package, the corresponding data encapsulation rule is determined according to the data encapsulation format, and the data encapsulation package is encapsulated by the data encapsulation rule.
  • the data to be transmitted needs to be classified according to the data identification and transmission requirements, and then the encapsulation format code corresponding to the to-be-transmitted data is determined, and the corresponding data encapsulation format is determined according to the encapsulation format code, and then according to The data encapsulation format determines the corresponding data encapsulation rules, and encapsulates the data encapsulation package through the data encapsulation rules, which realizes the design of the data to be transmitted according to the characteristics and transmission requirements of the data to be transmitted, thus realizing the different classification of the data to be transmitted. Data encapsulation is performed through different data encapsulation rules, thereby reducing bandwidth consumption.
  • Step o Determine the data output format corresponding to the data to be transmitted, and convert the encapsulated data to be transmitted into a transmission data source of the data output format and send it to the physical layer.
  • the digital broadcasting system determines the corresponding output data identifier according to the data type of the data to be transmitted, determines the corresponding data output format according to the mapping relationship between the data output identifier and the data output format in the digital broadcasting system, and then encapsulates the encapsulated to-be-transmitted data.
  • the data is converted into a transmission data source corresponding to the data output format, and then the transmission data source is sent to the physical layer.
  • the mapping relationship between the data output identifier and the data output format determines that the corresponding data output format is preset in the digital broadcasting system, which is not limited in this embodiment.
  • the output data format of the system configuration information is data output identifier + data length + upper layer application control parameter field + data transmission system parameter field.
  • the byte length of the data output identifier is 1 byte, and 0x30 indicates the system configuration information output format.
  • the byte length of the data length is 1 byte, which indicates the content length of the system configuration information, excluding the data identification and data length.
  • the upper-layer application control parameter field includes system startup time, timing function indication, spectrum mode and frame length.
  • the byte length of the system startup time is 4 bytes, 0 means immediate start, other values indicate the start time of the physical frame signal, and when the timing function is turned on, it also corresponds to the initial time when the timing is turned on.
  • the length of the byte indicated by the timing function is 1 byte, indicating whether the system enables the timing function and sends a timing message.
  • the byte length of the spectrum mode is 1 byte, and there are 8 spectrum modes in the symbiotic FM data broadcasting system.
  • the byte length of the frame length is 1 byte, and the value indicates the number of subframes included in a physical frame.
  • the data transmission system parameter field includes the number of services, the number of LDPC (Low Density Check Code) blocks, the coding rate, the interleaving depth, the mapping method, the data encapsulation format, the spreading factor, and the authorization sequence.
  • the byte length of the number of services is 1 byte, which indicates the number of services carried in the physical signal frame.
  • the byte length of the service number is 1 byte, indicating the identification and arrangement number of the service.
  • the byte length of the number of LDPC blocks is 1 byte, which indicates the number of FEC coding blocks for services in the physical frame.
  • the byte length of the coding rate is 1 byte, indicating the corresponding number in the FEC coding rate.
  • the byte length of the interleaving depth is 1 byte, indicating the interleaving depth of the service.
  • the byte length of the mapping mode is 1 byte, which indicates the constellation mapping mode of the service.
  • the byte length of the data encapsulation format is 1 byte, 1 represents the service flow, and 2 represents the service packet.
  • the byte length of the spreading factor is 1 byte, which indicates the spreading parameter when the service needs spreading.
  • the byte length of the authorization sequence is 1 byte, and is used to initialize the initial PN (Pseudo-Noise Code, PN code) value of the physical layer scrambling code.
  • the output data format of the message data is data output identifier+data length+message data transmission control parameter field+message packet list.
  • the byte length of the data output identifier is 1 byte, and 0x04 represents the message data output format.
  • the byte length of the data length is 2 bytes, indicating the length from the timestamp to the end of the message packet (including padding data), in bytes.
  • the message data transmission control parameter field includes a time stamp, the byte length is 4 bytes, 0 indicates immediate transmission, and other values correspond to the start time of the physical frame signal.
  • the message packet list includes control information message packets, message data encapsulation packets, service filling packets and filling data.
  • the byte length of the control information message packet is fixed at 16 bytes.
  • Message data encapsulation package 1 represents the message data encapsulation package 1 obtained after encapsulation according to the real-time situation of the message data
  • message data encapsulation package 2 represents the message obtained after encapsulation according to the real-time situation of the message data.
  • Data encapsulation packets 2.... to message data encapsulation packets n represent message data encapsulation packets n obtained after encapsulation according to the real-time conditions of message data, where n is any integer value greater than or equal to 1, which is not limited in this embodiment.
  • the byte length of the service padding packet is 1 byte, which is represented by 0xc0.
  • the padding data is all 0s.
  • the input data format of the service data is data output identifier + data length + service data transmission control parameter field + service data encapsulation column data field.
  • the byte length of the data output identifier is 1 byte, and 0x05 represents the service data output format.
  • the service data transmission control parameter field includes a timestamp byte with a length of 4 bytes, 0 indicates immediate transmission, and other values correspond to the start time of the physical frame signal.
  • the data field after the service data encapsulation column includes the service number, the interleaving number, the data length, the service data field, the service filling packet and the filling data.
  • the byte length of the service number is 1 byte, which indicates the service number corresponding to the transmission content.
  • the byte length of the interleaving number is 1 byte, which means that when the physical frame is divided into multiple interleaving blocks, the services should be sent to the physical layer in the order of the interleaving blocks.
  • the byte length of the data length is 2 bytes, indicating the total length of the service data field + service padding packet + padding data, and the unit is bytes.
  • the service data field indicates that the service data field contains multiple service encapsulation packages (service flow encapsulation packages or service package encapsulation packages), and the total length satisfies the requirement of the physical layer for the data volume of one interleaving block.
  • the byte length of the service padding packet is 1 byte, which is represented by 0xc0. Fill data with all 0s.
  • the service data field, the service filling packet and the filling data constitute the physical layer interleaving block.
  • FIG. 11 is the process of mapping the service payload of the application to the interleaving block.
  • the service encapsulation packet is filled into the link layer service data in the unit of the interleaving block according to the service distinction.
  • the service data field is not enough to form a complete physical layer interleaving block, it is supplemented with a service filling packet, and the service data field, filling packet, and filling data form a physical layer interleaving block.
  • the link layer service data is formed and transmitted to the physical layer. map.
  • the link layer transmits the link layer service data to the physical layer with the service interleaving block as the basic unit.
  • each link layer service data only contains the interleaving block of one service. data.
  • the link layer service data including the interleaving blocks of each layer should be transmitted in sequence in the order of the interleaving blocks.
  • the data of the next service is transmitted after all physical layer interleaving blocks of a service are transmitted in sequence according to the sequence of service numbers.
  • the data output format corresponding to the data to be transmitted is determined, and the encapsulated data to be transmitted is converted into a transmission data source of the data output format and sent to the physical layer. It can be seen from this that, by coordinating the data conversion relationship between the upper-layer application and the physical layer, this embodiment organizes the data to be transmitted and then transmits it to the physical layer, so as to ensure the transmission quality and simplify the operation of the upper-layer application and the physical layer. difficulty.
  • the present application also provides an apparatus for encapsulating data.
  • the apparatus for encapsulating data includes:
  • a receiving module 10 for receiving data to be transmitted
  • a classification module 20 configured to classify according to the data identifier and transmission requirement in the data to be transmitted, and determine the data type corresponding to the data to be transmitted;
  • a determination module 30 configured to determine the encapsulation format code corresponding to the data to be transmitted according to the data type, and determine the corresponding data encapsulation format according to the encapsulation format code;
  • a conversion module 40 for converting the data to be transmitted into a corresponding data package according to the data encapsulation format
  • the determining module 30 is further configured to determine a corresponding data encapsulation rule according to the data encapsulation format
  • the encapsulation module 50 is configured to encapsulate the data to be transmitted according to the data encapsulation rule.
  • the determining module 30 is further configured to, if the data encapsulation format is a message packet encapsulation format, determine that the data encapsulation packet is a message encapsulation packet, and determine that the data encapsulation rule is a message packet encapsulation rule.
  • packaging module 50 includes:
  • a first obtaining unit used for obtaining the remaining capacity of the message channel
  • a first detection unit configured to detect whether the remaining capacity is greater than or equal to the first byte length of the message encapsulation package; if it is detected that the remaining capacity is greater than or equal to the first byte length, then detect the first Whether the message sub-channel has the first remaining capacity;
  • a first encapsulation unit configured to encapsulate the message encapsulation packet into a second message sub-channel if it is detected that the first remaining capacity does not exist.
  • the determining module 30 is further configured to determine that the data encapsulation package is a service encapsulation package if the data encapsulation format is a service flow encapsulation format, and determine that the data encapsulation rule is a service flow encapsulation rule.
  • packaging module 50 includes:
  • a second acquiring unit configured to acquire the first channel length of the first service sub-channel
  • a second detection unit configured to detect whether the length of the second byte of the service encapsulation packet is less than the length of the first channel; if it is detected that the length of the second byte is less than the length of the first channel, detect whether there is a first service encapsulation package; if it is detected that the first service encapsulation package exists, then detect the remaining second channel length of the second service sub-channel after the first service encapsulation package is encapsulated;
  • a second encapsulation unit configured to encapsulate the service encapsulation packet into segments into the first service sub-channel and the second service sub-channel.
  • the determining module 30 includes:
  • the third obtaining unit is used to obtain the format coding mapping table
  • a determining unit configured to determine the encapsulation format encoding corresponding to the data to be transmitted in the format encoding mapping table according to the data type
  • the third obtaining unit is also used to obtain the encapsulation format mapping table
  • the determining unit is further configured to determine a data encapsulation format corresponding to the data to be transmitted according to the encapsulation format mapping table and the encapsulation format code.
  • the conversion module is also used to convert the data to be transmitted into a message encapsulation package if the data encapsulation format is a message package encapsulation format; if the data encapsulation format is a service flow encapsulation format or a service package encapsulation format, the data to be transmitted is converted into a service package.
  • the receiving module 10 is further configured to receive the data to be transmitted.
  • classification module 20 includes:
  • a fourth acquiring unit used for acquiring the data identifier and the data parameter transmission type in the data to be transmitted
  • a classification unit configured to classify the data to be transmitted in combination with the data identifier and the data parameter transmission type.
  • the determining module 30 is further configured to determine the data type corresponding to the data to be transmitted.
  • the device for encapsulating the data also includes:
  • the sending module is configured to send the input data format to the upper-layer application after detecting that the upper-layer application sends a data transmission instruction, so that the upper-layer application can convert the data format of the data to be sent into the input data format, and obtain the data format of the input data. data to be transmitted.
  • the specific implementation manner of the data-based encapsulation apparatus of the present application is basically the same as the above-mentioned embodiments of the data-based encapsulation method, and details are not described herein again.
  • FIG. 13 is a schematic structural diagram of the hardware operating environment involved in the solution of the embodiment of the present application.
  • FIG. 13 can be a schematic structural diagram of the hardware operating environment of the data encapsulation system.
  • the data packaging system may include: a processor 1001, such as a CPU (Central Processing Unit, central processing unit), memory 1005, user interface 1003, network interface 1004, communication bus 1002.
  • the communication bus 1002 is used to implement the connection communication between these components.
  • the user interface 1003 may include a display screen (Display), an input unit such as a keyboard (board), and the optional user interface 1003 may also include a standard wired interface (such as a USB (Universal Serial Bus) interface), a wireless interface (such as Bluetooth interface).
  • the network interface 1004 may include a standard wired interface and a wireless interface (eg, a WI-FI ((Wireless-Fidelity)) interface).
  • the memory 1005 may be a high-speed RAM memory or a non-volatile memory (non-volatile memory). memory), such as disk storage.
  • the memory 1005 may also be a storage device independent of the aforementioned processor 1001 .
  • the data encapsulation system may further include RF (Radio Frequency, radio frequency) circuits, sensors, WiFi modules, etc.
  • RF Radio Frequency, radio frequency
  • FIG. 13 does not constitute a limitation on the data encapsulation system, and may include more or less components than those shown in the figure, or combine some components, or different component layout.
  • the memory 1005 as a computer storage medium may include an operating device, a network communication module, a user interface module, and a data encapsulation program.
  • the operating device is a program that manages and controls the hardware and software resources of the data encapsulation system, and supports the operation of the data encapsulation program and other software or programs.
  • the user interface 1003 is mainly used for upper-layer applications to receive the data input format sent by the digital broadcasting system and send the data to be transmitted to the digital broadcasting system;
  • the network interface 1004 is mainly used for the digital broadcasting system.
  • the processor 1001 can be used to call the encapsulation program of the data stored in the memory 1005, and complete the encapsulation system of the data as described above steps of the control method.
  • an embodiment of the present application also proposes a computer-readable storage medium, where a data encapsulation program is stored on the computer-readable storage medium, and when the data encapsulation program is completed by a processor, the above-mentioned data encapsulation is implemented steps of the method.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请公开了一种数据的封装方法、装置、系统及计算机可读存储介质，该方法的步骤包括：接收待传输数据，根据待传输数据中的数据标识和传输需求进行分类，确定待传输数据对应的数据类型；根据数据类型确定待传输数据对应的封装格式编码，根据封装格式编码确定对应的数据封装格式，并根据数据封装格式将待传输数据转化为对应的数据封装包；根据数据封装格式确定对应的数据封装规则，通过数据封装规则将数据封装包进行封装。

Description

数据的封装方法、装置、系统及计算机可读存储介质
本申请要求于2020年7月16日申请的、申请号为202010690509.9的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及数字信息传输技术领域，尤其涉及支持多种格式的数据信息传输的数字广播系统，尤其涉及一种数据的封装方法、装置、系统及计算机可读存储介质。
 背景技术
目前数字广播系统的数据封装方法主要将所有的待传输数据都按照自身系统定义的数据封装方式进行封装，而不能根据待传输数据的数据特点对待传输数据进行相应方式的数据封装，从而导致宽带损耗。由此可知，目前数字广播系统的数据封装方法不能将待传输数据进行分类封装，以及宽带损耗大。
 技术问题
本申请的主要目的在于提供一种数据的封装方法、装置、系统及计算机可读存储介质，旨在解决目前数字广播系统的数据封装方法不能将待传输数据进行分类封装，以及宽带损耗大的技术问题。
 技术解决方案
为实现上述目的，本申请提供一种数据的封装方法，所述数据的封装方法包括以下步骤：
接收待传输数据，根据所述待传输数据中的数据标识和传输需求进行分类，确定所述待传输数据对应的数据类型；
根据所述数据类型确定所述待传输数据对应的封装格式编码，根据所述封装格式编码确定对应的数据封装格式，并根据所述数据封装格式将所述待传输数据转化为对应的数据封装包；
根据所述数据封装格式确定对应的数据封装规则，通过所述数据封装规则将所述数据封装包进行封装。
在一实施例中，所述根据所述数据封装格式确定对应的数据封装规则，通过所述数据封装规则将所述数据封装包进行封装的步骤包括：
若所述数据封装格式为消息包封装格式，则确定所述数据封装包为消息封装包，并确定所述数据封装规则为消息包封装规则；
获取消息信道的剩余容量，并检测所述剩余容量是否大于或者等于所述消息封装包的第一字节长度；
若检测到所述剩余容量大于或者等于所述第一字节长度，则检测第一消息子信道是否存在第一剩余容量；
若检测到不存在所述第一剩余容量，则将所述消息封装包封装至第二消息子信道。
在一实施例中，所述根据所述数据封装格式确定对应的数据封装规则，通过所述数据封装规则将所述数据封装包进行封装的步骤包括：
若所述数据封装格式为业务流封装格式，则确定所述数据封装包为业务封装包，并确定所述数据封装规则为业务流封装规则；
获取第一业务子信道的第一信道长度，并检测所述业务封装包的第二字节长度是否小于所述第一信道长度；
若检测到所述第二字节长度小于所述第一信道长度，则检测是否存在第一业务封装包；
若检测到存在所述第一业务封装包，则检测所述第一业务封装包封装后第二业务子信道剩余的第二信道长度，并将所述业务封装包分段封装至所述第一业务子信道和所述第二业务子信道。
在一实施例中，所述根据所述数据类型确定所述待传输数据对应的封装格式编码，根据所述封装格式编码确定对应的数据封装格式的步骤包括：
获取格式编码映射表，根据所述数据类型在所述格式编码映射表中确定所述待传输数据对应的封装格式编码；
获取封装格式映射表，根据所述封装格式映射表和所述封装格式编码确定所述待传输数据对应的数据封装格式。
在一实施例中，所述根据所述数据封装格式将所述待传输数据转化为对应的数据封装包的步骤包括：
若所述数据封装格式为消息包封装格式，则将所述待传输数据转化为消息封装包；
若所述数据封装格式为业务流封装格式或者业务包封装格式，则将所述待传输数据转化为业务封装包。
在一实施例中，所述接收待传输数据，根据所述待传输数据中的数据标识和传输需求进行分类，确定所述待传输数据对应的数据类型的步骤包括：
接收所述待传输数据，并获取所述待传输数据中的数据标识和数据参数传输类型，结合所述数据标识和所述数据参数传输类型将所述待传输数据进行分类，确定所述待传输数据对应的数据类型。
在一实施例中，所述接收待传输数据，根据所述待传输数据中的数据标识和传输需求进行分类，确定所述待传输数据对应的数据类型的步骤之前，还包括：
侦测到上层应用发出数据传输指令后，将输入数据格式发送至所述上层应用，以供所述上层应用将待发送数据的数据格式转换为所述输入数据格式，得到所述待传输数据。
此外，为实现上述目的，本申请还提供一种数据的封装装置，所述数据的封装装置包括：
接收模块，用于接收待传输数据；
分类模块，用于根据所述待传输数据中的数据标识和传输需求进行分类，确定所述待传输数据对应的数据类型；
确定模块，用于根据所述数据类型确定所述待传输数据对应的封装格式编码，根据所述封装格式编码确定对应的数据封装格式；
转化模块，用于根据所述数据封装格式将所述待传输数据转化为对应的数据封装包；
所述确定模块还用于根据所述数据封装格式确定对应的数据封装规则；
封装模块，用于通过所述数据封装规则将所述待传输数据进行封装。
此外，为实现上述目的，本申请还提供一种数据的封装系统，所述数据的封装系统包括存储器、处理器和存储在所述存储器上并在所述处理器上运行的数据的封装程序，所述数据的封装程序被所述处理器完成时实现如上所述的数据的封装方法的步骤。
此外，为实现上述目的，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质上存储有数据的封装程序，所述数据的封装程序被处理器完成时实现如上所述的数据的封装方法的步骤。
 有益效果
本申请实现通过接收待传输数据，根据待传输数据中的数据标识和传输需求进行分类，确定待传输数据对应的数据类型，根据数据类型确定待传输数据对应的封装格式编码，根据封装格式编码确定对应的数据封装格式，并根据数据封装格式将待传输数据转化为对应的数据封装包，根据数据封装格式确定对应的数据封装规则，通过数据封装规则将数据封装包进行封装。由此可知，本申请在数据封装的过程，需要根据数据标识和传输需求将待传输数据进行分类，然后确定待传输数据对应的封装格式编码，根据封装格式编码确定对应的数据封装格式，再根据数据封装格式确定对应的数据封装规则，并通过数据封装规则对数据封装包进行封装，实现了根据待传数据的特点和传输需求对待传输数据进行设计，从而实现了根据待传输数据的分类不同，通过不同的数据封装规则进行数据封装，从而减少了带宽损耗。
 附图说明
图1是本申请数据的封装方法第一实施例的流程示意图；
图2是本申请数据的分析方法第一实施例消息封装包的封装格式示意图；
图3是本申请数据的分析方法第一实施例业务封装包的业务流封装格式示意图；
图4是本申请数据的分析方法第一实施例业务封装包的业务包封装格式示意图；
图5是本申请数据的分析方法第一实施例的消息包封装规则示意图；
图6是本申请数据的分析方法第一实施例的业务流封装规则示意图；
图7是本申请数据的分析方法第一实施例的业务包封装规则示意图；
图8是本申请数据的分析方法第一实施例系统配置信息的输入数据格式示意图；
图9是本申请数据的分析方法第一实施例消息数据的输入数据格式示意图；
图10是本申请数据的分析方法第一实施例业务数据的输入数据格式示意图；
图11是本申请数据的分析方法第二实施例业务净荷映射到交织块的过程示意图；
图12是本申请数据的封装装置较佳的结构示意图；
图13是本申请实施例方案涉及的硬件运行环境的结构示意图。
本申请目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。
 本发明的实施方式
应当理解，此处所描述的具体实施例仅用以解释本申请，并不用于限定本申请。
本申请提供一种数据的封装方法，参照图1至图11，图1为本申请数据的封装方法第一实施例的流程示意图；图2为本申请数据的封装方法第一实施例的消息封装包封装格式示意图；图3为本申请数据的封装方法第一实施例业务封装包的业务流封装格式示意图；图4为本申请数据的封装方法第一实施例业务封装包的业务包封装格式示意图；图5为本申请数据的封装方法第一实施例的消息包封装规则示意图；图6为本申请数据的封装方法第一实施例的业务流封装规则示意图；图7为本申请数据的封装方法第一实施例的业务包封装规则示意图；图8为本申请数据的封装方法第一实施例系统配置信息的输入数据格式示意图；图9为本申请数据的封装方法第一实施例消息数据的输入数据格式示意图；图10为本申请数据的封装方法第一实施例业务数据的输入数据格式示意图；图11为本申请数据的封装方法第二实施例业务净荷映射到交织块的过程示意图。
本申请实施例提供了数据的封装方法的实施例，需要说明的是，虽然在流程图中示出了逻辑顺序，但是在某些数据下，可以以不同于此处的顺序完成所示出或描述的步骤。
数据的封装方法包括:
步骤S10，接收待传输数据，根据所述待传输数据中的数据标识和传输需求进行分类，确定所述待传输数据对应的数据类型。
数字广播系统接收上层应用发送的待传输数据，然后获取待传输数据中的数据标识，根据数据标识与业务类型的映射关系确定待传输数据的业务类型，并获取待传输数据对应的数据传输方式，再结合业务类型和数据传输方式将待传输数据进行分类，确定待传输数据对应的数据类型。
其中，上层应用包括但不限制于新型数字化广播系统，本实施例中尤其指共生调频数据广播（CD-Radio）系统，以及其他数字广播系统。业务类型包括但不限制于系统配置信息、消息数据和业务数据。系统配置信息包括但不限制于物理层发射端功能控制参数、消息数据传输控制参数和业务数据传输控制参数。消息数据包括系统消息数据和用户消息数据，系统消息数据来自于系统配置信息，用于物理层传输控制信息，用户消息数据为上层应用的功能，用于传输简短数据和已确定内容数据。业务数据包括业务流数据和业务包数据。数据传输方式包括但不限制于消息包传输方式、业务流传输方式和业务包传输方式。数据类型包括但不限制于物理层配置参数、系统信息、用户消息、业务流和业务包。
进一步地，所述步骤S10包括：
步骤a，接收所述待传输数据，并获取所述待传输数据中的数据标识和数据参数传输类型，结合所述数据标识和所述数据参数传输类型将所述待传输数据进行分类，确定所述待传输数据对应的数据类型。
具体地，数字广播系统接收上层应用发送的待传输数据，然后获取待传输数据中链路层接口的数据标识，根据数字广播系统中的预设数据映射表确定待传输数据对应的业务类型，然后获取待传输数据中数据参数传输类型，结合业务类型和数据参数传输类型进行分类，确定待传输数据对应的数据类型。
其中，链路层接口是待传输数据中数据格式的一部分。预设数据映射表是根据需求预先数字广播系统中设定的，本实施例不作限制。数据参数传输类型包括但不限制于系统信息包传输、用户消息包传输、业务流传输和业务包传输，其中，系统信息包传输和用户消息包传输都属于消息包传输。消息包传输应用于各类消息数据的传输。业务流传输和业务包传输均应用于业务数据的传输过程。业务流传输应用于在数据传输过程中对待传输数据没有完整性检测的场景。业务包传输具备一定的结构性，可对接收到的待传输数据进行完整性检测，主要应用于在数据传输过程中，待传输数据对数据缺失和准确性比较敏感的场景。
需要说明的是，待传输数据的数据格式为数据标识+数据长度或者数据编号+数据传输控制参数域或者上层应用控制参数域+数据传输系统参数域或者数据内容域。
在本实施例中，比如，预设数据映射表中数据标识与业务类型的映射关系为数据标识0x00对应系统配置信息、数据标识0x01对应消息数据和数据标识0x02对应业务数据，数字广播系统接收到待传输数据中的数据标识为0x01，获取到待传输数据中数据参数传输类型为用户消息包传输，数字广播系统确定接收到待传输数据的数据类型为用户消息。
步骤S20，根据所述数据类型确定所述待传输数据对应的封装格式编码，根据所述封装格式编码确定对应的数据封装格式，并根据所述数据封装格式将所述待传输数据转化为对应的数据封装包。
数字广播系统确定待传输数据对应的数据类型之后，根据数据类型与封装格式编码在数字广播系统的映射关系确定待传输数据对应的封装格式编码，然后根据封装格式编码与数据封装格式在数字广播系统的映射关系确定待传输数据对应的数据封装格式，再将待传输数据转化为与数据封装格式对应的数据封装包。
需要说明的是，数据类型与封装格式编码在数字广播系统的映射关系，以及封装格式编码与数据封装格式在数字广播系统的映射关系是预先在数字广播系统设定的，本实施例不作限制。
进一步地，所述步骤S20包括：
步骤b，获取格式编码映射表，根据所述数据类型在所述格式编码映射表中确定所述待传输数据对应的封装格式编码；
步骤c，获取封装格式映射表，根据所述封装格式映射表和所述封装格式编码确定所述待传输数据对应的数据封装格式。
具体地，数字广播系统获取数字广播系统中的格式编码映射表，根据数据类型与封装格式编码在格式编码映射表中的映射关系，确定待传输数据对应的封装格式编码，再获取数字广播系统中的封装格式映射表，根据封装格式编码与数据封装格式在封装格式映射表中的映射关系，确定待传输数据对应的数据封装格式。其中格式编码映射表和封装格式映射表是你根据需求在数字广播系统中预先设定的，本实施例不作限制。
在本实施例中，比如，格式编码映射表中数据类型与封装格式编码的映射关系为系统信息对应封装格式编码1、用户消息对应封装格式编码2、业务流对应封装格式编码3和业务包对应封装格式编码4。封装格式映射表中根据封装格式编码与数据封装格式的映射关系为封装格式编码1对应系统消息包封装格式，封装格式编码2对应用户消息包封装格式，封装格式编码3对应业务流封装格式和封装格式编码4对应业务包封装格式。数字广播系统获取到的待传输数据的数据类型为用户消息，则确定该待传输数据的封装格式编码为2，数据封装格式为用户消息包封装格式。
步骤d，若所述数据封装格式为消息包封装格式，则将所述待传输数据转化为消息封装包；
步骤e，若所述数据封装格式为业务流封装格式或者业务包封装格式，则将所述待传输数据转化为业务封装包。
具体地，数字广播系统若检测到获取的待传输数据的数据封装格式为消息包封装格式，则将该待传输数据转化为与该数据封装格式对应的消息封装包。数字广播系统若检测到获取的待传输数据的数据封装格式为业务流封装格式或者业务包封装格式，则将该待传输数据转化为与该数据封装格式对应的业务封装包。其中，消息包封装格式包括系统消息包封装格式和用户消息包封装格式，对应的消息封装包包括系统消息封装包和用户消息封装包。
需要说明的是，参照图2，图2为本申请消息封装包的封装格式。消息封装包的数据封装格式为包头+消息数据净荷，包头包括封装格式编码、消息数据编码、起始标识、结束标识和净荷长度，其中，封装格式编码的字节长度为2字节，消息数据编码的字节长度为6字节，起始标识的字节长度为1字节，结束标识的字节长度为1字节，净荷长度的字节长度为6字节，以及消息数据净荷的字节长度不作限制。若单个完整待传输数据的净荷长度最大字节长度限定为M字节，转化为对应数据封装格式的消息封装包最大字节长度为M+2字节。由于消息封装包的频谱模式不同，传输消息封装包的消息信道的容量也不相同，其中，消息信道中包括多个带有编码的FEC（Forward Error Correction，前向纠错码），即一个消息信道中包括多个带有编码的消息子信道。
进一步地，参照图3，图3为本申请业务封装包的业务流封装格式。业务封装包的业务流封装格式为包头+净荷分段，包头包括二进制编码、保留位和净荷长度，其中二进制编码的字节长度为2字节，保留位的字节长度为6字节，净荷长度的字节长度为8字节，以及净荷分段的字节长度不作限制。
进一步地，参照图4，图4为本申请业务封装包的业务包封装格式。业务封装包的业务包封装格式为包头+净荷分段，包头包括二进制编码、计数编码、起始标识、结束标识和净荷长度，其中，二进制编码的字节长度为2字节，计数编码的字节长度为4字节，起始标识的字节长度为1字节，结束标识的字节长度为1字节，净荷长度的字节长度为8字节，净荷分段的字节长度不作限制。业务封装包是通过多个带有编码的业务子信道传输的。
步骤S30，根据所述数据封装格式确定对应的数据封装规则，通过所述数据封装规则将所述数据封装包进行封装。
数字广播系统根据数据封装格式与数据封装规则在数字广播系统中的映射关系确定待传输数据对应的数据封装规则，然后通过数据封装规则将待传输数据对应的数据封装包进行封装。其中，数据封装格式与数据封装规则的映射关系是预先在数字广播系统中设定的，本实施例不作限制。
进一步地，所述步骤S30包括：
步骤f，若所述数据封装格式为消息包封装格式，则确定所述数据封装包为消息封装包，并确定所述数据封装规则为消息包封装规则；
步骤g，获取消息信道的剩余容量，并检测所述剩余容量是否大于或者等于所述消息封装包的第一字节长度；
步骤h，若检测到所述剩余容量大于或者等于所述第一字节长度，则检测第一消息子信道是否存在第一剩余容量；
步骤i，若检测到不存在所述第一剩余容量，则将所述消息封装包封装至第二消息子信道。
具体地，参照图5，图5为本申请消息包封装规则，数字广播系统若检测到数据封装格式为消息包封装格式，则确定数据封装包为消息封装包，并确定数据封装规则为消息包封装规则，数字广播系统获取消息信道的剩余容量，并检测剩余容量是否大于或者等于消息封装包的第一字节长度，若检测到剩余容量大于或者等于第一字节长度，则检测第一消息子信道是否存在第一剩余容量，若检测到剩余容量小于第一字节长度，则将该消息封装包封装至其他剩余容量大于或者等于第一字节长度的消息信道中。若检测到剩余容量大于或者等于第一字节长度，并检测到不存在第一剩余容量，则将消息封装包封装至第二消息子信道，若检测到存在第一剩余容量，则将第一字节长度拆分成与第一剩余容量大小相等的第一信息封装包，并将该第一消息封装包封装至第一消息子信道，再将剩余的第二消息封装包封装至第二消息子信道。
需要说明的是，同一个消息封装包可以被拆分到不同的消息子信道，但是不能被拆分到不同的消息信道。
在本实施例中，比如，消息信道的剩余容量为10字节，第一消息子信道的容量为2字节，第二消息子信道的容量为8字节，消息封装包的字节长度为9字节，数字广播系统将该消息封装包先拆分出2字节的第一信息封装包封装至第一消息子信道，再将剩余7字节的第二消息封装包封装至第二消息子信道。
步骤j，若所述数据封装格式为业务流封装格式，则确定所述数据封装包为业务封装包，并确定所述数据封装规则为业务流封装规则；
步骤k，获取第一业务子信道的第一信道长度，并检测所述业务封装包的第二字节长度是否小于所述第一信道长度；
步骤l，若检测到所述第二字节长度小于所述第一信道长度，则检测是否存在第一业务封装包；
步骤m，若检测到存在所述第一业务封装包，则检测所述第一业务封装包封装后第二业务子信道剩余的第二信道长度，并将所述业务封装包分段封装至所述第一业务子信道和所述第二业务子信道。
具体地，参照图6，图6为本申请业务流封装规则，数字广播系统若检测到数据封装格式为业务流封装格式，则确定数据封装包为业务封装包，并确定数据封装规则为业务流封装规则，数字广播系统获取第一业务子信道的第一信道长度，并检测业务封装包的第二字节长度是否小于第一信道长度，若检测到第二字节长度小于第一信道长度，则检测是否存在第一业务封装包，若检测到存在第一业务封装包，则检测第一业务封装包封装后第二业务子信道剩余的第二信道长度，并将该业务封装包拆分为与第二信道长度的长度大小相等的第二业务封装包，并将该第二业务封装包封装至第二业务子信道中，再将该业务封装包剩余的第三业务封装包封装至第一业务子信道。若检测到不存在第一业务封装包，则直接将该业务封装包封装至第一业务子信道。
需要说明的是，当业务封装包的剩余净荷长度大于或者等于对应的业务子信道长度时，业务流封装的大小限定为业务子信道长度。一个业务流封装可以封装多个业务封装包。
进一步地，参照图7，图7为本申请业务包封装规则，数字广播系统若检测到数据封装格式为业务包封装格式，则确定数据封装包为业务封装包，并确定数据封装规则为业务包封装规则，数字广播系统获取第一业务子信道的第一信道长度，并检测业务封装包的第二字节长度是否小于第一信道长度，若检测到第二字节长度小于第一信道长度，则检测是否存在第一业务封装包，若检测到存在第一业务封装包，则检测第一业务封装包封装后第二业务子信道剩余的第二信道长度，并将该业务封装包拆分为与第二信道长度的长度大小相等的第二业务封装包，并将该第二业务封装包封装至第二业务子信道中，再将该业务封装包剩余的第三业务封装包封装至第一业务子信道。若检测到不存在第一业务封装包，则直接将该业务封装包封装至业务子信道。
需要说明的是，当业务封装包的剩余净荷长度大于或者等于对应的业务子信道长度时，业务包封装的大小限定为业务子信道长度。一个业务包封装只可以封装一个业务封装包。
进一步地，所述数据的封装方法还包括：
步骤n，侦测到上层应用发出数据传输指令后，将输入数据格式发送至所述上层应用，以供所述上层应用将待发送数据的数据格式转换为所述输入数据格式，得到所述待传输数据。
数字广播系统侦测到上层应用发出数据传输指令后，将输入数据格式发送至上层应用，上层应用接收到该输入数据格式后，将待发送数据的数据格式转换为该输入数据格式，得到待传输数据，并将该待传输数据发送至数字广播系统。
其中，参照图8，图8为本申请系统配置信息的输入数据格式，系统配置信息的输入数据格式为数据标识+数据长度+上层应用控制参数域+数据传输系统参数域。数据标识的字节长度为1字节，0x00表示为系统配置信息。数据长度的字节长度为1字节，表示系统配置信息的内容长度，不包括数据标识和数据长度。
上层应用控制参数域包括系统启动时间、授时功能指示、频谱模式和帧长度。其中，系统启动时间的字节长度为4字节，0表示立即启动，其他值表示物理帧信号的开始发射时间，当授时功能开启时也对应授时开启时的初始时间。授时功能指示的字节长度为1字节，指示系统是否开启授时功能，发送授时消息。频谱模式的字节长度为1字节，共生调频数据广播系统中有8种频谱模式。帧长度的字节长度为1字节，取值表示一个物理帧包含子帧的个数。
数据传输系统参数域包括业务数量、业务编号LDPC（低密度校验码）块数、编码码率、交织深度、映射方式、数据封装格式、扩频倍率、授权序列。其中，业务数量的字节长度为1字节，表示物理信号帧内承载的业务个数。业务编号的字节长度为1字节，表示业务的标识和排列编号。LDPC块数的字节长度为1字节，表示取值为物理帧内业务的FEC编码块数。编码码率的字节长度为1字节，表示FEC编码码率中的对应编号。交织深度的字节长度为1字节，表示业务的交织深度。映射方式的字节长度为1字节，表示业务的星座映射方式。数据封装格式的字节长度为1字节，1表示业务流，2表示业务包。扩频倍率的字节长度为1字节，表示业务需要扩频时的扩频参数。授权序列的字节长度为1字节，用于初始化物理层扰码的初始PN（Pseudo-Noise Code，PN码）值。
进一步地，参照图9，图9为本申请消息数据的输入数据格式，消息数据的输入数据格式为数据标识+消息编号+消息数据传输控制参数域+消息数据内容域。其中，消息编码（十进制表示）和消息编码对应的类型为消息编码0对应控制消息，消息编码1对应授时消息，消息编码2对应紧急消息，消息编码3对应业务描述消息，消息编码4对应RTK（Real-time Kinematic，实时动态）消息，以及消息编码5至消息编码63对应其他用户消息。其中，数据标识的字节长度为1字节，0x01表示消息数据。消息编号的字节长度为1字节，取值范围1至63。
消息数据传输控制参数域包括消息时间戳、重复播发次数和播发间隔。其中消息时间戳的字节长度为1字节，表示消息的发送时间信息。重复播发次数的字节长度为1字节，表示消息重复播发多次后结束播发，0表示不重发，255表示无限重发，其他值表示实际重发次数。播发间隔的字节长度为1字节，表示。以物理帧为单位，0表示每个物理帧都播发，其他值表示间隔多少个物理帧再次播发。
消息数据内容域包括消息数据长度和消息数据净荷。其中，消息数据长度的字节长度为1字节，表示消息数据净荷的长度，单位为字节，取值范围1至60。消息数据净荷的字节长度不作限制，表示消息数据的净荷内容，对应用户定义的一条完整消息数据。
进一步地，参照图10，图10为本申请业务数据的输入数据格式，业务数据的输入数据格式为数据标识+业务编号+业务数据传输控制参数域+业务数据内容域。其中，数据标识的字节长度为1字节，0x02表示业务数据。业务编号的字节长度为1字节，表示业务的排列编号，业务在物理层上排列的顺序和业务数据对应调制参数在系统控制信息消息中的排列顺序由此编号给出，作为优先级的一个编号。业务数据传输控制参数域包括业务时间戳，字节长度为4字节，表示业务的发送时间信息（0则表示即时按顺序发送）。业务数据内容域包括业务长度和业务净荷，其中，业务长度的字节长度为2字节，表示业务净荷的长度，单位为字节。业务净荷字节长度不作限制，表示业务的净荷内容，对应用户的一个业务数据包。
本实施例通过接收待传输数据，根据待传输数据中的数据标识和传输需求进行分类，确定待传输数据对应的数据类型，根据数据类型确定待传输数据对应的封装格式编码，根据封装格式编码确定对应的数据封装格式，并根据数据封装格式将待传输数据转化为对应的数据封装包，根据数据封装格式确定对应的数据封装规则，通过数据封装规则将数据封装包进行封装。由此可知，本申请在数据封装的过程，需要根据数据标识和传输需求将待传输数据进行分类，然后确定待传输数据对应的封装格式编码，根据封装格式编码确定对应的数据封装格式，再根据数据封装格式确定对应的数据封装规则，并通过数据封装规则对数据封装包进行封装，实现了根据待传数据的特点和传输需求对待传输数据进行设计，从而实现了根据待传输数据的分类不同，通过不同的数据封装规则进行数据封装，从而减少了带宽损耗。
进一步地，提出本申请数据的封装方法第二实施例。
所述数据的封装方法第二实施例与所述数据的封装方法第一施例的区别在于，所述数据的封装方法还包括：
步骤o，确定所述待传输数据对应的数据输出格式，并将封装后的待传输数据转化为所述数据输出格式的传输数据源发送至物理层。
具体地，数字广播系统根据待传输数据的数据类型确定对应的输出数据标识，根据数据输出标识和数据输出格式在数字广播系统中的映射关系确定对应的数据输出格式，然后将封装后的待传输数据转化为与该数据输出格式对应的传输数据源，再将该传输数据源发送至物理层。其中，数据输出标识和数据输出格式的映射关系确定对应的数据输出格式是在数字广播系统预先设定的，本实施例不作限制。
其中，系统配置信息的输出数据格式为数据输出标识+数据长度+上层应用控制参数域+数据传输系统参数域。数据输出标识的字节长度为1字节，0x30表示为系统配置信息输出格式。数据长度的字节长度为1字节，表示系统配置信息的内容长度，不包括数据标识和数据长度。
上层应用控制参数域包括系统启动时间、授时功能指示、频谱模式和帧长度。其中，系统启动时间的字节长度为4字节，0表示立即启动，其他值表示物理帧信号的开始发射时间，当授时功能开启时也对应授时开启时的初始时间。授时功能指示的字节长度为1字节，指示系统是否开启授时功能，发送授时消息。频谱模式的字节长度为1字节，共生调频数据广播系统中有8种频谱模式。帧长度的字节长度为1字节，取值表示一个物理帧包含子帧的个数。
数据传输系统参数域包括业务数量、业务编号LDPC（低密度校验码）块数、编码码率、交织深度、映射方式、数据封装格式、扩频倍率、授权序列。其中，业务数量的字节长度为1字节，表示物理信号帧内承载的业务个数。业务编号的字节长度为1字节，表示业务的标识和排列编号。LDPC块数的字节长度为1字节，表示取值为物理帧内业务的FEC编码块数。编码码率的字节长度为1字节，表示FEC编码码率中的对应编号。交织深度的字节长度为1字节，表示业务的交织深度。映射方式的字节长度为1字节，表示业务的星座映射方式。数据封装格式的字节长度为1字节，1表示业务流，2表示业务包。扩频倍率的字节长度为1字节，表示业务需要扩频时的扩频参数。授权序列的字节长度为1字节，用于初始化物理层扰码的初始PN（Pseudo-Noise Code，PN码）值。
进一步地，消息数据的输出数据格式为数据输出标识+数据长度+消息数据传输控制参数域+消息包列表。其中，数据输出标识的字节长度为1字节，0x04表示消息数据输出格式。数据长度的字节长度为2字节，表示从时间戳开始到消息包结束（包括填充数据）的长度，单位为字节。消息数据传输控制参数域包括时间戳，字节长度为4字节，0表示立即发送，其他值对应物理帧信号的起始时间。消息包列表包括控制信息消息包、消息数据封装包、业务填充包和填充数据。其中，控制信息消息包字节长度固定为16字节。消息数据封装包可有多个，消息数据封装包1表示根据消息数据的实时情况进行封装后得到的消息数据封装包1，消息数据封装包2表示根据消息数据的实时情况进行封装后得到的消息数据封装包2....至消息数据封装包n表示根据消息数据的实时情况进行封装后得到的消息数据封装包n，n为大于或者等于1的任意整数值，本实施例不作限定。业务填充包的字节长度为1字节，用0xc0表示。填充数据为全0。
进一步地，业务数据的输入数据格式为数据输出标识+数据长度+业务数据传输控制参数域+业务数据封装列后数据域。其中，数据输出标识的字节长度为1字节，0x05表示业务数据输出格式。业务数据传输控制参数域包括时间戳字节长度为4字节，0表示立即发送，其他值对应物理帧信号的起始时间。
业务数据封装列后数据域包括业务编号、交织编号、数据长度、业务数据域、业务填充包和填充数据。其中，业务编号的字节长度为1字节，表示传输内容所对应的业务编号。交织编号的字节长度为1字节，表示业务在物理帧分为多个交织块时，应按照交织块的先后顺序依次发送给物理层。数据长度的字节长度为2字节，表示业务数据域+业务填充包+填充数据的总长度，单位为字节。业务数据域，表示业务数据域内包含多个业务封装包（业务流封装包或者业务包封装包），总长度满足物理层对一个交织块数据量的需求。业务填充包的字节长度为1字节，用0xc0表示。填充数据全0。其中，业务数据域、业务填充包和填充数据构成物理层交织块。
需要说明的是，参照图11，图11为本申请业务净荷映射到交织块的过程，在共生调频数据广播系统中，业务封装包按业务区分以交织块为单位填充到链路层业务数据的业务数据域，当业务数据域不够组成完整的物理层交织块时，以业务填充包补充完整，业务数据域、填充包、填充数据组成物理层交织块。物理层交织块加上必要的数据传输格式后，形成链路层业务数据传送到物理层，物理层根据“物理层配置信息表”中对各个业务的调制参数的描述完成对业务数据的调制和映射。链路层将链路层业务数据以业务的交织块为基本单元向物理层传输，向物理层发送链路层业务数据时，每个链路层业务数据中仅包含一个业务的一个交织块的数据。业务中包含多个交织块时应按交织块顺序依次传输包含各理层交织块的链路层业务数据。数字广播系统包含多业务时，按照业务编号的顺序，依次传送完一个业务的所有物理层交织块后再传送下一个业务的数据。
本实施例通过确定待传输数据对应的数据输出格式，并将封装后的待传输数据转化为数据输出格式的传输数据源发送至物理层。由此可知，本实施例通过协调上层应用与物理层之间的数据转换关系，对待传输数据进行整理后再向下传至物理层，保障传输质量的同时，简化了上层应用与物理层的操作难度。
此外，本申请还提供一种数据的封装装置，参照图12，所述数据的封装装置包括：
接收模块10，用于接收待传输数据；
分类模块20，用于根据所述待传输数据中的数据标识和传输需求进行分类，确定所述待传输数据对应的数据类型；
确定模块30，用于根据所述数据类型确定所述待传输数据对应的封装格式编码，根据所述封装格式编码确定对应的数据封装格式；
转化模块40，用于根据所述数据封装格式将所述待传输数据转化为对应的数据封装包；
所述确定模块30还用于根据所述数据封装格式确定对应的数据封装规则；
封装模块50，用于通过所述数据封装规则将所述待传输数据进行封装。
进一步地，所述确定模块30还用于若所述数据封装格式为消息包封装格式，则确定所述数据封装包为消息封装包，并确定所述数据封装规则为消息包封装规则。
进一步地，所述封装模块50包括：
第一获取单元，用于获取消息信道的剩余容量；
第一检测单元，用于检测所述剩余容量是否大于或者等于所述消息封装包的第一字节长度；若检测到所述剩余容量大于或者等于所述第一字节长度，则检测第一消息子信道是否存在第一剩余容量；
第一封装单元，用于若检测到不存在所述第一剩余容量，则将所述消息封装包封装至第二消息子信道。
进一步地，所述确定模块30还用于若所述数据封装格式为业务流封装格式，则确定所述数据封装包为业务封装包，并确定所述数据封装规则为业务流封装规则。
进一步地，所述封装模块50包括：
第二获取单元，用于获取第一业务子信道的第一信道长度；
第二检测单元，用于检测所述业务封装包的第二字节长度是否小于所述第一信道长度；若检测到所述第二字节长度小于所述第一信道长度，则检测是否存在第一业务封装包；若检测到存在所述第一业务封装包，则检测所述第一业务封装包封装后第二业务子信道剩余的第二信道长度；
第二封装单元，用于所述业务封装包分段封装至所述第一业务子信道和所述第二业务子信道。
进一步地，所述确定模块30包括：
第三获取单元，用于获取格式编码映射表；
确定单元，用于根据所述数据类型在所述格式编码映射表中确定所述待传输数据对应的封装格式编码；
所述第三获取单元还用于获取封装格式映射表；
所述确定单元还用于根据所述封装格式映射表和所述封装格式编码确定所述待传输数据对应的数据封装格式。
进一步地，所述转化模块还用于若所述数据封装格式为消息包封装格式，则将所述待传输数据转化为消息封装包；若所述数据封装格式为业务流封装格式或者业务包封装格式，则将所述待传输数据转化为业务封装包。
进一步地，所述接收模块10还用于接收所述待传输数据。
进一步地，所述分类模块20包括：
第四获取单元，用于获取所述待传输数据中的数据标识和数据参数传输类型；
分类单元，用于结合所述数据标识和所述数据参数传输类型将所述待传输数据进行分类。
进一步地，所述确定模块30还用于确定所述待传输数据对应的数据类型。
进一步地，所述数据的封装装置还包括：
发送模块，用于侦测到上层应用发出数据传输指令后，将输入数据格式发送至所述上层应用，以供所述上层应用将待发送数据的数据格式转换为所述输入数据格式，得到所述待传输数据。
本申请基于数据的封装装置具体实施方式与上述基于数据的封装方法各实施例基本相同，在此不再赘述。
此外，本申请还提供一种数据的封装系统。如图13所示，图13是本申请实施例方案涉及的硬件运行环境的结构示意图。
需要说明的是，图13即可为数据的封装系统的硬件运行环境的结构示意图。
如图13所示，该数据的封装系统可以包括：处理器1001，例如CPU（Central Processing Unit，中央处理器），存储器1005，用户接口1003，网络接口1004，通信总线1002。通信总线1002用于实现这些组件之间的连接通信。用户接口1003可以包括显示屏（Display）、输入单元比如键盘（board），可选用户接口1003还可以包括标准的有线接口（如USB（Universal Serial Bus，通用串行总线）接口）、无线接口（如蓝牙接口）。网络接口1004可选的可以包括标准的有线接口、无线接口（如WI-FI（（Wireless-Fidelity））接口）。存储器1005可以是高速RAM存储器，也可以是稳定的存储器（non-volatile memory），例如磁盘存储器。存储器1005可选的还可以是独立于前述处理器1001的存储装置。
在一实施例中，数据的封装系统还可以包括RF（Radio Frequency，射频）电路，传感器、WiFi模块等等。
本领域技术人员可以理解，图13中示出的数据的封装系统结构并不构成对数据的封装系统的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
如图13所示，作为一种计算机存储介质的存储器1005中可以包括操作设备、网络通信模块、用户接口模块以及数据的封装程序。其中，操作设备是管理和控制数据的封装系统硬件和软件资源的程序，支持数据的封装程序以及其它软件或程序的运行。
在图所示的数据的封装系统中，用户接口1003主要用于上层应用，以接收数字广播系统发送的数据输入格式和将待传输数据发送至数字广播系统；网络接口1004主要用于数字广播系统，以接收上层应用发送的待传输数据和将封装后的待传输数据发送至物理层；处理器1001可以用于调用存储器1005中存储的数据的封装程序，并完成如上所述的数据的封装系统的控制方法的步骤。
本申请数据的封装系统具体实施方式与上述数据的封装方法各实施例基本相同，在此不再赘述。
此外，本申请实施例还提出一种计算机可读存储介质，所述计算机可读存储介质上存储有数据的封装程序，所述数据的封装程序被处理器完成时实现如上所述的数据的封装方法的步骤。
本申请计算机可读存储介质具体实施方式与上述数据的封装方法各实施例基本相同，在此不再赘述。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的数据下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多数据下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件货物的形式体现出来，该计算机软件货物存储在一个存储介质（如ROM/RAM、磁碟、光盘）中，包括若干指令用以使得一台数据的封装系统完成本申请各个实施例所述的方法。

Claims (10)

  1. 一种数据的封装方法，其中，所述数据的封装方法包括以下步骤：
    接收待传输数据，根据所述待传输数据中的数据标识和传输需求进行分类，确定所述待传输数据对应的数据类型；
    根据所述数据类型确定所述待传输数据对应的封装格式编码，根据所述封装格式编码确定对应的数据封装格式，并根据所述数据封装格式将所述待传输数据转化为对应的数据封装包；
    根据所述数据封装格式确定对应的数据封装规则，通过所述数据封装规则将所述数据封装包进行封装。
  2. 如权利要求1所述的数据的封装方法，其中，所述根据所述数据封装格式确定对应的数据封装规则，通过所述数据封装规则将所述数据封装包进行封装的步骤包括：
    若所述数据封装格式为消息包封装格式，则确定所述数据封装包为消息封装包，并确定所述数据封装规则为消息包封装规则；
    获取消息信道的剩余容量，并检测所述剩余容量是否大于或者等于所述消息封装包的第一字节长度；
    若检测到所述剩余容量大于或者等于所述第一字节长度，则检测第一消息子信道是否存在第一剩余容量；
    若检测到不存在所述第一剩余容量，则将所述消息封装包封装至第二消息子信道。
  3. 如权利要求1所述的数据的封装方法，其中，所述根据所述数据封装格式确定对应的数据封装规则，通过所述数据封装规则将所述数据封装包进行封装的步骤包括：
    若所述数据封装格式为业务流封装格式，则确定所述数据封装包为业务封装包，并确定所述数据封装规则为业务流封装规则；
    获取第一业务子信道的第一信道长度，并检测所述业务封装包的第二字节长度是否小于所述第一信道长度；
    若检测到所述第二字节长度小于所述第一信道长度，则检测是否存在第一业务封装包；
    若检测到存在所述第一业务封装包，则检测所述第一业务封装包封装后第二业务子信道剩余的第二信道长度，并将所述业务封装包分段封装至所述第一业务子信道和所述第二业务子信道。
  4. 如权利要求1所述的数据的封装方法，其中，所述根据所述数据类型确定所述待传输数据对应的封装格式编码，根据所述封装格式编码确定对应的数据封装格式的步骤包括：
    获取格式编码映射表，根据所述数据类型在所述格式编码映射表中确定所述待传输数据对应的封装格式编码；
    获取封装格式映射表，根据所述封装格式映射表和所述封装格式编码确定所述待传输数据对应的数据封装格式。
  5. 如权利要求1所述的数据的封装方法，其中，所述根据所述数据封装格式将所述待传输数据转化为对应的数据封装包的步骤包括：
    若所述数据封装格式为消息包封装格式，则将所述待传输数据转化为消息封装包；
    若所述数据封装格式为业务流封装格式或者业务包封装格式，则将所述待传输数据转化为业务封装包。
  6. 如权利要求1所述的数据的封装方法，其中，所述接收待传输数据，根据所述待传输数据中的数据标识和传输需求进行分类，确定所述待传输数据对应的数据类型的步骤包括：
    接收所述待传输数据，并获取所述待传输数据中的数据标识和数据参数传输类型，结合所述数据标识和所述数据参数传输类型将所述待传输数据进行分类，确定所述待传输数据对应的数据类型。
  7. 如权利要求1至6任一项所述的数据的封装方法，其中，所述接收待传输数据，根据所述待传输数据中的数据标识和传输需求进行分类，确定所述待传输数据对应的数据类型的步骤之前，还包括：
    侦测到上层应用发出数据传输指令后，将输入数据格式发送至所述上层应用，以供所述上层应用将待发送数据的数据格式转换为所述输入数据格式，得到所述待传输数据。
  8. 一种数据的封装装置，其中，所述数据的封装装置包括：
    接收模块，用于接收待传输数据；
    分类模块，用于根据所述待传输数据中的数据标识和传输需求进行分类，确定所述待传输数据对应的数据类型；
    确定模块，用于根据所述数据类型确定所述待传输数据对应的封装格式编码，根据所述封装格式编码确定对应的数据封装格式；
    转化模块，用于根据所述数据封装格式将所述待传输数据转化为对应的数据封装包；
    所述确定模块还用于根据所述数据封装格式确定对应的数据封装规则；
    封装模块，用于通过所述数据封装规则将所述待传输数据进行封装。
  9. 一种数据的封装系统，其中，所述数据的封装系统包括存储器、处理器和存储在所述存储器上并在所述处理器上运行的数据的封装程序，所述数据的封装程序被所述处理器完成时实现如权利要求1至7中任一项所述的数据的封装方法的步骤。
  10. 一种计算机可读存储介质，其中，所述计算机可读存储介质上存储有数据的封装程序，所述数据的封装程序被处理器完成时实现如权利要求1至7中任一项所述的数据的封装方法的步骤。
PCT/CN2021/098392 2020-07-16 2021-06-04 数据的封装方法、装置、系统及计算机可读存储介质 WO2022012210A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010690509.9A CN111885038B (zh) 2020-07-16 2020-07-16 数据的封装方法、装置、系统及计算机可读存储介质
CN202010690509.9 2020-07-16

Publications (1)

Publication Number Publication Date
WO2022012210A1 true WO2022012210A1 (zh) 2022-01-20

Family

ID=73155727

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/098392 WO2022012210A1 (zh) 2020-07-16 2021-06-04 数据的封装方法、装置、系统及计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN111885038B (zh)
WO (1) WO2022012210A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114386368A (zh) * 2022-03-23 2022-04-22 百芯智能制造科技(深圳)有限公司 一种封装规格项数据的处理方法以及处理装置
CN117114032A (zh) * 2023-07-20 2023-11-24 深圳市飞易通科技有限公司 一种扫码数据传输方法、装置及存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111885038B (zh) * 2020-07-16 2022-06-10 深圳思凯微电子有限公司 数据的封装方法、装置、系统及计算机可读存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008154779A1 (fr) * 2007-06-19 2008-12-24 Zte Corporation Appareil et procédé d'encapsulation de données
WO2012108919A2 (en) * 2011-02-11 2012-08-16 Intel Corporation Media stream over pass through mechanism
WO2016187813A1 (zh) * 2015-05-26 2016-12-01 华为技术有限公司 一种光电混合网络的数据传输方法及装置
CN106656751A (zh) * 2016-12-05 2017-05-10 北京中交兴路信息科技有限公司 一种数据通信的方法及装置
CN109450875A (zh) * 2018-10-23 2019-03-08 清华大学 Mac层封装方法及装置
CN111885038A (zh) * 2020-07-16 2020-11-03 深圳思凯微电子有限公司 数据的封装方法、装置、系统及计算机可读存储介质

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6584118B1 (en) * 1998-08-27 2003-06-24 Nortel Networks Limited Payload mapping in synchronous networks
CN101212413A (zh) * 2006-12-30 2008-07-02 中兴通讯股份有限公司 一种移动多媒体广播数据的传输方法
CN101692675B (zh) * 2009-10-20 2012-05-30 中国电子科技集团公司第二十八研究所 多通道智能化数据通信处理系统
US20150049163A1 (en) * 2013-03-15 2015-02-19 James Paul Smurro Network system apparatus and method of use adapted for visual neural networking with multi-channel multiplexed streaming medical imagery and packetized clinical informatics
US9137216B2 (en) * 2013-08-13 2015-09-15 Verizon Patent And Licensing Inc. Session layer data security
CN103905922B (zh) * 2014-03-18 2017-08-25 深圳市云宙多媒体技术有限公司 一种基于http协议的流媒体协议封装方法及装置
CN106549989B (zh) * 2015-09-17 2020-02-18 腾讯科技（深圳）有限公司 一种数据传输方法及其系统、用户终端、应用服务器
CN106411692A (zh) * 2016-06-29 2017-02-15 宁波市由乐讯通讯科技有限公司 一种改进型移动端和服务器端消息进行同步的方法及系统
CN108965484B (zh) * 2018-09-30 2021-08-03 深圳市酷达通讯有限公司 一种物联网数据的传输方法、系统及终端
TWI685243B (zh) * 2018-10-09 2020-02-11 孕龍科技股份有限公司 邏輯分析儀之匯流排封包格式顯示方法
CN109814863A (zh) * 2018-12-14 2019-05-28 深圳壹账通智能科技有限公司 一种请求返回数据的处理方法、装置、计算机设备及计算机存储介质
CN111918091A (zh) * 2020-08-11 2020-11-10 四川九州电子科技股份有限公司 一种实现多媒体节目分发的方法及卫星电视直播系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008154779A1 (fr) * 2007-06-19 2008-12-24 Zte Corporation Appareil et procédé d'encapsulation de données
WO2012108919A2 (en) * 2011-02-11 2012-08-16 Intel Corporation Media stream over pass through mechanism
WO2016187813A1 (zh) * 2015-05-26 2016-12-01 华为技术有限公司 一种光电混合网络的数据传输方法及装置
CN106656751A (zh) * 2016-12-05 2017-05-10 北京中交兴路信息科技有限公司 一种数据通信的方法及装置
CN109450875A (zh) * 2018-10-23 2019-03-08 清华大学 Mac层封装方法及装置
CN111885038A (zh) * 2020-07-16 2020-11-03 深圳思凯微电子有限公司 数据的封装方法、装置、系统及计算机可读存储介质

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114386368A (zh) * 2022-03-23 2022-04-22 百芯智能制造科技(深圳)有限公司 一种封装规格项数据的处理方法以及处理装置
CN117114032A (zh) * 2023-07-20 2023-11-24 深圳市飞易通科技有限公司 一种扫码数据传输方法、装置及存储介质

Also Published As

Publication number Publication date
CN111885038B (zh) 2022-06-10
CN111885038A (zh) 2020-11-03

Similar Documents

Publication Publication Date Title
WO2022012210A1 (zh) 数据的封装方法、装置、系统及计算机可读存储介质
KR101995314B1 (ko) Ｄｖｂ 지상파 방송 시스템에서 ｍｐｅｇ ｍｍｔ를 위한 시그널링 정보를 송수신하는 장치 및 방법
KR102035259B1 (ko) 디지털 방송 시스템에서 시그널링 정보 송수신 장치 및 방법
KR102445458B1 (ko) 송신 장치, 송신 방법, 수신 장치 및 수신 방법
US7782836B2 (en) Method and system for transmission of different types of information in wireless communication
US8782732B2 (en) Method for signalling time-slicing parameters in the service information
KR102386821B1 (ko) 방송 시스템에서 시스템 시간 정보를 송수신하는 기법
EP3404922B1 (en) Fast dvb channel switching method, apparatus, and system
CN103650431B (zh) 视频数据传输方法及装置
WO2018166517A1 (zh) 一种数据传输方法、数据发送设备及数据接收设备
KR20140126827A (ko) Dvb 시스템에서 mmt를 이용하여 방송 서비스를 송수신하는 방법 및 장치
CN101729887B (zh) 一种数字广播系统的数据传输方法及装置
CN110944003A (zh) 文件传输方法和电子设备
US20180146077A1 (en) Method and apparatus for determining processing mode for data packet
CN111555855A (zh) 一种无线传输方法和装置
WO2020177169A1 (zh) 通信的方法、装置及系统
CN114360297A (zh) 一种低空空域通用航空器的数据传输方法、系统
CN113141520B (zh) 视频流传输方法、装置、电子设备及存储介质
CN112436919B (zh) 流数据传输方法、装置、设备及计算机可读存储介质
WO2010009652A1 (zh) 一种复用数据流的传输方法
CN116018799B (zh) 一种图像传输方法及装置
CN108631973A (zh) 一种信息指示的方法及设备
WO2018077417A1 (en) Sequence numbers in multiple protocol layered mobile communication
WO2012041165A1 (zh) Mbms状态报告的发送方法、系统、终端和网络侧设备
KR100799538B1 (ko) Ｄｖｂ－ｓ２ 기반 양방향 위성통신 시스템에서의 방송 및통신 데이터 송/수신장치

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 13/06/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 21841829

Country of ref document: EP

Kind code of ref document: A1