KR101632212B1 - Receiving system and method of processing broadcast signal in the receiving system - Google Patents

Abstract

A receiving system and a broadcast signal processing method for receiving and processing a broadcast signal are disclosed. The receiving system includes a signal receiving unit, a signaling decoding unit, an error correction unit, a first packet converting unit, a second packet converting unit, and an audio / video (A / V) decoding unit. The signal receiving unit receives a broadcast signal including mobile service data constituting a data group. The signaling decoding unit extracts Fast Information Channel (FIC) data and transmission parameter channel (TPC) data from the data group and decodes it. The error correction unit forms an RS frame from the mobile service data of the plurality of data groups, and performs error correction decoding on the RS frame basis. The first packet conversion unit packetizes the error-correction-decoded RS frame into a first packet. The second packet conversion unit packetizes the decoded FIC data into a second packet. The A / V decoder extracts and decodes the mobile service data corresponding to at least one of audio and video streams from the first packet based on the FIC data included in the second packet.

RS frame, fast information channel, packet, decoding

Description

[0001] The present invention relates to a receiving system and a broadcasting signal processing method,

The present invention relates to a digital broadcasting system for transmitting and receiving broadcast signals, and more particularly, to a receiving system for receiving and processing broadcast signals and a method for processing broadcast signals.

VSB (Vestigial Sideband) transmission system adopted as a digital broadcasting standard in North America and Korea in digital broadcasting is a single carrier system, so reception performance of a receiving system may be deteriorated in a poor channel environment. Particularly, in the case of a portable or mobile broadcast receiver, robustness against channel change and noise is further required, so that when the mobile service data is transmitted using the VSB transmission method, the reception performance is further degraded.

Accordingly, it is an object of the present invention to provide a digital broadcasting transmission / reception system and a broadcasting signal processing method which are resistant to channel changes and noise.

Another object of the present invention is to provide a receiving system and a broadcasting signal processing method for packetizing mobile service data and signaling data included in a received broadcast signal in the MPEG-2 transport packet format to perform audio / video decoding have.

According to an aspect of the present invention, there is provided a receiving system including a signal receiving unit, a signaling decoding unit, an error correction unit, a first packet converting unit, a second packet converting unit, and an audio / And a decoding unit.

The signal receiving unit receives a broadcast signal including mobile service data constituting a data group. One transmission frame is composed of a plurality of subframes, one subframe is composed of a plurality of slots, and the data group is allocated to at least one slot. The signaling decoding unit extracts Fast Information Channel (FIC) data and transmission parameter channel (TPC) data from the data group and decodes it. The error correction unit forms an RS frame from the mobile service data of the plurality of data groups, and performs error correction decoding on the RS frame basis. The first packet conversion unit packetizes the error-correction-decoded RS frame into a first packet. The second packet conversion unit packetizes the decoded FIC data into a second packet. The A / V decoder extracts and decodes the mobile service data corresponding to at least one of audio and video streams from the first packet based on the FIC data included in the second packet.

The RS frame is composed of 187 M / H service data packets, and each M / H service data packet is composed of 2 bytes of M / H header and N-2 bytes of M / H payload, The H payload contains mobile service data.

The first packet conversion unit packetizes data of the M / H service data packet into a first packet in units of M / H service data packets, and the first packet includes a header area of 4 bytes and a payload area of 184 bytes And the data of the M / H service data packet is inserted into the payload area.

Wherein the header field includes a synchronous field for indicating synchronous data, a type indicator field for indicating whether the first packet is a packet for an RS frame, a first indicator indicating whether the first packet is packetized in the M / H service data packet of the RS frame, H service data packet number field indicating whether the first packet is a packet received from the M / H service data packet, a packet order field indicating a number of the first packet in the M / H service data packet, A packet count field indicating the total number of the first packets, and a stuffing indicator field indicating whether there is stuffing data in the first packet.

Wherein the second packet conversion unit packetizes the FIC data into a second packet on a subframe basis, the second packet comprises a header area of 4 bytes and a payload area of 184 bytes, and the FIC Data is inserted.

Wherein the header area includes a synchronization field for displaying synchronization data, a type indicator field for indicating whether the second packet is a packet for the FIC, and a second indicator for indicating whether the second packet is a packetized packet in a subframe of the transmission frame A packet order field for indicating the number of packets in the corresponding subframe, a packet number field for indicating the total number of packets to be packetized in the corresponding subframe, And a stuffing indicator field indicating whether there is stuffing data in the packet.

A method of processing a broadcast signal in a receiving system according to an embodiment of the present invention is characterized in that one transmission frame is composed of a plurality of subframes, one subframe is composed of a plurality of slots, a data group is assigned to at least one slot Receiving a broadcast signal including mobile service data constituting the data group, extracting and decoding Fast Information Channel (FIC) data and transmission parameter channel (TPC) data from the data group, Comprising the steps of: constructing an RS frame from mobile service data of a group and performing error correction decoding in units of the RS frame; packetizing the error-correction decoded RS frame into a first packet; Packetized into a first packet based on the FIC data included in the second packet, Extracting mobile service data corresponding to at least one of an audio and a video stream and performing audio / video decoding.

Other objects, features and advantages of the present invention will become apparent from the detailed description of embodiments with reference to the accompanying drawings.

The reception system and the broadcast signal processing method according to the present invention packetize the error-correction-decoded RS frame into a packet of the MPEG-2 transport packet (TP) format and output it to an audio / video decoder, ) Data is also packetized into packets of the MPEG-2 TP format and outputted to an audio / video decoder, thereby enabling decoding of mobile service data in an audio / video decoder supporting MPEG-2 TP.

The present invention is advantageous in that it is error-resistant when transmitting mobile service data through a channel and is also compatible with existing receivers. The present invention is advantageous in that mobile service data can be received without error even in a channel with ghost and severe noise. The present invention can improve the reception performance of a receiving system in an environment where a channel change is severe by inserting and transmitting known data at a specific location in a data area. Particularly, the present invention is more effective when applied to portable and mobile receivers where channel changes are severe and robustness against noise is required.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings. The structure and operation of the present invention shown in the drawings and described by the drawings are described as at least one embodiment, and the technical ideas and the core structure and operation of the present invention are not limited thereby.

Definitions of terms used in the present invention

The terms used in the present invention are selected from general terms that are widely used in the present invention while considering the functions of the present invention. However, the terms may vary depending on the intention or custom of the artisan or the emergence of new technology. Also, in certain cases, there may be a term selected arbitrarily by the applicant, in which case the meaning thereof will be described in detail in the description of the corresponding invention. Therefore, it is to be understood that the term used in the present invention should be defined based on the meaning of the term rather than the name of the term, and on the contents of the present invention throughout.

Among the terms used in the present invention, main service data may include audio / video (A / V) data as data that can be received by a fixed receiving system. That is, the main service data may include HD (High Definition) or SD (Standard Definition) A / V data, and various data for data broadcasting may be included. The known data is previously known data by the promise of the transmitting / receiving side.

Among the terms used in the present invention, M / H (or MH) is the first letter of each of a mobile and a handheld, and is a concept opposite to a fixed type. The M / H service data includes at least one of mobile service data and handheld service data. For convenience of explanation, the M / H service data is also referred to as mobile service data. At this time, the mobile service data may include not only M / H service data but also service data indicating movement or carrying, so that the mobile service data will not be limited to the M / H service data.

The mobile service data defined above may be data having information such as a program executable file, stock information, etc., or A / V data. In particular, the mobile service data may be service data for a portable or mobile terminal (or broadcast receiver), and may be A / V data having a smaller resolution and smaller data rate than the main service data. For example, if the A / V codec used for the existing main service is an MPEG-2 codec, the A / V codec for mobile service may be MPEG-4 Advanced Video Coding (AVC), and Scalable Video Coding (SVC). Also, any kind of data can be transmitted with the mobile service data. For example, TPEG (Transport Protocol Expert Group) data for broadcasting traffic information in real time can be transmitted as mobile service data.

The data service using the mobile service data may include a weather service, a traffic service, a securities service, a viewer participation quiz program, a real-time opinion survey, an interactive education broadcast, a game service, a plot of a drama, Providing information on programs by service, media, hourly, or topic that enables information service for information, information on past competitions of sports, profiles and grades of athletes, and product information and orders Or the like, and the present invention is not limited thereto.

The transmission system of the present invention allows backward compatible, main service data and mobile service data to be multiplexed on the same physical channel without any influence on reception of main service data in an existing receiving system.

The transmission system of the present invention performs additional encoding on the mobile service data, and inserts known data, that is, known data, into both the transmitting and receiving sides.

By using the transmission system according to the present invention, it is possible to receive and receive mobile service data in a receiving system, and to receive stable mobile service data even with various distortions and noises occurring in a channel.

M / H frame structure

The mobile service data included in the broadcast signal of the present invention is multiplexed with main service data in units of M / H frames, modulated into a VSB scheme, and transmitted to a reception system.

At this time, one M / H frame is composed of K1 subframes, and one subframe may be composed of K2 slots. Also, one slot may be composed of K3 data packets. In the present invention, K1 is set to 5, K2 is set to 16, and K3 is set to 156, as an embodiment. The values of K1, K2, and K3 suggested in the present invention are preferred embodiments or merely examples, and the scope of the present invention is not limited to the above values.

FIG. 1 illustrates an M / H frame structure for transmitting and receiving mobile service data according to an embodiment of the present invention. Referring to FIG. FIG. 1 shows an example in which one M / H frame is composed of 5 subframes, and one subframe is composed of 16 slots. In this case, one M / H frame includes 5 subframes and 80 slots.

One slot consists of 156 data packets (i.e., transport stream packets) at the packet level and 156 data segments at the symbol level. Or a half of the VSB field. That is, since one data packet of 207 bytes has the same amount of data as one data segment, a data packet before data interleaving can be used as a concept of a data segment.

At this time, two VSB fields are gathered to form one VSB frame.

FIG. 2 shows an example of a VSB frame structure. One VSB frame is composed of two VSB fields (i.e., an odd field and an even field). Each VSB field is composed of one field sync segment and 312 data segments.

The slot is a basic time period for multiplexing mobile service data and main service data. One slot may include mobile service data, or may consist of only main service data.

If a data group containing mobile service data is transmitted during one slot, the first 118 data packets in the slot correspond to one data group and the remaining 38 packets become the main service data packet. As another example, if there is no data group in one slot, the slot is made up of 156 main service data packets.

On the other hand, when the slots are assigned to VSB frames, they have offsets at their positions.

FIG. 3 shows a mapping example of a first 4-slot position of a subframe in a space region with respect to one VSB frame. FIG. 4 shows a mapping example of a first 4-slot position of a subframe in a time domain for one VSB frame.

3 and 4, the 38th data packet (# 37) of the first slot (Slot # 0) is mapped to the first data packet of the od VSB field and the 38th data packet The packet # 37 is mapped to the 157th data packet of the odd VSB field. The 38th data packet (# 37) of the third slot (Slot # 2) is mapped to the first data packet of the even VSB field and the 38th data packet (# 37) of the fourth slot And is mapped to the 157th data packet of the even VSB field. Likewise, the remaining 12 slots in the subframe are mapped in the same way to the following VSB frame.

On the other hand, one data group can be divided into one or more layered areas, and the type of mobile service data inserted in each area can be changed according to the characteristics of each layered area. Each area in the data group can be classified based on the reception performance in the data group as an example.

In the present invention, one data group is divided into A, B, C, and D regions in a data structure after data interleaving.

FIG. 5 is a diagram in which data after data interleaving are sorted and listed. That is, the data structure as shown in FIG. 5 is transmitted to the receiving system. In other words, one data packet is data interleaved and distributed over several data segments to the receiving system. 5 shows an example in which one data group is distributed over 170 data segments. In this case, since one data packet of 207 bytes has the same data amount as one data segment, a packet before data interleaving is used as a concept of a segment.

FIG. 5 shows an example of dividing a data group into 10 M / H blocks (MH blocks B1 to B10) in the data structure after data interleaving. And each M / H block has a length of 16 segments. In FIG. 5, only the RS parity data is allocated to a part of the 5 segments preceding the M / H block B1 and the 5 segments after the M / H block B10, and the data is excluded from the A area to the D area of the data group.

That is, assuming that one data group includes at least the A, B, C, and D regions, each M / H block is divided into any one of the A region to the D region according to the characteristics of each M / . In this case, each M / H block may be included in any one of the A region to the D region according to the degree of interference of the main service data.

The reason why the data group is divided into a plurality of regions is to differentiate each use. That is, a region where there is no interference of the main service data or a region where there is no interference can show robust reception performance than the region where no interference occurs. In addition, when a system for inserting known data known by the promise of a transmitting / receiving end into a data group and transmitting the data is applied, when it is desired to periodically insert consecutively long base data into mobile service data, It is possible to periodically insert a known length of known data into an area where there is no interference of data (that is, an area where main service data is not mixed). However, it is difficult to periodically insert known data due to interference of main service data in an area where interference of main service data occurs, and it is also difficult to continuously insert long known data.

The M / H block B4 to the M / H block B7 in the data group of FIG. 5 show an example where long known data strings are inserted before and after each M / H block as an area free of interference of main service data. In the present invention, the A region (= B4 + B5 + B6 + B7) including the M / H block B4 to the M / H block B7 will be described. As described above, in the case of the A region having the known data sequence for each M / H block back and forth, the receiving system can perform equalization using the channel information obtained from the known data. Thus, the most robust equalization Performance can be obtained.

The M / H block B3 and the M / H block B8 in the data group of FIG. 5 are areas where interference of main service data is small, and an example in which a long known data row is inserted into only one of both M / H blocks is shown. That is, due to the interference of the main service data, the M / H block B3 inserts a long base data string only after the corresponding M / H block, and the M / H block B8 inserts a long base data string only in front of the corresponding M / H block . In the present invention, the B region (= B3 + B8) including the M / H block B3 and the M / H block B8 will be described. As described above, in the case of the B region having the known data sequence in either one of the M / H blocks, the receiving system can perform equalization using the channel information obtained from the known data, The equalization performance can be obtained.

The M / H block B2 and the M / H block B9 in the data group of FIG. 5 have more interference of the main service data than the B area, and can not insert a long known data row back and forth in both M / H blocks. In the present invention, a C region (= B2 + B9) including the M / H block B2 and the M / H block B9 will be described.

The M / H block B1 and the M / H block B10 in the data group of FIG. 5 have more interference of the main service data than the C area, and similarly, it is impossible to insert a long known data sequence back and forth in both M / H blocks. In the present invention, the D region (= B1 + B10) including the M / H block B1 and the M / H block B10 will be described. Since the C / D region is far away from the known data sequence, the reception performance may be poor if the channel changes rapidly.

That is, the field sync is located between the M / H block B2 and the M / H block B3 on the basis of FIG. 5, which means that the slot has an offset of 37 data packets for the corresponding VSB field.

The size of the data group, the number of layered areas in the data group and the size of each area, the number of M / H blocks included in each area, the size of each M / H block, The present invention is not limited to the above-mentioned examples.

6 shows an example of a data group allocation procedure to be assigned to one subframe among five subframes constituting an M / H frame. For example, the method of allocating data groups may be applied to all M / H frames or may be different for each M / H frame. The same applies to all subframes within one M / H frame, or may be applied to each subframe differently. Assuming that the assignment of the data group is applied to all the subframes in the M / H frame at this time, the number of data groups allocated to one M / H frame is a multiple of 5.

And consecutively allocating a plurality of data groups as far apart as possible in a subframe. This makes it possible to strongly respond to burst errors that may occur in one subframe.

For example, assuming that three groups are allocated to one subframe, the first slot (Slot # 0), the fifth slot (Slot # 4) and the ninth slot (Slot # 8) do. FIG. 6 shows an example in which 16 data groups are allocated in one subframe by applying the allocation rule. In this example, 0, 8, 4, 12, 1, 9, 5, 14, 3, 11, 7, and 15, respectively.

Equation (1) is a mathematical expression of rules for assigning data groups to one subframe as described above.

j = (4i + O) mod 16

Where O = 0 if i < 4,

        O = 2 else if i <8,

        O = 1 else if i <12,

        O = 3 else.

Here, j is a slot number in one subframe and may have a value between 0 and 15. The i is a group number and may have a value between 0 and 15.

In the present invention, a collection of data groups included in one M / H frame is referred to as a parade. The parade transmits data of one or more specific RS frames according to the RS frame mode.

The mobile service data in one RS frame may be all allocated to the A / B / C / D area in the data group or may be allocated to at least one area of the A / B / C / D area. In one embodiment, mobile service data in one RS frame is all allocated to an A / B / C / D area or allocated to only one of an A / B area and a C / D area. That is, in the latter case, the RS frame allocated to the A / B area in the data group is different from the RS frame allocated to the C / D area. For convenience of explanation, the RS frame allocated to the A / B area in the data group is referred to as a primary RS frame, and the RS frame allocated to the C / D area is referred to as a secondary RS frame frame. The primary RS frame and the secondary RS frame constitute one parade. That is, if mobile service data in one RS frame is all allocated in the A / B / C / D area in the data group, one parade transmits one RS frame. On the other hand, if the mobile service data in one RS frame is allocated to the A / B area in the data group and the mobile service data in the other RS frame is allocated to the C / D area in the corresponding data group, RS frames.

That is, the RS frame mode indicates whether one parade transmits one RS frame or two RS frames.

Table 1 below shows an example of the RS frame mode.

RS Frame mode Description 00 There is only a primary RS Frame
for all Group Regions 01 There are two separate RS Frames
- Primary RS Frame for Group A and B
- Secondary RS Frame for Group Region C and D 10 Reserved 11 Reserved

In Table 1, 2 bits are allocated to indicate the RS frame mode. Referring to Table 1, if the RS frame mode value is 00, it indicates that one parade transmits one RS frame. If the RS frame mode value is 01, one parade is transmitted to two RS frames, that is, primary RS Frame (Primary RS frame) and a secondary RS frame (Secondary RS frame). That is, when the RS frame mode value is 01, the data of the primary RS frame for region A / B is allocated to the A / B area of the data group and transmitted, and the secondary RS frame for region C / D) is assigned to the C / D area of the corresponding data group and is transmitted.

As in the case of the allocation of the data group, the parades are allocated as far as possible in the subframe as one embodiment. This makes it possible to strongly respond to burst errors that may occur in one subframe.

And, the allocation method of parades can be applied differently for each M / H frame based on M / H frame, and can be applied to all M / H frames equally. The same applies to all subframes within one M / H frame, or may be applied to each subframe differently. The present invention can be changed for each M / H frame, and is applied to all subframes in one M / H frame. That is, the M / H frame structure can be changed in units of M / H frames, which enables frequent and flexible adjustment of the ensemble data rate.

7 is a diagram showing an example of assigning a single parade to one M / H frame. That is, FIG. 7 shows an embodiment in which a single parade with three data groups included in one subframe is allocated to one M / H frame.

Referring to FIG. 7, when three data groups are sequentially allocated in a 4-slot period in one subframe and this process is performed on 5 subframes in the corresponding M / H frame, 15 Data groups are assigned. Here, the 15 data groups are data groups included in one parade. Therefore, one subframe is composed of four VSB frames, but one subframe includes three data groups. Therefore, a data group of the parade is allocated to one VSB frame of four VSB frames in one subframe Do not.

For example, assuming that one parade transmits one RS frame, RS encoding is performed in the RS frame encoder of the subsequent RS frame, and 24 bytes of parity data is added to the corresponding RS frame for transmission. The specific gravity occupied by the parity data among the lengths of the entire RS codeword is about 11.37% (= 24 / (187 + 24) x 100). Meanwhile, when three data groups are included in one subframe and 15 data groups form one RS frame when data groups within one parade are allocated as shown in FIG. 7, one burst frame Even if all the groups are in error, the percentage of them is 6.67% (= 1/15 x 100). Therefore, in the receiving system, all errors can be corrected by erasure RS decoding. That is, if erasure RS decoding is performed, channel errors corresponding to the number of RS parities can be corrected. Therefore, it is possible to correct all byte errors in RS codewords equal to or less than the number of RS parities. In this way, the receiving system can correct errors of at least one data group in one parade. The minimum burst noise length that can be corrected by one RS frame is more than 1 VSB frame. (Thus, the minimum burst noise length is correctable by a VSB frame.

Meanwhile, when data groups for one parade are allocated as shown in FIG. 7, main service data may be allocated between data groups and data groups of other parades may be allocated. That is, data groups for a plurality of parades may be allocated to one M / H frame.

Basically, the assignment of data groups to multiple parades is not different from that of a single parade. In other words, data groups in other parades allocated to one M / H frame are also allocated in 4-slot periods.

At this time, the data group of another parade may be allocated in a circular manner from a slot to which the data group of the previous parade is not allocated.

For example, assuming that the allocation of data groups for one parade is made as shown in FIG. 7, the data group for the next parade is allocated from the 12th slot in one subframe. This is an example, and for another example, the data group of the next parade may be sequentially allocated in another slot in one subframe, for example, from the third slot to the fourth slot period.

8 shows an example in which three parades (Parade # 0, Parade # 1, Parade # 2) are transmitted to one M / H frame. Particularly, one of five subframes Frame parade transmission example.

If the first parade includes three data groups per subframe, the positions of the groups in the subframe can be obtained by substituting 0 to 2 for the i value of Equation (1). That is, the data groups of the first parade are sequentially allocated to the first, fifth, and ninth slots (Slot # 0, Slot # 4, Slot # 8) in the subframe.

Assuming that the second parade includes two data groups per subframe, the positions of the groups in the subframe can be obtained by substituting 3 to 4 in the i value of Equation (1). That is, the data groups of the second parade are sequentially allocated to the second and twelfth slots (Slot # 1, Slot # 11) in the subframe.

Also, if the third parade includes two groups per subframe, the positions of the groups in the subframe can be obtained by substituting 5 to 6 for the i value of Equation (1). That is, the data groups of the third parade are sequentially allocated to the seventh and eleventh slots (Slot # 6, Slot # 10) in the subframe.

In this manner, data groups for a plurality of parades can be allocated to one M / H frame, and the allocation of data groups in one subframe is performed in serial from left to right with a group space of 4 slots.

Therefore, the number of groups of one parade per sub-frame (NOG) that can be assigned to one subframe can be any one of integers from 1 to 8. Since one M / H frame includes five subframes, the number of data groups of one parade that can be allocated to one M / H frame is any one of multiples of 5 from 5 to 40 .

FIG. 9 shows an example in which the allocation process of the three parades in FIG. 8 is extended to five subframes in one M / H frame.

FIG. 10 is a diagram illustrating a data transmission structure according to an embodiment of the present invention, in which signaling data is included in a data group and transmitted.

As described above, the M / H frame is divided into five subframes, and data groups corresponding to several parades are present in each subframe. Then, the data groups corresponding to each parade are bundled in M / H frame units to constitute one parade.

Also in Fig. 10, there are three parades (Parade # 0, Parade # 1, Parade # 2) in one M / H frame. At this time, a certain portion (e.g. 37 bytes / data group) of each data group is used to transmit FIC (Fast Information Channel) information encoded separately from RS encoding for mobile service data. The FIC area allocated to each data group constitutes one FIC segment.

In the present embodiment, M / H ensemble concept is introduced to define a set of services. One M / H ensemble has the same QoS and is coded with the same FEC code. Also, one M / H ensemble has the same unique identifier (i.e., ensemble id) and corresponds to successive RS frames.

As shown in FIG. 10, the FIC segment corresponding to each data group describes service information of the M / H ensemble to which the corresponding data group belongs.

FIC ( Fast Information Channel )

The transmitting / receiving system of the present invention operates two data channels according to an embodiment of the present invention. One of the data channels is an RS frame data channel for content transmission, and the other data channel is a Fast Information Channel (FIC) for service acquisition. In the present invention, mapping information between an ensemble and a mobile service is signaled using an FIC chunk, and the FIC chunk is divided into FIC segments and transmitted through an FIC, thereby enabling quick service acquisition in a receiving system.

The FIC chunk consists of a 5-byte FIC chunk header and a variable length FIC chunk payload.

11 shows an embodiment of the syntax structure of the FIC chunk header according to the present invention.

The FIC chunk header may include an FIC_major_protocol_version field, an FIC_minor_protocol_version field, an FIC_chunk_header_extension_length field, an ensemble_loop_header_extension_length field, an M / H_service_loop_extension_length field, a current_next_indicator field, a transport_stream_id field, and a num_ensembles field.

The FIC_major_protocol_version field allocates 2 bits in one embodiment and indicates a major protocol version of the corresponding FIC chunk syntax. The change of the major protocol version indicates a change in level that is not backward compatible. If this field value is updated, then the FIC chunk is not processed by a legacy receiving system capable of processing the previous major protocol version of the FIC chunk protocol (A two-bit unsigned integer field that represents the major version level of The FIC-Chunk protocol shall be attempted to avoid attempting to use the FIC-Chunk protocol. The FIC-Chunk protocol shall be a non-backward-compatible level of change. process the FIC Chunk).

The FIC_minor_protocol_version field allocates 3 bits in one embodiment and indicates a minor protocol version of the corresponding FIC chunk syntax. The change of the minor protocol version indicates a backward compatible level change. If this field is updated, then a legacy receiving system capable of handling the same major protocol version of the FIC chunk protocol can process a portion of the FIC chunk (A three-bit unsigned integer field that represents the minor The FIC-Chunk is the same as the FIC-Chunk, and the FIC-Chunk is the same as the FIC-Chunk. The FIC Chunk protocol may be a part of the FIC Chunk).

The FIC_Chunk_header_extension_length field allocates 3 bits in one embodiment and indicates the length of the FIC chunk header extension byte generated by the minor protocol version update of the corresponding FIC chunk. The extension bytes are appended to the end of the corresponding FIC chunk header (this 3-bit unsigned integer field identifies the length of the FIC-Chunk header extension bytes caused by the minor protocol version of the FIC-Chunk, where the extension bytes are appended at the end of the FIC-Chunk header).

The ensemble_header_extension_length field allocates 3 bits in one embodiment and indicates the length of the ensemble header extension byte generated by the minor protocol version update of the corresponding FIC chunk. The extension bytes are appended to the end of the corresponding ensemble loop header. (This 3-bit unsigned integer field identifies the length of the ensemble header extension caused by the minor protocol version of the FIC-Chunk, appended at the end of the ensemble loop header).

The M / H_service_loop_extension_length field is allocated 3 bits in one embodiment and indicates the length of the mobile service loop extension byte generated by the minor protocol version update of the corresponding FIC chunk. The extension bytes are appended to the end of the corresponding mobile service loop (This 3-bit unsigned integer field identifies the length of the ensemble header extension caused by the minor protocol version of the M / H service loop, where the extension bytes are appended at the end of the M / H service loop).

For example, suppose that there are two ensembles in the FIC chunk (i.e., ensemble 0, ensemble 1), two mobile services through ensemble 0, and one mobile service via ensemble 1. At this time, if the FIC chunk header is extended by one byte while the minor protocol version is changed, the FIC_chunk_header_extension_length field indicates 001. In this case, a 1-byte extension field (FIC_Chunk_header_extension_bytes field) is added to the end of the FIC chunk header. In the existing receiving system, 1-byte extension field added to the end of the FIC chunk header is skipped without being processed.

If the ensemble loop header in the FIC chunk is extended by 2 bytes, the ensemble_loop_header_extension_length field indicates 010. In this case, an extension field (Ensemble_loop_header_extension_bytes field) of 2 bytes is added to each end of the ensemble 0 loop header and the ensemble 1 loop header. In the existing receiving system, 2 bytes of extension added to the end of the ensemble 0 loop header and the ensemble 1 loop header The field is skipped without processing.

Also, if the mobile service loop of the FIC chunk is extended by one byte, the M / H_service_loop_extension_length field indicates 001. In this case, one extension field (M / H_service_loop_extension_bytes field) is added to each of two mobile service loops transmitted through ensemble 0 and one mobile service loop transmitted through ensemble 1. In the existing receiving system, the two mobile service loops transmitted through the ensemble 0 and the one-byte extended field added at the end of one mobile service loop transmitted through the ensemble 1 are skipped without being processed.

When the FIC_minor_protocol version field value is changed, the receiving system that can not accommodate the change of the minor protocol version of the existing receiving system, that is, the FIC chunk, processes the remaining fields except for the extension field, and sets FIC_chunk_header_extension_length, ensemble_loop_header_extension_length, and M / H_service_loop_extension_length fields The corresponding extension fields are skipped without being processed. If the receiving system can accommodate the change of the minor protocol version of the FIC chunk, it will process the corresponding extension field using each length field.

The current_next_indicator field allocates 1 bit in one embodiment, and when the field value is set to '1', it indicates that the FIC chunk is applied to the current M / H frame. If the field value is set to '0', it indicates that the corresponding FIC chunk is applied to the next M / H frame (A one-bit indicator, which when set to '1' The FIC-Chunk transmitted with the current_next_indicator bit is set to '1', and the FIC-Chunk will be used for the next M / H Frame. shall be currently applicable). That is, if the field value is set to '1', the FIC chunk indicates that the signaling data of the current M / H frame is transmitted. If the field value is set to 0, the FIC chunk indicates that the signaling data of the next M / H frame is transmitted. When reconfiguration in which the mapping information between the ensemble and the mobile service in the current M / H frame is different from the mapping information between the ensemble of the next M / H frame and the mobile service, reconfiguration is performed before the reconfiguration occurs, H frame is referred to as a current M / H frame, and an M / H frame in which reconfiguration occurs is referred to as a next M / H frame.

The transport_stream_id field allocates 16 bits in one embodiment and indicates a transport stream ID of a mobile broadcast in which the current FIC chunk is transmitted. This field value is identical to the transport_stream_id field value of the program map table (PAT). (This 16-bit unsigned integer number field serves as a label to identify this M / H Broadcast. the transport_stream_id field in the PAT in the MPEG-2 transport stream of the main ATSC broadcast).

In the num_ensembles field, an 8-bit field is allocated, and an 8-bit unsigned integer field indicates the number of ensembles to be transmitted on the corresponding physical transport channel. .

12 shows an embodiment of the syntax structure of the FIC chunk payload according to the present invention.

The FIC chunk payload includes configuration information of an ensemble and information on a mobile service transmitted through each ensemble, for each ensemble corresponding to the num_ensembles field value in the FIC chunk header of FIG. 11 have.

The FIC chunk payload consists of an ensemble loop and a mobile service loop under the ensemble loop. Through the FIC chunk payload, the receiving system can recognize which ensemble the desired mobile service is transmitted (which is composed of mapping between ensemble_id and M / H_service_id), and receive RS frames belonging to the ensemble.

To this end, the ensemble loop of the FIC chunk payload may include an ensemble_id field, an ensemble_protocol_version field, an SLT_ensemble_indicator field, a GAT_ensemble_indicator field, an MH_service_signaling_channel_version field, and a num_MH_services field repeated by the num_ensembles field value. The mobile service loop may include an MH_service_id field, a multi_ensemble_service field, an MH_service_status field, and an SP_indicator field repeated by a num_MH_services field value.

The ensemble_id field allocates 8 bits in one embodiment and indicates a unique identifier of the ensemble. For example, values of 0x00 to 0x7F may be assigned to the field values. This field binds mobile services and ensembles. The value of the field may be derived from the parade_id of the TPC data. For example, when the ensemble is transmitted through the primary RS frame, the MSB is set to '0', and the remaining 7 bits are used as the parade_id value of the corresponding parade. On the other hand, when the ensemble is transmitted through the secondary RS frame, the most significant bit (MSB) is set to '1', and the remaining seven bits are used as the parade_id value of the parade.

The ensemble_protocol_version field allocates 5 bits in one embodiment and indicates a version of the ensemble structure.

The SLT_ensemble_indicator field allocates 1 bit in one embodiment and indicates whether the SLT is transmitted in the service signaling channel of the ensemble. For example, if the value of the SLT_ensemble_indicator field is 1, it indicates that the SLT is transmitted on the service signaling channel, and if it is 0, it indicates that the SLT is not transmitted.

The GAT_ensemble_indicator field allocates 1 bit in one embodiment and indicates whether the GAT is transmitted in the service signaling channel of the ensemble. For example, if the value of the GAT_ensemble_indicator field is 1, it indicates that the GAT is transmitted on the service signaling channel, and if it is 0, it indicates that the GAT is not transmitted.

The MH_service_signaling_channel_version field allocates 5 bits in one embodiment and indicates the version number of the service signaling channel of the ensemble.

In the num_M / H_services field, 8 bits are allocated, and the number of mobile services transmitted in the ensemble is displayed (An 8-bit unsigned integer field represents the number of mobile ( ie, M / H) carried through this Ensemble).

In one example, if the minor protocol version in the FIC chunk header is changed and an extension field is added to the ensemble loop header, this extension field is added after the num_M / H_services field. In another embodiment, if the num_M / H_services field is included in the mobile service loop, an extension field added to the ensemble loop header is added after the M / H_service_configuration_version field.

The M / H_service_id field of the mobile service loop allocates 16 bits in one embodiment and indicates a unique identifier of the corresponding mobile service. The field value has a unique value in mobile broadcasting.

The multi_ensemble_service field allocates 2 bits in one embodiment and indicates whether the corresponding mobile service is transmitted through one ensemble or a plurality of ensembles. Also, the value of the multi_ensemble_service field indicates whether the mobile service is valid only for the mobile service part transmitted through the ensemble. (A two-bit enumerated field that indicates whether the M / H service is carried across more than one M / H Ensemble. Also, this field identifies whether the M / H Service can be rendered meaningfully with only a portion of the M / H Service carried through this M / H Ensemble).

The M / H_service_status field allocates 2 bits in one embodiment and indicates the status of the corresponding mobile service. For example, an upper bit of the field indicates whether the corresponding mobile service is active, and a lower bit indicates whether the corresponding mobile service is hidden (A 2-bit enumerated field that will identify the status of this M / H Service. The most significant bit is whether this M / H Service is active (when set to 1) or inactive (when set to 0) not (when set to 0).

The SP_indicator field is a 1 bit allocated to the mobile service, and indicates whether the mobile service is protected by a service (A 1-bit field indicates that when set to 1, service protection is applied to at least one of The components needed to provide a meaningful presentation of this M / H Service).

In one example, if the minor protocol version in the FIC chunk header is changed and an extension field is added to the mobile service loop, this extension field is added after the SP_indicator field.

The FIC chunk payload may also include a FIC_chunk_stuffing () field. Stuffing of the FIC_chunk_stuffing () field is necessary to allow the boundary of the FIC chunk to be aligned with the boundary of the last FIC segment of the FIC segments belonging to the FIC chunk (Stuffing may exist in an FIC-Chunk, The FIC-Chunk to be aligned with the boundary of the FIC-Segment among the FIC chunks. The length of the stuffing is determined by how much space is left after the parsing through the entire FIC- Chunk payload preceding the stuffing.).

At this time, the transmission system (not shown) according to the present invention divides the FIC chunk into a plurality of FIC segments and transmits them to the reception system on an FIC segment basis. Each FIC segment unit is 37 bytes in size, and each FIC segment consists of a 2-byte FIC segment header and a 35-byte FIC segment payload. That is, one FIC chunk consisting of FIC chunk header and FIC chunk payload is segmented by 35 bytes. Then, a 2-byte FIC segment header is added to each of the segmented 35 bytes to form an FIC segment.

In an embodiment of the present invention, the length of the FIC chunk payload is variable. The length of the FIC chunk depends on the number of ensembles transmitted through the physical transmission channel and the number of mobile services included in each ensemble.

And the FIC chunk payload may include stuffing data. In this case, the stuffing data is used for the alignment between the FIC chunk and the boundary of the last FIC segment among the FIC segments belonging to the FIC chunk. By minimizing the length of the stuffing data, waste of the FIC segment can be reduced.

In the present invention, FIC segments divided from one FIC chunk may be transmitted through one subframe or a plurality of subframes. If the amount of data to be transmitted through the FIC chunk is larger than the amount of FIC segments transmitted through one subframe (in this case, a plurality of services with a very low bit rate And the like), it is possible to transmit all the necessary signaling data through the FIC chunk.

At this time, the FIC segment number indicates the FIC segment number in each FIC chunk, not the FIC segment number in each subframe. By doing so, the dependency of the FIC chunk and the subframe can be eliminated, thereby reducing the waste of the FIC segment.

Also, the present invention can add a null FIC segment. The null FIC segment is used to process the remaining FIC segments when stuffing is required in the corresponding M / H frame despite repeated transmission of FIC chunks. For example, suppose TNoG is 3 and the FIC chunk is divided into two FIC segments. At this time, when the FIC chunk is repeatedly transmitted through five subframes in one M / H frame, two FIC segments (i.e., the last subframe in time order) . In this case, one null FIC segment is allocated to the corresponding subframe and transmitted. That is, the null FIC segment is used to align the boundaries of the FIC chunk and the boundary of the M / H frame. At this time, since the null FIC segment is not an FIC segment segmented from the FIC chunk, the null FIC segment is not assigned an FIC segment number.

In order to discard the null FIC segment without processing in the receiving system, identification information capable of distinguishing the null FIC segment is required.

The present invention uses the FIC_type field in the header of the null FIC segment as identification information capable of distinguishing the null FIC segment. The present invention sets the FIC_type field value in the header of the null FIC segment to '11' to distinguish the null FIC segment. That is, if the FIC_type field value of the null FIC segment is set to '11' and transmitted to the receiving system, the payload of the FIC segment whose FIC_type field value is set to '11' in the receiving system can be discarded without processing . The '11' is an embodiment for facilitating the understanding of the present invention, and any value that can distinguish the null FIC segment can be used if an agreement is made between the transmitting and receiving sides in advance. It will not be limited. Further, the identification information for distinguishing the null FIC segment may be displayed using another field in the FIC segment header.

FIG. 13 shows an embodiment of a syntax structure of an FIC segment header according to the present invention.

The FIC segment header may include a FIC_segment_type field, a FIC_chunk_major_protocol_version field, a current_next_indicator field, an error_indicator field, an FIC_segment_num field, and a FIC_last_segment_num field. The description of each field is as follows.

The FIC_segment_type field (2 bits) indicates the type of the corresponding FIC segment. If the field value is '00', it indicates that the corresponding FIC segment is an FIC segment transmitting a part of the FIC chunk. If the field value is '11', it indicates that the FIC segment is a null FIC segment for transmitting stuffing data. The remaining values are reserved for future use. (A two bit field, which indicates when set to '00', the FIC-Segment is carrying a portion of an FIC-Chunk and when set to '11' is a NULL FIC-Segment, which carries stuffing data.

The FIC_chunk_major_protocol_version field (2 bits) indicates the major protocol version of the corresponding FIC chunk. The value of this field shall be the same as the FIC_major_protocol_version field value in the corresponding FIC chunk header. A detailed description of the major protocol version of the FIC chunk syntax will be omitted since it will be described with reference to the description of the FIC chunk header of FIG. 11 described above.

The current_next_indicator field (1 bit) indicates whether the corresponding FIC segment is applied to the current M / H frame or the next M / H frame. For example, if the field value is set to 1, the corresponding FIC segment indicates that a part of the FIC chunk applicable to the current M / H frame is transmitted. Conversely, if the field value is set to 0, the corresponding FIC segment indicates to transmit a part of the FIC chunk that can be applied to the next M / H frame.

The error_indicator field (1 bit) indicates whether an error has occurred in the corresponding FIC segment during transmission. The error_indicator field is set to '1' when an error occurs and to '0' when there is no error. That is, when there is an error that can not be recovered in the process of configuring the FIC segment, this field is set to '1'. This field allows the receiving system to recognize the presence or absence of an error in the FIC segment.

The FIC_seg_number field (4 bits) indicates the number of the corresponding FIC segment when one FIC chunk is divided into a plurality of FIC segments. For example, if the corresponding FIC segment is the first FIC segment of the FIC chunk, the FIC_seg_number field value is set to 0x0, and if the FIC segment is the second FIC segment, the FIC_seg_number field value is set to 0x1. That is, the FIC_seg_number field is incremented by 1 with each additional FIC segment in the FIC chunk (A 4-bit unsigned integer number field which gives the number of this FIC-Segment. For the first FIC-Segment of an FIC-Chunk , the value of this field shall be set to 0x0. This field shall be incremented by one additional segment in the FIC Chunk). If the FIC chunk is divided into four FIC segments, the FIC_seg_number field value of the last FIC segment of the FIC chunk is indicated by 0x3.

The FIC_last_seg_number field (4 bits) indicates the number of the last FIC segment of the complete FIC chunk (that is, the FIC segment having the highest FIC_segment_num field value) (A 4-bit unsigned integer number field which gives the number of the last FIC -Segment (i.e., the FIC Segment with the highest FIC_segment_num) of the complete FIC Chunk).

In this case, since FIC segment numbers are sequentially assigned to FIC segments in one subframe, the last FIC segment number and TNOG always match in this case. However, in the FIC segment number allocation scheme according to the present invention, the last FIC segment number and the TNOG do not always coincide with each other. That is, they may or may not match. The TNoG is the total number of data groups allocated to one subframe. For example, if TNoG is 6 and the FIC chunk is divided into 8 FIC segments, then the TNoG is 6 and the last FIC segment number is 8.

In another embodiment of the present invention, the null FIC segment may be separated using the FIC_segment_num field value in the FIC segment header. That is, since the FIC segment number is not allocated to the null FIC segment, the transmission system allocates null data to the FIC_segment_num field value of the null FIC segment and transmits the null data. In the receiving system, the FIC segment to which the null data is allocated in the FIC_segment_num field value, It may be recognized as an FIC segment. It is also possible to allocate previously promised data in the transmitting / receiving system instead of the null data to the FIC_segment_num field value.

As described above, the FIC chunk may be divided into a plurality of FIC segments and transmitted through one subframe or a plurality of subframes. In addition, only FIC segments divided from one FIC chunk may be transmitted through one subframe, and FIC segments divided from a plurality of FIC chunks may be transmitted through one subframe. Here, the number assigned to each FIC segment is not a number in the corresponding subframe, but a number in the corresponding FIC chunk (i.e., the FIC_seg_number field value). In order to align the boundary of the M / H frame and the boundary of the FIC chunk, a null FIC segment may be transmitted. In this case, no segment number is allocated to the null FIC segment.

As described above, one FIC chunk may be transmitted through a plurality of subframes, and a plurality of FIC chunks may be transmitted through one subframe. However, the FIC segments may be interleaved and transmitted in units of subframes As an embodiment.

A schematic description of the transmission system

FIG. 14 is a schematic diagram showing an embodiment of a transmission system for applying the present invention having the above-described structure, and may include a service multiplexer 100 and a transmitter or exciter 200 .

Here, the service multiplexer 100 is located in a studio of each broadcasting station, and the transmitter 200 is located in a site away from the studio. At this time, the transmitter 200 may be located in a plurality of different areas. And, in one embodiment, the plurality of transmitters may share the same frequency, in which case the plurality of transmitters all transmit the same signal. This corresponds to data transmission using a single frequency network (SFN). Then, in the receiving system, the channel equalizer compensates the signal distortion due to the reflected wave to restore the original signal. In another embodiment, the plurality of transmitters may have different frequencies for the same channel. This corresponds to data transmission using a Multi Frequency Network (MFN).

Various methods may be used for the data communication between the service multiplexer and each remote transmission station, and an interface standard such as SMPTE-310M (Synchronous Serial Interface for transport of MPEG-2 data) may be used . In the SMPTE-310M interface standard, the output data rate of the service multiplexer is fixed at a constant data rate. For example, it is set at 19.39 Mbps for 8VSB and 38.78 Mbps for 16VSB. Also, in the conventional 8VSB transmission system, a transport stream (TS) packet having a data rate of about 19.39 Mbps can be transmitted to one physical channel. Even in the transmitter according to the present invention, which is backward compatible with the existing transmission system, the mobile service data is further encoded and multiplexed in the TS packet format with the main service data. At this time, the multiplexed TS packet data The rate is about 19.39 Mbps.

At this time, the service multiplexer 100 receives at least one kind of main service data and table information for each main service, for example, PSI / PSIP table data, and encapsulates it into a TS packet.

The service multiplexer 100 may include at least one type of mobile service data for a mobile service and table information for each mobile service, for example, program specific information (PSI) / program information (PSIP) Protocol) table data and encapsulates them into mobile service data packets in the form of transport stream (TS) packets, respectively.

The service multiplexer 100 receives an RS frame including at least one kind of mobile service data for a mobile service and table information for each mobile service, It can be encapsulated into a mobile service data packet.

The service multiplexer 100 multiplexes the encapsulated TS packets according to a preset multiplexing rule, and outputs the multiplexed TS packets to the transmitter 200.

Meanwhile, the RS frame has a size of N (row) x 187 (column) bytes as shown in FIG. N is the length of the row (i.e., the number of columns), and 187 is the length of the column (i.e., the number of rows).

In the present invention, each N-byte row is referred to as an M / H service data packet for convenience of explanation. The M / H service data packet may be composed of 2 bytes of M / H header and N-2 bytes of M / H payload. Here, the allocation of the M / H header area to 2 bytes is only an embodiment, and the designer allocates the M / H header area to be different, so that the present invention is not limited to the above embodiment.

The RS frame is generated by collecting N-2 (row) x 187 (column) byte table information and / or IP datagram. One RS frame may also include table information and IP datagrams (i.e., mobile service data) corresponding to one or more mobile services. For example, IP datagrams and table information of two types of mobile services, news (e.g., IP datagram for mobile service 1) and securities (e.g., IP datagram for mobile service 2) .

That is, table information of a section structure may be allocated to the M / H payload in the M / H service data packet constituting the RS frame, or an IP datagram of the mobile service data may be allocated.

Alternatively, an IP datagram of table information may be allocated to an M / H payload in an M / H service data packet constituting the RS frame, or an IP datagram of mobile service data may be allocated.

At this time, it may happen that the M / H service data packet does not become N bytes including the M / H header.

In this case, a stuffing byte may be allocated to the remaining payload portion of the corresponding M / H service data packet. For example, after assigning program table information to one M / H service data packet, if the length of the M / H service data packet is N-20 bytes including the M / H header, You can allocate bytes.

16 shows an example of fields allocated to an M / H header field in an M / H service data packet according to the present invention, and may include a type_indicator field, an error_indicator field, a stuff_indicator field, and a pointer field.

The type_indicator field may allocate 3 bits in one embodiment and indicate the type of data allocated to the payload in the corresponding M / H service data packet. That is, it indicates whether the data of the M / H payload is an IP datagram or signaling information including table information. At this time, each data type constitutes one logical channel. In a logical channel transmitting an IP datagram, a plurality of mobile services are multiplexed and transmitted, and each mobile service is demultiplexed in the IP layer.

The error_indicator field may allocate 1 bit in one embodiment and indicates whether the corresponding M / H service data packet is erroneous. For example, if the value of the error_indicator field is 0, it means that there is no error in the corresponding M / H service data packet, and if it is 1, it means that there is an error.

The stuff_indicator field may allocate 1 bit in one embodiment, and indicates whether there is a stuffing byte in the payload of the corresponding M / H service data packet. For example, if the stuff_indicator field value is 0, it means that there is no stuffing byte in the corresponding M / H service data packet, and if it is 1, it means that there is a stuffing byte.

The pointer field may allocate 11 bits in one embodiment and indicate location information where new data (i.e., new signaling information or a new IP datagram) starts in the corresponding M / H service data packet.

For example, if an IP datagram for mobile service 1 and an IP datagram for mobile service 2 are allocated to the first M / H service data packet in the RS frame as shown in FIG. 15, And the start position of the IP datagram for mobile service 2 in the service data packet.

If there is no new data to start in the corresponding M / H service data packet, the pointer field value is displayed as a maximum value. In the present invention, 11 bits are allocated to the pointer field. Thus, if 2047 is indicated in the pointer field value, it means that there is no data to be newly started. The point indicated when the pointer field is 0 may be changed according to the type_indicator field value and the stuff_indicator field value.

The order, location, and meaning of the fields allocated to the M / H header in the M / H service data packet shown in FIG. 16 are merely examples for facilitating understanding of the present invention. The order, location, meaning, and the number of fields to which additional fields are allocated can be easily changed by those skilled in the art, so that the present invention is not limited to the above embodiments.

17A and 17B show another example of an RS frame according to the present invention. FIG. 17A shows an example of an RS frame to be allocated to an A / B area in a data group, (B) shows a configuration example of an RS frame to be allocated to the C / D area in the data group.

17A and 17B, the column length (i.e., the number of rows) of the RS frame to be allocated to the A / B area and the column length (i.e., the number of rows) of the RS frame to be allocated to the C / , But the row length (i.e., the number of columns) may be different from each other.

In the present invention, when the row length of the primary RS frame to be allocated to the A / B area in the data group is N1 bytes and the row length of the secondary RS frame to be allocated to the C / D area is N2 bytes, As an embodiment. Herein, N1 and N2 may be changed according to transmission parameters or depending on which area in the data group the corresponding RS frame is transmitted.

Each row of N1 and N2 bytes is also referred to as an M / H service data packet for convenience of explanation. The M / H service data packet in the RS frame to be allocated to the A / B area in the data group may be composed of 2 bytes of M / H header and N1-2 bytes of M / H payload. The M / H service data packet in the RS frame to be allocated to the C / D area in the data group may be composed of 2 bytes of M / H header and N2-2 bytes of M / H payload.

In the present invention, the primary RS frame for the A / B area in the data group and the secondary RS frame for the C / D area may include at least one of the table information and the IP datagram. Also, one RS frame may include an IP datagram corresponding to one or more mobile services.

The portions that are not described in Figs. 17 (a) and 17 (b) can be applied as they are in Fig.

On the other hand, the number N of the columns in one RS frame is determined according to the following equation (2).

는 X 이하의 가장 큰 정수이다. In Equation (2), NoG denotes the number of data groups allocated to one subframe, PL denotes the number of SCCC (Concatenated Convolution Code) payload bytes allocated to one data group, and P denotes a number The number of RS parity bytes to be added. And

Is the largest integer less than or equal to X.

In Equation (2), PL (Portion Length) is an RS frame portion length, which is equal to the number of SCCC payload bytes allocated to the corresponding data group. The PL may vary according to the RS frame mode, the SCCC block mode, and the SCCC outer code mode. Tables 2 to 5 below illustrate examples of PL values depending on the RS frame mode, the SCCC block mode, and the SCCC outer code mode. A detailed description of the SCCC block mode and the SCCC outer code mode will be described later.

SCCC outer code mode PL for Region A for Region B for Region C for Region D 00 00 00 00 9624 00 00 00 01 9372 00 00 01 00 8886 00 00 01 01 8634 00 01 00 00 8403 00 01 00 01 8151 00 01 01 00 7665 00 01 01 01 7413 01 00 00 00 7023 01 00 00 01 6771 01 00 01 00 6285 01 00 01 01 6033 01 01 00 00 5802 01 01 00 01 5550 01 01 01 00 5064 01 01 01 01 4812 Others Reserved

Table 2 shows an example of the PL value of each data group in the RS frame according to the SCCC outer code mode value when the RS frame mode value is 00 and the SCCC block mode value is 00. [

For example, assuming that the SCCC outer code mode values of the A / B / C / D areas in the data group are respectively 00 (i.e., coding of 1/2 coding rate is performed in the block processor 302 in the subsequent stage) The PL value in each data group of the RS frame can be 9624 bytes. That is, mobile service data of 9624 bytes in one RS frame can be allocated to the A / B / C / D area of the corresponding data group.

SCCC outer code mode PL 00 9624 01 4812 Others Reserved

Table 3 shows an example of the PL value of each data group in the RS frame according to the SCCC outer code mode value when the RS frame mode value is 00 and the SCCC block mode value is 01. [

SCCC outer code mode PL For Region A for Region B 00 00 7644 00 01 6423 01 00 5043 01 01 3822 Others Reserved

Table 4 shows an example of the PL value of the primary RS frame varying according to the SCCC outer code mode value when the RS frame mode value is 01 and the SCCC block mode value is 00. [ For example, if the SCCC outer code mode value of the A / B area is 00 each, 7644 bytes of mobile service data in the primary RS frame can be allocated to the A / B area of the corresponding data group.

SCCC outer code mode PL For Region C for Region D 00 00 1980 00 01 1728 01 00 1242 01 01 990 Others Reserved

Table 5 shows an example of the PL value of the secondary RS frame which varies according to the SCCC outer code mode value when the RS frame mode value is 01 and the SCCC block mode value is 00. [ For example, if the SCCC outer code mode value of the C / D area is 00 each, 1980 bytes of mobile service data in the secondary RS frame can be allocated to the C / D area of the corresponding data group.

Service multiplexer

FIG. 18 is a detailed block diagram illustrating an exemplary embodiment of the service multiplexer, which includes a controller 110 for controlling overall operation of the service multiplexer, a table information generator 120 for a main service, A base station 130, a mobile service multiplexer 150, and a transport multiplexer 160.

The transport multiplexer 160 may include a main service multiplexer 161 and a transport stream (TS) packet multiplexer 162.

18, at least one kind of compression-encoded main service data and table data generated by the table information generator 120 for the main service are input to the main service multiplexer 161 of the transport multiplexer 160 do. The table information generator 120 generates PSI / PSIP table data in an MPEG-2 private section format.

The main service multiplexer 161 encapsulates the main service data and the PSI / PSIP table data in the form of an MPEG-2 TS packet, multiplexes the TS packets, and transmits the multiplexed TS packets to a TS packet multiplexer 162, . The data packet output from the main service multiplexer 161 will be referred to as a main service data packet for convenience of explanation.

The mobile service multiplexer 150 receives at least one type of compression-coded mobile service data and table information for the mobile service, for example, PSI / PSIP table data, and encapsulates them in the form of MPEG-2 TS packets, encodes the TS packets, and outputs the multiplexed TS packets to the TS packet multiplexer 162. The data packet output from the mobile service multiplexer 150 will be referred to as a mobile service data packet for convenience of explanation.

Alternatively, the mobile service multiplexer 150 receives an RS frame generated using at least one type of compression-coded mobile service data and table information for the mobile service, encapsulates the received RS frame in the form of MPEG-2 TS packets, ), And output these TS packets to the TS packet multiplexer 162. The data packet output from the mobile service multiplexer 150 will be referred to as a mobile service data packet for convenience of explanation.

The mobile service multiplexer 150 encapsulates an RS frame inputted in one of the formulas (a) and (b) in FIG. 15 or TS packets into an TS packet.

At this time, the transmitter 200 needs identification information to separate and process the main service data packet and the mobile service data packet. The identification information may be a predetermined value in accordance with the promise of the transmitting / receiving side, may be composed of separate data, or may be used by modifying a value of a predetermined position in the data packet.

In an embodiment of the present invention, different PIDs (Packet Identifiers) may be allocated to the main service data packet and the mobile service data packet, respectively. That is, by assigning a PID (or null PID) not used in the main service to the mobile service, the transmitter 200 can distinguish the main service data packet from the mobile service data packet by referring to the PID of the input data packet.

In another embodiment, by modifying the synchronization byte in the header of the mobile service data packet, the synchronization byte value of the service data packet can be used to distinguish the mobile service data packet. For example, the synchronous byte of the main service data packet is output without modification as it is defined in ISO / IEC13818-1 (for example, 0x47), and the synchronous byte of the mobile service data packet is transformed and output, It is possible to distinguish between the data packet and the mobile service data packet. Conversely, the main service data packet and the mobile service data packet can be distinguished by modifying the synchronization byte of the main service data packet and outputting the synchronization byte of the mobile service data packet without modification.

There are various methods for modifying the sync byte. For example, the synchronization byte may be inverted bit by bit, or only some bits may be inverted.

As described above, the identification information for distinguishing the main service data packet and the mobile service data packet can be any one, and therefore, the present invention is not limited to the above-described embodiments.

Meanwhile, the transport multiplexer 160 can use the transport multiplexer used in the existing digital broadcasting system as it is. That is, to multiplex the mobile service data with the main service data, the data rate of the main service is limited to a data rate of (19.39-K) Mbps, and K Mbps corresponding to the remaining data rate is allocated to the mobile service. By doing so, the already used transport multiplexer can be used without modification.

The transport multiplexer 160 multiplexes the main service data packet output from the main service multiplexer 161 and the mobile service data packet output from the mobile service multiplexer 150 and transmits the multiplexed main service data packet to the transmitter 200.

However, it may happen that the output data rate of the mobile service multiplexer 150 is less than K Mbps. For example, if K Mbps of 19.39 Mbps is assigned to mobile service data in the service multiplexer 100 and the remaining (19.39-K) Mbps is allocated to main service data, the service multiplexer 100 ), The data rate of the mobile service data multiplexed is smaller than K Mbps. This is because, in the case of the mobile service data, the pre-processor of the transmitter 200 performs additional encoding to increase the amount of data. As a result, the data rate of the mobile service data that can be transmitted by the service multiplexer 100 becomes smaller than K Mbps.

For example, the preprocessor of the transmitter 200 performs coding of at least a half coding rate for mobile service data, so that the amount of output data of the preprocessor is more than twice as much as the amount of input data. Therefore, the sum of the data rate of the main service data multiplexed by the service multiplexer 100 and the data rate of the mobile service data is always smaller than or equal to 19.39 Mbps.

The service multiplexer 100 of the present invention may perform various embodiments to adjust the final output data rate of the mobile service multiplexer 150 to K Mbps.

In one embodiment, the null packet generator 130 generates a null data packet and outputs the null data packet to the mobile service multiplexer 150. The mobile service multiplexer 150 multiplexes the null data packet and the mobile service data packet, The data rate can be set to K Mbps.

At this time, the null data packet is transmitted to the transmitter 200 and then discarded. That is, it is not transmitted to the receiving system. For this, identification information capable of distinguishing the null data is also needed. The identification information for identifying the null data packet may be a predetermined value or may be composed of separate data depending on the promise of the transmitting / receiving side, and the value of the predetermined position in the null data packet may be modified and used It is possible. For example, the null packet generator 130 may modify the synchronization byte value in the header of the null data packet to use it as identification information, or set the transport_error_indicator flag to 1 to use it as identification information. In the present invention, the transport_error_indicator flag of a header in a null data packet is used as identification information for distinguishing a null data packet. In this case, the transport_error_indicator flag of the null data packet is set to '1', and the transport_error_indicator flag of all the data packets other than the null data packet is reset to '0' to distinguish the null data packet. That is, when the null data packet is generated in the null packet generator 130, if the transport_error_indicator flag is set to '1' in the header field of the null data packet, the transmitter 200 can distinguish it. Since the identification information for identifying the null data packet can be any value that can distinguish the null data packet, the present invention is not limited to the above embodiment.

As another embodiment for adjusting the final output data rate of the mobile service multiplexer 150 to K Mbps, an Operations and Maintenance Packet (OMP) may also be used. In this case, the mobile service multiplexer 150 may multiplex the mobile service data packet, the null data packet, and the OM packet to set the output data rate to K Mbps.

In order to process the mobile service data in the transmitter 200, signaling data such as a transmission parameter is required.

In one embodiment of the present invention, the transmission parameter is inserted into the payload area of the OM packet and transmitted to the transmitter 200 as an embodiment.

At this time, to enable the transmitter 200 to identify that the transmission parameter is inserted in the OM packet, identification information that indicates that the transmission parameter is inserted into the type field (= OM_type field) of the corresponding OM packet is displayed As an embodiment.

That is, a packet called an Operations and Maintenance Packet (OMP) is defined for the purpose of operation and management of the transmission system. For example, the OMP conforms to the format of the MPEG-2 TS packet and the corresponding PID has a value of 0x1FFA. The OMP consists of a header of 4 bytes and a payload of 184 bytes. The first byte of the 184 bytes indicates the type of the OM packet as the OM_type field, and the remaining 183 bytes are the actual data as the OM_payload field.

In the present invention, it is possible to recognize that the transmission parameter is inserted in the corresponding OM packet by using a predetermined value among the unused field values of the OM_type field. Then, the transmitter 200 can find the OMP by looking at the PID. The OM_type field in the OMP can be parsed so that the transmitter 200 knows whether the transmission parameter is inserted in the OM packet.

The M / H frame information (e.g., M / H frame_index), FIC information, parade information (e.g., number_of_parades, parade_id, parade_repetition_cycle, ensemble_id), group information (E.g., number_of_group, start_group_number), SCCC information (e.g., SCCC_block_mode, SCCC_outer_code_mode), RS frame information (e.g., RS_Frame_mode, RS_frame_continuity_counter), and RS encoding information (e.g., RS_code_mode).

At this time, the OM packets into which the transmission parameters are inserted are generated at regular intervals and can be multiplexed with mobile service data packets.

The multiplexing rule of the mobile service multiplexer 150, the main service multiplexer 161 and the TS packet multiplexer 160 and the generation of null data packets are performed under the control of the controller 110.

The TS packet multiplexer 162 multiplexes the data packet output at (19.39-K) Mbps from the main service multiplexer 161 and the data packet multiplexed and output at K Mbps from the mobile service multiplexer 150, And transmits the multiplexed data packet to the transmitter 200 at a data rate of 19.39 Mbps.

transmitter

FIG. 19 is a block diagram of a transmitter 200 according to an embodiment of the present invention. The transmitter 200 includes a control unit 201, a demultiplexer 210, a packet jitter mitigator 220, a pre- Processor 230, a packet multiplexer 240, a post-processor 250, a synchronous multiplexer 260, and a transmission unit 270.

Upon receiving a data packet from the service multiplexer 100, the demultiplexer 210 should distinguish whether the received data packet is a main service data packet, a mobile service data packet, or a null data packet.

In one embodiment, the demultiplexer 210 can distinguish a mobile service data packet from a main service data packet using a PID in a received data packet, and distinguish a null data packet using a transport_error_indicator field.

If an OM packet is included in the received data packet, the OM packet can be identified using the PID in the received data packet. At this time, if the OM_type field in the separated OM packet is used, whether or not the transmission parameter is included in the payload area of the corresponding OM packet is received.

The main service data packet separated by the demultiplexer 210 is output to the packet jitter separator 220, the mobile service data packet is output to the preprocessor 230, and the null data packet is discarded. If the transmission parameter is included in the OM packet, the transmission parameter is extracted and output to the corresponding block, then the OM packet is discarded. In the present invention, the transmission parameters extracted from the OM packet are output to the corresponding block through the control unit 201 as an embodiment.

The pre-processor 230 demultiplexes the mobile service data in the mobile service data packet demultiplexed and output by the demultiplexer 210, and transmits the mobile service data to a mobile station A data group forming process is performed. This is to ensure that the mobile service data responds quickly and robustly to noise and channel changes. The preprocessor 230 may refer to transmission parameters extracted from the OM packet at the time of further encoding. Also, the preprocessor 230 forms a data group by collecting a plurality of mobile service data packets, and allocates the base data, the mobile service data, the RS parity data, the MPEG header, and the like to the predetermined area in the data group.

The preprocessor in the transmitter

20 is a block diagram showing an embodiment of the preprocessor 230 according to the present invention. The M / H frame encoder 301, the block processor 302, the group formatter 303, the signaling encoder 305, And a packet formatter 305.

The M / H frame encoder 301 in the preprocessor 230 configured as described above forms an RS frame corresponding to the ensemble after data-riding the mobile service data input through the demultiplexer 210, And performs encoding for error correction. The M / H frame encoder 301 may include one or more RS frame encoders. That is, the RS frame encoders may be provided in parallel for the number of parades in the M / H frame. As described above, an M / H frame is a basic time period for transmitting one or more parades. Each parade is made up of one or two RS frames.

FIG. 21 is a conceptual block diagram illustrating an embodiment of the M / H frame encoder 301. Referring to FIG. The M / H frame encoder 301 may include an input demultiplexer 309, M RS frame encoders 310 to 31M-1, and an output mux 320. Where M is the number of parades in one M / H frame.

The demultiplexer 309 outputs the input mobile service data to an RS frame encoder of M RS frame encoders on an ensemble basis.

At this time, the ensemble can be mapped to the RS frame encoder or parade. For example, if one parade consists of one RS frame, the ensemble, RS frame and parade can be mapped to 1: 1: 1 respectively.

The RS frame encoder forms a corresponding RS frame using the ensemble mobile service data, and performs an error correction coding process on an RS frame basis. The RS frame in which error correction coding is performed to allocate to a plurality of data groups is divided into a plurality of portions. At this time, data of one RS frame according to the RS frame mode of Table 1 may be all allocated to A / B / C / D regions in a plurality of data groups, or may be allocated to A / B regions or C / have.

If the RS frame mode value is 01, that is, if the data of the primary RS frame is allocated to the A / B area in the data group and the data in the secondary RS frame is allocated to the C / D area within the data group, The frame encoder forms a primary RS frame and a secondary RS frame for each parade. On the contrary, if the RS frame mode value is 00, that is, if the data of the primary RS frame is all allocated to the A / B / C / D area in the data group, each RS frame encoder outputs one RS frame for each parade, To form a primary RS frame.

Each of the RS frame encoders separates each RS frame into a plurality of portions. Each portion of the RS frame corresponds to an amount of data that can be transmitted by one data group. The multiplexer 320 multiplexes parts in the M RS frames 310 to 31M-1 and outputs the multiplexed parts to the block processor 302. [

For example, if one parade transmits two RS frames, the portions of the primary RS frame in the M RS frames 310 to 31M-1 are multiplexed and output, and the portions of the secondary RS frame are multiplexed .

The demultiplexer 309 and the multiplexer 320 operate according to the control signal of the controller 201. [ The control unit 201 may provide necessary FEC modes to each RS frame encoder. Examples of the FEC mode include an RS code mode and the like, which will be described later in detail.

22 is a detailed block diagram illustrating an embodiment of one RS frame encoder among a plurality of RS frame encoders in an M / H frame encoder.

One RS frame encoder may include a primary encoder 410 and a secondary encoder 420. Here, the secondary encoder 420 may be operated according to the RS frame mode or not. For example, if the RS frame mode is 00 as shown in Table 1, the secondary encoder 420 does not operate.

The primary encoder 410 may include a data randomizer 411, an RS-CRC encoder 412, and an RS frame divider 413. The secondary encoder 420 may include a data randomizer 421, an RS-CRC encoder 422, and an RS frame divider 423.

That is, the data randomizer 411 of the primary encoder 410 receives and renders the primary ensemble mobile service data output from the demultiplexer 309, and outputs the data to the RS-CRC encoder 412. At this time, the data renderer 411 performs rendering on the mobile service data, so that the data renderer 251 of the post-processor 250 can skip the process of rendering the mobile service data. The data renderer 411 may discard the synchronization byte in the mobile service data packet and perform rendering. Or perform randomization without discarding the sync byte, which is optional for the system designer. According to an embodiment of the present invention, randomizing is performed without discarding synchronization bytes in the mobile service data packet.

The RS-CRC encoder 412 forms an RS frame corresponding to the randomized primary ensemble, and performs FEC (Reed-Solomon) and CRC (Cyclic Redundancy Check) Forward Error Correction) and outputs it to the RS frame divider 413.

That is, the RS-CRC encoder 412 forms an RS frame by collecting a plurality of mobile service data packets input as randomized and performs at least one of an error correction encoding process and an error detection encoding process on an RS frame basis . In this way, robustness is given to mobile service data, and congestion errors caused by radio wave environment change are suppressed, so that it is possible to cope with extremely poor and rapidly changing radio wave environment.

In addition, the RS-CRC encoder 412 may combine a plurality of RS frames to form a super frame, and may perform row permutation on a super frame basis. The low permutation is also referred to as low interleaving, and will be referred to as low mixing in the present invention for convenience of explanation. The low shuffling process may be omitted.

In this case, when the RS-CRC encoder 412 performs a process of mixing each row of the super frame according to a predetermined rule, the positions of the rows before and after the low-mix are different in the super frame. Even if an error that can not be corrected is contained in one RS frame to be decoded because a section in which a large number of errors occur is very long in the super-frame-by-super-frame blurring, these errors are distributed throughout the super frame, The decoding capability is improved.

The RS-CRC encoder 412 applies RS coding for error correction coding and CRC (Cyclic Redundancy Check) coding for error detection coding. When the RS coding is performed, parity data to be used for error correction is generated, and CRC coding is performed to generate CRC data to be used for error detection.

The CRC data generated by the CRC encoding can be used to indicate whether the mobile service data is transmitted through the channel and is damaged by an error. The present invention may use other error detection coding methods other than CRC coding, or may increase the overall error correction capability on the receiving side by using an error correction coding method.

Here, the RS-CRC encoder 412 can perform RS frame configuration, RS encoding, CRC encoding, super frame configuration, and low frame mixing at a superframe by referring to the transmission parameters provided through the controller 201 have.

23A and 23B are diagrams illustrating a process of assigning one or two RS frames to a plurality of potions according to an RS frame mode value and assigning each potion to a corresponding area in a corresponding data group. The data allocation of the data group is performed in the group formatter 303 at the rear end.

That is, FIG. 23A shows a case where the RS frame mode is 00, and only the primary encoder 410 operates in FIG. 22 to form one RS frame for one parade. One RS frame is divided into a plurality of potions, and the data of each potion is allocated to the A / B / C / D area in the corresponding data group.

FIG. 23B shows a case where the RS frame mode is 01. In FIG. 22, both the primary encoder 410 and the secondary encoder 420 operate to generate two RS frames, that is, a primary RS frame And a secondary RS frame. The primary RS frame is also divided into a plurality of potions, and the secondary RS frame is divided into a plurality of potions. At this time, the data of each primary RS frame position is allocated to the A / B area in the corresponding data group, and the data of each secondary RS frame position is allocated to the C / D area in the corresponding data group.

Specific description of RS frame

24 (a) shows an example of an RS frame generated by the RS-CRC encoder 412 of the present invention.

When the RS frame is formed as shown in FIG. 24A, the RS-CRC encoder 412 generates Nc-Kc (= P) parity bytes by performing (Nc, Kc) -RS coding on each column (187 + P) bytes by adding the P parity bytes generated after the last byte of the corresponding column. Here, Kc is 187 as shown in FIG. 24 (a), and Nc is 187 + P.

Here, the P value may vary according to the RS code mode value.

Table 6 below shows an example of the RS code mode which is one of the RS encoding information.

RS code mode RS code Number of parity bytes (P) 00 (211, 187) 24 01 (223, 187) 36 10 (235,187) 48 11 Reserved Reserved

In Table 6, two bits are allocated to indicate the RS code mode. The RS code mode indicates the number of parity of the corresponding RS frame.

For example, if the RS code mode value is 10, (235, 187) -RS encoding is performed on the RS frame in FIG. 24A to generate 48 parity bytes, and 48 parity bytes are allocated to the last Add one byte after the byte to make a column of 235 bytes.

If the RS frame mode in Table 1 is 00, i.e., a single RS frame is displayed, only the Reed-Solomon (RS) code mode for the corresponding RS frame is displayed. However, if the RS frame mode of Table 1 is 01, i.e., a plurality of separate RS frames are displayed, the RS code mode is displayed corresponding to the primary and secondary RS frames, respectively. That is, the RS code mode is preferably applied independently to the primary RS frame and the secondary RS frame.

If the RS encoding process is performed for all N columns, an RS frame having a size of N (row) x (187 + P) (column) bytes as shown in FIG. 24B can be created.

At this time, each row of the RS frame is composed of N bytes. However, an error may be included in the RS frame according to channel conditions between the transmission and the reception. It is possible to use cyclic redundancy check (CRC) data (or a CRC code or a CRC checksum) to check whether an error occurs in each row unit.

The RS-CRC encoder 412 may perform CRC coding on the RS-coded mobile service data to generate the CRC data. The CRC data generated by the CRC encoding can be used to indicate whether the mobile service data is transmitted through the channel and is damaged by an error.

The present invention may use other error detection coding methods other than CRC coding, or may increase the overall error correction capability on the receiving side by using an error correction coding method.

24C shows an example of using a 2-byte (i.e., 16-bit) CRC checksum as CRC data. After generating a 2-byte CRC checksum for N bytes of each row, . By doing this, each row is expanded to N + 2 bytes.

The following Equation 3 shows an example of a polynomial for generating a 2-byte CRC checksum for each row of N bytes.

^{g (x) = x 16 +} x 12 + x 5 +1

Adding a 2-byte CRC checksum to each row is one embodiment, and the present invention is not limited to the above example.

When the RS coding and the CRC coding process described above are all performed, the RS frame of N x 187 bytes is expanded to the RS frame of (N + 2) x (187 + P) bytes.

Looking at the error correction scenario of the extended RS frame, the bytes in the RS frame are transmitted on the channel in the row direction. At this time, if a large amount of error occurs in the limited transmission time, an error occurs in the RS frame of the decoding process of the receiving system in the row direction. However, since the RS codes are performed in the column direction, errors are dispersed and effective error correction can be performed. At this time, parity byte (P) is increased as a method for more accurate error correction, but a proper compromise is needed because transmission efficiency is lowered. In addition, the error correction capability can be improved by using the error decoding in decoding.

In the RS-CRC encoder 412 of the present invention, it is also possible to perform low-permutation on a superframe basis in order to further improve the error correction capability of the RS frame.

25 (a) to 25 (d) show an embodiment of the low-mix process in units of super frames.

That is, the RS-CRC-encoded RS frames constitute a G-group super frame as shown in FIG. 25 (a). Since each RS frame is composed of (N + 2) x (187 + P) bytes, one superframe consists of (N + 2) x (187 + P) x G bytes.

When the process of mixing each row of the superframe with the preset rule is performed, the positions of the rows before and after the low-mix in the superframe are changed. That is, the i-th row of the superframe before low-mixing as shown in FIG. 25 (b) is located at the j-th row of the same superframe as shown in FIG. 25 (c) after low- The relationship between i and j can be found through the low-mix rule as shown in Equation (4) below.

Even after the superframe-based low mixing is performed, each row of the superframe consists of N + 2 bytes.

After all of the low-frame-by-super-frame shuffling is performed, the RS frame is divided into G low-mixed RS frames as shown in FIG. 25 (d) and provided to the RS frame divider 413.

Note that the RS parity and the number of columns of each RS frame constituting one superframe should be the same.

Similar to the above-described error correction scenario of the RS frame, even in the case of a superframe in which a large number of errors occur, since errors are contained in one RS frame to be decoded, the errors are dispersed throughout the superframe, The decoding capability is further improved as compared with the RS frame.

Until now, when dividing one data group into A / B / C / D regions, the RS frame forming and encoding process when allocating data of one RS frame to A / B / C / . That is, as one embodiment of transmitting one RS frame in one parade, in this case, the secondary encoder 420 is not operated.

On the other hand, when two RS frames are transmitted in one parade, the data of the primary RS frame can be allocated to the A / B area in the data group and the data of the secondary RS frame can be allocated to the C / D area in the corresponding data group. At this time, the primary encoder 410 receives the mobile service data to be allocated to the A / B area in the data group, forms a primary RS frame, and performs RS encoding and CRC encoding. The secondary encoder 420 receives the mobile service data to be allocated to the C / D area in the data group, forms a secondary RS frame, and performs RS coding and CRC coding. That is, the encoding of the primary RS frame and the secondary RS frame is performed independently of each other.

26 (a) and 26 (b) illustrate a case where mobile service data to be allocated to the A / B area in the data group is received and the primary RS frame is configured, the mobile service data to be allocated to the C / And error correction coding and error detection coding are performed, respectively.

26A, the mobile service data of the primary ensemble to be allocated to the A / B area in the data group is received from the RS-CRC encoder 412 of the primary encoder 410, and N1 (row) x An RS frame having a size of 187 (column) bytes is formed, RS encoding is performed for each column of the thus configured RS frame, P1 pieces of parity data are added for each column, CRC encoding is performed for each row, And a 2-byte CRC checksum is added every row.

(B) of FIG. 26 receives the secondary ensemble mobile service data to be allocated to the C / D area in the data group in the RS-CRC encoder 422 of the secondary encoder 420 and outputs N2 (row) x 187 RS encoding is performed on each column of the thus configured RS frame, P2 parity data is added for each column, CRC encoding is performed on each row, and a 2-byte CRC A checksum is added.

Referring to the transmission parameters provided through the controller 201, each of the RS-CRC encoders 412 and 422 encodes M / H frame information, FIC information, RS frame information (including RS frame mode), RS encoding information , SCCC information (including SCCC block mode information and SCCC outer code mode information), data group information, and data group area information. The transmission parameters are not only referenced for RS frame configuration, error correction coding, error detection coding in each RS-CRC encoder 412, 422, but also must be transmitted to the receiving system for normal decoding in the receiving system. In an embodiment of the present invention, the transmission parameters are transmitted to a reception system via a transmission parameter channel (TPC). The TPC will be described later in detail.

The data of the primary RS frame in which RS-frame encoding and super-frame low-mix are performed in the RS-CRC encoder 412 of the primary encoder 410 is output to the RS frame divider 413. If the secondary encoder 420 is operated, data of the secondary RS frame, which has been RS-CRC encoded by the RS-CRC encoder 422 of the secondary encoder 420 and low- (423).

The RS frame divider 413 of the primary encoder 410 separates the primary RS frame into a plurality of portions and outputs the divided signals to the multiplexer 320. Each portion of the primary RS frame corresponds to an amount of data that can be transmitted by one data group. Likewise, the RS frame divider 423 of the secondary encoder 420 separates the secondary RS frame into a plurality of portions, and outputs the secondary RS frame to the multiplexer 320.

The RS frame divider 413 of the primary encoder 410 will be described in detail. For convenience of description, an RS frame having a size of N (row) x 187 (column) bytes is formed as shown in FIGS. 24A to 24C, and RS Assume that parity data of bytes is appended and a CRC checksum of 2 bytes is appended to each row through CRC encoding.

Then, the RS frame divider 413 divides the encoded RS frame having the size of N + 2 (row) x 187 + P (column) bytes into a plurality of parts having a PL (where PL is the RS frame portion length) Partition.

In this case, the PL value may vary according to the RS frame mode, the SCCC block mode, and the SCCC outer code mode, as shown in Tables 2 to 5. In addition, the total number of bytes of the RS frame in which RS and CRC coding are performed is equal to or slightly smaller than 5 x NoG x PL. In this case, the RS frame is divided into ((5 x NoG) -1) pots of PL size and one pot of PL size or smaller size. That is, the size of each potion except the last potion among the potions divided from one RS frame is equal to PL.

If the size of the last portion is less than PL, stuffing bytes (or dummy bytes) are inserted into the last portion for the shortest number of bytes so that the size of the last portion is finally PL.

Each portion divided from one RS frame corresponds to an amount of data to be SCCC encoded and mapped into a single data group of one parade (each portion of a RS frame corresponds to the amount of data to be SCCC-encoded and mapped into a single data group of a Parade).

27 (a) and 27 (b) show that when dividing the (N + 2) x (187 + P) sized RS frame into (5 x NoG) As shown in FIG.

That is, as shown in FIG. 27 (a), RS and CRC-encoded RS frames are divided into a plurality of potions as shown in FIG. 27 (b). The number of potions to be divided from the RS frame is (5 x NoG). The first ((5 x NoG) - 1) potions include the PL size, but the last one potion may be equal to or less than the PL size. If the PL is smaller than the PL size, S stuffing bytes can be obtained and filled in as shown in Equation (5) so that the last portion is PL size.

S = (5 x No G x PL) - ((N + 2) x (187 + P))

Each portion including the PL size data is output to the block processor 302 via the multiplexer 320 of the M / H frame encoder 301.

In this case, the order of mapping the RS frame positions to the data groups of one parade is not the same as the order of allocation of the data groups defined in Equation (1) with the Group assignment order defined in Equation 1). That is, given a data group location of a parade in one M / H frame, the SCCC encoded RS frame positions are allocated in a time order (Given the Group positions of a Parade in an M / H Frame, the SCCC- RS Frame Portions shall be mapped in time order).

For example, in FIG. 11, the data groups of the second parade that is allocated are first allocated to the 13th slot (Slot # 12), and then allocated to the 3rd slot (Slot # 2). However, if data is placed in these assigned slots, the data is arranged in chronological order from left to right. That is, the first data group of parade # 1 is placed in the third slot (Slot # 2), and the second data group of parade # 1 is placed in the thirteenth slot (Slot # 13).

Block processor

Meanwhile, the block processor 302 performs SCCC outlier encoding on the output of the M / H frame encoder 301. That is, the block processor 302 encodes the data of each potion to be error-correction-coded and input to the group formatter 303 again with 1 / H (H is a natural number of 2 or more) code rate. The present invention is characterized in that the input data is encoded by either encoding at 1/2 coding rate (or 1/2 coding) or coding at 1/4 coding rate (or 1/4 coding) As an example. The data of each portion output from the M / H frame encoder 301 includes at least one of pure mobile service data, RS parity data, CRC data, stuffing data, and in a broad sense, data for mobile service. Therefore, the data of each potion will be described as mobile service data.

The group formatter 303 inserts the mobile service data encoded and output by the block processor 302 into a corresponding area in a data group formed according to a predefined rule, A holder or known data (or known data location holder) is also inserted in the corresponding area in the data group. Then, the group formatter 303 deinterleaves the data in the data group and the position holder.

In the present invention, the data group is divided into four areas A, B, C, and D, and consists of ten M / H blocks B1 to B10 based on the data interleaving as shown in FIG.

As shown in FIG. 5, if the data group is divided into a plurality of layered regions, the block processor 302 may encode the mobile service data to be inserted into each region at a different coding rate according to the characteristics of the layered region.

For example, the mobile service data to be inserted into the A / B area in the data group is encoded by the block processor 302 at a 1/2 coding rate, and the encoded mobile service data is transmitted to the group formatter 303 And can be inserted into the A / B area. The mobile service data to be inserted into the C / D region in the data group is encoded by the block processor 302 at a coding rate of 1/4, which has a higher error correction capability than 1/2 coding rate, May be inserted into the C / D area in the group formatter 303. [ As another example, the mobile service data to be inserted in the C / D region may be encoded by the block processor 302 at a code rate having a stronger error correction capability than the 1/4 code rate, May be inserted into the C / D area in the formatter 303, or may be left as a reserved area for future use.

The block processor 302 may perform 1 / H encoding on a SCCC block basis as another embodiment. The SCCC block includes at least one M / H block.

The M / H blocks B1 to B10 and the SCCC blocks SCB1 to SCB10 are equal to each other (SCB1 = B1, SCB2 = B2, SCB3 = B3, SCB4 = B4, SCB5 = B5, SCB6 = B6, SCB7 = B7, SCB8 = B8, SCB9 = B9, SCB10 = B10). For example, the M / H block B1 can perform coding at a 1/2 coding rate, the M / H block B2 at a 1/4 coding rate, and the M / H block B3 at a 1/2 coding rate. The same is true for the remaining M / H blocks.

Alternatively, a plurality of M / H blocks in the A, B, C, and D regions may be grouped into one SCCC block, and 1 / H encoding may be performed in units of SCCC blocks. This improves the reception performance of the C / D region. For example, the M / H block B1 to M / H block B5 are grouped into one SCCC block to perform 1/2 coding, and the encoded mobile service data is transmitted to the group formatter 303 from the M / H block B1 to the M / H block B5.

Further, 1/4 encoding is performed by grouping the M / H block B6 to the M / H block B10 into other SCCC blocks, and the thus-coded mobile service data is transmitted from the M / H block B6 of the data group in the group formatter 303 The M / H block B10 can be inserted. In this case, one data group is composed of two SCCC blocks.

As another embodiment, two M / H blocks may be combined into one SCCC block. For example, an M / H block B1 and an M / H block B6 may be combined to form one SCCC (SCB1) block. In the same manner, another SCCC (SCB2) block, an M / H block B3, and a block B8 are combined to form another SCCC (SCB3) block, an M / H block B4, B9 and another SCCC (SCB4) block, and another SCCC (SCB5) block by grouping the M / H block B5 and the M / H block B10. In this case, 10 M / H blocks are composed of 5 SCCC blocks. This can compensate for the reception performance of the C and D regions, where the reception performance is relatively low compared to the A region in the reception environment where the channel change is very severe. Also, the number of main service data symbols increases gradually from the area A to the area D, which causes performance degradation of the error correction code. As described above, by configuring a plurality of M / H blocks into one SCCC block, Can be reduced

When 1 / H encoding is performed in the block processor 302 as described above, the SCCC-related information must be transmitted to the receiving system in order to accurately recover the mobile service data.

Table 7 below shows an example of the SCCC block mode showing the relationship between the M / H block and the SCCC block among the SCCC related information.

SCCC Block Mode 00 01 10 11 Description One M / H Block per SCCC block Two M / H Blocks per SCCC block reserved reserved SCB SCB input, M / H Block SCB input, M / H Blocks SCB1 B1 B1 + B6 SCB2 B2 B2 + B7 SCB3 B3 B3 + B8 SCB4 B4 B4 + B9 SCB5 B5 B5 + B10 SCB6 B6 - SCB7 B7 - SCB8 B8 - SCB9 B9 - SCB10 B10 -

In Table 7, two bits are allocated to indicate the SCCC block mode. For example, if the SCCC block mode value is '00', it indicates that the SCCC block and the M / H block are identical. If the SCCC block mode value is 01, it indicates that each SCCC block is composed of two M / H blocks.

If one data group consists of two SCCC blocks as described above, this information can also be displayed in the SCCC block mode although it is not shown in Table 7. For example, when the SCCC block mode value is 10, each SCCC block is composed of 5 M / H blocks, and one data group can be composed of two SCCC blocks. Here, since the number of M / H blocks included in the SCCC block and the location of the M / H block may vary depending on the system designer, the present invention is not limited to the above embodiment, and the SCCC mode information can also be extended.

Table 8 below shows an example of code rate information of the SCCC block, that is, an SCCC outer code mode among the SCCC related information.

SCCC outer code mode Description 00 The outer code rate of a SCCC Block is 1/2 rate 01 The outer code rate of a SCCC Block is 1/4 rate 10 Reserved 11 Reserved

In Table 8, 2 bits are allocated to indicate the coding rate information of the SCCC block. For example, if the SCCC outer code mode value is 00, the code rate of the corresponding SCCC block indicates 1/2, and if 01 indicates 1/4.

If the SCCC block mode value in Table 7 indicates 00, the SCCC outer code mode can display the coding rate of each M / H block corresponding to each M / H block. In this case, since one data group includes 10 M / H blocks and each SCCC block mode is assumed to be allocated 2 bits, 20 bits are required to indicate the SCCC block mode for 10 M / H blocks .

As another example, if the SCCC block mode value in Table 7 indicates 00, the SCCC outer code mode may display the code rate of each region corresponding to each region in the data group. In this case, since one data group includes four areas A, B, C, and D, and each SCCC block mode is assumed to be allocated two bits, 8 bits are required to indicate the SCCC block mode for four areas Do.

As another example, if the SCCC block mode value in Table 7 indicates 01, the areas A, B, C, and D in the data group have the same SCCC outer code mode.

Meanwhile, Table 9 below shows an example of the SCCC output block length (SOBL) for each SCCC block when the SCCC block mode value is 00. FIG.

SCCC Block SOBL SIBL 1/2 rate 1/4 rate SCB1 (B1) 528 264 132 SCB2 (B2) 1536 768 384 SCB3 (B3) 2376 1188 594 SCB4 (B4) 2388 1194 597 SCB5 (B5) 2772 1386 693 SCB6 (B6) 2472 1236 618 SCB7 (B7) 2772 1386 693 SCB8 (B8) 2508 1254 627 SCB9 (B9) 1416 708 354 SCB10 (B10) 480 240 120

That is, knowing the SCCC output block length (SOBL) for each SCCC block determines the SCCC input block length (SIBL) for the corresponding SCCC block according to the outer code rate of each SCCC block . The SOBL is equal to the number of SCCC output (or outer encoded) bytes for each SCCC block, and SIBL is equal to the number of SCCC input (or payload) bytes for each SCCC block.

Table 10 below shows an example of SOBL and SIBL for each SCCC block when the SCCC block mode value is 01.

SCCC Block SOBL             SIBL 1/2 rate 1/4 rate SCB1 (B1 + B6) 3000 1500 750 SCB2 (B2 + B7) 4308 2154 1077 SCB3 (B3 + B8) 4884 2442 1221 SCB4 (B4 + B9) 3804 1902 951 SCB5 (B5 + B10) 3252 1626 813

To this end, the block processor 302 includes an RS frame portion-to-SCCC block converter 511, a byte-to-bit converter 512, a convolutional encoder 513, a symbol interleaver 514, a symbol- 515), and an SCCC block-MH block converter 516.

The convolutional encoder 513 and the symbol interleaver 514 are virtually concatenated with the trellis coding module 256 to construct the SCCC (the convolutional encoder 513 and the symbol interleaver 514 are virtually concatenated with the trellis encoder in the post-processor to construct the SCCC).

That is, the RS frame portion-to-SCCC block converter 511 uses the SIBL of Tables 9 and 10 according to the RS frame mode, the SCCC block mode, and the SCCC outer code mode to input the RS frame portion into a plurality of SCCC blocks . Here, the M / H frame encoder 301 outputs a primary RS frame portion according to an RS frame mode, or outputs a primary RS frame portion and a secondary RS frame portion.

If the RS frame mode is 00, the portion of the primary RS frame is equal to the amount of data mapped to 10 M / H blocks in one data group by SCCC outcoding in the block processor 302. If the SCCC block mode is 00, the primary RS frame is divided into 10 SCCC blocks according to Table 9. If the SCCC block mode is 01, the primary RS frame portion is divided into 5 SCCC blocks according to Table 10. On the other hand, if the RS frame mode is 01, the block processor 302 receives two RS frame positions. When the RS frame mode is 01, 01 is not used as the SCCC block mode value. The primary portion divided by the primary RS frame is SCCC outcoded by the block processor 302 as SCCC blocks SCB3, SCB4, SCB5, SCB6, SCB7, and SCB8. The SCCC blocks SCB3 and SCB8 are mapped to the intra-data group area B in the group formatter 303, and the SCCC blocks SCB4, SCB5, SCB6 and SCB7 are mapped to the area A. The secondary portion divided from the secondary RS frame is SCCC outcoded by the block processor 302 as SCCC blocks SCB1, SCB2, SCB9, and SCB10. The group formatter 303 maps the SCCC blocks SCB1 and SCB10 to the corresponding intra-data group area D, and the SCCC blocks SCB2 and SCB9 are mapped to the area C, respectively.

The byte-to-bit converter 512 separates the mobile service data bytes of each SCCC block output from the RS frame portion-to-SCCC block converter 511 into bits, and outputs the divided bits to the convolutional encoder 513.

The convolutional encoder 513 performs 1/2 coding or 1/4 coding on the input mobile service data bits.

FIG. 29 is a detailed block diagram showing an embodiment of the convolutional encoder 513, which is composed of two delayers 521 and 523 and three adders 522, 524 and 525. The input data bit U is encoded into 5 bits u0 to u4. At this time, the input data bit U is directly output as the most significant bit u0, and is simultaneously encoded and output to the lower bit u1u2u3u4.

That is, the input data bit U is directly output as the most significant bit u0 and simultaneously output to the first and third adders 522 and 525. The first adder 522 adds the input data bit U and the output of the first delay unit 521 and outputs the result to the second delay unit 523. The second adder 522 adds the input data bit U and the output of the first delay unit 521 to the second delay unit 523, 1 clock). The delayed data is output to the lower bit u1 and fed back to the first delay unit 521 at the same time. The first delay unit 521 delays the data fed back from the second delay unit 523 by a predetermined time (for example, one clock) and outputs the data at the lower bit u2. The first adder 522 and the first adder 522 2 adder 524, as shown in Fig.

The second adder 524 adds the outputs of the first and second delay units 521 and 523 and outputs the result as a lower bit u3. The third adder 525 adds the input data bit U and the output of the second adder 524 and outputs it as the least significant bit u4.

At this time, the first and second delay units 521 and 523 are reset to 0 at the beginning of each SCCC block. The convolutional encoder 513 of FIG. 29 may be used as a 1/2 coder or a 1/4 coder.

That is, when a part of the output bits of the convolutional encoder 513 of FIG. 29 are selected and output, they can be used as a 1/2 encoder or a 1/4 encoder.

Table 11 below shows an example of the output symbol of the convolutional encoder 513. [

Region 1/2 rate 1/4 rate SCCC Block mode = '00' SCCC Block mode = '01' A, B (u0, u1) (u0, u2), (u1, u4) (u0, u2), (u1, u4) C, D (u0, u1), (u3, u4)

For example, in the case of 1/2 code rate, one output symbol, that is, u0 and u1 bits, may be selected and output. In the case of the 1/4 code rate, two output symbols, i.e., four bits, may be selected and output according to the SCCC block mode. For example, when the SCCC block mode is 01, the output symbols of u 0 and u 2, and the output symbols of u 1 and u 4 are selected and output, the result of 1/4 coding is obtained.

The mobile service data symbols coded at 1/2 or 1/4 coding rate in the convolutional coding unit 513 are output to the symbol interleaver 514.

The symbol interleaver 514 performs block interleaving on the output data symbols of the convolutional encoder 513 on a symbol-by-symbol basis. That is, the symbol interleaver 514 is a type of block interleaver. The symbol interleaver 514 can be applied to any interleaver structurally as long as it is an interleaver that rearranges the interleaver. In the present invention, a variable length symbol interleaver applicable to a case where a symbol to be rearranged is a variable length symbol is used as an embodiment.

30 shows an embodiment of a symbol interleaver according to the present invention, where B is 2112 and L is 4096 is an example of symbol interleaving.

Where B is the block length in symbols output for symbol interleaving in the convolutional encoder 513 and L is the block length in symbol units actually interleaved in the symbol interleaver 514. [ At this time, the block length B of each symbol input to the symbol interleaver 514 is equal to 4 x SOBL. That is, since one symbol is composed of 2 bits, B can be set to 4 x SOBL.

In symbol interleaving, L = 2 ^m (where m is a natural number) and L ≥ B conditions. If the values of B and L are different, a null or dummy symbol is added as many as the number of differences (= LB), and an interleaving pattern is generated as shown in P '(i) of FIG.

Therefore, B is the block size of the actual symbols input to the symbol interleaver 514 for interleaving, and L is the interleaving unit in which the actual interleaving is performed by the interleaving pattern generated by the symbol interleaver 514. [

Equation to 6, after the input symbol B dog to rearrange the order at the symbol interleaver 514 in sequence, L = 2 ^m, yet find made rearranging the interleave pattern of L satisfying L ≥ B Conditions Is a mathematical expression of the process.

For all positions 0 ≤ i ≤ B-1,

P i (i) = 89 x i x (i + 1) / 2 mod L

Where L ≥ B, L = 2 ^m and m is a natural number.

30, the order of B input symbols and (LB) null symbols is rearranged in units of L symbols as shown in P '(i) of Equation (6) and FIG. 30, Remove and rearrange. That is, starting from the lowest i, the P (i) entries are shifted to the left to fill the position of the removed null symbol (Starting with the lowest i, shift the P (i) entries to the left to fill the empty entry locations. And outputs the symbols of the aligned interleaving pattern P (i) to the symbol-to-byte converter 515 in order.

The symbol-to-byte converter 515 converts the mobile service data symbols, which have been rearranged and reordered in the symbol interleaver 514, into bytes and outputs the converted bytes to the SCCC block-MH block converter 516. The SCCC block-MH block converter 516 converts the symbol-interleaved SCCC block into an M / H block and outputs the block to the group formatter 303.

If the SCCC block mode is 00, the SCCC block is mapped 1: 1 to each M / H block in the data group. As another example, if the SCCC block mode is 01, the SCCC block is mapped to two corresponding M / H blocks in the data group. For example, the SCCC block SCB1 corresponds to (B1, B6), the SCB2 corresponds to (B2, B7), the SCB3 corresponds to (B3, B8), the SCB4 corresponds to (B4, B9) Lt; / RTI &gt; The M / H block output from the SCCC block-MH block converter 516 includes mobile service data and FEC redundancy. In the present invention, not only the mobile service data of the M / H block but also the redundancy of the FEC is also considered as the mobile service data.

Group formatter

The group formatter 303 inserts the data of the M / H block output from the block processor 302 into a corresponding M / H block in a data group formed according to a predefined rule, Various position holders and known data (or known data location holders) are also inserted into the corresponding areas in the data group.

That is, in the group formatter 303, in addition to the encoded mobile service data output from the block processor 302, as shown in FIG. 5, an MPEG header position holder, an unstructured RS parity position holder, Insert the main service data location holder into the corresponding area of the data group. The reason for inserting the main service data location holder is that the mobile service data and the main service data are intermixed with each other in the areas B to D based on the data interleaving as shown in FIG. For example, the position holder for the MPEG header may be allocated in front of each packet when viewed from the output data after the data deinterleaving. Dummy bytes may also be inserted to form the intended group format. In addition, the group formatter 303 inserts the initialization data (i.e., the trellis initialization byte) of the Trellis Encoding Module 256 into the corresponding area. In one embodiment, the initialization data may be inserted before the known data sequence. The initialization data is used to initialize the memory in the trellis encoder 256, and is not transmitted to the receiving system.

Also, in the group formatter 303, the signaling information encoded and output by the signaling encoder 304 may be inserted into a corresponding area of the data group.

At this time, the signaling information may be referred to when each data and position holder is inserted into the data group in the group formatter 303. [ The process of encoding the signaling information and inserting it into the data group will be described later in detail.

The group formatter 303 inserts various data and position holders into corresponding areas of the data group, then deinterleaves the data in the data group and the position holder in the reverse process of data interleaving, and outputs the deinterleaved data to the packet formatter 305 . The group formatter 303 may include a group format organizer 527 and a data deinterleaver 529 as shown in FIG. The group formatting unit 527 inserts data and position holders into the corresponding area in the data group as described above, and the data deinterleaver 529 deinterleaves the data group and the position holder in the reverse process of data interleaving .

The packet formatter 305 removes the main service data location holder and the RS parity location holder, which were allocated for deinterleaving from the deinterleaved data, collects the remaining parts, and then stores the null packet And inserts an MPEG header having a PID (or a PID not used in the main service data packet). And adds sync bytes to the beginning of each 187-byte data packet.

The packet formatter 305 may insert the known known data into the known data location holder when the known data location holder is inserted in the group formatter 303 or may insert the known data location holder It can be output without adjustment.

Then, the packet formatter 305 divides the data in the packet formatted data group into 188-byte mobile service data packets (i.e., MPEG TS packets), and provides the packet data to the packet multiplexer 240.

The packet multiplexer 240 multiplexes the main service data packet output from the packet jitter separator 220 and the data group output by the packet formatter 305 under the control of the control unit 201, (Post-Processor) 250 to the data renderer 251. That is, the control unit 201 controls time multiplexing of the packet multiplexer 240. If the packet multiplexer 240 receives 118 mobile service data packets from the packet formatter 305, 37 of the 118 mobile service data packets are placed before the VSB field sync insertion location, 81 mobile service data packet is placed after the VSB field sync insertion position. The multiplexing method can be adjusted by various parameters of the system design. The multiplexing method and the multiplexing rule in the packet multiplexer 240 will be described later in detail.

Since the data group including the mobile service data is multiplexed (or allocated) between the main service data in the packet multiplexing process, the temporal location of the main service data packet is relatively moved. However, in a system target decoder (i.e., an MPEG decoder) for processing main service data of the receiving system, only the main service data is received and decoded, and the mobile service data packet is recognized as a null data packet.

Therefore, packet jitter occurs when the system target decoder of the receiving system receives the main service data packet multiplexed with the data group.

At this time, since the system target decoder has buffers of various stages for video data and its size is considerably large, the packet jitter generated in the packet multiplexer 240 is not a big problem in the case of video data. However, the size of the buffer for the audio data in the system target decoder may be a problem because it is small.

That is, due to the packet jitter, an overflow or an underflow may occur in a buffer for a main service data of the receiving system, for example, a buffer for audio data.

Therefore, the packet jitter buffer 220 resets the relative position of the main service data packet so that overflow or underflow does not occur in the buffer of the system target decoder.

Embodiments for rearranging the positions of the audio data packets of the main service data in order to minimize the influence on the operation of the audio buffer will be described. The packet jitter rewinders 220 rearrange the audio data packets in the main service data interval so that the audio data packets of the main service can be located as uniformly as possible.

Also, if the position of the main service data packet is relocated relatively, the PCR (Program Clock Reference) value should be corrected accordingly. The PCR value is inserted into a specific area of the TS packet as a time reference value for matching the time of the MPEG decoder and transmitted. The packet jitter decimator 220 may also perform the PCR value correction.

The output of the packet jitter separator 220 is input to a packet multiplexer 240. The packet multiplexer 240 multiplexes the main service data packet output from the packet jitter separator 220 and the mobile service data packet output from the preprocessor 230 according to a predetermined multiplexing rule, To the data renderer 251 of the memory 250.

If the input data is a main service data packet, the data renderer 251 performs the same rendering as the existing renderer. In other words, the synchronous bytes in the main service data packet are discarded and the remaining 187 bytes are randomized using internally generated pseudo random bytes, and then output to the RS encoder / unscrambler RS encoder 252.

However, if the input data is a mobile service data packet, only a part of the packet may be rendered. For example, if it is assumed that the preprocessor 230 performs randomization on the mobile service data, the data renderer 251 extracts a synchronization byte among 4-byte MPEG headers included in the mobile service data packet And performs the randomization only for the remaining 3 bytes, and outputs the result to the RS encoder / unscrambler RS encoder 252. That is, the mobile service data excluding the MPEG header are not subjected to rendering, and are output to the RS encoder / unscrambler RS encoder 252. The data renderer 251 may or may not render the known data (or known data location holder) and initialization data included in the mobile service data packet.

The RS encoder / unscrambler RS encoder 252 performs RS encoding on the data to be rendered or bypassed by the data randomizer 251, adds 20 bytes of RS parity, and then transmits the data to the data interleaver 253, . In this case, when the input data is the main service data packet, the RS encoder / unscrambler RS encoder 252 performs systematic RS encoding in the same manner as in the existing broadcasting system to add 20 bytes of RS parity after 187 bytes of data. If the mobile service data packet is a non-systematic RS encoding, the 20-byte RS parity obtained at this time is inserted into a predetermined parity byte position in the packet.

The data interleaver 253 is a convolutional interleaver on a byte basis.

The output of the data interleaver 253 is input to a parity substitution unit 254 and an unstructured RS encoder 255.

On the other hand, in order to convert the output data of the trellis encoder 256 located at the rear end of the parity substitution unit 254 into known data defined by an appointment at the transmitting / receiving end, initialization of the memory in the trellis encoder 256 . That is, the memory of the trellis encoder 256 must be initialized before the inputted known data sequence is Trellis encoded.

At this time, the beginning of the inputted known data sequence is not the actual known data but the initialization data inserted in the group formatter in the preprocessor 230. Therefore, it is necessary to replace the memory value in the trellis coder 256 with the corresponding initialization data immediately before the input known data sequence is Trellis coded.

In other words, the initialization data is replaced with a memory value in the trellis encoding unit 256 and input to the trellis encoding unit 256. At this time, the memory value for replacing the initialization data is calculated and excluded from the memory value in the trellis encoding unit 256 and input to the corresponding memory. Therefore, the corresponding memory is initialized to zero. Also, it is necessary to recalculate the RS parity with the memory value replacing the initialization data, and replace the RS parity with the RS parity output from the data interleaver 253.

Therefore, the non-systematic RS encoder 255 receives the mobile service data packet including the initialization data from the data interleaver 253 and receives the memory value from the trellis encoder 256. Then, the initialization data among the input mobile service data packets is replaced with a memory value, and the RS parity data added to the mobile service data packet is removed, followed by unstructured RS coding. And outputs the RS parity obtained by the non-systematic RS encoding to the parity substitution unit 255. The parity substitution unit 255 selects the output of the data interleaver 253 in the mobile service data packet and the output of the unstructured RS encoder 255 in the RS parity and outputs it to the trellis encoding unit 256. [ .

Meanwhile, when the main service data packet is input or the mobile service data packet including no initialization data is inputted, the parity substitution unit 254 selects the data and RS parity output from the data interleaver 253 and performs trellis encoding (256).

The trellis encoder 256 converts the data in units of bytes output from the parity substitution unit 254 on a symbol-by-symbol basis, performs 12-way interleaving on the data, and outputs the trellis-encoded data to the synchronous multiplexer 260.

32 is a detailed diagram of one trellis coder of the 12 trellis coders in the trellis coder 256. Fig. The trellis encoder may include two multiplexers 531, 541, two exclusive OR gates 532, 543, and three memories 533, 542, 544.

That is, the first to third memories 533, 542 and 544 are initialized by the memory value output in place of the initialization data in the parity substitution unit 254. In other words, when the first symbol (i.e., two bits) converted from the initialization data (i.e., each trellis initialization data byte) is input, the input bits of the trellis encoder are input to the trellis encoder The memory values are replaced by the memory values (see Figure 32), and the trellis encoders are replaced by the trellis encoders, as shown in Figure 32 ).

And since the two symbols (i.e., four bits) are required for the trellis initialization, the last two symbols of the trellis initialization data bytes are not used for the trellis initialization and are treated as symbols of known data bytes Since 2 symbols (4 bits) are required for trellis initialization, the last 2 symbols (4 bits) from trellis initialization bytes are not used for trellis initialization.

When the trellis encoder of FIG. 32 is in the initialization mode, the input of the trellis encoder comes from the internal trellis encoder instead of the output (X2X1) of the parity permutator 254 the parity of the parity replacer. In the normal mode, the trellis encoder receives the input symbol X2X1 from the parity substitution unit 254 and processes the input symbol X2X1. ). The trellis encoder provides the input data changed for the trellis initialization to the non-systematic RS encoder 255 (the trellis encoder provides the modified input data for the non-systematic RS encoder 255).

That is, when the selection signal indicates the normal mode, the first multiplexer 531 selects the upper bit X2 of the input symbol. When the initialization mode is indicated, the first multiplexer 531 outputs the output of the first memory 533 And outputs it to the first exclusive OR gate 532. The first exclusive OR gate 532 performs an exclusive OR operation on the output of the first multiplexer 531 and the output of the first memory 533 and outputs the result to the first memory 533, do. The first memory 533 delays the output data of the first exclusive OR gate 532 by one clock and then outputs the delayed data to the first multiplexer 531 and the first exclusive OR gate 532. Meanwhile, the second multiplexer 541 selects the lower bit X1 of the input symbol when the selection signal indicates the normal mode, and outputs the output of the second memory 542 when the selection signal indicates the initialization mode And outputs it to the second exclusive OR gate 543 and outputs it to the lower bit Z1. The second exclusive OR gate 543 performs an exclusive OR operation on the output of the second multiplexer 541 and the output of the second memory 542 and outputs the result to the third memory 544. The third memory 544 delays the output of the second exclusive OR gate 543 by one clock and then outputs the result to the second memory 542 and outputs the least significant bit Z0. The second memory 542 delays the output of the third memory 544 by one clock and outputs the result to the second exclusive OR gate 543 and the second multiplexer 541.

The select signal indicates an initialization mode during the first two symbols converted from the initialization data byte.

For example, if the select signal indicates an initialization mode, the first exclusive OR gate 532 may compare the value of the first memory 533 provided via the first multiplexer 531 with the value of the first memory 533 directly in the first memory 533. [ Perform the exclusive-OR operation on the provided memory value. That is, two identical bits are received and an exclusive-OR operation is performed. In general, an exclusive OR gate will produce a result of 1 if only one of the two bits of the operand is 1, and 0 otherwise. Therefore, if the value of the first memory 533 is subjected to the exclusive-OR operation, the result is always zero. Since the output of the first exclusive OR gate 532, that is, 0 is input to the first memory 533, the first memory 533 is initialized to zero.

Likewise, if the select signal indicates an initialization mode, the second exclusive OR gate 543 is coupled to the value of the second memory 542 provided through the first multiplexer 541 and the value of the second memory 542 provided directly in the second memory 542 Exclusive-OR operation of the memory value. therefore. The output of the second exclusive OR gate 543 is always zero. Since the output of the second exclusive OR gate 543, i.e., 0, is input to the third memory 544, the third memory 544 is also initialized to zero. The output of the third memory 544 is input to the second memory 542 at the next clock to initialize the second memory 542 to zero. At this time, the selection signal also indicates the initialization mode.

That is, when the first symbol converted from the initialization data byte is replaced with the values of the first and second memories 533 and 542 and input to the trellis encoder, the first and third memories 533 and 544 in the trellis encoder are initialized to 00 do. When the second symbol is replaced with the first and second memories 533 and 542 and input to the trellis encoder, the first, second and third memories 533, 542 and 544 in the trellis encoder are initialized to 000. Thus, two symbols are needed to initialize the memory of the trellis encoder. At this time, the output bits (X2'X1 ') of the first and second memories 533 and 542 are input to the unstructured RS encoder 255 for new RS parity calculation while the selection signal indicates the initialization mode.

The synchronous multiplexer 260 inserts field synchronization and segment synchronization into the output of the trellis encoder 256 and outputs it to the pilot inserter 271 of the transmitter 270.

The pilot inserted data in the pilot inserter 271 is modulated by a modulator 272 in a predetermined modulation scheme, for example, a VSB scheme, and then transmitted to each reception system through an RF up-converter 273. [

The multiplexing method of the packet multiplexer 240

That is, the data of the error correction coding and 1 / H encoded primary RS frame (i.e., the RS frame mode is 00) or the primary / secondary RS frame (i.e., the RS frame mode 01) And is allocated to at least one area of the A to D areas of each data group, or is allocated to at least one M / H block among the M / H blocks B1 to B10 and deinterleaved. The deinterleaved data group is multiplexed in the packet multiplexer 240 through the packet formatter 305 according to the main service data and the predetermined multiplexing rule.

The packet multiplexer 240 multiplexes and outputs a plurality of consecutive data groups in a subframe as far as possible. For example, assuming that three data groups are multiplexed and transmitted in one subframe, the three data groups are divided into a first slot (Slot # 0), a fifth slot (Slot # 4) Slots (Slot # 8) sequentially.

Like the assignment of the data group, the parades are multiplexed and outputted so as to be far apart from each other in the subframe. The method of allocating the data group and the parade may be applied differently for each M / H frame based on the M / H frame, and the same applies to all subframes within one M / H frame.

FIG. 10 shows an embodiment in which a single parade with three data groups included in one subframe is allocated to one M / H frame by the packet multiplexer 240. FIG. Referring to FIG. 10, when three data groups are sequentially allocated in a 4-slot period in one subframe and this process is performed on 5 subframes in the corresponding M / H frame, 15 Data group is allocated. Here, the 15 data groups are data groups included in one parade.

As shown in FIG. 10, when data groups for one parade are allocated to M / H frames, the packet multiplexer 240 may allocate main service data between data groups and data groups, Groups may be assigned. That is, the packet multiplexer 240 may allocate data groups for a plurality of parades to one M / H frame.

Basically, the method of assigning data groups to multiple parades is not different from that of a single parade. That is, the packet multiplexer 240 allocates data groups in other parades allocated to one M / H frame in a 4-slot period.

At this time, the data group of another parade may be allocated in a circular manner from a slot to which the data group of the previous parade is not allocated.

For example, assuming that the allocation of data groups for one parade is performed as shown in FIG. 10, the data group for the next parade can be allocated from the 12th slot in one subframe.

11 shows an example in which the packet multiplexer 240 allocates and transmits three parades (Parade # 0, Parade # 1, and Parade # 2) to one M / H frame.

For example, assuming that the first parade (Parade # 0) includes three data groups per subframe, the packet multiplexer 240 assigns 0 to 2 to the i value of Equation (1) The positions of the data groups can be obtained. That is, the data groups of the first parade are sequentially allocated and output to the first, fifth, and ninth slots (Slot # 0, Slot # 4, Slot # 8) in the subframe.

Assuming that the second parade (Parade # 1) includes two data groups per subframe, the packet multiplexer 240 substitutes 3 to 4 in the i value of Equation (1) Can be obtained. That is, the data groups of the second parade are sequentially allocated and output to the second and twelfth slots (Slot # 1, Slot # 11) in the subframe.

If the third parade (Parade # 2) includes two groups per subframe, the packet multiplexer 240 assigns 5 to 6 to the i value of Equation (1) Can be obtained. That is, the data groups of the third parade are sequentially allocated and output to the seventh and eleventh slots (Slot # 6, Slot # 10) in the subframe.

As described above, the packet multiplexer 240 can multiplex and output data groups for a plurality of parades in one M / H frame. The multiplexing of data groups in one subframe has a group space of four slots, To the right. Therefore, the number of data groups within one parade, which can be multiplexed in one subframe, can be any one of integers from 1 to 8. At this time, one M / H frame includes five subframes, which means that the number of data groups of one parade that can be multiplexed in one M / H frame is any one of multiples of 5 from 5 to 40 .

Signaling information processing

The present invention is an embodiment in which a signaling information area for inserting signaling information is allocated to a certain area within each data group.

33 shows an example in which a signaling information area for inserting signaling information is allocated from the first segment to the second segment of the M / H block B4 in the data group. That is, 276 (= 207 + 69) bytes of the M / H block B4 of each data group are allocated as areas for inserting signaling information. In other words, the signaling information area is composed of 207 bytes, which is the first segment of the M / H block B4, and the first 69 bytes of the second segment. For example, the first segment of the M / H block B4 corresponds to the 17th or 173rd segment of the VSB field.

The signaling information to be inserted into the signaling information area is FEC-coded by the signaling coder 304 and input to the group formatter 303. The signaling information may include a transmission parameter that is inserted into the payload area of the OM packet and received by the demultiplexer 210.

In the group formatter 303, the signaling encoder 304 inserts FEC-coded signaling information into the signaling information area in the data group.

The signaling information can be divided into two types of signaling channels. One is a Transmission Parameter Channel (TPC), and the other is a Fast Information Channel (FIC) described in Figs.

The TPC data is signaling information including transmission parameters such as RS frame information, RS coding information, FIC information, data group information, SCCC information, and M / H frame information. The TPC data is merely an example for facilitating understanding of the present invention, and addition and deletion of signaling information included in the TPC can be easily changed by those skilled in the art, so the present invention is not limited to the above embodiments.

The FIC data is provided to allow fast service acquisition at the receiver as shown in FIG. 11 to FIG. 13, and includes cross layer information between the physical layer and the upper layer (The FIC is provided to enable The fast service acquisition of receivers and it contains cross layer information between the physical layer and the upper layer (s).

FIG. 34 is a detailed block diagram illustrating an embodiment of a signaling encoder 304. FIG.

The signaling encoder 304 includes a TPC encoder 561, an FIC encoder 562, a block interleaver 563, a multiplexer 564, a signaling randomizer 565, and an Iterative Turbo Encoder 566 ).

The TPC encoder 561 receives 10-byte TPC data and performs (18,10) -RS encoding to add 8-byte parity data to 10-byte TPC data. The RS-encoded 18-byte TPC data is output to a multiplexer 564. [

The FIC encoder 562 receives 37 bytes of FIC data and performs (51, 37) -RS encoding to add 14 bytes of parity data to 37 bytes of FIC data. The RS-encoded 51-byte FIC data is input to the block interleaver 563 and interleaved in units of a predetermined block. For example, the block interleaver 563 is a variable-length block interleaver and interleaves the FIC data in each subframe RS-coded and input, in units of TNoG (column) x 51 (row) blocks, do. Here, the TNoG is the total number of data groups allocated to one subframe. The block interleaver 563 is synchronized with the first FIC data of each subframe.

The block interleaver 563 writes the 51-byte RS code word in left-to-right, top-down, row-by-column, top-down, left-to-right, and 51-byte units write the incoming RS codewords of 51 bytes Row-by-row from left to right and top-to-bottom and shall output the data in units of 51 bytes by column column top-to-bottom and left-to-right ).

The multiplexer 564 multiplexes RS-encoded TPC data in the TPC encoder 561 and FIC data interleaved in the block interleaver 563 on the time axis, and multiplexes the multiplexed 69-byte data into a signaling randomizer 565, .

The signaling randomizer 565 randomizes the multiplexed data and outputs the randomized data to the regression turbo encoder 566. The signaling randomizer 565 may use the generated polynomial of the randomizer for mobile service data as it is. Also, initialization occurs every data group.

The recursive turbo encoder 566 is an inner encoder for performing recursive turbo encoding on the randomized data, that is, the signaling information data in the PCCC scheme. The regression-based turbo encoder 566 may be composed of six odbcontainers and six odd-component encoders.

35 is a diagram showing a syntax structure of TPC data input to the TPC encoder 561. Referring to FIG. The TPC data is inserted into the signaling information area of each data group and transmitted.

The TPC data includes at least one of a Sub-Frame number field, a Slot_number field, a Parade_id field, a starting_Group_number field, a number_of_Group field, a Parade_repetition_cycle field, an RS_Frame_mode field, an RS_code_mode_primary field, an RS_code_mode_secondary field, an SC_CC_Block_mode field, an SCCC_outer_code_mode_A field, An SCCC_outer_code_mode_C field, an SCCC_outer_code_mode_D field, a FIC_version field, a Parade_continuity_counter field, a TNoG field, and the like.

The Sub-frame_number field indicates the number of current subframes in the M / H frame, and is transmitted for M / H frame synchronization. The Sub-frame_number field value may have a value between 0 and 4. (The Sub-Frame_number field shall be the current sub-frame number within the M / H Frame, which is transmitted for M / H Frame synchronization. shall range from 0 to 4).

The Slot_number field indicates the number of current slots in the corresponding subframe and is transmitted for M / H frame synchronization. The Slot_number field value may have a value between 0 and 15. (The Slot_number field is the current Slot number within the Sub-Frame, which is transmitted for M / H Frame synchronization.

The Parade_id field indicates an identifier for identifying a parade to which the data group belongs. The Parade_id field value can be expressed by 7 bits. In a M / H transmission, each parade has a unique Parade_id (Parade_id field identifies the Parade to which this Group belongs. The value of this field may be any 7-bit value. a unique Parade_id). At this time, the communication of the Parade_id between the physical layer and the upper layer is performed by the Ensemble_id formed by adding one bit to the left of the Parade_id (the communication layer of the physical layer and the management layer is formed by an ensemble_id formed by adding one bit to the left of the Parade_id). The Ensemble_id for distinguishing the primary ensemble transmitted through the parade is formed by marking 0 in the added MSB, and the Ensemble_id for distinguishing the secondary ensemble can be formed by displaying 1 in the added MSB (If The MSB shall be '0'. Otherwise, the MSB shall be '1').

The SGN field indicates the first slot number for the parade to which the data group belongs. (The starting_group_number (SGN) field shall be the first slot number for a Parade to which this Group belongs, as determined by Equation 1 For all preceding Parades have been calculated.) The SGN and NoG fields are used to obtain the slot number assigned to one parade in the corresponding subframe by applying Equation (1).

The NoG field indicates the number of groups assigned to the parade to which the data group belongs. (The number_of_Groups (NoG) field shall indicate the number of groups in a sub-frame assigned to the Parade. eg, NoG = 0 implies that one Group is allocated to this Parade in a Sub-Frame). The NoG field value may have a value between 0 and 7. The slot numbers assigned to the corresponding parade can be calculated from SGN and NoG using Equation (1).

The PRC field indicates the repetition period of the parade transmitted in units of M / H frames as shown in Table 12 below (The Parade_repetition_cycle (PRC) field shall be the parade is transmitted, minus 1, of M / H Frames, as described in Table 12).

[Table 12]

PRC Description 000 This Parade shall be transmitted once every MH Frame. 001 This Parade shall be transmitted once every 2 MH Frames. 010 This Parade shall be transmitted once every 3 MH Frames. 011 This Parade shall be transmitted once every 4 MH Frames. 100 This Parade shall be transmitted every 5 MH Frames. 101 This Parade shall be transmitted once every 6 MH Frames. 110 This Parade shall be transmitted every 7 MH Frames. 111 Reserved

For example, if the PRC field value is 001, the parade is transmitted once every 2 M / H frames.

The RS_Frame_mode field indicates whether one RS frame or two RS frames are transmitted in one parade, and is defined as shown in Table 1.

The RS_code_mode_primary field indicates an RS code mode for the primary RS frame, and may be defined as shown in Table 6.

The RS_code_mode_secondary field indicates the RS code mode for the secondary RS frame, and may be defined as shown in Table 6. [

The SCCC_Block_mode indicates how the M / H blocks in the data group are allocated to the SCCC block, and can be defined as shown in Table 7.

The SCCC_outer_code_mode_A field indicates the SCCC outer code mode for the area A in the data group, and can be defined as shown in Table 8.

The SCCC_outer_code_mode_B field indicates the SCCC outer code mode for the area B in the data group.

The SCCC_outer_code_mode_C field indicates the SCCC outer code mode for the area C in the data group.

The SCCC_outer_code_mode_D field indicates the SCCC outer code mode for the area D in the data group.

The FIC_version field indicates the version of the FIC data.

The Parade_continuity_counter field is incremented from 0 to 15, and increases by 1 for each (PRC + 1) M / H frame. For example, if PRC = 011, the Parade_continuity_counter field is incremented every fourth M / H frame.

The TNoG field indicates the total number of data groups allocated in one subframe.

The information included in the TPC data is only an example for facilitating understanding of the present invention. Addition and deletion of information included in the TPC data can be easily changed by those skilled in the art. I will not.

At this time, the TPC data (except for the Sub-Frame_number field and the Slot_number field) for each parade are not changed during one M / H frame. The same information is repeatedly transmitted through all the data groups in the parade during one M / H frame. By doing so, reception of TPC data becomes extremely robust, and reception performance can be enhanced. Since the Sub-Frame_number field and the Slot_number field value are incrementing counter values, the fields are robust due to the transmission of the expected values. (For Sub-Frame_number and Slot_number) for each Parade do Because the Sub-Tx data is transmitted to the M / H frame, the M / H frame is the same as the M / H frame, and the same information is transmitted repeatedly through the M / Frame_number and the Slot_number are increasing counter values, and they are also robust due to the transmission of regularly expected values.

36 is a diagram showing an example of a transmission scenario of TPC data and FIC data. The Sub-Frame_number, Slot_number, Parade_id, Parade_repetition_cycle, and Parade_continuity_counter information in FIG. 35 have their values corresponding to the current M / H frame through five subframes in a specific M / H frame (Sub-Frame_number, Slot_number, Parade_id , Parade_repetition_cycle, and Parade_continuity_counter shall have their values corresponding to the current M / H Frame throughout the 5 Sub-Frames within a particular M / H Frame). Some of the TPC data and the FIC data are signaled in advance.

The SGN, NoG, and all FEC modes have values corresponding to the current M / H frame in the first two subframes. The SGN, NoG, and all FEC modes have values corresponding to the M / H frame in which the next parade appears through the third, fourth, and fifth subframes of the current M / H frame. By doing so, the receiver can obtain reliable transmission parameters in advance (SGN, NoG and all FEC modes shall have values corresponding to the current M / H frame in the first two sub-frames. values corresponding to the Frame in which the Parade is next appearing throughout the 3 ^rd , 4 ^th and 5 ^th Sub-Frames of the current M / H Frame. This enables the M / H receivers to obtain the transmission parameters in advance very reliably.

 For example, if Parade_repetition_cycle = '000', the values of the third, fourth and fifth subframes of the current M / H frame correspond to the next M / H frame. If Parade_repetition_cycle = '011', the values of the third, fourth and fifth subframes of the current M / H frame correspond to the fourth and subsequent M / H frames.

The FIC_version and FIC_data have values applied to the current M / H frame during the first and second subframes of the current M / H frame. In addition, the FIC_version and FIC_data have values applied to the next M / H frame during the third, fourth and fifth subframes of the current M / H frame (FIC_version and FIC_data) the 1 ^st Sub-Frame and the 2 ^nd Sub-Frame, and they shall have values corresponding to the immediately following M / H Frame during the 3 ^rd , 4 ^th and 5 ^th Sub-Frames of the current M / H Frame.).

On the other hand, in the receiving system, power is turned on only in a period in which a desired parade data group is allocated, and power is turned off in other intervals, thereby reducing power consumption of the receiving system. This feature is particularly useful in portable receivers where power consumption is low. For example, assume that data groups of a first parade with NOG of 3, a second parade with NOG of 2, and a third parade of NOG of 2 are allocated to one M / H frame as shown in FIG. And the user selects a mobile service included in the first parade through a remote control or a keypad provided in the terminal. In this case, as shown in FIG. 37, the receiving system can reduce the power consumption by turning on the power in the slot to which the data group of the first parade is allocated and turning off the power in the remaining slots. At this time, it is necessary to turn on the power slightly earlier than the slot to which the actual data group to be received is allocated, so that the tuner or the demodulator converges in advance.

Base data ( known data or training signal Area allocation

The transmission system inserts a training sequence of a long and regular length into each data group. Each data group includes 6 training sequences as an embodiment. The training sequences are specified prior to trellis encoding. The training sequence is Trellis coded, and the Trellis coded sequences are known data sequences. This is because the memories of the trellis encoder are initialized according to preset values at the start position of each sequence. FIG. 38 shows an example of insertion of six training sequences at the byte level before Trellis coding. 38 is an example of the arrangement of the training sequence performed in the group formatter 303. Fig.

The first training sequence is inserted into the last two segments of the M / H block B3. A second training sequence is inserted into the second and third segments of M / H block B4. The second training sequence is next to the signaling information area as in FIG. The third to sixth training sequences are inserted into the last two segments of the M / H blocks B4, B5, B6 and B7, respectively.

As in FIG. 38, the first, third, and sixth training sequences are separated by 16 segments. In Figure 38, a dotted area indicates a trellis data byte, and a lined area indicates a training data byte. And the white area indicates other data such as FEC encoded mobile service data bytes or dummy data bytes.

FIG. 39 shows an example of inserting training sequences at symbol level after being trellis coded by a trellis encoder. In Fig. 39, the dotted area indicates the segment sync symbol, and the striated area indicates the training data symbols. And the white region may comprise FEC encoded mobile service data symbols, FEC encoded signaling data symbols, main service data symbols, RS parity data symbols, dummy data symbols, trellis initialization symbols, and / Such as data symbols.

After the trellis coding, the last 1416 (= 588 + 828) symbols of the first, third, fourth, fifth, and sixth training sequences may have the same data pattern.

The second training sequence may have a first 528-symbol sequence and a second 528-symbol sequence, both sequences being the same pattern. That is, the 528-symbol sequence is repeated after the 4-symbol data segment sync signal. At the end of each training sequence, the memory values of the twelve trellis encoders are reset to zero.

Receiving system

40 is a configuration block diagram of a receiving system according to an embodiment of the present invention.

The reception system according to the present invention includes a tuner 2001, an operation controller 2000, a demodulator 2002, an equalizer 2003, a known data detector 2004, a block decoder 2005, an RS frame decoder 2006, 1 packet converter 2007, and an A / V decoder 2015, as shown in FIG. The receiving system may further include a main service data processing unit 2008. The main service data processing unit may include a data deinterleaver, an RS decoder, and a data derandomizer. The receiving system may further include a signaling decoding unit 2013 and a second packet converting unit 2014. The receiving system may further include a power controller 5000 that controls power supply of some elements of the receiving system.

The tuner 2001 tunes the frequency of a specific channel through an antenna, a cable, or a satellite and downconverts the signal to an intermediate frequency (IF) signal, and outputs the down-converted signal to a demodulator 2002 and a known data detector 2004. Data received at the frequency of the specific channel includes main service data, mobile service data, program table information data for decoding the main service data and mobile service data, and transmission parameters.

At this time, the down-converted data is input to a demodulator 2002 and a known data detector 2004 through an analog / digital converter (ADC) (not shown) for converting an analog IF signal of a pass band into a digital IF signal As an embodiment.

The demodulator 2002 performs automatic gain control, carrier recovery, and timing recovery on a digital IF signal of an input passband to generate a baseband signal, and outputs the baseband signal to an equalizer 2003 and a known data detector 2004 .

The equalizer 2003 compensates for the distortion on the channel included in the demodulated signal, and outputs the compensated signal to the block decoder 2005.

At this time, the known data detector 2004 detects the known data positions inserted from the transmitting side from the input / output data of the demodulator 2002, that is, the data before demodulation or the demodulated data, The equalizer 2003, the signaling decoder 2013, and the operation controller 2000. The operation of the demodulator 2002, the equalizer 2003, the signaling decoder 2013, Also, the known data detector 2004 transmits information for further coding the mobile service data that has been further encoded and the main service data that has not undergone the additional coding to the block decoder 2005, .

40, the information detected by the known data detector 2004 may be used entirely in the receiving system, and may be used in the RS frame decoder 2006 or the like.

Data demodulated in the demodulator 2002 or channel equalized data in the equalizer 2003 are also input to the signaling decoding unit 2013. [ The known data position information detected by the known data detector 2004 is also input to the signaling decoding unit 2013. [

The signaling decoding unit 2013 extracts and decodes the signaling information (for example, TPC information) inserted and transmitted from the transmitting side from the input data, and provides the decoded signaling information as a necessary block.

That is, the signaling decoder 2013 extracts and decodes the TPC data and FIC data inserted and transmitted from the equalized data from the equalized data, and then the TPC data is transmitted to the operation controller 200, the known data detector 2004, To the controller 5000, and the FIC data is output to the second packet converter 2014. For example, the TPC data and the FIC data are inserted and received in the signaling information area of each data group.

The signaling decoder 2013 performs signaling decoding in the reverse process of the signaling encoder of FIG. 34 to extract TPC data and FIC data. For example, input data is decoded by the PCCC method, derandomized, and then separated into TPC data and FIC data. At this time, RS decoding is performed on the separated TPC data to correct errors generated in the TPC. Then, after performing deinterleaving on the separated FIC data, RS decoding is performed to correct errors generated in the FIC data. The error-corrected TPC data is output to an operation controller 2000, a known data detector 2004, and a power controller 5000. The error-corrected FIC data is output to the second packet converter 2014.

The TPC data may include a transmission parameter that is inserted into the payload area of the OM packet by the service multiplexer 100 and transmitted to the transmitter 200.

Here, the TPC data may include RS frame information, SCCC information, M / H frame information, and the like, as shown in FIG. The RS frame information may include RS frame mode information and RS code mode information. The SCCC information may include SCCC block mode information and SCCC outer code mode information. The M / H frame information may include M / H frame index information. The TPC data may include subframe count information, slot count information, parade_id information, SGN information, NOG information, and the like.

At this time, if the known data information output from the known data detector 2004 is used, the signaling information area in the data group can be known. That is, a first known data sequence (or a training sequence) is inserted into the last two segments of the M / H block B3 in the data group, and the second known data sequence is inserted into the second and third blocks of the M / H block B4 Th segment. Since the second known data sequence is inserted after the signaling information area, the signaling decoding unit 2013 extracts the signaling information of the signaling information area from the data output from the demodulator 2002 or the channel equalizer 2003 It is possible to decode it.

The power controller 5000 receives M / H frame related information from the signaling decoding unit 2013 and controls the power of a tuner, a demodulator, and the like. The power controller 5000 may receive power control information from the operation controller 2000 to control the power of the tuner, the demodulator, and the like.

The power controller 5000 may turn on power in a slot to which a data group of a parade including a mobile service desired by the user is allocated to receive data and turn off the power in the other slot.

For example, assume that the first parade with NOG of 3, the second parade with NOG of 2, and the third parade of NOG with 2 are allocated to one M / H frame as shown in FIG. And the user selects a mobile service included in the first parade through a remote control or a keypad provided in the terminal. In this case, the power controller 5000 can reduce the power consumption by turning on the power in the slot to which the data group of the first parade is allocated and turning off the power in the remaining period as shown in FIG. At this time, it is necessary to turn on the power slightly earlier than the slot to which the actual data group to be received is allocated, so that the tuner or the demodulator converges in advance.

The demodulator 2002 can improve the demodulation performance by using the known data symbol sequence in timing recovery or carrier recovery, and can improve the equalization performance by using the known data in the equalizer 2003 as well . Also, the decoding result of the block decoder 2005 may be fed back to the equalizer 2003 to improve the equalization performance.

Demodulator and base data detector

At this time, the receiving system can receive a data frame (or VSB frame) including a data group in which a known data sequence is periodically inserted, as shown in FIG. As shown in FIG. 5, the data group is divided into A to D regions, and the A region includes M / H block B4 to M / H block B7, the B region includes M / H block B3 and M / H block B8, An M / H block B2 and an M / H block B9, and a D area, an M / H block B1 and an M / H block B10.

As shown in FIGS. 38 and 39, the known data sequence in which the known data sequence is periodically inserted includes the known pattern data sequence of the same pattern. The known data sequence of the same pattern and the entire known data sequence of the known data section may be the same , May be different. In other cases, the entire known data sequence is longer than the known data sequence of the same pattern, and the known data sequence of the same pattern is included in the entire known data sequence.

When the known data is periodically inserted between the mobile service data, the channel equalizer of the receiving system can use the known data as a training sequence to be used as an accurate discrimination value. In another embodiment, the channel equalizer may use the known data to estimate the impulse response of the channel. In another embodiment, the channel equalizer may use the known data to update filter coefficients (i.e., equalization filters).

On the other hand, when known data of the same pattern is periodically inserted, each known data interval can be used as a guard interval in the channel equalizer according to the present invention. The guard interval serves to prevent interference between blocks caused by the multipath channel. This is because the base data behind the mobile service data interval (i.e., the data block) may be considered to have been copied before the mobile service data interval.

This structure is also referred to as a cyclic prefix, and this structure allows circular convolution of the impulse response of the data block and the channel transmitted in the transmission system in the time domain. Therefore, it is easy to perform channel equalization in the frequency domain using FFT (Fast Fourier Transform) and IFFT (Inverse FFT) in the channel equalizer of the receiving system.

That is, since the data block received in the receiving system is expressed by a product of a data block and a channel impulse response (CIR) in the frequency domain, channel equalization is performed by multiplying the inverse of the channel in the frequency domain during channel equalization, It is possible.

In the known data detector 2004, the known data offset can be estimated in the known data detection process while detecting the known data location inserted periodically. In this case, the demodulator 2002 can more accurately estimate and compensate the carrier frequency offset from the known data position information and the initial frequency offset estimation value.

On the other hand, when the known data is transmitted in the structure as shown in FIG. 5, the known data detector 2004 uses the known data of the second known data area in which the same pattern is repeated twice, .

Since the known data detector 2004 knows the structure of the data group, when the location of the second known data area is detected, the known data detector 2004 counts symbols or segments based on the second known data area location, It is possible to estimate the first and third to sixth known data area positions. If the data group is a data group including a field sync, a symbol or a segment is counted based on the second known data area position to estimate the position of the field sync in the corresponding data group located temporally before the second known data area can do. Also, the known data detector 2004 may output the base data position information and the field synchronization position information in the parade including the mobile service selected by the user by referring to the M / H frame related information input from the signaling decoding unit 2013 .

At least one of the estimated known data location information and the field synchronous location information is provided to the demodulator 2002, the channel equalizer 2003, the signaling decoding unit 2013, and the operation controller 2000.

Also, the known data detector 2004 may estimate an initial frequency offset using the known data inserted in the second known data area, i.e., the ACQ known data area. In this case, the demodulator 2002 can more accurately estimate and compensate the carrier frequency offset from the known data position information and the initial frequency offset estimation value.

Operation Controller

The operation controller 2000 receives M / H frame time information, presence / absence of a selected data group of parade, location information of known data in a data group, power control information, and the like on the basis of the known data location information and transmission parameter information, . The operation controller 2000 controls operations of the demodulator 2002, the equalizer 2003, the block decoder 2005 and the RS frame decoder 2006 as shown in the diagram of FIG. 40, The operation of the entire receiving system can be controlled.

41 is an overall block diagram of the operation controller 2000. Fig.

The Operation Controller 2000 includes a Parade ID Checker 3101, a Frame Synchronizer 3102, a Parade Mapper 3103, a group controller 3104, (Known Sequence Indication Controller) 3105 as shown in FIG.

The operation controller 2000 receives the known data position information from the known data detector 2004 and the transmission parameter information from the signaling decoder 2013 to generate a control signal necessary for the receiving system. For example, the known data position information detected by the known data detector 2004 is input to a known sequence indication controller 3105, and the transmission parameter information decoded by the signaling decoder 2013 (i.e., TPC data Is input to the Parade ID Checker 3101. [

The Parade ID Checker 3101 compares the Parade ID (User selected Parade ID) included in the User control signal with the Parade ID input from the signaling decoder 2013. At this time, if the two Parade IDs are not identical, the Parade ID Checker 3101 waits until the next transmission parameter is input from the signaling decoder 2013.

If the two parade IDs are the same, the parade ID checker 3101 outputs transmission parameter information to the blocks and the system throughout the operation controller 2000.

That is, if it is determined that the Parade ID among the transmission parameter information input to the Parade ID checker 3101 is the same as the Parade ID selected by the User, the Parade ID Checker 3101 transmits a starting_group_number () to the Parade Mapper 3103 SGN) and number_of_groups (NoG). The Parade ID Checker 3101 outputs a sub_frame_number, a slot_number and a parade_repetition_cycle (PRC) to a frame synchronizer 3102 and outputs SCCC_block_mode, SCCC_outer_code_mode_A, SCCC_outer_code_mode_B, SCCC_outer_code_mode_C and SCCC_outer_code_mode_D to the block decoder 2005 And outputs RS_frame_mode, RS_code_mode_primary, and RS_code_mode_secondary to the RS frame decoder 2006.

The Parade Mapper 3103 receives SGN and NoG from the Parade ID Checker 3101, determines which slot among the 16 Slots in the Sub-frame is to be transmitted, and outputs the information. The data group number (Group number) transmitted for each sub-frame is defined as a successive integer from SGN to (SGN + NoG-1). For example, if SGN = 3 and NoG = 4, four data groups with group numbers 3, 4, 5, and 6 are transmitted for each sub-frame. The Parade Mapper 3103 obtains a slot number j in which a data group is transmitted according to Equation (1) with Group number i obtained from SGN and NoG.

When SGN = 3 and NoG = 4 as in the above example, substituting this into Equation (1), the slot numbers of the data groups to be transmitted are 12, 2, 6, and 10, respectively.

The Parade Mapper 3103 outputs the obtained slot number information.

As an example of outputting the slot number, a bit vector having 16 bits can be used.

The bit vector SNi (i = 0 to 15) can be set to 1 if there is a data group transmitted in the i-th slot, and to 0 if there is a data group transmitted in the i-th slot, and this bit vector can be output as the slot number information.

The Frame Synchronizer 3102 receives sub_frame_number, slot_number, and PRC from the Parade ID Checker 3101, calculates a slot_counter and a frame_mask signal, and outputs the computed slot_counter and frame_mask signals. The slot_counter indicates a slot_number at the current time when the receiver operates, and the frame_mask indicates a signal indicating whether the corresponding Parade is transmitted to the current frame. The Frame Synchronizer 3102 initializes the slot_counter, the sub_frame_counter, and the frame_counter when receiving the first signaling information. In this process, the number of slots to be delayed is added according to the time taken until the input signaling information is decoded to generate a counter value at the present time. After the initialization process, the slot_counter is updated in each slot cycle, the sub_frame_counter is updated in each cycle of the slot_counter value, and the frame_counter is updated in each cycle of the sub_frame_counter. The frame_mask signal is generated by referring to the frame_counter information and the PRC information. In the embodiment, frame_mask outputs 1 if the corresponding parade is transmitted in the current frame, and 0 can be output in the frame_mask.

The group controller 3104 receives the slot number information from the Parade Mapper 3103, receives slot_counter and frame_mask information from the Frame Synchronizer 3102, and outputs a group_presence_indicator indicating whether the current data group is transmitted do. For example, if the slot number information input from the Parade Mapper 3103 is 12, 2, 6, or 10, the frame_mask information input from the Frame Synchronizer 3102 is 1 and the slot_counter is 2, 6, 10, When group_presence_indicator is set to 1, it outputs 1, otherwise it outputs 0.

The Known Sequence Indication Controller 3105 outputs location information of other known data, data group start position information, and the like with the location information of the specific known data to be input. At this time, since the known data exists in the predetermined position in the data group, knowing the position information of one known data string among the plurality of known data strings, data position information and data group start position information of other known strings can be known. The Known Sequence Indication Controller 3105 may output the known data and the data group location information required by the demodulation unit of the receiving system only when the data group is transmitted using the group_presence_indicator information. The role of the Known Sequence Indication Controller 3105 may be performed in the known data detector 2004.

Channel equalizer

The demodulated data using the known data in the demodulator 2002 is input to the equalizer 2003. The demodulated data may also be input to the known data detector 2004.

5, the A region is divided into M / H block B4 to M / H block B7, and the B region is divided into M / H block B3 and M / H block B8, the C area includes M / H block B2 and M / H block B9, and the D area includes M / H block B1 and M / H block B10. That is, one data group is divided into M / H blocks each having a length of 16 segments from B1 to B10 and a long training sequence (i.e., a known data sequence) is inserted at the beginning of the M / H blocks B4 to B8 do. Also, one VSB field may be assigned two data groups, one of which is the field sync after the 37 th segment of the data group.

According to the present invention, known data and / or field synchronization, which are known in terms of location and contents, can be used for channel equalization by the promise of the transmitting / receiving side.

The channel equalizer 2003 may perform channel equalization in various ways. In the present invention, a channel impulse response (CIR) is estimated using known data and / or field synchronization to perform channel equalization As an embodiment.

Particularly, in the present invention, estimation and application of a channel impulse response (CIR) are different according to each region in a data group layered and transmitted in a transmission system.

At this time, up to four data groups can be allocated and transmitted in one VSB frame. In this case, not all data groups include field synchronization. The present invention estimates CIR using field synchronization and known data for a data group including field synchronization, and estimates CIR using only known data for a data group that does not include field synchronization.

For example, in the case of a data group including field synchronization, the data of the M / H block B3 can be channelized using the CIR obtained from the field sync and the known data of the first known data area. Also, the data of the M / H blocks B1 and B2 can be compensated for the channel distortion using the CIR obtained from the CIR obtained from field synchronization and the known data of the first known data area. However, since the CIR can not be obtained from the field sync in the case of a data group that does not include field sync, the data of the M / H blocks B1 to B3 use the CIR obtained in the first known data area and the third known data area to perform channel distortion You can compensate.

The present invention performs channel equalization on the data in the data group using the estimated CIR in the known data region. In this case, one of the estimated CIRs is used as it is according to the characteristic of each region of the data group, CIRs generated by interpolation of a plurality of CIRs or extrapolation may be used.

Here, interpolation is a function value at a certain point between Q and S when a function value F (Q) at a point Q and a function value F (S) at a point S are known for a certain function F (x) And the most simple example of the interpolation is linear interpolation. 42 is a diagram showing an example of linear interpolation.

는 다음의 수학식 7과 같이 추정할 수 있다. 다시 말해, 시점 Q, S에서의 함수값 F(Q), F(S)를 알고 있으므로 두 지점을 지나는 직선을 구해서 P시점에서의 함수값의 근사값

를 구할 수 있다. 이때, (Q,F(Q)), (S,F(S))를 지나는 직선의 수식은 다음의 수학식 7과 같다. That is, given a function F (Q) of x = Q and a function F (S) of x = S in an arbitrary function F (x)

Can be estimated as the following Equation (7). In other words, since the function values F (Q) and F (S) at the points Q and S are known, a straight line passing through the two points is obtained and an approximate value of the function value at the point P

Can be obtained. At this time, a straight line passing through (Q, F (Q)) and (S, F (S)) is expressed by Equation (7).

을 구하면 다음의 수학식 8과 같다. Therefore, P is substituted into x in Equation (7), and an approximate value of the function value at the point P

The following equation (8) is obtained.

The linear interpolation technique of Equation (8) is the simplest example of the many interpolation techniques. Since various interpolation techniques can be used in addition to the above method, the present invention is not limited to the above example.

Also, extrapolation is a process that determines the function value F (Q) at time Q and the function value F (S) at time S for a certain function F (x) It means to estimate the function value at the time point. The simplest example of such extrapolation is linear extrapolation.

를 구할 수 있다.43 is a diagram showing an example of linear extrapolation. If the function values F (Q) and F (S) at the time Q and S are known in an arbitrary function F (x) in the case of the linear extrapolation as described above, a straight line passing through the two points is obtained, Approximate value of function at time

Can be obtained.

The linear extrapolation technique is the simplest example of a number of extrapolation techniques, and various extrapolation techniques can be used in addition to the above-described method, so that the present invention is not limited to the above example.

Figure 44 is an embodiment of a channel equalizer according to the present invention.

FIG. 44 is a block diagram illustrating an embodiment of a channel equalizer according to the present invention. The channel equalizer includes a first frequency domain transform unit 4100, a channel estimation unit 4110, a second frequency domain transform unit 4121, A distortion compensating unit 4130, and a time domain transforming unit 4140.

The channel equalizer may further include a residual carrier phase error removing unit, a noise canceler (NC), and a decision unit.

The first frequency domain transform unit 4100 includes an overlap unit 4101 for superimposing input data and an FFT (Fast Fourier Transform) unit 4102 for transforming the output data of the superposition unit 4101 into a frequency domain, .

The channel estimation unit 4110 includes a CIR estimator 4111, a first cleaner (Pre-CIR Cleaner) 4113, a CIR calculator 4114, 2 cleaner (Post-CIR Cleaner) 4115, and a zero-padding unit 4116.

The channel estimator 4110 may further include a phase compensator for compensating the phase of the CIR estimated by the CIR estimator 4111. [

The second frequency domain transformer 4121 includes an FFT unit for transforming the CIR output from the channel estimator 4110 into a frequency domain.

The time domain transforming unit 4140 includes an IFFT unit 4141 for transforming the distortion compensated data into the time domain by the distortion compensating unit 4130 and extracting only valid data from the output data of the IFFT unit 4141 And a save unit 4142. The output data of the save unit 4142 is channel equalized data.

At this time, the residual carrier phase error removing unit may be provided at the output of the time domain transforming unit 4140 to estimate and remove the residual carrier phase error included in the channel equalized data.

Also, the noise removing unit may further include a noise removing unit at an output terminal of the time domain transforming unit 4140 to estimate and remove the noise included in the channel equalized data.

The distortion compensator 4130 may be any element that performs a complex multiplication function.

44, the demodulated input data is superimposed in the overlapping part 4101 of the first frequency domain transforming part 4100 at a predetermined overlapping ratio, and is output to the FFT part 4102. The FFT unit 4102 transforms the time domain superposed data into frequency domain superposed data through the FFT, and outputs the superposed data to the distortion compensating unit 4130.

The distortion compensating unit 4130 complex-multiplies the frequency-domain superposed data output from the FFT unit 4102 of the first frequency-domain transform unit 4100 by the equalization coefficient calculated by the coefficient calculation unit 4122, Compensates the channel distortion of the superimposed data output from the IFFT unit 4102 and outputs the compensated channel distortion to the IFFT unit 4141 of the time domain transform unit 4140. The IFFT unit 4141 IFFTs the superposed data on which the distortion of the channel is compensated, converts the superposed data into a time domain, and outputs the converted time domain to the save unit 4142. The save unit 4142 extracts only the valid data from the overlapped data of the channel equalized time domain and outputs the extracted data.

The demodulated received data is input to the overlapping unit 4101 of the first frequency domain transform unit 4100 in the channel equalizer and also to the CIR estimator 4111 of the channel estimation unit 4110. [

The CIR estimator 4111 estimates the CIR using the training sequence. If the data to be channelized is data in a data group including field synchronization, the training sequence used in the CIR estimator 4111 may be field synchronization data and known data. However, if the data to be channelized is data in a data group that does not include field synchronization, the training sequence may be only known data.

For example, the CIR estimator 4111 estimates a channel impulse response (CIR) using data received during the known data interval and reference station data generated at the receiving side by the promise of the transmitting / receiving side. For this, the CIR estimator 4111 receives known data position information from the known data detector 2004.

In addition, the CIR estimator 4111 may calculate the impulse response (CIR_FS) of the channel using the data received during the field sync period and the reference field sync data generated at the receiver by the promise of the send / ) Can be estimated. For this, the CIR estimator 4111 may receive field sync position information from the known data detector 2004.

The estimated CIR is input to the CIR operator 4114 through the first cleaner 4113 or bypasses the first cleaner 4113. The CIR calculator 4114 interpolates or extrapolates the estimated CIR to the second cleaner 4115.

The first cleaner 4113 may or may not operate depending on whether the CIR operator 4114 interpolates or extrapolates the estimated CIR. For example, if interpolation is performed on the estimated CIR, the first cleaner 4113 does not operate and the first cleaner 4113 operates when the extrapolated CIR is estimated.

That is, the CIR estimated from the known data includes not only channel components to be obtained but also jitter components due to noise. Since such a jitter component is a factor for lowering the performance of the equalizer, it is preferable to remove the jitter component before using the CIR in the coefficient calculation unit 4122. [ Therefore, the first and second cleaners 4113 and 4115 remove (i.e., make '0') a portion of the input CIR component whose power is below a preset threshold value do. This removal process is called CIR cleaning.

That is, the CIR interpolation in the CIR calculator 4114 is performed by multiplying the two CIRs estimated by the CIR estimator 4112 by the coefficients. At this time, some of the noise components of the CIR are added together and canceled. Therefore, when performing the CIR interpolation in the CIR operator 4114, the original CIR with noise components remains. That is, when performing the CIR interpolation in the CIR computing unit 4114, the estimated CIR is input to the CIR computing unit 4114 by bypassing the first cleaner 4113. The CIR interpolated by the CIR calculator 4114 is cleaned by the second cleaner 4115.

On the other hand, the CIR extrapolation in the CIR calculator 4114 is performed by estimating a CIR located outside the two CIRs using the difference between the two CIRs estimated by the CIR estimator 4112. [ Therefore, at this time, the noise component of the CIR is rather amplified. Therefore, when the CIR calculator 4114 performs CIR extrapolation, the CIR cleaned by the first cleaner 4113 is used. That is, when performing the CIR extrapolation in the CIR operator 4114, the extrapolated CIR is input to the zero padding unit 4116 via the second cleaner 4115.

On the other hand, when the CIR output from the second cleaner 4115 is CIN that is input when the CIR is transformed from the second frequency domain transformer 4121 to the frequency domain, the FFT size does not coincide with the CIR length Lt; / RTI &gt; That is, the length of the CIR may be smaller than the FFT size. In this case, the zero padding unit 4116 adds '0' to the CIR by the difference between the FFT size and the inputted CIR length, and outputs the result to the second frequency domain transform unit 4121. Here, the zero padded CIR may be one of the interpolated CIR, the extrapolated CIR, and the estimated CIR in the known data interval.

The second frequency domain transformer 4121 FFTs the CIR of the input time domain to convert the input CIR to the frequency domain CIR, and outputs the CIR to the coefficient calculator 4122.

The coefficient calculator 4122 calculates the equalization coefficient using the CIR of the frequency domain output from the second frequency domain transformer 4121, and outputs the calculated equalization coefficient to the distortion compensator 4130. In this case, the coefficient calculator 4122 calculates a frequency-domain equalization coefficient for minimizing the mean square error (MMSE) from the CIR of the frequency domain, and outputs the equalized coefficient to the distortion compensator 4130 .

The distortion compensating unit 4130 complex-multiplies the frequency-domain superposed data output from the FFT unit 4102 of the first frequency-domain transform unit 4100 by the equalization coefficient calculated by the coefficient calculation unit 4122, Compensates the channel distortion of the superimposed data output from the superimposing unit 4102.

Block decoder

On the other hand, if the data input to the block decoder 2005 after channel equalization in the equalizer 2003 is data in which both block coding and trellis coding are performed on the transmitting side (for example, data in the RS frame) The trellis decoding and the block decoding are performed, and only the trellis decoding is performed if the data is the data on which only the Binary Coded is performed (e.g., the main service data) without performing the block coding.

The trellis-decoded and block-decoded data in the block decoder 2005 are output to the RS frame decoder 2006. That is, the block decoder 2005 decodes the known data among the data in the data group, the data used for initializing the trellis, the signaling information data, the MPEG header, and the RS encoder / non-systematic RS encoder or the non- And removes the added RS parity data and outputs it to the RS frame decoder 2006. Here, the data removal may be performed before the block decoding, or may be performed during the block decoding or after the block decoding.

Meanwhile, the trellis decoded data in the block decoder 2005 is output to the data deinterleaver of the main service data processor 2008. In this case, the data that is Trellis-decoded in the block decoder 2005 and output to the data deinterleaver may include not only the main service data, but also data in the RS frame and signaling information. Also, RS parity data added after the preprocessor 230 on the transmission side may be included in data output to the data deinterleaver.

In another embodiment, block coding is not performed on the transmission side, and data subjected to only trellis coding may be bypassed as it is in the block decoder 2005 and output to the data deinterleaver. In this case, a trellis decoder should be provided before the data deinterleaver.

The block decoder 2005 performs Viterbi (or trellis) decoding on the input data if the input data is data that is not subjected to block coding at the transmitting end but only Trellis coding and outputs a hard decision value Or hard decision of the soft decision value and output the result.

The block decoder 2005 outputs a soft decision value to the input data if the input data is data in which both block coding and trellis coding are performed on the transmission side.

That is, in the block decoder 2005, if the input data is block-encoded in the block processor 302 on the transmitting side and is Trellis-coded in the trellis encoder 256, Conversely, trellis decoding and block decoding are performed. At this time, the block processor on the transmission side can be regarded as an external encoder, and the trellis encoder can be regarded as an internal encoder.

In order to maximize the decoding performance of the outer code in decoding the concatenated code, it is preferable to output the soft decision value in the decoder of the inner code.

45 is a detailed block diagram illustrating an embodiment of a block decoder 2005 according to the present invention. The feedback controller 5010 includes an input buffer 5011, a trellis decoder 5012, a symbol-to-bit converter 5013, an outer block extractor 5014, a feedback deformatter 5015, a symbol deinterleaver 5016, an outer symbol mapper 5017, a symbol decoder 5018, (Inner Symbol Mapper) 5019, a symbol interleaver 5020, a feedback formatter 5021, and an output buffer 5022. Like the transmitting side, the trellis decoding unit 5012 can be regarded as an internal decoder, and the symbol decoder 5018 can be regarded as an external decoder.

The input buffer 5011 receives the block-coded mobile service data symbols (including RS parity data symbols and CRC data symbols added at the time of RS frame encoding) among the symbol values output from the equalizer 2003, And repeatedly outputs the stored symbol values to the trellis decoding unit 5012 M times for the turbo decoding size (TDL) for turbo decoding. The turbo decoding size (TDL) may be referred to as a turbo block. Here, the TDL must be able to contain at least one SCCC block size. Therefore, assuming that one M / H block is a 16-segment unit and a combination of 10 M / H blocks constitutes one SCCC block, as defined in FIG. 5, the TDL is larger Should be the same. For example, assuming that two M / H blocks constitute one SCCC block, the TDL may be 32 segments (828x32 = 26496 symbols) or more.

The M is a repetition number of turbo decoding predetermined by the feedback controller 5010.

Also, the input buffer 5011 does not include a mobile service data symbol (including RS parity data symbols and CRC data symbols added at the time of RS frame encoding) in the symbol values output by the equalizer 2003 The input symbol values in the non-period are bypassed without storing. That is, since only the trellis decoding is performed on the input symbol value of the interval in which the SCCC block coding has not been performed, the input buffer 5011 does not perform the storing and the iterative outputting process on the input and outputs the input symbol value to the trellis decoding unit 5012 ).

The storage, repetition, and output of the input buffer 5011 are controlled by the feedback controller 5010. The feedback controller 5010 refers to the SCCC block mode and the SCCC outer code mode output from the operation controller 2000 or the signaling decoding unit 2013 to store and output the input buffer 5011 Can be controlled.

The trellis decoding unit 5012 includes a 12-way Trellis Coded Modulation (TCM) decoder to correspond to a 12-way trellis encoder. The 12-way trellis coder performs a 12-way trellis decoding on the input symbol value.

That is, the trellis decoding unit 5012 receives the output symbol value of the input buffer 5011 and the soft-decision value of the feedback formatter 5021 as much as TDL, and performs TCM decoding of each symbol do.

At this time, the soft decision values output from the feedback formatter 5021 are matched one-to-one with the symbol positions of the TDL output from the input buffer 5011 under the control of the feedback controller 5010 and output to the trellis decoding unit 5012). That is, the symbol values output from the input buffer 5011 and the turbo decoded data are matched with each other at the same positions in the corresponding turbo block (TDL), and are output to the trellis decoding unit 5012. For example, if the turbo decoded data is the third symbol value in the turbo block, the third symbol value in the turbo block output from the input buffer 5011 is output to the trellis decoding unit 5012.

For this, the feedback controller 5010 controls to store the corresponding turbo block data in the input buffer 5011 during the regenerative turbo decoding, and outputs the soft decision value of the output symbol of the symbol interleaver 5020 LLR) and the symbol value of the input buffer 5011 corresponding to the same position in the block of the output symbol are matched one by one and input to the TCM decoder of the corresponding path. At this time, if the value is not a block-coded symbol value, null is input to the output position matched in the feedback formatter 5021 because turbo decoding is not performed.

After this process is performed for a predetermined number of times of turbo decoding, data of the next turbo block is output from the input buffer 5011 and the turbo decoding process is repeated.

The output of the trellis decoding unit 5012 indicates the reliability of the symbols input to the transmitting-side trellis encoder for the transmitted symbols. For example, since the input of the transmission side trellis coder 256 is a symbol of two bits, the log likelihood ratio (LLR) between the probability of one bit being '1' and the probability of being '0' And the lower bits, respectively (in units of bits). The Log Likelihood Ratio (LLR) means a logarithm of the ratio of the probability that the input bit is 1 to the probability that the probability of the input is 0. (LLR) of the probability value that two bits, that is, one symbol is "00", "01", "10", and "11" Symbol unit output). This is a soft decision value for the received symbol, which indicates the reliability of the bits input to the trellis encoder. As the decoding algorithm of each TCM decoder in the trellis decoding unit 5012, MAP (Maximum A Posteriori Probability) and SOVA (Soft-Out Viterbi Algorithm) can be used.

The output of the trellis decoding unit 5012 is output to a symbol-to-byte converter 5013 and an external block extractor 5014.

The symbol-to-byte converter 5013 performs a hard decision on the soft decision value output from the trellis decoding unit 5012 and outputs a trellis decoded result. The symbol-to- To the data deinterleaver of the main service data processing unit 2008 of FIG. That is, the symbol-to-byte converter 5013 performs hard decision on a bit-by-bit basis with respect to the soft decision value of the output symbol of the trellis decoding unit 5012. [ Therefore, the data that is hard-determined in the symbol-byte converter 5013 and output in units of bytes includes not only the main service data but also mobile service data, known data, signaling information data, RS parity data, and MPEG header.

The outer block extractor 5014 extracts a soft service value corresponding to the mobile service data symbol (including RS parity data and CRC data symbols added at the time of RS frame encoding) among soft decision values as much as the TDL of the trellis decoding unit 5012 B and outputs them to the feedback deformatter 5015. [ That is, in the outer block extractor 5014, soft decision values such as main service data, known data, signaling information data, RS parity data, and MPEG header are discarded without being outputted to the feedback deformer 5015.

The feedback deformatter 5015 receives an intermediate process (for example, a group formatter, a data deinterleaver, a packet formatter, and a data interleaver) in which the output symbols of the transmitting-side block processor 302 are input to the trellis encoder 256 And reordering the soft decision value of the mobile service data symbol, and outputs the result to the symbol deinterleaver 5016. The symbol deinterleaver 5016 decodes the soft decision value of the mobile service data symbol. This is because there are a plurality of blocks between the trellis encoding units 256 of the block processor 302 of the transmission side and the order of the mobile service data symbols output from the block processor 302 due to these blocks and the order of the trellis The order of the mobile service data symbols input to the encoding unit 256 is changed. Therefore, the feedback deformatter 5015 outputs the mobile service data symbols input from the symbol deinterleaver 5016 to the outer block extractor 5014 so that the order of the mobile service data symbols is identical to the output order of the block processor 302 on the transmission side Reordering the order of the mobile service data symbols. This reordering process can be implemented by at least one of software, hardware, and middleware.

The symbol deinterleaver 5016 deinterleaves the soft decision value of the output data symbol, which is changed in order by the feedback deformer 5015, as a reverse process of symbol interleaving of the symbol interleaver 514 on the transmitting side. The size of the block used for deinterleaving in the symbol deinterleaver 5016 is equal to the interleaving size (i.e., B) of the actual symbol of the symbol interleaver on the transmitting side. This is because turbo decoding is performed by the trellis decoding unit 5012, Decoder 5018 as shown in FIG.

The input and output of the symbol deinterleaver 5016 are both soft decision values, and the deinterleaved soft decision value is output to the outer symbol mapper 5017.

The operation of the external symbol mapper 5017 may be changed depending on the configuration and coding rate of the transmission side convolutional encoder 513. For example, if the convolutional encoder 513 encodes the data, the external symbol mapper 5017 outputs the input data to the symbol decoder 5018 as it is. As another example, if the convolutional encoder 513 encodes data that is 1/4 encoded and transmitted, the input data is converted according to the input format of the symbol decoder 5018 and is output to the symbol decoder 5018. For this purpose, the external symbol mapper 5017 can receive SCCC related information, for example, the SCCC block mode and the SCCC outer code mode, from the signaling decoding unit 2013. [

The symbol decoder 5018 (i.e., the outer decoder) performs symbol decoding on the output of the outer symbol mapper 5017, which is an inverse process of the convolutional encoder 513 on the transmitting side. At this time, the symbol decoder 5018 outputs two soft decision values. One is a soft decision value (hereinafter referred to as a first soft decision value) to be matched with the output symbol of the convolutional encoder 513 and the other is a soft decision value (hereinafter, referred to as a soft decision value), which matches the input bit of the convolutional encoder 513. [ Quot; second soft decision value &quot;). The first soft decision value indicates the reliability of the output symbol of the convolutional encoder 513, that is, the reliability of two bits, and the log ratio (LLR) between the probability of '1' (LLR) of the probability values for which the two bits are "00", "01", "10", "11" (Symbol unit output). The first soft decision value is fed back to the trellis decoding unit 5012 through the inner symbol mapper 5019, the symbol interleaver 5020, and the feedback formatter 5021. The second soft decision value indicates the reliability of the input bit of the transmission side convolutional encoder 513. The second soft decision value is represented by a log ratio (LLR) between a probability of '1' and a probability of '0' (5022). The decoding algorithm of the symbol decoder 5018 may be MAP (Maximum A Posteriori Probability), SOVA (Soft-Out Viterbi Algorithm), or the like.

The first soft decision value output from the symbol decoder 5018 is input to the inner symbol mapper 5019. The inner symbol mapper 5019 converts the first soft decision value into an input format of the trellis decoding unit 5012 and outputs it to the symbol interleaver 5020. The operation of the internal symbol mapper 5019 may be changed according to the structure and coding rate of the transmission side convolutional encoder 513.

The symbol interleaver 5020 symbol-interleaves the first soft decision value output from the internal symbol mapper 5019 as shown in FIG. 30, and outputs the result to the feedback formatter 5021. The output of the symbol interleaver 5020 also becomes a soft decision value.

The feedback formatter 5021 includes an intermediate process (for example, a group formatter, a data deinterleaver, a packet formatter, and a data interleaver) in which the output symbols of the transmission-side block processor 302 are input to the trellis encoder 256, And changes the order of the output values of the symbol interleaver 5020 according to a change in the processing order of the symbols generated in the trellis decoding unit 5012. The reordering process of the feedback formatter 5021 may be implemented by at least one of software, hardware, and middleware.

The soft decision values output from the symbol interleaver 5020 are one-to-one matched with the TDL mobile service data symbol positions output from the input buffer 5011 and input to the trellis decoding unit 5012. At this time, since the RS service parity symbol, the known data symbol, the signaling information data, etc. of the main service data symbol or the main service data are not mobile service data symbols, the feedback formatter 5021 inserts null data at the corresponding position, And outputs it to the unit 5012. Further, since there is no value fed back from the symbol interleaver 5020 at the start of the first decoding every time the TDL-sized symbols are turbo decoded, the feedback formatter 5021 receives the mobile service data 5010 under the control of the feedback controller 5010, And outputs null data to the trellis decoding unit 5012. The trellis decoding unit 5012 decodes the null data.

The output buffer 5022 receives the second soft decision value in the symbol decoder 5018 under the control of the feedback controller 5010, temporarily stores it, and outputs the result to the RS frame decoder 2006. For example, the output buffer 5022 overwrites the second soft decision value of the symbol decoder 5018 until M times of turbo decoding is performed, and performs M times of turbo decoding on one TDL And outputs the second soft decision value at that time to the RS frame decoder 2006.

The feedback controller 5010 controls the number of turbo decoding and turbo decoding iterations of the entire block decoder as shown in FIG.

That is, after the turbo decoding is performed for the preset number of repetitions, the second soft decision value of the symbol decoder 5018 is output to the RS frame decoder 2006 through the output buffer 5022, The process is complete.

This is referred to as a recursive turbo decoding process for convenience of explanation in the present invention.

At this time, the number of recursive turbo decoding operations between the trellis decoding unit 5012 and the symbol decoder 5018 can be defined in consideration of hardware complexity and error correction performance. If the number of times increases, the error correction capability is improved. However, It is complicated.

On the other hand, the main service data processing unit 2008 of FIG. 40 is a block necessary for receiving main service data, and may not be necessary in a reception system structure for receiving only mobile service data.

The data deinterleaver in the main service data processing unit 2008 deinterleaves the data output from the block decoder 2005 in the reverse process of the data interleaver on the transmitting side and outputs the deinterleaved data to the RS decoder. Data input to the data deinterleaver includes not only main service data but also mobile service data, known data, RS parity, MPEG header, and the like.

The RS decoder performs systematic RS decoding on the deinterleaved data and outputs the decoded data to the derandomizer.

The de-randomizer receives the output of the RS decoder and generates pseudo-random bytes that are the same as the renderer of the transmitter, bitwise XORs (exclusive OR) them, inserts MPEG sync bytes in front of every packet, .

RS  Frame decoder

The data output from the block decoder 2005 is a unit of a portion. That is, the RS frame on the transmitting side is divided into a plurality of potions, and the mobile service data of each potion is allocated to the A / B / C / D area in the data group or the A / B area and the C / D area And transmitted to the receiving side. Therefore, the RS frame decoder 2006 collects a plurality of potions in one parade to form one RS frame, forms two RS frames, and performs error correction decoding on an RS frame basis.

For example, if the RS frame mode is 00, one parade transmits one RS frame. At this time, one RS frame is divided into a plurality of potions, and mobile service data of each divided port is divided into A / B / C / D area. In this case, the RS frame decoder 2006 extracts the mobile service data in the A / B / C / D area in the data group and constructs a potion as shown in FIG. 46 (a) A plurality of potions can be obtained by performing the operation on the data groups. The mobile service data of a plurality of potions can be collected to form one RS frame. If a stuffing byte is added to the last portion, the stuffing byte is removed and an RS frame is constructed.

In another example, if the RS frame mode is 01, one parade transmits two RS frames, i.e., a primary RS frame and a secondary RS frame. At this time, the primary RS frame is divided into a plurality of primary parts, and the mobile service data of each divided primary part is allocated and transmitted to the A / B area in the corresponding data group. The secondary RS frame is divided into a plurality of secondary potions, and the mobile service data of each secondary position is assigned to the C / D area in the corresponding data group and transmitted. In this case, the RS frame decoder 2006 extracts the mobile service data from the A / B area in the data group and constructs one primary part as shown in FIG. 46 (b) A plurality of primary potions can be obtained by performing the operation on the A / B area of the group. A primary RS frame can be constructed by collecting a plurality of primary parts. If a stuffing byte is added to the last primary portion, the stuffing byte is removed and a primary RS frame is constructed. Also, a plurality of secondary potions can be obtained by performing the process of extracting the mobile service data from the C / D area in the data group and configuring one secondary potion for the C / D area of a plurality of data groups of one parade . A secondary RS frame can be formed by collecting a plurality of secondary potions. If a stuffing byte is added to the last secondary position, the stuffing byte is removed and a secondary RS frame is constructed.

That is, the RS frame decoder 2006 receives the mobile service data of each portion of RS-encoded and / or CRC-encoded portions from the block decoder 2005, and receives the mobile service data from the operation controller 2000 (or the signaling decoding unit 2013) And compiles the plurality of potions input according to the outputted RS frame related information to construct an RS frame, and then performs error correction. Referring to the RS frame mode value in the RS frame related information, an RS frame can be constructed, and information on the number of parities and the code size of the RS code used for constructing the RS frame can be known.

The RS frame decoder 2006 corrects errors in the RS frame by performing an inverse process in the RS frame encoder of the transmission system with reference to the RS frame related information. Then, one byte of the MPEG synchronization byte which has been removed in the RS frame coding process is added to the error corrected mobile service data packet, and then derandomization is performed.

FIG. 47 shows a process of forming one RS frame and an RS frame credit map (Reliability Map) when a RS frame mode value is 00, that is, collecting a plurality of potions transmitted in one parade.

That is, the RS frame decoder 2006 collects the received mobile service data and forms an RS frame. The mobile service data is RS-encoded data in units of RS frames in the transmission system. In this case, error correction coding, for example, CRC coding may be performed or may be omitted.

If the transmission system divides the (N + 2) x (187 + P) bytes of the RS frame into M potions, and the mobile service data of M potions is divided into A / B / C / D region, the receiving system constructs an RS frame of size (N + 2) x (187 + P) bytes by collecting the mobile service data of each port as shown in FIG.

At this time, if the stuffing byte S is added to at least one portion constituting the corresponding RS frame, the stuffing byte is removed and an RS frame and an RS frame credit map are configured. For example, if S stuffing bytes are added as shown in FIG. 27, the S stuffing bytes are removed and an RS frame and an RS frame credit map are constructed.

For example, assuming that the block decoder 2005 outputs a decoded result as a soft decision value, the RS frame decoder 2006 can determine 0 and 1 of the corresponding bit with the sign of the soft decision value, 8 bits are determined and one byte is formed. (N + 2) x (187 + P) bytes in size can be constructed by performing all of these processes on soft decisions of a plurality of potions (or data groups) in one parade.

Further, the present invention uses a soft decision value not only to construct an RS frame but also to construct a reliability map.

The credit map indicates whether the corresponding byte constituted by collecting eight bits determined by the sign of the soft decision value is reliable.

In one embodiment, when the absolute value of the soft decision value exceeds a predetermined threshold value, the corresponding bit value determined as the sign of the soft decision value is determined to be reliable, and if the absolute value is not exceeded, it is determined that it is unreliable. Then, if it is determined that even one bit in one byte composed of eight bits determined by the sign of the soft decision value is unreliable, the corresponding bit in the credit map indicates that there is no credit. Where one bit is one embodiment and may indicate that the corresponding byte in the credit map does not have a credit if, for example, four or more bits are determined to be non-creditable.

Conversely, if all bits in a byte are determined to be creditable, that is, if the absolute value of the soft decision value of all bits of one byte exceeds a predetermined threshold, the credit map indicates that the corresponding byte is credit. Similarly, if a plurality of bits within one byte, for example, four or more bits, are found to be creditable, the credit map indicates that the corresponding byte has credit.

The numerical values shown above are only examples, and the numerical values do not limit the scope of the present invention.

The configuration of the RS frame and the configuration of the credit map using the soft decision value can be performed simultaneously. At this time, the credit information in the credit map corresponds to each byte in the RS frame with 1: 1. For example, if one RS frame has a size of (N + 2) x (187 + P) bytes, then the credit map has a size of (N + 2) x (187 + P) bits. 47 (a ') and (b') show the process of forming a credit map according to the present invention.

And performs error correction using the RS frame credit map information for the RS frame.

FIG. 48 shows an embodiment of an error correction decoding process according to the present invention.

FIG. 48 shows an example of an error correction process in the case where both the RS encoding and the CRC encoding are performed on the RS frame in the transmission system.

Next, the error correction process shown in FIG. 48 will be described in detail.

That is, as shown in FIGS. 48 (a) and 48 (a '), an RS frame credit RS frame having an (N + 2) x (187 + A CRC syndrome check is performed on the RS frame to check whether an error has occurred in each row. Next, the 2-byte CRC checksum is removed as shown in FIG. 48 (b) to construct an RS frame of Nx (187 + P) bytes size and an error flag is displayed in the error flag corresponding to each row. Likewise, since the portion corresponding to the CRC checksum in the credit map is not utilized, this portion is removed to leave only Nx (187 + P) pieces of credit information as shown in (b ') of FIG.

After the CRC syndrome check is performed as described above, RS decoding is performed in the column direction. At this time, the RS may perform erasure correction according to the number of the CRC error flags. 48C, a CRC error flag corresponding to each row in the RS frame is checked, and when the number of rows having errors is RS-decoded in the column direction, RS is set to a maximum value capable of performing laser correction Is equal to or smaller than the number of errors. The maximum number of errors is the number (P) of RS parities inserted in RS encoding.

In an embodiment of the present invention, it is assumed that the number of RS parities P added for each column is 48.

In this case, if the number of rows with a CRC error is less than or equal to the maximum number of errors (48 according to an embodiment) that can be corrected by laser decoding, then (187 + P) (235, 187) -RS in the column direction with respect to the RS frame having 235 N-byte rows and removes 48 bytes of RS parity data added to the end of each column as shown in FIG. 48 (e) do.

However, if the number of rows with CRC errors is greater than the maximum number of errors (i.e., 48) that the RS can modify with laser decoding, the RS can not perform laser decoding.

In this case, error correction can be performed through general RS decoding. Further, the present invention can further enhance the error correction capability by using the credit map generated together with the RS frame from the soft decision value.

That is, in the RS frame decoder, the absolute value of the soft decision value of the block decoder 2005 is compared with a preset threshold value, and the reliability of the bit value determined by the sign of the soft decision value is determined. And the credit information for the corresponding byte composed of 8 bits of the bits determined by the sign of the soft decision value is displayed in the credit map.

Therefore, according to the present invention, even if it is determined that there is a CRC error in the row as a result of the CRC syndrome check of a specific row as shown in (c) of FIG. 48, it is not assumed that all bytes of the row have an error, The error is set only for the byte that is judged as not having a credit. That is, regardless of whether or not the CRC error of the corresponding row exists, only the byte that is judged to have no credit in the credit information of the credit map is set as the erasure point.

As another method, it is determined that there is a CRC error in the corresponding row as a result of the CRC syndrome check, and therefore, the credit information of the credit map is set as an error only for the byte that is judged to have no credit. That is, only the byte which is judged to have no credit in the credit information of the credit map with the CRC error in the corresponding row is set as the erasure point.

Then, if the number of error points for each column is less than or equal to the maximum number of errors that can be corrected by laser decoding (ie, 48), the RS performs laser decoding on that column. Conversely, if the number of error points is greater than the maximum number that can be corrected by laser decoding (i.e., 48), RS performs a general RS decoding on the column.

That is, if the number of rows with CRC errors is greater than the maximum error number (e.g., 48) that the RS can modify with laser decoding, then the number of rows in the column determined by the credit information in the credit map, The RS performs laser decoding on the RS, or performs general RS decoding on the RS.

For example, if the number of rows with CRC errors in the RS frame is greater than 48, the number of laser points determined by credit information in the credit map is 40 in the first column, and 50 in the second column Let's assume. Then, (235, 187) -RS performs laser decoding on the first column and (235, 187) -RS decoding on the second column.

If error correction decoding is performed in all column directions in the RS frame by performing the above-described process, 48-byte parity data added to the end of each column is removed as shown in (e) of FIG.

As described above, the number of all CRC errors corresponding to each row in the RS frame is larger than the maximum number of errors that can be corrected by laser decoding in the CR decoding of the specific column, If the number of low-confidence bytes is equal to or less than the maximum error count that can be corrected by laser decoding, the RS can perform laser decoding on that column.

Here, the difference between general RS decoding and RS-laser decoding is the number of correctable errors. That is, when general RS decoding is performed, the error can be corrected by a number (for example, 24) corresponding to the inserted (number of RS parities) / 2 in the RS encoding process. If RS performs laser decoding, The error can be corrected by the number of inserted RS parities (for example, 48).

After the error correction decoding is performed as described above, RS frames of 187 N-byte low (i.e., packets) can be obtained as shown in FIG. 48 (e).

A multiplexer for multiplexing a plurality of parts is provided at an input terminal of M RS frame decoders, and a multiplexer for multiplexing a plurality of parts at M input terminals of M RS frame decoders An output terminal may include a demultiplexer to configure an RS frame decoder.

In order to service the audio and / or video data included in the RS frame decoded by the RS frame decoder 2006 and the RS-decoded RS frame, the RS frame must be output to the A / V decoder 2015.

At this time, FIC data is required to extract and decode audio and / or video data included in the RS frame in the A / V decoder 2015. The A / V decoder 2015 supports an MPEG-2 transport packet (TP) format.

In this case, the data of the RS frame decoded by the RS frame decoder 2006 and the FEC data decoded by the signaling decoder 2013 are output to the A / V decoder 2015 in the MPEG-2 TP format .

To this end, the present invention includes a first packet conversion unit 2007 for converting the RS frame into a packet of the MPEG-2 TP format, a second packet conversion unit 2014 for converting the FIC data into a packet of the MPEG-2 TP format, . For convenience of explanation, the packet of the MPEG-2 TP format is referred to as TP.

The CRC-decoded and RS-decoded RS frames have N (row) x 187 (column) bytes. N is the length of the row (i.e., the number of columns), and 187 is the length of the column (i.e., the number of rows). That is, the CRC decoded and RS decoded RS frames are a set of 187 M / H service data packets. Each M / H service data packet consists of 2 bytes of M / H header and N-2 bytes of M / H payload. Here, N can be obtained by applying Equation (2) and can have various sizes ranging from 19 to 1822 bytes according to a transmission mode.

The first packet converter 2007 converts the RS frame data into MPEG-2 TP format packets on a per M / H service data packet basis.

The second packet conversion unit 2014 converts the FIC data into a packet of the MPEG-2 TP format on a subframe-by-frame basis.

49 and 50 show an example of a TP for an RS frame according to the present invention.

The TP for the RS frame according to the present invention is largely composed of a header area of 4 bytes and a payload area of 184 bytes.

The payload field includes a payload length field of 1 byte (i.e., 8 bits). The payload area may include a payload byte field of 1 to 183 bytes for transmitting RS frame data according to the payload length field value. The payload field may include a stuffing byte field of 1 to 183 bytes for transmitting stuffing data according to the payload length field value.

49 is an example of a TP when the stuffing byte field does not exist. At this time, the payload area consists of a payload length field of 1 byte and a payload byte field of 183 bytes.

Figure 50 is an example of a TP when a stuffing byte field is present. The payload area at this time is composed of a payload field of 1 byte, a payload byte field of 183-k bytes, and a stuffing byte field of k bytes. That is, the payload byte field may or may not exist according to the stuffing byte field length.

For example, if the value of the payload field in the payload area is 30 in decimal, a payload byte field of 30 bytes and a stuffing byte field of 153 bytes are allocated to the payload area. If the value of the payload field in the payload area is displayed as a decimal number 183, a payload byte field of 183 bytes is allocated to the payload field, and a stuffing byte field is not allocated. Also, if 0 is displayed as a decimal value in the payload field value in the payload area, a payload byte field is not allocated to the payload field, and only a stuffing byte field of 183 bytes is allocated.

In the present invention, the payload length field is allocated after the header area as an embodiment.

In the present invention, if the payload byte field is present, the stuffing byte field is allocated after the payload byte field. According to another embodiment of the present invention, the stuffing byte field may be allocated before the payload byte field if the payload byte field exists.

49 and 50, the header field of the TP for the RS frame includes a sync field, a type indicator field, an M / H service data packet number field, a packet order field, a # of packet field, and a stuffing indicator field.

The synchronization field (8 bits) indicates a value (for example, 0x47) defined by ISO / IEC 13818-1.

The type indicator field (4 bits) indicates a value for discriminating whether the corresponding TP is the TP of the RS frame or the TP of the FIC. If the type indicator field value is 0x0, it is the TP of the RS frame, and if it is 0xF, it is the TP of the FIC.

The M / H service data packet number field (8 bits) indicates the TP of the M / H service data packet of the corresponding RS frame. The M / H service data packet number field value has one of 0 to 186 as one embodiment. That is, if the value of the M / H service data packet number field is 0, the first M / H service data packet is indicated. If the value is 186, the last M / H service data packet is indicated.

The packet order field (4 bits) indicates the number of the TP in the corresponding M / H service data packet. And indicates the first TP if the packet order field value is 0.

The packet count field (4 bits) indicates the total number of TPs packetized from the corresponding M / H service data packet. The packet count field value depends on the N value, which is the length of the M / H service data packet. The packet number field value is a value obtained by subtracting 1 from the total number.

The stuffing indicator field (1 bit) indicates whether there is stuffing data in the corresponding TP. That is, it indicates whether a stuffing byte field is assigned to the corresponding TP. If the stuffing indicator field value is 0, there is no stuffing data, and if the stuffing indicator field is 1, there is stuffing data.

Also, a 3-bit reserved field is allocated to the header area for future use.

The order, position and meaning of the fields allocated to the header field of the TP for the RS frame shown in FIG. 49 and FIG. 50 are only an example for facilitating the understanding of the present invention, and the field assigned to the header field of the TP The order, the location, the meaning, and the number of additional allocated fields can be easily changed by those skilled in the art, the present invention is not limited to the above embodiment.

FIG. 51 is a view showing a first M / H service data packet (that is, FIG. 51 (a)) and a second M / H service data packet (B) of FIG. 18 is divided into units of 183 bytes and packetized in the MPEG-2 TP format.

Assuming that the N value is 407, up to 183 bytes of RS frame data can be inserted into the payload area of one TP, so that three TPs are generated from each M / H service data packet (= 2 * 183 +41). At this time, data of the last 41 bytes of the corresponding M / H service data packet is inserted into the payload byte field of the payload field of the last TP (i.e., third TP), and stuffing data of 138 bytes is inserted into the stuffing byte field.

51A shows an example in which the first M / H service data packet is divided into units of 183 bytes and packetized in the MPEG-2 TP format when N, which is the length of the M / H service data packet, is 407. FIG.

47 in the header field of the first TP, 0 in the type indicator field value, 0 in the M / H service data packet number field value, 0 in the packet order field value, 2 in the packet number field value, 2 in the stuffing indicator field value 0 &quot; is displayed. B7 is displayed in the payload field value of the payload field of the first TP, and data of the first 183 bytes of the first M / H service data packet is inserted into the payload byte field.

47, a type indicator field value of 0, an M / H service data packet number field value of 0, a packet order field value of 1, a packet number field value of 2, a stuffing indicator field value 0 &quot; is displayed. B7 is displayed in the payload field value of the payload field of the second TP, and 183 bytes of data following 183 bytes of the first M / H service data packet are inserted into the payload byte field.

47, a type indicator field value of 0, an M / H service data packet number field value of 0, a packet order field value of 2, a packet number field value of 2, a stuffing indicator field value 1 is displayed. 29 is displayed in the payload length field value of the payload field of the third TP, and data of the last 41 bytes of the first M / H service data packet is inserted into the payload byte field. Then, stuffing data of 138 bytes is inserted into the stuffing byte field.

51B shows an example in which the second M / H service data packet is divided into units of 183 bytes and packetized in the MPEG-2 TP format when N, which is the length of the M / H service data packet, is 407. FIG. 51 (a) is the M / H service data packet number field value in the header area. In this case, 1 is displayed in the field value.

When this process is performed on 187 M / H service data packets in one RS frame, 561 (= 3x187) MPEG-2 TP format packets are generated and output to the A / V decoder 2015.

52 is a flowchart showing an embodiment of a method of packetizing an RS frame according to the present invention into an MPEG-2 TP format.

First, the N value of the corresponding RS frame is calculated using Equation (2) (S6001). In step S6002, the number of TPs to be packetized from each M / H service data packet and the payload length field value of the last TP in each M / H service data packet are obtained using the N value. For example, if N is 407, the number of TPs to be packetized from each M / H service data packet is 3, and the payload length field value of the last TP in each M / H service data packet is 41 in decimal do.

After S6002 is performed, the data of the first M / H service data packet is divided into 183 bytes, and a 4-byte header area is added to the first 183 bytes, (S6003). Then, the value of the payload length field located next to the header area is set (S6004). Then, a TP of 188 bytes is generated. Then, it is confirmed whether the TP is the last TP of the corresponding M / H service data packet (S6005). If it is not the last TP, the payload area of the corresponding TP is composed of only the RS frame data, and the process returns to step S6003 to generate the next TP (S6006).

If it is determined in step S6005 that the TP is the last TP, it is checked whether the value of the payload field of the last TP is less than 183 in decimal (S6007).

If the value of the payload length field is not smaller than 183, that is, if the payload field value is equal to or smaller than 183, the payload area of the corresponding TP is composed of only RS frame data (S6008) and outputs the TP to the A / V decoder 2015 ). Then, it is confirmed whether the TP is a TP generated from the last M / H service data packet in the corresponding RS frame (S6010). For example, if the value of the M / H service data packet number field is 186, the TP determines that it is the last TP of the last M / H service data packet. If it is determined in step S6010 that the packet is not the last M / H service data packet, the process returns to step S6003 to packetize the next M / H service data packet into a packet of the MPEG-2 TP format.

If the value of the payload length field is smaller than 183, the payload area of the TP is composed of RS frame data and stuffing data (S6011), and outputs the TP to the A / V decoder 2015 (S6012) . Then, it is confirmed whether the TP is a TP generated from the last M / H service data packet in the corresponding RS frame (S6013). If it is determined in step S6013 that the packet is not the last M / H service data packet, the process returns to step S6003 to packetize the next M / H service data packet into a packet of the MPEG-2 TP format.

53 and 54 show examples of TPs for FIC according to the present invention.

The FIC according to the present invention comprises a header area of 4 bytes and a payload area of 184 bytes.

The payload field includes a payload length field of 1 byte (i.e., 8 bits). The payload area may include a payload byte field of 1 to 183 bytes for transmitting FIC data according to the payload length field value. The payload field may include a stuffing byte field of 1 to 183 bytes for transmitting stuffing data according to the payload length field value.

53 is an example of a TP when the stuffing byte field does not exist. The payload area at this time consists of a payload field of 1 byte and a payload byte field of 183 bytes.

54 is an example of a TP when a stuffing byte field exists. The payload area at this time is composed of a payload field of 1 byte, a payload byte field of 183-k bytes, and a stuffing byte field of k bytes. That is, the payload byte field may or may not exist according to the stuffing byte field length.

In the present invention, the payload length field is allocated after the header area as an embodiment.

In the present invention, if the payload byte field is present, the stuffing byte field is allocated after the payload byte field. According to another embodiment of the present invention, the stuffing byte field may be allocated before the payload byte field if the payload byte field exists.

The header fields of the TP for the FIC in FIGS. 53 and 54 include a sync field, a type indicator field, a sub-frame number field, a FIC packet order field, (# of FIC packet) field, and a stuffing indicator field.

The synchronization field (8 bits) indicates a value (for example, 0x47) defined by ISO / IEC 13818-1.

The type indicator field (4 bits) indicates a value for discriminating whether the corresponding TP is the TP of the RS frame or the TP of the FIC. If the type indicator field value is 0x0, it is the TP of the RS frame, and if it is 0xF, it is the TP of the FIC.

The sub-frame number field (8 bits) indicates the TP of the FIC data of the sub-frame of the corresponding M / H frame. At this time, since one M / H frame is composed of 5 subframes, the subframe number field value has one of 0 to 4 as an embodiment. That is, if the value of the sub-frame number field is 0, the first sub-frame is indicated, and if it is 4, the last sub-frame is indicated.

The Packet Order field (4 bits) indicates the number of the TP in the corresponding subframe. And indicates the first TP if the packet order field value is 0.

The packet count field (4 bits) indicates the total number of TPs packetized from the corresponding subframe. The packet count field value depends on the number TNOG of all data groups allocated to the subframe. The packet number field value is a value obtained by subtracting 1 from the total number.

The stuffing indicator field (1 bit) indicates whether there is stuffing data in the corresponding TP. That is, it indicates whether a stuffing byte field is assigned to the corresponding TP. If the stuffing indicator field value is 0, there is no stuffing data, and if the stuffing indicator field is 1, there is stuffing data.

Also, a 3-bit reserved field is allocated to the header area for future use.

The order, location, and meaning of the fields allocated to the header fields of the TP for the FIC shown in FIGS. 53 and 54 are merely examples for facilitating understanding of the present invention, and the order of fields allocated to the header fields of the TP , Location, meaning, and the number of additional allocated fields can be easily changed by those skilled in the art, the present invention is not limited to the above embodiment.

FIG. 55 shows an example in which when the TNOG is 5, the FIC data included in each data group is collected and divided into 183 byte units and packetized into the MPEG-2 TP format. That is, the transmission system according to the present invention constructs an FIC segment by segmenting the FIC chunk by 35 bytes, and adding a 2-byte FIC segment header before each segmented 35 bytes. Then, one FIC segment is allocated to the signaling information area of one data group and transmitted. In other words, one FIC segment is included for each data group. If the TNOG is 5, 5 FIC segments are received through 5 data groups in each subframe. The FIC data included in each data group is extracted by the signaling decoder 2013, subjected to error correction decoding, and then output to the second packet converter 2014. The FIC data extracted from the five data groups in the second packet conversion unit 2014 and error-correction-decoded FIC segments are assembled to form the FIC data of the corresponding subframe, and the FIC data is divided into the MPEG- Packetized into a packet.

Assuming that the TNOG value is 5, since a maximum of 183 bytes of FIC data can be inserted into the payload area of one TP, two TPs are generated from each subframe (= 5x37 = 185 = 183 + 2) . At this time, the FIC data of the last 2 bytes of the corresponding subframe is inserted into the payload field of the payload field of the last TP (i.e., the second TP), and 180 bytes of stuffing data is inserted into the stuffing byte field.

That is, FIG. 55 shows an example of packetizing the FIC data of the first subframe into the MPEG-2 TP format when the TNOG is 5, by dividing the FIC data by 183 bytes.

47 in the header field of the first TP, 1 in the type indicator field, 0 in the sub-frame number field value, 0 in the packet order field value, 1 in the packet count field value, and 0 in the stuffing indicator field value do. B7 is displayed in the payload field value of the payload field of the first TP, and FIC data of the first 183 bytes of the first subframe is inserted in the payload byte field.

47 in the synchronous field value of the header area of the second TP, 1 in the type indicator field value, 0 in the subframe number field value, 1 in the packet order field value, 1 in the packet count field value, and 1 in the stuffing indicator field value do. 2 is displayed in the payload field value of the payload field of the second TP, and FIC data of the last 2 bytes of the first subframe is inserted into the payload byte field. Then, 180 bytes of stuffing data are inserted into the stuffing byte field.

When this process is performed on five subframes in one M / H frame, 10 (= 2x5) MPEG-2 TP format packets are generated and output to the A / V decoder 2015.

The A / V decoder 2015 reconstructs the RS frame from the TPs of the RS frame output from the first packet converter 2007. Further, the A / V decoder 2015 restores the FIC chunk from the TPs of the FIC data output from the second packet converter 2014.

That is, the A / V decoder 2015 uses the field information of the header field of the TP of the RS frame to determine whether the corresponding TP is the TP of the RS frame, the TP of the second M / H service data packet, The number of the TP in the service data packet, whether stuffing data is inserted in the TP, and the like. The RS frame can be restored by collecting the RS frame data from each TP using this information. Further, the A / V decoder 2015 uses the field information of the header area of the FIC to determine whether the corresponding TP is the TP of the FIC, the TP of the sub frame, the number TP of the corresponding sub frame, Whether or not the stuffing data is inserted in the data stream. Using this information, the FIC chunk can be restored by collecting the FIC data from each TP.

Then, the audio and / or video streams selected by the user are separated from the RS frame using the data included in the FIC chunk, and decoded through the respective decoding algorithms. For example, the audio decoding algorithm may be an AC-3 decoding algorithm, an MPEG 2 audio decoding algorithm, an MPEG 4 audio decoding algorithm, an AAC decoding algorithm, an AAC + decoding algorithm, a HE AAC decoding algorithm, an AAC SBR decoding algorithm, Algorithm, and at least one of the MPEG 2 video decoding algorithm, the MPEG 4 video decoding algorithm, the H.264 decoding algorithm, the SVC decoding algorithm, and the VC-1 decoding algorithm can be applied as the video decoding algorithm.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not restrictive of the invention, .

1 is a diagram showing an example of an M / H frame structure for transmission and reception of mobile service data according to the present invention;

2 is a diagram showing an example of a general VSB frame structure;

FIG. 3 is a diagram illustrating a mapping example of a first four-slot position of a subframe for one VSB frame in the spatial domain

FIG. 4 is a diagram showing a mapping example of the first four slot positions of a subframe for one VSB frame in the time domain; FIG.

5 is a diagram showing an embodiment of a structure of a data group after data interleaving according to the present invention.

6 is a diagram showing an example of a data grouping order allocated to one subframe among 5 subframes constituting an M / H frame according to the present invention.

7 is a diagram showing an example of assigning a single parade to one M / H frame according to the present invention.

8 is a diagram showing an example of allocating three parades to one M / H frame according to the present invention.

FIG. 9 is a diagram showing an example in which the allocation process of three parades in FIG. 8 is extended to five subframes

FIG. 10 is a diagram illustrating a data transmission structure according to an embodiment of the present invention, in which signaling data is included in a data group and transmitted

11 is a diagram showing an embodiment of a syntax structure of an FIC chunk header according to the present invention.

12 is a diagram showing an embodiment of a syntax structure of an FIC chunk payload according to the present invention.

13 is a diagram showing an embodiment of a syntax structure of an FIC segment header according to the present invention.

14 is a schematic block diagram of a transmission system according to an embodiment of the present invention

15 is a view showing an embodiment of an RS frame according to the present invention;

16 is a diagram showing an example of an M / H header structure in an M / H service data packet according to the present invention.

17 (a) and 17 (b) are views showing another embodiment of the RS frame according to the present invention.

FIG. 18 is a block diagram showing an embodiment of the service multiplexer of FIG. 14

Fig. 19 is a block diagram showing an embodiment of the transmitter of Fig. 14

FIG. 20 is a block diagram showing an embodiment of the preprocessor of FIG. 19

FIG. 21 is a block diagram showing an embodiment of the M / H frame encoder of FIG. 20

22 is a detailed block diagram illustrating an embodiment of the RS frame encoder of FIG.

23 (a) and 23 (b) are diagrams showing a process in which one or two RS frames are divided into a plurality of potions according to the RS frame mode value according to the present invention, and each potion is assigned to each data group

24A to 24C illustrate an error correction coding and error detection coding process according to an embodiment of the present invention.

25 (a) to 25 (d) are diagrams showing a low-shuffling process in units of superframes according to an embodiment of the present invention

26 (a) and 26 (b) show an example in which one parade is composed of two RS frames

27 (a) and 27 (b) are diagrams showing an embodiment of a process of dividing an RS frame to form a data group according to the present invention

28 is a block diagram showing an embodiment of a block processor according to the present invention

29 is a view showing an embodiment of a convolutional encoder in a block processor according to the present invention;

30 is a diagram showing an example of symbol interleaving of a block processor according to the present invention;

FIG. 31 is a block diagram showing an embodiment of the group formatter of FIG. 20

32 is a block diagram showing an embodiment of a trellis encoder according to the present invention;

33 is a diagram showing an example of allocating a signaling information area to a partial area in a data group according to the present invention

FIG. 34 is a block diagram showing an embodiment of the signaling encoder of FIG. 20

35 is a diagram showing an embodiment of a syntax structure of TPC data according to the present invention.

36 is a diagram showing an example of a transmission scenario of TPC data and FIC data according to the present invention;

37 is a diagram showing an example for controlling power supply in units of a parade according to the present invention;

38 is a diagram showing an example of the arrangement of a training sequence in a data group before Trellis coding according to the present invention;

FIG. 39 is a diagram showing an example of the arrangement of a training sequence in a data group after Trellis coding according to the present invention; FIG.

40 is a block diagram showing an embodiment of a receiving system according to the present invention

FIG. 41 is a detailed block diagram showing an embodiment of the operation controller of FIG. 40

42 is a diagram showing an example of the linear interpolation according to the present invention;

43 is a diagram showing an example of linear extrapolation according to the present invention;

44 is a block diagram showing an embodiment of a channel equalizer according to the present invention;

45 is a detailed block diagram illustrating an embodiment of a block decoder according to the present invention.

46 (a) and 46 (b) are views showing an example of a process of collecting a plurality of potions and constructing one or two RS frames

47 and 48 are diagrams showing an embodiment of an error correction decoding process according to the present invention.

49 is a diagram showing an example of a TP structure for an RS frame according to the present invention;

50 is a diagram showing another example of a TP structure for an RS frame according to the present invention;

51 (a) and 51 (b) are diagrams showing an example in which an RS frame according to the present invention is packetized into packets of the MPEG-2 TP format

52 is a flowchart illustrating an embodiment of a method of packetizing RS frames according to the present invention into packets in MPEG-2 TP format

53 is a view showing an example of a TP structure for FIC according to the present invention;

54 is a view showing another example of the TP structure for FIC according to the present invention;

55 is a diagram showing an example in which the FIC according to the present invention is packetized into packets of the MPEG-2 TP format

Claims (20)

A tuner for receiving a broadcast signal including at least one signal frame; A decoding unit decoding the received broadcast signal and outputting a first packet for transmitting signaling data including a service identifier, information indicating a service state, service protection information, and second packets for transmitting broadcast service data; And And a conversion unit for obtaining the signaling data and the broadcast service data from the first packet and the second packet. The method according to claim 1, Wherein the signal frame further comprises transmission parameters. 3. The method of claim 2, Wherein the transmission parameters are transmitted over a specific area within the at least one signal frame. The method according to claim 1, Wherein the at least one signal frame further includes known data for transmitting a value already known to the broadcast signal receiving apparatus. 3. The method of claim 2, Wherein the transmission parameter data includes code rate information for decoding mobile service data. The method comprising: receiving a broadcast signal including at least one signal frame; Decoding the received broadcast signal and outputting a first packet for transmitting signaling data including service identifier, information indicating a service state, service protection information, and second packets for transmitting broadcast service data; And And obtaining the signaling data and the broadcast service data from the first packet and the second packet. The method according to claim 6, Wherein the signal frame further comprises transmission parameters. 8. The method of claim 7, Wherein the transmission parameters are transmitted over a specific area within the at least one signal frame. The method according to claim 6, Wherein the at least one signal frame further comprises known data for transmitting a value already known in the receiving system. 8. The method of claim 7, Wherein the transmission parameter data includes code rate information for decoding mobile service data. A coding unit for coding the service identifier transmitted through the first packet, the signaling data including the information indicating the service state, the service protection information, and the broadcast service data transmitted through the second packet; And And a transmitter for transmitting a broadcast signal including at least one or more signal frames to which the encoded signaling data and the encoded broadcast service data are allocated. 12. The method of claim 11, Wherein the signal frame further comprises transmission parameters. 13. The method of claim 12, Wherein the transmission parameters are transmitted over a particular area within the at least one signal frame. 12. The method of claim 11, Wherein the at least one signal frame further comprises known data for transmitting a value already known by the broadcast signal receiving apparatus. 13. The method of claim 12, Wherein the transmission parameter data includes code rate information of the encoded broadcast service data. The method comprising: coding a service identifier transmitted through a first packet, information indicating a service status, signaling data including service protection information, and broadcast service data transmitted through a second packet; And And transmitting a broadcast signal including at least one signal frame to which the encoded signaling data and the encoded broadcast service data are allocated. 17. The method of claim 16, Wherein the signal frame further comprises transmission parameter data. 18. The method of claim 17, Wherein the transmission parameters are transmitted over a particular area within the at least one signal frame. 17. The method of claim 16, Wherein the at least one signal frame further comprises known data for transmitting a known value in a broadcast signal receiving apparatus. 18. The method of claim 17, Wherein the transmission parameter data includes code rate information of the encoded broadcast service data.

Images