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

Abstract

The broadcast receiving device is disclosed. The broadcast receiving apparatus includes a receiving unit for receiving a transmission frame generated based on a packet including a header and a payload, a processing unit for obtaining a packet from the transmission frame and processing a payload based on a header included in the packet; , The first field includes a first value or a second value, the first value indicates that the second field is of a first length, the second value indicates that the second field is of a second length, and the first field is the first value. If it contains a value, the second field includes a least significant bit field; if the first field includes a second value, the second field is a least significant bit (LSB) field and a most significant bit (MSB) field. Wherein the second field includes a pointer value, the pointer value is an offset from the start position of the payload to the first start position of at least one input packet starting at the payload, wherein the first field is the second value. If you include, the header It may include a third field including a value indicating the extension mode.

Description

Transmitter, Receiver and Control Method {TRANSMITTING APPARATUS AND RECEIVING APPARATUS AND CONTROLLING METHOD THEREOF}

The present invention relates to a transmitting apparatus, a receiving apparatus, and a control method thereof, and more particularly, to a transmitting apparatus, a receiving apparatus, and a control method for mapping data to at least one signal processing path and transmitting the same.

In the information society of the 21st century, broadcasting and communication services are entering the age of full-fledged digitalization, multi-channelization, broadband, and high quality. In particular, with the recent expansion of high-definition digital TVs, PMPs, and mobile broadcasting devices, the demand for digital broadcasting services has also increased.

In response to these demands, standards groups have established various standards to provide various services that can satisfy user needs. Therefore, there is a demand for a method for providing better services through better performance.

The present invention has been made in accordance with the above-described needs, and an object of the present invention is to provide a transmitting apparatus, a receiving apparatus, 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 based on an input packet, a packet generator for generating a packet including a header and a payload, a signal processor for signal processing the generated packet and the signal And a transmitter for transmitting the processed packet, wherein a base field constituting the header is set to a first value indicating that the base field is of a first length or to a second value indicating that the base field is of a second length. And a first field, wherein when the first field is set to the second value, the base field is LSB of a pointer value indicating a first value of each start point of an input packet included in the payload. a second field indicating bits and a third field indicating most significant bits (MSB) of the pointer value.

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

The fourth field may include at least one of information on whether an optional field exists, a length of the optional field, and information on a structure of the extension field.

The fourth field may include a third value indicating that the Optional field and an Extension field are not present, 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 A fifth value indicating that an optional field is 2 bytes in length and a sixth value indicating that the optional field exists, the optional field is 2 bytes in length, and the extension field includes a plurality of extension payloads; Can be.

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, if the fifth field is set to a preset value, all of the extension fields may be filled with padding.

If the fourth field is set to the fifth value, the Optional field may include 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 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 an MSB part of a field indicating a length of the extension field.

The extension field may include a plurality of fields indicating 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.

The extension field may include the extension field if 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 smaller than the length of the extension field. Including the extension payload and the remaining part may include padding.

The extension field may include a plurality of extension payloads in the extension field and padding in the remaining parts when the fourth field is set to the sixth value.

On the other hand, the receiver according to an embodiment of the present invention is a receiver for receiving a stream including a packet including a header and a payload, information extraction for extracting the header from the packet, extracting information contained in the header And a signal processor for signal-processing an input packet included in the payload based on the extracted information, wherein a base field constituting the header is a first value or the base indicating that the base field is of a first length; And a first field set to a second value indicating that the field is of a second length, and when the first field is set to the second value, the base field is one of each starting point of an input packet included in the payload. A second field indicating the least significant bits (LSB) of the pointer value indicating the first value and the most significant bits (MSB) of the pointer value It may include three fields.

On the other hand, the control method of the transmitting apparatus according to an embodiment of the present invention, based on the input packet, generating a packet including a header and the payload, signal processing the generated packet and the signal processed packet And a base field constituting the header, the first field being a first value indicating that the base field is of a first length or a second value indicating that the base field is of a second length. Field, and when the first field is set to the second value, the base field includes LSBs (least significant bits) of a pointer value indicating a first value of each start point of an input packet included in the payload. And a second field indicating and a third field indicating the most significant bits (MSB) of the pointer value.

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

The fourth field may include at least one of information on whether an optional field exists, a length of the optional field, and information on a structure of the extension field.

The fourth field may include a third value indicating that the Optional field and an Extension field are not present, 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 A fifth value indicating that an optional field is 2 bytes in length and a sixth value indicating that the optional field exists, the optional field is 2 bytes in length, and the extension field includes a plurality of extension payloads; Can be.

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, if the fifth field is set to a preset value, all of the extension fields may be filled with padding.

If the fourth field is set to the fifth value, the Optional field may include 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 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 an MSB part of a field indicating a length of the extension field.

The extension field may include a plurality of fields indicating 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.

The extension field may include the extension field if 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 smaller than the length of the extension field. Including the extension payload and the remaining part may include padding.

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

On the other hand, the control method of the receiving apparatus according to an embodiment of the present invention comprises the steps of receiving a stream including a packet including a header and a payload, extracting the header from the packet, and extracts the information contained in the header And signal processing an input packet included in the payload based on the extracted information, wherein a base field constituting the header indicates that the base field is a first length; A first field set to a value or 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 a LSB (least significant bits) of a pointer value indicating a first value of each starting point of and indicating a most significant bit (MSB) of the pointer value It may comprise a third field.

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 view for explaining a schematic configuration of a broadcast link layer 1400 according to an embodiment of the present invention.
3A is a diagram for describing a schematic configuration of a transmission system (or a transmission device) according to an embodiment of the present invention.
3B and 3C are diagrams for describing a multiplexing method according to an embodiment of the present invention.
FIG. 4 is a block diagram showing the detailed configuration of the Input Formatting block shown in FIG. 3A.
5A and 5B are diagrams for describing a detailed configuration of a baseband framing block.
6 is a block diagram illustrating a configuration of a transmitting apparatus according to an embodiment of the present invention.
7A is a block diagram illustrating a detailed configuration of a packet generator according to an exemplary 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 the structure of a header according to an embodiment of the present invention.
10 is a diagram illustrating a detailed configuration of an optional field according to an embodiment of the present invention.
11 to 16D illustrate a structure of a packet according to various embodiments of the present disclosure.
17 is a diagram showing the structure of a packet according to another embodiment of the present invention.
FIG. 18 is a diagram illustrating a detailed configuration of the header shown in FIG. 17.
19 is a diagram illustrating a detailed configuration of an optional field according to another embodiment of the present invention.
20 to 24 illustrate a structure of a packet according to various embodiments of the present disclosure.
25 is a diagram illustrating the structure of an extension field according to an embodiment of the present invention.
26A is a block diagram illustrating a configuration of a receiving apparatus according to an embodiment of the present invention.
FIG. 26B is a block diagram illustrating in detail a signal processor according to an exemplary embodiment. Referring to FIG.
27 is a block diagram showing a configuration of a receiver according to an embodiment of the present invention.
28 is a block diagram illustrating the 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 at which a user selects a service to reproduction of a actually selected service according to an embodiment of the present invention.
30 is a flowchart illustrating a control method of a transmitting apparatus according to an embodiment of the present invention.
31 is a flowchart illustrating a control method of a receiving apparatus 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 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. Terms to be described later are terms defined in consideration of functions in the present invention, and may be changed according to intentions or customs of users or operators. Therefore, the definition should be made based on the contents throughout the specification.

An apparatus and method proposed in an embodiment of the present invention are a digital multimedia broadcasting (DMB) service and a digital video broadcasting handheld: DVP-H (hereinafter, referred to as 'DMB'). DVP-H '), and Advanced Television Systems Committee Mobile / Handheld (ATSC-M / H), ATSC-M / H, hereinafter referred to as ATSC-M / H. Mobile video services such as services, digital video broadcasting systems such as Internet protocol television (IPTV) services, and MPEG Media Transport (MPEG (moving picture experts group)). media transport: MMT, hereinafter referred to as 'MMT' system, evolved packet system (EPS), and long-term evolution (lon) g-term evolution: LTE, hereinafter referred to as 'LTE') A mobile communication system, and long-term evolution-advanced (LTE-A, hereinafter referred to as 'LTE-A') Mobile communication system, high speed downlink packet access (HSDPA, hereinafter referred to as "HSDPA") Mobile communication system, high speed uplink packet access (HSUPA, hereinafter "HSUPA" High rate packet data (HRPD) of a mobile communication system and a 3rd generation project partnership 2: 3GPP2 (hereinafter referred to as 3GPP2). Mobile communication system, 3GPP2 wideband code division multiple access (WCDMA), and 3GPP2 code division multiple access (code divi) sion multiple access (CDMA), a mobile communication system, and the Institute of Electrical and Electronics Engineers (IEEE), an 802.16m communication system. Applicable to various communication systems such as a communication system and a mobile internet protocol (mobile internet protocol).

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 a service and signaling 1050 for conveying information necessary to acquire and consume media data in a receiver. The media data may be encapsulated in a form suitable for transmission prior to transmission. Encapsulation can 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 by an application layer protocol.

FIG. 1 illustrates a case of using an MMT protocol (MMTP) 1110 and a Real-Time Object Delivery over Unidirectional Transport (ROUTE) protocol 1120 defined in MMT as an application layer protocol. In this case, in order to know in which application layer protocol a specific service is transmitted in a receiver, a method for informing information about an application protocol through which a service is transmitted is required in a manner independent of the application layer protocol.

The Service List Table (SLT) 1150 illustrated in FIG. 1 configures information about a service into a table and packetizes it in a signaling manner for satisfying the above-described purpose. The details of the SLT will be described later. The above-described packetized media data and signaling including the SLT are transmitted through a broadcast link layer 1400 via a User Datagram Protocol (UDP) 1200 and an Internet Protocol (IP) 1300. Is passed). An example of a broadcast link layer is the ATSC 3.0 Link-Layer Protocol (ALP) defined in ATSC 3.0. The ALP protocol generates an ALP packet as an input of an IP packet 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 an IP packet 1300 including media data or signaling as an input, but uses an MPEG2-TS packet or a packetized data in a general form as an input. Note that you can. In this case, signaling information necessary for controlling the broadcast link layer is also transmitted 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 the signal. In this case, the broadcast physical layer 1500 has at least one signal processing path. An example of a signal processing path may be a physical layer pipe (PLP) of DVB-T2 or ATSC 3.0, and one or more services may be mapped to a PLP or a part of a service may be mapped.

2 is a view for explaining 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, MPEG2-TS packet 1320, and other packetized data 1330. can do.

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

3A is a diagram for describing a schematic configuration of a transmission system (or a transmission device) according to an embodiment of the present invention. Referring to FIG. 3A, a transmission system 10000 according to an embodiment of the present invention may include input formatting blocks (or parts) 11000 and 11000-1 and bit interleaved and coded modulation (BICM) blocks 12000 and 12000-1. , Framing / Interleaving blocks 13000 and 13000-1 and Waveform Generation blocks 14000 and 14000-1.

Input Formatting blocks (or parts) 11000 and 11000-1 generate baseband packets from input streams for the data to be serviced. Here, the input stream may be a transport stream (TS), an Internet packet (IP) (for example, IPv4, IPv6), an MPEG media transport (MT), a generic stream (GS), a generic stream encapsulation (GSE), or the like. 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. Bit Interleaved and Coded Modulation (BICM) blocks 12000 and 12000-1 determine and encode FEC coding rates and constellation orders according to areas (Fixed PHY Frame or Mobile PHY Frame) to which data to be serviced is transmitted. And time interleaving. Meanwhile, the signaling information for 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 an implementation.

The framing / interleaving blocks 13000 and 13000-1 combine the time interleaved data with a signaling signal to generate a transmission frame.

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 the receiver.

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

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

3B is a block diagram for implementing TDM (Time Division Multiplexing) according to an embodiment of the present invention.

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

Data is input and formatted into the Input Formatting block 1100, omnidirectional error correction is applied in the BICM block 12000, and mapped to constellations. Subsequently, time and frequency interleaving is performed in the Framing / Interleaving block 13000, and frame generation is performed. Thereafter, 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 before the Framing / Interleaving block 13000 in the LDM injection block. And Waveform Generation block 14000 are similar to TDM.

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

As shown in FIG. 4, the Input Formatting block 11000 consists of three blocks that control packets distributed to PLPs. Specifically, the method includes an encapsulation and compression block 11100, a baseband formatting (or baseband framing block) 11200, and a scheduler block 11300.

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

Packets output from the encapsulation and compression block 11200 are ALP 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 easy to extract the length of the ALP packet from the ALP packet itself without additional information. The maximum length of an ALP packet is 64 kB. The maximum length of an ALP packet including a header is 4 bytes. ALP packets are integer bytes long.

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

The scheduler block 11200 receives the encapsulated ALP packets and specifies how the packets are allocated to the physical layer resource. In detail, the scheduler block 11200 specifies how the baseband formatting block 1130 outputs the baseband packet.

The function of the scheduler block 11200 is defined by data size and time. The physical layer may transmit a portion of the data in this distributed time. The scheduler block uses inputs and information such as encapsulated data packets, quality of service metadata for encapsulated data packets, system buffer models, constraints from system management, and configuration, Create a suitable solution in terms of configuration of physical layer parameters. The solution is subject to the available configuration and control parameters and the aggregate spectrum.

On the other hand, the operation of the scheduler block 11200 is limited to a set of dynamic, quasi-static and static configurations. The definition of this restriction may vary from implementation to implementation.

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

The baseband formatting block 11300 is a baseband packet construction block 3100, 3100-1, ... 3100-n, a baseband packet header construction block 3200, 3200-1, ... 3200, as shown in FIG. 5A. -n), consisting 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.

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

The baseband packet header construction blocks 3200, 3200-1, ... 3200-n constitute a header 3500-1. The header 3500-1 may include three parts, as shown in FIG. 5B: a base field (or base header) 3710, an optional field (or optional header) 3720, and an extended field (or extended header). (3730). Here, the base field 3710 may appear 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 to the start of the next ALP packet in the baseband packet containing the offset value in bytes. If the ALP packet starts a baseband packet, the pointer value is zero. If there is no ALP packet starting within the baseband packet, the pointer value is 8191 and a two byte base header may be used.

The extension field 3730 may be utilized later and may be used, for example, for baseband packet packet counters, 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 directional error correction encoding so that payload data mapped to constellations is not always mapped to the same point, such as in the case of a repetitive sequence.

6 is a block diagram illustrating a configuration of a transmitting apparatus according to an embodiment of the present invention.

According to FIG. 6, the transmitter 100 includes a packet generator 110, a signal processor 120, and a transmitter 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. Where the packet is a header and a. It includes a payload that contains an input packet, and the packet is defined as a fixed length K payload. The length of the packet can be set according to the selected code rate and code length. Here, the input packet may be, for example, an ASC (ATSC Link layer Protocol) packet. The ALP packet may include one or a combination of an Internet Protocol (IP) packet, a TS packet, and a signaling packet, and specifically, an incoming IP packet, a TS packet, and various types of data may be encapsulated. may be generated as an ALP packet for transmission to each PLP, which 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 kinds of data. Hereinafter, for convenience of description, a packet generated by the packet generator 110 is called a baseband packet, and an input packet is called 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 illustrating a detailed configuration of a packet generator according to an exemplary 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. The packet generator 110 may transmit the generated baseband packet to the baseband packet scrambler 115.

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

In detail, 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 the ALP packet, and may include information about ALP payload data included in the ALP packet and information about a packet included in the ALP packet.

The baseband packet header generation unit 110-1 may generate a header inserted into the baseband packet. Here, the header inserted into the baseband packet is called a baseband packet header, and the baseband packet header includes information about the baseband packet.

In particular, when the input stream is TS, the baseband packet header generation unit 110-1 may generate a baseband packet header including information on the number of TS packets in the ALP packet, the number of removed null packets, and the like. . 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 from the baseband packet header generator 110-1 into an ALP packet output from the ALP packet constructor 110 '. Baseband packet can be generated.

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

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 a 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 consist of baseband packets having a fixed size. In other words, the input stream may be encapsulated into baseband packets for one PLP.

On the other hand, PLP refers to a signal path that is processed independently. That is, each service (eg, video, extended video, audio, data streams, etc.) can be transmitted and received over multiple RF channels, where the PLP is the path over which this service is transmitted or the stream transmitted over that path. . In addition, the PLP may be located in slots that are distributed at time intervals on multiple RF channels, or may be distributed at time intervals on one RF channel. That is, one PLP may be transmitted by being distributed at a time interval on one RF channel or multiple RF channels.

The PLP structure consists of input mode A providing one PLP and input mode B providing a plurality of PLPs. In particular, in case of supporting input mode B, it is possible not only to provide robust specific service but also to transmit one stream in a distributed manner. In this way, a time diversity gain can be obtained by increasing the time interleaving length. In addition, when only a specific stream is received, the receiver can be used at low power by turning off the receiver for the rest of the time.

Here, in order to reduce the deterioration of transmission quality in a mobile communication transmission path, time diversity means that when the transmitting side transmits the same signal several times at a predetermined time interval, the receiving side recombines these received signals to obtain a good transmission quality. Technology.

In addition, transmission efficiency can be improved by including and transmitting information that can be commonly transmitted to a plurality of PLPs in one PLP. PLP0 plays such a role, and such a PLP is called a common PLP, and PLP0 The remaining PLPs can be used for data transmission, and these PLPs are called data PLPs. By using such a PLP, SDTV programs can be provided not only in a home HDTV program but also in a portable and mobile environment. In addition, through broadcasting stations or broadcast content providers, not only various broadcasting services may be provided to viewers, but also differentiated services that can receive broadcasts in a difficult viewing area are difficult to view.

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 'generates a plurality of ALP packets 111' and 112 'by storing TS packets in an ALP Payload and inserting headers, the packet generator 110 generates the generated ALP packets 111 and 112'. A plurality of baseband packets 121 and 122 may be generated by grouping the plurality of ALP packets 111 'and 112' and inserting a baseband packet header. Here, each baseband packet 121 and 122 may include a plurality of ALP packets and may also include a portion of the ALP packets.

The baseband packet scrambler 115 may randomly scramble the generated baseband packets 121 and 122 to generate a plurality of scrambled baseband packets 125-1 and 125-2. 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 processor 120 may signal-process the generated packet. Here, the generated packet may mean a baseband packet as described above.

In detail, the signal processor 120 may signal-process the baseband packet to generate a transmission frame.

In addition, the signal processor 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 the preamble into which the L1 signaling information is inserted may include an L1 pre-signaling region and an L1 post signaling region. The L1 post signaling region also includes a configurable field and a dynamic field.

Meanwhile, the L1 pre signaling area may include information for interpreting the L1 post signaling and information about the entire system, and the L1 pre signaling area 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 the system, and the L1 signaling region included in each frame in one super frame may have the same length but may include different contents.

Although not shown in the drawings, the signal processor 120 may include the bit interleaved and coded modulation (BICM) blocks 12000 and 12000-1 and the 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 receiver (not shown).

In detail, 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 the RF signal and transmits the RF signal to a receiving device (not shown).

8 is a diagram illustrating the structure of a packet according to an embodiment of the present invention. Here, the packet generated from the packet generator 110 used in the present specification has already been defined as a baseband packet.

Referring to FIG. 8, the baseband packet includes 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 is defined as having the same meaning as the base field. The babe band packet header 3100 necessarily includes the base field 3110, and the existence of the optional field 3120 may vary depending on the control field value of the base field 3110. In addition, the presence or absence of the extension field 3130 may be selected using the control field of the optional field 3120.

Meanwhile, the basic field, optional field, and extended field used in the present specification may be used as names of the basic header, optional header, and extended header.

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

9 is a diagram illustrating the 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.

In the present specification, terms such as a base header, an optional field, and an extension field have been described. However, these terms may be expressed by general words such as a first header, a second field, and a third field.

Specifically, the baseband packet can be largely divided into a header and a payload, where the header can be composed of three parts, as shown in FIG. 9. The first part is the base header 2310 and is present in every packet. 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 every frame, 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 regarding the existence 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 may be the start point of the next generic packet present in the packet 2300. A function that provides a pointer including an offset value of up to byte can be performed. Here, the start point of the data packet 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 by the above-described offset value in bytes.

As shown in FIG. 7B, the first ALP packet 111 ′ may be included in the first packet 121 without being split, but may be divided like the second ALP packet 112 ′ and may be divided with the first packet 121. 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 payload start of the first packet 121 is started. It may include information including a value relating to the 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 a start point of an ALP packet included after the second packet 112 ′.

For example, if a generic packet is placed from the start point in the packet, the value of the pointer may be set to zero. The pointer can be extended up to 2 bytes, and the value indicated by the pointer can be increased to 8191 bytes. The base header 2310 may represent the distance to the starting point where 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 about the existence of the MSB part according to the distance between the start point of the payload and the start point of the data packet, and the first value indicating that the MSB part is absent. And a second value indicating that the MSB part is present. That is, when the information indicating the start point of the data packet is set to 0, it indicates that the MSB part is not present. When 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 the MSB part of the pointer exists. Here, the MODE field 2311 may have a size of 1 bit.

If 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 in the payload 2340 is the short pointer length. Indicates that Here, the short pointer length means a length not exceeding 128 bytes. Accordingly, the pointer field including information about the distance from the start point of the payload 2340 to the start point of the new generic packet in the payload 2340 is a pointer (LSB) field 2312 corresponding to the short pointer length. It contains only 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, the pointer field includes only the pointer (LSB) field 2312, and thus the length of the base header 2310 is 1 byte.

On the other hand, if 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 a new generic packet in the payload 2340. length). Here, the long pointer length may be greater than or equal to 128 bytes. Accordingly, the pointer field containing information about the distance from the start point of payload 2340 to the start point of new generic packet in 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 whether there is 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 sets the MODE field 2311, the pointer (LSB) field 2312, the pointer (MSB) field 2313, and the 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'.

On the other hand, the information on the existence of the additional field included in the base header 2310, 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 May contain information that indicates.

Further, the information regarding the existence of the additional field may include a first value indicating that the Optional field 2320 and the Extension field 2330 are absent, the Optional field 2320 is present, the Extension field 2330 is absent, and the Optional field ( A second value indicating that the length of 2320 is 1 byte, an optional field 2320 is present, an extension field 2330 is absent, and a third value indicating that the length of the optional field 2320 is 2 bytes and an optional field 2320 And an Extenstion field 2330, 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.

The optional field 2320 may include information indicating the length of the extension field 2330 when the information on the existence of the additional field is set to a fourth value, and may be included in the LSB part and the MSB part according to the length of the extension field. It may include at least one.

Information regarding the presence or absence of such an additional field may be stored in an optional header indicator (OHI) field 2314. In detail, 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 the value stored in the OHI field 2314 may be summarized as shown in Table 1 below.

OHI Field Contents 00 Optional field and extension field are missing. 01 The Optional field is present, the Extension field is absent, and the Optional field is 1 byte long. 10 The Optional field is present, the Extension field is absent, and the Optional field is 2 bytes long. 11 Optional and Extenstion fields exist and the length of the Optional and Extension fields 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.

10 is a diagram illustrating a detailed configuration of an optional field according to an embodiment of the present invention.

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

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. In more detail, 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. The remaining area 2322 of 5 bits except the EXT_TYPE field 2321 of 1 byte of the optional field 2320 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 the meaningless data may be randomly determined in various ways according to system design. In addition, such padding is not necessarily filled with only zero, but may be filled with only one, or may be filled with a meaningless combination of zeros and ones. However, the padding according to an embodiment of the present invention will be described with an example of filling with only zero.

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, wherein the EXT_TYPE field ( The length of 2321 is 3 bits. The remaining 5 bit region 2322 and 8 bit region 2323 except for the EXT_TYPE field 2321 among the 2 bytes of the optional field 2320 may include preset information or padding. The remaining 5 bit region 2322 and the 8 bit region 2323 may include preset information or padding according to information stored in the EXT_TYPE field 2321. Here, padding means meaningless data, and the 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. In this case, 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, wherein the EXT_TYPE field ( The length of 2321 is 3 bits.

However, when the OHI field 2314 is set to 11, a value corresponding to the type of the extension field 2330 is set in the EXT_TYPE field 2321. For example, when padding is stored in the extension field 2330, the EXT_TYPE is stored. The field 2321 stores a value indicating that padding is stored in the extension field 2330. If 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 (LSB) field 2325 may be 8 bits.

On the other hand, in the above-described EXT_TYPE field 2321, the EXT_TYPE field 2321 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" may be additionally stored in the Optional field 2320 in addition to the bit sequence of "00000". 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 arranged. Herein, when the EXT_TYPE field 2321 is set to 000, padding (that is, a bit sequence of 00000 or a bit sequence of 00000000) is filled in the Optional field 2320, but this is only an example. The EXT_TYPE field 2321 is described. Of course, the meaning of the value set in the () 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 if such an EXT_LEN (MSB) field 2325 is present, the Optional field 2320 may correspond to the EXT_LEN (LSB) field 2324. The EXT_LEN (MSB) field 2325 includes a total of 13 bit EXT_LEN fields. Accordingly, when the length of the extension field 2330 is less than or equal to the 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 generally changes according to values set in the MODE field 2311 and the OHI field 2314 will be described with reference to FIGS. 11 through 16D.

11 to 16D illustrate 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 a short pointer length. Therefore, the base header 2310 includes only the pointer (LSB) field 2312 and the MODE field 1211 is set to 0. In this case, the Optional field 2320 and the Extension field 2330 are not included in the packet 2300, and as a result, the packet 2300 includes a base header 2310 and a payload 2340 having a length of one byte. Done.

Referring to FIG. 12, when the MODE field 2311 is set to 1, it means a long pointer length. Thus, the base header 2310 includes a pointer (LSB) field 2312 and a pointer (MSB) field 2313. It may further include an OHI field 2314 including information on the existence of an optional field 2320 and an extension field 2330.

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 and 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. It includes a base header 2310 and the payload 2340 having a.

Referring to FIG. 13, when the MODE field 2311 is set to 1, it means a long pointer length. Thus, the base header 2310 includes a pointer (LSB) field 2312 and a pointer (MSB) field 2313. It may further include an OHI field 2314 including information on the existence of an optional field 2320 and an extension field 2330.

Accordingly, the packet 2300 includes a base header 2340 having a length of 2 bytes. In FIG. 13, however, 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. 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 2232.

Referring to FIG. 14, when the MODE field 2311 is set to 1, it means a long pointer length. Thus, the base header 2310 includes a pointer (LSB) field 2312 and a pointer (MSB) field 2313. It may further include an OHI field 2314 including information on the existence of an optional field 2320 and an extension field 2330.

Accordingly, the packet 2300 includes a base header 2340 having a length of 2 bytes. In FIG. 14, however, the OHI field 2314 is set to 10 so that 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. 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 2232, 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. Thus, the base header 2310 includes a pointer (LSB) field 2312 and a pointer (MSB) field 2313. In addition, the OHI field 2314 including information on the existence 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. In FIG. 15, however, the OHI field 2314 is set to 11, so that a 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.

In FIG. 15, the Optional field 2320 includes both the EXT_LEN (LSB) field 2324 and the EXT_LEN (MSB) field 2325. However, the Optional field 2320 has an EXT_LEN (LSB) field ( 2324, in which case the packet 2300 may include 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. ) May be included.

In the above-described example, the Optional field 2320 has at least one of a 5-bit padding field 2232 and an 8-bit padding field 2323 is described as an example. However, the optional field 2320 may include preset data instead of padding. In addition, the EXT_TYPE field 2321 may include a value indicating preset data.

16A to 16D, when the OHI field 2314 is set to 11, data filled in the Optional field 2320 and the Extension field 2330 may vary according to a value set in the EXT_TYPE field 2321. Indicates.

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

In this case, when the TYPE field 2321 is set to 001, the Optional field 2320 may include only the EXT_LEN (LSB) field 2324, and the Extension field 2330 may include an ISSY field 2331 and a padding 2332. Can be. Here, the ISSY field 2331 is an example for explaining the case where the extension field 2330 includes preset data. This ISSY field (Input Stream Synchronization) 2331 is used to transmit the clock counter value according to the clock modulation ratio and to reproduce the correct timing for restoring the output stream by the receiver.

Also, 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 a padding 2332.

Of course, the extension field 2330 is preset data and may include various data instead of 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 In-band Signal TYPE A field 2334 and padding 2332, and referring to FIG. 16D, if 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, and the extension field 2330 may include an in-band signal type B field 2335 and a padding 2332.

On the other hand, the ALP packet and the baseband packet described above may vary in name depending on the system. For example, the ALP packet and the baseband packet may be named 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 having different structures, which will be described in detail with reference to FIGS. 17 to 25. In addition, the Optional field and the Extension field will be described to include fields having different structures. The description of the fields included in the base field, which will be described later, may correspond to those described in FIG. 9, but will be described again using general terms. Shall be.

Referring back to FIG. 6, the transmitter 100 includes a packet generator 110, a signal processor 120, and a transmitter 130, and the packet generator 110 is based on an input packet and includes a header and a pay page. A packet containing the load may be generated.

Here, the input packet may be, for example, 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 name may vary according to a system. For example, the above-described ALP packet and BBP packet may be named as a BBP packet and a baseband frame (BBB), respectively, depending on the system.

Meanwhile, the packet, that is, the 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 can be set according to the selected code rate and code length.

The input packet, that is, the ALP packet, may include one of an IP packet, a TS packet, and a signaling packet, or a combination thereof. Specifically, an input packet, an TS packet, and various types of IP packets may be included. Data can be encapsulated and generated as ALP packets for transmission to each PLP, which 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 kinds of data.

The signal processor 120 may signal-process the generated packet. In detail, the signal processor 120 may process the packet to generate a transmission frame. In addition, the signal processor 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 the preamble into which the L1 signaling information is inserted may include an L1 pre-signaling region and an L1 post signaling region. The L1 post signaling region also includes a configurable field and a dynamic field.

Although not shown in the drawings, the signal processor 120 may include the bit interleaved and coded modulation (BICM) blocks 12000 and 12000-1 and the 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 a signal processed packet to a receiver (not shown).

In detail, 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 modulates the generated packet into an RF signal, and transmits the RF signal to a receiving device (not shown).

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

In addition, the header 4100 of the packet 4000 may 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 necessarily includes a base field, and an optional field. The presence of may vary depending on the value of the control field included in the base field. In addition, depending on the value of the control field included in the Optional field, the existence of the Extension field can be selected.

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 is a diagram showing the structure of a packet according to another embodiment of the present invention.

Referring to FIG. 17, the 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, one input packet may be split and included in payloads of different packets like the first input packet among the plurality of input packets 4201. The base field may inform the start point of the input packet through a 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 may be a first value indicating that the base field is of a first length, that is, 1 byte, or a second value indicating that the base field is of a second length, that is, 2 bytes. It can be set to a value.

In particular, when the first field 4111 is set to the first value and the base field is 1 byte, the base field is LSB (least) of the pointer value indicating the first value of each start point of the input packet included in the payload 4200. only a second field indicating significant bits), and accordingly, the pointer value may represent only up to a predetermined value.

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. And a third field indicating the most significant bits (MSB) of the pointer value. Accordingly, the pointer value may represent up to a predetermined value or more.

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

For example, when 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 input point corresponding to the start point of the corresponding input packet is matched. The pointer value representing the value can be zero. That is, since the start point of the input packet may be numerically calculated based on the start point of the payload 4200, a pointer indicating a value corresponding to the start point of the corresponding input packet starting with the start point of the payload 4200. The value can be zero.

As shown in FIG. 17, when the first input packet is divided into the first input packet 4201 and included in the payload 4200, the starting point of the first input packet exists in the previous packet and the corresponding payload is present. Since it does not exist at 4200, the first value of each start point of the input packet included in the payload 4200 is a start point of the second input packet. Accordingly, the pointer value indicating the 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. .

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 when 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. If the MODE field is set to 0, the length of the base field may be 1 byte. If the MODE field is set to 1, it may represent that the length of the base field is 2 bytes.

Further, the MODE field may indicate the presence of the third field 4113 indicating the MSB of the pointer value and the existence of the fourth field indicating the extension mode of the header. Specifically, when the MODE field is set to 0, the base field indicates the pointer. It 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 the pointer (LSB) field may have a size of 7 bits. Accordingly, when the MODE field is set to 0, the pointer value can only represent up to 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 extended to 8191 bytes through 13 bits including the pointer (LSB) field (7 bits) and the pointer (MSB) field (6 bits). 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 fourth field indicating the pointer (MSB) field and the extension mode of the header 4100 may be included in the base field only when the MODE field is set to '1'.

Accordingly, when the pointer value indicating the first value of the start 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 set to 0. Pointer value indicating that the first field of the input packet in the payload 4200 of the packet 4000 has a size of 1 byte so that the base field includes only the second field 4112, that is, the pointer (LSB) field. If this is more than 128 bytes, the first field 4111, that is, the MODE field is set to 1, and the base field is the second field 4112, that is, the pointer (LSB) field and the third field 4113, that is, the pointer MSB. The field and the fourth field are included so that the base field has a total size of 2 bytes.

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 input packet cannot be defined, so the pointer value is 8191 and accordingly, the MODE field is 1. The base field has a size of 2 bytes.

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

18 is a diagram showing the detailed configuration of the header shown in FIG. Referring to FIG. 18, as described above, the header 4100 may include a base field 4110, and may further include an optional field 4120 and an extension field 4130, which may be described later. The inclusion may be determined by the fourth field 4114 indicating the extension mode of 4100.

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 the second value, the base field 4110 may indicate an extension mode of the second field 4112, the third field 4113, and the header 4110. Four fields 4114, whereby the length of the base field 4110 is one bit of the first field 4111, seven bits of the second field 4112, six bits of the third field 4113, and so on. It can be seen that it has a total size of 2 bytes including 2 bits of the fourth field 4114.

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. The fourth field 4114 may be optional. It may include at least one of the presence 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 indicates that a third value indicating that the Optional field 4120 and the Extension field 4130 are absent, the Optional field 4120 exists, and that the length of the Optional field 4120 is 1 byte. The fourth value, the optional field 4120 is present and the fifth value indicating that the optional field 4120 is 2 bytes in length, and the optional field 4120 is present, and 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 extension 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, the information indicated by the value set in the OFI field may be summarized as shown in Table 2 below.

OFI Contents 00 No Extension Mode:
Optional field and extension field are missing. 01 Short Extension Mode:
The Optional field is present and the Optional field is 1 byte long. 10 Long Extension Mode:
The Optional field is present and the Optional field is 2 bytes long. 11 Mixed Extension Mode:
The Optional field exists, the Optional field is 2 bytes long, and the extension field contains multiple extension payloads.

In detail, 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.

19 is a diagram illustrating a detailed configuration of an optional field according to another embodiment of the present invention.

Referring to FIG. 19, when the fourth field 4114 is set to '00', where the fourth field 4114 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 "01", which is the fourth value, 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. 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, which 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, the length of the extension field 4130 is 0. Therefore, the extension field 4130 does not exist in the header 4100.

Meanwhile, in FIG. 19, when the fourth field 4114 is set to “01” as the fourth value, 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 separate, but this is merely shown separately to illustrate that the Optional field 4120 may have a size of 1 byte or may have a size of 2 bytes, and is actually a fourth. If the field 4114 is set to "01" as the fourth value, the optional field 4120 has a size of 1 byte, so that the extension field 4130 is added to the optional field 4120 in succession, and thus the optional field 4120. ) And the extension payload 4131 included in the extension field 4130 are continuously arranged.

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 indicates a field (EXT_TYPE field) 4121 indicating the type of the extension payload 4132 included in the extension field 4130, and an LSB part of the field indicating the length of the extension field 4130. A field (EXT_LEN (LSB) field) 4123 and a field (EXT_LEN (MSB) field) 4124 indicating the MSB part of the field indicating the length of the extension field 4130 may be included. Here, as described above, since the EXT_TYPE field 4121 is defined as the fifth field and the field indicating the length of the extension field 4130 is defined as the sixth field, the EXT_LEN (LSB) field 4123 is the sixth field. And an EXT_LEN (MSB) field 4124 may be defined to represent 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, which will be described in detail later.

Also, 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 (LSB) field 4124 may have an extension field (4124). It may have a size of 8 bits of the MSB part of the total 13 bits to indicate the length of 4130). The total 13-bit field connecting 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, when the total 13-bit field connecting the EXT_LEN (LSB) field 4123 and the EXT_LEN (MSB) field 4124 is 0, the length of the extension field 4130 is 0. Therefore, the header 4100 has an extension. Field 4130 does not exist.

In addition, when the fourth field 4114 is set to '11', which is the sixth value, this is 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. The presence and length of the extension field 4130 and the structure of the extension field 4130 may be determined by the fields included in the optional 4120.

Specifically, the Optional field 4120 is a field (NUM_EXT field) 4125 indicating the number of extension payloads 4133 included in the extension field 4130, and an LSB of the field indicating the length of the extension field 4130. A field indicating the part (EXT_LEN (LSB) field) 4126 and a field indicating the MSB part of the 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 extension payloads 4133 that are not 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 among a total of 13 bits for indicating the length of the extension field 4130, and the EXT_LEN (LSB) field 4127 is an extension field ( It may have a size of 8 bits of the MSB part of the total 13 bits to indicate the length of 4130).

On the other hand, with regard to the length of the extension field 4130 that can be represented by a total 13-bit field connecting the EXT_LEN (LSB) field 4126 and the EXT_LEN (MSB) field 4127, the structure of the extension field 4130 is described. Let's explain together.

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

When the fourth field 4114 is set to the 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 the sixth value, that is, “11”, this means Mixed Extension Mode. Accordingly, the extension field 4130 may include a plurality of extension payloads. (Extension Payload 1 (4145) ... Extension Payload N (4146)), where the Extension field 4130 may include a plurality of Extension Payloads (Extension Payload 1 (4145) ... Extension Pay Load N (4146)) A plurality of fields (EXT_TYPE 1 (4141) ... EXT_TYPE N (4143)) representing each type and a plurality of Extension payloads (Extension payload 1 (4145) ... Extension payload N (4146)) A plurality of fields indicating the length (EXT_LEN 1 field 4142... EXT_LEN N field 4144) may be included. As described above, since the extension field 4130 may include two to seven extension payloads, N may range from 2 to 7.

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

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

Accordingly, when the extension field 4130 includes N extension payloads, 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 associated with each extension payload. 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, if the value of the EXT_LEN field is 0, there is no extension payload, and in this case, the length of the extension field 4130 must be at least 4 bytes.

As a result, the length of the extension field 4130 that can be represented by a total of 13 bit fields connecting the EXT_LEN (LSB) field 4126 and the EXT_LEN (MSB) field 4127 described with reference to FIG. 19 is 4 bytes to the 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 and the EXT_LEN N field 4144 illustrated in FIG. 25 may include a 5-bit EXT_LEN (LSB) field and an 8-bit EXT_LEN (MSB) field. Accordingly, one 2-byte size header for one extension payload includes 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. It will include.

In addition, the extension field 4130 is set when the fourth field 4114 is set to one of the fourth value and the fifth value, and the length of the extension payload included in the extension field 4130 is smaller than the length of the extension field 4130. The 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 "01" as the fourth value, the actual length of the extension payload 4131 included in the extension field 4130 is defined by the EXT_LEN field 4122. When the length of the extension field 4130 is smaller than the length of the extension field 4130, the extension field 4130 may include the extension payload 4131 and include padding in the remaining portions. Here, padding means meaningless data, and the meaningless data may be randomly determined in various ways according to system design. In addition, such padding is not necessarily filled with only zero, but may be filled with only one, or may be filled with a meaningless combination of zeros and ones. However, the padding according to an embodiment of the present invention will be described with an example of filling with only zero.

For example, in FIG. 19, when the fourth field 4114 is set to “10” as the fifth value, the actual length of the extension payload 4132 included in the extension field 4130 is the EXT_LEN (LSB) field 4123. If less than the length of the extension field 4130 defined by the < RTI ID = 0.0 > EXT_LEN (MSB) < / RTI > field 4124, the extension field 4130 contains the extension payload 4132 and includes padding in the remaining portions. can do.

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

For example, referring to FIG. 25, when the fourth field 4114 is set to the sixth value “11”, the plurality of extension payloads 1145 included in the extension field 4130 may be used. Extension payloads N (4146)) A plurality of fields representing each type (EXT_TYPE 1 (4141) ... EXT_TYPE N (4143)), a plurality of extension payloads (Extension payload 1 (4145) ... Extension pay A plurality of fields (EXT_LEN 1 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. A plurality of fields indicating the type of each extension payload (EXT_TYPE 1 (4141) ... EXT_TYPE N (4143)), and a plurality of fields indicating the length of each of the plurality of extension payloads (EXT_ LEN 1 field (4142) ... EXT_LEN N field (4144) and a plurality of payloads (Extension payload 1 (4145) ... Extension payload N (4146)) and the remaining portion contains padding can do.

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

20 to 24 illustrate a structure of a packet according to various embodiments of the present disclosure.

Referring to FIG. 20, when the first field 4111 is set to the first value, the base field 4110 includes only the second field 4112 indicating the least significant bits (LSB) of the pointer value, and the optional field 4120. ) And the extension field 4130 are not included in the packet 4000, and 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 may include a second field 4112 indicating the least significant bits (LSB) of the pointer value, and the most significant MSB of the pointer value. and a third field 4113 indicating the bits, and further include a fourth field 4114 indicating the extension mode of the header 4100.

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 the 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 may include a base field 4110 and a payload 4200 having a size of 2 bytes.

Referring to FIG. 22, if the first field 4111 is set to a second value, the base field 4110 may include a second field 4112 indicating the least significant bits (LSB) of the pointer value, and the most significant MSB of the pointer value. and a third field 4113 indicating the bits, and further include a fourth field 4114 indicating the extension mode of the header 4100.

Accordingly, the packet 4000 includes a base field 4110 having a size of 2 bytes. In FIG. 22, however, 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 are provided. ) 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. 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 may include a second field 4112 indicating the least significant bits (LSB) of the pointer value, and the most significant MSB of the pointer value. and a third field 4113 indicating the bits, and further include a fourth field 4114 indicating the extension mode of the header 4100.

Accordingly, the packet 4000 includes a base field 4110 having a size of 2 bytes. In FIG. 23, however, since the fourth field 4114 is set to the fifth value, that is, "10", the optional field 4120 and the extension field 4130 having a size of 2 bytes are included in the packet 4000. Will be. Herein, 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 0 to 2 ¹³ -1 bytes. Can be. 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 may include a second field 4112 indicating the least significant bits (LSB) of the pointer value, and the most significant MSB of the pointer value. and a third field 4113 indicating the bits, and further include a fourth field 4114 indicating the extension mode of the header 4100.

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 the 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. Will be. Herein, 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 0 to 2 ¹³ -1 bytes. Can be. 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. 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 with reference to FIG. 25.

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

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", this indicates that a counter function can be performed. Specifically, a preset field having a size equal to a value included in the EXT_LEN field is extended to the extension field 4130. It can be included as a payload. In this case, the preset field may perform a function of identifying one by one for each of the plurality of packets included in the current PLP, and the counter value may increase linearly from zero.

For example, when the fourth field 4114 is set to "01", which is the fourth value, and the EXT_LEN field includes a value of 1, the preset field has a size of 1 byte and thus the counting value is 0. It can have a value from 255.

Here, the preset packet that performs the counter function can be used independently for each PLP. When the counter value reaches a maximum value, the counter value of the next packet is reset to 0 and then increments 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, which may be performed before the packet is assigned to a specific RF channel.

On the other hand, the above description is equally applicable to EXT_TYPE 1 (4141) ... EXT_TYPE N (4143) included in the Extension field 4130 when the fourth field 4114 is set to the sixth value, that is, "11". Can be.

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

In detail, when the fourth field 4114 is set to the fourth value, that is, "01" or the fifth value, that is, "10", the optional field 4120 may include an extension payload included in the extension field 4130. The fifth field indicating the type, that is, the sixth field indicating the length of the EXT_TYPE field 4121 and the extended field 4130 (if the fourth field 4114 is the fourth value, it is the EXT_LEN field 4122 and the fourth field ( If 4114) is the fifth value, the method further includes an EXT_LEN (LSB) field 4123 and an EXT_LEN (MSB) field 4124), and if the fifth field, that is, the EXT_TYPE field 4121 is set to a preset value, The extension field 4130 may be 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 filled with padding as defined in Table 3, and thus, the extended field 4130. Will be padded with padding.

As another example, when the fourth field 4114 is set to a fourth value, that is, "01", and the EXT_LEN field 4122 includes a value indicating that the length of the extension field 4130 is 0 bytes, This may be regarded as a case where one 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 one-byte Optional field 4120 soon serves as padding of one byte.

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. In the case of including the indicating value, this may be regarded as a case in which two bytes of padding are included in the header 4100 when compared to the case where the fourth field 4114 is set to the 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 the sixth value, that is, “11”, as described above, the extension field 4130 may be filled with a plurality of extension payloads, and padding may be filled in the remaining portions. In such a case, EXT_TYPE 1 (4141) ... EXT_TYPE N (4143) need not be individually set to "111".

26A is a block diagram illustrating a configuration of a receiving apparatus 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 receiver 210 receives a frame including data mapped to at least one signal processing path. In detail, 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 about an input type of an input stream input to the transmitting device and information about a data type mapped to at least one signal processing path. Here, the information about 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, a detailed description thereof will be omitted.

The information extracting unit 220 may extract a header from the packet, and extract information indicating the start point of the data packet from the extracted header and information regarding the existence of additional fields.

The information indicating the start point of the data packet and the information on the existence of the additional field in the payload included in the header have already been described in the section on the reception apparatus 100, and thus a detailed description thereof will be omitted.

The signal processor 230 may signal-process the data packet included in the payload based on the information indicating the start point of the extracted data packet and the information on the existence of the additional field. That is, it is possible to accurately detect the starting point of the data packet in the payload based on the information indicating the starting point of the data packet, and perform decoding and decoding from the starting point of the data packet. In addition, the signal processor 230 may determine whether the received packet includes an Optional field and an Extension field based on the information about the existence of the additional field, and may 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 about the existence 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 about the existence of the additional field may include information indicating at least one existence 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.

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

In detail, the signal processor 230 generates a baseband packet by processing a frame received through the receiver 210, and extracts header information from the generated baseband packet.

The signal processor 230 may reconstruct the stream, that is, the first input stream input to the above-described transmitting apparatus 100 by processing the payload data included in the baseband packet based on the extracted header information.

Meanwhile, the receiver 200 according to another embodiment of the present invention includes a receiver 210, an information extractor 220, and a signal processor 230, and the receiver 210 includes a header and a payload. The packet may include a packet, and the information extractor 220 may extract a header from the packet and extract information included in the header. The signal processor 230 may extract an input packet included in the payload based on the extracted information. Signal processing. Here, since the detailed description of the receiver 210, the information extractor 220, and the signal processor 230 has been made, the detailed description thereof will be omitted.

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

FIG. 26B is a block diagram for describing in detail a signal processor according to an exemplary embodiment. Referring to FIG.

According to FIG. 26B, the signal processor 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, and performs sync detection. When the sink is detected, the demodulator 231 recognizes whether the frame currently received from the signaling information stored in the sync area is a frame including necessary service data. . For example, it may be recognized whether a mobile frame or a fixed frame is received.

In this case, when the OFDM parameters for the signaling area and the data area are not predetermined, the OFDM parameters for the signaling area and the data area stored in the sink area are obtained, and the signaling area and the data area immediately following the sink area are acquired. 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 a parameter such as an FEC scheme, a modulation scheme, or the like for the data stored in each data region using the signaling information. In addition, the signal decoder 232 may calculate the position of the required data based on the data information included in the header. That is, it is possible to calculate where 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 information. Specifically, the stream generator 233 may include de-jitter buffers that may regenerate the correct timing for reconstructing the output stream based on various information. Accordingly, the delay for the synchronization between the plurality of PLPs can be compensated.

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

Referring to FIG. 27, the receiver 4400 may include a controller 4410, an RF receiver 4420, a demodulator 4430, and a service regenerator 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 may be transmitted through one or more PLPs belonging to one or more RF channels for each component constituting the service, but for the convenience of description, all data necessary for reproducing one service is transmitted through one RF channel. Assume that it is transmitted in one PLP. That is, the service has a unique data acquisition path for reproduction of the service, and the data acquisition path is specified by the RF channel and the PLP.

The RF receiver 4420 detects an RF signal in the RF channel selected by the controller 4410, performs signal processing on the RF signal, and delivers the extracted OFDM symbols to the demodulator 4430. Here, the signal processing may include synchronization, channel estimation and equalization, and the information for signal processing may be included in a specific OFDM symbol promised by the transmitter / receiver or in advance of an OFDM symbol according to its use and implementation. Is delivered from the receiver.

The demodulator 4430 performs signal processing on the OFDM symbols to extract a user packet and delivers the user packet to the service reproducer 4440. The service reproducer 4440 reproduces and outputs a service selected by a user using the user packet. In this case, the format of the user packet may vary depending on a service implementation method. For example, a TS packet or an IPv4 packet may be used.

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

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

The frame demapper 4431 selects the OFDM cells constituting the FEC blocks belonging to the selected PLP in the frame composed of the OFDM symbols based on the control information transmitted from the controller 4435, and transmits the OFDM cells to the BICM decoder 4342, and also 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 signals the OFDM cell corresponding to the FEC block including the L1 signaling, extracts the L1 signaling bits, and transfers the L1 signaling bits to the controller 4435. In this case, signal processing may include extracting a log-likelihood ratio (LLR) value for LDPC code decoding in an OFDM cell and decoding an LDPC code using the extracted LLR value.

The controller 4435 extracts the L1 signaling table from the L1 signaling bits and controls the operations of the frame demapper 4431, the BICM decoder 4342, and the output processor 4435 using the values of the L1 signaling table. In FIG. 28, for convenience of description, the BICM decoder 4432 for L1 signaling does not use the control information of the controller 4435. However, when the L1 signaling has a hierarchical structure similar to the above-described structures of L1-PRE and L1-POST, the BICM decoder 4432 for L1 signaling may be configured with one or more BICM decoding blocks, and BICM decoding blocks and frames. It is apparent that the operation of the demapper 4431 can be controlled by higher layer L1 signaling information.

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

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

29 is a flowchart schematically illustrating an operation of a receiver from a time point at which a user selects a service to reproduction of a actually selected service according to an embodiment of the present invention.

It is assumed that service information on all services that can be selected in the initial scan (S4600) has been obtained before the user's service selection (S4610). Here, the service information may include information about an RF channel and a PLP through which data necessary for reproducing a specific service in the current broadcast system is transmitted. Here, as an example of the service information, there is PSI / SI (Program-Specific Information / Service Information) of MPEG2-TS, and can be generally 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 performs RF signal detection (S4630). The service information may be used in the process of changing to the 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). The 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 demapping the transmission frame to select OFDM cells belonging to the PLP, and extracting a log-likelihood ratio (LLR) value for LDPC code / decoding from the OFDM cell. The method may include decoding an LDPC code using the extracted LLR value.

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

30 is a flowchart illustrating a control method of a transmitting apparatus according to an embodiment of the present invention.

The control method of the transmitter of FIG. 30 generates a packet including a header and a payload based on an input packet (S3510).

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 of a first length or a second value indicating that the base field is of a second length, and the first field is a second value. If set to, the base field indicates a second field indicating the least significant bits (LSB) of the pointer value indicating the first value of each start point of the input packet included in the payload and the most significant bits (MSB) of the pointer value. It may include a third field.

The first field, the second field, and the third field may be included in a base field constituting a 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 whether an optional field exists, a length of an optional field, and a structure of an extension field.

In addition, the fourth field may include a third value indicating that the Optional field and the Extension field are absent, a fourth value indicating that the Optional field exists and the length of the Optional field is 1 byte, the Optional field exists, and the length of the Optional field is 2 The fifth value indicating that the byte and the Optional field exist, the Optional field may be set to one of the sixth values indicating that the length of the Optional field is 2 bytes, and that the Extension field includes a plurality of extension payloads.

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

In addition, when the fourth field is set to the fifth value, the Optional field indicates 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 length of the extension field. It may include a field indicating the MSB part of the field.

In addition, if the fourth field is set to the sixth value, the Optional field may include a field indicating the number of the plurality 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 a length of the extension field. It may include a field indicating the MSB part of the field indicating.

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.

In addition, the extension field includes the extension payload 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 smaller than the extension field length. The remaining part may include padding.

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.

On the other hand, the control method of the transmitting apparatus according to another embodiment of the present invention, a header including a base header including information indicating the start point of the data packet in the payload and information on the existence of the additional field, and the payload Generates a packet comprising a.

Here, the information indicating the start point of the data packet may include information about the existence 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 exists.

In addition, the information about the existence of the additional field may include information indicating at least one existence 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 existence of the additional field is a first value indicating that the Optional field and the Extension field is absent, a second value indicating that the Optional field is present and the Extension field is absent and the length of the Optional field is 1 byte, Optional field Is a third value indicating that the Extension field is absent, the Optional field is 2 bytes long, and one of the fourth values indicates that the Optional and Extension fields are present, and that the Optional and Extension fields are longer than 2 bytes. It may include.

In addition, the Optional field may include information indicating the length of the extension field when the information on the existence of the additional field is set to the fourth value.

The 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.

Thereafter, the signal-processed frame is transmitted.

31 is a flowchart illustrating a control method of a receiving apparatus according to an embodiment of the present invention.

In the control method of the receiving apparatus illustrated in FIG. 31, a stream including a packet including a header and a payload is received (S3610).

Then, the 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 of a first length or a second value indicating that the base field is of a second length, and the first field is a second value. When set to, the base field includes a second field indicating the least significant bits (LSB) of the pointer value indicating the first value of each start point of the input packet included in the payload and the most significant bits (MSB) of the pointer value. It may include a third field indicating.

On the other hand, the control method of the receiving apparatus according to another embodiment of the present invention, receives a stream including a packet including a header and a payload.

Then, the header is extracted from the packet, and information indicating the start point of the data packet in the payload and information regarding the existence of the additional field are extracted from the extracted header.

The data packet included in the payload is signal-processed based on the information indicating the start point of the extracted data packet and the information on the existence of the additional field.

Here, the information indicating the start point of the data packet may include information about the existence 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 about the existence of the additional field may include information indicating at least one existence 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 disclosure, various types of data may be mapped to a transportable physical layer, and data processing efficiency may be increased.

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

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

Also, as an example, receiving a stream including a packet including a header and a payload, extracting a header from the packet, and extracting the header from the extracted header, the information indicating the starting point of the data packet in the payload and the presence of additional fields A non-transitory readable stored program having a step of extracting information relating to 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 existence of additional fields. A non-transitory computer readable medium may be provided.

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

In addition, although the bus is not shown in the above-described block diagram of the transmitting apparatus and the receiving apparatus, communication between each component in the transmitting apparatus and the receiving apparatus may be performed through a bus. In addition, each device may further include a processor such as a CPU, a microprocessor, and the like for performing the above-described various steps.

In addition, although the preferred embodiment of the present invention has been shown and described above, the present invention is not limited to the above-described specific embodiment, the technical field to which the invention belongs without departing from the spirit of the invention claimed in the claims. Of course, various modifications can be made by those skilled in the art, and these modifications should not be individually understood from the technical spirit or the prospect of the present invention.

100: transmitter 110: packet generation unit
120: signal processor 130: transmitter

Claims (2)

A receiver configured to receive input data from an upper layer;
A packet generator configured to generate a packet including a header and a payload based on the received input data and encoding parameters;
A processing unit encoding the generated packet and interleaving the encoded packet; And
And a transmitter configured to transmit a transmission signal generated based on the interleaved packet.
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 is of a first length, and the second value indicates that the second field is of a second length,
If the first field includes the first value, the second field includes a least significant bit (LSB) field,
If 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 includes 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 at the payload,
And if the first field includes the second value, the header includes a third field including a value indicating an extension mode of the header. In the broadcast signal transmission method of the broadcast transmission device,
Receiving input data from an upper layer;
Generating a packet comprising a header and a payload based on the received input data and encoding parameters;
Encoding the generated packet and interleaving the encoded packet; And
Transmitting a transmission signal generated based on the interleaved packet;
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 is of a first length, and the second value indicates that the second field is of a second length,
If the first field includes the first value, the second field includes a least significant bit (LSB) field,
If 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 includes 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 at the payload,
And if the first field includes the second value, the header comprises a third field including a value indicating an extension mode of the header.

Images