KR101649532B1 - Digital broadcasting receiver and method for controlling the same - Google Patents

Abstract

According to another aspect of the present invention, there is provided a method for transmitting mobile service data, the method comprising: receiving a broadcast signal in which mobile service data and main service data are multiplexed; extracting TPC signaling information and FIC signaling information from a data group in the received mobile service data; Acquiring a first program table describing an ensemble virtual channel information and service, which is a virtual channel group of the received mobile service data, using the extracted FIC signaling information; and using the obtained first program table Detecting a control access descriptor indicating whether the mobile service data has been encrypted; and controlling the encrypted mobile service data to be decrypted using information of the detected control access descriptor do.

Description

[0001] DIGITAL BROADCASTING RECEIVER AND METHOD FOR CONTROLLING THE SAME [0002]

The present invention relates to a digital broadcasting system, and more particularly, to a digital broadcasting receiver and a control method thereof.

The digital broadcasting system may include a digital broadcasting transmitter and a digital broadcasting receiver. Also, the digital broadcast transmitter processes data such as a broadcast program in a digital manner and transmits the processed data to the digital broadcast receiver. Such digital broadcasting systems are gradually replacing analog broadcasting systems due to various advantages such as efficiency of data transmission.

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

In a conventional mobile digital broadcasting environment, there is no specific technique for setting a reception restriction for a specific service or releasing it.

An embodiment of the present invention is to provide a digital broadcasting receiver and a control method thereof that are resistant to channel variation and noise.

Another embodiment of the present invention provides a data processing method capable of setting a reception restriction for a specific service in a mobile digital broadcasting environment or canceling the reception restriction.

A method of controlling a digital broadcast receiver according to an exemplary embodiment of the present invention includes receiving a broadcast signal in which mobile service data and main service data are multiplexed, receiving transmission parameter channel signaling information from a data group in the received mobile service data, Acquiring a first program table describing an ensemble virtual channel information and a service, which is a virtual channel group of the received mobile service data, using the extracted high-speed information channel signaling information; Detecting, by using the obtained first program table, a control access descriptor indicating whether the mobile service data has been encrypted; and using the information of the detected control access descriptor, Encrypted Mobile And a step of controlling the service data to be decrypted (decrypt).

According to another aspect of the present invention, there is provided a digital broadcast receiver including: a receiver for receiving a broadcast signal in which mobile service data and main service data are multiplexed; and a transmitter for transmitting transmission parameter channel signaling information from a data group in the received mobile service data, Acquiring a first program table describing an ensemble virtual channel information and a service as a virtual channel group of the received mobile service data using the extracted high speed information channel signaling information; And a control unit operable to detect a control access descriptor indicating whether or not the mobile service data has been incremented using the obtained first program table, The above- One service data is a control unit that controls to decrypt (decrypt).

A method of controlling a digital broadcast transmitter according to an exemplary embodiment of the present invention includes generating a broadcast signal including a control access descriptor indicating whether or not mobile service data is encapsulated, The method comprising: transmitting a broadcast signal including a descriptor to a digital broadcast receiver, the control access descriptor including information identifying the level at which the mobile service data is encrypted, Contains information about control data used when decrypting service data.

According to an embodiment of the present invention, a digital broadcast receiver and a control method thereof that are resistant to channel variation and noise can be provided.

In addition, according to another embodiment of the present invention, it is possible to easily implement a function of setting a reception restriction for a specific service in a mobile digital broadcasting environment or releasing it.

According to another embodiment of the present invention, in a mobile digital broadcasting environment, it is possible to control that a service to which an anti-piracy function is applied is transmitted through an external interface.

FIG. 1 is a block diagram illustrating a configuration of a reception system according to an embodiment of the present invention. Referring to FIG.
2 is a diagram illustrating a structure of a data group according to an embodiment of the present invention.
3 is a diagram illustrating an RS frame according to an embodiment of the present invention.
4 is a diagram illustrating an MH frame structure for transmitting mobile service data according to the present invention.
5 is a diagram showing an example of a VSB frame structure.
FIG. 6 is a diagram illustrating a mapping example of a first 4-slot position of a subframe in a spatial region with respect to one VSB frame.
FIG. 7 is a diagram showing a mapping example of a first 4-slot position of a subframe in a time domain for one VSB frame.
FIG. 8 is a diagram showing an example of a data group allocation procedure to be allocated to one subframe among 5 subframes constituting an MH frame
9 is a diagram showing an example of assigning a single parade to one MH frame.
10 is a diagram showing an example of transmitting three parades to one MH frame.
FIG. 11 is a diagram showing an example in which the allocation process of three parades in FIG. 10 is extended to five subframes in one MH frame
12 is a diagram illustrating a data transmission structure according to an embodiment of the present invention.
13 is a diagram illustrating a hierarchical signaling structure according to an embodiment of the present invention.
14 is a diagram illustrating an embodiment of an FIC body format according to the present invention.
15 is a diagram showing an embodiment of a data structure of an FIC segment according to the present invention.
16 is a diagram illustrating an embodiment of a bitstream syntax structure for a payload of an FIC segment when the FIC type field value is '0' according to the present invention.
17 is a diagram showing an embodiment of a bitstream syntax of a service map table (hereinafter referred to as "SMT ") according to an embodiment of the present invention.
18 is a diagram showing the syntax of the MH Audio Descriptor according to the embodiment of the present invention.
19 is a diagram showing a syntax of an MH RTP payload type descriptor according to an embodiment of the present invention.
20 is a diagram showing a syntax of an MH Current Event Descriptor according to an embodiment of the present invention.
21 is a diagram showing a syntax of an MH Next Event Descriptor according to an embodiment of the present invention.
22 is a diagram showing a syntax of an MH System Time Descriptor according to an embodiment of the present invention.
23 is a diagram for explaining the segmentation and encapsulation of the SMT according to the present invention.
24 is a flow diagram illustrating accessing a virtual channel using FIC and SMT in accordance with an embodiment of the present invention.
25 is a diagram showing a protocol stack of an MH system according to an embodiment of the present invention.
26 is a diagram illustrating a configuration of a digital broadcast receiver according to an embodiment of the present invention.
FIG. 27 is a diagram illustrating another embodiment of a bitstream syntax of a service map table according to an embodiment of the present invention. Referring to FIG.
28 is a diagram illustrating a control access descriptor according to an embodiment of the present invention.
29 is a diagram illustrating an RS frame structure according to an embodiment of the present invention.
30 is a diagram illustrating an MH-TP format according to an embodiment of the present invention.
31 is a diagram illustrating the structure of data that is encrypted at the IP level according to an embodiment of the present invention.
32 is a diagram illustrating the structure of data that is encrypted at the RTP level according to an embodiment of the present invention.
33 is a diagram illustrating the structure of data that is encrypted at a raw level according to an embodiment of the present invention.
34 is a diagram illustrating an AES-CTR mode encryption process that can be applied to an embodiment of the present invention.
35 is a diagram illustrating an AES-CTR mode decryption process that can be applied to an embodiment of the present invention.
FIG. 36 is a diagram illustrating a counter value in the AES-CTR mode that can be applied to an embodiment of the present invention.
37 is a diagram illustrating a process of processing a RESIDUE block in an AES-CTR mode encryption / decryption process applicable to an embodiment of the present invention.
Figure 38 is a more specific view of an SMT including a control access descriptor according to an embodiment of the present invention.
39 is a diagram illustrating a structure of an RS frame including an MH service to which reception restriction is applied according to an embodiment of the present invention.
40 is a flowchart illustrating a method of controlling a digital broadcasting receiver according to an embodiment of the present invention.
FIG. 41 is a table defining CCI (Copy Control Information) according to an embodiment of the present invention.
FIG. 42 is a diagram illustrating the EMI (Encryption Mode Indicator) shown in FIG.
FIG. 43 is a diagram illustrating the APS (Analog Protection System) shown in FIG.
FIG. 44 is a view illustrating the CIT (Constrained Image Trigger) shown in FIG. 41; FIG.
45 is a flowchart illustrating a method of controlling a digital broadcasting receiver and a digital broadcasting transmitter according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings and accompanying drawings, but the present invention is not limited to or limited by the embodiments.

As used herein, terms used in the present invention are selected from general terms that are widely used in the present invention while taking into account the functions of the present invention, but these may vary depending on the intention or custom of a person skilled in the art or the emergence of new technologies. Also, in certain cases, there may be a term chosen arbitrarily by the applicant, in which case the meaning thereof will be described in the description of the corresponding invention. Therefore, it is intended that the terminology used herein should be interpreted based on the meaning of the term rather than on the name of the term, and on the entire contents of the specification.

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

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

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

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

The transmission system according to the present invention is capable of multiplexing the main service data and the mobile service data on the same physical channel without any influence on receiving the main service data in the existing receiving system.

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

With the transmission system according to the present invention, mobile service data can be received and received in the receiving system, and stable reception of mobile service data is possible even with various distortions and noises occurring in the channel.

FIG. 1 is a block diagram illustrating a configuration of a reception system according to an embodiment of the present invention. Referring to FIG.

The receiving system according to the present embodiment includes a baseband processor 100, a management processor 200, and a presentation processor 300.

The baseband processor 100 includes an operation controller 110, a tuner 120, a demodulator 130, an equalizer 140, a known sequence detector A mobile handheld block decoder 160, a primary RS frame decoder 170, a secondary RS frame decoder 180, and a signaling decoder 190, . ≪ / RTI >

The operation controller 110 controls the operation of each block of the baseband processor 100.

The tuner 120 serves to receive main service data, which is a broadcast signal for a fixed broadcast receiving apparatus, and mobile service data, which is a broadcast signal for a mobile broadcast receiving apparatus, by tuning the receiving system at a specific physical channel frequency . At this time, the frequency of the tuned specific channel is down-converted to an intermediate frequency (IF) signal and output to the demodulator 130 and the known data detector 140. The passband digital IF signal output from the tuner 120 may include only main service data, only mobile service data, or both main service data and mobile service data.

The demodulator 130 performs automatic gain control, carrier recovery, and timing recovery on a digital IF signal of a passband inputted from the tuner 120, converts the signal into a baseband signal, and then outputs the baseband signal to an equalizer 140 and a known data detector 150. The demodulator 130 can improve demodulation performance by using a known data symbol sequence received from the known data detector 150 during timing recovery or carrier recovery.

The equalizer 140 compensates for the distortion on the channel included in the demodulated signal from the demodulator 130, and outputs the compensated signal to the block decoder 160. The equalizer 140 can improve equalization performance by using a known data symbol sequence input from the known data detector 150. [ Also, the equalizer 140 may feedback the decoding result of the block decoder 150 to improve the equalization performance.

The known data detector 150 detects the known data position inserted from the transmitting side from the input / output data of the demodulator 130, that is, the data before the demodulation or the demodulated data, To the demodulator 130 and the equalizer 140. The equalizer 140 generates a sequence of known data generated by the demodulator 130 and the equalizer 140, Also, the known data detector 150 outputs to the block decoder 160 information for enabling the block decoder 160 to distinguish the mobile service data that has been further encoded on the transmitting side and the main service data that has not undergone the additional coding .

If the data input after the channel equalization in the equalizer 140 is data in which block encoding and trellis encoding are both performed (i.e., data in the RS frame, signaling data), the block decoder 160 outputs Performs trellis decoding and block decoding, and performs only trellis decoding if the data is only Trellis-encoded (i.e., main service data) without performing block encoding.

The signaling decoder 190 decodes the signaling data input after being equalized by the equalizer 140. It is assumed that the signaling data input to the signaling decoder 190 is data in which both block encoding and trellis encoding are performed in the transmission system. Examples of such signaling data include transmission parameter channel (TPC) data and fast information channel (FIC) data. Each data item is described in detail below. The FIC data decoded by the signaling decoder 190 is output to an FIC handler 215 and the decoded TPC data is output to a TPC handler 214.

Meanwhile, according to the present invention, the transmission system uses the RS frame concept as an encoding unit. The RS frame is divided into a primary RS frame and a secondary RS frame. However, the primary RS frame and the secondary RS frame are distinguished from each other according to the importance of data.

The primary RS frame decoder 170 receives the output of the block decoder 160 as an input. In this case, the primary RS frame decoder 170 receives only Reed Solomon (RS) encoded and / or CRC (Cyclic Redundancy Check) encoded mobile service data from the block decoder 160 as an example. That is, the primary RS frame decoder 170 receives only the mobile service data, not the main service data. The primary RS frame decoder 170 performs an inverse process of an RS frame encoder (not shown) of the transmission system to correct errors in the primary RS frame. That is, the primary RS frame decoder 170 collects a plurality of data groups to form a primary RS frame, and then performs error correction on a primary RS frame basis. In other words, the primary RS frame decoder 170 decodes a primary RS frame transmitted for an actual broadcast service or the like.

The secondary RS frame decoder 180 receives the output of the block decoder 160 as an input. In this case, the secondary RS frame decoder 180 receives only RS-encoded and / or CRC-encoded mobile service data. That is, the secondary RS frame decoder 180 receives only the mobile service data, not the main service data. The secondary RS frame decoder 180 performs an inverse process of the RS frame encoder (not shown) of the transmission system to correct errors in the secondary RS frame. That is, the secondary RS frame decoder 180 collects a plurality of data groups to form a secondary RS frame, and then performs error correction on a secondary RS frame basis. In other words, the secondary RS frame decoder 180 decodes secondary RS frames transmitted for mobile audio service data, mobile video service data, guide data, and the like.

The management processor 200 according to an exemplary embodiment of the present invention includes an MH physical adaptation processor 210, an IP network stack 220, a streaming handler 230 An SI handler 240, a file handler 250, a Multipurpose Internet Mail Extensions (MIME) type handler 260, an ESG handler 270, An ESG decoder (ESG decoder) 280, and a storage unit 290.

The MH physical adaptation processor 210 includes a primary RS frame handler 211, a secondary RS frame handler 212 and an MH-TP handler 213 ), A TPC handler 214, a FIC handler 215, and a Physical Adaptation Control Signal Handler 216.

The TPC handler 214 receives and processes baseband information required by the modules corresponding to the MH physical adaptation processor 210. The baseband information is input in the form of TPC data, And processes FIC data or the like received from the baseband processor 100 using this information.

The TPC data is transmitted from the transmission system to the reception system through a predetermined area of the data group. The TPC data may include at least one of an MH-Ensemble ID, an MH-Subframe Number, a TNoG (Total Number of MH-Groups), an RS frame Continuity Counter, a N (Column Size of RS-frame) have.

The MH-Ensemble ID is an identification number for each MH ensemble transmitted on the corresponding physical channel (Identification number for each MH-Ensemble carried in this physical channel).

The MH-Subframe Number is a number indicating a subframe in the MH frame (A number that identifies the MH-Subframe number in an MH-frame, where each MH-Group is associated with this MH-Ensemble is transmitted).

The Total Number of MH-Groups (TNoG) represents the total number of data groups belonging to all the MH parades in one subframe (Total Number of MH-Groups including all MH-Groups belonging to all MH- MH-Subframe).

The RS frame continuity counter is a number indicative of a continuous indicator of an RS frame transmitted in the corresponding MH frame, and increases by 1 while employing modulo 16 for each successive RS frame (A number which serves as a continuity indicator of the RS- frames carrying this MH-Ensemble. The value will be incremented by 1 modulo 16 for each successive RS-frame).

The size of the MH-TP (Transport Packet) is determined based on the column size of the RS frame belonging to the corresponding MH ensemble. belongs to this MH-Ensemble.

The FIC Version Number indicates the version number of the FIC body, which is the FIC transmission structure transmitted on the corresponding physical channel (A number, which represents the version number of the FIC body carried on the physical channel).

The TPC data is input to the TPC handler 214 through the signaling decoder 190 of Figure 1 and processed by the TPC handler 214 and is also used by the FIC handler 215 to process the FIC data do.

The FIC handler 215 processes the FIC data received from the baseband processor 100 in association with the TPC data received from the TPC handler 214.

The physical adaptive control signal handler 216 collects the FIC data transmitted through the FIC handler 215 and the SI data received through the RS frame and uses the generated SI data to configure and access information of the IP datagram and the mobile broadcast service. And stores it in the storage unit 290.

The primary RS frame handler 211 divides the primary RS frame received from the primary RS frame decoder 170 of the baseband processor 100 into units of each row to form an MH-TP, And outputs it to the handler 213.

The secondary RS frame handler 212 divides the secondary RS frame received from the secondary RS frame decoder 180 of the baseband processor 100 into units of each row to form an MH-TP, and transmits the secondary RS frame to the MH-TP handler 213 .

The MH-TP handler 213 extracts each header of the MH-TP transmitted from the primary and secondary RS frame handlers 211 and 212 to determine data included in the corresponding MH-TP. If the determined corresponding data is SI data, the data is output to the physical adaptive control signal handler 216 (i.e., the SI data is not encapsulated in the IP datagram). In case of the IP datagram, the IP network stack 220 .

The IP network stack 220 processes broadcast data transmitted in an IP datagram format. That is, the IP network stack 220 includes a UDP (User Datagram Protocol), an RTP (Real-time Transport Protocol), an RTCP (Real-time Transport Control Protocol), an Asynchronous Layered Coding / Layered Coding Transport (File Delivery over Unidirectional Transport) or the like. If the processed data is streaming data, the streaming data is output to the streaming handler 230. If the processed data is data of a file format, the data is output to the file handler 250, .

The SI handler 240 receives and processes the SI data in the form of an IP datagram input to the IP network stack 220.

The SI handler 240 outputs the SI data to the MIME type handler 260 when the input SI data is a MIME type.

The MIME type handler 260 receives and processes MINE type SI data output from the SI handler 240.

The file handler 250 receives data in the form of an object according to the ALC / LCT and the FLUTE structure from the IP network stack 220. The file handler 250 collects the received data to form a file. When the file includes an electronic service guide (ESG), the file handler 250 outputs the file to the ESG handler 270. Data for other file- And outputs it to the presentation controller 330 of the presentation processor 300.

The ESG handler 270 processes the ESG data received from the file handler 250 and stores the processed ESG data in the storage unit 290 or outputs the ESG data to the ESG decoder 280 to use the ESG data in the ESG decoder 280 do.

The storage unit 290 stores SI (System Information) received from the physical adaptation control signal handler 216 and the ESG handler 270, and transmits the stored data to each block.

The ESG decoder 280 restores the ESG data and the SI data stored in the storage unit 290 or the ESG data received from the ESG handler 270 and outputs the ESG data to the presentation controller 330 Output.

The streaming handler 230 receives data from the IP network stack 220 according to the RTP and RTCP structures. The streaming handler 230 extracts an audio / video stream from the received data and outputs the extracted audio / video stream to the audio / video decoder 310 of the presentation processor 300. The audio / video decoder 311 decodes the audio stream and the video stream received from the streaming handler 230, respectively.

The display module 320 of the presentation processor 300 receives the decoded audio and video signals from the A / V decoder 310 and provides the decoded audio and video signals to a user through a speaker and / or a screen.

The presentation controller 330 is a controller for modules for outputting data received by the receiving system to a user.

The channel service manager 340 interfaces with a user to enable a channel service, such as channel map management and channel service access, to be used by the user.

The Application Manager (350) is responsible for interfacing with the user to use application services other than the ESG display or other channel services.

Meanwhile, the data structure used in the mobile broadcasting technology according to the present embodiment includes a data group structure and an RS frame structure. This will be described in detail as follows.

2 is a diagram illustrating a structure of a data group according to an embodiment of the present invention.

In the data structure according to FIG. 2, the data group is divided into 10 MH blocks (MH blocks B1 to B10). And each MH block has a length of 16 segments as an embodiment. In FIG. 2, only the RS parity data is allocated to some of the 5 segments before the MH block B1 and the 5 segments after the MH block B10, and the data is excluded from the A region to the D region of the data group.

That is, assuming that one data group is divided into A, B, C, and D regions, each MH block may be included in any one of the A region to the D region according to the characteristics of each MH block in the data group . At this time, each MH block is included in one of the A region and the D region according to the degree of interference of the main service data.

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

MH block B4 to MH block B7 in the data group of FIG. 2 show an example in which a long known data sequence is inserted before and after each MH block as an area without interference of main service data. In the present invention, the area A (= B4 + B5 + B6 + B7) including the MH block B4 to the MH block B7 will be described. As described above, in the case of the A region having the known data sequence for each MH block, the receiving system can perform equalization using the channel information obtained from the known data. Thus, the most robust equalization performance among the A region to the D region I can get it.

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

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

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

The data group includes a signaling information area to which signaling information is allocated.

The present invention can use a part of the second segment from the first segment of the MH block B4 in the data group as a signaling information area.

The present invention uses 276 (= 207 + 69) bytes of the MH block B4 of each data group as a signaling information area. That is, the signaling information area is composed of 207 bytes, which is the first segment of the MH block B4, and the first 69 bytes of the second segment. The first segment of the MPH block B4 corresponds to the 17th or 173rd segment of the VSB field.

The signaling information can be divided into two types of signaling channels. One is a transmission parameter channel (TPC), and the other is a fast information channel (FIC).

The TPC data may include at least one of an MH-Ensemble ID, an MH-Subframe Number, a TNoG (Total Number of MH-Groups), an RS frame Continuity Counter, a N (Column Size of RS-frame) have. The TPC information is only an example for facilitating the understanding of the present invention, and addition and deletion of signaling information included in the TPC can be easily changed by those skilled in the art, so the present invention is not limited to the above embodiments. The FIC data is provided to enable a fast service acquisition at a receiver, and includes cross-layer information between a physical layer and an upper layer.

For example, when the data group includes six known data strings as shown in FIG. 2, the signaling information area is located between the first known data string and the second known data string. That is, the first known data sequence is inserted into the last two segments of the MH block B3 in the data group, and the second known sequence data sequence is inserted into the second and third segments of the MH block B4. And the third to sixth known data sequences are inserted into the last two segments of the MH blocks B4, B5, B6 and B7, respectively. The first, third, and sixth to sixth known data streams are separated by 16 segments.

3 is a diagram illustrating an RS frame according to an embodiment of the present invention.

The RS frame shown in FIG. 3 is a set of one or more data groups. This RS frame is received for each MH frame with the receiving system switched to the time slicing mode so as to receive the MH ensemble including the ESG entry point after receiving the FIC and processing the FIC. One RS frame includes IP streams of each service or ESG, and SMT section data may exist in all RS frames.

The RS frame according to an exemplary embodiment of the present invention includes at least one MH TP (Transport Packet). The MH TP consists of an MH header and an MH payload.

The MH payload may include mobile service data as well as signaling data. That is, one MH payload may contain only mobile service data, only signaling data, or both service data and signaling data.

An embodiment of the present invention distinguishes data included in an MH payload by an MH header. That is, if the MH TP has a first MH header, it indicates that the MH payload contains signaling data. Also, if the MH TP has a second MH header, it indicates that the MH payload contains the signaling data and the service data. If the MH TP has a third MH header, it indicates that the MH payload contains the service data.

The RS frame of FIG. 3 shows an example in which IP datagrams (i.e., IP Datagram 1 and IP Datagram 2) for two types of services are allocated.

4 is a diagram illustrating an MH frame structure for transmitting mobile service data according to the present invention.

FIG. 4 shows an example in which one MH frame is composed of 5 subframes, and one subframe is composed of 16 slots. In this case, one MH frame includes 5 subframes, 80 slots.

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

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

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

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

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

FIG. 6 shows a mapping example of a first 4-slot position of a subframe for one VSB frame in a spatial domain. FIG. 7 shows a mapping example of a first 4-slot position of a subframe in a time domain for one VSB frame.

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

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

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

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

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

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

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

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

That is, the RS frame mode indicates whether one parade transmits one RS frame or two RS frames. This RS frame mode is transmitted as TPC data described above.

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

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

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

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

And the parade allocation method can be applied differently for each MH frame, and the same applies to all MH frames. The same applies to all subframes within one MH frame, or may be applied to each subframe differently. The present invention can be changed for each MH frame, and is applied to all subframes within one MH frame. That is, the MH frame structure can be changed in units of MH frames, which makes it possible to flexibly adjust the MH ensemble data rate.

9 is a diagram showing an example of assigning a single parade to one MH frame. That is, FIG. 9 shows an embodiment in which a single parade having three data groups included in one subframe is allocated to one MH frame.

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

For example, one parade transmits one RS frame, performs RS encoding in the RS frame encoder (not shown) of the transmission system for the corresponding RS frame, adds 24 bytes of parity data to the corresponding RS frame In this case, the specific gravity occupied by the parity data among the lengths of the entire RS codewords is about 11.37% (= 24 / (187 + 24) x 100). On the other hand, when three data groups are included in one subframe and fifteen data groups form one RS frame in the case of assigning data groups in one parade, the burst noise generated in the channel causes one group to fail Even if the situation occurs, the proportion is 6.67% (= 1/15 x 100). Therefore, in the receiving system, all errors can be corrected by erasure RS decoding. That is, when Erasure RS decoding is performed, channel errors corresponding to the number of RS parities can be corrected. Therefore, all byte errors below the number of RS parities in one RS codeword can be corrected. In this way, the receiving system can correct errors of at least one data group in one parade. The minimum burst noise length that can be corrected by one RS frame is equal to or greater than one VSB frame (i.e., the minimum burst noise length is correctable by a VSB frame).

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

Basically, the assignment of data groups to multiple parades is not different from that of a single parade. In other words, data groups in other parades allocated to one MH frame are also allocated in each of four slot periods.

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

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

FIG. 10 shows an example of transmitting three parades (Parade # 0, Parade # 1, Parade # 2) to one MH frame. Particularly, parade transmission of one subframe among five subframes constituting an MH frame For example.

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

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

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

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

Therefore, the number of groups of one parade per sub-frame (NOG) that can be assigned to one subframe can be any one of integers from 1 to 8. In this case, since one MH frame includes 5 subframes, it means that the number of data groups of one parade that can be allocated to one MH frame can be any one of multiples of 5 from 5 to 40 do.

FIG. 11 shows an example in which the allocation process of three parades in FIG. 10 is extended to five subframes in one MH frame.

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

As described above, the MH frame is divided into five subframes, and data groups corresponding to several parades are present in each subframe. Data groups corresponding to each parade are grouped in units of MH frames Will constitute a parade. There are three parades in FIG. 12, and there is one EDG (ESG Dedicated Channel) parade (NoG = 1) and two service parades (NoG = 4, NoG = 3). Also, a certain portion (e.g. 37 bytes / data group) of each data group is used to transmit FIC information encoded separately from RS encoding for mobile service data. The FIC region allocated to each data group constitutes one FIC segment, and these FIC segments are interleaved for each MH subframe to form one complete FIC transmission structure, FIC body. However, if necessary, the FIC segments may be interleaved not only in a subframe but also in an MH frame, and may have integrity in an MH frame.

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

As shown in FIG. 12, the FIC segment corresponding to each data group describes the service information of the MH ensemble to which the corresponding data group belongs. When the FIC segments in one subframe are collected and deinterleaved, all the service information of the physical channel through which the corresponding FIC is transmitted can be obtained. Therefore, the receiving system can acquire the channel information of the corresponding physical channel during the sub frame period after the physical channel tuning.

In FIG. 12, Electronic Service Guide (ESG) data is transmitted at a first slot position of each subframe with a EDC parade different from a service parade.

13 is a diagram illustrating a hierarchical signaling structure according to an embodiment of the present invention. The mobile broadcasting technology according to the present embodiment employs a signaling method using FIC and SMT as shown in FIG. This is referred to as a hierarchical signaling structure in the present invention.

Hereinafter, a description will be given of how the receiving system approaches the virtual channel by FIC and SMT, with reference to FIG.

The physical channel level signaling data, FIC body, informs the physical location of each data stream for each virtual channel. In addition, the FIC body provides the upper level information of each virtual channel. (The FIC body identifies the physical location of each virtual channel and provides a very high level description of each virtual channel.) .

The SM ensemble level signaling data SM provides the MH ensemble level signaling information. Each SMT provides IP access information of each virtual channel belonging to the corresponding MH ensemble including each SMT. In addition, the SMT provides IP stream component level information necessary for the service of the corresponding virtual channel (SMT). The SMT provides the IP stream component level information necessary for the service of the corresponding virtual channel. and the IP stream component level information required for the virtual channel service acquisition.

Each of the MH ensembles (Ensemble 0, 1, ..., K) includes stream information (for example, Virtual Channel 0 IP Stream, Virtual Channel 1 IP Stream, Virtual Channel 2 IP Stream). For example, Ensemble 0 includes Virtual Channel 0 IP Stream and Virtual Channel 1 IP Stream. Also, in each MH ensemble, information related to a related virtual channel (Virtual Channel 0 Table Entry, Virtual Channel 0 Access Info., Virtual Channel 1 Table Entry, Virtual Channel 1 Access Info., Virtual Channel 2 Table Entry, Virtual Channel 2 Access Info ., Virtual Channel N Table Entry, and Virtual Channel N Access Info.).

The FIC body payload includes information about the ensemble of the MH (the ensemble_id field and the like), information on the virtual channel related to the corresponding MH ensemble (the major channel num field and the minor channel num field, 1, ..., N in the figure).

Finally, the application in the receiving system is as follows.

When the user selects a channel desired to be viewed (referred to as 'channel θ' for convenience of explanation), the receiving system first parses the received FIC. Then, the receiving system acquires information (Ensemble Location) about the MH ensemble associated with the virtual channel corresponding to the channel [theta] (referred to as 'MH ensemble [theta]' for convenience of explanation). The receiving system obtains only the slots corresponding to the MH ensemble &thetas; by means of the time slicing method to construct the ensemble &thetas;. As described above, the ensemble? Comprises the SMT for the associated virtual channels (including channel?) And the IP stream for the virtual channels concerned. Therefore, the receiving system acquires various information (Virtual Channel? Table Entry) about the channel? And stream access information (Virtual Channel? Access Info.) For the channel? By using the SMT included in the configured MH ensemble?. The receiving system receives only the related IP stream using the stream access information for the channel [theta], and provides the user with a service for the channel [theta].

In addition, the receiving system according to the present invention introduces a fast information channel (FIC) to allow a user to access a currently broadcasted service more quickly.

That is, the FIC handler 215 of FIG. 1 parses the FIC body, which is an FIC transmission structure, and outputs the result to the physical adaptive control signal handler 216.

14 is a diagram illustrating an embodiment of an FIC body format according to the present invention. According to the present embodiment, the FIC format is composed of an FIC body header and an FIC body payload.

Meanwhile, according to the present embodiment, the data transmitted through the FIC body header and the FIC body payload are transmitted in FIC segment units. Each FIC segment unit is 37 bytes in size, and each FIC segment consists of a 2-byte FIC segment header and a 35-byte FIC segment payload. That is, one FIC body composed of the FIC body header and the FIC body payload is segmented by 35 bytes and carried in the FIC segment payload in one or more FIC segments.

In the present invention, one FIC segment is inserted into one data group and transmitted. In this case, the receiving system receives a slot corresponding to each data group by a time slicing method.

Meanwhile, the signaling decoder 190 in the receiving system of FIG. 1 collects each FIC segment inserted into each data group. And the signaling decoder 190 constructs one FIC body using each FIC segment collected. The signaling decoder 190 performs a decoding operation on the FIC body payload of one FIC body corresponding to the encoding of a signaling encoder (not shown) in the transmission system, and one decoded FIC body payload is FIC And outputs it to the handler 215. The FIC handler 215 parses the FIC data in the FIC body payload and outputs the parsed FIC data to the physical adaptive control signal handler 216. The physical adaptive control signal handler 216 performs operations related to the MH ensemble, the virtual channel, the SMT, and the like using the input FIC data.

Meanwhile, according to one embodiment, when one FIC body is segmented, if the last segment segmented is 35 bytes or less, a stuffing byte is allocated to the remaining portion of the FIC segment payload so as to make the size of the last FIC segment 35 bytes. Can be assumed.

Each byte value (FIC segment: 37 bytes, FIC segment header: 2 bytes, FIC segment payload: 35 bytes) described above is only an example, and the present invention is not limited thereto.

15 is a diagram showing an embodiment of a data structure of an FIC segment according to the present invention. Here, the FIC segment means a unit used for transmission of FIC data.

The FIC segment consists of an FIC segment header and an FIC segment payload. According to FIG. 15, the FIC segment payload can be regarded as a portion of the for loop. The FIC segment header may include an FIC_type field, an error_indicator field, an FIC_seg_number field, and an FIC_last_seg_number field. The description of each field is as follows.

The FIC_type field (2 bits) indicates the type of the corresponding FIC.

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

The FIC_seg_number field (4 bits) indicates the number of the corresponding FIC segment when one FIC body is divided into a plurality of FIC segments.

The FIC_last_seg_number field (4 bits) indicates the last FIC segment number of the corresponding FIC body.

16 is a diagram illustrating an embodiment of a bitstream syntax structure for a payload of an FIC segment when the FIC type field value is '0' according to the present invention.

In this embodiment, the payload of the FIC segment is divided into three areas.

The first area exists only when the FIC_seg_number is '0', and may include a current_next_indicator field, an ESG_version field, and a transport_stream_id field. However, it can be assumed that the above three fields are present regardless of the FIC_seg_number depending on the embodiment.

The current_next_indicator field (1 bit) indicates whether the corresponding FIC data includes MH ensemble configuration information of the MH frame including the current FIC segment or MH ensemble configuration information of the next MH frame Indicator).

The ESG_version field (5 bits) indicates the version information of the ESG, and a version of the service guide providing channel of the corresponding ESG is provided to inform the receiving system whether the ESG is updated.

The transport_stream_id field (16 bits) indicates a unique identifier of a broadcast stream to which the FIC segment is transmitted.

The second area is an ensemble loop area, and may include an ensemble_id field, an SI_version field, and a num_channel field.

The ensemble_id field (8 bits) indicates the identifier of the MH ensemble to which MH services described later are transmitted. This field binds the MH services with the MH ensemble.

The SI_version field (4 bits) indicates the version information of the SI data of the corresponding ensemble transmitted in the RS frame.

The num_channel field (8 bits) indicates the number of virtual channels transmitted through the ensemble.

The third region may include a channel_type field, a channel_activity field, a CA_indicator field, a stand_alone_service_indicator field, a major_channel_num field, and a minor_channel_num field in a channel loop region.

The channel_type field (5 bits) indicates a service type of the corresponding virtual channel. For example, this field may represent an audio / video channel, an audio / video and data channel, an audio only channel, a data only channel, a file download channel, an ESG delivery channel, a notification channel,

The channel_activity field (2 bits) indicates the activity information of the corresponding virtual channel, so that it can know whether the corresponding virtual channel provides the current service.

The CA_indicator field (1 bit) indicates whether a conditional access (CA) is applied to the corresponding virtual channel.

The stand_alone_service_indicator field (1 bit) indicates whether the virtual channel service is a stand alone service.

The major_channel_num field (8 bits) indicates the major channel number of the corresponding virtual channel.

The minor_channel_num field (8 bits) indicates the minor channel number of the corresponding virtual channel.

17 is a diagram showing an embodiment of a bitstream syntax of a service map table (hereinafter referred to as "SMT ") according to an embodiment of the present invention.

The SMT according to this embodiment is written in the MPEG-2 private section form, but the scope of the present invention is not limited thereto. The SMT according to the present embodiment includes description information of each virtual channel in one MH ensemble, and other additional information may be included in the descriptor area.

The SMT according to the present embodiment is transmitted from the transmission system to the reception system, including at least one field.

As described above in FIG. 3, the SMT section may be included in the MH TP in the RS frame and transmitted. In this case, the RS frame decoders 170 and 180 of FIG. 1 decode the input RS frame, and the decoded RS frame is output to the corresponding RS frame handlers 211 and 212. Each of the RS frame handlers 211 and 212 divides the inputted RS frame in units of rows to form an MH TP and outputs the MH TP to the MH TP handler 213.

If it is determined that the corresponding MH TP includes the SMT section based on the header of each inputted MH TP, the MH TP handler 213 parses the included SMT section and transmits the SI data in the parsed SMT section to the physical adaptive control signal And outputs it to the handler 216. However, in this case, SMT is not encapsulated in IP datagram.

On the other hand, when the SMT is encapsulated into an IP datagram, the MH TP handler 213 determines that the corresponding MH TP includes an SMT section based on the header of each MH TP inputted, 220. Then, the IP network stack 220 performs IP and UDP processing on the SMT section and outputs the IP and UDP processing to the SI handler 240. The SI handler 240 parses the input SMT section and controls the parsed SI to be stored in the storage unit 290.

On the other hand, examples of fields that can be transmitted through the SMT are as follows.

The table_id field (8 bits) is an 8-bit field for identifying the type of the table, which indicates that the table is SMT (table_id: An 8-bit unsigned integer number indicates that the type of table section being defined in Service Map Table (SMT)).

The ensemble_id field (8 bits) is an ID value associated with the corresponding MH ensemble, and values of 0x00 to 0x3F may be assigned. The value of this field is preferably derived from the parade_id of the TPC data. If the corresponding MH ensemble is transmitted through the primary RS frame, the most significant bit (MSB) is set to '0', and the remaining 7 bits are used as the parade_id value of the corresponding MH parade. If the corresponding MH ensemble is transmitted through the secondary RS frame, the most significant bit (MSB) is set to '1' and the remaining 7 bits are used as the parade_id value of the corresponding MH parade (This 8-bit unsigned integer field in the range 0x00 to 0x3F Ensemble ID associated with this MH Ensemble. The value of this field shall be derived from the parade_id carried from the baseband processor of the MH physical layer subsystem, by the parade_id of the associated MH Parade for The least significant bit, and using '0' for the most significant bit when the MH Ensemble is carried over the Primary RS frame, and using '1' for the most significant bit when the MH Ensemble is performed over the Secondary RS frame. ).

The num_channels field (8 bits) indicates the number of virtual channels in the SMT section (This 8 bit field specifies the number of virtual channels in this SMT section.).

Meanwhile, the SMT according to the present embodiment provides information on a plurality of virtual channels using a for loop.

The major_channel_num field (8 bits) indicates the major channel number associated with the virtual channel, and may be assigned from 0x00 to 0xFF (this 8-bit unsigned integer field in the range 0x00 to 0xFF represents the major channel number associated with this virtual channel.).

The minor_channel_num field (8 bits) indicates the minor channel number associated with the virtual channel, and may be assigned from 0x00 to 0xFF (this 8-bit unsigned integer field in the range 0x00 to 0xFF represents the minor channel number associated with this virtual channel.).

The short_channel_name field indicates the short name of the virtual channel (the short name of the virtual channel.).

The service_id field (16 bits) indicates a value for identifying the virtual channel service (A 16-bit unsigned integer number that identifies the virtual channel service).

The service_type field (6 bits) indicates the type of service to be transmitted on the virtual channel, as defined in Table 2 below. (A 6-bit enumerated type field that will identify the type of service carried in this virtual channel as defined in Table 2).

0x00 [Reserved] 0x01 MH_digital_television - The virtual channel carries the television programming (audio, video and optional associated data) conforming to ATSC standards. 0x02 MH_audio - The virtual channel carries audio programming and optional associated data conforming to ATSC standards. 0x03 MH_data_only_service - The virtual channel carries a data service conforming to ATSC standards, but no video or audio component. 0x04- 0xFF [Reserved for future ATSC use]

The virtual_channel_activity field (2 bits) identifies whether the corresponding virtual channel is activated or not. If the most significant bit (MSB) of the virtual_channel_activity field is '1', it indicates that the corresponding virtual channel is active. If the MSB is '0', it indicates that the corresponding virtual channel is not active. If the least significant bit (LSB) is '1', it indicates that the corresponding virtual channel is a hidden channel. If the LSB is '0', it indicates that the corresponding virtual channel is not a hidden channel (A 2-bit enumerated field The virtual channel is active (when set to 1) or the inactive (when set to 0) and the least significant bit is if the virtual channel is hidden (when set to 1) or not (when set to 0).

The num_components field (5 bits) indicates the number of the IP stream component on the virtual channel (This 5-bit field specifies the number of IP stream components in this virtual channel.).

When the IP_version_flag field (1 bit) is set to '1', the source_IP_address field, the virtual_channel_target_IP_address field, and the component_target_IP_address field indicate an IPv6 address, and when set to '0', a source_IP_address field, a virtual_channel_target_IP_address field, and a component_target_IP_address field indicate IPv4 addresses IP_address, virtual_channel_target_IP_address, and component_target_IP_address fields that are present, are IPv6 addresses, and when set to '0' indicate that source_IP_address, virtual_channel_target_IP_address, and component_target_IP_address fields are IPv4 addresses.

When the source_IP_address_flag field (1 bit) is set, it indicates that the source IP address of the virtual channel exists for a specific multicast source (A 1-bit Boolean flag indicating that when a source IP address of this virtual channel is present for source specific multicast.

When the virtual_channel_target_IP_address_flag field (1 bit) is set, it indicates that the corresponding IP stream component is transmitted through an IP datagram having a target IP address different from virtual_channel_target_IP_address. Therefore, when this flag is set, the receiving system uses component_target_IP_address as target_IP_address and ignores the virtual_channel_target_IP_address field in the num_channels loop to access the corresponding IP stream component (when set, this IP stream component IP_address to IP_address to IP_address to IP_address to IP_address to IP_address to IP_address to IP_address to IP_address to IP_address to IP_address to IP_address to IP_address to IP_address to IP_address to IP_address to IP_address to IP_address to IP_address to IP_address to IP_address to virtual_channel_target_IP_address.

The source_IP_address field (32 or 128 bits) needs to be interpreted when the source_IP_address_flag is set to '1', but it need not be interpreted if the source_IP_address_flag is not set to '0'. When the source_IP_address_flag is set to '1' and the IP_version_flag field is set to '0', this field indicates a 32-bit IPv4 address indicating the source of the virtual channel. If the IP_version_flag field is set to '1', this field indicates a 32-bit IPv6 address indicating the source of the corresponding virtual channel (This field shall be present if the source_IP_address_flag is set to '1' and shall not present the source_IP_address_flag is If the IP_version_flag field is set to '0', this field specifies a 32-bit IPv4 address indicating the source of this virtual channel. bit IPv6 address indicating the source of this virtual channel.

The virtual_channel_target_IP_address field (32 or 128 bits) needs to be interpreted when the virtual_channel_target_IP_address_flag is set to '1', but not when the virtual_channel_target_IP_address_flag is set to '0'. When the virtual_channel_target_IP_address_flag is set to '1' and the IP_version_flag field is set to '0', this field indicates a 32-bit target IPv4 address for the virtual channel. When the virtual_channel_target_IP_address_flag is set to '1' and the IP_version_flag field is set to '1', this field indicates a 64-bit target IPv6 address for the virtual channel. If the corresponding virtual_channel_target_IP_address can not be interpreted, the component_target_IP_address field in the num_channels loop must be interpreted and the receiving system must use component_target_IP_address to access the IP stream component (this field shall be the virtual_channel_target_IP_address_flag is set to '1' If the IP_version_flag field is set to '1', this field is set to '0', this field is set to '0'. field is 128-bit target IPv6 address for this virtual channel. If this virtual_channel_target_IP_address does not present, then the component_target_IP_address field in the num_channels loop will present and the receiver will utilize the component_target_IP_address to access IP stream components.

Meanwhile, the SMT according to the present embodiment provides information on a plurality of components using a for loop.

The RTP_payload_type field (7 bits) indicates the encoding format of the component according to Table 3 below. This field shall be ignored if the IP stream component is not encapsulated by RTP. (This 7-bit field identifies the encoding format of the component according to Table 3.If the IP stream component is not encapsulated in RTP, this field shall be deprecated.).

Table 3 below shows an example of the RTP Payload Type.

RTP_payload_type Meaning 35 AVC video 36 MH audio 37 -72 [Reserved for future ATSC use]

The component_target_IP_address_flag field (1 bit) indicates that when the flag is set, the corresponding IP stream component is transmitted via an IP datagram having a target IP address different from virtual_channel_target_IP_address. When this flag is set, the receiving system uses component_target_IP_address as the target IP address to access the corresponding IP stream component and ignores the virtual_channel_target_IP_address in the num_channels loop (when the A-bit Boolean flag indicates that when set, this IP stream component The IP address of the target IP address to be accessed is the IP address of the virtual IP address of the virtual IP address of the virtual IP address of the virtual IP address.

The component_target_IP_address field (32 or 128 bits) indicates the 32-bit target IPv4 address for the corresponding IP stream component when the IP_version_flag field is set to '0'. If the IP_version_flag field is set to '1', this field indicates a 128-bit target IPv6 address for the corresponding IP stream component (When IP_version_flag field is set to '0', this field is set to 32-bit target IPv4 address for this IP stream component. When IP_version_flag field is set to '1', this field specifies 128-bit target IPv6 address for this IP stream component.

The port_num_count field (6 bits) indicates the number of the UDP port associated with the corresponding IP stream component. The target UDP port number value is incremented by 1, starting from the value of the target_UDP_port_num field. For the RTP stream, the target UDP port number is incremented by 2, starting from the value of the target_UPD_port_num field, in order to include the RTCP stream associated with the RTP stream (this field indicates the number of UDP ports associated with this IP stream component. The values of the target UDP port numbers shall start from the target_UDP_port_num field and shall be incremented by one. For RTP streams, the target UDP port numbers shall start from the target_UPD_port_num field and shall be incremented by two, to incorporate RTCP streams associated with the RTP streams.

The target_UDP_port_num field (16 bits) indicates the target UDP port number for the corresponding IP stream component. For the RTP stream, the value of target_UDP_port_num is even, and the next higher value represents the target UDP port number of the associated RTCP stream (A 16-bit unsigned integer field, which represents the target UDP port number for this IP stream component. , the value of target_UDP_port_num shall be even, and the next higher value shall represent the target UDP port number of the associated RTCP stream.

The component_level_descriptor () indicates a descriptor providing additional information about the corresponding IP component (Zero or more descriptors providing additional information for this IP stream component, may be included).

virtual_channel_level_descriptor () indicates a descriptor providing additional information about the virtual channel (Zero or more descriptors providing additional information for this virtual channel, may be included).

The ensemble_level_descriptor () indicates a descriptor that provides additional information on the MH ensembles described by the SMT (Zero or more descriptors providing for the MH Ensemble which SMT describes, may be included.).

18 is a diagram showing the syntax of the MH Audio Descriptor according to the embodiment of the present invention.

The MH_audio_descriptor () should be used as the component_level_descriptor in the SMT when there is one or more audio services present as a component of the current event. This teller can tell you the type of audio language and whether it is in stereo mode. If there is no audio service associated with the current event, MH_audio_descriptor () is preferably not interpreted for the current event (The MH_audio_descriptor is used as a component_level_descriptor of the SMT when there is one or more audio services present as a component of the If there is no audio service associated with the current event, then the MH_audio_descriptor will not be present for that event.

The fields shown in FIG. 18 will be described in detail as follows.

The descriptor_tag field (8 bits) indicates that the corresponding descriptor is MH_audio_descriptor () (This 8-bit unsigned integer shall have the value TBD, identifying this descriptor as MH_audio_descriptor.).

The descriptor_length field (8 bits) indicates the length in bytes from the end of this field to the end of the descriptor (This 8-bit unsigned integer specifies the length (in bytes) immediately following this field.

The channel_configuration field (8 bits) indicates the number and configuration of the audio channel. The values from 1 to 6 indicate the number and configuration of the audio channel specified in the "Default bit stream index number" on table 42 of ISO / IEC 13818-7: 2006. Table 42. ISO / IEC 13818-7: 2006.All other values taken that the the number of audio channels number and configuration of audio channels is undefined.

The sample_rate_code field (3 bits) indicates the sample rate of the encoded audio (This is a 3-bit field which indicates the sample rate of the encoded audio. The indication may be one specific sample rate, A set of values that include the sample rate of the encoded audio as defined in Table A3.3 of ATSCA / 52B.).

The lower 5 bits of the bit_rate_code field (6 bits) indicate the nominal bit rate. If the most significant bit is '0', the corresponding bit rate is correct. If the most significant bit is '1' The rate is the upper bound defined in Table A3.4 of ATSC A / 53 (This is a 6-bit field. The lower 5 bits indicate a nominal bit rate. The MSB indicates whether the indicated bit rate is exact = 0) or an upper limit (MSB = 1) as defined in Table A3.4 of ATSCA / 53B.

The ISO_639_language_code field (3 bytes: 24 bits) indicates the language used for the audio stream component. If there is no language specified for the audio stream component, set each byte value to 0x00 (This 3-byte (24 bits) field, in conformance with ISO 639.2 / B [ In case of no language specified for this audio stream component, each byte should have the value 0x00.).

19 is a diagram showing a syntax of an MH RTP payload type descriptor according to an embodiment of the present invention.

The MH_RTP_payload_type_descriptor () indicates the type of the RTP payload, and exists only when the RTP_payload_type value in the num_components loop of the SMT has a value of 96 to 127. And this descriptor is used as a component_level_descriptor of SMT.

MH_RTP_payload_type_decryptor matches the RTP_payload_type value to the MIME type. As a result, the receiving system may collect the encoding format of the RTP-encapsulated IP stream component (The MH_RTP_payload_type_descriptor shall present and only if the value of RTP_payload_type in the num_components loop of the SMT is a dynamic value in the range of 96 -127. When MH_RTP_payload_type_descriptor is used, an MH_RTP_payload_type_descriptor translates a dynamic RTP_payload_type_descriptor value to a MIME type, so that the receiver can gather the IP stream component, encapsulated in RTP .).

Details of the fields included in the MH_RTP_payload_type_descriptor () are as follows.

The descriptor_tag field (8 bits) indicates that the corresponding descriptor is MH_RTP_payload_type_descriptor (). This 8-bit unsigned integer shall have the value TBD, identifying this descriptor as MH_RTP_payload_type_descriptor.

The descriptor_length field (8 bits) indicates the size from this field to the last field in this descriptor. (This 8-bit unsigned integer specifies the length (in bytes) immediately following this field.

The RTP_payload_type field (7 bits) indicates the encoding format of the IP stream component, and the RTP_payload_type value has a value ranging from 96 to 127 (this 7-bit field identifies the encoding format of the IP stream component, where the value of this RTP_payload_type is in the dynamic value range 96-127.).

The MIME_type_length field indicates the size of the MIME type (this field specifies the length (in bytes) of the MIME_type.).

The MIME_type field indicates a MIME type corresponding to the encoding format of the IP stream component described by this MH_RTP_payload_type_descriptor (). The MIME_type field describes the MH_RTP_payload_type_descriptor describing the encoding format of the IP stream component.

20 is a diagram showing a syntax of an MH Current Event Descriptor according to an embodiment of the present invention.

The MH_current_event_descriptor () is used as a virtual_channel_level_descriptor in the SMT. This descriptor provides basic information (e.g., current event start time, duration, title) about the current event transmitted on the virtual channel (The MH_current_event_descriptor, when present, when used as a virtual_channel_level_descriptor of the SMT . The MH_current_event_descriptor provides the basic information on the current event carried through this virtual channel (current event start time, duration and title).

Details of each field included in the MH_current_event_descriptor are as follows.

The descriptor_tag field (8 bits) is a field indicating that this descriptor is MH_current_event_descriptor (). (This 8-bit unsigned integer shall have the value TBD, identifying this descriptor as MH_current_event_descriptor.)

The descriptor_length field (8 bits) indicates the size from this field to the last field in this descriptor. (This 8-bit unsigned integer specifies the length (in bytes) immediately following this field.

The current_event_start_time field (32 bits) indicates the start time of this event (A 32-bit unsigned integer representing the start time of the current event as the number of GPS seconds since 00:00:00 UTC, January 6, 1980).

The current_event_duration field (24 bits) indicates the duration of this event (A 24-bit field contains the duration of the current event in hours, minutes, seconds, format: 6 digits, 4-bit BCD = 24 bits).

The title_length field indicates the size of the title_text (This field specifies the length (in bytes) of the title_text. Value 0 means that title exists for this event.).

The title_text field indicates the title of the corresponding event. (The event title in the format of a multiple string structure as defined in ATSC A / 65C [x].).

21 is a diagram showing a syntax of an MH Next Event Descriptor according to an embodiment of the present invention.

The MH_next_event_descriptor () is used as a virtual_channel_level_descriptor of the SMT. The MH_next_event_descriptor () provides basic information (for example, a future event start time, duration, title) on a future event transmitted through the corresponding virtual channel (the optional MH_next_event_descriptor, may present as a virtual_channel_level_descriptor of the SMT. MH next event descriptor provides the basic information on the next event.

Details of each field included in the MH_next_event_descriptor are as follows.

The descriptor_tag field (8 bits) indicates that this descriptor is MH_next_event_descriptor (). This 8-bit unsigned integer shall have the value TBD, identifying this descriptor as MH_next_event_descriptor.

The descriptor_length field (8 bits) indicates the size from this field to the last field in this descriptor. (This 8-bit unsigned integer specifies the length (in bytes) immediately following this field.

The next_event_start_time field (32 bits) represents the start time of the future event (A 32-bit unsigned integer representing the start time of the next event as the number of GPS seconds since 00:00:00 UTC, January 6, 1980).

The next_event_duration field (24 bits) indicates the duration of the future event (A 24-bit field contains the duration of the next event in hours, minutes, seconds, Format: 6 digits, 4-bit BCD = 24 bits).

The title_length field indicates the size of the title_text (This field specifies the length (in bytes) of the title_text. Value 0 means that title exists for this event.).

The title_text field indicates the title of the corresponding event. (The event title in the format of a multiple string structure as defined in ATSC A / 65C [x].).

22 is a diagram showing a syntax of an MH System Time Descriptor according to an embodiment of the present invention.

The MH_system_time_descriptor () is used as the ensemble_level_descriptor of the SMT. The MH_system_time_descriptor () provides current time and date information. In addition, the MH_system_time_descriptor provides time zone information for a transmission system for transmitting a received broadcast stream in consideration of a mobile environment (The MH_system_time_descriptor, when present, used as an ensemble_level_descriptor of the SMT. The MH system time descriptor provides the current date and time of day information. In addition, taking the mobile / portable characteristic of MH, the MH system time descriptor provides the time zone information for the transmitter of this broadcast stream.

Details of each field included in the MH_system_time_descriptor () are as follows.

The descriptor_tag field (8 bits) indicates that this descriptor is MH_system_time_descriptor () (This 8-bit unsigned integer shall have the value TBD, identifying this descriptor as MH_system_time_descriptor.).

The descriptor_length field (8 bits) indicates the size from this field to the last field in this descriptor (This 8-bit unsigned integer specifies the length (in bytes) immediately following this field.

The system_time field (32 bits) represents the current time on the GPS (A 32-bit unsigned integer representing the current system time as the number of GPS seconds since 00:00:00 UTC, January 6th, 1980.).

The GPS_UTC_offset field (8 bits) indicates the current offset between GPS and UTC. To convert the GPS time to UTC time, subtract GPS_UTC_offset from GPS (An 8-bit unsigned integer that defines the current offset in whole seconds between GPS and UTC time standards. To convert GPS time to UTC, the GPS_UTC_offset is subtracted from GPS time. Whenever the International Bureau of Weights and Measures decides that the current offset is too far in error, an additional leap may be added (or subtracted), and the GPS_UTC_offset will reflect the change.

The time_zone_offset_polarity field (1 bit) indicates whether the time for the time zone of the broadcast station position precedes or follows UTC. If this field is '0', it means that the time in the current time zone is ahead of UTC, so the value of time_zone_offset is added to UTC. On the other hand, if this field is '1', it means that the time in the current time zone is behind UTC, so that the time_zone_offset value is added in UTC (an one-bit indicator that indicates whether or not the time zone is the broadcast This field indicates that the current time zone is the UTC (ie, the time_zone_offset is added to UTC) and when set to '1', this field indicates that is the current time zone lags UTC.

The time_zone_offset field (31 bits) represents the time offset value for the broadcast station position as compared to UTC (representing the time offset of the time zone in GPS seconds, where the broadcast station is located, compared to UTC .).

The daylight_savings field (16 bits) provides information about daylight saving time (Daylight Savings Time control bytes. Refer to Annex A of ATSC-A / 65C with amd. # 1 [x], for the use of these two bytes.) .

The time_zone field (5x8 bits) represents the time zone for the transmission system transmitting the received broadcast stream.

23 is a diagram for explaining the segmentation and encapsulation of the SMT according to the present invention.

According to the present invention, the SMT is encapsulated in UDP with the target IP address and the target UDP port number on the IP datagram. That is, the SMT is segmented into a predetermined number of sections, then encapsulated into a UDP header, and then encapsulated into an IP header.

The SMT section also provides signaling information for all the virtual channels contained in the MH ensemble containing the SMT section. And the SMT section describing the MH ensemble includes at least one in each RS frame belonging to the corresponding MH ensemble. And each SMT section is distinguished by the ensemble_id included in each section. In the embodiment of the present invention, the receiving system recognizes the target IP address and the target UDP port number so that the receiving system can parse the target IP address and the target UDP port number without requesting additional information.

24 is a flow diagram illustrating accessing a virtual channel using FIC and SMT in accordance with an embodiment of the present invention.

That is, one physical channel is tuned (S501), and if there is an MH signal in the tuned physical channel (S502), the MH signal is demodulated (S503). Then, the FIC segments are collected in units of subframes from the demodulated MH signal (S504, S505).

In the present invention, one FIC segment is inserted into one data group and transmitted. That is, the FIC segment corresponding to each data group describes the service information of the MH ensemble to which the corresponding data group belongs. When the FIC segments are deinterleaved by collecting in units of subframes, all the service information of the physical channel through which the corresponding FIC segment is transmitted can be obtained. Therefore, the receiving system can acquire the channel information of the corresponding physical channel during the sub frame period after the physical channel tuning. When the FIC segments are collected by the steps S504 and S505, the broadcast stream to which the corresponding FIC segment is transmitted is identified (S506). The broadcast stream can be identified, for example, by parsing the transport_stream_id field of the FIC body configured by collecting the FIC segments.

Further, an ensemble identifier, a major channel number, a minor channel number, and channel type information are extracted from the FIC body (S507). Then, only the slots corresponding to the ensemble desired to be received are acquired by the time slicing method using the extracted ensemble information to configure an ensemble (S508).

Then, the RS frame corresponding to the desired ensemble is decoded (S509), and an IP socket is opened to receive the SMT (S510).

The SMT is encapsulated in UDP with a target IP address and a target UDP port number on an IP datagram. That is, the SMT is segmented into a predetermined number of sections, then encapsulated into a UDP header, and then encapsulated into an IP header. In the embodiment of the present invention, the receiving system knows the target IP address and the target UDP port number so that the receiving system parses the SMT section and the descriptors of each SMT section without requesting additional information (S511).

The SMT section provides signaling information for all the virtual channels included in the MH ensemble including the corresponding SMT section. And the SMT section describing the MH ensemble includes at least one in each RS frame belonging to the corresponding MH ensemble. And each SMT section is distinguished by the ensemble_id included in each section.

Also, each SMT provides IP access information of each virtual channel belonging to the corresponding MH ensemble including each SMT. Also, the SMT provides IP stream component level information necessary for the service of the corresponding virtual channel.

Accordingly, an IP stream component belonging to a virtual channel desired to be received is accessed using the information parsed from the SMT (S513), and a service for the virtual channel is provided to the user (S514).

On the other hand, a digital broadcast receiver according to an embodiment of the present invention will be described in detail below with reference to FIGS. 1 to 24 described above. Therefore, a digital broadcast receiver according to an embodiment of the present invention can be applied to some or all of the descriptions of FIGS. 1 to 24 described above. However, the scope of rights of the present invention should, in principle, be determined in accordance with the contents of the claims.

25 is a diagram showing a protocol stack of an MH system according to an embodiment of the present invention. Hereinafter, a protocol stack of the MH system according to an embodiment of the present invention will be briefly described with reference to FIG.

According to an embodiment of the present invention, before data of an IP level, an RTP level, and a raw level are transmitted through an MH transport layer and a physical layer, (For example, a protocol between an MH Encryption / Decryption Layer and an MH Signaling Layer), and a signaling method for implementing the above-described technology Etc.), and defines how to control the service to which control access is applied to the external interface.

In addition, throughout this specification, the term "control access" is used. The term "reception restriction" refers to a state in which mobile service data is encrypted (for example, encrypted, scrambled, etc.), and may correspond to a case where a reception restriction function is set by a CAS (Control Access System), or the like.

Throughout this specification, the term control data is used, and the control data corresponds to the data necessary to remove the reception restriction function of the reception restriction data. The control data may be referred to as a key value. The control data may include, for example, an Entitlement Management Message (EMM), an Entitlement Control Message (ECM), or the like. In addition, the ECM may include a control word (CW).

26 is a diagram illustrating a configuration of a digital broadcast receiver according to an embodiment of the present invention. Hereinafter, a function of processing mobile service data with a reception restriction by a digital broadcast receiver according to an embodiment of the present invention will be described with reference to FIG. Meanwhile, FIG. 1 and FIG. 26 are similar in terms of handling mobile digital broadcasting, but in particular, the digital broadcasting receiver shown in FIG. 26 can also process mobile service data with limited reception. Those skilled in the art can also easily understand the operation of the digital broadcast receiver of FIG. 26 with reference to the entire description of this specification. It is to be understood that the scope of the present invention is not limited to the contents described in the drawings, but, in principle, should be construed in accordance with the contents of claims.

26, a digital broadcasting receiver 2600 according to an embodiment of the present invention includes a receiving module 2610, an MH signaling DB 2620, a user interface / (MH TP / IP based Signaling Decoder) 2640, a transport handler 2650, a secure handler 2660 An application decoder 2670, a post processor / output module 2680, and the like. For reference, a dotted line in the drawing shown in Fig. 26 indicates a flow of data for controlling each module, and a solid line indicates a flow of actual data to be transmitted.

Further, the receiving module 2610 may include a tuner 2611, an operation controller 2612, a VSB demodulator 2613, an equalizer 2614, an MH block decoder 2614, (MH Block Decoder) 2615, an RS frame decoder 2616, a known sequence detector 2617, and a signaling decoder 2618.

Meanwhile, the user interface unit / controller 2630 may include an application manager 2631 and a user interface 2632. Meanwhile, the MH TP / IP based signaling decoder 2640 may include an MH Transport Signaling Decoder 2641 and an IP-based Signaling Decoder 2642 .

On the other hand, the transport handler 2650 includes an MH-TP demux 2651, an IP data handler 2652, a UDP data handler 2653 A File Delivery Handler 2654, a Stream Delivery Handler 2655, and an MH Encrypt / Decrypt Handler 2656. The File Delivery Handler 2654 may be any of the following:

On the other hand, the secure handler 2660 includes a smart card interface 2661, a secure signaling DB 2662, a copy protection handler 2663, And an encrypt / decrypt handler 2656. For reference, an embedded secure processor may be used instead of the smart card interface 2661.

The application decoder 2670 includes an application handler 2671, an audio decoder 2672, a video decoder 2673, and a data decoder 2674 .

The tuner 2611 of the digital broadcast receiver 2600 according to an embodiment of the present invention receives a broadcast signal in which mobile service data and main service data are multiplexed. Of course, a module responsible for such a function may also be referred to as a receiver.

The RS frame decoder 2616 extracts transmission parameter channel signaling information and fast information channel signaling information from the received data group in the mobile service data. Of course, a module responsible for such a function may also be referred to as an extraction unit. Alternatively, a separate FIC decoder may be added to extract the FIC signaling information.

The MH transport signaling decoder 2641 may use the extracted fast information channel signaling information to generate a first program table for describing an ensemble virtual channel information and a service as a virtual channel group of the received mobile service data, . Of course, a module responsible for such a function may also be referred to as an acquisition unit.

Meanwhile, the first program table may correspond to a SMT (Service Map Table) which is a configuration information table of mobile service data, and the SMT may be configured as shown in FIG. 17 or FIG. 27, for example.

Also, the transport handler 2650 and the securer handler 2660 can use the obtained first program table to determine whether the mobile service data has been encrypted, And detects a descriptor (Control Access Descriptor). Of course, a module responsible for such a function may also be referred to as a detection unit. However, the control access descriptor will be described later in detail with reference to FIG.

The transport handler 2650 and the security handler 2660 use the information of the detected CA Descriptor to determine whether the encrypted mobile service data is encrypted To be decrypted. Of course, a module responsible for such a function may be referred to as a control unit.

Therefore, according to an embodiment of the present invention, in the MH digital broadcasting environment, a legitimate right to a service to which a reception restriction is applied (for example, an encrypted service, a scrambled service, etc.) Only the broadcasting receiver can utilize the service. And, according to an embodiment of the present invention, a clear signaling method for implementing this is defined.

Furthermore, the above-described data group includes, for example, a plurality of known data sequences, and the transmission parameter signaling information and the fast information channel signaling information are, for example, It may be designed to be located between the known data string and the second known data string.

Therefore, the known data detection unit of the digital broadcast receiver according to an embodiment of the present invention detects the known data in the received broadcast signal, and the equalizer uses the detected known data to determine the known data corresponding to the detected known data The mobile service data may also be channelized. For reference, the functions of the known data detector and the equalizer have been fully described in the description of FIG.

Also, according to the embodiment of the present invention, the equalizer can improve the equalization performance by using the known data symbol sequence input from the known data detector.

Referring to FIG. 26, the operation of a broadcast receiver capable of processing a service to which reception restriction is applied will be described in more detail as follows.

The MH signaling DB 2620 is a database (DataBase) for storing MH signaling data received in the form of non-IP or IP and providing the data when necessary.

The MH transport signaling decoder 2641 processes non-IP MH signaling information among MH signaling information and the IP-based signaling decoder 2642 processes IP-based MH signaling among MH signaling information, Process information.

The MH-TP demultiplexer 2651 processes the MH-TP (Transport Packet) extracted from the RS frame, which is the output of the RS frame decoder 2626, and the IP data handler 2652 processes the MH -PTP Handles IP datagrams to be transmitted to IP layer among packets. The UDP data handler 2653 processes a UDP datagram to be transmitted to the UDP layer of the IP datagram.

The file transfer handler 2654 processes a file to be transferred to the file transfer protocol layer of the UDP datagram. The stream transmission handler 2655 processes data to be transmitted to an RTP layer (for example, a stream layer for a real-time service) among UDP datagrams.

The application manager 2631 manages a user input signal related to channel setting through a service guide display and a service guide. The application decoder 2670 manages middleware and decoders for outputting services in the MH broadcasting system. The post processor / output unit 2680 is an interface for post processing for decoded services and outputting various data to an external device.

In particular, the module responsible for the main function of the present invention includes the MH encrypt / decrypt handler 2656, the smart card interface 2661, the security signaling DB 2662, (2663), etc., will be described in more detail.

The MH encry / decrypt handler 2656 controls the MH services such that services to which control access is applied are encrypted and decrypted corresponding to the level of each layer, do.

In addition, the secure signaling DB 2662 may be configured to securely process data required to encipher or decrypt a service to which reception restriction is applied, that is, High Value Services, among the MH services, It is a database (DataBase) that stores necessary data and provides stored data when necessary.

In addition, the smart card interface 2661 refers to a processor for processing data to be safely processed, and may be replaced with an embedded secure processor.

When the high-value service is transmitted to the external interface, the copy protection handler 2663 carries out an encryption for the high-value service and processes control data necessary for the encryption.

On the other hand, in implementing the reception restriction function, information related to authentication of the device and the user, information on the reception right level of the user, control word used for performing encryption and decryption (for example, key), and so on.

To summarize again, the control data is composed of an EMM (Entitlement Management Message), an ECM (Entitlement Control Message), etc., and the ECM may include control words. The control data may be included in an Electronic Service Guide (ESG) and transmitted, or may be transmitted in other ways.

The digital broadcasting receiver 2600 receiving the control data may store the control data in the MH signaling DB 2620 or may store the control data in the secure signaling DB 2662 as a secure storage space. In some cases, the control data may be received and used in real time.

Accordingly, when a digital broadcasting receiver having a proper authority desires to use a service to which reception restriction is applied, the digital broadcasting receiver receives control data corresponding to the service from the MH signaling DB 2620 and the security signaling DB 2662 Or extracts control data corresponding to the service in real time.

Also, the extracted control data is transmitted to the MH encry / decrypt handler 2656, and the MH encry / decrypt handler 2656 uses the transmitted control data to receive the corresponding service Remove the restriction function.

Meanwhile, a packet level structure of the MH encrypted physical layer will be briefly described with reference to FIG.

When the reception restriction is applied, the encrypted MH service, the control word necessary for decrypting the encrypted MH service, and other control data necessary for reception restriction are transmitted to the MH payload Payload area of the digital broadcasting receiver. That is, the MH service to which the reception restriction is applied is transmitted through the MH payload area after being encrypted, and control data for setting and releasing the reception restriction function is also transmitted through the MH payload area.

Hereinafter, concrete data and signaling methods necessary for processing a service to which the reception restriction is applied in the MH digital broadcasting environment will be described in detail below.

27 is a diagram showing another embodiment of a bitstream syntax of a service map table (SMT) according to an embodiment of the present invention. 28 is a diagram illustrating a Control Access Descriptor according to an embodiment of the present invention. Hereinafter, tables and descriptors necessary for implementing the reception restriction function will be described with reference to FIG. 27 and FIG. 28 (see FIG. 17 as an auxiliary reference).

According to one embodiment of the present invention, an SMT (e.g., FIG. 17 or FIG. 27) representing a structure for MH services is transmitted. The SMT defines various information necessary for processing the MH service transmitted through the RS frame. For example, the MH transport signaling decoder 2641 of FIG. 26 may process the SMT. The SMT may be designed to inform the MH of services transmitted through the corresponding RS frame, , In particular, the control data necessary for processing the reception restriction function is transmitted to the digital broadcast receiver through the control access descriptor illustrated in FIG. Of course, the control data may be transmitted to the digital broadcast receiver through the ESG.

However, the SMT of FIG. 27 can be understood with reference to the SMT of FIG. 17, but some other fields are mainly described below.

The "service_provider_id" field shown in FIG. 27 indicates information identifying the service provider, the "number_of_ensemble" field indicates the number of ensembles delivered through the table, and the "physical_freq_idx" Field indicates an index of a physical frequency, an " ensemble_id " field indicates information identifying at least one ensemble, a number_of_service field indicates a number of services belonging to a specific ensemble, and a number_of_target_IP_address field indicates an index Indicates the number of target IP addresses. The description of the remaining fields shown in Fig. 27 can be easily understood through the field description of Fig.

In addition, the information necessary for accessing the reception-restricted service may be included in the descriptor shown in FIG. 28 in particular, and may be referred to as a control access descriptor for convenience. However, such a name is only an example. For the sake of convenience of description, the term MH CA descriptor may be used in place of the control access descriptor.

The control access descriptor shown in FIG. 28 includes information for identifying each level in which the mobile service data is encrypted and information about control data used when decrypting the encrypted mobile service data.

28, the " descriptor_tag " field indicates that the descriptor is the MH CA descriptor, and the " descriptor_length " field indicates the length from the present field to the last field of the descriptor (for example, quot ;, the " CA_System_ID " field indicates the type of the CA system associated with the ECM and the EMM, and the " ECM_EMM_flag " field indicates whether the current MH_CA_Desciptor is a descriptor for the ECM or a descriptor for the EMM. For example, if the value of the " ECM_EMM_flag " field is '0', MH_CA_Desciptor is a descriptor for the ECM. If the value of the ECM_EMM_flag field is 1, then MH_CA_Desciptor is a descriptor for the EMM. Of course, the above values are only examples.

The " encrypt_level_flag " field corresponds to information that identifies each level where the mobile service data is encrypted or the reception restriction is applied. For example, when the field value is '000', 'No Encryption' is displayed. If '001', 'IP Level Encryption' is displayed. , "Raw Level Encryption" is displayed in case of "011", and "reserved" is displayed in case of "others".

The " IP_flag " field indicates whether or not the information of the " destination_IP_address " field is present in the current MH_CA_Descriptor. For example, when the value of the "IP_flag" field is "0", it indicates that the information of the "IP_version_flag" field and the "destination_IP_address" field does not exist. In this case, the ECM and the EMM are transmitted to the digital broadcast receiver using the same IP address as the " destination_IP_address " of the corresponding service and the port number different from the destination_port_number of the service.

On the other hand, when the value of the "IP_flag" field is "1", it indicates that information of the "IP_version_flag" field and the "destination_IP_address" field exists.

The "IP_version_flag" field indicates the version of the "destination_IP_address". If the field value is '0', the IPv4 address is used. If the field value is '1', the IPv6 address is used.

The "destination_IP_address" field indicates a destination IP address of an IP datagram to which the ECM and the EMM are transmitted. The "destination_port_number" field indicates a destination port of the UDP datagram to which the ECM and the EMM are transmitted. Quot; field indicates a destination port number, and a " private_data_byte " field indicates data defined individually by a CAS (Control Access System).

The control access descriptor (MH_CA_Descriptor) thus defined may correspond to the descriptor in the SMT shown in FIG. 17 or FIG. More specifically, for example, the control access descriptor may be defined as a component level descriptor, a virtual channel level descriptor, and an ensemble level descriptor of the SMT shown in FIG. 17, or the control access descriptor may be defined as an SMT A descriptor of an ensemble, a descriptor of a service, and a descriptor of a target IP address.

If the control access descriptor is defined as a descriptor of the SMT service provider, the reception restriction function operates on all data corresponding to the specific service provider. On the other hand, when the control access descriptor is defined as the descriptor of the ensemble of the SMT, the reception limiting function operates on all data corresponding to the specific ensemble.

On the other hand, when the control access descriptor is defined as a descriptor of the SMT service, the reception restriction function operates on all data corresponding to the specific service. Of course, the service may correspond to a virtual channel. Then, when the control access descriptor is defined as a descriptor of the target IP address of the SMT, the reception restriction function operates on all data corresponding to the specific target IP address.

29 is a diagram illustrating an RS frame structure according to an embodiment of the present invention. 30 is a diagram illustrating an MH-TP format according to an embodiment of the present invention. Hereinafter, a packet level structure of the MH encrypted transport layer according to an embodiment of the present invention will be described with reference to FIGS. 29 and 30. FIG.

3 and FIG. 29 illustrate an example of an RS frame structure in which data to which control access is applied does not exist in the case of FIG. 3, and FIG. , An example of an RS frame structure including data to which reception restriction is applied is shown.

FIG. 29 shows a format of an RS frame for transmitting data corresponding to an MH ensemble corresponding to each MH frame, which may be an output of an MH Physical Layer Subsystem. As shown in FIG. 29, one RS frame can transmit several MH services, and one MH service is composed of several IP datagrams. In addition, the RS frame is composed of a two dimensional byte array of 187 * N bytes (BYTES). From the viewpoint of the MH transport layer, each row (ROW) Configure the transport packet.

On the other hand, one MH-TP is a format composed of a 2-byte MH-TP header and an MH-TP payload of N-2 bytes, and the format is illustrated in FIG. However, if the Stuffing bytes are k bytes, the MH-TP header may be (N-2-k) bytes.

The " type indicator " field shown in FIG. 30 indicates the data type of the payload data. When the field value is '000', it means that the MH-TP transmits signaling data. It means that the MH-TP sends an IP datagram.

The "error indicator" field indicates whether or not an error is detected in the MH-TP. The "stuff indicator" field indicates whether stuffing bytes included in the MH-TP are present. field indicates the start point of a new packet in the payload of the MH-TP, and the " stuffing bytes " field indicates a payload (if stuffing exists in K- Lt; / RTI >

31 is a diagram illustrating the structure of data that is encrypted at the IP level according to an embodiment of the present invention. 32 is a diagram illustrating the structure of data that is encrypted at the RTP level according to an embodiment of the present invention. 33 is a diagram illustrating the structure of data that is encrypted at a raw level according to an embodiment of the present invention. Hereinafter, the process of encrypting and broadcasting each level will be described with reference to FIGS. 31 to 33. FIG.

Data such as video, audio, and timed text among the IP datagrams is transmitted through a layer for a real-time application such as RTP (Real-time Transport Protocol) . For example, the data such as video, audio, and time text may be transmitted to the MH-TP layer 2660 through a stream transmission handler 2655, a UDP data handler 2653, an IP data handler 2652, Lt; / RTI >

FIG. 31 illustrates a method of packetizing real-time application data with an MH-TP after receiving restriction (for example, an encryption process) at an IP level.

First, referring to FIG. 31 and the like, a process of encrypting mobile service data at an IP level by a digital broadcast transmitter or the like will be described.

Among the MH services, the real-time application delivered through the RTP layer is packetized into the MH-TP via the UDP layer and the IP layer. At this time, the MH service to which the reception restriction is applied at the IP level is first enciphered in the Crypt / Decrypt layer where the IP datagram, which is the output of the IP layer, is MH before being packetized into the MH-TP. The IP datagram to which the encryption is applied is packetized from the MH TP layer to the MH TP, and then transmitted to the physical layer.

A process of decrypting the mobile service data encrypted at the IP level by a digital broadcast receiver or the like will be described with reference to FIG. 31 and the like.

The digital broadcast receiver can check whether or not the reception restriction is applied to the corresponding MH service using the control access descriptor included in the SMT (Fig. 17 or Fig. 27) (specifically, the encrypt_level_flag value is 001 ', Decryption is performed at the IP level. When the digital broadcast receiver performs decryption at the IP level, the MH TP demux 2651 extracts the corresponding MH service and control data (for example, ECM, EMM, etc.) from the RS frame, The decrypt handler 2656 performs decryption on the encrypted MH service using the control data processed by the securer handler 2660. The IP data handler 2652 receives the decrypted MH service and controls the other modules of the digital broadcast receiver to normally output the MH service. Of course, the encryption process can be reversed to the above-described decryption process.

FIG. 32 schematically illustrates a method of packetizing the data in the MH-TP after data of a real-time application is subjected to reception restriction (for example, an encryption process) at an RTP (stream) level .

First, referring to FIG. 32 and the like, a process of encrypting mobile service data at an RTP level by a digital broadcast transmitter or the like will be described.

When the reception restriction is applied at the RTP (stream) level, the data of the real-time application is encrypted at the crypt / decrypt layer where the output data of the RTP layer is MH, and then the encrypted data passes through the UDP layer and the IP layer MH TP layer to MH TP, and then to the physical layer.

Of course, when the reception restriction is not made, the RTP (stream) data as the output of the RTP layer bypasses the MH encrypt / decrypt layer, and then the un-encrypted RTP data is transmitted to the UDP layer and the IP Layer, MHTP layer to MHTP packetized, and then to the physical layer.

A process of decrypting the mobile service data encrypted at the RTP level by a digital broadcast receiver or the like will be described with reference to FIG. 32 and the like.

The digital broadcast receiver can confirm whether or not the reception restriction is applied to the corresponding MH service using the control access descriptor included in the SMT (Fig. 17 or Fig. 27) (specifically, the encrypt_level_flag value is 010 ', Decryption is performed at the RTP level. When the digital broadcast receiver performs decryption at the RTP level, the MH TP demux 2651 extracts the corresponding MH service and control data (for example, ECM, EMM, etc.) from the RS frame and transmits the encrypted MH The service is transmitted to the MH encrypt / decrypt handler 2656 via the IP data handler 2652 and the UDP data handler 2653. The MH encrypt / decrypt handler 2656 performs decryption on the encrypted MH service using the control data processed by the securer handler 2660. The stream transmission handler 2655 receives the decrypted MH service and controls the other modules of the digital broadcast receiver to normally output the MH service. Of course, the encryption process can be reversed to the above-described decryption process.

FIG. 33 schematically illustrates a method for packetizing the data to the MH-TP after data in the real-time application is subjected to reception restriction (for example, an encryption process) at a raw level .

First, referring to FIG. 33 and the like, a process of encrypting mobile service data at a low level by a digital broadcast transmitter or the like will be described.

If the receive limit is applied at the raw level, the raw data in the real-time application is encrypted at the MH encrypt / decrypt layer before being encapsulated at the RTP layer. The encrypted data is packetized from the MH TP layer to the MH TP via the RTP layer, the UDP layer and the IP layer, and then transmitted to the physical layer.

Of course, if reception is not restricted, the Raw data, which is the output of the application layer, bypasses the MH encrypt / decrypt layer and then passes through the RTP layer, the UDP layer, and the IP layer, TP layer to MH TP, and then to the physical layer.

A process of decrypting mobile service data encrypted at a low level by a digital broadcast receiver or the like will be described with reference to FIG. 33 and the like.

The digital broadcast receiver can check whether or not the reception restriction is applied to the corresponding MH service using the control access descriptor included in the SMT (Fig. 17 or Fig. 27) (specifically, the encrypt_level_flag value is 011 ', Decryption is performed at the low level. When the digital broadcast receiver performs decryption at a raw level, the MH TP demux 2651 extracts the corresponding MH service and control data (e.g., ECM, EMM, etc.) from the RS frame, The encrypted MH service is transmitted to the MH encrypt / decrypt handler 2656 via the IP data handler 2652, the UDP data handler 2653, and the stream transmission handler 2655. The MH encrypt / decrypt handler 2656 performs decryption on the encrypted MH service using the control data processed by the securer handler 2660. The application decoder 2670 receives the decrypted MH service and controls the other modules of the digital broadcast receiver to normally output the MH service. Of course, the encryption process can be reversed to the above-described decryption process.

34 is a diagram illustrating an AES-CTR mode encryption process that can be applied to an embodiment of the present invention. 35 is a diagram illustrating an AES-CTR mode decryption process that can be applied to an embodiment of the present invention. FIG. 36 is a diagram illustrating a counter value in the AES-CTR mode that can be applied to an embodiment of the present invention. 37 is a diagram illustrating a process of processing a residual block in the AES-CTR mode encryption / decryption process. Hereinafter, with reference to FIGS. 34 to 37, a concrete method of encrypting and decrypting to implement the reception restriction function according to an embodiment of the present invention will be described.

For example, AES (Advanced Encryption Standard) -CTR (CounTeR) -128 can be used as the encryption and decryption algorithm applied to the MH service for reception restriction. In this case, it is possible to perform the encryption at the IP level, the RTP level, and the raw level as shown in FIG. 34, and conversely, the IP level, the RTP level, the raw level Lt; / RTI >

However, when the AES-CTR-128 algorithm shown in FIGS. 34 and 35 is used, a first Counter value is required. In the present invention, the counter value is newly defined as shown in FIG.

The "type indicator" field shown in FIG. 36 indicates the type of the encrypted stream, the "system time" field indicates the system time of the superframe, and the "destination port number" And indicates the destination port number of the stream to which the packet is to be transmitted. Therefore, by using the counter value thus defined, the counter value of each data block of 16 bytes can be uniquely defined, and the efficiency can also be improved.

36 may be designed so as to correspond to the " type indicator " field of the MH-TP shown in FIG. 30. In this case, the " type indicator " Indicates that the MH-TP of the encrypted stream transmits signaling data. If the value of the " type indicator " field of FIG. 36 is '001', the MH-TP of the encrypted stream transmits the IP datagram .

Thus, according to one embodiment of the present invention, by using the type indicator of the MH-TP as the counter value used in the encryption and decryption algorithm (e.g., AES-CTR-128 algorithm, etc.) It is possible to set different counter values for the MH-TP that transmits the IP datagram and the MH-TP that transmits the IP datagram, and also the encryption and decryption algorithm operates according to the MH- There is an advantage to be able to design.

Meanwhile, according to an embodiment of the present invention, the encryption and decrypted data are divided into 128-bit blocks, and then encryption and decryption are performed. Therefore, as shown in FIG. 37, the last data block may not be 128 bits. In this case, from the value of the upper bit of the output output from the AES Encryption block, &Quot; is designed to be performed.

Figure 38 is a more specific view of an SMT including a control access descriptor according to an embodiment of the present invention. 39 is a diagram illustrating a structure of an RS frame including an MH service to which reception restriction is applied according to an embodiment of the present invention. 38 and 39, a process of processing a service to which reception restriction is applied in a mobile digital broadcasting environment will be described as an example.

The MH_CA_descriptors shown in FIG. 38 indicate the level to which the reception restriction is applied, and the control data necessary for the decryption process. The MH_CA_Descriptor_1 provides information on the ECM to which the reception restriction is applied only for the service whose target IP address is 200.200.200.5 out of services for which the ensemble ID is 1 and the major channel number and the minor channel number are 30-5.

MH_CA_Descriptor_2 provides information on the ECM to which the reception restriction is applied for the entire service whose ensemble ID is 1 and whose major channel number and minor channel number are 30-6. That is, information on the ECM to which the reception restriction is applied is provided for the services having the target IP addresses 200.200.200.6 and 200.200.200.7.

Meanwhile, as described above, the digital broadcast receiver according to the embodiment of the present invention uses the " encrypt_level_flag " of the MH_CA_Descriptor to determine whether the service to which the reception restriction is applied is at a low level, an RTP level, or an IP level . At this time, the digital broadcasting receiver needs control data and the like for obtaining the right to allow access to the services to which reception restriction is applied. That is, the digital broadcasting receiver can obtain the EMM information for obtaining the reception right for all services whose ensemble ID is '1' by using the fact that the value of ECM_EMM_flag of MH_CA_Descriptor_3 is '1'.

On the other hand, FIG. 39 shows the structure of the RS frame including the services whose ensemble ID is '1' and reception restriction is applied, in the SMT shown in FIG.

When Service 2 is selected in the RS frame structure of FIG. 39, the digital broadcast receiver according to the embodiment of the present invention can confirm that there is an MH_CA_descriptor related to the service 2 among the SMT of FIG. That is, the digital broadcasting receiver can confirm that the reception restriction is applied in the case of the service 2.

At this time, the digital broadcasting receiver receives a Destination IP address of '200.200.200.9' and '1000' of ECM (including Cotrol Word) required to remove the reception restriction function of Service 2 from MH_CA_Descriptor_2 related to Service 2, It is confirmed that the packet is transmitted using the destination port number of the destination. In addition, in the digital broadcast receiver, the EMM of the control data necessary for obtaining the right for the encrypted service 2 is transmitted using the destination IP address of '200.200.200.10' and the destination port number of '1000' . Therefore, the digital broadcasting receiver can remove the reception restriction function for the encrypted service 2 by using the checked ECM, EMM, or the like.

40 is a flowchart illustrating a method of controlling a digital broadcasting receiver according to an embodiment of the present invention. Hereinafter, a method of controlling a digital broadcast receiver according to an embodiment of the present invention will be described with reference to FIG. For reference, Figs. 40 and 45 relate to the method invention, and can be interpreted by applying supplementary explanations to the above-mentioned object invention.

A digital broadcast receiver according to an embodiment of the present invention decodes an RS frame (S4000). The digital broadcasting receiver extracts the decoding result SMT (S4001), parses the extracted SMT, and checks information necessary to remove the reception limiting function (S4002).

The digital broadcasting receiver extracts MH-TP according to the SMT to extract control data and the like (S4003). The digital broadcast receiver parses the MH-TP header (S4004), and confirms the value of the Type_Indicator field (S4005). If the field value is '001', the control access descriptor of the SMT (however, this is not shown in FIG. 28A). If the field value is '0001', the signaling data is processed (S4017) Encrypt_level_flag 'field value of the MH_CA_Descriptor shown in FIG. 4B) (S4006).

If the 'encrypt_level_flag' field value is '001' (S4006), the digital broadcasting receiver decrypts the encrypted mobile service data at the IP level (S4007). That is, it decrypts the IP datagram.

If the 'encrypt_level_flag' field value is not '001' (S4006), the digital broadcasting receiver processes the IP datagram (S4008) and processes the UDP datagram (S4009). In addition, the digital broadcast receiver determines whether the data transmitted from a digital broadcast transmitter or the like is a file or a stream (S4010). If it is determined in operation S4010 that the stream is a stream, the digital broadcast receiver determines an 'encrypt_level_flag' field value in operation S4012. On the other hand, if the determination result is the file S4010, the digital broadcast receiver processes the file (S4011).

If the 'encrypt_level_flag' field value is '010' (S4012), the digital broadcasting receiver decrypts the encrypted mobile service data at the RTP level (S4013). That is, the stream data is decrypted.

If the 'encrypt_level_flag' field value is not '010', the digital broadcasting receiver processes the stream (S4014) and determines the 'encrypt_level_flag' field value (S4016). If the 'encrypt_level_flag' field value is '011' (S4016), the digital broadcasting receiver decrypts the introduced mobile service data at a low level (S4015). That is, the row data is decrypted.

On the other hand, if the 'encrypt_level_flag' field value is not '011' as a result of the determination (S4016), control is performed so that the application is processed according to the format (S4018). The format may be, for example, a file, stream, signaling data, or the like.

In addition, it is also possible that the step S4010 or S4011 of determining whether the data to be transmitted is a file or a stream is deleted, and the step S4012 may be continued after the step S4009.

FIG. 41 is a table defining the CCI according to an embodiment of the present invention, FIG. 42 is a diagram illustrating the EMI shown in FIG. 41, FIG. 43 is a diagram illustrating the APS shown in FIG. 41, 44 is a diagram illustrating the CIT shown in FIG. 41 to 44, a method for securely setting copy protection when transmitting an MH service with a reception restriction to an external interface according to an embodiment of the present invention will be described.

As described above, the MH service to which the reception restriction is applied is transmitted to the digital broadcasting receiver, and only the authorized user or the digital broadcasting receiver can use the MH service. However, in order to prevent an illegal copying problem that occurs when the MH service is transmitted through an external interface, an embodiment of the present invention intends to define new signaling data.

The signaling data for preventing illegal copying as described above can be illustrated as shown in FIG. For example, the signaling data may be CCI (Copy Control Information) composed of 8 bits.

The EMI (Encryption Mode Indicator) of the CCI field shown in FIG. 41 may be configured as shown in FIG. 42. The EMI is information for copy control of digital data, and controls the replication authority for the output of the digital data .

On the other hand, among the CCI fields shown in FIG. 41, the APS (Analog Protection System) can be configured as shown in FIG. 43, and the APS is used to control the replication authority for the output of the analog data.

41, the CIT may be configured as shown in FIG. 44, and the CIT may control the replication authority for the image of the High Definition Analog Component Output (High Definition Analog Component Output) .

The CCI is not required to be transmitted, but the digital broadcasting receiver must check whether the received CCI is legitimate data transmitted by the service provider. Therefore, according to an embodiment of the present invention, the CCI may be included in the ECM and transmitted, or may be included in the descriptor of the SMT and transmitted, or may be transmitted using a secure method such as a PKI (Public Key Infrastructure) And may transmit the CCI.

For example, according to an embodiment of the present invention, the control access descriptor shown in FIG. 28 includes an EMI defining a replication authority for outputting digital data, an APS defining replication authority for outputting analog data, You can additionally define a CIT that defines the replication rights for the output of high-quality analog component data.

In this case, when the service having the CCI is outputted to various external interfaces such as IEEE-1394, USB, DVI, HDMI, and components (RGB, YPbPr), the copy protection handler 2663 transmits the CCI Defined), it is possible to output a stream or service for which a replication right is set according to the type of data to the external interface. For reference, the copy protection handler 2663 may be referred to as a transfer unit.

In addition, when the CCI is stored in the secure signaling DB 2662 or other storage unit and the service is to be output to the external interface, the digital broadcast receiver according to an embodiment of the present invention transmits the CCI Can be used.

45 is a flowchart illustrating a method of controlling a digital broadcasting receiver and a digital broadcasting transmitter according to an embodiment of the present invention. Hereinafter, a method of controlling a digital broadcasting receiver and a digital broadcasting transmitter according to an embodiment of the present invention will be described in detail with reference to FIG.

A digital broadcast transmitter according to an embodiment of the present invention generates a broadcast signal including a control access descriptor indicating whether or not mobile service data has been encrypted (S4501), and includes the generated control access descriptor The broadcast signal is transmitted to the digital broadcast receiver (S4502).

However, the control access descriptor includes information for identifying each level in which the mobile service data is encrypted and control data used in decrypting the encrypted mobile service data. do. Further, the control access descriptor may be configured as shown in FIG. 28 and may be referred to as MH_CA_Descriptor.

A digital broadcast receiver according to an embodiment of the present invention receives a broadcast signal in which mobile service data and main service data are multiplexed (S4503), and extracts TPC / FIC signaling information from the received data group in the mobile service data (S4504).

In addition, the digital broadcast receiver obtains a first program table describing an ensemble virtual channel information and a service, which is a virtual channel group of the received mobile service data, using the extracted FIC signaling information (S4505). Next, the digital broadcast receiver detects a control access descriptor indicating whether the mobile service data is encrypted using the obtained first program table (S4506). However, the control access descriptor may be more specifically, for example, a descriptor which separately defines each level in which the mobile service data is encrypted.

The digital broadcast receiver controls the encrypted mobile service data to be decrypted using the detected information of the control access descriptor (S4507). However, in step S4507, more specifically, for example, the encrypted mobile service data may be controlled to be decrypted corresponding to the encrypted level.

However, for reference, the first program table may correspond to the SMT shown in FIG. 17 or 27, and the control access descriptor may correspond to the MH_CA_Descriptor shown in FIG.

Accordingly, the step S4507 may include the steps of: determining the encrypted level of the mobile service data using, for example, the MH_CA_Descriptor of the SMT; and using the information on the control data, And decrypting the crypted mobile service data.

As described above, according to an embodiment of the present invention, it is possible to easily decrypt the mobile service data encrypted at the low level, the RTP level, and the IP level regardless of the position of the level in the mobile digital broadcasting environment.

In addition, according to an embodiment of the present invention, mobile service data that does not require reception restriction is designed to bypass the MH encrypt / decrypt layer, so that compatibility with existing systems may be maintained.

According to the embodiment of the present invention, illegal copying can be prevented even when the mobile service data is output to the external interface.

The method inventions according to the present invention can all be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions recorded on the medium may be those specially designed and constructed for the present invention or may be available to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. This is possible.

Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined by the equivalents of the claims, as well as the claims.

100: MH Baseband Processor
200: MH Management Processor
300: MH Presentation Processor

Claims (10)

Generating broadcast service including broadcast service data, decryption related information of the broadcast service, and signaling information for the broadcast service;
Generating a packet including at least one of the broadcast service data, the decryption related information, and the signaling information; And
Transmitting the generated packet,
Wherein the signaling information includes first information indicating whether a reception restriction is applied to at least one component constituting the broadcast service, and second information for receiving a component to which reception restriction is applied. The method according to claim 1,
And the second information includes location information on which the decryption related information is transmitted. The method according to claim 1,
And the second information includes information indicating the type of the decryption related information. The method according to claim 1,
Wherein the packet includes a header and a payload, the header includes information for identifying a start position of a new packet in the payload, and the payload includes the broadcast service data. The method according to claim 1,
Wherein the signaling information further includes a provider identification information for identifying a provider that provides the broadcast service. Receiving a packet including at least one of broadcast service data of a broadcast service, decryption related information of the broadcast service, and signaling information of the broadcast service; And
Parsing at least one of the broadcast service data, the decryption related information, and the signaling information in the received packet;
Wherein the signaling information includes first information indicating whether a reception restriction is applied to at least one component constituting the broadcast service, and second information for receiving a component to which reception restriction is applied. The method according to claim 6,
And the second information includes location information on which the decryption related information is transmitted. The method according to claim 6,
And the second information includes information indicating a type of the decryption related information. The method according to claim 6,
Wherein the packet includes a header and a payload, the header includes information for identifying a start position of a new packet in the payload, and the payload includes the broadcast service data. The method according to claim 6,
Wherein the signaling information further includes a provider identification information for identifying a provider providing the broadcast service.

Images