CN111052700B

CN111052700B - Transmitting apparatus, receiving apparatus, and control method thereof

Info

Publication number: CN111052700B
Application number: CN201580061292.2D
Authority: CN
Inventors: 黄盛凞; 李学周; 梁贤九
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2014-11-11
Filing date: 2015-11-11
Publication date: 2022-05-10
Anticipated expiration: 2035-11-11

Abstract

Provided are a transmitting apparatus, a receiving apparatus, and control methods thereof. The transmission 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 signal-processes the generated packet; and a transmitter configured to transmit the signal-processed packet. The basic field configuring the header includes a first field set to a first value indicating that the basic field is a first length or a second value indicating that the basic field is a second length.

Description

Transmitting apparatus, receiving apparatus, and control method thereof

Technical Field

Apparatuses and methods consistent with exemplary embodiments relate to a transmitting apparatus, a receiving apparatus, and a signaling method thereof, which transmit data by mapping the data to at least one signal processing path.

Background

In the 21 st century of information-oriented society, broadcast communication services are entering an era of digitalization, multi-channel, broadband, and high quality. Particularly in recent years, as the use of high-quality digital Televisions (TVs), Portable Multimedia Players (PMPs), and portable broadcasting devices has increased, the need to support various receiving methods has increased even in digital broadcasting services.

Disclosure of Invention

Technical problem

In the actual situation where a standard set establishes various standards as needed to provide various services that meet the needs of users, there is a need to find ways to provide better services with better performance.

Technical scheme

Exemplary embodiments may overcome the above disadvantages and other disadvantages not described above. However, the exemplary embodiments are not required to overcome the disadvantages described above, and may not overcome some of the problems described above.

Exemplary embodiments provide a transmitting device, a receiving device, and a control method capable of generating a frame having a format suitable for transmitting various types of data.

According to an aspect of an exemplary embodiment, there is provided a transmission apparatus, which may include: 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 signal-processes the generated packet; and a transmitter configured to transmit the signal-processed packet. The basic field configuring the header includes a first field set to a first value indicating that the basic field is a first length or a second value indicating that the basic field is a second length. When the first field is set to the second value, the basic field includes a second field representing a Least Significant Bit (LSB) of the pointer value and a third field representing a Most Significant Bit (MSB) of the pointer value indicating a first one of the start points of the input packet included in the payload.

Here, the basic field includes a fourth field indicating an extension mode of the header, and the fourth field includes at least one of information on whether the optional field exists, a length of the optional field, and a structure of the extension field.

Further, the fourth field is set to one of a third value indicating that the optional field and the extension field do not exist, a fourth value indicating that the optional field exists and that the length of the optional field is 1 byte, a fifth value indicating that the optional field exists and that the length of the optional field is 2 bytes, and a sixth value indicating that the optional field exists and that the length of the optional field is 2 bytes and that the extension field has a structure including a plurality of extension payloads.

Further, when the fourth field is set to a fourth value or a fifth value, the optional fields further include a fifth field indicating a type of an extension payload included in the extension field and a sixth field indicating a length of the extension field, and when the fifth field is set to a predetermined value, the extension field is full padding.

Further, when the fourth field is set to the fifth value, the optional fields include a field indicating a type of an extension payload included in the extension field, a field indicating an LSB portion of an extension field length, and a field indicating an MSB portion of the extension field length.

Further, when the fourth field is set to the sixth value, the optional fields include a field indicating the number of the plurality of extension payloads included in the extension field, a field indicating the LSB portion of the extension field length, and a field indicating the MSB portion of the extension field length.

Further, the extension field includes 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.

Further, when the fourth field is set to one of the fourth value and the fifth value and the length of the extension payload included in the extension field is less than the length of the extension field, the extension field includes the extension payload and the padding.

Further, when the fourth field is set to a sixth value, the extension field includes a plurality of extension payloads and padding.

According to another aspect of exemplary embodiments, there is provided a receiving apparatus, which may include: a receiver configured to receive a stream comprising packets including a header and a payload; and at least one processor configured to implement an information extractor that extracts a header from the packet and extracts information included in the header, and a signal processor that performs signal processing on a plurality of input packets included in the payload based on the extracted information. The basic field configuring the header includes a first field set to a first value indicating that the basic field is a first length or a second value indicating that the basic field is a second length. When the first field is set to the second value, the basic field includes a second field representing a Least Significant Bit (LSB) of the pointer value and a third field representing a Most Significant Bit (MSB) of the pointer value indicating a first one of the start points of the input packet included in the payload.

According to another aspect of the exemplary embodiments, there is provided a control method of a transmitting apparatus, which may include: generating a packet including a header and a payload based on a plurality of input packets; performing signal processing on the generated packet; and transmitting the signal-processed packet, the basic field configuring the header including a first field set to a first value indicating that the basic field is a first length or a second value indicating that the basic field is a second length. When the first field is set to the second value, the basic field includes a second field representing a Least Significant Bit (LSB) of the pointer value and a third field representing a Most Significant Bit (MSB) of the pointer value indicating a first one of the start points of the input packet included in the payload.

Further, the basic field includes a fourth field indicating an extension mode of the header, and the fourth field includes at least one of information on whether the optional field exists, a length of the optional field, and a structure of the extension field.

Further, when the fourth field is set to a fourth value or a fifth value, the optional fields further include a fifth field indicating a type of an extension payload included in the extension field and a sixth field indicating a length of the extension field, and when the fifth field is set to a predetermined value, the extension field is completely filled with padding.

According to another aspect of the exemplary embodiments, there is provided a control method of a reception apparatus, which may include: receiving a stream comprising packets including a header and a payload; extracting a header from the packet and extracting information included in the header; a plurality of input packets included in the payload are signal-processed based on the extracted information. The basic field configuring the header includes a first field set to a first value indicating that the basic field is a first length or a second value indicating that the basic field is a second length. The header may include a first field set to a first value indicating that a pointer value indicating a first one of start points of the input packet included in the payload is less than a predetermined value or a second value indicating that the pointer value is equal to or greater than the predetermined value. When the first field is set to the second value, the basic field includes a second field representing a Least Significant Bit (LSB) of the pointer value and a third field representing a Most Significant Bit (MSB) of the pointer value indicating a first one of the start points of the input packet included in the payload.

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

Additional and/or other aspects and advantages of the exemplary embodiments will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the exemplary embodiments.

Technical effects

-

Drawings

The foregoing and/or other aspects will become more apparent by describing certain exemplary embodiments with reference to the attached drawings, wherein:

FIG. 1 is a diagram depicting a hierarchical structure of a transmission system in accordance with an illustrative embodiment;

fig. 2 is a diagram showing a schematic configuration of a broadcast link layer 1400 according to an exemplary embodiment;

fig. 3A is a diagram for describing a schematic configuration of a transmission system according to an exemplary embodiment;

fig. 3B and 3C are diagrams for describing a multiplexing method according to an exemplary embodiment;

FIG. 4 is a block diagram illustrating a detailed configuration of the input formatting block shown in FIG. 3A, according to an exemplary embodiment;

fig. 5A is a block diagram showing a configuration of a baseband formatting block according to an exemplary embodiment, and fig. 5B is a diagram for describing a detailed configuration of a baseband packet according to an exemplary embodiment;

fig. 6 is a block diagram showing a configuration of a transmitting apparatus according to an exemplary embodiment;

fig. 7A is a block diagram showing a detailed configuration of a packet generator according to an exemplary embodiment, and fig. 7B is a diagram showing an ALP packet, a baseband packet, and a scrambled baseband packet according to an exemplary embodiment;

FIG. 8 is a diagram illustrating a packet 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 according to an exemplary embodiment;

fig. 11 to 16D are diagrams illustrating a structure of a pack according to an exemplary embodiment;

fig. 17 is a diagram showing a structure of a package according to another exemplary embodiment;

fig. 18 is a diagram illustrating a detailed configuration of the header illustrated in fig. 17 according to an exemplary embodiment;

fig. 19 is a diagram illustrating a detailed configuration of an optional field according to another exemplary embodiment;

fig. 20 to 24 are diagrams showing the structure of a pack according to an exemplary embodiment;

FIG. 25 is a diagram illustrating the structure of an extension field in accordance with an illustrative embodiment;

fig. 26A is a block diagram showing a configuration of a reception apparatus according to an exemplary embodiment;

fig. 26B is a block diagram illustrating a signal processor according to an exemplary embodiment;

fig. 27 is a block diagram showing a configuration of a receiver according to an exemplary embodiment;

FIG. 28 is a block diagram illustrating a demodulator in more detail according to an example embodiment;

fig. 29 is a flowchart schematically illustrating the operation of a receiver according to an exemplary embodiment;

fig. 30 is a flowchart for describing a control method of a transmitting apparatus according to an exemplary embodiment; and

fig. 31 is a flowchart for describing a control method in a receiving apparatus according to an exemplary embodiment.

Best Mode for Carrying Out The Invention

-

Detailed Description

Hereinafter, various exemplary embodiments of the inventive concept will be described in detail with reference to the accompanying drawings. Further, in the following description, a detailed explanation of known related functions or configurations may be omitted to avoid unnecessarily obscuring the subject matter. Further, terms described below may be changed into terms defined by considering functions according to intentions, conventions, etc. of users and operators. Therefore, the definitions should be made according to the contents of the present specification.

The apparatus and method set forth in the exemplary embodiments can of course be applied to various communication systems including a mobile broadcast service including a Digital Multimedia Broadcasting (DMB) service, a digital video broadcasting handheld (DVP-H), an advanced television systems committee mobile/handheld (ATSC-M/H) service, an Internet Protocol Television (IPTV), and the like, and a communication system including a Moving Picture Experts Group (MPEG) media transmission (MMT) system, an Evolved Packet System (EPS), a Long Term Evolution (LTE) mobile communication system, a long term evolution advanced (LTE-a) mobile communication system, a high speed downlink packet access (HDSPA) mobile communication system, a High Speed Uplink Packet Access (HSUPA) mobile communication system, a third generation partnership project 2(3GPP2) High Rate Packet Data (HRPD) mobile communication system, a method, a communication system, a method, and a method, a communication system, a method, a communication system, and a communication system, a method, and a method, and a method for which are provided for example, A 3GPP2 Wideband Code Division Multiple Access (WCDMA) Mobile communication system, a 3GPP2 Code Division Multiple Access (CDMA) Mobile communication system, an Institute of Electrical and Electronics Engineers (IEEE)802.16m communication system, a Mobile internet protocol (Mobile IP) system, and the like.

Fig. 1 is a diagram illustrating a hierarchical structure of a transmission system according to an exemplary embodiment.

Referring to fig. 1, a service includes media data 1000 and signaling 1050, and the signaling 1050 is used to transmit information required to acquire and consume the media data at a receiver. Media data may be encapsulated into a format suitable for transmission prior to transmission. The encapsulation method may follow the Media Processor (MPU) defined in ISO/IEC 23008-1 MPEG Media Transport (MMT) or the dynamic adaptive streaming over ISO/IEC 23009-1 HTTP (DASH) segment format defined in DASH. Media data 1000 and signaling 1050 are packetized according to an application layer protocol.

Fig. 1 shows a case of using an MMT protocol (MMTP)1110 and a transport-over-the-real-time object transport (ROUTE) protocol 1120 defined in MMT as application layer protocols. In this case, a method is required to notify information about an application protocol through which a service is transmitted by a separate method different from the application layer protocol so that a receiver knows through which application layer protocol the service is transmitted.

The Service List (SLT)1150 shown in fig. 1 represents or indicates a signaling method, and packetizes information on services in the table to satisfy the above object. Details of the SLT will be described below. The packetized media data and signaling including the SLT are transmitted to the broadcast link layer 1400 through a User Datagram Protocol (UDP)1200 and an Internet Protocol (IP) 1300. Examples of the broadcast link layer 1400 include 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 by using an IP packet as an input and transfers the ALP packet to the broadcast physical layer 1500.

However, in accordance with fig. 2 to be described below, it is noted that the broadcast link layer 1400 may use not only IP packets 1300 including media data and/or signaling as inputs, but also MPEG2-TS packets or packetized data in a common format. In this case, signaling information required for controlling the broadcast link layer is also transferred to the broadcast physical layer 1500 in the form of an ALP packet.

The broadcast physical layer 1500 generates a physical layer frame by signal-processing the ALP packet as an input, converts the physical layer frame into a radio signal, and transmits the radio signal. In this case, the broadcast physical layer 1500 has at least one signal processing path. Examples of signal processing paths may include the physical layer channel (PLP) of ATSC 3.0 or the digital video broadcasting-second generation terrestrial (DVB-T2) standard, and one or more services or some services may be mapped to the PLP.

Fig. 2 is a diagram showing a schematic configuration of a broadcast link layer 1400 according to an exemplary embodiment.

Referring to fig. 2, the input to the broadcast link layer 1400 includes IP packets 1300, and may also include link layer signaling 1310, MPEG2-TS packets 1320, and other packetized data 1330.

The incoming data may undergo additional signal processing prior to ALP packet 1450 based on the type of incoming data. As an example 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 packetization, the input packets may be split and combined.

Fig. 3A is a diagram showing a schematic configuration of a transmission system or a transmission apparatus according to an exemplary embodiment. According to fig. 3A, a transmission system 10000 according to an exemplary embodiment may include input formatting blocks 11000 and 11000-1, Bit Interleaving and Coded Modulation (BICM) blocks 12000 and 12000-1, framing/interleaving blocks 13000 and 13000-1, and waveform generating blocks 14000 and 14000-1.

Input formatting blocks 11000 and 11000-1 generate baseband packets from the data input stream to be serviced. Here, the input stream may be a Transport Stream (TS), an Internet Packet (IP) (e.g., IPv4 and IPv6), an MPEG Media Transport (MMT), a General Stream (GS), a General Stream Encapsulation (GSE), and the like. For example, an ATSC 3.0 link layer protocol (ALP) packet may be generated based on an input stream, and a baseband packet may be generated based on the generated ALP packet.

Bit Interleaving and Code Modulation (BICM) blocks 12000 and 12000-1 determine a Forward Error Correction (FEC) coding rate and a constellation order according to a region (fixed PHY frame or mobile PHY frame) to which data to be serviced is to be transmitted, and perform coding and time interleaving. Meanwhile, the signaling information on the data to be serviced may be encoded by a separate BICM encoder according to a user implementation or by sharing a BICM encoder with the data to be serviced.

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

The waveform generation blocks 14000 and 14000-1 generate an Orthogonal Frequency Division Multiplexing (OFDM) signal in a time domain of the generated transmission frame, modulate the generated OFDM signal into an RF signal, and transmit the RF signal to a receiver.

The transmission system 10000 according to the exemplary embodiment shown in fig. 3A includes a standard block marked with a solid line and an information block marked with a dotted line. Here, the block marked with a solid line is a normal block, and the block marked with a dotted line is a block that can be used when information Multiple Input Multiple Output (MIMO) is realized.

Fig. 3B and 3C are diagrams illustrating a multiplexing method according to an exemplary embodiment.

Fig. 3B illustrates a block diagram for implementing Time Division Multiplexing (TDM), according to an example embodiment.

The TDM system architecture includes four main blocks (or portions): input formatting block 11000, BICM block 12000, framing/interleaving block 13000, and waveform generation block 14000.

Data is input and formatted in an input formatting block 11000 and forward error correction is applied to the data in a BICM block 12000. Next, the data is mapped to a constellation. Subsequently, the data is time-interleaved and frequency-interleaved in a framing/interleaving block 13000, and a frame is generated. Thereafter, an output waveform is generated in the waveform generation block 14000.

Fig. 3C shows a block diagram for implementing Layered Division Multiplexing (LDM), according to an example embodiment.

The LDM system architecture includes several other blocks compared to the TDM system architecture. Specifically, two separate input formatting blocks 11000 and 11000-1 and BCIM blocks 12000 and 12000-1 for one of the various layers of LDM are included in the LDM system architecture. These blocks are combined in an LDM injection block before the framing/interleaving block 13000. Also, the waveform generation block 14000 is similar to TDM.

Fig. 4 is a block diagram illustrating a detailed configuration of an input formatting block illustrated in fig. 3A according to an exemplary embodiment.

As shown in fig. 4, the 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 (or baseband framing block) 11300, and a scheduler block 11200.

The input stream to the encapsulation and compression block 11100 may be of various types. For example, the input stream may be a Transport Stream (TS), an Internet Packet (IP) (e.g., IPv4 and IPv6), an MPEG Media Transport (MMT), a General Stream (GS), a General Stream Encapsulation (GSE), and the like.

The packet output from the encapsulation and compression block 11100 becomes an ALP packet (general packet) (also referred to as an L2 packet). Here, the format of the ALP packet may be one of a Type Length Value (TLV), GSE, and ALP.

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

The scheduler block 11200 receives an input stream including encapsulated ALP packets to form a physical layer channel (PLP) in the form of baseband packets. In TDM systems, only one PLP, referred to as a single PLP (S-PLP) or multiple PLPs (M-PLPs), may be used. One service may not use four or more PLPs. In an LDM system consisting of two layers, one per layer, i.e. two PLPs, is used.

The scheduler block 11200 receives the encapsulated ALP packets to specify how the encapsulated ALP packets are to be allocated to physical layer resources. In detail, scheduler block 11200 specifies how baseband formatting block 11300 outputs baseband packets.

The function of the scheduler block 11200 is defined by data size and time. The physical layer may send some data in a distributed time. The scheduler block 11200 generates a solution suitable for the configuration of physical layer parameters by using the input and information from the encapsulated packet (such as constraints and configuration), the quality of service metadata for the encapsulated packet, the system buffer model, and system management. The goal of this solution is to achieve available configuration and control parameters and aggregated spectrum.

At the same time, the operation of the scheduler block 11200 is constrained to a set of dynamic, quasi-static, and static components. The definition of constraints may vary depending on the user implementation.

In addition, a maximum of four PLPs can be used for each service. Multiple services including multi-type interleaving blocks may be implemented by up to 64 PLPs for bandwidths of 6MHz, 7MHz, or 8 MHz.

Baseband formatting block 11300 includes baseband packet building blocks 3100, 3100-1,.. times, 3100-n, baseband packet header building blocks 3200, 3200-1,.. times, 3200-n, and baseband packet scrambling blocks 3300, 3300-1, i.times, 3300-n, as shown in fig. 5A. In M-PLP operation, the baseband formatted block generates multiple PLPs as needed.

Base band package building blocks 3100, 3100-1. Each baseband packet 3500 includes a header 3500-1 and a payload 3500-2 as shown in fig. 5B. The baseband packet is fixed as a length K payload. The ALP packets 3610 to 3650 are sequentially mapped to the base band packet 3500. When the ALP packets 3610 to 3650 do not fit completely into the baseband packet 3500, these packets are distributed between the current baseband packet and the next baseband packet. The ALP packet is distributed in units of bytes.

Baseband packet header building blocks 3200, 3200-1, 3200-n construct a header 3500-1. The header 3500-1 includes three parts, a basic field (also referred to as a basic 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 shown in fig. 5B. Here, a basic field 3710 is shown in each baseband packet, and an optional field 3720 and an extension field 3730 may not be shown in each baseband packet.

The main function of the basic field 3710 is to provide an offset value pointer as a byte to indicate the start of the next ALP packet in the base band packet. When the baseband packet starts with an ALP packet, the value of the pointer is 0. When the baseband packet does not start with an ALP packet, the value of the pointer may be 8191, and a 2-byte basic header may be used.

The extension field 3730 may be used later and is used, for example, for baseband packet counters, baseband packet timestamps, additional signaling, and so forth.

Base band packet scrambling blocks 3300, 3300-1.

Fig. 6 is a block diagram illustrating a configuration of a transmitting apparatus according to an exemplary embodiment.

Referring to fig. 6, the transmitting apparatus 100 includes a packet generator 110, a signal processor 120, and a transmitter 130.

The packet generator 110 may generate a packet, such as a baseband packet (optionally, an L1 packet), including a header and a payload based on the input packet. Here, the packet includes a header and a payload containing the input packet, and is defined as k payloads having a fixed length. The length of the packet may be set according to the selected code rate and code length. Here, the input packet may be, for example, an ATSC link layer protocol (ALP) packet. The ALP packet includes one of an Internal Protocol (IP) packet, a Transport Stream (TS) packet, and a signaling packet, or may include a combination thereof. In detail, an input IP packet, a TS packet, and various types of data are encapsulated to be generated as an ALP packet for transmission to each PLP, and the ALP packet corresponds to an L2 packet in the ISO 7-layer model. Further, the data included in the payload is not limited to the above-described examples, and the payload may include various types of data. Hereinafter, for convenience of explanation, the packet generated by the packet generator 110 is referred to as a baseband packet, and the input packet is referred to as an ALP packet.

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

Fig. 7A is a block diagram showing a detailed configuration of a packet generator according to an exemplary embodiment.

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

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

In detail, the ALP packet constructor 110' may generate an ALP packet (i.e., an L2 packet) including a header and ALP payload data based on an input stream. Here, the header denotes a header of the ALP packet and may include information on ALP payload data included in the ALP packet and information on at least one packet included in the ALP packet.

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

Specifically, when the input stream is a TS, the baseband packet header generator 110-1 may generate a baseband packet header including information on the number of TS packets, the number of removed null packets, and the like in the ALP packet. In addition, the baseband packet header generated by the baseband packet header generator 110-1 may include various information to be described below.

In addition, the baseband packet constructor 110-2 encapsulates the baseband packet header generated from the baseband packet header generator 110-1 in the ALP packet output from the ALP packet constructor 110' to generate a baseband packet.

Further, the packet generator 110 arranges a plurality of ALP packets including IP packets and headers to generate the arranged ALP packets as base band packets having a size corresponding to the FEC code. The baseband packets according to the exemplary embodiment may be TS packets, but the same procedure may be applied to the various types of data and TS packets described above.

In addition, the baseband packet scrambler 115 mixes data stored in the baseband packets in a random order before the FEC code is added to each baseband packet to generate scrambled baseband packets. The scrambled baseband packet is transmitted through the PLP for signal processing. In this case, one PLP may be constituted by a baseband packet of a fixed size. That is, the input stream may be encapsulated into a baseband packet for one PLP.

Meanwhile, PLP refers to a signal path processed independently. That is, respective services (e.g., video, extended video, audio, data streams, etc.) may be transmitted and received through a plurality of RF channels, and the PLP is a path through which the services are transmitted or a stream transmitted through the path. Further, the PLPs may be located at time slots distributed over a plurality of RF channels at intervals, or distributed over one RF channel at intervals. That is, one PLP may be transmitted while being distributed over one RF channel or a plurality of RF channels at time intervals.

The PLP structure is composed of an input pattern a providing one PLP and an input pattern B providing a plurality of PLPs. When the PLP structure supports the input mode B, the PLP structure can provide a strong specific service and increase a time interleaving length by distributing and transmitting one stream to obtain a time diversity gain. Further, when only a specific stream is received, the power of the receiver is turned off for use at low power for the remaining time, and as a result, the receiver is suitable for providing portable and mobile broadcasting services.

Here, time diversity is a technique in which, when a transmitting side transmits the same signal a plurality of times at predetermined time intervals to reduce deterioration of transmission quality in a mobile communication transmission path, a receiving side synthesizes the received signals again to obtain excellent transmission quality.

In addition, information that can be commonly transmitted to a plurality of PLPs is included in one PLP to be transmitted to improve transmission efficiency. In this case, the PLP0 performs such a role, and the PLP is referred to as a common PLP, and the remaining PLPs other than the PLP0 can be used for data transmission, and the remaining PLPs are referred to as data PLPs. When such PLPs are used, home HDTV programs can be received and SDTV programs can be provided even when carried and moved. In addition, various broadcasting services can be provided to viewers through a broadcasting base station or a broadcasting content provider, and a differentiated service that can receive broadcasts can be provided even in an edge area where viewing is difficult.

Meanwhile, fig. 7B is a diagram illustrating an ALP packet, a baseband packet, and a scrambled baseband packet according to an exemplary embodiment.

Referring to fig. 7B, when the ALP packet constructor 110' stores a TS packet in an ALP payload and inserts a header to generate a plurality of ALP packets 111' and 112', the packet generator 110 aggregates and inserts a plurality of generated ALP packets 111' and 112' into a base band packet header to generate a plurality of

base band packets

121 and 122. Here, each of the

baseband packets

121 and 122 may include a plurality of ALP packets, and may further include some of the ALP packets.

Base band packet scrambler 115 randomly scrambles

base band packets

121 and 122 to generate a plurality of scrambled base band packets 125-1 and 125-2. Further, the scrambled baseband packets 125-1 and 125-2 are transmitted to the PLP as described above, and signal processing for adding the FEC codes is performed.

Referring back to fig. 6, the signal processor 120 may perform signal processing on the generated packet. Here, the generated packet refers to the baseband packet as described above.

In detail, the signal processor 120 performs signal processing on the baseband packet to generate a transmission frame.

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

Meanwhile, the L1 pre-signaling region may include information for analyzing the L1 post-signaling and information on the entire system, and the L1 pre-signaling region may be implemented to always have the same length. In addition, the L1 post-signaling region may include information on individual PLPs and information on a system, and the L1 signaling region included in individual frames has the same length in one superframe, but the content included in the L1 signaling region may vary.

Meanwhile, although not shown, the signal processor 120 may perform functions corresponding to the Bit Interleaving and Code Modulation (BICM) blocks 12000 and 12000-1 and the framing/interleaving blocks 13000 and 13000-1 shown in fig. 3A through 3C.

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

In detail, the transmitter 130 may perform functions corresponding to the waveform generation blocks 14000 and 14000-1 shown in fig. 3A to 3C. That is, the transmitter 130 performs modulation for modulating the generated frame into an RF signal and transmits the RF signal to a receiving apparatus (not shown).

Meanwhile, fig. 8 is a diagram illustrating a packet structure according to an exemplary embodiment. Here, it is predefined that the packet generated from the packet generator 110 used in this specification is a baseband packet.

Referring to fig. 8, a baseband packet is composed of a header 3100 and a payload 3200. The header 3100 may be divided into a basic field 3110, an optional field 3120, and an extended field 3130 again according to its role. Here, the basic field will be defined to have the same meaning as the basic header. The baseband packet header 3100 may necessarily include a basic field 3110, and whether or not an optional field 3120 exists may be changed according to a control field value of the basic field 3110. Further, whether the extension field 3130 exists may be selected by using the control field of the optional field 3120.

Meanwhile, the basic field, the optional field, and the extension field used in this specification may correspond to a basic header, an optional header, and an extension header, respectively.

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

Fig. 9 is a diagram illustrating a structure of a header according to an exemplary embodiment.

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

Meanwhile, in this specification, terms such as a basic header, an optional field, and an extension field are used and described, but of course, these terms may be expressed by general words such as a first header, a second field, and a third field.

In detail, the baseband packet may be largely divided into a header and a payload, and here, the header may be composed of three parts as shown in fig. 9. The first part is a basic header 2310 and is present in all packets. Further, the second part is an optional field 2320 and the third part is an extension field 2330. The optional field 2320 and the extension field 2330 are not always present in all packets, and the base header 2310 includes information indicating (or indicating) whether the optional field 2320 and the extension field 2330 are present.

In addition, the header may include a basic header 2310 including information indicating the start point of the packet in the payload 2340 and information including whether additional fields exist. That is, the base header 2310 may include information indicating the start point of the packet in the payload 2340. In detail, the base header 2310 may perform a function of providing a pointer including a byte unit offset value up to a start point of a next general packet (also referred to as a "data packet" or an "ALP packet") existing in the packet 2300. Here, the start point of the packet refers to a distance between the start point of the payload 2340 and the start point of the packet, and the distance may be expressed by the above byte unit offset value.

As shown in fig. 7B, the first ALP packet 111 'is not fragmented and may be included in the first packet 121, but may be fragmented together with the second ALP packet 112' to be included in the first packet 121 and the second packet 122.

In this case, the basic header included in the header of the first packet 121 may include information indicating a start point of the first ALP packet 111', and in detail, may include information including a distance between a payload start point of the first packet 121 and a start point of the first ALP packet 111'.

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

For example, when the general packet is arranged from the start point in the packet, the value of the pointer may be set to 0. In addition, the pointer may be extended to 2 bytes, and thus, the value represented by the pointer may be increased to 8191. That is, the base header 2310 may represent a distance to a starting point (where the general packet starts in the packet) by a value 8191.

Specifically, the information indicating the start point of the packet (i.e., the ALP packet) may include information on whether a Most Significant Bit (MSB) portion of the indicator is present, which is obtained according to a distance between the start point of the payload and the start point of the packet, and may include one of a first value indicating that the MSB portion is not present and a second value indicating that the MSB portion is present. That is, when the information indicating the start point of the packet is set to 0, it indicates that the MSB part does not exist, and when the information indicating the start point of the packet is set to 1, it indicates that the MSB part exists.

Referring to fig. 9, the basic header 2310 has a MODE field 2311, the MODE field 2311 including information on a start point of a packet, and the MODE field 2311 indicating whether there is an MSB portion of a pointer. Here, the MODE field 2311 may be 1 bit in size.

When the MODE field 2311 is set to 0, the MODE field 2311 indicates that the distance from the start of the payload 2340 to the start of a new general packet (i.e., a data packet) in the payload 2340 is a short pointer length. Here, the short pointer length means a length of not more than 127 bytes. Thus, the pointer field, which includes information about the distance from the start point of the payload 2340 to the start point of the new generic packet in the payload 2340, includes only the pointer (LSB) field 2312 corresponding to the short pointer length and does not include the pointer (MSB) field 2313. Here, the pointer (LSB) field 2312 is 7 bits in length.

Also, when the MODE field 2311 is set to 0, the pointer field includes only the pointer (LSB) field 2312, and thus the length of the basic header 2310 becomes 1 byte.

Meanwhile, when the MODE field 2311 is set to 1, the MODE field 2311 indicates that the distance from the start point of the payload 2340 to the start point of the new general packet in the payload 2340 is a long pointer length. Here, the long pointer length may be equal to or greater than 128 bytes. Thus, the pointer field, which includes information about the distance from the start of the payload 2340 to the start of the new generic packet in the payload 2340, may include a pointer (MSB) field 2313 and a pointer (LSB) field 2312 to represent a long pointer length. The pointer (MSB) field 2313 is 6 bits in length.

In addition, when the MODE field 2311 is set to 1, the basic header 2310 may include an OHI field 2314 indicating information on whether additional fields exist in the header. OHI field 2314 is 2 bits in length.

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

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

Meanwhile, the information on whether the additional field exists in the header may include information on whether at least one of the optional field 2320 and the extension field 2330 exists and the lengths of the optional field 2320 and the extension field 2330.

Further, the information on whether the additional field exists may include one of a first value indicating that the optional field 2320 and the extension field 2330 do not exist, a second value indicating that the optional field 2320 exists and the extension field 2330 does not exist and the length of the optional field 2320 is 1 byte, a third value indicating that the optional field 2320 exists and the extension field 2330 does not exist and the length of the optional field 2320 is 2 bytes, and a fourth value indicating that the optional field 2320 and the extension field 2330 exist and the length of the optional field 2320 and the extension field 2330 exceeds 2 bytes.

Also, when information on whether the additional field exists is set to a fourth value, the optional field 2320 may include information indicating the length of the extension field 2330, and may include at least one of the LSB portion and the MSB portion according to the length of the extension field.

Information regarding whether additional fields are present may be stored in the Optional Header Indicator (OHI) field 2314. In detail, the length of the OHI field 2314 is 2 bytes, and the length of the optional field 2320 may be equal to or less than 2 bytes. Information indicating the value stored in the OHI field 2314 may be summarized in table 1 below.

TABLE 1

[ Table 1]

In detail, how to include the optional field 2320 and the extension field 2330 in the header according to the value set in the OHI field 2314 will be described with reference to fig. 10.

Fig. 10 is a diagram illustrating a detailed configuration of an optional field according to an exemplary embodiment.

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.

In addition, when OHI field 2314 is set to 01, the header includes an optional field 2320 that is 1 byte in length. Here, the optional field 2320 may include information indicating whether the optional field 2320 includes padding. In detail, the optional field 2320 may include an EXT _ TYPE field 2321 indicating whether the optional field 2320 includes padding. Here, the EXT _ TYPE field 2321 is 3 bits long. In addition, in the optional field 2320 of 1 byte, a 5-bit residual region 2322 excluding the EXT _ TYPE field 2321 may include predetermined information or padding. The remaining area 2322 may include predetermined information or padding according to information included in the EXT _ TYPE field 2321. Here, the padding refers to meaningless data, and the meaningless data may be randomly determined by various methods according to system design. Further, the padding need not be padded with only 0, may be padded with only 1, and may be padded with a meaningless combination of 0 and 1. However, a case where the padding is only 0 will be described as an example.

In addition, when the OHI field 2314 is set to 10, the header includes an optional field 2320 that is 2 bytes in length. Similarly, optional field 2320 may include information indicating whether optional field 2320 includes padding. In detail, the optional field 2320 may include an EXT _ TYPE field 2321 indicating whether the optional field 2320 includes padding, and here, the EXT _ TYPE field 2321 is 3 bits long. Further, of the 2 bytes of the optional field 2320, the remaining 5-bit region 2322 and 8-bit region 2323 excluding the EXT _ TYPE field 2321 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 information stored in the EXT _ TYPE field 2321. Here, the padding refers to meaningless data, and the meaningless data may be randomly determined by various methods according to system design.

Meanwhile, when the OHI field 2314 is set to 11, the header may include an extension field 2330 and an optional field 2320. Here, the 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 1 byte or may be 2 bytes. In addition, the optional field 2320 may include information indicating whether at least one of the optional field 2320 and the extension field 2330 includes padding. In detail, the optional field 2320 may include an EXT _ TYPE field 2321 indicating whether at least one of the optional field 2320 and the extension field 2330 includes padding, and here the length of the EXT _ TYPE field 2321 is 3 bits.

However, when the OHI field 2314 is set to 11, the EXT _ TYPE field 2321 sets a value corresponding to the TYPE of the extension field 2330. For example, when padding is stored in the extension field 2330, the EXT _ TYPE field 2321 has a value that means that padding is stored in the extension field 2330. Further, when the OHI field 2314 is set to 11, the optional field 2320 includes information indicating the length of the extension field 2330, and thus may include at least one of an LSB portion and an MSB portion depending on the length of the extension field 2330. Here, the optional field 2320 may include at least one of an EXT _ len (lsb) field 2324 and an EXT _ len (msb) field 2325 indicating the length of the extension field 2330. EXT _ len (lsb) field 2324 may be 5 bits in length and EXT _ len (msb) field 2325 may be 8 bits in length.

When the EXT _ TYPE field 2321 described above is summarized, the EXT _ TYPE field 2321 is a 3-bit field indicating the TYPE of the extension field, the OHI field 2314 is set to 01, and when the EXT _ TYPE field 2321 is set to 000, a bit sequence "00000" may be stored in the optional field 2320. In addition, the OHI field 2314 is set to 10, and when the EXT _ TYPE field 2321 is set to 000, a bit sequence "00000000" other than the bit sequence "00000" may be additionally stored in the optional field 2320. Further, when the OHI field 2314 is set to 11, the EXT _ TYPE field 2321 is filled with a value corresponding to the TYPE of the extension field 2330, and at least one of an EXT _ len (lsb) field 2324 and an EXT _ len (msb) field 2325 may be connected and arranged. Here, when the EXT _ TYPE field 2321 is set to 000, padding (i.e., a bit sequence 00000 or a bit sequence 00000000) is padded in the optional field 2320, but this is merely an example, and of course, what the value set in the EXT _ TYPE field 2321 indicates may vary according to a design method.

The EXT _ LEN (LSB) field 2324 represents the length of the extension field 2330 and includes the 5 LSB bits of the EXT _ LEN field. When the OHI field 2314 is set to 11, the EXT _ len (lsb) field 2324 is always present.

Further, when the EXT _ LEN (MSB) field 2325 includes 8 MSB bits of the EXT _ LEN field and the EXT _ LEN (MSB) field 2325 is present, the optional field 2320 includes a total of 13 bits of the EXT _ LEN field, in which the EXT _ LEN (lsb) field 2324 and the EXT _ LEN (MSB) field 2325 are connected to each other. Accordingly, when the length of the extension field 2330 is equal to or less than a 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 a predetermined length, the optional fields 2320 may include an EXT _ len (lsb) field 2324 and an EXT _ len (msb) field 2325.

Meanwhile, how the structure of the packet 2300 is completely changed according to the values set in the MODE field 2311 and OHI field 2314 will be described with reference to fig. 11 to 16D.

Fig. 11 to 16D are diagrams illustrating a structure of a pack according to various exemplary embodiments.

Referring to fig. 11, when the MODE field 2311 is set to 0, the MODE field 2311 indicates a short pointer length, and thus the base header 2310 includes only the pointer (LSB) field 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 a basic header 2310 and a payload 2340 of 1 byte length.

Referring to fig. 12, when the MODE field 2311 is set to 1, the MODE field 2311 indicates a long pointer length, and thus the basic header 2310 includes a pointer (LSB) field 2312 and a pointer (MSB) field 2313, and may further include an OHI field 2314, the OHI field 2314 including information on whether the optional field 2320 and the extension field 2330 exist.

Thus, the packet 2300 includes a basic header 2310 that is 2 bytes in length. 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 a base header 2310 and a payload 2340 that are 2 bytes in length.

Referring to fig. 13, when the MODE field 2311 is set to 1, the MODE field 2311 indicates a long pointer length, and thus, the basic header 2310 includes a pointer (LSB) field 2312 and a pointer (MSB) field 2313, and may further include OHI field 2314, the OHI field 2314 including information on whether the optional field 2320 and the extension field 2330 exist.

Thus, the packet 2300 includes a basic header 2310 that is 2 bytes in length. However, in fig. 13, the OHI field 2314 is set to 01, and thus, an optional field 2320 of 1 byte length is included in the package 2300, and an extension field 2330 is not included in the package 2300. As a result, the packet 2300 includes a base header 2310 of length 2 bytes, an optional field 2320 of length 1 byte, and a payload 2340. In addition, optional field 2320 may include a 3-bit EXT _ TYPE field 2321 and a 5-bit padding field 2322.

Referring to fig. 14, when the MODE field 2311 is set to 1, the MODE field 2311 indicates a long pointer length, and thus the basic header 2310 includes a pointer (LSB) field 2312 and a pointer (MSB) field 2313, and may further include an OHI field 2314, the OHI field 2314 including information on whether the optional field 2320 and the extension field 2330 exist.

Thus, the packet 2300 includes a basic header 2310 that is 2 bytes in length. However, in fig. 14, the OHI field 2314 is set to 10, and thus, an optional field 2320 of 2 bytes in length is included in the package 2300, and an extension field 2330 is not included in the package 2300. As a result, the packet 2300 includes a base header 2310 of length 2 bytes, an optional field 2320 of length 2 bytes, and a payload 2340. In addition, optional fields 2320 may include a 3-bit EXT _ TYPE field 2321, a 5-bit pad field 2322, and an 8-bit pad field 2323.

Referring to fig. 15, when the MODE field 2311 is set to 1, the MODE field 2311 indicates a long pointer length, and thus the basic header 2310 includes a pointer (LSB) field 2312 and a pointer (MSB) field 2313, and may further include an OHI field 2314, the OHI field 2314 including information on whether the optional field 2320 and the extension field 2330 exist.

Thus, the packet 2300 includes a basic header 2310 that is 2 bytes in length. However, in fig. 15, the OHI field 2314 is set to 11 to include a basic header 2310 of length 2 bytes, an optional field 2320 of length 2 bytes, an extension field 2330, and a payload 2340. In addition, optional fields 2320 may include an EXT _ TYPE field 2321, an EXT _ len (lsb) field 2324, and an EXT _ len (msb) field 2325.

In fig. 15, a case is shown where the optional fields 2320 include an EXT _ len (lsb) field 2324 and an EXT _ len (msb) field 2325. However, optional field 2320 may include only EXT _ len (lsb) field 2324. In this case, the package 2300 may include a basic header 2310 of length 2 bytes, an optional field 2320 of length 1 byte, an extension field 2330, and a payload 2340.

Further, in the above example, the case where the optional field 2320 has at least one of the 5-bit pad field 2322 and the 8-bit pad field 2323 is exemplified, but the optional field 2320 may include predetermined data other than pad and the EXT _ TYPE field 2321 may further include a value representing the predetermined data.

Meanwhile, fig. 16A to 16D illustrate that when the OHI field 2314 is set to 11, data filled in the optional field 2320 and the extension field 2330 may vary according to a value set in the EXT _ TYPE field 2321.

Referring to fig. 16A, when the OHI field is set to 11, the optional fields 2320 include a TYPE field 2321, an EXT _ len (lsb) field 2324, and an EXT _ len (msb) field 2325, and a representative example of the presence of an extension field 2330 is shown.

Here, when the TYPE field 2321 is set to 001, the optional field 2320 may include only an EXT _ len (lsb) field 2324, and the extension field 2330 may include an Input Stream Synchronization (ISSY) field 2331 and padding 2332. Here, in order to describe a case where the extension field 2330 includes predetermined data, the ISSY field 2331 is illustrated. ISSY field 2331 is used to transmit the clock counter value according to the clock modulation ratio and regenerate the exact timing for recovery of the output stream by the receiver of the transmitted frame.

Further, referring to fig. 16B, when the TYPE field 2321 is set to 010, the optional field 2320 may include an EXT _ len (lsb) field 2324 and an EXT _ len (msb) field 2325, and the extension field 2330 may include an ISSY field 2333 and padding 2332.

Of course, the extension field 2330 may include various data other than the ISSY field 2333 as predetermined data. Referring to fig. 16C, when the TYPE field 2321 is set to 011, the optional field 2320 includes an EXT _ len (lsb) field 2324 and an EXT _ len (msb) field 2325, and the extension field 2330 may include an in-band signal TYPE a field 2334 and padding 2332. Referring to fig. 16D, when the TYPE field 2321 is set to 100, the optional field 2320 includes an EXT _ len (lsb) field 2324 and an EXT _ len (msb) field 2325, and the extension field 2330 may include an in-band signal TYPE B field 2335 and a pad 2332.

Meanwhile, terms used to describe the above-described ALP packet and baseband packet may vary according to a system, and for example, the above-described ALP packet and baseband packet may be referred to as baseband packet and baseband frame, respectively, according to the system.

According to another exemplary embodiment, the optional field and the extension field may include fields having different structures, and will be described in detail with reference to fig. 17 to 25. Further, before describing that the optional fields and the extension fields may include fields having different structures, the description of the fields included in the basic field described below may correspond to a portion described in fig. 9, but will be described again by using general terms.

Referring back to fig. 6, the transmitting apparatus 100 includes a packet generator 110, a signal processor 120, and a transmitter 130, and the packet generator 110 may generate a packet including a header and a payload based on an input packet.

Here, the input packet may be, for example, an ALP packet (also referred to as an L2 packet), and the packet generated in the packet generator 110 may be a baseband packet (BBP) (also referred to as an L1 packet). Of course, as described above, the terminology of the packets may vary according to the system, and for example, the above-described ALP packet and BBP packet may be referred to as a BBP packet and a baseband frame (BBF), respectively, according to the system.

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

Further, the input packet, i.e., the ALP packet, includes one of an Internal Protocol (IP) packet, a TS packet, and a signaling packet, or may include a combination thereof. In detail, input IP packets and TS packets and various types of data are encapsulated to generate ALP packets for transmission to each PLP, and the ALP packets correspond to L2 packets in the ISO 7-layer model. However, the data included in the payload is not limited to the above example, and the payload may include various types of data.

In addition, the signal processor 120 may perform signal processing on the generated packet. In detail, the signal processor 120 performs signal processing on the packet to generate a transmission frame. In addition, the signal processor 120 may insert signaling information into a signaling region of a frame. Here, the signaling information may be a layer 1(L1) signaling signal transmitting an L1 signal for frame synchronization, and the preamble into which the L1 signaling information is inserted may include an L1 pre-signaling region and an L1 post-signaling region. Further, the post-L1 signaling region includes a configurable field and a dynamic field.

Although not shown, the signal processor 120 may perform functions corresponding to the Bit Interleaving and Code Modulation (BICM) blocks 12000 and 12000-1 and the framing/interleaving blocks 13000 and 13000-1 shown in fig. 3A through 3C.

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

In detail, the transmitter 130 may perform functions corresponding to the waveform generation blocks 14000 and 14000-1 shown in fig. 3A to 3C. That is, the transmitter 130 performs modulation for modulating the generated frame into an RF signal and transmits the RF signal to a receiving device or a receiver.

Meanwhile, the basic field of the configuration header includes a first field set to a first value indicating that the basic field is a first length or a second value indicating that the basic field is a second length, and when the first field is set to the second value, the basic field may include a second field indicating Least Significant Bits (LSBs) of a pointer value indicating a first value among respective start points of an input packet included in the payload and a third field indicating Most Significant Bits (MSBs) of the pointer value.

Further, the header of the packet may be divided into a basic field, an optional field, and an extension field according to its role, as shown in fig. 8 described above, and the header must include the basic field and whether the optional field exists may vary according to the value of the control value included in the basic field. Further, whether the extension field exists may be selected according to the value of the control field included in the optional field.

Here, the first field, the second field, and the third field may be included in a basic field of the configuration header.

In detail, it will be described in detail with reference to fig. 17.

Fig. 17 is a diagram illustrating a structure of a package according to another exemplary embodiment.

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 the packet 4000.

Here, one input packet is divided to be included in payloads of different packets, like the first input packet in the plurality of input packets 4201. In addition, the basic field may inform the start point of the input packet by a pointer value. Here, the pointer value refers to an offset from a start point of the payload to a first one of respective start points of the input packets included in the payload.

In detail, a first field 4111 included in the basic field of the header 4100 may be set to a first value indicating that the basic field is a first length, i.e., 1 byte, or a second value indicating that the basic field is a second length, i.e., 2 bytes.

In particular, when the first field 4111 is set to a first value and thus the basic field is 1 byte, the basic field may include only the second field representing the LSB of the pointer value representing the first value in each start point of the input packet included in the payload 4200, and as a result, the pointer value may represent only less than a predetermined value.

Further, when the first field 4111 is set to a second value and thus the basic field is 2 bytes, the basic field may include a second field representing the LSB of the pointer value and a third field representing the MSB of the pointer value, which indicates the first value in each start point of the input packet included in the payload, and as a result, the pointer value may indicate even greater than or equal to a predetermined value.

Here, the predetermined value may be 128 bytes, and as a result, the pointer value may represent only less than 128 bytes when the first field 4111 is set to a first value, and the pointer value may represent even more than or equal to 128 bytes when the first field 4111 is set to a second value.

For example, when any one input packet is arranged to match the start point of the payload 4200 of the packet 4000 and thus the start point of the corresponding input packet is the same as the start point of the payload, the pointer value representing the value corresponding to the start point of the corresponding input packet may become 0. That is, since the start point of the input packet may be digitized and calculated based on the start point of the payload 4200, the pointer value representing the value corresponding to the start point of the corresponding input packet, which is at the same start point as the payload 4200, may become 0.

Further, as shown in fig. 17, when any one input packet is divided to be included in the payload 4200 as the first input packet among the plurality of input packets 4201, the start point of the first input packet exists in the previous packet and does not exist in the corresponding payload 4200, and thus, the first start point of the respective start points of the input packets included in the payload 4200 immediately becomes the start point of the second input packet. Accordingly, the pointer value representing the value corresponding to the start point of the second input packet may immediately become a value corresponding to the distance 4202 from the start point of the second input packet based on the start point of the payload 4200.

Further, when the first field 4111 is set to a first value, the basic field of the header 4100 may include only the second field 4112 representing the LSB of the pointer value, and when the first field 4111 is set to a second value, the basic field of the header 4100 may include the second field 4112 representing the LSB of the pointer value and the third field 4113 representing the MSB of the pointer value.

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

In addition, the MODE field may indicate whether there is a third field 4113 indicating the MSB of the pointer value and whether there is a fourth field indicating the extension MODE of the header. In detail, when the MODE field is set to 0, the indication basic field includes only the second field 4112 indicating the LSB of the pointer value. Here, the second field 4112 may be a pointer (LSB) field indicating the LSB of the pointer value, and the size of the pointer (LSB) field may be 7 bits. Therefore, when the MODE field is set to 0, the pointer value has to be expressed below 128 bytes, and the size of the basic field is 1 byte including the MODE field (1 bit) and the pointer (LSB) field (7 bits).

In addition, when the MODE field is set to 1, the basic field may include a second field 4112 representing the LSB of the pointer value and a third field 4113 representing the MSB of the pointer value. Here, the third field 4113 indicating the MSB of the pointer value may be a pointer (MSB) field, and the size of the pointer (MSB) field may be 6 bits. Therefore, when the MODE field is set to 1, the pointer value can be extended and expressed as 8191 bytes by a total of 13 bits obtained by adding the pointer (LSB) field (7 bits) and the pointer (MSB) field (6 bits), and the size of the basic field is 2 bytes including the MODE field (1 bit), the pointer (LSB) field (7 bits), the pointer (MSB) field (6 bits), and the fourth field (2 bits) indicating the extension MODE of the header 4100 to be described below. As a result, only when the MODE field is set to 1, a pointer (MSB) field and a fourth field indicating the extension MODE of the header 4100 may be included in the basic field.

Accordingly, when the pointer value representing the first value in the start point of the input packet in the payload 4200 of the packet 4000 is less than 128 bytes, the first field 4111, i.e., the MODE field, is set to 0, and the basic field includes the second field 4112, i.e., the pointer only (LSB) field, and thus the size of the basic field is 1 byte. When the pointer value representing the first value in the start point of the input packet in the payload 4200 of the packet 4000 is equal to or greater than 128 bytes, the first field 4111, i.e., the MODE field, is set to 1, and the basic fields include the second field 4112, i.e., the pointer (LSB) field, the third field 4113, i.e., the pointer (MSB) field, and the fourth field, and thus the size of the basic fields is a total of 2 bytes.

Further, when the start point of an input packet in the payload 4200 of the packet 4000 does not exist, since a value corresponding to the start point of the corresponding input packet is not defined, the pointer value becomes 8191, and thus, the MODE field is set to 1 and the size of the basic field is 2 bytes.

Further, even when the input packet does not exist and only padding exists in the payload 4200 of the packet 4000, the pointer value becomes 8191, and thus, the MODE field is set to 1 and the size of the basic field is 2 bytes.

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, the header 4100 includes the basic field 4110, and may further include the optional field 4120 and the extension field 4130, and may determine whether the fourth field 4114 representing the extension mode of the header 4100 described below is included.

Further, as described above, when the first field 4111 is set to a first value, the basic field 4110 includes only the second field 4112, and thus it can be seen that the length of the basic field 4110 has a size of 1 byte in total, including 1 bit of the first field 4111 and 7 bits of the second field 4112.

Further, as described above, when the first field 4111 is set to the second value, the basic field 4110 includes the second field 4112, the third field 4113, and the fourth field 4114 representing the extension mode of the header 4100, and thus it can be seen that the length of the basic field 4110 has a size of 2 bytes in total, including the 1-bit first field 4111, the 7-bit second field 4112, the 6-bit third field 4113, and the 2-bit fourth field 4114.

Meanwhile, when the first field 4111 is set to a second value, the basic field 4110 includes a fourth field 4114 indicating an extension mode of the header 4100, and the fourth field 4114 may include at least one of information on whether the optional field 4120 and the extension field 4130 exist, a length of the optional field 4120, and a structure of the extension field 4130.

In detail, the fourth field 4114 is set to one of a third value indicating that the optional field 4120 and the extension field 4130 are not present, a fourth value indicating that the optional field 4120 is present and the length of the optional field 4120 is 1 byte, a fifth value indicating that the optional field 4120 is present and the length of the optional field 4120 is 2 bytes, and a sixth value indicating that the optional field 4120 is present and the length of the optional field 4120 is 2 bytes and the extension field 4130 has a structure including a plurality of extension payloads.

Here, the fourth field 4114 may be an OFI field, and the size of the OFI field may be 2 bits. In detail, the information represented by the value set in the OFI field may be summarized as in table 2 below.

TABLE 2

[ Table 2]

In detail, how to include the optional field 4120 and the extension field 4130 in the header 4100 according to the value set in the fourth field 4114 will be described with reference to fig. 19.

Fig. 19 is a diagram illustrating a detailed configuration of an optional field according to another exemplary embodiment.

Referring to fig. 19, when the fourth field is set to "00" as a third value, the header 4100 includes only the basic field 4110 and does not include the optional field 4120 and the extension field 4130.

Further, when the fourth field is set to "01" as a fourth value, the header 4100 may further include an optional field 4120 of 1 byte size in addition to the basic field 4110 as a short extension mode. In addition, the presence or absence and the length of the extension field 4130 may be determined by fields included in the optional field 4120.

In detail, the optional fields 4120 may include a field 4121(EXT _ TYPE field) indicating the TYPE of the extension payload 4131 included in the extension field 4130 and a field 4122(EXT _ LEN field) indicating the length of the extension field 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.

Here, the EXT _ TYPE field 4121 is 3 bits in size and indicates the TYPE of the extension payload 4131 included in the extension field 4130, which will be described in detail below. Further, the EXT _ LEN field 4122 is 5 bits in size and may represent the length of the extension field 4130 in the range of 0 to 31 bytes.

When the EXT _ LEN field 4122 is 0, the length of the extension field 4130 is 0, and thus the extension field 4130 is not present in the header 4100.

In fig. 19, it is shown that when the fourth field 4114 is set to "01" as a 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 the case where there is 1 byte in the size of the optional field 4120, and the case where there is 2 bytes in the size of the optional field 4120, two fields are separated in the figure. In practice, when the fourth field 4114 is set to "01" as a fourth value, the size of the optional field 4120 is 1 byte, and thus the extension field 4130 is subsequently added to the optional field 4120. Accordingly, the EXT _ LEN field 4122 included in the optional field 4120 and the extension payload 4131 included in the extension field 4130 are arranged adjacent to each other.

Further, when the fourth field 4114 is set to "10" as a fifth value, the header 4100 may further include an optional field 4120 of 2 bytes in size, in addition to the basic field 4110, as a long extension mode. In addition, the presence or absence and the length of the extension field 4130 may be determined by fields included in the optional field 4120.

In detail, the optional fields 4120 may include a field (EXT _ TYPE field) 4121 indicating the TYPE of the extended payload 4132 included in the extension field 4130, a field (EXT _ Len (LSB) field) 4123 indicating the LSB part of the length of the extension field 4130, and a field (EXT _ len (MSB) field) 4124 indicating the MSB part of the length of the extension field 4130. Here, as described above, since the EXT _ TYPE field 4121 is defined as the fifth field and the field indicating the length of the extension field 4130 is defined as the sixth field, the EXT _ Len (LSB) field 4123 may be defined as the LSB portion indicating the sixth field and the EXT _ len (MSB) field 4124 may be defined as the MSB portion indicating the sixth field.

Here, the EXT _ TYPE field 4121 is 3 bits in size and indicates the TYPE of the extension payload 4132 included in the extension field 4130, which will be described in detail below.

Further, the size of the EXT _ Len (LSB) field 4123 may be 5 bits for representing the LSB portion of the total 13 bits of the length of the extension field 4130, and the size of the EXT _ len (MSB) field 4124 may be 8 bits for representing the MSB portion of the total 13 bits of the length of the extension field 4130. In addition, a field of total 13 bits connecting the EXT _ len (lsb) field 4123 and the EXT _ len (msb) field 4124 may represent the length of the extension field 4130 in a range from 0 to the entire length of the packet 4000.

Of course, when the field of the total 13 bits connecting the EXT _ len (lsb) field 4123 and the EXT _ len (msb) field 4124 is 0, the length of the extension field is 0, and thus the extension field 4130 is not present in the header 4100.

Further, when the fourth field is set to "11" as a sixth value, the header 4100 may further include an optional field 4120 of 2 bytes in size in addition to the basic field 4110 as a hybrid extension mode. In addition, the presence or absence and the length of the extension field 4130 and the structure of the extension field 4130 may be determined by fields included in the optional field 4120.

In detail, the optional fields 4120 may include a field (NUM _ EXT field) 4125 indicating the number of the plurality of extended payloads 4133 included in the extended field 4130, a field (EXT _ Len (LSB) field) 4126 indicating an LSB portion of the length of the extended field 4130, and a field (EXT _ len (MSB) field) 4127 indicating an MSB portion of the length of the extended field 4130.

Here, the NUM _ EXT field 4125 is 3 bits in size and may indicate the number of the plurality of extended payloads 4133 included in the extended field 4130 except for padding.

In particular, the extension field 4130 may indicate the presence of two to seven extension payloads, and a detailed structure thereof will be described with reference to fig. 25.

Further, the EXT _ Len (LSB) field 4126 may be 5 bits in size for representing the LSB portion of the total 13 bits of the length of the extension field 4130, and the EXT _ len (MSB) field 4127 may be 8 bits in size for representing the MSB portion of the total 13 bits of the length of the extension field 4130.

Meanwhile, while the structure of the extension field 4130 will be described, the length of the extension field 4130, which may be represented by a field of total 13 bits connecting the EXT _ len (lsb) field 4126 and the EXT _ len (msb) field 4127, will be described together.

Fig. 25 is a diagram illustrating a structure of an extension field according to an exemplary embodiment.

When the fourth field 4114 is set to a 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 extension payloads.

In detail, referring to fig. 25, when the fourth field 4114 is set to a sixth value, i.e., "11", this means a hybrid extension mode, and thus the extension field 4130 may include a plurality of extension payload extension payloads 1(4145),. -, extension payload N (4146). In this case, the extension field 4130 may include a plurality of fields EXT _ TYPE 1(4141) representing respective TYPEs of the plurality of extended payload extension payloads 1(4145),. ·, extended payload N (4146), EXT _ TYPE N (4143), and a plurality of fields EXT _ LEN 1 fields (4142),.., EXT _ LEN fields (4144) representing respective lengths of the plurality of extended payload extension payloads 1(4145),.., extended payload N (4146). Here, as described above, since the extension field 4130 may include 2 to 7 extension payloads, N may range from 2 to 7.

None of the plurality of extended payloads (extended payload 1(4145),.., extended payload N (4146)) includes padding.

In addition, when one extended payload is included in the extension field 4130, one EXT _ TYPE field and one EXT _ LEN field indicating the TYPE of the corresponding extended payload are included in the extension field 4130. Here, when it is considered that the size of the EXT _ TYPE field is 3 bits and the size of the EXT _ LEN field is 13 bits, a header having a size of a total of 2 bytes with respect to one extended payload is included in the extended field 4130. Here, the header includes an EXT _ TYPE field and an EXT _ LEN field, and will be defined by general terms of fields set at the front end of the extension field 4130.

Accordingly, when N extended payloads are included in the extended field 4130, the extended field 4130 includes a header having a total of 2N bytes, including a plurality of EXT _ TYPE fields and EXT _ LEN fields associated with the respective extended payloads.

As described above, the extension field 4130 may include at least two extension payloads, and as a result, may include a header having 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 payload, and in this case, the length of the extension field 4130 has to be at least 4 bytes.

As a result, the length of the extension field 4130, which may be represented by a field of total 13 bits connecting the EXT _ len (lsb) field 4126 and the EXT _ len (msb) field 4127 described in fig. 19, may represent the length of the extension field 4130 in a range from 4 bytes to the entire length of the packet 4000.

Each of the EXT _ LEN 1 fields (4142),.. and EXT _ LEN fields (4144) shown in fig. 25 may include an EXT _ LEN (lsb) field of 5 bits in size and an EXT _ LEN (msb) field of 8 bits in size. Thus, for an extended payload, a header of size 2 bytes includes an EXT _ TYPE field of size 3 bits, an EXT _ len (lsb) field of size 5 bits, and an EXT _ len (msb) field of size 8 bits.

Further, in the extension field 4130, when the fourth field 4114 is set to one of a fourth value and a fifth value, a length of an extension payload included in the extension field 4130 is smaller than a length of the extension field 4130, the extension payload is included in the extension field 4130, and padding may be included in the remaining portion.

For example, in fig. 19, when the fourth field 4114 is set to "01" as a fourth value and the actual length of the extension payload 4131 included in the extension field 4130 is smaller 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 padding may be included in the remaining portion of the extension field 4130. Here, the filler means meaningless data, and the meaningless data may be randomly determined by various methods according to system design. Further, the padding need not be padded with only 0, may be padded with only 1, and may be padded with a meaningless combination of 0 and 1. However, a case where the padding is only 0 according to the exemplary embodiment will be described as an example.

Further, for example, in fig. 19, when the fourth field 4114 is set to "10" as a fifth value and the actual length of the extension payload 4132 included in the extension field 4130 is smaller than the length of the extension field 4130 defined by the EXT _ len (lsb) field 4123 and the EXT _ len (msb) field 4124, the extension field 4130 includes the extension payload 4132 and padding may be included in the remaining portion of the extension field 4130.

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

For example, referring to fig. 25, when the fourth field 4114 is set to "11" as a sixth value, in the case where a plurality of fields EXT _ TYPE 1(4141) representing respective TYPEs of a plurality of extended payload extended payloads 1(4145), EXT _ TYPE N (4146) included in the extended field 4130 and a plurality of fields EXT _ LEN 1 fields (4142) representing respective lengths of a plurality of extended payload extended payloads 1(4145), EXT _ TYPE N (4143), and a plurality of fields EXT _ LEN 1 fields (4142) representing respective lengths of a plurality of extended payload extended payloads 1(4145), EXT _ LEN fields (4144), and a plurality of payload extended payloads 1(4145), the total actual length of the EXT _ LEN, extended payload N (4146) is smaller than the length of the extended field 30 defined by the EXT _ LEN (lsb) field 4126 and the EXT _ LEN (msb) field 4127, the extension field 4130 includes a plurality of fields EXT _ TYPE 1(4141), EXT., EXT _ TYPE N (4143) representing respective TYPEs of a plurality of extension payloads, a plurality of fields EXT _ LEN 1 fields (4142), EXT., EXT _ LEN N fields (4144) representing respective lengths of a plurality of extension payloads, and a plurality of payload extension payloads 1(4145), EXT., extension payload N (4146), and padding may be included in the remaining portion.

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

Fig. 20 to 24 are diagrams illustrating a structure of a pack according to various exemplary embodiments.

Referring to fig. 20, when the first field 4111 is set to a first value, the basic field 4110 includes only the second field 4112 representing the LSB of the pointer value, and the optional field 4120 and the extension field 4130 are not included in the packet 4000, and as a result, the packet 4000 includes the basic field 4110 and the payload 4200 having a size of 1 byte.

Referring to fig. 21, when the first field 4111 is set to a second value, the basic field 4110 includes a second field 4112 representing the LSB of the pointer value and a third field 4113 representing the MSB of the pointer value, and may further include a fourth field 4114 representing the extension mode of the header 4100.

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

Referring to fig. 22, when the first field 4111 is set to a second value, the basic field 4110 includes a second field 4112 representing the LSB of the pointer value and a third field 4113 representing the MSB of the pointer value, and may further include a fourth field 4114 representing the extension mode of the header 4100.

Thus, the packet 4000 includes a basic field 4110 having a length of 2 bytes. However, in fig. 22, since the fourth field 4114 is set to a fourth value, i.e., "01", an optional field 4120 of 1 byte in size and an extension field 4130 of 1 to 31 bytes in size are included in the packet 4000. As a result, the packet 4000 includes a base field 4110 of 2 bytes in size, an optional field 4120 of 1 byte in size, an extension field 4130 of 1 to 31 bytes in size, and a payload 4200. In addition, the optional fields 4120 may include an EXT _ TYPE field 4121 and an EXT _ LEN field 4122.

Referring to fig. 23, when the first field 4111 is set to a second value, the basic field 4110 includes a second field 4112 representing the LSB of the pointer value and a third field 4113 representing the MSB of the pointer value, and may further include a fourth field 4114 representing the extension mode of the header 4100.

Thus, the packet 4000 includes a basic field 4110 having a length of 2 bytes. However, in fig. 23, since the fourth field 4114 is set to a fifth value, i.e., "10", an optional field 4120 and an extension field 4130 of 2 bytes in size are included in the packet 4000. Here, the length of the extension field 4130 may be defined by an EXT _ len (lsb) field 4123 and an EXT _ len (msb) field 4124 included in the optional field 4120, and may be from 0 to 2¹³1 byte. In addition, the optional fields 4120 may include an EXT _ TYPE field 4121, an EXT _ len (lsb) field 4123, and an EXT _ len (msb) field 4124.

Referring to fig. 24, when the first field 4111 is set to a second value, the basic field 4110 includes a second field 4112 representing the LSB of the pointer value and a third field 4113 representing the MSB of the pointer value, and may further include a fourth field 4114 representing the extension mode of the header 4100.

Thus, the packet 4000 includes a basic field 4110 having a length of 2 bytes. However, in fig. 24, since the fourth field 4114 is set to a sixth value, "11", an optional field 4120 and an extension field 4130 of 2 bytes in size are included in the packet 4000. Here, the length of the extension field 4130 may be defined by an EXT _ len (lsb) field 4126 and an EXT _ len (msb) field 4127 included in the optional field 4120, and may be from 0 to 2¹³1 byte. Further, the optional fields 4120 may include a NUM _ EXT field 4125, an EXT _ len (lsb) field 4126, and an EXT _ len (msb) field 4127. In addition, the extension field 4130 may include a plurality of extension payloads, a detailed description of which is described in advance in fig. 25 and will be omitted.

The EXT _ TYPE field 4121 included in the optional field 4120 indicates the TYPEs of the

extension payloads

4131 and 4132 included in the extension field 4130, and may be used to perform various functions according to a predetermined value. For example, different information according to the value set in the EXT _ TYPE field is as shown in table 3 below.

TABLE 3

[ Table 3]

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

In detail, when the EXT _ TYPE field 4121 is set to "000", a counter function may be performed, and in detail, a predetermined field having a size of a value included in the EXT _ LEN field may be included in the extension field 4130 as an extension payload. Here, the predetermined field may perform a function of numbering and identifying a plurality of packets included in the current PLP one by one, and the counter value may be linearly increased from 0.

For example, when the fourth field 4114 is set to a fourth value, i.e., "01", and the EXT _ LEN field includes a value of 1, the predetermined field size is 1 byte, and as a result, the counter value may have values of 0 to 255.

Here, a predetermined field performing a counter function may be independently used for 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.

Further, for PLPs to which channel bonding is applied, a single counter, i.e., a single predetermined field, may be used to increase the counter value in the packet, and may be performed before the packet is allocated to a specific RF channel.

When the fourth field 4114 is set to a sixth value, i.e., "11", the above may be applied even to EXT _ TYPE 1(4141), …, EXT _ TYPE N (4143) included in the extension field 4130.

When the fourth field 4114 is set to one of a fourth value, i.e., "01", and a fifth value, i.e., "10", and the EXT _ TYPE field 4121 is set to "111", all of the extension fields 4130 are filled with padding.

In detail, when the fourth field 4114 is set to a fourth value, i.e., "01", or a fifth value, i.e., "10", the optional fields 4120 further include a fifth field, i.e., an EXT _ TYPE field 4121, indicating the TYPE of the payload included in the extension field 4130, and a sixth field, i.e., an EXT _ len (lsb) field 4123 when the fourth field 4114 is the fourth value and an EXT _ len (msb) field 4124 when the fourth field 4114 is the fifth value, and when the fifth field, i.e., the EXT _ TYPE field 4121, is set to a predetermined value, the extension field 4130 may be completely filled with padding.

For example, when the fifth field, i.e., the EXT _ TYPE field 4121, is set to "111", this means that the extension field 4130 is completely filled with padding, as defined in table 3, and as a result, the extension field 4130 is completely filled with padding.

For example, in the case where the fourth field 4114 is set to a fourth value, "01", and the EXT _ LEN field 4122 includes a value indicating that the length of the extension field 4130 is 0 bytes, 1-byte padding is included in the header 4100, as compared to the case where the fourth field 4114 is set to a third value, "00". That is, the optional field 4120 of 1 byte serves as a padding of 1 byte.

Further, in the case where the fourth field 4114 is set to a fifth value, i.e., "10", and the EXT _ len (lsb) field 4123 and the EXT _ len (msb) field 4124 include a value indicating that the length of the extension field 4130 is 0 bytes, 2 bytes of padding are included in the header 4100, as compared to the case where the fourth field 4114 is set to a third value, i.e., "00". That is, the optional field 4120 of 2 bytes serves as a pad of 2 bytes.

When the fourth field 4114 is set to a sixth value, "11", the extension field 4130 is filled with a plurality of extension payloads, and the remaining portion may be filled with the padding, as described above. In this case, it is not necessary to set EXT _ TYPE 1(4141), …, EXT _ TYPE N (4143) to "111", respectively.

Fig. 26A is a block diagram showing a configuration of a reception apparatus according to an exemplary embodiment.

Referring to fig. 26A, the receiving apparatus 200 includes a receiver 210, an information extractor 220, and a signal processor 230.

The receiving device 200 may be implemented to receive data, and the transmitting device maps and transmits data included in an input stream on at least one signal processing path.

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

The information extractor 220 extracts a header from the packet, and may extract information indicating a start point of the packet in the payload and information on whether there is an additional field from the extracted header.

A portion for the transmitting apparatus 100 is described in advance with respect to information indicating a start point of a packet included in a payload in a header and information regarding whether an additional field exists, and a detailed description will be omitted.

The signal processor 230 may perform signal processing on the data packet included in the payload based on the information indicating the start point of the extracted data packet and the information regarding whether the additional field exists. That is, the start point of the packet in the payload is accurately detected based on the information indicating the start point of the packet, and decoding can be performed from the start point of the packet. Further, the signal processor 230 may determine whether the received packet includes an optional field and an extension field based on information on whether the additional field exists and detect information required for signal processing of the data packet from the optional field and the extension field.

Here, the information indicating the start point of the packet may include information on whether or not the MSB part exists depending on the distance between the start point of the payload and the start point of the packet.

Further, the information on whether the additional field exists may include information indicating whether at least one of the optional field and the extension field exists and lengths of the optional field and the extension field.

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

Further, the signal processor 230 extracts signaling information from the received frame. In particular, the signal processor 230 extracts and decodes the L1 signaling to obtain various information on the corresponding PLPs included in the L1 pre-signaling region and the L1 post-signaling region. Further, the signal processor 230 may perform signal processing on the frame based on the extracted signaling information. For example, signal processing may perform demodulation, frame de-framing, BICM decoding, and input de-processing.

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

Further, the signal processor 230 may restore a stream, i.e., an input stream initially input to the above-described transmitting apparatus 100, by signal-processing payload data included in the baseband packet based on the extracted header information.

Meanwhile, the reception apparatus 200 according to another exemplary embodiment includes a receiver 210, an information extractor 220, and a signal processor 230, the receiver 210 includes a packet including a header and a payload, the information extractor 220 may extract the header from the packet and extract information included in the header, and the signal processor 230 may perform signal processing on an input packet included in the payload based on the extracted information. Here, the descriptions of the receiver 210, the information extractor 220, and the signal processor 230 are as above, and a detailed description will be omitted.

Further, the header includes a first field set to a first value indicating that a pointer value indicating a first one of start points of the input packet included in the payload is less than a predetermined value or a second value indicating 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 representing the LSB of the pointer value and a third field representing the MSB of the pointer value.

Fig. 26B is a block diagram illustrating in detail a signal processor according to an exemplary embodiment.

Referring to fig. 26B, the signal processor 230 includes a demodulator 231, a decoder 232, and a stream generator 233.

The demodulator 231 performs demodulation according to the OFDM parameters from the received RF signal, performs synchronization detection, and recognizes whether the currently received frame includes necessary service data when synchronization is detected from the signaling information stored in the synchronization area. For example, the demodulator 231 may identify whether a moving frame is received or a fixed frame is received.

In this case, if the OFDM parameter is not previously determined for the signaling region and the data region, the demodulator 231 may perform demodulation by obtaining the OFDM parameter for the signaling region and the data region stored in the synchronization region and obtaining information on the OFDM parameter for the signaling region and the data region disposed after the synchronization region.

The decoder 232 performs decoding of necessary data. In this case, the decoder 232 may perform decoding by obtaining parameters of the FEC method and the modulation method for the data stored in each data region based on the signaling information. In addition, the decoder 232 may calculate the position of necessary data based on data information included in the configurable field and the dynamic field. Therefore, it can calculate the position of the frame transmitting the requested PLP.

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

For example, the stream generator 233 may generate an ALP packet from an error-corrected baseband packet based on an ISSY pattern, a buffer size (BUFS), a time-to-output (TTO) value, and an Input Stream Clock Reference (ISCR) value.

In particular, stream generator 233 may include a de-jitter buffer. The de-jitter buffer may regenerate the correct timing to restore the output stream based on the ISSY pattern, BUFS, TTO value and ISCR value. So that the synchronization delay between the PLPs can be compensated.

Fig. 27 is a block diagram of a receiving device according to an example embodiment.

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

The controller 4410 determines an RF channel and a PLP in which the selected service is transmitted. In this procedure, the RF channel may be defined by a center frequency and a bandwidth, and the PLP may be defined by a PLP Identifier (ID). Some services may be transmitted through more than one PLP belonging to more than one RF channel served by each component. However, it is assumed in the following description that all data required for playing one service is transmitted through one PLP having one RF channel for convenience of explanation. Therefore, the service is provided with a unique data acquisition path to play the service, and the data acquisition path is specified by the RF channel and the PLP.

The RF receiver 4420 extracts an RF signal from the selected RF channel by the controller 4410 and transfers an OFDM symbol extracted by performing signal processing on the RF signal to the demodulator 4430. Signal processing may include synchronization, channel estimation, and equalization. Information required for signal processing is predetermined between the transmitting apparatus and the receiving apparatus or transmitted to the receiving apparatus in a predetermined OFDM symbol among OFDM symbols.

The demodulator 4430 extracts a user packet by performing signal processing on the OFDM symbol and transmits to the service player 4440. The service player 4440 plays and outputs the service of the user package selected by the user. The format of the user packets may vary depending on the implementation service. For example, the TS packet or IPv4 packet may be a user packet.

Fig. 28 is a block diagram depicting the demodulator of fig. 27 according to an exemplary embodiment.

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.

The frame demapper 4431 selects OFDM cells constituting an FEC block belonging to the selected PLP from a frame constituted by OFDM symbols based on the control information transmitted from the controller 4433, and transmits it to the decoder 4434. In addition, the frame demapper 4431 selects OFDM cells corresponding to more than one FEC block included in the L1 signaling and transfers them to the BICM decoder 4432 for the L1 signaling.

The BICM decoder 4432 for L1 signaling performs signal processing on the OFDM cells corresponding to the FEC blocks belonging to L1 signaling, extracts L1 signaling bits, and transfers to the controller 4433. In this case, the signal processing may include extracting log-likelihood ratio (LLR) values for decoding low-density parity-check (LDPC) codes in the OFDM cell, and decoding the LDPC codes by using the extracted LLR values.

The controller 4433 extracts an L1 signaling table from the L1 signaling bits and controls the operations of the frame demapper 4431, BICM decoder 4434, and output processor 4435 by using the values of the L1 signaling table. Fig. 28 shows that the BICM decoder 4432 for L1 signaling does not use the control information of the controller 4433 for convenience of explanation. However, if the L1 signaling includes a layer structure similar to the above-described L1 pre-signaling and L1 post-signaling, the BICM decoder 4432 for the L1 signaling may be composed of more than one BICM decoding block, and the operations of the BICM decoding blocks and the frame demapper 4431 may be controlled based on the upper layer L1 signaling information, as clearly understood in the above description.

The BICM decoder 4434 performs signal processing on the OFDM cells constituting the FEC block belonging to the selected PLP, extracts a baseband packet, and transfers the baseband packet to the output processor 4435. The signal processing may include extracting LLR values for encoding and decoding the LDPC code in the OFDM cell and decoding the LDPC code by using the extracted LLR values. Both operations may be performed based on control information transmitted from the controller 4433.

The output processor 4435 performs signal processing on the baseband packet, extracts a user packet, and transmits the extracted user packet to the service player. In this case, signal processing may be performed on the control information transmitted from the controller 4433.

Meanwhile, according to an exemplary embodiment, the output processor 1235 may include an ALP packet processor (not shown) extracting an ALP packet from the baseband packet.

Fig. 29 is a flowchart for briefly explaining an operation of the reception apparatus from a time point when the user selects a service to a play time point of the selected service.

It is assumed that service information on all services that can be selected in the initial scanning procedure of S4600 is obtained before the service selection procedure of S4610. The service information may include information on an RF channel and a PLP transmitting data required for playing a specific service in the current broadcasting system. An example of the service information may be program specific information/service information (PSI/SI) of MPEG-2TS, which can be generally obtained through L2 signaling and upper layer signaling.

When the user selects a service in S4610, the receiving apparatus modifies the frequency of transmitting the selected service in S4620 and performs extraction of the RF signal in S4630. The service information may be used when performing S4620 to modify the frequency of transmitting the selected service.

When extracting the RF signal, the receiver performs S4640 to extract L1 signaling from the extracted RF signal. The receiving apparatus selects a PLP to transmit the selected service by using the extracted L1 signaling S4650, and extracts a baseband packet from the selected PLP S4660. The PLP that transmits the selected service is selected at S4650, and the service information may be used.

Further, S4660 extracting the baseband packet may include selecting OFDM cells belonging to the PLP by demapping the transmission frame, extracting LLR values for encoding/decoding the LDPC, and decoding the LDPC code by using the extracted LLR values.

The receiving apparatus extracts an ALP packet from the extracted baseband packet by performing S4670 using header information on the extracted baseband packet, and extracts a user packet from the extracted ALP packet by performing S4680 using header information on the extracted baseband packet. The extracted user package is used in S4690, which plays the selected service. Extracting the ALP packet at S4670 and extracting the user packet at S4680 may use the L1 signaling information acquired at S4640 where the L1 signaling is extracted. In this case, the process of extracting the user packet from the ALP packet (restoring the zero TS packet and inserting the TS sync byte) is the same as described above. According to the above exemplary embodiments, various types of data can be mapped to a transmittable physical layer, and data processing efficiency can be improved.

Fig. 30 is a flowchart illustrating a control method of a transmitting apparatus according to an exemplary embodiment.

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

In addition, the generated packet is subjected to signal processing (S3520).

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

Here, the basic field of the configuration header includes a first field set to a first value indicating that the basic field is a first length or a second value indicating that the basic field is a second length, and when the first field is set to the second value, the basic field may include a second field indicating a LSB of a pointer value and a third field indicating a MSB of the pointer value, the pointer value indicating the first value among respective start points of the input packet included in the payload.

Further, when the first field, the second field, and the third field are included in a basic field of the configuration header, the basic field may include a fourth field indicating an extension mode of the header.

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

Further, the fourth field may be set to one of a third value indicating that the optional field and the extension field do not exist, a fourth value indicating that the optional field exists and that the length of the optional field is 1 byte, a fifth value indicating that the optional field exists and that the length of the optional field is 2 bytes, and a sixth value indicating that the optional field exists and that the length of the optional field is 2 bytes and that the extension field has a structure including a plurality of extension payloads.

Further, when the fourth field is set to a fourth value or a fifth value, the optional fields further include a fifth field indicating a type of an extension payload included in the extension field and a sixth field indicating a length of the extension field, and when the fifth field is set to a predetermined value, the extension field may be completely filled with padding.

Further, when the fourth field is set to the fifth value, the optional fields may include a field indicating a type of an extension payload included in the extension field, a field indicating an LSB portion of the extension field length, and a field indicating an MSB portion of the extension field length.

Further, when the fourth field is set to the sixth value, the optional fields may include a field indicating the number of the plurality of extension payloads included in the extension field, a field indicating the LSB portion of the extension field length, and a field indicating the MSB portion of the extension field length.

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

Further, when the fourth field is set to one of the fourth value and the fifth value and the length of the extension payload included in the extension field is less than the length of the extension field, the extension field may include the extension payload and the remaining portion may include padding.

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

Meanwhile, in a control method of a transmitting apparatus according to another exemplary embodiment, a packet including a header including a basic header in which information on a start point of a data packet in a payload and information on whether an additional field exists is included, and the payload is generated.

Here, the information on the start point of the packet may include information on whether or not the MSB part exists depending on a distance between the start point of the payload and the start point of the packet.

Further, the information about the start point of the packet may include one of a first value indicating that the MSB portion is not present and a second value indicating that the MSB portion is present.

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

Further, the information on whether the additional field exists may include one of a first value indicating that the optional field and the extension field do not exist, a second value indicating that the optional field exists and the extension field does not exist and the length of the optional field is 1 byte, a third value indicating that the optional field exists and the extension field does not exist and the length of the optional field is 2 bytes, and a fourth value indicating that the optional field and the extension field exist and the length of the optional field and the extension field exceeds 2 bytes.

Further, when the information on whether there is an additional field is set to a fourth value, the optional field may include information indicating the length of the extension field.

Further, the information indicating the length of the extension field may include at least one of the LSB portion and the MSB portion according to the length of the extension field.

In addition, the generated frame is signal-processed.

Thereafter, the signal-processed frame is transmitted.

Meanwhile, fig. 31 is a flowchart for describing a control method of a receiving apparatus according to an exemplary embodiment.

In the control method of the receiving apparatus shown in fig. 31, a stream including packets including a header and a payload is received (S3610).

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

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

Here, the basic field configuring the header includes a first field set to a first value indicating that the basic field is a first length or a second value indicating that the basic field is a second length, and when the first field is set to the second value, the basic field may include a second field indicating a LSB of a pointer value and a third field indicating a MSB of the pointer value, the pointer value indicating the first value among respective start points of the input packet included in the payload.

Meanwhile, in a control method of a reception apparatus according to another exemplary embodiment, a stream including packets in which a header and a payload are contained is received.

Further, a header is extracted from the packet, and information indicating a start point of the packet in the payload and information on whether there is an additional field is extracted from the extracted header.

Further, the data packet included in the payload is signal-processed based on the information on the start point of the extracted data packet and the information on whether the additional field exists.

Here, the information on the start point of the packet may include information on whether there is an MSB part depending on a distance between the start point of the payload and the start point of the packet.

Further, the information on whether the additional field exists may include information on whether at least one of the optional field and the extension field exists and information on lengths of the optional field and the extension field.

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

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

Meanwhile, a non-transitory computer readable medium storing a program that sequentially executes the signal processing method according to the above-described exemplary embodiment may be provided.

As an example, a non-transitory computer-readable medium storing a program that generates a packet including a header and a payload based on at least one input packet, performs signal processing on the generated packet, and transmits the signal-processed packet may be provided.

Further, as an example, a non-transitory computer-readable medium storing a program that performs the steps of: receiving a stream including packets including a header and a payload, extracting the header from the packets and information included in the header, and signal-processing an input packet included in the payload based on the extracted information.

A non-transitory computer-readable medium refers to a medium that semi-permanently stores data and is readable by a corresponding device, and not a medium that stores data for a short time such as a register, a cache, and a memory. In detail, various above-described applications or programs may be stored and provided in a non-transitory computer readable medium such as, but not limited to, a Compact Disc (CD), a Digital Versatile Disc (DVD), a hard disk, a blu-ray disc, a Universal Serial Bus (USB), a memory card, and a Read Only Memory (ROM).

At least one of the components, elements, modules or units represented by blocks shown in the figures, such as fig. 6, 7A, 8, 26A, 26B, 27 and 28, may be implemented as various numbers of hardware, software and/or firmware structures performing the various functions described above according to example embodiments. For example, at least one of these components, elements or units may use direct circuit structures, such as memories, processes, logic, look-up tables, etc., which may perform various functions under the control of one or more microprocessors or other control devices. Furthermore, at least one of these components, elements or units may be embodied by a module, program, or portion of code that includes one or more executable instructions for performing 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), a microprocessor, or the like, which performs the respective functions. Two or more of these components, elements or units may be combined into a single component, element or unit that performs all of the operations or functions of the combined two or more components, elements or units. Further, at least a part of the function of at least one of these components, elements or units may be performed by another one of these components, elements or units. Further, although a bus is not shown in the above block diagrams, communication between components, elements, or units may be performed through the bus. The functional aspects of the exemplary embodiments described above may be implemented in algorithms executed on one or more processors. Further, the components, elements or units represented by the blocks or process steps may employ any number of related techniques for electronic configuration, signal processing and/or control, data processing, and the like.

Meanwhile, the detailed exemplary embodiments have been described so far, but various modifications may be made without departing from the scope of the inventive concept. Accordingly, the inventive concept should not be limited to the exemplary embodiments, but should be defined by the following claims and their equivalents.

Industrial applicability

-

Sequence listing text

-

Claims

1. A transmitting device, the transmitting device comprising:

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 the generated packet; and

a transmitter that transmits the processed packet,

wherein the header includes a base field including a first field, wherein the first field is set to a first value indicating that a length of the base field is a first length or a second value indicating that the length of the base field is a second length, and wherein the base field includes a second field and a third field when the first field is set to the second value, wherein the second field indicates a Least Significant Bit (LSB) of a pointer value, wherein the third field indicates a Most Significant Bit (MSB) of the pointer value, wherein the pointer value indicates an offset from a start point of the payload to a first start point among start points of input packets included in the payload.

2. The transmission apparatus of claim 1, wherein the basic field comprises a fourth field indicating an extension mode of the header, and the fourth field comprises at least one of information on whether an optional field exists, a length of the optional field, and a structure of an extension field.

3. The transmission apparatus according to claim 2, wherein the fourth field is set to one of a third value indicating that the optional field and the extension field are not present, a fourth value indicating that the optional field is present and the optional field is 1 byte in length, a fifth value indicating that the optional field is present and the optional field is 2 bytes in length, and a sixth value indicating that the optional field is present and the optional field is 2 bytes in length and the extension field has a structure including a plurality of extension payloads.

4. The transmission apparatus according to claim 3, wherein the optional fields further include a fifth field indicating a type of an extension payload included in the extension field and a sixth field indicating a length of the extension field when the fourth field is set to the fourth value or the fifth value, and the extension field is filled completely when the fifth field is set to a predetermined value.

5. The transmission apparatus according to claim 3, wherein when the fourth field is set to the fifth value, the optional fields include a field indicating a type of an extension payload included in the extension field, a field indicating a LSB part of a length of the extension field, and a field indicating a MSB part of the length of the extension field.

6. The transmission apparatus according to claim 3, wherein when the fourth field is set to the sixth value, the optional fields include a field indicating a number of a plurality of extension payloads included in the extension field, a field indicating an LSB part of the extension field length, and a field indicating an MSB part of the extension field length.

7. The transmitting device of claim 6, wherein 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.

8. The transmission apparatus according to claim 7, wherein the extension field includes the extension payload and padding when the fourth field is set to one of a fourth value and a fifth value and a length of an extension payload included in the extension field is smaller than a length of the extension field.

9. The transmitting device of claim 3, wherein the extension field comprises a plurality of extension payloads and padding when the fourth field is set to a sixth value.

10. A receiving device, comprising:

a receiver configured to receive a stream comprising packets including a header and a payload; and

at least one processor configured to extract the header from the packet and extract information included in the header, and process a plurality of input packets included in the payload based on the extracted information,

wherein the header includes a basic field including a first field, wherein the first field is set to a first value indicating that a length of the basic field is a first length or a second value indicating that the length of the basic field is a second length, and

wherein the basic field includes a second field and a third field when the first field is set to the second value, wherein the second field represents Least Significant Bits (LSBs) of a pointer value, wherein the third field represents Most Significant Bits (MSBs) of the pointer value, wherein the pointer value indicates an offset from a start point of the payload to a first start point among start points of input packets included in the payload.