Digital broadcasting system and data processing method
Claim Score by NHIP
Abstract
A digital broadcasting system and a method of processing data are disclosed, which are robust to error when mobile service data are transmitted. To this end, additional encoding is performed for the mobile service data, whereby it is possible to strongly cope with fast channel change while giving robustness to the mobile service data.

Term
Projected expiry 26 June 2028.
- Priority and filed
- Granted
- Today
- Projected expiry
18 claims: 4 independent, 14 dependent
- 1A broadcast transmitter comprising:a Reed-Solomon (RS) frame encoder for generating an RS frame by adding RS parity data and Cyclic Redundancy Check (CRC) data to an RS frame payload, the RS frame payload comprising a plurality of mobile and handheld (M/H) transport packets, each of the plurality of M/H transport packets including an M-byte header, k stuffing bytes, and an (N-M-k)-byte payload, wherein the (N-M-k)-byte payload includes mobile service data, wherein N and M are natural numbers, and k is equal to or greater than 0;a group formatter for mapping a portion of the RS frame into at least one region of a group that includes a plurality of regions and adding known data sequences, fast information channel (FIC) data and transmission parameter channel (TPC) data to the group, wherein the FIC data contains information for rapid mobile service acquisition, and wherein the TPC data contains FIC version information for identifying an update of the FIC data;and a modulator for modulating a broadcast signal including the group.
- 8A method of processing broadcast data in a broadcast transmitter, the method comprising:generating, by a Reed-Solomon (RS) frame encoder, an RS frame by adding RS parity data and Cyclic Redundancy Check (CRC) data to an RS frame payload, the RS frame payload comprising a plurality of mobile and handheld (M/H) transport packets, each of the plurality of M/H transport packets including an M-byte header, k stuffing bytes, and an (N-M-k)-byte payload, wherein the (N-M-k)-byte payload includes mobile service data, wherein N and M are natural numbers, and k is equal to or greater than 0;mapping, by a group formatter, a portion of the RS frame into at least one region of a group that includes a plurality of regions and adding known data sequences, fast information channel (FIC) data and transmission parameter channel (TPC) data to the group, wherein the FIC data contains information for rapid mobile service acquisition, and wherein the TPC data contains FIC version information for identifying an update of the FIC data;and modulating, by a modulator, a broadcast signal including the group.
- 15Broadest claimClaim Score 49, average(NHIP)A method of transmitting a broadcast signal in a broadcast transmitter, the method comprising:formatting broadcast service data for a service and service signaling data to output data packets, wherein each data packet includes a header and a payload, the header including type information indicating a type of the data packet;encoding data of the data packets to add first parity data;interleaving the encoded data;encoding transmission parameter data for signaling the broadcast service data to add second parity data;and transmitting a signal frame including the interleaved data and the encoded transmission parameter data, wherein the signal frame is configured to multiple sub-frames that are concatenated in time, wherein the transmission parameter data include information related to at least one of the multiple sub-frames, and wherein the service signaling information includes service type information and hidden information for the service.
- 16A broadcast transmitter for transmitting a broadcast signal, the broadcast transmitter comprising:a service multiplexer to format broadcast service data for a service and service signaling data to output data packets, wherein each data packet includes a header and a payload, the header including type information indicating a type of the data packet;a first encoder to encode data of the data packets to add first parity data;an interleaver to interleave the encoded data;a second encoder to encode transmission parameter data for signaling the broadcast service data to add second parity data;and a transmitting unit to transmit a signal frame including the interleaved data and the encoded transmission parameter data, wherein the signal frame is configured to multiple sub-frames that are concatenated in time, wherein the transmission parameter data include information related to at least one of the multiple sub-frames, and wherein the service signaling data include service type information and hidden information for the service.
Independent claims4
827 paragraphs in 5 sections, as filed
CROSS-REFERENCE TO RELATED APPLICATIONS
0001This application is a Reissue application of U.S. Pat. No. 8,374,252, issued on Feb. 12, 2013 from U.S. patent application Ser. No. 12/976,963, filed on Dec. 22, 2010, which is a continuation of U.S. patent application Ser. No. 12/146,938, filed on Jun. 26, 2008, now U.S. Pat. No. 7,953,157, which claims the benefit of earlier filing date and right of priority to Korean Patent Application No. 10-2008-0060491, filed on Jun. 25, 2008, and also claims the benefit of U.S. Provisional Application Ser. Nos. 60/946,143, filed on Jun. 26, 2007, 60/957,714, filed on Aug. 24, 2007, 60/974,084, filed on Sep. 21, 2007, and 60/977,379, filed on Oct. 4, 2007, the contents of which are all hereby incorporated by reference herein in their entirety.
BACKGROUND OF THE INVENTION
00021. Field of the Invention
0003The present invention relates to a digital broadcasting system, and more particularly, to a digital broadcasting system and a data processing method.
00042. Discussion of the Related Art
0005The Vestigial Sideband (VSB) transmission mode, which is adopted as the standard for digital broadcasting in North America and the Republic of Korea, is a system using a single carrier method. Therefore, the receiving performance of the digital broadcast receiving system may be deteriorated in a poor channel environment. Particularly, since resistance to changes in channels and noise is more highly required when using portable and/or mobile broadcast receivers, the receiving performance may be even more deteriorated when transmitting mobile service data by the VSB transmission mode.
SUMMARY OF THE INVENTION
0006Accordingly, the present invention is directed to a digital broadcasting system and a data processing method that substantially obviate one or more problems due to limitations and disadvantages of the related art.
0007An object of the present invention is to provide a digital broadcasting system and a data processing method that are highly resistant to channel changes and noise.
0008Another object of the present invention is to provide a digital broadcasting system and a data processing method that can enhance the receiving performance of the receiving system by performing additional encoding on mobile service data and by transmitting the processed data to the receiving system.
0009A further object of the present invention is to provide a digital broadcasting system and a data processing method that can also enhance the receiving performance of the receiving system by inserting known data already known in accordance with a pre-agreement between the receiving system and the transmitting system in a predetermined region within a data region.
0010Additional advantages, objects, and features of the invention will be set forth in part in the description which follows and in part will become apparent to those having ordinary skill in the art upon examination of the following or may be learned from practice of the invention. The objectives and other advantages of the invention may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
0011To achieve these objects and other advantages and in accordance with the purpose of the invention, as embodied and broadly described herein, a digital broadcast transmitting system may include a service multiplexer and a transmitter. The service multiplexer may multiplex mobile service data and main service data at a predetermined coding rate and may transmit the multiplexed data to the transmitter. The transmitter may perform additional encoding on the mobile service data being transmitted from the service multiplexer. The transmitter may also group a plurality of additionally encoded mobile service data packets so as to form a data group. The transmitter may multiplex mobile service data packets including mobile service data and main service data packets including main service data in packet units and may transmit the multiplexed data packets to a digital broadcast receiving system.
0012Herein, the data group may be divided into a plurality of regions depending upon a degree of interference of the main service data. Also, a long known data sequence may be periodically inserted in regions without interference of the main service data. Also, a digital broadcast receiving system according to an embodiment of the present invention may be used for modulating and channel equalizing the known data sequence.
0013In another aspect of the present invention, a receiving system may include a signal receiving unit, a demodulating unit, a demultiplexer, and IP data processor. The signal receiving unit receives a broadcasting signal including RS frame and main service data, the RS frame consisting of a plurality of MPH service data packets, each of which includes MPH header of M bytes including identification information and payload of N-M bytes. The demodulating unit demodulates data of the RS frame of the broadcasting signal received in the signal receiving unit. The demultiplexer identifies an MPH service data packet including IP datagram of mobile service data with reference to MPH header within each MPH service data packet within the RS frame demodulated by the demodulating unit, and outputs IP datagram of the mobile service data from payload within the identified MPH service data packet. The IP data processor outputs audio/video data for audio/video decoding if the IP datagram of the mobile service data output from the demultiplexer is the audio/video data.
0014In another aspect of the present invention, a method of processing data in a receiving system may include receiving a broadcasting signal including RS frame and main service data, the RS frame consisting of a plurality of MPH service data packets, each of which includes MPH header of M bytes including identification information and payload of N-M bytes, demodulating data of the RS frame of the received broadcasting signal, identifying an MPH service data packet including IP datagram of mobile service data with reference to MPH header within each MPH service data packet within the demodulated RS frame, and extracting IP datagram of the mobile service data from payload within the identified MPH service data packet, and outputting audio/video data for audio/video decoding if the extracted IP datagram of the mobile service data is the audio/video data.
0015It is to be understood that both the foregoing general description and the following detailed description of the present invention are exemplary and explanatory and are intended to provide further explanation of the invention as claimed.
BRIEF DESCRIPTION OF THE DRAWINGS
0016The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the principle of the invention. In the drawings:
0017<figref idref="DRAWINGS">FIG. 1</figref> illustrates a structure of a MPH frame for transmitting and receiving mobile service data according to the present invention;
0018<figref idref="DRAWINGS">FIG. 2</figref> illustrates an exemplary structure of a VSB frame;
0019<figref idref="DRAWINGS">FIG. 3</figref> illustrates a mapping example of the positions to which the first 4 slots of a sub-frame are assigned with respect to a VSB frame in a space region;
0020<figref idref="DRAWINGS">FIG. 4</figref> illustrates a mapping example of the positions to which the first 4 slots of a sub-frame are assigned with respect to a VSB frame in a time region;
0021<figref idref="DRAWINGS">FIG. 5</figref> illustrates an alignment of data after being data interleaved and identified;
0022<figref idref="DRAWINGS">FIG. 6</figref> illustrates an enlarged portion of the data group shown in <figref idref="DRAWINGS">FIG. 5</figref> for a better understanding of the present invention;
0023<figref idref="DRAWINGS">FIG. 7</figref> illustrates an alignment of data before being data interleaved and identified;
0024<figref idref="DRAWINGS">FIG. 8</figref> illustrates an enlarged portion of the data group shown in <figref idref="DRAWINGS">FIG. 7</figref> for a better understanding of the present invention;
0025<figref idref="DRAWINGS">FIG. 9</figref> illustrates an exemplary assignment order of data groups being assigned to one of 5 sub-frames according to the present invention;
0026<figref idref="DRAWINGS">FIG. 10</figref> illustrates an example of multiple data groups of a single parade being assigned (or allocated) to an MPH frame;
0027<figref idref="DRAWINGS">FIG. 11</figref> illustrates an example of transmitting 3 parades to an MPH frame according to the present invention;
0028<figref idref="DRAWINGS">FIG. 12</figref> illustrates an example of expanding the assignment process of 3 parades to 5 sub-frames within an MPH frame;
0029<figref idref="DRAWINGS">FIG. 13</figref> illustrates a block diagram showing a general structure of a digital broadcast transmitting system according to an embodiment of the present invention;
0030<figref idref="DRAWINGS">FIG. 14</figref> illustrates a block diagram showing an example of a service multiplexer;
0031<figref idref="DRAWINGS">FIG. 15</figref> illustrates a block diagram showing an example of a transmitter according to an embodiment of the present invention;
0032<figref idref="DRAWINGS">FIG. 16</figref> illustrates a block diagram showing an example of a pre-processor according to the present invention;
0033<figref idref="DRAWINGS">FIG. 17</figref> illustrates a conceptual block diagram of the MPH frame encoder according to an embodiment of the present invention;
0034<figref idref="DRAWINGS">FIG. 18</figref> illustrates a detailed block diagram of an RS frame encoder among a plurality of RS frame encoders within an MPH frame encoder;
0035<figref idref="DRAWINGS">FIG. 19(a)</figref> and <figref idref="DRAWINGS">FIG. 19(b)</figref> illustrate a process of one or two RS frame being divided into several portions, based upon an RS frame mode value, and a process of each portion being assigned to a corresponding region within the respective data group;
0036<figref idref="DRAWINGS">FIG. 20(a)</figref> to <figref idref="DRAWINGS">FIG. 20(c)</figref> illustrate error correction encoding and error detection encoding processes according to an embodiment of the present invention;
0037<figref idref="DRAWINGS">FIG. 21</figref> illustrates an example of performing a row permutation (or interleaving) process in super frame units according to the present invention;
0038<figref idref="DRAWINGS">FIG. 22(a)</figref> and <figref idref="DRAWINGS">FIG. 22(b)</figref> illustrate an example of creating an RS frame by grouping data, thereby performing error correction encoding and error detection encoding;
0039<figref idref="DRAWINGS">FIG. 23(a)</figref> and <figref idref="DRAWINGS">FIG. 23(b)</figref> illustrate an exemplary process of dividing an RS frame for configuring a data group according to the present invention;
0040<figref idref="DRAWINGS">FIG. 24</figref> illustrates a block diagram of a block processor according to an embodiment of the present invention;
0041<figref idref="DRAWINGS">FIG. 25</figref> illustrates a detailed block diagram of a convolution encoder of the block processor of <figref idref="DRAWINGS">FIG. 24</figref>;
0042<figref idref="DRAWINGS">FIG. 26</figref> illustrates a symbol interleaver of the block processor of <figref idref="DRAWINGS">FIG. 24</figref>;
0043<figref idref="DRAWINGS">FIG. 27</figref> illustrates a block diagram of a group formatter according to an embodiment of the present invention;
0044<figref idref="DRAWINGS">FIG. 28</figref> illustrates a detailed diagram of one of 12 trellis encoders included in the trellis encoding module of <figref idref="DRAWINGS">FIG. 15</figref>;
0045<figref idref="DRAWINGS">FIG. 29</figref> illustrates an example of assigning signaling information area according to an embodiment of the present invention;
0046<figref idref="DRAWINGS">FIG. 30</figref> illustrates a detailed block diagram of a signaling encoder according to the present invention;
0047<figref idref="DRAWINGS">FIG. 31</figref> illustrates an example of a syntax structure of TPC data according to the present invention;
0048<figref idref="DRAWINGS">FIG. 32</figref> illustrates an example of power saving of in a receiver when transmitting 3 parades to an MPH frame level according to the present invention;
0049<figref idref="DRAWINGS">FIG. 33</figref> illustrates an example of a transmission scenario of the TPC data and the FIC data level according to the present invention;
0050<figref idref="DRAWINGS">FIG. 34</figref> illustrates an example of a training sequence at the byte level according to the present invention;
0051<figref idref="DRAWINGS">FIG. 35</figref> illustrates an example of a training sequence at the symbol according to the present invention;
0052<figref idref="DRAWINGS">FIG. 36</figref> illustrates a block diagram of a demodulating unit in a receiving system according to the present invention;
0053<figref idref="DRAWINGS">FIG. 37</figref> illustrates a data structure showing an example of known data being periodically inserted in valid data according to the present invention;
0054<figref idref="DRAWINGS">FIG. 38</figref> illustrates a block diagram showing a structure of a demodulator of the demodulating unit shown in <figref idref="DRAWINGS">FIG. 36</figref>;
0055<figref idref="DRAWINGS">FIG. 39</figref> illustrates a detailed block diagram of the demodulator shown in <figref idref="DRAWINGS">FIG. 38</figref>;
0056<figref idref="DRAWINGS">FIG. 40</figref> illustrates a block diagram of a frequency offset estimator according to an embodiment of the present invention;
0057<figref idref="DRAWINGS">FIG. 41</figref> illustrates a block diagram of a known data detector and initial frequency offset estimator according to the present invention;
0058<figref idref="DRAWINGS">FIG. 42</figref> illustrates a block diagram of a partial correlator shown in <figref idref="DRAWINGS">FIG. 41</figref>;
0059<figref idref="DRAWINGS">FIG. 43</figref> illustrates a second example of the timing recovery unit according to the present invention;
0060<figref idref="DRAWINGS">FIG. 44(a)</figref> and <figref idref="DRAWINGS">FIG. 44(b)</figref> illustrate examples of detecting timing error in a time domain;
0061<figref idref="DRAWINGS">FIG. 45(a)</figref> and <figref idref="DRAWINGS">FIG. 45(b)</figref> illustrate other examples of detecting timing error in a time domain;
0062<figref idref="DRAWINGS">FIG. 46</figref> illustrates an example of detecting timing error using correlation values of <figref idref="DRAWINGS">FIG. 44</figref> and <figref idref="DRAWINGS">FIG. 45</figref>;
0063<figref idref="DRAWINGS">FIG. 47</figref> illustrates an example of a timing error detector according to the present invention;
0064<figref idref="DRAWINGS">FIG. 48</figref> illustrates an example of detecting timing error in a frequency domain according to an embodiment of the present invention;
0065<figref idref="DRAWINGS">FIG. 49</figref> illustrates another example of a timing error detector according to the present invention;
0066<figref idref="DRAWINGS">FIG. 50</figref> illustrates a block diagram of a DC remover according to an embodiment of the present invention;
0067<figref idref="DRAWINGS">FIG. 51</figref> illustrates an example of shifting sample data inputted to a DC estimator shown in <figref idref="DRAWINGS">FIG. 50</figref>;
0068<figref idref="DRAWINGS">FIG. 52</figref> illustrates a block diagram of a DC remover according to another embodiment of the present invention;
0069<figref idref="DRAWINGS">FIG. 53</figref> illustrates a block diagram of another example of a channel equalizer according to the present invention;
0070<figref idref="DRAWINGS">FIG. 54</figref> illustrates a detailed block diagram of an example of a remaining carrier phase error estimator according to the present invention;
0071<figref idref="DRAWINGS">FIG. 55</figref> illustrates a block diagram of a phase error detector obtaining a remaining carrier phase error and phase noise according to the present invention;
0072<figref idref="DRAWINGS">FIG. 56</figref> illustrates a phase compensator according to an embodiment of the present invention;
0073<figref idref="DRAWINGS">FIG. 57</figref> illustrates a block diagram of another example of a channel equalizer according to the present invention;
0074<figref idref="DRAWINGS">FIG. 58</figref> illustrates a block diagram of another example of a channel equalizer according to the present invention;
0075<figref idref="DRAWINGS">FIG. 59</figref> illustrates a block diagram of another example of a channel equalizer according to the present invention;
0076<figref idref="DRAWINGS">FIG. 60</figref> illustrates a block diagram of an example of a CIR estimator according to the present invention;
0077<figref idref="DRAWINGS">FIG. 61</figref> illustrates a block diagram of an example of a block decoder according to the present invention;
0078<figref idref="DRAWINGS">FIG. 62</figref> illustrates a block diagram of an example of a feedback deformatter according to the present invention;
0079<figref idref="DRAWINGS">FIG. 63</figref> to <figref idref="DRAWINGS">FIG. 65</figref> illustrate process steps of error correction decoding according to an embodiment of the present invention;
0080<figref idref="DRAWINGS">FIG. 66</figref> illustrates a block diagram of a receiving system according to an embodiment of the present invention;
0081<figref idref="DRAWINGS">FIG. 67</figref> illustrates a bit stream syntax for a VCT according to the present invention;
0082<figref idref="DRAWINGS">FIG. 68</figref> illustrates a service_type field according to an embodiment of the present invention;
0083<figref idref="DRAWINGS">FIG. 69</figref> illustrates a service location descriptor according to an embodiment of the present invention;
0084<figref idref="DRAWINGS">FIG. 70</figref> illustrates examples that may be assigned to the stream_type field according to the present invention;
0085<figref idref="DRAWINGS">FIG. 71</figref> illustrates a bit stream syntax for an EIT according to the present invention; and
0086<figref idref="DRAWINGS">FIG. 72</figref> illustrates a block diagram of a receiving system according to another embodiment of the present invention;
0087<figref idref="DRAWINGS">FIG. 73</figref> illustrates an example of a protocol stack for a main service according to the embodiment of the present invention;
0088<figref idref="DRAWINGS">FIG. 74</figref> illustrates an example of a protocol stack for a mobile service according to the embodiment of the present invention;
0089<figref idref="DRAWINGS">FIG. 75</figref> illustrates an example of an IP datagram generated by <figref idref="DRAWINGS">FIG. 74</figref>;
0090<figref idref="DRAWINGS">FIG. 76</figref> illustrates another example of a protocol stack for a mobile service according to the embodiment of the present invention;
0091<figref idref="DRAWINGS">FIG. 77</figref> illustrates an example of an IP datagram generated by <figref idref="DRAWINGS">FIG. 76</figref>;
0092<figref idref="DRAWINGS">FIG. 78</figref> illustrates another example of an RS frame according to the embodiment of the present invention;
0093<figref idref="DRAWINGS">FIG. 79</figref> illustrates an example of an MPH header structure within an MPH service data packet according to the embodiment of the present invention;
0094<figref idref="DRAWINGS">FIG. 80(a)</figref> and <figref idref="DRAWINGS">FIG. 80(b)</figref> illustrate another examples of an RS frame according to the embodiment of the present invention;
0095<figref idref="DRAWINGS">FIG. 81(a)</figref> to <figref idref="DRAWINGS">FIG. 81(f)</figref> illustrate extension examples of an MPH service data packet according to the embodiment of the present invention;
0096<figref idref="DRAWINGS">FIG. 82</figref> illustrates an example of a temporary header structure added during extension of <figref idref="DRAWINGS">FIG. 81</figref>;
0097<figref idref="DRAWINGS">FIG. 83</figref> illustrates another example of a service multiplexer according to the embodiment of the present invention;
0098<figref idref="DRAWINGS">FIG. 84</figref> illustrates another example of packet multiplexing according to the embodiment of the present invention;
0099<figref idref="DRAWINGS">FIG. 85</figref> illustrates an example of a protocol stack for a parade structure of <figref idref="DRAWINGS">FIG. 84</figref>;
0100<figref idref="DRAWINGS">FIG. 86</figref> is a block diagram illustrating another example of a receiving system according to the embodiment of the present invention;
0101<figref idref="DRAWINGS">FIG. 87</figref> is a flow chart illustrating an operation example of a demultiplexer of <figref idref="DRAWINGS">FIG. 86</figref>;
0102<figref idref="DRAWINGS">FIG. 88</figref> is a flow chart illustrating an example of a procedure of demultiplexing IP datagram in a demultiplexer of <figref idref="DRAWINGS">FIG. 86</figref>;
0103<figref idref="DRAWINGS">FIG. 89</figref> is a flow chart illustrating an example of a procedure of demultiplexing PSI/PSIP data in a demultiplexer of <figref idref="DRAWINGS">FIG. 86</figref>;
0104<figref idref="DRAWINGS">FIG. 90</figref> is a flow chart illustrating an example of a procedure of demultiplexing IP datagram in a demultiplexer of <figref idref="DRAWINGS">FIG. 86</figref>; and
0105<figref idref="DRAWINGS">FIG. 91</figref> is a flow chart illustrating an example of a procedure of demultiplexing PSI/PSIP data in a demultiplexer of <figref idref="DRAWINGS">FIG. 86</figref>.
DETAILED DESCRIPTION OF THE INVENTION
0106Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts. In addition, although the terms used in the present invention are selected from generally known and used terms, some of the terms mentioned in the description of the present invention have been selected by the applicant at his or her discretion, the detailed meanings of which are described in relevant parts of the description herein. Furthermore, it is required that the present invention is understood, not simply by the actual terms used but by the meaning of each term lying within.
0107Among the terms used in the description of the present invention, main service data correspond to data that can be received by a fixed receiving system and may include audio/video (A/V) data. More specifically, the main service data may include A/V data of high definition (HD) or standard definition (SD) levels and may also include diverse data types required for data broadcasting. Also, the known data correspond to data pre-known in accordance with a pre-arranged agreement between the receiving system and the transmitting system. Additionally, among the terms used in the present invention, “MPH” corresponds to the initials of “mobile”, “pedestrian”, and “handheld” and represents the opposite concept of a fixed-type system. Furthermore, the MPH service data may include at least one of mobile service data, pedestrian service data, and handheld service data, and will also be referred to as “mobile service data” for simplicity. Herein, the mobile service data not only correspond to MPH service data but may also include any type of service data with mobile or portable characteristics. Therefore, the mobile service data according to the present invention are not limited only to the MPH service data.
0108The above-described mobile service data may correspond to data having information, such as program execution files, stock information, and so on, and may also correspond to A/V data. Most particularly, the mobile service data may correspond to A/V data having lower resolution and lower data rate as compared to the main service data. For example, if an A/V codec that is used for a conventional main service corresponds to a MPEG-2 codec, a MPEG-4 advanced video coding (AVC) or scalable video coding (SVC) having better image compression efficiency may be used as the A/V codec for the mobile service. Furthermore, any type of data may be transmitted as the mobile service data. For example, transport protocol expert group (TPEG) data for broadcasting real-time transportation information may be transmitted as the main service data.
0109Also, a data service using the mobile service data may include weather forecast services, traffic information services, stock information services, viewer participation quiz programs, real-time polls and surveys, interactive education broadcast programs, gaming services, services providing information on synopsis, character, background music, and filming sites of soap operas or series, services providing information on past match scores and player profiles and achievements, and services providing information on product information and programs classified by service, medium, time, and theme enabling purchase orders to be processed. Herein, the present invention is not limited only to the services mentioned above. In the present invention, the transmitting system provides backward compatibility in the main service data so as to be received by the conventional receiving system. Herein, the main service data and the mobile service data are multiplexed to the same physical channel and then transmitted.
0110Furthermore, the digital broadcast transmitting system according to the present invention performs additional encoding on the mobile service data and inserts the data already known by the receiving system and transmitting system (e.g., known data), thereby transmitting the processed data. Therefore, when using the transmitting system according to the present invention, the receiving system may receive the mobile service data during a mobile state and may also receive the mobile service data with stability despite various distortion and noise occurring within the channel.
0000MPH Frame Structure
0111In the embodiment of the present invention, the mobile service data are first multiplexed with main service data in MPH frame units and, then, modulated in a VSB mode and transmitted to the receiving system. At this point, one MPH frame consists of K<b>1</b> number of sub-frames, wherein one sub-frame includes K<b>2</b> number of slots. Also, each slot may be configured of K<b>3</b> number of data packets. In the embodiment of the present invention, K<b>1</b> will be set to 5, K<b>2</b> will be set to 16, and K<b>3</b> will be set to 156 (i.e., K<b>1</b>=5, K<b>2</b>=16, and K<b>3</b>=156). The values for K<b>1</b>, K<b>2</b>, and K<b>3</b> presented in this embodiment either correspond to values according to a preferred embodiment or are merely exemplary. Therefore, the above-mentioned values will not limit the scope of the present invention.
0112<figref idref="DRAWINGS">FIG. 1</figref> illustrates a structure of a MPH frame for transmitting and receiving mobile service data according to the present invention. In the example shown in <figref idref="DRAWINGS">FIG. 1</figref>, one MPH frame consists of 5 sub-frames, wherein each sub-frame includes 16 slots. In this case, the MPH frame according to the present invention includes 5 sub-frames and 80 slots. Also, in a packet level, one slot is configured of 156 data packets (i.e., transport stream packets), and in a symbol level, one slot is configured of 156 data segments. Herein, the size of one slot corresponds to one half (½) of a VSB field. More specifically, since one 207-byte data packet has the same amount of data as a data segment, a data packet prior to being interleaved may also be used as a data segment. At this point, two VSB fields are grouped to form a VSB frame.
0113<figref idref="DRAWINGS">FIG. 2</figref> illustrates an exemplary structure of a VSB frame, wherein one VSB frame consists of 2 VSB fields (i.e., an odd field and an even field). Herein, each VSB field includes a field synchronization segment and 312 data segments. The slot corresponds to a basic time period for multiplexing the mobile service data and the main service data. Herein, one slot may either include the mobile service data or be configured only of the main service data. If one MPH frame is transmitted during one slot, the first 118 data packets within the slot correspond to a data group. And, the remaining 38 data packets become the main service data packets. In another example, when no data group exists in a slot, the corresponding slot is configured of 156 main service data packets. Meanwhile, when the slots are assigned to a VSB frame, an off-set exists for each assigned position.
0114<figref idref="DRAWINGS">FIG. 3</figref> illustrates a mapping example of the positions to which the first 4 slots of a sub-frame are assigned with respect to a VSB frame in a space region. And, <figref idref="DRAWINGS">FIG. 4</figref> illustrates a mapping example of the positions to which the first 4 slots of a sub-frame are assigned with respect to a VSB frame in a time region. Referring to <figref idref="DRAWINGS">FIG. 3</figref> and <figref idref="DRAWINGS">FIG. 4</figref>, a 38<sup>th </sup>data packet (TS packet #<b>37</b>) of a 1<sup>st </sup>slot (Slot #<b>0</b>) is mapped to the 1<sup>st </sup>data packet of an odd VSB field. A 38<sup>th </sup>data packet (TS packet #<b>37</b>) of a 2<sup>nd </sup>slot (Slot #<b>1</b>) is mapped to the 157<sup>th </sup>data packet of an odd VSB field. Also, a 38<sup>th </sup>data packet (TS packet #<b>37</b>) of a 3<sup>rd </sup>slot (Slot #<b>2</b>) is mapped to the 1<sup>st </sup>data packet of an even VSB field. And, a 38<sup>th </sup>data packet (TS packet #<b>37</b>) of a 4<sup>th </sup>slot (Slot #<b>3</b>) is mapped to the 157<sup>th </sup>data packet of an even VSB field. Similarly, the remaining 12 slots within the corresponding sub-frame are mapped in the subsequent VSB frames using the same method.
0115Meanwhile, one data group may be divided into at least one or more hierarchical regions. And, depending upon the characteristics of each hierarchical region, the type of mobile service data being inserted in each region may vary. For example, the data group within each region may be divided (or categorized) based upon the receiving performance. In an example given in the present invention, a data group is divided into regions A, B, C, and D in a data configuration prior to data deinterleaving.
0116<figref idref="DRAWINGS">FIG. 5</figref> illustrates an alignment of data after being data interleaved and identified. <figref idref="DRAWINGS">FIG. 6</figref> illustrates an enlarged portion of the data group shown in <figref idref="DRAWINGS">FIG. 5</figref> for a better understanding of the present invention. <figref idref="DRAWINGS">FIG. 7</figref> illustrates an alignment of data before being data interleaved and identified. And, <figref idref="DRAWINGS">FIG. 8</figref> illustrates an enlarged portion of the data group shown in <figref idref="DRAWINGS">FIG. 7</figref> for a better understanding of the present invention. More specifically, a data structure identical to that shown in <figref idref="DRAWINGS">FIG. 5</figref> is transmitted to a receiving system. In other words, one data packet is data-interleaved so as to be scattered to a plurality of data segments, thereby being transmitted to the receiving system. <figref idref="DRAWINGS">FIG. 5</figref> illustrates an example of one data group being scattered to 170 data segments. At this point, since one 207-byte packet has the same amount of data as one data segment, the packet that is not yet processed with data-interleaving may be used as the data segment.
0117<figref idref="DRAWINGS">FIG. 5</figref> shows an example of dividing a data group prior to being data-interleaved into 10 MPH blocks (i.e., MPH block <b>1</b> (B<b>1</b>) to MPH block <b>10</b> (B<b>10</b>)). In this example, each MPH block has the length of 16 segments. Referring to <figref idref="DRAWINGS">FIG. 5</figref>, only the RS parity data are allocated to portions of the first 5 segments of the MPH block <b>1</b> (B<b>1</b>) and the last 5 segments of the MPH block <b>10</b> (B<b>10</b>). The RS parity data are excluded in regions A to D of the data group. More specifically, when it is assumed that one data group is divided into regions A, B, C, and D, each MPH block may be included in any one of region A to region D depending upon the characteristic of each MPH block within the data group.
0118Herein, the data group is divided into a plurality of regions to be used for different purposes. More specifically, a region of the main service data having no interference or a very low interference level may be considered to have a more resistant (or stronger) receiving performance as compared to regions having higher interference levels. Additionally, when using a system inserting and transmitting known data in the data group, wherein the known data are known based upon an agreement between the transmitting system and the receiving system, and when consecutively long known data are to be periodically inserted in the mobile service data, the known data having a predetermined length may be periodically inserted in the region having no interference from the main service data (i.e., a region wherein the main service data are not mixed). However, due to interference from the main service data, it is difficult to periodically insert known data and also to insert consecutively long known data to a region having interference from the main service data.
0119Referring to <figref idref="DRAWINGS">FIG. 5</figref>, MPH block <b>4</b> (B<b>4</b>) to MPH block <b>7</b> (B<b>7</b>) correspond to regions without interference of the main service data. MPH block <b>4</b> (B<b>4</b>) to MPH block <b>7</b> (B<b>7</b>) within the data group shown in <figref idref="DRAWINGS">FIG. 5</figref> correspond to a region where no interference from the main service data occurs. In this example, a long known data sequence is inserted at both the beginning and end of each MPH block. In the description of the present invention, the region including MPH block <b>4</b> (B<b>4</b>) to MPH block <b>7</b> (B<b>7</b>) will be referred to as “region A (=B<b>4</b>+B<b>5</b>+B<b>6</b>+B<b>7</b>)”. As described above, when the data group includes region A having a long known data sequence inserted at both the beginning and end of each MPH block, the receiving system is capable of performing equalization by using the channel information that can be obtained from the known data. Therefore, the strongest equalizing performance may be yielded (or obtained) from one of region A to region D.
0120In the example of the data group shown in <figref idref="DRAWINGS">FIG. 5</figref>, MPH block <b>3</b> (B<b>3</b>) and MPH block <b>8</b> (B<b>8</b>) correspond to a region having little interference from the main service data. Herein, a long known data sequence is inserted in only one side of each MPH block B<b>3</b> and B<b>8</b>. More specifically, due to the interference from the main service data, a long known data sequence is inserted at the end of MPH block <b>3</b> (B<b>3</b>), and another long known data sequence is inserted at the beginning of MPH block <b>8</b> (B<b>8</b>). In the present invention, the region including MPH block <b>3</b> (B<b>3</b>) and MPH block <b>8</b> (B<b>8</b>) will be referred to as “region B(=B<b>3</b>+B<b>8</b>)”. As described above, when the data group includes region B having a long known data sequence inserted at only one side (beginning or end) of each MPH block, the receiving system is capable of performing equalization by using the channel information that can be obtained from the known data. Therefore, a stronger equalizing performance as compared to region C/D may be yielded (or obtained).
0121Referring to <figref idref="DRAWINGS">FIG. 5</figref>, MPH block <b>2</b> (B<b>2</b>) and MPH block <b>9</b> (B<b>9</b>) correspond to a region having more interference from the main service data as compared to region B. A long known data sequence cannot be inserted in any side of MPH block <b>2</b> (B<b>2</b>) and MPH block <b>9</b> (B<b>9</b>). Herein, the region including MPH block <b>2</b> (B<b>2</b>) and MPH block <b>9</b> (B<b>9</b>) will be referred to as “region C(=B<b>2</b>+B<b>9</b>)”. Finally, in the example shown in <figref idref="DRAWINGS">FIG. 5</figref>, MPH block <b>1</b> (B<b>1</b>) and MPH block <b>10</b> (B<b>10</b>) correspond to a region having more interference from the main service data as compared to region C. Similarly, a long known data sequence cannot be inserted in any side of MPH block <b>1</b> (B<b>1</b>) and MPH block <b>10</b> (B<b>10</b>). Herein, the region including MPH block <b>1</b> (B<b>1</b>) and MPH block <b>10</b> (B<b>10</b>) will be referred to as “region D (=B<b>1</b>+B<b>10</b>)”. Since region C/D is spaced further apart from the known data sequence, when the channel environment undergoes frequent and abrupt changes, the receiving performance of region C/D may be deteriorated.
0122<figref idref="DRAWINGS">FIG. 7</figref> illustrates a data structure prior to data interleaving. More specifically, <figref idref="DRAWINGS">FIG. 7</figref> illustrates an example of 118 data packets being allocated to a data group. <figref idref="DRAWINGS">FIG. 7</figref> shows an example of a data group consisting of 118 data packets, wherein, based upon a reference packet (e.g., a 1<sup>st </sup>packet (or data segment) or 157<sup>th </sup>packet (or data segment) after a field synchronization signal), when allocating data packets to a VSB frame, 37 packets are included before the reference packet and 81 packets (including the reference packet) are included afterwards. In other words, with reference to <figref idref="DRAWINGS">FIG. 5</figref>, a field synchronization signal is placed (or assigned) between MPH block <b>2</b> (B<b>2</b>) and MPH block <b>3</b> (B<b>3</b>). Accordingly, this indicates that the slot has an off-set of 37 data packets with respect to the corresponding VSB field. The size of the data groups, number of hierarchical regions within the data group, the size of each region, the number of MPH blocks included in each region, the size of each MPH block, and so on described above are merely exemplary. Therefore, the present invention will not be limited to the examples described above.
0123<figref idref="DRAWINGS">FIG. 9</figref> illustrates an exemplary assignment order of data groups being assigned to one of 5 sub-frames, wherein the 5 sub-frames configure an MPH frame. For example, the method of assigning data groups may be identically applied to all MPH frames or differently applied to each MPH frame. Furthermore, the method of assigning data groups may be identically applied to all sub-frames or differently applied to each sub-frame. At this point, when it is assumed that the data groups are assigned using the same method in all sub-frames of the corresponding MPH frame, the total number of data groups being assigned to an MPH frame is equal to a multiple of ‘5’. According to the embodiment of the present invention, a plurality of consecutive data groups is assigned to be spaced as far apart from one another as possible within the MPH frame. Thus, the system can be capable of responding promptly and effectively to any burst error that may occur within a sub-frame.
0124For example, when it is assumed that 3 data groups are assigned to a sub-frame, the data groups are assigned to a 1<sup>st </sup>slot (Slot #<b>0</b>), a 5<sup>th </sup>slot (Slot #<b>4</b>), and a 9<sup>th </sup>slot (Slot #<b>8</b>) in the sub-frame, respectively. <figref idref="DRAWINGS">FIG. 9</figref> illustrates an example of assigning 16 data groups in one sub-frame using the above-described pattern (or rule). In other words, each data group is serially assigned to 16 slots corresponding to the following numbers: 0, 8, 4, 12, 1, 9, 5, 13, 2, 10, 6, 14, 3, 11, 7, and 15. Equation 1 below shows the above-described rule (or pattern) for assigning data groups in a sub-frame. <br />j=(4i+0)mod 16 Equation 1<ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0125">0=0 if i<4,</li><li id="ul0002-0002" num="0126">0=2 else if i<8,</li><li id="ul0002-0003" num="0127">Herein,</li><li id="ul0002-0004" num="0128">0=1 else if i<12,</li><li id="ul0002-0005" num="0129">0=3 else.</li><li id="ul0002-0006" num="0130">Herein, j indicates the slot number within a sub-frame. The value of j may range from 0 to 15 (i.e., 0≦j≦15). Also, variable i indicates the data group number. The value of i may range from 0 to 15 (i.e., 0≦i≦15).</li></ul></li></ul>
0131In the present invention, a collection of data groups included in a MPH frame will be referred to as a “parade”. Based upon the RS frame mode, the parade transmits data of at least one specific RS frame. The mobile service data within one RS frame may be assigned either to all of regions A/B/C/D within the corresponding data group, or to at least one of regions A/B/C/D. In the embodiment of the present invention, the mobile service data within one RS frame may be assigned either to all of regions A/B/C/D, or to at least one of regions A/B and regions C/D. If the mobile service data are assigned to the latter case (i.e., one of regions A/B and regions C/D), the RS frame being assigned to regions A/B and the RS frame being assigned to regions C/D within the corresponding data group are different from one another.
0132In the description of the present invention, the RS frame being assigned to regions A/B within the corresponding data group will be referred to as a “primary RS frame”, and the RS frame being assigned to regions C/D within the corresponding data group will be referred to as a “secondary RS frame”, for simplicity. Also, the primary RS frame and the secondary RS frame form (or configure) one parade. More specifically, when the mobile service data within one RS frame are assigned either to all of regions A/B/C/D within the corresponding data group, one parade transmits one RS frame. Conversely, when the mobile service data within one RS frame are assigned either to at least one of regions A/B and regions C/D, one parade may transmit up to 2 RS frames. More specifically, the RS frame mode indicates whether a parade transmits one RS frame, or whether the parade transmits two RS frames. Table 1 below shows an example of the RS frame mode.
0133<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="70pt" align="center" /><colspec colname="2" colwidth="147pt" align="left" /><thead><row><entry namest="1" nameend="2" rowsep="1">TABLE 1</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>RS frame mode</entry><entry /></row><row><entry>(2 bits)</entry><entry>Description</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>00</entry><entry>There is only one primary RS frame for all group</entry></row><row><entry /><entry>regions</entry></row><row><entry>01</entry><entry>There are two separate RS frames.</entry></row><row><entry /><entry>Primary RS frame for group regions A and B</entry></row><row><entry /><entry>Secondary RS frame for group regions C and D</entry></row><row><entry>10</entry><entry>Reserved</entry></row><row><entry>11</entry><entry>Reserved</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>
0134Table 1 illustrates an example of allocating 2 bits in order to indicate the RS frame mode. For example, referring to Table 1, when the RS frame mode value is equal to ‘00’, this indicates that one parade transmits one RS frame. And, when the RS frame mode value is equal to ‘01’, this indicates that one parade transmits two RS frames, i.e., the primary RS frame and the secondary RS frame. More specifically, when the RS frame mode value is equal to ‘01’, data of the primary RS frame for regions A/B are assigned and transmitted to regions A/B of the corresponding data group. Similarly, data of the secondary RS frame for regions C/D are assigned and transmitted to regions C/D of the corresponding data group.
0135Additionally, one RS frame transmits one ensemble. Herein, the ensemble is a collection of services requiring the same quality of service (QOS) and being encoded with the same FEC codes. More specifically, when one parade is configured of one RS frame, then one parade transmits one ensemble. Conversely, when one parade is configured of two RS frames, i.e., when one parade is configured of a primary RS frame and a secondary RS frame, then one parade transmits two ensembles (i.e., a primary ensemble and a secondary ensemble). More specifically, the primary ensemble is transmitted through a primary RS frame of a parade, and the secondary ensemble is transmitted through a secondary RS frame of a parade. The RS frame is a 2-dimensional data frame through which an ensemble is RS-CRC encoded.
0136As described in the assignment of data groups, the parades are also assigned to be spaced as far apart from one another as possible within the sub-frame. Thus, the system can be capable of responding promptly and effectively to any burst error that may occur within a sub-frame. Furthermore, the method of assigning parades may be identically applied to all sub-frames or differently applied to each sub-frame. According to the embodiment of the present invention, the parades may be assigned differently for each MPH frame and identically for all sub-frames within an MPH frame. More specifically, the MPH frame structure may vary by MPH frame units. Thus, an ensemble rate may be adjusted on a more frequent and flexible basis.
0137<figref idref="DRAWINGS">FIG. 10</figref> illustrates an example of multiple data groups of a single parade being assigned (or allocated) to an MPH frame. More specifically, <figref idref="DRAWINGS">FIG. 10</figref> illustrates an example of a plurality of data groups included in a single parade, wherein the number of data groups included in a sub-frame is equal to ‘3’, being allocated to an MPH frame. Referring to <figref idref="DRAWINGS">FIG. 10</figref>, 3 data groups are sequentially assigned to a sub-frame at a cycle period of 4 slots. Accordingly, when this process is equally performed in the 5 sub-frames included in the corresponding MPH frame, 15 data groups are assigned to a single MPH frame. Herein, the 15 data groups correspond to data groups included in a parade. Therefore, since one sub-frame is configured of 4 VSB frame, and since 3 data groups are included in a sub-frame, the data group of the corresponding parade is not assigned to one of the 4 VSB frames within a sub-frame.
0138For example, when it is assumed that one parade transmits one RS frame, and that a RS frame encoder located in a later block performs RS-encoding on the corresponding RS frame, thereby adding 24 bytes of parity data to the corresponding RS frame and transmitting the processed RS frame, the parity data occupy approximately 11.37% (=24/(187+24)×100) of the total code word length. Meanwhile, when one sub-frame includes 3 data groups, and when the data groups included in the parade are assigned, as shown in <figref idref="DRAWINGS">FIG. 10</figref>, a total of 15 data groups form an RS frame. Accordingly, even when an error occurs in an entire data group due to a burst noise within a channel, the percentile is merely 6.67% (= 1/15×100). Therefore, the receiving system may correct all errors by performing an erasure RS decoding process. More specifically, when the erasure RS decoding is performed, a number of channel errors corresponding to the number of RS parity bytes may be corrected. By doing so, the receiving system may correct the error of at least one data group within one parade. Thus, the minimum burst noise length correctable by a RS frame is over 1 VSB frame.
0139Meanwhile, when data groups of a parade are assigned as described above, either main service data may be assigned between each data group, or data groups corresponding to different parades may be assigned between each data group. More specifically, data groups corresponding to multiple parades may be assigned to one MPH frame. Basically, the method of assigning data groups corresponding to multiple parades is very similar to the method of assigning data groups corresponding to a single parade. In other words, data groups included in other parades that are to be assigned to an MPH frame are also respectively assigned according to a cycle period of 4 slots. At this point, data groups of a different parade may be sequentially assigned to the respective slots in a circular method. Herein, the data groups are assigned to slots starting from the ones to which data groups of the previous parade have not yet been assigned. For example, when it is assumed that data groups corresponding to a parade are assigned as shown in <figref idref="DRAWINGS">FIG. 10</figref>, data groups corresponding to the next parade may be assigned to a sub-frame starting either from the 12<sup>th </sup>slot of a sub-frame. However, this is merely exemplary. In another example, the data groups of the next parade may also be sequentially assigned to a different slot within a sub-frame at a cycle period of 4 slots starting from the 3<sup>rd </sup>slot.
0140<figref idref="DRAWINGS">FIG. 11</figref> illustrates an example of transmitting 3 parades (Parade #<b>0</b>, Parade #<b>1</b>, and Parade #<b>2</b>) to an MPH frame. More specifically, <figref idref="DRAWINGS">FIG. 11</figref> illustrates an example of transmitting parades included in one of 5 sub-frames, wherein the 5 sub-frames configure one MPH frame. When the 1<sup>st </sup>parade (Parade #<b>0</b>) includes 3 data groups for each sub-frame, the positions of each data groups within the sub-frames may be obtained by substituting values ‘0’ to ‘2’ for i in Equation 1. More specifically, the data groups of the 1<sup>st </sup>parade (Parade #<b>0</b>) are sequentially assigned to the 1<sup>st</sup>, 5<sup>th</sup>, and 9<sup>th </sup>slots (Slot #<b>0</b>, Slot #<b>4</b>, and Slot #<b>8</b>) within the sub-frame. Also, when the 2<sup>nd </sup>parade includes 2 data groups for each sub-frame, the positions of each data groups within the sub-frames may be obtained by substituting values ‘3’ and ‘4’ for i in Equation 1. More specifically, the data groups of the 2<sup>nd </sup>parade (Parade #<b>1</b>) are sequentially assigned to the 2<sup>nd </sup>and 12<sup>th </sup>slots (Slot #<b>3</b> and Slot #<b>11</b>) within the sub-frame. Finally, when the 3<sup>rd </sup>parade includes 2 data groups for each sub-frame, the positions of each data groups within the sub-frames may be obtained by substituting values ‘5’ and ‘6’ for i in Equation 1. More specifically, the data groups of the 3<sup>rd </sup>parade (Parade #<b>2</b>) are sequentially assigned to the 7<sup>th </sup>and 11<sup>th </sup>slots (Slot #<b>6</b> and Slot #<b>10</b>) within the sub-frame.
0141As described above, data groups of multiple parades may be assigned to a single MPH frame, and, in each sub-frame, the data groups are serially allocated to a group space having 4 slots from left to right. Therefore, a number of groups of one parade per sub-frame (NOG) may correspond to any one integer from ‘1’ to ‘8’. Herein, since one MPH frame includes 5 sub-frames, the total number of data groups within a parade that can be allocated to an MPH frame may correspond to any one multiple of ‘5’ ranging from ‘5’ to ‘40’.
0142<figref idref="DRAWINGS">FIG. 12</figref> illustrates an example of expanding the assignment process of 3 parades, shown in <figref idref="DRAWINGS">FIGS. 11</figref>, to 5 sub-frames within an MPH frame.
0000General Description of the Transmitting System
0143<figref idref="DRAWINGS">FIG. 13</figref> illustrates a block diagram showing a general structure of a digital broadcast transmitting system according to an embodiment of the present invention.
0144Herein, the digital broadcast transmitting includes a service multiplexer <b>100</b> and a transmitter <b>200</b>. Herein, the service multiplexer <b>100</b> is located in the studio of each broadcast station, and the transmitter <b>200</b> is located in a site placed at a predetermined distance from the studio. The transmitter <b>200</b> may be located in a plurality of different locations. Also, for example, the plurality of transmitters may share the same frequency. And, in this case, the plurality of transmitters receives the same signal. Accordingly, in the receiving system, a channel equalizer may compensate signal distortion, which is caused by a reflected wave, so as to recover the original signal. In another example, the plurality of transmitters may have different frequencies with respect to the same channel.
0145A variety of methods may be used for data communication each of the transmitters, which are located in remote positions, and the service multiplexer. For example, an interface standard such as a synchronous serial interface for transport of MPEG-2 data (SMPTE-310M). In the SMPTE-310M interface standard, a constant data rate is decided as an output data rate of the service multiplexer. For example, in case of the 8VSB mode, the output data rate is 19.39 Mbps, and, in case of the 16VSB mode, the output data rate is 38.78 Mbps. Furthermore, in the conventional 8VSB mode transmitting system, a transport stream (TS) packet having a data rate of approximately 19.39 Mbps may be transmitted through a single physical channel. Also, in the transmitting system according to the present invention provided with backward compatibility with the conventional transmitting system, additional encoding is performed on the mobile service data. Thereafter, the additionally encoded mobile service data are multiplexed with the main service data to a TS packet form, which is then transmitted. At this point, the data rate of the multiplexed TS packet is approximately 19.39 Mbps.
0146At this point, the service multiplexer <b>100</b> receives at least one type of mobile service data and program specific information/program and system information protocol (PSI/PSIP) table data for each mobile service so as to encapsulate the received data to each TS packet. Also, the service multiplexer <b>100</b> receives at least one type of main service data and PSI/PSIP table data for each main service and encapsulates the received data to a transport stream (TS) packet. Subsequently, the TS packets are multiplexed according to a predetermined multiplexing rule and outputs the multiplexed packets to the transmitter <b>200</b>.
0000Service Multiplexer
0147<figref idref="DRAWINGS">FIG. 14</figref> illustrates a block diagram showing an example of the service multiplexer. The service multiplexer includes a controller <b>110</b> for controlling the overall operations of the service multiplexer, a PSI/PSIP generator <b>120</b> for the main service, a PSI/PSIP generator <b>130</b> for the mobile service, a null packet generator <b>140</b>, a mobile service multiplexer <b>150</b>, and a transport multiplexer <b>160</b>.
0148The transport multiplexer <b>160</b> may include a main service multiplexer <b>161</b> and a transport stream (TS) packet multiplexer <b>162</b>.
0149Referring to <figref idref="DRAWINGS">FIG. 14</figref>, at least one type of compression encoded main service data and the PSI/PSIP table data generated from the PSI/PSIP generator <b>120</b> for the main service are inputted to the main service multiplexer <b>161</b> of the transport multiplexer <b>160</b>. The main service multiplexer <b>161</b> encapsulates each of the inputted main service data and PSI/PSIP table data to MPEG-2 TS packet forms. Then, the MPEG-2 TS packets are multiplexed and outputted to the TS packet multiplexer <b>162</b>. Herein, the data packet being outputted from the main service multiplexer <b>161</b> will be referred to as a main service data packet for simplicity.
0150Thereafter, at least one type of the compression encoded mobile service data and the PSI/PSIP table data generated from the PSI/PSIP generator <b>130</b> for the mobile service are inputted to the mobile service multiplexer <b>150</b>.
0151The mobile service multiplexer <b>150</b> encapsulates each of the inputted mobile service data and PSI/PSIP table data to MPEG-2 TS packet forms. Then, the MPEG-2 TS packets are multiplexed and outputted to the TS packet multiplexer <b>162</b>. Herein, the data packet being outputted from the mobile service multiplexer <b>150</b> will be referred to as a mobile service data packet for simplicity.
0152At this point, the transmitter <b>200</b> requires identification information in order to identify and process the main service data packet and the mobile service data packet. Herein, the identification information may use values pre-decided in accordance with an agreement between the transmitting system and the receiving system, or may be configured of a separate set of data, or may modify predetermined location value with in the corresponding data packet.
0153As an example of the present invention, a different packet identifier (PID) may be assigned to identify each of the main service data packet and the mobile service data packet.
0154In another example, by modifying a synchronization data byte within a header of the mobile service data, the service data packet may be identified by using the synchronization data byte value of the corresponding service data packet. For example, the synchronization byte of the main service data packet directly outputs the value decided by the ISO/IEC13818-1 standard (i.e., 0x47) without any modification. The synchronization byte of the mobile service data packet modifies and outputs the value, thereby identifying the main service data packet and the mobile service data packet. Conversely, the synchronization byte of the main service data packet is modified and outputted, whereas the synchronization byte of the mobile service data packet is directly outputted without being modified, thereby enabling the main service data packet and the mobile service data packet to be identified.
0155A plurality of methods may be applied in the method of modifying the synchronization byte. For example, each bit of the synchronization byte may be inversed, or only a portion of the synchronization byte may be inversed.
0156As described above, any type of identification information may be used to identify the main service data packet and the mobile service data packet. Therefore, the scope of the present invention is not limited only to the example set forth in the description of the present invention.
0157Meanwhile, a transport multiplexer used in the conventional digital broadcasting system may be used as the transport multiplexer <b>160</b> according to the present invention. More specifically, in order to multiplex the mobile service data and the main service data and to transmit the multiplexed data, the data rate of the main service is limited to a data rate of (19.39-K) Mbps. Then, K Mbps, which corresponds to the remaining data rate, is assigned as the data rate of the mobile service. Thus, the transport multiplexer which is already being used may be used as it is without any modification.
0158Herein, the transport multiplexer <b>160</b> multiplexes the main service data packet being outputted from the main service multiplexer <b>161</b> and the mobile service data packet being outputted from the mobile service multiplexer <b>150</b>. Thereafter, the transport multiplexer <b>160</b> transmits the multiplexed data packets to the transmitter <b>200</b>.
0159However, in some cases, the output data rate of the mobile service multiplexer <b>150</b> may not be equal to K Mbps. In this case, the mobile service multiplexer <b>150</b> multiplexes and outputs null data packets generated from the null packet generator <b>140</b> so that the output data rate can reach K Mbps. More specifically, in order to match the output data rate of the mobile service multiplexer <b>150</b> to a constant data rate, the null packet generator <b>140</b> generates null data packets, which are then outputted to the mobile service multiplexer <b>150</b>.
0160For example, when the service multiplexer <b>100</b> assigns K Mbps of the 19.39 Mbps to the mobile service data, and when the remaining (19.39-K) Mbps is, therefore, assigned to the main service data, the data rate of the mobile service data that are multiplexed by the service multiplexer <b>100</b> actually becomes lower than K Mbps. This is because, in case of the mobile service data, the pre-processor of the transmitting system performs additional encoding, thereby increasing the amount of data. Eventually, the data rate of the mobile service data, which may be transmitted from the service multiplexer <b>100</b>, becomes smaller than K Mbps.
0161For example, since the pre-processor of the transmitter performs an encoding process on the mobile service data at a coding rate of at least 1/2, the amount of the data outputted from the pre-processor is increased to more than twice the amount of the data initially inputted to the pre-processor. Therefore, the sum of the data rate of the main service data and the data rate of the mobile service data, both being multiplexed by the service multiplexer <b>100</b>, becomes either equal to or smaller than 19.39 Mbps.
0162Therefore, in order to match the data rate of the data that are finally outputted from the service multiplexer <b>100</b> to a constant data rate (e.g., 19.39 Mbps), an amount of null data packets corresponding to the amount of lacking data rate is generated from the null packet generator <b>140</b> and outputted to the mobile service multiplexer <b>150</b>.
0163Accordingly, the mobile service multiplexer <b>150</b> encapsulates each of the mobile service data and the PSI/PSIP table data that are being inputted to a MPEG-2 TS packet form. Then, the above-described TS packets are multiplexed with the null data packets and, then, outputted to the TS packet multiplexer <b>162</b>.
0164Thereafter, the TS packet multiplexer <b>162</b> multiplexes the main service data packet being outputted from the main service multiplexer <b>161</b> and the mobile service data packet being outputted from the mobile service multiplexer <b>150</b> and transmits the multiplexed data packets to the transmitter <b>200</b> at a data rate of 19.39 Mbps.
0165According to an embodiment of the present invention, the mobile service multiplexer <b>150</b> receives the null data packets. However, this is merely exemplary and does not limit the scope of the present invention. In other words, according to another embodiment of the present invention, the TS packet multiplexer <b>162</b> may receive the null data packets, so as to match the data rate of the finally outputted data to a constant data rate. Herein, the output path and multiplexing rule of the null data packet is controlled by the controller <b>110</b>. The controller <b>110</b> controls the multiplexing processed performed by the mobile service multiplexer <b>150</b>, the main service multiplexer <b>161</b> of the transport multiplexer <b>160</b>, and the TS packet multiplexer <b>162</b>, and also controls the null data packet generation of the null packet generator <b>140</b>. At this point, the transmitter <b>200</b> discards the null data packets transmitted from the service multiplexer <b>100</b> instead of transmitting the null data packets.
0166Further, in order to allow the transmitter <b>200</b> to discard the null data packets transmitted from the service multiplexer <b>100</b> instead of transmitting them, identification information for identifying the null data packet is required. Herein, the identification information may use values pre-decided in accordance with an agreement between the transmitting system and the receiving system. For example, the value of the synchronization byte within the header of the null data packet may be modified so as to be used as the identification information. Alternatively, a transport_error_indicator flag may also be used as the identification information.
0167In the description of the present invention, an example of using the transport_error_indicator flag as the identification information will be given to describe an embodiment of the present invention. In this case, the transport_error_indicator flag of the null data packet is set to ‘1’, and the transport_error_indicator flag of the remaining data packets are reset to ‘0’, so as to identify the null data packet. More specifically, when the null packet generator <b>140</b> generates the null data packets, if the transport_error_indicator flag from the header field of the null data packet is set to ‘1’ and then transmitted, the null data packet may be identified and, therefore, be discarded. In the present invention, any type of identification information for identifying the null data packets may be used. Therefore, the scope of the present invention is not limited only to the examples set forth in the description of the present invention.
0168According to another embodiment of the present invention, a transmission parameter may be included in at least a portion of the null data packet, or at least one table or an operations and maintenance (OM) packet (or OMP) of the PSI/PSIP table for the mobile service. In this case, the transmitter <b>200</b> extracts the transmission parameter and outputs the extracted transmission parameter to the corresponding block and also transmits the extracted parameter to the receiving system if required. More specifically, a packet referred to as an OMP is defined for the purpose of operating and managing the transmitting system. For example, the OMP is configured in accordance with the MPEG-2 TS packet format, and the corresponding PID is given the value of 0x1FFA. The OMP is configured of a 4-byte header and a 184-byte payload. Herein, among the 184 bytes, the first byte corresponds to an OM_type field, which indicates the type of the OM packet.
0169In the present invention, the transmission parameter may be transmitted in the form of an OMP. And, in this case, among the values of the reserved fields within the OM_type field, a pre-arranged value is used, thereby indicating that the transmission parameter is being transmitted to the transmitter <b>200</b> in the form of an OMP. More specifically, the transmitter <b>200</b> may find (or identify) the OMP by referring to the PID. Also, by parsing the OM_type field within the OMP, the transmitter <b>200</b> can verify whether a transmission parameter is included after the OM_type field of the corresponding packet. The transmission parameter corresponds to supplemental data required for processing mobile service data from the transmitting system and the receiving system.
0170The transmission parameter corresponds to supplemental data required for processing mobile service data from the transmitting system and the receiving system. Herein, the transmission parameter may include data group information, region information within the data group, block information, RS frame information, super frame information, MPH frame information, parade information, ensemble information, information associated with serial concatenated convolution code (SCCC), and RS code information. The significance of some information within the transmission parameters has already been described in detail. Descriptions of other information that have not yet been described will be in detail in a later process.
0171The transmission parameter may also include information on how signals of a symbol domain are encoded in order to transmit the mobile service data, and multiplexing information on how the main service data and the mobile service data or various types of mobile service data are multiplexed.
0172The information included in the transmission parameter are merely exemplary to facilitate the understanding of the present invention. And, the adding and deleting of the information included in the transmission parameter may be easily modified and changed by anyone skilled in the art. Therefore, the present invention is not limited to the examples proposed in the description set forth herein.
0173Furthermore, the transmission parameters may be provided from the service multiplexer <b>100</b> to the transmitter <b>200</b>. Alternatively, the transmission parameters may also be set up by an internal controller (not shown) within the transmitter <b>200</b> or received from an external source.
0000Transmitter
0174<figref idref="DRAWINGS">FIG. 15</figref> illustrates a block diagram showing an example of the transmitter <b>200</b> according to an embodiment of the present invention. Herein, the transmitter <b>200</b> includes a controller <b>200</b>, a demultiplexer <b>210</b>, a packet jitter mitigator <b>220</b>, a pre-processor <b>230</b>, a packet multiplexer <b>240</b>, a post-processor <b>250</b>, a synchronization (sync) multiplexer <b>260</b>, and a transmission unit <b>270</b>. Herein, when a data packet is received from the service multiplexer <b>100</b>, the demultiplexer <b>210</b> should identify whether the received data packet corresponds to a main service data packet, a mobile service data packet, or a null data packet. For example, the demultiplexer <b>210</b> uses the PID within the received data packet so as to identify the main service data packet and the mobile service data packet. Then, the demultiplexer <b>210</b> uses a transport_error_indicator field to identify the null data packet. The main service data packet identified by the demultiplexer <b>210</b> is outputted to the packet jitter mitigator <b>220</b>, the mobile service data packet is outputted to the pre-processor <b>230</b>, and the null data packet is discarded. If a transmission parameter is included in the null data packet, then the transmission parameter is first extracted and outputted to the corresponding block. Thereafter, the null data packet is discarded.
0175The pre-processor <b>230</b> performs an additional encoding process of the mobile service data included in the service data packet, which is demultiplexed and outputted from the demultiplexer <b>210</b>. The pre-processor <b>230</b> also performs a process of configuring a data group so that the data group may be positioned at a specific place in accordance with the purpose of the data, which are to be transmitted on a transmission frame. This is to enable the mobile service data to respond swiftly and strongly against noise and channel changes. The pre-processor <b>230</b> may also refer to the transmission parameter when performing the additional encoding process. Also, the pre-processor <b>230</b> groups a plurality of mobile service data packets to configure a data group. Thereafter, known data, mobile service data, RS parity data, and MPEG header are allocated to pre-determined regions within the data group.
0000Pre-processor within Transmitter
0176<figref idref="DRAWINGS">FIG. 16</figref> illustrates a block diagram showing the structure of a pre-processor <b>230</b> according to the present invention. Herein, the pre-processor <b>230</b> includes an MPH frame encoder <b>301</b>, a block processor <b>302</b>, a group formatter <b>303</b>, a signaling encoder <b>304</b>, and a packet formatter <b>305</b>. The MPH frame encoder <b>301</b>, which is included in the pre-processor <b>230</b> having the above-described structure, data-randomizes the mobile service data that are inputted to the demultiplexer <b>210</b>, thereby creating a RS frame. Then, the MPH frame encoder <b>301</b> performs an encoding process for error correction in RS frame units. The MPH frame encoder <b>301</b> may include at least one RS frame encoder. More specifically, RS frame encoders may be provided in parallel, wherein the number of RS frame encoders is equal to the number of parades within the MPH frame. As described above, the MPH frame is a basic time cycle period for transmitting at least one parade. Also, each parade consists of one or two RS frames.
0177<figref idref="DRAWINGS">FIG. 17</figref> illustrates a conceptual block diagram of the MPH frame encoder <b>301</b> according to an embodiment of the present invention. The MPH frame encoder <b>301</b> includes an input demultiplexer (DEMUX) <b>309</b>, M number of RS frame encoders <b>310</b> to <b>31</b>M−1, and an output multiplexer (MUX) <b>320</b>. Herein, M represent the number of parades included in one MPH frame. The input demultiplexer (DEMUX) <b>309</b> splits input ensembles. Then, the split input ensembles decide the RS frame to which the ensembles are to be inputted. Thereafter, the inputted ensembles are outputted to the respective RS frame. At this point, an ensemble may be mapped to each RS frame encoder or parade. For example, when one parade configures one RS frame, the ensembles, RS frames, and parades may each be mapped to be in a one-to-one (1:1) correspondence with one another. More specifically, the data in one ensemble configure a RS frame. And, a RS frame is divided into a plurality of data groups. Based upon the RS frame mode of Table 1, the data within one RS frame may be assigned either to all of regions A/B/C/D within multiple data groups, or to at least one of regions A/B and regions C/D within multiple data groups.
0178When the RS frame mode value is equal to ‘01’, i.e., when the data of the primary RS frame are assigned to regions A/B of the corresponding data group and data of the secondary RS frame are assigned to regions C/D of the corresponding data group, each RS frame encoder creates a primary RS frame and a secondary RS frame for each parade. Conversely, when the RS frame mode value is equal to ‘00’, when the data of the primary RS frame are assigned to all of regions A/B/C/D, each RS frame encoder creates a RS frame (i.e., a primary RS frame) for each parade. Also, each RS frame encoder divides each RS frame into several portions. Each portion of the RS frame is equivalent to a data amount that can be transmitted by a data group.
0179The output multiplexer (MUX) <b>320</b> multiplexes portions within M number of RS frame encoders <b>310</b> to <b>310</b>M−1 are multiplexed and then outputted to the block processor <b>302</b>. For example, if one parade transmits two RS frames, portions of primary RS frames within M number of RS frame encoders <b>310</b> to <b>310</b>M−1 are multiplexed and outputted. Thereafter, portions of secondary RS frames within M number of RS frame encoders <b>310</b> to <b>310</b>M−1 are multiplexed and transmitted. The input demultiplexer (DEMUX) <b>309</b> and the output multiplexer (MUX) <b>320</b> operate based upon the control of the control unit <b>200</b>. The control unit <b>200</b> may provide necessary (or required) FEC modes to each RS frame encoder. The FEC mode includes the RS code mode, which will be described in detail in a later process.
0180<figref idref="DRAWINGS">FIG. 18</figref> illustrates a detailed block diagram of an RS frame encoder among a plurality of RS frame encoders within an MPH frame encoder. One RS frame encoder may include a primary encoder <b>410</b> and a secondary encoder <b>420</b>. Herein, the secondary encoder <b>420</b> may or may not operate based upon the RS frame mode. For example, when the RS frame mode value is equal to ‘00’, as shown in Table 1, the secondary encoder <b>420</b> does not operate. The primary encoder <b>410</b> may include a data randomizer <b>411</b>, a Reed-Solomon-cyclic redundancy check (RS-CRC) encoder (<b>412</b>), and a RS frame divider <b>413</b>. And, the secondary encoder <b>420</b> may also include a data randomizer <b>421</b>, a RS-CRC encoder (<b>422</b>), and a RS frame divider <b>423</b>.
0181More specifically, the data randomizer <b>411</b> of the primary encoder <b>410</b> receives mobile service data of a primary ensemble outputted from the output demultiplexer (DEMUX) <b>309</b>. Then, after randomizing the received mobile service data, the data randomizer <b>411</b> outputs the randomized data to the RS-CRC encoder <b>412</b>. At this point, since the data randomizer <b>411</b> performs the randomizing process on the mobile service data, the randomizing process that is to be performed by the data randomizer <b>251</b> of the post-processor <b>250</b> on the mobile service data may be omitted. The data randomizer <b>411</b> may also discard the synchronization byte within the mobile service data packet and perform the randomizing process. This is an option that may be chosen by the system designer. In the example given in the present invention, the randomizing process is performed without discarding the synchronization byte within the corresponding mobile service data packet.
0182The RS-CRC encoder <b>412</b> uses at least one of a Reed-Solomon (RS) code and a cyclic redundancy check (CRC) code, so as to perform forward error collection (FEC) encoding on the randomized primary ensemble, thereby forming a primary RS frame. Therefore, the RS-CRC encoder <b>412</b> outputs the newly formed primary RS frame to the RS frame divider <b>413</b>. The RS-CRC encoder <b>412</b> groups a plurality of mobile service data packets that is randomized and inputted, so as to create a RS frame. Then, the RS-CRC encoder <b>412</b> performs at least one of an error correction encoding process and an error detection encoding process in RS frame units. Accordingly, robustness may be provided to the mobile service data, thereby scattering group error that may occur during changes in a frequency environment, thereby enabling the mobile service data to respond to the frequency environment, which is extremely vulnerable and liable to frequent changes. Also, the RS-CRC encoder <b>412</b> groups a plurality of RS frame so as to create a super frame, thereby performing a row permutation process in super frame units. The row permutation process may also be referred to as a “row interleaving process”. Hereinafter, the process will be referred to as “row permutation” for simplicity.
0183More specifically, when the RS-CRC encoder <b>412</b> performs the process of permuting each row of the super frame in accordance with a pre-determined rule, the position of the rows within the super frame before and after the row permutation process is changed. If the row permutation process is performed by super frame units, and even though the section having a plurality of errors occurring therein becomes very long, and even though the number of errors included in the RS frame, which is to be decoded, exceeds the extent of being able to be corrected, the errors become dispersed within the entire super frame. Thus, the decoding ability is even more enhanced as compared to a single RS frame.
0184At this point, as an example of the present invention, RS-encoding is applied for the error correction encoding process, and a cyclic redundancy check (CRC) encoding is applied for the error detection process in the RS-CRC encoder <b>412</b>. When performing the RS-encoding, parity data that are used for the error correction are generated. And, when performing the CRC encoding, CRC data that are used for the error detection are generated. The CRC data generated by CRC encoding may be used for indicating whether or not the mobile service data have been damaged by the errors while being transmitted through the channel. In the present invention, a variety of error detection coding methods other than the CRC encoding method may be used, or the error correction coding method may be used to enhance the overall error correction ability of the receiving system. Herein, the RS-CRC encoder <b>412</b> refers to a pre-determined transmission parameter provided by the control unit <b>200</b> and/or a transmission parameter provided from the service multiplexer <b>100</b> so as to perform operations including RS frame configuration, RS encoding, CRC encoding, super frame configuration, and row permutation in super frame units.
0185<figref idref="DRAWINGS">FIG. 19</figref> illustrates a process of one or two RS frame being divided into several portions, based upon an RS frame mode value, and a process of each portion being assigned to a corresponding region within the respective data group. More specifically, <figref idref="DRAWINGS">FIG. 19(a)</figref> shows an example of the RS frame mode value being equal to ‘00’. Herein, only the primary encoder <b>410</b> of <figref idref="DRAWINGS">FIG. 18</figref> operates, thereby forming one RS frame for one parade. Then, the RS frame is divided into several portions, and the data of each portion are assigned to regions A/B/C/D within the respective data group. <figref idref="DRAWINGS">FIG. 19(b)</figref> shows an example of the RS frame mode value being equal to ‘01’. Herein, both the primary encoder <b>410</b> and the secondary encoder <b>420</b> of <figref idref="DRAWINGS">FIG. 18</figref> operate, thereby forming two RS frames for one parade, i.e., one primary RS frame and one secondary RS frame. Then, the primary RS frame is divided into several portions, and the secondary RS frame is divided into several portions. At this point, the data of each portion of the primary RS frame are assigned to regions A/B within the respective data group. And, the data of each portion of the secondary RS frame are assigned to regions C/D within the respective data group.
0000Detailed Description of the RS Frame
0186<figref idref="DRAWINGS">FIG. 20(a)</figref> illustrates an example of an RS frame being generated from the RS-CRC encoder <b>412</b> according to the present invention. According to this embodiment, in the RS frame, the length of a column (i.e., number of rows) is set to 187 bytes, and the length of a row (i.e., number of column) is set to N bytes. At this point, the value of N, which corresponds to the number of columns within an RS frame, can be decided according to Equation 2.
0187<maths id="MATH-US-00001" num="00001"><math overflow="scroll"><mtable><mtr><mtd><mrow><mi>N</mi><mo>=</mo><mrow><mrow><mo>⌊</mo><mfrac><mrow><mn>5</mn><mo>×</mo><mi>NoG</mi><mo>×</mo><mi>PL</mi></mrow><mrow><mn>187</mn><mo>+</mo><mi>P</mi></mrow></mfrac><mo>⌋</mo></mrow><mo>-</mo><mn>2</mn></mrow></mrow></mtd><mtd><mrow><mi>Equation</mi><mo></mo><mstyle><mspace width="0.8em" height="0.8ex" /></mstyle><mo></mo><mn>2</mn></mrow></mtd></mtr></mtable></math></maths><img file="USRE46728E_D0001.tif" /><img file="USRE46728E_D0002.tif" /><img file="USRE46728E_D0003.tif" /><img file="USRE46728E_D0004.tif" /><img file="USRE46728E_D0005.tif" /><img file="USRE46728E_D0006.tif" /><ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0000"><ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0188">Herein, NoG indicates the number of data groups assigned to a sub-frame. PL represents the number of SCCC payload data bytes assigned to a data group. And, P signifies the number of RS parity data bytes added to each column of the RS frame. Finally, └X┘ is the greatest integer that is equal to or smaller than X.</li></ul></li></ul>
0189More specifically, in Equation 2, PL corresponds to the length of an RS frame portion. The value of PL is equivalent to the number of SCCC payload data bytes that are assigned to the corresponding data group. Herein, the value of PL may vary depending upon the RS frame mode, SCCC block mode, and SCCC outer code mode. Table 2 to Table 5 below respectively show examples of PL values, which vary in accordance with the RS frame mode, SCCC block mode, and SCCC outer code mode. The SCCC block mode and the SCCC outer code mode will be described in detail in a later process.
0190<tables id="TABLE-US-00002" num="00002"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="182pt" align="center" /><colspec colname="2" colwidth="35pt" align="center" /><thead><row><entry namest="1" nameend="2" rowsep="1">TABLE 2</entry></row></thead><tbody valign="top"><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>SCCC outer code mode</entry><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="1" colwidth="42pt" align="center" /><colspec colname="2" colwidth="49pt" align="center" /><colspec colname="3" colwidth="42pt" align="center" /><colspec colname="4" colwidth="49pt" align="center" /><colspec colname="5" colwidth="35pt" align="center" /><tbody valign="top"><row><entry>for Region A</entry><entry>for Region B</entry><entry>for Region C</entry><entry>for Region D</entry><entry>PL</entry></row><row><entry namest="1" nameend="5" align="center" rowsep="1" /></row><row><entry>00</entry><entry>00</entry><entry>00</entry><entry>00</entry><entry>9624</entry></row><row><entry>00</entry><entry>00</entry><entry>00</entry><entry>01</entry><entry>9372</entry></row><row><entry>00</entry><entry>00</entry><entry>01</entry><entry>00</entry><entry>8886</entry></row><row><entry>00</entry><entry>00</entry><entry>01</entry><entry>01</entry><entry>8634</entry></row><row><entry>00</entry><entry>01</entry><entry>00</entry><entry>00</entry><entry>8403</entry></row><row><entry>00</entry><entry>01</entry><entry>00</entry><entry>01</entry><entry>8151</entry></row><row><entry>00</entry><entry>01</entry><entry>01</entry><entry>00</entry><entry>7665</entry></row><row><entry>00</entry><entry>01</entry><entry>01</entry><entry>01</entry><entry>7413</entry></row><row><entry>01</entry><entry>00</entry><entry>00</entry><entry>00</entry><entry>7023</entry></row><row><entry>01</entry><entry>00</entry><entry>00</entry><entry>01</entry><entry>6771</entry></row><row><entry>01</entry><entry>00</entry><entry>01</entry><entry>00</entry><entry>6285</entry></row><row><entry>01</entry><entry>00</entry><entry>01</entry><entry>01</entry><entry>6033</entry></row><row><entry>01</entry><entry>01</entry><entry>00</entry><entry>00</entry><entry>5802</entry></row><row><entry>01</entry><entry>01</entry><entry>00</entry><entry>01</entry><entry>5550</entry></row><row><entry>01</entry><entry>01</entry><entry>01</entry><entry>00</entry><entry>5064</entry></row><row><entry>01</entry><entry>01</entry><entry>01</entry><entry>01</entry><entry>4812</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="182pt" align="center" /><colspec colname="2" colwidth="35pt" align="center" /><tbody valign="top"><row><entry>Others</entry><entry>Reserved</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>
0191Table 2 shows an example of the PL values for each data group within an RS frame, wherein each PL value varies depending upon the SCCC outer code mode, when the RS frame mode value is equal to ‘00’, and when the SCCC block mode value is equal to ‘00’. For example, when it is assumed that each SCCC outer code mode value of regions A/B/C/D within the data group is equal to ‘00’ (i.e., the block processor <b>302</b> of a later block performs encoding at a coding rate of 1/2), the PL value within each data group of the corresponding RS frame may be equal to 9624 bytes. More specifically, 9624 bytes of mobile service data within one RS frame may be assigned to regions A/B/C/D of the corresponding data group.
0192<tables id="TABLE-US-00003" num="00003"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="offset" colwidth="42pt" align="left" /><colspec colname="1" colwidth="70pt" align="center" /><colspec colname="2" colwidth="105pt" align="center" /><thead><row><entry /><entry namest="offset" nameend="2" rowsep="1">TABLE 3</entry></row><row><entry /><entry namest="offset" nameend="2" align="center" rowsep="1" /></row><row><entry /><entry>SCCC outer code mode</entry><entry>PL</entry></row><row><entry /><entry namest="offset" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>00</entry><entry>9624</entry></row><row><entry /><entry>01</entry><entry>4812</entry></row><row><entry /><entry>Others</entry><entry>Reserved</entry></row><row><entry /><entry namest="offset" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>
0193Table 3 shows an example of the PL values for each data group within an RS frame, wherein each PL value varies depending upon the SCCC outer code mode, when the RS frame mode value is equal to ‘00’, and when the SCCC block mode value is equal to ‘01’.
0194<tables id="TABLE-US-00004" num="00004"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="133pt" align="center" /><colspec colname="2" colwidth="84pt" align="center" /><thead><row><entry namest="1" nameend="2" rowsep="1">TABLE 4</entry></row></thead><tbody valign="top"><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>SCCC outer code mode</entry><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="91pt" align="center" /><colspec colname="2" colwidth="42pt" align="center" /><colspec colname="3" colwidth="84pt" align="center" /><tbody valign="top"><row><entry>for Region A</entry><entry>for Region B</entry><entry>PL</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry>00</entry><entry>00</entry><entry>7644</entry></row><row><entry>00</entry><entry>01</entry><entry>6423</entry></row><row><entry>01</entry><entry>00</entry><entry>5043</entry></row><row><entry>01</entry><entry>01</entry><entry>3822</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="133pt" align="center" /><colspec colname="2" colwidth="84pt" align="center" /><tbody valign="top"><row><entry>Others</entry><entry>Reserved</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>
0195Table 4 shows an example of the PL values for each data group within a primary RS frame, wherein each PL value varies depending upon the SCCC outer code mode, when the RS frame mode value is equal to ‘01’, and when the SCCC block mode value is equal to ‘00’. For example, when each SCCC outer code mode value of regions A/B is equal to ‘00’, 7644 bytes of mobile service data within a primary RS frame may be assigned to regions A/B of the corresponding data group.
0196<tables id="TABLE-US-00005" num="00005"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="133pt" align="center" /><colspec colname="2" colwidth="84pt" align="center" /><thead><row><entry namest="1" nameend="2" rowsep="1">TABLE 5</entry></row></thead><tbody valign="top"><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>SCCC outer code mode</entry><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="91pt" align="center" /><colspec colname="2" colwidth="42pt" align="center" /><colspec colname="3" colwidth="84pt" align="center" /><tbody valign="top"><row><entry>for Region C</entry><entry>for Region D</entry><entry>PL</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="91pt" align="center" /><colspec colname="2" colwidth="42pt" align="center" /><colspec colname="3" colwidth="84pt" align="char" char="." /><tbody valign="top"><row><entry>00</entry><entry>00</entry><entry>1980</entry></row><row><entry>00</entry><entry>01</entry><entry>1728</entry></row><row><entry>01</entry><entry>00</entry><entry>1242</entry></row><row><entry>01</entry><entry>01</entry><entry>990</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="133pt" align="center" /><colspec colname="2" colwidth="84pt" align="center" /><tbody valign="top"><row><entry>Others</entry><entry>Reserved</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>
0197Table 5 shows an example of the PL values for each data group within a secondary RS frame, wherein each PL value varies depending upon the SCCC outer code mode, when the RS frame mode value is equal to ‘01’, and when the SCCC block mode value is equal to ‘00’. For example, when each SCCC outer code mode value of regions C/D is equal to ‘00’, 1980 bytes of mobile service data within a secondary RS frame may be assigned to regions C/D of the corresponding data group.
0198According to the embodiment of the present invention, the value of N is equal to or greater than 187 (i.e., N≧187). More specifically, the RS frame of <figref idref="DRAWINGS">FIG. 20(a)</figref> has the size of N(row)×187(column) bytes. More specifically, the RS-CRC encoder <b>412</b> first divides the inputted mobile service data bytes to units of a predetermined length. The predetermined length is decided by the system designer. And, in the example of the present invention, the predetermined length is equal to 187 bytes, and, therefore, the 187-byte unit will be referred to as a “packet” for simplicity. For example, the inputted mobile service data may correspond either to an MPEG transport stream (TS) packet configured of 188-byte units or to an IP datagram. Alternatively, the IP datagram may be encapsulated to a TS packet of 188-byte units and, then, inputted.
0199When the mobile service data that are being inputted correspond to a MPEG transport packet stream configured of 188-byte units, the first synchronization byte is removed so as to configure a 187-byte unit. Then, N number of packets are grouped to form an RS frame. Herein, the synchronization byte is removed because each mobile service data packet has the same value. Meanwhile, when the input mobile service data of the RS frame do not correspond to the MPEG TS packet format, the mobile service data are inputted N number of times in 187-byte units without being processed with the removing of the MPEG synchronization byte, thereby creating a RS frame.
0200In addition, when the input data format of the RS frame supports both the input data corresponding to the MPEG TS packet and the input data not corresponding to the MPEG TS packet, such information may be included in a transmission parameter transmitted from the service multiplexer <b>100</b>, thereby being sent to the transmitter <b>200</b>. Accordingly, the RS-CRC encoder <b>412</b> of the transmitter <b>200</b> receives this information to be able to control whether or not to perform the process of removing the MPEG synchronization byte. Also, the transmitter provides such information to the receiving system so as to control the process of inserting the MPEG synchronization byte that is to be performed by the RS frame decoder of the receiving system. Herein, the process of removing the synchronization byte may be performed during a randomizing process of the data randomizer <b>411</b> in an earlier process. In this case, the process of the removing the synchronization byte by the RS-CRC encoder <b>412</b> may be omitted.
0201Moreover, when adding synchronization bytes from the receiving system, the process may be performed by the data derandomizer instead of the RS frame decoder. Therefore, if a removable fixed byte (e.g., synchronization byte) does not exist within the mobile service data packet that is being inputted to the RS-CRC encoder <b>412</b>, or if the mobile service data that are being inputted are not configured in a packet format, the mobile service data that are being inputted are divided into 187-byte units, thereby configuring a packet for each 187-byte unit.
0202Subsequently, N number of packets configured of 187 bytes is grouped to configure a RS frame. At this point, the RS frame is configured as a RS frame having the size of N(row)×187(column) bytes, in which 187-byte packets are sequentially inputted in a row direction. More specifically, each of the N number of columns included in the RS frame includes 187 bytes. When the RS frame is created, as shown in <figref idref="DRAWINGS">FIG. 20(a)</figref>, the RS-CRC encoder <b>412</b> performs a (Nc,Kc)-RS encoding process on each column, so as to generate Nc−Kc(=P) number of parity bytes. Then, the RS-CRC encoder <b>412</b> adds the newly generated P number of parity bytes after the very last byte of the corresponding column, thereby creating a column of (187+P) bytes. Herein, as shown in <figref idref="DRAWINGS">FIG. 20(a)</figref>, Kc is equal to 187 (i.e., Kc=187), and Nc is equal to 187+P (i.e., Nc=187+P). Herein, the value of P may vary depending upon the RS code mode. Table 6 below shows an example of an RS code mode, as one of the RS encoding information.
0203<tables id="TABLE-US-00006" num="00006"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="70pt" align="center" /><colspec colname="2" colwidth="35pt" align="center" /><colspec colname="3" colwidth="112pt" align="center" /><thead><row><entry namest="1" nameend="3" rowsep="1">TABLE 6</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry>RS code mode</entry><entry>RS code</entry><entry>Number of Parity Bytes (P)</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>00</entry><entry>(211, 187)</entry><entry>24</entry></row><row><entry>01</entry><entry>(223, 187)</entry><entry>36</entry></row><row><entry>10</entry><entry>(235, 187)</entry><entry>48</entry></row><row><entry>11</entry><entry>Reserved</entry><entry>Reserved</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>
0204Table 6 shows an example of 2 bits being assigned in order to indicate the RS code mode. The RS code mode represents the number of parity bytes corresponding to the RS frame. For example, when the RS code mode value is equal to ‘10’, (235,187)-RS-encoding is performed on the RS frame of <figref idref="DRAWINGS">FIG. 20(a)</figref>, so as to generate 48 parity data bytes. Thereafter, the 48 parity bytes are added after the last data byte of the corresponding column, thereby creating a column of 235 data bytes. When the RS frame mode value is equal to ‘00’ in Table 1 (i.e., when the RS frame mode indicates a single RS frame), only the RS code mode of the corresponding RS frame is indicated. However, when the RS frame mode value is equal to ‘01’ in Table 1 (i.e., when the RS frame mode indicates multiple RS frames), the RS code mode corresponding to a primary RS frame and a secondary RS frame. More specifically, it is preferable that the RS code mode is independently applied to the primary RS frame and the secondary RS frame.
0205When such RS encoding process is performed on all N number of columns, a RS frame having the size of N(row)×(187+P)(column) bytes may be created, as shown in <figref idref="DRAWINGS">FIG. 20(b)</figref>. Each row of the RS frame is configured of N bytes. However, depending upon channel conditions between the transmitting system and the receiving system, error may be included in the RS frame. When errors occur as described above, CRC data (or CRC code or CRC checksum) may be used on each row unit in order to verify whether error exists in each row unit. The RS-CRC encoder <b>412</b> may perform CRC encoding on the mobile service data being RS encoded so as to create (or generate) the CRC data. The CRC data being generated by CRC encoding may be used to indicate whether the mobile service data have been damaged while being transmitted through the channel.
0206The present invention may also use different error detection encoding methods other than the CRC encoding method. Alternatively, the present invention may use the error correction encoding method to enhance the overall error correction ability of the receiving system. <figref idref="DRAWINGS">FIG. 20(c)</figref> illustrates an example of using a 2-byte (i.e., 16-bit) CRC checksum as the CRC data. Herein, a 2-byte CRC checksum is generated for N number of bytes of each row, thereby adding the 2-byte CRC checksum at the end of the N number of bytes. Thus, each row is expanded to (N+2) number of bytes. Equation 3 below corresponds to an exemplary equation for generating a 2-byte CRC checksum for each row being configured of N number of bytes. <br />g(x)=x<sup>16</sup>+x<sup>12</sup>+x<sup>5</sup>+1 Equation 3
0207The process of adding a 2-byte checksum in each row is only exemplary. Therefore, the present invention is not limited only to the example proposed in the description set forth herein. As described above, when the process of RS encoding and CRC encoding are completed, the (N×187)-byte RS frame is expanded to a (N+2)×(187+P)-byte RS frame. Based upon an error correction scenario of a RS frame expanded as described above, the data bytes within the RS frame are transmitted through a channel in a row direction. At this point, when a large number of errors occur during a limited period of transmission time, errors also occur in a row direction within the RS frame being processed with a decoding process in the receiving system. However, in the perspective of RS encoding performed in a column direction, the errors are shown as being scattered. Therefore, error correction may be performed more effectively. At this point, a method of increasing the number of parity data bytes (P) may be used in order to perform a more intense error correction process. However, using this method may lead to a decrease in transmission efficiency. Therefore, a mutually advantageous method is required. Furthermore, when performing the decoding process, an erasure decoding process may be used to enhance the error correction performance.
0208Additionally, the RS-CRC encoder <b>412</b> according to the present invention also performs a row permutation (or interleaving) process in super frame units in order to further enhance the error correction performance when error correction the RS frame. <figref idref="DRAWINGS">FIG. 21(a)</figref> to <figref idref="DRAWINGS">FIG. 21(d)</figref> illustrates an example of performing a row permutation process in super frame units according to the present invention. More specifically, G number of RS frames RS-CRC-encoded is grouped to form a super frame, as shown in <figref idref="DRAWINGS">FIG. 21(a)</figref>. At this point, since each RS frame is formed of (N+2)×(187+P) number of bytes, one super frame is configured to have the size of (N+2)×(187+P)×G bytes.
0209When a row permutation process permuting each row of the super frame configured as described above is performed based upon a pre-determined permutation rule, the positions of the rows prior to and after being permuted (or interleaved) within the super frame may be altered. More specifically, the i<sup>th </sup>row of the super frame prior to the interleaving process, as shown in <figref idref="DRAWINGS">FIG. 21(b)</figref>, is positioned in the j<sup>th </sup>row of the same super frame after the row permutation process, as shown in <figref idref="DRAWINGS">FIG. 21(c)</figref>. The above-described relation between i and j can be easily understood with reference to a permutation rule as shown in Equation 4 below. <br />j=G(imod(187+P))+└i/(187+P)┘<br />i=(187+P)(jmod G)+└j/G┘<br />where 0≦i, j≦(187+P)G−1; or<br />where 0≦i, j<(187+P)G Equation 4<ul id="ul0005" list-style="none"><li id="ul0005-0001" num="0000"><ul id="ul0006" list-style="none"><li id="ul0006-0001" num="0210">Herein, each row of the super frame is configured of (N+2) number of data bytes even after being row-permuted in super frame units.</li></ul></li></ul>
0211When all row permutation processes in super frame units are completed, the super frame is once again divided into G number of row-permuted RS frames, as shown in <figref idref="DRAWINGS">FIG. 21(d)</figref>, and then provided to the RS frame divider <b>413</b>. Herein, the number of RS parity bytes and the number of columns should be equally provided in each of the RS frames, which configure a super frame. As described in the error correction scenario of a RS frame, in case of the super frame, a section having a large number of error occurring therein is so long that, even when one RS frame that is to be decoded includes an excessive number of errors (i.e., to an extent that the errors cannot be corrected), such errors are scattered throughout the entire super frame. Therefore, in comparison with a single RS frame, the decoding performance of the super frame is more enhanced.
0212The above description of the present invention corresponds to the processes of forming (or creating) and encoding an RS frame, when a data group is divided into regions A/B/C/D, and when data of an RS frame are assigned to all of regions A/B/C/D within the corresponding data group. More specifically, the above description corresponds to an embodiment of the present invention, wherein one RS frame is transmitted using one parade. In this embodiment, the secondary encoder <b>420</b> does not operate (or is not active).
0213Meanwhile, 2 RS frames are transmitting using one parade, the data of the primary RS frame may be assigned to regions A/B within the data group and be transmitted, and the data of the secondary RS frame may be assigned to regions C/D within the data group and be transmitted. At this point, the primary encoder <b>410</b> receives the mobile service data that are to be assigned to regions A/B within the data group, so as to form the primary RS frame, thereby performing RS-encoding and CRC-encoding. Similarly, the secondary encoder <b>420</b> receives the mobile service data that are to be assigned to regions C/D within the data group, so as to form the secondary RS frame, thereby performing RS-encoding and CRC-encoding. More specifically, the primary RS frame and the secondary RS frame are created independently.
0214<figref idref="DRAWINGS">FIG. 22</figref> illustrates examples of receiving the mobile service data that are to be assigned to regions A/B within the data group, so as to form the primary RS frame, and receives the mobile service data that are to be assigned to regions C/D within the data group, so as to form the secondary RS frame, thereby performing error correction encoding and error detection encoding on each of the first and secondary RS frames. More specifically, <figref idref="DRAWINGS">FIG. 22(a)</figref> illustrates an example of the RS-CRC encoder <b>412</b> of the primary encoder <b>410</b> receiving mobile service data of the primary ensemble that are to be assigned to regions A/B within the corresponding data group, so as to create an RS frame having the size of N<b>1</b>(row)×187(column). Then, in this example, the primary encoder <b>410</b> performs RS-encoding on each column of the RS frame created as described above, thereby adding P<b>1</b> number of parity data bytes in each column. Finally, the primary encoder <b>410</b> performs CRC-encoding on each row, thereby adding a 2-byte checksum in each row.
0215<figref idref="DRAWINGS">FIG. 22(b)</figref> illustrates an example of the RS-CRC encoder <b>422</b> of the secondary encoder <b>420</b> receiving mobile service data of the secondary ensemble that are to be assigned to regions C/D within the corresponding data group, so as to create an RS frame having the size of N<b>2</b>(row)×187(column). Then, in this example, the secondary encoder <b>420</b> performs RS-encoding on each column of the RS frame created as described above, thereby adding P<b>2</b> number of parity data bytes in each column. Finally, the secondary encoder <b>420</b> performs CRC-encoding on each row, thereby adding a 2-byte checksum in each row. At this point, each of the RS-CRC encoders <b>412</b> and <b>422</b> may refer to a pre-determined transmission parameter provided by the control unit <b>200</b> and/or a transmission parameter provided from the service multiplexer <b>100</b>, the RS-CRC encoders <b>412</b> and <b>422</b> may be informed of RS frame information (including RS frame mode), RS encoding information (including RS code mode), SCCC information (including SCCC block information and SCCC outer code mode), data group information, and region information within a data group. The RS-CRC encoders <b>412</b> and <b>422</b> may refer to the transmission parameters for the purpose of RS frame configuration, error correction encoding, error detection encoding. Furthermore, the transmission parameters should also be transmitted to the receiving system so that the receiving system can perform a normal decoding process.
0216The data of the primary RS frame, which is encoded by RS frame units and row-permuted by super frame units from the RS-CRC encoder <b>412</b> of the primary encoder <b>410</b>, are outputted to the RS frame divider <b>413</b>. If the secondary encoder <b>420</b> also operates in the embodiment of the present invention, the data of the secondary RS frame, which is encoded by RS frame units and row-permuted by super frame units from the RS-CRC encoder <b>422</b> of the secondary encoder <b>420</b>, are outputted to the RS frame divider <b>423</b>. The RS frame divider <b>413</b> of the primary encoder <b>410</b> divides the primary RS frame into several portions, which are then outputted to the output multiplexer (MUX) <b>320</b>. Each portion of the primary RS frame is equivalent to a data amount that can be transmitted by one data group. Similarly, the RS frame divider <b>423</b> of the secondary encoder <b>420</b> divides the secondary RS frame into several portions, which are then outputted to the output multiplexer (MUX) <b>320</b>.
0217Hereinafter, the RS frame divider <b>413</b> of the primary RS encoder <b>410</b> will now be described in detail. Also, in order to simplify the description of the present invention, it is assumed that an RS frame having the size of N(row)×187(column), as shown in <figref idref="DRAWINGS">FIG. 20(a)</figref> to <figref idref="DRAWINGS">FIG. 20(c)</figref>, that P number of parity data bytes are added to each column by RS-encoding the RS frame, and that a 2-byte checksum is added to each row by CRC-encoding the RS frame. Accordingly, the RS frame divider <b>413</b> divides (or partitions) the encoded RS frame having the size of (N+2)(row)×187(column) into several portions, each having the size of PL (wherein PL corresponds to the length of the RS frame portion).
0218At this point, as shown in Table 2 to Table 5, the value of PL may vary depending upon the RS frame mode, SCCC block mode, and SCCC outer coder mode. Also, the total number of data bytes of the RS-encoded and CRC-encoded RS frame is equal to or smaller than 5×NoG×PL. In this case, the RS frame is divided (or partitioned) into ((5×NoG)−1) number of portions each having the size of PL and one portion having a size equal to smaller than PL. More specifically, with the exception of the last portion of the RS frame, each of the remaining portions of the RS frame has an equal size of PL. If the size of the last portion is smaller than PL, a stuffing byte (or dummy byte) may be inserted in order to fill (or replace) the lacking number of data bytes, thereby enabling the last portion of the RS frame to also be equal to PL. Each portion of an RS frame corresponds to the amount of data that are to be SCCC-encoded and mapped into a single data group of a parade.
0219<figref idref="DRAWINGS">FIG. 23(a)</figref> and <figref idref="DRAWINGS">FIG. 23(b)</figref> respectively illustrate examples of adding S number of stuffing bytes, when an RS frame having the size of (N+2)(row)×(187+P)(column) is divided into 5×NoG number of portions, each having the size of PL. More specifically, the RS-encoded and CRC-encoded RS frame, shown in <figref idref="DRAWINGS">FIG. 23(a)</figref>, is divided into several portions, as shown in <figref idref="DRAWINGS">FIG. 23(b)</figref>. The number of divided portions at the RS frame is equal to (5×NoG). Particularly, the first ((5×NoG)−1) number of portions each has the size of PL, and the last portion of the RS frame may be equal to or smaller than PL. If the size of the last portion is smaller than PL, a stuffing byte (or dummy byte) may be inserted in order to fill (or replace) the lacking number of data bytes, as shown in Equation 5 below, thereby enabling the last portion of the RS frame to also be equal to PL. <br />S=(5×NoG×PL)−((N+2)×(187+P)) Equation 5<ul id="ul0007" list-style="none"><li id="ul0007-0001" num="0000"><ul id="ul0008" list-style="none"><li id="ul0008-0001" num="0220">Herein, each portion including data having the size of PL passes through the output multiplexer <b>320</b> of the MPH frame encoder <b>301</b>, which is then outputted to the block processor <b>302</b>.</li></ul></li></ul>
0221At this point, the mapping order of the RS frame portions to a parade of data groups in not identical with the group assignment order defined in Equation 1. When given the group positions of a parade in an MPH frame, the SCCC-encoded RS frame portions will be mapped in a time order (i.e., in a left-to-right direction). For example, as shown in <figref idref="DRAWINGS">FIG. 11</figref>, data groups of the 2<sup>nd </sup>parade (Parade #<b>1</b>) are first assigned (or allocated) to the 13<sup>th </sup>slot (Slot #<b>12</b>) and then assigned to the 3<sup>rd </sup>slot (Slot #<b>2</b>). However, when the data are actually placed in the assigned slots, the data are placed in a time sequence (or time order, i.e., in a left-to-right direction). More specifically, the 1<sup>st </sup>data group of Parade #<b>1</b> is placed in Slot #<b>2</b>, and the 2<sup>nd </sup>data group of Parade #<b>1</b> is placed in Slot #<b>12</b>.
0000Block Processor
0222Meanwhile, the block processor <b>302</b> performs an SCCC outer encoding process on the output of the MPH frame encoder <b>301</b>. More specifically, the block processor <b>302</b> receives the data of each error correction encoded portion. Then, the block processor <b>302</b> encodes the data once again at a coding rate of 1/H (wherein H is an integer equal to or greater than 2 (i.e., H≧2)), thereby outputting the 1/H-rate encoded data to the group formatter <b>303</b>. According to the embodiment of the present invention, the input data are encoded either at a coding rate of 1/2 (also referred to as “1/2-rate encoding”) or at a coding rate of 1/4 (also referred to as “1/4-rate encoding”). The data of each portion outputted from the MPH frame encoder <b>301</b> may include at least one of pure mobile service data, RS parity data, CRC data, and stuffing data. However, in a broader meaning, the data included in each portion may correspond to data for mobile services. Therefore, the data included in each portion will all be considered as mobile service data and described accordingly.
0223The group formatter <b>303</b> inserts the mobile service data SCCC-outer-encoded and outputted from the block processor <b>302</b> in the corresponding region within the data group, which is formed in accordance with a pre-defined rule. Also, in association with the data deinterleaving process, the group formatter <b>303</b> inserts various place holders (or known data place holders) in the corresponding region within the data group. Thereafter, the group formatter <b>303</b> deinterleaves the data within the data group and the place holders.
0224According to the present invention, with reference to data after being data-interleaved, as shown in <figref idref="DRAWINGS">FIG. 5</figref>, a data groups is configured of 10 MPH blocks (B<b>1</b> to B<b>10</b>) and divided into 4 regions (A, B, C, and D). Also, as shown in <figref idref="DRAWINGS">FIG. 5</figref>, when it is assumed that the data group is divided into a plurality of hierarchical regions, as described above, the block processor <b>302</b> may encode the mobile service data, which are to be inserted to each region based upon the characteristic of each hierarchical region, at different coding rates. For example, the block processor <b>302</b> may encode the mobile service data, which are to be inserted in region A/B within the corresponding data group, at a coding rate of 1/2. Then, the group formatter <b>303</b> may insert the 1/2-rate encoded mobile service data to region A/B. Also, the block processor <b>302</b> may encode the mobile service data, which are to be inserted in region C/D within the corresponding data group, at a coding rate of 1/4 having higher (or stronger) error correction ability than the 1/2-coding rate. Thereafter, the group formatter <b>303</b> may insert the 1/2-rate encoded mobile service data to region C/D. In another example, the block processor <b>302</b> may encode the mobile service data, which are to be inserted in region C/D, at a coding rate having higher error correction ability than the 1/4-coding rate. Then, the group formatter <b>303</b> may either insert the encoded mobile service data to region C/D, as described above, or leave the data in a reserved region for future usage.
0225According to another embodiment of the present invention, the block processor <b>302</b> may perform a 1/H-rate encoding process in SCCC block units. Herein, the SCCC block includes at least one MPH block. At this point, when 1/H-rate encoding is performed in MPH block units, the MPH blocks (B<b>1</b> to B<b>10</b>) and the SCCC block (SCB<b>1</b> to SCB<b>10</b>) become identical to one another (i.e., SCB<b>1</b>=B<b>1</b>, SCB<b>2</b>=B<b>2</b>, SCB<b>3</b>=B<b>3</b>, SCB<b>4</b>=B<b>4</b>, SCB<b>5</b>=B<b>5</b>, SCB<b>6</b>=B<b>6</b>, SCB<b>7</b>=B<b>7</b>, SCB<b>8</b>=B<b>8</b>, SCB<b>9</b>=B<b>9</b>, and SCB<b>10</b>=B<b>10</b>). For example, the MPH block <b>1</b> (B<b>1</b>) may be encoded at the coding rate of 1/2, the MPH block <b>2</b> (B<b>2</b>) may be encoded at the coding rate of 1/4, and the MPH block <b>3</b> (B<b>3</b>) may be encoded at the coding rate of 1/2. The coding rates are applied respectively to the remaining MPH blocks.
0226Alternatively, a plurality of MPH blocks within regions A, B, C, and D may be grouped into one SCCC block, thereby being encoded at a coding rate of 1/H in SCCC block units. Accordingly, the receiving performance of region C/D may be enhanced. For example, MPH block <b>1</b> (B<b>1</b>) to MPH block <b>5</b> (B<b>5</b>) may be grouped into one SCCC block and then encoded at a coding rate of 1/2. Thereafter, the group formatter <b>303</b> may insert the 1/2-rate encoded mobile service data to a section starting from MPH block <b>1</b> (B<b>1</b>) to MPH block <b>5</b> (B<b>5</b>). Furthermore, MPH block <b>6</b> (B<b>6</b>) to MPH block <b>10</b> (B<b>10</b>) may be grouped into one SCCC block and then encoded at a coding rate of 1/4. Thereafter, the group formatter <b>303</b> may insert the 1/4-rate encoded mobile service data to another section starting from MPH block <b>6</b> (B<b>6</b>) to MPH block <b>10</b> (B<b>10</b>). In this case, one data group may consist of two SCCC blocks.
0227According to another embodiment of the present invention, one SCCC block may be formed by grouping two MPH blocks. For example, MPH block <b>1</b> (B<b>1</b>) and MPH block <b>6</b> (B<b>6</b>) may be grouped into one SCCC block (SCB<b>1</b>). Similarly, MPH block <b>2</b> (B<b>2</b>) and MPH block <b>7</b> (B<b>7</b>) may be grouped into another SCCC block (SCB<b>2</b>). Also, MPH block <b>3</b> (B<b>3</b>) and MPH block <b>8</b> (B<b>8</b>) may be grouped into another SCCC block (SCB<b>3</b>). And, MPH block <b>4</b> (B<b>4</b>) and MPH block <b>9</b> (B<b>9</b>) may be grouped into another SCCC block (SCB<b>4</b>). Furthermore, MPH block <b>5</b> (B<b>5</b>) and MPH block <b>10</b> (B<b>10</b>) may be grouped into another SCCC block (SCB<b>5</b>). In the above-described example, the data group may consist of 10 MPH blocks and 5 SCCC blocks. Accordingly, in a data (or signal) receiving environment undergoing frequent and severe channel changes, the receiving performance of regions C and D, which is relatively more deteriorated than the receiving performance of region A, may be reinforced. Furthermore, since the number of mobile service data symbols increases more and more from region A to region D, the error correction encoding performance becomes more and more deteriorated. Therefore, when grouping a plurality of MPH block to form one SCCC block, such deterioration in the error correction encoding performance may be reduced.
0228As described-above, when the block processor <b>302</b> performs encoding at a 1/H-coding rate, information associated with SCCC should be transmitted to the receiving system in order to accurately recover the mobile service data. Table 7 below shows an example of a SCCC block mode, which indicating the relation between an MPH block and an SCCC block, among diverse SCCC block information.
0229<tables id="TABLE-US-00007" num="00007"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="35pt" align="left" /><colspec colname="2" colwidth="182pt" align="center" /><thead><row><entry namest="1" nameend="2" rowsep="1">TABLE 7</entry></row></thead><tbody valign="top"><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry /><entry>SCCC Block Mode</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="1" colwidth="35pt" align="left" /><colspec colname="2" colwidth="56pt" align="center" /><colspec colname="3" colwidth="56pt" align="center" /><colspec colname="4" colwidth="35pt" align="center" /><colspec colname="5" colwidth="35pt" align="center" /><tbody valign="top"><row><entry /><entry>00</entry><entry>01</entry><entry>10</entry><entry>11</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="35pt" align="left" /><colspec colname="2" colwidth="182pt" align="center" /><tbody valign="top"><row><entry /><entry>Description</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="1" colwidth="35pt" align="left" /><colspec colname="2" colwidth="56pt" align="center" /><colspec colname="3" colwidth="56pt" align="center" /><colspec colname="4" colwidth="35pt" align="center" /><colspec colname="5" colwidth="35pt" align="center" /><tbody valign="top"><row><entry /><entry>One MPH Block</entry><entry>Two MPH Blocks</entry><entry /><entry /></row><row><entry /><entry>per SCCC Block</entry><entry>per SCCC Block</entry><entry>Reserved</entry><entry>Reserved</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="35pt" align="left" /><colspec colname="2" colwidth="182pt" align="center" /><tbody valign="top"><row><entry /><entry>SCB</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="1" colwidth="35pt" align="left" /><colspec colname="2" colwidth="56pt" align="center" /><colspec colname="3" colwidth="56pt" align="center" /><colspec colname="4" colwidth="35pt" align="center" /><colspec colname="5" colwidth="35pt" align="center" /><tbody valign="top"><row><entry /><entry>SCB input,</entry><entry>SCB input,</entry><entry /><entry /></row><row><entry /><entry>MPH Block</entry><entry>MPH Blocks</entry></row><row><entry namest="1" nameend="5" align="center" rowsep="1" /></row><row><entry>SCB1</entry><entry>B1</entry><entry>B1 + B6</entry><entry /><entry /></row><row><entry>SCB2</entry><entry>B2</entry><entry>B2 + B7</entry><entry /><entry /></row><row><entry>SCB3</entry><entry>B3</entry><entry>B3 + B8</entry><entry /><entry /></row><row><entry>SCB4</entry><entry>B4</entry><entry>B4 + B9</entry><entry /><entry /></row><row><entry>SCB5</entry><entry>B5</entry><entry> B5 + B10</entry><entry /><entry /></row><row><entry>SCB6</entry><entry>B6</entry><entry>—</entry><entry /><entry /></row><row><entry>SCB7</entry><entry>B7</entry><entry>—</entry><entry /><entry /></row><row><entry>SCB8</entry><entry>B8</entry><entry>—</entry><entry /><entry /></row><row><entry>SCB9</entry><entry>B9</entry><entry>—</entry><entry /><entry /></row><row><entry>SCB10</entry><entry> B10</entry><entry>—</entry></row><row><entry namest="1" nameend="5" align="center" rowsep="1" /></row></tbody></tgroup></table></tables><ul id="ul0009" list-style="none"><li id="ul0009-0001" num="0000"><ul id="ul0010" list-style="none"><li id="ul0010-0001" num="0230">More specifically, Table 4 shows an example of 2 bits being allocated in order to indicate the SCCC block mode. For example, when the SCCC block mode value is equal to ‘00’, this indicates that the SCCC block and the MPH block are identical to one another. Also, when the SCCC block mode value is equal to ‘01’, this indicates that each SCCC block is configured of 2 MPH blocks.</li></ul></li></ul>
0231As described above, if one data group is configured of 2 SCCC blocks, although it is not indicated in Table 7, this information may also be indicated as the SCCC block mode. For example, when the SCCC block mode value is equal to ‘10’, this indicates that each SCCC block is configured of 5 MPH blocks and that one data group is configured of 2 SCCC blocks. Herein, the number of MPH blocks included in an SCCC block and the position of each MPH block may vary depending upon the settings made by the system designer. Therefore, the present invention will not be limited to the examples given herein. Accordingly, the SCCC mode information may also be expanded.
0232An example of a coding rate information of the SCCC block, i.e., SCCC outer code mode, is shown in Table 8 below.
0233<tables id="TABLE-US-00008" num="00008"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="84pt" align="center" /><colspec colname="2" colwidth="133pt" align="left" /><thead><row><entry namest="1" nameend="2" rowsep="1">TABLE 8</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>SCCC outer</entry><entry /></row><row><entry>code mode (2 bits)</entry><entry>Description</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>00</entry><entry>Outer code rate of SCCC block is ½ rate</entry></row><row><entry>01</entry><entry>Outer code rate of SCCC block is ¼ rate</entry></row><row><entry>10</entry><entry>Reserved</entry></row><row><entry>11</entry><entry>Reserved</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables><ul id="ul0011" list-style="none"><li id="ul0011-0001" num="0000"><ul id="ul0012" list-style="none"><li id="ul0012-0001" num="0234">More specifically, Table 8 shows an example of 2 bits being allocated in order to indicate the coding rate information of the SCCC block. For example, when the SCCC outer code mode value is equal to ‘00’, this indicates that the coding rate of the corresponding SCCC block is 1/2. And, when the SCCC outer code mode value is equal to ‘01’, this indicates that the coding rate of the corresponding SCCC block is 1/4.</li></ul></li></ul>
0235If the SCCC block mode value of Table 7 indicates ‘00’, the SCCC outer code mode may indicate the coding rate of each MPH block with respect to each MPH block. In this case, since it is assumed that one data group includes 10 MPH blocks and that 2 bits are allocated for each SCCC block mode, a total of 20 bits are required for indicating the SCCC block modes of the 10 MPH modes. In another example, when the SCCC block mode value of Table 7 indicates ‘00’, the SCCC outer code mode may indicate the coding rate of each region with respect to each region within the data group. In this case, since it is assumed that one data group includes 4 regions (i.e., regions A, B, C, and D) and that 2 bits are allocated for each SCCC block mode, a total of 8 bits are required for indicating the SCCC block modes of the 4 regions. In another example, when the SCCC block mode value of Table 7 is equal to ‘01’, each of the regions A, B, C, and D within the data group has the same SCCC outer code mode.
0236Meanwhile, an example of an SCCC output block length (SOBL) for each SCCC block, when the SCCC block mode value is equal to ‘00’, is shown in Table 9 below.
0237<tables id="TABLE-US-00009" num="00009"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="offset" colwidth="14pt" align="left" /><colspec colname="1" colwidth="42pt" align="left" /><colspec colname="2" colwidth="63pt" align="center" /><colspec colname="3" colwidth="98pt" align="center" /><thead><row><entry /><entry namest="offset" nameend="3" rowsep="1">TABLE 9</entry></row></thead><tbody valign="top"><row><entry /><entry namest="offset" nameend="3" align="center" rowsep="1" /></row><row><entry /><entry /><entry /><entry>SIBL</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="offset" colwidth="14pt" align="left" /><colspec colname="1" colwidth="42pt" align="left" /><colspec colname="2" colwidth="63pt" align="center" /><colspec colname="3" colwidth="28pt" align="center" /><colspec colname="4" colwidth="70pt" align="center" /><tbody valign="top"><row><entry /><entry>SCCC Block</entry><entry>SOBL</entry><entry>½ rate</entry><entry>¼ rate</entry></row><row><entry /><entry namest="offset" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="offset" colwidth="14pt" align="left" /><colspec colname="1" colwidth="42pt" align="left" /><colspec colname="2" colwidth="63pt" align="char" char="." /><colspec colname="3" colwidth="28pt" align="char" char="." /><colspec colname="4" colwidth="70pt" align="center" /><tbody valign="top"><row><entry /><entry>SCB1 (B1)</entry><entry>528</entry><entry>264</entry><entry>132</entry></row><row><entry /><entry>SCB2 (B2)</entry><entry>1536</entry><entry>768</entry><entry>384</entry></row><row><entry /><entry>SCB3 (B3)</entry><entry>2376</entry><entry>1188</entry><entry>594</entry></row><row><entry /><entry>SCB4 (B4)</entry><entry>2388</entry><entry>1194</entry><entry>597</entry></row><row><entry /><entry>SCB5 (B5)</entry><entry>2772</entry><entry>1386</entry><entry>693</entry></row><row><entry /><entry>SCB6 (B6)</entry><entry>2472</entry><entry>1236</entry><entry>618</entry></row><row><entry /><entry>SCB7 (B7)</entry><entry>2772</entry><entry>1386</entry><entry>693</entry></row><row><entry /><entry>SCB8 (B8)</entry><entry>2508</entry><entry>1254</entry><entry>627</entry></row><row><entry /><entry>SCB9 (B9)</entry><entry>1416</entry><entry>708</entry><entry>354</entry></row><row><entry /><entry>SCB10 (B10)</entry><entry>480</entry><entry>240</entry><entry>120</entry></row><row><entry /><entry namest="offset" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables><ul id="ul0013" list-style="none"><li id="ul0013-0001" num="0000"><ul id="ul0014" list-style="none"><li id="ul0014-0001" num="0238">More specifically, when given the SCCC output block length (SOBL) for each SCCC block, an SCCC input block length (SIBL) for each corresponding SCCC block may be decided based upon the outer coding rate of each SCCC block. The SOBL is equivalent to the number of SCCC output (or outer-encoded) bytes for each SCCC block. And, the SIBL is equivalent to the number of SCCC input (or payload) bytes for each SCCC block. Table 10 below shows an example of the SOBL and SIBL for each SCCC block, when the SCCC block mode value is equal to ‘01’.</li></ul></li></ul>
0239<tables id="TABLE-US-00010" num="00010"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="offset" colwidth="21pt" align="left" /><colspec colname="1" colwidth="56pt" align="left" /><colspec colname="2" colwidth="56pt" align="center" /><colspec colname="3" colwidth="84pt" align="center" /><thead><row><entry /><entry namest="offset" nameend="3" rowsep="1">TABLE 10</entry></row></thead><tbody valign="top"><row><entry /><entry namest="offset" nameend="3" align="center" rowsep="1" /></row><row><entry /><entry /><entry /><entry>SIBL</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="offset" colwidth="21pt" align="left" /><colspec colname="1" colwidth="56pt" align="left" /><colspec colname="2" colwidth="56pt" align="center" /><colspec colname="3" colwidth="28pt" align="center" /><colspec colname="4" colwidth="56pt" align="center" /><tbody valign="top"><row><entry /><entry>SCCC Block</entry><entry>SOBL</entry><entry>½ rate</entry><entry>¼ rate</entry></row><row><entry /><entry namest="offset" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="offset" colwidth="21pt" align="left" /><colspec colname="1" colwidth="56pt" align="left" /><colspec colname="2" colwidth="56pt" align="char" char="." /><colspec colname="3" colwidth="28pt" align="char" char="." /><colspec colname="4" colwidth="56pt" align="center" /><tbody valign="top"><row><entry /><entry>SCB1 (B1 + B6)</entry><entry>528</entry><entry>264</entry><entry>132</entry></row><row><entry /><entry>SCB2 (B2 + B7)</entry><entry>1536</entry><entry>768</entry><entry>384</entry></row><row><entry /><entry>SCB3 (B3 + B8)</entry><entry>2376</entry><entry>1188</entry><entry>594</entry></row><row><entry /><entry>SCB4 (B4 + B9)</entry><entry>2388</entry><entry>1194</entry><entry>597</entry></row><row><entry /><entry>SCB5 (B5 + B10)</entry><entry>2772</entry><entry>1386</entry><entry>693</entry></row><row><entry /><entry namest="offset" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>
0240In order to do so, as shown in <figref idref="DRAWINGS">FIG. 24</figref>, the block processor <b>302</b> includes a RS frame portion-SCCC block converter <b>511</b>, a byte-bit converter <b>512</b>, a convolution encoder <b>513</b>, a symbol interleaver <b>514</b>, a symbol-byte converter <b>515</b>, and an SCCC block-MPH block converter <b>516</b>. The convolutional encoder <b>513</b> and the symbol interleaver <b>514</b> are virtually concatenated with the trellis encoding module in the post-processor in order to configure an SCCC block. More specifically, the RS frame portion-SCCC block converter <b>511</b> divides the RS frame portions, which are being inputted, into multiple SCCC blocks using the SIBL of Table 9 and Table 10 based upon the RS code mode, SCCC block mode, and SCCC outer code mode. Herein, the MPH frame encoder <b>301</b> may output only primary RS frame portions or both primary RS frame portions and secondary RS frame portions in accordance with the RS frame mode.
0241When the RS Frame mode is set to ‘00’, a portion of the primary RS Frame equal to the amount of data, which are to be SCCC outer encoded and mapped to 10 MPH blocks (B<b>1</b> to B<b>10</b>) of a data group, will be provided to the block processor <b>302</b>. When the SCCC block mode value is equal to ‘00’, then the primary RS frame portion will be split into 10 SCCC Blocks according to Table 9. Alternatively, when the SCCC block mode value is equal to ‘01’, then the primary RS frame will be split into 5 SCCC blocks according to Table 10.
0242When the RS frame mode value is equal to ‘01’, then the block processor <b>302</b> may receive two RS frame portions. The RS frame mode value of ‘01’ will not be used with the SCCC block mode value of ‘01’. The first portion from the primary RS frame will be SCCC-outer-encoded as SCCC Blocks SCB<b>3</b>, SCB<b>4</b>, SCB<b>5</b>, SCB<b>6</b>, SCB<b>7</b>, and SCB<b>8</b> by the block processor <b>302</b>. The SCCC Blocks SCB<b>3</b> and SCB<b>8</b> will be mapped to region B and the SCCC blocks SCB<b>4</b>, SCB<b>5</b>, SCB<b>6</b>, and SCB<b>7</b> shall be mapped to region A by the group formatter <b>303</b>. The second portion from the secondary RS frame will also be SCCC-outer-encoded, as SCB<b>1</b>, SCB<b>2</b>, SCB<b>9</b>, and SCB<b>10</b>, by the block processor <b>302</b>. The group formatter <b>303</b> will map the SCCC blocks SCB<b>1</b> and SCB<b>10</b> to region D as the MPH blocks B<b>1</b> and B<b>10</b>, respectively. Similarly, the SCCC blocks SCB<b>2</b> and SCB<b>9</b> will be mapped to region C as the MPH blocks B<b>2</b> and B<b>9</b>.
0243The byte-bit converter <b>512</b> identifies the mobile service data bytes of each SCCC block outputted from the RS frame portion-SCCC block converter <b>511</b> as data bits, which are then outputted to the convolution encoder <b>513</b>. The convolution encoder <b>513</b> performs one of 1/2-rate encoding and 1/4-rate encoding on the inputted mobile service data bits.
0244<figref idref="DRAWINGS">FIG. 25</figref> illustrates a detailed block diagram of the convolution encoder <b>513</b>. The convolution encoder <b>513</b> includes two delay units <b>521</b> and <b>523</b> and three adders <b>522</b>, <b>524</b>, and <b>525</b>. Herein, the convolution encoder <b>513</b> encodes an input data bit U and outputs the coded bit U to 5 bits (u<b>0</b> to u<b>4</b>). At this point, the input data bit U is directly outputted as uppermost bit u<b>0</b> and simultaneously encoded as lower bit u<b>1</b>u<b>2</b>u<b>3</b>u<b>4</b> and then outputted. More specifically, the input data bit U is directly outputted as the uppermost bit u<b>0</b> and simultaneously outputted to the first and third adders <b>522</b> and <b>525</b>.
0245The first adder <b>522</b> adds the input data bit U and the output bit of the first delay unit <b>521</b> and, then, outputs the added bit to the second delay unit <b>523</b>. Then, the data bit delayed by a pre-determined time (e.g., by 1 clock) in the second delay unit <b>523</b> is outputted as a lower bit u<b>1</b> and simultaneously fed-back to the first delay unit <b>521</b>. The first delay unit <b>521</b> delays the data bit fed-back from the second delay unit <b>523</b> by a pre-determined time (e.g., by 1 clock). Then, the first delay unit <b>521</b> outputs the delayed data bit as a lower bit u<b>2</b> and, at the same time, outputs the fed-back data to the first adder <b>522</b> and the second adder <b>524</b>. The second adder <b>524</b> adds the data bits outputted from the first and second delay units <b>521</b> and <b>523</b> and outputs the added data bits as a lower bit u<b>3</b>. The third adder <b>525</b> adds the input data bit U and the output of the second delay unit <b>523</b> and outputs the added data bit as a lower bit u<b>4</b>.
0246At this point, the first and second delay units <b>521</b> and <b>523</b> are reset to ‘0’, at the starting point of each SCCC block. The convolution encoder <b>513</b> of <figref idref="DRAWINGS">FIG. 25</figref> may be used as a 1/2-rate encoder or a 1/4-rate encoder. More specifically, when a portion of the output bit of the convolution encoder <b>513</b>, shown in <figref idref="DRAWINGS">FIG. 25</figref>, is selected and outputted, the convolution encoder <b>513</b> may be used as one of a 1/2-rate encoder and a 1/4-rate encoder. Table 11 below shown an example of output symbols of the convolution encoder <b>513</b>.
0247<tables id="TABLE-US-00011" num="00011"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="35pt" align="left" /><colspec colname="2" colwidth="28pt" align="left" /><colspec colname="3" colwidth="154pt" align="center" /><thead><row><entry namest="1" nameend="3" rowsep="1">TABLE 11</entry></row></thead><tbody valign="top"><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry /><entry /><entry>¼ rate</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="35pt" align="left" /><colspec colname="2" colwidth="28pt" align="left" /><colspec colname="3" colwidth="77pt" align="left" /><colspec colname="4" colwidth="77pt" align="left" /><tbody valign="top"><row><entry>Region</entry><entry>½ rate</entry><entry>SCCC block mode = ‘00’</entry><entry>SCCC block mode = ‘01’</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry>A, B</entry><entry>(u0, u1)</entry><entry>(u0, u2), (u1, u3)</entry><entry>(u0, u2), (u1, u4)</entry></row><row><entry>C, D</entry><entry /><entry>(u0, u1), (u3, u4)</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>
0248For example, at the 1/2-coding rate, 1 output symbol (i.e., u<b>0</b> and u<b>1</b> bits) may be selected and outputted. And, at the 1/4-coding rate, depending upon the SCCC block mode, 2 output symbols (i.e., 4 bits) may be selected and outputted. For example, when the SCCC block mode value is equal to ‘01’, and when an output symbol configured of u<b>0</b> and u<b>2</b> and another output symbol configured of u<b>1</b> and u<b>4</b> are selected and outputted, a 1/4-rate coding result may be obtained.
0249The mobile service data encoded at the coding rate of 1/2 or 1/4 by the convolution encoder <b>513</b> are outputted to the symbol interleaver <b>514</b>. The symbol interleaver <b>514</b> performs block interleaving, in symbol units, on the output data symbol of the convolution encoder <b>513</b>. More specifically, the symbol interleaver <b>514</b> is a type of block interleaver. Any interleaver performing structural rearrangement (or realignment) may be applied as the symbol interleaver <b>514</b> of the block processor. However, in the present invention, a variable length symbol interleaver that can be applied even when a plurality of lengths is provided for the symbol, so that its order may be rearranged, may also be used.
0250<figref idref="DRAWINGS">FIG. 26</figref> illustrates a symbol interleaver according to an embodiment of the present invention. Particularly, <figref idref="DRAWINGS">FIG. 26</figref> illustrates an example of the symbol interleaver when B=2112 and L=4096. Herein, B indicates a block length in symbols that are outputted for symbol interleaving from the convolution encoder <b>513</b>. And, L represents a block length in symbols that are actually interleaved by the symbol interleaver <b>514</b>. At this point, the block length in symbols B inputted to the symbol interleaver <b>514</b> is equivalent to 4×SOBL . More specifically, since one symbol is configured of 2 bits, the value of B may be set to be equal to 4×SOBL.
0251In the present invention, when performing the symbol-interleaving process, the conditions of L=2<sup>m </sup>(wherein m is an integer) and of L≧B should be satisfied. If there is a difference in value between B and L, (L−B) number of null (or dummy) symbols is added, thereby creating an interleaving pattern, as shown in P′(i) of <figref idref="DRAWINGS">FIG. 26</figref>. Therefore, B becomes a block size of the actual symbols that are inputted to the symbol interleaver <b>514</b> in order to be interleaved. L becomes an interleaving unit when the interleaving process is performed by an interleaving pattern created from the symbol interleaver <b>514</b>.
0252Equation 6 shown below describes the process of sequentially receiving B number of symbols, the order of which is to be rearranged, and obtaining an L value satisfying the conditions of L=2<sup>m </sup>(wherein m is an integer) and of L≧B, thereby creating the interleaving so as to realign (or rearrange) the symbol order. <br />In relation to all places, wherein 0≦i≦B−1,<br />P′(i)={89×i×(i+1)/2} mod L<br />Herein, L≧B ,L=2<sup>m</sup>, wherein m is an integer. Equation 6
0253As shown in P′(i) of <figref idref="DRAWINGS">FIG. 26</figref>, the order of B number of input symbols and (L−B) number of null symbols is rearranged by using the above-mentioned Equation 6. Then, as shown in P(i) of <figref idref="DRAWINGS">FIG. 26</figref>, the null byte places are removed, so as to rearrange the order. Starting with the lowest value of i, the P(i) are shifted to the left in order to fill the empty entry locations. Thereafter, the symbols of the aligned interleaving pattern P(i) are outputted to the symbol-byte converter <b>515</b> in order. Herein, the symbol-byte converter <b>515</b> converts to bytes the mobile service data symbols, having the rearranging of the symbol order completed and then outputted in accordance with the rearranged order, and thereafter outputs the converted bytes to the SCCC block-MPH block converter <b>516</b>. The SCCC block-MPH block converter <b>516</b> converts the symbol-interleaved SCCC blocks to MPH blocks, which are then outputted to the group formatter <b>303</b>.
0254If the SCCC block mode value is equal to ‘00’, the SCCC block is mapped at a one-to-one (1:1) correspondence with each MPH block within the data group. In another example, if the SCCC block mode value is equal to ‘01’, each SCCC block is mapped with two MPH blocks within the data group. For example, the SCCC block SCB<b>1</b> is mapped with (B<b>1</b>, B<b>6</b>), the SCCC block SCB<b>2</b> is mapped with (B<b>2</b>, B<b>7</b>), the SCCC block SCB<b>3</b> is mapped with (B<b>3</b>, B<b>8</b>), the SCCC block SCB<b>4</b> is mapped with (B<b>4</b>, B<b>9</b>), and the SCCC block SCB<b>5</b> is mapped with (B<b>5</b>, B<b>10</b>). The MPH block that is outputted from the SCCC block-MPH block converter <b>516</b> is configured of mobile service data and FEC redundancy. In the present invention, the mobile service data as well as the FEC redundancy of the MPH block will be collectively considered as mobile service data.
0000Group Formatter
0255The group formatter <b>303</b> inserts data of MPH blocks outputted from the block processor <b>302</b> to the corresponding MPH blocks within the data group, which is formed in accordance with a pre-defined rule. Also, in association with the data-deinterleaving process, the group formatter <b>303</b> inserts various place holders (or known data place holders) in the corresponding region within the data group. More specifically, apart from the encoded mobile service data outputted from the block processor <b>302</b>, the group formatter <b>303</b> also inserts MPEG header place holders, non-systematic RS parity place holders, main service data place holders, which are associated with the data deinterleaving in a later process, as shown in <figref idref="DRAWINGS">FIG. 5</figref>.
0256Herein, the main service data place holders are inserted because the mobile service data bytes and the main service data bytes are alternately mixed with one another in regions B to D based upon the input of the data deinterleaver, as shown in <figref idref="DRAWINGS">FIG. 5</figref>. For example, based upon the data outputted after data deinterleaving, the place holder for the MPEG header may be allocated at the very beginning of each packet. Also, in order to configure an intended group format, dummy bytes may also be inserted. Furthermore, the group formatter <b>303</b> inserts place holders for initializing the trellis encoding module <b>256</b> in the corresponding regions. For example, the initialization data place holders may be inserted in the beginning of the known data sequence. Additionally, the group formatter <b>303</b> may also insert signaling information, which are encoded and outputted from the signaling encoder <b>304</b>, in corresponding regions within the data group. At this point, reference may be made to the signaling information when the group formatter <b>303</b> inserts each data type and respective place holders in the data group. The process of encoding the signaling information and inserting the encoded signaling information to the data group will be described in detail in a later process.
0257After inserting each data type and respective place holders in the data group, the group formatter <b>303</b> may deinterleave the data and respective place holders, which have been inserted in the data group, as an inverse process of the data interleaver, thereby outputting the deinterleaved data and respective place holders to the packet formatter <b>305</b>. More specifically, when the data and respective place holders within the data group, which is configured (or structured) as shown in <figref idref="DRAWINGS">FIG. 5</figref>, are deinterleaved by the group formatter <b>303</b> and outputted to the packet formatter <b>305</b>, the structure of the data group may be identical to the structure shown in <figref idref="DRAWINGS">FIG. 7</figref>. In order to do so, the group formatter <b>303</b> may include a group format organizer <b>527</b>, and a data deinterleaver <b>529</b>, as shown in <figref idref="DRAWINGS">FIG. 27</figref>. The group format organizer <b>527</b> inserts data and respective place holders in the corresponding regions within the data group, as described above. And, the data deinterleaver <b>529</b> deinterleaves the inserted data and respective place holders as an inverse process of the data interleaver.
0258The packet formatter <b>305</b> removes the main service data place holders and the RS parity place holders that were allocated for the deinterleaving process from the deinterleaved data being inputted. Then, the packet formatter <b>305</b> groups the remaining portion and inserts the 3-byte MPEG header place holder in an MPEG header having a null packet PID (or an unused PID from the main service data packet). Furthermore, the packet formatter <b>305</b> adds a synchronization data byte at the beginning of each 187-byte data packet. Also, when the group formatter <b>303</b> inserts known data place holders, the packet formatter <b>303</b> may insert actual known data in the known data place holders, or may directly output the known data place holders without any modification in order to make replacement insertion in a later process. Thereafter, the packet formatter <b>305</b> identifies the data within the packet-formatted data group, as described above, as a 188-byte unit mobile service data packet (i.e., MPEG TS packet), which is then provided to the packet multiplexer <b>240</b>.
0259Based upon the control of the control unit <b>200</b>, the packet multiplexer <b>240</b> multiplexes the data group packet-formatted and outputted from the packet formatter <b>306</b> and the main service data packet outputted from the packet jitter mitigator <b>220</b>. Then, the packet multiplexer <b>240</b> outputs the multiplexed data packets to the data randomizer <b>251</b> of the post-processor <b>250</b>. More specifically, the control unit <b>200</b> controls the time-multiplexing of the packet multiplexer <b>240</b>. If the packet multiplexer <b>240</b> receives 118 mobile service data packets from the packet formatter <b>305</b>, 37 mobile service data packets are placed before a place for inserting VSB field synchronization. Then, the remaining 81 mobile service data packets are placed after the place for inserting VSB field synchronization. The multiplexing method may be adjusted by diverse variables of the system design. The multiplexing method and multiplexing rule of the packet multiplexer <b>240</b> will be described in more detail in a later process.
0260Also, since a data group including mobile service data in-between the data bytes of the main service data is multiplexed (or allocated) during the packet multiplexing process, the shifting of the chronological position (or place) of the main service data packet becomes relative. Also, a system object decoder (i.e., MPEG decoder) for processing the main service data of the receiving system, receives and decodes only the main service data and recognizes the mobile service data packet as a null data packet.
0261Therefore, when the system object decoder of the receiving system receives a main service data packet that is multiplexed with the data group, a packet jitter occurs.
0262At this point, since a multiple-level buffer for the video data exists in the system object decoder and the size of the buffer is relatively large, the packet jitter generated from the packet multiplexer <b>240</b> does not cause any serious problem in case of the video data. However, since the size of the buffer for the audio data in the object decoder is relatively small, the packet jitter may cause considerable problem. More specifically, due to the packet jitter, an overflow or underflow may occur in the buffer for the main service data of the receiving system (e.g., the buffer for the audio data). Therefore, the packet jitter mitigator <b>220</b> re-adjusts the relative position of the main service data packet so that the overflow or underflow does not occur in the system object decoder.
0263In the present invention, examples of repositioning places for the audio data packets within the main service data in order to minimize the influence on the operations of the audio buffer will be described in detail. The packet jitter mitigator <b>220</b> repositions the audio data packets in the main service data section so that the audio data packets of the main service data can be as equally and uniformly aligned and positioned as possible. Additionally, when the positions of the main service data packets are relatively re-adjusted, associated program clock reference (PCR) values may also be modified accordingly. The PCR value corresponds to a time reference value for synchronizing the time of the MPEG decoder. Herein, the PCR value is inserted in a specific region of a TS packet and then transmitted.
0264In the example of the present invention, the packet jitter mitigator <b>220</b> also performs the operation of modifying the PCR value. The output of the packet jitter mitigator <b>220</b> is inputted to the packet multiplexer <b>240</b>. As described above, the packet multiplexer <b>240</b> multiplexes the main service data packet outputted from the packet jitter mitigator <b>220</b> with the mobile service data packet outputted from the pre-processor <b>230</b> into a burst structure in accordance with a pre-determined multiplexing rule. Then, the packet multiplexer <b>240</b> outputs the multiplexed data packets to the data randomizer <b>251</b> of the post-processor <b>250</b>.
0265If the inputted data correspond to the main service data packet, the data randomizer <b>251</b> performs the same randomizing process as that of the conventional randomizer. More specifically, the synchronization byte within the main service data packet is deleted. Then, the remaining 187 data bytes are randomized by using a pseudo random byte generated from the data randomizer <b>251</b>. Thereafter, the randomized data are outputted to the RS encoder/non-systematic RS encoder <b>252</b>.
0266On the other hand, if the inputted data correspond to the mobile service data packet, the data randomizer <b>251</b> may randomize only a portion of the data packet. For example, if it is assumed that a randomizing process has already been performed in advance on the mobile service data packet by the pre-processor <b>230</b>, the data randomizer <b>251</b> deletes the synchronization byte from the 4-byte MPEG header included in the mobile service data packet and, then, performs the randomizing process only on the remaining 3 data bytes of the MPEG header. Thereafter, the randomized data bytes are outputted to the RS encoder/non-systematic RS encoder <b>252</b>. More specifically, the randomizing process is not performed on the remaining portion of the mobile service data excluding the MPEG header. In other words, the remaining portion of the mobile service data packet is directly outputted to the RS encoder/non-systematic RS encoder <b>252</b> without being randomized. Also, the data randomizer <b>251</b> may or may not perform a randomizing process on the known data (or known data place holders) and the initialization data place holders included in the mobile service data packet.
0267The RS encoder/non-systematic RS encoder <b>252</b> performs an RS encoding process on the data being randomized by the data randomizer <b>251</b> or on the data bypassing the data randomizer <b>251</b>, so as to add 20 bytes of RS parity data. Thereafter, the processed data are outputted to the data interleaver <b>253</b>. Herein, if the inputted data correspond to the main service data packet, the RS encoder/non-systematic RS encoder <b>252</b> performs the same systematic RS encoding process as that of the conventional broadcasting system, thereby adding the 20-byte RS parity data at the end of the 187-byte data. Alternatively, if the inputted data correspond to the mobile service data packet, the RS encoder/non-systematic RS encoder <b>252</b> performs a non-systematic RS encoding process. At this point, the 20-byte RS parity data obtained from the non-systematic RS encoding process are inserted in a pre-decided parity byte place within the mobile service data packet.
0268The data interleaver <b>253</b> corresponds to a byte unit convolutional interleaver. The output of the data interleaver <b>253</b> is inputted to the parity replacer <b>254</b> and to the non-systematic RS encoder <b>255</b>. Meanwhile, a process of initializing a memory within the trellis encoding module <b>256</b> is primarily required in order to decide the output data of the trellis encoding module <b>256</b>, which is located after the parity replacer <b>254</b>, as the known data pre-defined according to an agreement between the receiving system and the transmitting system. More specifically, the memory of the trellis encoding module <b>256</b> should first be initialized before the received known data sequence is trellis-encoded. At this point, the beginning portion of the known data sequence that is received corresponds to the initialization data place holder and not to the actual known data. Herein, the initialization data place holder has been included in the data by the group formatter within the pre-processor <b>230</b> in an earlier process. Therefore, the process of generating initialization data and replacing the initialization data place holder of the corresponding memory with the generated initialization data are required to be performed immediately before the inputted known data sequence is trellis-encoded.
0269Additionally, a value of the trellis memory initialization data is decided and generated based upon a memory status of the trellis encoding module <b>256</b>. Further, due to the newly replaced initialization data, a process of newly calculating the RS parity and replacing the RS parity, which is outputted from the data interleaver <b>253</b>, with the newly calculated RS parity is required. Therefore, the non-systematic RS encoder <b>255</b> receives the mobile service data packet including the initialization data place holders, which are to be replaced with the actual initialization data, from the data interleaver <b>253</b> and also receives the initialization data from the trellis encoding module <b>256</b>.
0270Among the inputted mobile service data packet, the initialization data place holders are replaced with the initialization data, and the RS parity data that are added to the mobile service data packet are removed and processed with non-systematic RS encoding. Thereafter, the new RS parity obtained by performing the non-systematic RS encoding process is outputted to the parity replacer <b>255</b>. Accordingly, the parity replacer <b>255</b> selects the output of the data interleaver <b>253</b> as the data within the mobile service data packet, and the parity replacer <b>255</b> selects the output of the non-systematic RS encoder <b>255</b> as the RS parity. The selected data are then outputted to the trellis encoding module <b>256</b>.
0271Meanwhile, if the main service data packet is inputted or if the mobile service data packet, which does not include any initialization data place holders that are to be replaced, is inputted, the parity replacer <b>254</b> selects the data and RS parity that are outputted from the data interleaver <b>253</b>. Then, the parity replacer <b>254</b> directly outputs the selected data to the trellis encoding module <b>256</b> without any modification. The trellis encoding module <b>256</b> converts the byte-unit data to symbol units and performs a 12-way interleaving process so as to trellis-encode the received data. Thereafter, the processed data are outputted to the synchronization multiplexer <b>260</b>.
0272<figref idref="DRAWINGS">FIG. 28</figref> illustrates a detailed diagram of one of 12 trellis encoders included in the trellis encoding module <b>256</b>. Herein, the trellis encoder includes first and second multiplexers <b>531</b> and <b>541</b>, first and second adders <b>532</b> and <b>542</b>, and first to third memories <b>533</b>, <b>542</b>, and <b>544</b>. More specifically, the first to third memories <b>533</b>, <b>542</b>, and <b>544</b> are initialized by a set of trellis initialization data inserted in an initialization data place holder by the parity replacer <b>254</b> and, then, outputted. More specifically, when the first two 2-bit symbols, which are converted from each trellis initialization data byte, are inputted, the input bits of the trellis encoder will be replaced by the memory values of the trellis encoder, as shown in <figref idref="DRAWINGS">FIG. 28</figref>.
0273Since 2 symbols (i.e., 4 bits) are required for trellis initialization, the last 2 symbols (i.e., 4 bits) from the trellis initialization bytes are not used for trellis initialization and are considered as a symbol from a known data byte and processed accordingly. When the trellis encoder is in the initialization mode, the input comes from an internal trellis status (or state) and not from the parity replacer <b>254</b>. When the trellis encoder is in the normal mode, the input symbol provided from the parity replacer <b>254</b> will be processed. The trellis encoder provides the converted (or modified) input data for trellis initialization to the non-systematic RS encoder <b>255</b>.
0274More specifically, when a selection signal designates a normal mode, the first multiplexer <b>531</b> selects an upper bit X<b>2</b> of the input symbol. And, when a selection signal designates an initialization mode, the first multiplexer <b>531</b> selects the output of the first memory <b>533</b> and outputs the selected output data to the first adder <b>532</b>. The first adder <b>532</b> adds the output of the first multiplexer <b>531</b> and the output of the first memory <b>533</b>, thereby outputting the added result to the first memory <b>533</b> and, at the same time, as a most significant (or uppermost) bit Z<b>2</b>. The first memory <b>533</b> delays the output data of the first adder <b>532</b> by 1 clock, thereby outputting the delayed data to the first multiplexer <b>531</b> and the first adder <b>532</b>.
0275Meanwhile, when a selection signal designates a normal mode, the second multiplexer <b>541</b> selects a lower bit X<b>1</b> of the input symbol. And, when a selection signal designates an initialization mode, the second multiplexer <b>541</b> selects the output of the second memory <b>542</b>, thereby outputting the selected result to the second adder <b>543</b> and, at the same time, as a lower bit Z<b>1</b>. The second adder <b>543</b> adds the output of the second multiplexer <b>541</b> and the output of the second memory <b>542</b>, thereby outputting the added result to the third memory <b>544</b>. The third memory <b>544</b> delays the output data of the second adder <b>543</b> by 1 clock, thereby outputting the delayed data to the second memory <b>542</b> and, at the same time, as a least significant (or lowermost) bit Z<b>0</b>. The second memory <b>542</b> delays the output data of the third memory <b>544</b> by 1 clock, thereby outputting the delayed data to the second adder <b>543</b> and the second multiplexer <b>541</b>.
0276The synchronization multiplexer <b>260</b> inserts a field synchronization signal and a segment synchronization signal to the data outputted from the trellis encoding module <b>256</b> and, then, outputs the processed data to the pilot inserter <b>271</b> of the transmission unit <b>270</b>. Herein, the data having a pilot inserted therein by the pilot inserter <b>271</b> are modulated by the modulator <b>272</b> in accordance with a pre-determined modulating method (e.g., a VSB method). Thereafter, the modulated data are transmitted to each receiving system though the radio frequency (RF) up-converter <b>273</b>.
0000Multiplexing Method of Packet Multiplexer <b>240</b>
0277Data of the error correction encoded and 1/H-rate encoded primary RS frame (i.e., when the RS frame mode value is equal to ‘00’) or primary/secondary RS frame (i.e., when the RS frame mode value is equal to ‘01’), are divided into a plurality of data groups by the group formatter <b>303</b>. Then, the divided data portions are assigned to at least one of regions A to D of each data group or to an MPH block among the MPH blocks B<b>1</b> to B<b>10</b>, thereby being deinterleaved. Then, the deinterleaved data group passes through the packet formatter <b>305</b>, thereby being multiplexed with the main service data by the packet multiplexer <b>240</b> based upon a de-decided multiplexing rule. The packet multiplexer <b>240</b> multiplexes a plurality of consecutive data groups, so that the data groups are assigned to be spaced as far apart from one another as possible within the sub-frame. For example, when it is assumed that 3 data groups are assigned to a sub-frame, the data groups are assigned to a 1<sup>st </sup>slot (Slot #<b>0</b>), a 5<sup>th </sup>slot (Slot #<b>4</b>), and a 9<sup>th </sup>slot (Slot #<b>8</b>) in the sub-frame, respectively.
0278As described-above, in the assignment of the plurality of consecutive data groups, a plurality of parades are multiplexed and outputted so as to be spaced as far apart from one another as possible within a sub-MPH frame. For example, the method of assigning data groups and the method of assigning parades may be identically applied to all sub-frames for each MPH frame or differently applied to each MPH frame.
0279<figref idref="DRAWINGS">FIG. 10</figref> illustrates an example of a plurality of data groups included in a single parade, wherein the number of data groups included in a sub-frame is equal to ‘3’, and wherein the data groups are assigned to an MPH frame by the packet multiplexer <b>240</b>. Referring to <figref idref="DRAWINGS">FIG. 10</figref>, 3 data groups are sequentially assigned to a sub-frame at a cycle period of 4 slots. Accordingly, when this process is equally performed in the 5 sub-frames included in the corresponding MPH frame, 15 data groups are assigned to a single MPH frame. Herein, the 15 data groups correspond to data groups included in a parade.
0280When data groups of a parade are assigned as shown in <figref idref="DRAWINGS">FIG. 10</figref>, the packet multiplexer <b>240</b> may either assign main service data to each data group, or assign data groups corresponding to different parades between each data group. More specifically, the packet multiplexer <b>240</b> may assign data groups corresponding to multiple parades to one MPH frame. Basically, the method of assigning data groups corresponding to multiple parades is very similar to the method of assigning data groups corresponding to a single parade. In other words, the packet multiplexer <b>240</b> may assign data groups included in other parades to an MPH frame according to a cycle period of 4 slots. At this point, data groups of a different parade may be sequentially assigned to the respective slots in a circular method. Herein, the data groups are assigned to slots starting from the ones to which data groups of the previous parade have not yet been assigned. For example, when it is assumed that data groups corresponding to a parade are assigned as shown in <figref idref="DRAWINGS">FIG. 10</figref>, data groups corresponding to the next parade may be assigned to a sub-frame starting either from the 12<sup>th </sup>slot of a sub-frame.
0281<figref idref="DRAWINGS">FIG. 11</figref> illustrates an example of assigning and transmitting 3 parades (Parade #<b>0</b>, Parade #<b>1</b>, and Parade #<b>2</b>) to an MPH frame. For example, when the 1<sup>st </sup>parade (Parade #<b>0</b>) includes 3 data groups for each sub-frame, the packet multiplexer <b>240</b> may obtain the positions of each data groups within the sub-frames by substituting values ‘0’ to ‘2’ for i in Equation 1. More specifically, the data groups of the 1<sup>st </sup>parade (Parade #<b>0</b>) are sequentially assigned to the 1<sup>st</sup>, 5<sup>th</sup>, and 9<sup>th </sup>slots (Slot #<b>0</b>, Slot #<b>4</b>, and Slot #<b>8</b>) within the sub-frame. Also, when the 2<sup>nd </sup>parade includes 2 data groups for each sub-frame, the packet multiplexer <b>240</b> may obtain the positions of each data groups within the sub-frames by substituting values ‘3’ and ‘4’ for i in Equation 1. More specifically, the data groups of the 2<sup>nd </sup>parade (Parade #<b>1</b>) are sequentially assigned to the 2<sup>nd </sup>and 12<sup>th </sup>slots (Slot #<b>3</b> and Slot #<b>11</b>) within the sub-frame. Finally, when the 3<sup>rd </sup>parade includes 2 data groups for each sub-frame, the packet multiplexer <b>240</b> may obtain the positions of each data groups within the sub-frames by substituting values ‘5’ and ‘6’ for i in Equation 1. More specifically, the data groups of the 3<sup>rd </sup>parade (Parade #<b>2</b>) are sequentially assigned and outputted to the 7<sup>th </sup>and 11<sup>th </sup>slots (Slot #<b>6</b> and Slot #<b>10</b>) within the sub-frame.
0282As described above, the packet multiplexer <b>240</b> may multiplex and output data groups of multiple parades to a single MPH frame, and, in each sub-frame, the multiplexing process of the data groups may be performed serially with a group space of 4 slots from left to right. Therefore, a number of groups of one parade per sub-frame (NOG) may correspond to any one integer from ‘1’ to ‘8’. Herein, since one MPH frame includes 5 sub-frames, the total number of data groups within a parade that can be allocated to an MPH frame may correspond to any one multiple of ‘5’ ranging from ‘5’ to ‘40’.
0000Processing Signaling Information
0283The present invention assigns signaling information areas for inserting signaling information to some areas within each data group. <figref idref="DRAWINGS">FIG. 29</figref> illustrates an example of assigning signaling information areas for inserting signaling information starting from the 1<sup>st </sup>segment of the 4<sup>th </sup>MPH block (B<b>4</b>) to a portion of the 2<sup>nd </sup>segment. More specifically, 276(=207+69) bytes of the 4<sup>th </sup>MPH block (B<b>4</b>) in each data group are assigned as the signaling information area. In other words, the signaling information area consists of 207 bytes of the 1<sup>st </sup>segment and the first 69 bytes of the 2<sup>nd </sup>segment of the 4<sup>th </sup>MPH block (B<b>4</b>). For example, the 1<sup>st </sup>segment of the 4<sup>th </sup>MPH block (B<b>4</b>) corresponds to the 17<sup>th </sup>or 173<sup>rd </sup>segment of a VSB field. The signaling information that is to be inserted in the signaling information area is FEC-encoded by the signaling encoder <b>304</b>, thereby inputted to the group formatter <b>303</b>.
0284The group formatter <b>303</b> inserts the signaling information, which is FEC-encoded and outputted by the signaling encoder <b>304</b>, in the signaling information area within the data group. Herein, the signaling information may be identified by two different types of signaling channels: a transmission parameter channel (TPC) and a fast information channel (FIC). Herein, the TPC information corresponds to signaling information including transmission parameters, such as RS frame-associated information, SCCC-associated information, and MPH frame-associated information. However, the signaling information presented herein is merely exemplary. And, since the adding or deleting of signaling information included in the TPC may be easily adjusted and modified by one skilled in the art, the present invention will, therefore, not be limited to the examples set forth herein. Furthermore, the FIC is provided to enable a fast service acquisition of data receivers, and the FIC includes cross layer information between the physical layer and the upper layer(s).
0285<figref idref="DRAWINGS">FIG. 30</figref> illustrates a detailed block diagram of the signaling encoder <b>304</b> according to the present invention. Referring to <figref idref="DRAWINGS">FIG. 30</figref>, the signaling encoder <b>304</b> includes a TPC encoder <b>561</b>, an FIC encoder <b>562</b>, a block interleaver <b>563</b>, a multiplexer <b>564</b>, a signaling randomizer <b>565</b>, and a PCCC encoder <b>566</b>. The TPC encoder <b>561</b> receives 10-bytes of TPC data and performs (18,10)-RS encoding on the 10-bytes of TPC data, thereby adding 8 bytes of parity data to the 10 bytes of TPC data. The 18 bytes of RS-encoded TPC data are outputted to the multiplexer <b>564</b>. The FIC encoder <b>562</b> receives 37-bytes of FIC data and performs (51,37)-RS encoding on the 37-bytes of FIC data, thereby adding 14 bytes of parity data to the 37 bytes of FIC data. Thereafter, the 51 bytes of RS-encoded FIC data are inputted to the block interleaver <b>563</b>, thereby being interleaved in predetermined block units.
0286Herein, the block interleaver <b>563</b> corresponds to a variable length block interleaver. The block interleaver <b>563</b> interleaves the FIC data within each sub-frame in TNoG(column)×51 (row) block units and then outputs the interleaved data to the multiplexer <b>564</b>. Herein, the TNoG corresponds to the total number of data groups being assigned to all sub-frames within an MPH frame. The block interleaver <b>563</b> is synchronized with the first set of FIC data in each sub-frame. The block interleaver <b>563</b> writes 51 bytes of incoming (or inputted) RS codewords in a row direction (i.e., row-by-row) and left-to-right and up-to-down directions and reads 51 bytes of RS codewords in a column direction (i.e., column-by-column) and left-to-right and up-to-down directions, thereby outputting the RS codewords.
0287The multiplexer <b>564</b> multiplexes the RS-encoded TPC data from the TPC encoder <b>561</b> and the block-interleaved FIC data from the block interleaver <b>563</b> along a time axis. Then, the multiplexer <b>564</b> outputs 69 bytes of the multiplexed data to the signaling randomizer <b>565</b>. The signaling randomizer <b>565</b> randomizes the multiplexed data and outputs the randomized data to the PCCC encoder <b>566</b>. The signaling randomizer <b>565</b> may use the same generator polynomial of the randomizer used for mobile service data. Also, initialization occurs in each data group. The PCCC encoder <b>566</b> corresponds to an inner encoder performing PCCC-encoding on the randomized data (i.e., signaling information data). The PCCC encoder <b>566</b> may include 6 even component encoders and 6 odd component encoders.
0288<figref idref="DRAWINGS">FIG. 31</figref> illustrates an example of a syntax structure of TPC data being inputted to the TPC encoder <b>561</b>. The TPC data are inserted in the signaling information area of each data group and then transmitted. The TPC data may include a sub-frame_number field, a slot_number field, a parade_id field, a starting_group_number (SGN) field, a number_of_groups (NoG) field, a parade_repetition_cycle (PRC) field, an RS_frame_mode field, an RS_code_mode_primary field, an RS_code_mode_secondary field, an SCCC_block_mode field, an SCCC_outer_code_mode_A field, an SCCC_outer_code_mode_B field, an SCCC_outer_code_mode_C field, an SCCC_outer_code_mode_D field, an FIC_version field, a parade_continuity_counter field, and a TNoG field.
0289The Sub-Frame_number field corresponds to the current Sub-Frame number within the MPH frame, which is transmitted for MPH frame synchronization. The value of the Sub-Frame_number field may range from 0 to 4. The Slot_number field indicates the current slot number within the sub-frame, which is transmitted for MPH frame synchronization. Also, the value of the Sub-Frame_number field may range from 0 to 15. The Parade_id field identifies the parade to which this group belongs. The value of this field may be any 7-bit value. Each parade in a MPH transmission shall have a unique Parade_id field.
0290Communication of the Parade_id between the physical layer and the management layer may be performed by means of an Ensemble_id field formed by adding one bit to the left of the Parade_id field. If the Ensemble_id field is used for the primary Ensemble delivered through this parade, the added MSB shall be equal to ‘0’. Otherwise, if the Ensemble_id field is used for the secondary ensemble, the added MSB shall be equal to ‘1’. Assignment of the Parade_id field values may occur at a convenient level of the system, usually in the management layer. The starting_group_number (SGN) field shall be the first Slot_number for a parade to which this group belongs, as determined by Equation 1 (i.e., after the Slot numbers for all preceding parades have been calculated). The SGN and NoG shall be used according to Equation 1 to obtain the slot numbers to be allocated to a parade within the sub-frame.
0291The number_of_Groups (NoG) field shall be the number of groups in a sub-frame assigned to the parade to which this group belongs, minus 1, e.g., NoG=0 implies that one group is allocated (or assigned) to this parade in a sub-frame. The value of NoG may range from 0 to 7. This limits the amount of data that a parade may take from the main (legacy) service data, and consequently the maximum data that can be carried by one parade. The slot numbers assigned to the corresponding Parade can be calculated from SGN and NoG, using Equation 1. By taking each parade in sequence, the specific slots for each parade will be determined, and consequently the SGN for each succeeding parade. For example, if for a specific parade SGN=3 and NoG=3 (010b for 3-bit field of NoG), substituting i=3, 4, and 5 in Equation 1 provides slot numbers <b>12</b>, <b>2</b>, and <b>6</b>. The Parade_repetition_cycle (PRC) field corresponds to the cycle time over which the parade is transmitted, minus 1, specified in units of MPH frames, as described in Table 12.
0292<tables id="TABLE-US-00012" num="00012"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="35pt" align="center" /><colspec colname="2" colwidth="182pt" align="left" /><thead><row><entry namest="1" nameend="2" rowsep="1">TABLE 12</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>PRC</entry><entry>Description</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>000</entry><entry>This parade shall be transmitted once every MPH frame.</entry></row><row><entry>001</entry><entry>This parade shall be transmitted once every 2 MPH frames.</entry></row><row><entry>010</entry><entry>This parade shall be transmitted once every 3 MPH frames.</entry></row><row><entry>011</entry><entry>This parade shall be transmitted once every 4 MPH frames.</entry></row><row><entry>100</entry><entry>This parade shall be transmitted once every 5 MPH frames.</entry></row><row><entry>101</entry><entry>This parade shall be transmitted once every 6 MPH frames.</entry></row><row><entry>110</entry><entry>This parade shall be transmitted once every 7 MPH frames.</entry></row><row><entry>111</entry><entry>Reserved</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>
0293The RS_Frame_mode field shall be as defined in Table 1. The RS_code_mode_primary field shall be the RS code mode for the primary RS frame. Herein, the RS code mode is defined in Table 6. The RS_code_mode_secondary field shall be the RS code mode for the secondary RS frame. Herein, the RS code mode is defined in Table 6. The SCCC_Block_mode field shall be as defined in Table 7. The SCCC_outer_code_mode_A field corresponds to the SCCC outer code mode for Region A. The SCCC outer code mode is defined in Table 8. The SCCC_outer_code_mode_B field corresponds to the SCCC outer code mode for Region B. The SCCC_outer_code_mode_C field corresponds be the SCCC outer code mode for Region C. And, the SCCC_outer_code_mode_D field corresponds to the SCCC outer code mode for Region D.
0294The FIC_version field may be supplied by the management layer (which also supplies the FIC data). The Parade_continuity_counter field counter may increase from 0 to 15 and then repeat its cycle. This counter shall increment by 1 every (PRC+1) MPH frames. For example, as shown in Table 12, PRC=011 (decimal 3) implies that Parade_continuity_counter increases every fourth MPH frame. The TNoG field may be identical for all sub-frames in an MPH Frame. However, the information included in the TPC data presented herein is merely exemplary. And, since the adding or deleting of information included in the TPC may be easily adjusted and modified by one skilled in the art, the present invention will, therefore, not be limited to the examples set forth herein.
0295Since the TPC parameters (excluding the Sub-Frame_number field and the Slot_number field) for each parade do not change their values during an MPH frame, the same information is repeatedly transmitted through all MPH groups belonging to the corresponding parade during an MPH frame. This allows very robust and reliable reception of the TPC data. Because the Sub-Frame_number and the Slot_number are increasing counter values, they also are robust due to the transmission of regularly expected values.
0296Furthermore, the FIC information is provided to enable a fast service acquisition of data receivers, and the FIC information includes cross layer information between the physical layer and the upper layer(s).
0297<figref idref="DRAWINGS">FIG. 32</figref> illustrates an example of a transmission scenario of the TPC data and the FIC data. The values of the Sub-Frame_number field, Slot_number field, Parade_id field, Parade_repetition_cycle field, and Parade_continuity_counter field may corresponds to the current MPH frame throughout the 5 sub-frames within a specific MPH frame. Some of TPC parameters and FIC data are signaled in advance. The SGN, NoG and all FEC modes may have values corresponding to the current MPH frame in the first two sub-frames. The SGN, NoG and all FEC modes may have values corresponding to the frame in which the parade next appears throughout the 3<sup>rd</sup>, 4<sup>th </sup>and 5<sup>th </sup>sub-frames of the current MPH frame. This enables the MPH receivers to receive (or acquire) the transmission parameters in advance very reliably.
0298For example, when Parade_repetition_cycle=‘000’, the values of the 3<sup>rd</sup>, 4<sup>th</sup>, and 5<sup>th </sup>sub-frames of the current MPH frame correspond to the next MPH frame. Also, when Parade_repetition_cycle=‘011’, the values of the 3<sup>rd</sup>, 4<sup>th</sup>, and 5<sup>th </sup>sub-frames of the current MPH frame correspond to the 4<sup>th </sup>MPH frame and beyond. The FIC_version field and the FIC_data field may have values that apply to the current MPH Frame during the 1<sup>st </sup>sub-frame and the 2<sup>nd </sup>sub-frame, and they shall have values corresponding to the MPH frame immediately following the current MPH frame during the 3<sup>rd</sup>, 4<sup>th</sup>, and 5<sup>th </sup>sub-frames of the current MPH frame.
0299Meanwhile, the receiving system may turn the power on only during a slot to which the data group of the designated (or desired) parade is assigned, and the receiving system may turn the power off during the remaining slots, thereby reducing power consumption of the receiving system. Such characteristic is particularly useful in portable or mobile receivers, which require low power consumption. For example, it is assumed that data groups of a 1<sup>st </sup>parade with NOG=3, a 2<sup>nd </sup>parade with NOG=2, and a 3<sup>rd </sup>parade with NOG=3 are assigned to one MPH frame, as shown in <figref idref="DRAWINGS">FIG. 33</figref>. It is also assumed that the user has selected a mobile service included in the 1<sup>st </sup>parade using the keypad provided on the remote controller or terminal. In this case, the receiving system turns the power on only during a slot that data groups of the 1<sup>st </sup>parade is assigned, as shown in <figref idref="DRAWINGS">FIG. 33</figref>, and turns the power off during the remaining slots, thereby reducing power consumption, as described above. At this point, the power is required to be turned on briefly earlier than the slot to which the actual designated data group is assigned (or allocated). This is to enable the tuner or demodulator to converge in advance.
0000Assignment of Known Data (or Training Signal)
0300In addition to the payload data, the MPH transmission system inserts long and regularly spaced training sequences into each group. The regularity is an especially useful feature since it provides the greatest possible benefit for a given number of training symbols in high-Doppler rate conditions. The length of the training sequences is also chosen to allow fast acquisition of the channel during bursted power-saving operation of the demodulator. Each group contains 6 training sequences. The training sequences are specified before trellis-encoding. The training sequences are then trellis-encoded and these trellis-encoded sequences also are known sequences. This is because the trellis encoder memories are initialized to pre-determined values at the beginning of each sequence. The form of the 6 training sequences at the byte level (before trellis-encoding) is shown in <figref idref="DRAWINGS">FIG. 34</figref>. This is the arrangement of the training sequence at the group formatter <b>303</b>.
0301The 1<sup>st </sup>training sequence is located at the last 2 segments of the 3<sup>rd </sup>MPH block (B<b>3</b>). The 2<sup>nd </sup>training sequence may be inserted at the 2<sup>nd </sup>and 3<sup>rd </sup>segments of the 4<sup>th </sup>MPH block (B<b>4</b>). The 2<sup>nd </sup>training sequence is next to the signaling area, as shown in <figref idref="DRAWINGS">FIG. 5</figref>. Then, the 3<sup>rd </sup>training sequence, the 4<sup>th </sup>training sequence, the 5<sup>th </sup>training sequence, and the 6<sup>th </sup>training sequence may be placed at the last 2 segments of the 4<sup>th</sup>, 5<sup>th</sup>, 6<sup>th</sup>, and 7<sup>th </sup>MPH blocks (B<b>4</b>, B<b>5</b>, B<b>6</b>, and B<b>7</b>), respectively. As shown in <figref idref="DRAWINGS">FIG. 34</figref>, the 1<sup>st </sup>training sequence, the 3<sup>rd </sup>training sequence, the 4<sup>th </sup>training sequence, the 5<sup>th </sup>training sequence, and the 6<sup>th </sup>training sequence are spaced 16 segments apart from one another. Referring to <figref idref="DRAWINGS">FIG. 34</figref>, the dotted area indicates trellis initialization data bytes, the lined area indicates training data bytes, and the white area includes other bytes such as the FEC-coded MPH service data bytes, FEC-coded signaling data, main service data bytes, RS parity data bytes (for backwards compatibility with legacy ATSC receivers) and/or dummy data bytes.
0302<figref idref="DRAWINGS">FIG. 35</figref> illustrates the training sequences (at the symbol level) after trellis-encoding by the trellis encoder. Referring to <figref idref="DRAWINGS">FIG. 35</figref>, the dotted area indicates data segment sync symbols, the lined area indicates training data symbols, and the white area includes other symbols, such as FEC-coded mobile service data symbols, FEC-coded signaling data, main service data symbols, RS parity data symbols (for backwards compatibility with legacy ATSC receivers), dummy data symbols, trellis initialization data symbols, and/or the first part of the training sequence data symbols. Due to the intra-segment interleaving of the trellis encoder, various types of data symbols will be mixed in the white area.
0303After the trellis-encoding process, the last 1416 (=588+828) symbols of the 1<sup>st </sup>training sequence, the 3<sup>rd </sup>training sequence, the 4<sup>th </sup>training sequence, the 5<sup>th </sup>training sequence, and the 6<sup>th </sup>training sequence commonly share the same data pattern. Including the data segment synchronization symbols in the middle of and after each sequence, the total length of each common training pattern is 1424 symbols. The 2<sup>nd </sup>training sequence has a first 528-symbol sequence and a second 528-symbol sequence that have the same data pattern. More specifically, the 528-symbol sequence is repeated after the 4-symbol data segment synchronization signal. At the end of each training sequence, the memory contents of the twelve modified trellis encoders shall be set to zero(0).
0000Demodulating Unit within Receiving System
0304<figref idref="DRAWINGS">FIG. 36</figref> illustrates an example of a demodulating unit in a digital broadcast receiving system according to the present invention. The demodulating unit of <figref idref="DRAWINGS">FIG. 36</figref> uses known data information, which is inserted in the mobile service data section and, then, transmitted by the transmitting system, so as to perform carrier synchronization recovery, frame synchronization recovery, and channel equalization, thereby enhancing the receiving performance. Also the demodulating unit may turn the power on only during a slot to which the data group of the designated (or desired) parade is assigned, thereby reducing power consumption of the receiving system.
0305Referring to <figref idref="DRAWINGS">FIG. 36</figref>, the demodulating unit includes a demodulator <b>1002</b>, an equalizer <b>1003</b>, a known sequence detector <b>1004</b>, a block decoder <b>1005</b>, a RS frame decoder <b>1006</b>, a derandomizer <b>1007</b>. The demodulating unit may further include a data deinterleaver <b>1009</b>, a RS decoder <b>1010</b>, and a data derandomizer <b>1011</b>. The demodulating unit may further include a signaling information decoder <b>1013</b>. The receiving system also may further include a power controller <b>5000</b> for controlling power supply of the demodulating unit.
0306Herein, for simplicity of the description of the present invention, the RS frame decoder <b>1006</b>, and the derandomizer <b>1007</b> will be collectively referred to as a mobile service data processing unit. And, the data deinterleaver <b>1009</b>, the RS decoder <b>1010</b>, and the data derandomizer <b>1011</b> will be collectively referred to as a main service data processing unit. More specifically, a frequency of a particular channel tuned by a tuner down converts to an intermediate frequency (IF) signal. Then, the down-converted data <b>1001</b> outputs the down-converted IF signal to the demodulator <b>1002</b> and the known sequence detector <b>1004</b>. At this point, the down-converted data <b>1001</b> is inputted to the demodulator <b>1002</b> and the known sequence detector <b>1004</b> via analog/digital converter ADC (not shown). The ADC converts pass-band analog IF signal into pass-band digital IF signal.
0307The demodulator <b>1002</b> performs self gain control, carrier recovery, and timing recovery processes on the inputted pass-band digital IF signal, thereby modifying the IF signal to a base-band signal. Then, the demodulator <b>1002</b> outputs the newly created base-band signal to the equalizer <b>1003</b> and the known sequence detector <b>1004</b>. The equalizer <b>1003</b> compensates the distortion of the channel included in the demodulated signal and then outputs the error-compensated signal to the block decoder <b>1005</b>.
0308At this point, the known sequence detector <b>1004</b> detects the known sequence place inserted by the transmitting end from the input/output data of the demodulator <b>1002</b> (i.e., the data prior to the demodulation process or the data after the demodulation process). Thereafter, the place information along with the symbol sequence of the known data, which are generated from the detected place, is outputted to the demodulator <b>1002</b> and the equalizer <b>1003</b>. Also, the known data detector <b>1004</b> outputs a set of information to the block decoder <b>1005</b>. This set of information is used to allow the block decoder <b>1005</b> of the receiving system to identify the mobile service data that are processed with additional encoding from the transmitting system and the main service data that are not processed with additional encoding. In addition, although the connection status is not shown in <figref idref="DRAWINGS">FIG. 36</figref>, the information detected from the known data detector <b>1004</b> may be used throughout the entire receiving system and may also be used in the RS frame decoder <b>1006</b>.
0309The demodulator <b>1002</b> uses the known data symbol sequence during the timing and/or carrier recovery, thereby enhancing the demodulating performance. Similarly, the equalizer <b>1003</b> uses the known data so as to enhance the equalizing performance. Moreover, the decoding result of the block decoder <b>1005</b> may be fed-back to the equalizer <b>1003</b>, thereby enhancing the equalizing performance.
0000Power On/Off Control
0310The data demodulated in the demodulator <b>1002</b> or the data equalized in the channel equalizer <b>1003</b> is inputted to the signaling information decoder <b>1013</b>. The known data information detected in the known sequence detector <b>1004</b> is inputted to the signaling information decoder <b>1013</b>.
0311The signaling information decoder <b>1013</b> extracts and decodes signaling information from the inputted data, the decoded signaling information provides to blocks requiring the signaling information. For example, the SCCC-associated information may output to the block decoder <b>1005</b>, and the RS frame-associated information may output to the RS frame decoder <b>1006</b>. The MPH frame-associated information may output to the known sequence detector <b>1004</b> and the power controller <b>5000</b>.
0312Herein, the RS frame-associated information may include RS frame mode information and RS code mode information. The SCCC-associated information may include SCCC block mode information and SCCC outer code mode information. The MPH frame-associated information may include sub-frame count information, slot count information, parade_id information, SGN information, NoG information, and so on, as shown in <figref idref="DRAWINGS">FIG. 32</figref>.
0313More specifically, the signaling information between first known data area and second known data area can know by using known data information being outputted in the known sequence detector <b>1004</b>. Therefore, the signaling information decoder <b>1013</b> may extract and decode signaling information from the data being outputted in the demodulator <b>1002</b> or the channel equalizer <b>1003</b>.
0314The power controller <b>5000</b> is inputted the MPH frame-associated information from the signaling information decoder <b>1013</b>, and controls power of the tuner and the demodulating unit.
0315According to the embodiment of the present invention, the power controller <b>5000</b> turns the power on only during a slot to which a slot of the parade including user-selected mobile service is assigned. The power controller <b>5000</b> then turns the power off during the remaining slots.
0316For example, it is assumed that data groups of a 1<sup>st </sup>parade with NOG=3, a 2<sup>nd </sup>parade with NOG=2, and a 3<sup>rd </sup>parade with NOG=3 are assigned to one MPH frame, as shown in <figref idref="DRAWINGS">FIG. 33</figref>. It is also assumed that the user has selected a mobile service included in the 1<sup>st </sup>parade using the keypad provided on the remote controller or terminal. In this case, the power controller <b>5000</b> turns the power on only during a slot that data groups of the 1<sup>st </sup>parade is assigned, as shown in <figref idref="DRAWINGS">FIG. 33</figref>, and turns the power off during the remaining slots, thereby reducing power consumption.
0000Demodulator and Known Sequence Detector
0317At this point, the transmitting system may receive a data frame (or VSB frame) including a data group which known data sequence (or training sequence) is periodically inserted therein. Herein, the data group is divided into regions A to D, as shown in <figref idref="DRAWINGS">FIG. 5</figref>. More specifically, in the example of the present invention, each region A, B, C, and D are further divided into MPH blocks B<b>4</b> to B<b>7</b>, MPH blocks B<b>3</b> and B<b>8</b>, MPH blocks B<b>2</b> and B<b>9</b>, MPH blocks B<b>1</b> and B<b>10</b>, respectively.
0318<figref idref="DRAWINGS">FIG. 37</figref> illustrates an example of known data sequence being periodically inserted and transmitted in-between actual data by the transmitting system. Referring to <figref idref="DRAWINGS">FIG. 37</figref>, AS represents the number of valid data symbols, and BS represents the number of known data symbols. Therefore, BS number of known data symbols are inserted and transmitted at a period of (AS+BS) symbols. Herein, AS may correspond to mobile service data, main service data, or a combination of mobile service data and main service data. In order to be differentiated from the known data, data corresponding to AS will hereinafter be referred to as valid data.
0319Referring to <figref idref="DRAWINGS">FIG. 37</figref>, known data sequence having the same pattern are included in each known data section that is being periodically inserted. Herein, the length of the known data sequence having identical data patterns may be either equal to or different from the length of the entire (or total) known data sequence of the corresponding known data section (or block). If the two lengths are different from one another, the length of the entire known data sequence should be longer than the length of the known data sequence having identical data patterns. In this case, the same known data sequences are included in the entire known data sequence. The known sequence detector <b>1004</b> detects the position of the known data being periodically inserted and transmitted as described above. At the same time, the known sequence detector <b>1004</b> may also estimate initial frequency offset during the process of detecting known data. In this case, the demodulator <b>1002</b> may estimate with more accuracy carrier frequency offset from the information on the known data position (or known sequence position indicator) and initial frequency offset estimation value, thereby compensating the estimated initial frequency offset.
0320<figref idref="DRAWINGS">FIG. 38</figref> illustrates a detailed block diagram of a demodulator according to the present invention. Referring to <figref idref="DRAWINGS">FIG. 38</figref>, the demodulator includes a phase splitter <b>1010</b>, a numerically controlled oscillator (NCO) <b>1020</b>, a first multiplier <b>1030</b>, a resampler <b>1040</b>, a second multiplier <b>1050</b>, a matched filter <b>1060</b>, a DC remover <b>1070</b>, a timing recovery unit <b>1080</b>, a carrier recovery unit <b>1090</b>, and a phase compensator <b>1110</b>. Herein, the known sequence detector <b>1004</b> includes a known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> for estimating known data information and initial frequency offset. Also referring to <figref idref="DRAWINGS">FIG. 38</figref>, the phase splitter <b>1010</b> receives a pass band digital signal and splits the received signal into a pass band digital signal of a real number element and a pass band digital signal of an imaginary number element both having a phase of 90 degrees between one another. In other words, the pass band digital signal is split into complex signals. The split portions of the pass band digital signal are then outputted to the first multiplier <b>1030</b>. Herein, the real number signal outputted from the phase splitter <b>1010</b> will be referred to as an ‘I’ signal, and the imaginary number signal outputted from the phase splitter <b>1010</b> will be referred to as a ‘Q’ signal, for simplicity of the description of the present invention.
0321The first multiplier <b>1030</b> multiplies the I and Q pass band digital signals, which are outputted from the phase splitter <b>1010</b>, to a complex signal having a frequency proportional to a constant being outputted from the NCO <b>1020</b>, thereby changing the I and Q pass band digital signals to baseband digital complex signals. Then, the baseband digital signals of the first multiplier <b>1030</b> are inputted to the resampler <b>1040</b>. The resampler <b>1040</b> resamples the signals being outputted from the first multiplier <b>1030</b> so that the signal corresponds to the timing clock provided by the timing recovery unit <b>1080</b>. Thereafter, the resampler <b>1040</b> outputs the resampled signals to the second multiplier <b>1050</b>.
0322For example, when the analog/digital converter uses a 25 MHz fixed oscillator, the baseband digital signal having a frequency of 25 MHz, which is created by passing through the analog/digital converter, the phase splitter <b>1010</b>, and the first multiplier <b>1030</b>, is processed with an interpolation process by the resampler <b>1040</b>. Thus, the interpolated signal is recovered to a baseband digital signal having a frequency twice that of the receiving signal of a symbol clock (i.e., a frequency of 21.524476 MHz). Alternatively, if the analog/digital converter uses the timing clock of the timing recovery unit <b>1080</b> as the sampling frequency (i.e., if the analog/digital converter uses a variable frequency) in order to perform an A/D conversion process, the resampler <b>1040</b> is not required and may be omitted.
0323The second multiplier <b>1050</b> multiplies an output frequency of the carrier recovery unit <b>1090</b> with the output of the resampler <b>1040</b> so as to compensate any remaining carrier included in the output signal of the resampler <b>1040</b>. Thereafter, the compensated carrier is outputted to the matched filter <b>1060</b> and the timing recovery unit <b>1080</b>. The signal matched-filtered by the matched filter <b>1060</b> is inputted to the DC remover <b>1070</b>, the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b>, and the carrier recovery unit <b>1090</b>.
0324The known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> detects the place (or position) of the known data sequences that are being periodically or non-periodically transmitted. Simultaneously, the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> estimates an initial frequency offset during the known sequence detection process. More specifically, while the transmission data frame is being received, as shown in <figref idref="DRAWINGS">FIG. 5</figref>, the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> detects the position (or place) of the known data included in the transmission data frame. Then, the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> outputs the detected information on the known data place (i.e., a known sequence position indicator) to the timing recovery unit <b>1080</b>, the carrier recovery unit <b>1090</b>, and the phase compensator <b>1110</b> of the demodulator <b>1002</b> and the equalizer <b>1003</b>. Furthermore, the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> estimates the initial frequency offset, which is then outputted to the carrier recovery unit <b>1090</b>. At this point, the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> may either receive the output of the matched filter <b>1060</b> or receive the output of the resampler <b>1040</b>. This may be optionally decided depending upon the design of the system designer.
0325The timing recovery unit <b>1080</b> uses the output of the second multiplier <b>1050</b> and the known sequence position indicator detected from the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b>, so as to detect the timing error and, then, to output a sampling clock being in proportion with the detected timing error to the resampler <b>1040</b>, thereby adjusting the sampling timing of the resampler <b>1040</b>. At this point, the timing recovery unit <b>1080</b> may receive the output of the matched filter <b>1060</b> instead of the output of the second multiplier <b>1050</b>. This may also be optionally decided depending upon the design of the system designer.
0326Meanwhile, the DC remover <b>1070</b> removes a pilot tone signal (i.e., DC signal), which has been inserted by the transmitting system, from the matched-filtered signal. Thereafter, the DC remover <b>1070</b> outputs the processed signal to the phase compensator <b>1110</b>. The phase compensator <b>1110</b> uses the data having the DC removed by the DC remover <b>1070</b> and the known sequence position indicator detected by the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> to estimate the frequency offset and, then, to compensate the phase change included in the output of the DC remover <b>1070</b>. The data having its phase change compensated are inputted to the equalizer <b>1003</b>. Herein, the phase compensator <b>1110</b> is optional. If the phase compensator <b>1110</b> is not provided, then the output of the DC remover <b>1070</b> is inputted to the equalizer <b>1003</b> instead.
0327<figref idref="DRAWINGS">FIG. 39</figref> includes detailed block diagrams of the timing recovery unit <b>1080</b>, the carrier recovery unit <b>1090</b>, and the phase compensator <b>1110</b> of the demodulator. According to an embodiment of the present invention, the carrier recovery unit <b>1090</b> includes a buffer <b>1091</b>, a frequency offset estimator <b>1092</b>, a loop filter <b>1093</b>, a holder <b>1094</b>, an adder <b>1095</b>, and a NCO <b>1096</b>. Herein, a decimator may be included before the buffer <b>1091</b>. The timing recovery unit <b>1080</b> includes a decimator <b>1081</b>, a buffer <b>1082</b>, a timing error detector <b>1083</b>, a loop filter <b>1084</b>, a holder <b>1085</b>, and a NCO <b>1086</b>. Finally, the phase compensator <b>1110</b> includes a buffer <b>1111</b>, a frequency offset estimator <b>1112</b>, a holder <b>1113</b>, a NCO <b>1114</b>, and a multiplier <b>1115</b>. Furthermore, a decimator <b>1200</b> may be included between the phase compensator <b>1110</b> and the equalizer <b>1003</b>. The decimator <b>1200</b> may be outputted in front of the DC remover <b>1070</b> instead of at the outputting end of the phase compensator <b>1110</b>.
0328Herein, the decimators correspond to components required when a signal being inputted to the demodulator is oversampled to N times by the analog/digital converter. More specifically, the integer N represents the sampling rate of the received signal. For example, when the input signal is oversampled to 2 times (i.e., when N=2) by the analog/digital converter, this indicates that two samples are included in one symbol. In this case, each of the decimators corresponds to a 1/2 decimator. Depending upon whether or not the oversampling process of the received signal has been performed, the signal may bypass the decimators.
0329Meanwhile, the output of the second multiplier <b>1050</b> is temporarily stored in the decimator <b>1081</b> and the buffer <b>1082</b> both included in the timing recovery unit <b>1080</b>. Subsequently, the temporarily stored output data are inputted to the timing error detector <b>1083</b> through the decimator <b>1081</b> and the buffer <b>1082</b>. Assuming that the output of the second multiplier <b>1050</b> is oversampled to N times its initial state, the decimator <b>1081</b> decimates the output of the second multiplier <b>1050</b> at a decimation rate of 1/N. Then, the 1/N-decimated data are inputted to the buffer <b>1082</b>. In other words, the decimator <b>1081</b> performs decimation on the input signal in accordance with a VSB symbol cycle. Furthermore, the decimator <b>1081</b> may also receive the output of the matched filter <b>1060</b> instead of the output of the second multiplier <b>1050</b>. The timing error detector <b>1083</b> uses the data prior to or after being processed with matched-filtering and the known sequence position indicator outputted from the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> in order to detect a timing error. Thereafter, the detected timing error is outputted to the loop filter <b>1084</b>. Accordingly, the detected timing error information is obtained once during each repetition cycle of the known data sequence.
0330For example, if a known data sequence having the same pattern is periodically inserted and transmitted, as shown in <figref idref="DRAWINGS">FIG. 37</figref>, the timing error detector <b>1083</b> may use the known data in order to detect the timing error. There exists a plurality of methods for detecting timing error by using the known data. In the example of the present invention, the timing error may be detected by using a correlation characteristic between the known data and the received data in the time domain, the known data being already known in accordance with a pre-arranged agreement between the transmitting system and the receiving system. The timing error may also be detected by using the correlation characteristic of the two known data types being received in the frequency domain. Thus, the detected timing error is outputted. In another example, a spectral lining method may be applied in order to detect the timing error. Herein, the spectral lining method corresponds to a method of detecting timing error by using sidebands of the spectrum included in the received signal.
0331The loop filter <b>1084</b> filters the timing error detected by the timing error detector <b>1083</b> and, then, outputs the filtered timing error to the holder <b>1085</b>. The holder <b>1085</b> holds (or maintains) the timing error filtered and outputted from the loop filter <b>1084</b> during a pre-determined known data sequence cycle period and outputs the processed timing error to the NCO <b>1086</b>. Herein, the order of positioning of the loop filter <b>1084</b> and the holder <b>1085</b> may be switched with one another. In additionally, the function of the holder <b>1085</b> may be included in the loop filter <b>1084</b>, and, accordingly, the holder <b>1085</b> may be omitted. The NCO <b>1086</b> accumulates the timing error outputted from the holder <b>1085</b>. Thereafter, the NCO <b>1086</b> outputs the phase element (i.e., a sampling clock) of the accumulated timing error to the resampler <b>1040</b>, thereby adjusting the sampling timing of the resampler <b>1040</b>.
0332Meanwhile, the buffer <b>1091</b> of the carrier recovery unit <b>1090</b> may receive either the data inputted to the matched filter <b>1060</b> or the data outputted from the matched filter <b>1060</b> and, then, temporarily store the received data. Thereafter, the temporarily stored data are outputted to the frequency offset estimator <b>1092</b>. If a decimator is provided in front of the buffer <b>1091</b>, the input data or output data of the matched filter <b>1060</b> are decimated by the decimator at a decimation rate of 1/N. Thereafter, the decimated data are outputted to the buffer <b>1091</b>. For example, when the input data or output data of the matched filter <b>1060</b> are oversampled to 2 times (i.e., when N=2), this indicates that the input data or output data of the matched filter <b>1060</b> are decimated at a rate of 1/2 by the decimator <b>1081</b> and then outputted to the buffer <b>1091</b>. More specifically, when a decimator is provided in front of the buffer <b>1091</b>, the carrier recovery unit <b>1090</b> operates in symbol units. Alternatively, if a decimator is not provided, the carrier recovery unit <b>1090</b> operates in oversampling units.
0333The frequency offset estimator <b>1092</b> uses the input data or output data of the matched filter <b>1060</b> and the known sequence position indicator outputted from the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> in order to estimate the frequency offset. Then, the estimated frequency offset is outputted to the loop filter <b>1093</b>. Therefore, the estimated frequency offset value is obtained once every repetition period of the known data sequence. The loop filter <b>1093</b> performs low pass filtering on the frequency offset value estimated by the frequency offset estimator <b>1092</b> and outputs the low pass-filtered frequency offset value to the holder <b>1094</b>. The holder <b>1094</b> holds (or maintains) the low pass-filtered frequency offset value during a pre-determined known data sequence cycle period and outputs the frequency offset value to the adder <b>1095</b>. Herein, the positions of the loop filter <b>1093</b> and the holder <b>1094</b> may be switched from one to the other. Furthermore, the function of the holder <b>1085</b> may be included in the loop filter <b>1093</b>, and, accordingly, the holder <b>1094</b> may be omitted.
0334The adder <b>1095</b> adds the value of the initial frequency offset estimated by the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> to the frequency offset value outputted from the loop filter <b>1093</b> (or the holder <b>1094</b>). Thereafter, the added offset value is outputted to the NCO <b>1096</b>. Herein, if the adder <b>1095</b> is designed to also receive the constant being inputted to the NCO <b>1020</b>, the NCO <b>1020</b> and the first multiplier <b>1030</b> may be omitted. In this case, the second multiplier <b>1050</b> may simultaneously perform changing signals to baseband signals and removing remaining carrier.
0335The NCO <b>1096</b> generates a complex signal corresponding to the frequency offset outputted from the adder <b>1095</b>, which is then outputted to the second multiplier <b>1050</b>. Herein, the NCO <b>1096</b> may include a ROM. In this case, the NCO <b>1096</b> generates a compensation frequency corresponding to the frequency offset being outputted from the adder <b>1095</b>. Then, the NCO <b>1096</b> reads a complex cosine corresponding to the compensation frequency from the ROM, which is then outputted to the second multiplier <b>1050</b>. The second multiplier <b>1050</b> multiplies the output of the NCO <b>1094</b> included in the carrier recovery unit <b>1090</b> to the output of the resampler <b>1040</b>, so as to remove the carrier offset included in the output signal of the resampler <b>1040</b>.
0336<figref idref="DRAWINGS">FIG. 40</figref> illustrates a detailed block diagram of the frequency offset estimator <b>1092</b> of the carrier recovery unit <b>1090</b> according to an embodiment of the present invention. Herein, the frequency offset estimator <b>1092</b> operates in accordance with the known sequence position indicator detected from the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b>. At this point, if the input data or output data of the matched filter <b>1060</b> are inputted through the decimator, the frequency offset estimator <b>1092</b> operates in symbol units. Alternatively, if a decimator is not provided, the frequency offset estimator <b>1092</b> operates in oversampling units. In the example given in the description of the present invention, the frequency offset estimator <b>1092</b> operates in symbol units. Referring to <figref idref="DRAWINGS">FIG. 40</figref>, the frequency offset estimator <b>1092</b> includes a controller <b>1310</b>, a first N symbol buffer <b>1301</b>, a K symbol delay <b>1302</b>, a second N symbol buffer <b>1303</b>, a conjugator <b>1304</b>, a multiplier <b>1305</b>, an accumulator <b>1306</b>, a phase detector <b>1307</b>, a multiplier <b>1308</b>, and a multiplexer <b>1309</b>. The frequency offset estimator <b>1092</b> having the above-described structure, as shown in <figref idref="DRAWINGS">FIG. 40</figref>, will now be described in detail with respect to an operation example during a known data section.
0337The first N symbol buffer <b>1301</b> may store a maximum of N number of symbol being inputted thereto. The symbol data that are temporarily stored in the first N symbol buffer <b>1301</b> are then inputted to the multiplier <b>1305</b>. At the same time, the inputted symbol is inputted to the K symbol delay <b>1302</b> so as to be delayed by K symbols. Thereafter, the delayed symbol passes through the second N symbol buffer <b>1303</b> so as to be conjugated by the conjugator <b>1304</b>. Thereafter, the conjugated symbol is inputted to the multiplier <b>1305</b>. The multiplier <b>1305</b> multiplies the output of the first N symbol buffer <b>1301</b> and the output of the conjugator <b>1304</b>. Then, the multiplier <b>1305</b> outputs the multiplied result to the accumulator <b>1306</b>. Subsequently, the accumulator <b>1306</b> accumulates the output of the multiplier <b>1305</b> during N symbol periods, thereby outputted the accumulated result to the phase detector <b>1307</b>.
0338The phase detector <b>1307</b> extracts the corresponding phase information from the output of the accumulator <b>1306</b>, which is then outputted to the multiplier <b>1308</b>. The multiplier <b>1308</b> then divides the phase information by K, thereby outputting the divided result to the multiplexer <b>1309</b>. Herein, the result of the phase information divided by becomes the frequency offset estimation value. More specifically, at the point where the input of the known data ends or at a desired point, the frequency offset estimator <b>1092</b> accumulates during an N symbol period multiplication of the complex conjugate of N number of the input data stored in the first N symbol buffer <b>1301</b> and the complex conjugate of the N number of the input data that are delayed by K symbols and stored in the second N symbol buffer <b>1303</b>. Thereafter, the accumulated value is divided by K, thereby extracting the frequency offset estimation value.
0339Based upon a control signal of the controller <b>1310</b>, the multiplexer <b>1309</b> selects either the output of the multiplier <b>1308</b> or ‘0’ and, then, outputs the selected result as the final frequency offset estimation value. The controller <b>1310</b> receives the known data sequence position indicator from the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> in order to control the output of the multiplexer <b>1309</b>. More specifically, the controller <b>1310</b> determines based upon the known data sequence position indicator whether the frequency offset estimation value being outputted from the multiplier <b>1308</b> is valid. If the controller <b>1310</b> determines that the frequency offset estimation value is valid, the multiplexer <b>1309</b> selects the output of the multiplier <b>1308</b>. Alternatively, if the controller <b>1310</b> determines that the frequency offset estimation value is invalid, the controller <b>1310</b> generates a control signal so that the multiplexer <b>1309</b> selects ‘0’. At this point, it is preferable that the input signals stored in the first N symbol buffer <b>1301</b> and in the second N symbol buffer <b>1303</b> correspond to signals each being transmitted by the same known data and passing through almost the same channel. Otherwise, due to the influence of the transmission channel, the frequency offset estimating performance may be largely deteriorated.
0340Further, the values N and K of the frequency offset estimator <b>1092</b> (shown in <figref idref="DRAWINGS">FIG. 40</figref>) may be diversely decided. This is because a particular portion of the known data that are identically repeated may be used herein. For example, when the data having the structure described in <figref idref="DRAWINGS">FIG. 37</figref> are being transmitted, N may be set as BS (i.e., N=BS), and K may be set as (AS+BS) (i.e., K=AS+BS)). The frequency offset estimation value range of the frequency offset estimator <b>1092</b> is decided in accordance with the value K. If the value K is large, then the frequency offset estimation value range becomes smaller. Alternatively, if the value K is small, then the frequency offset estimation value range becomes larger. Therefore, when the data having the structure of <figref idref="DRAWINGS">FIG. 37</figref> is transmitted, and if the repetition cycle (AS+BS) of the known data is long, then the frequency offset estimation value range becomes smaller.
0341In this case, even if the initial frequency offset is estimated by the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b>, and if the estimated value is compensated by the second multiplier <b>1050</b>, the remaining frequency offset after being compensated will exceed the estimation range of the frequency offset estimator <b>1092</b>. In order to overcome such problems, the known data sequence that is regularly transmitted may be configured of a repetition of a same data portion by using a cyclic extension process. For example, if the known data sequence shown in <figref idref="DRAWINGS">FIG. 37</figref> is configured of two identical portions having the length of BS/2, then the N and K values of the frequency offset estimator <b>1092</b> (shown in <figref idref="DRAWINGS">FIG. 40</figref>) may be respectively set as B/2 and B/2 (i.e., N=BS/2 and K=BS/2). In this case, the estimation value range may become larger than when using repeated known data.
0342Meanwhile, the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> detects the place (o position) of the known data sequences that are being periodically or non-periodically transmitted. Simultaneously, the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> estimates an initial frequency offset during the known sequence detection process. The known data sequence position indicator detected by the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> is outputted to the timing recovery unit <b>1080</b>, the carrier recovery unit <b>1090</b>, and the phase compensator <b>1110</b> of the demodulator <b>1002</b>, and to the equalizer <b>1003</b>. Thereafter, the estimated initial frequency offset is outputted to the carrier recovery unit <b>1090</b>. At this point, the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> may either receive the output of the matched filter <b>1060</b> or receive the output of the resampler <b>1040</b>. This may be optionally decided depending upon the design of the system designer. Herein, the frequency offset estimator shown in <figref idref="DRAWINGS">FIG. 40</figref> may be directly applied in the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> or in the phase compensator <b>1110</b> of the frequency offset estimator.
0343<figref idref="DRAWINGS">FIG. 41</figref> illustrates a detailed block diagram showing a known sequence detector and initial frequency offset estimator according to an embodiment of the present invention. More specifically, <figref idref="DRAWINGS">FIG. 41</figref> illustrates an example of an initial frequency offset being estimated along with the known sequence position indicator. Herein, <figref idref="DRAWINGS">FIG. 41</figref> shows an example of an inputted signal being oversampled to N times of its initial state. In other words, N represents the sampling rate of a received signal. Referring to <figref idref="DRAWINGS">FIG. 41</figref>, the known sequence detector and initial frequency offset estimator includes N number of partial correlators <b>1411</b> to <b>141</b>N configured in parallel, a known data place detector and frequency offset decider <b>1420</b>, a known data extractor <b>1430</b>, a buffer <b>1440</b>, a multiplier <b>1450</b>, a NCO <b>1460</b>, a frequency offset estimator <b>1470</b>, and an adder <b>1480</b>. Herein, the first partial correlator <b>1411</b> consists of a 1/N decimator, and a partial correlator. The second partial correlator <b>1412</b> consists of a 1 sample delay, a 1/N decimator, and a partial correlator. And, the N<sup>th </sup>partial correlator <b>141</b>N consists of a N−1 sample delay, a 1/N decimator, and a partial correlator. These are used to match (or identify) the phase of each of the samples within the oversampled symbol with the phase of the original (or initial) symbol, and to decimate the samples of the remaining phases, thereby performing partial correlation on each sample. More specifically, the input signal is decimated at a rate of 1/N for each sampling phase, so as to pass through each partial correlator.
0344For example, when the input signal is oversampled to 2 times (i.e., when N=2), this indicates that two samples are included in one signal. In this case, two partial correlators (e.g., <b>1411</b> and <b>1412</b>) are required, and each 1/N decimator becomes a 1/2 decimator. At this point, the 1/N decimator of the first partial correlator <b>1411</b> decimates (or removes), among the input samples, the samples located in-between symbol places (or positions). Then, the corresponding 1/N decimator outputs the decimated sample to the partial correlator. Furthermore, the 1 sample delay of the second partial correlator <b>1412</b> delays the input sample by 1 sample (i.e., performs a 1 sample delay on the input sample) and outputs the delayed input sample to the 1/N decimator. Subsequently, among the samples inputted from the 1 sample delay, the 1/N decimator of the second partial correlator <b>1412</b> decimates (or removes) the samples located in-between symbol places (or positions). Thereafter, the corresponding 1/N decimator outputs the decimated sample to the partial correlator.
0345After each predetermined period of the VSB symbol, each of the partial correlators outputs a correlation value and an estimation value of the coarse frequency offset estimated at that particular moment to the known data place detector and frequency offset decider <b>1420</b>. The known data place detector and frequency offset decider <b>1420</b> stores the output of the partial correlators corresponding to each sampling phase during a data group cycle or a pre-decided cycle. Thereafter, the known data place detector and frequency offset decider <b>1420</b> decides a position (or place) corresponding to the highest correlation value, among the stored values, as the place (or position) for receiving the known data. Simultaneously, the known data place detector and frequency offset decider <b>1420</b> finally decides the estimation value of the frequency offset estimated at the moment corresponding to the highest correlation value as the coarse frequency offset value of the receiving system. At this point, the known sequence position indicator is inputted to the known data extractor <b>1430</b>, the timing recovery unit <b>1080</b>, the carrier recovery unit <b>1090</b>, the phase compensator <b>1110</b>, and the equalizer <b>1003</b>, and the coarse frequency offset is inputted to the adder <b>1480</b> and the NCO <b>1460</b>.
0346In the meantime, while the N numbers of partial correlators <b>1411</b> to <b>141</b>N detect the known data place (or known sequence position) and estimate the coarse frequency offset, the buffer <b>1440</b> temporarily stores the received data and outputs the temporarily stored data to the known data extractor <b>1430</b>. The known data extractor <b>1430</b> uses the known sequence position indicator, which is outputted from the known data place detector and frequency offset decider <b>1420</b>, so as to extract the known data from the output of the buffer <b>1440</b>. Thereafter, the known data extractor <b>1430</b> outputs the extracted data to the multiplier <b>1450</b>. The NCO <b>1460</b> generates a complex signal corresponding to the coarse frequency offset being outputted from the known data place detector and frequency offset decider <b>1420</b>. Then, the NCO <b>1460</b> outputs the generated complex signal to the multiplier <b>1450</b>.
0347The multiplier <b>1450</b> multiplies the complex signal of the NCO <b>1460</b> to the known data being outputted from the known data extractor <b>1430</b>, thereby outputting the known data having the coarse frequency offset compensated to the frequency offset estimator <b>1470</b>. The frequency offset estimator <b>1470</b> estimates a fine frequency offset from the known data having the coarse frequency offset compensated. Subsequently, the frequency offset estimator <b>1470</b> outputs the estimated fine frequency offset to the adder <b>1480</b>. The adder <b>1480</b> adds the coarse frequency offset to the fine frequency offset. Thereafter, the adder <b>1480</b> decides the added result as a final initial frequency offset, which is then outputted to the adder <b>1095</b> of the carrier recovery unit <b>1090</b> included in the demodulator <b>1002</b>. More specifically, during the process of acquiring initial synchronization, the present invention may estimate and use the coarse frequency offset as well as the fine frequency offset, thereby enhancing the estimation performance of the initial frequency offset.
0348It is assumed that the known data is inserted within the data group and then transmitted, as shown in <figref idref="DRAWINGS">FIG. 5</figref>. Then, the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> may use the known data that have been additionally inserted between the A<b>1</b> area and the A<b>2</b> area, so as to estimate the initial frequency offset. The known position indicator, which was periodically inserted within the A area estimated by the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b>, is inputted to the timing error detector <b>1083</b> of the timing error recovery unit <b>1080</b>, to the frequency offset estimator <b>1092</b> of the carrier recovery unit <b>1090</b>, to the frequency offset estimator <b>1112</b> of the phase compensator <b>1110</b>, and to the equalizer <b>1003</b>.
0349<figref idref="DRAWINGS">FIG. 42</figref> illustrates a block diagram showing the structure of one of the partial correlators shown in <figref idref="DRAWINGS">FIG. 41</figref>. During the step of detecting known data, since a frequency offset is included in the received signal, each partial correlator divides the known data, which is known according to an agreement between the transmitting system and the receiving system, to K number of parts each having an L symbol length, thereby correlating each divided part with the corresponding part of the received signal. In order to do so, each partial correlator includes K number of phase and size detector <b>1511</b> to <b>151</b>K each formed in parallel, an adder <b>1520</b>, and a coarse frequency offset estimator <b>1530</b>.
0350The first phase and size detector <b>1511</b> includes an L symbol buffer <b>1511</b>-<b>2</b>, a multiplier <b>1511</b>-<b>3</b>, an accumulator <b>1511</b>-<b>4</b>, and a squarer <b>1511</b>-<b>5</b>. Herein, the first phase and size detector <b>1511</b> calculates the correlation value of the known data having a first L symbol length among the K number of sections. Also, the second phase and size detector <b>1512</b> includes an L symbol delay <b>1512</b>-<b>1</b>, an L symbol buffer <b>1512</b>-<b>2</b>, a multiplier <b>1512</b>-<b>3</b>, an accumulator <b>1512</b>-<b>4</b>, and a squarer <b>1512</b>-<b>5</b>. Herein, the second phase and size detector <b>1512</b> calculates the correlation value of the known data having a second L symbol length among the K number of sections. Finally, the N<sup>th </sup>phase and size detector <b>151</b>K includes a (K-<b>1</b>)L symbol delay <b>151</b>K-<b>1</b>, an L symbol buffer <b>151</b>K-<b>2</b>, a multiplier <b>151</b>K-<b>3</b>, an accumulator <b>151</b>K-<b>4</b>, and a squarer <b>151</b>K-<b>5</b>. Herein, the N<sup>th </sup>phase and size detector <b>151</b>K calculates the correlation value of the known data having an N<sup>th </sup>L symbol length among the K number of sections.
0351Referring to <figref idref="DRAWINGS">FIG. 42</figref>, {P<sub>0</sub>, P<sub>1</sub>, . . . , P<sub>KL-1</sub>} each being multiplied with the received signal in the multiplier represents the known data known by both the transmitting system and the receiving system (i.e., the reference known data generated from the receiving system). And, * represents a complex conjugate. For example, in the first phase and size detector <b>1511</b>, the signal outputted from the 1/N decimator of the first partial correlator <b>1411</b>, shown in <figref idref="DRAWINGS">FIG. 41</figref>, is temporarily stored in the L symbol buffer <b>1511</b>-<b>2</b> of the first phase and size detector <b>1511</b> and then inputted to the multiplier <b>1511</b>-<b>3</b>. The multiplier <b>1511</b>-<b>3</b> multiplies the output of the L symbol buffer <b>1511</b>-<b>2</b> with the complex conjugate of the known data parts P<sub>0</sub>, P<sub>1</sub>, . . . , P<sub>KL-1</sub>, each having a first L symbol length among the known K number of sections. Then, the multiplied result is outputted to the accumulator <b>1511</b>-<b>4</b>. During the L symbol period, the accumulator <b>1511</b>-<b>4</b> accumulates the output of the multiplier <b>1511</b>-<b>3</b> and, then, outputs the accumulated value to the squarer <b>1511</b>-<b>5</b> and the coarse frequency offset estimator <b>1530</b>. The output of the accumulator <b>1511</b>-<b>4</b> is a correlation value having a phase and a size. Accordingly, the squarer <b>1511</b>-<b>5</b> calculates an absolute value of the output of the multiplier <b>1511</b>-<b>4</b> and squares the calculated absolute value, thereby obtaining the size of the correlation value. The obtained size is then inputted to the adder <b>1520</b>.
0352The adder <b>1520</b> adds the output of the squares corresponding to each size and phase detector <b>1511</b> to <b>151</b>K. Then, the adder <b>1520</b> outputs the added result to the known data place detector and frequency offset decider <b>1420</b>. Also, the coarse frequency offset estimator <b>1530</b> receives the output of the accumulator corresponding to each size and phase detector <b>1511</b> to <b>151</b>K, so as to estimate the coarse frequency offset at each corresponding sampling phase. Thereafter, the coarse frequency offset estimator <b>1530</b> outputs the estimated offset value to the known data place detector and frequency offset decider <b>1420</b>.
0353When the K number of inputs that are outputted from the accumulator of each phase and size detector <b>1511</b> to <b>151</b>K are each referred to as {Z<sub>0</sub>, Z<sub>1</sub>, . . . , Z<sub>K-1</sub>} the output of the coarse frequency offset estimator <b>1530</b> may be obtained by using Equation 7 shown below.
0354<maths id="MATH-US-00002" num="00002"><math overflow="scroll"><mtable><mtr><mtd><mrow><msub><mi>ω</mi><mn>0</mn></msub><mo>=</mo><mrow><mfrac><mn>1</mn><mi>L</mi></mfrac><mo></mo><mi>arg</mi><mo></mo><mrow><mo>{</mo><mrow><munderover><mo>∑</mo><mrow><mi>n</mi><mo>=</mo><mn>1</mn></mrow><mrow><mi>K</mi><mo>-</mo><mn>1</mn></mrow></munderover><mo></mo><mrow><mrow><mo>(</mo><mfrac><msub><mi>Z</mi><mi>n</mi></msub><mrow><mo></mo><msub><mi>Z</mi><mi>n</mi></msub><mo></mo></mrow></mfrac><mo>)</mo></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><msup><mrow><mo>(</mo><mfrac><msub><mi>Z</mi><mrow><mi>n</mi><mo>-</mo><mn>1</mn></mrow></msub><mrow><mo></mo><msub><mi>Z</mi><mrow><mi>n</mi><mo>-</mo><mn>1</mn></mrow></msub><mo></mo></mrow></mfrac><mo>)</mo></mrow><mo>*</mo></msup></mrow></mrow><mo>}</mo></mrow></mrow></mrow></mtd><mtd><mrow><mi>Equation</mi><mo></mo><mstyle><mspace width="0.8em" height="0.8ex" /></mstyle><mo></mo><mn>7</mn></mrow></mtd></mtr></mtable></math></maths><img file="USRE46728E_D0007.tif" /><img file="USRE46728E_D0008.tif" /><img file="USRE46728E_D0009.tif" /><img file="USRE46728E_D0010.tif" /><img file="USRE46728E_D0011.tif" /><img file="USRE46728E_D0012.tif" />
0355The known data place detector and frequency offset decider <b>1420</b> stores the output of the partial correlator corresponding to each sampling phase during an enhanced data group cycle or a pre-decided cycle. Then, among the stored correlation values, the known data place detector and frequency offset decider <b>1420</b> decides the place (or position) corresponding to the highest correlation value as the place for receiving the known data.
0356Furthermore, the known data place detector and frequency offset decider <b>1420</b> decides the estimated value of the frequency offset taken (or estimated) at the point of the highest correlation value as the coarse frequency offset value of the receiving system. For example, if the output of the partial correlator corresponding to the second partial correlator <b>1412</b> is the highest value, the place corresponding to the highest value is decided as the known data place. Thereafter, the coarse frequency offset estimated by the second partial correlator <b>1412</b> is decided as the final coarse frequency offset, which is then outputted to the demodulator <b>1002</b>.
0357Meanwhile, the output of the second multiplier <b>1050</b> is temporarily stored in the decimator <b>1081</b> and the buffer <b>1082</b> both included in the timing recovery unit <b>1080</b>. Subsequently, the temporarily stored output data are inputted to the timing error detector <b>1083</b> through the decimator <b>1081</b> and the buffer <b>1082</b>. Assuming that the output of the second multiplier <b>1050</b> is oversampled to N times its initial state, the decimator <b>1081</b> decimates the output of the second multiplier <b>1050</b> at a decimation rate of 1/N. Then, the 1/N-decimated data are inputted to the buffer <b>1082</b>. In other words, the decimator <b>1081</b> performs decimation on the input signal in accordance with a VSB symbol cycle. Furthermore, the decimator <b>1081</b> may also receive the output of the matched filter <b>1060</b> instead of the output of the second multiplier <b>1050</b>.
0358The timing error detector <b>1083</b> uses the data prior to or after being processed with matched-filtering and the known sequence position indicator outputted from the known data detector and initial frequency offset estimator <b>1004</b>-<b>1</b> in order to detect a timing error. Thereafter, the detected timing error is outputted to the loop filter <b>1084</b>. Accordingly, the detected timing error information is obtained once during each repetition cycle of the known data sequence.
0359For example, if a known data sequence having the same pattern is periodically inserted and transmitted, as shown in <figref idref="DRAWINGS">FIG. 37</figref>, the timing error detector <b>1083</b> may use the known data in order to detect the timing error. There exists a plurality of methods for detecting timing error by using the known data.
0360In the example of the present invention, the timing error may be detected by using a correlation characteristic between the known data and the received data in the time domain, the known data being already known in accordance with a pre-arranged agreement between the transmitting system and the receiving system. The timing error may also be detected by using the correlation characteristic of the two known data types being received in the frequency domain. Thus, the detected timing error is outputted. In another example, a spectral lining method may be applied in order to detect the timing error. Herein, the spectral lining method corresponds to a method of detecting timing error by using sidebands of the spectrum included in the received signal.
0361The loop filter <b>1084</b> filters the timing error detected by the timing error detector <b>1083</b> and, then, outputs the filtered timing error to the holder <b>1085</b>.
0362The holder <b>1085</b> holds (or maintains) the timing error filtered and outputted from the loop filter <b>1084</b> during a pre-determined known data sequence cycle period and outputs the processed timing error to the NCO <b>1086</b>. Herein, the order of positioning of the loop filter <b>1084</b> and the holder <b>1085</b> may be switched with one another. In additionally, the function of the holder <b>1085</b> may be included in the loop filter <b>1084</b>, and, accordingly, the holder <b>1085</b> may be omitted.
0363The NCO <b>1086</b> accumulates the timing error outputted from the holder <b>1085</b>. Thereafter, the NCO <b>1086</b> outputs the phase element (i.e., a sampling clock) of the accumulated timing error to the resampler <b>1040</b>, thereby adjusting the sampling timing of the resampler <b>1040</b>.
0364<figref idref="DRAWINGS">FIG. 43</figref> illustrates an example of the timing recovery unit included in the demodulator <b>1002</b> shown in <figref idref="DRAWINGS">FIG. 36</figref>. Referring to <figref idref="DRAWINGS">FIG. 43</figref>, the timing recovery unit <b>1080</b> includes a first timing error detector <b>1611</b>, a second timing error detector <b>1612</b>, a multiplexer <b>1613</b>, a loop-filter <b>1614</b>, and an NCO <b>1615</b>. The timing recovery unit <b>1080</b> would be beneficial when the input signal is divided into a first area in which known data having a predetermined length are inserted at predetermined position(s) and a second area that includes no known data. Assuming that the first timing error detector <b>1611</b> detects a first timing error using a sideband of a spectrum of an input signal and the second timing error detector <b>1612</b> detects a second timing error using the known data, the multiplexer <b>1613</b> can output the first timing error for the first area and can output the second timing error for the second area. The multiplexer <b>1613</b> may output both of the first and second timing errors for the first area in which the known data are inserted. By using the known data a more reliable timing error can be detected and the performance of the timing recovery unit <b>1080</b> can be enhanced.
0365This disclosure describes two ways of detecting a timing error. One way is to detect a timing error using correlation in the time domain between known data pre-known to a transmitting system and a receiving system (reference known data) and the known data actually received by the receiving system, and the other way is to detect a timing error using correlation in the frequency domain between two known data actually received by the receiving system. In <figref idref="DRAWINGS">FIG. 44</figref>, a timing error is detected by calculating correlation between the reference known data pre-known to and generated by the receiving system and the known data actually received. In <figref idref="DRAWINGS">FIG. 44</figref>, correlation between an entire portion of the reference know data sequence and an entire portion of the received known data sequence is calculated. The correlation output has a peak value at the end of each known data sequence actually received.
0366In <figref idref="DRAWINGS">FIG. 45</figref>, a timing error is detected by calculating correlation values between divided portions of the reference known data sequence and divided portions of the received known data sequence, respectively. The correlation output has a peak value at the end of each divided portion of the received known data sequence. The correlation values may be added as a total correlation value as shown <figref idref="DRAWINGS">FIG. 45</figref>, and the total correlation value can be used to calculate the timing error. When an entire portion of the received known data is used for correlation calculation, the timing error can be obtained for each data block. If the correlation level of the entire portion of the known data sequence is low, a more precise correlation can be obtained by using divided portions of the known data sequence as shown in <figref idref="DRAWINGS">FIG. 45</figref>.
0367The use of a final correlation value which is obtained based upon a plurality of correlation values of divided portions of a received known data sequence may reduce the carrier frequency error. In addition, the process time for the timing recovery can be greatly reduced when the plurality of correlation values are used to calculate the timing error. For example, when the reference known data sequence which is pre-known to the transmitting system and receiving system is divided into K portions, K correlation values between the K portions of the reference known data sequence and the corresponding divided portions of the received known data sequence can be calculated, or any combination(s) of the correlation values can be used. Therefore, the period of the timing error detection can be reduced when the divided portions of the known data sequence are used instead of the entire portion of the sequence.
0368The timing error can be calculated from the peak value of the correlation values. The timing error is obtained for each data block if an entire portion of the known data sequence is used as shown in <figref idref="DRAWINGS">FIG. 46</figref>. On the other hand, if K divided portions of the known data sequence are used for correlation calculation, K correlation values and corresponding peak values can be obtained. This indicates that the timing error can be detected K times.
0369A method of detecting a timing error using the correlation between the reference known data and the received known data shown will now be described in more detail. <figref idref="DRAWINGS">FIG. 46</figref> illustrates correlation values between the reference known data and the received known data. The correlation values correspond to data samples sampled at a rate two times greater than the symbol clock. When the random data effect is minimized and there is no timing clock error, the correlation values between the reference known data and the received known data are symmetrical. However, if a timing phase error exists, the correlation values adjacent to the peak value are not symmetrical as shown in <figref idref="DRAWINGS">FIG. 46</figref>. Therefore, the timing error can be obtained by using a difference (timing phase error shown in <figref idref="DRAWINGS">FIG. 46</figref>) between the correlation values before and after the peak value.
0370<figref idref="DRAWINGS">FIG. 47</figref> illustrates an example of the timing error detector shown in <figref idref="DRAWINGS">FIG. 43</figref>. The timing error detector includes a correlator <b>1701</b>, a down sampler <b>1702</b>, an absolute value calculator <b>1703</b>, a delay <b>1704</b>, and a subtractor <b>1705</b>. The correlator <b>1701</b> receives a known data sequence sampled at a rate at least two times higher than the symbol clock frequency and calculates the correlation values between the received known data sequence and a reference known data sequence. The down sampler <b>1702</b> performs down sampling on the correlation values and obtains samples having a symbol frequency. For example, if the data inputted to the correlator <b>1701</b> is pre-sampled at a sampling rate of 2, then the down sampler <b>1702</b> performs down sampling at a rate of 1/2 to obtain samples having the symbol frequency. The absolute value calculator <b>1703</b> calculates absolute values (or square values) of the down-sampled correlation values. These absolute values are inputted to the delay <b>1704</b> and the subtractor <b>1705</b>. The delay <b>1704</b> delays the absolute values for a symbol and the subtractor then outputs a timing error by subtracting the delayed absolute value from the values outputted from the absolute value calculator <b>1703</b>.
0371The arrangement of the correlator <b>1701</b>, the down sampler <b>1702</b>, the absolute value calculator <b>1703</b>, and the delay <b>1704</b>, and the subtractor <b>1705</b> shown in <figref idref="DRAWINGS">FIG. 47</figref> can be modified. For example, the timing phase error can be calculated in the order of the down sampler <b>1702</b>, the correlator <b>1701</b>, and the absolute value calculator <b>1703</b>, or in the order of the correlator <b>1701</b>, the absolute value calculator <b>1703</b>, and the down sampler <b>1702</b>.
0372The timing error can also be obtained using the frequency characteristic of the known data. When there is a timing frequency error, a phase of the input signal increases at a fixed slope as the frequency of the signal increases and this slope is different for current and next data block. Therefore, the timing error can be calculated based on the frequency characteristic of two different known data blocks. In <figref idref="DRAWINGS">FIG. 48</figref>, a current known data sequence (right) and a previous known data sequence (left) are converted into first and second frequency domain signals, respectively, using a Fast Fourier Transform (FFT) algorithm. The conjugate value of the first frequency domain signal is then multiplied with the second frequency domain signal in order to obtain the correlation value between two frequency domain signals. In other words, the correlation between the frequency value of the previous known data sequence and the frequency value of the current known data sequence is used to detect a phase change between the known data blocks for each frequency. In this way the phase distortion of a channel can be eliminated.
0373The frequency response of a complex VSB signal does not have a full symmetric distribution as shown in <figref idref="DRAWINGS">FIG. 46</figref>. Rather, its distribution is a left or right half of the distribution and the frequency domain correlation values also have a half distribution. In order to the phase difference between the frequency domain correlation values, the frequency domain having the correlation values can be divided into two sub-areas and a phase of a combined correlation value in each sub-area can be obtained. Thereafter, the difference between the phases of sub-areas can be used to calculate a timing frequency error. When a phase of a combined correlation values is used for each frequency, the magnitude of each correlation value is proportional to reliability and a phase component of each correlation value is reflected to the final phase component in proportion to the magnitude.
0374<figref idref="DRAWINGS">FIG. 49</figref> illustrates another example of the timing error detector shown in <figref idref="DRAWINGS">FIG. 43</figref>. The timing error detector shown in <figref idref="DRAWINGS">FIG. 49</figref> includes a Fast Fourier Transform (FFT) unit <b>1801</b>, a first delay <b>1802</b>, a conjugator <b>1803</b>, a multiplier <b>1804</b>, an accumulator (adder) <b>1805</b>, a phase detector <b>1806</b>, a second delay <b>1807</b>, and a subtractor <b>1808</b>. The first delay <b>1802</b> delays for one data block and the second delay <b>1807</b> delays for 1/4 data block. One data block includes a frequency response of a sequence of N known data symbol sequences. When a known data region is known and the data symbols are received, the FFT unit <b>1801</b> converts complex values of consecutive N known data symbol sequences into complex values in the frequency domain. The first delay <b>1802</b> delays the frequency domain complex values for a time corresponding to one data block, and the conjugator <b>1803</b> generate conjugate values of the delayed complex values. The multiplier <b>1804</b> multiplies the current block of known data outputted from the FFT unit <b>1801</b> with the previous block of known data outputted from the conjugator <b>1803</b>. The output of the multiplier <b>1804</b> represents frequency region correlation values within a known data block.
0375Since the complex VSB data exist only on a half of the frequency domain, the accumulator <b>1805</b> divides a data region in the known data block into two sub-regions, and accumulates correlation values for each sub-region. The phase detector <b>1806</b> detects a phase of the accumulated correlation value for each sub-region. The second delay <b>1807</b> delays the detected phase for a time corresponding to a 1/4 data block. The subtractor <b>1808</b> obtains a phase difference between the delayed phase and the phase outputted from the accumulator <b>1806</b> and outputs the phase difference as a timing frequency error.
0376In the method of calculating a timing error by using a peak of correlation between the reference known data and the received known data in the time domain, the contribution of the correlation values may affect a channel when the channel is a multi path channel. However, this can be greatly eliminated if the timing error is obtained using the correlation between two received known data. In addition, the timing error can be detected using an entire portion of the known data sequence inserted by the transmitting system, or it can be detected using a portion of the known data sequence which is robust to random or noise data.
0377Meanwhile, the DC remover <b>1070</b> removes pilot tone signal (i.e., DC signal), which has been inserted by the transmitting system, from the matched-filtered signal. Thereafter, the DC remover <b>1070</b> outputs the processed signal to the phase compensator <b>1110</b>.
0378<figref idref="DRAWINGS">FIG. 50</figref> illustrates a detailed block diagram of a DC remover according to an embodiment of the present invention. Herein, identical signal processing processes are performed on each of a real number element (or in-phase (I)) and an imaginary number element (or a quadrature (Q)) of the inputted complex signal, thereby estimating and removing the DC value of each element. In order to do so, the DC remover shown in <figref idref="DRAWINGS">FIG. 50</figref> includes a first DC estimator and remover <b>1900</b> and a second DC estimator and remover <b>1950</b>. Herein, the first DC estimator and remover <b>1900</b> includes an R sample buffer <b>1901</b>, a DC estimator <b>1902</b>, an M sample holder <b>1903</b>, a C sample delay <b>1904</b>, and a subtractor <b>1905</b>. Herein, the first DC estimator and remover <b>1900</b> estimates and removes the DC of the real number element (i.e., an in-phase DC). Furthermore, the second DC estimator and remover <b>1950</b> includes an R sample buffer <b>1951</b>, a DC estimator <b>1952</b>, an M sample holder <b>1953</b>, a C sample delay <b>1954</b>, and a subtractor <b>1955</b>. The second DC estimator and remover <b>1950</b> estimates and removes the DC of the imaginary number element (i.e., a quadrature DC). In the present invention, the first DC estimator and remover <b>1900</b> and the second DC estimator and remover <b>1950</b> may receive different input signals. However, each DC estimator and remover <b>1900</b> and <b>1950</b> has the same structure. Therefore, a detailed description of the first DC estimator and remover <b>1900</b> will be presented herein, and the second DC estimator and remover <b>1950</b> will be omitted for simplicity.
0379More specifically, the in-phase signal matched-filtered by the matched filter <b>1060</b> is inputted to the R sample buffer <b>1901</b> of the first DC estimator and remover <b>1900</b> within the DC remover <b>1070</b> and is then stored. The R sample buffer <b>1901</b> is a buffer having the length of R sample. Herein, the output of the R sample buffer <b>1901</b> is inputted to the DC estimator <b>1902</b> and the C sample delay <b>1904</b>. The DC estimator <b>1902</b> uses the data having the length of R sample, which are outputted from the buffer <b>1901</b>, so as to estimate the DC value by using Equation 8 shown below.
0380<maths id="MATH-US-00003" num="00003"><math overflow="scroll"><mtable><mtr><mtd><mrow><mrow><mi>y</mi><mo></mo><mrow><mo>[</mo><mi>n</mi><mo>]</mo></mrow></mrow><mo>=</mo><mrow><mfrac><mn>1</mn><mi>R</mi></mfrac><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><munderover><mo>∑</mo><mrow><mi>k</mi><mo>=</mo><mn>0</mn></mrow><mrow><mi>R</mi><mo>-</mo><mn>1</mn></mrow></munderover><mo></mo><mrow><mi>x</mi><mo></mo><mrow><mo>[</mo><mrow><mi>k</mi><mo>+</mo><mrow><mi>M</mi><mo>*</mo><mi>n</mi></mrow></mrow><mo>]</mo></mrow></mrow></mrow></mrow></mrow></mtd><mtd><mrow><mi>Equation</mi><mo></mo><mstyle><mspace width="0.8em" height="0.8ex" /></mstyle><mo></mo><mn>8</mn></mrow></mtd></mtr></mtable></math></maths><img file="USRE46728E_D0013.tif" /><img file="USRE46728E_D0014.tif" /><img file="USRE46728E_D0015.tif" /><img file="USRE46728E_D0016.tif" /><img file="USRE46728E_D0017.tif" /><img file="USRE46728E_D0018.tif" />
0381In the above-described Equation 8, x[n] represents the inputted sample data stored in the buffer <b>1901</b>. And, y[n] indicates the DC estimation value. More specifically, the DC estimator <b>1902</b> accumulates R number of sample data stored in the buffer <b>1901</b> and estimates the DC value by dividing the accumulated value by R. At this point, the stored input sample data set is shifted as much as M sample. Herein, the DC estimation value is outputted once every M samples.
0382<figref idref="DRAWINGS">FIG. 51</figref> illustrates a shifting of the input sample data used for DC estimation. For example, when M is equal to 1 (i.e., M=1), the DC estimator <b>1902</b> estimates the DC value each time a sample is shifted to the buffer <b>1901</b>. Accordingly, each estimated result is outputted for each sample. If M is equal to R (i.e., M=R), the DC estimator <b>1902</b> estimates the DC value each time R number of samples are shifted to the buffer <b>1901</b>. Accordingly, each estimated result is outputted for each cycle of R samples. Therefore, in this case, the DC estimator <b>1902</b> corresponds to a DC estimator that operates in a block unit of R samples. Herein, any value within the range of 1 and R may correspond to the value M.
0383As described above, since the output of the DC estimator <b>1902</b> is outputted after each cycle of M samples, the M sample holder <b>1903</b> holds the DC value estimated from the DC estimator <b>1902</b> for a period of M samples. Then, the estimated DC value is outputted to the subtractor <b>1905</b>. Also, the C sample delay <b>1904</b> delays the input sample data stored in the buffer <b>1901</b> by C samples, which are then outputted to the subtractor <b>1905</b>. The subtractor <b>1905</b> subtracts the output of the M sample holder <b>1903</b> from the output of the C sample delay <b>1904</b>. Thereafter, the subtractor <b>1905</b> outputs the signal having the in-phase DC removed.
0384Herein, the C sample delay <b>1904</b> decides which portion of the input sample data is to be compensated with the output of the DC estimator <b>1902</b>. More specifically, the DC estimator and remover <b>1900</b> may be divided into a DC estimator <b>1902</b> for estimating the DC and the subtractor for compensating the input sample data within the estimated DC value. At this point, the C sample delay <b>1904</b> decides which portion of the input sample data is to be compensated with the estimated DC value. For example, when C is equal to 0 (i.e., C=0), the beginning of the R samples is compensated with the estimated DC value obtained by using R samples. Alternatively, when C is equal to R (i.e., C=R), the end of the R samples is compensated with the estimated DC value obtained by using R samples. Similarly, the data having the DC removed are inputted to the buffer <b>1111</b> and the frequency offset estimator <b>1112</b> of the phase compensator <b>1110</b>.
0385Meanwhile, <figref idref="DRAWINGS">FIG. 52</figref> illustrates a detailed block diagram of a DC remover according to another embodiment of the present invention. Herein, identical signal processing processes are performed on each of a real number element (or in-phase (I)) and an imaginary number element (or a quadrature (Q)) of the inputted complex signal, thereby estimating and removing the DC value of each element. In order to do so, the DC remover shown in <figref idref="DRAWINGS">FIG. 52</figref> includes a first DC estimator and remover <b>2100</b> and a second DC estimator and remover <b>2150</b>. <figref idref="DRAWINGS">FIG. 52</figref> corresponds to an infinite impulse response (IIR) structure.
0386Herein, the first DC estimator and remover <b>2100</b> includes a multiplier <b>2101</b>, an adder <b>2102</b>, an 1 sample delay <b>2103</b>, a multiplier <b>2104</b>, a C sample delay <b>2105</b>, and a subtractor <b>2106</b>. Also, the second DC estimator and remover <b>2150</b> includes a multiplier <b>2151</b>, an adder <b>2152</b>, an 1 sample delay <b>2153</b>, a multiplier <b>2154</b>, a C sample delay <b>2155</b>, and a subtractor <b>2156</b>. In the present invention, the first DC estimator and remover <b>2100</b> and the second DC estimator and remover <b>2150</b> may receive different input signals. However, each DC estimator and remover <b>2100</b> and <b>2150</b> has the same structure. Therefore, a detailed description of the first DC estimator and remover <b>2100</b> will be presented herein, and the second DC estimator and remover <b>2150</b> will be omitted for simplicity.
0387More specifically, the in-phase signal matched-filtered by the matched filter <b>1060</b> is inputted to the multiplier <b>2101</b> and the C sample delay <b>2105</b> of the first DC estimator and remover <b>2100</b> within the DC remover <b>1070</b>. The multiplier <b>2101</b> multiplies a pre-determined constant a to the in-phase signal that is being inputted. Then, the multiplier <b>2101</b> outputs the multiplied result to the adder <b>2102</b>. The adder <b>2102</b> adds the output of the multiplier <b>2101</b> to the output of the multiplier <b>2104</b> that is being fed-back. Thereafter, the adder <b>2102</b> outputs the added result to the 1 sample delay <b>2103</b> and the subtractor <b>2106</b>. More specifically, the output of the adder <b>2102</b> corresponds to the estimated in-phase DC value.
0388The 1 sample delay <b>2103</b> delays the estimated DC value by 1 sample and outputs the DC value delayed by 1 sample to the multiplier <b>2104</b>. The multiplier <b>2104</b> multiplies a pre-determined constant (1−α) to the DC value delayed by 1 sample. Then, the multiplier <b>2104</b> feeds-back the multiplied result to the adder <b>2102</b>.
0389Subsequently, the C sample delay <b>2105</b> delays the in-phase sample data by C samples and, then, outputs the delayed in-phase sample data to the subtractor <b>2106</b>. The subtractor <b>2106</b> subtracts the output of the adder <b>2102</b> from the output of the C sample delay <b>2105</b>, thereby outputting the signal having the in-phase DC removed therefrom.
0390Similarly, the data having the DC removed are inputted to the buffer <b>1111</b> and the frequency offset estimator <b>1112</b> of the phase compensator <b>1110</b> of <figref idref="DRAWINGS">FIG. 39</figref>.
0391The frequency offset estimator <b>1112</b> uses the known sequence position indicator outputted from the known sequence detector and initial frequency offset estimator <b>1004</b>-<b>1</b> in order to estimate the frequency offset from the known data sequence that is being inputted, the known data sequence having the DC removed by the DC remover <b>1070</b>. Then, the frequency offset estimator <b>1112</b> outputs the estimated frequency offset to the holder <b>1113</b>. Similarly, the frequency offset estimation value is obtained at each repetition cycle of the known data sequence.
0392Therefore, the holder <b>1113</b> holds the frequency offset estimation value during a cycle period of the known data sequence and then outputs the frequency offset estimation value to the NCO <b>1114</b>. The NCO <b>1114</b> generates a complex signal corresponding to the frequency offset held by the holder <b>1113</b> and outputs the generated complex signal to the multiplier <b>1115</b>.
0393The multiplier <b>1115</b> multiplies the complex signal outputted from the NCO <b>1114</b> to the data being delayed by a set period of time in the buffer <b>1111</b>, thereby compensating the phase change included in the delayed data. The data having the phase change compensated by the multiplier <b>1115</b> pass through the decimator <b>1200</b> so as to be inputted to the equalizer <b>1003</b>. At this point, since the frequency offset estimated by the frequency offset estimator <b>1112</b> of the phase compensator <b>1110</b> does not pass through the loop filter, the estimated frequency offset indicates the phase difference between the known data sequences. In other words, the estimated frequency offset indicates a phase offset.
0000Channel Equalizer
0394The demodulated data using the known data in the demodulator <b>1002</b> is inputted to the channel equalizer <b>1003</b>. The demodulated data is inputted to the known sequence detector <b>1004</b>.
0395The equalizer <b>1003</b> may perform channel equalization by using a plurality of methods. An example of estimating a channel impulse response (CIR) so as to perform channel equalization will be given in the description of the present invention. Most particularly, an example of estimating the CIR in accordance with each region within the data group, which is hierarchically divided and transmitted from the transmitting system, and applying each CIR differently will also be described herein. Furthermore, by using the known data, the place and contents of which is known in accordance with an agreement between the transmitting system and the receiving system, and/or the field synchronization data, so as to estimate the CIR, the present invention may be able to perform channel equalization with more stability.
0396Herein, the data group that is inputted for the equalization process is divided into regions A to D, as shown in <figref idref="DRAWINGS">FIG. 5</figref>. More specifically, in the example of the present invention, each region A, B, C, and D are further divided into MPH blocks B<b>4</b> to B<b>7</b>, MPH blocks B<b>3</b> and B<b>8</b>, MPH blocks B<b>2</b> and B<b>9</b>, MPH blocks B<b>1</b> and B<b>10</b>, respectively.
0397More specifically, a data group can be assigned and transmitted a maximum the number of 4 in a VSB frame in the transmitting system. In this case, all data group do not include field synchronization data. In the present invention, the data group including the field synchronization data performs channel-equalization using the field synchronization data and known data. And the data group not including the field synchronization data performs channel-equalization using the known data. For example, the data of the MPH block B<b>3</b> including the field synchronization data performs channel-equalization using the CIR calculated from the field synchronization data area and the CIR calculated from the first known data area. Also, the data of the MPH blocks B<b>1</b> and B<b>2</b> performs channel-equalization using the CIR calculated from the field synchronization data area and the CIR calculated from the first known data area. Meanwhile, the data of the MPH blocks B<b>4</b> to B<b>6</b> not including the field synchronization data performs channel-equalization using CIRS calculated from the first known data area and the third known data area.
0398As described above, the present invention uses the CIR estimated from the field synchronization data and the known data sequences in order to perform channel equalization on data within the data group. At this point, each of the estimated CIRs may be directly used in accordance with the characteristics of each region within the data group. Alternatively, a plurality of the estimated CIRs may also be either interpolated or extrapolated so as to create a new CIR, which is then used for the channel equalization process.
0399Herein, when a value F(Q) of a function F(x) at a particular point Q and a value F(S) of the function F(x) at another particular point S are known, interpolation refers to estimating a function value of a point within the section between points Q and S. Linear interpolation corresponds to the simplest form among a wide range of interpolation operations. The linear interpolation described herein is merely exemplary among a wide range of possible interpolation methods. And, therefore, the present invention is not limited only to the examples set forth herein.
0400Alternatively, when a value F(Q) of a function F(x) at a particular point Q and a value F(S) of the function F(x) at another particular point S are known, extrapolation refers to estimating a function value of a point outside of the section between points Q and S. Linear extrapolation is the simplest form among a wide range of extrapolation operations. Similarly, the linear extrapolation described herein is merely exemplary among a wide range of possible extrapolation methods. And, therefore, the present invention is not limited only to the examples set forth herein.
0401<figref idref="DRAWINGS">FIG. 53</figref> illustrates a block diagram of a channel equalizer according to another embodiment of the present invention. Herein, by estimating and compensating a remaining carrier phase error from a channel-equalized signal, the receiving system of the present invention may be enhanced. Referring to <figref idref="DRAWINGS">FIG. 53</figref>, the channel equalizer includes a first frequency domain converter <b>3100</b>, a channel estimator <b>3110</b>, a second frequency domain converter <b>3121</b>, a coefficient calculator <b>3122</b>, a distortion compensator <b>3130</b>, a time domain converter <b>3140</b>, a remaining carrier phase error remover <b>3150</b>, a noise canceller (NC) <b>3160</b>, and a decision unit <b>3170</b>.
0402Herein, the first frequency domain converter <b>3100</b> includes an overlap unit <b>3101</b> overlapping inputted data, and a fast fourier transform (FFT) unit <b>3102</b> converting the data outputted from the overlap unit <b>3101</b> to frequency domain data.
0403The channel estimator <b>3110</b> includes a CIR estimator, a phase compensator <b>3112</b>, a pre-CIR cleaner <b>3113</b>, CIR interpolator/extrapolator <b>3114</b>, a post-CIR cleaner, and a zero-padding unit.
0404The second frequency domain converter <b>3121</b> includes a fast fourier transform (FFT) unit converting the CIR being outputted from the channel estimator <b>3110</b> to frequency domain CIR.
0405The time domain converter <b>3140</b> includes an IFFT unit <b>3141</b> converting the data having the distortion compensated by the distortion compensator <b>3130</b> to time domain data, and a save unit <b>3142</b> extracting only valid data from the data outputted from the IFFT unit <b>3141</b>.
0406The remaining carrier phase error remover <b>3150</b> includes an error compensator <b>3151</b> removing the remaining carrier phase error included in the channel equalized data, and a remaining carrier phase error estimator <b>3152</b> using the channel equalized data and the decision data of the decision unit <b>3170</b> so as to estimate the remaining carrier phase error, thereby outputting the estimated error to the error compensator <b>3151</b>. Herein, any device performing complex number multiplication may be used as the distortion compensator <b>3130</b> and the error compensator <b>3151</b>.
0407At this point, since the received data correspond to data modulated to VSB type data, 8-level scattered data exist only in the real number element. Therefore, referring to <figref idref="DRAWINGS">FIG. 53</figref>, all of the signals used in the noise canceller <b>3160</b> and the decision unit <b>3170</b> correspond to real number (or in-phase) signals. However, in order to estimate and compensate the remaining carrier phase error and the phase noise, both real number (in-phase) element and imaginary number (quadrature) element are required. Therefore, the remaining carrier phase error remover <b>3150</b> receives and uses the quadrature element as well as the in-phase element. Generally, prior to performing the channel equalization process, the demodulator <b>902</b> within the receiving system performs frequency and phase recovery of the carrier. However, if a remaining carrier phase error that is not sufficiently compensated is inputted to the channel equalizer, the performance of the channel equalizer may be deteriorated. Particularly, in a dynamic channel environment, the remaining carrier phase error may be larger than in a static channel environment due to the frequent and sudden channel changes. Eventually, this acts as an important factor that deteriorates the receiving performance of the present invention.
0408Furthermore, a local oscillator (not shown) included in the receiving system should preferably include a single frequency element. However, the local oscillator actually includes the desired frequency elements as well as other frequency elements. Such unwanted (or undesired) frequency elements are referred to as phase noise of the local oscillator. Such phase noise also deteriorates the receiving performance of the present invention. It is difficult to compensate such remaining carrier phase error and phase noise from the general channel equalizer. Therefore, the present invention may enhance the channel equaling performance by including a carrier recovery loop (i.e., a remaining carrier phase error remover <b>3150</b>) in the channel equalizer, as shown in <figref idref="DRAWINGS">FIG. 53</figref>, in order to remove the remaining carrier phase error and the phase noise.
0409More specifically, the receiving data demodulated in <figref idref="DRAWINGS">FIG. 53</figref> are overlapped by the overlap unit <b>3101</b> of the first frequency domain converter <b>3100</b> at a pre-determined overlapping ratio, which are then outputted to the FFT unit <b>3102</b>. The FFT unit <b>3102</b> converts the overlapped time domain data to overlapped frequency domain data through by processing the data with FFT. Then, the converted data are outputted to the distortion compensator <b>3130</b>.
0410The distortion compensator <b>3130</b> performs a complex number multiplication on the overlapped frequency domain data outputted from the FFT unit <b>3102</b> included in the first frequency domain converter <b>3100</b> and the equalization coefficient calculated from the coefficient calculator <b>3122</b>, thereby compensating the channel distortion of the overlapped data outputted from the FFT unit <b>3102</b>. Thereafter, the compensated data are outputted to the IFFT unit <b>3141</b> of the time domain converter <b>3140</b>. The IFFT unit <b>3141</b> performs IFFT on the overlapped data having the channel distortion compensated, thereby converting the overlapped data to time domain data, which are then outputted to the error compensator <b>3151</b> of the remaining carrier phase error remover <b>3150</b>.
0411The error compensator <b>3151</b> multiplies a signal compensating the estimated remaining carrier phase error and phase noise with the valid data extracted from the time domain. Thus, the error compensator <b>3151</b> removes the remaining carrier phase error and phase noise included in the valid data.
0412The data having the remaining carrier phase error compensated by the error compensator <b>3151</b> are outputted to the remaining carrier phase error estimator <b>3152</b> in order to estimate the remaining carrier phase error and phase noise and, at the same time, outputted to the noise canceller <b>3160</b> in order to remove (or cancel) the noise.
0413The remaining carrier phase error estimator <b>3152</b> uses the output data of the error compensator <b>3151</b> and the decision data of the decision unit <b>3170</b> to estimate the remaining carrier phase error and phase noise. Thereafter, the remaining carrier phase error estimator <b>3152</b> outputs a signal for compensating the estimated remaining carrier phase error and phase noise to the error compensator <b>3151</b>. In this embodiment of the present invention, an inverse number of the estimated remaining carrier phase error and phase noise is outputted as the signal for compensating the remaining carrier phase error and phase noise.
0414<figref idref="DRAWINGS">FIG. 54</figref> illustrates a detailed block diagram of the remaining carrier phase error estimator <b>3152</b> according to an embodiment of the present invention. Herein, the remaining carrier phase error estimator <b>3152</b> includes a phase error detector <b>3211</b>, a loop filter <b>3212</b>, a numerically controlled oscillator (NCO) <b>3213</b>, and a conjugator <b>3214</b>. Referring to <figref idref="DRAWINGS">FIG. 54</figref>, the decision data, the output of the phase error detector <b>3211</b>, and the output of the loop filter <b>3212</b> are all real number signals. And, the output of the error compensator <b>3151</b>, the output of the NCO <b>3213</b>, and the output of the conjugator <b>3214</b> are all complex number signals.
0415The phase error detector <b>3211</b> receives the output data of the error compensator <b>3151</b> and the decision data of the decision unit <b>3170</b> in order to estimate the remaining carrier phase error and phase noise. Then, the phase error detector <b>3211</b> outputs the estimated remaining carrier phase error and phase noise to the loop filter.
0416The loop filter <b>3212</b> then filters the remaining carrier phase error and phase noise, thereby outputting the filtered result to the NCO <b>3213</b>. The NCO <b>3213</b> generates a cosine corresponding to the filtered remaining carrier phase error and phase noise, which is then outputted to the conjugator <b>3214</b>.
0417The conjugator <b>3214</b> calculates the conjugate value of the cosine wave generated by the NCO <b>3213</b>. Thereafter, the calculated conjugate value is outputted to the error compensator <b>3151</b>. At this point, the output data of the conjugator <b>3214</b> becomes the inverse number of the signal compensating the remaining carrier phase error and phase noise. In other words, the output data of the conjugator <b>3214</b> becomes the inverse number of the remaining carrier phase error and phase noise.
0418The error compensator <b>3151</b> performs complex number multiplication on the equalized data outputted from the time domain converter <b>3140</b> and the signal outputted from the conjugator <b>3214</b> and compensating the remaining carrier phase error and phase noise, thereby removing the remaining carrier phase error and phase noise included in the equalized data. Meanwhile, the phase error detector <b>3211</b> may estimate the remaining carrier phase error and phase noise by using diverse methods and structures. According to this embodiment of the present invention, the remaining carrier phase error and phase noise are estimated by using a decision-directed method.
0419If the remaining carrier phase error and phase noise are not included in the channel-equalized data, the decision-directed phase error detector according to the present invention uses the fact that only real number values exist in the correlation values between the channel-equalized data and the decision data. More specifically, if the remaining carrier phase error and phase noise are not included, and when the input data of the phase error detector <b>3211</b> are referred to as x<sub>i</sub>+jx<sub>q</sub>, the correlation value between the input data of the phase error detector <b>3211</b> and the decision data may be obtained by using Equation 9 shown below: <br />E{(x<sub>i</sub>+jx<sub>q</sub>)({circumflex over (x)}<sub>i</sub>+j{circumflex over (x)}<sub>q</sub>)*} Equation 9
0420At this point, there is no correlation between x<sub>i </sub>and x<sub>q</sub>. Therefore, the correlation value between x<sub>i </sub>and x<sub>q </sub>is equal to 0. Accordingly, if the remaining carrier phase error and phase noise are not included, only the real number values exist herein. However, if the remaining carrier phase error and phase noise are included, the real number element is shown in the imaginary number value, and the imaginary number element is shown in the real number value. Thus, in this case, the imaginary number element is shown in the correlation value. Therefore, it can be assumed that the imaginary number portion of the correlation value is in proportion with the remaining carrier phase error and phase noise. Accordingly, as shown in Equation 10 below, the imaginary number of the correlation value may be used as the remaining carrier phase error and phase noise. <br />Phase Error=imag{(x<sub>i</sub>+jx<sub>q</sub>)({circumflex over (x)}<sub>i</sub>+j{circumflex over (x)}<sub>q</sub>)*}<br />Phase Error=x<sub>q</sub>{circumflex over (x)}<sub>i</sub>−x<sub>i</sub>{circumflex over (x)}<sub>q </sub> Equation 10
0421<figref idref="DRAWINGS">FIG. 55</figref> illustrates a block diagram of a phase error detector <b>3211</b> obtaining the remaining carrier phase error and phase noise. Herein, the phase error detector <b>3211</b> includes a Hilbert converter <b>3311</b>, a complex number configurator <b>3312</b>, a conjugator <b>3313</b>, a multiplier <b>3314</b>, and a phase error output <b>3315</b>. More specifically, the Hilbert converter <b>3311</b> creates an imaginary number decision data {circumflex over (x)}<sub>q </sub>by performing a Hilbert conversion on the decision value {circumflex over (x)}<sub>i </sub>of the decision unit <b>3170</b>. The generated imaginary number decision value is then outputted to the complex number configurator <b>3312</b>. The complex number configurator <b>3312</b> uses the decision data {circumflex over (x)}<sub>i </sub>and {circumflex over (x)}<sub>q </sub>to configure the complex number decision data {circumflex over (x)}<sub>i</sub>+j{circumflex over (x)}<sub>q</sub>, which are then outputted to the conjugator <b>3313</b>. The conjugator <b>3313</b> conjugates the output of the complex number configurator <b>3312</b>, thereby outputting the conjugated value to the multiplier <b>3314</b>. The multiplier <b>3314</b> performs a complex number multiplication on the output data of the error compensator <b>3151</b> and the output data {circumflex over (x)}<sub>i</sub>−j{circumflex over (x)}<sub>q </sub>of the conjugator <b>3313</b>, thereby obtaining the correlation between the output data x<sub>i</sub>+jx<sub>q </sub>of the error compensator <b>3151</b> and the decision value {circumflex over (x)}<sub>i</sub>−j{circumflex over (x)}<sub>q </sub>of the decision unit <b>3170</b>. The correlation data obtained from the multiplier <b>3314</b> are then inputted to the phase error output <b>3315</b>. The phase error output <b>3315</b> outputs the imaginary number portion x<sub>q</sub>{circumflex over (x)}<sub>i</sub>−x<sub>i</sub>{circumflex over (x)}<sub>q </sub>of the correlation data outputted from the multiplier <b>3314</b> as the remaining carrier phase error and phase noise.
0422The phase error detector shown in <figref idref="DRAWINGS">FIG. 55</figref> is an example of a plurality of phase error detecting methods. Therefore, other types of phase error detectors may be used in the present invention. Therefore, the present invention is not limited only to the examples and embodiments presented in the description of the present invention. Furthermore, according to another embodiment of the present invention, at least 2 phase error detectors are combined so as to detect the remaining carrier phase error and phase noise.
0423Accordingly, the output of the remaining carrier phase error remover <b>3150</b> having the detected remaining carrier phase error and phase noise removed as described above, is configured of an addition of the original (or initial) signal having the channel equalization, the remaining carrier phase error and phase noise, and the signal corresponding to a white noise being amplified to a colored noise during the channel equalization.
0424Therefore, the noise canceller <b>3160</b> receives the output data of the remaining carrier phase error remover <b>3150</b> and the decision data of the decision unit <b>3170</b>, thereby estimating the colored noise. Then, the noise canceller <b>3160</b> subtracts the estimated colored noise from the data having the remaining carrier phase error and phase noise removed therefrom, thereby removing the noise amplified during the equalization process.
0425In order to do so, the noise canceller <b>3160</b> includes a subtractor and a noise predictor. More specifically, the subtractor subtracts the noise predicted by the noise predictor from the output data of the residual carrier phase error estimator <b>3150</b>. Then, the subtractor outputs the signal from which amplified noise is cancelled (or removed) for data recovery and, simultaneously, outputs the same signal to the decision unit <b>3170</b>. The noise predictor calculates a noise element by subtracting the output of the decision unit <b>3170</b> from the signal having residual carrier phase error removed therefrom by the residual carrier phase error estimator <b>3150</b>. Thereafter, the noise predictor uses the calculated noise element as input data of a filter included in the noise predictor. Also, the noise predictor uses the filter (not shown) in order to predict any color noise element included in the output symbol of the residual carrier phase error estimator <b>3150</b>. Accordingly, the noise predictor outputs the predicted color noise element to the subtractor.
0426The data having the noise removed (or cancelled) by the noise canceller <b>3160</b> are outputted for the data decoding process and, at the same time, outputted to the decision unit <b>3170</b>.
0427The decision unit <b>3170</b> selects one of a plurality of pre-determined decision data sets (e.g., 8 decision data sets) that is most approximate to the output data of the noise canceller <b>3160</b>, thereby outputting the selected data to the remaining carrier phase error estimator <b>3152</b> and the noise canceller <b>3160</b>.
0428Meanwhile, the received data are inputted to the overlap unit <b>3101</b> of the first frequency domain converter <b>3100</b> included in the channel equalizer and, at the same time, inputted to the CIR estimator <b>3111</b> of the channel estimator <b>3110</b>.
0429The CIR estimator <b>3111</b> uses a training sequence, for example, data being inputted during the known data section and the known data in order to estimate the CIR, thereby outputting the estimated CIR to the phase compensator <b>3112</b>. If the data to be channel-equalizing is the data within the data group including field synchronization data, the training sequence using in the CIR estimator <b>3111</b> may become the field synchronization data and known data. Meanwhile, if the data to be channel-equalizing is the data within the data group not including field synchronization data, the training sequence using in the CIR estimator <b>3111</b> may become only the known data.
0430For example, the CIR estimator <b>3111</b> estimates CIR using the known data correspond to reference known data generated during the known data section by the receiving system in accordance with an agreement between the receiving system and the transmitting system. For this, the CIR estimator <b>3111</b> is provided known data position information from the known sequence detector <b>1004</b>. Also the CIR estimator <b>3111</b> may be provided field synchronization position information from the known sequence detector <b>1004</b>.
0431Furthermore, in this embodiment of the present invention, the CIR estimator <b>3111</b> estimates the CIR by using the least square (LS) method.
0432The LS estimation method calculates a cross correlation value p between the known data that have passed through the channel during the known data section and the known data that are already known by the receiving end. Then, a cross correlation matrix R of the known data is calculated. Subsequently, a matrix operation is performed on R<sup>−1</sup>·p so that the cross correlation portion within the cross correlation value p between the received data and the initial known data, thereby estimating the CIR of the transmission channel.
0433The phase compensator <b>3112</b> compensates the phase change of the estimated CIR. Then, the phase compensator <b>3112</b> outputs the compensated CIR to the linear interpolator <b>3113</b>. At this point, the phase compensator <b>3112</b> may compensate the phase change of the estimated CIR by using a maximum likelihood method.
0434More specifically, the remaining carrier phase error and phase noise that are included in the demodulated received data and, therefore, being inputted change the phase of the CIR estimated by the CIR estimator <b>3111</b> at a cycle period of one known data sequence. At this point, if the phase change of the inputted CIR, which is to be used for the linear interpolation process, is not performed in a linear form due to a high rate of the phase change, the channel equalizing performance of the present invention may be deteriorated when the channel is compensated by calculating the equalization coefficient from the CIR, which is estimated by a linear interpolation method.
0435Therefore, the present invention removes (or cancels) the amount of phase change of the CIR estimated by the CIR estimator <b>3111</b> so that the distortion compensator <b>3130</b> allows the remaining carrier phase error and phase noise to bypass the distortion compensator <b>3130</b> without being compensated. Accordingly, the remaining carrier phase error and phase noise are compensated by the remaining carrier phase error remover <b>3150</b>.
0436For this, the present invention removes (or cancels) the amount of phase change of the CIR estimated by the phase compensator <b>3112</b> by using a maximum likelihood method.
0437The basic idea of the maximum likelihood method relates to estimating a phase element mutually (or commonly) existing in all CIR elements, then to multiply the estimated CIR with an inverse number of the mutual (or common) phase element, so that the channel equalizer, and most particularly, the distortion compensator <b>3130</b> does not compensate the mutual phase element.
0438More specifically, when the mutual phase element is referred to as θ, the phase of the newly estimated CIR is rotated by θ as compared to the previously estimated CIR. When the CIR of a point t is referred to as h<sub>i</sub>(t), the maximum likelihood phase compensation method obtains a phase θ<sub>ML </sub>corresponding to when h<sub>i</sub>(t) is rotated by θ, the squared value of the difference between the CIR of h<sub>i</sub>(t) and the CIR of h<sub>i</sub>(t+1), i.e., the CIR of a point (t+1), becomes a minimum value. Herein, when i represents a tap of the estimated CIR, and when N represents a number of taps of the CIR being estimated by the CIR estimator <b>3111</b>, the value of θ<sub>ML </sub>is equal to or greater than 0 and equal to or less than N−1. This value may be calculated by using Equation 11 shown below:
0439<maths id="MATH-US-00004" num="00004"><math overflow="scroll"><mtable><mtr><mtd><mrow><msub><mi>θ</mi><mi>ML</mi></msub><mo>=</mo><mrow><munder><mi>min</mi><mi>θ</mi></munder><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><munderover><mo>∑</mo><mrow><mi>i</mi><mo>=</mo><mn>0</mn></mrow><mrow><mi>N</mi><mo>-</mo><mn>1</mn></mrow></munderover><mo></mo><msup><mrow><mo></mo><mrow><mrow><mrow><msub><mi>h</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mi>t</mi><mo>)</mo></mrow></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><msup><mi>e</mi><mrow><mi>j</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>θ</mi></mrow></msup></mrow><mo>-</mo><mrow><msub><mi>h</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mrow><mi>t</mi><mo>+</mo><mn>1</mn></mrow><mo>)</mo></mrow></mrow></mrow><mo></mo></mrow><mn>2</mn></msup></mrow></mrow></mrow></mtd><mtd><mrow><mi>Equation</mi><mo></mo><mstyle><mspace width="0.8em" height="0.8ex" /></mstyle><mo></mo><mn>11</mn></mrow></mtd></mtr></mtable></math></maths><img file="USRE46728E_D0019.tif" /><img file="USRE46728E_D0020.tif" /><img file="USRE46728E_D0021.tif" /><img file="USRE46728E_D0022.tif" /><img file="USRE46728E_D0023.tif" /><img file="USRE46728E_D0024.tif" />
0440Herein, in light of the maximum likelihood method, the mutual phase element θ<sub>ML </sub>is equal to the value of θ, when the right side of Equation 11 being differentiated with respect to θ is equal to 0. The above-described condition is shown in Equation 12 below:
0441<maths id="MATH-US-00005" num="00005"><math overflow="scroll"><mtable><mtr><mtd><mrow><mrow><mfrac><mi>d</mi><mrow><mi>d</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>θ</mi></mrow></mfrac><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><munderover><mo>∑</mo><mrow><mi>i</mi><mo>=</mo><mn>0</mn></mrow><mrow><mi>N</mi><mo>-</mo><mn>1</mn></mrow></munderover><mo></mo><msup><mrow><mo></mo><mrow><mrow><mrow><msub><mi>h</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mi>t</mi><mo>)</mo></mrow></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><msup><mi>e</mi><mrow><mi>j</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>θ</mi></mrow></msup></mrow><mo>-</mo><mrow><msub><mi>h</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mrow><mi>t</mi><mo>+</mo><mn>1</mn></mrow><mo>)</mo></mrow></mrow></mrow><mo></mo></mrow><mn>2</mn></msup></mrow></mrow><mo>=</mo><mrow><mrow><mfrac><mi>d</mi><mrow><mi>d</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>θ</mi></mrow></mfrac><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><munderover><mo>∑</mo><mrow><mi>i</mi><mo>=</mo><mn>0</mn></mrow><mrow><mi>N</mi><mo>-</mo><mn>1</mn></mrow></munderover><mo></mo><mrow><mrow><mo>(</mo><mrow><mrow><mrow><msub><mi>h</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mi>t</mi><mo>)</mo></mrow></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><msup><mi>e</mi><mrow><mi>j</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>θ</mi></mrow></msup></mrow><mo>-</mo><mrow><msub><mi>h</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mrow><mi>t</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo>+</mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mn>1</mn></mrow><mo>)</mo></mrow></mrow></mrow><mo>)</mo></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><msup><mrow><mo>(</mo><mrow><mrow><mrow><msub><mi>h</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mi>t</mi><mo>)</mo></mrow></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><msup><mi>e</mi><mrow><mi>j</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>θ</mi></mrow></msup></mrow><mo>-</mo><mrow><msub><mi>h</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mrow><mi>t</mi><mo>+</mo><mn>1</mn></mrow><mo>)</mo></mrow></mrow></mrow><mo>)</mo></mrow><mo>*</mo></msup></mrow></mrow></mrow><mo>=</mo><mrow><mrow><mfrac><mi>d</mi><mrow><mi>d</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>θ</mi></mrow></mfrac><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><munderover><mo>∑</mo><mrow><mi>i</mi><mo>=</mo><mn>0</mn></mrow><mrow><mi>N</mi><mo>-</mo><mn>1</mn></mrow></munderover><mo></mo><mrow><mo>{</mo><mrow><msup><mrow><mo></mo><mrow><msub><mi>h</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mi>t</mi><mo>)</mo></mrow></mrow><mo></mo></mrow><mn>2</mn></msup><mo>+</mo><msup><mrow><mo></mo><mrow><msub><mi>h</mi><mrow><mi>i</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo>+</mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mn>1</mn></mrow></msub><mo></mo><mrow><mo>(</mo><mi>t</mi><mo>)</mo></mrow></mrow><mo></mo></mrow><mn>2</mn></msup><mo>-</mo><mrow><mrow><msub><mi>h</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mi>t</mi><mo>)</mo></mrow></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><msubsup><mi>h</mi><mi>i</mi><mo>*</mo></msubsup><mo></mo><mrow><mo>(</mo><mrow><mi>t</mi><mo>+</mo><mn>1</mn></mrow><mo>)</mo></mrow></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><msup><mi>e</mi><mrow><mi>j</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>θ</mi></mrow></msup></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo>-</mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><mrow><msubsup><mi>h</mi><mi>i</mi><mo>*</mo></msubsup><mo></mo><mrow><mo>(</mo><mi>t</mi><mo>)</mo></mrow></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><msub><mi>h</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mrow><mi>t</mi><mo>+</mo><mn>1</mn></mrow><mo>)</mo></mrow></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><msup><mi>e</mi><mrow><mrow><mo>-</mo><mi>j</mi></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>θ</mi></mrow></msup></mrow></mrow><mo>}</mo></mrow></mrow></mrow><mo>=</mo><mrow><mrow><munderover><mo>∑</mo><mrow><mi>i</mi><mo>=</mo><mn>0</mn></mrow><mrow><mi>N</mi><mo>-</mo><mn>1</mn></mrow></munderover><mo></mo><mrow><mo>{</mo><mrow><mrow><mi>j</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><msubsup><mi>h</mi><mi>i</mi><mo>*</mo></msubsup><mo>(</mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>t</mi><mo>)</mo></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><msub><mi>h</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mrow><mi>t</mi><mo>+</mo><mn>1</mn></mrow><mo>)</mo></mrow></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><msup><mi>e</mi><mrow><mrow><mo>-</mo><mi>j</mi></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>θ</mi></mrow></msup></mrow><mo>-</mo><mrow><mi>j</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><msubsup><mi>h</mi><mi>i</mi><mo>*</mo></msubsup><mo></mo><mrow><mo>(</mo><mi>t</mi><mo>)</mo></mrow></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><msub><mi>h</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mrow><mi>t</mi><mo>+</mo><mn>1</mn></mrow><mo>)</mo></mrow></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><msup><mi>e</mi><mrow><mi>j</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>θ</mi></mrow></msup></mrow></mrow><mo>}</mo></mrow></mrow><mo>=</mo><mrow><mrow><mi>j</mi><mo></mo><mrow><munderover><mo>∑</mo><mrow><mi>i</mi><mo>=</mo><mn>0</mn></mrow><mrow><mi>N</mi><mo>-</mo><mn>1</mn></mrow></munderover><mo></mo><mrow><mn>2</mn><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>Im</mi><mo></mo><mrow><mo>{</mo><mrow><mrow><msubsup><mi>h</mi><mi>i</mi><mo>*</mo></msubsup><mo></mo><mrow><mo>(</mo><mi>t</mi><mo>)</mo></mrow></mrow><mo></mo><mrow><msub><mi>h</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mrow><mi>t</mi><mo>+</mo><mn>1</mn></mrow><mo>)</mo></mrow></mrow><mo></mo><msup><mi>e</mi><mrow><mrow><mo>-</mo><mi>j</mi></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>θ</mi></mrow></msup></mrow><mo>}</mo></mrow></mrow></mrow></mrow><mo>=</mo><mn>0</mn></mrow></mrow></mrow></mrow></mrow></mtd><mtd><mrow><mi>Equation</mi><mo></mo><mstyle><mspace width="0.8em" height="0.8ex" /></mstyle><mo></mo><mn>12</mn></mrow></mtd></mtr></mtable></math></maths><img file="USRE46728E_D0025.tif" /><img file="USRE46728E_D0026.tif" /><img file="USRE46728E_D0027.tif" /><img file="USRE46728E_D0028.tif" /><img file="USRE46728E_D0029.tif" /><img file="USRE46728E_D0030.tif" />
0442The above Equation 12 may be simplified as shown in Equation 13 below:
0443<maths id="MATH-US-00006" num="00006"><math overflow="scroll"><mtable><mtr><mtd><mrow><mrow><mrow><mi>Im</mi><mo></mo><mrow><mo>{</mo><mrow><msup><mi>e</mi><mrow><mrow><mo>-</mo><mi>j</mi></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>θ</mi></mrow></msup><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><munderover><mo>∑</mo><mrow><mi>i</mi><mo>=</mo><mn>0</mn></mrow><mrow><mi>N</mi><mo>-</mo><mn>1</mn></mrow></munderover><mo></mo><mrow><mo>{</mo><mrow><mrow><msubsup><mi>h</mi><mi>i</mi><mo>*</mo></msubsup><mo></mo><mrow><mo>(</mo><mi>t</mi><mo>)</mo></mrow></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><msub><mi>h</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mrow><mi>t</mi><mo>+</mo><mn>1</mn></mrow><mo>)</mo></mrow></mrow></mrow><mo>}</mo></mrow></mrow></mrow><mo>}</mo></mrow></mrow><mo>=</mo><mn>0</mn></mrow><mo></mo><mstyle><mtext></mtext></mstyle><mo></mo><mrow><msub><mi>θ</mi><mi>ML</mi></msub><mo>=</mo><mrow><mi>arg</mi><mo>(</mo><mrow><munderover><mo>∑</mo><mrow><mi>i</mi><mo>=</mo><mn>0</mn></mrow><mrow><mi>N</mi><mo>-</mo><mn>1</mn></mrow></munderover><mo></mo><mrow><mrow><msubsup><mi>h</mi><mi>i</mi><mo>*</mo></msubsup><mo></mo><mrow><mo>(</mo><mi>t</mi><mo>)</mo></mrow></mrow><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><msub><mi>h</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mrow><mi>t</mi><mo>+</mo><mn>1</mn></mrow><mo>)</mo></mrow></mrow></mrow></mrow><mo>)</mo></mrow></mrow></mrow></mtd><mtd><mrow><mi>Equation</mi><mo></mo><mstyle><mspace width="0.8em" height="0.8ex" /></mstyle><mo></mo><mn>13</mn></mrow></mtd></mtr></mtable></math></maths><img file="USRE46728E_D0031.tif" /><img file="USRE46728E_D0032.tif" /><img file="USRE46728E_D0033.tif" /><img file="USRE46728E_D0034.tif" /><img file="USRE46728E_D0035.tif" /><img file="USRE46728E_D0036.tif" />
0444More specifically, Equation 13 corresponds to the θ<sub>ML </sub>value that is to be estimated by the argument of the correlation value between h<sub>i</sub>(t) and h<sub>i</sub>(t+1).
0445<figref idref="DRAWINGS">FIG. 56</figref> illustrates a phase compensator according to an embodiment of the present invention, wherein the mutual phase element θ<sub>ML </sub>is calculated as described above, and wherein the estimated phase element is compensated at the estimated CIR. Referring to <figref idref="DRAWINGS">FIG. 56</figref>, the phase compensator includes a correlation calculator <b>3410</b>, a phase change estimator <b>3420</b>, a compensation signal generator <b>3430</b>, and a multiplier <b>3440</b>.
0446The correlation calculator <b>3410</b> includes a first N symbol buffer <b>3411</b>, an N symbol delay <b>3412</b>, a second N symbol buffer <b>3413</b>, a conjugator <b>3414</b>, and a multiplier <b>3415</b>. More specifically, the first N symbol buffer <b>3411</b> included in the correlation calculator <b>3410</b> is capable of storing the data being inputted from the CIR estimator <b>3111</b> in symbol units to a maximum limit of N number of symbols. The symbol data being temporarily stored in the first N symbol buffer <b>3411</b> are then inputted to the multiplier <b>3415</b> included in the correlation calculator <b>3410</b> and to the multiplier <b>3440</b>.
0447At the same time, the symbol data being outputted from the CIR estimator <b>3111</b> are delayed by N symbols from the N symbol delay <b>3412</b>. Then, the delayed symbol data pass through the second N symbol buffer <b>3413</b> and inputted to the conjugator <b>3414</b>, so as to be conjugated and then inputted to the multiplier <b>3415</b>.
0448The multiplier <b>3415</b> multiplies the output of the first N symbol buffer <b>3411</b> and the output of the conjugator <b>3414</b>. Then, the multiplier <b>3415</b> outputs the multiplied result to an accumulator <b>3421</b> included in the phase change estimator <b>3420</b>.
0449More specifically, the correlation calculator <b>3410</b> calculates a correlation between a current CIR h<sub>i</sub>(t+1) having the length of N and a previous CIR h<sub>i</sub>(t) also having the length of N. then, the correlation calculator <b>3410</b> outputs the calculated correlation value to the accumulator <b>3421</b> of the phase change estimator <b>3420</b>.
0450The accumulator <b>3421</b> accumulates the correlation values outputted from the multiplier <b>3415</b> during an N symbol period. Then, the accumulator <b>3421</b> outputs the accumulated value to the phase detector <b>3422</b>. The phase detector <b>3422</b> then calculates a mutual phase element θ<sub>ML </sub>from the output of the accumulator <b>3421</b> as shown in the above-described Equation 11. Thereafter, the calculated θ<sub>ML </sub>value is outputted to the compensation signal generator <b>3430</b>.
0451The compensation signal generator <b>3430</b> outputs a complex signal e<sup>−jθ</sup><sup><sub2>ML </sub2></sup>having a phase opposite to that of the detected phase as the phase compensation signal to the multiplier <b>3440</b>. The multiplier <b>3440</b> multiplies the current CIR h<sub>i</sub>(t+1) being outputted from the first N symbol buffer <b>3411</b> with the phase compensation signal e<sup>−jθ</sup><sup><sub2>ML</sub2></sup>, thereby removing the amount of phase change of the estimated CIR.
0452The CIR having its phase change compensated, as described above, passes through a first cleaner (or pre-CIR cleaner) <b>3113</b> or bypasses the first cleaner <b>3113</b>, thereby being inputted to a CIR calculator (or CIR interpolator-extrapolator) <b>3114</b>. The CIR interpolator-extrapolator <b>3114</b> either interpolates or extrapolates an estimated CIR, which is then outputted to a second cleaner (or post-CIR cleaner) <b>3115</b>. Herein, the estimated CIR corresponds to a CIR having its phase change compensated. The first cleaner <b>3113</b> may or may not operate depending upon whether the CIR interpolator-extrapolator <b>3114</b> interpolates or extrapolates the estimated CIR. For example, if the CIR interpolator-extrapolator <b>3114</b> interpolates the estimated CIR, the first cleaner <b>3113</b> does not operate. Conversely, if the CIR interpolator-extrapolator <b>3114</b> extrapolates the estimated CIR, the first cleaner <b>3113</b> operates.
0453More specifically, the CIR estimated from the known data includes a channel element that is to be obtained as well as a jitter element caused by noise. Since such jitter element deteriorates the performance of the equalizer, it preferable that a coefficient calculator <b>3122</b> removes the jitter element before using the estimated CIR. Therefore, according to the embodiment of the present invention, each of the first and second cleaners <b>3113</b> and <b>3115</b> removes a portion of the estimated CIR having a power level lower than the predetermined threshold value (i.e., so that the estimated CIR becomes equal to ‘0’). Herein, this removal process will be referred to as a “CIR cleaning” process.
0454The CIR interpolator-extrapolator <b>3114</b> performs CIR interpolation by multiplying a CIR estimated from the CIR estimator <b>3112</b> by a coefficient and by multiplying a CIR having its phase change compensated from the phase compensator (or maximum likelihood phase compensator) <b>3112</b> by another coefficient, thereby adding the multiplied values. At this point, some of the noise elements of the CIR may be added to one another, thereby being cancelled. Therefore, when the CIR interpolator-extrapolator <b>3114</b> performs CIR interpolation, the original (or initial) CIR having noise elements remaining therein. In other words, when the CIR interpolator-extrapolator <b>3114</b> performs CIR interpolation, an estimated CIR having its phase change compensated by the phase compensator <b>3112</b> bypasses the first cleaner <b>3113</b> and is inputted to the CIR interpolator-extrapolator <b>3114</b>. Subsequently, the second cleaner <b>3115</b> cleans the CIR interpolated by the CIR interpolator-extrapolator <b>3114</b>.
0455Conversely, the CIR interpolator-extrapolator <b>3114</b> performs CIR extrapolation by using a difference value between two CIRs, each having its phase change compensated by the phase compensator <b>3112</b>, so as to estimate a CIR positioned outside of the two CIRs. Therefore, in this case, the noise element is rather amplified. Accordingly, when the CIR interpolator-extrapolator <b>3114</b> performs CIR extrapolation, the CIR cleaned by the first cleaner <b>3113</b> is used. More specifically, when the CIR interpolator-extrapolator <b>3114</b> performs CIR extrapolation, the extrapolated CIR passes through the second cleaner <b>3115</b>, thereby being inputted to the zero-padding unit <b>3116</b>.
0456Meanwhile, when a second frequency domain converter (or fast fourier transform (FFT2)) <b>3121</b> converts the CIR, which has been cleaned and outputted from the second cleaner <b>3115</b>, to a frequency domain, the length and of the inputted CIR and the FFT size may not match (or be identical to one another). In other words, the CIR length may be smaller than the FFT size. In this case, the zero-padding unit <b>3116</b> adds a number of zeros ‘0’s corresponding to the difference between the FFT size and the CIR length to the inputted CIR, thereby outputting the processed CIR to the second frequency domain converter (FFT2) <b>3121</b>. Herein, the zero-padded CIR may correspond to one of the interpolated CIR, extrapolated CIR, and the CIR estimated in the known data section.
0457The second frequency domain converter <b>3121</b> performs FFT on the CIR being outputted from the zero padding unit <b>3116</b>, thereby converting the CIR to a frequency domain CIR. Then, the second frequency domain converter <b>3121</b> outputs the converted CIR to the coefficient calculator <b>3122</b>.
0458The coefficient calculator <b>3122</b> uses the frequency domain CIR being outputted from the second frequency domain converter <b>3121</b> to calculate the equalization coefficient. Then, the coefficient calculator <b>3122</b> outputs the calculated coefficient to the distortion compensator <b>3130</b>. Herein, for example, the coefficient calculator <b>3122</b> calculates a channel equalization coefficient of the frequency domain that can provide minimum mean square error (MMSE) from the CIR of the frequency domain, which is outputted to the distortion compensator <b>3130</b>.
0459The distortion compensator <b>3130</b> performs a complex number multiplication on the overlapped data of the frequency domain being outputted from the FFT unit <b>3102</b> of the first frequency domain converter <b>3100</b> and the equalization coefficient calculated by the coefficient calculator <b>3122</b>, thereby compensating the channel distortion of the overlapped data being outputted from the FFT unit <b>3102</b>.
0460<figref idref="DRAWINGS">FIG. 57</figref> illustrates a block diagram of a channel equalizer according to another embodiment of the present invention. In other words, <figref idref="DRAWINGS">FIG. 57</figref> illustrates a block diagram showing another example of a channel equalizer by using different CIR estimation and application methods in accordance with regions A, B, C, and D, when the data group is divided into the structure shown in <figref idref="DRAWINGS">FIG. 5</figref>.
0461More specifically, as shown in <figref idref="DRAWINGS">FIG. 5</figref>, known data that are sufficiently are being periodically transmitted in regions A/B (i.e., MPH blocks B<b>3</b> to B<b>8</b>). Therefore, an indirect equalizing method using the CIR may be used herein. However, in regions C/D (i.e., MPH blocks B<b>1</b>, B<b>2</b>, B<b>9</b>, and B<b>10</b>), the known data are neither able to be transmitted at a sufficiently long length nor able to be periodically and equally transmitted. Therefore, it is inadequate to estimate the CIR by using the known data. Accordingly, in regions C/D, a direct equalizing method in which an error is obtained from the output of the equalizer, so as to update the coefficient.
0462The examples presented in the embodiments of the present invention shown in <figref idref="DRAWINGS">FIG. 57</figref> include a method of performing indirect channel equalization by using a cyclic prefix on the data of regions A/B, and a method of performing direct channel equalization by using an overlap & save method on the data of regions C/D.
0463Accordingly, referring to <figref idref="DRAWINGS">FIG. 57</figref>, the frequency domain channel equalizer includes a frequency domain converter <b>3510</b>, a distortion compensator <b>3520</b>, a time domain converter <b>3530</b>, a first coefficient calculating unit <b>3540</b>, a second coefficient calculating unit <b>3550</b>, and a coefficient selector <b>3560</b>.
0464Herein, the frequency domain converter <b>3510</b> includes an overlap unit <b>3511</b>, a select unit <b>3512</b>, and a first FFT unit <b>3513</b>.
0465The time domain converter <b>3530</b> includes an IFFT unit <b>3531</b>, a save unit <b>3532</b>, and a select unit <b>3533</b>.
0466The first coefficient calculating unit <b>3540</b> includes a CIR estimator <b>3541</b>, an average calculator <b>3542</b>, and second FFT unit <b>3543</b>, and a coefficient calculator <b>3544</b>.
0467The second coefficient calculating unit <b>3550</b> includes a decision unit <b>3551</b>, a select unit <b>3552</b>, a subtractor <b>3553</b>, a zero-padding unit <b>3554</b>, a third FFT unit <b>3555</b>, a coefficient updater <b>3556</b>, and a delay unit <b>3557</b>.
0468Also, a multiplexer (MUX), which selects data that are currently being inputted as the input data depending upon whether the data correspond to regions A/B or to regions C/D, may be used as the select unit <b>3512</b> of the frequency domain converter <b>3510</b>, the select unit <b>3533</b> of the time domain converter <b>3530</b>, and the coefficient selector <b>3560</b>.
0469In the channel equalizer having the above-described structure, as shown in <figref idref="DRAWINGS">FIG. 57</figref>, if the data being inputted correspond to the data of regions A/B, the select unit <b>3512</b> of the frequency domain converter <b>3510</b> selects the input data and not the output data of the overlap unit <b>3511</b>. In the same case, the select unit <b>3533</b> of the time domain converter <b>3530</b> selects the output data of the IFFT unit <b>3531</b> and not the output data of the save unit <b>3532</b>. The coefficient selector <b>3560</b> selects the equalization coefficient being outputted from the first coefficient calculating unit <b>3540</b>.
0470Conversely, if the data being inputted correspond to the data of regions C/D, the select unit <b>3512</b> of the frequency domain converter <b>3510</b> selects the output data of the overlap unit <b>3511</b> and not the input data. In the same case, the select unit <b>3533</b> of the time domain converter <b>3530</b> selects the output data of the save unit <b>3532</b> and not the output data of the IFFT unit <b>3531</b>. The coefficient selector <b>3560</b> selects the equalization coefficient being outputted from the second coefficient calculating unit <b>3550</b>.
0471More specifically, the received data are inputted to the overlap unit <b>3511</b> and select unit <b>3512</b> of the frequency domain converter <b>3510</b>, and to the first coefficient calculating unit <b>3540</b>. If the inputted data correspond to the data of regions A/B, the select unit <b>3512</b> selects the received data, which are then outputted to the first FFT unit <b>3513</b>. On the other hand, if the inputted data correspond to the data of regions C/D, the select unit <b>3512</b> selects the data that are overlapped by the overlap unit <b>3513</b> and are, then, outputted to the first FFT unit <b>3513</b>. The first FFT unit <b>3513</b> performs FFT on the time domain data that are outputted from the select unit <b>3512</b>, thereby converting the time domain data to frequency domain data. Then, the converted data are outputted to the distortion compensator <b>3520</b> and the delay unit <b>3557</b> of the second coefficient calculating unit <b>3550</b>.
0472The distortion compensator <b>3520</b> performs complex multiplication on frequency domain data outputted from the first FFT unit <b>3513</b> and the equalization coefficient outputted from the coefficient selector <b>3560</b>, thereby compensating the channel distortion detected in the data that are being outputted from the first FFT unit <b>3513</b>.
0473Thereafter, the distortion-compensated data are outputted to the IFFT unit <b>3531</b> of the time domain converter <b>3530</b>. The IFFT unit <b>3531</b> of the time domain converter <b>3530</b> performs IFFT on the channel-distortion-compensated data, thereby converting the compensated data to time domain data. The converted data are then outputted to the save unit <b>3532</b> and the select unit <b>3533</b>. If the inputted data correspond to the data of regions A/B, the select unit <b>3533</b> selects the output data of the IFFT unit <b>3531</b>. On the other hand, if the inputted data correspond to regions C/D, the select unit <b>3533</b> selects the valid data extracted from the save unit <b>3532</b>. Thereafter, the selected data are outputted to be decoded and, simultaneously, outputted to the second coefficient calculating unit <b>3550</b>.
0474The CIR estimator <b>3541</b> of the first coefficient calculating unit <b>3540</b> uses the data being received during the known data section and the known data of the known data section, the known data being already known by the receiving system in accordance with an agreement between the receiving system and the transmitting system, in order to estimate the CIR. Subsequently, the estimated CIR is outputted to the average calculator <b>3542</b>. The average calculator <b>3542</b> calculates an average value of the CIRs that are being inputted consecutively. Then, the calculated average value is outputted to the second FFT unit <b>3543</b>. For example, referring to <figref idref="DRAWINGS">FIG. 37</figref>, the average value of the CIR value estimated at point T<b>1</b> and the CIR value estimated at point T<b>2</b> is used for the channel equalization process of the general data existing between point T<b>1</b> and point T<b>2</b>. Accordingly, the calculated average value is outputted to the second FFT unit <b>3543</b>.
0475The second FFT unit <b>3543</b> performs FFT on the CIR of the time domain that is being inputted, so as to convert the inputted CIR to a frequency domain CIR. Thereafter, the converted frequency domain CIR is outputted to the coefficient calculator <b>3544</b>. The coefficient calculator <b>3544</b> calculates a frequency domain equalization coefficient that satisfies the condition of using the CIR of the frequency domain so as to minimize the mean square error. The calculated equalizer coefficient of the frequency domain is then outputted to the coefficient calculator <b>3560</b>.
0476The decision unit <b>3551</b> of the second coefficient calculating unit <b>3550</b> selects one of a plurality of decision values (e.g., 8 decision values) that is most approximate to the equalized data and outputs the selected decision value to the select unit <b>3552</b>. Herein, a multiplexer may be used as the select unit <b>3552</b>. In a general data section, the select unit <b>3552</b> selects the decision value of the decision unit <b>3551</b>. Alternatively, in a known data section, the select unit <b>3552</b> selects the known data and outputs the selected known data to the subtractor <b>3553</b>. The subtractor <b>3553</b> subtracts the output of the select unit <b>3533</b> included in the time domain converter <b>3530</b> from the output of the select unit <b>652</b> so as to calculate (or obtain) an error value. Thereafter, the calculated error value is outputted to the zero-padding unit <b>3554</b>.
0477The zero-padding unit <b>3554</b> adds (or inserts) the same amount of zeros (0) corresponding to the overlapped amount of the received data in the inputted error. Then, the error extended with zeros (0) is outputted to the third FFT unit <b>3555</b>. The third FFT unit <b>3555</b> converts the error of the time domain having zeros (0) added (or inserted) therein, to the error of the frequency domain. Thereafter, the converted error is outputted to the coefficient update unit <b>3556</b>. The coefficient update unit <b>3556</b> uses the received data of the frequency domain that have been delayed by the delay unit <b>3557</b> and the error of the frequency domain so as to update the previous equalization coefficient. Thereafter, the updated equalization coefficient is outputted to the coefficient selector <b>3560</b>.
0478At this point, the updated equalization coefficient is stored so as that it can be used as a previous equalization coefficient in a later process. If the input data correspond to the data of regions A/B, the coefficient selector <b>3560</b> selects the equalization coefficient calculated from the first coefficient calculating unit <b>3540</b>. On the other hand, if the input data correspond to the data of regions C/D, the coefficient selector <b>3560</b> selects the equalization coefficient updated by the second coefficient calculating unit <b>3550</b>. Thereafter, the selected equalization coefficient is outputted to the distortion compensator <b>3520</b>.
0479<figref idref="DRAWINGS">FIG. 58</figref> illustrates a block diagram of a channel equalizer according to another embodiment of the present invention. In other words, <figref idref="DRAWINGS">FIG. 58</figref> illustrates a block diagram showing another example of a channel equalizer by using different CIR estimation and application methods in accordance with regions A, B, C, and D, when the data group is divided into the structure shown in <figref idref="DRAWINGS">FIG. 5</figref>. In this example, a method of performing indirect channel equalization by using an overlap & save method on the data of regions A/B, and a method of performing direct channel equalization by using an overlap & save method on the data of regions C/D are illustrated.
0480Accordingly, referring to <figref idref="DRAWINGS">FIG. 58</figref>, the frequency domain channel equalizer includes a frequency domain converter <b>3610</b>, a distortion compensator <b>3620</b>, a time domain converter <b>3630</b>, a first coefficient calculating unit <b>3640</b>, a second coefficient calculating unit <b>3650</b>, and a coefficient selector <b>3660</b>.
0481Herein, the frequency domain converter <b>3610</b> includes an overlap unit <b>3611</b> and a first FFT unit <b>3612</b>.
0482The time domain converter <b>3630</b> includes an IFFT unit <b>3631</b> and a save unit <b>3632</b>.
0483The first coefficient calculating unit <b>3640</b> includes a CIR estimator <b>3641</b>, an interpolator <b>3642</b>, a second FFT unit <b>3643</b>, and a coefficient calculator <b>3644</b>.
0484The second coefficient calculating unit <b>3650</b> includes a decision unit <b>3651</b>, a select unit <b>3652</b>, a subtractor <b>3653</b>, a zero-padding unit <b>3654</b>, a third FFT unit <b>3655</b>, a coefficient updater <b>3656</b>, and a delay unit <b>3657</b>.
0485Also, a multiplexer (MUX), which selects data that are currently being inputted as the input data depending upon whether the data correspond to regions A/B or to regions C/D, may be used as the coefficient selector <b>3660</b>. More specifically, if the input data correspond to the data of regions A/B, the coefficient selector <b>3660</b> selects the equalization coefficient calculated from the first coefficient calculating unit <b>3640</b>. On the other hand, if the input data correspond to the data of regions C/D, the coefficient selector <b>3660</b> selects the equalization coefficient updated by the second coefficient calculating unit <b>3650</b>.
0486In the channel equalizer having the above-described structure, as shown in <figref idref="DRAWINGS">FIG. 58</figref>, the received data are inputted to the overlap unit <b>3611</b> of the frequency domain converter <b>3610</b> and to the first coefficient calculating unit <b>3640</b>. The overlap unit <b>3611</b> overlaps the input data to a pre-determined overlapping ratio and outputs the overlapped data to the first FFT unit <b>3612</b>. The first FFT unit <b>3612</b> performs FFT on the overlapped time domain data, thereby converting the overlapped time domain data to overlapped frequency domain data. Then, the converted data are outputted to the distortion compensator <b>3620</b> and the delay unit <b>3657</b> of the second coefficient calculating unit <b>3650</b>.
0487The distortion compensator <b>3620</b> performs complex multiplication on the overlapped frequency domain data outputted from the first FFT unit <b>3612</b> and the equalization coefficient outputted from the coefficient selector <b>3660</b>, thereby compensating the channel distortion detected in the overlapped data that are being outputted from the first FFT unit <b>3612</b>. Thereafter, the distortion-compensated data are outputted to the IFFT unit <b>3631</b> of the time domain converter <b>3630</b>. The IFFT unit <b>3631</b> of the time domain converter <b>3630</b> performs IFFT on the distortion-compensated data, thereby converting the compensated data to overlapped time domain data. The converted overlapped data are then outputted to the save unit <b>3632</b>. The save unit <b>3632</b> extracts only the valid data from the overlapped time domain data, which are then outputted for data decoding and, at the same time, outputted to the second coefficient calculating unit <b>3650</b> in order to update the coefficient.
0488The CIR estimator <b>3641</b> of the first coefficient calculating unit <b>3640</b> uses the data received during the known data section and the known data in order to estimate the CIR. Subsequently, the estimated CIR is outputted to the interpolator <b>3642</b>. The interpolator <b>3642</b> uses the inputted CIR to estimate the CIRs (i.e., CIRs of the region that does not include the known data) corresponding to the points located between the estimated CIRs according to a predetermined interpolation method. Thereafter, the estimated result is outputted to the second FFT unit <b>3643</b>. The second FFT unit <b>3643</b> performs FFT on the inputted CIR, so as to convert the inputted CIR to a frequency domain CIR. Thereafter, the converted frequency domain CIR is outputted to the coefficient calculator <b>3644</b>. The coefficient calculator <b>3644</b> calculates a frequency domain equalization coefficient that satisfies the condition of using the CIR of the frequency domain so as to minimize the mean square error. The calculated equalizer coefficient of the frequency domain is then outputted to the coefficient calculator <b>3660</b>.
0489The structure and operations of the second coefficient calculating unit <b>3650</b> is identical to those of the second coefficient calculating unit <b>3550</b> shown in <figref idref="DRAWINGS">FIG. 57</figref>. Therefore, the description of the same will be omitted for simplicity.
0490If the input data correspond to the data of regions A/B, the coefficient selector <b>3660</b> selects the equalization coefficient calculated from the first coefficient calculating unit <b>3640</b>. On the other hand, if the input data correspond to the data of regions C/D, the coefficient selector <b>3660</b> selects the equalization coefficient updated by the second coefficient calculating unit <b>3650</b>. Thereafter, the selected equalization coefficient is outputted to the distortion compensator <b>3620</b>.
0491<figref idref="DRAWINGS">FIG. 59</figref> illustrates a block diagram of a channel equalizer according to another embodiment of the present invention. In other words, <figref idref="DRAWINGS">FIG. 59</figref> illustrates a block diagram showing another example of a channel equalizer by using different CIR estimation and application methods in accordance with regions A, B, C, and D, when the data group is divided into the structure shown in <figref idref="DRAWINGS">FIG. 5</figref>. For example, in regions A/B, the present invention uses the known data in order to estimate the CIR by using a least square (LS) method, thereby performing the channel equalization process. On the other hand, in regions C/D, the present invention estimates the CIR by using a least mean square (LMS) method, thereby performing the channel equalization process. More specifically, since the periodic known data do not exist in regions C/D, as in regions A/B, the same channel equalization process as that of regions A/B cannot be performed in regions C/D. Therefore, the channel equalization process may only be performed by using the LMS method.
0492Referring to <figref idref="DRAWINGS">FIG. 59</figref>, the channel equalizer includes an overlap unit <b>3701</b>, a first fast fourier transform (FFT) unit <b>3702</b>, a distortion compensator <b>3703</b>, an inverse fast fourier transform (IFFT) unit <b>3704</b>, a save unit <b>3705</b>, a first CIR estimator <b>3706</b>, a CIR interpolator <b>3707</b>, a decision unit <b>3708</b>, a second CIR estimator <b>3710</b>, a selection unit <b>3711</b>, a second FFT unit <b>3712</b>, and a coefficient calculator <b>3713</b>. Herein, any device performed complex number multiplication may be used as the distortion compensator <b>3703</b>. In the channel equalizer having the above-described structure, as shown in <figref idref="DRAWINGS">FIG. 59</figref>, the overlap unit <b>3701</b> overlaps the data being inputted to the channel equalizer to a predetermined overlapping ratio and then outputs the overlapped data to the first FFT unit <b>3702</b>. The first FFT unit <b>3702</b> converts (or transforms) the overlapped data of the time domain to overlapped data of the frequency domain by using fast fourier transform (FFT). Then, the converted data are outputted to the distortion compensator <b>3703</b>.
0493The distortion converter <b>3703</b> performs complex multiplication on the equalization coefficient calculated from the coefficient calculator <b>3713</b> and the overlapped data of the frequency domain, thereby compensating the channel distortion of the overlapped data being outputted from the first FFT unit <b>3702</b>. Thereafter, the distortion-compensated data are outputted to the IFFT unit <b>3704</b>. The IFFT unit <b>3704</b> performs inverse fast fourier transform (IFFT) on the distortion-compensated overlapped data, so as to convert the corresponding data back to data (i.e., overlapped data) of the time domain. Subsequently, the converted data are outputted to the save unit <b>3705</b>. The save unit <b>3705</b> extracts only the valid data from the overlapped data of the time domain. Then, the save unit <b>3705</b> outputs the extracted valid data for a data decoding process and, at the same time, outputs the extracted valid data to the decision unit <b>3708</b> for a channel estimation process.
0494The decision unit <b>3708</b> selects one of a plurality of decision values (e.g., 8 decision values) that is most approximate to the equalized data and outputs the selected decision value to the select unit <b>3709</b>. Herein, a multiplexer may be used as the select unit <b>3709</b>. In a general data section, the select unit <b>3709</b> selects the decision value of the decision unit <b>3708</b>. Alternatively, in a known data section, the select unit <b>3709</b> selects the known data and outputs the selected known data to the second CIR estimator <b>3710</b>.
0495Meanwhile, the first CIR estimator <b>3706</b> uses the data that are being inputted in the known data section and the known data so as to estimate the CIR.
0496Thereafter, the first CIR estimator <b>3706</b> outputs the estimated CIR to the CIR interpolator <b>3707</b>. Herein, the known data correspond to reference known data created during the known data section by the receiving system in accordance to an agreement between the transmitting system and the receiving system. At this point, according to an embodiment of the present invention, the first CIR estimator <b>3706</b> uses the LS method to estimate the CIR. The LS estimation method calculates a cross correlation value p between the known data that have passed through the channel during the known data section and the known data that are already known by the receiving end. Then, a cross correlation matrix R of the known data is calculated. Subsequently, a matrix operation is performed on R<sup>−1</sup>·p so that the cross correlation portion within the cross correlation value p between the received data and the initial known data, thereby estimating the CIR of the transmission channel.
0497The CIR interpolator <b>3707</b> receives the CIR from the first CIR estimator <b>3706</b>. And, in the section between two sets of known data, the CIR is interpolated in accordance with a pre-determined interpolation method. Then, the interpolated CIR is outputted. At this point, the pre-determined interpolation method corresponds to a method of estimating a particular set of data at an unknown point by using a set of data known by a particular function. For example, such method includes a linear interpolation method. The linear interpolation method is only one of the most simple interpolation methods. A variety of other interpolation methods may be used instead of the above-described linear interpolation method. It is apparent that the present invention is not limited only to the example set forth in the description of the present invention. More specifically, the CIR interpolator <b>3707</b> uses the CIR that is being inputted in order to estimate the CIR of the section that does not include any known data by using the pre-determined interpolation method. Thereafter, the estimated CIR is outputted to the select unit <b>3711</b>.
0498The second CIR estimator <b>3710</b> uses the input data of the channel equalizer and the output data of the select unit <b>3709</b> in order to estimate the CIR. Then, the second CIR estimator <b>3710</b> outputs the estimated CIR to the select unit <b>3711</b>. At this point, according to an embodiment of the present invention, the CIR is estimated by using the LMS method. The LMS estimation method will be described in detail in a later process.
0499In regions A/B (i.e., MPH blocks B<b>3</b> to B<b>8</b>), the select unit <b>3711</b> selects the CIR outputted from the CIR interpolator <b>3707</b>. And, in regions C/D (i.e., MPH blocks B<b>1</b>, B<b>2</b>, B<b>9</b>, and B<b>10</b>), the select unit <b>3711</b> selects the CIR outputted from the second CIR estimator <b>3710</b>. Thereafter, the select unit <b>3711</b> outputs the selected CIR to the second FFT unit <b>3712</b>.
0500The second FFT unit <b>3712</b> converts the CIR that is being inputted to a CIR of the frequency domain, which is then outputted to the coefficient calculator <b>3713</b>. The coefficient calculator <b>3713</b> uses the CIR of the frequency domain that is being inputted, so as to calculate the equalization coefficient and to output the calculated equalization coefficient to the distortion compensator <b>3703</b>. At this point, the coefficient calculator <b>3713</b> calculates a channel equalization coefficient of the frequency domain that can provide minimum mean square error (MMSE) from the CIR of the frequency domain. At this point, the second CIR estimator <b>3710</b> may use the CIR estimated in regions A/B as the CIR at the beginning of regions C/D. For example, the CIR value of MPH block B<b>8</b> may be used as the CIR value at the beginning of the MPH block B<b>9</b>. Accordingly, the convergence speed of regions C/D may be reduced.
0501The basic principle of estimating the CIR by using the LMS method in the second CIR estimator <b>3710</b> corresponds to receiving the output of an unknown transmission channel and to updating (or renewing) the coefficient of an adaptive filter (not shown) so that the difference value between the output value of the unknown channel and the output value of the adaptive filter is minimized. More specifically, the coefficient value of the adaptive filter is renewed so that the input data of the channel equalizer is equal to the output value of the adaptive filter (not shown) included in the second CIR estimator <b>3710</b>. Thereafter, the filter coefficient is outputted as the CIR after each FFT cycle.
0502Referring to <figref idref="DRAWINGS">FIG. 60</figref>, the second CIR estimator <b>3710</b> includes a delay unit T, a multiplier, and a coefficient renewal unit for each tab. Herein, the delay unit T sequentially delays the output data {circumflex over (x)}(n) of the select unit <b>3709</b>. The multiplier multiplies respective output data outputted from each delay unit T with error data e(n). The coefficient renewal unit renews the coefficient by using the output corresponding to each multiplier. Herein, the multipliers that are being provided as many as the number of tabs will be referred to as a first multiplying unit for simplicity. Furthermore, the second CIR estimator <b>3710</b> further includes a plurality of multipliers each multiplying the output data of the select unit <b>3709</b> and the output data of the delay unit T (wherein the output data of the last delay unit are excluded) with the output data corresponding to each respective coefficient renewal unit. These multipliers are also provided as many as the number of tabs. This group of multipliers will be referred to as a second multiplying unit for simplicity.
0503The second CIR estimator <b>3710</b> further includes an adder and a subtractor. Herein, the adder adds all of the data outputted from each multipliers included in the second multiplier unit. Then, the added value is outputted as the estimation value ŷ(n) of the data inputted to the channel equalizer. The subtractor calculates the difference between the output data ŷ(n) of the adder and the input data y(n) of the channel equalizer. Thereafter, the calculated difference value is outputted as the error data e(n). Referring to <figref idref="DRAWINGS">FIG. 60</figref>, in a general data section, the decision value of the equalized data is inputted to the first delay unit included in the second CIR estimator <b>3710</b> and to the first multiplier included in the second multiplier. In the known data section, the known data are inputted to the first delay unit included in the second CIR estimator <b>3710</b> and to the first multiplier included in the second multiplier unit. The input data {circumflex over (x)}(n) are sequentially delayed by passing through a number of serially connected delay units T, the number corresponding to the number of tabs. The output data of each delay unit T and the error data e(n) are multiplied by each corresponding multiplier included in the first multiplier unit. Thereafter, the coefficients are renewed by each respective coefficient renewal unit.
0504Each coefficient that is renewed by the corresponding coefficient renewal unit is multiplied with the input data the output data {circumflex over (x)}(n) and also with the output data of each delay unit T with the exception of the last delay. Thereafter, the multiplied value is inputted to the adder. The adder then adds all of the output data outputted from the second multiplier unit and outputs the added value to the subtractor as the estimation value ŷ(n) of the input data of the channel equalizer. The subtractor calculates a difference value between the estimation value ŷ(n) and the input data y(n) of the channel equalizer. The difference value is then outputted to each multiplier of the first multiplier unit as the error data e(n). At this point, the error data e(n) is outputted to each multiplier of the first multiplier unit by passing through each respective delay unit T. As described above, the coefficient of the adaptive filter is continuously renewed. And, the output of each coefficient renewal unit is outputted as the CIR of the second CIR estimator <b>3710</b> after each FFT cycle.
0000Block Decoder
0505Meanwhile, if the data being inputted to the block decoder <b>1005</b>, after being channel-equalized by the equalizer <b>1003</b>, correspond to the data having both block encoding and trellis encoding performed thereon (i.e., the data within the RS frame, the signaling information data, etc.) by the transmitting system, trellis decoding and block decoding processes are performed on the inputted data as inverse processes of the transmitting system. Alternatively, if the data being inputted to the block decoder <b>1005</b> correspond to the data having only trellis encoding performed thereon (i.e., the main service data), and not the block encoding, only the trellis decoding process is performed on the inputted data as the inverse process of the transmitting system.
0506The trellis decoded and block decoded data by the block decoder <b>1005</b> are then outputted to the RS frame decoder <b>1006</b>. More specifically, the block decoder <b>1005</b> removes the known data, data used for trellis initialization, and signaling information data, MPEG header, which have been inserted in the data group, and the RS parity data, which have been added by the RS encoder/non-systematic RS encoder or non-systematic RS encoder of the transmitting system. Then, the block decoder <b>1005</b> outputs the processed data to the RS frame decoder <b>1006</b>. Herein, the removal of the data may be performed before the block decoding process, or may be performed during or after the block decoding process.
0507Meanwhile, the data trellis-decoded by the block decoder <b>1005</b> are outputted to the data deinterleaver <b>1009</b>. At this point, the data being trellis-decoded by the block decoder <b>1005</b> and outputted to the data deinterleaver <b>1009</b> may not only include the main service data but may also include the data within the RS frame and the signaling information. Furthermore, the RS parity data that are added by the transmitting system after the pre-processor <b>230</b> may also be included in the data being outputted to the data deinterleaver <b>1009</b>.
0508According to another embodiment of the present invention, data that are not processed with block decoding and only processed with trellis encoding by the transmitting system may directly bypass the block decoder <b>1005</b> so as to be outputted to the data deinterleaver <b>1009</b>. In this case, a trellis decoder should be provided before the data deinterleaver <b>1009</b>. More specifically, if the inputted data correspond to the data having only trellis encoding performed thereon and not block encoding, the block decoder <b>1005</b> performs Viterbi (or trellis) decoding on the inputted data so as to output a hard decision value or to perform a hard-decision on a soft decision value, thereby outputting the result.
0509Meanwhile, if the inputted data correspond to the data having both block encoding process and trellis encoding process performed thereon, the block decoder <b>1005</b> outputs a soft decision value with respect to the inputted data.
0510In other words, if the inputted data correspond to data being processed with block encoding by the block processor <b>302</b> and being processed with trellis encoding by the trellis encoding module <b>256</b>, in the transmitting system, the block decoder <b>1005</b> performs a decoding process and a trellis decoding process on the inputted data as inverse processes of the transmitting system. At this point, the RS frame encoder of the pre-processor included in the transmitting system may be viewed as an outer (or external) encoder. And, the trellis encoder may be viewed as an inner (or internal) encoder. When decoding such concatenated codes, in order to allow the block decoder <b>1005</b> to maximize its performance of decoding externally encoded data, the decoder of the internal code should output a soft decision value.
0511<figref idref="DRAWINGS">FIG. 61</figref> illustrates a detailed block diagram of the block decoder <b>1005</b> according to an embodiment of the present invention. Referring to <figref idref="DRAWINGS">FIG. 61</figref>, the block decoder <b>1005</b> includes a feedback controller <b>4010</b>, an input buffer <b>4011</b>, a trellis decoding unit (or 12-way trellis coded modulation (TCM) decoder or inner decoder) <b>4012</b>, a symbol-byte converter <b>4013</b>, an outer block extractor <b>4014</b>, a feedback deformatter <b>4015</b>, a symbol deinterleaver <b>4016</b>, an outer symbol mapper <b>4017</b>, a symbol decoder <b>4018</b>, an inner symbol mapper <b>4019</b>, a symbol interleaver <b>4020</b>, a feedback formatter <b>4021</b>, and an output buffer <b>4022</b>. Herein, just as in the transmitting system, the trellis decoding unit <b>4012</b> may be viewed as an inner (or internal) decoder. And, the symbol decoder <b>4018</b> may be viewed as an outer (or external) decoder.
0512The input buffer <b>4011</b> temporarily stores the mobile service data symbols being channel-equalized and outputted from the equalizer <b>1003</b>. (Herein, the mobile service data symbols may include symbols corresponding to the signaling information, RS parity data symbols and CRC data symbols added during the encoding process of the RS frame.) Thereafter, the input buffer <b>4011</b> repeatedly outputs the stored symbols for M number of times to the trellis decoding unit <b>4012</b> in a turbo block (TDL) size required for the turbo decoding process.
0513The turbo decoding length (TDL) may also be referred to as a turbo block. Herein, a TDL should include at least one SCCCC block size. Therefore, as defined in <figref idref="DRAWINGS">FIG. 5</figref>, when it is assumed that one MPH block is a 16-segment unit, and that a combination of 10 MPH blocks form one SCCC block, a TDL should be equal to or larger than the maximum possible combination size. For example, when it is assumed that 2 MPH blocks form one SCCC block, the TDL may be equal to or larger than 32 segments (i.e., 828*32=26496 symbols). Herein, M indicates a number of repetitions for turbo-decoding pre-decided by the feed-back controller <b>4010</b>.
0514Also, M represents a number of repetitions of the turbo decoding process, the number being predetermined by the feedback controller <b>4010</b>.
0515Additionally, among the values of symbols being channel-equalized and outputted from the equalizer <b>1003</b>, the input symbol values corresponding to a section having no mobile service data symbols (including RS parity data symbols during RS frame encoding and CRC data symbols) included therein, bypass the input buffer <b>4011</b> without being stored. More specifically, since trellis-encoding is performed on input symbol values of a section wherein SCCC block-encoding has not been performed, the input buffer <b>4011</b> inputs the inputted symbol values of the corresponding section directly to the trellis encoding module <b>4012</b> without performing any storage, repetition, and output processes. The storage, repetition, and output processes of the input buffer <b>4011</b> are controlled by the feedback controller <b>4010</b>. Herein, the feedback controller <b>4010</b> refers to SCCC-associated information (e.g., SCCC block mode and SCCC outer code mode), which are outputted from the signaling information decoding unit <b>1013</b>, in order to control the storage and output processes of the input buffer <b>4011</b>.
0516The trellis decoding unit <b>4012</b> includes a 12-way TCM decoder. Herein, the trellis decoding unit <b>4012</b> performs 12-way trellis decoding as inverse processes of the 12-way trellis encoder.
0517More specifically, the trellis decoding unit <b>4012</b> receives a number of output symbols of the input buffer <b>4011</b> and soft-decision values of the feedback formatter <b>4021</b> equivalent to each TDL, so as to perform the TCM decoding process.
0518At this point, based upon the control of the feedback controller <b>4010</b>, the soft-decision values outputted from the feedback formatter <b>4021</b> are matched with a number of mobile service data symbol places so as to be in a one-to-one (1:1) correspondence. Herein, the number of mobile service data symbol places is equivalent to the TDL being outputted from the input buffer <b>4011</b>.
0519More specifically, the mobile service data being outputted from the input buffer <b>4011</b> are matched with the turbo decoded data being inputted, so that each respective data place can correspond with one another. Thereafter, the matched data are outputted to the trellis decoding unit <b>4012</b>. For example, if the turbo decoded data correspond to the third symbol within the turbo block, the corresponding symbol (or data) is matched with the third symbol included in the turbo block, which is outputted from the input buffer <b>4011</b>. Subsequently, the matched symbol (or data) is outputted to the trellis decoding unit <b>4012</b>.
0520In order to do so, while the regressive turbo decoding is in process, the feedback controller <b>4010</b> controls the input buffer <b>4011</b> so that the input buffer <b>4011</b> stores the corresponding turbo block data. Also, by delaying data (or symbols), the soft decision value (e.g., LLR) of the symbol outputted from the symbol interleaver <b>4020</b> and the symbol of the input buffer <b>4011</b> corresponding to the same place (or position) within the block of the output symbol are matched with one another to be in a one-to-one correspondence. Thereafter, the matched symbols are controlled so that they can be inputted to the TCM decoder through the respective path. This process is repeated for a predetermined number of turbo decoding cycle periods. Then, the data of the next turbo block are outputted from the input buffer <b>4011</b>, thereby repeating the turbo decoding process.
0521The output of the trellis decoding unit <b>4012</b> signifies a degree of reliability of the transmission bits configuring each symbol. For example, in the transmitting system, since the input data of the trellis encoding module correspond to two bits as one symbol, a log likelihood ratio (LLR) between the likelihood of a bit having the value of ‘1’ and the likelihood of the bit having the value of ‘0’ may be respectively outputted (in bit units) to the upper bit and the lower bit. Herein, the log likelihood ratio corresponds to a log value for the ratio between the likelihood of a bit having the value of ‘1’ and the likelihood of the bit having the value of ‘0’. Alternatively, a LLR for the likelihood of 2 bits (i.e., one symbol) being equal to “00”, “01”, “10”, and “11” may be respectively outputted (in symbol units) to all 4 combinations of bits (i.e., 00, 01, 10, 11). Consequently, this becomes the soft decision value that indicates the degree of reliability of the transmission bits configuring each symbol. A maximum a posteriori probability (MAP) or a soft-out Viterbi algorithm (SOVA) may be used as a decoding algorithm of each TCM decoder within the trellis decoding unit <b>4012</b>.
0522The output of the trellis decoding unit <b>4012</b> is inputted to the symbol-byte converter <b>4013</b> and the outer block extractor <b>4014</b>.
0523The symbol-byte converter <b>4013</b> performs a hard-decision process of the soft decision value that is trellis decoded and outputted from the trellis decoding unit <b>4012</b>. Thereafter, the symbol-byte converter <b>4013</b> groups 4 symbols into byte units, which are then outputted to the data deinterleaver <b>1009</b> of <figref idref="DRAWINGS">FIG. 36</figref>. More specifically, the symbol-byte converter <b>4013</b> performs hard-decision in bit units on the soft decision value of the symbol outputted from the trellis decoding unit <b>4012</b>. Therefore, the data processed with hard-decision and outputted in bit units from the symbol-byte converter <b>4013</b> not only include main service data, but may also include mobile service data, known data, RS parity data, and MPEG headers.
0524Among the soft decision values of TDL size of the trellis decoding unit <b>4012</b>, the outer block extractor <b>4014</b> identifies the soft decision values of B size of corresponding to the mobile service data symbols (wherein symbols corresponding to signaling information, RS parity data symbols that are added during the encoding of the RS frame, and CRC data symbols are included) and outputs the identified soft decision values to the feedback deformatter <b>4015</b>.
0525The feedback deformatter <b>4015</b> changes the processing order of the soft decision values corresponding to the mobile service data symbols. This is an inverse process of an initial change in the processing order of the mobile service data symbols, which are generated during an intermediate step, wherein the output symbols outputted from the block processor <b>302</b> of the transmitting system are being inputted to the trellis encoding module <b>256</b> (e.g., when the symbols pass through the group formatter, the data deinterleaver, the packet formatter, and the data interleaver). Thereafter, the feedback deformatter <b>1015</b> performs reordering of the process order of soft decision values corresponding to the mobile service data symbols and, then, outputs the processed mobile service data symbols to the symbol deinterleaver <b>4016</b>.
0526This is because a plurality of blocks exist between the block processor <b>302</b> and the trellis encoding module <b>256</b>, and because, due to these blocks, the order of the mobile service data symbols being outputted from the block processor <b>302</b> and the order of the mobile service data symbols being inputted to the trellis encoding module <b>256</b> are not identical to one another. Therefore, the feedback deformatter <b>4015</b> reorders (or rearranges) the order of the mobile service data symbols being outputted from the outer block extractor <b>4014</b>, so that the order of the mobile service data symbols being inputted to the symbol deinterleaver <b>4016</b> matches the order of the mobile service data symbols outputted from the block processor <b>302</b> of the transmitting system. The reordering process may be embodied as one of software, middleware, and hardware.
0527<figref idref="DRAWINGS">FIG. 62</figref> illustrates a detailed block view of the feedback deformatter <b>4015</b> according to an embodiment of the present invention. Herein, the feedback deformatter <b>4015</b> includes a data deinterleaver <b>5011</b>, a packet deformatter <b>5012</b>, a data interleaver <b>5013</b>, and a group deformatter <b>5014</b>. Referring to <figref idref="DRAWINGS">FIG. 62</figref>, the soft decision value of the mobile service data symbol, which is extracted by the outer block extractor <b>4014</b>, is outputted directly to the data deinterleaver <b>5011</b> of the feedback deformatter <b>4015</b> without modification. However, data place holders (or null data) are inserted in data places (e.g., main service data places, known data places, signaling information places, RS parity data places, and MPEG header places), which are removed by the outer block extractor <b>4014</b>, thereby being outputted to the data deinterleaver <b>5011</b> of the feedback deformatter <b>4015</b>.
0528The data deinterleaver <b>5011</b> performs an inverse process of the data interleaver <b>253</b> included in the transmitting system. More specifically, the data deinterleaver <b>5011</b> deinterleaves the inputted data and outputs the deinterleaved data to the packet deformatter <b>5012</b>. The packet deformatter <b>5012</b> performs an inverse process of the packet formatter <b>305</b>. More specifically, among the data that are deinterleaved and outputted from the data deinterleaver <b>5011</b>, the packet deformatter <b>5012</b> removes the place holder corresponding to the MPEG header, which had been inserted to the packet formatter <b>305</b>. The output of the packet deformatter <b>5012</b> is inputted to the data interleaver <b>5013</b>, and the data interleaver <b>5013</b> interleaves the data being inputted, as an inverse process of the data deinterleaver <b>529</b> included in the transmitting system. Accordingly, data having a data structure as shown in <figref idref="DRAWINGS">FIG. 5</figref>, are outputted to the group deformatter <b>5014</b>.
0529The data deformatter <b>5014</b> performs an inverse process of the group formatter <b>303</b> included in the transmitting system. More specifically, the group formatter <b>5014</b> removes the place holders corresponding to the main service data, known data, signaling information data, and RS parity data. Then, the group formatter <b>5014</b> outputs only the reordered (or rearranged) mobile service data symbols to the symbol deinterleaver <b>4016</b>. According to another embodiment of the present invention, when the feedback deformatter <b>4015</b> is embodied using a memory map, the process of inserting and removing place holder to and from data places removed by the outer block extractor <b>4014</b> may be omitted.
0530The symbol deinterleaver <b>4016</b> performs deinterleaving on the mobile service data symbols having their processing orders changed and outputted from the feedback deformatter <b>4015</b>, as an inverse process of the symbol interleaving process of the symbol interleaver <b>514</b> included in the transmitting system. The size of the block used by the symbol deinterleaver <b>4016</b> during the deinterleaving process is identical to interleaving size of an actual symbol (i.e., B) of the symbol interleaver <b>514</b>, which is included in the transmitting system. This is because the turbo decoding process is performed between the trellis decoding unit <b>4012</b> and the symbol decoder <b>4018</b>. Both the input and output of the symbol deinterleaver <b>4016</b> correspond to soft decision values, and the deinterleaved soft decision values are outputted to the outer symbol mapper <b>4017</b>.
0531The operations of the outer symbol mapper <b>4017</b> may vary depending upon the structure and coding rate of the convolution encoder <b>513</b> included in the transmitting system. For example, when data are 1/2-rate encoded by the convolution encoder <b>513</b> and then transmitted, the outer symbol mapper <b>4017</b> directly outputs the input data without modification. In another example, when data are 1/4-rate encoded by the convolution encoder <b>513</b> and then transmitted, the outer symbol mapper <b>4017</b> converts the input data so that it can match the input data format of the symbol decoder <b>4018</b>. For this, the outer symbol mapper <b>4017</b> may be inputted SCCC-associated information (i.e., SCCC block mode and SCCC outer code mode) from the signaling information decoder <b>1013</b>. Then, the outer symbol mapper <b>4017</b> outputs the converted data to the symbol decoder <b>4018</b>.
0532The symbol decoder <b>4018</b> (i.e., the outer decoder) receives the data outputted from the outer symbol mapper <b>4017</b> and performs symbol decoding as an inverse process of the convolution encoder <b>513</b> included in the transmitting system. At this point, two different soft decision values are outputted from the symbol decoder <b>4018</b>. One of the outputted soft decision values corresponds to a soft decision value matching the output symbol of the convolution encoder <b>513</b> (hereinafter referred to as a “first decision value”). The other one of the outputted soft decision values corresponds to a soft decision value matching the input bit of the convolution encoder <b>513</b> (hereinafter referred to as a “second decision value”).
0533More specifically, the first decision value represents a degree of reliability the output symbol (i.e., 2 bits) of the convolution encoder <b>513</b>. Herein, the first soft decision value may output (in bit units) a LLR between the likelihood of 1 bit being equal to ‘1’ and the likelihood of 1 bit being equal to ‘0’ with respect to each of the upper bit and lower bit, which configures a symbol. Alternatively, the first soft decision value may also output (in symbol units) a LLR for the likelihood of 2 bits being equal to “00”, “01”, “10”, and “11” with respect to all possible combinations. The first soft decision value is fed-back to the trellis decoding unit <b>4012</b> through the inner symbol mapper <b>4019</b>, the symbol interleaver <b>4020</b>, and the feedback formatter <b>4021</b>. On the other hand, the second soft decision value indicates a degree of reliability the input bit of the convolution encoder <b>513</b> included in the transmitting system. Herein, the second soft decision value is represented as the LLR between the likelihood of 1 bit being equal to ‘1’ and the likelihood of 1 bit being equal to ‘0’. Thereafter, the second soft decision value is outputted to the outer buffer <b>4022</b>. In this case, a maximum a posteriori probability (MAP) or a soft-out Viterbi algorithm (SOVA) may be used as the decoding algorithm of the symbol decoder <b>4018</b>.
0534The first soft decision value that is outputted from the symbol decoder <b>4018</b> is inputted to the inner symbol mapper <b>4019</b>. The inner symbol mapper <b>4019</b> converts the first soft decision value to a data format corresponding the input data of the trellis decoding unit <b>4012</b>. Thereafter, the inner symbol mapper <b>4019</b> outputs the converted soft decision value to the symbol interleaver <b>4020</b>. The operations of the inner symbol mapper <b>4019</b> may also vary depending upon the structure and coding rate of the convolution encoder <b>513</b> included in the transmitting system.
0535The symbol interleaver <b>4020</b> performs symbol interleaving, as shown in <figref idref="DRAWINGS">FIG. 26</figref>, on the first soft decision value that is outputted from the inner symbol mapper <b>4019</b>. Then, the symbol interleaver <b>4020</b> outputs the symbol-interleaved first soft decision value to the feedback formatter <b>4021</b>. Herein, the output of the symbol interleaver <b>4020</b> also corresponds to a soft decision value.
0536With respect to the changed processing order of the soft decision values corresponding to the symbols that are generated during an intermediate step, wherein the output symbols outputted from the block processor <b>302</b> of the transmitting system are being inputted to the trellis encoding module (e.g., when the symbols pass through the group formatter, the data deinterleaver, the packet formatter, the RS encoder, and the data interleaver), the feedback formatter <b>4021</b> alters (or changes) the order of the output values outputted from the symbol interleaver <b>4020</b>. Subsequently, the feedback formatter <b>4020</b> outputs values to the trellis decoding unit <b>4012</b> in the changed order. The reordering process of the feedback formatter <b>4021</b> may configure at least one of software, hardware, and middleware. For example, the feedback formatter <b>4021</b> may configure to be performed as an inverse process of <figref idref="DRAWINGS">FIG. 62</figref>.
0537The soft decision values outputted from the symbol interleaver <b>4020</b> are matched with the positions of mobile service data symbols each having the size of TDL, which are outputted from the input buffer <b>4011</b>, so as to be in a one-to-one correspondence. Thereafter, the soft decision values matched with the respective symbol position are inputted to the trellis decoding unit <b>4012</b>. At this point, since the main service data symbols or the RS parity data symbols and known data symbols of the main service data do not correspond to the mobile service data symbols, the feedback formatter <b>4021</b> inserts null data in the corresponding positions, thereby outputting the processed data to the trellis decoding unit <b>4012</b>. Additionally, each time the symbols having the size of TDL are turbo decoded, no value is fed-back by the symbol interleaver <b>4020</b> starting from the beginning of the first decoding process. Therefore, the feedback formatter <b>4021</b> is controlled by the feedback controller <b>4010</b>, thereby inserting null data into all symbol positions including a mobile service data symbol. Then, the processed data are outputted to the trellis decoding unit <b>4012</b>.
0538The output buffer <b>4022</b> receives the second soft decision value from the symbol decoder <b>4018</b> based upon the control of the feedback controller <b>4010</b>. Then, the output buffer <b>4022</b> temporarily stores the received second soft decision value. Thereafter, the output buffer <b>4022</b> outputs the second soft decision value to the RS frame decoder <b>10006</b>. For example, the output buffer <b>4022</b> overwrites the second soft decision value of the symbol decoder <b>4018</b> until the turbo decoding process is performed for M number of times. Then, once all M number of turbo decoding processes is performed for a single TDL, the corresponding second soft decision value is outputted to the RS frame decoder <b>1006</b>.
0539The feedback controller <b>4010</b> controls the number of turbo decoding and turbo decoding repetition processes of the overall block decoder, shown in <figref idref="DRAWINGS">FIG. 61</figref>. More specifically, once the turbo decoding process has been repeated for a predetermined number of times, the second soft decision value of the symbol decoder <b>4018</b> is outputted to the RS frame decoder <b>1006</b> through the output buffer <b>4022</b>. Thus, the block decoding process of a turbo block is completed. In the description of the present invention, this process is referred to as a regressive turbo decoding process for simplicity.
0540At this point, the number of regressive turbo decoding rounds between the trellis decoding unit <b>4012</b> and the symbol decoder <b>4018</b> may be defined while taking into account hardware complexity and error correction performance. Accordingly, if the number of rounds increases, the error correction performance may be enhanced. However, this may lead to a disadvantageous of the hardware becoming more complicated (or complex).
0541Meanwhile, the data deinterleaver <b>1009</b>, the RS decoder <b>1010</b>, and the data derandomizer <b>1011</b> correspond to blocks required for receiving the main service data. Therefore, the above-mentioned blocks may not be necessary (or required) in the structure of a digital broadcast receiving system for receiving mobile service data only.
0542The data deinterleaver <b>1009</b> performs an inverse process of the data interleaver included in the transmitting system. In other words, the data deinterleaver <b>1009</b> deinterleaves the main service data outputted from the block decoder <b>1005</b> and outputs the deinterleaved main service data to the RS decoder <b>1010</b>. The data being inputted to the data deinterleaver <b>1009</b> include main service data, as well as mobile service data, known data, RS parity data, and an MPEG header. At this point, among the inputted data, only the main service data and the RS parity data added to the main service data packet may be outputted to the RS decoder <b>1010</b>. Also, all data outputted after the data derandomizer <b>1011</b> may all be removed with the exception for the main service data. In the embodiment of the present invention, only the main service data and the RS parity data added to the main service data packet are inputted to the RS decoder <b>1010</b>.
0543The RS decoder <b>1010</b> performs a systematic RS decoding process on the deinterleaved data and outputs the processed data to the data derandomizer <b>1011</b>.
0544The data derandomizer <b>1011</b> receives the output of the RS decoder <b>1010</b> and generates a pseudo random data byte identical to that of the randomizer included in the digital broadcast transmitting system. Thereafter, the data derandomizer <b>1011</b> performs a bitwise exclusive OR (XOR) operation on the generated pseudo random data byte, thereby inserting the MPEG synchronization bytes to the beginning of each packet so as to output the data in 188-byte main service data packet units.
0000RS Frame Decoder
0545The data outputted from the block decoder <b>1005</b> are in portion units. More specifically, in the transmitting system, the RS frame is divided into several portions, and the mobile service data of each portion are assigned either to regions A/B/C/D within the data group or to any one of regions A/B and regions C/D , thereby being transmitted to the receiving system. Therefore, the RS frame decoder <b>1006</b> groups several portions included in a parade so as to form an RS frame. Alternatively, the RS frame decoder <b>1006</b> may also group several portions included in a parade so as to form two RS frames. Thereafter, error correction decoding is performed in RS frame units.
0546For example, when the RS frame mode value is equal to ‘00’, then one parade transmits one RS frame. At this point, one RS frame is divided into several portions, and the mobile service data of each portion are assigned to regions A/B/C/D of the corresponding data group, thereby being transmitted. In this case, the MPH frame decoder <b>1006</b> extracts mobile service data from regions A/B/C/D of the corresponding data group, as shown in <figref idref="DRAWINGS">FIG. 63(a)</figref>. Subsequently, the MPH frame decoder <b>1006</b> may perform the process of forming (or creating) a portion on a plurality of data group within a parade, thereby forming several portions. Then, the several portions of mobile service data may be grouped to form an RS frame. Herein, if stuffing bytes are added to the last portion, the RS frame may be formed after removing the stuffing byte.
0547In another example, when the RS frame mode value is equal to ‘01’, then one parade transmits two RS frames (i.e., a primary RS frame and a secondary RS frame). At this point, a primary RS frame is divided into several primary portions, and the mobile service data of each primary portion are assigned to regions A/B of the corresponding data group, thereby being transmitted. Also, a secondary RS frame is divided into several secondary portions, and the mobile service data of each secondary portion are assigned to regions C/D of the corresponding data group, thereby being transmitted.
0548In this case, the MPH frame decoder <b>1006</b> extracts mobile service data from regions A/B of the corresponding data group, as shown in <figref idref="DRAWINGS">FIG. 63(b)</figref>. Subsequently, the MPH frame decoder <b>1006</b> may perform the process of forming (or creating) a primary portion on a plurality of data group within a parade, thereby forming several primary portions. Then, the several primary portions of mobile service data may be grouped to form a primary RS frame. Herein, if stuffing bytes are added to the last primary portion, the primary RS frame may be formed after removing the stuffing byte. Also, the MPH frame decoder <b>1006</b> extracts mobile service data from regions C/D of the corresponding data group. Subsequently, the MPH frame decoder <b>1006</b> may perform the process of forming (or creating) a secondary portion on a plurality of data group within a parade, thereby forming several secondary portions. Then, the several secondary portions of mobile service data may be grouped to form a secondary RS frame. Herein, if stuffing bytes are added to the last secondary portion, the secondary RS frame may be formed after removing the stuffing byte.
0549More specifically, the RS frame decoder <b>1006</b> receives the RS-encoded and/or CRC-encoded mobile service data of each portion from the block decoder <b>1005</b>. Then, the RS frame decoder <b>1006</b> groups several portions, which are inputted based upon RS frame-associated information outputted from the signaling information decoder <b>1013</b>, thereby performing error correction. By referring to the RS frame mode value included in the RS frame-associated information, the RS frame decoder <b>1006</b> may form an RS frame and may also be informed of the number of RS code parity data bytes and the code size. Herein, the RS code is used to configure (or form) the RS frame. The RS frame decoder <b>1006</b> also refers to the RS frame-associated information in order to perform an inverse process of the RS frame encoder, which is included in the transmitting system, thereby correcting the errors within the RS frame. Thereafter, the RS frame decoder <b>1006</b> adds 1 MPEG synchronization data byte to the error-correction mobile service data packet. In an earlier process, the 1 MPEG synchronization data byte was removed from the mobile service data packet during the RS frame encoding process. Finally, the RS frame decoder <b>1006</b> outputs the processed mobile service data packet to the derandomizer <b>1007</b>.
0550<figref idref="DRAWINGS">FIG. 64</figref> illustrates, when the RS frame mode value is equal to ‘00’, an exemplary process of grouping several portion being transmitted to a parade, thereby forming an RS frame and an RS frame reliability map, and an exemplary process of performing a row de-permutation process in super frame units as an inverse process of the transmitting system, thereby re-distinguishing (or identifying) the row-de-permuted RS frame and RS frame reliability map. More specifically, the RS frame decoder <b>1006</b> receives and groups a plurality of mobile service data bytes, so as to form an RS frame. According to the present invention, in transmitting system, the mobile service data correspond to data RS-encoded in RS frame units and also correspond to data row-permuted in super frame units. At this point, the mobile service data may already be error correction encoded (e.g., CRC-encoded). Alternatively, the error correction encoding process may be omitted.
0551It is assumed that, in the transmitting system, an RS frame having the size of (N+2)×(187+P) bytes is divided into M number of portions, and that the M number of mobile service data portions are assigned and transmitted to regions A/B/C/D in M number of data groups, respectively. In this case, in the receiving system, each mobile service data portion is grouped, as shown in <figref idref="DRAWINGS">FIG. 64(a)</figref>, thereby forming an RS frame having the size of (N+2)×(187+P) bytes. At this point, when stuffing bytes (S) are added to at least one portion included in the corresponding RS frame and then transmitted, the stuffing bytes are removed, thereby configuring an RS frame and an RS frame reliability map. For example, as shown in <figref idref="DRAWINGS">FIG. 23</figref>, when S number of stuffing bytes are added to the corresponding portion, the S number of stuffing bytes are removed, thereby configuring the RS frame and the RS frame reliability map.
0552Herein, when it is assumed that the block decoder <b>1005</b> outputs a soft decision value for the decoding result, the RS frame decoder <b>1006</b> may decide the ‘0’ and ‘1’ of the corresponding bit by using the codes of the soft decision value. 8 bits that are each decided as described above are grouped to create 1 data byte. If the above-described process is performed on all soft decision values of several portions (or data groups) included in a parade, the RS frame having the size of (N+2)×(187+P) bytes may be configured.
0553Additionally, the present invention uses the soft decision value not only to configure the RS frame but also to configure a reliability map.
0554Herein, the reliability map indicates the reliability of the corresponding data byte, which is configured by grouping 8 bits, the 8 bits being decided by the codes of the soft decision value.
0555For example, when the absolute value of the soft decision value exceeds a pre-determined threshold value, the value of the corresponding bit, which is decided by the code of the corresponding soft decision value, is determined to be reliable. Conversely, when the absolute value of the soft decision value does not exceed the pre-determined threshold value, the value of the corresponding bit is determined to be unreliable. Thereafter, if even a single bit among the 8 bits, which are decided by the codes of the soft decision value and group to configure one data byte, is determined to be unreliable, the corresponding data byte is marked on the reliability map as an unreliable data byte.
0556Herein, determining the reliability of one data byte is only exemplary. More specifically, when a plurality of data bytes (e.g., at least 4 data bytes) are determined to be unreliable, the corresponding data bytes may also be marked as unreliable data bytes within the reliability map. Conversely, when all of the data bits within the one data byte are determined to be reliable (i.e., when the absolute value of the soft decision values of all 8 bits included in the one data byte exceed the predetermined threshold value), the corresponding data byte is marked to be a reliable data byte on the reliability map. Similarly, when a plurality of data bytes (e.g., at least 4 data bytes) are determined to be reliable, the corresponding data bytes may also be marked as reliable data bytes within the reliability map. The numbers proposed in the above-described example are merely exemplary and, therefore, do not limit the scope or spirit of the present invention.
0557The process of configuring the RS frame and the process of configuring the reliability map both using the soft decision value may be performed at the same time. Herein, the reliability information within the reliability map is in a one-to-one correspondence with each byte within the RS frame. For example, if a RS frame has the size of (N+2)×(187+P) bytes, the reliability map is also configured to have the size of (N+2)×(187+P) bytes. <figref idref="DRAWINGS">FIG. 64</figref>(a′) and <figref idref="DRAWINGS">FIG. 64</figref>(b′) respectively illustrate the process steps of configuring the reliability map according to the present invention.
0558At this point, the RS frame of <figref idref="DRAWINGS">FIG. 64(b)</figref> and the RS frame reliability map of <figref idref="DRAWINGS">FIG. 64</figref>(b′) are interleaved in super frame units (as shown in <figref idref="DRAWINGS">FIG. 21</figref>). Therefore, the RS frame and the RS frame reliability maps are grouped to create a super frame and a super frame reliability map. Subsequently, as shown in <figref idref="DRAWINGS">FIG. 64(c)</figref> and <figref idref="DRAWINGS">FIG. 64</figref>(c′), a de-permutation (or deinterleaving) process is performed in super frame units on the RS frame and the RS frame reliability maps, as an inverse process of the transmitting system. Then, when the de-permutation process is performed in super frame units, the processed data are divided into de-permuted (or deinterleaved) RS frames having the size of (N+2)×(187+P) bytes and de-permuted RS frame reliability maps having the size of (N+2)×(187+P) bytes, as shown in <figref idref="DRAWINGS">FIG. 64(d)</figref> and <figref idref="DRAWINGS">FIG. 64</figref>(d′). Subsequently, the RS frame reliability map is used on the divided RS frames so as to perform error correction.
0559<figref idref="DRAWINGS">FIG. 65</figref> illustrates example of the error correction processed according to embodiments of the present invention. <figref idref="DRAWINGS">FIG. 65</figref> illustrates an example of performing an error correction process when the transmitting system has performed both RS encoding and CRC encoding processes on the RS frame.
0560As shown in <figref idref="DRAWINGS">FIG. 65(a)</figref> and <figref idref="DRAWINGS">FIG. 65</figref>(a′), when the RS frame having the size of (N+2)×(187+P) bytes and the RS frame reliability map having the size of (N+2)×(187+P) bytes are created, a CRC syndrome checking process is performed on the created RS frame, thereby verifying whether any error has occurred in each row. Subsequently, as shown in <figref idref="DRAWINGS">FIG. 65(b)</figref>, a 2-byte checksum is removed to configure an RS frame having the size of N×(187+P) bytes. Herein, the presence (or existence) of an error is indicated on an error flag corresponding to each row. Similarly, since the portion of the reliability map corresponding to the CRC checksum has hardly any applicability, this portion is removed so that only N×(187+P) number of the reliability information bytes remain, as shown in <figref idref="DRAWINGS">FIG. 65</figref>(b′).
0561After performing the CRC syndrome checking process, as described above, a RS decoding process is performed in a column direction. Herein, a RS erasure correction process may be performed in accordance with the number of CRC error flags. More specifically, as shown in <figref idref="DRAWINGS">FIG. 65(c)</figref>, the CRC error flag corresponding to each row within the RS frame is verified. Thereafter, the RS frame decoder <b>1006</b> determines whether the number of rows having a CRC error occurring therein is equal to or smaller than the maximum number of errors on which the RS erasure correction may be performed, when performing the RS decoding process in a column direction. The maximum number of errors corresponds to P number of parity bytes inserted when performing the RS encoding process. In the embodiment of the present invention, it is assumed that 48 parity bytes have been added to each column (i.e., P=48).
0562If the number of rows having the CRC errors occurring therein is smaller than or equal to the maximum number of errors (i.e., 48 errors according to this embodiment) that can be corrected by the RS erasure decoding process, a (235,187)-RS erasure decoding process is performed in a column direction on the RS frame having (187+P) number of N-byte rows (i.e., 235 N-byte rows), as shown in <figref idref="DRAWINGS">FIG. 65(d)</figref>. Thereafter, as shown in <figref idref="DRAWINGS">FIG. 65(e)</figref>, the 48-byte parity data that have been added at the end of each column are removed. Conversely, however, if the number of rows having the CRC errors occurring therein is greater than the maximum number of errors (i.e., 48 errors) that can be corrected by the RS erasure decoding process, the RS erasure decoding process cannot be performed. In this case, the error may be corrected by performing a general RS decoding process. In addition, the reliability map, which has been created based upon the soft decision value along with the RS frame, may be used to further enhance the error correction ability (or performance) of the present invention.
0563More specifically, the RS frame decoder <b>1006</b> compares the absolute value of the soft decision value of the block decoder <b>1005</b> with the pre-determined threshold value, so as to determine the reliability of the bit value decided by the code of the corresponding soft decision value. Also, 8 bits, each being determined by the code of the soft decision value, are grouped to form one data byte. Accordingly, the reliability information on this one data byte is indicated on the reliability map. Therefore, as shown in <figref idref="DRAWINGS">FIG. 65(c)</figref>, even though a particular row is determined to have an error occurring therein based upon a CRC syndrome checking process on the particular row, the present invention does not assume that all bytes included in the row have errors occurring therein. The present invention refers to the reliability information of the reliability map and sets only the bytes that have been determined to be unreliable as erroneous bytes. In other words, with disregard to whether or not a CRC error exists within the corresponding row, only the bytes that are determined to be unreliable based upon the reliability map are set as erasure points.
0564According to another method, when it is determined that CRC errors are included in the corresponding row, based upon the result of the CRC syndrome checking result, only the bytes that are determined by the reliability map to be unreliable are set as errors. More specifically, only the bytes corresponding to the row that is determined to have errors included therein and being determined to be unreliable based upon the reliability information, are set as the erasure points. Thereafter, if the number of error points for each column is smaller than or equal to the maximum number of errors (i.e., 48 errors) that can be corrected by the RS erasure decoding process, an RS erasure decoding process is performed on the corresponding column. Conversely, if the number of error points for each column is greater than the maximum number of errors (i.e., 48 errors) that can be corrected by the RS erasure decoding process, a general decoding process is performed on the corresponding column
0565More specifically, if the number of rows having CRC errors included therein is greater than the maximum number of errors (i.e., 48 errors) that can be corrected by the RS erasure decoding process, either an RS erasure decoding process or a general RS decoding process is performed on a column that is decided based upon the reliability information of the reliability map, in accordance with the number of erasure points within the corresponding column. For example, it is assumed that the number of rows having CRC errors included therein within the RS frame is greater than 48. And, it is also assumed that the number of erasure points decided based upon the reliability information of the reliability map is indicated as 40 erasure points in the first column and as 50 erasure points in the second column. In this case, a (235,187)-RS erasure decoding process is performed on the first column. Alternatively, a (235,187)-RS decoding process is performed on the second column. When error correction decoding is performed on all column directions within the RS frame by using the above-described process, the 48-byte parity data which were added at the end of each column are removed, as shown in <figref idref="DRAWINGS">FIG. 65(e)</figref>.
0566As described above, even though the total number of CRC errors corresponding to each row within the RS frame is greater than the maximum number of errors that can be corrected by the RS erasure decoding process, when the number of bytes determined to have a low reliability level, based upon the reliability information on the reliability map within a particular column, while performing error correction decoding on the particular column. Herein, the difference between the general RS decoding process and the RS erasure decoding process is the number of errors that can be corrected. More specifically, when performing the general RS decoding process, the number of errors corresponding to half of the number of parity bytes (i.e., (number of parity bytes)/2) that are inserted during the RS encoding process may be error corrected (e.g., 24 errors may be corrected). Alternatively, when performing the RS erasure decoding process, the number of errors corresponding to the number of parity bytes that are inserted during the RS encoding process may be error corrected (e.g., 48 errors may be corrected).
0567After performing the error correction decoding process, as described above, a RS frame configured of 187 N-byte rows (or packet) may be obtained as shown in <figref idref="DRAWINGS">FIG. 65(e)</figref>. The RS frame having the size of N×187 bytes is outputted by the order of N number of 187-byte units. At this point, 1 MPEG synchronization byte, which had been removed by the transmitting system, is added to each 187-byte packet, as shown in <figref idref="DRAWINGS">FIG. 65(f)</figref>. Therefore, a 188-byte unit mobile service data packet is outputted.
0568As described above, the RS frame decoded mobile service data is outputted to the data derandomizer <b>1007</b>. The data derandomizer <b>1007</b> performs a derandomizing process, which corresponds to the inverse process of the randomizer included in the transmitting system, on the received mobile service data. Thereafter, the derandomized data are outputted, thereby obtaining the mobile service data transmitted from the transmitting system. In the present invention, the RS frame decoder <b>1006</b> may perform the data derandomizing function. An MPH frame decoder may be configured of M number of RS frame decoders provided in parallel, wherein the number of RS frame encoders is equal to the number of parades (=M) within an MPH frame, a multiplexer for multiplexing each portion and being provided to each input end of the M number of RS frame decoders, and a demultiplexer for demultiplexing each portion and being provided to each output end of the M number of RS frame decoders.
0000General Digital Broadcast Receiving System
0569<figref idref="DRAWINGS">FIG. 66</figref> illustrates a block diagram showing a structure of a digital broadcast receiving system according to an embodiment of the present invention. Herein, the demodulating unit of <figref idref="DRAWINGS">FIG. 36</figref> may be applied in the digital broadcast receiving system. Referring to <figref idref="DRAWINGS">FIG. 66</figref>, the digital broadcast receiving system includes a tuner <b>6001</b>, a demodulating unit <b>6002</b>, a demultiplexer <b>6003</b>, an audio decoder <b>6004</b>, a video decoder <b>6005</b>, a native TV application manager <b>6006</b>, a channel manager <b>6007</b>, a channel map <b>6008</b>, a first memory <b>6009</b>, an SI and/or data decoder <b>6010</b>, a second memory <b>6011</b>, a system manager <b>6012</b>, a data broadcast application manager <b>6013</b>, a storage controller <b>6014</b>, a third memory <b>6015</b>, and a GPS module <b>6020</b>. Herein, the first memory <b>6009</b> corresponds to a non-volatile random access memory (NVRAM) (or a flash memory). The third memory <b>6015</b> corresponds to a large-scale storage device, such as a hard disk drive (HDD), a memory chip, and so on.
0570The tuner <b>6001</b> tunes a frequency of a specific channel through any one of an antenna, cable, and satellite. Then, the tuner <b>6001</b> down-converts the tuned frequency to an intermediate frequency (IF), which is then outputted to the demodulating unit <b>6002</b>. At this point, the tuner <b>6001</b> is controlled by the channel manager <b>6007</b>. Additionally, the result and strength of the broadcast signal of the tuned channel are also reported to the channel manager <b>6007</b>. The data that are being received by the frequency of the tuned specific channel include main service data, mobile service data, and table data for decoding the main service data and mobile service data.
0571According to the embodiment of the present invention, audio data and video data for mobile broadcast programs may be applied as the mobile service data. Such audio data and video data are compressed by various types of encoders so as to be transmitted to a broadcasting station. In this case, the video decoder <b>6004</b> and the audio decoder <b>6005</b> will be provided in the receiving system so as to correspond to each of the encoders used for the compression process. Thereafter, the decoding process will be performed by the video decoder <b>6004</b> and the audio decoder <b>6005</b>. Then, the processed video and audio data will be provided to the users. Examples of the encoding/decoding scheme for the audio data may include AC 3, MPEG 2 AUDIO, MPEG 4 AUDIO, AAC, AAC+, HE AAC, AAC SBR, MPEG-Surround, and BSAC. And, examples of the encoding/decoding scheme for the video data may include MPEG 2 VIDEO, MPEG 4 VIDEO, H.264, SVC, and VC-1.
0572Depending upon the embodiment of the present invention, examples of the mobile service data may include data provided for data service, such as Java application data, HTML application data, XML data, and so on. The data provided for such data services may correspond either to a Java class file for the Java application, or to a directory file designating positions (or locations) of such files. Furthermore, such data may also correspond to an audio file and/or a video file used in each application. The data services may include weather forecast services, traffic information services, stock information services, services providing information quiz programs providing audience participation services, real time poll, user interactive education programs, gaming services, services providing information on soap opera (or TV series) synopsis, characters, original sound track, filing sites, services providing information on past sports matches, profiles and accomplishments of sports players, product information and product ordering services, services providing information on broadcast programs by media type, airing time, subject, and so on. The types of data services described above are only exemplary and are not limited only to the examples given herein. Furthermore, depending upon the embodiment of the present invention, the mobile service data may correspond to meta data. For example, the meta data be written in XML format so as to be transmitted through a DSM-CC protocol.
0573The demodulating unit <b>6002</b> performs VSB-demodulation and channel equalization on the signal being outputted from the tuner <b>6001</b>, thereby identifying the main service data and the mobile service data. Thereafter, the identified main service data and mobile service data are outputted in TS packet units. An example of the demodulating unit <b>6002</b> is shown in <figref idref="DRAWINGS">FIG. 36</figref> to <figref idref="DRAWINGS">FIG. 65</figref>. Therefore, the structure and operation of the demodulator will be described in detail in a later process. However, this is merely exemplary and the scope of the present invention is not limited to the example set forth herein. In the embodiment given as an example of the present invention, only the mobile service data packet outputted from the demodulating unit <b>6002</b> is inputted to the demultiplexer <b>6003</b>. In this case, the main service data packet is inputted to another demultiplexer (not shown) that processes main service data packets. Herein, the storage controller <b>6014</b> is also connected to the other demultiplexer in order to store the main service data after processing the main service data packets. The demultiplexer of the present invention may also be designed to process both mobile service data packets and main service data packets in a single demultiplexer.
0574The storage controller <b>6014</b> is interfaced with the demultiplexer so as to control instant recording, reserved (or pre-programmed) recording, time shift, and so on of the mobile service data and/or main service data. For example, when one of instant recording, reserved (or pre-programmed) recording, and time shift is set and programmed in the receiving system (or receiver) shown in <figref idref="DRAWINGS">FIG. 66</figref>, the corresponding mobile service data and/or main service data that are inputted to the demultiplexer are stored in the third memory <b>6015</b> in accordance with the control of the storage controller <b>6014</b>. The third memory <b>6015</b> may be described as a temporary storage area and/or a permanent storage area. Herein, the temporary storage area is used for the time shifting function, and the permanent storage area is used for a permanent storage of data according to the user's choice (or decision).
0575When the data stored in the third memory <b>6015</b> need to be reproduced (or played), the storage controller <b>6014</b> reads the corresponding data stored in the third memory <b>6015</b> and outputs the read data to the corresponding demultiplexer (e.g., the mobile service data are outputted to the demultiplexer <b>6003</b> shown in <figref idref="DRAWINGS">FIG. 66</figref>). At this point, according to the embodiment of the present invention, since the storage capacity of the third memory <b>6015</b> is limited, the compression encoded mobile service data and/or main service data that are being inputted are directly stored in the third memory <b>6015</b> without any modification for the efficiency of the storage capacity. In this case, depending upon the reproduction (or reading) command, the data read from the third memory <b>6015</b> pass trough the demultiplexer so as to be inputted to the corresponding decoder, thereby being restored to the initial state.
0576The storage controller <b>6014</b> may control the reproduction (or play), fast-forward, rewind, slow motion, instant replay functions of the data that are already stored in the third memory <b>6015</b> or presently being buffered. Herein, the instant replay function corresponds to repeatedly viewing scenes that the viewer (or user) wishes to view once again. The instant replay function may be performed on stored data and also on data that are currently being received in real time by associating the instant replay function with the time shift function. If the data being inputted correspond to the analog format, for example, if the transmission mode is NTSC, PAL, and so on, the storage controller <b>6014</b> compression encodes the inputted data and stored the compression-encoded data to the third memory <b>6015</b>. In order to do so, the storage controller <b>6014</b> may include an encoder, wherein the encoder may be embodied as one of software, middleware, and hardware. Herein, an MPEG encoder may be used as the encoder according to an embodiment of the present invention. The encoder may also be provided outside of the storage controller <b>6014</b>.
0577Meanwhile, in order to prevent illegal duplication (or copies) of the input data being stored in the third memory <b>6015</b>, the storage controller <b>6014</b> scrambles (or encrypts) the input data and stores the scrambled (or encrypted) data in the third memory <b>6015</b>. Accordingly, the storage controller <b>6014</b> may include a scramble algorithm (or encryption algorithm) for scrambling the data stored in the third memory <b>6015</b> and a descramble algorithm (or decryption algorithm) for descrambling (or decrypting) the data read from the third memory <b>6015</b>. The scrambling method may include using an arbitrary key (e.g., control word) to modify a desired set of data, and also a method of mixing signals.
0578Meanwhile, the demultiplexer <b>6003</b> receives the real-time data outputted from the demodulating unit <b>6002</b> or the data read from the third memory <b>6015</b> and demultiplexes the received data. In the example given in the present invention, the demultiplexer <b>6003</b> performs demultiplexing on the mobile service data packet. Therefore, in the present invention, the receiving and processing of the mobile service data will be described in detail. However, depending upon the many embodiments of the present invention, not only the mobile service data but also the main service data may be processed by the demultiplexer <b>6003</b>, the audio decoder <b>6004</b>, the video decoder <b>6005</b>, the native TV application manager <b>6006</b>, the channel manager <b>6007</b>, the channel map <b>6008</b>, the first memory <b>6009</b>, the SI and/or data decoder <b>6010</b>, the second memory <b>6011</b>, a system manager <b>6012</b>, the data broadcast application manager <b>6013</b>, the storage controller <b>6014</b>, the third memory <b>6015</b>, and the GPS module <b>6020</b>. Thereafter, the processed data may be used to provide diverse services to the users.
0579The demultiplexer <b>6003</b> demultiplexes mobile service data and system information (SI) tables from the mobile service data packet inputted in accordance with the control of the SI and/or data decoder <b>6010</b>. Thereafter, the demultiplexed mobile service data and SI tables are outputted to the SI and/or data decoder <b>6010</b> in a section format. In this case, it is preferable that data for the data service are used as the mobile service data that are inputted to the SI and/or data decoder <b>6010</b>. In order to extract the mobile service data from the channel through which mobile service data are transmitted and to decode the extracted mobile service data, system information is required. Such system information may also be referred to as service information. The system information may include channel information, event information, etc. In the embodiment of the present invention, the PSI/PSIP tables are applied as the system information. However, the present invention is not limited to the example set forth herein. More specifically, regardless of the name, any protocol transmitting system information in a table format may be applied in the present invention.
0580The PSI table is an MPEG-2 system standard defined for identifying the channels and the programs. The PSIP table is an advanced television systems committee (ATSC) standard that can identify the channels and the programs. The PSI table may include a program association table (PAT), a conditional access table (CAT), a program map table (PMT), and a network information table (NIT). Herein, the PAT corresponds to special information that is transmitted by a data packet having a PID of ‘0’. The PAT transmits PID information of the PMT and PID information of the NIT corresponding to each program. The CAT transmits information on a paid broadcast system used by the transmitting system. The PMT transmits PID information of a transport stream (TS) packet, in which program identification numbers and individual bit sequences of video and audio data configuring the corresponding program are transmitted, and the PID information, in which PCR is transmitted. The NIT transmits information of the actual transmission network.
0581The PSIP table may include a virtual channel table (VCT), a system time table (STT), a rating region table (RRT), an extended text table (ETT), a direct channel change table (DCCT), an event information table (EIT), and a master guide table (MGT). The VCT transmits information on virtual channels, such as channel information for selecting channels and information such as packet identification (PID) numbers for receiving the audio and/or video data. More specifically, when the VCT is parsed, the PID of the audio/video data of the broadcast program may be known. Herein, the corresponding audio/video data are transmitted within the channel along with the channel name and the channel number.
0582<figref idref="DRAWINGS">FIG. 67</figref> illustrates a VCT syntax according to an embodiment of the present invention. The VCT syntax of <figref idref="DRAWINGS">FIG. 67</figref> is configured by including at least one of a table_id field, a section_syntax_indicator field, a private_indicator field, a section_length field, a transport_stream_id field, a version_number field, a current_next_indicator field, a section_number field, a last_section_number field, a protocol_version field, and a num_channels_in_section field.
0583The VCT syntax further includes a first ‘for’ loop repetition statement that is repeated as much as the num_channels_in_section field value. The first repetition statement may include at least one of a short_name field, a major_channel_number field, a minor_channel_number field, a modulation_mode field, a carrier_frequency field, a channel_TSID field, a program_number field, an ETM_location field, an access_controlled field, a hidden field, a service_type field, a source_id field, a descriptor_length field, and a second ‘for’ loop statement that is repeated as much as the number of descriptors included in the first repetition statement. Herein, the second repetition statement will be referred to as a first descriptor loop for simplicity. The descriptor descriptors( ) included in the first descriptor loop is separately applied to each virtual channel.
0584Furthermore, the VCT syntax may further include an additional_descriptor_length field, and a third ‘for’ loop statement that is repeated as much as the number of descriptors additionally added to the VCT. For simplicity of the description of the present invention, the third repetition statement will be referred to as a second descriptor loop. The descriptor additional_descriptors( ) included in the second descriptor loop is commonly applied to all virtual channels described in the VCT.
0585As described above, referring to <figref idref="DRAWINGS">FIG. 67</figref>, the table_id field indicates a unique identifier (or identification) (ID) that can identify the information being transmitted to the table as the VCT. More specifically, the table_id field indicates a value informing that the table corresponding to this section is a VCT. For example, a 0xC8 value may be given to the table_id field.
0586The version_number field indicates the version number of the VCT. The section_number field indicates the number of this section. The last_section_number field indicates the number of the last section of a complete VCT. And, the num_channel_in_section field designates the number of the overall virtual channel existing within the VCT section. Furthermore, in the first ‘for’ loop repetition statement, the short name field indicates the name of a virtual channel. The major_channel_number field indicates a ‘major’ channel number associated with the virtual channel defined within the first repetition statement, and the minor_channel_number field indicates a ‘minor’ channel number. More specifically, each of the channel numbers should be connected to the major and minor channel numbers, and the major and minor channel numbers are used as user reference numbers for the corresponding virtual channel.
0587The program_number field is shown for connecting the virtual channel having an MPEG-2 program association table (PAT) and program map table (PMT) defined therein, and the program_number field matches the program number within the PAT/PMT. Herein, the PAT describes the elements of a program corresponding to each program number, and the PAT indicates the PID of a transport packet transmitting the PMT. The PMT described subordinate information, and a PID list of the transport packet through which a program identification number and a separate bit sequence, such as video and/or audio data configuring the program, are being transmitted.
0588<figref idref="DRAWINGS">FIG. 68</figref> illustrates a service_type field according to an embodiment of the present invention. The service_type field indicates the service type provided in a corresponding virtual channel. Referring to <figref idref="DRAWINGS">FIG. 68</figref>, it is provided that the service_type field should only indicate an analog television, a digital television, digital audio data, and digital video data. Also, according to the embodiment of the present invention, it may be provided that a mobile broadcast program should be designated to the service_type field. The service_type field, which is parsed by the SI and/or data decoder <b>6010</b> may be provided to a receiving system, as shown in <figref idref="DRAWINGS">FIG. 66</figref>, and used accordingly. According to other embodiments of the present invention, the parsed service_type field may also be provided to each of the audio decoder <b>6004</b> and video decoder <b>6005</b>, so as to be used in the decoding process.
0589The source_id field indicates a program source connected to the corresponding virtual channel. Herein, a source refers to a specific source, such as an image, a text, video data, or sound. The source_id field value has a unique value within the transport stream transmitting the VCT. Meanwhile, a service location descriptor may be included in a descriptor loop (i.e., descriptor { }) within a next ‘for’ loop repetition statement. The service location descriptor may include a stream type, PID, and language code for each elementary stream.
0590<figref idref="DRAWINGS">FIG. 69</figref> illustrates a service location descriptor according to an embodiment of the present invention. As shown in <figref idref="DRAWINGS">FIG. 69</figref>, the service location descriptor may include a descriptor_tag field, a descriptor_length field, and a PCR_PID field. Herein, the PCR_PID field indicates the PID of a transport stream packet within a program specified by a program_number field, wherein the transport stream packet includes a valid PCR field. Meanwhile, the service location descriptor includes a number_elements field so as to indicate a number of PIDs used in the corresponding program. The number of repetition of a next ‘for’ descriptor loop repetition statement can be decided, depending upon the value of the number_elements field. Referring to <figref idref="DRAWINGS">FIG. 69</figref>, the ‘for’ loop repetition statement includes a stream_type field, an elementary_PID field, and an ISO_639_language_code field. Herein, the stream_type field indicates the stream type of the corresponding elementary stream (i.e., video/audio data). The elementary_PID field indicates the PID of the corresponding elementary stream. The ISO_639_language_code field indicates a language code of the corresponding elementary stream.
0591<figref idref="DRAWINGS">FIG. 70</figref> illustrates examples that may be assigned to the stream_type field according to the present invention. As shown in <figref idref="DRAWINGS">FIG. 70</figref>, ISO/IEC 11172 Video, ITU-T Rec. H.262|ISO/IEC 13818-2 Video or ISO/IEC 11172-2 constrained parameter video stream, ISO/IEC 11172 Audio, ISO/IEC 13818-3 Audio, ITU-T Rec. H.222.0|ISO/IEC 13818-1 private_sections, ITU-T Rec. H.222.0|ISO/IEC 13818-1 PES packets containing private data, ISO/IEC 13522 MHEG, ITU-T Rec. H.222.0|ISO/IEC 13818-1 Annex A DSM CC, ITU-T Rec. H.222.1, ISO/IEC 13818-6 type A, ISO/IEC 13818-6 type B, ISO/IEC 13818-6 type C, ISO/IEC 13818-6 type D, ISO/IEC 13818-1 auxiliary, and so on may be applied as the stream type. Meanwhile, according to the embodiment of the present invention, MPH video stream: Non-hierarchical mode, MPH audio stream: Non-hierarchical mode, MPH Non-A/V stream: Non-hierarchical mode, MPH High Priority video stream: Hierarchical mode, MPH High Priority audio stream: Hierarchical mode, MPH Low Priority video stream: Hierarchical mode, MPH Low priority audio stream: Hierarchical mode, and so on may further be applied as the stream type.
0592As described above, “MPH” corresponds to the initials of “mobile”, “pedestrian”, and “handheld” and represents the opposite concept of a fixed-type system. Therefore, the MPH video stream: Non-hierarchical mode, the MPH audio stream: Non-hierarchical mode, the MPH Non-A/V stream: Non-hierarchical mode, the MPH High Priority video stream: Hierarchical mode, the MPH High Priority audio stream: Hierarchical mode, the MPH Low Priority video stream: Hierarchical mode, and the MPH Low priority audio stream: Hierarchical mode correspond to stream types that are applied when mobile broadcast programs are being transmitted and received. Also the Hierarchical mode and the Non-hierarchical mode each correspond to values that are used in stream types having different priority levels. Herein, the priority level is determined based upon a hierarchical structure applied in any one of the encoding or decoding method.
0593Therefore, when a hierarchical structure-type codec is used, a field value including the hierarchical mode and the non-hierarchical mode is respectively designated so as to identify each stream. Such stream type information is parsed by the SI and/or data decoder <b>6010</b>, so as to be provided to the video and audio decoders <b>6004</b> and <b>6005</b>. Thereafter, each of the video and audio decoders <b>6004</b> and <b>6005</b> uses the parsed stream type information in order to perform the decoding process. Other stream types that may be applied in the present invention may include MPEG 4 AUDIO, AC 3, AAC, AAC+, BSAC, HE AAC, AAC SBR, and MPEG-S for the audio data, and may also include MPEG 2 VIDEO, MPEG 4 VIDEO, H.264, SVC, and VC-1 for the video data.
0594Furthermore, referring to <figref idref="DRAWINGS">FIG. 70</figref>, in fields using the hierarchical mode and the non-hierarchical mode, such as the MPH video stream: Non-hierarchical mode and the MPH audio stream: Non-hierarchical mode, examples of using the MPEG 4 AUDIO, AC 3, AAC, AAC+, BSAC, HE AAC, AAC SBR, and MPEG-S for the audio data, and the MPEG 2 VIDEO, MPEG 4 VIDEO, H.264, SVC, and VC-1 for the video data may also be respectively used as replacements for each of the audio stream and the video stream may be considered as other embodiments of the present invention and may, therefore, be included in the scope of the present invention. Meanwhile, the stream_type field may be provided as one of the fields within the PMT. And, in this case, it is apparent that such stream_type field includes the above-described syntax. The STT transmits information on the current data and timing information. The RRT transmits information on region and consultation organs for program ratings. The ETT transmits additional description of a specific channel and broadcast program. The EIT transmits information on virtual channel events (e.g., program title, program start time, etc.).
0595<figref idref="DRAWINGS">FIG. 71</figref> illustrates a bit stream syntax for an event information table (EIT) according to the present invention. In this embodiment, the EIT shown in <figref idref="DRAWINGS">FIG. 71</figref> corresponds to a PSIP table including information on a title, start time, duration, and so on of an event in a virtual channel. Referring to <figref idref="DRAWINGS">FIG. 71</figref>, the EIT is configured of a plurality of fields including a table_id field, a section_syntax_indicator field, a private_indicator field, a source_ID, a version_numbers_in_section field, a current_next_indicator field, and a num_event field. More specifically, the table_id field is an 8-bit field having the value of ‘oxCB’, which indicates that the corresponding section is included in the EIT. The section_syntax_indicator field is a 1-bit field having the value of ‘1’. This indicates that the corresponding section passes through the section_length field and is in accordance with a generic section syntax. The private_indicator field corresponds to a 1-bit field having the value of ‘1’.
0596Also, the source_ID corresponds to an ID identifying a virtual channel that carries an event shown in the above-described table. The version_numbers_in_section field indicates the version of an element included in the event information table. In the present invention, with respect to the previous version number, an event change information included in the event information table, wherein the event change information has a new version number is recognized as the latest change in information. The current_next_indicator field indicates whether the event information included in the corresponding EIT is a current information or a next information. And, finally, the num_event field represents the number of events included in the channel having a source ID. More specifically, an event loop shown below is repeated as many times as the number of events.
0597The above-described EIT field is commonly applied to at least one or more events included in one EIT syntax. A loop statement, which is included as “for(j=0; j<num_event_in_section;j++) { }”, describes the characteristics of each event. The following fields represent detailed information of each individual event. Therefore, the following fields are individually applied to each corresponding event described by the EIT syntax. An event_ID included in an event loop is an identifier for identifying each individual event. The number of the event ID corresponds to a portion of the identifier for even extended text message (i.e., ETM_ID). A start_time field indicates the starting time of an event. Therefore, the start_time field collects the starting time information of a program provided from an electronic program information. A length_in_seconds field indicates the duration of an event. Therefore, the length_in_seconds field collects the ending time information of a program provided from an electronic program information. More specifically, the ending time information is collected by adding the start_time field value and the length_in_seconds field value. A title_text( )field may be used to indicate the tile of a broadcast program.
0598Meanwhile, the descriptor applied to each event may be included in the EIT. Herein, a descriptors_length field indicates the length of a descriptor. Also, a descriptor loop (i.e., descriptor{ }) included in a ‘for’ loop repetition statement includes at least one of an AC-3 audio descriptor, an MPEG 2 audio descriptor, an MPEG 4 audio descriptor, an AAC descriptor, an AAC+ descriptor, an HE AAC descriptor, an AAC SBR descriptor, an MPEG surround descriptor, a BSAC descriptor, an MPEG 2 video descriptor, an MPEG 4 video descriptor, an H.264 descriptor, an SVC descriptor, and a VC-1 descriptor. Herein, each descriptor describes information on audio/video codec applied to each event. Such codec information may be provided to the audio/video decoder <b>6004</b> and <b>6005</b> and used in the decoding process.
0599Finally, the DCCT/DCCSCT transmits information associated with automatic (or direct) channel change. And, the MGT transmits the versions and PID information of the above-mentioned tables included in the PSIP. Each of the above-described tables included in the PSI/PSIP is configured of a basic unit referred to as a “section”, and a combination of one or more sections forms a table. For example, the VCT may be divided into 256 sections. Herein, one section may include a plurality of virtual channel information. However, a single set of virtual channel information is not divided into two or more sections. At this point, the receiving system may parse and decode the data for the data service that are transmitting by using only the tables included in the PSI, or only the tables included in the PSIP, or a combination of tables included in both the PSI and the PSIP. In order to parse and decode the mobile service data, at least one of the PAT and PMT included in the PSI, and the VCT included in the PSIP is required. For example, the PAT may include the system information for transmitting the mobile service data, and the PID of the PMT corresponding to the mobile service data (or program number). The PMT may include the PID of the TS packet used for transmitting the mobile service data. The VCT may include information on the virtual channel for transmitting the mobile service data, and the PID of the TS packet for transmitting the mobile service data.
0600Meanwhile, depending upon the embodiment of the present invention, a DVB-SI may be applied instead of the PSIP. The DVB-SI may include a network information table (NIT), a service description table (SDT), an event information table (EIT), and a time and data table (TDT). The DVB-SI may be used in combination with the above-described PSI. Herein, the NIT divides the services corresponding to particular network providers by specific groups. The NIT includes all tuning information that are used during the IRD set-up. The NIT may be used for informing or notifying any change in the tuning information. The SDT includes the service name and different parameters associated with each service corresponding to a particular MPEG multiplex. The EIT is used for transmitting information associated with all events occurring in the MPEG multiplex. The EIT includes information on the current transmission and also includes information selectively containing different transmission streams that may be received by the IRD. And, the TDT is used for updating the clock included in the IRD.
0601Furthermore, three selective SI tables (i.e., a bouquet associate table (BAT), a running status table (RST), and a stuffing table (ST)) may also be included. More specifically, the bouquet associate table (BAT) provides a service grouping method enabling the IRD to provide services to the viewers. Each specific service may belong to at least one ‘bouquet’ unit. A running status table (RST) section is used for promptly and instantly updating at least one event execution status. The execution status section is transmitted only once at the changing point of the event status. Other SI tables are generally transmitted several times. The stuffing table (ST) may be used for replacing or discarding a subsidiary table or the entire SI tables.
0602In the present invention, when the mobile service data correspond to audio data and video data, it is preferable that the mobile service data included (or loaded) in a payload within a TS packet correspond to PES type mobile service data. According to another embodiment of the present invention, when the mobile service data correspond to the data for the data service (or data service data), the mobile service data included in the payload within the TS packet consist of a digital storage media-command and control (DSM-CC) section format. However, the TS packet including the data service data may correspond either to a packetized elementary stream (PES) type or to a section type. More specifically, either the PES type data service data configure the TS packet, or the section type data service data configure the TS packet. The TS packet configured of the section type data will be given as the example of the present invention. At this point, the data service data are includes in the digital storage media-command and control (DSM-CC) section. Herein, the DSM-CC section is then configured of a 188-byte unit TS packet.
0603Furthermore, the packet identification of the TS packet configuring the DSM-CC section is included in a data service table (DST). When transmitting the DST, ‘0x95’ is assigned as the value of a stream_type field included in the service location descriptor of the PMT or the VCT. More specifically, when the PMT or VCT stream_type field value is ‘0x95’, the receiving system may acknowledge the reception of the data broadcast program including mobile service data. At this point, the mobile service data may be transmitted by a data/object carousel method. The data/object carousel method corresponds to repeatedly transmitting identical data on a regular basis.
0604At this point, according to the control of the SI and/or data decoder <b>6010</b>, the demultiplexer <b>6003</b> performs section filtering, thereby discarding repetitive sections and outputting only the non-repetitive sections to the SI and/or data decoder <b>6010</b>. The demultiplexer <b>6003</b> may also output only the sections configuring desired tables (e.g., VCT or EIT) to the SI and/or data decoder <b>6010</b> by section filtering. Herein, the VCT or EIT may include a specific descriptor for the mobile service data. However, the present invention does not exclude the possibilities of the mobile service data being included in other tables, such as the PMT. The section filtering method may include a method of verifying the PID of a table defined by the MGT, such as the VCT, prior to performing the section filtering process. Alternatively, the section filtering method may also include a method of directly performing the section filtering process without verifying the MGT, when the VCT includes a fixed PID (i.e., a base PID). At this point, the demultiplexer <b>6003</b> performs the section filtering process by referring to a table_id field, a version_number field, a section_number field, etc.
0605As described above, the method of defining the PID of the VCT broadly includes two different methods. Herein, the PID of the VCT is a packet identifier required for identifying the VCT from other tables. The first method consists of setting the PID of the VCT so that it is dependent to the MGT. In this case, the receiving system cannot directly verify the VCT among the many PSI and/or PSIP tables. Instead, the receiving system must check the PID defined in the MGT in order to read the VCT. Herein, the MGT defines the PID, size, version number, and so on, of diverse tables. The second method consists of setting the PID of the VCT so that the PID is given a base PID value (or a fixed PID value), thereby being independent from the MGT. In this case, unlike in the first method, the VCT according to the present invention may be identified without having to verify every single PID included in the MGT. Evidently, an agreement on the base PID must be previously made between the transmitting system and the receiving system.
0606Meanwhile, in the embodiment of the present invention, the demultiplexer <b>6003</b> may output only an application information table (AIT) to the SI and/or data decoder <b>6010</b> by section filtering. The AIT includes information on an application being operated in the receiver for the data service. The AIT may also be referred to as an XAIT, and an AMT. Therefore, any table including application information may correspond to the following description. When the AIT is transmitted, a value of ‘0x05’ may be assigned to a stream_type field of the PMT. The AIT may include application information, such as application name, application version, application priority, application ID, application status (i.e., auto-start, user-specific settings, kill, etc.), application type (i.e., Java or HTML), position (or location) of stream including application class and data files, application platform directory, and location of application icon.
0607In the method for detecting application information for the data service by using the AIT, component_tag, original network_id, transport_stream_id, and service_id fields may be used for detecting the application information. The component_tag field designates an elementary stream carrying a DSI of a corresponding object carousel. The original_network_id field indicates a DVB-SI original_network_id of the TS providing transport connection. The transport_stream_id field indicates the MPEG TS of the TS providing transport connection, and the service_id field indicates the DVB-SI of the service providing transport connection. Information on a specific channel may be obtained by using the original_network_id field, the transport_stream_id field, and the service_id field. The data service data, such as the application data, detected by using the above-described method may be stored in the second memory <b>6011</b> by the SI and/or data decoder <b>6010</b>.
0608The SI and/or data decoder <b>6010</b> parses the DSM-CC section configuring the demultiplexed mobile service data. Then, the mobile service data corresponding to the parsed result are stored as a database in the second memory <b>6011</b>. The SI and/or data decoder <b>6010</b> groups a plurality of sections having the same table identification (table_id) so as to configure a table, which is then parsed. Thereafter, the parsed result is stored as a database in the second memory <b>6011</b>. At this point, by parsing data and/or sections, the SI and/or data decoder <b>6010</b> reads all of the remaining actual section data that are not section-filtered by the demultiplexer <b>6003</b>. Then, the SI and/or data decoder <b>6010</b> stores the read data to the second memory <b>6011</b>. The second memory <b>6011</b> corresponds to a table and data/object carousel database storing system information parsed from tables and mobile service data parsed from the DSM-CC section. Herein, a table_id field, a section_number field, and a last_section_number field included in the table may be used to indicate whether the corresponding table is configured of a single section or a plurality of sections. For example, TS packets having the PID of the VCT are grouped to form a section, and sections having table identifiers allocated to the VCT are grouped to form the VCT. When the VCT is parsed, information on the virtual channel to which mobile service data are transmitted may be obtained.
0609Also, according to the present invention, the SI and/or data decoder <b>6010</b> parses the SLD of the VCT, thereby transmitting the stream type information of the corresponding elementary stream to the audio decoder <b>6004</b> or the video decoder <b>6005</b>. In this case, the corresponding audio decoder <b>6004</b> or video decoder <b>6005</b> uses the transmitted stream type information so as to perform the audio or video decoding process. Furthermore, according to the present invention, the SI and/or data decoder <b>6010</b> parses an AC-3 audio descriptor, an MPEG 2 audio descriptor, an MPEG 4 audio descriptor, an AAC descriptor, an AAC+ descriptor, an HE AAC descriptor, an AAC SBR descriptor, an MPEG surround descriptor, a BSAC descriptor, an MPEG 2 video descriptor, an MPEG 4 video descriptor, an H.264 descriptor, an SVC descriptor, a VC-1 descriptor, and so on, of the EIT, thereby transmitting the audio or video codec information of the corresponding event to the audio decoder <b>6004</b> or video decoder <b>6005</b>. In this case, the corresponding audio decoder <b>6004</b> or video decoder <b>6005</b> uses the transmitted audio or video codec information in order to perform an audio or video decoding process.
0610The obtained application identification information, service component identification information, and service information corresponding to the data service may either be stored in the second memory <b>6011</b> or be outputted to the data broadcasting application manager <b>6013</b>. In addition, reference may be made to the application identification information, service component identification information, and service information in order to decode the data service data. Alternatively, such information may also prepare the operation of the application program for the data service. Furthermore, the SI and/or data decoder <b>6010</b> controls the demultiplexing of the system information table, which corresponds to the information table associated with the channel and events. Thereafter, an A/V PID list may be transmitted to the channel manager <b>6007</b>.
0611The channel manager <b>6007</b> may refer to the channel map <b>6008</b> in order to transmit a request for receiving system-related information data to the SI and/or data decoder <b>6010</b>, thereby receiving the corresponding result. In addition, the channel manager <b>6007</b> may also control the channel tuning of the tuner <b>6001</b>. Furthermore, the channel manager <b>6007</b> may directly control the demultiplexer <b>6003</b>, so as to set up the A/V PID, thereby controlling the audio decoder <b>6004</b> and the video decoder <b>6005</b>.
0612The audio decoder <b>6004</b> and the video decoder <b>6005</b> may respectively decode and output the audio data and video data demultiplexed from the main service data packet. Alternatively, the audio decoder <b>6004</b> and the video decoder <b>6005</b> may respectively decode and output the audio data and video data demultiplexed from the mobile service data packet. Meanwhile, when the mobile service data include data service data, and also audio data and video data, it is apparent that the audio data and video data demultiplexed by the demultiplexer <b>6003</b> are respectively decoded by the audio decoder <b>6004</b> and the video decoder <b>6005</b>. For example, an audio-coding (AC)-3 decoding algorithm, an MPEG-2 audio decoding algorithm, an MPEG-4 audio decoding algorithm, an AAC decoding algorithm, an AAC+ decoding algorithm, an HE AAC decoding algorithm, an AAC SBR decoding algorithm, an MPEG surround decoding algorithm, and a BSAC decoding algorithm may be applied to the audio decoder <b>6004</b>. Also, an MPEG-2 video decoding algorithm, an MPEG-4 video decoding algorithm, an H.264 decoding algorithm, an SVC decoding algorithm, and a VC-1 decoding algorithm may be applied to the video decoder <b>6005</b>. Accordingly, the decoding process may be performed.
0613Meanwhile, the native TV application manager <b>6006</b> operates a native application program stored in the first memory <b>6009</b>, thereby performing general functions such as channel change. The native application program refers to software stored in the receiving system upon shipping of the product. More specifically, when a user request (or command) is transmitted to the receiving system through a user interface (UI), the native TV application manger <b>6006</b> displays the user request on a screen through a graphic user interface (GUI), thereby responding to the user's request. The user interface receives the user request through an input device, such as a remote controller, a key pad, a jog controller, an a touchscreen provided on the screen, and then outputs the received user request to the native TV application manager <b>6006</b> and the data broadcasting application manager <b>6013</b>. Furthermore, the native TV application manager <b>6006</b> controls the channel manager <b>6007</b>, thereby controlling channel-associated operations, such as the management of the channel map <b>6008</b>, and controlling the SI and/or data decoder <b>6010</b>. The native TV application manager <b>6006</b> also controls the GUI of the overall receiving system, thereby storing the user request and status of the receiving system in the first memory <b>6009</b> and restoring the stored information.
0614The channel manager <b>6007</b> controls the tuner <b>6001</b> and the SI and/or data decoder <b>6010</b>, so as to managing the channel map <b>6008</b> so that it can respond to the channel request made by the user. More specifically, channel manager <b>6007</b> sends a request to the SI and/or data decoder <b>6010</b> so that the tables associated with the channels that are to be tuned are parsed. The results of the parsed tables are reported to the channel manager <b>6007</b> by the SI and/or data decoder <b>6010</b>. Thereafter, based on the parsed results, the channel manager <b>6007</b> updates the channel map <b>6008</b> and sets up a PID in the demultiplexer <b>6003</b> for demultiplexing the tables associated with the data service data from the mobile service data.
0615The system manager <b>6012</b> controls the booting of the receiving system by turning the power on or off. Then, the system manager <b>6012</b> stores ROM images (including downloaded software images) in the first memory <b>6009</b>. More specifically, the first memory <b>6009</b> stores management programs such as operating system (OS) programs required for managing the receiving system and also application program executing data service functions. The application program is a program processing the data service data stored in the second memory <b>6011</b> so as to provide the user with the data service. If the data service data are stored in the second memory <b>6011</b>, the corresponding data service data are processed by the above-described application program or by other application programs, thereby being provided to the user. The management program and application program stored in the first memory <b>6009</b> may be updated or corrected to a newly downloaded program. Furthermore, the storage of the stored management program and application program is maintained without being deleted even if the power of the system is shut down. Therefore, when the power is supplied, the programs may be executed without having to be newly downloaded once again.
0616The application program for providing data service according to the present invention may either be initially stored in the first memory <b>6009</b> upon the shipping of the receiving system, or be stored in the first memory <b>6009</b> after being downloaded. The application program for the data service (i.e., the data service providing application program) stored in the first memory <b>6009</b> may also be deleted, updated, and corrected. Furthermore, the data service providing application program may be downloaded and executed along with the data service data each time the data service data are being received.
0617When a data service request is transmitted through the user interface, the data broadcasting application manager <b>6013</b> operates the corresponding application program stored in the first memory <b>6009</b> so as to process the requested data, thereby providing the user with the requested data service. And, in order to provide such data service, the data broadcasting application manager <b>6013</b> supports the graphic user interface (GUI). Herein, the data service may be provided in the form of text (or short message service (SMS)), voice message, still image, and moving image. The data broadcasting application manager <b>6013</b> may be provided with a platform for executing the application program stored in the first memory <b>6009</b>. The platform may be, for example, a Java virtual machine for executing the Java program. Hereinafter, an example of the data broadcasting application manager <b>6013</b> executing the data service providing application program stored in the first memory <b>6009</b>, so as to process the data service data stored in the second memory <b>6011</b>, thereby providing the user with the corresponding data service will now be described in detail.
0618Assuming that the data service corresponds to a traffic information service, the data service according to the present invention is provided to the user of a receiver that is not equipped with an electronic map and/or a GPS system in the form of at least one of a text (or short message service (SMS)), a voice message, a graphic message, a still image, and a moving image. In this case, when a GPS module <b>6020</b> is mounted on the receiving system, as shown in <figref idref="DRAWINGS">FIG. 66</figref>, the GPS module <b>6020</b> receives satellite signals transmitted from a plurality of low earth orbit satellites and extracts the current position (or location) information (e.g., longitude, latitude, altitude), thereby outputting the extracted information to the data broadcasting application manager <b>6013</b>.
0619At this point, it is assumed that the electronic map including information on each link and nod and other diverse graphic information are stored in one of the second memory <b>6011</b>, the first memory <b>6009</b>, and another memory that is not shown. More specifically, according to the request made by the data broadcasting application manager <b>6013</b>, the data service data stored in the second memory <b>6011</b> are read and inputted to the data broadcasting application manager <b>6013</b>. The data broadcasting application manager <b>6013</b> translates (or deciphers) the data service data read from the second memory <b>6011</b>, thereby extracting the necessary information according to the contents of the message and/or a control signal. In other words, the data broadcasting application manager <b>6013</b> uses the current position information and the graphic information, so that the current position information can be processed and provided to the user in a graphic format.
0620<figref idref="DRAWINGS">FIG. 72</figref> illustrates a block diagram showing the structure of a digital broadcast (or television) receiving system according to another embodiment of the present invention. Referring to <figref idref="DRAWINGS">FIG. 72</figref>, the digital broadcast receiving system includes a tuner <b>7001</b>, a demodulating unit <b>7002</b>, a demultiplexer <b>7003</b>, a first descrambler <b>7004</b>, an audio decoder <b>7005</b>, a video decoder <b>7006</b>, a second descrambler <b>7007</b>, an authentication unit <b>7008</b>, a native TV application manager <b>7009</b>, a channel manager <b>7010</b>, a channel map <b>7011</b>, a first memory <b>7012</b>, a data decoder <b>7013</b>, a second memory <b>7014</b>, a system manager <b>7015</b>, a data broadcasting application manager <b>7016</b>, a storage controller <b>7017</b>, a third memory <b>7018</b>, a telecommunication module <b>7019</b>, and a GPS module <b>7020</b>. Herein, the third memory <b>7018</b> is a mass storage device, such as a hard disk drive (HDD) or a memory chip. Also, during the description of the digital broadcast (or television or DTV) receiving system shown in <figref idref="DRAWINGS">FIG. 72</figref>, the components that are identical to those of the digital broadcast receiving system of <figref idref="DRAWINGS">FIG. 66</figref> will be omitted for simplicity.
0621As described above, in order to provide services for preventing illegal duplication (or copies) or illegal viewing of the enhanced data and/or main data that are transmitted by using a broadcast network, and to provide paid broadcast services, the transmitting system may generally scramble and transmit the broadcast contents. Therefore, the receiving system needs to descramble the scrambled broadcast contents in order to provide the user with the proper broadcast contents. Furthermore, the receiving system may generally be processed with an authentication process with an authentication means before the descrambling process. Hereinafter, the receiving system including an authentication means and a descrambling means according to an embodiment of the present invention will now be described in detail.
0622According to the present invention, the receiving system may be provided with a descrambling means receiving scrambled broadcasting contents and an authentication means authenticating (or verifying) whether the receiving system is entitled to receive the descrambled contents. Hereinafter, the descrambling means will be referred to as first and second descramblers <b>7004</b> and <b>7007</b>, and the authentication means will be referred to as an authentication unit <b>7008</b>. Such naming of the corresponding components is merely exemplary and is not limited to the terms suggested in the description of the present invention. For example, the units may also be referred to as a decryptor. Although <figref idref="DRAWINGS">FIG. 72</figref> illustrates an example of the descramblers <b>7004</b> and <b>7007</b> and the authentication unit <b>7008</b> being provided inside the receiving system, each of the descramblers <b>7004</b> and <b>7007</b> and the authentication unit <b>7008</b> may also be separately provided in an internal or external module. Herein, the module may include a slot type, such as a SD or CF memory, a memory stick type, a USB type, and so on, and may be detachably fixed to the receiving system.
0623As described above, when the authentication process is performed successfully by the authentication unit <b>7008</b>, the scrambled broadcasting contents are descrambled by the descramblers <b>7004</b> and <b>7007</b>, thereby being provided to the user. At this point, a variety of the authentication method and descrambling method may be used herein. However, an agreement on each corresponding method should be made between the receiving system and the transmitting system. Hereinafter, the authentication and descrambling methods will now be described, and the description of identical components or process steps will be omitted for simplicity.
0624The receiving system including the authentication unit <b>7008</b> and the descramblers <b>7004</b> and <b>7007</b> will now be described in detail. The receiving system receives the scrambled broadcasting contents through the tuner <b>7001</b> and the demodulating unit <b>7002</b>. Then, the system manager <b>7015</b> decides whether the received broadcasting contents have been scrambled. Herein, the demodulating unit <b>7002</b> may be included as a demodulating means according to embodiment of the present invention as described in <figref idref="DRAWINGS">FIG. 36</figref> to <figref idref="DRAWINGS">FIG. 65</figref>. However, the present invention is not limited to the examples given in the description set forth herein. If the system manager <b>7015</b> decides that the received broadcasting contents have been scrambled, then the system manager <b>7015</b> controls the system to operate the authentication unit <b>7008</b>. As described above, the authentication unit <b>7008</b> performs an authentication process in order to decide whether the receiving system according to the present invention corresponds to a legitimate host entitled to receive the paid broadcasting service. Herein, the authentication process may vary in accordance with the authentication methods.
0625For example, the authentication unit <b>7008</b> may perform the authentication process by comparing an IP address of an IP datagram within the received broadcasting contents with a specific address of a corresponding host. At this point, the specific address of the corresponding receiving system (or host) may be a MAC address. More specifically, the authentication unit <b>7008</b> may extract the IP address from the decapsulated IP datagram, thereby obtaining the receiving system information that is mapped with the IP address. At this point, the receiving system should be provided, in advance, with information (e.g., a table format) that can map the IP address and the receiving system information. Accordingly, the authentication unit <b>7008</b> performs the authentication process by determining the conformity between the address of the corresponding receiving system and the system information of the receiving system that is mapped with the IP address. In other words, if the authentication unit <b>7008</b> determines that the two types of information conform to one another, then the authentication unit <b>7008</b> determines that the receiving system is entitled to receive the corresponding broadcasting contents.
0626In another example, standardized identification information is defined in advance by the receiving system and the transmitting system. Then, the identification information of the receiving system requesting the paid broadcasting service is transmitted by the transmitting system. Thereafter, the receiving system determines whether the received identification information conforms with its own unique identification number, so as to perform the authentication process. More specifically, the transmitting system creates a database for storing the identification information (or number) of the receiving system requesting the paid broadcasting service. Then, if the corresponding broadcasting contents are scrambled, the transmitting system includes the identification information in the EMM, which is then transmitted to the receiving system.
0627If the corresponding broadcasting contents are scrambled, messages (e.g., entitlement control message (ECM), entitlement management message (EMM)), such as the CAS information, mode information, message position information, that are applied to the scrambling of the broadcasting contents are transmitted through a corresponding data header or another data packet. The ECM may include a control word (CW) used for scrambling the broadcasting contents. At this point, the control word may be encoded with an authentication key. The EMM may include an authentication key and entitlement information of the corresponding data. Herein, the authentication key may be encoded with a receiving system-specific distribution key. In other words, assuming that the enhanced data are scrambled by using the control word, and that the authentication information and the descrambling information are transmitted from the transmitting system, the transmitting system encodes the CW with the authentication key and, then, includes the encoded CW in the entitlement control message (ECM), which is then transmitted to the receiving system. Furthermore, the transmitting system includes the authentication key used for encoding the CW and the entitlement to receive data (or services) of the receiving system (i.e., a standardized serial number of the receiving system that is entitled to receive the corresponding broadcasting service or data) in the entitlement management message (EMM), which is then transmitted to the receiving system.
0628Accordingly, the authentication unit <b>7008</b> of the receiving system extracts the identification information of the receiving system and the identification information included in the EMM of the broadcasting service that is being received. Then, the authentication unit <b>7008</b> determines whether the identification information conform to each other, so as to perform the authentication process. More specifically, if the authentication unit <b>7008</b> determines that the information conform to each other, then the authentication unit <b>7008</b> eventually determines that the receiving system is entitled to receive the request broadcasting service.
0629In yet another example, the authentication unit <b>7008</b> of the receiving system may be detachably fixed to an external module. In this case, the receiving system is interfaced with the external module through a common interface (CI). In other words, the external module may receive the data scrambled by the receiving system through the common interface, thereby performing the descrambling process of the received data. Alternatively, the external module may also transmit only the information required for the descrambling process to the receiving system. The common interface is configured on a physical layer and at least one protocol layer. Herein, in consideration of any possible expansion of the protocol layer in a later process, the corresponding protocol layer may be configured to have at least one layer that can each provide an independent function.
0630The external module may either consist of a memory or card having information on the key used for the scrambling process and other authentication information but not including any descrambling function, or consist of a card having the above-mentioned key information and authentication information and including the descrambling function. Both the receiving system and the external module should be authenticated in order to provide the user with the paid broadcasting service provided (or transmitted) from the transmitting system. Therefore, the transmitting system can only provide the corresponding paid broadcasting service to the authenticated pair of receiving system and external module.
0631Additionally, an authentication process should also be performed between the receiving system and the external module through the common interface. More specifically, the module may communicate with the system manager <b>7015</b> included in the receiving system through the common interface, thereby authenticating the receiving system. Alternatively, the receiving system may authenticate the module through the common interface. Furthermore, during the authentication process, the module may extract the unique ID of the receiving system and its own unique ID and transmit the extracted IDs to the transmitting system. Thus, the transmitting system may use the transmitted ID values as information determining whether to start the requested service or as payment information. Whenever necessary, the system manager <b>7015</b> transmits the payment information to the remote transmitting system through the telecommunication module <b>7019</b>.
0632The authentication unit <b>7008</b> authenticates the corresponding receiving system and/or the external module. Then, if the authentication process is successfully completed, the authentication unit <b>7008</b> certifies the corresponding receiving system and/or the external module as a legitimate system and/or module entitled to receive the requested paid broadcasting service. In addition, the authentication unit <b>7008</b> may also receive authentication-associated information from a mobile telecommunications service provider to which the user of the receiving system is subscribed, instead of the transmitting system providing the requested broadcasting service. In this case, the authentication-association information may either be scrambled by the transmitting system providing the broadcasting service and, then, transmitted to the user through the mobile telecommunications service provider, or be directly scrambled and transmitted by the mobile telecommunications service provider. Once the authentication process is successfully completed by the authentication unit <b>7008</b>, the receiving system may descramble the scrambled broadcasting contents received from the transmitting system. At this point, the descrambling process is performed by the first and second descramblers <b>7004</b> and <b>7007</b>. Herein, the first and second descramblers <b>7004</b> and <b>7007</b> may be included in an internal module or an external module of the receiving system.
0633The receiving system is also provided with a common interface for communicating with the external module including the first and second descramblers <b>7004</b> and <b>7007</b>, so as to perform the descrambling process. More specifically, the first and second descramblers <b>7004</b> and <b>7007</b> may be included in the module or in the receiving system in the form of hardware, middleware or software. Herein, the descramblers <b>7004</b> and <b>7007</b> may be included in any one of or both of the module and the receiving system. If the first and second descramblers <b>7004</b> and <b>7007</b> are provided inside the receiving system, it is advantageous to have the transmitting system (i.e., at least any one of a service provider and a broadcast station) scramble the corresponding data using the same scrambling method.
0634Alternatively, if the first and second descramblers <b>7004</b> and <b>7007</b> are provided in the external module, it is advantageous to have each transmitting system scramble the corresponding data using different scrambling methods. In this case, the receiving system is not required to be provided with the descrambling algorithm corresponding to each transmitting system. Therefore, the structure and size of receiving system may be simplified and more compact. Accordingly, in this case, the external module itself may be able to provide CA functions, which are uniquely and only provided by each transmitting systems, and functions related to each service that is to be provided to the user. The common interface enables the various external modules and the system manager <b>7015</b>, which is included in the receiving system, to communicate with one another by a single communication method. Furthermore, since the receiving system may be operated by being connected with at least one or more modules providing different services, the receiving system may be connected to a plurality of modules and controllers.
0635In order to maintain successful communication between the receiving system and the external module, the common interface protocol includes a function of periodically checking the status of the opposite correspondent. By using this function, the receiving system and the external module is capable of managing the status of each opposite correspondent. This function also reports the user or the transmitting system of any malfunction that may occur in any one of the receiving system and the external module and attempts the recovery of the malfunction.
0636In yet another example, the authentication process may be performed through software. More specifically, when a memory card having CAS software downloaded, for example, and stored therein in advanced is inserted in the receiving system, the receiving system receives and loads the CAS software from the memory card so as to perform the authentication process. In this example, the CAS software is read out from the memory card and stored in the first memory <b>7012</b> of the receiving system. Thereafter, the CAS software is operated in the receiving system as an application program. According to an embodiment of the present invention, the CAS software is mounted on (or stored) in a middleware platform and, then executed. A Java middleware will be given as an example of the middleware included in the present invention. Herein, the CAS software should at least include information required for the authentication process and also information required for the descrambling process.
0637Therefore, the authentication unit <b>7008</b> performs authentication processes between the transmitting system and the receiving system and also between the receiving system and the memory card. At this point, as described above, the memory card should be entitled to receive the corresponding data and should include information on a normal receiving system that can be authenticated. For example, information on the receiving system may include a unique number, such as a standardized serial number of the corresponding receiving system. Accordingly, the authentication unit <b>7008</b> compares the standardized serial number included in the memory card with the unique information of the receiving system, thereby performing the authentication process between the receiving system and the memory card.
0638If the CAS software is first executed in the Java middleware base, then the authentication between the receiving system and the memory card is performed. For example, when the unique number of the receiving system stored in the memory card conforms to the unique number of the receiving system read from the system manager <b>7015</b>, then the memory card is verified and determined to be a normal memory card that may be used in the receiving system. At this point, the CAS software may either be installed in the first memory <b>7012</b> upon the shipping of the present invention, or be downloaded to the first memory <b>7012</b> from the transmitting system or the module or memory card, as described above. Herein, the descrambling function may be operated by the data broadcasting application manger <b>7016</b> as an application program.
0639Thereafter, the CAS software parses the EMM/ECM packets outputted from the demultiplexer <b>7003</b>, so as to verify whether the receiving system is entitled to receive the corresponding data, thereby obtaining the information required for descrambling (i.e., the CW) and providing the obtained CW to the descramblers <b>7004</b> and <b>7007</b>. More specifically, the CAS software operating in the Java middleware platform first reads out the unique (or serial) number of the receiving system from the corresponding receiving system and compares it with the unique number of the receiving system transmitted through the EMM, thereby verifying whether the receiving system is entitled to receive the corresponding data. Once the receiving entitlement of the receiving system is verified, the corresponding broadcasting service information transmitted to the ECM and the entitlement of receiving the corresponding broadcasting service are used to verify whether the receiving system is entitled to receive the corresponding broadcasting service. Once the receiving system is verified to be entitled to receive the corresponding broadcasting service, the authentication key transmitted to the EMM is used to decode (or decipher) the encoded CW, which is transmitted to the ECM, thereby transmitting the decoded CW to the descramblers <b>7004</b> and <b>7007</b>. Each of the descramblers <b>7004</b> and <b>7007</b> uses the CW to descramble the broadcasting service.
0640Meanwhile, the CAS software stored in the memory card may be expanded in accordance with the paid service which the broadcast station is to provide. Additionally, the CAS software may also include other additional information other than the information associated with the authentication and descrambling. Furthermore, the receiving system may download the CAS software from the transmitting system so as to upgrade (or update) the CAS software originally stored in the memory card. As described above, regardless of the type of broadcast receiving system, as long as an external memory interface is provided, the present invention may embody a CAS system that can meet the requirements of all types of memory card that may be detachably fixed to the receiving system. Thus, the present invention may realize maximum performance of the receiving system with minimum fabrication cost, wherein the receiving system may receive paid broadcasting contents such as broadcast programs, thereby acknowledging and regarding the variety of the receiving system. Moreover, since only the minimum application program interface is required to be embodied in the embodiment of the present invention, the fabrication cost may be minimized, thereby eliminating the manufacturer's dependence on CAS manufacturers. Accordingly, fabrication costs of CAS equipments and management systems may also be minimized.
0641Meanwhile, the descramblers <b>7004</b> and <b>7007</b> may be included in the module either in the form of hardware or in the form of software. In this case, the scrambled data that being received are descrambled by the module and then demodulated. Also, if the scrambled data that are being received are stored in the third memory <b>7018</b>, the received data may be descrambled and then stored, or stored in the memory at the point of being received and then descrambled later on prior to being played (or reproduced). Thereafter, in case scramble/descramble algorithms are provided in the storage controller <b>7017</b>, the storage controller <b>7017</b> scrambles the data that are being received once again and then stores the re-scrambled data to the third memory <b>7018</b>.
0642In yet another example, the descrambled broadcasting contents (transmission of which being restricted) are transmitted through the broadcasting network. Also, information associated with the authentication and descrambling of data in order to disable the receiving restrictions of the corresponding data are transmitted and/or received through the telecommunications module <b>7019</b>. Thus, the receiving system is able to perform reciprocal (or two-way) communication. The receiving system may either transmit data to the telecommunication module within the transmitting system or be provided with the data from the telecommunication module within the transmitting system. Herein, the data correspond to broadcasting data that are desired to be transmitted to or from the transmitting system, and also unique information (i.e., identification information) such as a serial number of the receiving system or MAC address.
0643The telecommunication module <b>7019</b> included in the receiving system provides a protocol required for performing reciprocal (or two-way) communication between the receiving system, which does not support the reciprocal communication function, and the telecommunication module included in the transmitting system. Furthermore, the receiving system configures a protocol data unit (PDU) using a tag-length-value (TLV) coding method including the data that are to be transmitted and the unique information (or ID information). Herein, the tag field includes indexing of the corresponding PDU. The length field includes the length of the value field. And, the value field includes the actual data that are to be transmitted and the unique number (e.g., identification number) of the receiving system.
0644The receiving system may configure a platform that is equipped with the Java platform and that is operated after downloading the Java application of the transmitting system to the receiving system through the network. In this case, a structure of downloading the PDU including the tag field arbitrarily defined by the transmitting system from a storage means included in the receiving system and then transmitting the downloaded PDU to the telecommunication module <b>7019</b> may also be configured. Also, the PDU may be configured in the Java application of the receiving system and then outputted to the telecommunication module <b>7019</b>. The PDU may also be configured by transmitting the tag value, the actual data that are to be transmitted, the unique information of the corresponding receiving system from the Java application and by performing the TLV coding process in the receiving system. This structure is advantageous in that the firmware of the receiving system is not required to be changed even if the data (or application) desired by the transmitting system is added.
0645The telecommunication module within the transmitting system either transmits the PDU received from the receiving system through a wireless data network or configures the data received through the network into a PDU which is transmitted to the host. At this point, when configuring the PDU that is to be transmitted to the host, the telecommunication module within the transmitting end may include unique information (e.g., IP address) of the transmitting system which is located in a remote location. Additionally, in receiving and transmitting data through the wireless data network, the receiving system may be provided with a common interface, and also provided with a WAP, CDMA 1×EV-DO, which can be connected through a mobile telecommunication base station, such as CDMA and GSM, and also provided with a wireless LAN, mobile internet, WiBro, WiMax, which can be connected through an access point. The above-described receiving system corresponds to the system that is not equipped with a telecommunication function. However, a receiving system equipped with telecommunication function does not require the telecommunication module <b>7019</b>.
0646The broadcasting data being transmitted and received through the above-described wireless data network may include data required for performing the function of limiting data reception. Meanwhile, the demultiplexer <b>7003</b> receives either the real-time data outputted from the demodulating unit <b>7002</b> or the data read from the third memory <b>7018</b>, thereby performing demultiplexing. In this embodiment of the present invention, the demultiplexer <b>7003</b> performs demultiplexing on the enhanced data packet. Similar process steps have already been described earlier in the description of the present invention. Therefore, a detailed of the process of demultiplexing the enhanced data will be omitted for simplicity.
0647The first descrambler <b>7004</b> receives the demultiplexed signals from the demultiplexer <b>7003</b> and then descrambles the received signals. At this point, the first descrambler <b>7004</b> may receive the authentication result received from the authentication unit <b>7008</b> and other data required for the descrambling process, so as to perform the descrambling process. The audio decoder <b>7005</b> and the video decoder <b>7006</b> receive the signals descrambled by the first descrambler <b>7004</b>, which are then decoded and outputted. Alternatively, if the first descrambler <b>7004</b> did not perform the descrambling process, then the audio decoder <b>7005</b> and the video decoder <b>7006</b> directly decode and output the received signals. In this case, the decoded signals are received and then descrambled by the second descrambler <b>7007</b> and processed accordingly.
0000Other Embodiment of Transmitting System
0648In other embodiment of a transmitting system, it is intended to transmit mobile service data based on Internet Protocol (IP).
0649In the embodiment of the present invention, main service data are transmitted based on MPEG-2, and mobile service data are transmitted based on IP.
0650<figref idref="DRAWINGS">FIG. 73</figref> illustrates an example of a protocol stack for providing a main service based on MPEG-2.
0651In <figref idref="DRAWINGS">FIG. 73</figref>, A/V streamings for a main service are elementary streams (ES), and are packetized in a packetized elementary stream (PES). The PES packets are again packetized in MPEG-2 TS of 188-byte unit. Signaling information such as PSI/PSIP data, which includes configuration information of each service, is sectioned. In other words, signaling information such as the PSI/PSIP tables is divided into a plurality of sections. For example, VCT within the PSIP can be divided into 256 sections. At this time, although one section can include several kinds of virtual channel information, one kind of virtual channel information is not divided into two or more sections. Hereinafter, a table type of signaling information will be referred to as program table information or program table in the present invention.
0652Data broadcasting is sectioned by a digital storage media-command and control (DSM-CC) scheme. The DSM-CC section is again packetized in MPEG-2 TS of 188-byte unit. The IP datagram for IP multicast is encapsulated in a DSM-CC addressable section structure, and the encapsulated DSM-CC addressable section is again packetized in MPEG-2 TS of 188-byte unit. The TS packetization is performed in a network layer.
0653The PES type TS packets or the section type TS packets packetized as above are modulated in a physical layer in accordance with a previously determined transmission scheme, for example, VSB transmission scheme, and then transmitted to the receiving system. In other words, the physical layer provides a main service using the VSB transmission scheme, and corresponds to a first layer of an open systems interconnection (OSI) model.
0654<figref idref="DRAWINGS">FIG. 74</figref> illustrates an example of a protocol stack for a mobile service based on IP. <figref idref="DRAWINGS">FIG. 74</figref> is an example of a protocol stack for a mobile service through encapsulated IP datagrams.
0655In other words, in <figref idref="DRAWINGS">FIG. 74</figref>, signaling information for a mobile service is encapsulated in a section structure such as PSI/PSIP. A/V streaming for a mobile service is packetized in IP layer in accordance with a real time protocol (RTP) scheme as shown in (a) of <figref idref="DRAWINGS">FIG. 75</figref>. The RTP packets are again packetized in accordance with a user datagram protocol (UDP) scheme, and the RTP/UDP packets are again packetized in accordance with the IP scheme to obtain RTP/UDP/IP packet data. For convenience of description, the packetized RTP/UDP/IP packet data will be referred to as IP datagram in the present invention.
0656The IP datagram is encapsulated in a DSM-CC addressable section structure, and the encapsulated DSM-CC addressable section is again packetized in MPEG-2 TS of 188-byte unit as shown in (b) of <figref idref="DRAWINGS">FIG. 75</figref>.
0657(a) and (b) of <figref idref="DRAWINGS">FIG. 75</figref> illustrate examples of TS packet mapping of the IP datagram through the DSM-CC addressable section.
0658In other words, one addressable section is additionally provided with an RTP header, a UDP header, an IP header, and an addressable section header at the front of A/V data, and is also additionally provided with stuffing data (optional), and CRC at the rear of A/V data, as shown in (a) of <figref idref="DRAWINGS">FIG. 75</figref>. This addressable section is divided in a fixed length, i.e., 184-byte unit, as shown in (b) of <figref idref="DRAWINGS">FIG. 75</figref>, and is additionally provided with a TS packet header of 4 bytes to constitute TS packets of 188 bytes.
0659In <figref idref="DRAWINGS">FIG. 74</figref>, file/data download is packetized in accordance with a file transfer protocol scheme, and the file transfer protocol packet is again packetized in accordance with an asynchronous layered coding/layered coding transport (ALC/LCT) scheme. The ALC/LCT packet is again packetized in accordance with a UDP scheme, and the ALC/LCT/UDP packet is again packetized in accordance with an IP scheme to obtain ALC/LCT/UDP/IP packet data. For convenience of description, the packetized ALC/LCT/UDP/IP packet data will be referred to as the IP datagram in the present invention. The IP datagram is encapsulated in a DSM-CC addressable section structure, and the encapsulated DSM-CC addressable section is again packetized in MPEG-2 TS of 188-byte unit.
0660Furthermore, the UDP multicast is packetized in accordance with the UDP scheme, and the UDP packet is again packetized in accordance with the IP scheme. The IP datagram packetized in accordance with the IP scheme is encapsulated in a DSM-CC addressable section structure, and the encapsulated DSM-CC addressable section is again packetized in MPEG-2 TS of 188-byte unit.
0661The MPEG-2 TS packets are modulated in a mobile physical layer in accordance with a previously determined transmission scheme, for example, VSB transmission scheme, and then transmitted to the receiving system.
0662If the IP based mobile service is provided as shown in <figref idref="DRAWINGS">FIG. 74</figref>, all the data can be divided into the IP datagram and program table information of a section format (i.e., the PSI/PSIP data).
0663Since the IP datagram and the program table information such as the PSI/PSIP data are transmitted in MPEG-2 TS format, they may be accompanied with overhead. In other words, information of the TS packet header included per TS packet may act as overhead.
0664In order to solve this overhead, <figref idref="DRAWINGS">FIG. 76</figref> illustrates another example of a protocol stack for a mobile service based on IP.
0665In <figref idref="DRAWINGS">FIG. 76</figref>, an adaptation layer is included between the IP layer and the physical layer, so that the IP datagram and program table information (i.e., the PSI/PSIP data) can be transmitted without MPEG-2 TS format. Since an upper layer including the IP layer of <figref idref="DRAWINGS">FIG. 76</figref> has the same structure as that of <figref idref="DRAWINGS">FIG. 75</figref>, its detailed description will be omitted.
0666In <figref idref="DRAWINGS">FIG. 76</figref>, signaling information for a mobile service is encapsulated in program table information structure such as a PSI/PSIP section, and will be referred to as PSI/PSIP data or program table information for convenience of description. A/V streaming for a mobile service is additionally provided with an RTP header, a UDP header, and an IP header, sequentially, as shown in <figref idref="DRAWINGS">FIG. 77</figref>, so as to constitute one IP datagram. As another embodiment of the present invention, a transmission parameter of signaling information for a mobile service may be constituted by the IP datagram.
0667The adaptation layer is a data link layer which divides the IP datagram from the program table information and connects the divided data with each other to allow the upper layer to process the data.
0668In other words, the adaptation layer generates RS frame, which includes program table information, IP datagram, and identification information to divide program table information and the IP datagram.
0669<figref idref="DRAWINGS">FIG. 78</figref> illustrates another example of the RS frame generated in the adaptation layer according to the embodiment of the present invention.
0670In one RS frame, a length of column (i.e., the number of rows) is 187 bytes, and a length of row (i.e., the number of columns) is N bytes, wherein the N may depend on signaling information such as a transmission parameter. The transmission parameter (or TPC information) can include sub-frame information, slot information, parade related information (for example, parade ID, parade repetition period, etc.), data group information with sub-frame, RS frame mode information, RS code mode information, SCCC block information, SCCC outer code mode information, FIC version information, etc.
0671Also, the N may depend on regions within a data group to which the RS frame will be allocated. This is because that the probability of error is reduced in the order of A>B>C>D within the data group.
0672According to the embodiment of the present invention, the N is equal to or greater than 187. In other words, the RS frame of <figref idref="DRAWINGS">FIG. 78</figref> has a byte size of N(row)*187(column).
0673For convenience of description, each row of the N bytes will be referred to as MPH service data packet in the present invention. The MPH service data packet can be comprised of MPH header of 2 bytes and payload of N−2 bytes. In this case, the MPH header region of 2 bytes is allocated exemplarily. Since the MPH header region may depend on a designer, the present invention is not limited to the above example.
0674The RS frame is generated by program table information of N−2(row)*187(column) byte size and/or IP datagram. Also, one RS frame can include program table information and IP datagram corresponding to one or more mobile services. For example, program table information and IP datagram of two kinds of mobile services such as news and stock can be included in one RS frame.
0675The program table information or the IP datagram is allocated to payload within the MPH service data packet constituting the RS frame.
0676At this time, according to the embodiment of the present invention, the program table information and the IP datagram are not together allocated to one MPH service data packet.
0677In <figref idref="DRAWINGS">FIG. 78</figref>, the program table information are allocated to two MPH service data packets within one RS frame, and the IP datagram is allocated to the other MPH service data packets.
0678In <figref idref="DRAWINGS">FIG. 78</figref>, the position of the MPH service data packets within one RS frame, to which the program table information such as the PSI/PSIP data are allocated, and the number of the MPH service data packets are illustrated exemplarily. Since the position of the MPH service data packets and the number of the MPH service data packets may depend on a designer, the present invention will not be limited to the above example.
0679When the program table information or the IP datagram is allocated to one MPH service data packet, if the corresponding MPH service data packet including the MPH header does not reach N bytes, stuffing bytes can be allocated to the other part. For example, after the program table information are allocated to one MPH service data packet, the length of the MPH service data packet including the MPH header is N−20 bytes, stuffing bytes can be allocated to the other 20 bytes.
0680Also, the program table information can include a plurality of tables, for example, PMT, PAT, VCT, MGT, RRT, ETT, and EIT data. The plurality of table data within the program table information may sequentially be allocated to one MPH service data packet in a predetermined order as shown in <figref idref="DRAWINGS">FIG. 78</figref>. Alternatively, the data corresponding to one table may be allocated to one MPH service data packet.
0681<figref idref="DRAWINGS">FIG. 79</figref> illustrates an example of fields allocated to the MPH header region within the MPH service data packet according to the embodiment of the present invention. Examples of the fields include a type_indicator field, an error_indicator field, a priority field (or stuff indicator), and a pointer field.
0682The type_indicator field can allocate 3 bits, for example, and expresses a type of data allocated to payload within the corresponding MPH service data packet. In other words, the type_indicator field indicates whether data of the payload is IP datagram or signaling information such as program table information.
0683At this time, each data type constitutes one logical channel. In the logical channel which transmits the IP datagram, several mobile services are multiplexed and then transmitted. Each mobile service undergoes demultiplexing in the IP layer.
0684The error_indicator field can allocate 1 bit, for example, and expresses whether the corresponding MPH service data packet has an error. For example, if the error_indicator field has a value of 0, it means that there is no error in the corresponding MPH service data packet. If the error_indicator field has a value of 1, it means that there may be an error in the corresponding MPH service data packet.
0685The priority field can allocate 1 bit, for example, and expresses region information within a data group to which data of payload within the corresponding MPH service data packet will be inserted. For example, if the priority field has a value of 1, it means that the data of payload within the corresponding MPH service data packet is data to be inserted to A/B region within the data group. If the priority field has a value of 0, it means that the data of payload within the corresponding MPH service data packet is data to be inserted to C/D region within the data group. The stuff indicator instead of the priority field can be assigned. The stuff indicator field may indicate whether Stuff byte exists in the payload of MPH service data packet.
0686The pointer field can allocate 11 bits, for example, and expresses position information where new data (i.e., new signaling information or new IP datagram) starts in the corresponding MPH service data packet.
0687For example, if IP datagram <b>1</b> and IP datagram <b>2</b> are allocated to the first MPH service data packet within the RS frame as shown in <figref idref="DRAWINGS">FIG. 78</figref>, the pointer field value expresses the start position of the IP datagram <b>2</b> within the MPH service data packet.
0688Also, if there is no new data in the corresponding MPH service data packet, the corresponding field value is expressed as a maximum value exemplarily. In the present invention, since 11 bits are allocated to the pointer field, if 2047 is expressed as the pointer field value, it means that there is no new data in the packet.
0689It is to be understood that the order, the position, and the meaning of the field allocated to the header within the MPH service data packet illustrated in <figref idref="DRAWINGS">FIG. 79</figref> are exemplarily illustrated for understanding of the present invention. Since the order, the position and the meaning of the field allocated to the header within the MPH service data packet and the number of additionally allocated fields can easily be modified by those skilled in the art, the present invention will not be limited to the above example.
0690<figref idref="DRAWINGS">FIG. 80(a)</figref> and <figref idref="DRAWINGS">FIG. 80(b)</figref> illustrate another examples of an RS frame according to the embodiment of the present invention. (a) of <figref idref="DRAWINGS">FIG. 80</figref> illustrates an example of RS frame to be allocated to A/B region within the data group, and (b) of <figref idref="DRAWINGS">FIG. 80</figref> illustrates an example of RS frame to be allocated to C/D region within the data group.
0691In (a) and (b) of <figref idref="DRAWINGS">FIG. 80</figref>, a column length (i.e., the number of rows) of the RS frame to be allocated to the A/B region and a column length (i.e., the number of rows) of the RS frame to be allocated to the C/D region are 187 equally. However, row lengths (i.e, the number of columns) may be different from each other. In the present invention, the data group is exemplarily divided into the regions A, B, C and D depending on interference level of the main service data. Interference of the main service data is reduced in the order of the A>B>C>D regions. If interference of the main service data becomes smaller, receiving performance becomes better.
0692In the present invention, the RS frame to be allocated to the A/B region within the data group will be referred to as primary RS frame, and the RS frame to be allocated to the C/D region within the data group will be referred to as secondary RS frame.
0693According to the embodiment of the present invention, when the row length of the primary RS frame to be allocated to the A/B region within the data group is N1 bytes and the row length of the secondary RS frame to be allocated to the C/D region within the data group is N2 bytes, a condition of N1>N2 is satisfied. In this case, N1 and N2 can be varied depending on the transmission parameter or a region of the data group, to which the corresponding RS frame will be transmitted.
0694For convenience of the description, each row of the N1 and N2 bytes will be referred to as the MPH service data packet. The MPH service data packet within the RS frame to be allocated to the A/B region within the data group can be comprised of MPH header of 2 bytes and payload of N1−2 bytes. Also, the MPH service data packet within the RS frame to be allocated to the C/D region within the data group can be comprised of MPH header of 2 bytes and payload of N2−2 bytes.
0695In this case, the MPH header of 2 bytes is only example. Since the allocation bytes of the MPH header can be varied depending on a designer, the present invention will not be limited to the above example. The order, position, and meaning of the fields allocated to the MPH header of each MPH service data packet in <figref idref="DRAWINGS">FIG. 79</figref> can be applied to those of (a) and (b) of <figref idref="DRAWINGS">FIG. 80</figref>.
0696In the present invention, the primary RS frame for the A/B region and the secondary RS frame for the C/D region within the data group include at least one of the program table information and the IP datagram. Also, one RS frame can include IP datagram corresponding to one or more mobile services.
0697The primary RS frame in (a) of <figref idref="DRAWINGS">FIG. 80</figref> exemplarily includes program table information and IP datagram for two kinds of mobile services. On the other hand, the secondary RS frame in <figref idref="DRAWINGS">FIG. 80(b)</figref> exemplarily includes IP datagram for two kinds of mobile services.
0698In (a) of <figref idref="DRAWINGS">FIG. 80</figref>, program table information for two kinds of mobile services are allocated to two MPH service data packets within one RS frame, and IP datagram for two kinds of mobile services is allocated to the other MPH service data packet.
0699The position of the MPH service data packet within the RS frame, to which the program table information are allocated, and the number of the MPH service data packets are exemplarily illustrated in (a) of <figref idref="DRAWINGS">FIG. 80</figref>. Since they can be varied depending on a designer, the present invention will not be limited to the above example.
0700Corresponding parts of <figref idref="DRAWINGS">FIG. 78</figref> can be applied to the other parts, which are not described in (a) and (b) of <figref idref="DRAWINGS">FIG. 80</figref>.
0701In the embodiment of the present invention, the RS frame of <figref idref="DRAWINGS">FIG. 78</figref> or <figref idref="DRAWINGS">FIG. 80(a)</figref> and <figref idref="DRAWINGS">FIG. 80(b)</figref> is generated in the MPH frame encoder <b>301</b> of the pre-processor <b>230</b>.
0702The MPH service data packet within the RS frame as shown in <figref idref="DRAWINGS">FIG. 78</figref> or (a) and (b) of <figref idref="DRAWINGS">FIG. 80</figref> is again extended to a plurality of MPH service data packets.
0703<figref idref="DRAWINGS">FIG. 81(a)</figref> to <figref idref="DRAWINGS">FIG. 81(f)</figref> illustrate examples of a procedure of extending the MPH service data packet to a plurality of MPH service data packets.
0704In (a) to (f) of <figref idref="DRAWINGS">FIG. 81</figref>, N MPH service data packets within the RS frame having N(row)*187(column) byte size are exemplarily extended to 2N MPH service data packets.
0705If the RS frame having N(row)*187(column) byte size is divided into 187-byte unit in a row direction as shown in (a) of <figref idref="DRAWINGS">FIG. 81</figref>, one RS frame is divided into N temporary packets of 187 bytes as shown in (b) of <figref idref="DRAWINGS">FIG. 81</figref>. In other words, If N temporary packets of 187 bytes divided as shown in (b) of <figref idref="DRAWINGS">FIG. 81</figref> are sequentially collected, the RS frame as shown in (a) of <figref idref="DRAWINGS">FIG. 81</figref> is obtained.
0706The temporary packets of 187 bytes divided as shown in (b) of <figref idref="DRAWINGS">FIG. 81</figref> are again divided into a plurality of temporary packets. At this time, when the temporary packets of 187 bytes are divided into a plurality of packets, the plurality of packets may have the same size or different sizes.
0707In (c) of <figref idref="DRAWINGS">FIG. 81</figref>, the temporary packets of 187 bytes are exemplarily divided into temporary packets of 102 bytes and temporary packets of 85 bytes. This is only one example, and the scope of the present invention will not be limited to the above numerical values.
0708For convenience of the description in the present invention, the temporary packets of 102 bytes will be referred to as first temporary packets, and the temporary packets of 85 bytes will be referred to as second temporary packets.
0709In the present invention, as shown in (d) of <figref idref="DRAWINGS">FIG. 81</figref>, a temporary header mph_stl_header of 8 bytes is additionally provided at the front of the first temporary packets, and dummy bytes of 74 bytes are additionally provided at the rear of the first temporary packets, whereby the first temporary packets of 184 bytes are obtained. Also, a temporary header of 8 bytes is additionally provided at the front of the second temporary packets, and dummy bytes of 91 bytes are additionally provided at the rear of the second temporary packets, whereby the second temporary packets of 184 bytes are obtained.
0710In other words, one temporary packet of 187 bytes is extended to two temporary packets of 184 bytes.
0711<figref idref="DRAWINGS">FIG. 82</figref> illustrates an example of fields allocated to header regions of the first and second temporary packets according to the present invention. The fields can include parade_id field, region_id field, pkt_number field, max_pkt_number field, parade_size field, sccc_mode field, and rs_mode field.
0712The parade_id field can allocate 8 bits, for example, and represents unique identifier (id) of parade to which the corresponding RS frame will be transmitted.
0713The region_id field can allocate 1 bit, for example, and represents information of a region to which the corresponding RS frame will be transmitted. For example, if the region_id field has a value of ‘0’, the RS frame is allocated to the A/B region. If the region_id field has a value of ‘1’, the RS frame is allocated to the C/D region.
0714A reserved field of 7 bits can be allocated next to the region_id field for future use.
0715The pkt_number field can allocate 16 bits, for example, and represents the order of 184-byte packets extended to two time as shown in (d) of <figref idref="DRAWINGS">FIG. 81</figref>. For example, the pkt_number field has a value of 0 to max_packet number (for example, 2N−1). At this time, the pkt_number field value of even numbers including 0 is expressed in the packets extended from 102 bytes, and the pkt_number field value of odd numbers is expressed in the packets extended from 85 bytes.
0716The max_packet_number field can allocate 16 bits, for example, and represents a maximum value where the pkt_number field value will reach in the corresponding RS frame. For example, 2N−1 can be expressed as the max_packet_number field value.
0717The parade_size field can allocate 5 bits, for example, and represents one parade size.
0718The sccc_mode field can allocate 3 bits, for example, and represents a coding rate of each region within the data group. For example, the SCCC outer code mode within the TPC information of <figref idref="DRAWINGS">FIG. 31</figref> can be expressed as it is.
0719The rs_mode field can allocate 4 bits, for example, and represents RS code mode of each region within the data group.
0720A reserved field of 6 bits can be allocated next to the rs_mode field for future use.
0721The order, position, and meaning of the fields allocated to the temporary header within the extended temporary packets illustrated in <figref idref="DRAWINGS">FIG. 82</figref> are only examples for understanding of the present invention. Since the order, position, and meaning of the fields allocated to the temporary header and the number of additionally allocated fields can easily be varied depending on a designer, the present invention will not be limited to the above examples.
0722As described above, if the temporary header of 8 bytes and dummy bytes of 74 bytes or 91 bytes are added to the first and second temporary packets, the RS frame of N(row)*187(column) bytes can be extended to 2N packets of 184 bytes as shown in (e) of <figref idref="DRAWINGS">FIG. 81</figref>. Namely, the RS frame of N(row)*187(column) bytes is extended to RS frame of 184 (row)*2N(column) bytes.
0723A MPEG header of 4 bytes as shown in <figref idref="DRAWINGS">FIG. 81(f)</figref> in added in each 184-byte packet within the extended RS frame as shown in <figref idref="DRAWINGS">FIG. 81(e)</figref> to configure 188-byte TS packet. Namely, the RS frame of 184(row)*2N(column) bytes is again extended to RS frame of 188(row)*2N(column) bytes.
0724According to the embodiment of the present invention, the generation of the RS frame illustrated in <figref idref="DRAWINGS">FIG. 78</figref> to <figref idref="DRAWINGS">FIG. 82</figref> and extension of each packet within the generated RS frame are performed by a service multiplexer.
0725<figref idref="DRAWINGS">FIG. 83</figref> illustrates another example of a service multiplexer according to the embodiment of the present invention.
0726The service multiplexer of <figref idref="DRAWINGS">FIG. 83</figref> is located in a studio of each broadcasting station, and can include a PSI/PSIP generator <b>8010</b>, an RS frame generator <b>8020</b>, a studio-to-transmitter link (STL) adaptor <b>8030</b>, and a transport multiplexer <b>8040</b>.
0727The transport multiplexer <b>8040</b> can include a main service multiplexer <b>8041</b>, and a transport stream (TS) packet multiplexer <b>8042</b>.
0728The RS frame generator <b>8020</b> corresponds to the adaptation layer of <figref idref="DRAWINGS">FIG. 76</figref>, and receives IP datagram and program table information of at least one kind of mobile service to constitute the RS frame as shown in <figref idref="DRAWINGS">FIG. 78</figref> or (a) and (b) of <figref idref="DRAWINGS">FIG. 80</figref>.
0729For example, in case of <figref idref="DRAWINGS">FIG. 78</figref>, the RS frame is the same as that 187 MPH service data packets are comprised of MPH header of 2 bytes and payload of N−2 bytes.
0730The RS frame generated by the RS frame generator <b>8020</b> is input to the STL adaptor <b>8030</b>.
0731The STL adaptor <b>8030</b> performs the procedure of (a) to (f) of <figref idref="DRAWINGS">FIG. 81</figref> for the RS frame output from the RS frame generator <b>8020</b> to extend <b>187</b> packets of N bytes to 2N TS packets of 188 bytes.
0732For convenience of the description, the TS packets of 188 bytes extended from the STL adaptor <b>8030</b> will be referred to as the mobile service data packets in the present invention.
0733Furthermore, at least one kind of main service data and the PSI/PSIP data generated for the main service by the PSI/PSIP generator <b>8010</b> are input to the main service multiplexer <b>8041</b> of the transport multiplexer <b>8040</b>. The main service multiplexer <b>8041</b> respectively encapsulates the input main service data and PSI/PSIP data in MPEG-2 TS packet format, and multiplexes the TS packets to output the multiplexed TS packets to the TS packet multiplexer <b>8042</b>. For convenience of the description, the data packets output from the main service multiplexer <b>8041</b> will be referred to as the main service data packets.
0734At this time, in order that the transmitter identifies the main service data packets from the mobile service data packets to process them, identification information is required. A value previously determined by agreement between the transmitter and the receiver may be used as the identification information, or separate data may be used as the identification information. Also, a value obtained by modifying a value of a previously set position within the corresponding data packet may be used as the identification information.
0735According to the embodiment of the present invention, different packet identifiers (PIDs) can respectively be allocated to the main service data packets and the mobile service data packets.
0736To this end, when the STL adaptor <b>8030</b> adds the MPEG header per packet of 184 bytes, PID agreed between the STL adaptor and the transmitter (exciter) can be set in the MPEG header.
0737According to another embodiment of the present invention, the main service data packets can be identified from the mobile service data packets by a synchronization byte value of the mobile service data packets, which is obtained by modifying synchronization bytes within the MPEG header of the mobile service data packets.
0738Since anything that can identify the main service data packets from the mobile service data packets can be used as the identification information, the present invention will not be limited to the above embodiments.
0739Meanwhile, the transport multiplexer used in the existing digital broadcasting system can be used as the transport multiplexer <b>8040</b>. Namely, in order to multiplex the mobile service data with the main service data and transmit them, a data rate of the main service is limited to a data rate of M Mbps, and L Mbps corresponding to the other data rate is allocated to the mobile service output from the STL adaptor <b>8030</b>. In this case, the existing transport multiplexer can be used as it is without any change. Then, the TS packet multiplexer <b>8042</b> multiplexes the main service data packets output from the main service multiplexer <b>8041</b> at a data rate of M Mbps with the mobile service data packets output from the STL adaptor <b>8030</b> at a data rate of L Mbps and transmits the multiplexed data packets to the transmitter.
0740However, there may be a case where the output data rate of the TS packet multiplexer <b>8042</b> does not reach 19.39 Mbps even though the output data rate L Mbps of the STL adaptor <b>8030</b> and the output data rate M Mbps of the main service multiplexer <b>8041</b> are added to each other.
0741In this case, the TS packet multiplexer <b>8042</b> receives null data packets of a data rate of (19.39-M-L) Mbps, multiplexes the null data packets with the main service data packets and the mobile service data packets, and output the multiplexed data packets. Even in this case, the identification information is included in the null data packets so that the transmitter can identify the null data packets.
0742In this case, the output data rate of the TS packet multiplexer <b>8042</b> can be adjusted to 19.39 Mbps.
0743In other words, since the mobile service data are extended by additional encoding in the transmitter, even though the STL adaptor <b>8030</b> allocates 187 bytes to two TS packets to obtain data of L Mbps, if the data rate of L Mbps is added to the output data rate of the main service multiplexer <b>8041</b>, the output data rate of the TS packet multiplexer <b>8042</b> may be smaller than 19.39 Mbps. In this case, the null data packets are added to the service data packets by the difference so that the output data rate of the TS packet multiplexer <b>8042</b> is adjusted to 19.39 Mbps.
0744In order that the transmitter can identify the main service data, the mobile service data, and the null data from one another, the service multiplexer can insert identification information. Since a method of inserting the identification information can refer to the service multiplexer of <figref idref="DRAWINGS">FIG. 14</figref>, its detailed description will be omitted.
0745As an example of the above transmitter, the transmitter of <figref idref="DRAWINGS">FIG. 15</figref> can be used. In this case, if the data packets are received from the service multiplexer, the demultiplexer <b>210</b> identifies whether the received data packets are the main service data packets, the mobile service data packets or the null data packets, by using the identification information (for example, PID within MPEG header) included in the corresponding data packets.
0746The null data packets identified by the demultiplexer <b>210</b> are disused without being processed, and the main service data packets are output to the packet jitter mitigator <b>220</b>. Since the operation after the main service data packets are processed can refer to the transmitter of <figref idref="DRAWINGS">FIG. 15</figref>, its detailed description will be omitted.
0747The mobile service data packets identified by the demultiplexer <b>210</b> are input to the pre-processor <b>230</b>.
0748The pre-processor <b>230</b> performs an inverse procedure of the procedure of (a) to (f) in <figref idref="DRAWINGS">FIG. 81</figref> to constitute the RS frame as shown in <figref idref="DRAWINGS">FIG. 78</figref> or the RS frame as shown in (a) and (b) of <figref idref="DRAWINGS">FIG. 80</figref>.
0749For example, the pre-processor <b>230</b> removes the MPEG header of 4 bytes added to the mobile service data packets, and collects all the data having the pkt_number field value of 0 to max_pkt_number among the data of which the parade_id field value and the region_id field value of the MPH header added to the first and second temporary packets of 184-byte unit is the same, whereby one RS frame having N*187 byte size can be obtained as shown in (a) of <figref idref="DRAWINGS">FIG. 81</figref>. mph_stl_header and the dummy bytes are not included in the RS frame. At this time, transmission parameters required pre-processing/post-processing of the corresponding RS frame can be determined as parade related information of mph_stl_header. Also, the transmission parameters are transmitted to the receiving system by being included in the region previously set within the data group, or by being included in the field synchronization region. In this case, examples of the transmission parameters include sub-frame information, slot information, parade related information (for example, parade ID, parade repetition period, etc.), data group information with sub-frame, RS frame mode information, RS code mode information, SCCC block information, SCCC outer code mode information, and FIC version information.
0750The procedure of constituting the RS frame from the mobile service data packets can be performed before or after randomizing in the MPH frame encoder <b>301</b> of the pre-processor <b>230</b>. If the procedure of constituting the RS frame is performed before randomizing, randomizing can be performed in MPH service data packet unit of N bytes. If the procedure of constituting the RS frame is performed after randomizing, randomizing can be performed in mobile service data packet unit of 187 bytes.
0751According to the embodiment of the present invention, the MPH frame encoder <b>301</b> performs an inverse procedure of (a) to (f) of <figref idref="DRAWINGS">FIG. 81</figref> after data randomizing, whereby the RS frame as shown in <figref idref="DRAWINGS">FIG. 78</figref> or the RS frame as shown in (a) and (b) of <figref idref="DRAWINGS">FIG. 80</figref> is constituted.
0752If the RS frame is constituted as shown in <figref idref="DRAWINGS">FIG. 78</figref> or (a) and (b) of <figref idref="DRAWINGS">FIG. 80</figref>, the MPH frame encoder <b>301</b> performs at least one of error encoding and error detection encoding in RS frame unit. In this case, it is possible to disperse burst error that can occur due to change of electric wave environment while giving robustness to the mobile service data, thereby coping with the electric wave environment which is rapidly changed.
0753Furthermore, the MPH frame encoder <b>301</b> can constitute a super frame by collecting a plurality of RS frames, and can perform row permutation in a super frame unit.
0754Error correction encoding, error detection encoding, and row permutation, which are performed by the MPH frame encoder <b>301</b>, will refer to the aforementioned description, and their detailed description will be omitted.
0755Furthermore, each block within the pre-processor next to the MPH frame encoder <b>301</b> will refer to the aforementioned description, and its detailed description will be omitted.
0756The packet multiplexer <b>240</b> provided at the output of the pre-processor <b>230</b> and the packet jitter mitigator <b>220</b> multiplexes the mobile service data packets output from the pre-processor <b>230</b> and the main service data packets output from the packet jitter mitigator <b>220</b> in accordance with the multiplexing method which is previously defined, and outputs the multiplexed data to the data randomizer <b>251</b> of the post-processor <b>250</b>.
0757<figref idref="DRAWINGS">FIG. 84</figref> illustrates an example of a multiplexing method of the packet multiplexer <b>240</b>. In other words, <figref idref="DRAWINGS">FIG. 84</figref> illustrates an example of multiplexing the main service data and the mobile service data so that three parades exist in one sub-frame and one or more mobile services are transmitted from each parade.
0758Each parade is repeated per parade_id to transmit the same mobile service. At this time, this transmission path will be referred to as a parade in the present invention. In other words, one or more parades are temporally multiplexed in one physical channel determined by frequency.
0759For example, mobile service <b>1</b> and mobile service <b>2</b> can be transmitted from parade alpha, mobile service <b>3</b> and mobile service <b>4</b> can be transmitted from parade beta, and mobile service <b>5</b> can be transmitted from parade gamma
0760At this time, each parade has information of unique ID (parade_id), parade repetition cycle, parade size (NoG), etc. This information can be transmitted to the receiving system by being included in a specific region of the RS frame as the transmission parameter (or TPC information).
0761At this time, one parade may transmit either one RS frame as shown in <figref idref="DRAWINGS">FIG. 78</figref> or two RS frames, i.e., a primary RS frame and a secondary RS frame as shown in (a) and (b) of <figref idref="DRAWINGS">FIG. 80</figref>. If one parade transmits both the primary RS frame and the secondary RS frame as shown in (a) and (b) of <figref idref="DRAWINGS">FIG. 80</figref>, the information that can identify the two RS frames can be transmitted to the receiving system by being included in the specific region of the RS frame as the transmission parameter (or TPC information).
0762The receiving system can control parade demultiplexing using this transmission parameter. In this case, region_id can be transmitted as information that can identify the primary RS frame from the secondary RS frame within one parade. The region_id represents information of a region within the data group to which data of the corresponding RS frame will be transmitted. For example, if the region_id has a value of 0, the data of the RS frame is allocated to the A/B region within the data group. If the region_id field has a value of 1, the RS frame is allocated to the C/D region.
0763At this time, the data of the A/B region and the data of the C/D region are those corresponding to the same parade, and a hierarchical mobile service or separate mobile services can be constituted using these data. According to the embodiment of the present invention, the A/B region and the C/D region within the data group are allocated to one parade.
0764The data of the RS frame transmitted to one parade constitute two logical channels through the MPH service data packets. One channel is for PSI/PSIP information, and the other channel is for IP datagram. The IP datagram is only transmitted to the channel for IP datagram. Multiplexing between components constituting the mobile service and multiplexing of the mobile services transmitted to one parade are performed in the IP layer.
0765The receiving system can identify each ensemble by combination of the parade_id and the region_id. The receiving system can also generate ensemble identifier (ensemble_id) by combination of the parade_id and the region_id.
0766In other words, one RS frame transmits one ensemble. The ensemble is a collection of services requiring the same quality of service (QoS) and encoded with the same FEC codes.
0767For example, if one parade is comprised of one RS frame, the ensemble, the RS frame, and the parade can be mapped at 1:1:1. For another example, if one parade is comprised of the primary RS frame and the secondary RS frame, the primary ensemble can be mapped with the primary RS frame and the secondary ensemble can be mapped with the secondary RS frame. In other words, the primary ensemble is transmitted through the primary RS frame of one parade, and the secondary ensemble is transmitted through the secondary RS frame of the parade.
0768Therefore, if the parade_id is combined with the region_id, the primary ensemble and the secondary ensemble can be identified from each other within one parade.
0769As another method of identifying the ensemble, at least one bit is added to the parade_id, for example, the left of the parade_id, so as to constitute ensemble_id, whereby each ensemble can be identified from another ensemble using the ensemble_id. In this case, the ensemble identifier (i.e., ensemble_id) includes parade identifier (i.e., parade_id).
0770For example, if the ensemble_id is for the primary Ensemble delivered through this Parade, the added MSB shall be ‘0’. Otherwise, if it is for the secondary Ensemble, the added MSB shall be ‘1’.
0771The receiving system can perform parade demultiplexing and power control using the parade_id. Also, the receiving system can perform demultiplexing of the ensemble by combining the parade_id with the region_id, or can perform demultiplexing of the ensemble using the ensemble_id obtained by adding one bit to the left of the parade_id.
0772In <figref idref="DRAWINGS">FIG. 85</figref>, an example of a procedure of temporally multiplexing three parades (parade alpha, parade beta, and parade gamma) in a physical channel determined by one frequency and multiplexing each parade with two logical channels (program table information channel and IP datagram channel) is illustrated using a protocol stack.
0773If the mobile service data are transmitted in a parade format as described above, the receiving system receives the mobile service data by turning on the power in only a slot to which parade of a desired mobile service is allocated and does not receive the data in the other slots by turning off the power in the other slots. As a result, power consumption of the receiving system can be reduced. This feature is especially useful for a portable receiver, which requires less power consumption.
0774For example, the mobile service which the receiving system desires to receive exists in parade alpha, the receiving system turns on the power in only the slot to which data of parade alpha is allocated as shown in (b) of <figref idref="DRAWINGS">FIG. 84</figref>.
0775Each block within the transmitter next to the packet multiplexer <b>240</b> will refer to the aforementioned description, and thus its detailed description will be omitted.
0776<figref idref="DRAWINGS">FIG. 86</figref> is a block diagram illustrating another example of a receiving system according to the embodiment of the present invention.
0777The receiving system of <figref idref="DRAWINGS">FIG. 86</figref> can include a tuner <b>8301</b>, a demodulating unit <b>8302</b>, a demultiplexer <b>8303</b>, a program table buffer <b>8304</b>, a program table decoder <b>8305</b>, a program table database (DB) <b>8306</b>, an IP datagram buffer <b>8307</b>, an IP filter <b>8308</b>, a data handler <b>8309</b>, a middleware engine <b>8310</b>, an A/V decoder <b>8311</b>, an A/V post-processor <b>8312</b>, an application manager <b>8313</b>, and a user interface <b>8316</b>. The application manager <b>8313</b> can include a channel manager <b>8314</b> and a service manager <b>8315</b>.
0778In <figref idref="DRAWINGS">FIG. 86</figref>, a flow of data is marked with a solid line, and a flow of control is marked with a dotted line.
0779The tuner <b>8301</b> tunes a frequency of a specific channel through any one of antenna, cable, satellite, performs down-conversion for the tuned frequency into an intermediate frequency signal, and outputs the resultant signal to the demodulating unit <b>8302</b>. At this time, the tuner <b>8301</b> is controlled by the channel manager <b>8314</b> of the application manager <b>8313</b>, and reports the result and strength of a broadcasting signal of the tuned channel to the channel manager <b>8314</b>. Examples of the data received to the frequency of the specific channel include main service data, mobile service data, table data for decoding of the main service data and the mobile service data, and transmission parameter.
0780The demodulating unit <b>8302</b> performs VSB demodulation and channel equalization for the signal output from the tuner <b>8301</b>, and then outputs the resultant signal by dividing the signal into the main service data and the mobile service data. The aforementioned demodulating unit illustrated in <figref idref="DRAWINGS">FIG. 36</figref> can be used as an example of the demodulating unit <b>8302</b>. However, it is to be understood that the demodulating unit is only an example, and the scope of the present invention is not limited to the above example.
0781Meanwhile, the transmitter can transmit signaling information (or TPC information) including the transmission parameter to at least one of the field synchronization region, the base data region, and the mobile service data region. Accordingly, the demodulating unit <b>8302</b> can extract the transmission parameter from the field synchronization region, the base data region, and the mobile service data region.
0782The transmission parameter can include sub-frame information, slot information, parade related information (for example, parade ID, parade repetition period, etc.), data group information with sub-frame, RS frame mode information, RS code mode information, SCCC block information, SCCC outer code mode information, FIC version information, etc.
0783The demodulating unit <b>8302</b> performs block decoding, RS frame decoding, etc. using the extracted transmission parameter. For example, the demodulating unit <b>8302</b> performs block decoding of each region within the data group with reference to SCCC related information (for example, SCCC block information and SCCC outer code mode) within the transmission parameter, and performs RS frame decoding of each region within the data group with reference to RS related information (for example, RS code mode).
0784According to the embodiment of the present invention, the RS frame including the mobile service data demodulated by the demodulating unit <b>8302</b> is exemplarily input to the demultiplexer <b>8303</b>.
0785In other words, the data input to the demultiplexer <b>8303</b> has RS frame data format as shown in <figref idref="DRAWINGS">FIG. 78</figref> or (a) and (b) of <figref idref="DRAWINGS">FIG. 80</figref>. Namely, the RS frame decoder within the demodulating unit <b>8302</b> performs an inverse procedure of that performed in the RS frame encoder of the transmitting system to correct errors within the RS frame, and then outputs the resultant data to the data de-randomizer. The data de-randomizer performs de-randomizing for the error-corrected RS frame in the inverse procedure of the transmitting system. As a result, the data de-randomizer can obtain the RS frame as shown in <figref idref="DRAWINGS">FIG. 78</figref> or (a) and (b) of <figref idref="DRAWINGS">FIG. 80</figref>.
0786The demultiplexer <b>8303</b> may receive the RS frame of every parade, or may receive only the RS frame of the parade, which includes a desired mobile service, in accordance with the power control. For example, if the demultiplexer <b>8303</b> receives the RS frame of every parade, the demultiplexer <b>8303</b> can demultiplex the parade, which includes a desired mobile service, using the parade_id.
0787At this time, since one parade transmits one or two RS frames and one ensemble is mapped with one RS frame, if one parade transmits two RS frames, the demultiplexer <b>8303</b> needs to identify the RS frame, which transmits ensemble including mobile service data to be decoded, from the parade which includes a desired mobile service. That is, when the inputted one parade or the demultiplexed parade of a plurality of parades transmits both the primary ensemble and the secondary ensemble, the demultiplexer <b>8303</b> selects any one of the primary ensemble and the secondary ensemble.
0788For example, the demultiplexer <b>8303</b> can demultiplex the RS frame, which transmits ensemble including mobile service data to be decoded, by combining the parade_id with the region_id within the transmission parameter. For another example, the demultiplexer <b>8303</b> can demultiplex the RS frame, which transmits ensemble including mobile service data to be decoded, using the ensemble_id obtained by adding one bit to the left of the parade_id.
0789The demultiplexer <b>8303</b> identifies whether the corresponding MPH service data packets are program table information or IP datagram, with reference to the MPH header of the MPH service data packet within the RS frame corresponding to the ensemble, which includes mobile service data to be decoded. The identified program table information are output to the program table buffer <b>8304</b>, and the IP datagram is output to the IP datagram buffer <b>8307</b>.
0790The program table buffer <b>8304</b> temporarily stores the program table information of section type and then outputs the data to the program table decoder <b>8305</b>.
0791The program table decoder <b>8305</b> divides tables using table id and section length within the program table information and then parses the sections of the divided tables. Subsequently, the program table decoder <b>8305</b> stores the parsed result in the program table DB <b>8306</b>. For example, the program table decoder <b>8305</b> collects sections having the same table identifier table_id to constitute tables and then parses the tables to store the parsed result in the program table DB <b>8306</b>.
0792The IP datagram buffer <b>8307</b> temporarily stores the IP datagram and then outputs the IP datagram to the IP filter <b>8308</b>.
0793The IP filter <b>8308</b> filters the IP datagram only corresponding to a desired mobile service under the control of the service manager <b>8315</b> and outputs the filtered IP datagram to the A/V decoder <b>8311</b> and/or the data handler <b>8309</b>. If the transmission parameter (or TPC information) is transmitted to the IP datagram, the IP filter <b>8308</b> divides the IP datagram, which includes the transmission parameter, under the control of the service manager <b>8315</b>, and outputs the divided IP datagram to the corresponding block (for example, program table DB, application manager, data handler, etc.).
0794The A/V decoder <b>8311</b> divides audio and video from the IP datagram, decodes the divided audio and video through each decoding algorithm, and then outputs the decoded result to the A/V post-processor <b>8312</b>. For example, at least one of AC-3 decoding algorithm, MPEG 2 audio decoding algorithm, MPEG 4 audio decoding algorithm, AAC decoding algorithm, AAC+ decoding algorithm, HE AAC decoding algorithm, AAC SBR decoding algorithm, MPEG surround decoding algorithm, and BSAC decoding algorithm can be used as the audio decoding algorithm. At least one of MPEG 2 video decoding algorithm, MPEG 4 video decoding algorithm, H.264 decoding algorithm, SVC decoding algorithm, and VC-1 decoding algorithm can be used as the video decoding algorithm.
0795The data handler <b>8309</b> processes datagram required for data broadcasting from the IP datagram, and then allows the processed datagram to be mixed with A/V data through the middleware engine <b>8310</b>. According to the embodiment of the present invention, the middleware engine <b>8310</b> is a JAVA middleware engine.
0796The application manager <b>8313</b> receives key input of a TV viewer through the user interface (UI) and responds to the viewer's request through the graphic user interface (GUI) on the TV screen. Also, the application manager <b>8313</b> stores and recovers GUI control of the TV, user request, and TV system state in a memory (for example, NVRAM or Flash).
0797Also, the application manager <b>8313</b> receives parade related information, for example, parade_id from the demodulating unit <b>8302</b> or the IP filter <b>8308</b> and controls the demultiplexer <b>8303</b> to select the RS frame of the parade channel where a desired mobile service exists. Also, the application manager <b>8313</b> receives parade_id and region_id or ensemble_id from the demodulating unit <b>8302</b> or the IP filter <b>8308</b> and controls the demultiplexer <b>8303</b> to select the RS frame of ensemble including mobile service data to be decoded from the parade. The application manager <b>8313</b> controls the channel manager <b>8314</b> to perform channel related operation (channel map management and operation of program table decoder).
0798The channel manager <b>8314</b> manages a physical channel map and a logical channel map, and responds to the viewer's channel request by controlling the tuner <b>8301</b> and the program table decoder <b>8305</b>. Also, the channel manager <b>8314</b> requests the program table decoder <b>8305</b> to parse channel related table to be tuned and receives the result. Further, the channel manager <b>8314</b> updates the channel map based on the result, and transfers information of a desired mobile service to the service manager <b>8316</b> so that the service manager <b>8316</b> can control the IP filter <b>8308</b>.
0799The service manager <b>8316</b> takes IP datagram only corresponding to the user's desired mobile service from the IP datagram buffer <b>8307</b>, and transmits the IP datagram to the application layer. In this case, the service manager <b>8316</b> divides components (for example, audio and video streams) of the mobile service from the corresponding IP datagram and outputs the divided components to the A/V decoder <b>8311</b>. In other words, the IP layer demultiplexes audio and video streams within the IP datagram.
0800<figref idref="DRAWINGS">FIG. 87</figref> illustrates an example of a procedure of identifying whether the MPH service data packet within the RS frame is IP datagram or program table information, through the demultiplexer <b>8303</b>.
0801In other words, the demultiplexer <b>8303</b> receives one MPH service data packet within the RS frame (step <b>9101</b>), and parses type_indicator field of the MPH header within the corresponding MPH service data packet (step <b>9102</b>). If the type_indicator field value is parsed, it is possible to identify whether the corresponding MPH service data packet is data constituting program table information section or IP datagram.
0802If it is determined that the corresponding MPH service data packet is data constituting program table information section in step <b>9103</b>, the current step proceeds to <figref idref="DRAWINGS">FIG. 89</figref> to output data included in payload within the corresponding MPH service data packet to the program table buffer <b>8304</b> (step <b>9106</b>).
0803If it is determined that the corresponding MPH service data packet is IP datagram in step <b>9104</b>, the current step proceeds to <figref idref="DRAWINGS">FIG. 88</figref> to output data included in payload within the corresponding MPH service data packet to the IP datagram buffer <b>8307</b> (step <b>9107</b>). If it is determined that the corresponding MPH service data packet is neither data constituting program table information section or nor IP datagram in step <b>9104</b>, since it is reserved data for extension of the system, the demultiplexer disuses the corresponding MPH service data packet and receives next packet (steps <b>9105</b> and <b>9108</b>).
0804<figref idref="DRAWINGS">FIG. 88</figref> is a flow chart performed when the type_indicator field indicates that the corresponding MPH service data packet is IP datagram.
0805In other words, if the type_indicator field of the MPH header within the MPH service data packet read out from the RS frame indicates that the data included in payload within the corresponding MPH service data packet is IP datagram (step <b>9201</b>), it is identified whether the pointer field pt_field value expresses a maximum value (step <b>9202</b>).
0806If the pointer field pt_field value expresses a maximum value in step <b>9202</b>, since all the data of payload within the corresponding MPH service data packet are those on a continuous line of the IP datagram ongoing from the previous MPH service data packet, the demultiplexer transfers the data of payload to the IP datagram buffer which is previously allocated (step <b>9204</b>), and receives next MPH service data packet (step <b>9209</b>). If it is determined that the pointer field value is not maximum value in step <b>9202</b>, it is determined whether the pointer field value is 0 (step <b>9203</b>). If it is determined that the pointer field value is not 0 in step <b>9203</b>, since the previous data of the data indicated by the pointer field correspond to the IP datagram ongoing from the previous MPH service data packet, the data are copied in the previous IP datagram (step <b>9205</b>). If it is determined that the pointer field value is 0 in step <b>9203</b>, since it represents start of new IP datagram, a new IP datagram buffer is allocated (step <b>9206</b>). Afterwards, the data of payload are copied in the new IP datagram buffer (step <b>9207</b>).
0807If one IP datagram is completed through the above steps (step <b>9208</b>), a procedure of receiving a new IP datagram is repeated. If the IP datagram has not been completed, since next MPH service data packet will be followed by data, the current step proceeds to the next step for receiving next data packet.
0808<figref idref="DRAWINGS">FIG. 90</figref> is a flow chart illustrating an example of a detailed procedure of <figref idref="DRAWINGS">FIG. 88</figref>.
0809In other words, if the MPH service data packet including IP datagram is received (step <b>9401</b>), a length of the current IP datagram is compared with a size of valid data (valid_data_size) stored in the IP datagram buffer <b>8307</b> (IP_datagram_length>valid_data_size) in step <b>9402</b>. At this time, if the length of the current IP datagram is greater than the size of the valid data, since it means that there exist data required to complete one IP datagram in payload of the corresponding MPH service data packet, the current step proceeds to step <b>9403</b>. If not so, since it means that new data should be received, the current step proceeds to step <b>9404</b> and then amount of data is set to 0′. In step <b>9403</b>, amount of data included in payload of the corresponding MPH service data packet is determined, and the data as much as the determined amount are transmitted to the IP datagram buffer <b>8307</b>. And, the current step proceeds to step <b>9405</b> so that the amount is compared with the pointer field value (amount>pt_field). If the amount is equal to the pointer field value, it means that one IP datagram has been completed as a rule. However, since there may exist the possibility of error, the current step proceeds to step <b>9406</b> to test completeness. If the amount is different from the pt_field in step <b>9405</b>, since the payload of the corresponding packet is data belonging to the same IP datagram as designated in step <b>9403</b>, the current step returns to a routine for processing next MPH service data packet (step <b>9413</b>).
0810If it is identified that completeness of data has not assured in step <b>9407</b>, the current step proceeds to step <b>9408</b> to report that error has occurred and then proceeds to step <b>9409</b>. In step <b>9409</b>, a length of IP datagram is identified from the data included in the IP datagram header by reading out data at the front from the part indicated by the pointer field pt_field. Also, a memory for the IP datagram is allocated, and valid_data_size is initiated to ‘0’. Afterwards, similarly to step <b>9403</b>, data are transferred to the IP datagram buffer <b>8307</b>, and valid_data_size is updated (step <b>9410</b>). If the amount of the data transferred to the IP datagram buffer <b>8307</b> is equal to that of the IP datagram (step <b>9411</b>), since it means that another IP datagram has been completely transmitted, the pointer field pt_field is transferred as much as the amount and completeness of the datagram is notified (step <b>9412</b>). Afterwards, since there may exist data to be processed, the current step returns to step <b>9409</b>. If the size of the data copied in step <b>9411</b> is different from that of the IP datagram, since it means that it has reached the end of payload of the corresponding MPH service data packet, the current step proceeds to step <b>9413</b> to process next packet.
0811<figref idref="DRAWINGS">FIG. 89</figref> is an example of a flow chart performed when the type_indicator field indicates that the corresponding MPH service data packet is program table information. The procedure of <figref idref="DRAWINGS">FIG. 89</figref> is the same as that of <figref idref="DRAWINGS">FIG. 88</figref> except that the program table information included in payload of the MPH service data packet are transmitted to the program table buffer <b>8304</b>. Accordingly, each part constituting <figref idref="DRAWINGS">FIG. 89</figref>, which is repeated with <figref idref="DRAWINGS">FIG. 88</figref>, will refer to the description of <figref idref="DRAWINGS">FIG. 88</figref>, and thus its detailed description will be omitted.
0812<figref idref="DRAWINGS">FIG. 91</figref> is a flow chart illustrating an example of a detailed procedure of processing program table information of <figref idref="DRAWINGS">FIG. 89</figref>. The procedure of <figref idref="DRAWINGS">FIG. 89</figref> is the same as that of <figref idref="DRAWINGS">FIG. 88</figref> except that the program table information included in payload of the MPH service data packet are transmitted to the program table buffer <b>8304</b>. Accordingly, each part constituting <figref idref="DRAWINGS">FIG. 89</figref>, which is repeated with <figref idref="DRAWINGS">FIG. 88</figref>, will refer to the description of <figref idref="DRAWINGS">FIG. 88</figref>, and thus its detailed description will be omitted.
0813The procedure of <figref idref="DRAWINGS">FIG. 91</figref> is the same as that of <figref idref="DRAWINGS">FIG. 90</figref> except that the program table information are processed. Accordingly, each part constituting <figref idref="DRAWINGS">FIG. 91</figref>, which is repeated with <figref idref="DRAWINGS">FIG. 90</figref>, will refer to the description of <figref idref="DRAWINGS">FIG. 90</figref>, and thus its detailed description will be omitted.
0814As described above, the digital broadcasting system and the method of processing data according to the present invention has the following advantages.
0815The present invention is robust to error when mobile service data are transmitted through a channel, and can be compatible with the existing receiver.
0816Even a channel having ghost and strong noise can receive mobile service data without any error.
0817Since base data are transmitted by being inserted to a predetermined position of a data region, it is possible to improve receiving performance of the receiving system under the channel variable environment.
0818Since the mobile service data is multiplexed with the main service data in a parade format, it is possible to reduce the power of the receiving system.
0819In particular, the present invention is more effective when it is applied to a mobile receiver of which channel change is frequent and which requires robustness to noise.
0820It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the inventions. Thus, it is intended that the present invention covers the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.
Contents5
120 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20 Sheet 21 Sheet 22 Sheet 23 Sheet 24 Sheet 25 Sheet 26 Sheet 27 Sheet 28 Sheet 29 Sheet 30 Sheet 31 Sheet 32 Sheet 33 Sheet 34 Sheet 35 Sheet 36 Sheet 37 Sheet 38 Sheet 39 Sheet 40 Sheet 41 Sheet 42 Sheet 43 Sheet 44 Sheet 45 Sheet 46 Sheet 47 Sheet 48 Sheet 49 Sheet 50 Sheet 51 Sheet 52 Sheet 53 Sheet 54 Sheet 55 Sheet 56 Sheet 57 Sheet 58 Sheet 59 Sheet 60 Sheet 61 Sheet 62 Sheet 63 Sheet 64 Sheet 65 Sheet 66 Sheet 67 Sheet 68 Sheet 69 Sheet 70 Sheet 71 Sheet 72 Sheet 73 Sheet 74 Sheet 75 Sheet 76 Sheet 77 Sheet 78 Sheet 79 Sheet 80 Sheet 81 Sheet 82 Sheet 83 Sheet 84 Sheet 85 Sheet 86 Sheet 87 Sheet 88 Sheet 89 Sheet 90 Sheet 91 Sheet 92 Sheet 93 Sheet 94 Sheet 95 Sheet 96 Sheet 97 Sheet 98 Sheet 99 Sheet 100 Sheet 101 Sheet 102 Sheet 103 Sheet 104 Sheet 105 Sheet 106 Sheet 107 Sheet 108 Sheet 109 Sheet 110 Sheet 111 Sheet 112 Sheet 113 Sheet 114 Sheet 115 Sheet 116 Sheet 117 Sheet 118 Sheet 119 Sheet 120
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| WO0044145A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO0044145A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO0045552A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO0045552A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO0105157A2 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO0105157A2 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO03017254A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO03017254A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO03049449A2 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO03049449A2 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| EP0996291A1 | Cites | European Patent Office (EPO) | Applicant |
| KR100211248B1 | Cites | Republic of Korea | Applicant |
| KR100710248B1 | Cites | Republic of Korea | Applicant |
| KR100710248B1 | Cites | Republic of Korea | Applicant |
| CN101018105A | Cites | China | Applicant |
| CN101018223A | Cites | China | Applicant |
| CN101022435A | Cites | China | Applicant |
| EP1014711A1 | Cites | European Patent Office (EPO) | Applicant |
| EP1085750A2 | Cites | European Patent Office (EPO) | Applicant |
| CN1463126A | Cites | China | Applicant |
| CN1496107A | Cites | China | Applicant |
| EP1528700A2 | Cites | European Patent Office (EPO) | Applicant |
| EP1566905A1 | Cites | European Patent Office (EPO) | Applicant |
| EP1628420A2 | Cites | European Patent Office (EPO) | Applicant |
| CN1678068A | Cites | China | Applicant |
| EP1696595A2 | Cites | European Patent Office (EPO) | Applicant |
| CN1738436A | Cites | China | Applicant |
| EP1768396A2 | Cites | European Patent Office (EPO) | Applicant |
| CN1829270A | Cites | China | Applicant |
| CN1946190A | Cites | China | Applicant |
| KR20000040481A | Cites | Republic of Korea | Applicant |
| JP2000224136A | Cites | Japan | Applicant |
| US2001011213A1 | Cites | United States of America | Applicant |
| US2001034867A1 | Cites | United States of America | Applicant |
| US2001038744A1 | Cites | United States of America | Applicant |
| JP2001054031A | Cites | Japan | Applicant |
| JP2001274769A | Cites | Japan | Applicant |
| KR20020080992A | Cites | Republic of Korea | Applicant |
| KR20020089078A | Cites | Republic of Korea | Applicant |
| US2002085632A1 | Cites | United States of America | Applicant |
| US2002126222A1 | Cites | United States of America | Applicant |
| US2002136197A1 | Cites | United States of America | Applicant |
| US2002136276A1 | Cites | United States of America | Applicant |
| US2002138806A1 | Cites | United States of America | Applicant |
| JP2002141877A | Cites | Japan | Applicant |
| US2002150246A1 | Cites | United States of America | Applicant |
| US2002154709A1 | Cites | United States of America | Applicant |
| US2002157099A1 | Cites | United States of America | Applicant |
| US2002159520A1 | Cites | United States of America | Applicant |
| US2002172154A1 | Cites | United States of America | Applicant |
| US2002186790A1 | Cites | United States of America | Applicant |
| US2002187767A1 | Cites | United States of America | Applicant |
| US2002191716A1 | Cites | United States of America | Applicant |
| US2002194570A1 | Cites | United States of America | Applicant |
| JP2002218339A | Cites | Japan | Applicant |
| KR20030026236A | Cites | Republic of Korea | Applicant |
| KR20030030175A | Cites | Republic of Korea | Applicant |
| KR20030037138A | Cites | Republic of Korea | Applicant |
| KR20030062138A | Cites | Republic of Korea | Applicant |
| US2003018980A1 | Cites | United States of America | Applicant |
| JP2003032640A | Cites | Japan | Applicant |
| US2003046431A1 | Cites | United States of America | Applicant |
| US2003066082A1 | Cites | United States of America | Applicant |
| US2003067899A9 | Cites | United States of America | Applicant |
| US2003093798A1 | Cites | United States of America | Applicant |
| US2003099303A1 | Cites | United States of America | Applicant |
| US2003115540A1 | Cites | United States of America | Applicant |
| US2003121045A1 | Cites | United States of America | Applicant |
| US2003125033A1 | Cites | United States of America | Applicant |
| JP2003134117A | Cites | Japan | Applicant |
| US2003152107A1 | Cites | United States of America | Applicant |
| US2003193618A1 | Cites | United States of America | Applicant |
| US2003206053A1 | Cites | United States of America | Applicant |
| JP2003209525A | Cites | Japan | Applicant |
| US2003223519A1 | Cites | United States of America | Applicant |
| US2003234890A1 | Cites | United States of America | Applicant |
| JP2003284037A | Cites | Japan | Applicant |
| KR20040032282A | Cites | Republic of Korea | Applicant |
| KR20040032283A | Cites | Republic of Korea | Applicant |
| US2004022307A1 | Cites | United States of America | Applicant |
| US2004028076A1 | Cites | United States of America | Applicant |
| US2004034491A1 | Cites | United States of America | Applicant |
| WO2004057873A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO2004057873A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| US2004061645A1 | Cites | United States of America | Applicant |
| WO2004066652A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO2004066652A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| US2004081199A1 | Cites | United States of America | Applicant |
| US2004090997A1 | Cites | United States of America | Applicant |
| US2004101046A1 | Cites | United States of America | Applicant |
| US2004105507A1 | Cites | United States of America | Applicant |
| US2004110522A1 | Cites | United States of America | Applicant |
| US2004123332A1 | Cites | United States of America | Applicant |
| US2004125235A1 | Cites | United States of America | Applicant |
| JP2004129126A | Cites | Japan | Applicant |
| US2004148642A1 | Cites | United States of America | Applicant |
| US2004156460A1 | Cites | United States of America | Applicant |
| US2004237024A1 | Cites | United States of America | Applicant |
| US2004260985A1 | Cites | United States of America | Applicant |
| KR20050036552A | Cites | Republic of Korea | Applicant |
1,273 members in 10 offices
Members1,273
| Document | Office | Kind | |
|---|---|---|---|
| CA2688380A1 | Canada | A1 | |
| CA2688391A1 | Canada | A1 | |
| CA2689103A1 | Canada | A1 | |
| CA2689415A1 | Canada | A1 | |
| CA2692025A1 | Canada | A1 | |
| CA2692312A1 | Canada | A1 | |
| CA2692315A1 | Canada | A1 | |
| CA2692318A1 | Canada | A1 | |
| KR20080114569A | Republic of Korea | A | |
| KR20080114570A | Republic of Korea | A | |
| KR20080114592A | Republic of Korea | A | |
| KR20080114594A | Republic of Korea | A | |
| KR20080114595A | Republic of Korea | A | |
| KR20080114596A | Republic of Korea | A | |
| WO2009002094A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009002095A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009002113A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009002116A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009002117A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009002118A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009002128A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009002130A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009002131A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009002132A1 | World Intellectual Property Organization (WIPO) | A1 | |
| CA2691652A1 | Canada | A1 | |
| CA2691938A1 | Canada | A1 | |
| CA2691977A1 | Canada | A1 | |
| CA2691978A1 | Canada | A1 | |
| CA2691981A1 | Canada | A1 | |
| CA2691982A1 | Canada | A1 | |
| CA2691983A1 | Canada | A1 | |
| CA2692107A1 | Canada | A1 | |
| CA2692335A1 | Canada | A1 | |
| CA2692339A1 | Canada | A1 | |
| CA2692390A1 | Canada | A1 | |
| CA2692447A1 | Canada | A1 | |
| CA2692449A1 | Canada | A1 | |
| CA2692484A1 | Canada | A1 | |
| CA2692492A1 | Canada | A1 | |
| KR20090001359A | Republic of Korea | A | |
| KR20090001402A | Republic of Korea | A | |
| KR20090001403A | Republic of Korea | A | |
| WO2009005264A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009005277A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2009005278A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009005279A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2009005301A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009005302A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009005303A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009005304A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009005305A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009005306A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009005307A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009005308A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2009005309A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009005315A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009005331A2 | World Intellectual Property Organization (WIPO) | A2 | |
| KR20090002855A | Republic of Korea | A | |
| KR20090003105A | Republic of Korea | A | |
| KR20090003142A | Republic of Korea | A | |
| KR20090004059A | Republic of Korea | A | |
| KR20090004060A | Republic of Korea | A | |
| KR20090004061A | Republic of Korea | A | |
| KR20090004267A | Republic of Korea | A | |
| KR20090004579A | Republic of Korea | A | |
| KR20090004580A | Republic of Korea | A | |
| KR20090004581A | Republic of Korea | A | |
| KR20090004582A | Republic of Korea | A | |
| KR20090004653A | Republic of Korea | A | |
| KR20090004658A | Republic of Korea | A | |
| KR20090004659A | Republic of Korea | A | |
| KR20090004660A | Republic of Korea | A | |
| KR20090004661A | Republic of Korea | A | |
| KR20090004663A | Republic of Korea | A | |
| KR20090004664A | Republic of Korea | A | |
| KR20090004665A | Republic of Korea | A | |
| KR20090004666A | Republic of Korea | A | |
| KR20090004667A | Republic of Korea | A | |
| KR20090004722A | Republic of Korea | A | |
| KR20090004724A | Republic of Korea | A | |
| KR20090004725A | Republic of Korea | A | |
| KR20090004773A | Republic of Korea | A | |
| CA2692000A1 | Canada | A1 | |
| CA2692003A1 | Canada | A1 | |
| CA2692338A1 | Canada | A1 | |
| CA2692375A1 | Canada | A1 | |
| CA2692464A1 | Canada | A1 | |
| CA2692551A1 | Canada | A1 | |
| WO2009008647A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2009008648A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2009008649A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2009008650A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009008651A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009008652A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2009008653A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2009008654A1 | World Intellectual Property Organization (WIPO) | A1 | |
| KR20090009175A | Republic of Korea | A | |
| CA2691528A1 | Canada | A1 | |
| CA2693358A1 | Canada | A1 | |
| US2009028079A1 | United States of America | A1 |
119 transactions on the USPTO file
Allowed after 1 non-final rejection and 1 final rejection.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Expire PatentEXP. | EXP. | |
| Maintenance Fee Reminder MailedREM. | REM. | |
| Correspondence Address ChangeC.ADB | C.ADB | |
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Email NotificationEML_NTR | EML_NTR | |
| Application ready for PDX access by participating foreign officesCCRDY | CCRDY | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Printer Rush- No mailingTCPB | TCPB | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Paralegal or electronic terminal disclaimer approvedP574 | P574 | |
| Terminal Disclaimer FiledDIST | DIST | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Response after Final ActionA.NE | A.NE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Correspondence Address ChangeC.AD | C.AD | |
| Correspondence Address ChangeC.AD | C.AD | |
| Correspondence Address ChangeC.AD | C.AD | |
| Notice of Reissue Published in Official GazetteNRE. | NRE. | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Email NotificationEML_NTR | EML_NTR | |
| Application Is Now CompleteCOMP | COMP | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Application Dispatched from OIPEOIPE | OIPE | |
| FITF set to NO - revise initial settingFTFI | FTFI | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Email NotificationEML_NTR | EML_NTR | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Additional Application Filing FeesADDFLFEE | ADDFLFEE | |
| A statement by one or more inventors satisfying the requirement under 35 USC 115, Oath of the ApplicOATHDECL | OATHDECL | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Electronic Information Disclosure StatementEIDS. | EIDS. |
4 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS | LAPS | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS |
Numbers
- Publication
- RE046728
- Application
- 14618910
Titles
- English
- Digital broadcasting system and data processing method
Classification
- CPC, 22
- H03M13/2915
- H04H20/30
- H04N7/015
- H03M13/09
- H03M13/2936
- H03M13/15
- H03M13/2945
- H03M13/1515
- H03M13/23
- H04H20/57
- H04L1/006
- H04L1/0057
- H04L1/0065
- H04L25/0232
- H04L25/03159
- H04L25/03292
- H04N19/89
- H04N21/2393
- H04N21/4382
- H04N21/6112
- H04L2001/0093
- H04N21/2383
- IPC, 11
- H03K9 00
- H03M13 29
- H04H20 30
- H04H20 57
- H04L1 00
- H04L25 03
- H04L25 02
- H04N21 438
- H04N19 89
- H04N21 61
- H04N21 239
- USPC, 1
- 001001000