KR20210034571A - Transmitting apparatus and receiving apparatus and controlling method thereof - Google Patents

Abstract

Disclosed is a transmission apparatus. The transmission apparatus includes: a packet generation part generating a packet including a header and a payload, based on an input packet; a signal processing part signalizing the generated packet; and a transmission part transmitting the signalized packet. A base field constituting the header includes a first field set with a first value indicating that the base field is a first length or a second value indicating that the base field is a second length. When the first field is set with the second value, the base field includes a second field indicating least significant bits (LSB) of a pointer value indicating the first value of each starting point of the input packet included in the payload and a third field indicating most significant bits (MSB) of the pointer value. Therefore, since an input stream can be efficiently mapped with a physical hierarchy, data processing efficiency can be increased.

Description

Transmitting device, receiving device, and control method thereof {TRANSMITTING APPARATUS AND RECEIVING APPARATUS AND CONTROLLING METHOD THEREOF}

The present invention relates to a transmission apparatus, a reception apparatus, and a control method thereof, and more particularly, to a transmission apparatus, a reception apparatus, and a control method thereof that map and transmit data to at least one signal processing path.

In the information society of the 21st century, broadcasting and communication services are entering the era of full-scale digitalization, multi-channelization, broadbandization, and high quality. In particular, as the spread of high-definition digital TVs, PMPs, and portable broadcasting devices is expanding in recent years, there is an increasing demand for supporting various reception methods for digital broadcasting services.

In response to these demands, the standard group has established various standards to provide various services that can satisfy the needs of users. Therefore, a search for a method to provide better services through better performance is requested.

The present invention has been conceived in accordance with the above-described necessity, and an object of the present invention is to provide a transmitting device, a receiving device, and a control method for generating a frame having a format suitable for transmitting various types of data.

According to an embodiment for achieving the above object, a transmission device includes a packet generator for generating a packet including a header and a payload based on an input packet, a signal processor for signal processing the generated packet, and the signal. Including a transmission unit for transmitting the processed packet, the base field (Base field) constituting the header is set to a first value indicating that the base field is a first length or a second value indicating that the base field is a second length The first field is included, and when the first field is set to the second value, the base field is LSB (least significant) of a pointer value indicating the first value of each starting point of the input packet included in the payload. bits) and a third field indicating the most significant bits (MSBs) of the pointer value.

Here, the base field includes a fourth field indicating an extension mode of the header, and the fourth field includes the presence or absence of an optional field, a length of the optional field, and an extension field It may include at least one of information on the structure of.

In addition, the fourth field may include at least one of information on the presence or absence of an optional field, a length of the optional field, and a structure of the extension field. (Deleted)

In addition, the fourth field includes a third value indicating that the optional field and the extension field do not exist, a fourth value indicating that the optional field is present and the length of the optional field is 1 byte, and the optional field is present and the A fifth value indicating that the length of the optional field is 2 bytes, and the optional field is present, the length of the optional field is 2 bytes, and the extension field is set to one of sixth values indicating a structure including a plurality of extension payloads. I can.

In addition, when the fourth field is set to the fourth value or the fifth value, the optional field is a fifth field indicating a type of an extension payload included in the extension field and a sixth field indicating a length of the extension field. Further includes, and when the fifth field is set to a preset value, all the extension fields may be filled with padding.

In addition, when the fourth field is set to the fifth value, the optional field is a field indicating a type of an extension payload included in the extension field, a field indicating an LSB part of a field indicating a length of the extension field, and the A field indicating the MSB part of the field indicating the length of the Extension field may be included.

In addition, when the fourth field is set to the sixth value, the optional field is a field indicating the number of a plurality of extension payloads included in the extension field, and a field indicating an LSB part of a field indicating the length of the extension field. And a field indicating the MSB part of the field indicating the length of the Extension field.

In addition, the Extension field may include a plurality of fields indicating a type of each of the plurality of extension payloads and a plurality of fields indicating a length of each of the plurality of extension payloads.

In addition, in the Extension field, when the fourth field is set to one of the fourth value and the fifth value, and the length of the extension payload included in the Extension field is less than the length of the Extension field, You can include the extension payload and padding for the rest of the parts.

In addition, when the fourth field is set to the sixth value, the Extension field may include a plurality of extension payloads in the Extension field and padding in the remaining portion.

Meanwhile, the receiving device according to an embodiment of the present invention includes a receiving unit receiving a stream including a packet including a header and a payload, extracting the header from the packet, and extracting information included in the header. A signal processor for signal processing the input packet included in the payload based on the sub and the extracted information, wherein the base field constituting the header is a first value indicating that the base field is a first length or the base Includes a first field that is set to a second value indicating that the field is a second length, and when the first field is set to the second value, the base field is among the starting points of each input packet included in the payload. A second field indicating the least significant bits (LSB) of the pointer value indicating the first value and a third field indicating the most significant bits (MSB) of the pointer value may be included.

Meanwhile, a method for controlling a transmission device according to an embodiment of the present invention includes generating a packet including a header and a payload based on an input packet, signal processing the generated packet, and the signal-processed packet. And transmitting, wherein the base field (Base field) constituting the header is set to a first value indicating that the base field is a first length or a second value indicating that the base field is a second length. Field, and when the first field is set to the second value, the base field indicates LSB (least significant bits) of a pointer value indicating a first value of each start point of an input packet included in the payload. A second field indicating and a third field indicating most significant bits (MSBs) of the pointer value may be included.

In addition, the base field includes a fourth field indicating an extension mode of the header, and the fourth field includes the presence or absence of an optional field, a length of the optional field, and an extension field. It may include at least one of information on the structure of.

In addition, the fourth field may include at least one of information on the presence or absence of an optional field, a length of the optional field, and a structure of the extension field. (Deleted)

In addition, the fourth field includes a third value indicating that the optional field and the extension field do not exist, a fourth value indicating that the optional field is present and the length of the optional field is 1 byte, and the optional field is present and the A fifth value indicating that the length of the optional field is 2 bytes, and the optional field is present, the length of the optional field is 2 bytes, and the extension field is set to one of sixth values indicating a structure including a plurality of extension payloads. I can.

In addition, when the fourth field is set to the fourth value or the fifth value, the optional field is a fifth field indicating a type of an extension payload included in the extension field and a sixth field indicating a length of the extension field. Further includes, and when the fifth field is set to a preset value, all the extension fields may be filled with padding.

In addition, when the fourth field is set to the fifth value, the optional field is a field indicating a type of an extension payload included in the extension field, a field indicating an LSB part of a field indicating a length of the extension field, and the A field indicating the MSB part of the field indicating the length of the Extension field may be included.

In addition, when the fourth field is set to the sixth value, the optional field is a field indicating the number of a plurality of extension payloads included in the extension field, and a field indicating an LSB part of a field indicating the length of the extension field. And a field indicating the MSB part of the field indicating the length of the Extension field.

In addition, the Extension field may include a plurality of fields indicating a type of each of the plurality of extension payloads and a plurality of fields indicating a length of each of the plurality of extension payloads.

In addition, in the extension field, when the fourth field is set to one of the fourth value and the fifth value, and the length of the extension payload included in the extension field is less than the length of the extension field, You can include the extension payload and padding for the rest of the parts.

In addition, when the fourth field is set to the sixth value, the extension field may include a plurality of extension payloads in the extension field and padding in the remaining part.

Meanwhile, the control method of a receiving device according to an embodiment of the present invention includes receiving a stream including a packet including a header and a payload, extracting the header from the packet, and extracting information included in the header. And signal-processing the input packet included in the payload based on the extracted information, wherein the base field constituting the header indicates that the base field is a first length. A value or a first field set to a second value indicating that the base field is a second length, and when the first field is set to the second value, the base field is an input packet included in the payload A second field indicating the least significant bits (LSB) of a pointer value indicating a first value of each starting point of, and a third field indicating the most significant bits (MSB) of the pointer value may be included.

According to various embodiments of the present disclosure as described above, since an input stream can be efficiently mapped to a physical layer, data processing efficiency can be improved.

1 is a diagram illustrating a hierarchical structure of a transmission system according to an embodiment of the present invention.
2 is a diagram illustrating a schematic configuration of a broadcast link layer 1400 according to an embodiment of the present invention.
3A is a diagram illustrating a schematic configuration of a transmission system (or transmission device) according to an embodiment of the present invention.
3B and 3C are diagrams for explaining a multiplexing method according to an embodiment of the present invention.
4 is a block diagram showing a detailed configuration of the Input Formatting block shown in FIG. 3A.
5A and 5B are diagrams for explaining a detailed configuration of a baseband framing block.
6 is a block diagram showing the configuration of a transmission device according to an embodiment of the present invention.
7A is a block diagram showing a detailed configuration of a packet generator according to an embodiment of the present invention.
8 is a diagram illustrating a structure of a packet according to an embodiment of the present invention.
9 is a diagram illustrating a structure of a header according to an embodiment of the present invention.
10 is a diagram showing a detailed configuration of an optional field according to an embodiment of the present invention.
11 to 16D are diagrams illustrating a structure of a packet according to various embodiments of the present disclosure.
17 is a diagram illustrating a structure of a packet according to another embodiment of the present invention.
18 is a diagram showing a detailed configuration of the header shown in FIG. 17;
19 is a diagram showing a detailed configuration of an optional field according to another embodiment of the present invention.
20 to 24 are diagrams showing the structure of a packet according to various embodiments of the present invention.
25 is a diagram illustrating a structure of an extension field according to an embodiment of the present invention.
26A is a block diagram showing the configuration of a receiving device according to an embodiment of the present invention.
26B is a block diagram illustrating in detail a signal processing unit according to an embodiment of the present invention.
27 is a block diagram showing the configuration of a receiver according to an embodiment of the present invention.
28 is a block diagram showing a demodulator in more detail according to an embodiment of the present invention.
29 is a flowchart schematically illustrating an operation of a receiver from a time point when a user selects a service until an actual selected service is played according to an embodiment of the present invention.
30 is a flowchart illustrating a method of controlling a transmission device according to an embodiment of the present invention.
31 is a flowchart illustrating a method of controlling a reception device according to an embodiment of the present invention.

Hereinafter, various embodiments of the present invention will be described in detail with reference to the accompanying drawings. In addition, in describing the present invention, when it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to the intention or custom of users or operators. Therefore, the definition should be made based on the contents throughout the present specification.

An apparatus and method proposed in an embodiment of the present invention include a digital multimedia broadcasting (DMB, hereinafter referred to as'DMB') service, and a portable digital video broadcasting handheld (DVP-H, hereinafter referred to as'DMB') service. DVP-H'), and the mobile/portable advanced television systems committee mobile/handheld: ATSC-M/H, hereinafter referred to as'ATSC-M/H'. A) mobile broadcasting services such as services, digital video broadcasting systems such as Internet protocol television (IPTV, hereinafter referred to as'IPTV') services, and MPEG (moving picture experts group) media transport: MMT, hereinafter referred to as'MMT') system, evolved packet system (EPS, hereinafter referred to as'EPS'), and long-term evolution (LTE) , Hereinafter referred to as'LTE') a mobile communication system, a long-term evolution-advanced (LTE-A, hereinafter referred to as'LTE-A') mobile communication system, and a high-speed Downlink packet access (high speed downlink packet access: HSDPA, hereinafter referred to as'HSDPA') mobile communication system, and high speed uplink packet access (high speed uplink packet access: HSUPA, hereinafter referred to as'HSUPA') High-speed rate packet of mobile communication system and 3rd generation project partnership 2 (3GPP2, hereinafter referred to as '3GPP2') Data (high rate packet data: HRPD, hereinafter referred to as'HRPD') mobile communication system and 3GPP2 wideband code division multiple access (WCDMA, hereinafter referred to as'WCDMA') mobile communication The system and 3GPP2 code division multiple access (CDMA, hereinafter referred to as'CDMA') mobile communication system, and the International Institute of Electrical and Electronics Engineers (IEEE) Of course, it can be applied to various communication systems such as a communication system such as an 802.16m communication system and a mobile internet protocol (Mobile IP, hereinafter referred to as'Mobile IP') system.

1 is a diagram illustrating a hierarchical structure of a transmission system according to an embodiment of the present invention.

Referring to FIG. 1, a service includes media data 1000 constituting the service and signaling 1050 for delivering information required to acquire and consume media data in a receiver. Media data may be encapsulated in a form suitable for transmission prior to transmission. The encapsulation method may follow the Media Processing Unit (MPU) defined in ISO/IEC 23008-1 MPEG Media Transport (MMT) or the DASH segment format defined in ISO/IEC 23009-1 Dynamic Adaptive Streaming over HTTP (DASH). Media data 1000 and signaling 1050 are packetized according to an application layer protocol.

FIG. 1 shows a case in which an MMT protocol (MMTP) 1110 defined in MMT and a Real-Time Object Delivery over Unidirectional Transport (ROUTE) protocol 1120 are used as application layer protocols. In this case, in order to know which application layer protocol a specific service has been transmitted by the receiver, a method of notifying information on the application protocol through which the service is transmitted is required in a method independent of the application layer protocol.

The Service List Table (SLT) 1150 shown in FIG. 1 is a signaling method for satisfying the above-described purpose, and organizes service information into a table and packetizes it. Details of the SLT will be described later. The above-described packetized media data and signaling including the SLT are performed through the User Datagram Protocol (UDP) 1200 and the Internet Protocol (IP) 1300, and the broadcast link layer 1400 ). An example of a broadcast link layer is ATSC 3.0 Link-Layer Protocol (ALP) defined in ATSC 3.0. The ALP protocol generates an ALP packet by taking an IP packet as an input and delivers the ALP packet to the broadcast physical layer 1500.

However, according to FIG. 2 to be described later, the broadcast link layer 1400 does not use only the IP packet 1300 including media data or signaling as an input, but uses an MPEG2-TS packet or general packetized data as an input. Note that you can. In this case, signaling information required for control of the broadcast link layer is also delivered to the broadcast physical layer 1500 in the form of an ALP packet.

The broadcast physical layer 1500 signals an ALP packet as an input to generate a physical layer frame, converts the physical layer frame into a radio signal, and transmits it. In this case, the broadcast physical layer 1500 has at least one signal processing path. An example of a signal processing path may be DVB-T2 or ATSC 3.0 Physical Layer Pipe (PLP), and one or more services may be mapped to the PLP, or a part of the service may be mapped.

2 is a diagram illustrating a schematic configuration of a broadcast link layer 1400 according to an embodiment of the present invention.

Referring to FIG. 2, the input of the broadcast link layer 1400 includes an IP packet 1300, and further includes link layer signaling 1310, an MPEG2-TS packet 1320, and other packetized data 1330. can do.

The input data may undergo an additional signal processing process according to the type of input data before the ALP packetization 1450. As an example of the additional signal processing process, in the case of the IP packet 1300, the IP header compression process 1410 may be performed, and in the case of the MPEG2-TS packet, the header reduction process 1420 may be performed. In the ALP packetization process, input packets may be divided and merged.

3A is a diagram illustrating a schematic configuration of a transmission system (or transmission device) according to an embodiment of the present invention. 3A, a transmission system 10000 according to an embodiment of the present invention includes an Input Formatting block (or part) 11000, 11000-1, and a Bit Interleaved and Coded Modulation (BICM) block 12000, 12000-1). , Framing/Interleaving blocks 13000 and 13000-1, and Waveform Generation blocks 14000 and 14000-1.

The Input Formatting blocks (or parts) 11000 and 11000-1 generate baseband packets from an input stream for data to be serviced. Here, the input stream may be TS (Transport Stream), IP (Internet Packets) (e.g. IPv4, IPv6), MMT (MPEG Media Transport), GS (Generic Stream), GSE (Generic Stream Encapsulation), etc. have. For example, an ALP (ATSC 3.0 Link Protocol) packet may be generated based on an input stream including IP, and a baseband packet may be generated based on the generated ALP packet. BICM (Bit Interleaved and Coded Modulation) blocks (12000, 12000-1) are encoded by determining the FEC coding rate and constellation order according to the region (Fixed PHY Frame or Mobile PHY Frame) to which the data to be serviced is transmitted. And time interleaving. Meanwhile, the signaling information on the data to be serviced may be encoded through a separate BICM encoder or may be encoded by sharing the BICM encoder with the data to be serviced according to implementation.

Framing/Interleaving blocks 13000 and 13000-1 combine time-interleaved data with a signaling signal to generate a transmission frame.

The Waveform Generation blocks 14000 and 14000-1 generate OFDM signals in the time domain for the generated transmission frames, modulate the generated OFDM signals into RF signals, and transmit them to a receiver.

The transmission system 10000 according to an embodiment of the present invention shown in FIG. 3A includes normative blocks indicated by a solid line and informaive blocks indicated by a dotted line. Here, blocks indicated by solid lines are normal blocks, and blocks indicated by dotted lines are blocks that can be used when implementing informaive MIMO.

3B and 3C are diagrams for explaining a multiplexing method according to an embodiment of the present invention.

3B is a block diagram illustrating a time division multiplexing (TDM) according to an embodiment of the present invention.

In the TDM system architecture, there are four main blocks (or parts) of an Input Formatting block 11000, a BICM block 12000, a Framing/Interleaving block 13000, and a Waveform Generation block 14000.

Data is input to the Input Formatting block 1100 and formatted, and omni-directional error correction is applied in the BICM block 12000, and mapped to a constellation. Subsequently, time and frequency interleaving is performed in the Framing/Interleaving block 13000, and a frame is generated. After that, an output waveform is generated in the Waveform Generation block 14000.

3C is a block diagram for implementing Layered Division Multiplexing (LDM) according to another embodiment of the present invention.

In the LDM system architecture, there are several different blocks compared to the TDM system architecture. Specifically, there are two separate Input Formatting blocks 11000 and 11000-1 and BICM blocks 12000 and 12000-1 for one of each layer of the LDM. These are combined in the LDM injection block before the Framing/Interleaving block 13000. And Waveform Generation block 14000 is similar to TDM.

4 is a block diagram showing a detailed configuration of the Input Formatting block shown in FIG. 3A.

As shown in FIG. 4, the Input Formatting block 11000 is composed of three blocks for controlling packets distributed to PLPs. Specifically, an encapsulation and compression block 11100, a baseband formatting (or baseband framing block) 11200, and a scheduler block 11300 are included.

The input stream input to the encapsulation and compression block 11100 may be configured in various types. For example, the input stream could be TS (Transport Stream), IP (Internet Packets) (e.g. IPv4, IPv6), MMT (MPEG Media Transport), GS (Generic Stream), GSE (Generic Stream Encapsulation)). I can.

Packets output from the encapsulation and compression block 11200 become generic packets (or ALP packets, L2 packets). Here, the format of the ALP packet may be one of TLV/GSE/ALP.

The length of each ALP packet is variable. It is possible to easily extract the length of the ALP packet from the ALP packet itself without additional information. The maximum length of the ALP packet is 64kB. The maximum length of the ALP packet including the header is 4 bytes. The ALP packet is an integer byte long.

The scheduler block 11200 receives an input stream composed of encapsulated ALP packets and forms physical layer pipes (PLPs) in the shape of a baseband packet. In the above-described TDM system, there may be only one PLP called single PLP or S-PLP, or multiple PLPs called M-PLP may exist. One service cannot use more than 4 PLPs. In the case of an LDM system composed of two layers, two PLPs are used, one for each layer.

The scheduler block 11200 receives encapsulated ALP packets and designates how the packets are allocated to physical layer resources. Specifically, the scheduler block 11200 designates how the baseband formatting block 1130 outputs a baseband packet.

The function of the scheduler block 11200 is defined by data size and time. The physical layer can transmit a portion of the data at these distributed times. The scheduler block uses input and information such as encapsulated data packets, quality of service metadata for encapsulated data packets, system buffer model, constraints and configuration from system management, It creates a suitable solution in terms of the composition of physical layer parameters. The solution is subject to the available configuration and control parameters and aggregate spectrum.

Meanwhile, the operation of the scheduler block 11200 is limited to a set of dynamic, quasi-static, and static configurations. The definition of these restrictions may vary depending on the implementation.

In addition, up to 4 PLPs may be used for each service. A plurality of services composed of a plurality of type interleaving blocks can be configured with up to 64 PLPs for a bandwidth of 6, 7, or 8 MHz.

As shown in FIG. 5A, the baseband formatting block 11300 includes baseband packet construction blocks 3100, 3100-1,... 3100-n, and baseband packet header construction blocks 3200, 3200-1,... 3200. -n), consists of three blocks of baseband packet scrambling blocks (3300, 3300-1,... 3300-n). In the M-PLP operation, the baseband formatting block generates a plurality of PLPs as needed.

The baseband packet construction blocks 3100, 3100-1,... 3100-n construct a baseband packet. Each baseband packet 3500 includes a header 3500-1 and a payload 3500-2, as shown in FIG. 5B. The baseband packet is fixed to the length Kpayload. The ALP packets 3610 to 3650 are sequentially mapped to the baseband packet 3500. If the ALP packets 3610-3650 do not fit completely within the baseband packet 3500, the packets are distributed between the current baseband packet and the next baseband packet. Packet distribution is done only in bytes.

The baseband packet header construction blocks 3200, 3200-1, ... 3200-n constitute a header 3500-1. The header 3510-1 has three parts, namely, a base field (or base header) 3710, an optional field (or optional header) 3720, and an extension field (or an extension header), as shown in FIG. 5B. ) (3730). Here, the base field 3710 appears in every baseband packet, and the optional field 3720 and the extension field 3730 may not appear in every baseband packet.

The main function of the base field 3710 is to provide a pointer including an offset value in bytes as the start of the next ALP packet in the baseband packet. When the ALP packet starts the baseband packet, the pointer value becomes 0. If there is no ALP packet starting in the baseband packet, the pointer value is 8191, and a 2-byte base header may be used.

The extension field 3730 may be used later, and may be used, for example, a baseband packet packet counter, baseband packet time stamping, additional signaling, and the like.

The baseband packet scrambling blocks 3300, 3300-1,... 3300-n scramble the baseband packets.

Payload data is always scrambled before direction error correction encoding in order not to always map to the same point, such as when payload data mapped to constellations is composed of a repetitive sequence.

6 is a block diagram showing the configuration of a transmission device according to an embodiment of the present invention.

Referring to FIG. 6, the transmission device 100 includes a packet generation unit 110, a signal processing unit 120, and a transmission unit 130.

The packet generator 110 may generate a packet including a header and a payload, for example, a baseband packet (or an L1 packet) based on the input packet. Here, the packet is a header and. It includes a payload including an input packet, and the packet is defined as a fixed length K payload. The length of the packet may be set according to the selected code rate and code length. Here, the input packet may be, for example, an ALP (ATSC Link Layer Protocol) packet. These ALP packets may include one of an IP (Internet Protocal) packet, a TS packet, and a signaling packet, or a combination thereof. Specifically, input IP packets, TS packets, and various types of data are encapsulated. (encapsulating) can be generated as an ALP packet for transmission to each PLP, and this ALP packet corresponds to an L2 packet in the ISO 7 layer model. In addition, the data included in the payload is not limited to the above-described example, and may include various types of data. Hereinafter, for convenience of description, a packet generated by the packet generator 110 is referred to as a baseband packet, and an input packet is referred to as an ALP packet.

A process of generating a baseband packet will be described with reference to FIGS. 7A and 7B.

7A is a block diagram showing a detailed configuration of a packet generator according to an embodiment of the present invention.

Referring to FIG. 7A, the packet generator 110 may include a baseband packet header generator 110-1 and a baseband packet constructor 110-2. In addition, the packet generator 110 may transmit the generated baseband packet to the baseband packet scrambler 115.

In addition, the ALP packet constructor 110 ′ may generate an ALP packet for transmission to each PLP in connection with an input mode from input IP packets, TS packets, and various types of data. Here, the ALP packet corresponds to an L2 packet in the ISO 7 layer model. That is, the ALP packet constructor 110 ′ may generate an ALP packet by encapsulating a packet (IP packet, TS packet, etc.) input from an input layer 2 or higher.

Specifically, the ALP packet generator 110 ′ may generate an ALP packet (or L2 packet) including a header and ALP payload data based on the input stream. Here, the header means a header of an ALP packet, and may include information about ALP payload data included in the corresponding ALP packet and information about a packet included in the corresponding ALP packet.

The baseband packet header generator 110-1 may generate a header inserted into the baseband packet. Here, the header inserted into the baseband packet is referred to as a baseband packet header, and the baseband packet header includes information on the baseband packet.

In particular, when the input stream is a TS, the baseband packet header generator 110-1 may generate a baseband packet header including information on the number of TS packets in the ALP packet and the number of removed null packets. . In addition, the baseband packet header generated by the baseband packet header generation unit 110-1 may include various types of information, which will be described later.

In addition, the baseband packet constructor 110-2 encapsulates the baseband packet header generated by the baseband packet header generator 110-1 into the ALP packet output from the ALP packet constructor 110'. Thus, a baseband packet can be generated.

In addition, the packet generator 110 may generate a baseband packet having a size corresponding to a forward error correcting code by arranging a plurality of ALP packets including an IP packet and a header. The baseband packet according to an embodiment of the present invention may be a TS packet, but the same process may be applied not only to the TS packet but also to various types of data described above.

In addition, the baseband packet scrambler 115 may generate a scrambled baseband packet by mixing data stored in the baseband packet in a random order before the forward error correction code is added to each baseband packet. The scrambled baseband packet is transmitted through the PLP to perform signal processing. In this case, one PLP may be composed of baseband packets having a fixed size. That is, the input stream may be encapsulated as a baseband packet for one PLP.

Meanwhile, PLP refers to a signal path that is independently processed. That is, each service (e.g., video, extended video, audio, data stream, etc.) can be transmitted and received through multiple RF channels, and the PLP is a path through which these services are transmitted or a stream transmitted through the path. . In addition, the PLP may be located in slots distributed with temporal intervals on a plurality of RF channels, or may be distributed with temporal intervals on one RF channel. That is, one PLP may be distributed and transmitted on one RF channel or a plurality of RF channels at a time interval.

The PLP structure consists of Input mode A that provides one PLP and Input mode B that provides multiple PLPs. In particular, when input mode B is supported, it is possible to provide a robust specific service, as well as distributed transmission of one stream. By doing so, it is possible to obtain a time diversity gain by increasing the time interleaving length. In addition, when only a specific stream is received, power of the receiver is turned off for the rest of the time, so it can be used with low power, which is suitable for providing portable and mobile broadcasting services.

Here, time diversity means that if the transmitting side transmits the same signal several times at a certain time interval in order to reduce the deterioration of the transmission quality in the mobile communication transmission path, the receiving side synthesizes these received signals again to obtain good transmission quality. It's technology.

In addition, transmission efficiency can be improved by including information that can be commonly transmitted to a plurality of PLPs in one PLP, and PLP0 plays this role, and this PLP is referred to as a common PLP (common PLP), and PLP0 is referred to as PLP0. Other PLPs can be used for data transmission, and this PLP is called a data PLP. By using such a PLP, it is possible not only to receive HDTV programs at home, but also to provide SDTV programs while carrying and moving. In addition, it is possible to provide a variety of broadcasting services to viewers through a broadcasting station or a broadcasting content provider, as well as a differentiated service capable of receiving broadcasting even in a difficult-to-view area.

Meanwhile, FIG. 7B is a diagram illustrating an ALP packet, a baseband packet, and a scrambled baseband packet according to an embodiment of the present invention.

Referring to FIG. 7B, when the ALP packet constructor 110 ′ stores a TS packet in an ALP payload and inserts a header to generate a plurality of ALP packets 111 ′ and 112 ′, the packet generator 110 A plurality of ALP packets 111 ′ and 112 ′ may be grouped and a base band packet header may be inserted to generate a plurality of base band packets 121 and 122. Here, each of the baseband packets 121 and 122 may include a plurality of ALP packets, and may also include some of the ALP packets.

The baseband packet scrambler 115 may randomly scramble each of the generated baseband packets 121 and 122 to generate a plurality of scrambled baseband packets 125-1 and 125-2. In addition, the generated scrambled baseband packets 125-1 and 125-2 are transmitted to the PLP as described above, and signal processing for adding a forward error coding code may be performed.

Referring back to FIG. 6, the signal processing unit 120 may signal-process the generated packet. Here, the generated packet may mean a baseband packet as described above.

Specifically, the signal processing unit 120 may generate a transmission frame by signal processing the baseband packet.

In addition, the signal processing unit 120 may insert signaling information into the signaling region of the frame. Here, the signaling information may be an L1 (Layer 1) signaling signal that transmits an L1 signal for frame synchronization, and a preamble into which the L1 signaling information is inserted may include an L1 pre-signaling region and an L1 post signaling region. In addition, the L1 post signaling region includes a configurable field and a dynamic field.

Meanwhile, the L1 pre-signaling region may include information for analyzing the L1 post signaling and information on the entire system, and the L1 pre-signaling region may be implemented to always have the same length. In addition, the L1 post signaling region may include information about each PLP and information about a system, and the L1 signaling region included in each frame within one super frame has the same length, but the included content may vary.

Meanwhile, the signal processing unit 120 is not shown in the drawing, but BICM (Bit Interleaved and Coded Modulation) blocks 12000 and 12000-1 and Framing/Interleaving blocks 13000 and 13000-1 shown in FIGS. 3A to 3C It can perform a function corresponding to.

The transmitter 130 may transmit the signal-processed frame to a receiving device (not shown).

Specifically, the transmitter 130 may perform a function corresponding to the Waveform Generation blocks 14000 and 14000-1 shown in FIGS. 3A to 3C. That is, the transmitter 130 performs modulation to modulate the generated frame into an RF signal, and transmits the RF signal to a receiving device (not shown).

Meanwhile, FIG. 8 is a diagram showing the structure of a packet according to an embodiment of the present invention. Here, the packet generated by the packet generator 110 used in the present specification has already been defined to mean a baseband packet.

Referring to FIG. 8, a baseband packet is composed of a header 3100 and a payload 3200. The header 3100 may be further divided into a base field 3110, an optional field 3120, and an extension field 3130 according to its role. Here, the basic field will be defined as having the same meaning as the base field. The babe band packet header 3100 necessarily includes the base field 3110, and whether the optional field 3120 is present may vary according to a control field value of the base field 3110. In addition, presence or absence of the extended field 3130 may be selected using the control field of the optional field 3120.

Meanwhile, a basic field, an optional field, and an extended field used in this specification may be used as names of a basic header, an optional header, and an extended header.

Hereinafter, the structure of the header will be described with reference to the drawings. Here, the header may mean a header of a baseband packet.

9 is a diagram illustrating a structure of a header according to an embodiment of the present invention.

Referring to FIG. 9, the baseband packet 2300 may include a base header 2310, an optional field 2320, an extension field 2330, and a payload 2340.

Meanwhile, in the present specification, terms such as a base header, an optional field, and an extension field have been described, but it is natural that such terms may be expressed in general words such as a first header, a second field, and a third field.

Specifically, the baseband packet may be largely divided into a header and a payload. Here, the header may be composed of three parts as shown in FIG. 9. The first part is the base header 2310 and is present in all packets. In addition, the second part is an optional field 2320, and the third part is an extension field 2330. The optional field 2320 and the extension field 2330 do not always exist in all frames, and the base header 2310 includes information indicating whether the optional field 2320 and the extension field 2330 exist.

In addition, the header may include a base header 2310 including information indicating a start point of a data packet in the payload 2340 and information about the presence or absence of an additional field. That is, the base header 2310 may include information indicating the start point of the data packet in the payload 2340, and specifically, the base header 2310 is the start point of the next generic packet present in the packet 2300. It is possible to perform a function of providing a pointer including an offset value in bytes of up to. Here, the data packet start point means a distance between the start point of the payload 2340 and the start point of the data packet, and this distance may be expressed as an offset value in units of bytes described above.

As shown in FIG. 7B, the first ALP packet 111 ′ is not divided and may be included in the first packet 121, but is divided like the second ALP packet 112 ′ and In some cases, it may be included in the second packet 122.

In this case, the base header included in the header of the first packet 121 may include information indicating the starting point of the first ALP packet 111 ′, and specifically, the start of the payload of the first packet 121 It may include information including a value regarding a distance between the point and the start point of the first ALP packet 111 ′.

In addition, the base header included in the header of the second packet 122 may include information indicating the start point of the ALP packet included next to the second packet 112 ′.

For example, if the generic packet is arranged from the start point in the packet, the value of the pointer may be set to 0. In addition, since the pointer can be extended to 2 bytes, the value indicated by the pointer can be extended to 8191 bytes. In other words, the base header 2310 may represent a distance to a start point at which the generic packet starts in the packet up to 8191 bytes.

Specifically, the information indicating the start point of the data packet may include information on the presence or absence of the MSB part according to the distance between the start point of the payload and the start point of the data packet, and a first value indicating that the MSB part does not exist. And a second value indicating that the MSB part is present. That is, if the information indicating the start point of the data packet is set to 0, it indicates that the MSB part does not exist, and if the information indicating the start point of the data packet is set to 1, it indicates that the MSB part is present.

Referring to FIG. 9, the base header 2310 includes a MODE field 2311 including information indicating a start point of a data packet, and this MODE field 2311 indicates whether an MSB part of a pointer exists. Here, the MODE field 2311 may have a size of 1 bit.

When the MODE field 2311 is set to 0, the MODE field 2311 is the distance from the start point of the payload 2340 to the start point of the new generic packet from the payload 2340 is a short pointer length. Indicates that it is. Here, the short pointer length means a length not exceeding 128 bytes. Accordingly, a pointer field including information about the distance from the start point of the payload 2340 to the start point of the new generic packet from the payload 2340 is a pointer (LSB) field 2312 corresponding to the short pointer length. It includes only, and does not include the pointer (MSB) field 2313. Here, the length of the pointer (LSB) field 2312 is 7 bits.

In addition, when the MODE field 2311 is set to 0, since the pointer field includes only the pointer (LSB) field 2312, the length of the base header 2310 is 1 byte.

On the other hand, when the MODE field 2311 is set to 1, the MODE field 2311 has a long pointer length from the start point of the payload 2340 to the start point of the new generic packet from the payload 2340. length). Here, the length of the long pointer may be greater than or equal to 128 bytes. Accordingly, a pointer field including information about the distance from the start point of the payload 2340 to the start point of the new generic packet from the payload 2340 is a pointer (LSB) field 2312 to indicate the long pointer length. ), as well as a pointer (MSB) field 2313. The length of the pointer (MSB) field 2313 is 6 bits.

In addition, when the MODE field 2311 is set to 1, the base header 2310 may include an OHI field 2314 indicating information on the presence or absence of an additional field. The length of this OHI field 2314 is 2 bits.

Accordingly, when the MODE field 2311 is set to 1, the base header 2310 includes a MODE field 2311, a pointer (LSB) field 2312, a pointer (MSB) field 2313, and an OHI field 2314. Since it is included, the length of the base header 2310 is 2 bytes.

As a result, the pointer (MSB) field 2313 and the OHI field 2314 may be included in the base header 2310 only when the MODE field is set to 1.

Meanwhile, the information on the presence or absence of an additional field included in the base header 2310 includes the presence or absence of at least one of the optional field 2320 and the extension field 2330, and the length of the optional field 2320 and the extension field 2330. It may contain information to indicate.

In addition, information on the presence or absence of an additional field is a first value indicating that the optional field 2320 and the extension field 2330 do not exist, the optional field 2320 exists, the extension field 2330 does not exist, and the optional field ( A second value indicating that the length of 2320) is 1 byte, the optional field 2320 is present, the extension field 2330 is not present, and a third value indicating that the length of the optional field 2320 is 2 bytes, and optional field 2320 And an extension field 2330 exists and may include one of a fourth value indicating that the length of the optional field 2320 and the extension field 2330 exceeds 2 bytes.

In addition, the optional field 2320 may include information indicating the length of the extension field 2330 when information on the presence or absence of an additional field is set to a fourth value, and among the LSB part and the MSB part according to the length of the extension field. It may include at least one.

Information about the presence or absence of such an additional field may be stored in an optional header indicator (OHI) field 2314. Specifically, the length of the OHI field 2314 is 2 bits, and the length of the optional field 2320 may be equal to or less than 2 bytes. Information indicated by a value stored in the OHI field 2314 may be organized as shown in Table 1 below.

OHI field Contents 00 Optional field and Extension field are absent. 01 Optional field exists, extension field does not exist, and optional field is 1 byte long. 10 The optional field is present, the extension field is not, and the length of the optional field is 2 bytes. 11 There is an optional field and an extension field, and the length of the optional field and extension field exceeds 2 bytes. The length of the optional field is 1 byte or 2 bytes, and the actual length of the extension field is indicated in the EXT_LEN field of the optional field.

Specifically, how the optional field 2320 and the extension field 2330 are included in the header according to the value set in the OHI field 2314 will be described with reference to FIG. 10. It is a diagram showing the detailed configuration of the optional field according to.

Referring to FIG. 10, when the OHI field 2314 is set to 00, the header does not include an optional field 2320 and an external field 2330.

In addition, when the OHI field 2314 is set to 01, the header includes an optional field 2320 having a length of 1 byte. Here, the optional field 2320 may include information indicating whether at least one of the optional field 2320 and the extension field 2330 includes padding. Specifically, the optional field 2320 may include an EXT_TYPE field 2321 indicating whether at least one of the optional field 2320 and the extension field 2330 includes padding. Here, the length of the EXT_TYPE field 2321 is 3 bits. In addition, among 1 byte of the optional field 2320, the remaining area 2322 of 5 bits excluding the EXT_TYPE field 2321 may include preset information or padding. The remaining area 2322 may include preset information or padding according to information stored in the EXT_TYPE field 2321. Here, padding means meaningless data, and such meaningless data may be randomly determined in various ways according to system design. In addition, this padding does not necessarily need to be filled with zeros, it may be filled with only ones, or it may be filled with an insignificant combination of zeros and ones. However, a case where padding according to an embodiment of the present invention is filled with only 0 will be described as an example.

In addition, when the OHI field 2314 is set to 10, the header includes an optional field 2320 having a length of 2 bytes. Similarly, the optional field 2320 may include information indicating whether at least one of the optional field 2320 and the extension field 2330 includes padding. Specifically, the optional field 2320 may include an EXT_TYPE field 2321 indicating whether at least one of the optional field 2320 and the extension field 2330 includes padding, where, the EXT_TYPE field ( 2321) is 3 bits long. In addition, the remaining 5-bit area 2322 and 8-bit area 2323 of 2 bytes of the optional field 2320 excluding the EXT_TYPE field 2321 may include preset information or padding. The remaining 5-bit area 2322 and 8-bit area 2323 may include preset information or padding according to information stored in the EXT_TYPE field 2321. Here, padding means meaningless data, and such meaningless data may be randomly determined in various ways according to system design.

Meanwhile, when the OHI field 2314 is set to 11, the header may include not only the optional field 2320 but also the extension field 2320. Here, the total length of the optional field 2320 and the extension field 2320 exceeds 2 bytes, and the length of the optional field 2320 may be 1 byte or 2 bytes. In addition, the optional field 2320 may include information indicating whether at least one of the optional field 2320 and the extension field 2330 includes padding. Specifically, the optional field 2320 may include an EXT_TYPE field 2321 indicating whether at least one of the optional field 2320 and the extension field 2330 includes padding, where, the EXT_TYPE field ( 2321) is 3 bits long.

However, when the OHI field 2314 is set to 11, the EXT_TYPE field 2321 is set to a value corresponding to the type of the extension field 2330. For example, when padding is stored in the extension field 2330, EXT_TYPE In the field 2321, a value indicating that padding is stored in the extension field 2330 is stored. And, when the OHI field 2314 is set to 11, the optional field 2320 includes information indicating the length of the Etension field 2330, and includes at least one of an LSB part and an MSB part according to the length of the Extenson field. In this regard, the optional field 2320 may include at least one of an EXT_LEN (LSB) field 2324 and an EXT_LEN field 2325 indicating the length of the Extension field 2330. Here, the length of the EXT_LEN(LSB) field 2324 may be 5 bits, and the length of the EXT_LEN(MAB) field 2325 may be 8 bits.

Meanwhile, in summary, the EXT_TYPE field 2321 described above is a 3-bit field indicating the type of the extension field, the OHI field 2314 is set to 01, and the EXT_TYPE field 2321 is set to 000. If set, a bit sequence of "00000" may be stored in the optional field 2320. In addition, when the OHI field 2314 is set to 10 and the EXT_TYPE field 2321 is set to 000, a bit sequence of "00000000" in addition to the bit sequence of "00000" may be additionally stored in the optional field 2320. In addition, when the OHI field 2314 is set to 11, the EXT_TYPE 2321 is filled with a value corresponding to the type of the Extension field 2330, and at least one of the EXT_LEN (LSB) field 2324 and the EXT_LEN (MSB) field Can be connected and placed. Here, when the EXT_TYPE field 2321 is set to 000, it has been described that padding (ie, a bit sequence of 00000 or a bit sequence of 00000000) is filled in the optional field 2320, but this is only an example, and the EXT_TYPE field 2321 It is natural that the meaning of the value set in) may vary depending on the design method.

Meanwhile, the EXT_LEN (LSB) field 2324 indicates the length of the Extension field 2330 and includes 5 LSB bits of the EXT_LEN field. This EXT_LEN (LSB) field 2324 is always present when the OHI field 2314 is set to 11.

In addition, the EXT_LEN (MSB) field 2325 includes 8 LSB bits of the EXT_LEN field, and when the EXT_LEN (MSB) field 2325 is present, the optional field 2320 includes the EXT_LEN (LSB) field 2324 and A 13-bit EXT_LEN field to which the EXT_LEN (MSB) field 2325 is connected is included. Accordingly, when the length of the extension field 2330 is less than a preset length, the optional field 2320 may include only the EXT_LEN (LSB) field 2324, and the length of the extension field 2330 exceeds the preset length. In this case, the optional field 2320 may include both an EXT_LEN (LSB) field 2324 and an EXT_LEN (MSB) field 2325.

Meanwhile, how the structure of the packet 2300 changes as a whole according to values set in the MODE field 2311 and the OHI field 2314 will be described with reference to FIGS. 11 to 16D.

11 to 16D are diagrams illustrating a structure of a packet according to various embodiments of the present disclosure.

Referring to FIG. 11, when the MODE field 2311 is set to 0, it means the short pointer length, so the base header 2310 includes only the pointer (LSB) field 2312, and the MODE field 1211 is set to 0. In this case, since the Optional field 2320 and the Extension field 2330 are not included in the packet 2300, as a result, the packet 2300 includes a base header 2310 and a payload 2340 having a length of 1 byte. It is done.

Referring to FIG. 12, when the MODE field 2311 is set to 1, it means a long pointer length, so the base header 2310 includes a pointer (LSB) field 2312 and a pointer (MSB) field 2313, An OHI field 2314 including information about the presence or absence of the optional field 2320 and the extension field 2330 may be additionally included.

Accordingly, the packet 2300 includes a base header 2340 having a length of 2 bytes. However, in FIG. 12, since the OHI field 2314 is set to 00, the optional field 2320 and the extension field 2330 are not included in the packet 2300, as a result, the packet 2300 has a length of 2 bytes. A base header 2310 and a payload 2340 are included.

Referring to FIG. 13, when the MODE field 2311 is set to 1, it means a long pointer length, so the base header 2310 includes a pointer (LSB) field 2312 and a pointer (MSB) field 2313, An OHI field 2314 including information about the presence or absence of the optional field 2320 and the extension field 2330 may be additionally included.

Accordingly, the packet 2300 includes a base header 2340 having a length of 2 bytes. However, in FIG. 13, the OHI field 2314 is set to 01, so that an optional field 2320 having a length of 1 byte is included in the packet 2300, and the extension field 2330 is not included in the packet 2300. Will not be. As a result, the packet 2300 includes a base header 2310 having a length of 2 bytes, an optional field 2320 having a length of 1 byte, and a payload 2340. In addition, the optional field 2320 may include an EXT_TYPE field 2321 and a 5-bit padding field 2322.

Referring to FIG. 14, when the MODE field 2311 is set to 1, it means a long pointer length, so the base header 2310 includes a pointer (LSB) field 2312 and a pointer (MSB) field 2313, An OHI field 2314 including information about the presence or absence of the optional field 2320 and the extension field 2330 may be additionally included.

Accordingly, the packet 2300 includes a base header 2340 having a length of 2 bytes. However, in FIG. 14, the OHI field 2314 is set to 10, and an optional field 2320 having a length of 2 bytes is included in the packet 2300, and the extension field 2330 is not included in the packet 2300. Will not be. As a result, the packet 2300 includes a base header 2310 having a length of 2 bytes, an optional field 2320 having a length of 2 bytes, and a payload 2340. In addition, the optional field 2320 may include an EXT_TYPE field 2321, a 5-bit padding field 2322, and an 8-bit padding field 2323.

Meanwhile, referring to FIG. 15, when the MODE field 2311 is set to 1, it means a long pointer length, so the base header 2310 includes a pointer (LSB) field 2312 and a pointer (MSB) field 2313. In addition, an OHI field 2314 including information on the presence or absence of the optional field 2320 and the extension field 2330 may be additionally included.

Accordingly, the packet 2300 includes a base header 2340 having a length of 2 bytes. However, in FIG. 15, the OHI field 2314 is set to 11, and the base header 2310 having a length of 2 bytes, an optional field 2320 having a length of 2 bytes, an extension field 2330, and a payload ( 2340). In addition, the optional field 2320 may include an EXT_TYPE field 2321, an EXT_LEN (LSB) field 2324 and an EXT_LEN (MSB) field 2325.

Meanwhile, FIG. 15 illustrates a case where the optional field 2320 includes both an EXT_LEN (LSB) field 2324 and an EXT_LEN (MSB) field 2325, but the optional field 2320 is an EXT_LEN (LSB) field ( 2324), and in this case, the packet 2300 includes a base header 2310 having a length of 2 bytes, an optional field 2320 having a length of 1 byte, an extension field 2330, and a payload 2340. ) Can be included.

In addition, in the above-described example, a case where the optional field 2320 has at least one of a 5-bit padding field 2322 and an 8-bit padding field 2323 has been described as an example, but may include preset data other than padding. In addition, the EXT_TYPE field 2321 may include a value representing preset data.

Meanwhile, in FIGS. 16A to 16D, when the OHI field 2314 is set to 11, data to be filled in the optional field 2320 and the extension field 2330 may vary according to a value set in the EXT_TYPE field 2321. Is shown.

Referring to FIG. 16A, when the OHI field 2314 is set to 11, the Optional field 2320 includes a TYPE field 2321, EXT_LEN(LSB) 2324 and EXT_LEN(MSB) 2325, and Extension A representative example in which field 2330 is present is shown.

Here, when the TYPE field 2321 is set to 001, the optional field 2320 includes only the EXT_LEN (LSB) field 2324, and the extension field 2330 includes the ISSY field 2331 and padding 2332. I can. Here, the ISSY field 2331 is taken as an example to describe a case where the extension field 2330 includes preset data. The ISSY field (Input Stream Synchronization) 2331 is used to transmit a clock counter value according to a clock modulation ratio and to regenerate an accurate timing for restoring an output stream by a receiver.

In addition, referring to FIG. 16B, when the TYPE field 2321 is set to 010, the Optional field 2320 includes an EXT_LEN (LSB) field 2324 and an EXT_LEN (MSB) field 2325, and an Extension field 2330 ) May include an ISSY field 2333 and padding 2332.

Of course, the extension field 2330 is preset data and may include various data other than the ISSY field 2333. Referring to FIG. 16C, when the TYPE field 2321 is set to 011, the Optional field 2320 includes an EXT_LEN (LSB) field 2324 and an EXT_LEN (MSB) field 2325, and the Extension field 2330 is In-band Signal TYPE A field 2334 and padding 2332 may be included. Referring to FIG. 16D, when the TYPE field 2321 is set to 100, the optional field 2320 is an EXT_LEN (LSB) field ( 2324) and an EXT_LEN (MSB) field 2325 may be included, and the extension field 2330 may include an in-band Signal TYPE B field 2335 and padding 2332.

Meanwhile, the above-described ALP packet and baseband packet may have different names depending on the system. For example, the above-described ALP packet and baseband packet may be referred to as a baseband packet and a baseband frame, respectively, depending on the system.

Meanwhile, according to another embodiment of the present invention, the optional field and the extension field may include fields of different structures, which will be described in detail with reference to FIGS. 17 to 25. In addition, the description of the optional field and the extension field including fields of different structures, the description of the field included in the base field to be described later may correspond to the part described in FIG. 9, but will be described again using general terms. It should be.

Referring back to FIG. 6, the transmission device 100 includes a packet generation unit 110, a signal processing unit 120, and a transmission unit 130, and the packet generation unit 110 includes a header and a page based on the input packet. You can create a packet containing the load.

Here, the input packet may be an ALP packet (or L2 packet), and the packet generated by the packet generator 110 may be a baseband packet (BBP) (or L1 packet). Of course, as described above, the names may vary depending on the system. For example, the above-described ALP packet and BBP packet may be referred to as a BBP packet and a baseband frame (BBF), respectively, depending on the system.

Meanwhile, a packet, that is, a baseband packet, may include a header and a payload including an input packet, and the packet is defined as a fixed length K payload. The length of the packet may be set according to the selected code rate and code length.

And, the input packet, that is, the ALP packet, may include one of an Internet Protocol (IP) packet, a TS packet, and a signaling packet, or a combination thereof, and specifically, an input IP packet, a TS packet, and various types of Data may be encapsulated and generated as ALP packets for transmission to each PLP, and these ALP packets correspond to L2 packets in the ISO 7 layer model. In addition, the data included in the payload is not limited to the above-described example, and may include various types of data.

In addition, the signal processing unit 120 may signal-process the generated packet. Specifically, the signal processing unit 120 may generate a transmission frame by signal processing the packet. In addition, the signal processing unit 120 may insert signaling information into the signaling region of the frame. Here, the signaling information may be an L1 (Layer 1) signaling signal that transmits an L1 signal for frame synchronization, and a preamble into which the L1 signaling information is inserted may include an L1 pre-signaling region and an L1 post signaling region. In addition, the L1 post signaling region includes a configurable field and a dynamic field.

Meanwhile, the signal processing unit 120 is not shown in the drawing, but BICM (Bit Interleaved and Coded Modulation) blocks 12000 and 12000-1 and Framing/Interleaving blocks 13000 and 13000-1 shown in FIGS. 3A to 3C It can perform a function corresponding to.

The transmitter 130 may transmit the signal-processed packet to a receiving device (not shown).

Specifically, the transmitter 130 may perform a function corresponding to the Waveform Generation blocks 14000 and 14000-1 shown in FIGS. 3A to 3C. That is, the transmitter 130 performs modulation to modulate the generated packet into an RF signal, and transmits the RF signal to a receiving device (not shown).

Meanwhile, the base field constituting the header includes a first field set to a first value indicating that the base field is a first length or a second value indicating that the base field is a second length, and the first field is a second value. When set to, the base field represents a second field representing the least significant bits (LSB) of a pointer value representing the first value of each starting point of the input packet included in the payload, and the MSB (most significant bits) of the pointer value. May include a third field.

In addition, the header 4100 of the packet 4000 can be divided into a base field, an optional field, and an extension field according to its role, as shown in FIG. 8, and the header 4100 must include a base field and an optional field. Whether or not is may vary according to the value of the control field included in the base field. Also, it is possible to select the existence or nonexistence of the extension field according to the value of the control field included in the optional field.

Here, the first field, the second field, and the third field may be included in the base field constituting the header.

Specifically, it will be described in detail with reference to FIG. 17.

17 is a diagram illustrating a structure of a packet according to another embodiment of the present invention.

Referring to FIG. 17, a packet 4000 may include a header 4100 and a payload 4200, and a plurality of input packets 4201 may be mapped to the payload 4200 of the packet 4000. .

Here, like the first input packet among the plurality of input packets 4201, one input packet may be split and included in payloads of different packets. In addition, the base field may inform the starting point of the input packet through the pointer value. Here, the pointer value means an offset from the start point of the payload to the first start point of each start point of the input packet included in the payload.

Specifically, the first field 4111 included in the base field of the header 4100 is a first value indicating that the base field is a first length, that is, 1 byte, or a second field indicating that the base field is a second length, that is, 2 bytes. Can be set to a value.

In particular, when the first field 4111 is set to a first value and the base field is 1 byte, the base field is the LSB of a pointer value indicating the first value of each starting point of the input packet included in the payload 4200. Significant bits) may be included, and accordingly, the pointer value may indicate only up to a preset value.

In addition, when the first field 4111 is set to a second value and the base field is 2 bytes, the base field is LSB (least significant bits) of a pointer value indicating the first value of each start point of the input packet included in the payload. A second field indicating, and a third field indicating the most significant bits (MSBs) of the pointer value may be included, and accordingly, the pointer value may also indicate a preset value or more.

Here, the preset value may be 128 bytes. Accordingly, when the first field 4111 is set to the first value, the pointer value may be less than 128 bytes, and the first field 4111 is the first field. When set to a value of 2, the pointer value can represent up to 128 bytes or more.

For example, if any one input packet is arranged to match the start point of the payload 4200 of the packet 4000 and the start point of the corresponding input packet is the same as the start point of the payload, The pointer value indicating the value can be 0. That is, since the starting point of the input packet can be numerically calculated and calculated based on the starting point of the payload 4200, a pointer indicating a value corresponding to the starting point of the corresponding input packet starting the same as the starting point of the payload 4200 The value can be 0.

In addition, as shown in FIG. 17, when the first input packet is split like the first input packet among the plurality of input packets and is included in the payload 4200, the starting point of the first input packet exists in the previous packet and the corresponding payload Since it does not exist at 4200, the first value of each start point of the input packet included in the payload 4200 becomes the start point of the second input packet. Accordingly, a pointer value indicating a value corresponding to the start point of the second input packet may be a value corresponding to the distance 4202 from the start point of the payload 4200 to the start point of the second input packet. .

In addition, when the first field 4111 is set to the first value, the base field of the header 4100 includes only the second field 4112 indicating the LSB of the pointer value, and if the first field is set to the second value, the header The base field of 4100 may include a second field 4112 indicating the LSB of the pointer value and a third field 4113 indicating the MSB of the pointer value.

Here, the first field 4111 may be a MODE field, and this MODE field may have a size of 1 bit. In addition, when the MODE field is set to 0, the length of the base field is 1 byte, and when set to 1, the length of the base field is 2 bytes.

In addition, the MODE field may indicate the presence or absence of the third field 4113 indicating the MSB of the pointer value and the presence or absence of the fourth field indicating the extension mode of the header. Specifically, when the MODE field is set to 0, the base field is a pointer. This indicates that only the second field 4112 indicating the LSB of the value is included. Here, the second field 4112 may be a pointer (LSB) field indicating the LSB of the pointer value, and such a pointer (LSB) field may have a size of 7 bits. Accordingly, when the MODE field is set to 0, the pointer value is bound to be less than 128 bytes, and the base field has a size of 1 byte including the MODE field (1 bit) and the pointer (LSB) field (7 bits). .

In addition, when the MODE field is set to 1, the base field may include a second field 4112 indicating the LSB of the pointer value and a third field 4113 indicating the MSB of the pointer value. Here, the third field 4113 indicating the MSB of the pointer value may be a pointer MSB field, and the pointer MSB field may have a size of 6 bits. Accordingly, when the MODE field is set to 1, the pointer value can be expressed by extending up to 8191 bytes through a total of 13 bits in which the pointer (LSB) field (7 bits) and the pointer (MSB) field (6 bits) are combined. The field includes a MODE field (1 bit), a pointer (LSB) field (7 bits), a pointer (MSB) field (6 bits), and a fourth field (2 bits) indicating an extension mode of the header 4100 to be described later. It has a size of 2 bytes. As a result, the pointer (MSB) field and the fourth field indicating the extended mode of the header 4100 may be included in the base field only when the MODE field is set to 1.

Accordingly, if the pointer value representing the first value of the starting point of the input packet in the payload 4200 of the packet 4000 is less than 128 bytes, the first field 4111, that is, the MODE field is set to 0, and the base field is The second field 4112, that is, only the pointer (LSB) field, is included so that the base field has a size of 1 byte, and a pointer value indicating the first value of the start points of the input packet in the payload 4200 of the packet 4000 If this is 128 bytes or more, the first field 4111, that is, the MODE field is set to 1, and the base field is the second field 4112, that is, a pointer (LSB) field and a third field 4113, that is, a pointer (MSB). Since the field and the fourth field are included, the base field has a total size of 2 bytes.

And, if the start point of the input packet does not exist in the payload 4200 of the packet 4000, a value corresponding to the start point of the corresponding input packet cannot be defined, so the pointer value is 8191, and accordingly, the MODE field is 1 It is set to and the base field has a size of 2 bytes.

In addition, even if there is no input packet in the payload 4200 of the packet 4000 and only padding exists, the pointer value is 8191, and accordingly, the MODE field is set to 1, and the base field is 2 bytes in size. Will have.

Meanwhile, FIG. 18 is a diagram showing a detailed configuration of the header shown in FIG. 17. Referring to FIG. 18, as described above, the header 4100 includes a base field 4110, and may further include an optional field 4120 and an extension field 4130, which will be described later ( Whether to include or not may be determined by the fourth field 4114 indicating the extended mode of 4100.

And, as described above, when the first field 4111 is set to the first value, the base field 4110 includes only the second field 4112, and accordingly, the length of the base field 4110 is the first field. It can be seen that it has a total size of 1 byte including 1 bit of (4111) and 7 bits of the second field (4112).

In addition, as described above, when the first field 4111 is set to a second value, the base field 4110 is a second field indicating the extension mode of the second field 4112, the third field 4113, and the header 4110. Including 4 fields 4114, and accordingly, the length of the base field 4110 is 1 bit of the first field 4111, 7 bits of the second field 4112, 6 bits of the third field 4113, and It can be seen that the fourth field 4114 has a total size of 2 bytes including 2 bits.

Meanwhile, the base field 4110 may include a fourth field 4114 indicating an extension mode of the header 4110 when the first field 4111 is set to a second value, and the fourth field 4114 is optional. It may include at least one of information on the presence or absence of the field 4120 and the extension field 4130, the length of the optional field 4120, and the structure of the extension field 4130.

Specifically, the fourth field 4114 is a third value indicating that the optional field 4120 and the extension field 4130 do not exist, indicating that the optional field 4120 is present and the length of the optional field 4120 is 1 byte. A fourth value, a fifth value indicating that the optional field 4120 is present and the length of the optional field 4120 is 2 bytes, and the optional field 4120 are present, the length of the optional field 4120 is 2 bytes, and the extension field ( 4130) may be set to one of sixth values indicating that the structure includes a plurality of extension payloads.

Here, the fourth field 4114 may be an OFI field, and the OFI field has a size of 2 bits. Specifically, information indicated by a value set in the OFI field may be arranged as shown in Table 2 below.

OFI Contents 00 No Extension Mode:
Optional field and Extension field are absent. 01 Short Extension Mode:
The optional field is present and the length of the optional field is 1 byte. 10 Long Extension Mode:
The optional field is present and the length of the optional field is 2 bytes. 11 Mixed Extension Mode:
There is an optional field, the length of the optional field is 2 bytes, and the extension field includes a plurality of extension payloads.

Specifically, how the optional field 4130 and the extension field 4130 are included in the header 4100 according to the value set in the fourth field 4114 will be described with reference to FIG. 19. FIG. 19 is a diagram of the present invention. A diagram showing a detailed configuration of an optional field according to another embodiment.

Referring to FIG. 19, when the fourth field 4114 is set to "00", which is the third value, the header 4100 includes only the base field 4110, and the optional field 4120 and extension Field 4130 is not included.

In addition, when the fourth field 4114 is set to the fourth value “01”, this is a short extension mode, and the header 4100 further includes an optional field 4120 having a size of 1 byte in addition to the base field 4110 can do. In addition, the existence and length of the extension field 4130 may be determined by a field included in the optional field 4120.

Specifically, the optional field 4120 is a field indicating the type of the extension payload 4131 included in the extension field 4130 (EXT_TYPE field) 4121 and a field indicating the length of the extension field 4130 (EXT_LEN field) (4122) may be included. Here, the EXT_TYPE field 4121 will be defined as a fifth field, and the EXT_LEN field 4122 will be defined as a sixth field.

Here, the EXT_TYPE field 4121 has a size of 3 bits, and indicates the type of the extension payload 4131 included in the extension field 4130, and a detailed description thereof will be described later. In addition, the EXT_LEN field 4122 has a size of 5 bits and may indicate the length of the Extension field 4130 within a range of 0 to 31 bytes.

In particular, when the EXT_LEN field 4122 is 0, it means that the length of the extension field 4130 is 0, and thus the extension field 4130 does not exist in the header 4100.

Meanwhile, in FIG. 19, when the fourth field 4114 is set to the fourth value “01”, the EXT_LEN field 4122 included in the optional field 4120 and the extension payload 4131 included in the extension field 4130 Is shown as being separated, but this is only displayed separately to explain that the optional field 4120 has a size of 1 byte and sometimes has a size of 2 bytes. When the field 4114 is set to the fourth value of "01", the optional field 4120 has a size of 1 byte, so an extension field 4130 is added consecutively to the optional field 4120, and accordingly, the optional field 4120 The EXT_LEN field 4122 included in) and the extension payload 4131 included in the extension field 4130 are arranged in succession.

In addition, when the fourth field 4114 is set to the fifth value “10”, this is a Long Extension Mode, and the header 4100 further includes an optional field 4120 having a size of 2 bytes in addition to the base field 4110 can do. In addition, the existence and length of the extension field 4130 may be determined by a field included in the optional field 4120.

Specifically, the optional field 4120 is a field indicating the type of the extension payload 4132 included in the extension field 4130 (EXT_TYPE field) 4121, and the LSB part of the field indicating the length of the extension field 4130. A field indicating a field (EXT_LEN (LSB) field) 4123 and a field indicating an MSB part of a field indicating the length of the extension field 4130 (EXT_LEN (MSB) field) 4124 may be included. Here, as described above, since the EXT_TYPE field 4121 is defined as a fifth field, and the field indicating the length of the Extension field 4130 is defined as a sixth field, the EXT_LEN (LSB) field 4123 is a sixth field. May be defined as indicating the LSB part of, and the EXT_LEN(MSB) field 4124 may be defined as indicating the MSB part of the sixth field.

Here, the EXT_TYPE field 4121 has a size of 3 bits, and indicates the type of the extension payload 4132 included in the extension field 4130, and a detailed description thereof will be described later.

In addition, the EXT_LEN (LSB) field 4123 may have a size of 5 bits of the LSB part among a total of 13 bits for indicating the length of the extension field 4130, and the EXT_LEN (MSB) field 4124 is an Extension field ( 4130) may have a size of 8 bits of the MSB part out of a total of 13 bits for indicating the length. In addition, a 13-bit field that connects the EXT_LEN (LSB) field 4123 and the EXT_LEN (MSB) field 4124 may indicate the length of the extension field 4130 within the entire length range of the packet 4000 from 0. have.

Of course, if a field of 13 bits in which the EXT_LEN (LSB) field 4123 and the EXT_LEN (MSB) field 4124 are connected is 0, it means that the length of the extension field 4130 is 0. The field 4130 does not exist.

In addition, when the fourth field 4114 is set to the sixth value “11”, this is a mixed extension mode, and the header 4100 further includes an Optonal field 4120 having a size of 2 bytes in addition to the base field 4110 can do. Further, the existence and length of the extension field 4130 and the structure of the extension field 4130 may be determined by fields included in the optional 4120.

Specifically, the optional field 4120 is a field indicating the number of a plurality of extension payloads 4133 included in the extension field 4130 (NUM_EXT field) 4125, the LSB of a field indicating the length of the extension field 4130 A field indicating a part (EXT_LEN (LSB) field) 4126 and a field indicating an MSB part of a field indicating the length of the extension field 4130 (EXT_LEN(MSB) field) 4127 may be included.

Here, the NUM_EXT field 4125 has a size of 3 bits and may indicate the number of a plurality of extension payloads 4133 instead of padding included in the extension field 4130.

In particular, the extension field 4130 may include 2 to 7 extension payloads, and a detailed structure thereof will be described with reference to FIG. 25.

In addition, the EXT_LEN (LSB) field 4126 may have a size of 5 bits of the LSB part out of a total of 13 bits for indicating the length of the extension field 4130, and the EXT_LEN (MSB) field 4127 is an Extension field ( 4130) may have a size of 8 bits of the MSB part out of a total of 13 bits for indicating the length.

On the other hand, regarding the length of the extension field 4130 that can be represented by a field of 13 bits in which the EXT_LEN (LSB) field 4126 and the EXT_LEN (MSB) field 4127 are connected, the structure of the extension field 4130 We will explain together while explaining.

25 is a diagram illustrating a structure of an extension field according to an embodiment of the present invention.

When the fourth field 4114 is set to a sixth value, the extension field 4130 includes a plurality of fields indicating the types of each of the plurality of extension payloads and a plurality of fields indicating the length of each of the plurality of extension payloads. can do.

Specifically, referring to FIG. 25, when the fourth field 4114 is set to a sixth value, that is, “11”, this means a mixed extension mode, and accordingly, the extension field 4130 is a plurality of extension payloads. (Extension payload 1(4145)...Extension payload N(4146)), where the Extension field 4130 is a plurality of extension payloads (Extension payload 1(4145)...Extension payload). Load N (4146)) Multiple fields representing each type (EXT_TYPE 1 (4141)...EXT_TYPE N (4143)) and multiple extension payloads (Extension payload 1 (4145)... Extension payload N (4146)) A plurality of fields indicating respective lengths (EXT_LEN 1 field 4142 ... EXT_LEN N field 4144) may be included. Here, as described above, since the extension field 4130 may include 2 to 7 extension payloads, N may range from 2 to 7.

All of the plurality of extension payloads (Extension payload 1 (4145) ... Extension payload N (4146)) do not include padding.

In addition, when one extension payload is included in the extension field 4130, one EXT_TYPE field indicating the type of the corresponding extension payload and one EXT_LEN field are included in the extension field 4130, where the EXT_TYPE field is Considering that it has a size of 3 bits and the EXT_LEN field has a size of 13 bits, a header having a total size of 2 bytes is included in the extension field 4130 for one extension payload. Here, the header includes an EXT_TYPE field and an EXT_LEN field, and fields disposed at the front end of the extension field 4130 are collectively defined.

Accordingly, when N extension payloads are included in the extension field 4130, the extension field 4130 includes a header having a total size of 2N bytes including a plurality of EXT_TYPE fields and EXT_LEN fields related to each extension payload. It is done.

Meanwhile, as described above, the extension field 4130 may include at least two extension payloads, and thus may include a header having a size of 4 bytes. However, when the value of the EXT_LEN field is 0, it can be considered that there is no extension payload, and in this case, the length of the extension field 4130 is bound to be at least 4 bytes.

As a result, the length of the extension field 4130 that can be represented by a 13-bit field connecting the EXT_LEN (LSB) field 4126 and the EXT_LEN (MSB) field 4127 described in FIG. 19 is 4 bytes to a packet 4000 It may indicate the length of the Extension field 4130 within the entire length range of

Meanwhile, each of the EXT_LEN 1 field 4142 ... EXT_LEN N field 4144 shown in FIG. 25 may include a 5-bit EXT_LEN (LSB) field and an 8-bit EXT_LEN (MSB) field. Accordingly, a header having a size of 2 bytes for one extension payload is an EXT_TYPE field having a size of 3 bits, an EXT_LEN (LSB) field having a size of 5 bits, and an EXT_LEN (MSB) field having a size of 8 bits. Will include.

In addition, when the extension field 4130 is set to one of a fourth value and a fifth value, and the length of the extension payload included in the extension field 4130 is less than the length of the extension field 4130 , Extension payload may be included in the Extension field 4130 and padding may be included in the remaining part.

For example, in FIG. 19, when the fourth field 4114 is set to the fourth value “01”, the actual length of the extension payload 4131 included in the extension field 4130 is defined by the EXT_LEN field 4122. If the length is less than the length of the extension field 4130, the extension field 4130 may include the extension payload 4131 and padding in the remaining portion. Here, padding means meaningless data, and such meaningless data may be randomly determined in various ways according to system design. In addition, this padding does not necessarily need to be filled with zeros, it may be filled with only ones, or it may be filled with an insignificant combination of zeros and ones. However, a case where padding according to an embodiment of the present invention is filled with only 0 will be described as an example.

In addition, for example, when the fourth field 4114 in FIG. 19 is set to the fifth value “10”, the actual length of the extension payload 4132 included in the extension field 4130 is the EXT_LEN (LSB) field 4123 ) And the length of the Extension field 4130 defined by the EXT_LEN (MSB) field 4124, the Extension field 4130 includes the Extension Payload 4132 and padding in the remaining part. can do.

Meanwhile, when the fourth field 4114 is set to a sixth value, the extension field 4130 may include a plurality of extension payloads in the extension field 4130 and padding in the remaining portions.

For example, referring to FIG. 25, when the fourth field 4114 is set to the sixth value “11”, a plurality of extension payloads included in the extension field 4130 (Extension payload 1 4145)... Extension payload N(4146)) Multiple fields representing each type (EXT_TYPE 1(4141)...EXT_TYPE N(4143)), multiple extension payloads (Extension payload 1(4145)...Extension payload) Load N (4146)) A plurality of fields indicating the length of each (EXT_LEN 1 field (4142)... EXT_LEN N field (4144)) and a plurality of payloads (Extension payload 1 (4145)... Extension payload) If the total actual length of N (4146)) is less than the length of the extension field 4130 defined by the EXT_LEN (LSB) field 4126 and the EXT_LEN (MSB) field 4127, the extension field 4130 is A plurality of fields indicating each type of extension payload (EXT_TYPE 1(4141)...EXT_TYPE N(4143)), a plurality of fields indicating the length of each of a plurality of extension payloads (EXT_LEN 1 field 4142)... The EXT_LEN N field 4144) and a plurality of payloads (Extension payload 1 (4145)...Extension payload N (4146)) may be included, and padding may be included in the remaining portions.

Meanwhile, how the structure of the packet 4000 changes as a whole according to values set in the first field 4111 and the fourth field 4114 will be described with reference to FIGS. 20 to 24.

20 to 24 are diagrams showing the structure of a packet according to various embodiments of the present invention.

Referring to FIG. 20, when the first field 4111 is set to a first value, the base field 4110 includes only the second field 4112 indicating the least significant bits (LSBs) of the pointer value, and the optional field 4120 ) And the Extension field 4130 are not included in the packet 4000, as a result, the packet 4000 includes a base field 4110 and a payload 4200 having a size of 1 byte.

Referring to FIG. 21, when the first field 4111 is set to a second value, the base field 4110 is a second field 4112 indicating the least significant bits (LSB) of the pointer value, and the most significant bits (MSB) of the pointer value. bits), and a fourth field 4114 indicating an extension mode of the header 4100 may be additionally included.

Accordingly, the packet 4000 includes a base field 4110 having a length of 2 bytes. However, in FIG. 21, since the fourth field 4114 is set to a third value, that is, "00", the optional field 4120 and the extension field 4130 are not included in the packet 4000, as a result, The packet 4000 includes a base field 4110 and a payload 4200 having a size of 2 bytes.

Referring to FIG. 22, when a first field 4111 is set to a second value, a base field 4110 is a second field 4112 indicating the least significant bits (LSB) of a pointer value, and the most significant bits (MSB) of the pointer value. bits), and a fourth field 4114 indicating an extension mode of the header 4100 may be additionally included.

Accordingly, the packet 4000 includes a base field 4110 having a size of 2 bytes. However, in FIG. 22, since the fourth field 4114 is set to a fourth value, that is, "01", an optional field 4120 having a size of 1 byte and an extension field 4130 having a size of 0 to 31 bytes. ) Is included in the packet 4000. As a result, the packet 4000 includes a base field 4110 having a size of 2 bytes, an optional field 4120 having a size of 1 byte, an extension field 4130 having a size of 0 to 31 bytes, and a payload. (4200) will be included. In addition, the optional field 4120 may include an EXT_TYPE field 4121 and an EXT_LEN field 4122.

Referring to FIG. 23, when the first field 4111 is set to a second value, the base field 4110 is a second field 4112 indicating the least significant bits (LSBs) of the pointer value, and the most significant bits (MSB) of the pointer value. bits), and a fourth field 4114 indicating an extension mode of the header 4100 may be additionally included.

Accordingly, the packet 4000 includes a base field 4110 having a size of 2 bytes. However, in FIG. 23, since the fourth field 4114 is set to a fifth value, that is, "10", an optional field 4120 and an extension field 4130 having a size of 2 bytes are included in the packet 4000. It will be. Here, the length of the extension field 4130 may be defined by the EXT_LEN (LSB) field 4123 and the EXT_LEN (MSB) field 4124 included in the optional field 4120 and may be from 0 to 2 ¹³ -1 bytes. I can. In addition, the optional field 4120 may include an EXT_TYPE field 4121, an EXT_LEN (LSB) field 4123, and an EXT_LEN (MSB) field 4124.

Referring to FIG. 24, when the first field 4111 is set to a second value, the base field 4110 is a second field 4112 indicating the least significant bits (LSB) of the pointer value, and the most significant bits (MSB) of the pointer value. bits), and a fourth field 4114 indicating an extension mode of the header 4100 may be additionally included.

Accordingly, the packet 4000 includes a base field 4110 having a size of 2 bytes. However, in FIG. 24, since the fourth field 4114 is set to a sixth value, that is, "11", the optional field 4120 and the extension field 4130 having a size of 2 bytes are included in the packet 4000. It will be. Here, the length of the extension field 4130 may be defined by the EXT_LEN (LSB) field 4126 and the EXT_LEN (MSB) field 4127 included in the optional field 4120, and may be from 0 to 2 ¹³ -1 bytes. I can. In addition, the optional field 4120 may include a NUM_EXT field 4125, an EXT_LEN (LSB) field 4126, and an EXT_LEN (MSB) field 4127. In addition, the extension field 4130 may include a plurality of extension payloads, and a detailed description thereof will be omitted since it has already been described in FIG. 25.

Meanwhile, the EXT_TYPE field 4121 included in the optional field 4120 indicates the type of the extension payloads 4131 and 4132 included in the extension field 4130, and may be used to perform various functions according to a set value. have. For example, different information is displayed according to a value set in the EXT_TYPE field as shown in Table 3 below.

EXT_TYPE Description 000 Counter 001-110 These fields are reserved for future extension types 111 Padding
All bytes of extension field are padded with 0x00

Specifically, when the EXT_TYPE field 4121 is set to "000", it indicates that the counter function can be performed. Specifically, a preset field having a size as large as the value included in the EXT_LEN field is extended in the extension field 4130. It can be included as a payload. Here, the preset field may perform a function of identifying each of a plurality of packets included in the current PLP by ordering one by one, and a counter value may linearly increase from 0. For example, the fourth field When (4114) is set to the fourth value of "01" and the EXT_LEN field contains a value of 1, the preset field has a size of 1 byte, and accordingly, the counting value has a value from 0 to 255. I can.

Here, the preset packet performing the counter function can be used independently for each PLP, and when the counter value reaches the maximum value, the counter value of the next packet is reset to 0 and increased again.

In addition, for a PLP to which channel bonding is applied, a single counter, that is, a single preset field may be used to increase a counter value in a packet, and this may be performed before the packet is assigned to a specific RF channel.

On the other hand, the above description is applied equally to EXT_TYPE 1 (4141) ... EXT_TYPE N (4143) included in the extension field 4130 when the fourth field 4114 is set to a sixth value, that is, "11". I can.

Meanwhile, when the fourth field 4114 is set to one of a fourth value, that is, "01" and a fifth value, that is, "10", and the EXT_TYPE field 4121 is set to "111", all of the extension fields 4130 are It will be filled with padding.

Specifically, when the fourth field 4114 is set to a fourth value, that is, "01" or a fifth value, that is, "10", the optional field 4120 is The fifth field indicating the type, that is, the EXT_TYPE field 4121 and the sixth field indicating the length of the extended field 4130 (when the fourth field 4114 is the fourth value, the EXT_LEN field 4122), and the fourth field ( 4114) further includes an EXT_LEN (LSB) field 4123 and an EXT_LEN (MSB) field 4124). , The extended field 4130 may be entirely filled with padding.

For example, if the fifth field, that is, the EXT_TYPE field 4121 is set to "111", this means that the extended field 4130 is all filled with padding, as defined in Table 3, so the extended field 4130 Are all filled with padding.

For another example, when the fourth field 4114 is set to a fourth value, that is, "01", and the EXT_LEN field 4122 contains a value indicating that the length of the extension field 4130 is 0 bytes, This can be regarded as a case in which 1 byte of padding is included in the header 4100 when compared to the case where the fourth field 4114 is set to a third value, that is, “00”. That is, the 1-byte optional field 4120 soon serves as 1-byte padding.

In addition, the fourth field 4114 is set to a fifth value, that is, "10", and the EXT_LEN (LSB) field 4123 and the EXT_LEN (MSB) field 4124 indicate that the length of the extension field 4130 is 0 bytes. When the indicated value is included, this may be regarded as a case in which 2 bytes of padding are included in the header 4100 as compared to the case where the fourth field 4114 is set to a third value, that is, “00”. That is, the 2-byte optional field 4120 soon serves as 2-byte padding.

Meanwhile, when the fourth field 4114 is set to a sixth value, that is, “11”, as described above, a plurality of extension payloads may be filled in the extension field 4130 and padding may be filled in the remaining portions. In this case, EXT_TYPE 1 (4141) ... EXT_TYPE N (4143) need not be individually set to "111".

26A is a block diagram showing the configuration of a receiving device according to an embodiment of the present invention.

Referring to FIG. 26A, the receiving device 200 includes a receiving unit 210, an information extracting unit 220, and a signal processing unit 220.

The reception device 200 may be implemented to receive data from a transmission device that maps and transmits data included in an input stream to at least one signal processing path.

The receiver 210 may receive a stream including a packet including a header and a payload. That is, the receiving unit 210 receives a frame including data mapped to at least one signal processing path. Specifically, the receiver 210 may receive a stream including signaling information and data mapped to at least one signal processing path. Here, the signaling information may include information on an input type of an input stream input to the transmission device and information on a data type mapped to at least one signal processing path. Here, the information on the input type of the input stream may indicate whether all signal processing paths in the frame are the same input type. In addition, since detailed information included in the signaling information has been described above, detailed description will be omitted.

The information extracting unit 220 may extract a header from the packet, and extract information indicating a starting point of a data packet from the extracted header and information about the presence or absence of an additional field from the payload.

Information indicating the start point of the data packet in the payload included in the header and information on the presence or absence of an additional field have already been described in the section regarding the receiving device 100, and thus a detailed description thereof will be omitted.

The signal processing unit 230 may signal-process the data packet included in the payload based on information indicating the starting point of the extracted data packet and information about the presence or absence of an additional field. That is, based on information indicating the start point of the data packet, the point where the data packet starts in the payload is accurately detected, and decoding and decoding may be performed from the point where the data packet starts. In addition, the signal processing unit 230 may determine whether the received packet includes an optional field and an extension field based on the information on the presence or absence of the additional field, and process the data packet from the optional field and the extension field. The necessary information can be detected.

Here, the information indicating the start point of the data packet may include information on the presence or absence of the MSB part according to the distance between the start point of the payload and the start point of the data packet.

In addition, the information on the presence or absence of the additional field may include information indicating the presence or absence of at least one of the optional field and the extension field, and the length of the optional field and the extension field.

In addition, the optional field may include information indicating whether at least one of the optional field and the extension field includes padding.

Also, the signal processing unit 230 extracts signaling information from the received frame. In particular, the signal processing unit 230 may extract and decode the L1 signaling to obtain various information on the corresponding PLP included in the L1 pre-signaling region and the L1 post-signaling region. Also, the signal processing unit 230 may signal-process the frame based on the extracted signaling information. For example, signal processing may perform demodulation, frame de-builder, BICM decoding, and input de-processing.

Specifically, the signal processing unit 230 processes a frame received through the reception unit 210 to generate a baseband packet, and extracts header information from the generated baseband packet.

Further, the signal processing unit 230 may reconstruct a stream, that is, an input stream initially input to the above-described transmission device 100 by signal processing the payload data included in the baseband packet based on the extracted header information.

Meanwhile, the receiving device 200 according to another embodiment of the present invention includes a receiving unit 210, an information extracting unit 220 and a signal processing unit 230, and the receiving unit 210 includes a header and a payload. Including a packet, the information extracting unit 220 extracts a header from the packet and extracts information included in the header, and the signal processing unit 230 selects an input packet included in the payload based on the extracted information. Signal processing can be done. Here, a detailed description of the receiving unit 210, the information extracting unit 220, and the signal processing unit 230 has already been made, and a detailed description thereof will be omitted.

In addition, the header is a first value that indicates that a pointer value indicating the first value of each starting point of the input packet included in the payload is less than a preset value, or a second value indicating that the pointer value is greater than or equal to a preset value. A field is included, and when the first field is set to a second value, the header includes a second field indicating the least significant bits (LSB) of the pointer value and a third field indicating the most significant bits (MSB) of the pointer value. can do.

26B is a block diagram illustrating in detail a signal processing unit according to an embodiment of the present invention.

Referring to FIG. 26B, the signal processing unit 230 includes a demodulator 231, a signal decoder 232 and a stream generator 233.

The demodulator 231 performs demodulation according to the OFDM parameter from the received RF signal, performs sync detection, and when the sync is detected, recognizes whether the currently received frame from the signaling information stored in the sync area is a frame including necessary service data. . For example, it is possible to recognize whether a mobile frame or a fixed frame is received.

In this case, if OFDM parameters for the signaling region and the data region are not predetermined, OFDM parameters for the signaling region and data region stored in the sync region are obtained, and the signaling region and the data region immediately following the sync region are obtained. Demodulation may be performed by obtaining OFDM parameter information.

The signal decoder 232 decodes necessary data. In this case, the signal decoder 232 may perform decoding by acquiring parameters such as an FEC method and a modulation method for data stored in each data region by using the signaling information. Also, the signal decoder 232 may calculate the location of necessary data based on data information included in the header. That is, it is possible to calculate from which position in the frame the required PLP is transmitted.

The stream generator 233 may generate data to be serviced by processing the baseband packet BBP received from the signal decoder 232.

For example, the stream generator 233 may generate an ALP packet from an error-corrected baseband packet based on various pieces of information. Specifically, the stream generator 233 may include de-jitter buffers, and the de-jitter buffers may regenerate accurate timing for restoring an output stream based on various pieces of information. Accordingly, a delay for synchronization between a plurality of PLPs may be compensated.

* Fig. 27 is a block diagram showing the configuration of a receiver according to an embodiment of the present invention.

Referring to FIG. 27, a receiver 4400 may include a controller 4410, an RF receiver 4420, a demodulator 4430, and a service player 4440.

The controller 4410 determines an RF channel and a PLP through which the selected service is transmitted. In this case, the RF channel may be specified by a center frequency and a bandwidth, and the PLP may be specified by a PLP ID. A specific service can be transmitted through one or more PLPs belonging to one or more RF channels for each component constituting the service, but after that, for convenience of explanation, all data necessary to reproduce one service is transmitted through one RF channel. It is assumed that it is transmitted through one PLP. That is, a service has a unique data acquisition path for reproducing a service, and the data acquisition path is specified by an RF channel and a PLP.

The RF receiver 4420 detects an RF signal in an RF channel selected by the controller 4410, performs signal processing on the RF signal, and transmits the extracted OFDM symbols to the demodulator 4430. Here, signal processing may include synchronization, channel estimation, and equalization, and information for signal processing is a value previously promised by the transmitter/receiver depending on its use and implementation, or included in a specific OFDM symbol that is previously promised among OFDM symbols. And transmitted from the receiver.

The demodulator 4430 performs signal processing on OFDM symbols, extracts a user packet, and delivers it to the service player 4440, and the service player 4440 reproduces and outputs a service selected by the user using the user packet. In this case, the format of the user packet may vary according to the implementation method of the service, and examples include TS packet or IPv4 packet.

28 is a block diagram showing a demodulator in more detail according to an embodiment of the present invention.

Referring to FIG. 28, a demodulator 4430 includes a frame demapper 441, a BICM decoder 4432 for L1 signaling, a controller 443, a BICM decoder 4434, and an output processor 4435. Can be configured.

The frame demapper 441 selects OFDM cells constituting the FEC blocks belonging to the PLP selected from the frame composed of the OFDM symbol based on the control information transmitted from the controller 4443 and transmits the selected OFDM cells to the BICM decoder 4434, and L1 OFDM cells corresponding to one or more FEC blocks including signaling are selected and transmitted to the BICM decoder 1232 for L1 signaling.

The BICM decoder 4432 for L1 signaling processes an OFDM cell corresponding to an FEC block including L1 signaling, extracts L1 signaling bits, and transmits the extracted L1 signaling bits to the controller 4443. In this case, signal processing may include a process of extracting a log-likelihood ratio (LLR) value for decoding an LDPC code in an OFDM cell and a process of decoding the LDPC code using the extracted LLR value.

The controller 4443 extracts the L1 signaling table from the L1 signaling bits and controls the operation of the frame demapper 441, the BICM decoder 4434, and the output processor 4435 using the value of the L1 signaling table. In FIG. 28, for convenience of explanation, it is shown that the BICM decoder 4432 for L1 signaling does not use control information of the controller 4443. However, when L1 signaling has a hierarchical structure similar to the structure of L1-PRE and L1-POST described above, the BICM decoder 4432 for L1 signaling may be composed of one or more BICM decoding blocks, and BICM decoding blocks and frames It is clear that the operation of the demapper 441 can be controlled by upper layer L1 signaling information.

The BICM decoder 4434 signal-processes OFDM cells constituting FEC blocks belonging to the selected PLP, extracts baseband packets, and transfers the baseband packets to the output processor 4435. Signal processing may include a process of extracting an LDPC code and a log-likelihood ratio (LLR) value for decoding in an OFDM cell, and a process of decoding the LDPC code using the extracted LLR value, which is transmitted from the controller 443 It can be performed based on the control information.

The output processor 4435 signal-processes the baseband packets, extracts a user packet, and delivers the extracted user packets to the service player 4440. In this case, signal processing may be performed based on control information transmitted from the controller 1233.

29 is a flowchart schematically illustrating an operation of a receiver from a point in time when a user selects a service until an actual selected service is played according to an embodiment of the present invention.

It is assumed that service information for all services selectable in the initial scan (S4600) step has been obtained before the user's service selection (S4610). Here, the service information may include information on an RF channel and a PLP through which data necessary for reproducing a specific service in the current broadcasting system are transmitted. Here, as an example of service information, there is PSI/SI (Program-Specific Information/Service Information) of MPEG2-TS, which can be obtained through L2 signaling and higher layer signaling.

When the user selects a service (S4610), the receiver changes to a frequency for transmitting the selected service (S4620) and detects an RF signal (S4630). Service information may be used in the process of changing to a frequency for transmitting the selected service (S4620).

When the RF signal is detected, the receiver performs an L1 signaling extraction operation (S4640) from the detected RF signal. Thereafter, the receiver selects a PLP for transmitting the selected service using the L1 signaling extracted in the previous process (S4650), and extracts a baseband packet from the selected PLP (S4660). Service information may be used in the process of selecting a PLP for transmitting the selected service (S4650).

In addition, the process of extracting the baseband packet (S4660) includes a process of demapping a transmission frame to select OFDM cells belonging to a PLP, a process of extracting a log-likelihood ratio (LLR) value for LDPC code/decoding from the OFDM cell, and It may include a process of decoding the LDPC code by using the extracted LLR value.

The receiver performs ALP packet extraction (S4670) from the extracted baseband packet using header information of the extracted baseband packet, and User packet extraction (S4670) from the extracted ALP packet using header information of the extracted ALP packet. S4680). The extracted user packet is used for the selected service playback (S4690). In the ALP packet extraction (S4670) process and the user packet extraction (S4680) process, the L1 signaling information obtained in the L1 signaling extraction (S4640) process may be used. In this case, the process of extracting a user packet from an ALP packet (recovering a null TS packet and inserting a TS sync byte) is the same as described above.

30 is a flowchart illustrating a method of controlling a transmission device according to an embodiment of the present invention.

In the control method of the transmission device shown in FIG. 30, a packet including a header and a payload is generated based on an input packet (S3510).

Then, the generated packet is signal-processed (S3520).

Thereafter, the signal-processed packet is transmitted (S3530).

Here, the base field constituting the header includes a first field set to a first value indicating that the base field is a first length or a second value indicating that the base field is a second length, and the first field is a second value When set to, the base field represents a second field representing the least significant bits (LSB) of a pointer value representing the first value of each starting point of the input packet included in the payload, and the MSB (most significant bits) of the pointer value. May include a third field.

In addition, the first field, the second field, and the third field are included in a base field constituting the header, and the base field may include a fourth field indicating an extension mode of the header.

In addition, the fourth field may include at least one of information on the presence or absence of the optional field, the length of the optional field, and the structure of the extension field.

In addition, the fourth field includes a third value indicating that the optional field and the extension field do not exist, a fourth value indicating that the optional field exists and the length of the optional field is 1 byte, and the optional field exists and the length of the optional field is 2 A fifth value indicating byte and an optional field exist, and the length of the optional field is 2 bytes, and may be set to one of sixth values indicating that the extension field includes a plurality of extension payloads.

In addition, when the fourth field is set to a fourth value or a fifth value, the optional field further includes a fifth field indicating a type of an extension payload included in the extension field and a sixth field indicating a length of the extension field, When the fifth field is set to a preset value, all of the extended fields may be filled with padding.

In addition, when the fourth field is set to a fifth value, the optional field is a field indicating the type of the extension payload included in the extension field, a field indicating the LSB part of the field indicating the length of the extension field, and a field indicating the length of the extension field. It may include a field indicating the MSB part of the field.

In addition, when the fourth field is set to the sixth value, the optional field is a field indicating the number of extension payloads included in the extension field, a field indicating the LSB part of the field indicating the length of the extension field, and the length of the extension field. The field indicating the MSB part of the field indicating may be included.

Here, the extension field may include a plurality of fields indicating the types of each of the plurality of extension payloads and a plurality of fields indicating the length of each of the plurality of extension payloads.

Further, in the extension field, when the fourth field is set to one of the fourth value and the fifth value, and the length of the extension payload included in the extension field is less than the length of the extension field, the extension field includes the extension payload and the remaining Padding may be included in the remaining part.

In addition, when the fourth field is set to a sixth value, the extension field may include a plurality of extension payloads in the extension field and padding in the remaining part.

Meanwhile, a control method of a transmitting device according to another embodiment of the present invention includes a header including a base header including information indicating a starting point of a data packet in a payload and information about the presence or absence of an additional field, and a payload. Generates a packet containing.

Here, the information indicating the start point of the data packet may include information on the presence or absence of the MSB part according to the distance between the start point of the payload and the start point of the data packet.

In addition, the information indicating the start point of the data packet may include one of a first value indicating that the MSB part does not exist and a second value indicating that the MSB part is present.

In addition, the information on the presence or absence of the additional field may include information indicating the presence or absence of at least one of the optional field and the extension field, and the length of the optional field and the extension field.

Here, the optional field may include information indicating whether at least one of the optional field and the extension field includes padding.

In addition, the information on the presence or absence of the additional field includes a first value indicating that the optional field and the extension field do not exist, a second value indicating that the optional field exists and the extension field does not exist, and the length of the optional field is 1 byte, and an optional field. Is present, the Extension field is absent, and one of the third value indicating that the length of the Optional field is 2 bytes, and the fourth value indicating that the Optional field and Extension field exist, and the length of the Optional field and Extension field exceeds 2 bytes. Can include.

In addition, the optional field may include information indicating the length of the extension field when information on the presence or absence of the additional field is set to a fourth value.

In addition, information indicating the length of the extension field may include at least one of an LSB part and an MSB part according to the length of the extension field.

Then, the generated frame is signal-processed.

Then, the signal-processed frame is transmitted.

Meanwhile, FIG. 31 is a flowchart illustrating a method of controlling a reception device according to an embodiment of the present invention.

In the control method of the reception device shown in FIG. 31, a stream including a packet including a header and a payload is received (S3610).

Then, a header is extracted from the packet, and information included in the header is extracted (S3620).

Thereafter, the input packet included in the payload is signal-processed based on the extracted information (S3630).

Here, the base field constituting the header includes a first field set to a first value indicating that the base field is a first length or a second value indicating that the base field is a second length, and the first field is a second value If set to, the base field indicates the second field indicating the least significant bits (LSB) of the pointer value indicating the first value of each starting point of the input packet included in the payload, and the MSB (most significant bits) of the pointer value. It may include a third field indicating.

Meanwhile, in a method of controlling a reception device according to another embodiment of the present invention, a stream including a packet including a header and a payload is received.

Then, a header is extracted from the packet, and information indicating the start point of the data packet and information about the presence or absence of an additional field are extracted from the extracted header.

Then, the data packet included in the payload is signal-processed based on information indicating the start point of the extracted data packet and information on the presence or absence of an additional field.

Here, the information indicating the start point of the data packet may include information on the presence or absence of the MSB part according to the distance between the start point of the payload and the start point of the data packet.

In addition, the information on the presence or absence of the additional field may include information indicating the presence or absence of at least one of the optional field and the extension field, and the length of the optional field and the extension field.

In addition, the optional field may include information indicating whether at least one of the optional field and the extension field includes padding.

As described above, according to various embodiments of the present invention, various types of data can be mapped to a transmittable physical layer, and data processing efficiency can be improved.

Meanwhile, a non-transitory computer readable medium in which a program sequentially performing a signal processing method according to the present invention is stored may be provided.

As an example, generating a packet including a header including a base header including information indicating the start point of a data packet in the payload and information on the presence or absence of an additional field, and a packet including the payload, and signal processing the generated frame A non-transitory computer readable medium in which a program for performing the step of performing the step of performing and the step of transmitting the signal-processed frame is stored may be provided.

In addition, as an example, the step of receiving a stream including a packet including a header and a payload, extracting a header from the packet, and indicating the start point of the data packet in the payload from the extracted header, and the presence or absence of an additional field Non-transitory reading is possible in which a program that performs the step of extracting information about the data packet and signal processing the data packet included in the payload based on the information indicating the starting point of the extracted data packet and the information on the presence or absence of an additional field A medium (non-transitory computer readable medium) may be provided.

The non-transitory readable medium refers to a medium that stores data semi-permanently and can be read by a device, rather than a medium that stores data for a short moment, such as a register, a cache, and a memory. Specifically, the above-described various applications or programs may be provided by being stored in a non-transitory readable medium such as a CD, DVD, hard disk, Blu-ray disk, USB, memory card, ROM, or the like.

In addition, although a bus is not shown in the above-described block diagram showing the transmitting device and the receiving device, communication between components in the transmitting device and the receiving device may be performed through a bus. In addition, each device may further include a processor such as a CPU or a microprocessor that performs the various steps described above.

In addition, although the preferred embodiments of the present invention have been illustrated and described above, the present invention is not limited to the specific embodiments described above, and the technical field to which the present invention belongs without departing from the gist of the present invention claimed in the claims. In addition, various modifications are possible by those of ordinary skill in the art, and these modifications should not be individually understood from the technical spirit or prospect of the present invention.

100: transmitting device 110: packet generating unit
120: signal processing unit 130: transmitting unit

Claims (2)

A packet generator for generating a packet including a header and a payload;
A frame generator that generates a frame based on the generated packet and signaling information; And
Includes; a transmission unit for transmitting the frame,
The header includes a first field and a second field,
The first field includes a first value or a second value,
The first value indicates that the second field has a first length, the second value indicates that the second field has a second length,
If the first field includes the first value, the second field includes a least significant bit (LSB) field,
When the first field includes the second value, the second field includes a least significant bit (LSB) field and a most significant bit (MSB) field,
The second field contains a pointer value,
The pointer value is an offset from a start position of the payload to a first start position of at least one input packet starting from the payload,
When the first field includes the second value, the header includes a third field including a value indicating an extension mode of the header. A receiver configured to receive a frame generated based on the packet and signaling information; And
A processing unit that obtains the packet from the received frame based on the signaling information and processes the obtained packet; and
The packet includes a header and a payload,
The header includes a first field and a second field,
The first field includes a first value or a second value,
The first value indicates that the second field has a first length, the second value indicates that the second field has a second length,
If the first field includes the first value, the second field includes a least significant bit (LSB) field,
When the first field includes the second value, the second field includes a least significant bit (LSB) field and a most significant bit (MSB) field,
The second field contains a pointer value,
The pointer value is an offset from a start position of the payload to a first start position of at least one input packet starting from the payload,
When the first field includes the second value, the header includes a third field including a value indicating an extension mode of the header.

Images