BR112017009808B1 - TRANSMISSION APPARATUS, RECEIVING APPARATUS, TRANSMISSION METHOD OF A TRANSMISSION APPARATUS, AND RECEIVING METHOD OF A RECEIVING APPARATUS - Google Patents

Abstract

TRANSMISSION APPARATUS, RECEIVING APPARATUS, TRANSMISSION METHOD OF A TRANSMISSION APPARATUS, AND RECEIVING METHOD OF A RECEIVING APPARATUS. A transmitting apparatus, a receiving apparatus and methods of controlling the same are provided. The transmitting apparatus includes: at least one processor configured to implement a packet generator that generates a packet including a header and a payload based on a plurality of input packets; and a signal processor that processes signals from the generated packet, and a transmitter configured to transmit the signal-processed packet. A base field that configures the header includes a first field defined as a first value representing that the base field is a first length or a second value representing that the base field is a second length.

Description

Technical Field

[0001] Apparatus and methods consistent with the exemplary embodiments refer to a Transmitting apparatus, a receiving apparatus, and a method of signaling the same, which transmit data by mapping the data to at least one signal processing path.

Background of the Technique

[0002] In the information-oriented society of the 21st century, broadcast communication services are entering an era of digitalization, multichannel, broadband and high quality. In particular, as high-quality digital television (TV), portable multimedia players (PMP) and portable broadcasting devices have been increasingly used in recent years, even in digital broadcasting services, a demand for Various reception methods have been increased.

Disclosure of the Invention Technical problem

[0003] In a real state where the standard group has established various standards according to demands to provide various services to satisfy user needs, it is necessary to find methods to provide better services with better performance. Solution to the Problem

[0004] Exemplary embodiments can overcome the above disadvantages and other disadvantages not described above. However, exemplary embodiments are not necessary to overcome the disadvantages described above, and may not overcome any of the problems described above.

[0005] Exemplary embodiments provide a transmission apparatus, a reception apparatus and a control method, capable of generating a structure with a format suitable for transmitting various types of data.

[0006] According to one aspect of an exemplary embodiment, a transmission apparatus is provided that may include: at least one processor configured to implement a packet generator that generates a packet that includes a header and a payload based on a plurality of input packets, and a signal processor processing the generated packet signal; and a transmitter configured to transmit the processed signal packet. A base field that configures the header includes a first field defined as a first value representing that the base field is a first length or a second value representing that the base field is a second length. When the first field is set to the second value, the base field comprises a second field that represents the least significant bits (LSB) of the pointer value indicating a first starting point between the respective starting points of the input packets included in the payload and a third field that represents the most significant bits (MSB) of the pointer value.

[0007] Here, the base field comprises a fourth field representing a header extension mode, and the fourth field comprises at least one of information about whether an optional field is present, a length of the optional field, and a structure of an extension field.

[0008] Additionally, the fourth field is defined as one of a third value representing that the optional field and the extension field are not present, a fourth value representing that the optional field is present, and a length of the optional field is 1 byte, a fifth value that represents that the optional field is present and the length of the optional field is 2 bytes and a sixth value that represents that the optional field is present, the length of the optional field is 2 bytes and the field of extension has a structure comprising a plurality of extension payloads.

[0009] Additionally, when the fourth field is defined as the fourth value or the fifth value, the optional field further includes a fifth field that represents an extension payload type included in the extension field and a sixth field that represents a length of the extension field, and when the fifth field is set to the default value, the extension field is completely filled for padding.

[00010] Additionally, when the fourth field is set to the fifth value, the optional field comprises a field representing a type of an extension payload included in the extension field, a field representing an LSB portion of a length of the extension field and a field that represents an MSB portion of the length of the extension field.

[00011] Furthermore, when the fourth field is set to the sixth value, the optional field comprises a field representing a number of a plurality of extension payloads included in the extension field, a field representing an LSB portion of a length of the extension field, and a field representing an MSB portion of the length of the extension field.

[00012] Furthermore, the extension field comprises a plurality of fields representing respective types of the plurality of extension payloads and a plurality of fields representing respective lengths of the plurality of extension payloads.

[00013] Furthermore, when the fourth field is defined as a fourth value and a fifth value and a length of an extension charge included in the extension field is less than a length of the extension field, the extension field comprises the charge useful extension and filling.

[00014] Furthermore, when the fourth field is set to a sixth value, the extension field comprises a plurality of extension and padding payloads.

[00015] According to another aspect of an exemplary embodiment, a receiving apparatus is provided that may include: a receiver configured to receive a current that includes a packet that includes a header and a payload; and at least one processor configured to implement an information extractor that extracts the packet header and extracts information included in the header, and a signal processor that processes signals from a plurality of input packets included in the payload based on the extracted information. A base field that configures the header includes a first field defined as a first value representing that the base field is a first length or a second value representing that the base field is a second length. When the first field is set to the second value, the base field comprises a second field that represents the least significant bits (LSB) of the pointer value indicating a first starting point between the respective starting points of the input packets included in the payload and a third field that represents the most significant bits (MSB) of the pointer value.

[00016] According to yet another aspect of an exemplary embodiment, there is provided a method of controlling a transmission apparatus that may include: generating a packet that includes a header and a payload based on a plurality of input packets; process signals from the generated packet; and transmit the processed signal packet. A base field that configures the header includes a first field defined as a first value representing that the base field is a first length or a second value representing that the base field is a second length. When the first field is set to the second value, the base field comprises a second field representing least significant bits (LSB) of the pointer value that indicates a first starting point between the respective starting points of the input packets included in the payload and a third field that represents most significant bits (MSB) of the pointer value.

[00017] Furthermore, the base field comprises a fourth field representing a header extension mode, and the fourth field comprises at least one of information about whether an optional field is present, a length of the optional field, and a structure of an extension field.

[00018] Additionally, the fourth field is defined as one of a third value representing that the optional field and the extension field are not present, a fourth value representing that the optional field is present, and a length of the optional field is 1 byte, a fifth value that represents that the optional field is present and the length of the optional field is 2 bytes and a sixth value that represents that the optional field is present, the length of the optional field is 2 bits and the field of extension has a structure comprising a plurality of extension payloads.

[00019] Additionally, when the fourth field is defined as the fourth value or the fifth value, the optional field further includes a fifth field that represents an extension payload type included in the extension field and a sixth field that represents a length of the extension field and when the fifth field is set to the default value, the extension field is completely filled by padding.

[00020] Additionally, when the fourth field is set to the fifth value, the optional field comprises a field representing a type of an extension payload included in the extension field, a field representing an LSB portion of a length of extension field and a field that represents an MSB portion of the length of the extension field.

[00021] Furthermore, when the fourth field is set to the sixth value, the optional field comprises a field representing a number of a plurality of extension payloads included in the extension field, a field representing an LSB portion of a length of the extension field and a field that represents an MSB portion of the length of the extension field.

[00022] Furthermore, the extension field comprises a plurality of fields representing respective types of the plurality of extension payloads and a plurality of fields representing respective lengths of the plurality of extension payloads.

[00023] Furthermore, when the fourth field is set to one of a fourth value and a fifth value, and a length of an extension charge included in the extension field is less than a length of the extension field, the extension field comprises the extension and filling payload.

[00024] Furthermore, when the fourth field is set to a sixth value, the extension field comprises a plurality of extension and padding payloads.

[00025] According to yet another aspect of an exemplary embodiment, there is provided a method of controlling a receiving apparatus that may include: receiving a stream of packets that includes a header and a payload; extract the packet header and extract information included in the header; and processing signals from a plurality of input packets included in the payload based on the extracted information. A base field that configures the header that includes a first field, defined as a first value representing that the base field is a first length or a second value representing that the base field is a second length. The header may include a first field, which is defined as a first value, which represents that a pointer value indicating a first starting point among the respective starting points of the input packets included in the payload is less than a predetermined value or a second value that represents that the pointer value is equal to or greater than the predetermined value. When the first field is set to the second value, the base field comprises a second field that represents the least significant bits (LSB) of the pointer value that indicates a first starting point between the respective starting points of the incoming packets, included in the payload, and a third field that represents the most significant bits (MSB) of the pointer value.

[00026] According to exemplary embodiments, since an input stream can be efficiently mapped to a physical layer, the efficiency of data processing can be improved.

[00027] Additional aspects and/or other aspects and advantages of the exemplary modalities will be set forth in part in the description that follows, and in part will be obvious from the description, or can be learned by practicing the exemplary modalities.

Advantageous Effects of the Invention Brief Description of the Drawings

[00028] The above and/or other aspects will be more apparent when describing certain exemplary embodiments with reference to the accompanying drawings, in which: FIG. 1 is a diagram for describing a hierarchical structure of a transmission system, according to an exemplary embodiment; FIG. 2 is a diagram illustrating a schematic configuration of a diffusion bonding layer 1400, in accordance with an exemplary embodiment; FIG. 3A is a diagram for describing a schematic configuration of a transmission system, according to an exemplary embodiment; FIGS. 3B and 3C are diagrams for describing a multiplexing method, in accordance with exemplary embodiments; FIG. 4 is a block diagram illustrating a detailed configuration of an input formatting block illustrated in FIG. 3A, according to an exemplary embodiment; FIG. 5A is a block diagram illustrating a configuration of a baseband formatting block, in accordance with an exemplary embodiment, and FIG. 5B is a diagram for describing a detailed configuration of a baseband package, in accordance with an exemplary embodiment; FIG. 6 is a block diagram illustrating a configuration of a transmission apparatus, in accordance with an exemplary embodiment; FIG. 7A is a block diagram illustrating a detailed configuration of a packet generator, in accordance with an exemplary embodiment, and FIG. 7B is a diagram illustrating an ALP packet, a baseband packet, and a coded baseband packet, in accordance with an exemplary embodiment; FIG. 8 is a diagram illustrating a package structure, according to an exemplary embodiment; FIG. 9 is a diagram illustrating a header structure, according to an exemplary embodiment; FIG. 10 is a diagram illustrating a detailed configuration of an optional field, in accordance with an exemplary embodiment; FIGS. 11 to 16D are diagrams illustrating structures of a package, in accordance with exemplary embodiments; FIG. 17 is a diagram illustrating a structure of a package, according to another exemplary embodiment; FIG. 18 is a diagram illustrating a detailed configuration of a header illustrated in FIG. 17, according to an exemplary embodiment; FIG. 19 is a diagram illustrating a detailed configuration of an optional field, in accordance with another exemplary embodiment; FIGS. 20 to 24 are diagrams illustrating structures of a package, in accordance with exemplary embodiments; FIG. 25 is a diagram illustrating a structure of an extension field, according to an exemplary embodiment; FIG. 26A is a block diagram illustrating a configuration of a receiving apparatus, in accordance with an exemplary embodiment; FIG. 26B is a block diagram illustrating a signal processor in accordance with an exemplary embodiment in detail; FIG. 27 is a block diagram illustrating a configuration of a receiver, in accordance with an exemplary embodiment; FIG. 28 is a block diagram illustrating a demodulator, according to an exemplary embodiment in more detail; FIG. 29 is a flow chart schematically illustrating an operation of a receiver, in accordance with an exemplary embodiment; FIG. 30 is a flowchart for describing a method of controlling a transmission apparatus, in accordance with an exemplary embodiment; and FIG. 31 is a flowchart for describing a method of control in a receiving apparatus, in accordance with an exemplary embodiment.

Best way to carry out the invention Mode for Invention

[00029] In the following, several exemplary embodiments of the inventive concept will be described in detail with reference to the attached drawings. Furthermore, in the description that follows, a detailed explanation of related known functions or settings may be omitted to avoid unnecessarily obscuring the subject. Furthermore, the terms to be described below may vary according to a user's and an operator's intentions, convention, or the like, such as terms defined by consideration functions. Therefore, the definition must be made in accordance with the content throughout this description.

[00030] An apparatus and method proposed in the exemplary embodiments can, of course, be applied to various communication systems, which include mobile broadcasting services, which include a digital multimedia broadcasting service (DMB), a digital video broadcasting computer (DVP-H) and similar communication systems that include a moving picture expert group (MPEG) media transport system, an evolved packet system (EPS), a long-term evolution mobile communication system ( LTE), a long-term advanced evolution (LTE-A) mobile communication system, a high-speed packet downlink access (HDSPA) mobile communications system, a high-speed uplink packet access (HSUPA) (3GPP2), a high-rate packet data (HRPD) mobile communications system, a 3GPP2 broadband code division multiple access (WCDMA) mobile communications system, a codec, a mobile communications system (CDMA )division multiple access3GPP2, an Institute of Electrical and Electronics Engineers (IEEE) 802.16m communication system, a Mobile Internet Protocol (Mobile IP) system, and the like.

[00031] FIG. 1 is a diagram illustrating a hierarchical structure of a transmission system according to an exemplary embodiment.

[00032] With reference to FIG. 1, a service includes media data 1000 and signaling 1050 for transferring information necessary to acquire and consume the media data at a receiver. Media data can be encapsulated in a format suitable for transmission before transmission. An encapsulation method may follow a Media Processor (MPU) defined in ISO/IEC 23008-1 MPEG Media Transport (MMT), or a DASH segment format, defined in ISO/IEC 23009-1 Dynamic Adaptive Stream over HTTP ( DASH). Media data 1000 and signaling 1050 are packaged according to an application layer protocol.

[00033] FIG. 1 illustrates a case in which an MMT protocol (MMTP) 1110 defined in the MMT and a unidirectional transport over real-time delivery (ROUTE) 1120 are used as the application layer protocol. In this case, a method for notifying information about an application protocol, in which a service is transmitted, by an independent method other than the application layer protocol is necessary for the receiver to know by which application layer protocol the service is transmitted. transmitted.

[00034] A service list table (SLT) 1150, illustrated in FIG. 1, represents or indicates a signaling method and information packaged with respect to the service in a table to satisfy said object. The detailed content of the SLT will be described below. The packaged media data and signaling that includes the SLT is transferred to a broadcast link layer 1400 via a user datagram protocol (UDP) 1200 and an Internet protocol (IP) 1300. An example of the data layer broadcast link 1400 includes an ATSC 3.0 link layer protocol (ALP) defined in the ATSC 3.0 standard (hereinafter referred to as "ATSC 3.0"). The ALP protocol generates an ALP packet using an IP packet as input and transfers the ALP packet to a broadcast physical layer 1500.

[00035] However, according to FIG. 2 to be described below, it is noted that the broadcast link layer 1400 does not only use the IP packet 1300, which includes the media data and/or signaling as input, and may instead use a packet MPEG2-TS or general formatted packet data as input. In this case, signaling information necessary to control the broadcast link layer is also transferred to the broadcast physical layer 1500 in the form of the ALP packet.

[00036] The broadcast physical layer 1500 generates a physical layer structure by processing the ALP packet signal as input, converts the physical layer structure into a radio signal, and transmits the radio signal. In this case, the broadcast physical layer 1500 has at least one signal processing path. An example of the signal processing path may include a physical layer tube (PLP) of ATSC 3.0 or the Digital Video Broadcasting-Second Generation Terrestrial (DVB-T2) standard, and one or more services or some of the services may be mapped for the PLP.

[00037] FIG. 2 is a diagram illustrating a schematic configuration of the broadcast link layer 1400, in accordance with an exemplary embodiment.

[00038] With reference to FIG. 2, broadcast link layer input 1400 includes IP packet 1300 and may further include link layer signaling 1310, an MPEG2-TS packet 1320, and other packetized data 1330.

[00039] The input data may be subjected to additional signal processing based on the input data type prior to ALP packaging 1450 . As an exemplary embodiment of additional signal processing, the IP packet 1300 may be subjected to an IP header compression process 1410 and the MPEG2-TS packet may be subjected to an overhead reduction process 1420. During ALP packaging , input packets can be subjected to splitting and merging processes.

[00040] FIG. 3A is a diagram illustrating a schematic configuration of a transmission system or a transmission apparatus, in accordance with an exemplary embodiment. According to FIG. 3A, a transmission system 10000, in accordance with the exemplary embodiment, may include input formatting blocks 11000 and 11000-1, bit interleaving and coded modulation (BICM) blocks 12000 and 12000-1, framing blocks/ interleaving 13000 and 13000-1 and waveform generation blocks 14000 and 14000-1.

[00041] Input formatting blocks 11000 and 11000-1 generate a baseband packet from an input stream of data to be served. Here, the input stream can be a transport stream (TS), Internet (IP) packets (e.g. IPv4 and IPv6), an MPEG media transport (MMT), a generic stream (GS), stream encapsulation generic (GSE) and Taste. For example, an ATSC 3.0 Link Layer Protocol (ALP) packet can be generated based on the input current, and the baseband packet can be generated based on the generated ALP packet.

[00042] Bit interleaving and coded modulation (BICM) blocks 12000 and 12000-1 determine a forward error correction coding (FEC) rate and constellation order according to an area (fixed PHY structure or mobile PHY structure) to which the data to be processed will be transmitted, and perform coding and time interleaving. However, signaling information about the data to be served may be encoded by a separate BICM encoder according to the user's implementation or encoded by sharing a BICM encoder with the data to be served.

[00043] Framing/interleaving blocks 13000 and 13000-1 combine the time-interleaved data with a signaling signal that includes the signaling information to generate a transmission structure.

[00044] Waveform generation blocks 14000 and 14000-1 generate an orthogonal frequency division multiplexing (OFDM) signal in a time domain for the generated transmission structure, modulate the generated OFDM signal into an RF signal and transmit the RF signal to a receiver.

[00045] The transmission system, 10000 according to the exemplary embodiment illustrated in FIG. 3A, includes normative blocks marked with a solid line and informative blocks marked with dotted lines. In this case, the blocks marked with the solid line are normal blocks and the blocks marked with the dotted lines are blocks that can be used when multiple input multiple information (MIMO) is implemented.

[00046] FIGS. 3B and 3C are diagrams illustrating a multiplexing method, in accordance with exemplary embodiments.

[00047] FIG. 3B illustrates a block diagram for implementing time division multiplexing (TDM), in accordance with an exemplary embodiment.

[00048] A TDM system architecture includes four main blocks (alternatively, parts) of the input formatting block 11000, the BICM block 12000, the framing/interleaving block 13000, and the waveform generation block 14000.

[00049] Data is input and formatted in input formatting block 11000 and forward error correction is applied to the data in BICM block 12000. Then the data is mapped to a constellation. Subsequently, the data is time and frequency interleaved in the framing/interleaving block 13000 and a structure is generated. An output waveform is then generated in the waveform generation block 14000.

[00050] FIG. 3C illustrates a block diagram for implementing layer division multiplexing (LDM), according to an exemplary embodiment.

[00051] An LDM system architecture includes several other blocks compared to the TDM system architecture. In detail, two separate input formatting blocks 11000 and 11000-1 and BCIM blocks 12000 and 12000-1 for one of the respective LDM layers are included in the LDM system architecture. The blocks are combined into an LDM injection block before the framing/interleaving block 13000. And, the waveform generation block 14000 is similar to TDM.

[00052] FIG. 4 is a block diagram illustrating a detailed configuration of the input formatting block illustrated in FIG. 3A, according to an exemplary embodiment.

[00053] As illustrated in FIG. 4, input formatting block 11000 includes three blocks that control packets distributed to PLPs. In detail, the input formatting block 11000 includes an encapsulation and compression block 11100, a baseband formatting block (alternatively, baseband structure block) 11300, and a programming block 11200.

[00054] An input current input to the encapsulation and compression block 11100 can be of various types. For example, the input stream may be a transport stream (TS), an Internet packet (IP) stream (e.g., IPv4 and IPv6), an MPEG media transport (MMT), a generic stream (GS), a generic current encapsulation(GSE), and similar.

[00055] Packets leaving the encapsulation and compression block 11100 become ALP packets (generic packets) (also referred to as L2 packets). Here, a format of an ALP packet can be one of the Type Length Value (TLV), the GSE and the ALP.

[00056] The length of each ALP packet is variable. The ALP packet length can be easily extracted from the ALP packet itself without additional information. The maximum ALP packet length is 64 kB. The maximum length of an ALP packet header is 4 bytes. The ALP packet is integer bytes long.

[00057] Programming block 11200 receives an input stream that includes ALP packets encapsulated to form physical layer pipes (PLPs) in a baseband packet form. In TDM system, only one PLP called a single PLP (S-PLP) or multiple PLPs (M-PLP) can be used. A service cannot use four or more PLPs. In the LDM system consisting of two layers, one in each layer, that is, two PLPs are used.

[00058] Programming block 11200 receives the encapsulated ALP packets to designate how the encapsulated ALP packets are assigned to physical layer resources. In detail, programming block 11200 designates how baseband formatting block 1130 issues a baseband packet.

[00059] A function of programming block 11200 is defined by a data size and a time. A physical layer can transmit some data in distributed time. The programming block generates a solution that is suitable in terms of a configuration of a physical layer parameter using inputs and information such as constraints and configuration of an encapsulated data packet, the quality of service metadata for the encapsulated data packet, a system buffer model, and systems management. The target solution is a configuration and a control parameter that are used and an aggregated spectrum.

[00060] However, an operation of programming block 11200 is limited to a set of dynamic, quasi-static and static components. The limitation definition may vary depending on the user's implementation.

[00061] Additionally, a maximum of four PLPs can be used with respect to each service. A plurality of services that include a plurality of interleaving block types can be implemented up to a maximum of 64 PLPs with respect to a bandwidth of 6, 7 or 8 MHz.

[00062] Baseband formatting block 11300 includes baseband packet building blocks 3100, 3100- 1, ... 3100-n, baseband packet header building blocks 3200, 3200- 1,..., 3200-n and baseband packet coding blocks 3300, 3300-1,..., 3300-n, as illustrated in FIG. 5A. In an M-PLP operation, the baseband formatting block generates a plurality of PLPs as needed.

[00063] Baseband package building blocks 3100, 3100-1,..., 3100-n construct baseband packages. Each baseband packet 3500 includes a header 3500-1 and a payload 3500-2, as illustrated in FIG. 5B. A baseband packet is fixed to a payload length K. ALP packets 3610 to 3650 are sequentially mapped to a baseband packet 3500. When ALP packets 3610 to 3650 do not completely fit into the baseband packet base 3500, these packets are distributed between a current baseband packet and a next baseband packet. ALP packets are distributed in a one-byte unit.

[00064] Baseband packet header building blocks 3200, 3200-1,..., 3200-n construct a header 3500-1. The header 3500-1 includes three parts, i.e., a base field (also referred to as a base header) 3710, an optional field (also referred to as an option header) 3720, and an extension field (also referred to as, an extension header) 3730, as illustrated in FIG. 5B. Here, the base field 3710 is shown in each baseband package and the optional field 3720 and extension field 3730 may not be shown in each baseband package.

[00065] A main function of base field 3710 provides a pointer of an offset value as bytes to indicate a start of a next ALP packet in a baseband packet. When an ALP packet starts a baseband packet, the pointer value becomes 0. When there is no ALP packet that starts from the baseband packet, the pointer value can be 8191 and a base header of 2 bytes can be used.

[00066] Extension field 3730 may be used later and, for example, used for a baseband packet counter, baseband packet timestamping, additional signaling, and the like.

[00067] Baseband packet scrambling blocks 3300, 3300-1,..., 3000-n encode the baseband packet.

[00068] FIG. 6 is a block diagram illustrating a configuration of a transmission apparatus, in accordance with an exemplary embodiment.

[00069] With reference to FIG. 6, a transmission apparatus 100 includes a packet generator 110, a signal processor 120, and a transmitter 130.

[00070] Packet generator 110 may generate a packet that includes a header and a payload, e.g., a baseband packet (alternatively, an L1 packet) based on an input packet. Here, the packet includes the header and the payload, which includes the input packet, and is defined as a payload k with a fixed length. The packet length can be set according to the selected code rate and code length. Here, the input packet can be, for example, an ATSC Link Layer Protocol (ALP) packet. The ALP packet includes one of an internal protocol (IP) packet, a transport chain (TS) packet, and a signaling packet or may include a combination thereof. In detail, the input IP packet, TS packet and various types of data are encapsulated to be generated as the ALP packet for transmission to each PLP, and the ALP packet corresponds to an L2 packet in an ISO 7 layer model. Furthermore, the data included in the payload is not limited to the above-mentioned example, and the payload may include multiple types of data. Hereinafter, for convenience of description, the packet generated by packet generator 110 is called a baseband packet and the input packet is called an ALP packet.

[00071] A baseband packet generation process will be described with reference to FIGs. 7A and 7B.

[00072] FIG. 7A is a block diagram illustrating a detailed configuration of a packet generator, in accordance with an exemplary embodiment.

[00073] With reference to FIG. 7A, packet generator 110 may include a baseband packet header generator 110-1 and a baseband packet builder 110-2. Additionally, the packet generator 110 may transmit a generated baseband packet to a baseband packet scrambler 115.

[00074] Additionally, an ALP packet builder 110' can generate an ALP packet for transmission from each PLP, in association with an input mode from an IP input packet, a TS packet, and various types of data. Here, the ALP packet corresponds to an L2 packet in an ISO 7 layer model. That is, the ALP packet builder 110' can generate an ALP packet by encapsulating the incoming packets (the IP packet, the TS, and the like) from higher input layers of Layer 2 or higher.

[00075] In detail, the ALP packet builder 110' can generate an ALP packet (i.e., an L2 packet) that includes an ALP header and payload data based on the input current. Here, the header means the header of the ALP packet, and may include information about the ALP payload data included in the ALP packet and information about at least one packet included in the ALP packet.

[00076] The baseband packet header generator 110-1 can generate a header inserted within the baseband packet. Here, the header inserted inside the baseband packet is referred to as a baseband packet header, and the baseband packet header includes information about the baseband packet.

[00077] In particular, the baseband packet header generator 110-1 can generate the baseband packet header, which includes information about the number of TS packets in the ALP packet, the number of packets nulls removed, and the like when an input current is a TS. Furthermore, the baseband packet header generated by the baseband packet header generator 110-1 may include various information that will be described below.

[00078] Additionally, the baseband packet builder 110-2 encapsulates the baseband packet header generated from the baseband packet header generator 110-1 in the ALP packet output from of the ALP packet builder 110' to generate the baseband packet.

[00079] Furthermore, the packet generator 110 provides a plurality of ALP packets, which includes the IP packet and the header for generating the ALP packets arranged as a baseband packet with a size corresponding to an IP code. FEC. The baseband packet, according to the exemplary embodiment, may be a TS packet, but the same process can be applied to various types of data described above as well as the TS packet.

[00080] Additionally, the baseband packet scrambler 115 shuffles the data stored in the baseband packet in a random order before the FEC code is added to each baseband packet to generate the baseband packet. base shuffled. The scrambled baseband packet is transmitted through a PLP for signal processing. In this case, a PLP can be made up of baseband packets that have a fixed size. That is, the input current can be encapsulated into the baseband packet for a PLP.

[00081] However, PLP means a signal path that is processed independently. That is, respective services (e.g., video, extended video, audio, a data stream, and the like) may be transmitted and received over multiple RF channels and the PLP is a path through which the services are transmitted or a current transmitted through the path. Furthermore, the PLP can be positioned in slots distributed over several RF channels in a time slot or distributed over one RF channel in each time slot. That is, a PLP can be transmitted while being distributed over an RF channel or multiple RF channels in a time slot.

[00082] The PLP structure consists of input mode A providing one PLP and input mode B providing multiple PLPs. When the PLP structure supports input mode B, the PLP structure can provide a strong specific service and a time interleaving length is increased by distributing and transmitting a current to acquire a time diversity gain. Furthermore, when only a specific current is received, the receiver's power supply is switched off for a residual time to be used with low power consumption, and as a result, the receiver is suitable for providing portable and mobile broadcasting services. .

[00083] Here, time diversity is a technology that, when a transmission side transmits the same signal at several predetermined time intervals, in order to reduce the deterioration of a transmission quality in a mobile communication transmission path, a receiving side synthesizes the received signals again to achieve excellent transmission quality.

[00084] Furthermore, information that can be transmitted generally to a plurality of PLPs is transmitted while being included in a PLP to increase transmission efficiency. In this case, PLP0 performs such a role and the PLP is referred to as an ordinary PLP, and other residual PLPs besides PLP0 can be used for data transmission and the PLP is referred to as a data PLP. When such a PLP is used, a home HDTV program can be received and an SDTV program can be provided even while carrying out and on the move. Furthermore, various broadcasting services can be provided to a viewer through a broadcasting station or a broadcasting content provider, and differentiated services in which a broadcast can be received can be provided even in a marginal area where viewing is difficult.

[00085] However, FIG. 7B is a diagram illustrating an ALP packet, a baseband packet, and a scrambled baseband packet, in accordance with an exemplary embodiment.

[00086] Referring to FIG. 7B, when ALP packet builder 110' stores the TS packet in the ALP payload and inserts the header to generate a plurality of ALP packets 111' and 112', the packet generator 130 groups the plurality of generated ALP packets 111' and 112' and inserts the baseband packet header to generate a plurality of baseband packets 121 and 122. Here, the respective baseband packets 121 and 122 may include a plurality of ALP packets and may further include some of the ALP packets.

[00087] The baseband packet scrambler 115 randomly shuffles the baseband packets 121 and 122 to generate a plurality of scrambled baseband packets 125-1 and 125-2. Furthermore, scrambled baseband packets 125-1 and 125-2 are transmitted to the PLP as described above and subjected to signal processing for the addition of the FEC code.

[00088] Referring again to FIG. 6, the signal processor 120 can process the generated packet signal. Here, the generated packet means the baseband packet as described above.

[00089] In detail, the signal processor 120 processes the signal and baseband packets to generate a transmission structure.

[00090] Additionally, signal processor 120 may insert signaling information into a signaling area of the structure. Here, the signaling information may be a signaling layer 1 (L1) transmitting signal of an L1 signal for frame synchronization, and a preamble into which the L1 signaling information is inserted may include a pre-signaling area of L1 and an L1 post-signaling area. Additionally, the L1 post-signaling area includes a configurable field and a dynamic field.

[00091] However, the L1 pre-signaling area may include information for analyzing L1 post-signaling and information about the entire system, and the L1 pre-signaling area may be implemented to have the same length on all moments. Furthermore, the L1 post-signaling area may include information about the respective PLP and system information, and in a superstructure, the L1 signaling areas are included in the respective structures that have the same length, but contents included in the L1 signaling areas may vary.

[00092] However, although not illustrated, signal processor 120 can perform functions corresponding to bit interleaving and coded modulation (BICM) blocks 12000 and 12000-1 and framing/interleaving blocks 13000 and 13000-1, illustrated in FIGs. . 3A to 3C.

[00093] Transmitter 130 can transmit processed signal structure to a receiving apparatus (not illustrated).

[00094] In detail, transmitter 130 can perform functions corresponding to waveform generation blocks 14000 and 14000-1, illustrated in FIGs. 3A to 3C. That is, the transmitter 130 performs modulation to modulate the structure generated for the RF signal, and transmits the RF signal to a receiving apparatus (not illustrated).

[00095] However, FIG. 8 is a diagram illustrating a package structure, in accordance with an exemplary embodiment. Here, it is defined in advance that the packet generated from the packet generator 110 used in the present description means a baseband packet.

[00096] Referring to FIG. 8, the baseband packet consists of a header 3100 and a payload 3200. The header 3100 can again be divided into a base field 3110, an optional field 3120 and an of extension 3130, in accordance with a rule thereof. Here the base field will be set to the same meaning as the base header. The header of the baseband packet 3100 may necessarily include the base field 3110, and whether the optional field 3120 is present may vary depending on a base field control field value of 3110. Additionally, if extension field 3130 is present can be selected via an optional field control field 3120.

[00097] However, the base field, the optional field, and the extension field used in this description may correspond to a base header, an optional header, and an extension header, respectively.

[00098] Hereinafter, a header structure will be described with reference to the attached drawings. Here, the header can mean a baseband packet header.

[00099] FIG. 9 is a diagram illustrating a structure of a header, according to an exemplary embodiment.

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

[000101] However, in the present description, terms such as base header, optional field and extension field are used and described, but of course, the terms can be expressed by general words, such as a first header, a second field and a third field.

[000102] In detail, the baseband packet can be broadly divided into a header and a payload, and here, the header can be constituted of three parts, as illustrated in FIG. 9. The first part is the 2310 base header and exists in all packets. Furthermore, the second part is the optional field 2320 and the third part is the extension field 2330. The optional field 2320 and the extension field 2330 are not always present in all packets, and the base header 2310 includes information representing (or indicating) whether optional field 2320 and extension field 2330 are present.

[000103] Additionally, the header may include base header 2310 which includes information representing a starting point of a data packet in payload 2340 and information about whether an additional field is present. That is, base header 2310 may include information representing the starting point of the data packet in payload 2340. In detail, base header 2310 may perform a function of providing a pointer that includes an offset value of a byte unit to a starting point of a next generic packet (also referred to as a “data packet” or “ALP packet”) that is present in packet 2300. Here, the starting point of the data packet designates a distance between the starting point of the payload 2340 and the starting point of the data packet, and the distance can be expressed by the above-mentioned offset value of the byte unit.

[000104] As illustrated in FIG. 7B, a first ALP packet 111' is not segmented and may be included in the first packet 121, but may be segmented together with a second ALP packet 112', to be included in the first packet 121 and the second package 122.

[000105] In this case, the base header included in the header of the first packet 121 may include information representing a starting point of the first ALP packet 111', and in detail, may include information, which includes a value of a distance between the payload starting point of the first packet 121 and the starting point of the first ALP packet 111'.

[000106] Additionally, the base header included in the header of the second packet 122 may include information representing a starting point of the ALP packet included alongside the second packet 112'.

[000107] For example, when the generic packet is dropped from the starting point in the packet, a pointer value may be set to 0. Additionally, the pointer may be extended to 2 bytes, and thus, the value represented by the pointer can be increased up to 8191. That is, the 2310 base header can express the distance to the starting point, where the generic packet begins in the packet, by the value of 8191.

[000108] In detail, the information representing the starting point of the data packet (i.e., the ALP packet) may include information about whether a most significant bit (MSB) part of the pointer is present according to the distance between the start point of the payload and the start point of the data packet, and may include one of a first value representing the MSB portion that is not present and a second value representing the MSB portion that is present. That is, when the information representing the starting point of the data packet is set to 0, it represents that the MSB part is not present, and when the information representing the starting point of the data packet is set to 1, represents that the MSB part is present.

[000109] Referring to FIG. 9, the base header 2310 has a MODE field 2311 that includes therein information about the starting point of the data packet, and the MODE field 2311 represents whether an MSB portion of the pointer is gift. Here, the MODE field 2311 has a size of 1 bit.

[000110] When the MODE field 2311 is set to 0, the MODE field 2311 represents a distance from a start point of payload 2340 to a start point of a new generic packet (i.e., packets data) in payload 2340 is a short pointer length. Here short pointer length means a length that is not beyond 127 bytes. Therefore, a pointer field that includes information about the distance from the starting point of the payload 2340 to the starting point of the new generic packet in the payload 2340 includes only a pointer field (LSB) 2312 corresponding to the length of short pointer and the 2313 pointer field (MSB) is not included. Here, the length of the pointer field (LSB) 2312 is 7 bits.

[000111] Furthermore, when the MODE field 2311 is set to 0, the pointer field includes only the pointer field (LSB) 2312, and therefore the length of the base header 2310 becomes one byte.

[000112] However when the MODE field 2311 is set to 1, the MODE field 2311 represents that the distance from a start point of the payload 2340 to a start point of a new generic packet in the payload 2340 is a long pointer length. Here, the long pointer length can be equal to or greater than 128 bytes. Therefore, pointer field including information about the distance from a starting point of payload field 2340 to a starting point of a new generic packet in the payload may include a pointer field (MSB) 2313 as well as a pointer length (LSB) 2312 in order to represent the long pointer length. The length of the 2313 pointer field (MSB) is 6 bits.

[000113] Additionally, when the MODE field 2311 is set to 1, the base header 2310 may include an OHI field 2314 that represents information about whether an additional field is present in the header. The length of the OHI 2314 field is 2 bits.

[000114] Therefore, when the MODE field 2311 is set to 1, the base header 2310 includes the MODE field 2311, the pointer field (LSB) 2312, the pointer field (MSB) 2313, and the OHI field 2314, and thus the base header length becomes 2310 2 bytes.

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

[000116] However, information about whether the additional field is present in the header may include information about whether at least one of the optional field 2320 and the extension field 2330 is present and a length of the optional field 2320 and the extension field 2330 .

[000117] Additionally, information about whether the additional field is present may include one of a first value representing that the optional field 2320 and the extension field 2330 are not present, a second value representing that the optional field 2320 is present, the extension field 2330 is not present, and the length of the optional field 2320 is one byte, a third value representing that the optional field 2320 is present, the extension field 2330 is not present, and the length of the optional field 2320 is of 2 bytes, and a fourth value representing that the optional field 2320 and the extension field 2330 are present and the length of the optional field 2320 and the extension field 2330 exceeds 2 bytes.

[000118] Additionally, optional field 2320 may include information representing a length of extension field 2330 when information about whether the additional field is present is defined as the fourth value and may include at least one part of LSB and the part of MSB according to the length of the extension field.

[000119] Information about whether the additional field is present can be stored in the optional header pointer (OHI) field 2314. In detail, the length of the OHI field 2314 is 2 bytes, and the length of the optional field 2320 can be equal to or less than 2 bytes. Information representing values stored in the OHI 2314 field can be summarized in the following Table 1.

[000120] In detail, how the optional field 2320 and the extension field 2330 are included in the header according to a value defined in the OHI field 2314 will be described with reference to FIG. 10.

[000121] FIG. 10 is a diagram illustrating a detailed configuration of the optional field, in accordance with an exemplary embodiment.

[000122] Referring to FIG. 10, when the OHI field 2314 is set to 00, the header does not include the optional field 2320 and the extension field 2330.

[000123] Additionally, when the OHI field 2314 is set to 01, the header includes the optional field 2320 which is 1 byte long. Here, the optional field 2320 may include information representing whether the optional field 2320 includes padding. In detail, the optional field 2320 may include an EXT_TYPE field 2321 that represents whether the optional field 2320 2330 includes padding. Here the length of the EXT_TYPE 2321 field is 3 bits. Additionally, a 5-bit remainder region 2322 except for the EXT_TYPE field 2321 within 1 byte of the optional field 2320 may include predetermined information or padding. The remaining region 2322 may include predetermined information or padding in accordance with the information included in the EXT_TYPE field 2321. Here, padding means nonsense data, and nonsense data may be determined randomly by various methods in accordance with a system design. Furthermore, the filler is not required to be filled with only 0, it can be filled with only 1, and it can be filled with a combination of sense 0 and 1. However, in a case where the filler is filled with only 0 will be described as an example.

[000124] Additionally, when the OHI field 2314 is set to 10, the header includes the optional field 2320 which has a length of 2 bytes. Likewise, optional field 2320 may include information representing whether optional field 2320 includes padding. In detail, the optional field 2320 may include an EXT_TYPE field 2321 that represents whether the optional field 2320 includes padding, and here, the length of the EXT_TYPE field 2321 is 3 bits. Furthermore, the remaining 5-bit region 2322 and 8-bit region 2323, except for the EXT_TYPE field 2321 between the 2 bytes of the optional field 2320 may include predetermined information or padding. The remaining 5-bit region 2322 and the 8-bit region 2323 may include predetermined information or padding according to the information stored in the EXT_TYPE field 2321. Here, padding means nonsense data, and nonsense data can be determined randomly by different methods according to a system design.

[000125] However, when the OHI field is set to 11, the header may include the extension field 2330 as well as the optional field 2320. Here, a total length of the optional field 2320 and the extension field 2330 exceeds 2 bytes, and the length of the optional field 2320 may be one byte or may be 2 bytes. Additionally, optional field 2320 may include information representing whether at least one of optional field 2320 and extension field 2330 includes padding zone. In detail, the optional field 2320 may include an EXT_TYPE field 2321 that represents whether at least one of the optional field 2320 and the extension field 2330 includes padding, and here, the length of the EXT_TYPE field 2321 is 3 bits.

[000126] However, when the OHI field 2314 is set to 11, the EXT_TYPE field 2321 sets a value corresponding to an extension field type 2330. For example, when padding is stored in the extension field 2330, the EXT_TYPE field 2321 has a value which means the padding is stored in the extension field 2330 is stored. Furthermore, when the OHI field 2314 is set to 11, the optional field 2320 includes information representing the length of the extension field 2330, and thus may include at least one of the LSB portion and the MSB portion. according to the length of the extension field. Here, the optional field 2320 may include at least one of an EXT_LEN (LSB) field 2324 and an EXT_LEN (MSB) field 2325, which represents the length of the extension field 2330. The length of the EXT_LEN (LSB) field 2324 may be 5 bits and the length of the EXT_LEN (MSB) 2325 field can be 8 bits.

[000127] When summarizing the above-mentioned EXT_TYPE field 2321, the EXT_TYPE field 2321 is a 3-bit field that represents an extension field type, the OHI field 2314 is set to 01, and when the EXT_TYPE field 2321 is set to 000 , a bit sequence of “00000” may be stored in the optional field 2320. Additionally, the OHI field 2314 is set to 10, and when the EXT_TYPE field 2321 is set to 000, a bit sequence of “00000000” other than the bit bit “00000” may be additionally stored in the optional field 2320. Additionally, when the OHI field 2314 is set to 11, the EXT_TYPE field 2321 is populated with a value corresponding to the type of the extension field 2330 and at least one of the EXT_LEN field (LSB) 2324 and the (MSB) EXT_LEN field 2325 can be linked and deleted. Here, when the EXT_TYPE field 2321 is set to 000, the padding (that is, the bit sequence 00000 or the bit sequence 00000000) is padded in the optional field 2320, but it is only exemplified, and of course the value defined in the EXT_TYPE field 2321 means that they can vary according to a creation method.

[000128] The EXT_LEN (LSB) field 2324 represents the length of the extension field 2330 and includes 5 LSB bits of the EXT_LEN field. The EXT_LEN (LSB) 2324 field always exists when the OHI 2314 field is set to 11.

[000129] Additionally, when the EXT_LEN (MSB) field 2325 includes 8 bits of the MSB of the EXT_LEN field and the EXT_LEN (MSB) field 2325 is present, the optional field 2320 includes an EXT_LEN field of a total of 13 bits in which the EXT_LEN field (LSB) 2324 and EXT_LEN field (MSB) 2325 are linked to each other. Therefore, when the length of the extension field 2330 is equal to or less than the predetermined length, the optional field 2320 may include only the EXT_LEN (LSB) field 2324. When the length of the extension field 2330 is greater than the predetermined length, the optional field 2320 may include both the EXT_LEN (LSB) field 2324 and the EXT_LEN (MSB) field 2325.

[000130] However, as the structure of the packet 2300 is completely changed according to the values defined in the MODE field 2311 and the OHI field 2314 will be described with reference to FIGs. 11 to 16D.

[000131] FIGS. 11 to 16D are diagrams illustrating package structures, in accordance with various exemplary embodiments.

[000132] With reference to FIG. 11, when the MODE field 2311 is set to 0, the MODE field 2311 means the short pointer length, and thus, the base header 2310 includes only the pointer field (LSB) 2312. When the MODE field 2311 is set to 0, the optional field 2320 and the extension field 2330 are not included in the packet 2300, and as a result, the packet 2300 includes the base header that is 1 byte long and the payload 2340.

[000133] Referring to FIG. 12, when the MODE field 2311 is set to 1, the MODE field 2311 means the long pointer length, and thus, the base header 2310 includes the pointer field (LSB) 2312 and the pointer (MSB) field 2313, and may additionally include the OHI field 2314 which includes information about whether the optional field 2320 and the extension field 2330 are present.

[000134] Therefore, packet 2300 includes base header 2340 which is 2 bytes long. However, in fig. 12, when the OHI field 2314 is set to 00, the optional field 2320 and the extension field 2330 are not included in the packet 2300, and as a result, the packet 2300 includes the base header 2310 which has a length of 2 bytes and the useful field 2340.

[000135] Referring to FIG. 13, when the MODE field 2311 is set to 1, the MODE field 2311 means the long pointer length, and thus, the base header 2310 includes the pointer field (LSB) 2312 and pointer field (MSB) 2313 and may additionally include OHI field 2314 which includes information about whether optional field 2320 and extension field 2330 are present.

[000136] Therefore, packet 2300 includes base header 2340 which is 2 bytes long. However, in fig. 13, the OHI field 2314 is set to 01 and therefore the optional field 2320 which has a length of 1 byte is included in the packet 2300 and the extension field 2330 is not included in the packet 2300. As a result, the packet includes 2300 the base header that has a length of 2 bytes, the optional field 2320 that has a length of 1 byte, and the payload 2340. Additionally, the optional field 2320 may include the 3-bit EXT_TYPE field 2321 and a 5-bit 2322 padding field.

[000137] Referring to FIG. 14, when the MODE field 2311 is set to 1, the MODE field 2311 means the long pointer length, and thus, the base header 2310 includes the pointer field (LSB) 2312 and pointer field (MSB) 2313 and may additionally include OHI field 2314 which includes information about whether optional field 2320 and extension field 2330 are present.

[000138] Therefore, packet 2300 includes base header 2340 which is 2 bytes long. However, in fig. 14, the OHI field 2314 is set to 10 and therefore the optional field 2320 which has a length of 2 bytes is included in packet 2300 and the extension field 2330 is not included in packet 2300. As a result, packet 2300 includes the base header 2310 that has a length of 2 bytes, the optional field 2320 that has a length of 2 bytes, and the payload 2340. Additionally, the optional field 2320 may include the 3-bit EXT_TYPE field 2321, a 5-bit padding field 2322, and an 8-bit padding field 2323.

[000139] Referring to FIG. 15, when the MODE field 2311 is set to 1, the MODE field 2311 means the long pointer length, and thus, the base header 2310 includes the pointer field (LSB) 2312 and the pointer field (MSB) 2313 and may additionally include the OHI field 2314 which includes information about whether the optional field 2320 and the extension field 2330 are present.

[000140] Therefore, packet 2300 includes base header 2340 which is 2 bytes long. However, in Fig. 15, the OHI field 2314 is set to 11 to include the base header 2310 which is 2 bytes long, the optional field 2320 which is 2 bytes long, the extension field 2330, and the payload 2340. Additionally, the optional field 2320 may include the EXT_TYPE field 2321, the EXT_LEN (LSB) field 2324, and the EXT_LEN (MSB) field 2325.

[000141] In FIG. 15, the case in which the optional field 2320 includes both the EXT_LEN (LSB) field 2324 and the EXT_LEN (MSB) field 2325 is illustrated. However, the optional field 2320 may include only the EXT_LEN (LSB) field 2324. In this case, the packet 2300 may include the base header 2310 which is 2 bytes long, the optional field 2320 which is one byte long. , the extension field 2330, and the payload 2340.

[000142] Furthermore, in the above-mentioned example, the case where the optional field 2320 has at least one of the 5-bit padding fields 2322 and the 8-bit padding field 2323 is exemplified, but the optional field 2320 may include other predetermined data other than padding and the EXT_TYPE field 2321 may also include a value representing the predetermined data.

[000143] However, FIGS. 16A to 16D illustrate that the data populated in the optional field 2320 and the extension field 2330 may vary according to the value set in the EXT_TYPE field 2321 when the OHI field 2314 is set to 11.

[000144] Referring to FIG. 16A, when the OHI field is set to 11, the optional field 2320 includes a TYPE field 2321, an EXT_LEN (LSB) field 2324, and an EXT_LEN (MSB) field 2325, and a representative example , where extension field 2330 is present is illustrated.

[000145] Here, 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 input current synchronization (ISSY) field 2331 and a padding 2332. Here, the ISSY field 2331 is exemplified in order to describe a case in which the extension field 2330 includes the predetermined data. The ISSY 2331 field is used to transmit a clock counter value according to a clock modulation and timing relationship that needs to regenerate to restore an output current by a receiver of the transmission structure.

[000146] Furthermore, with reference to FIG. 16B, when the TYPO field 2321 is set to 010, the optional field 2320 may include the EXT_LEN (LSB) field 2324 and the EXT_LEN (MSB) field 2325, and the extension field 2330 may include an ISSY field 2333 and a padding 2332 .

[000147] Of course, the extension field 2330 can include various other data than the ISSY field 2333, such as the predetermined data given. Referring to FIG. 16C, when the TYPE field 2321 is set to 011, the optional field 2320 includes the EXT_LEN (LSB) field 2324 and the EXT_LEN (MSB) field 2325, and the extension field 2330 may include an in-band of signal type A field 2334 and a padding 2332. Referring to FIG. 16D, when the TYPE field 2321 is set to 100, the optional field 2320 includes the EXT_LEN (LSB) field 2324 and the EXT_LEN (MSB) field 2325, and the extension field 2330 may include a TYPO B signal type field within band 2335 and a filler 2332.

[000148] However, the terms used to describe the above-mentioned ALP package and baseband packages may vary depending on the system, and for example, the above-mentioned ALP package and baseband package may be referred to as a baseband package and a baseband structure, respectively, according to the system.

[000149] According to another exemplary embodiment, the optional field and the extension field may include fields with different structures and this will be described in detail with reference to FIGs. 17 to 25. Furthermore, before describing that the optional field and the extension field may include fields that have different structures, the description for a field included a base field to be described below may correspond to a portion described in FIG. 9, but will be described once again using general terms.

[000150] Referring again to FIG. 6, the transmission apparatus 100 includes a packet generator 110, a signal processor 120, a transmitter 130, and the packet generator 110 can generate a packet that includes a header and a payload based on an input packet.

[000151] Here, the input packet may be, for example, an ALP packet (also referred to as an L2 packet) and the packet generated in packet generator 110 may be a baseband packet (BBP) (also referred to as as an L1 package). Of course, as described above, the terms of the packages may vary depending on the system and, for example, the above-mentioned ALP package and BBP package may be referred to as the BBP packages and a baseband structure ( BBF), respectively, according to the system.

[000152] The packet, that is, the baseband packet may include a header and a payload, which includes an input packet, and the packet is defined as a K payload with a fixed length. The packet length can be set according to the selected code rate and code length.

[000153] Furthermore, the input packet, that is, the packet, includes an ALP, an internal protocol (IP) packet, a TS packet, and a signaling packet, or may include a combination thereof. In detail, the input IP packet and TS packet, and various types of data are encapsulated to be generated as the ALP packet for transmission to each PLP, and the ALP packet corresponds to an L2 packet in the layer model ISO 7. However, the data included in the payload is not limited to the above-mentioned example, and the payload can include multiple types of data.

[000154] Additionally, the signal processor 120 can process the generated packet signal. In detail, the signal processor 120 processes signal from the packets to generate the transmission structure. Additionally, signal processor 120 may input signaling information to a signaling area of the structure. Here, the signaling information may be a signal transmission layer 1 (L1) signaling an L1 signal for frame synchronization, and a preamble into which the L1 signaling information is inserted may include an L1 pre-signaling area. and an L1 post-signaling area. Additionally, the L1 post-signaling area includes a configurable field and a dynamic field.

[000155] Although not illustrated, signal processor 120 can perform functions corresponding to bit interleaving and coded modulation (BICM) blocks 12000 and 12000-1 and framing/interleaving blocks 13000 and 13000-1 illustrated in FIGs. 3A to 3C.

[000156] Transmitter 130 can transmit the processing signal structure to a receiving or receiving apparatus (not illustrated).

[000157] In detail, transmitter 130 can perform functions corresponding to waveform generation blocks 14000 and 14000-1 illustrated in FIGs. 3A to 3C. That is, the transmitter 130 performs modulation to modulate the structure generated for the RF signal, and transmits the RF signal to the receiving apparatus or receiver.

[000158] However, the header base field configuration includes a first field, defined as a first value, which represents that the base field is a first length, or a second value, which represents that the base field is a second length, and when the first field is set to the second value, the base field may include a second field representing the least significant bits (LSB) of a pointer value representing a first value between the respective starting points of the included input packets in the payload and a third field that represents most significant bits (MSB) of the pointer value.

[000159] Furthermore, a packet header can be divided into a base field, an optional field and an extension field, according to a rule thereof, as illustrated in FIG. 8 described above, and the header necessarily includes a base field and whether the optional field is present may vary according to a value of a control value included in the base field. Furthermore, whether the extension field is present can be selected according to the value of the control field included in the optional field.

[000160] Here, the first field, the second field, and the third field can be included in the base field of the header configuration.

[000161] In detail, this will be described in detail with reference to FIG. 17.

[000162] FIG. 17 is a diagram illustrating a structure of a package according to another exemplary embodiment.

[000163] Referring to FIG. 17, a packet 4000 includes a header 4100 and a payload 4200 and a plurality of input packets 4201 may be mapped into the payload 4200 of packet 4000.

[000164] Here, according to the first input packet among the plurality of input packets 4201, a packet of one input is divided to be included in the payload of different packets. Furthermore, the base field can notify the starting point of the incoming packet through the pointer value. Here, the pointer value means an offset from the start point of the payload to the first start point among the respective start points of the input packets included in the payload.

[000165] In detail, a first field 4111 included in the header base field 4100 may be defined as a first value representing that the base field is a first length, that is, a byte, or a second value representing that the base field is a second length, i.e. 2 bytes.

[000166] In particular, when the first field 4111 is defined as the first value and therefore the base field is 1 byte, the base field may include only the second field representing pointer value LSB representing the first value between the respective starting points of the input packets included in the payload 4200, and as a result, the value of the pointer may represent just less than the predetermined value.

[000167] Additionally, when the first field 4111 is defined as the second value and therefore the base field is 2 bytes, the base field may include the second field representing the pointer LSB representing the first value between the respective starting points of the input packets included in the payload and the third field representing the MSB of the pointer value, and as a result, the pointer value may represent being greater than or equal to the predetermined value.

[000168] Here, the default value may be 128 bytes, and as a result, when the first field 4111 is set as the first value, the pointer value may represent only less than 128 bytes, and when the first field 4111 is set to the second value, the pointer value can represent being greater than or equal to 128 bytes.

[000169] For example, when any of the input packets are arranged to be combined with the starting point of the payload 4200 of the packet 4000, and thus the starting point of the corresponding input packet is the same as the starting point of the payload start point, the pointer value representing the corresponding value for the start point of the corresponding input packet can become 0. That is, since the start point of the input packet can be digitized and calculated Based on the starting point of the payload 4200, the value of the pointer representing the value corresponding to the starting point of the corresponding input packet, which starts at the same starting point of the payload 4200, may become 0.

[000170] Furthermore, as illustrated in FIG. 17, when any of an input packet is split to be included in the payload 4200 as the first input packet among the plurality of input packets 4201, the starting point of the first input packet is present in the previous packet and is not present in the corresponding payload 4200, and thus the first starting point of their respective starting points of the input packets included in the payload 4200 immediately becomes a starting point of the second input packet. Therefore, the pointer value that represents a value corresponding to the starting point of the second input packet can immediately become a value corresponding to a distance of 4202 to the starting point of the second input packet based on the starting point of the payload useful 4200.

[000171] Furthermore, when the first field 4111 is set as the first value, the header base field 4100 includes only a second field 4112, which represents the pointer LSBs, and when the first field 4111 is set as the second value, header base field 4100 may include second field 4112, which represents the LSBs of the pointer value, and a third field 4113, which represents the MSBs of the pointer value.

[000172] Here, the first field 4111 may be the MODE field and the MODE field may have a size of 1 bit. Furthermore, when the MODE field is set to 0, the length of the base field represents 1 byte, and when the MODE field is set to 1, the length of the base field can represent 2 bytes.

[000173] Additionally, the MODE field can represent whether the third field 4113, which represents the MSB of the pointer value is present, and whether a fourth field which represents a header extension mode is present. In detail, when the MODE field is set to 0, it is represented that the base field includes only the second field 4112 that represents the LSBs of the pointer value. Here, the second field 4112 may be the pointer field (LSB) representing the LSBs of the pointer value, and the pointer field (LSB) may have a size of 7 bits. Therefore, when the MODE field is set to 0, the pointer value has no choice but to be represented up to less than 128 bytes, and the base field has the size of 1 byte, which includes the MODE field ( 1 bit) and the pointer field (LSB) (7 bits).

[000174] Additionally, when the MODE field is set to 1, the base field may include the second field 4112 that represents the LSBs of the pointer value and the third field 4113 that represents the MSBs of the pointer value. Here, the third field 4113 representing the MSBs of the pointer value may be the pointer field (MSB) and the pointer field (MSB) may have a size of 6 bits. Therefore, when the MODE field is set to 1, the pointer value can be extended and represented up to 8191 bytes through a total of 13 bits, obtained by the sum of the pointer field (MSB) (7 bits) and the MODE field. pointer (MSB) (6 bits), and the base field has a size of 2 bytes that includes the MODE field (1 bit), the pointer field (LSB) (7 bits), the pointer field (MSB) (6 bits), and the fourth field (2 bits), which represents the 4100 header extension mode to be described below. As a result, the pointer field (MSB) and the fourth field representing the extension mode of the 4100 header can be included in the base field only when the MODE field is set to 1.

[000175] Therefore, when the value of the pointer representing the first value between the starting points of the input packets in payload 4200 of packet 4000 is less than 128 bytes, the first field 4111, that is, the MODE field is set to 0 and the base field includes the second field 4112, that is, only the pointer field (LSB), and thus the base field is 1 byte in size. When the value of the pointer representing the first value among the starting points of incoming packets in payload 4200 of packet 4000 is equal to or greater than 128 bytes, the first field 4111, that is, the MODE field is set to 1 and the base field includes the second field 4112, i.e., the pointer field (LSB), the third field 4113, i.e., the pointer field (MSB), and the fourth field, and thus, the base field is the size of a total of 2 bytes.

[000176] Furthermore, when the input packet start point in payload 4200 of packet 4000 is not present, since the corresponding value for the corresponding input packet start point cannot be set, the value of pointer becomes 8191 and consequently the MODE field is set to 1 and the base field is 2 bytes in size.

[000177] Furthermore, even when in payload 4200 of packet 4000, the input packet is not present and only the padding is present, the pointer value becomes 8191 and therefore the MODE field is set to 1 and the base field is 2 bytes in size.

[000178] FIG. 18 is a diagram illustrating a detailed configuration of the header illustrated in FIG. 17, according to an exemplary embodiment. Referring to FIG. 18, as described above, header 4100 includes a base field 4110, and may further include an optional field 4120 and an extension field 4130, and if a fourth field 4114, which represents the extension mode of the header 4100, to be described below is included can be determined.

[000179] Furthermore, as described above, when the first field 4111 is set as the first value, the base field 4110 includes only the second field 4112, and therefore it can be seen that the length of the base field 4110 has the size of a total of 1 byte that includes 1 bit of the first 4111 field and 7 bits of the second 4112 field.

[000180] Furthermore, as described above, when the first field 4111 is set as the second value, the base field 4110 includes the second field 4112, the third field 4113, and the fourth field 4114 that represents the extension mode of the header 4110, and therefore it can be seen that the length of the base field 4110 is the size of the total 2 bytes which includes 1 bit of the first field 4111, 7 bits of the second field 4112, 6 bits of the third field 4113, and 2 bits of the fourth field 4114.

[000181] However, when the first field 4111 is defined as the second value, the base field 4110 includes the fourth field 4114 that represents the extension mode of the header 4110, and the fourth field 4114 may include at least one of the information about whether the optional field 4120 and the extension field 4130 are present, the length of the optional field 4120, and the structure of the extension field 4130.

[000182] In detail, the fourth field 4114 can be defined as one of a third value representing that the optional field 4120 and the extension field 4130 are not present, a fourth value representing that the optional field 4120 is present, and the length of the optional field 4120 is one byte, a fifth value representing that the optional field 4120 is present and the length of the optional field 4120 is 2 bytes, and a sixth value representing the optional field 4120 is present, the length of the field optional 4120 is 2 bytes, and extension field 4130 is structured to include a plurality of extension payloads.

[000183] Here, the fourth field 4114 may be an OFI field and the OFI field may have a size of 2 bits. In detail, the information represented by values established in the OFI field can be summarized as in the following Table 2.

[000184] In detail, how the optional field 4130 and the extension field 4130 are included in the header 4100, according to the value defined in the fourth field 4114 will be described with reference to FIG. 19.

[000185] FIG. 19 is a diagram illustrating a detailed configuration of an optional field, in accordance with another exemplary embodiment.

[000186] Referring to FIG. 19, when the fourth field is set to “00”, which is the third value, the header 4100 only includes the base field 4110 and does not include the optional field 4120 and the extension field 4120 .

[000187] Furthermore, when the fourth field is set to “01”, which is the fourth value, as a short extension mode, the header 4100 may further include the optional field 4120 which has a size of 1 byte different from the field base 4110. Additionally, the presence or absence of the length of the extension field 4130 can be determined by fields included in the optional field 4120.

[000188] In detail, the optional field 4120 may include a field 4121 (EXT_TYPE field) representing a type of an extension payload 4131 included in the extension field 4130 and a field 4122 (EXT_LEN field) representing a length of the extension 4130. 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.

[000189] Here, the EXT_TYPE field 4121 has a size of 3 bits and represents the type of extension payload 4131 included in the extension field 4130, and the detailed description thereof will be described below. Furthermore, the EXT_LEN field 4122 has a size of 5 bits and can represent a length of the extension field 4130 in a range of 0 to 31 bytes.

[000190] When the EXT_LEN field 4122 is 0, the length of the extension field 4130 is 0, and therefore the extension field 4130 is not present in the header 4100.

[000191] In FIG. 19, it is illustrated that when the fourth field 4114 is set to “01”, which is 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 are separated from each other. However, in order to describe that there is a case in which the optional field 4120 is 1 byte in size and there is a case in which the optional field 4120 is 2 bytes in size, the two fields are separated in the drawing. In fact, when the fourth field 4114 is set to “01”, which is the fourth value, the optional field 4120 is 1 byte in size and thus the extension field 4130 is subsequently added to the optional field 4120. Therefore, the EXT_LEN field 4122 included in the optional field 4120 and the extension payload 4131 included in the extension field 4130 are arranged next to each other.

[000192] Furthermore, when the fourth field 4114 is set to “10”, which is the fifth value, as a long extension mode, the header 4100 may further include the optional field 4120 which has a size of 2 bytes different from the base field 4110. Additionally, the presence or absence and length of extension field 4130 may be determined by fields included in optional field 4120.

[000193] In detail, the optional field 4120 may include a field (EXT_TYPE field) 4121 that represents an extension payload type 4132 included in the extension field 4130, a field (EXT_LEN (LSB) field) 4123 represents a portion of LSB of a length of the extension field 4130, and a field of (EXT_LEN field (MSB)) 4124 that represents an MSB portion of the length of the extension field 4130. Here, as described above, since the EXT_TYPE field 4121 is defined as a fifth field and the field representing the length of the extension field 4130 is defined as a sixth field, the EXT_LEN (LSB) field 4123 may be defined as representing the LSB portion of the sixth field and the EXT_LEN (MSB) field 4124 can be defined as representing the MSB part of the sixth field.

[000194] Here, the EXT_TYPE field 4121 has a size of 3 bits and represents the type of extension payload 4132 included in the extension field 4130, and the detailed description thereof will be described below.

[000195] Additionally, the EXT_LEN (LSB) field 4123 may have a size of 5 bits of LSB part among the total 13 bits to represent the length of the extension field 4130, and the EXT_LEN (MSB) field 4124 may have an 8-bit size of the MSB part between the total 13 bits, to represent the length of the extension field 4130. Additionally, the total 13-bit field connecting the EXT_LEN (LSB) field 4123 and the EXT_LEN field ( MSB) 4124 may represent the length of extension field 4130 over the entire packet length range 4000 to 0.

[000196] Of course, when the field of the total 13 bits connecting the EXT_LEN field (LSB) 4123 and the EXT_LEN field (MSB) 4124 is 0, the length of the extension field is 0, and therefore the field of extension 4130 is not present in header 4100.

[000197] Furthermore, when the fourth field is set to “11”, which is the sixth value, as a mixed extension mode, the header 4100 may further include the optional field 4120 having a size of 2 bytes, different from the field base 4110. Additionally, the presence or absence and length of extension field 4130 and the structure of extension field 4130 may be determined by fields included in optional field 4120.

[000198] In detail, the optional field 4120 may include a field (NUM_EXT field) 4125 that represents the number of a plurality of extension payloads 4133 included in the extension field 4130, a field (EXT_LEN (LSB) field) 4126 that represents an LSB portion of the length of the extension field 4130, and a field (EXT_LEN (MSB) field) 4127 that represents an MSB portion of the length of the extension field 4130.

[000199] Here, the NUM_EXT field 4125 has a size of 3 bits and may represent the number of the plurality of extension payloads 4133 other than the padding included in the extension field 4130.

[000200] Particularly, extension field 4130 may indicate the presence of two to seven extension payloads, and the detailed structure thereof will be described with reference to FIG. 25.

[000201] Additionally, the EXT_LEN (LSB) field 4126 may have a size of 5 bits of the LSB part among the total 13 bits to represent the length of the extension field 4130, and the EXT_LEN (MSB) field 4127 may have an 8-bit size of the MSB part among the total 13 bits to represent the length of the 4130 extension field.

[000202] However, the length of the extension field 4130, which can be represented by the field of the total 13 bits that connect the EXT_LEN field (LSB) 4126 and the EXT_LEN field (MSB) 4127 will be described together, while describing the structure from extension field 4130.

[000203] FIG. 25 is a diagram illustrating a structure of the extension field, according to an exemplary embodiment.

[000204] When the fourth field 4114 is set to the sixth value, the extension field 4130 may include a plurality of fields representing respective types of the plurality of extension payloads and a plurality of fields representing respective lengths of the plurality of payloads useful extensions.

[000205] In detail, with reference to FIG. 25, when the fourth field 4114 is set to the sixth value, that is, "11", this means a mixed extension mode, and accordingly, the extension field 4130 may include the plurality of extension payload 1 (4145 ),..., Payload extension N (4146). In this case, extension field 4130 may include a plurality of EXT_TYPE 1 (4141),..., EXT_TYPE N (4143) fields representing respective types of the plurality of extension payloads of Extension 1 (4145),... ., Extension payload N (4146) and a plurality of fields EXT_LEN 1 field (4142),..., EXT_LEN field N (4144), which represent respective lengths of the plurality of extension payload 1 (4145), .. ., extension payload N (4146). Here, as described above, since the extension field 4130 can include two to seven extension payloads, a range of N can become 2 to 7.

[000206] The plurality of extension payloads (extension payload 1 (4145),..., N extension payload (4146)), all do not include padding.

[000207] Furthermore, when an extension payload is included in extension field 4130, an EXT_TYPE field representing the corresponding extension payload type and an EXT_LEN field are included in extension field 4130. Here, when considering that the EXT_TYPE field is sized 3 bits and the EXT_LEN field is sized 13 bits, a header that is sized 2 bytes total with respect to the 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 by the generic term of fields arranged at the front end of the 4130 extension field.

[000208] Therefore, when N extension payloads are included in extension field 4130, extension field 4130 includes a header having a total size of 2N bytes that includes a plurality of EXT_TYPE fields associated with the respective extension payloads and an EXT_LEN field.

[000209] As described above, extension field 4130 may include at least two extension payloads and, as a result, may include a header that has a size of 4 bytes. However, when the value of the EXT_LEN field is 0, it can be seen that there is no extension load, and in this case, the length of the 4130 extension field may have no choice but to be at least 4 bytes.

[000210] As a result, the length of the extension field 4130, which can be represented by the field of the total 13 bits connecting the EXT_LEN (LSB) field 4126 and the EXT_LEN (MSB) field 4127 described in FIG. 19 can represent the length of the extension field 4130 in a range of the entire length of the packet 4000 starting from 4 bytes.

[000211] Each of the EXT_LEN 1 (4142),..., EXT_LEN N (4144) fields, illustrated in FIG. 25, may include the EXT_LEN field (LSB) with a size of 5 bits and the EXT_LEN field (MSB) with a size of 8 bits. Therefore, a header that has a size of 2 bytes for an extension payload includes an EXT_TYPE field with a size of 3 bits, an EXT_LEN field (LSB) with a size of 5 bits, and an EXT_LEN field (MSB) having a size eight BITS.

[000212] Furthermore, in extension field 4130, when the fourth field 4114 is set to a fourth value and the fifth value, the size of the extension payload included in the extension field 4130 is less than the length of the extension field 4130, the extension payload is included in the extension field 4130 and the padding may be included in the remaining portion.

[000213] For example, in FIG. 19, when the fourth field 4114 is set to “01”, which is the fourth value and an actual length of the extension payload 4131 included in the extension field 4130 is less than the length of the extension field 4130, defined by the EXT_LEN field 4122, the extension field 4130 includes the extension payload 4131, and the padding may be included in the remaining part of the extension field 4130. Here, the padding means nonsense data, and the nonsense data may be determined randomly by various methods according to a system design. Furthermore, the filler is not required to be filled with just 0, it can be filled with just 1, and it can be filled with a combination of sense 0 and 1. However, in a case where the filler, according to the embodiment exemplary, is filled only with 0 will be described as an example.

[000214] Furthermore, for example, in FIG. 19, when the fourth field 4114 is set to “10”, which is the fifth value and an actual length of the extension payload 4132 included in the extension field 4123 is less than the length of the extension field 4130, defined by the EXT_LEN field. (LSB) 4123 and the EXT_LEN field (MSB) 4124, the extension field 4130 includes the extension payload 4132, and padding may be included in the remaining part of the extension field 4130.

[000215] However in extension field 4130, when the fourth field 4114 is set to the sixth value, the plurality of extension payloads are included in the extension field 4130 and padding can be included in the remaining part.

[000216] For example, with reference to FIG. 25, when the fourth field 4114 is set to “11”, which is the sixth value, in which case a total effective length of the plurality of fields EXT_TYPE 1 (4141),..., EXT_TYPE N (4143) representing the respective extension payload types the plurality of extension payloads 1 (4145),..., extension payload N (4146) included in extension field 4130, the plurality of fields EXT_LEN field 1 (4142),. .., EXT_LEN field N (4144) representing the respective lengths of the plurality of extension payloads of extension payload 1 (4145), ..., extension payload N (4146), and the plurality of payloads of extension extension payload 1 (4145),..., extension payload N (4146) is less than the length of the extension field 4130, defined by the EXT_LEN field (LSB) 4126 and the EXT_LEN field (MSB) 4127, the extension field 4130 includes the plurality of fields EXT_TYPE 1 (4141),..., EXT_TYPE N (4143), which represents the respective types of the plurality of extension payloads, the plurality of fields EXT_LEN field 1 (4142), ..., EXT_LEN field N (4144), which represent the respective lengths of the plurality of extension payloads, and the plurality of extension payloads of extension payload 1 (4145), ..., extension payload N (4146) and the filler can be included in the remaining part.

[000217] However, how the structure of the packet 4000 is completely changed according to the values defined in the first field 4111 and the fourth field 4114 will be described with reference to FIGS. 20 to 24.

[000218] FIGS. 20 to 24 are diagrams illustrating structures of a package, according to various exemplary embodiments.

[000219] With reference to FIG. 20, when the first field 4111 is set as the first value, the base field 4110 only includes the second field 4112 that represents the LSSBs of the pointer value, and the optional field 4120 and the extension field 4130 are not included in the package 4000, and as a result, the packet includes 4000 includes the base field 4110 which has a size of 1 byte and the payload 4200.

[000220] Referring to FIG. 21, when the first field 4111 is defined as the second value, the base field 4110 includes a second field 4112 that represents the LSBs of the pointer value and a third field 4113 that represents the MSB of the pointer value, and may additionally include a fourth field 4114 that represents an extension mode of the header 4100.

[000221] Therefore, packet 4000 includes base field 4110 which is 2 bytes long. However, in fig. 21, since the fourth field 4114 is defined as the third value, i.e., "00", the optional field 4120 and the extension field 4130 are not included in the package 4000, and as a result, the package 4000 includes the base field 4110 having a size of 2 bytes and the payload 4200.

[000222] Referring to FIG. 22, when the first field 4111 is defined as the second value, the base field 4110 includes a second field 4112, which represents the LSBs of the pointer value, and a third field 4113, which represents the MSBs of the pointer value, and may additionally include a fourth field 4114, which represents an extension mode of the header 4100.

[000223] Therefore, packet 4000 includes base field 4110 which is 2 bytes long. However, in Fig. 22, since the fourth field 4114 is defined as the fourth value, i.e., “01”, the optional field 4120 having a size of 1 byte and the extension field 4130 having a size 1 to 31 bytes are included in packet 4000. As a result, packet 4000 includes base field 4110 which is 2 byte in size, optional field 4120 which is 1 byte in size, extension field 4130 with the size from 1 to 31 bytes, and the payload 4200. Additionally, the optional field 4120 may include an EXT_TYPE field 4121 and an EXT_LEN field 4122.

[000224] Referring to FIG. 23, when the first field 4111 is defined as the second value, the base field 4110 includes a second field 4112, which represents the LSBs of the pointer value, and a third field 4113, which represents the MSB of the pointer value, and may additionally include a fourth field 4114 that represents an extension mode of the header 4100.

[000225] Therefore, packet 4000 includes base field 4110 which is 2 bytes long. However, in Fig. 23, since the fourth field 4114 is set to the fifth value, i.e., “10”, the optional field 4120 with a size of 2 bytes and the extension field 4130 are included in the packet 4000. Here , the length of the extension field 4130 can be defined by the EXT_LEN (LSB) field 4123 and the EXT_LEN (MSB) field 4124, included in the optional field 4120 and can be from 0 to 213 -1 bytes. Additionally, optional field 4120 may include EXT_TYPE field 4121, EXT_LEN (LSB) field 4123, and EXT_LEN (MSB) field 4124.

[000226] Referring to FIG. 24, when the first field 4111 is defined as the second value, the base field 4110 includes a second field 4112, which represents the LSBs of the pointer value, and a third field 4113, which represents the MSB of the pointer value, and may additionally include a fourth field 4114, which represents an extension mode of the header 4100.

[000227] Therefore, packet 4000 includes base header 4110 which is 2 bytes long. However, in fig. 24, since the fourth field 4114 is defined as the sixth value, i.e., “11”, the optional field 4120 which has a size of 2 bytes and the extension field 4130 are included in the packet 4000. Here, the length of extension field 4130 can be defined by the EXT_LEN (LSB) field 4126 and the EXT_LEN (MSB) field 4127, included in the optional field 4127 and can be from 0 to 213-1 bytes. Additionally, the optional field 4120 may include the NUM_EXT field 4125, the EXT_LEN (LSB) field 4126, and the EXT_LEN (MSB) field 4127. Additionally, the extension field 4130 may include the plurality of extension payloads, and its detailed description is described in FIG. 25 in advance and will be omitted.

[000228] The EXT_TYPE field 4121 included in the optional field 4120 represents types of the extension payloads 4131 and 4132, included in the extension field 4130, and can be used to perform various functions according to the predetermined value. For example, different information according to the value defined in the EXT_TYPE field is illustrated in Table 3 below.

[000229] In detail, when the EXT_TYPE field 4121 is set to “000”, the counter function can be performed, and in detail, a predetermined field has a size by a value included in the EXT_LEN field can be included in the extension field 4130 as an extension payload. Here, the predetermined field can perform a function of numbering and identifying a plurality of packets included in a current PLP one by one and the counter value can be increased linearly from 0.

[000230] For example, when the fourth field 4114 is defined as the fourth value, that is, “01” and the EXT_LEN field includes the value of 1, the default field has the size of 1 byte and, as a result, the value The counter can have values from 0 to 255.

[000231] Here, the predetermined field performing the counter function can be used independently, with respect to each PLP, and when the counter value reaches a maximum value, the counter value of the next packet is reset to 0 and increased again.

[000232] Furthermore, with respect to the PLP to which channel bonding is applied, a single counter, that is, a single predetermined field can be used to increase a counter value in the packet, and this can be performed before of the packet being assigned to a specific RF channel.

[000233] The above-mentioned content can be applied to both EXT_TYPE 1 (4141),..., EXT_TYPE N (4143) included in extension field 4130, when the fourth field 4114 is defined as the sixth value, that is, “ 11”.

[000234] When the fourth field 4114 is set to one of the fourth value, i.e., “01” and the fifth value, i.e., “10” and the EXT_TYPE field 4121 is set to “111”, all extension fields 4130 are filled with filler.

[000235] In detail, when the first field 4114 is defined as the fourth value, i.e., “01” or the fifth value, i.e., “10”, the optional field 4120 further includes a fifth field that represents the type of extension payload included in the extension field 4130, that is, the EXT_TYPE field 4121 and a sixth field representing the length of the extension field 4130 (which means the EXT_LEN field 4122 when the fourth field 4114 is the fourth value and the EXT_LEN (LSB) field 4123 and the EXT_LEN (MSB) 4124 field when the fourth field 4114 is the fifth value), and when the fifth field, that is, the EXT_TYPE field 4121 is set to the default value, the extension field 4130 can be completely filled by filling.

[000236] For example, when the fifth field, that is, the EXT_TYPE field 4121 is set to “111”, which means that the extension field 4130 is completely filled by padding, as defined in Table 3, and as a As a result, extension field 4130 is completely filled by padding.

[000237] For example, in the case where the fourth field 4114 is defined as the fourth value, that is, “01” and the EXT_LEN field 4122 includes a value representing that the length of the extension field 4130 is 0 bytes, in Compared to a case where the fourth field 4114 is set to the third value, i.e., "00", the one-byte padding is included in the header 4100. That is, the optional one-byte field 4120 serves as the padding of a byte.

[000238] Furthermore, in the case where the fourth field 4114 is defined as the fifth value, that is, “10” and the EXT_LEN (LSB) field 4123 and the EXT_LEN (MSB) field 4124 include a value representing that the length of the extension field 4130 is 0 bytes, as compared to a case where the fourth field 4114 is set to the third value, i.e., “00”, the 2-byte padding is included in the header 4100. That is, the Optional 2-byte field 4120 serves as the 2-byte padding.

[000239] When the fourth field 4114 is set to the sixth value, that is, "11", as described above, the extension field 4130 is filled with a plurality of extension payloads and the remaining part can be filled with the filling. In this case, it is not necessary for EXT_TYPE 1 (4141),..., EXT_TYPE N (4143) to be defined separately for “111”.

[000240] FIG. 26A is a block diagram illustrating a configuration of a receiving apparatus, in accordance with an exemplary embodiment.

[000241] Referring to FIG. 26A, the receiving apparatus 200 includes a receiver 210, a data extractor 220, and a signal processor 220.

[000242] The receiving apparatus 200 may be implemented to receive data from a mapping of the transmitting apparatus and transmit data included in an input stream in at least one signal processing path.

[000243] Receiver 210 may receive input stream that includes a packet that includes a header and a payload. That is, receiver 210 receives a transmission frame, which includes data mapped into at least one signal processing path. In detail, the receiver 210 may receive signaling information and the stream, which includes data mapped into at least one signal processing path. Here, the signaling information may include information about an input type of the input stream input to the receiving apparatus and information about a type of data mapped into at least one signal processing path. Here, information about the input type of the input stream can represent whether all signal processing paths in the structure are of the same input type. In addition, the detailed information included in the signaling information is described above and the detailed description will be omitted.

[000244] The data extractor 220 extracts the packet header and can extract information representing the starting point of a data packet in the payload and information about whether an additional field is present from the extracted header.

[000245] With regard to the information representing the starting point of the data packet in the payload included in the header and the information about whether the additional field is present, the part for the transmission apparatus 100 is described below and the description details will be omitted.

[000246] The signal processor 230 may process the signal from the data packet included in the payload, based on information representing the starting point of the extracted data packet and information about whether an additional field is present. That is, the starting point of the data packet in the payload is accurately detected based on the information representing the starting point of the data packet, and decoding can be performed from the starting point of the data packet. Additionally, the signal processor 230 can determine whether the received packet includes an optional field and an extension field, based on information about whether the additional field is present, and detect information necessary for signal processing of the data packet to be processed. from the optional field and the extension field.

[000247] Here, the information representing the starting point of the data packet may include information about whether an MSB part is present, according to a distance between the starting point of the payload and the starting point of the data packet .

[000248] Furthermore, information about whether the additional field is present may include information representing whether at least one of the optional field and the extension field are present and the length of the optional field and the extension field.

[000249] Additionally, the optional field may include information representing whether at least one of the optional field and the extension field includes padding.

[000250] Additionally, signal processor 230 extracts signaling information from the received structure. Particularly, the signal processor 230 extracts and decodes the L1 signals to obtain different information about a corresponding PLP included in a pre-signaling area of L1 and a post-signaling area of L1. Furthermore, the signal processor 230 may signal the structure process based on the extracted signaling information. For example, signal processing can perform demodulation, structure building, BICM decoding, and input processing.

[000251] In detail, the signal processor 230 generates a baseband packet by processing the signal structure received by the receiver 210 and generated from it.

[000252] Furthermore, the signal processor 230 can restore current, that is, the input current initially enters the above-mentioned transmission apparatus 100 by signal processing of the payload data included in the baseband packet, with based on the extracted header information.

[000253] However, a receiving apparatus 200, according to another exemplary embodiment, includes a receiver 210, a data extractor 220, and a signal processor 230, the receiver 210 includes a packet that includes a header and a payload, the data extractor 220 can extract the packet header and extract information included in the header, and the signal processor 230 can process the incoming packet signal included in the payload based on the extracted information. Here, the detailed description for the receiver 210, the data extractor 220, and the signal processor 230 is described above and the detailed description will be omitted.

[000254] Additionally, the header includes a first field, defined as a first value representing that a pointer value indicating a first starting point among the respective starting points of the input packets included in the payload is less than the value predetermined, or a second value, which represents that the pointer value is equal to or greater than the predetermined value. When the first field is set to the second value, the header may include a second field that represents the LSBs of the pointer value and a third field that represents the MSBs of the pointer value.

[000255] FIG. 26B is a block diagram provided to explain in detail a signal processor, in accordance with an exemplary embodiment.

[000256] Referring to FIG. 26B, the signal processor 230 includes a demodulator 231, a decoder 232 and a current generator 233.

[000257] The demodulator 231 performs demodulation according to OFDM parameters from received RF signals, performs synchronization detection, and recognizes whether a currently received frame includes necessary data services when synchronization is detected from of signaling information stored in a synchronization area. For example, the demodulator 221 may recognize whether a moving frame is received or a fixed frame is received.

[000258] In this case, if the OFDM parameters are not previously determined with respect to a signaling area and a data area, the demodulator 221 can perform demodulation by obtaining OFDM parameters over the signaling area and the data area. stored in the synchronization area, and obtain information about the OFDM parameters regarding the signaling zone and the data area, which are deleted immediately after the synchronization area.

[000259] The decoder 232 performs the necessary data decoding. In this case, the decoder 232 may perform decoding by obtaining parameters from an FEC method and a modulation method with respect to the data stored in each data area based on the signaling information. Furthermore, decoder 232 can calculate required data positions based on data information included in a configurable field and a dynamic field. Thus, it can be calculated which positions of the structure of a requested PLP are transmitted.

[000260] The current generator 233 can generate data to be served by processing incoming baseband packets from the decoder 232.

[000261] For example, the current generator 233 may generate an ALP packet from the baseband packet, where errors are corrected based on an ISSY mode, buffer size (BUFs), time to output (TTO) and input current clock (ISCR) reference values.

[000262] Specifically, the current generator 233 may include jitter-DE dampers. Jitter-DE dampers can regenerate the correct timing to restore an output current based on ISSY mode, BUFS, TTO values, and ISCR values. In this way, a delay in synchronizing between a plurality of PLPs can be compensated.

[000263] FIG. 27 is a block diagram of a receiving apparatus, according to an exemplary embodiment.

[000264] Referring to FIG. 27, the receiving apparatus 4400 may include a controller 4410, an RF receiver 4420, a demodulator 4430, and a service reader 4440.

[000265] Controller 4410 determines an RF channel and a PLP on which a selected service is transmitted. In this process, the RF channel can be defined by a center frequency and bandwidth, and the PLP can be defined by a PLP identifier (ID). Certain services may be transmitted through more than one PLP, belonging to more than one RF channel by component services. However, it is assumed in the following descriptions that all data necessary for reproducing a service is transmitted through a PLP with an RF channel for convenient explanation. Thus, services are provided with a set of original data obtained from service path, and the obtained path data is specified by an RF channel and a PLP.

[000266] The RF receiver 4420 extracts RF signals from an RF channel selected by the controller 4410, and provides OFDM symbols, extracted by performing signal processing for the RF signals, to the demodulator 4430. The processing Signal processing can include synchronization, channel estimation and equalization. Information required for signal processing is predetermined between a transmitting device and receiving devices or transmitted to the receiving device, in a predetermined OFDM symbol among OFDM symbols.

[000267] The demodulator 4430 extracts a user packet by performing signal processing of the OFDM symbols, and provides service reader 4440. The service reader 4440 executes and outputs the service selected by a user with the user packet. A user package format may be different depending on the execution services. For example, a TS packet or an IPv4 packet can be the user packet.

[000268] FIG. 28 is a block diagram describing the demodulator of Fig. 27, according to an exemplary embodiment.

[000269] Referring to FIG. 28, the demodulator 4430 may include a frame demapper 4431, a BICM decoder 4432 for L1 signaling, a controller 4433, a BICM decoder 4434, and an output processor 4435.

[000270] Frame demapper 4431 selects OFDM cells that constitute FEC blocks belonging to a PLP selected from a frame comprised of OFDM symbols based on control information delivered from controller 4433 and provides to decoder 4434. Furthermore , frame demapper 4431 selects OFDM cells corresponding to more than one FEC block included in L1 signaling, and provides it to BICM decoder 4432 for L1 signaling.

[000271] The BICM decoder 4432 for the L1 signaling signal processor of the OFDM cells corresponding to the FEC blocks belonging to L1 signaling, extracts L1 signaling bits, and provides it to the controller 4433. In this case, the processing of signal may include extracting log likelihood (LLR) values to decode the low density parity check (LDPC) codes in OFDM cells, and decoding the LDPC codes using the extracted LLR values.

[000272] Controller 4433 extracts an L1 signaling table from L1 signaling bits, and controls the operations of the frame demapper 4431, the BICM decoder 4434, and the output processor 4435, using the table values. L1 signaling. FIG. 37 illustrates that the BICM decoder 4432 for L1 signaling does not use control information from the controller 4433 for convenient explanation. However, if L1 signaling includes a layer structure similar to the L1 pre-signaling and L1 post-signaling described above, the BICM decoder 4432 for L1 signaling may be constituted with more decoding blocks than a BICM, and operations of the BICM decoding blocks and the frame demapper 4431 can be controlled based on the upper L1 layer of signaling information, as clearly understood from the above description.

[000273] The BICM decoder 4434 processes the OFDM cells that constitute FEC blocks belonging to the selected PLP, extracts baseband packets, and provides the baseband packets to the output processor 4435. Signal processing may include extracting LLR values for encoding and decoding LDPC codes in OFDM cells, and decoding the LDPC codes using the extracted LLR values. These two operations can be performed based on control information provided from the 4433 controller.

[000274] The output processor 4435 processes the baseband packet signal, extracts a user packet, and provides the extracted user packet to the service reader. In this case, signal processing can be performed on the control information delivered from the 4433 controller.

[000275] However, according to an exemplary embodiment, the output processor 1235 may include an ALP packet processor (not illustrated), which extracts an ALP packet from a baseband packet.

[000276] FIG. 29 is a flow chart provided to briefly explain an operation of a receiving apparatus from a point of time when a user selects a service to a point of time when the selected service is played.

[000277] It is assumed that service information about all services that can be selected in an initial verification process of S4600 is obtained before a service selection process in S4610. The service information may include information about an RF and PLP channel that transmits data necessary for reproduction of a specific service in a current broadcast system. An example of the information service may be Program Specific Information/Service Information (PSI/SI) of an MPEG-2 TS encoder, which may generally be obtained through L2 signaling and a higher layer signaling.

[000278] When a user selects a service on S4610, the receiving device modifies a transmission frequency of the selected service on S4620, and extracts the RF signals on S4630. During execution S4620 by modifying the transmission frequency of the selected service, the service information can be used.

[000279] When RF signals are extracted, the receiver performs S4640 extracting L1 signaling from extracted RF signals. The receiving apparatus selects the PLP transmitting the selected service through the use of L1 signaling extracted at S4650, and extracts baseband packets from the PLP selected by S4660. In the S4650 selecting the PLP transmitting the selected service, the service information can be used.

[000280] Additionally, S4660 extracts baseband packets that may include selected OFDM cells belonging to the PLP by unmapping a transmission frame, extracting the LLR values for LDPC encoding/decoding, and decoding LDPC codes using the LLR values extracted.

[000281] The receiving apparatus performs S4670 extracting an ALP packet from the extracted baseband packet using header information about the extracted baseband packet, and performs S4680 extracting a user packet from the ALP packet extracted using header information about the extracted baseband packet. The extracted user package is used on S1690 running the selected service. In S4670 extract ALP packet and in S4680 extract user packet, L1 signaling information obtained in S4640 extracting L1 signaling can be used. In this case, a process of extracting the user packet from the ALP packet (restoring null TS packet and inserting a TS byte synchronization) is the same as described above. According to exemplary embodiments as described above, various types of data can be mapped to a transmittable physical layer and data processing efficiency can be improved.

[000282] FIG. 30 is a flowchart illustrating a method of controlling a transmission apparatus according to an exemplary embodiment.

[000283] In the method of controlling the transmission apparatus illustrated in FIG. 30, a packet including a header and a payload is generated based on an input packet (S3510).

[000284] Furthermore, the packet is generated from processed signal. (S3520)

[000285] Then, the processed signal packet is transmitted (S3530).

[000286] Here, the header base field configuration includes a first field, defined as a first value, which represents that the base field is a first length, or a second value, which represents that the base field is a second length, and when the first field is set to the second value, the base field may include a second field that represents the LSB of a pointer value, which represents a first value between the respective starting points of the included input packets in the payload and a third field that represents the MSB of the pointer value.

[000287] Additionally, when the first field, the second field, and the third field are included in the header base field configuration, the base field may include a fourth field that represents a header extension mode.

[000288] Additionally, the fourth field may include at least one of the information about whether the optional field is present, a length of the optional field, and an extension field structure.

[000289] Additionally, the fourth field can be defined as a third value representing that the optional field and the extension field are not present, a fourth value representing that the optional field is present, and a length of the optional field is a byte, a fifth value representing that the optional field is present and the length of the optional field is 2 bytes, and a sixth value representing that the optional field is present, the length of the optional field is 2 bytes, and the field extension has a structure to include a plurality of extension payloads.

[000290] Additionally, when the first field is defined as the fourth value or the fifth value, the optional field further includes a fifth field that represents an extension payload type included in the extension field and a sixth field that represents the length of the extension field, and when the fifth field is set to the default value, the extension field can be completely filled by filling.

[000291] Additionally, when the fourth field is set to the fifth value, the optional field may include a field that represents an extension payload type included in the extension field, a field that represents an LSB portion of the length of the extension field, and a field that represents an MSB portion of the length of the extension field.

[000292] Additionally, when the fourth field is set to the sixth value, the optional field may include a field representing the number of a plurality of extension payloads included in the extension field, a field representing a portion of LSB of the length of the extension field, and a field representing an MSB portion of the length of the extension field.

[000293] Here, the extension field may include a plurality of fields representing respective types of the plurality of extension payloads and a plurality of fields representing respective lengths of the plurality of extension payloads.

[000294] Furthermore, the extension field may include an extension payload and the remaining part may include padding, wherein the fourth field is defined as one between the fourth value and the fifth value and the duration of the extension payload. extension included in the extension field is less than the length of the extension field.

[000295] Furthermore, the extension field may include a plurality of extension payloads and the remaining part may include padding when the fourth field is set to the sixth value.

[000296] However, in a method of controlling the transmission apparatus, according to another exemplary embodiment, a packet that includes a header that includes a base header in which information about a starting point of a data packet of payload and information about whether an additional field is present are included, and the payload is generated.

[000297] Here, information about the starting point of the data packet may include information about whether an MSB part is present, according to a distance between the starting point of the payload and the starting point of the data packet. data.

[000298] Furthermore, information about the starting point of the data packet may include one of a first value, which represents the portion of MSB is not present, and a second value which represents the portion of MSB and is present.

[000299] Additionally, information about whether the additional field is present may include information representing whether at least one of the optional field and the extension field are present and the length of the optional field and the extension field.

[000300] Here, the optional field may include information representing whether at least one of the optional field and the extension field includes padding.

[000301] Additionally, information about whether the additional field is present may include one of a first value, which represents that the optional field and the extension field are not present, a second value, which represents that the optional field is present , the extension field is not present and the length of the optional field is one byte, a third value that represents the optional field is present, the extension field is not present and the length of the optional field is 2 bytes, and a fourth value representing that the optional field and extension field are present and the length of the optional field and extension field is greater than 2 bytes.

[000302] Additionally, the optional field may include information representing the length of the extension field when information about whether the additional field is present is set to the fourth value.

[000303] Furthermore, the information representing the length of the extension field may include at least one of the LSB part and the MSB part according to the length of the extension field.

[000304] Furthermore, the generated structure is signal-processed.

[000305] Next, the signal-processed structure is transmitted.

[000306] However, FIG. 31 is a flow chart describing a method for controlling a receiving apparatus in accordance with an exemplary embodiment.

[000307] In the method of controlling the receiving apparatus illustrated in FIG. 31, a stream of packets including a header and a payload is received (S3610).

[000308] Furthermore, the header is extracted from the packet and the information included in the header is extracted (S3620).

[000309] After that, an input packet included in the payload is signal-processed based on the extracted information (S3630).

[000310] Here, the header base field configuration includes a first field defined as a first value representing that the base field is a first length or a second value representing that the base field is a second length, and when the first field is set to the second value, the base field may include a second field representing LSB of a pointer value representing a first value between the respective starting points of the input packets included in the payload and a third field representing MSB of the point value.

[000311] However, in a method of controlling a receiving apparatus, according to another exemplary embodiment, a stream of packets including one in which a header and a payload are included is received.

[000312] Furthermore, the header is extracted from the packet, and information representing a starting point of a data packet in the payload and information about whether an additional field is present are extracted from the extracted header.

[000313] Furthermore, the data packet included in the payload is signal-processed based on information about the starting point of the extracted data packet and information about whether an additional field is present.

[000314] Here, information about the starting point of the data packet may include information about whether an MSB part is present according to a distance between the starting point of the payload and the starting point of the data packet.

[000315] Additionally, information about whether the additional field is present may include information about whether at least one of the optional field and the extension field is present and the length of the optional field and the extension field.

[000316] Additionally, the optional field may include information about whether at least one of the optional field and the extension field includes a filler.

[000317] As described above, according to exemplary embodiments, various types of data can be mapped to a transmittable layer and physical data processing efficiency can be improved.

[000318] However, a non-transitory computer readable medium, in which programs sequentially carrying out the signal processing method according to the above exemplary embodiments are stored can be provided.

[000319] As an example, a non-transitory computer readable medium, in which programs execute generate a packet that includes a header and a payload based on at least one input packet, the generated packet processing signal, and packet transmission of processed signals are stored can be provided.

[000320] Further, as an example, a non-transitory computer readable medium, in which programs execute receiving a stream, which includes a packet that includes a header and a payload, extracting the header from the packet and extracting information included in the header, and signal-processing of an input packet included in the payload based on extracted stored information, may be provided.

[000321] Non-transitory computer readable medium means a medium that semipermanently stores data and can be read by a corresponding apparatus, but a medium that stores data for a short period of time, such as a register, a cache, and a memory. In detail, various applications or programs mentioned above can be stored and delivered to a non-transitory computer readable medium such as a compact disc (CD), a Digital Versatile Disc (DVD), a hard drive, a Blu-ray disc, a universal Serial bus (USB), a memory card, and a read-only memory (ROM) not limited to them.

[000322] At least one of the components, elements, modules or units represented by a block, as illustrated in the drawings, such as FIGs. 6, 7A, 8, 26A, 26B, 27 and 28 may be embodied as various numbers of hardware, software and/or firmware structures that perform respective functions described above, according to an exemplary embodiment. For example, at least one of these components, elements or units may utilize a direct circuit structure, such as a memory, processing, logic, a look-up table, etc., which may perform respective functions through controls of one or more microprocessors or other control devices. Furthermore, at least one of these components, elements or units may be specifically incorporated by a module, a program, or a piece of code, which contains one or more executable instructions to perform the specified logical functions, and executed by one or more microprocessors. or other control devices. Furthermore, at least one of these components, elements or units may further include a processor, such as a central processing unit (CPU), which performs respective functions, a microprocessor, or the like. Two or more of these components, elements or units may be combined into a single component, element or unit that performs all the operations and functions of the combined two or more components, elements or units. Furthermore, at least part of the functions of at least one of these components, elements or units may be performed by another such component, or element of units. Furthermore, although a bus is not illustrated in the block diagrams above, communication between components, elements or units can be carried out through the bus. The functional aspects of exemplary embodiments described above can be implemented in algorithms that run on one or more processors. Furthermore, the components, elements or units represented by a block or processing step may employ any number of related art techniques for electronic configuration, signal processing and/or control, data processing and the like.

[000323] However, detailed exemplary embodiments have been described so far, but various modifications can be made without departing from the scope of the inventive concept. Therefore, the inventive concept should not be limited to the exemplary embodiment and should be defined by the appended claims and equivalents of the appended claims. Industrial Applicability — Sequence Listing Free Text

Claims (12)

1. TRANSMISSION APPARATUS, characterized by the fact that it comprises: a packet generator configured to generate a packet comprising a header and a payload; and a transmitter configured to transmit the generated packet, wherein the header comprises a first field and a second field, wherein the first field comprises a first value or a second value, wherein the first value indicates that a length of the second field is a first length and the second value indicates that the length of the second field is a second length, and wherein, if the first field comprises the first value, the second field is represented as a pointer field, and if the first field comprises the second value, the second field is a concatenation of the pointer field and an added pointer field, wherein the second field comprises a pointer value, wherein the pointer value is an offset from a start of the payload to a first position header of at least one incoming packet starting from the payload, wherein if the first field comprises the second value, the header comprises a third field including one of a third value, a fourth value and a fifth value, wherein the third value indicates the absence of a fourth field and a fifth field in the packet, where the fourth value indicates the presence of the fourth field, the length of which is 1 byte, where the fifth value indicates the presence of the fourth field, the length of which is 2 bytes, wherein the fourth field comprises length information indicating a length of the fifth field, and wherein the third field comprises the fifth value, the fourth field comprises the least significant bits LSB and the most significant bits MSB. 2. Transmission apparatus according to claim 1, characterized by the fact that if the third field comprises the fourth value or the fifth value, the fourth field comprises a sixth field indicating a type of the fifth field. 3. Transmission apparatus according to claim 2, characterized in that the sixth field comprises a value indicating the type of counter or a value indicating all types of filling. 4. Transmission apparatus according to claim 3, characterized by the fact that if the sixth field comprises the value indicating all padding types and the third field comprises a value indicating that the length of the fifth field is 0 bytes , the third field is used as padding. 5. Transmission apparatus according to claim 4, characterized by the fact that if the third field comprises the fourth value, the third field is used as a 1-byte padding, and wherein if the third field comprises the fifth value, the third field is used as 2-byte padding. 6. Transmission apparatus according to claim 1, characterized by the fact that the third field comprises one of the third value, the fourth value, the fifth value and a sixth value, and wherein if the third field comprises the sixth value, the fourth field comprises a seventh field that indicates the number of unfilled extensions in the fifth field. 7. RECEIVING APPARATUS, characterized by the fact that it comprises: a receiver configured to receive a packet comprising a header and a payload; and a processor that processes the received packet, wherein the header comprises a first field and a second field, wherein the first field comprises a first value or a second value, wherein the first value indicates that a length of the second field is a first length and the second value indicates that the length of the second field is a second length, and wherein, if the first field comprises the first value, the second field is represented as a pointer field, and if the first field comprises the second value, the second field is a concatenation of the pointer field and an added pointer field, wherein the second field comprises a pointer value, wherein the pointer value is an offset from a start of the payload to a first start position of at least one input packet starting from the payload, wherein if the first field comprises the second value, the header comprises a third field including one of a third value, a fourth value and a fifth value, wherein the third value indicates the absence of a fourth field and a fifth field in the packet, where the fourth value indicates the presence of the fourth field, the length of which is 1 byte, where the fifth value indicates the presence of the fourth field, the length of which is 2 bytes, wherein the fourth field comprises length information indicating a length of the fifth field, and wherein if the third field comprises the fifth value, the fourth field comprises the least significant bits LSB and the most significant bits MSB. 8. TRANSMISSION METHOD OF A TRANSMISSION APPARATUS, the transmission method characterized by the fact that it comprises: generating a packet comprising a header and a payload; and transmitting the generated packet, wherein the header comprises a first field and a second field, wherein the first field comprises a first value or a second value, wherein the first value indicates that a length of the second field is a first length and the second value indicates that the length of the second field is a second length, and wherein, if the first field comprises the first value, the second field is represented as a pointer field, and if the first field comprises the second value, the second field is a concatenation of the pointer field and an added pointer field, wherein the second field comprises a pointer value, wherein the pointer value is an offset from a start of the payload to a first start position of at least an incoming packet starting at the payload, wherein if the first field comprises the second value, the header comprises a third field including one of a third value, a fourth value and a fifth value, wherein the third value indicates the absence of a fourth field and a fifth field in the packet, where the fourth value indicates the presence of the fourth field, the length of which is 1 byte, where the fifth value indicates the presence of the fourth field, the length of which is 2 bytes, in that the fourth field comprises length information indicating a length of the fifth field, and wherein if the third field comprises the fifth value, the fourth field comprises the least significant bits LSB and the most significant bits MSB. 9. Method according to claim 8, characterized by the fact that if the third field comprises the fourth value or the fifth value, the fourth field comprises a sixth field indicating a type of the fifth field. 10. Method, according to claim 9, characterized by the fact that the sixth field comprises a value that indicates the type of counter or a value that indicates all types of filling. 11. Method according to claim 12, characterized by the fact that if the sixth field comprises the value indicating all padding types and the third field comprises a value indicating that the length of the fifth field is 0 bytes, the third field is used as a filler. 12. METHOD OF RECEIVING A RECEIVING APPARATUS, the method characterized by the fact that it comprises: receiving a packet comprising a header and a payload; and processing the received packet, wherein the header comprises a first field and a second field, wherein the first field comprises a first value or a second value, wherein the first value indicates that a length of the second field is a first length and the second value indicates that the length of the second field is a second length, and wherein, if the first field comprises the first value, the second field is represented as a pointer field, and if the first field comprises the second value, the second field is a concatenation of the pointer field and an added pointer field, wherein the second field comprises a pointer value, wherein the pointer value is an offset from a start of the payload to a first start position of at least one input packet beginning in the payload, wherein if the first field comprises the second value, the header comprises a third field including one of a third value, a fourth value and a fifth value, wherein the third value indicates the absence of a fourth field and a fifth field in the packet, where the fourth value indicates the presence of the fourth field, the length of which is 1 byte, where the fifth value indicates the presence of the fourth field, the length of which is 2 bytes, wherein the fourth field comprises length information indicating a length of the fifth field, and wherein if the third field comprises the fifth value, the fourth field comprises the least significant bits LSB and the most significant bits MSB.