BR112012028605B1 - METHOD FOR STREAM PROCESSING OF A DIGITAL BROADCASTING TRANSMITTER, DIGITAL BROADCASTING TRANSMITTER, METHOD FOR STREAM PROCESSING OF A DIGITAL BROADCASTING RECEIVER, AND DIGITAL BROADCASTING RECEIVER - Google Patents

Abstract

method for processing stream from a digital broadcast transmitter, digital broadcast transmitter, method for processing stream from a digital broadcast receiver, and digital broadcast receiver. The present invention relates to a method for processing stream for digital broadcast transmitter. the method comprises: flow building step to build a flow, wherein slots of different types are sequentially arranged, wherein mobile data, normal data, and/or new existing mobile data are arranged in different formats in each slot; and a transmission step of encoding and interleaving the stream, and outputting the encoded and interleaved stream as a transmission stream. the flow construction step places new mobile data, training data, and/or dummy data in the orphaned regions between sequential intervals, to which, no data is allocated due to the format difference. thus, streams can be used in a variety of ways.

Description

Technical Field

(0001) The present invention generally relates to a digital broadcast transmitter, a digital broadcast receiver, and methods for building and processing their streams. More particularly, the present invention relates to a digital broadcast transmitter for generating and transmitting a transport stream including normal data and mobile data, a digital broadcast receiver for receiving and processing the transport stream, and thereto. methods.

Previous Technique

(0002) When digital broadcasting is propagated, various electronic devices support a digital broadcasting service. In particular, recently, in addition to devices such as digital broadcast TV and a converter in the home, personal portable devices, for example, mobile phone, navigation, PDA and MP3 player, have a function to support the digital broadcast service.

(0003) Thus, digital broadcasting standards for providing digital broadcasting service for portable devices are under discussion.

(0004) Among them, the ATSC-MH standard is under discussion. The ATSC-MH standard describes a technique for placing and transmitting mobile data in a transport stream, to carry data for conventional digital broadcasting service, that is, normal data.

(0005) Since mobile data is data received and processed by the handheld device, it is processed robustly against errors, compared to normal data, due to the mobility of the handheld device, and included in the transport stream.

(0006) FIG. 1 is a diagram of an example transport flow, including mobile data and normal data.

(0007) FIG. 1A illustrates the flow, in which mobile data and normal data are each placed and multiplexed into their allocated packets.

(0008) The flow of FIG. 1A is converted to a stream of FIG. 1B, by means of interleaving. Referring to FIG. 1B, MH, that is, mobile data can be divided into a region A and a region B, according to the interleaving. Region A indicates a region within a certain range, based on the aggregation of mobile data over a certain size, into a plurality of transmission units, and region B indicates a region excluding region A. Division of region A and region B is merely exemplary, and may be divided differently in some cases. That is, in FIG. 1B, the part not including normal data can be defined as region A, and the part corresponding to the transmission unit including normal data can be defined as region B.

(0009) On the other hand, compared to region A, region B is relatively vulnerable to errors. That is, digital broadcast data can include known data, for example a training sequence, which is correctly demodulated and equalized by a receiver for error correction. As per the conventional ATSC-MH standard, region B does not include known data and is therefore vulnerable to errors.

(00010) Due to the flow structure of FIG. 1, mobile data transmission may be limited. That is, although broadcasting stations and devices supporting the mobile broadcasting service gradually increase, the degradation of flow efficiency is highlighted, due to the fact that the part assigned to normal data is not available in the flow, as constructed in FIG. 1A.

(00011) Thus, a technique is needed to efficiently use the structure of the transport flow.

Detailed Description of the Invention Technical Object of the Invention

(00012) To address the above-discussed deficiencies of the prior art, a main aspect of the present invention is to provide a digital broadcast transmitter, a digital broadcast receiver, and methods for building and processing their streams, to diversify the transmission efficiency of the mobile data and improve the reception performance of a transport stream by distinctly using a packet allocated to normal data in the transport stream.

Construction and Operation of the Invention

(00013) According to one aspect of the present invention, a method for processing a digital broadcast transmitter stream includes generating a stream, wherein a plurality of different format slots are consecutively arranged; stream encoding and interleaving; and outputting the encoded and interleaved stream as a transport stream. Here, generating a stream comprises an arrangement of at least one of the new mobile data, training data, and dummy data in an orphan region generated, due to a format difference between consecutive intervals.

(00014) The orphan region can be one of a first type of orphan region generated at an upper part of an SFCMM interval, when a CMM interval and the SFCMM interval of a block mode 01 are arranged consecutively, or when a complete main interval , comprising only the normal data, and the block mode SFCMM interval 01 are arranged consecutively, a second type of orphan region generated in a later part of the CMM interval, when the block mode SFCMM interval 01 and the CMM interval are arranged consecutively, and a third type of orphan region generated in a body part of the complete major interval, when the 01 block mode SFCMM interval and the complete major interval comprising only the normal data are arranged consecutively.

(00015) The CMM range is a range, which organizes existing mobile data into a first region allocated for existing mobile data, and arranges normal data into a second region allocated for normal data, and

(00016) the SFCMM range is a range, which organizes new mobile data according to a defined mode, at least in part of the whole region, which encompasses the first region and the second region.

(00017) The generation of a stream comprises, when new mobile data is placed in the orphan region, adding signaling data, as to the presence and a type of the new mobile data placed in the orphan region, to the stream.

(00018) Stream encoding comprises, when training data is placed in the orphan region, initializing a Trellis encoder according to the training data and then Trellis encoding the part of the training data.

(00019) According to an aspect of the present invention, a digital broadcast transmitter includes a stream generator for generating a stream, in which a plurality of slots of different formats are consecutively arranged, and an exciter for encoding and interleaving the stream, and emission as a transport stream.

(00020) The flow generator can organize at least one of the new moving data, training data, and dummy data into an orphan region generated by a format difference between consecutive intervals.

(00021) The orphan region can be one of a first type of orphan region generated on top of an SFCMM interval, when a CMM interval and the SFCMM interval of a block mode 01 are arranged consecutively, or when a complete major interval , comprising only the normal data, and the block mode SFCMM interval 01 are arranged consecutively, a second type of orphan region generated in a later part of the CMM interval, when the block mode SFCMM interval 01 and the CMM interval are arranged consecutively, and a third type of orphan region generated in a body part of the complete major interval, when the 01 block mode SFCMM interval and the complete major interval comprising only the normal data are arranged consecutively.

(00022) The CMM range is a range, which organizes existing mobile data into a first region allocated for existing mobile data, and arranges normal data into a second region allocated for normal data, and

(00023) the SFCMM interval is an interval, which organizes the new mobile data, according to a defined mode, at least in part of the whole region, which covers the first region and the second region.

(00024) When new mobile data is placed in the orphan region, the flow generator can add signaling data, relating to presence and a type of the new mobile data placed in the orphan region, to the flow.

(00025) When training data is placed in the orphan region, the driver can initialize a Trellis encoder according to the training data and then encode by Trellis the part of the training data.

(00026) According to an aspect of the present invention, a method for stream processing a digital broadcast receiver includes receiving an encoded and interleaved transport stream, while a plurality of different format slots are consecutively arranged; transport flow demodulation; equalization of the demodulated transport stream; and decoding the new mobile data from the equalized stream.

(00027) The transport stream may include an orphan region generated by a format difference between consecutive intervals, and at least one of the new mobile data, training data, and dummy data may be placed in the orphan region.

(00028) The orphan region can be one of a first type of orphan region generated on top of an SFCMM interval, when a CMM interval and the SFCMM interval of a block mode 01 are arranged consecutively, or when a complete main interval , comprising only the normal data, and the block mode SFCMM interval 01 are arranged consecutively, a second type of orphan region generated in a later part of the CMM interval, when the block mode SFCMM interval 01 and the CMM interval are arranged consecutively, and a third type of orphan region generated in a body part of the complete major interval, when the 01 block mode SFCMM interval and the complete major interval comprising only the normal data are arranged consecutively.

(00029) CMM range is a range, which organizes existing mobile data into a first region allocated for existing mobile data, and arranges normal data into a second region allocated for normal data, and SFCMM range is a range, which organizes the new mobile data, according to a defined mode, in at least part of the whole region, which encompasses the first region and the second region.

(00030) The method for stream processing may further include presence identification and a data type in the orphan region, by decoding the signaling information.

(00031) According to an aspect of the present invention, a digital broadcast receiver includes a receiver for receiving an encoded and interleaved transport stream, while a plurality of different format slots are consecutively arranged; a demodulator to demodulate the transport stream; an equalizer to equalize the demodulated transport stream; and a decoder for decoding the new mobile data from the equalized stream.

(00032) The transport stream may include an orphan region generated by a format difference between consecutive intervals, and at least one of the new mobile data, training data and dummy data, may be placed in the orphan region.

(00033) The orphan region can be one of a first type of orphan region generated on top of an SFCMM interval, when a CMM interval and the SFCMM interval of a block mode 01 are arranged consecutively, or when a complete major interval , comprising only the normal data, and the block mode SFCMM interval 01 are arranged consecutively, a second type of orphan region generated in a later part of the CMM interval, when the block mode SFCMM interval 01 and the CMM interval are arranged consecutively, and a third type of orphan region generated in a body part of the complete major interval, when the 01 block mode SFCMM interval and the complete major interval comprising only the normal data are arranged consecutively.

(00034) The CMM range can be a range, which organizes existing mobile data into a first region allocated for the existing mobile data, and arranges normal data into a second region allocated for the normal data, and

(00035) the SFCMM interval can be an interval, which organizes the new mobile data, according to a defined mode, at least in part of the whole region, which covers the first region and the second region.

(00036) The digital broadcast receiver may further include a signaling decoder to identify the presence and a type of data in the orphan region, by decoding the signaling information.

Effect of the Invention

(00037) According to various embodiments of the present invention as defined above, since the transport stream is constructed and transmitted in various ways, the receiver can receive various mobile data. Brief Description of the Drawings FIG. 1 is a diagram of an example transport flow, according to the ATSC-MH standard, FIGS. 2 to 4 are block diagrams of a digital broadcast transmitter, in accordance with various embodiments of the present invention, FIG. 5 is a block diagram of a frame encoder, FIG. 6 is a block diagram of an RS frame encoder of the frame encoder of FIG. 5, blocks of a block processor, FIG. 8 is a diagram of flow block division, FIG. 9 is a block diagram of a signaling encoder, FIGS. 10 to 13 are diagrams of various Trellis encoders, FIG. 14 is a diagram of a mobile data frame structure, FIGS. 15 to 21 are diagrams of a flow construction, according to various embodiments of the present invention, diagrams of a known pattern of data entry, according to various embodiments of the present invention, a pattern of mobile data organization in a normal data region, according to a first mode, interleaved stream of FIG. 29 to FIG. 31 is a diagram of a pattern of mobile data organization in the normal data region according to a second mode, FIG. 32 is a diagram of the interleaved flow of FIG. 31, FIG. 33 is a diagram of a mobile data organization pattern in the normal data region according to a third mode, FIG. 34 is an interleaved flow diagram of FIG. 33, FIG. 35 is a diagram of a mobile data organization pattern in the normal data region according to a fourth mode, FIG. 36 is a diagram of the interleaved flow of FIG. 35, FIGS. 37 to 40 are diagrams of the mobile data organization pattern, according to different modes of the present invention, FIGS. 41 to 43 are diagrams of various intervals repeatedly arranged in sequence, FIGS. 44 to 47 are diagrams of a block assignment method, in accordance with various embodiments of the present invention, FIG. 48 is a diagram of different embodiments for defining a starting point of an RS frame, FIG. 49 is a diagram of an insertion location of signaling data, FIG. 50 is a data field synchronization construction diagram for carrying the signaling data, FIGS. 51 to 53 are diagrams of a digital broadcast receiver, in accordance with various embodiments of the present invention, FIG. 54 is a stream format, after interleaving, FIG. 55 is a method of pre-signaling the following frame information, FIG. 56 is the flow structure, after interleaving in Scalable Mode 11a, FIG. 57 is the flow structure, before interleaving in Scalable Mode 11a, FIG. 58 is the flow structure, which indicates a first type of orphan region, after interleaving, FIG. 59 is the flow structure, indicating the first type of orphan region, before interleaving, FIG. 60 is the flow structure, which indicates a second type of orphan region, after interleaving, FIG. 61 is the flow structure, indicating the second type of orphan region, before interleaving, FIG. 62 is the flow structure, which indicates a third type of orphan region, after interleaving, FIG. 63 is the flow structure, indicating the third type of orphan region, before interleaving, FIG. 64 is the flow structure, before interleaving in a 00 block mode, FIG. 57 is the flow structure, after interleaving in block 00 mode.

Construction and Operation of the Invention

(00038) The present invention will now be described in greater detail with reference to the accompanying drawings.

Digital Broadcasting Transmitter

(00039) Referring to FIG. 2, the digital broadcast transmitter according to an embodiment of the present invention includes a data preprocessor 100 and a MUX 200.

(00040) Data preprocessor 100 receives and processes mobile data properly, and converts it into a format suitable for transmission.

(00041) The MUX 200 generates a transport stream, including the emission of the mobile data, from the data preprocessor 100. By transmitting normal data together, the MUX 200 generates the transport stream by multiplexing the mobile data and of the normal data.

(00042) The data preprocessor 100 can process to organize the mobile data also in all or part of a packet assigned to the normal data in the entire stream.

(00043) That is, as indicated in FIG. 1, according to ATSC-MH standard, some of the packets are assigned to normal data. In detail, for example, as shown in FIG. 1, the stream can be divided into a plurality of slots on time bases as shown in FIG. 1, and a range can include 156 packets in total. Among them, 38 packets can be assigned to normal data, and the remaining 118 packets can be assigned to mobile data. For ease of understanding, the 118 packets are referred to as a region allocated mobile data, or a first region, and the 38 packets are referred to as a region allocated normal data, or a second region. Normal data indicates various existing data received and processed by the existing TV, and mobile data indicates data received and processed by a mobile device. In some cases, mobile data can be expressed using various terms such as solid data, turbo data, and additional data.

(00044) Data preprocessor 100 can place mobile data into a packet region assigned to mobile data. Separately, data processor 100 may place mobile data in part or all of the packets allocated to normal data. For ease of understanding, the mobile data placed in the data packet assigned to the mobile data is referred to as existing mobile data, and the region assigned to the existing mobile data is referred to as the first region, as mentioned above. In contrast, mobile data placed in the second region, that is, in the packet assigned to the normal data is referred to as new mobile data, or mobile data, for ease of understanding. Existing mobile data and mobile data can be the same data, or different data.

(00045) On the other hand, data preprocessor 100 can organize mobile data into various patterns, according to a frame mode, or mode setting condition. The layout pattern of mobile data will be explained with reference to the drawing.

(00046) The MUX 200 generates the transport stream, by multiplexing the stream issued by the data preprocessor 100 and the normal data.

(00047) FIG. 3 illustrates a controller 310 added to the digital broadcast transmitter of FIG. 2. Referring to FIG. 3, digital broadcast transmitter controller 310 controls the operation of data preprocessor 100 by determining the frame mode setting condition.

(00048) In detail, upon determining that a first frame mode is set, controller 310 controls data preprocessor 100 to place the mobile data in the first region only, rather than placing the mobile data in the entire allocated packet. to normal data. That is, the data preprocessor 100 outputs the stream, including only the existing mobile data. Thus, the MUX 200 places the normal data in the packet assigned to the normal data to thus generate the transport stream.

(00049) On the other hand, by determining that a second frame mode is set, controller 310 controls data preprocessor 100 to place existing mobile data into packets assigned to the mobile data, i.e., in the first region, and also to place the mobile data in at least part of the packets assigned to the normal data, that is, in at least part of the second region.

(00050) In this case, the controller 310 can determine the setting condition of a mode separately provided from the frame mode, i.e. a mode for determining the number of packets to place the mobile data among the packets destined for the normal data. In this way, the controller 310 can control the data preprocessor 100 to place the mobile data in the packets in number corresponding to the mode setting condition among all the packets destined for the normal data.

(00051) Here, the mode can be provided in various styles. For example, the mode can include one or more compatible modes and incompatible modes. Compatible mode indicates a mode, which maintains compatibility with an existing normal data receiver, receiving and processing normal data, and incompatible mode indicates a mode, which does not maintain compatibility.

(00052) More specifically, the compatible mode may include a plurality of compatible modes, which places the new mobile data in at least part of the second region. For example, the compliant mode can be one of the first compliant mode, which places mobile data only in some of the packets assigned to normal data, and the second compliant mode, which places mobile data in all packets destined for normal data.

(00053) Here, the first compatible mode can be a mode, which places the mobile data in only some of the data regions of each of some packets in the second region. That is, the first supported mode can be the mode, which places mobile data in some data regions of some packets, and places normal data in the remaining data regions.

(00054) Alternatively, the first compatible mode can be a mode, which places the mobile data in all data regions of some packets in the second region.

(00055) In addition, the mode can be provided in a wide variety of styles by collective consideration of the number of packets intended for normal data and a size, a type, a transmission time, and a mobile data transmission medium.

(00056) For example, when 38 packets are assigned normal data, as shown in FIG. 1, the first compatible mode may include: 1) a first mode for putting the new mobile data into the 38 packets at a rate of 1/4; 2) a second way to put the new mobile data into the 38 packets at a rate of 2/4; 3) a third way to put the new mobile data into the 38 packets at a rate of 3/4; 4) a fourth way to put the new mobile data in all 38 packets.

(00057) Here, in the first mode, the new mobile data can be put into 11 packets in total, that is, the sum of 2 packets out of 38 packets and 9 packets corresponding to the quotient of the remaining 36 packets divided by 4. In the second mode , the new mobile data can be put into 20 packets in total, that is, the sum of two packets out of 38 packets and 18 packets corresponding to the quotient of the remaining 36 packets divided by 2. In the third mode, the new mobile data can be placed in 29 packages in total, that is, the sum of two packages out of 38 packages and 27 packages, which corresponds to the product of the remaining 36 packages times 3/4. In the fourth mode, new mobile data can be placed into all 38 packets.

(00058) At the same time, the incompatible mode indicates the mode, which can disregard the compatibility with the receiver receiving the normal data, and increase a transmission capacity of the new mobile data. More specifically, the incompatible mode can be a mode, which places the new mobile data even using an MPEG header and an RS parity region of the first region in addition to the entire second region.

(00059) As a result, data preprocessor 100 of FIG. 2 or FIG. 3 can generate the transport stream, placing the new mobile data, according to the following different modes. 1) a first way to put new mobile data into 11 packets out of 38 packets assigned to normal data, 2) a second way to put new mobile data into 20 packets out of 38 packets assigned to normal data, 3) a third mode to put new mobile data in 29 packets out of 38 packets assigned to normal data, 4) a fourth mode to put new mobile data in all 38 packets assigned to normal data, 5) a fifth mode to put new mobile data in all the 38 packets allocated to the normal data, and a region corresponding to the MPEG header and the parity of the region allocated to the existing mobile data.

(00060) Here, although the fifth mode is known as the incompatible mode, and the first through fourth modes are known as the compatible modes, for ease of understanding, the name of each mode may vary. Furthermore, although the five modes in total, including the four compatible modes and one incompatible mode, are described in the above embodiment, the number of compatible modes may vary. For example, the first to third modes can be used as the compatible modes, and the fourth mode can be set to the fifth mode, that is, to the incompatible mode.

(00061) On the other hand, data preprocessor 100 can input known data in addition to mobile data. The data indicates a known sequence, which is normally known, to the digital broadcast transmitter and the digital broadcast receiver. The digital broadcast receiver can receive the known data from the digital broadcast transmitter, identify a difference from a pre-known sequence, and then detect error correction. Known data can be expressed differently, such as training data, training sequence, reference signal, and additional reference signal. Here, the term "known data" is applied.

(00062) The data preprocessor 100 can insert at least one of the mobile data and the known data into different parts of the total transport stream, thus improving reception performance.

(00063) That is, in the flow of FIG. 1B, the MH, that is, the mobile data is collected in region A and formed in region B, in a conical shape. Therefore, region A can be referred to as a body region, and region B can be referred to as an upper/posterior region. In the related art, the upper/posterior region does not contain the known data and therefore does not perform well compared to the body region data.

(00064) Thus, the data preprocessor 100 inserts the known data into a suitable location so that the known data can be placed in the top/back region. Known data can be arranged as a long training sequence, in which data of a certain size is continued, or it can be distributed discontinuously.

(00065) Mobile data and known data can be entered in various ways, according to embodiments, which will be explained in detail with reference to the drawings. However, a detailed structure of the digital broadcast transmitter is explained first.

(00066) Example of Detailed Construction of Digital Broadcasting Transmitter

(00067) FIG. 4 is a detailed block diagram of the digital broadcast transmitter, according to an embodiment of the present invention. Referring to FIG. 4, the digital broadcast transmitter may include a normal processor 320 and an exciter 400, in addition to the data preprocessor 100 and the MUX 200. Therein, a part, including the data preprocessor 100, the normal processor 320 , and the MUX 200, can be referred to as a flow generator, for ease of understanding.

(00068) Although controller 310 of FIG. 3 is omitted from FIG. 4, it is understood that controller 310 may be included in the digital broadcast transmitter. Also, in some cases, some components of the digital broadcast transmitter of FIG. 4, may be deleted, or new components may be added, and the order of arrangement and the number of components may vary.

(00069) Referring to FIG. 4, the normal processor 320 receives and converts the normal data into a format suitable for generating the transport stream. That is, the current digital broadcast transmitter generates and transmits the transport stream, including normal data and mobile data, and the receiver to receive normal data must be able to receive and process normal data properly. Therefore, the normal processor 320 sets a packet interval and a PCR of the normal data (which may be referred to as main service data) in the format suitable for the MPEG/ATSC standard, which is used to decode the normal data. Its detailed description is disclosed in Annex B of the ATSC-MH and is therefore omitted here.

(00070) Data preprocessor 100 includes frame encoder 110, block processor 120, group formatter 130, packet formatter 140, and signaling encoder 150.

(00071) Frame encoder 110 performs RS frame encoding. More specifically, frame encoder 110 receives a single service and builds a predefined number of RS frames. For example, when the only service is an M/H set unit including a plurality of M/H stops, a certain number of RS frames are constructed for each M/H stop. In particular, the frame encoder 110 randomly chooses the incoming mobile data, performs RS - CRC encoding, divides each RS frame according to a predefined frame mode, and generates a certain number of RS frames.

(00072) FIG. 5 is a block diagram of frame encoder 110. Referring to FIG. 5, frame encoder 110 includes an input DEMUX 111, a plurality of frame encoders RS 112-1 to 112M, and an output MUX 113.

(00073) When the mobile data of a given service unit (eg the M/S set) is the input, the input DEMUX 111 demultiplexes the mobile data into a plurality of sets, for example into a primary set and a secondary set, according to predefined construction information, i.e. the frame mode, and output them to frame encoders RS 112-1 to 112-M. The RS 112-1 to 122-M frame encoders each perform randomization, RS-CRC encoding, and division of the input sets, and output the sets to the output MUX 113. The output MUX 113 generates a primary part of RS frames and a secondary part of RS frames, by multiplexing the frame parts outputted by RS frame encoders 112-1 to 112-M. In this case, only the primary part of RS frames can be output according to the frame mode setting condition.

(00074) FIG. 6 is a block diagram of an RS frame encoder that can be implemented using one of the RS frame encoders 112-1 to 112-M. Referring to FIG. 6, frame encoder 112 includes a plurality of M/H random number generators 112-1a and 112-1b, a plurality of RS CRC encoders 112-2a and 112-2b, and a plurality of RS frame dividers 112- 3a and 112-3b.

(00075) When the primary M/H set and the secondary M/H set are received from the 111 input DEMUX, the M/H random number generators 112-1a and 112-1b randomize, and the RS-CRC encoders 112-2a and 112-2b RS-CRC encode the randomized data. RS frame dividers 112-3a and 112-3b appropriately divide the data to be encoded into blocks, and output the divided data to the output MUX 113, so that the block processor 120 disposed at the rear end of the frame encoder 110 can properly encode the data in blocks. The output MUX 113 suitably combines and multiplexes the frame parts and then outputs the frame parts to block processor 120 so that block processor 120 can encode them into blocks.

(00076) Block processor 120 encodes, i.e. block encodes, the stream outputted by frame encoder 110 based on the unit of blocks.

(00077) FIG. 7 is a block diagram of block processor 120.

(00078) Referring to FIG. 7, block processor 120 includes a first converter 121, a byte-to-bit converter 122, a convolution encoder 123, a symbol interleaver 124, a symbol-to-byte converter 125, and a second converter 126.

(00079) The first converter 121 converts RS frame input from frame encoder 110 into blocks. That is, the first converter 121 combines the mobile data in the RS frame according to a predefined block mode and outputs a Convolutional Serial Concatenated Code (SCCC) block.

(00080) For example, when the block mode is "00", a single M/H block is converted to a single SCCC block.

(00081) FIG. 8 is a diagram of the M/H blocks divided from the moving data, based on blocks. Referring to FIG. 8, a mobile data unit, for example an M/H group can be divided into 10 blocks B1 to B10. When block mode is "00", blocks B1 to B10 are output as SCCC blocks. When the block mode is "01", two M/H blocks are combined and output as a single SCCC block. The matching pattern can be set in a number of ways. For example, B1 and B6 are merged to form an SCB1 block, and B2 and B7, B3 and B8, B4 and B9, and B5 and B10 are merged to form SCB2, SCB3, SCB4 and SCB. According to other block modes, blocks can be combined in various ways and numbers.

(00082) Byte to bit converter 122 converts the SCCC block, from byte unit to bit unit. This is because the 123 convolutional encoder operates on a bit basis. Thus, the convolutional encoder 123 convolutionally encodes the converted data.

(00083) Then, symbol interleaver 124 interleaves the symbol. Symbol merging can be performed in the same way as block merging. The interleaved symbol data is converted into bytes by the symbol to byte converter 125, re-converted into M/H blocks by the second converter 126, and then outputted.

(00084) The group formatter 130 receives the stream processed by the block processor 120 and formats the stream, on a group basis. More specifically, group formatter 130 maps the data outputted by block processor 120 to suitable locations in the stream, and adds known data, signaling data, and initialization data. In addition, the group formatter 130 adds a placeholder byte to normal data, an MPEG-2 header, and a non-systematic RS parity, and a dummy byte for the format consistency of the groups.

(00085) The signaling data indicates various information needed for transport stream processing. The signaling data can be suitably processed by the signaling encoder 150 and then provided to the group formatter 130.

(00086) A Transmission Parameters Channel (TPC) and a Fast Information Channel (FIC) can be used to transmit the mobile data. TPC is used to provide various parameters such as various Early Error Correction (FEC) mode information and M/H frame information. FIC is used for fast acquisition of receiver services, and includes 'cross layer' information between a physical layer and an upper layer. When the TPC information and the FIC information are provided to the signaling encoder 150, the signaling encoder 150 properly processes the provided information, and provides it as the signaling data.

(00087) FIG. 9 is a block diagram of signaling encoder 150.

(00088) Referring to FIG. 9, signaling encoder 150 includes an RS to TPC encoder 151, a MUX 152, an RS to FIC encoder 153, a block interleaver 154, a random signaling generator 155, and a PCCC encoder 156. the TPC 151 forms a TPC codeword by RS encoding the TPC input data. The RS encoder for the FIC 153 and the block interleaver 154 RS encode and block interleave the input data of the FIC to form an FIC codeword. The MUX 152 generates a series of sequences by placing the FIC codeword after the TPC codeword. The generated sequence is randomized by the signaling random generator 155, Convolutional Concatenated Code in Parallel (PCCC) encoded by the PCCC encoder 156, and then outputted to the group formatter 130 as the signaling data.

(00089) At the same time, the known data indicates the commonly known sequence for the digital broadcast receiver as described above. Group formatter 130 inserts the known data into a suitable location according to a control signal provided by a separate component (eg controller 310) so that the known data is interleaved by exciter 400 and then , arranged in a suitable place in the flow. For example, known data can be inserted in a suitable location so as to be placed evenly in region B of the flow structure of FIG. 1B. The group formatter 130 can determine the place of insertion of known data, considering an interleaving rule, by itself.

(00090) At the same time, initialization data indicates data to the Trellis encoder 450 of exciter 400 to initialize internal memories at a suitable time, which will be described in detail in relation to exciter 400.

(00091) The group formatter 130 may include a group formatter (not shown) for generating the stream in group format by inserting various regions and signals into the stream, and a data deinterleaver for deinterleaving the generated stream in the format of groups.

(00092) The data deinterleaver rearranges the data in the reverse order of the interleaver 430 disposed at the rear end, with reference to the stream. The stream deinterleaved by the data deinterleaver can be provided to the packet formatter 140.

(00093) The packet formatter 140 can remove various space reservations generated by the group formatter 130 in the stream, and add the MPEG header having a packet identifier (PID) of the mobile data. Thus, the packet formatter 140 generates the stream in a predefined number of packets for each group. For example, packet formatter 140 can output 118 TS packets.

(00094) As such, the data preprocessor 100 is implemented in various ways to generate the mobile data in a suitable way. In particular, when a plurality of mobile services are provided, data preprocessor 100 may include a plurality of components.

(00095) The MUX 200 generates the transport stream by multiplexing the normal stream processed by the normal processor 320 and the mobile stream processed by the data preprocessor 100. The emission of the transport stream from the MUX 200 comprises the normal data and mobile data, and may further include known data in order to improve reception performance.

(00096) Exciter 400 encodes, interleaves, encodes by Trellis, and modulates the transport stream generated by the MUX 200, and generates the processed transport stream. In some cases, exciter 400 may be referred to as a data post-processor.

(00097) Referring to FIG. 4, exciter 400 includes a random generator 410, an RS 420 encoder, an interleaver 430, a parity surrogate 440, a Trellis encoder 450, an RS 460 recoder, a sync MUX 470, a pilot introducer 480 , an 8-VSB 490 modulator, and an RF 495 up-converter.

(00098) The random generator 410 randomly chooses the transport stream emission of the MUX 200. The random generator 410 can basically perform the same function as a random generator, according to the ATSC standard.

(00099) Random generator 410 can apply an XOR operation with the MPEG header of the mobile data and the complete normal data with a Pseudo-Random Binary Sequence (PRBS) of maximum 16 bits length, but may not apply the XOR operation. to one byte of mobile data payload. Still, a PRBS generator can continue changing a shift register. That is, the random generator 410 ignores the mobile data pay byte.

(000100) The RS 420 encoder RS encodes the randomized stream.

(000101) More specifically, when the part corresponding to the normal data is entered, the RS 420 encoder performs systematic RS encoding in the same way as the conventional ATSC system. That is, the RS 420 encoder adds a 20-byte parity to the end of each 187-byte packet. In contrast, when the part corresponding to the mobile data is entered, the RS encoder 420 performs non-systematic RS encoding. In this case, the 20 bytes of FEC RS data obtained by unsystematic RS encoding are placed in a certain byte parity location within each mobile data packet. In this way, the data is compatible with a conventional receiver of the ATSC standard.

(000102) The interleaver 430 interleaves the stream encoded by the RS 420 encoder. The interleaving can be performed in the same way as in the conventional ATSC system. That is, the interleaver 430 can sequentially select a plurality of lanes, including different numbers of shift registers via a switch, and write and read the data, to thereby perform the interleaving, as many times as the shift registers in the lane.

(000103) The 440 parity surrogate corrects the parity, which is changed according to the Trellis 450 encoder memory initialization at the rear end.

(000104) That is, the Trellis encoder 450 receives and Trellis encodes the interleaved stream. The Trellis 450 encoder uses 12 Trellis encoders in general. Therefore, the Trellis encoder 450 can use a DEMUX to split the stream into 12 independent streams, and output the streams to the Trellis encoders, respectively, and a MUX to combine the Trellis encoded streams, by the Trellis encoders into the single stream.

(000105) Trellis encoders each use a plurality of internal memories to perform Trellis encoding, by logically operating and outputting a new input value and a pre-stored value to the internal memory.

(000106) As described above, the transport stream can include the known data. The known data is the sequence normally known to the digital broadcast transmitter and the digital broadcast receiver. The digital broadcast receiver can determine the degree of error correction by checking the status of known received data. As such, the known data must be transmitted, as it is known, to the receiver. However, since the value stored in the Trellis encoder's internal memory is unknown, the internal memories need to be initialized to an arbitrary value, prior to inputting known data. Therefore, the Trellis encoder 450 initializes the memory, prior to Trellis encoding the known data. Memory initialization may be referred to as resetting Trellis.

(000107) FIG. 10 is a diagram of one of the plurality of Trellis encoders provided in Trellis encoder 450.

(000108) Referring to FIG. 10, the Trellis encoder includes first and second MUXs 451 and 452, first and second adders 453 and 454, first and third memories 455, 456 and 457, and a mapper 458.

(000109) The first MUX 451 receives data N from the stream and an I value stored in the first memory 455, and generates a value, ie, N or I, in accordance with an N/I control signal. More specifically, when a value corresponding to a section of initialization data is entered, a control signal instructing to select I is applied, and the first MUX 451 issues I.N is issued in other sections. Likewise, the second MUX 452 issues I only to the boot data section.

(000110) Therefore, for the non-initialization data section, the first MUX 451 outputs the interleaved value for the back end, and the output value is inserted to the first adder 453 together with a pre-stored value for the first memory 455. The first adder 453 applies the logical operation, for example, the XOR, to the input values and thus outputs Z2. At this time, in the initialization data section, the value stored in the first memory 455 is selected and output by the first MUX 451. Therefore, as the same two values are entered for the first adder 453, the value of the logic operation is constant. That is, the XOR produces the output 0. Since the output value of the first adder 453 is inserted into the first memory 455, the value of the first memory 455 is initialized to 0.

(000111) In the initialization data section, the second MUX 452 selects and outputs a value stored in the third memory 457. The send value is entered into the second adder 454, along with a value stored in the third memory 457. The adder 454 operates logically the same two values, and outputs the result to the second memory 456. Since the input values of the second adder 454 are the same, the logical operation value, for example, the XOR of the same values inserts 0 into the second memory 456. Thus, the second memory 456 is initialized. In contrast, the value stored in the second memory 456 is shifted and stored in the third memory 457. Consequently, when the next initialization data is entered, the current value of the second memory 456, i.e. zero is entered into the third memory 457, to initialize the third memory 457.

(000112) The mapper 458 receives and maps the send value from the first adder 453, the send value from the second MUX 452, and the send value from the second memory 456, onto a corresponding symbol R value, and outputs the mapped values . For example, when Z0, Z1 and Z2 are output as 0, 1, and 0, the mapper 458 outputs the -3 symbol.

(000113) Since the RS 420 encoder is located before the Trellis 450 encoder, parity has already been added to the value issued to the Trellis 450 encoder. So when the Trellis 450 encoder is initialized and a data value is changed, it is also need to change the parity.

(000114) The RS-460 re-encoder generates a new parity by changing the value of the initialization data section using the X1' and X2' output of the Trellis 450 encoder. The RS 460 re-encoder can be referred to as an encoder RS not systematic.

(000115) On the other hand, although memory is initialized to zero in FIG. 10, the memory can be initialized to a non-zero value.

(000116) FIG. 11 is a diagram of another Trellis encoder.

(000117) With reference to FIG. 11, the Trellis encoder may include first and second multiplexer MUXs 451 and 452, first to four adders 453, 454, 459-1, and 459-2, and first to third memories 455, 456, and 457. Mapper 458 is omitted in FIG. 11.

(000118) As constructed above, the first MUX 451 can output a stream input value X2, and a value from the third adder 459-1. I_X2 and a storage value from the first memory 455 are output to the third adder 459-1. The I_X2 indicates a memory reset value entered from the outside. For example, in order to initialize the first memory 455 to 1, I_X2 is entered as 1. When the storage value of the first memory 455 is zero, the output value of the third adder 459-1 is 1 and therefore the first MUX 451 outputs 1. Therefore, the first adder 453 XORs the output value 1 of the first MUX 451 and the storage value 0 of the first memory 455, and stores the value of result 1 in the first memory 455. As a result, the first memory 455 is initialized to 1.

(000119) Likewise, the second MUX 452 selects and generates the send value of the fourth adder 459-2 in the initialization data section. The fourth adder 459-2 produces the XOR value of the memory reset value I_X1 entered from the outside and the third memory 457. For example, when the second and third memories 456 and 457 store values 1 and 0, respectively, and the two memories need to be initialized to 1 and 1, respectively, the second MUX 452 outputs 1, which is the XOR value of the value 0 stored in the third memory 457 and the value I_X1 1. The output of 1 is processed by XOR with 0 stored in the third memory 457 in the second adder 454, and the resulting value 1 is inserted into the second memory 456. At the same time, the original value 1 stored in the second memory 456 is shifted to the third memory 457, to set the third memory 457 to 1. In this state, when the second I_X1 is also entered as 1, it is processed by XOR with the value 1 from the third memory 457, and the resulting value 0 is issued by the second MUX 452. When the second adder 454 processes by XOR 0 issued by the according to MUX 452 and 1 stored in the third memory 457, the result value 1 is an entry 1 in the second memory 456, and the value 1 stored in the second memory 456 is shifted and stored in the third memory 457. As a result, the second and third memories 456 and 457 can be initialized as 1.

(000120) FIGS. 12 and 13 are diagrams of the Trellis encoder, in accordance with various exemplary embodiments.

(000121) Referring to FIG. 12, the Trellis encoder may further include third and fourth MUXs 459-3 and 459-4, in addition to the structure of FIG. 11. The third and fourth MUXs 459-3 and 459-4 can output the send value of the first and second adders 453 and 454, or the I_X2 and I_X1 values, according to their N/I control signal. Thus, the first through third memories 455, 456, and 457 can be initialized with the desired values.

(000122) FIG. 13 shows the most simplified Trellis encoder. Referring to FIG. 13, the Trellis encoder may include first and second adders 453 and 454, first and third memories 455, 456, and 457, and third and fourth MUXs 459-3 and 459-4. Therefore, the first to third memories 455, 456, and 457 can be initialized, in accordance with the input I_X1 and I_X2 values in the third and fourth MUXs 459-3 and 459-4. That is, referring to FIG. . 13, I_X2 and I_X1 are inputs to the first memory 455 and the second memory 456, and become the value of the first memory 455 and the value of the second memory 456.

(000123) Further detailed descriptions of the Trellis encoder operation of Figs. 12 and 13 are omitted.

(000124) Referring again to FIG. 4, the sync MUX 470 adds a field sync and a segment sync to the Trellis encoded stream by the Trellis encoder 450.

(000125) As described above, when the data preprocessor 100 places and uses the mobile data evenly in the packets destined for the existing normal data, it is necessary to inform the receiver about the new mobile data. The existence of new mobile data can be notified in several ways, one of which is a method using field synchronization, which will be described in detail later.

(000126) Pilot inserter 480 inserts a pilot into the transport stream, which is processed by the sync MUX 470, and the 8-VSB modulator 490 modulates the transport stream according to an 8-VSV modulation scheme. The 495 RF up-converter converts the modulated stream into a higher band RF signal for transmission, and the converted signal is transmitted through an antenna.

(000127) As described above, the transport stream is transmitted to the receiver, including normal data, mobile data, and known data.

(000128) FIG. 14 is a diagram of the unit structure of the mobile data frame of the transport stream, i.e., the M/H frame. Referring to FIG. 14A, an M/H frame can be 968 ms in size in total, as a function of time, and can be divided into 5 sub-frames as shown in FIG. 14B. A subframe can have a time unit of 193.6 ms. As shown in FIG. 14C, each subframe can be divided into 16 intervals. Each interval has the unit of time of 12.1 ms and can include 156 transport stream packets in total. As described above, 38 packets of them are assigned to normal data, and the remaining 118 packets are assigned to mobile data. That is, an M/H group includes 118 packages.

(000129) At this time, the data preprocessor 100 can place the mobile data and the known data also in packets intended for normal data to thereby improve the mobile data transmission efficiency and reception performance.

(000130) [Various embodiments of altered transport flow]

(000131) FIGS. 15 to 21 are transport flow diagrams in accordance with various embodiments of the present invention.

(000132) FIG. 15 shows, as the most simplified modified structure, the flow structure interleaved with the mobile data placed in the conventional packets assigned to the normal data, i.e. in the second region. In the flow of FIG. 15, the known data can be placed in the second region along with the mobile data.

(000133) Therefore, even the unused portion for mobile data in conventional ATSC-MH, ie 38 packets, can be used for mobile data. Furthermore, since the second region is used independently of the existing mobile data region (i.e., the first region), one or more services may be additionally provided. When new mobile data needs to be used for the same service as existing mobile data, data transmission efficiency can be further improved.

(000134) On the other hand, when new mobile data and known data are transmitted, as shown in FIG. 15, the presence and location of new mobile data and known data can be notified to the receiver using the signaling data or field synchronization.

(000135) Mobile data and known data can be organized by data preprocessor 100. More specifically, group formatter 130 of data preprocessor 100 can organize mobile data and known data, also into 38 packets. .

(000136) In FIG. 15, the known data, in the form of 6 long training sequences, is placed in the body region where existing mobile data is collected. Furthermore, because of the robustness to error of the signaling data, the signaling data is interposed between the first and second long training sequences. In contrast, in packets intended for normal data, known data may not only be arranged, such as the long training sequence type, but also distributed.

(000137) In FIG. 15, the dashed area 1510 indicates an MPEG header portion, the dashed area 1520 indicates an RS parity region, the dashed area 1530 indicates a dummy region, the dashed area 1540 indicates the signaling data, and the dashed area 1550 indicates the boot data. Referring to FIG. 15, the initialization data precedes the known data. Reference number 1400 indicates M/H data from the (N-1)-th range, reference number 1550 indicates M/H data from the N-th range, and reference number 1600 indicates M/H data from the (N) +1)-th range.

(000138) FIG. 16 represents the structure of the transport stream for transmitting the mobile data and the known data using part of the first region allocated to the existing mobile data, together with the packets destined for the normal data, i.e. the second region.

(000139) Referring to FIG. 16, in region A, i.e. in the body region where the existing mobile data is gathered, the known data is arranged in the form of 6 long training sequences. Furthermore, the known data is arranged in the form of the long training sequences, also in region B. To organize the data known as the long training sequences in the region, not only the 38 packets, but also some of the 118 packets assigned to the existing mobile data includes known data. New mobile data is placed in the remaining region of the 38 packets not including the known data. Therefore, region B error correction performance can be improved.

(000140) On the other hand, as the known data is newly added to a part of the region for the existing mobile data, it is possible to add information regarding the new location of the known data, to the existing signaling data, or process the header of the existing mobile packet, in which the new known data is entered in a format unrecognizable by the conventional mobile data receiver, such as in a null packet format, for the sake of compatibility with the existing mobile data receiver. Thus, the existing mobile data receiver does not cause a malfunction because it does not recognize the newly added known data at all.

(000141) FIG. 17 represents the stream construction, in which at least one of the mobile data and the known data is placed equally in place, such as MPEG header, RS parity, at least part of the dummy data, and existing M/H data. In this case, a plurality of new mobile data can be placed, according to the location.

(000142) That is, compared to FIG. 15, FIG. 17 shows that new mobile data and new known data are formed in MPEG header, RS parity, and part of the dummy data. The mobile data inserted for those parties and the mobile data inserted in the normal data packet can be different or the same data.

(000143) In addition, new mobile data can be spread across the existing mobile data region.

(000144) The flow, constructed as in FIG. 17, can further increase the transmission efficiency of mobile data and known data with respect to FIGS. 15 and 16. In particular, a plurality of mobile data services can be provided.

(000145) The flow, constructed as in FIG. 17, can notify whether or not new mobile data is included, by including new signaling data in the new mobile data region, using existing signaling data, or field synchronization.

(000146) FIG. 18 represents the flow, which organizes the new mobile data and the known data, not only in the second region, but also in region B, that is, in the first region corresponding to the secondary service part.

(000147) As shown in FIG. 18, the entire flow is divided into a primary service region and a secondary service region. The primary service region may be referred to as a body region, and the secondary service region may be referred to as an upper/posterior region. Since the upper/posterior region does not include the known data and includes data from different intervals, its performance is inferior to that of the body region. Therefore, the known data can be organized and used in conjunction with the new mobile data in that region. Here, although the known data can be arranged in the form of, but not limited to, long training sequences, as in the body region, the known data can be distributed or arranged, as a combination of the long training sequence and the sequence. distributed.

(000148) However, when the existing mobile data portion is used as the new mobile data region, the packet header including the new mobile data or the known data from the existing mobile data region may be generated in the format unrecognizable by the existing receiver to maintain compatibility with the receiver in accordance with the conventional ATSC-MH standard.

(000149) Alternatively, existing signaling data, or new signaling data, may notify this information.

(000150) FIG. 19 represents an example of the transport stream for transmitting new mobile data and known data using the entire conventional region of normal data, the MPEG header, the RS parity region, at least part of the dummy data of the existing mobile data, and the region of existing mobile data. FIG. 17 depicts the transmission of new mobile data other than new mobile data located in the normal data region using those regions, while FIG. 19 represents the transmission of the new mobile data using the entire normal data region and these regions.

(000151) FIG. 20 represents the transport stream for carrying new mobile data and known data using the entire B region, the normal data region, the MPEG header, the RS parity region, and at least part of the dummy data of the existing mobile data.

(000152) As noted above, it is preferable not to recognize the party, including new mobile data and known data, for the purpose of compatibility with the existing receiver.

(000153) FIG. 21 represents the transport flow, when the dummy data of the region used in the existing mobile data is replaced by parity, or the new mobile data region, and the mobile data and the known data are placed using the replaced dummy data and the region of normal data. Referring to FIG. 21, the dummy data of the (N-1)th interval and the dummy data of the Nth interval are shown.

(000154) As described above, Figs. 15 through 21 illustrate the flow after interleaving. The data preprocessor 100 organizes the mobile data and the known data in appropriate places so as to construct the flow of FIGS. 15 to 21, after the interleaving.

(000155) More specifically, the data preprocessor 100 organizes the mobile data packets into the normal data region, that is, into the 38 packets in a given pattern in the flow of FIG. 1A. In this case, mobile data can be placed in the entire payload of the packet, or in some region of the packet. Furthermore, in addition to the normal data region, the mobile data can be placed in the region corresponding to the top or the back of the mobile region existing after the interleaving.

(000156) At the same time, the known data can be arranged in each mobile data packet, or in the normal data packet. In this case, the known data can be arranged continuously or intermittently in a vertical direction in FIG. 1A, so that the known data, after interleaving, is arranged as the long training sequence, or similar long training sequence, in a horizontal direction.

(000157) Furthermore, in addition to a long training sequence, known data can be distributed, as mentioned above. Below, several examples of the known data arrangement are described.

(000158) [Disposition of known data]

(000159) As described above, the known data is placed in the proper location by the group formatter 130 of the data preprocessor 100 and then interleaved by the interleaver 430 of the exciter 400 along with the flux. FIGS. 22 to 28 are diagrams of a known method of organizing data, according to various embodiments.

(000160) FIG. 22 represents the known data, distributed, arranged with the long training sequence existing in the body region, and the additional arrangement of the known data in the conical part of the upper/posterior region. As such, by keeping the conventional known data and the recent addition of the known data, synchronization, channel estimation performance, and receiver equalization performance can be improved.

(000161) The known data arrangement of FIG. 22 is performed by the group formatter 130. The group formatter 130 can determine the insertion location of the known data by considering the interleaving rule of the interleaver 430. The interleaving rule may vary according to various embodiments. By knowing the merge rule, the group formatter 130 can correctly determine the location of the known data. For example, when known data of a certain size is inserted in the payload part, or in a separate field every 4 packets, the known data, distributed in a uniform pattern, can be obtained through interleaving.

(000162) FIG. 23 represents the stream, according to another known data entry method.

(000163) Referring to FIG. 23, the known distributed data of the conical region is not placed, and the known distributed data is placed only in the body region together with the long training sequence.

(000164) Next, FIG. 24 represents the flow, which reduces the length of the long training sequence, compared to FIG. 23, and organizes the known, distributed data as much as the reduced number. Consequently, data efficiency remains the same, and Doppler control performance can be improved.

(000165) FIG. 25 represents the stream, according to yet another known data entry method.

(000166) Referring to FIG. 25, the first sequence of the 6 long training sequences in the body region is maintained, and the remaining sequences are replaced by the known distributed data. Therefore, initial synchronization and channel estimation performance can be maintained, thanks to the first long training sequence, where the body region is started, and the Doppler shift performance can be improved.

(000167) FIG. 26 shows a stream according to yet another known data entry method. Referring to FIG. 26, the second sequence of the 6 long training sequences is replaced by known distributed data.

(000168) FIG. 27 shows that the known, distributed, substituted data and signaling data are alternately arranged in the flow of FIG. 26.

(000169) FIG. 28 shows a stream, which adds the known distributed data not only to the upper region but also to the posterior region.

(000170) As noted above, known data can be arranged in various ways.

(000171) On the other hand, when mobile data is newly allocated to packets destined for normal data, the distribution pattern can change variably. Hereinafter, the transport flow is explained, including mobile data arranged in various ways according to a mode.

(000172) [Mobile Data Arrangement]

(000173) Data preprocessor 100 checks frame mode setting condition. Frame mode can be different. For example, a first frame mode may use packets destined for normal data, such as normal data, and only use packets destined for existing mobile data, such as mobile data, and a second frame mode may even use at least part of packets assigned to normal data, such as mobile data. Such a frame mode can be arbitrarily defined considering the intent of a digital broadcast transmission provider and a transmission and reception medium.

(000174) When determining the first frame mode, which organizes normal data into all packets destined for normal data, data preprocessor 100 places mobile data only in packets destined for mobile data, in the same way as in ATSC -conventional MH.

(000175) In contrast, by determining that the second frame mode has been set, data preprocessor 100 re-determines the mode setting state. The mode determines the pattern and number of packets, to organize the mobile data into packets assigned to normal data, that is, into the second region. Various modes can be provided, according to different embodiments.

(000176) More specifically, the mode can be set to one of the mode, which arranges mobile data into some of the packets assigned to normal data, mode, which arranges mobile data into all packets intended for normal data, and incompatible mode, which arranges the mobile data into all packets destined for the normal data, and arranges the mobile data in the RS parity region and the header region provided for compatibility with the receiver, to receive the normal data. In this case, the mode, which organizes the mobile data only in some of the packets, can be set differently for a mode, to use the data region of some packets, i.e. the entire load region as the mobile data, or a mode to use only part of the load region as mobile data.

(000177) Specifically, when 38 packets correspond to the second region assigned to normal data, the mode is 1) a first mode to organize the new mobile data into 11 packets out of the 38 packets assigned to normal data, 2) a second mode to organize the new mobile data in 20 packets out of 38 packets assigned to normal data, 3) a third mode to organize new mobile data in 29 packets out of 38 packets assigned to normal data, 4) a fourth mode to organize new mobile data in all 38 packets assigned to normal data, 5) a fifth way to organize the new mobile data into all 38 packets assigned to normal data and into regions corresponding to MPEG header and parity between region allocated to existing mobile data.

(000178) As above, the fifth mode may be referred to as an incompatible mode, and the first through fourth modes may be referred to as compatible modes. A supported mode type and the number of packages in each mode may vary.

(000179) FIG. 29 represents a flow when the group formatter 130 organizes the mobile data and the known data according to the first mode in one embodiment, in which the new mobile data is transmitted using the second region and the upper/later region.

(000180) Referring to FIG. 29, the new mobile data 2950 and the known data 2960 are placed in the second region in a certain pattern, and the new mobile data and the known data are placed in a portion 2950 corresponding to the upper/later region 2950 in addition to the second region.

(000181) In addition, an MPEG header 2910, known data 2920, signaling data 2930, existing mobile data 2940, and dummy data 2970 are arranged vertically in the stream. In this arrangement, when normal data fills the empty space in the second region and then encoding and interleaving are applied, the flow in FIG. 30 is generated.

(000182) FIG. 30 shows a stream after interleaving in the first mode.

(000183) Referring to FIG. 30, new mobile data 3010 and known data 3030 are placed in part of a packet region assigned to normal data. In particular, the known data is discontinuously arranged in the second region, thus forming long training sequences similar to the long training sequences of the body region.

(000184) Mobile data 2950, placed in the portion corresponding to the top/back region in FIG. 29, correspond to mobile data 3020 placed in the upper/back region of FIG. 30, and the known data 2955, placed together with the mobile data 2950, form the known data 3030 of similar long training sequences together with the known data in the second region of FIG. 30.

(000185) FIG. 31 shows a flow when group formatter 130 places mobile data and known data according to the second mode into an embodiment where new mobile data is transmitted using the second region and the upper/later region.

(000186) In FIG. 31, the rate of mobile data included in the second region is higher than that of FIG. 29. Compared to FIG. 29, the portion occupied by the mobile data and the known data is increased in FIG. 31.

(000187) FIG. 32 illustrates the interleaved stream of FIG. 31. Referring to FIG. 32, the known data in the second region forms a similar long training sequence denser than the known data in the second region of FIG. 30.

(000188) FIG. 33 shows a flow when the group formatter 130 places mobile data and known data according to the third mode into an embodiment, in which new mobile data is transmitted using the second region and the upper/later region. FIG. 34 illustrates the interleaved flow of FIG. 33.

(000189) FIGS. 33 and 34 show no special features, except for the denser arrangement of moving data and known data, than the first mode and the second mode, and their further explanations are omitted.

(000190) FIG. 35 shows a flow, according to the fourth mode, using the entire normal data region, in one embodiment, in which all packets destined for the normal data and the packet region assigned to the existing mobile data, which corresponds to the region top/back, are usable.

(000191) Referring to FIG. 35, the known data is arranged in a vertical direction, in the second region and its peripheral region, and the other region is filled with new mobile data.

(000192) FIG. 36 illustrates the interleaved flow of FIG. 35. Referring to FIG. 36, the upper/back region and the entire normal data region are filled with the new mobile data and the known data and, in particular, the known data is arranged in the form of long training sequences.

(000193) In these regions, the known data can be repeatedly inserted little by little, according to a plurality of standard periods, to make the known data, distributed, after the interleaving.

(000194) FIG. 37 is a diagram of a method for inserting new mobile data into the second region, i.e., within packets (e.g., 38 packets) assigned to normal data, in various ways. Hereinafter, for ease of understanding, new mobile data is referred to as ATSC 1.1 mobile data (or version 1.1 data), and existing mobile data is referred to as 1.0 ATSC mobile data (or version 1.0 data). a) In the first mode, version 1.1 data can be placed in each of the first and last packets, and a 1.1 packet and 3 normal data packets can be repeatedly inserted into the packets, between the first and last packets. Therefore, a total of 11 packets can be used to transmit the version 1.1 data, that is, the new mobile data. b) In the second mode, in the same way, version 1.1 data can be placed in each of the first and last packets, and a 1.1 packet and a normal data packet can be alternately placed in packets, between the first and last packets. repeatedly. Therefore, a total of 20 packets can be used to transmit the version 1.1 data, that is, the new mobile data. c) In the third mode, similarly, version 1.1 data can be placed in each of the first and last packets, and three 1.1 packets and one normal data packet can be repeatedly placed in packets between them. d) In the fourth mode, all packets, which correspond to the second region, can be used to transmit version 1.1 data.

(000195) Here, the fourth mode can be realized as the compatible mode, which uses only the packets corresponding to the second region, to transmit the version 1.1 data, or the incompatible mode, which fills not only the packets that correspond to the second region , but also the MPEG header and the parity region provided for compatibility with the normal data receiver with version 1.1 data. Alternatively, the incompatible mode can be provided as a separate fifth mode.

(000196) The cases, using 1/4, 2/4, 3/4, and 4/4 of all packets from the second region to transmit the mobile data, can correspond to the first to four modes respectively. However, the total number of packages is 38, which is not a multiple of four. Therefore, the modes can be divided, by correcting some packets for the purpose of transmitting the new mobile data packet or the normal data, and sorting the remaining packets according to the above rate as shown in FIG. 37. That is, with reference to Figs. 37A, 37B and 37C, among the 38 packages, 36 packages, except for a predefined number of packages, ie two packages, can include 1.1 packages at the rates of 1/4, 2/4 and 3/4.

(000197) FIG. 38 is a diagram of a pattern of organizing mobile data in different modes.

(000198) Referring to FIG. 38, two version 1.1 data are placed in a central packet, based on the location of the flow between the total packets in the second region, ie 38 packets, and the version 1.1 data and normal data are placed in the packets, accordingly with a set rate in each mode.

(000199) That is, a) the first mode organizes the mobile data into packets, differently from the two core packets, by repeating three normal data packets and one version 1.1 data packet at the top, and repeating one packet of version 1.1 data and 3 normal data packets at the bottom.

(000200) b) The second mode organizes the mobile data into packets, differently from the two core packets, repeating two normal data packets and two version 1.1 data packets at the top, and repeating two version data packets 1.1 and two normal data packets at the bottom.

(000201) c) The third mode organizes the mobile data into packets, differently from the two core packets, repeating one normal data packet and three version 1.1 data packets at the top, and repeating three version data packets 1.1 and a normal data pack at the bottom.

(000202) d) The fourth mode arranges all packets, such as version 1.1 data, which is the same as the fourth mode of FIG. 37.

(000203) Next, FIG. 39 illustrates a sequential arrangement of version 1.1 data from the central packet to the upper and lower packets, based on location in the stream.

(000204) That is, the first mode of FIG. 39A sequentially arranges 11 packets up and down from the center of all packets in the second region.

(000205) The second mode of FIG. 39B sequentially arranges a total of 20 packets, up and down from the center, and the third mode of FIG. 39C sequentially arranges 30 packages in total up and down from the center. The fourth mode of FIG. 39D fills all packages with version 1.1 data.

(000206) FIG. 40 shows a flow, which sequentially places the upper and lower packet mobile data towards the center, unlike FIG. 39. In FIG. 40, the number of new mobile data packets in the first to four modes is different than in the above-described embodiments.

(000207) That is, the first mode of FIG. 40A sorts four version 1.1 data packets down from the top packet, and sorts four version 1.1 data packets up from the bottom packet. In other words, eight version 1.1 data packets in total are placed.

(000208) Next, the second mode of FIG. 40B sorts eight version 1.1 data packets down from the top packet, and eight version 1.1 data packets up from the bottom packet. In other words, 16 version 1.1 data packets in total are placed.

(000209) The third mode of FIG. 40C sorts 12 version 1.1 data packets down from the top packet, and 12 version 1.1 data packets up from the bottom packet. In other words, 24 version 1.1 data packets in total are placed.

(000210) The remaining packages are filled with normal data. The pattern of packets in the fourth mode is the same as in Figs. 37, 38, and 39 and therefore omitted in FIG. 40.

(000211) Although the entry of known data is not illustrated in Figs. 37 to 40, known data can be inserted in part of the same packet, such as mobile data, part of a separate packet, or the entire payload region. The method of entering known data has been described and will be omitted in Figures 37 to 40.

(000212) In the fifth mode, that is, in the incompatible mode, the new mobile data is further embedded in the RS parity region and the header region within the existing mobile data region, instead of in the normal data region, the which is not illustrated in Figs. 37 to 40.

(000213) Although the above-noted fifth mode may be provided as a new mode separate from the fourth mode, a total of four modes may be realized, the fourth mode or fifth mode including the first to third modes.

(000214) That is, Figs. 37 to 40 illustrate the method for inserting the new mobile data in the second region, i.e. packets destined for normal data (e.g. 38 packets) in various modes. The method for organizing the new mobile data into packets assigned to the normal data, according to a predefined mode in FIGS. 37 to 40, may differ as the first to four modes as described above. Here, the fourth mode can be a mode for embedding all 38 packets with the new mobile data, or a mode for embedding not only the 38 packets but also the RS parity region and the header region with the new data furniture. Alternatively, as mentioned above, the method can include all of the first to fifth modes.

(000215) On the other hand, when a mode, to determine the number of packets out of the 38 packets, to which new mobile data is allocated, and how to build the blocks in the M/H group, is, for example, a scalable mode, a) a scalable mode 00, b) a scalable mode 01, c) a scalable mode 10, and d) a scalable mode 11 can be defined, according to a 2-bit signaling field in FIG. 37. Here, even when all 38 packets are assigned to the new mobile data, as in FIG. 37D, 118 packets, which is the region of existing mobile data, and the 38 packets, to which the new mobile data is assigned, can form an M/H group.

(000216) In this case, two scalable modes can be defined, according to the way to build the block in this group. For example, as long as the entire 19.4 Mbps transmission data rate is or is not assigned to mobile data, M/H groups of different block constructions can be generated, even when all 38 packets in a range are assigned to the mobile data as shown in FIG. 37.

(000217) When all the existing transmission data rate of 19.4 Mbps is assigned to mobile data, the normal data rate is 0 Mbps, and a broadcast service provider provides the service, considering only the receiver to receive the mobile data, without regard to the receiver to receive the normal data. In this case, the region, which includes the MPEG header placeholder and RS parity, which is conserved for compatibility with the existing receiver to receive normal data, is defined as a mobile data region and thus the capability mobile data transmission speed can be increased up to about 21.5 Mbps.

(000218) In order to allocate the entire existing 19.4 Mbps transmission data rate to mobile data, 156 packets of all M/H intervals forming the M/H frame must be assigned to mobile data, which implies that all 16 slots in each M/H subframe are set to scalable mode 11. In this case, all 38 packets, being the normal data region, are filled with the mobile data, and an SB5 block, corresponding to the region including the MPEG header placeholder and the RS parity existing in the body region can be obtained. When the 16 intervals in the M/H subframe are set to scalable mode 11, and the RS frame mode is 00 (single frame mode), the SB5 block does not exist separately, and the placeholder corresponding to the SB5 is absorbed by M/H blocks B4, B5, B6, and B7. When all 16 intervals in subframe M/H are set to scalable mode 11 and frame mode RS is 01 (double frame mode), the placeholder located in SB5 forms block SB5. In addition to the body region, the top/back RS parity placeholder region is filled with the moving data and absorbed by a block including a segment of the RS parity placeholder. The placeholder located in the corresponding segments of the M/H blocks B8 and B9 is occupied by SB1. The placeholder located in the first 14 segments of the M/H block B10 is occupied by SB2. The placeholder located in the last 14 segments of the M/H block B1 of the subsequent slot is occupied by SB3. The placeholder located in the corresponding segments of blocks M/H B2 and B3 of the next interval is occupied by SB4. As shown in FIG. 20, there is no region for MPEG header and RS parity in group format after interleaving.

(000219) At the same time, when the entire existing transmission data rate of 19.4 Mbps is not assigned to mobile data, the normal data rate is not equal to 0 Mbps, and the broadcast service provider provides the service, considering both the normal data receiver and the mobile data receiver. In this case, in order to maintain compatibility with the existing normal data receiver, MPEG header and RS parity cannot be redefined as mobile data, but must be transmitted as is. That is, when only some of the 38 packets are filled with the new mobile data, as in the compatible mode indicated above, or all 38 packets are filled with the new mobile data, the MPEG header and RS parity region are not filled with the new mobile data. Therefore, even when all 38 packets, being the normal data region of a given range, are filled with mobile data, the SB5 block corresponding to the region including the MPEG header and RS parity in the body region cannot be obtained.

(000220) FIG. 57 illustrates a group format based on packets before interleaving, taking into account compatibility, when the 38 packets, being the normal data region, are filled with the mobile data. All 38 packets are assigned to mobile data as shown in Figs. 37-40D, but the region including MPEG header and RS parity is kept in a group format based on segments after interleaving, and block SB5 is not obtained, as shown in FIG. 56. This group format can be defined as a group format corresponding to the fourth mode, or the scalable mode 11. Alternatively, the fourth mode, which only fills the 38 packets with the new mobile data, considering compatibility, can be referred to as a scalable mode 11a.

(000221) On the other hand, when scalable mode 11, being incompatible mode, is used, it cannot be used in conjunction with the range filled with the new mobile data in a different mode. That is, all intervals, that is, all 0 to 15th intervals must be filled with the new mobile data according to scalable mode 11. In contrast, the intervals can be used in combination in the first to four modes.

(000222) As such, the normal data region of each range can be filled with the moving data in a number of ways. Thus, the type of interval may vary according to frame mode and mode setting status.

(000223) When four modes are provided, as mentioned above, each interval including mobile data, according to the first to four modes, can be referred to as first to four interval types.

(000224) The digital broadcast transmitter can generate the same type of interval in each interval. On the other hand, the stream can be generated to repeat different types of intervals, based on a certain number of intervals.

(000225) That is, as shown in FIG. 41, the data preprocessor 100 can organize the mobile data such that one interval of the first type and three intervals of type 0 are repeatedly arranged. A range of type 0 can indicate a range, which distributes normal data to packets destined for normal data as original.

(000226) Such an interval type can be defined using a specific part of the existing signaling data, for example TPC or FIC.

(000227) On the other hand, when frame mode is set to 1, the mode can be set to one of a plurality of modes, such as the first through four modes as described above. Here, the fourth mode may be scalable mode 11, or scalable mode 11a, described above. Alternatively, the mode can be one of five modes, including scalable modes 11 and 11a. Furthermore, the mode can be divided into at least one compatible mode and the incompatible mode, that is, the scalable mode 11.

(000228) When modes include the first to four modes, for example, intervals corresponding to the respective modes may be referred to as 1-1, 1-2, 1-3, and 1-4 type intervals.

(000229) That is, the 1-1 type range indicates a range, in which the 38 packets are allocated in the first mode, the type 1-2 range indicates a range, in which the 38 ranges are allocated in the second mode, the range of type 1-3 indicates a range, in which 38 packets are allocated in the third mode, and range of type 1-4 indicates a range, in which 38 packets are allocated in the fourth mode.

(000230) FIG. 42 shows examples of a flow, which repeatedly arranges different types of intervals.

(000231) According to the first example of FIG. 42, the type 0 interval and the type intervals 1-1, 1-2, 1-3, 1-4 are repeatedly arranged in sequence in the stream.

(000232) According to the second example of FIG. 42, the flow alternately arranges the 1-4 type range and 0 type range. As described above, since the fourth mode is the mode, which fills the entire normal data region with the moving data, the second example indicates the alternative range arrangement used for mobile data and the range used for normal data across the normal data region.

(000233) In addition, several types of intervals can be repeatedly arranged, in different ways, as shown in the third, fourth, and fifth examples. In particular, all ranges can be combined into a single type range to generate the stream, as shown in the sixth example.

(000234) FIG. 43 illustrates the flow, according to the second example of FIG. 42. Referring to FIG. 43, although the normal data region is used for the normal data in the type 0 range, the entire normal data region is used for the mobile data in the type 1 range, and at the same time, the known data is placed under the shape of long training sequences. As such, the type of range may vary.

(000235) FIGS. 44 to 47 illustrate flows for explaining a block allocation method in the first to four modes. As described above, the first region and the second region each can be divided into a plurality of blocks.

(000236) The data preprocessor 100 can perform block encoding, based on the single block, or based on the multiple blocks combined, according to a predefined block mode.

(000237) FIG. 44 illustrates the division of blocks in the first mode. Referring to FIG. 44, the body region is divided into B3-B8, and the upper/posterior region is divided into BN1-BN4.

(000238) FIGS. 45 and 46 illustrate the division of blocks in the second mode and the third mode. Similar to FIG. 44, the body region and the upper/back region are each divided into a plurality of blocks.

(000239) For its part, FIG. 47 illustrates block splitting in the fourth mode, which fills the top/back region with moving data. As the normal data region is filled with the mobile data, the body region MPEG header and the parity part of the normal data are unnecessary and therefore they are defined as BN5 in FIG. 47. Part BN5 is filled with the new mobile data in incompatible mode, and used as header and parity in compatible mode. Unlike FIG. 44 to 46, the superior/posterior region is divided into BN1-BN5 in FIG. 47.

(000240) As explained above, block processor 120 of data preprocessor 100 converts and processes RS frame based on blocks. That is, as shown in FIG. 7, block processor 120 includes first converter 121. First converter 121 combines the RS frame mobile data according to a predefined block mode and thus outputs the Convolutional Serial Concatenated Code (SCCC) block.

(000241) Block mode can be set in several ways.

(000242) For example, when the block mode is set to 0, the respective blocks, i.e. BN1, BN2, BN3, BN4 and BN5 are output as a single SCCC block, and become the SCCC encoding unit.

(000243) In contrast, when the block is set to 1, the blocks are combined to form the SCCC block. More specifically, BN1 + BN3 = SCBN1, BN2 + BN4 = SCBN2, and BN5 becomes exclusively SCBN3.

(000244) On the other hand, in addition to the mobile data placed in the second region, the existing mobile data placed in the first region can be combined into one or multiple block(s) and coded per block, according to the block mode. This operation is the same as the conventional ATSC-MH and its detailed description is omitted.

(000245) Block mode information can be recorded in the existing signaling data, or contained in the region, in the new signaling data and then notified to the receiver. The receiver can retrieve the original stream by properly identifying and decoding the notified block mode information.

(000246) On the other hand, RS frame can be generated by combining the data to be coded per block as indicated above. That is, frame encoder 110 of data preprocessor 100 generates RS frame by properly combining frame parts so that block processor 120 can perform proper block encoding.

(000247) More specifically, an RS 0 frame can be generated by combining SCBN1 and SCBN2, and an RS 1 frame can be generated by combining SCBN3 and SCBN4.

(000248) Alternatively, frame RS 0 can be generated by combining SCBN1, SCBN2, SCBN3 and SCBN4, and frame RS 1 can be generated with SCBN 5.

(000249) Alternatively, SCBN1 + SCBN2 + SCBN3 + SCBN4 + SCBN5 can generate an RS frame.

(000250) Otherwise, RS frame can be generated by combining the block corresponding to the existing mobile data and the newly added blocks SCBN1 to SCBN5.

(000251) FIG. 48 illustrates various methods for setting the start point of the RS frame. Referring to FIG. 48, the transport stream is divided into a plurality of blocks. In conventional ATSC-MH, the RS frame is split between BN2 and BN3. However, as the present invention inserts the mobile data and the known data into the normal data region, the starting point of the RF frame can be defined differently.

(000252) For example, RS frame can start based on a boundary between BN1 and B8, based on a boundary between BN2 and BN3 as the current reference point, or based on a boundary between B8 and BN1. The starting point of the RS frame can be determined differently according to the block coding combination condition.

(000253) On the other hand, RS frame constitution information can be transported to the receiver by region in the existing signaling data or in the new signaling data.

(000254) As above, once the new mobile data and the known data are inserted into the region allocated to the original normal data and into the region assigned to the existing mobile data, various pieces of information are needed to communicate this information to the receiver. Such information may be transmitted via a reserved bit in a TPC region of the conventional ATSC-MH standard, or may be transmitted as new signaling data via a new signaling data region. Since the new signaling data region must be located at the same location in each mode, it is placed in the top/back region.

(000255) FIG. 49 shows a stream indicating a location of the conventional signaling data and the location of the new signaling data.

(000256) Referring to FIG. 49, the conventional signaling data is located between the long training sequences of the body region, and the new signaling data is located in the upper/back region. The new signaling data encoded by signaling encoder 150 is inserted by group formatter 130 at a predefined location, as shown in FIG. 49.

(000257) On the other hand, the signaling encoder 150 can improve performance by using a different code than the conventional signaling encoder, or by encoding at a different code rate.

(000258) That is, a PCCC code of 1/8 can be used in addition to the existing RS code, or the equivalent effect of the PCCC code with a rate of 1/8 can be obtained, by means of a PCCC code RS + 1/ 4 and sending the same data twice.

(000259) For its part, since the known data is contained in the transport stream as described above, the memory in the Trellis encoder needs to be initialized, before the known data is encoded by Trellis.

(000260) When long training sequences are provided as in the fourth mode, there is no big problem, because the corresponding sequence can be processed through single initialization. However, when known data is discontinuously arrayed, as in other modes, it is difficult to initialize multiple times. Also, when memory is initialized to 0, it is difficult to generate the symbol, as in the fourth mode.

(000261) Based on this, a Trellis encoder memory value (ie a register value) of the fourth mode at the same location can be loaded directly into the Trellis encoder without resetting the Trellis, so as to generate the same symbol, either as possible in the fourth mode, as in the first to third modes. To do this, the Trellis encoder memory storage values in the fourth mode can be recorded and stored in a table, and encoded by Trellis with a location value corresponding to the stored table. Alternatively, a value obtained by the Trellis encoder can be used, by separately adding a Trellis encoder, operating in the fourth mode.

(000262) As mentioned above, mobile data can be provided in various ways using the normal data region and the mobile data region existing in the transport stream. Thus, compared to the conventional ATSC standard, the most suitable stream for mobile data transmission can be provided.

(000263) [Signaling]

(000264) As new mobile data and known data are added to the transport stream, as mentioned above, a technique to notify the receiver is needed in order to process the data. Notification can be done in a number of ways.

(000265) That is, firstly, the presence or absence of the new mobile data can be notified using a data field synchronizer which is used to transmit the existing mobile data.

(000266) FIG. 50 shows the construction of the data field synchronizer. Referring to FIG. 50, the data field synchronizer includes 832 symbols in total, and 104 symbols of them correspond to a reserved area. 83 to 92 symbols, that is, 10 symbols in the reserved area correspond to an accessory region.

(000267) When only version 1.0 data is contained, the 85th symbol is set to +5 and the remaining symbols, ie 83rd, 84th, and 86th to 92nd symbols are set to -5 in the field of odd data. In the even data field, the symbol sign of the odd data field is inverted.

(000268) However, when version 1.1 data is contained, the 85th and 86th symbols are defined as +5 and the remaining symbols, that is, the 83rd, 84th, and 87th to 92nd symbols are defined as -5 in the odd data field. The symbol sign of the odd data field in the even data field is inverted. That is, whether or not version 1.1 data is included can be notified using the 86th symbol.

(000269) On the other hand, the fact that version 1.1 data is included can be notified by using another symbol in the accessory region. That is, if the fact that version 1.1 data is included can be notified by creating one or more symbols, except 85th symbol like +5 or other value. For example, the 87th symbol can be used.

(000270) Data field synchronization can be generated by the controller of FIG. 3, the signaling encoder, or a field sync generator (not shown) provided separately, provided to sync MUX 470 of FIG. 4, and multiplexed to the stream by sync MUX 470.

(000271) In a second method, TPC can be used to notify the presence or absence of version 1.1 data. TPC includes syntax from the following table: Table 1

(000272) As shown in Table 1, the TPC information includes a reserved area. In this way, one or more bits in the reserved area can be used to signal, whether packets assigned to normal data, i.e. packets in the second region include the mobile data, its location, whether new known data has been added, and the location of the added known data.

(000273) The information entered can be represented in the table below. Table 2

(000274) In Table 2, frame mode 1.1 is information that indicates whether the data packet assigned to normal data is used for normal data or for new mobile data, that is, version 1.1 data, as indicated above.

(000275) Mobile Mode 1.1 is information indicating the pattern for organizing mobile data for packets assigned to normal data. That is, one of the first to four modes above can be expressed by marking "00", "01", "10" and "11", using 2 bits. Thus, the flow can be organized in various ways, as shown in Figs. 29, 31, 33, 35, 37, 38, 39, and 40, and the receiver can identify the mobile mode information and locate the mobile data.

(000276) An SCCC 1.1 block mode is information indicating the block mode of version 1.1 data. SCCCBM1 to SCCCBM5 1.1 are information indicating the coding unit of version 1.1 data.

(000277) In addition to the information recorded in Table 2, various information can also be provided so that the receiver can correctly detect and decode the new mobile data. If necessary, the number of bits assigned to the information can be changed. The location of each field can be arranged in a different order from table 2.

(000278) FIC information can notify, if new mobile data is contained, to the digital broadcast receiver receiving the stream, including the new mobile data.

(000279) That is, a version 1.1 receiver for receiving and processing new mobile data must be able to process service 1.0 information and service 1.1 information at the same time. On the other hand, a version 1.0 receiver must be able to ignore 1.1 service information.

(000280) In this way, by changing the syntax of the existing FIC segment, a region to notify the presence or absence of version 1.1 data can be secured.

(000281) Existing FIC segment syntax can be generated as in the following table. Table 3

(000282) The FIC segment of Table 3 can be modified to notify the presence or absence of version 1.1 data as follows. Table 4

(000283) Referring to Table 4, FIC_segment_num and FIC_last_segment_num are extended to 5 bits instead of the reserved area.

(000284) In Table 4, by adding 01 to the FIC_segment_type value, the presence or absence of version 1.1 data can be notified. That is, when FIC_segment_type is set to 01, version 1.1 receiver can decode FIC information and process version 1.1 data. In this case, the version 1.0 receiver cannot detect the FIC information. On the other hand, when FIC_segment_type is set to 00 or null segment, the version 1.0 receiver decodes the FIC information and processes the existing mobile data.

(000285) At the same time, the presence or absence of version 1.1 data can be notified, using certain area, eg the reserved area, while maintaining the syntax of the FIC part, without changing the original FIC syntax.

(000286) The FIC can include up to 16 bits when generating the maximum FIC part. By changing part of the syntax for building the FIC part, the status of version 1.1 data can be notified.

(000287) More specifically, "MH 1.1 service_status" can be added to the reserved area of a service pool loop, as shown in the following table. Table 5

(000288) Referring to Table 5, MH 1.1_service_status can be displayed using two bits of the three bits in the reserved area. MH 1.1_service_status can be data indicating whether the stream includes version 1.1 data.

(000289) Alternatively, in addition to MH 1.1_service_status, MH 1.1_ensemble_indicator can be added. That is, the FIC part syntax can be generated as follows. Table 6

(000290) Referring to Table 6, 1 bit of the 3 bits in the first reserved area is allocated to MH1.1_ensemble_indicator. MH1.1_ensemble_indicator denotes information relating to a set, which is a service unit of version 1.1 data. In Table 6, MH1.1_service_status_extension can be represented using 2 bits of the 3 bits of the second reserved area.

(000291) Alternatively, a version 1.1 service can be specified as 1.1, using a value assigned to a reserved area of 1.0, changing a suite protocol version, as shown in the following Table 7. Table 7

(000292) Alternatively, signaling data can be transmitted by changing the length of the set loop header extension of the FIC part header syntax field by adding a set extension to the FIC part payload syntax field , and adding MH1.1_service_status to the 3 bits reserved for the service loop of the FIC part load syntax, as shown in Table 8 below. Table 8

(000293) Alternatively, H_service_loop_extension_length of the FIC part header syntax field can be changed, and an information field of MH1.1_service_status of the FIC part load field can be added, as shown in the following table. Table 9

(000294) As above, signaling data can be provided to the receiver using different regions such as field sync, TPC information, and FIC information.

(000295) At the same time, signaling data can be entered in a region other than these regions. That is, the signaling data can be inserted into a payload part of the existing data packet. In this case, the presence of version 1.1 data or the location of the signaling data can be recorded using the FIC information as shown in Table 5, and signaling data for version 1.1 can be separately provided, so that the receiver version 1.1 can detect and use the corresponding signaling data.

(000296) Signaling data can be generated and transmitted as a separate stream to the receiver, via a channel separate from a stream transmission channel.

(000297) In addition, in addition to the different information mentioned above, the signaling data may also include information for signaling at least one of the presence or absence of existing mobile data or new mobile data, the location of the mobile data, the addition of the known data, the location of the added known data, the arrangement pattern of the mobile data and the known data, the block mode, and the encoding unit.

(000298) At the same time, the digital broadcast transmitter using the signaling data may include a data preprocessor for organizing at least one of the mobile data and the known data into at least part of the normal data region among all the packets from the stream, and a MUX to generate the transport stream, including mobile data and signaling data. A detailed structure of the data preprocessor can be implemented, using one of the aforementioned embodiments, or by defaulting, adding, or modifying some components. In particular, the signaling data can be generated by the signaling encoder, the controller, or the additionally equipped field sync generator (not shown) and inserted into the transport stream by the MUX, or the sync MUX. In this case, the signaling data can be implemented, using data field synchronization or the TPC or FIC information, as mentioned above, as the information notifying at least one of the presence or absence and the disposition pattern of the mobile data.

(000299) As described above, when the scalable mode 11a exists, in addition to the existence of the scalable mode 11, that is, when the first to fifth modes exist, a method for representing the mode in the signaling data may be different.

(000300) According to one embodiment, a signaling field name in a TPC field can be defined as a scalable mode, and two bits are allocated to define the four modes of FIGS. 37A to 40D, such as 00, 01, 10, and 11. In this case, the fourth mode has the same bit value of 11, regardless of whether it is the compatible mode, or the incompatible mode. However, since MPEG header and parity region may or may not be used in both modes, the group format may be different.

(000301) A receiver checks not only the TPC of the interval including the M/H group of the M/H stop to receive, but also of TPCs of other intervals. When the scalable mode of all slots is 11, and a CMM slot does not exist, that is, when a normal data rate is 0 Mpbs, the receiver can determine and decode the bit value of 11, such as scalable mode 11 .

(000302) In contrast, when the scalable mode of all intervals is not 11, or the CMM interval exists, that is, when the normal data rate is not 0 Mbps, the receiver, which must consider compatibility, can determine and decode the bit value of 11, such as scalable mode 11a.

(000303) According to another embodiment, the signaling field name in the TPC field can be set as the scalable mode, and three bits can be assigned to that field. Consequently, five group formats in total, including the three group formats corresponding to those in Figs. 37A to 40C, i.e. the first to third modes, as well as the two group formats corresponding to Figs. 37 to 40D, that is, the fourth mode and the fifth mode, can be flagged.

(000304) That is, the modes described above may include: 1) a first mode, which organizes the new mobile data into 11 packets out of 38 packets assigned to the normal data, 2) a second mode, which arranges the new mobile data into 20 packets out of 38 packets assigned to normal data, 3) a third mode, which arranges the new mobile data into 29 packets out of 38 packets assigned to normal data, 4) a fourth mode, which arranges new mobile data into all 38 packets allocated to normal data, 5) a fifth mode, which organizes the new mobile data into all 38 packets assigned to the normal data, and also into the region corresponding to the MPEG header and parity among the regions assigned to the existing mobile data.

(000305) The first mode can be defined as a scalable mode 000, the second mode can be defined as a scalable mode 001, and the third mode can be defined as a scalable mode 010. The fourth mode, that is, the mode for filling the 38 packets with the mobile data, and taking into account the compatibility, can be defined as a scalable mode 011, and the fifth mode, that is, the mode for filling the 38 packets with the mobile data, and not considering compatibility , can be set to a scalable mode 111.

(000306) Furthermore, in order to define an additional group format, a scalable mode bit value can be assigned, or a signal bit can be added.

(000307) The digital broadcast transmitter, according to the various embodiments as described above, can organize and transmit the existing mobile data, the new mobile data, as well as the normal data in the stream in various styles, according to the modes.

(000308) For example, in FIG. 4, the stream generator, i.e. the group formatter 130 arranged in the data preprocessor 100 adds the known data, the signaling data as well as the initialization data to the stream processed by the block processor 120, and formats the stream according to the group.

(000309) So when the packet formatter formats the packet, the MUX 200 performs multiplexing. In this case, the MUX 200 also multiplexes the normal data processed by the normal processor 320 in the first to third modes. On the other hand, in the fourth and fifth modes, the normal processor 320 does not output any normal data, and the MUX 200 outputs the stream provided by the packet formatter 140 as is.

(000310) [Digital Broadcast Receiver]

(000311) As indicated above, the digital broadcast transmitter can transmit the new mobile data using part or all of the packets destined for the normal data, and part or all of the packets assigned to the existing mobile data in the existing stream.

(000312) The digital broadcast receiver, upon receiving the stream, can receive and process at least one of the existing mobile data, the normal data, and the new mobile data, depending on its version.

(000313) That is, after receiving the various streams as mentioned above, the conventional digital broadcast receiver for processing the normal data can identify the signaling data and thus detect and decode the normal data. As described above, when the stream is generated in the mode, not including the normal data at all, the receiver for processing the normal data cannot provide the normal data service.

(000314) On the other hand, by receiving the various streams as mentioned above, the digital broadcast receiver for version 1.0 can identify the signaling data and thus detect and decode the existing mobile data. When version 1.1 mobile data is located throughout the region, the version 1.0 digital broadcast receiver cannot provide mobile service either.

(000315) In contrast, a version 1.1 digital broadcast receiver can detect and process not only version 1.1 data but also version 1.0 data. In this case, when the receiver includes a decoding block for processing normal data, it can provide normal data service.

(000316) FIG. 51 is a block diagram of a digital broadcast receiver, according to an embodiment of the present invention. Although the digital broadcast receiver may have a construction, wherein components corresponding to the various components of the digital broadcast transmitter of FIGs. 2 to 4 are arranged inversely, only the essential components are illustrated in FIG. 51, for ease of understanding.

(000317) That is, referring to FIG. 51, the digital broadcast receiver includes a receiver 5100, a demodulator 5200, an equalizer 5300, and a decoder 5400.

(000318) Receiver 5100 receives the transport stream transmitted from the digital broadcast transmitter through an antenna or cable.

(000319) The demodulator 5200 demodulates the transport stream received through the receiver 5100. A frequency and a clock signal of the signal received by the receiver 5100 are synchronized with the digital broadcast transmitter as they pass through the demodulator 5200.

(000320) The 5300 equalizer equalizes the demodulated transport stream.

(000321) The demodulator 5200 and the equalizer 5300 can perform synchronization and equalization more quickly using the known data contained in the transport stream, in particular the known data, which is added together with the new mobile data.

(000322) The 5400 decoder detects and decodes the mobile data in the equalized transport stream.

(000323) The insertion location and size of mobile data and known data can be notified by signaling data contained in the transport stream, or by signaling data received over a separate channel.

(000324) The decoder 5400 can locate the appropriate mobile data to the digital broadcast receiver, using the signaling data, and detect and decode the mobile data at the detected location.

(000325) The construction of decoder 5400 may vary according to various embodiments.

(000326) That is, the decoder 5400 may include two decoders, including a Trellis decoder (not shown) and a convolution decoder (not shown). The two decoders can improve performance, such as exchanging their decoding reliability information with each other. The convolution decoder output can be identical to the transmitter RS encoder input.

(000327) FIG. 52 is a detailed block diagram of the digital broadcast receiver, according to an embodiment of the present invention.

(000328) Referring to FIG. 52, the digital broadcast receiver may include receiver 5100, demodulator 5200, equalizer 5300, decoder 5400, detector 5500, and signaling decoder 5600.

(000329) Since the functions of the 5100 receiver, 5200 demodulator, and 5300 equalizer are the same as those of FIG. 51, your explanations are omitted.

(000330) Decoder 5400 may include a first decoder 5410 and a second decoder 5420.

(000331) The first decoder 5410 decodes at least one of the existing mobile data and the new mobile data. The first decoder 5410 can perform block-based SCCC decoding.

(000332) The second decoder 5420 RS decodes the stream decoded by the first decoder 5410.

(000333) The first and second decoders 5410 and 5420 can process the mobile data using the send value of the signaling decoder 5600.

(000334) That is, the signaling decoder 5600 can detect and decode the signaling data in the stream. Specifically, the signaling decoder 5600 demultiplexes the reserved area in the field sync data, or the TPC information region and the FIC information region of the transport stream. Thus, the signaling data can be recovered by convolutional decoding, RS decoding, and demultiplexed part de-multiplexing. The retrieved signaling data is provided to the components of the digital broadcast receiver, i.e., the 5200 demodulator, the 5300 equalizer, the 5400 decoder, and the 5500 detector. The signaling data may include information, which must be used by the components , that is, block mode information, mode information, known data insertion pattern information, and frame mode. The types and functions of such information have been explained in detail earlier, so their additional explanations are not presented here.

(000335) In addition, a number of information, such as a mobile data encoding rate, a data rate, an insertion location, a type of error correction code used, a main service information, support information time cutoffs, a description of the mobile data, information regarding changing the mode information, and information to provide an IP service, may be provided to the receiver, in the form of signaling data or additional data.

(000336) On the other hand, it is assumed in FIG. 52, that the signaling data is contained in the stream. However, when the signaling data signal is transmitted over a separate channel, the signaling decoder 5600 can decode that signaling data signal, and provide the information.

(000337) The 5500 detector detects the known data in the stream using the known data insertion pattern information provided by the 5600 beacon decoder. In this case, the known data, added with the existing mobile data, can be processed in addition of known data, added with the new mobile data.

(000338) Specifically, known data can be inserted into at least one body region and the upper/back region of the mobile data in various locations and various patterns, as shown in Figs. 22 to 36. The known data insertion pattern information, i.e. the location, starting point, and length information can be included in the signaling data. Detector 5500 can detect the known data from an appropriate location, in accordance with the signaling data, and provide the known, sensed data to the demodulator 5200, the equalizer 5300, and the decoder 5400.

(000339) FIG. 53 is a detailed diagram of a digital broadcast receiver, according to another exemplary embodiment.

(000340) Referring to FIG. 53, the digital broadcast receiver includes a receiver 5100, a demodulator 5200, an equalizer 5300, a FEC processor 5411, a TCM decoder 5412, a CV deinterleaver 5412, an external deinterleaver 5414, an external decoder 5415, an RS decoder 5416 , a derander 5417, an outer interleaver 5418, a CV interleaver 5419, and a signaling decoder 5600.

(000341) Since receiver 5100, demodulator 5200, equalizer 5300, and signaling decoder 5600 have been described in FIG. 52, their overlapping explanations are omitted. Unlike FIG. 52, the detector 5500 is not shown. That is, the components can directly detect the known data using the signaling data, which is decoded by the signaling decoder 5600, as in that embodiment.

(000342) The FEC 5411 processor can perform early error correction for the transport stream equalized by the 5300 equalizer. The FEC 5411 processor can detect the known data in the transport stream using the known data location information, or the pattern of inserting within the information provided by the 5600 signaling decoder, and using the known data for early error correction. Alternatively, an additional reference signal may not be used for forward error correction, depending on the application.

(000343) On the other hand, in FIG. 53, the components are arranged in such a way that mobile data is decoded after FEC processing. That is, FEC processing is applied to the entire transport stream. However, only mobile data can be detected from the transport stream and then FEC can only be applied to mobile data.

(000344) The TCM 5412 decoder detects the mobile data from the transmission stream of the FEC 5411 processor, and performs the Trellis decoding. In this case, when the FEC processor 5411 has already detected the mobile data, and performed the forward error correction only for the detected data, the TCM decoder 5412 can immediately Trellis decode the input data.

(000345) CV deinterleaver 5413 convolutionally deinterleaves the data decoded by Trellis. As described above, since the construction of the digital broadcast receiver corresponds to the construction of the digital broadcast transmitter, which generates and processes the transport stream, the CV deinterleaver 5413 may be unnecessary, according to the structure of the transmitter.

(000346) External deinterleaver 5414 performs external deinterleaving of the convolution-deinterleaved data. The outer decoder 5415 then decodes to remove the parity added to the mobile data.

(000347) In some cases, the performance in receiving mobile data can be improved by repeating operations from decoder TCM5412 to external decoder 5415 one or more times. For the repeated operations, the decoded data from the outer decoder 5415 can be inserted into the TCM decoder 5412, through the outer interleaver 5418 and the CV interleaver 5419. At this time, the CV interleaver 5419 may be unnecessary, according to the structure of the transmitter.

(000348) As such, the data decoded by Trellis is provided to the RS decoder 5416. The RS decoder 5416 can RS-decode the provided data, and the Rasterizer 5417 can perform the derivationing. Thus, mobile data stream, in particular, newly defined version 1.1 mobile data can be processed.

(000349) At the same time, as described above, when the digital broadcast receiver next goes to version 1.1, it can process version 1.0 data in addition to version 1.1 data.

(000350) That is, at least one of FEC processor 5411 and TCM decoder 5412 can detect all mobile data, except for normal data, and process the detected data.

(000351) When the digital broadcast receiver is an ordinary receiver, it may include the entirety of a block for processing normal data, a block for processing version 1.0 data, and a block for processing version data 1.1. In this case, a plurality of processing paths are provided at the rear end of the equalizer 5300, each of the above blocks is arranged in each processing path, and at least one of the processing paths is selected under control of a controller (not shown) equipped separately. Thus, data appropriate for the transport stream can be included.

(000352) As described above, the transport stream can arrange the mobile data in a different pattern for each slot. That is, several intervals can be constructed several times, according to a previously defined pattern, such as, for example, interval of the first type, including normal data, as it is, interval of the second type, including the new mobile data throughout normal data region, third type range including new mobile data in part of normal data region, and fourth type range including new mobile data throughout normal data region and in existing mobile data region.

(000353) The signaling decoder 5600 decodes the signaling data and notifies each component of the frame mode information, or the mode information. Therefore, each component, in particular the FEC processor 5411, or the TCM decoder 5412, detects and processes the mobile data at the location designated for each slot.

(000354) Although the controller is omitted in FIGS. 51 to 53, a controller may be further provided to apply a suitable control signal to each block using the signaling data decoded by signal decoder 5600. Such controller may control a tuning operation of receiver 5100 in accordance with user selection.

(000355) A version 1.1 receiver can selectively provide version 1.0 data, or version 1.1 data, according to user selection. When a plurality of version 1.1 data is provided, one of the services can be provided, according to the user's selection.

(000356) In particular, at least one of the normal data, existing mobile data, and new mobile data can be organized and transmitted in the stream, as in the first to four modes (in this document, all the first to four modes can be compatible modes, or only the fourth mode can be the incompatible mode), or in the first to fifth modes.

(000357) In this case, the digital broadcast receiver can detect each data from an appropriate place, according to the mode, and decode the data, by applying an appropriate decoding system.

(000358) More specifically, when the mode is represented with two bits, and a TPC signaling field registered as 00, 01, 10, or 11 is restored, as described above, to the digital broadcast receiver, by confirming the value of 11 in the signaling data, checks the TPCs of not only the interval including the M/H group of the M/H stop to be received, but also other intervals. Consequently, when the mode information for each range is 11, and the CMM range does not exist, it is determined that the fourth mode is set to the incompatible mode. Thus, the digital broadcast receiver can decode the MPEG header, and the parity region including the new mobile data, for example, the SB5 region, in the same way as in the remaining body region stream. In contrast, when the scalable mode of each range is not 11, or the CMM range exists, it is determined that the defined mode is the compatible mode, i.e., the scalable mode 11a, and the MPEG header and parity region, i.e. that is, region SB5, can be decoded in a different way than the stream of the remaining body region, that is, in a decoding scheme corresponding to the encoding scheme of the new mobile data. The TPC and mode of each slot can be identified by the signaling decoder, or by a separate controller.

(000359) When the mode is represented with three bits, and signal bits such as 000, 001, 010, 011, and 111 are transmitted as described above, the digital broadcast receiver identifies the mode according to the value of the bit, and performs the corresponding decoding.

(000360) The digital broadcast transmitter can generate and transmit a transport stream, combining normal data, existing mobile data, and new mobile data.

(000361) In this way, the digital broadcast receiver, receiving and processing the transport stream, can be realized in various ways. That is, the digital broadcast receiver can be realized, as a normal data receiver, capable of processing normal data only, an existing mobile data receiver, capable of processing only existing mobile data, a new mobile data receiver, capable of processing only new mobile data, and a common receiver capable of processing at least two of the data.

(000362) When normal data receiver is performed, there is no data to be processed in fourth incompatible mode or fifth incompatible mode, unlike in first to fourth compatible modes. Thus, the digital broadcast receiver can ignore the transport stream, which it cannot recognize and process.

(000363) In contrast, the existing mobile data receiver, or the common receiver capable of processing the existing mobile data and the normal data decodes the range, including only the normal packets, or the normal data included in all 38 packets, or in part of the 38 packets, to process the normal data, and detects and decodes the existing mobile data included in packets, other than the 38 packets, in order to process the existing mobile data. In particular, when the range includes the new mobile data, and the block mode is separated, as described above, the main set part is filled with the existing mobile data, and the secondary set part is filled with the new mobile data , in order to transmit existing mobile data and new mobile data using an interval. Therefore, when the mode is scalable mode 11, the receiver decodes the remaining body region, except for SB5, in order to process the existing mobile data. In contrast, when the mode is scalable mode 11a, SB5 is not filled with the new mobile data and hence the whole body region is decoded in order to process the existing mobile data. On the other hand, when the block mode is paired, all blocks are filled only with mobile data 1.1 and thus the receiver ignores the corresponding interval in order to process the existing mobile data.

(000364) Likewise, the new mobile data receiver, or the common receiver capable of processing the new mobile data and other data, performs decoding according to the block mode and the mode. That is, when the block mode is separated, and the mode is scalable mode 11, a block independent of the SB5 region and a block allocated to the new mobile data are decoded in a decoding scheme corresponding to the encoding scheme of the new mobile data . When the mode is scalable mode 11a, the block allocated to the new mobile data is decoded in a decoding scheme corresponding to the encoding scheme of the new mobile data. In contrast, when block mode is paired, all blocks can be decoded.

(000365) In FIGS. 51-53, the separately provided controller, or signaling decoder, can identify the block mode and the mode, and control the decoding as described above. In particular, when two bits of the signaling data indicate the mode, and the bit value of 11 is transmitted, the controller or the signaling decoder can identify not only the TPC of the interval including the M/H group of the stop M/ H to be received, but also the TPCs from the other ranges. Therefore, when the normal data rate is 0 Mbps, the bit value of 11 can be determined, such as scalable mode 11, and decoded. In contrast, when the scalable mode of all ranges is not 11, or when the CMM range exists, that is, when the normal data rate is not 0 Mbps, the bit value of 11 can be determined as the scalable mode 11a and decoded.

(000366) Although the digital broadcast receiver of Figs. 51 to 53 can be implemented, using a converter or a TV, it can be implemented, using various portable devices, such as personal computers, PDA, MP3 player, electronic dictionary, and notebook. Furthermore, although not shown in FIG. 51 to 53, it is understood that the receiver may include a component, which appropriately scales or converts the decoded result data, and outputs the data onto a screen in the form of audio and video data.

(000367) On the other hand, a method for generating digital broadcast transmitter stream and a method for processing digital broadcast receiver stream, according to an exemplary embodiment, can be explained using block diagrams and the above mentioned flow diagrams.

(000368) That is, the digital broadcast transmitter stream generation method can largely include organizing the mobile data into at least part of the packets assigned to the normal data of all packets generating the stream, and generating the transport stream, inserting normal data into the stream, including mobile data.

(000369) Mobile data organization may be performed by data preprocessor 100 illustrated in FIGS. 2 to 4.

(000370) Mobile data can be placed in various locations, together with normal data and existing mobile data, or just as in the various embodiments mentioned above. In other words, mobile data and known data can be placed in various styles as shown in Figs. 15 to 40.

(000371) Stream generation multiplexes the normal processed data, in addition to the mobile data, with the mobile data to generate the transport stream.

(000372) The generated transport stream passes through various processes, such as RS encoding, interleaving, Trellis encoding, synchronous multiplexing, and modulation, and then is transmitted to the receiver. Transport stream processing may be performed by various components of the digital broadcast transmitter depicted in FIG. 4.

(000373) The various embodiments of the method for stream generation refer to the various operations of the digital broadcast transmitter mentioned above. Thus, the flowchart of the method for flow generation is omitted.

(000374) On the other hand, the method for processing digital broadcast receiver stream, according to an embodiment, may include receiving the transport stream, which is divided into the first region assigned to the existing mobile data, and in the second region assigned to normal data, and organizes the mobile data separately from existing mobile data in at least part of the second region, demodulation of the received transport stream, equalization of the demodulated transport stream, and decoding of at least one of the existing mobile data and mobile data from the equalized transport stream.

(000375) The transport stream received in the present method may be generated and transmitted by the digital broadcast transmitter, according to the various embodiments mentioned above. That is, the transport stream can place the mobile data in various ways, as shown in Figs. 15 to 21 and 29 to 40. In addition, known data can also be placed in various ways, as shown in Figs. 22 to 28.

(000376) The various embodiments for the method for stream processing refer to the various embodiments of the digital broadcast receiver mentioned above. Thus, the flowchart of the method for flow processing is omitted.

(000377) On the other hand, examples of the different flow constructions as shown in Figs. 15 to 40, as mentioned above, are not limited to one constitution, but can be linked to different constitutions, according to situations. That is, the data pre-processor 100 can organize and block-encode the moving data and the known data, applying different frame modes, block modes and modes, according to the control signal, applied by the separately supplied controller, or with the externally input control signal. Thus, a digital broadcasting provider can provide the desired data, in particular mobile data in various sizes.

(000378) In addition, the above-mentioned new mobile data, i.e. version 1.1 data, may be the same data as the existing mobile data, i.e. version 1.0 data, or different data entered by another source . In addition, a plurality of version 1.1 data may be contained and transmitted in one slot. Thus, the user of the digital broadcast receiver is able to view his desired data of various types.

<Block Processing Method>

(000379) The various embodiments described above can be modified in various ways.

(000380) For example, block processor 120 of FIG. 4 can perform block encoding by appropriately combining existing mobile data, normal data, new mobile data, and known data placed in the stream. In this, the new mobile data and the known data can be placed, not only in at least part of the normal data region assigned to the normal data, but also at least in part of the existing mobile data region, assigned to the existing mobile data. That is, normal data, new mobile data, and existing mobile data can coexist.

(000381) FIG. 54 illustrates an example of the stream format after interleaving. Referring to FIG. 54, a stream including a mobile data group includes 208 data segments. Five leading segments among them correspond to RS parity data and therefore are excluded from the mobile data group. Thus, the mobile data group of the 203 data segments in total is divided into 15 mobile data blocks. More specifically, the mobile data group includes blocks B1 to B10 and SB1 to SB5. Among them, blocks B1 to B10 can correspond to mobile data placed in the existing mobile data region as shown in FIG. 8. In contrast, blocks SB1 to SB5 can correspond to new mobile data destined for the existing normal data region. SB5 includes an MPEG header and an RS parity, because of backward compatibility.

(000382) B1 to B10 each include 16 segments, SB1 and SB4 may each include 31 segments, and SB2 and SB3 may each include 14 segments.

(000383) These blocks, ie B1 to B10 and SB1 to SB5 can be combined in different ways and encoded into blocks.

(000384) That is, as described above, the block mode can be set in various ways, such as 00 or 01. SCB blocks, when the block mode is set to "00", and a Send Block Length SCCC (SOBL) and an SCCC Emission Block Length (SIBL) of the SCB blocks are presented below. Table 10

(000385) With reference to Table 10, B1 to B10 becomes SCB1 to SCB10.

(000386) On the other hand, the SCB blocks, when the block mode is set to "01", and the SCCC Send Block Length (SOBL) and the SCCC Input Block Length (SIBL) of the SCB blocks are presented below. Table 11

(000387) Referring to Table 11, B1 and B6 are combined to generate an SCB1, B2 and B7, B3 and B8, B4 and B9, and B5 and B10 are combined to generate SCB2, SCB3, SCB4 and SCB5, respectively. Also, the length of the input block varies depending on whether the ratio is 1/2 or 1/4.

(000388) As described above, SCB blocks are generated, by combining B1 to B10, when new mobile data is not placed, that is, in CMM mode operation.

(000389) In SFCMM mode, where new mobile data is placed, blocks can be combined differently to generate SCB blocks. That is, existing mobile data and new mobile data can be combined so that SCCC block encoding can be performed. Tables 12 and 13 below show examples of blocks being combined differently according to RS frame mode and interval mode. Table 12

(000390) In Table 12, RS frame mode indicates information, informing whether a range includes a set (when RS frame mode is 00), or whether a range includes a plurality of sets, such as primary set and secondary set (when RS frame mode is 01). The SCCC block mode indicates information indicating whether the mode is to process an individual SCCC block, or whether the mode is to process the SCCC block, by combining a plurality of blocks, as in the block mode described above.

(000391) Table 12 shows that the interval mode is 00. The interval mode is information indicating a basis for discriminating a beginning and an end of the interval. That is, interval mode 00 implies that the part including B1 to B10 and SB1 to SB5 for the same interval is classified as an interval, and interval mode 01 implies that B1 and B2 are given to a previous interval, and B1 and B2 of the next range are included in the current range, so that the part including 15 blocks in total is classified as a range. Interval mode can be called up in different ways, depending on a version of a standard document. For example, it can be called a block-extension mode. This will be explained in detail below.

(000392) Referring to Table 12, when RS frame mode is 00 and SCCC block mode is 00, B1 through B8 are used as SCB1 through SCB8, and B9 and SB1 are combined to generate SCB9. B10 and SB2 are combined to generate SCB10, and SB3 and SB4 are used as SCB11 and SCB12, respectively. In contrast, when SCCC block mode is 01, B1, B6, and SB3 are combined and used as SCB1, B2 + B7 + SB4 are used as SCB2, and B3 + B8, B4 + B9 + SB1, and B5 + B10 + SB2 are used as SCB3, SCB4 and SCB5 respectively.

(000393) In contrast, when RS frame mode is 01, and SCCC block mode is 00, B1, B2, B9 + SB1, B10 + SB2, SB3, and SB4 are used as SCB1 to SCB6, respectively. When SCCC block mode is 01, B1 + SB3 + B9 + SB1 is used as SCB1, and B2 + SB4 + B10 + SB2 is used as SCB2.

(000394) In addition, when the interval mode is 01, and the new mobile data is arranged according to the first, second, and third modes as described above, SCCC blocks can be combined as listed in table a follow. Table 13

(000395) Referring to Table 13, according to the setting status, such as RS frame mode and SCCC block mode, B1 to B10 and SB1 to SB5 can be combined in various ways.

(000396) When the interval mode is 01, and the new mobile data is placed across the normal data region, according to the fourth mode, as described above, the SCB blocks can be generated in various combinations, as shown in table below. Table 14

(000397) As described above, existing mobile data, normal data, and new mobile data can be classified into blocks, and blocks can be combined in various ways, according to the mode, in order to generate SCCC blocks . Thus, the generated SCCC blocks can be combined to build the RS frame.

(000398) Such combining and encoding blocks can be performed by the data preprocessor 100 described in the previous embodiments. More specifically, block processor 120 of data preprocessor 100 can combine blocks and perform block encoding. Processes other than combination have been described in the previous embodiments and therefore their redundant descriptions are omitted here.

(000399) On the other hand, the coding rate for coding the SCCC block, i.e. an external SCCC code rate can be determined differently, according to an external code mode, in detail, which is shown in the table following: Table 15

(000400) As described in Table 15, the SCCC external code mode can be set in various ways, such as 00, 01, 10, and 11. As for 00, the SCCC block is coded in code rate of 1/2 . As for 01, the SCCC block is encoded at the code rate of 1/4. As for 10, the SCCC block is encoded at the 1/3 code rate. The code rate can be changed in various ways according to the standard version. A newly added code rate can be assigned to SCCC external code mode 11. The correspondence relationship between the above described SCCC external code mode and code rate can be changed. Data preprocessor 100 can encode the SCC block by an appropriate code rate in accordance with an external code mode setting status. External code mode setting status can be notified by controller 310, or by other components, or identified through a separate signaling channel. However, the 1/3 code rate receives 1 bit input and outputs 3 bits. An encoder can be configured differently. For example, the encoder can be configured by combining the code rate 1/2 and the code rate of an M, or by tagging a broadcast from a 4-state convolution encoder.

[Block Extension Mode: BEM]

(000401) As described above, the encoding method of the blocks existing in the interval differs, according to the interval mode, or the block extension mode. As described above, when the block extension mode is 00, a part including B1 to B10 and SB1 to SB5 for the same interval is classified as an interval. When block span mode is 01, B1 and B2 are sent to the previous interval, and a part including B1 and B2 from the next interval in the current interval is classified as an interval.

(000402) Range blocks can be sorted into group regions. For example, four blocks B4 to B7 can be classified into a group A region, two blocks B3 and B8 can be classified into a group B region, two blocks B2 and B9 can be classified into a group C region, and two blocks B1 and B10 can be classified into a group D region. In addition, four blocks SB1 to SB4 generated by interleaving the 38 packets, which are the normal data region, can be referred to as an E group region.

(000403) When the span mode for blocks of certain range is 01, the group A and B regions, including blocks B3 to B8, can be defined as a primary set. Blocks B1 and B2 are sent to the previous interval, and group regions C, D, and E, including blocks B9 and B10, blocks SB1 to S4, and blocks B1 and B2 of the next interval, can be defined new secondary sets. The secondary set can fill the top/hind region with long training data of the length corresponding to a data segment, similar to the main set, and can improve the top/hind region receive performance up to the level equal to the receive performance of the body region.

(000404) When the specified range block extension mode is 00, the main set is the same as in the case of BEM 01, but the secondary set is different. The secondary set can be defined, including blocks B1 and B2, blocks B9 and B10, and blocks SB1 to SB4 of the current range. Unlike the primary set, the secondary set has a saw-shaped upper/back region and therefore cannot populate the upper/back region with long training data. Therefore, the reception performance of the upper/back region is inferior to that of the body region.

(000405) On the other hand, when certain two intervals are adjacent to each other, such as the BEM 00 mode, the long training data can fill an intersection part of its upper/back regions in a saw shape. As shown in FIGS. 64 and 65, in the region where the two BEM 00 mode intervals are adjacent and their saws are engaged, their segmented workouts are connected. As a result, the training is long as long as a data segment can be generated. FIGS. 64 and 65 mark the location of the Trellis encoder initialization byte and the location of the known data (byte).

(000406) When an M/H frame is generated, according to a service type, an interval (SFCMM interval) filled with the new mobile data can be placed adjacent to an interval (SMM interval) filled with the existing mobile data or ranges (full key ranges) filling 156 packets with normal data. At this time, when the BEM mode of the SFCMM range is 00, blocks can be combined without problems even if the CMM range, or the entire main range, is arranged as the adjacent range. Out of 16 intervals in an M/H subframe, when an interval BEM 00 is arranged in Interval no. 0, and a CMM range is arranged in Range no. 1, the combination of blocks B1 to B10 in interval no. 0 and from blocks SB1 to SB4 is coded in blocks. Likewise, in Interval no. 1, the combination of blocks B1 to B10 in Interval no. 1 is coded in blocks.

(000407) On the other hand, when the BEM mode of the SFCMM range is 01, and the CMM range, or the entire major range is arranged as the adjacent range, an orphan region must be considered. The orphan region indicates a region, which is difficult to use in any interval, because a plurality of intervals of different types are continuously arranged.

(000408) For example, among the 16 intervals in subframe M/H, as long as an interval BEM 01 is allocated to Interval no. 0, and the CMM range is allocated to Range no. 1, blocks B1 and B2 in Interval no. 0 are sent to a previous slot, and blocks B3 to B10 and SB1 to SB4, and blocks B1 and B2 of the next slot are embedded and then coded into blocks. In other words, two gaps filled with mobile data 1.0 and mobile data 1.1, which are incompatible with each other, must avoid mutual interference, according to the block coding scheme of BEM 01.

(000409) On the other hand, the interval with BEM 00 and the interval with BEM 01 can be defined, not to be combined with each other. In contrast, in BEM 01, CMM mode, BEM 01 mode, and full main mode ranges can be combined and used together. In this case, a region that is difficult to use, because of the mode difference, is considered and used as the orphan region.

[Orphan Region]

(000410) The orphan region, to avoid the interference of the two gaps, differs according to what kind of gap, the gap of BEM 01 is adjacent, and according to the order of the adjacent gaps.

(000411) First, when an (i)-th interval is the CMM interval, and a (i +1)-th interval is the BEM 01 interval, blocks B1 and B2 exist in the upper region of the BEM 01 interval are sent to the previous interval. However, since the CMM interval is not coded in blocks using the blocks B1 and B2 of the next interval, the region of blocks B1 and B2 of the (i+1)-th interval remains unassigned to any service. This region is defined as an orphan of type 1. Similarly, when the (i)th interval is the complete major interval, and the (i +1)th following interval is the BEM 01 interval, the block region B1 and B2 of the (i+1)-th interval remains unassigned to any service and therefore the type 1 orphan can be generated.

(000412) Second, when the (i)-th interval is the BEM 01 interval, and the (i +1)-th next interval is the CMM interval, block encoding is performed using blocks B1 and B2 of the next interval in the (i)-th interval BEM 01 and thus blocks B1 and B2 are not available in the next interval. That is, since the next CMM interval is defined as a double-frame mode, a service is only assigned to the primary set, and the secondary set must be empty. At this time, in the secondary set, including blocks B1 and B2 and B9 and B10, blocks B1 and B2 are used by the (i)-th previous interval, but the remaining region of blocks B9 and B10 remains unassigned to any service . This region is defined as a type 2 orphan.

(000413) Finally, when the (i)th interval being the BEM 01 interval, and the (i+1)th interval being the complete major interval are adjacent, a type 3 orphan is generated. When BEM 01 interval uses the region corresponding to blocks B1 and B2 from the next complete major interval, normal data cannot be transmitted over the 32 largest packets existing in the region of blocks B1 and B2 of the next 156 intervals. That is, part of the first 32 packets of the next interval, which corresponds to the region of blocks B1 and B2, is used in the interval BEM 01 being the (i)-th interval, but the remaining region does not correspond to the region of block B1 and B2 in the 32 packages it remains unallocated to any service. In the first 32 packets of the next interval, the remaining region not corresponding to block region B1 and B2 is interleaved and then distributed in part of group regions A and B in group format. Thus, the type 3 orphan is generated in the body region of the next interval.

(000414) [Using Orphans]

(000415) The orphan region can include, if necessary, the new mobile data, the training data, or the dummy byte. When the orphan region is filled with the new mobile data, the presence or absence and a type of the corresponding data and signaling information necessary for the receiver to recognize and decode the data can be added.

(000416) When the orphan region is filled with training data, the Trellis encoder is initialized according to the training sequence to generate and then the known byte is set so that the receiver can recognize the sequence of training.

(000417) Table 16 shows locations and use of the orphan, when BEM = 01. Table 16

(000418) Alternatively, when BEM = 01, the orphan region can be generated, as shown in Table 17. Table 17

(000419) As shown in the table, the orphan region can be formed in various locations and different sizes, according to the types of two consecutive intervals. In addition, the orphan region can be used for various purposes such as training data and fictitious usage. Although Tables 16 and 17 do not show mobile data being used in the orphan region, this case is possible.

(000420) On the other hand, when the orphan region is used, a method for processing the stream from the digital broadcast transmitter may include a step of generating the stream to generate the stream, wherein a plurality of intervals of different types, including by at least one of the existing mobile data, normal data, and new mobile data in different formats are arranged consecutively, and a transmission step for stream encoding and interleaving and issuing the transport stream. Here, the transmission step can be performed by the exciter 400 of the digital broadcast transmitter described above.

(000421) On the other hand, the stream generation step can organize at least one of the new mobile data, the training data, and the dummy data into the orphan region, to which the data is not assigned, due to the format difference between consecutive intervals. The use of the orphan region was described above.

(000422) The orphan region can be of various types, as described above.

(000423) That is, when CMM interval and SFCMM interval of block extension mode 01 are arranged consecutively, or when the complete main interval, including only normal data, and SFCMM interval of block extension mode 01 are arranged consecutively, the first type of orphan region may appear at the top of the SFCMM range.

(000424) When the 01 block span mode SFCMM range and the CMM range are arranged consecutively, the second type orphan may appear at a later part of the CMM range.

(000425) When the 01 block span mode SFCMM range and the complete main range including only normal data are arranged consecutively, the third type of orphan region can appear in a body part of the complete main range.

(000426) Herein, the CMM interval is the interval, in which the existing mobile data is placed in the first region allocated for the existing mobile data, and normal data is placed in the second region allocated for the normal data, as described above.

(000427) The SFCMM range is the range, in which new mobile data is placed in at least a part of the entire region, including the first region and the second region, according to the default mode.

(000428) FIG. 58 illustrates a flow structure, showing the first type of orphan region after interleaving, and FIG. 59 illustrates a flow structure, showing the first type of orphan region before interleaving.

(000429) FIG. 60 illustrates a flow structure showing the second type of orphan region after interleaving, and FIG. 61 illustrates a flow structure, showing the second type of orphan region before interleaving.

(000430) FIG. 62 illustrates a flow structure showing the third type of orphan region after interleaving, and FIG. 63 illustrates a flow structure, showing the third type of orphan region before interleaving.

(000431) According to the drawings, the orphan can be formed in various positions, according to the gap arrangement patterns.

(000432) At the same time, the transmitted transport stream from a digital broadcast transmitter can be received and processed by the digital broadcast receiver.

(000433) That is, the digital broadcast receiver may include a receiver for receiving the encoded and interleaved transport stream, while the plurality of intervals of different types including at least one of existing mobile data, normal data, and new mobile data in different formats is consecutively arranged, a demodulator to demodulate the transport stream, an equalizer to equalize the demodulated transport stream, and a decoder to decode the new mobile data from the equalized stream. Here, the transport stream can include the orphan region, to which the data is not allocated, because of the format difference between the consecutive intervals, and at least one of the new mobile data, the training data, and the dummy data can be placed in the orphan region.

(000434) The digital broadcast receiver can detect and process only the data, which it can process, according to its type, that is, according to the fact that it is the normal data receiver, the CMM receiver, the SFCMM receiver , or the common receiver.

(000435) On the other hand, signaling information can tell if data exists in the orphan region and the type of data, as described above. That is, the digital broadcast receiver can additionally include a signaling decoder to decode the signaling information and thus identify whether the data exists in the orphan region and the type of the data.

[Data Signaling]

(000436) As described above, information such as the number of new mobile data and existing data packets added, or the code rate, can be transmitted to the receiver as signaling information.

(000437) For example, the signaling information can be transmitted through the reserved area of the TPC. In this case, "Early Signaling" can be achieved by transmitting current frame information over some subframes, and next frame information over other subframes. That is, a certain TPC parameter and FIC data can be signaled in advance.

(000438) More specifically, an M/H frame can be divided into five sub-frames as shown in FIG. 55. Parameters, TPC, such as sub_frame_number, slot_number, parade_id, parade_repetition, cycle_minus_1, parade_continuity_counter, fic_version, and the aforementioned added interval mode can transmit the current frame information over the five sub-frames. On the other hand, TPC parameters such as SGN, number_of_groups_minus_1, FEC Modes, TNoG, and the number of new mobile data packets, or existing added data packets, or code rate, as mentioned above, can be recorded differently , according to the number of subframes. That is, sub-frames no. 0 and no. 1 can transmit the information of the current frame, and subframes no. 2, no. 3, no. 4 can transmit the information of the next frame, considering the Stop Repetition Cycle (PRC). As for TNoG, sub-frames no. 0 and no. 1 can transmit only the information of the current frame, and subframes no. 2, no. 3, and no. 4 can transmit the information of the current frame and the next frame.

(000439) In detail, TPC information can be generated as in the following table. Table 18

(000440) As shown in Table 18, when the number of subframes is less than or equal to 1, that is, when the number of subframes is no. 0 or no. 1, Various information of the current M/H frame is transmitted. When the number of subframes is greater than or equal to 2, that is, when the number of subframes is n°. 2, no. 3 or no. 4, various information of the next M/H frame can be transmitted considering the Stop Repetition Cycle (PRC). Therefore, the information in the following table can be known in advance and thus the processing speed can be improved.

(000441) At the same time, the receiver structure can be modified, in accordance with variations of the above-described embodiments. That is, the receiver can decode the data, which is combined in various ways, according to block mode, and encoded into blocks, and restore existing mobile data, normal data, and new mobile data. Furthermore, the receiver can identify the signaling information of the next frame in advance, so as to prepare the process, according to the identified information.

(000442) More specifically, in the digital broadcast receiver as constructed in FIG. 51, the receiver 5100 receives the stream generated by combining the data placed in the existing mobile data region and the new mobile data placed in the normal data region, based on the blocks and performing SCCC encoding.

(000443) Here, the stream is split, based on frames, and a frame is split into a plurality of sub-frames. At least some of the subframes can include the signaling information of the current frame, and the remaining subframes can include the signaling information of the next frame, considering the Stop Repeat Cycle (PRC). For example, among the five sub-frames in total, sub-frames no. 0 and no. 1 may include the information of the current frame, and sub-frames no. 2, no. 3 and no. 4 may include the information in the next table, considering the PRC.

(000444) In addition, the stream described above may be the stream encoded by SCCC by the digital broadcast transmitter at one of the 1/2 rate, the 1/3 rate, and the 1/4 rate.

(000445) When the above described stream is transmitted, the demodulator 5200 demodulates the stream and the equalizer 5300 equalizes the demodulated stream.

(000446) The decoder 5400 decodes at least one of the existing mobile data and the new mobile data from the equalized stream. In this case, the processing of the next frame can be prepared in advance using the frame information contained in each subframe.

(000447) As described above, the digital broadcast receiver can properly process the stream transmitted from the digital broadcast transmitter, according to various embodiments. The explanation and illustration of the method for processing the digital broadcast receiver stream is omitted.

(000448) Since the receiver, according to various modified embodiments, is similar to other embodiments described above, the explanation and illustration of the receiver is omitted.

(000449) On the other hand, FIG. 56 is a diagram of the M/H group format, before the data is interleaved in the above-described compatible mode, i.e., in scalable mode 11a.

(000450) Referring to FIG. 56, the M/H group including the mobile data, includes 208 data segments. When the M/H group is distributed into 156 packets in the M/H interval generated on the basis of 156 packets, the 156 packets are spread over the 208 data segments as the result of the interleaving, according to an interleaving rule of intercalator 430.

(000451) The mobile data group of the 208 data segments is divided into 15 mobile data blocks. Specifically, the mobile data group includes blocks B1 to B10 and blocks SB1 to SB5. Blocks B1 to B10 can correspond to mobile data placed in the existing mobile data region as shown in FIG. 8. In contrast, blocks SB1 to SB5 can correspond to new mobile data destined for the existing normal data region. SB5 is the region including MPEG header and RS parity, because of backward compatibility.

(000452) Blocks B1 to B10 each include 16 segments, just like the existing mobile data region, block SB4 can include 31 segments, blocks SB2 and SB3 each can include 14 segments. Block SB1 can have a different length than the distributed segment, according to the mode. When no normal data is transmitted in all frames, that is, when the total data rate of 19.4 Mbps is filled with mobile data, block SB1 can include 32 segments. When some normal data is transmitted, block SB1 can include 31 segments.

(000453) Block SB5 is the region, in which the MPEG header and RS parity existing in 51 segments of the body region are distributed. When no normal data is transmitted in all frames, that is, when the total data rate of 19.4 Mbps is filled with the mobile data, the mobile data can be filled to define the SB5 block. This corresponds to the incompatible mode described above. As above, when all data is assigned as mobile data and therefore there is no need to consider compatibility, the region, which includes the distributed MPEG header and the existing RS parity for compatibility with the receiver, which receives the existing normal data, can be re-defined and used as mobile data.

(000454) As mentioned above, blocks, namely B1 to B10 and SB1 to SB5 can be combined and coded into blocks in various ways.

(000455) That is, when SCCC block mode is 00 (block separated), external SCCC code mode is applied differently according to group regions (A, B, C, D). In contrast, when SCCC block mode is 01 (paired block), the external SCCC code mode needs to be the same for all regions. For example, SB1 and SB4, which are the newly added mobile data blocks, conform to the external SCCC code mode defined in the group C region, and the SB2 and SB3 blocks conform to the external SCCC code mode defined in the group region D. Lastly, the SB5 block conforms to the external SCCC code mode defined in the group A region.

(000456) In particular, when block SB5 is obtained, the service is performed only with mobile data. In this case, different SB5 encoding can be applied, considering the compatibility between the receiver to receive the existing mobile data and the receiver to additionally receive the new mobile data.

(000457) That is, when the interval block mode, from which the SB5 block is obtained, is separated, the main set is filled with 1.0 mobile data, and the secondary set is filled with 1.1 and mobile data. , thus, compatibility with receivers to receive mobile data needs to be maintained. Therefore, block SB5 can be independently encoded.

(000458) On the other hand, when the interval block mode, from which the SB5 block is obtained, is paired, only 1.1 mobile data is filled as a single frame and thus compatibility with mobile data receiver existing ones should not be considered. Therefore, the SB5 block can be absorbed into the existing body region and encoded.

(000459) More specifically, similar to incompatible mode, ie scalable mode 11, when new mobile data is placed in every second region in a range, an encoding other than SB5 can be applied, according to the mode of block. For example, when the block mode defined for the corresponding slot is separate mode, including existing mobile data and new mobile data, the block including MPEG header and RS parity region, i.e. SB5, can be encoded independently of the body region in the corresponding range. In contrast, when the block mode is paired mode, including only the new mobile data, the block including the MPEG header and the RS parity region, i.e. SB5, can be encoded together with the remaining part of the region. body. As described above, block encoding can be performed in a number of ways.

(000460) Thus, the digital broadcast receiver for receiving the transport stream checks the mode, according to the signaling data, and detects and reproduces the new mobile data, according to the mode. In other words, when the new mobile data is transmitted in the paired block mode, in the incompatible mode described above (i.e., the fifth mode, or the scalable mode 11), the BS5 block can be decoded along with the included mobile data. in the existing body region, rather than separate decoding.

(000461) As described above, when the known data, i.e. the training sequence exists, it is necessary to initialize memories of the Trellis encoder, before the training sequence is encoded by Trellis. In this case, the region intended for memory initialization, ie the initialization byte, must be provided before the training sequence.

(000462) FIG. 56 presents a flow structure after interleaving. Referring to FIG. 56, the training sequence is displayed in the body region as a plurality of long training sequences, and also appears in the upper/back region as a plurality of long training sequences. Specifically, five long training sequences in total appear in the upper/back region. Unlike the first and fifth training sequences, with respect to the second, third, and fourth training sequences, the Trellis initialization byte can start after a certain byte, instead of starting from the first byte of each segment.

(000463) Such relocation of the Trellis initialization byte is not limited to the top/back region. That is, in some of the plurality of long training sequences included in the body region, the Trellis initialization byte can be designed to start after a certain byte of each segment.

(000464) [PL, SOBL and SIBL sizes, according to block mode]

(000465) At the same time, RS Frame Part Length (PL), SCCC Send Block Length (SOBL), and SCCC Input Block Length (SIBL) sizes may vary, depending on the block mode . The following table shows the PL of the primary RS frame, when the RS frame mode is 00 (ie single image), the SCCC block mode is 00 (ie a separate block), and the extension mode of SCCC block for 01. Table 19

(000466) In addition, the following table shows the PL of the primary RS frame, when the RS frame mode is 00 (ie single image), the SCCC block mode is 01 (ie the paired block), and the SCCC block extension mode is 01. Table 20

(000467) In addition, the following table shows the PL of the secondary RS frame, when the RS frame mode is 01 (ie double frame), the SCCC block mode is 00 (ie a separate block), and the SCCC block extension mode is 01. Table 21

(000468) In addition, the following table shows the SOBL and SIBL, when the SCCC block mode is 00 (ie a separate block), the RS frame mode is 00 (ie single image), and the SCCC block extension mode for 01. Table 22

(000469) The following table shows SOBL and SIBL, when SCCC block mode is 01 (ie paired block), RS frame mode is 01 (ie double frame), and extend mode of SCCC block for 01. Table 23

(000470) As above, PL, SOBL and SIBL in various sizes can be realized according to block mode. The data written in the tables above are merely exemplary and it is understood that the data is not limited to that example.

[Startup]

(000471) On the other hand, when known data, ie training data, is included in the stream as described above, initialization is required. That is, an ATSC-M/H transmission system initializes the Trellis encoder, according to the training sequence, to generate and then set the known byte so that the receiver can recognize the training sequence.

(000472) In BEM 00 mode group format, the Trellis initialization byte is located on a boundary surface of the saw teeth, and the known byte is distributed thereafter. When Trellis encoding is performed from the upper segment to the lower segment, and from the left byte to the right byte, the Trellis encoding is performed on the boundary surface between the saw teeth filled with data from a different range and, therefore, a Trellis encoder memory value cannot be predicted on the boundary surface between the saw teeth filled with the data of the next current interval. Thus, the Trellis encoder must be initialized on each boundary surface of the saw teeth. As shown in FIGS. 56 and 57, the initialization byte can be distributed over each edge of the upper region sawtooth, including blocks B1 and B2, and also over each edge of the posterior region sawtooth, including blocks SB1 to SB4.

(000473) When certain two intervals are adjacent to each other, such as BEM 00, the short workout data for each upper/back region is located and continuously connected in the same segment, thus serving as long workout data. When the two BEM 00 intervals are adjacent to each other and thus the training is concatenated, only the first 12 maximum initialization bytes of the segment, in which the existing training data is used as an initialization mode and the initialization byte existing in a part, in which the saw teeth are interlocked with each other, is inserted and coded by Trellis as the known byte.

(000474) An intermediate initialization byte in the coupled sawtooth portion, except for the first 12 maximum initial bytes of the segment, can be entered as the known byte, or the initialization byte, according to the fact of the BEM interval 00 be adjacent to the same interval, or adjacent to a different interval than the BEM 00 interval. That is, the Trellis encoder operation can be multiplexed in normal mode, or in initialization mode, during the intermediate period of the initialization byte. Since the generated symbol differs according to the mode in which the Trellis encoder multiplexes the input, the symbol value to be used by the receiver as training may differ. Therefore, in order to minimize receiver confusion, when two BEM 00 intervals are adjacent to each other to build the long workout, based on the symbol generated by multiplexing all the intermediate initialization bytes to the known byte, when the interval BEM 00 is not adjacent to the same range, the intermediate boot byte value to be used in boot mode can be determined. That is, the value of the intermediate initialization byte can be determined to emit the same value, as the value of the long training symbol generated in the concatenation case. At this time, the value may be different from the symbol value generated in the concatenation during the first two symbols of the middle initialization byte.

(000475) As mentioned above, the method for processing digital broadcast transmitter stream to generate the long training sequence at the boundary between consecutive intervals can be performed.

(000476) That is, the method for processing the stream of the transmitter may include a stream generating operation to generate the stream, which consecutively arranges the slots including the plurality of blocks and a transmit operation to encode and interleave the stream, and issue a transport stream.

(000477) Here, when the ranges defined for block extension mode 00 for using all blocks of the corresponding range are arranged consecutively, the flow generation operation can put the known data into a predefined segment of each of the adjacent intervals, so that the long training sequence is formed at the boundary between adjacent intervals interlocked with each other in the form of saw teeth. Block extension mode 00 is the mode that uses the blocks B1 and B2 described above in the range. Therefore, at the boundary of the next gap, the saw-tooth part of the previous gap and the saw-tooth part of the next gap are engaged with each other. In this case, the known data is arranged in a suitable segment position of the previous gap and a suitable segment position of the next gap, so that the known data is connected in the saw tooth parts of the two gaps. More specifically, when the known data is placed in the 130th segment of the previous interval and the 15th segment of the next interval, the known data is connected at the boundary to thus form a long training sequence.

(000478) When the first known dice, placed in the sawtooth portion of the adjacent intervals, and the second known dice, placed in the sawtooth portion of the next interval of the adjacent intervals, are alternately linked together at the boundary, a value of the first known data and a value of the second known data can be preset to form the long training sequence, which is known by the digital broadcast receiver.

(000479) Alternatively, the known data can be entered so as to have the same sequence as the long training sequence used in the 01 block extension mode interval, where in some blocks of the corresponding interval are given to other intervals , with reference to the long training sequence.

(000480) FIG. 64 illustrates a flow structure before interleaving when the block extension mode is 00, and FIG. 65 illustrates a flow structure after interleaving when the block extension mode is 00.

(000481) On the other hand, when the known data is put in the form of the long training sequence, as described above, it is not necessary to perform initialization for each known data. Therefore, in this case, the method may further include an operation of initializing the Trellis encoder, before encoding by Trellis the known data corresponding to the first part of the long training sequence.

(000482) In contrast, when intervals defined for different block extent modes are arranged consecutively, the known data cannot continue on the boundary. Therefore, in this case, the transmission operation can initialize the Trellis encoder, before the known data placed in the saw-tooth part, at the boundary between consecutive intervals, is encoded by Trellis.

(000483) On the other hand, when the known data is arranged and transmitted at the boundary, in the form of a long training sequence, a method for processing digital broadcast receiver stream can be properly realized.

(000484) That is, the method for processing digital broadcast receiver stream may include a receive operation to receive the encoded transport stream interleaved with the slots, including the plurality of consecutively arranged blocks, a demodulation operation to demodulate the received transport stream, an equalizing operation to equalize the demodulated transport stream, and a decoding operation to decode the new mobile data from the equalized stream.

(000485) Here, each transport stream interval can include at least one of normal data, existing mobile data, and new mobile data.

(000486) When the intervals defined in block extension mode 00, to use all blocks in a corresponding interval, are arranged consecutively, the transport stream can organize the known data into a predefined segment of each of the adjacent intervals, so that the long training sequence is formed on the boundary of adjacent intervals interlocked with each other in the shape of the saw teeth.

(000487) As described above, each of the known data at the boundary between consecutive previous and subsequent intervals can be continued so as to form the long training sequence known by the digital broadcast transmitter.

(000488) The long training sequence can have the same sequence as the long training sequence used in the interval of block extension mode 01 for providing some blocks in the interval corresponding to other intervals, with reference to the long training sequence.

(000489) The digital broadcast receiver can know whether such long string is used or not by identifying the block extension mode of each slot.

(000490) That is, the method for processing the digital broadcast receiver stream may further include an operation to identify the block extension mode of each slot, by decoding the signaling data for each slot. More specifically, the block extension mode can be written to the TPC of each interval.

(000491) In this case, the digital broadcast receiver can defer the known data, detecting and processing, until the block extension mode of the next slot is identified, even when reception of one slot is completed. That is, when the signaling data of the next slot, among the adjacent slots, is completely decoded and therefore the block extension mode of the next slot is identified as 00, the method can include an operation of detecting and processing the data. known from the sawtooth part at the boundary between adjacent intervals, such as the long training sequence.

(000492) According to another embodiment, signaling data of each slot can be performed to inform information of adjacent slots in advance.

(000493) In this case, the digital broadcast receiver can identify the pre-slot and the next-slot block extension modes by decoding the pre-slot signaling data from the adjacent slots.

(000494) As such, the method for stream processing of the digital broadcast transmitter and the digital broadcast receiver can be performed by the digital broadcast transmitter and the digital broadcast receiver having the structure as shown in the drawings as explained above. For example, the digital broadcast receiver may further include a detector to detect and process known data, in addition to essential components such as receiver, demodulator, equalizer, and decoder. In this case, after determining that two block 00 extension mode intervals are received, the detector can detect the long training data placed on the boundary between the intervals, and use it for error correction. Furthermore, the detection result can be provided to at least one of the demodulator, equalizer, and decoder.

(000495) [Training data location, considering RS parity]

(000496) With respect to the segment of the predetermined RS parity value, the receiver can operate normally without causing errors, only when the pre-calculated RS parity value is changed, when the segment data is changed during the encoder initialization Trellis. When the packet includes the Trellis start byte, the unsystematic RS 20 parity bytes of the corresponding packet cannot precede the Trellis start byte. The Trellis initialization byte can only exist in one place, where this constraint condition is satisfied, and that initialization byte can generate the training data.

(000497) As shown in FIGS. 64 and 65, in order to place the Trellis initialization byte ahead of RS parity, the RS parity location is changed differently from the BEM 01 interval group format. That is, in the BEM 01 interval group format , only RS parity is located in the first 5 segments out of the 208 data segments after the interleaving. However, in the case of interval BEM 00, the parity location RS can be changed so that a lower part of block B2 is filled, as shown in Figs. 64 and 65.

(000498) When the changed RS parity is considered, the training data is distributed over the BEM 00 interval, so that the first, second and third training data are located in the 7th and 8th segments, in the 20th and 21st ° segments, and in the 31st and 32nd segments of the region of blocks B1 and B2. The changed RS parities can be arranged in the 33° to 37° segments of the region of blocks B1 and B2. In addition, the first, second, third, fourth, and fifth training data can be located in the 134th and 135th segments, in the 150° and 151st segments, in the 163th and 164th segments, in the 176th and 177th segments. segments, and in the 187° and 188° segments of the posterior region, respectively. When two BEM 00 intervals are adjacent to generate the concatenated long training data, the first training data from the block region B1 and B2 can be linked to the third training data from the later region, the second training data from the block region B1 and B2 can be linked to the fourth training data of the posterior region, and the third training data of the block region B1 and B2 can be linked to the fifth training data of the posterior region.

(000499) As above, training data can be put into various forms and initialized.

(000500) The digital broadcast receiver detects the training data from where the training data is placed. More specifically, the signaling detector or decoder as shown in FIG. 52, can detect information indicating the location of arrangement of training data. Thus, training data can be detected from the identified location and the error can be corrected.

(000501) Although some embodiments of the present general inventive concept have been shown and described, it will be appreciated by those skilled in the art what changes can be made to these embodiments without departing from the principles and spirit of the general inventive concept which scope is defined in the appended claims and their equivalents.

Claims (15)

1. METHOD FOR FLOW PROCESSING OF A DIGITAL BROADCASTING TRANSMITTER, characterized by the fact that it comprises: generation of a stream, in which a plurality of intervals of different formats are consecutively arranged; and encoding and interleaving the generated stream, and outputting the encoded and interleaved stream as a transport stream, wherein the stream generation comprises at least one arrangement of training data and dummy data in a generated orphan region, according to a difference of the formats between consecutive intervals of the plurality of intervals. 2. METHOD FOR FLOW PROCESSING, according to claim 1, characterized in that the orphan region is one of: a first type of orphan region generated in an upper part of a Scalable Full Channel Mobile Mode (SFCMM) interval, when a Core Mobile Mode (CMM) range and the SFCMM range of a 01 block extension mode are arranged consecutively, or when a complete core range, comprising only the normal data, and the SFCMM range of the 01 block extension mode are arranged consecutively, a second type of orphan region generated in a later part of the CMM interval, when the SFCMM interval of block extension mode 01 and the CMM interval are arranged consecutively, and a third type of orphan region generated in a body part of the full major interval, when the SFCMM interval of block-extending mode 01 and the full major interval, comprising only the normal data, are arranged consecutively. 3. METHOD FOR FLOW PROCESSING, according to claim 1, characterized in that the CMM interval is an interval, which organizes the existing mobile data in a first region allocated to the existing mobile data, and organizes the normal data in a second region allocated for normal data; and the SFCMM interval is an interval, which organizes the new mobile data, according to a defined mode, at least in part of the entire region covering the first region and the second region. 4. METHOD FOR FLOW PROCESSING, according to claim 1, characterized in that the flow generation comprises: when new mobile data are placed in the orphan region, addition to the signaling data flow, indicating a presence and a type of new mobile data placed in the orphan region. 5. METHOD FOR FLOW PROCESSING, according to claim 1, characterized in that the flow coding comprises: when training data is placed in the orphan region, initialization of a Trellis encoder, according to the training data, and Trellis encoding, by the initialized Trellis encoder, of the training data. 6. DIGITAL BROADCASTING TRANSMITTER, characterized in that it comprises: a flow generator to generate a flow, in which a plurality of intervals of different formats are consecutively arranged; and driver for encoding and interleaving the generated stream, and outputting the encoded and interleaved stream as a transport stream, wherein the stream generator organizes at least one of the training data and dummy data into an orphan region generated by a difference of formats between consecutive intervals of the plurality of intervals. 7. DIGITAL BROADCASTING TRANSMITTER, according to claim 6, characterized in that the orphan region is one of: a first type of orphan region generated in an upper part of a Scalable Full Channel Mobile Mode (SFCMM) range, when a Core Mobile Mode (CMM) range and the SFCMM range of a 01 block extension mode are arranged consecutively, or when a complete main range, comprising only the normal data, and the SFCMM range of the 01 block extension mode, are arranged consecutively, a second type of orphan region generated in a later part of the CMM interval, when the SFCMM interval of block extension mode 01 and the CMM interval are arranged consecutively, and a third type of orphan region generated in a body part of the full major interval, when the SFCMM interval of block-extending mode 01 and the full major interval, comprising only the normal data, are arranged consecutively. 8. DIGITAL BROADCASTING TRANSMITTER according to claim 6, characterized in that the CMM interval is an interval, which organizes the existing mobile data in a first region allocated to the existing mobile data, and organizes the normal data in a second region allocated to normal data; and the SFCMM interval is an interval, which organizes the new mobile data according to a mode defined at least in part of the entire region covering the first region and the second region. 9. DIGITAL BROADCASTING TRANSMITTER, according to claim 6, characterized in that when the new mobile data are placed in the orphan region, the flow generator adds the signaling data to the flow, indicating a presence and a type of the new mobile data placed in the orphan region. 10. DIGITAL BROADCASTING TRANSMITTER according to claim 6, characterized in that when the training data is placed in the orphan region, the exciter initializes a Trellis encoder, according to the training data, and the Trellis encoder initialized Trellis encodes training data. 11. METHOD FOR FLOW PROCESSING OF A DIGITAL BROADCASTING RECEIVER, characterized in that it comprises: reception of a coded and interleaved transport stream, while a plurality of intervals of different formats are consecutively arranged; demodulation of the received transport stream; equalization of the demodulated transport stream; and decoding the second mobile data from the equalized stream, wherein the transport stream comprises an orphan region generated by a difference in formats between consecutive intervals of the plurality of intervals, and at least one of the second mobile data, training data, and dummy data is placed in the orphan region. 12. METHOD FOR FLOW PROCESSING, according to claim 11, characterized in that the orphan region is one of: a first type of orphan region generated in an upper part of a Scalable Full Channel Mobile Mode (SFCMM) interval, when a Core Mobile Mode (CMM) range and the SFCMM range of a 01 block extension mode are arranged consecutively, or when a complete core range, comprising only the normal data, and the SFCMM range of the 01 block extension mode are arranged consecutively, a second type of orphan region generated in a later part of the CMM interval, when the SFCMM interval of block extension mode 01 and the CMM interval are arranged consecutively, and a third type of orphan region generated in a body part of the complete major interval, when the SFCMM interval of block extension mode 01 and the complete major interval, comprising only the normal data, are arranged consecutively; 13. METHOD FOR FLOW PROCESSING, according to claim 11, characterized in that the CMM interval is an interval, which organizes first mobile data in a first region allocated for the first mobile data, and organizes normal data in a second region allocated to normal data; and the SFCMM interval is an interval, which organizes the second mobile data, according to a defined mode, at least in part of the whole region, which encompasses the first region and the second region. 14. DIGITAL BROADCASTING RECEIVER, characterized in that it comprises: receiver for receiving an encoded and interleaved transport stream, while a plurality of intervals of different formats are consecutively arranged; demodulator to demodulate the received transport stream; equalizer to equalize the demodulated transport stream; and decoder for decoding the second mobile data of the equalized stream, wherein the transport stream comprises an orphan region generated by a format difference between consecutive intervals of the plurality of intervals, and at least one of the second mobile data, training data, and dummy data is placed in the orphan region. 15. DIGITAL BROADCASTING RECEIVER, according to claim 14, characterized in that the orphan region is one of: a first type of orphan region generated at an upper part of a Scalable Full Channel Mobile Mode (SFCMM) range, when a Core Mobile Mode (CMM) range and the SFCMM range of a 01 block extension mode are arranged consecutively, or when a complete main range, comprising only the normal data, and the SFCMM range of the 01 block extension mode are arranged consecutively, a second type of orphan region generated in a later part of the CMM interval, when the 01 block extension mode SFCMM interval and the CMM interval are arranged consecutively, and a third type of orphan region generated in a body part of the full major interval, when the SFCMM interval of block extension mode 01 and the complete major interval comprising only normal data are arranged consecutively.

Images