Patent Publication Number: US-2016227271-A1

Title: Broadcast transmission device and operating method thereof, and broadcast reception device and operating method thereof

Description:
TECHNICAL FIELD 
     The present disclosure relates to a broadcast transmission device and an operating method thereof, and a broadcast reception device and an operating method thereof. 
     BACKGROUND ART 
     Unlike analog broadcast, one broadcast service may include a plurality of media components in digital broadcast. Accordingly, user may selectively view a plurality of media for one broadcast service. For example, a user may select one of English, Chinese, and Japanese dubbing voices for one movie. Additionally, a user may select one of English, Chinese, and Japanese subtitles for one drama and may then view the drama. 
     Additionally, recently, an adaptive streaming service transmitting different qualities of a media component according to a communication environment receives great attentions. Accordingly, a user may select one of various qualities of media components including the same content according to a communication environment and may then view the selected one. 
     Furthermore, a multi view service displaying a plurality of media components on one screen simultaneously is provided. Accordingly, a user may view a plurality of images or data broadcasts through one screen. For example, a user may view a game of another stadium while viewing a baseball game through an additional Picture In Picture (PIP) screen. 
     In such a way, as broadcast services including a plurality of media components are diversified and increased, broadcast transmission/reception devices efficiently transmitting/receiving media components are required. 
     DISCLOSURE OF INVENTION 
     Technical Problem 
     Embodiments provide a broadcast transmission device and an operating method thereof for efficiently transmitting/receiving a plurality of media components. Embodiments also provide a broadcast reception device and an operating method thereof. 
     Solution to Problem 
     Embodiments also provide a broadcast transmission device and an operating method thereof for efficiently transmitting information on a plurality of media components and transmission paths. Embodiments also provide a broadcast reception device and an operating method thereof. 
     In one embodiment, a broadcast reception device includes: a broadcast reception unit receiving a broadcast signal; and a control unit obtaining a broadcast service signaling table that signals a broadcast service on the basis of the broadcast signal and obtaining information on a first media component that the broadcasts service includes on the basis of the signaling table. 
     The first media component may include at least one among a composite component, that is, a collection of a plurality of media components necessary for playing one scene, and an adaptive component, that is, a collection of a plurality of media component that are replaceable with each other and representing the same scene. 
     The adaptive media component may be a collection of a plurality of media components obtained by encoding the same content with different qualities. 
     The composite component may be a collection of a plurality of media components configuring a 3D image. 
     The signaling information table may include a broadcast service transmission path signaling table signaling a transmission path of the first media component; and the control unit may receive the media component on the basis of the broadcast service transmission path signaling table. 
     The broadcast service may further include a second media component; and the broadcast service transmission path signaling table may signal a transmission path of the first media component received through a broadcast network and the second media component received through an internet network. 
     The control unit may obtain program information signaling a property of a program that the broadcast service include on the basis of the broadcast signal, and may obtain information on a media component that the program includes on the basis of the program information. 
     The control unit may obtain segment information signaling a property of a segment representing a time interval configuring the program on the basis of the broadcast signal. 
     The segment may include a show segment broadcasting a feature content of a program and an interstitial segment broadcasting a content not relating to the feature content between the feature content of the program. 
     The property of the segment may include a unique identifier for identifying the segment, a list of media components played during a time interval of the segment, a start time and duration of the segment, a type of the segment, a targeting/personalization property, and a contents advisory rating. 
     The control unit may determine whether to play the segment on the basis of the property of the segment. 
     The control unit may obtain segment targeting set information including targeting properties of a plurality of segments having the same time and duration on the basis of the, broadcast signal and may determine whether to play the segment on the basis of the segment targeting set information. 
     In another embodiment, a method of operating a broadcast reception device includes: receiving a broadcast signal; obtaining a broadcast service signaling table signaling a broadcast service on the basis of the broadcast signal; and obtaining information on a first media component that the broadcasts service includes on the basis of the signaling table. 
     The first media component may include at least one among a composite component, that is, a collection of a plurality of media components necessary for playing one scene, and an adaptive component, that is, a collection of a plurality of media component that are replaceable with each other and representing the same scene. 
     The adaptive media component may be a collection of a plurality of media components obtained by encoding the same content with different qualities. 
     The composite component may be a collection of a plurality of media components configuring a 3D image. 
     The signaling information table may include a broadcast service transmission path signaling table signaling a transmission path of the first media component. The method may further include receiving the media component on the basis of the broadcast service transmission path signaling table. 
     The broadcast service may further include a second media component; and the broadcast service transmission path signaling table signals a transmission path of the first media component received through a broadcast network and the second media component received through an internet network. 
     The method may further include: obtaining program information signaling a property of a program that the broadcast service include on the basis of the broadcast signal; and obtaining information on a media component that the program includes on the basis of the program information. 
     In further another embodiment, a broadcast transmission device includes: a control unit obtaining media component information that a broadcast service includes and generating a broadcast service signaling table signaling the broadcast service on the basis of the media component information; and a transmission unit transmitting a broadcast signal including the broadcast service signaling table. 
     Advantageous Effects of Invention 
     According to an embodiment of the present invention, provided are a broadcast transmission device, an operation method thereof, a broadcast reception device, and an operation method thereof in order to efficiently transmit/receive a plurality of media components. 
     Especially, according to an embodiment of the present invention, provided are a broadcast transmission device, an operation method thereof, a broadcast reception device, and an operation method thereof in order to efficiently broadcast information on a plurality of media components and a transmission path. 
    
    
     
       BRIEF DESCRIPTION OF DRAWINGS 
         FIG. 1  illustrates a structure of an apparatus for transmitting broadcast signals for future broadcast services according to an embodiment of the present invention. 
         FIG. 2  illustrates an input formatting module according to one embodiment of the present invention. 
         FIG. 3  illustrates an input formatting block according to another embodiment of the present invention. 
         FIG. 4  illustrates an input formatting block according to another embodiment of the present invention. 
         FIG. 5  illustrates a BICM block according to an embodiment of the present invention. 
         FIG. 6  illustrates a BICM block according to another embodiment of the present invention. 
         FIG. 7  illustrates a frame building block according to one embodiment of the present invention. 
         FIG. 8  illustrates an OFMD generation block according to an embodiment of the present invention. 
         FIG. 9  illustrates a structure of an apparatus for receiving broadcast signals for future broadcast services according to an embodiment of the present invention. 
         FIG. 10  illustrates a frame structure according to an embodiment of the present invention. 
         FIG. 11  illustrates a signaling hierarchy structure of the frame according to an embodiment of the present invention. 
         FIG. 12  illustrates preamble signaling data according to an embodiment of the present invention. 
         FIG. 13  illustrates PLS1 data according to an embodiment of the present invention. 
         FIG. 14  illustrates PLS2 data according to an embodiment of the present invention. 
         FIG. 15  illustrates PLS2 data according to another embodiment of the present invention. 
         FIG. 16  illustrates a logical structure of a frame according to an embodiment of the present invention. 
         FIG. 17  illustrates PLS mapping according to an embodiment of the present invention. 
         FIG. 18  illustrates EAC mapping according to an embodiment of the present invention. 
         FIG. 19  illustrates FIC mapping according to an embodiment of the present invention. 
         FIG. 20  illustrates a type of DP according to an embodiment of the present invention. 
         FIG. 21  illustrates DP mapping according to an embodiment of the present invention. 
         FIG. 22  illustrates an FEC structure according to an embodiment of the present invention. 
         FIG. 23  illustrates a bit interleaving according to an embodiment of the present invention. 
         FIG. 24  illustrates a cell-word demultiplexing according to an embodiment of the present invention. 
         FIG. 25  illustrates a time interleaving according to an embodiment of the present invention. 
         FIG. 26  illustrates the basic operation of a twisted row-column block interleaver according to an embodiment of the present invention. 
         FIG. 27  illustrates an operation of a twisted row-column block interleaver according to another embodiment of the present invention. 
         FIG. 28  illustrates a diagonal-wise reading pattern of a twisted row-column block interleaver according to an embodiment of the present invention. 
         FIG. 29  illustrates interleaved XFECBLOCKs from each interleaving array according to an embodiment of the present invention. 
         FIG. 30  is a view of a protocol stack for supporting a broadcast service according to an embodiment of the present invention. 
         FIG. 31  is a view illustrating a broadcast transmission frame according to an embodiment of the present invention. 
         FIG. 32  is a view of a broadcast transmission frame according to another embodiment of the present invention. 
         FIG. 33  is a view illustrating a structure of a transport packet transmitting a broadcast service according to an embodiment of the present invention. 
         FIG. 34  is a view illustrating a value that a network_protocol field has in a transport packet transmitting a broadcast service according to an embodiment of the present invention. 
         FIG. 35  is a view illustrating a configuration of a broadcast reception device according to an embodiment of the present invention. 
         FIG. 36  is a view that a broadcast service signaling table and broadcast service transmission path signaling information signal broadcast service and a broadcast service transmission path. 
         FIG. 37  is a view illustrating a broadcast service signaling table according to an embodiment of the present invention. 
         FIG. 38  is a view illustrating a value that a service_category field has in a broadcast service signaling table according to an embodiment of the present invention. 
         FIG. 39  is a view of a broadcast service signaling table according to another embodiment of the present invention. 
         FIG. 40  is a view of a stream identifier descriptor according to another embodiment of the present invention. 
         FIG. 41  is a view illustrating an operation when a broadcast transmission device transmits a broadcast service signaling table according to an embodiment of the present invention. 
         FIG. 42  is a view illustrating an operation when a broadcast reception device receives a broadcast service signaling table according to an embodiment of the present invention. 
         FIG. 43  is a view illustrating broadcast service transmission path signaling information according to an embodiment of the present invention. 
         FIG. 44  is a view illustrating a value that a delivery_network_type field has in broadcast service transmission path signaling information according to an embodiment of the present invention. 
         FIG. 45  is a view that broadcast service transmission path signaling information signals the transmission of a broadcast service through IP stream according to an embodiment of the present invention. 
         FIG. 46  is a view that broadcast service transmission path signaling information signals the transmission of a broadcast service through an IP stream of another broadcaster according to an embodiment of the present invention. 
         FIG. 47  is a view that broadcast service transmission path signaling information signals the transmission of a broadcast service through a FLUTE session according to an embodiment of the present invention. 
         FIG. 48  is a view that broadcast service transmission path signaling information signals the transmission of a broadcast service through a FLUTE protocol of another broadcaster according to an embodiment of the present invention. 
         FIG. 49  is a view that broadcast service transmission path signaling information signals the transmission of a broadcast service through MPEG-2 TS stream of another broadcaster according to an embodiment of the present invention. 
         FIG. 50  is a view that broadcast service transmission path signaling information signals the transmission of a broadcast service through a packet based stream of another broadcaster, according to an embodiment of the present invention. 
         FIG. 51  is a view that broadcast service transmission path signaling information signals the transmission of a broadcast service through a packet based stream of an IP based broadcast network according to an embodiment of the present invention. 
         FIG. 52  is a view that broadcast service transmission path signaling information signals a broadcast service through URL according to an embodiment of the present invention. 
         FIG. 53  is a view when a broadcast transmission device transmits broadcast service transmission path signaling information according to an embodiment of the present invention. 
         FIG. 54  is a view when a broadcast reception device receives a broadcast service on the basis of a broadcast service transmission path according to an embodiment of the present invention. 
         FIG. 55  is a view illustrating media component signaling information signaling a media component according to an embodiment of the present invention. 
         FIG. 56  is a view illustrating a value that a component_type field in media component signaling information according to an embodiment of the present invention. 
         FIG. 57  is a view illustrating a component_data field in media component signaling information according to an embodiment of the present invention. 
         FIG. 58  is a view illustrating a component_data field in media component signaling information according to another embodiment of the present invention. 
         FIG. 59  is a view illustrating the type of a media component according to an embodiment of the present invention. 
         FIG. 60  is a view illustrating a configuration of a complex component according to an embodiment of the present invention. 
         FIG. 61  is a view illustrating a complex video component according to an embodiment of the present invention. 
         FIG. 62  is a view illustrating a complex audio component according to an embodiment of the present invention. 
         FIG. 63  is a view illustrating a media component configuration of an audio service according to an embodiment of the present invention. 
         FIG. 64  is a view illustrating a configuration of a broadcast service including both audio and video according to an embodiment of the present invention. 
         FIG. 65  is a view illustrating a configuration of a user request content service according to an embodiment of the present invention. 
         FIG. 66  is a view illustrating a configuration of a standalone data service according to an embodiment of the present invention. 
         FIG. 67  is a view illustrating graphic icon information according to an embodiment of the present invention. 
         FIG. 68  is a view illustrating a value that an icon_transport_mode field of graphic icon information has according to an embodiment of the present invention. 
         FIG. 69  is a view illustrating a value that a coordinate_system field of graphic icon information has according to an embodiment of the present invention. 
         FIG. 70  is a view illustrating media component list information according to an embodiment of the present invention. 
         FIG. 71  is a view illustrating media component information according to an embodiment of the present invention. 
         FIG. 72  is a view illustrating complex component information according to an embodiment of the present invention. 
         FIG. 73  is a view illustrating a descriptor including complex component information according to an embodiment of the present invention. 
         FIG. 74  is a view illustrating related component list information according to an embodiment of the present invention. 
         FIG. 75  is a view when a media component or a broadcast service is mapped through URI in a broadcast service signaling table according to an embodiment of the present invention. 
         FIG. 76  is a view illustrating targeting criteria information signaling the targeting criteria of a broadcast service or a media component. 
         FIG. 77  is a view illustrating text information for describing a broadcast service or a media component. 
         FIG. 78  is a view illustrating program information according to an embodiment of the present invention. 
         FIG. 79  is a view illustrating a program information block according to an embodiment of the present invention. 
         FIG. 80  is a view illustrating a program information block according to another embodiment of the present invention. 
         FIG. 81  is a view when a broadcast service is divided into a plurality of segments. 
         FIG. 82  is a view illustrating segment information program information according to an embodiment of the present invention. 
         FIG. 83  is a view illustrating a segment information block according to an embodiment of the present invention. 
         FIG. 84  is a view illustrating a targeting segment set information according to an embodiment of the present invention. 
         FIG. 85  is a view when a broadcast transmission device transmits broadcast signal including at least one among program information and segment information according to an embodiment of the present invention. 
         FIG. 86  is a view when a broadcast reception device receives broadcast signal including at least one among program information and segment information according to an embodiment of the present invention. 
     
    
    
     BEST MODE FOR CARRYING OUT THE INVENTION 
     Hereinafter, embodiments of the present invention will be described in more detail with reference to the accompanying drawings, in order to allow those skilled in the art to easily realize the present invention. The present invention may be realized in different forms, and is not limited to the embodiments described herein. Moreover, detailed descriptions related to well-known functions or configurations will be ruled out in order not to unnecessarily obscure subject matters of the present invention. Like reference numerals refer to like elements throughout. 
     In additional, when a part “includes” some components, this means that the part does not exclude other components unless stated specifically and further includes other components. 
     Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. The detailed description, which will be given below with reference to the accompanying drawings, is intended to explain exemplary embodiments of the present invention, rather than to show the only embodiments that can be implemented according to the present invention. The following detailed description includes specific details in order to provide a thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention may be practiced without such specific details. 
     Although most terms used in the present invention have been selected from general ones widely used in the art, some terms have been arbitrarily selected by the applicant and their meanings are explained in detail in the following description as needed. Thus, the present invention should be understood based upon the intended meanings of the terms rather than their simple names or meanings. 
     The present invention provides apparatuses and methods for transmitting and receiving broadcast signals for future broadcast services. Future broadcast services according to an embodiment of the present invention include a terrestrial broadcast service, a mobile broadcast service, a UHDTV service, etc. 
     The apparatuses and methods for transmitting according to an embodiment of the present invention may be categorized into a base profile for the terrestrial broadcast service, a handheld profile for the mobile broadcast service and an advanced profile for the UHDTV service. In this case, the base profile can be used as a profile for both the terrestrial broadcast service and the mobile broadcast service. That is, the base profile can be used to define a concept of a profile which includes the mobile profile. This can be changed according to intention of the designer. 
     The present invention may process broadcast signals for the future broadcast services through non-MIMO (Multiple Input Multiple Output) or MIMO according to one embodiment. A non-MIMO scheme according to an embodiment of the present invention may include a MISO (Multiple Input Single Output) scheme, a SISO (Single Input Single Output) scheme, etc. 
     While MISO or MIMO uses two antennas in the following for convenience of description, the present invention is applicable to systems using two or more antennas. 
     The present invention may defines three physical layer (PL) profiles (base, handheld and advanced profiles) each optimized to minimize receiver complexity while attaining the performance required for a particular use case. The physical layer (PHY) profiles are subsets of all configurations that a corresponding receiver should implement. 
     The three PHY profiles share most of the functional blocks but differ slightly in specific blocks and/or parameters. Additional PHY profiles can be defined in the future. For the system evolution, future profiles can also be multiplexed with the existing profiles in a single RF channel through a future extension frame (FEF). The details of each PHY profile are described below. 
     1. Base Profile 
     The base profile represents a main use case for fixed receiving devices that are usually connected to a roof-top antenna. The base profile also includes portable devices that could be transported to a place but belong to a relatively stationary reception category. Use of the base profile could be extended to handheld devices or even vehicular by some improved implementations, but those use cases are not expected for the base profile receiver operation. 
     Target SNR range of reception is from approximately 10 to 20 dB, which includes the 15 dB SNR reception capability of the existing broadcast system (e.g. ATSC A/53). The receiver complexity and power consumption is not as critical as in the battery-operated handheld devices, which will use the handheld profile. Key system parameters for the base profile are listed in below table 1. 
     
       
         
           
               
               
             
               
                 TABLE 1 
               
               
                   
               
             
            
               
                 LDPC codeword length 
                 16K, 64K bits 
               
               
                 Constellation size 
                 4~10 bpcu (bits per channel use) 
               
               
                 Time de-interleaving memory size 
                 ≦2 19  data cells 
               
               
                 Pilot patterns 
                 Pilot pattern for fixed reception 
               
               
                 FFT size 
                 16K, 32K points 
               
               
                   
               
            
           
         
       
     
     2. Handheld Profile 
     The handheld profile is designed for use in handheld and vehicular devices that operate with battery power. The devices can be moving with pedestrian or vehicle speed. The power consumption as well as the receiver complexity is very important for the implementation of the devices of the handheld profile. The target SNR range of the handheld profile is approximately 0 to 10 dB, but can be configured to reach below 0 dB when intended for deeper indoor reception. 
     In addition to low SNR capability, resilience to the Doppler Effect caused by receiver mobility is the most important performance attribute of the handheld profile. Key system parameters for the handheld profile are listed in the below table 2. 
     
       
         
           
               
               
               
             
               
                   
                 TABLE 2 
               
               
                   
                   
               
             
            
               
                   
                 LDPC codeword length 
                 16K bits 
               
               
                   
                 Constellation size 
                 2~8 bpcu 
               
               
                   
                 Time de-interleaving memory size 
                 ≦2 18  data cells 
               
               
                   
                 Pilot patterns 
                 Pilot patterns for mobile and 
               
               
                   
                   
                 indoor reception 
               
               
                   
                 FFT size 
                 8K, 16K points 
               
               
                   
                   
               
            
           
         
       
     
     3. Advanced Profile 
     The advanced profile provides highest channel capacity at the cost of more implementation complexity. This profile requires using MIMO transmission and reception, and UHDTV service is a target use case for which this profile is specifically designed. The increased capacity can also be used to allow an increased number of services in a given bandwidth, e.g., multiple SDTV or HDTV services. 
     The target SNR range of the advanced profile is approximately 20 to 30 dB. MIMO transmission may initially use existing elliptically-polarized transmission equipment, with extension to full-power cross-polarized transmission in the future. Key system parameters for the advanced profile are listed in below table 3. 
     
       
         
           
               
               
             
               
                 TABLE 3 
               
               
                   
               
             
            
               
                 LDPC codeword length 
                 16K, 64K bits 
               
               
                 Constellation size 
                 8~12 bpcu 
               
               
                 Time de-interleaving memory size 
                 ≦2 19  data cells 
               
               
                 Pilot patterns 
                 Pilot pattern for fixed reception 
               
               
                 FFT size 
                 16K, 32K points 
               
               
                   
               
            
           
         
       
     
     In this case, the base profile can be used as a profile for both the terrestrial broadcast service and the mobile broadcast service. That is, the base profile can be used to define a concept of a profile which includes the mobile profile. Also, the advanced profile can be divided advanced profile for a base profile with MIMO and advanced profile for a handheld profile with MIMO. Moreover, the three profiles can be changed according to intention of the designer. 
     The following terms and definitions may apply to the present invention. The following terms and definitions can be changed according to design. 
     auxiliary stream: sequence of cells carrying data of as yet undefined modulation and coding, which may be used for future extensions or as required by broadcasters or network operators 
     base data pipe: data pipe that carries service signaling data 
     baseband frame (or BBFRAME): set of K bch  bits which form the input to one FEC encoding process (BCH and LDPC encoding) 
     cell: modulation value that is carried by one carrier of the OFDM transmission 
     coded block: LDPC-encoded block of PLS1 data or one of the LDPC-encoded blocks of PLS2 data 
     data pipe: logical channel in the physical layer that carries service data or related metadata, which may carry one or multiple service(s) or service component(s). 
     data pipe unit: a basic unit for allocating data cells to a DP in a frame. 
     data symbol: OFDM symbol in a frame which is not a preamble symbol (the frame signaling symbol and frame edge symbol is included in the data symbol) 
     DP_ID: this 8-bit field identifies uniquely a DP within the system identified by the SYSTEM_ID 
     dummy cell: cell carrying a pseudo-random value used to fill the remaining capacity not used for PLS signaling, DPs or auxiliary streams 
     emergency alert channel: part of a frame that carries EAS information data 
     frame: physical layer time slot that starts with a preamble and ends with a frame edge symbol 
     frame repetition unit: a set of frames belonging to same or different physical layer profile including a FEF, which is repeated eight times in a super-frame 
     fast information channel: a logical channel in a frame that carries the mapping information between a service and the corresponding base DP 
     FECBLOCK: set of LDPC-encoded bits of a DP data 
     FFT size: nominal FFT size used for a particular mode, equal to the active symbol period T S  expressed in cycles of the elementary period T 
     frame signaling symbol: OFDM symbol with higher pilot density used at the start of a frame in certain combinations of FFT size, guard interval and scattered pilot pattern, which carries a part of the PLS data 
     frame edge symbol: OFDM symbol with higher pilot density used at the end of a frame in certain combinations of FFT size, guard interval and scattered pilot pattern 
     frame-group: the set of all the frames having the same PHY profile type in a super-frame. 
     future extension frame: physical layer time slot within the super-frame that could be used for future extension, which starts with a preamble 
     Futurecast UTB system: proposed physical layer broadcasting system, of which the input is one or more MPEG2-TS or IP or general stream(s) and of which the output is an RF signal 
     input stream: A stream of data for an ensemble of services delivered to the end users by the system. 
     normal data symbol: data symbol excluding the frame signaling symbol and the frame edge symbol 
     PHY profile: subset of all configurations that a corresponding receiver should implement 
     PLS: physical layer signaling data consisting of PLS1 and PLS2 
     PLS1: a first set of PLS data carried in the FSS symbols having a fixed size, coding and modulation, which carries basic information about the system as well as the parameters needed to decode the PLS2 
     NOTE: PLS1 data remains constant for the duration of a frame-group. 
     PLS2: a second set of PLS data transmitted in the FSS symbol, which carries more detailed PLS data about the system and the DPs 
     PLS2 dynamic data: PLS2 data that may dynamically change frame-by-frame 
     PLS2 static data: PLS2 data that remains static for the duration of a frame-group 
     preamble signaling data: signaling data carried by the preamble symbol and used to identify the basic mode of the system 
     preamble symbol: fixed-length pilot symbol that carries basic PLS data and is located in the beginning of a frame 
     NOTE: The preamble symbol is mainly used for fast initial band scan to detect the system signal, its timing, frequency offset, and FFT-size. 
     reserved for future use: not defined by the present document but may be defined in future 
     super-frame: set of eight frame repetition units 
     time interleaving block (TI block): set of cells within which time interleaving is carried out, corresponding to one use of the time interleaver memory 
     TI group: unit over which dynamic capacity allocation for a particular DP is carried out, made up of an integer, dynamically varying number of XFECBLOCKs. 
     NOTE: The TI group may be mapped directly to one frame or may be mapped to multiple frames. It may contain one or more TI blocks. 
     Type 1 DP: DP of a frame where all DPs are mapped into the frame in TDM fashion 
     Type 2 DP: DP of a frame where all DPs are mapped into the frame in FDM fashion 
     XFECBLOCK: set of N cells  cells carrying all the bits of one LDPC FECBLOCK 
       FIG. 1  illustrates a structure of an apparatus for transmitting broadcast signals for future broadcast services according to an embodiment of the present invention. 
     The apparatus for transmitting broadcast signals for future broadcast services according to an embodiment of the present invention can include an input formatting block  1000 , a BICM (Bit interleaved coding &amp; modulation) block  1010 , a frame structure block  1020 , an OFDM (Orthogonal Frequency Division Multiplexing) generation block  1030  and a signaling generation block  1040 . A description will be given of the operation of each module of the apparatus for transmitting broadcast signals. 
     IP stream/packets and MPEG2-TS are the main input formats, other stream types are handled as General Streams. In addition to these data inputs, Management Information is input to control the scheduling and allocation of the corresponding bandwidth for each input stream. One or multiple TS stream(s), IP stream(s) and/or General Stream(s) inputs are simultaneously allowed. 
     The input formatting block  1000  can demultiplex each input stream into one or multiple data pipe(s), to each of which an independent coding and modulation is applied. The data pipe (DP) is the basic unit for robustness control, thereby affecting quality-of-service (QoS). One or multiple service(s) or service component(s) can be carried by a single DP. Details of operations of the input formatting block  1000  will be described later. 
     The data pipe is a logical channel in the physical layer that carries service data or related metadata, which may carry one or multiple service(s) or service component(s). 
     Also, the data pipe unit: a basic unit for allocating data cells to a DP in a frame. 
     In the BICM block  1010 , parity data is added for error correction and the encoded bit streams are mapped to complex-value constellation symbols. The symbols are interleaved across a specific interleaving depth that is used for the corresponding DP. For the advanced profile, MIMO encoding is performed in the BICM block  1010  and the additional data path is added at the output for MIMO transmission. Details of operations of the BICM block  1010  will be described later. 
     The Frame Building block  1020  can map the data cells of the input DPs into the OFDM symbols within a frame. After mapping, the frequency interleaving is used for frequency-domain diversity, especially to combat frequency-selective fading channels. Details of operations of the Frame Building block  1020  will be described later. 
     After inserting a preamble at the beginning of each frame, the OFDM Generation block  1030  can apply conventional OFDM modulation having a cyclic prefix as guard interval. For antenna space diversity, a distributed MISO scheme is applied across the transmitters. In addition, a Peak-to-Average Power Reduction (PAPR) scheme is performed in the time domain. For flexible network planning, this proposal provides a set of various FFT sizes, guard interval lengths and corresponding pilot patterns. Details of operations of the OFDM Generation block  1030  will be described later. 
     The Signaling Generation block  1040  can create physical layer signaling information used for the operation of each functional block. This signaling information is also transmitted so that the services of interest are properly recovered at the receiver side. Details of operations of the Signaling Generation block  1040  will be described later. 
       FIGS. 2, 3 and 4  illustrate the input formatting block  1000  according to embodiments of the present invention. A description will be given of each figure. 
       FIG. 2  illustrates an input formatting block according to one embodiment of the present invention.  FIG. 2  shows an input formatting module when the input signal is a single input stream. 
     The input formatting block illustrated in  FIG. 2  corresponds to an embodiment of the input formatting block  1000  described with reference to  FIG. 1 . 
     The input to the physical layer may be composed of one or multiple data streams. Each data stream is carried by one DP. The mode adaptation modules slice the incoming data stream into data fields of the baseband frame (BBF). The system supports three types of input data streams: MPEG2-TS, Internet protocol (IP) and Generic stream (GS). MPEG2-TS is characterized by fixed length (188 byte) packets with the first byte being a sync-byte (0×47). An IP stream is composed of variable length IP datagram packets, as signaled within IP packet headers. The system supports both IPv4 and IPv6 for the IP stream. GS may be composed of variable length packets or constant length packets, signaled within encapsulation packet headers. 
     (a) shows a mode adaptation block  2000  and a stream adaptation  2010  for signal DP and (b) shows a PLS generation block  2020  and a PLS scrambler  2030  for generating and processing PLS data. A description will be given of the operation of each block. 
     The Input Stream Splitter splits the input TS, IP, GS streams into multiple service or service component (audio, video, etc.) streams. The mode adaptation module  2010  is comprised of a CRC Encoder, BB (baseband) Frame Slicer, and BB Frame Header Insertion block. 
     The CRC Encoder provides three kinds of CRC encoding for error detection at the user packet (UP) level, i.e., CRC-8, CRC-16, and CRC-32. The computed CRC bytes are appended after the UP. CRC-8 is used for TS stream and CRC-32 for IP stream. If the GS stream doesn&#39;t provide the CRC encoding, the proposed CRC encoding should be applied. 
     BB Frame Slicer maps the input into an internal logical-bit format. The first received bit is defined to be the MSB. The BB Frame Slicer allocates a number of input bits equal to the available data field capacity. To allocate a number of input bits equal to the BBF payload, the UP packet stream is sliced to fit the data field of BBF. 
     BB Frame Header Insertion block can insert fixed length BBF header of 2 bytes is inserted in front of the BB Frame. The BBF header is composed of STUFFI (1 bit), SYNCD (13 bits), and RFU (2 bits). In addition to the fixed 2-Byte BBF header, BBF can have an extension field (1 or 3 bytes) at the end of the 2-byte BBF header. 
     The stream adaptation  2010  is comprised of stuffing insertion block and BB scrambler. 
     The stuffing insertion block can insert stuffing field into a payload of a BB frame. If the input data to the stream adaptation is sufficient to fill a BB-Frame, STUFFI is set to ‘0’ and the BBF has no stuffing field. Otherwise STUFFI is set to ‘1’ and the stuffing field is inserted immediately after the BBF header. The stuffing field comprises two bytes of the stuffing field header and a variable size of stuffing data. 
     The BB scrambler scrambles complete BBF for energy dispersal. The scrambling sequence is synchronous with the BBF. The scrambling sequence is generated by the feed-back shift register. 
     The PLS generation block  2020  can generate physical layer signaling (PLS) data. The PLS provides the receiver with a means to access physical layer DPs. The PLS data consists of PLS1 data and PLS2 data. 
     The PLS1 data is a first set of PLS data carried in the FSS symbols in the frame having a fixed size, coding and modulation, which carries basic information about the system as well as the parameters needed to decode the PLS2 data. The PLS1 data provides basic transmission parameters including parameters required to enable the reception and decoding of the PLS2 data. Also, the PLS1 data remains constant for the duration of a frame-group. 
     The PLS2 data is a second set of PLS data transmitted in the FSS symbol, which carries more detailed PLS data about the system and the DPs. The PLS2 contains parameters that provide sufficient information for the receiver to decode the desired DP. The PLS2 signaling further consists of two types of parameters, PLS2 Static data (PLS2-STAT data) and PLS2 dynamic data (PLS2-DYN data). The PLS2 Static data is PLS2 data that remains static for the duration of a frame-group and the PLS2 dynamic data is PLS2 data that may dynamically change frame-by-frame. 
     Details of the PLS data will be described later. 
     The PLS scrambler  2030  can scramble the generated PLS data for energy dispersal. 
     The above-described blocks may be omitted or replaced by blocks having similar or identical functions. 
       FIG. 3  illustrates an input formatting block according to another embodiment of the present invention. 
     The input formatting block illustrated in  FIG. 3  corresponds to an embodiment of the input formatting block  1000  described with reference to  FIG. 1 . 
       FIG. 3  shows a mode adaptation block of the input formatting block when the input signal corresponds to multiple input streams. 
     The mode adaptation block of the input formatting block for processing the multiple input streams can independently process the multiple input streams. 
     Referring to  FIG. 3 , the mode adaptation block for respectively processing the multiple input streams can include an input stream splitter  3000 , an input stream synchronizer  3010 , a compensating delay block  3020 , a null packet deletion block  3030 , a head compression block  3040 , a CRC encoder  3050 , a BB frame slicer  3060  and a BB header insertion block  3070 . Description will be given of each block of the mode adaptation block. 
     Operations of the CRC encoder  3050 , BB frame slicer  3060  and BB header insertion block  3070  correspond to those of the CRC encoder, BB frame slicer and BB header insertion block described with reference to  FIG. 2  and thus description thereof is omitted. 
     The input stream splitter  3000  can split the input TS, IP, GS streams into multiple service or service component (audio, video, etc.) streams. 
     The input stream synchronizer  3010  may be referred as ISSY. The ISSY can provide suitable means to guarantee Constant Bit Rate (CBR) and constant end-to-end transmission delay for any input data format. The ISSY is always used for the case of multiple DPs carrying TS, and optionally used for multiple DPs carrying GS streams. 
     The compensating delay block  3020  can delay the split TS packet stream following the insertion of ISSY information to allow a TS packet recombining mechanism without requiring additional memory in the receiver. 
     The null packet deletion block  3030 , is used only for the TS input stream case. Some TS input streams or split TS streams may have a large number of null-packets present in order to accommodate VBR (variable bit-rate) services in a CBR TS stream. In this case, in order to avoid unnecessary transmission overhead, null-packets can be identified and not transmitted. In the receiver, removed null-packets can be re-inserted in the exact place where they were originally by reference to a deleted null-packet (DNP) counter that is inserted in the transmission, thus guaranteeing constant bit-rate and avoiding the need for time-stamp (PCR) updating. 
     The head compression block  3040  can provide packet header compression to increase transmission efficiency for TS or IP input streams. Because the receiver can have a priori information on certain parts of the header, this known information can be deleted in the transmitter. 
     For Transport Stream, the receiver has a-priori information about the sync-byte configuration (0×47) and the packet length (188 Byte). If the input TS stream carries content that has only one PID, i.e., for only one service component (video, audio, etc.) or service sub-component (SVC base layer, SVC enhancement layer, MVC base view or MVC dependent views), TS packet header compression can be applied (optionally) to the Transport Stream. IP packet header compression is used optionally if the input steam is an IP stream. 
     The above-described blocks may be omitted or replaced by blocks having similar or identical functions. 
       FIG. 4  illustrates an input formatting block according to another embodiment of the present invention. 
     The input formatting block illustrated in  FIG. 4  corresponds to an embodiment of the input formatting block  1000  described with reference to  FIG. 1 . 
       FIG. 4  illustrates a stream adaptation block of the input formatting module when the input signal corresponds to multiple input streams. 
     Referring to  FIG. 4 , the mode adaptation block for respectively processing the multiple input streams can include a scheduler  4000 , an 1-Frame delay block  4010 , a stuffing insertion block  4020 , an in-band signaling  4030 , a BB Frame scrambler  4040 , a PLS generation block  4050  and a PLS scrambler  4060 . Description will be given of each block of the stream adaptation block. 
     Operations of the stuffing insertion block  4020 , the BB Frame scrambler  4040 , the PLS generation block  4050  and the PLS scrambler  4060  correspond to those of the stuffing insertion block, BB scrambler, PLS generation block and the PLS scrambler described with reference to  FIG. 2  and thus description thereof is omitted. 
     The scheduler  4000  can determine the overall cell allocation across the entire frame from the amount of FECBLOCKs of each DP. Including the allocation for PLS, EAC and FIC, the scheduler generate the values of PLS2-DYN data, which is transmitted as in-band signaling or PLS cell in FSS of the frame. Details of FECBLOCK, EAC and FIC will be described later. 
     The 1-Frame delay block  4010  can delay the input data by one transmission frame such that scheduling information about the next frame can be transmitted through the current frame for in-band signaling information to be inserted into the DPs. 
     The in-band signaling  4030  can insert un-delayed part of the PLS2 data into a DP of a frame. 
     The above-described blocks may be omitted or replaced by blocks having similar or identical functions. 
       FIG. 5  illustrates a BICM block according to an embodiment of the present invention. 
     The BICM block illustrated in  FIG. 5  corresponds to an embodiment of the BICM block  1010  described with reference to  FIG. 1 . 
     As described above, the apparatus for transmitting broadcast signals for future broadcast services according to an embodiment of the present invention can provide a terrestrial broadcast service, mobile broadcast service, UHDTV service, etc. 
     Since QoS (quality of service) depends on characteristics of a service provided by the apparatus for transmitting broadcast signals for future broadcast services according to an embodiment of the present invention, data corresponding to respective services needs to be processed through different schemes. Accordingly, the a BICM block according to an embodiment of the present invention can independently process DPs input thereto by independently applying SISO, MISO and MIMO schemes to the data pipes respectively corresponding to data paths. Consequently, the apparatus for transmitting broadcast signals for future broadcast services according to an embodiment of the present invention can control QoS for each service or service component transmitted through each DP. 
     (a) shows the BICM block shared by the base profile and the handheld profile and (b) shows the BICM block of the advanced profile. 
     The BICM block shared by the base profile and the handheld profile and the BICM block of the advanced profile can include plural processing blocks for processing each DP. 
     A description will be given of each processing block of the BICM block for the base profile and the handheld profile and the BICM block for the advanced profile. 
     A processing block  5000  of the BICM block for the base profile and the handheld profile can include a Data FEC encoder  5010 , a bit interleaver  5020 , a constellation mapper  5030 , an SSD (Signal Space Diversity) encoding block  5040  and a time interleaver  5050 . 
     The Data FEC encoder  5010  can perform the FEC encoding on the input BBF to generate FECBLOCK procedure using outer coding (BCH), and inner coding (LDPC). The outer coding (BCH) is optional coding method. Details of operations of the Data FEC encoder  5010  will be described later. 
     The bit interleaver  5020  can interleave outputs of the Data FEC encoder  5010  to achieve optimized performance with combination of the LDPC codes and modulation scheme while providing an efficiently implementable structure. Details of operations of the bit interleaver  5020  will be described later. 
     The constellation mapper  5030  can modulate each cell word from the bit interleaver  5020  in the base and the handheld profiles, or cell word from the Cell-word demultiplexer  5010 - 1  in the advanced profile using either QPSK, QAM-16, non-uniform QAM (NUQ-64, NUQ-256, NUQ-1024) or non-uniform constellation (NUC-16, NUC-64, NUC-256, NUC-1024) to give a power-normalized constellation point, e I . This constellation mapping is applied only for DPs. Observe that QAM-16 and NUQs are square shaped, while NUCs have arbitrary shape. When each constellation is rotated by any multiple of 90 degrees, the rotated constellation exactly overlaps with its original one. This “rotation-sense” symmetric property makes the capacities and the average powers of the real and imaginary components equal to each other. Both NUQs and NUCs are defined specifically for each code rate and the particular one used is signaled by the parameter DP_MOD filed in PLS2 data. 
     The SSD encoding block  5040  can precode cells in two (2D), three (3D), and four (4D) dimensions to increase the reception robustness under difficult fading conditions. 
     The time interleaver  5050  can operates at the DP level. The parameters of time interleaving (TI) may be set differently for each DP. Details of operations of the time interleaver  5050  will be described later. 
     A processing block  5000 - 1  of the BICM block for the advanced profile can include the Data FEC encoder, bit interleaver, constellation mapper, and time interleaver. However, the processing block  5000 - 1  is distinguished from the processing block  5000  further includes a cell-word demultiplexer  5010 - 1  and a MIMO encoding block  5020 - 1 . 
     Also, the operations of the Data FEC encoder, bit interleaver, constellation mapper, and time interleaver in the processing block  5000 - 1  correspond to those of the Data FEC encoder  5010 , bit interleaver  5020 , constellation mapper  5030 , and time interleaver  5050  described and thus description thereof is omitted. 
     The cell-word demultiplexer  5010 - 1  is used for the DP of the advanced profile to divide the single cell-word stream into dual cell-word streams for MIMO processing. Details of operations of the cell-word demultiplexer  5010 - 1  will be described later. 
     The MIMO encoding block  5020 - 1  can processing the output of the cell-word demultiplexer  5010 - 1  using MIMO encoding scheme. The MIMO encoding scheme was optimized for broadcasting signal transmission. The MIMO technology is a promising way to get a capacity increase but it depends on channel characteristics. Especially for broadcasting, the strong LOS component of the channel or a difference in the received signal power between two antennas caused by different signal propagation characteristics makes it difficult to get capacity gain from MIMO. The proposed MIMO encoding scheme overcomes this problem using a rotation-based pre-coding and phase randomization of one of the MIMO output signals. 
     MIMO encoding is intended for a 2×2 MIMO system requiring at least two antennas at both the transmitter and the receiver. Two MIMO encoding modes are defined in this proposal; full-rate spatial multiplexing (FR-SM) and full-rate full-diversity spatial multiplexing (FRFD-SM). The FR-SM encoding provides capacity increase with relatively small complexity increase at the receiver side while the FRFD-SM encoding provides capacity increase and additional diversity gain with a great complexity increase at the receiver side. The proposed MIMO encoding scheme has no restriction on the antenna polarity configuration. 
     MIMO processing is required for the advanced profile frame, which means all DPs in the advanced profile frame are processed by the MIMO encoder. MIMO processing is applied at DP level. Pairs of the Constellation Mapper outputs NUQ (e 1,i  and e 2,i ) are fed to the input of the MIMO Encoder. Paired MIMO Encoder output (g 1 ,i and g 2 ,i) is transmitted by the same carrier k and OFDM symbol I of their respective TX antennas. 
     The above-described blocks may be omitted or replaced by blocks having similar or identical functions. 
       FIG. 6  illustrates a BICM block according to another embodiment of the present invention. 
     The BICM block illustrated in  FIG. 6  corresponds to an embodiment of the BICM block  1010  described with reference to  FIG. 1 . 
       FIG. 6  illustrates a BICM block for protection of physical layer signaling (PLS), emergency alert channel (EAC) and fast information channel (FIC). EAC is a part of a frame that carries EAS information data and FIC is a logical channel in a frame that carries the mapping information between a service and the corresponding base DP. Details of the EAC and FIC will be described later. 
     Referring to  FIG. 6 , the BICM block for protection of PLS, EAC and FIC can include a PLS FEC encoder  6000 , a bit interleaver  6010 , a constellation mapper  6020  and time interleaver  6030 . 
     Also, the PLS FEC encoder  6000  can include a scrambler, BCH encoding/zero insertion block, LDPC encoding block and LDPC parity punturing block. Description will be given of each block of the BICM block. 
     The PLS FEC encoder  6000  can encode the scrambled PLS 1/2 data, EAC and FIC section. 
     The scrambler can scramble PLS1 data and PLS2 data before BCH encoding and shortened and punctured LDPC encoding. 
     The BCH encoding/zero insertion block can perform outer encoding on the scrambled PLS 1/2 data using the shortened BCH code for PLS protection and insert zero bits after the BCH encoding. For PLS1 data only, the output bits of the zero insertion may be permitted before LDPC encoding. 
     The LDPC encoding block can encode the output of the BCH encoding/zero insertion block using LDPC code. To generate a complete coded block, C ldpc , parity bits, P ldpc  are encoded systematically from each zero-inserted PLS information block, I ldpc  and appended after it. 
         C   ldpc   =[I   ldpc    P   ldpc   ]=[i   0   ,i   1   , . . . , i   K     ldpc     −1   , p   0   ,p   1   , . . . , p   N     ldpc     −K     ldpc     −1 ]  [Math Figure 1]
 
     The LDPC code parameters for PLS1 and PLS2 are as following table 4. 
     
       
         
           
               
               
               
               
               
               
               
               
               
             
               
                 TABLE 4 
               
               
                   
               
               
                 Signaling 
                   
                   
                   
                 K ldpc   
                   
                   
                 code 
                   
               
               
                 Type 
                 K sig   
                 K bch   
                 N bch     —     parity   
                 (=N bch ) 
                 N ldpc   
                 N ldpc     —     parity   
                 rate 
                 Q ldpc   
               
               
                   
               
             
            
               
                   
               
            
           
           
               
               
               
               
               
               
               
               
               
            
               
                 PLS1 
                 342 
                 1020 
                 60 
                 1080 
                 4320 
                 3240 
                 1/4  
                 36 
               
               
                 PLS2 
                 &lt;1021 
               
               
                   
                 &gt;1020 
                 2100 
                   
                 2160 
                 7200 
                 5040 
                 3/10 
                 56 
               
               
                   
               
            
           
         
       
     
     The LDPC parity punturing block can perform puncturing on the PLS1 data and PLS 2 data. 
     When shortening is applied to the PLS1 data protection, some LDPC parity bits are punctured after LDPC encoding. Also, for the PLS2 data protection, the LDPC parity bits of PLS2 are punctured after LDPC encoding. These punctured bits are not transmitted. 
     The bit interleaver  6010  can interleave the each shortened and punctured PLS1 data and PLS2 data. 
     The constellation mapper  6020  can map the bit interleaved PLS1 data and PLS2 data onto constellations. 
     The time interleaver  6030  can interleave the mapped PLS1 data and PLS2 data. 
     The above-described blocks may be omitted or replaced by blocks having similar or identical functions. 
       FIG. 7  illustrates a frame building block according to one embodiment of the present invention. 
     The frame building block illustrated in  FIG. 7  corresponds to an embodiment of the frame building block  1020  described with reference to  FIG. 1 . 
     Referring to  FIG. 7 , the frame building block can include a delay compensation block  7000 , a cell mapper  7010  and a frequency interleaver  7020 . Description will be given of each block of the frame building block. 
     The delay compensation block  7000  can adjust the timing between the data pipes and the corresponding PLS data to ensure that they are co-timed at the transmitter end. The PLS data is delayed by the same amount as data pipes are by addressing the delays of data pipes caused by the Input Formatting block and BICM block. The delay of the BICM block is mainly due to the time interleaver. In-band signaling data carries information of the next TI group so that they are carried one frame ahead of the DPs to be signaled. The Delay Compensating block delays in-band signaling data accordingly. 
     The cell mapper  7010  can map PLS, EAC, FIC, DPs, auxiliary streams and dummy cells into the active carriers of the OFDM symbols in the frame. The basic function of the cell mapper  7010  is to map data cells produced by the TIs for each of the DPs, PLS cells, and EAC/FIC cells, if any, into arrays of active OFDM cells corresponding to each of the OFDM symbols within a frame. Service signaling data (such as PSI(program specific information)/SI) can be separately gathered and sent by a data pipe. The Cell Mapper operates according to the dynamic information produced by the scheduler and the configuration of the frame structure. Details of the frame will be described later. 
     The frequency interleaver  7020  can randomly interleave data cells received from the cell mapper  7010  to provide frequency diversity. Also, the frequency interleaver  7020  can operate on very OFDM symbol pair comprised of two sequential OFDM symbols using a different interleaving-seed order to get maximum interleaving gain in a single frame. Details of operations of the frequency interleaver  7020  will be described later. 
     The above-described blocks may be omitted or replaced by blocks having similar or identical functions. 
       FIG. 8  illustrates an OFMD generation block according to an embodiment of the present invention. 
     The OFMD generation block illustrated in  FIG. 8  corresponds to an embodiment of the OFMD generation block  1030  described with reference to  FIG. 1 . 
     The OFDM generation block modulates the OFDM carriers by the cells produced by the Frame Building block, inserts the pilots, and produces the time domain signal for transmission. Also, this block subsequently inserts guard intervals, and applies PAPR (Peak-to-Average Power Radio) reduction processing to produce the final RF signal. 
     Referring to  FIG. 8 , the frame building block can include a pilot and reserved tone insertion block  8000 , a 2D-eSFN encoding block  8010 , an IFFT (Inverse Fast Fourier Transform) block  8020 , a PAPR reduction block  8030 , a guard interval insertion block  8040 , a preamble insertion block  8050 , other system insertion block  8060  and a DAC block  8070 . Description will be given of each block of the frame building block. 
     The pilot and reserved tone insertion block  8000  can insert pilots and the reserved tone. 
     Various cells within the OFDM symbol are modulated with reference information, known as pilots, which have transmitted values known a priori in the receiver. The information of pilot cells is made up of scattered pilots, continual pilots, edge pilots, FSS (frame signaling symbol) pilots and FES (frame edge symbol) pilots. Each pilot is transmitted at a particular boosted power level according to pilot type and pilot pattern. The value of the pilot information is derived from a reference sequence, which is a series of values, one for each transmitted carrier on any given symbol. The pilots can be used for frame synchronization, frequency synchronization, time synchronization, channel estimation, and transmission mode identification, and also can be used to follow the phase noise. 
     Reference information, taken from the reference sequence, is transmitted in scattered pilot cells in every symbol except the preamble, FSS and FES of the frame. Continual pilots are inserted in every symbol of the frame. The number and location of continual pilots depends on both the FFT size and the scattered pilot pattern. The edge carriers are edge pilots in every symbol except for the preamble symbol. They are inserted in order to allow frequency interpolation up to the edge of the spectrum. FSS pilots are inserted in FSS(s) and FES pilots are inserted in FES. They are inserted in order to allow time interpolation up to the edge of the frame. 
     The system according to an embodiment of the present invention supports the SFN network, where distributed MISO scheme is optionally used to support very robust transmission mode. The 2D-eSFN is a distributed MISO scheme that uses multiple TX antennas, each of which is located in the different transmitter site in the SFN network. 
     The 2D-eSFN encoding block  8010  can process a 2D-eSFN processing to distorts the phase of the signals transmitted from multiple transmitters, in order to create both time and frequency diversity in the SFN configuration. Hence, burst errors due to low flat fading or deep-fading for a long time can be mitigated. 
     The IFFT block  8020  can modulate the output from the 2D-eSFN encoding block  8010  using OFDM modulation scheme. Any cell in the data symbols which has not been designated as a pilot (or as a reserved tone) carries one of the data cells from the frequency interleaver. The cells are mapped to OFDM carriers. 
     The PAPR reduction block  8030  can perform a PAPR reduction on input signal using various PAPR reduction algorithm in the time domain. 
     The guard interval insertion block  8040  can insert guard intervals and the preamble insertion block  8050  can insert preamble in front of the signal. Details of a structure of the preamble will be described later. The other system insertion block  8060  can multiplex signals of a plurality of broadcast transmission/reception systems in the time domain such that data of two or more different broadcast transmission/reception systems providing broadcast services can be simultaneously transmitted in the same RF signal bandwidth. In this case, the two or more different broadcast transmission/reception systems refer to systems providing different broadcast services. The different broadcast services may refer to a terrestrial broadcast service, mobile broadcast service, etc. Data related to respective broadcast services can be transmitted through different frames. 
     The DAC block  8070  can convert an input digital signal into an analog signal and output the analog signal. The signal output from the DAC block  7800  can be transmitted through multiple output antennas according to the physical layer profiles. A Tx antenna according to an embodiment of the present invention can have vertical or horizontal polarity. 
     The above-described blocks may be omitted or replaced by blocks having similar or identical functions according to design. 
       FIG. 9  illustrates a structure of an apparatus for receiving broadcast signals for future broadcast services according to an embodiment of the present invention. 
     The apparatus for receiving broadcast signals for future broadcast services according to an embodiment of the present invention can correspond to the apparatus for transmitting broadcast signals for future broadcast services, described with reference to  FIG. 1 . 
     The apparatus for receiving broadcast signals for future broadcast services according to an embodiment of the present invention can include a synchronization &amp; demodulation module  9000 , a frame parsing module  9010 , a demapping &amp; decoding module  9020 , an output processor  9030  and a signaling decoding module  9040 . A description will be given of operation of each module of the apparatus for receiving broadcast signals. 
     The synchronization &amp; demodulation module  9000  can receive input signals through m Rx antennas, perform signal detection and synchronization with respect to a system corresponding to the apparatus for receiving broadcast signals and carry out demodulation corresponding to a reverse procedure of the procedure performed by the apparatus for transmitting broadcast signals. 
     The frame parsing module  9100  can parse input signal frames and extract data through which a service selected by a user is transmitted. If the apparatus for transmitting broadcast signals performs interleaving, the frame parsing module  9100  can carry out deinterleaving corresponding to a reverse procedure of interleaving. In this case, the positions of a signal and data that need to be extracted can be obtained by decoding data output from the signaling decoding module  9400  to restore scheduling information generated by the apparatus for transmitting broadcast signals. 
     The demapping &amp; decoding module  9200  can convert the input signals into bit domain data and then deinterleave the same as necessary. The demapping &amp; decoding module  9200  can perform demapping for mapping applied for transmission efficiency and correct an error generated on a transmission channel through decoding. In this case, the demapping &amp; decoding module  9200  can obtain transmission parameters necessary for demapping and decoding by decoding the data output from the signaling decoding module  9400 . 
     The output processor  9300  can perform reverse procedures of various compression/signal processing procedures which are applied by the apparatus for transmitting broadcast signals to improve transmission efficiency. In this case, the output processor  9300  can acquire necessary control information from data output from the signaling decoding module  9400 . The output of the output processor  8300  corresponds to a signal input to the apparatus for transmitting broadcast signals and may be MPEG-TSs, IP streams (v4 or v6) and generic streams. 
     The signaling decoding module  9400  can obtain PLS information from the signal demodulated by the synchronization &amp; demodulation module  9000 . As described above, the frame parsing module  9100 , demapping &amp; decoding module  9200  and output processor  9300  can execute functions thereof using the data output from the signaling decoding module  9400 . 
       FIG. 10  illustrates a frame structure according to an embodiment of the present invention. 
       FIG. 10  shows an example configuration of the frame types and FRUs in a super-frame. (a) shows a super frame according to an embodiment of the present invention, (b) shows FRU (Frame Repetition Unit) according to an embodiment of the present invention, (c) shows frames of variable PHY profiles in the FRU and (d) shows a structure of a frame. 
     A super-frame may be composed of eight FRUs. The FRU is a basic multiplexing unit for TDM of the frames, and is repeated eight times in a super-frame. 
     Each frame in the FRU belongs to one of the PHY profiles, (base, handheld, advanced) or FEF. The maximum allowed number of the frames in the FRU is four and a given PHY profile can appear any number of times from zero times to four times in the FRU (e.g., base, base, handheld, advanced). PHY profile definitions can be extended using reserved values of the PHY_PROFILE in the preamble, if required. 
     The FEF part is inserted at the end of the FRU, if included. When the FEF is included in the FRU, the minimum number of FEFs is 8 in a super-frame. It is not recommended that FEF parts be adjacent to each other. 
     One frame is further divided into a number of OFDM symbols and a preamble. As shown in (d), the frame comprises a preamble, one or more frame signaling symbols (FSS), normal data symbols and a frame edge symbol (FES). 
     The preamble is a special symbol that enables fast Futurecast UTB system signal detection and provides a set of basic transmission parameters for efficient transmission and reception of the signal. The detailed description of the preamble will be will be described later. 
     The main purpose of the FSS(s) is to carry the PLS data. For fast synchronization and channel estimation, and hence fast decoding of PLS data, the FSS has more dense pilot pattern than the normal data symbol. The FES has exactly the same pilots as the FSS, which enables frequency-only interpolation within the FES and temporal interpolation, without extrapolation, for symbols immediately preceding the FES. 
       FIG. 11  illustrates a signaling hierarchy structure of the frame according to an embodiment of the present invention. 
       FIG. 11  illustrates the signaling hierarchy structure, which is split into three main parts: the preamble signaling data  11000 , the PLS1 data  11010  and the PLS2 data  11020 . The purpose of the preamble, which is carried by the preamble symbol in every frame, is to indicate the transmission type and basic transmission parameters of that frame. The PLS1 enables the receiver to access and decode the PLS2 data, which contains the parameters to access the DP of interest. The PLS2 is carried in every frame and split into two main parts: PLS2-STAT data and PLS2-DYN data. The static and dynamic portion of PLS2 data is followed by padding, if necessary. 
       FIG. 12  illustrates preamble signaling data according to an embodiment of the present invention. 
     Preamble signaling data carries 21 bits of information that are needed to enable the receiver to access PLS data and trace DPs within the frame structure. Details of the preamble signaling data are as follows: 
     PHY_PROFILE: This 3-bit field indicates the PHY profile type of the current frame. The mapping of different PHY profile types is given in below table 5. 
     
       
         
           
               
               
               
             
               
                   
                 TABLE 5 
               
               
                   
                   
               
               
                   
                 Value 
                 PHY profile 
               
               
                   
                   
               
             
            
               
                   
                 000 
                 Base profile 
               
               
                   
                 001 
                 Handheld profile 
               
               
                   
                 010 
                 Advanced profiled 
               
               
                   
                 011~110 
                 Reserved 
               
               
                   
                 111 
                 FEF 
               
               
                   
                   
               
            
           
         
       
     
     FFT_SIZE: This 2 bit field indicates the FFT size of the current frame within a frame-group, as described in below table 6. 
     
       
         
           
               
               
               
             
               
                   
                 TABLE 6 
               
               
                   
                   
               
               
                   
                 Value 
                 FFT size 
               
               
                   
                   
               
             
            
               
                   
                 00 
                  8K FFT 
               
               
                   
                 01 
                 16K FFT 
               
               
                   
                 10 
                 32K FFT 
               
               
                   
                 11 
                 Reserved 
               
               
                   
                   
               
            
           
         
       
     
     GI_FRACTION: This 3 bit field indicates the guard interval fraction value in the current super-frame, as described in below table 7. 
     
       
         
           
               
               
               
             
               
                   
                 TABLE 7 
               
               
                   
                   
               
               
                   
                 Value 
                 GI_FRACTION 
               
               
                   
                   
               
             
            
               
                   
                 000 
                 ⅕ 
               
               
                   
                 001 
                  1/10 
               
               
                   
                 010 
                  1/20 
               
               
                   
                 011 
                  1/40 
               
               
                   
                 100 
                  1/80 
               
               
                   
                 101 
                  1/160 
               
               
                   
                 110~111 
                 Reserved 
               
               
                   
                   
               
            
           
         
       
     
     EAC_FLAG: This 1 bit field indicates whether the EAC is provided in the current frame. If this field is set to ‘1’, emergency alert service (EAS) is provided in the current frame. If this field set to ‘0’, EAS is not carried in the current frame. This field can be switched dynamically within a super-frame. 
     PILOT_MODE: This 1-bit field indicates whether the pilot mode is mobile mode or fixed mode for the current frame in the current frame-group. If this field is set to ‘0’, mobile pilot mode is used. If the field is set to ‘1’, the fixed pilot mode is used. 
     PAPR_FLAG: This 1-bit field indicates whether PAPR reduction is used for the current frame in the current frame-group. If this field is set to value ‘1’, tone reservation is used for PAPR reduction. If this field is set to ‘0’, PAPR reduction is not used. 
     FRU_CONFIGURE: This 3-bit field indicates the PHY profile type configurations of the frame repetition units (FRU) that are present in the current super-frame. All profile types conveyed in the current super-frame are identified in this field in all preambles in the current super-frame. The 3-bit field has a different definition for each profile, as show in below table 8. 
     
       
         
           
               
               
               
               
               
             
               
                   
                 TABLE 8 
               
               
                   
                   
               
               
                   
                   
                 Current 
                 Current 
                   
               
               
                   
                 Current 
                 PHY_PROFILE = 
                 PHY_PROFILE = 
                 Current 
               
               
                   
                 PHY_PROFILE = 
                 ‘001’ 
                 ‘010’ 
                 PHY_PROFILE = 
               
               
                   
                 ‘000’ (base) 
                 (handheld) 
                 (advanced) 
                 ‘111’ (FEF) 
               
               
                   
                   
               
             
            
               
                   
               
            
           
           
               
               
               
               
               
            
               
                 FRU_CONFIGURE = 
                 Only base 
                 Only handheld 
                 Only advanced 
                 Only FEF 
               
               
                 000 
                 profile 
                 profile present 
                 profile present 
                 present 
               
               
                   
                 present 
               
               
                 FRU_CONFIGURE = 
                 Handheld profile 
                 Base profile 
                 Base profile 
                 Base profile 
               
               
                 1XX 
                 present 
                 present 
                 present 
                 present 
               
               
                 FRU_CONFIGURE = 
                 Advanced 
                 Advanced 
                 Handheld profile 
                 Handheld profile 
               
               
                 X1X 
                 profile 
                 profile 
                 present 
                 present 
               
               
                   
                 present 
                 present 
               
               
                 FRU_CONFIGURE = 
                 FEF 
                 FEF 
                 FEF 
                 Advanced 
               
               
                 XX1 
                 present 
                 present 
                 present 
                 profile 
               
               
                   
                   
                   
                   
                 present 
               
               
                   
               
            
           
         
       
     
     RESERVED: This 7-bit field is reserved for future use. 
       FIG. 13  illustrates PLS1 data according to an embodiment of the present invention. 
     PLS1 data provides basic transmission parameters including parameters required to enable the reception and decoding of the PLS2. As above mentioned, the PLS1 data remain unchanged for the entire duration of one frame-group. The detailed definition of the signaling fields of the PLS1 data are as follows: 
     PREAMBLE_DATA: This 20-bit field is a copy of the preamble signaling data excluding the EAC_FLAG. 
     NUM_FRAME_FRU: This 2-bit field indicates the number of the frames per FRU. 
     PAYLOAD_TYPE: This 3-bit field indicates the format of the payload data carried in the frame-group. PAYLOAD_TYPE is signaled as shown in table 9. 
     
       
         
           
               
               
             
               
                 TABLE 9 
               
               
                   
               
               
                 value 
                 Payload type 
               
               
                   
               
             
            
               
                 1XX 
                 TS stream is transmitted 
               
               
                 X1X 
                 IP stream is transmitted 
               
               
                 XX1 
                 GS stream is transmitted 
               
               
                   
               
            
           
         
       
     
     NUM_FSS: This 2-bit field indicates the number of FSS symbols in the current frame. 
     SYSTEM_VERSION: This 8-bit field indicates the version of the transmitted signal format. The SYSTEM_VERSION is divided into two 4-bit fields, which are a major version and a minor version. 
     Major version: The MSB four bits of SYSTEM_VERSION field indicate major version information. A change in the major version field indicates a non-backward-compatible change. The default value is ‘0000’. For the version described in this standard, the value is set to ‘0000’. 
     Minor version: The LSB four bits of SYSTEM_VERSION field indicate minor version information. A change in the minor version field is backward-compatible. 
     CELL_ID: This is a 16-bit field which uniquely identifies a geographic cell in an ATSC network. An ATSC cell coverage area may consist of one or more frequencies, depending on the number of frequencies used per Futurecast UTB system. If the value of the CELL_ID is not known or unspecified, this field is set to ‘0’. 
     NETWORK_ID: This is a 16-bit field which uniquely identifies the current ATSC network. 
     SYSTEM_ID: This 16-bit field uniquely identifies the Futurecast UTB system within the ATSC network. The Futurecast UTB system is the terrestrial broadcast system whose input is one or more input streams (TS, IP, GS) and whose output is an RF signal. The Futurecast UTB system carries one or more PHY profiles and FEF, if any. The same Futurecast UTB system may carry different input streams and use different RF frequencies in different geographical areas, allowing local service insertion. The frame structure and scheduling is controlled in one place and is identical for all transmissions within a Futurecast UTB system. One or more Futurecast UTB systems may have the same SYSTEM_ID meaning that they all have the same physical layer structure and configuration. 
     The following loop consists of FRU_PHY_PROFILE, FRU_FRAME_LENGTH, FRU_GI_FRACTION, and RESERVED which are used to indicate the FRU configuration and the length of each frame type. The loop size is fixed so that four PHY profiles (including a FEF) are signaled within the FRU. If NUM_FRAME_FRU is less than 4, the unused fields are filled with zeros. 
     FRU_PHY_PROFILE: This 3-bit field indicates the PHY profile type of the (i+1) th  (i is the loop index) frame of the associated FRU. This field uses the same signaling format as shown in the table 8. 
     FRU_FRAME_LENGTH: This 2-bit field indicates the length of the (i+1) th  frame of the associated FRU. Using FRU_FRAME_LENGTH together with FRU_GI_FRACTION, the exact value of the frame duration can be obtained. 
     FRU_GI_FRACTION: This 3-bit field indicates the guard interval fraction value of the (i+1) th  frame of the associated FRU. FRU_GI_FRACTION is signaled according to the table 7. 
     RESERVED: This 4-bit field is reserved for future use. 
     The following fields provide parameters for decoding the PLS2 data. 
     PLS2_FEC_TYPE: This 2-bit field indicates the FEC type used by the PLS2 protection. The FEC type is signaled according to table 10. The details of the LDPC codes will be described later. 
     
       
         
           
               
               
               
             
               
                   
                 TABLE 10 
               
               
                   
                   
               
               
                   
                 Content 
                 PLS2 FEC type 
               
               
                   
                   
               
             
            
               
                   
                 00 
                 4K-1/4 and 7K-3/10 LDPC codes 
               
               
                   
                 01~11 
                 Reserved 
               
               
                   
                   
               
            
           
         
       
     
     PLS2_MOD: This 3-bit field indicates the modulation type used by the PLS2. The modulation type is signaled according to table 11. 
     
       
         
           
               
               
               
             
               
                   
                 TABLE 11 
               
               
                   
                   
               
               
                   
                 Value 
                 PLS2_MODE 
               
               
                   
                   
               
             
            
               
                   
                 000 
                 BPSK 
               
               
                   
                 001 
                 QPSK 
               
               
                   
                 010 
                 QAM-16 
               
               
                   
                 011 
                 NUQ-64 
               
               
                   
                 100~111 
                 Reserved 
               
               
                   
                   
               
            
           
         
       
     
     PLS2_SIZE_CELL: This 15-bit field indicates C total   _   partial   _   block , the size (specified as the number of QAM cells) of the collection of full coded blocks for PLS2 that is carried in the current frame-group. This value is constant during the entire duration of the current frame-group. 
     PLS2_STAT_SIZE_BIT: This 14-bit field indicates the size, in bits, of the PLS2-STAT for the current frame-group. This value is constant during the entire duration of the current frame-group. 
     PLS2_DYN_SIZE_BIT: This 14-bit field indicates the size, in bits, of the PLS2-DYN for the current frame-group. This value is constant during the entire duration of the current frame-group. 
     PLS2_REP_FLAG: This 1-bit flag indicates whether the PLS2 repetition mode is used in the current frame-group. When this field is set to value ‘1’, the PLS2 repetition mode is activated. When this field is set to value ‘0’, the PLS2 repetition mode is deactivated. 
     PLS2_REP_SIZE_CELL: This 15-bit field indicates C total   _   partial   _   block , the size (specified as the number of QAM cells) of the collection of partial coded blocks for PLS2 carried in every frame of the current frame-group, when PLS2 repetition is used. If repetition is not used, the value of this field is equal to 0. This value is constant during the entire duration of the current frame-group. 
     PLS2_NEXT_FEC_TYPE: This 2-bit field indicates the FEC type used for PLS2 that is carried in every frame of the next frame-group. The FEC type is signaled according to the table 10. 
     PLS2_NEXT_MOD: This 3-bit field indicates the modulation type used for PLS2 that is carried in every frame of the next frame-group. The modulation type is signaled according to the table 11. 
     PLS2_NEXT_REP_FLAG: This 1-bit flag indicates whether the PLS2 repetition mode is used in the next frame-group. When this field is set to value ‘1’, the PLS2 repetition mode is activated. When this field is set to value ‘0’, the PLS2 repetition mode is deactivated. 
     PLS2_NEXT_REP_SIZE_CELL: This 15-bit field indicates C total   _   full   _   block , The size (specified as the number of QAM cells) of the collection of full coded blocks for PLS2 that is carried in every frame of the next frame-group, when PLS2 repetition is used. If repetition is not used in the next frame-group, the value of this field is equal to 0. This value is constant during the entire duration of the current frame-group. 
     PLS2_NEXT_REP_STAT_SIZE_BIT: This 14-bit field indicates the size, in bits, of the PLS2-STAT for the next frame-group. This value is constant in the current frame-group. 
     PLS2_NEXT_REP_DYN_SIZE_BIT: This 14-bit field indicates the size, in bits, of the PLS2-DYN for the next frame-group. This value is constant in the current frame-group. 
     PLS2_AP_MODE: This 2-bit field indicates whether additional parity is provided for PLS2 in the current frame-group. This value is constant during the entire duration of the current frame-group. The below table 12 gives the values of this field. When this field is set to ‘00’, additional parity is not used for the PLS2 in the current frame-group. 
     
       
         
           
               
               
               
             
               
                   
                 TABLE 12 
               
               
                   
                   
               
               
                   
                 Value 
                 PLS2-AP mode 
               
               
                   
                   
               
             
            
               
                   
                 00 
                 AP is not provided 
               
               
                   
                 01 
                 AP1 mode 
               
               
                   
                 10~11 
                 Reserved 
               
               
                   
                   
               
            
           
         
       
     
     PLS2_AP_SIZE_CELL: This 15-bit field indicates the size (specified as the number of QAM cells) of the additional parity bits of the PLS2. This value is constant during the entire duration of the current frame-group. 
     PLS2_NEXT_AP_MODE: This 2-bit field indicates whether additional parity is provided for PLS2 signaling in every frame of next frame-group. This value is constant during the entire duration of the current frame-group. The table 12 defines the values of this field 
     PLS2_NEXT_AP_SIZE_CELL: This 15-bit field indicates the size (specified as the number of QAM cells) of the additional parity bits of the PLS2 in every frame of the next frame-group. This value is constant during the entire duration of the current frame-group. 
     RESERVED: This 32-bit field is reserved for future use. 
     CRC_32: A 32-bit error detection code, which is applied to the entire PLS1 signaling. 
       FIG. 14  illustrates PLS2 data according to an embodiment of the present invention. 
       FIG. 14  illustrates PLS2-STAT data of the PLS2 data. The PLS2-STAT data are the same within a frame-group, while the PLS2-DYN data provide information that is specific for the current frame. 
     The details of fields of the PLS2-STAT data are as follows: 
     FIC_FLAG: This 1-bit field indicates whether the FIC is used in the current frame-group. If this field is set to ‘1’, the FIC is provided in the current frame. If this field set to ‘0’, the FIC is not carried in the current frame. This value is constant during the entire duration of the current frame-group. 
     AUX_FLAG: This 1-bit field indicates whether the auxiliary stream(s) is used in the current frame-group. If this field is set to ‘1’, the auxiliary stream is provided in the current frame. If this field set to ‘0’, the auxiliary stream is not carried in the current frame. This value is constant during the entire duration of current frame-group. 
     NUM_DP: This 6-bit field indicates the number of DPs carried within the current frame. The value of this field ranges from 1 to 64, and the number of DPs is NUM_DP+1. 
     DP_ID: This 6-bit field identifies uniquely a DP within a PHY profile. 
     DP_TYPE: This 3-bit field indicates the type of the DP. This is signaled according to the below table 13. 
     
       
         
           
               
               
               
             
               
                   
                 TABLE 13 
               
               
                   
                   
               
               
                   
                 Value 
                 DP Type 
               
               
                   
                   
               
             
            
               
                   
                 000 
                 DP Type 1 
               
               
                   
                 001 
                 DP Type 2 
               
               
                   
                 010~111 
                 reserved 
               
               
                   
                   
               
            
           
         
       
     
     DP_GROUP_ID: This 8-bit field identifies the DP group with which the current DP is associated. This can be used by a receiver to access the DPs of the service components associated with a particular service, which will have the same DP_GROUP_ID. 
     BASE_DP_ID: This 6-bit field indicates the DP carrying service signaling data (such as PSI/SI) used in the Management layer. The DP indicated by BASE_DP_ID may be either a normal DP carrying the service signaling data along with the service data or a dedicated DP carrying only the service signaling data 
     DP_FEC_TYPE: This 2-bit field indicates the FEC type used by the associated DP. The FEC type is signaled according to the below table 14. 
     
       
         
           
               
               
               
             
               
                   
                 TABLE 14 
               
               
                   
                   
               
               
                   
                 Value 
                 FEC_TYPE 
               
               
                   
                   
               
             
            
               
                   
                 00 
                 16K LDPC 
               
               
                   
                 01 
                 64K LDPC 
               
               
                   
                 10~11 
                 Reserved 
               
               
                   
                   
               
            
           
         
       
     
     DP_COD: This 4-bit field indicates the code rate used by the associated DR The code rate is signaled according to the below table 15. 
     
       
         
           
               
               
               
             
               
                   
                 TABLE 15 
               
               
                   
                   
               
               
                   
                 Value 
                 Code rate 
               
               
                   
                   
               
             
            
               
                   
                 0000 
                 5/15 
               
               
                   
                 0001 
                 6/15 
               
               
                   
                 0010 
                 7/15 
               
               
                   
                 0011 
                 8/15 
               
               
                   
                 0100 
                 9/15 
               
               
                   
                 0101 
                 10/15  
               
               
                   
                 0110 
                 11/15  
               
               
                   
                 0111 
                 12/15  
               
               
                   
                 1000 
                 13/15  
               
               
                   
                 1001~1111 
                 Reserved 
               
               
                   
                   
               
            
           
         
       
     
     DP_MOD: This 4-bit field indicates the modulation used by the associated DP. The modulation is signaled according to the below table 16. 
     
       
         
           
               
               
               
             
               
                   
                 TABLE 16 
               
               
                   
                   
               
               
                   
                 Value 
                 Modulation 
               
               
                   
                   
               
             
            
               
                   
                 0000 
                 QPSK 
               
               
                   
                 0001 
                 QAM-16 
               
               
                   
                 0010 
                 NUQ-64 
               
               
                   
                 0011 
                 NUQ-256 
               
               
                   
                 0100 
                 NUQ-1024 
               
               
                   
                 0101 
                 NUC-16 
               
               
                   
                 0110 
                 NUC-64 
               
               
                   
                 0111 
                 NUC-256 
               
               
                   
                 1000 
                 NUC-1024 
               
               
                   
                 1001~1111 
                 reserved 
               
               
                   
                   
               
            
           
         
       
     
     DP_SSD_FLAG: This 1-bit field indicates whether the SSD mode is used in the associated DP. If this field is set to value ‘1’, SSD is used. If this field is set to value ‘0’, SSD is not used. 
     The following field appears only if PHY_PROFILE is equal to ‘010’, which indicates the advanced profile: 
     DP_MIMO: This 3-bit field indicates which type of MIMO encoding process is applied to the associated DP. The type of MIMO encoding process is signaled according to the table 17. 
     
       
         
           
               
               
               
             
               
                   
                 TABLE 17 
               
               
                   
                   
               
               
                   
                 Value 
                 MIMO encoding 
               
               
                   
                   
               
             
            
               
                   
                 000 
                 FR-SM 
               
               
                   
                 001 
                 FRFD-SM 
               
               
                   
                 010~111 
                 reserved 
               
               
                   
                   
               
            
           
         
       
     
     DP_TI_TYPE: This 1-bit field indicates the type of time-interleaving. A value of ‘0’ indicates that one TI group corresponds to one frame and contains one or more TI-blocks. A value of ‘1’ indicates that one TI group is carried in more than one frame and contains only one TI-block. 
     DP_TI_LENGTH: The use of this 2-bit field (the allowed values are only 1, 2, 4, 8) is determined by the values set within the DP_TI_TYPE field as follows: 
     If the DP_TI_TYPE is set to the value ‘1’, this field indicates P i , the number of the frames to which each TI group is mapped, and there is one TI-block per TI group (N TI =1). The allowed P i  values with 2-bit field are defined in the below table 18. 
     If the DP_TI_TYPE is set to the value ‘0’, this field indicates the number of TI-blocks N TI , per TI group, and there is one TI group per frame (P i =1). The allowed P i  values with 2-bit field are defined in the below table 18. 
     
       
         
           
               
               
               
             
               
                 TABLE 18 
               
               
                   
               
               
                 2-bit field 
                 P I   
                 N TI   
               
               
                   
               
             
            
               
                 00 
                 1 
                 1 
               
               
                 01 
                 2 
                 2 
               
               
                 10 
                 4 
                 3 
               
               
                 11 
                 8 
                 4 
               
               
                   
               
            
           
         
       
     
     DP_FRAME_INTERVAL: This 2-bit field indicates the frame interval (I jump ) within the frame-group for the associated DP and the allowed values are 1, 2, 4, 8 (the corresponding 2-bit field is ‘00’, ‘01’, ‘10’, or ‘11’, respectively). For DPs that do not appear every frame of the frame-group, the value of this field is equal to the interval between successive frames. For example, if a DP appears on the frames 1, 5, 9, 13, etc., this field is set to ‘4’. For DPs that appear in every frame, this field is set to ‘1’. 
     DP_TI_BYPASS: This 1-bit field determines the availability of time interleaver. If time interleaving is not used for a DP, it is set to ‘1’. Whereas if time interleaving is used it is set to ‘0’. 
     DP_FIRST_FRAME_IDX: This 5-bit field indicates the index of the first frame of the super-frame in which the current DP occurs. The value of DP_FIRST_FRAME_IDX ranges from 0 to 31 
     DP_NUM_BLOCK_MAX: This 10-bit field indicates the maximum value of DP_NUM_BLOCKS for this DP. The value of this field has the same range as DP_NUM_BLOCKS. 
     DP_PAYLOAD_TYPE: This 2-bit field indicates the type of the payload data carried by the given DP. DP_PAYLOAD_TYPE is signaled according to the below table 19. 
     
       
         
           
               
               
             
               
                 TABLE 19 
               
               
                   
               
               
                 Value 
                 Payload Type 
               
               
                   
               
             
            
               
                 00 
                 TS. 
               
               
                 01 
                 IP 
               
               
                 10 
                 GS 
               
               
                 11 
                 reserved 
               
               
                   
               
            
           
         
       
     
     DP_INBAND_MODE: This 2-bit field indicates whether the current DP carries in-band signaling information. The in-band signaling type is signaled according to the below table 20. 
     
       
         
           
               
               
             
               
                 TABLE 20 
               
               
                   
               
               
                 Value 
                 In-band mode 
               
               
                   
               
             
            
               
                 00 
                 In-band signaling is not carried. 
               
               
                 01 
                 INBAND-PLS is carried only 
               
               
                 10 
                 INBAND-ISSY is carried only 
               
               
                 11 
                 INBAND-PLS and INBAND-ISSY are carried 
               
               
                   
               
            
           
         
       
     
     DP_PROTOCOL_TYPE: This 2-bit field indicates the protocol type of the payload carried by the given DP. It is signaled according to the below table 21 when input payload types are selected. 
     
       
         
           
               
               
               
               
             
               
                 TABLE 21 
               
               
                   
               
               
                   
                 If DP_PAYLOAD_TYPE 
                 If DP_PAYLOAD_TYPE 
                 If DP_PAYLOAD_TYPE 
               
               
                 Value 
                 Is TS 
                 Is IP 
                 Is GS 
               
               
                   
               
             
            
               
                 00 
                 MPEG2-TS 
                 IPv4 
                 (Note) 
               
               
                 01 
                 Reserved 
                 IPv6 
                 Reserved 
               
               
                 10 
                 Reserved 
                 Reserved 
                 Reserved 
               
               
                 11 
                 Reserved 
                 Reserved 
                 Reserved 
               
               
                   
               
            
           
         
       
     
     DP_CRC_MODE: This 2-bit field indicates whether CRC encoding is used in the Input Formatting block. The CRC mode is signaled according to the below table 22. 
     
       
         
           
               
               
             
               
                 TABLE 22 
               
               
                   
               
               
                 Value 
                 CRC mode 
               
               
                   
               
             
            
               
                 00 
                 Not used 
               
               
                 01 
                 CRC-8 
               
               
                 10 
                 CRC-16 
               
               
                 11 
                 CRC-32 
               
               
                   
               
            
           
         
       
     
     DNP_MODE: This 2-bit field indicates the null-packet deletion mode used by the associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). DNP_MODE is signaled according to the below table 23. If DP_PAYLOAD_TYPE is not TS (‘00’), DNP_MODE is set to the value ‘00’. 
     
       
         
           
               
               
             
               
                 TABLE 23 
               
               
                   
               
               
                 Value 
                 Null-packet deletion mode 
               
               
                   
               
             
            
               
                 00 
                 Not used 
               
               
                 01 
                 DNP-NORMAL 
               
               
                 10 
                 DNP-OFFSET 
               
               
                 11 
                 reserved 
               
               
                   
               
            
           
         
       
     
     ISSY_MODE: This 2-bit field indicates the ISSY mode used by the associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). The ISSY_MODE is signaled according to the below table 24 If DP_PAYLOAD_TYPE is not TS (‘00’), ISSY_MODE is set to the value ‘00’. 
     
       
         
           
               
               
             
               
                 TABLE 24 
               
               
                   
               
               
                 Value 
                 ISSY mode 
               
               
                   
               
             
            
               
                 00 
                 Not used 
               
               
                 01 
                 ISSY-UP 
               
               
                 10 
                 ISSY-BBF 
               
               
                 11 
                 reserved 
               
               
                   
               
            
           
         
       
     
     HC_MODE_TS: This 2-bit field indicates the TS header compression mode used by the associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). The HC_MODE_TS is signaled according to the below table 25. 
     
       
         
           
               
               
             
               
                 TABLE 25 
               
               
                   
               
               
                 Value 
                 Header compression mode 
               
               
                   
               
             
            
               
                 00 
                 HC_MODE_TS 1 
               
               
                 01 
                 HC_MODE_TS 2 
               
               
                 10 
                 HC_MODE_TS 3 
               
               
                 11 
                 HC_MODE_TS 4 
               
               
                   
               
            
           
         
       
     
     HC_MODE_IP: This 2-bit field indicates the IP header compression mode when DP_PAYLOAD_TYPE is set to IP (‘01’). The HC_MODE_IP is signaled according to the below table 26. 
     
       
         
           
               
               
             
               
                 TABLE 26 
               
               
                   
               
               
                 Value 
                 Header compression mode 
               
               
                   
               
             
            
               
                 00 
                 No compression 
               
               
                 01 
                 HC_MODE_IP 1 
               
               
                 10~11 
                 reserved 
               
               
                   
               
            
           
         
       
     
     PID: This 13-bit field indicates the PID number for TS header compression when DP_PAYLOAD_TYPE is set to TS (‘00’) and HC_MODE_TS is set to ‘01’ or ‘10’. 
     RESERVED: This 8-bit field is reserved for future use. 
     The following field appears only if FIC_FLAG is equal to ‘I’: 
     FIC_VERSION: This 8-bit field indicates the version number of the FIC. 
     FIC_LENGTH_BYTE: This 13-bit field indicates the length, in bytes, of the FIC. 
     RESERVED: This 8-bit field is reserved for future use. 
     The following field appears only if AUX_FLAG is equal to ‘I’: 
     NUM_AUX: This 4-bit field indicates the number of auxiliary streams. Zero means no auxiliary streams are used. 
     AUX_CONFIG_RFU: This 8-bit field is reserved for future use. 
     AUX_STREAM_TYPE: This 4-bit is reserved for future use for indicating the type of the current auxiliary stream. 
     AUX_PRIVATE_CONFIG: This 28-bit field is reserved for future use for signaling auxiliary streams. 
       FIG. 15  illustrates PLS2 data according to another embodiment of the present invention. 
       FIG. 15  illustrates PLS2-DYN data of the PLS2 data. The values of the PLS2-DYN data may change during the duration of one frame-group, while the size of fields remains constant. 
     The details of fields of the PLS2-DYN data are as follows: 
     FRAME_INDEX: This 5-bit field indicates the frame index of the current frame within the super-frame. The index of the first frame of the super-frame is set to ‘0’. 
     PLS_CHANGE_COUNTER: This 4-bit field indicates the number of super-frames ahead where the configuration will change. The next super-frame with changes in the configuration is indicated by the value signaled within this field. If this field is set to the value ‘0000’, it means that no scheduled change is foreseen: e.g., value ‘1’ indicates that there is a change in the next super-frame. 
     FIC_CHANGE_COUNTER: This 4-bit field indicates the number of super-frames ahead where the configuration (i.e., the contents of the FIC) will change. The next super-frame with changes in the configuration is indicated by the value signaled within this field. If this field is set to the value ‘0000’, it means that no scheduled change is foreseen: e.g. value ‘0001’ indicates that there is a change in the next super-frame. 
     RESERVED: This 16-bit field is reserved for future use. 
     The following fields appear in the loop over NUM_DP, which describe the parameters associated with the DP carried in the current frame. 
     DP_ID: This 6-bit field indicates uniquely the DP within a PHY profile. 
     DP_START: This 15-bit (or 13-bit) field indicates the start position of the first of the DPs using the DPU addressing scheme. The DP_START field has differing length according to the PHY profile and FFT size as shown in the below table 27. 
     
       
         
           
               
               
               
             
               
                   
                 TABLE 27 
               
             
            
               
                   
                   
               
               
                   
                 DP_START 
                   
               
               
                   
                 field size 
               
            
           
           
               
               
               
               
            
               
                   
                 PHY profile 
                 64K 
                 16K 
               
               
                   
                   
               
               
                   
                 Base 
                 13 bit 
                 15 bit 
               
               
                   
                 Handheld 
                 — 
                 13 bit 
               
               
                   
                 Advanced 
                 13 bit 
                 15 bit 
               
               
                   
                   
               
            
           
         
       
     
     DP_NUM_BLOCK: This 10-bit field indicates the number of FEC blocks in the current TI group for the current DP. The value of DP_NUM_BLOCK ranges from 0 to 1023 
     RESERVED: This 8-bit field is reserved for future use. 
     The following fields indicate the FIC parameters associated with the EAC. 
     EAC_FLAG: This 1-bit field indicates the existence of the EAC in the current frame. This bit is the same value as the EAC_FLAG in the preamble. 
     EAS_WAKE_UP_VERSION_NUM: This 8-bit field indicates the version number of a wake-up indication. 
     If the EAC_FLAG field is equal to ‘1’, the following 12 bits are allocated for EAC_LENGTH_BYTE field. If the EAC_FLAG field is equal to ‘0’, the following 12 bits are allocated for EAC_COUNTER. 
     EAC_LENGTH_BYTE: This 12-bit field indicates the length, in byte, of the EAC. 
     EAC_COUNTER: This 12-bit field indicates the number of the frames before the frame where the EAC arrives. 
     The following field appears only if the AUX_FLAG field is equal to ‘1’: 
     AUX_PRIVATE_DYN: This 48-bit field is reserved for future use for signaling auxiliary streams. The meaning of this field depends on the value of AUX_STREAM_TYPE in the configurable PLS2-STAT. 
     CRC_32: A 32-bit error detection code, which is applied to the entire PLS2. 
       FIG. 16  illustrates a logical structure of a frame according to an embodiment of the present invention. 
     As above mentioned, the PLS, EAC, FIC, DPs, auxiliary streams and dummy cells are mapped into the active carriers of the OFDM symbols in the frame. The PLS1 and PLS2 are first mapped into one or more FSS(s). After that, EAC cells, if any, are mapped immediately following the PLS field, followed next by FIC cells, if any. The DPs are mapped next after the PLS or EAC, FIC, if any. Type 1 DPs follows first, and Type 2 DPs next. The details of a type of the DP will be described later. In some case, DPs may carry some special data for EAS or service signaling data. The auxiliary stream or streams, if any, follow the DPs, which in turn are followed by dummy cells. Mapping them all together in the above mentioned order, i.e. PLS, EAC, FIC, DPs, auxiliary streams and dummy data cells exactly fill the cell capacity in the frame. 
       FIG. 17  illustrates PLS mapping according to an embodiment of the present invention. 
     PLS cells are mapped to the active carriers of FSS(s). Depending on the number of cells occupied by PLS, one or more symbols are designated as FSS(s), and the number of FSS(s) N FSS  is signaled by NUM_FSS in PLS1. The FSS is a special symbol for carrying PLS cells. Since robustness and latency are critical issues in the PLS, the FSS(s) has higher density of pilots allowing fast synchronization and frequency-only interpolation within the FSS. 
     PLS cells are mapped to active carriers of the N FSS  FSS(s) in a top-down manner as shown in an example in  FIG. 17 . The PLS1 cells are mapped first from the first cell of the first FSS in an increasing order of the cell index. The PLS2 cells follow immediately after the last cell of the PLS1 and mapping continues downward until the last cell index of the first FSS. If the total number of required PLS cells exceeds the number of active carriers of one FSS, mapping proceeds to the next FSS and continues in exactly the same manner as the first FSS. 
     After PLS mapping is completed, DPs are carried next. If EAC, FIC or both are present in the current frame, they are placed between PLS and “normal” DPs. 
       FIG. 18  illustrates EAC mapping according to an embodiment of the present invention. 
     EAC is a dedicated channel for carrying EAS messages and links to the DPs for EAS. EAS support is provided but EAC itself may or may not be present in every frame. EAC, if any, is mapped immediately after the PLS2 cells. EAC is not preceded by any of the FIC, DPs, auxiliary streams or dummy cells other than the PLS cells. The procedure of mapping the EAC cells is exactly the same as that of the PLS. 
     The EAC cells are mapped from the next cell of the PLS2 in increasing order of the cell index as shown in the example in  FIG. 18 . Depending on the EAS message size, EAC cells may occupy a few symbols, as shown in  FIG. 18 . 
     EAC cells follow immediately after the last cell of the PLS2, and mapping continues downward until the last cell index of the last FSS. If the total number of required EAC cells exceeds the number of remaining active carriers of the last FSS mapping proceeds to the next symbol and continues in exactly the same manner as FSS(s). The next symbol for mapping in this case is the normal data symbol, which has more active carriers than a FSS. 
     After EAC mapping is completed, the FIC is carried next, if any exists. If FIC is not transmitted (as signaled in the PLS2 field), DPs follow immediately after the last cell of the EAC. 
       FIG. 19  illustrates FIC mapping according to an embodiment of the present invention. 
     (a) shows an example mapping of FIC cell without EAC and (b) shows an example mapping of FIC cell with EAC. 
     FIC is a dedicated channel for carrying cross-layer information to enable fast service acquisition and channel scanning. This information primarily includes channel binding information between DPs and the services of each broadcaster. For fast scan, a receiver can decode FIC and obtain information such as broadcaster ID, number of services, and BASE_DP_ID. For fast service acquisition, in addition to FIC, base DP can be decoded using BASE_DP_ID. Other than the content it carries, a base DP is encoded and mapped to a frame in exactly the same way as a normal DP. Therefore, no additional description is required for a base DP. The FIC data is generated and consumed in the Management Layer. The content of FIC data is as described in the Management Layer specification. 
     The FIC data is optional and the use of FIC is signaled by the FIC_FLAG parameter in the static part of the PLS2. If FIC is used, FIC_FLAG is set to ‘1’ and the signaling field for FIC is defined in the static part of PLS2. Signaled in this field are FIC_VERSION, and FIC_LENGTH_BYTE. FIC uses the same modulation, coding and time interleaving parameters as PLS2. FIC shares the same signaling parameters such as PLS2_MOD and PLS2_FEC. FIC data, if any, is mapped immediately after PLS2 or EAC if any. FIC is not preceded by any normal DPs, auxiliary streams or dummy cells. The method of mapping FIC cells is exactly the same as that of EAC which is again the same as PLS. 
     Without EAC after PLS, FIC cells are mapped from the next cell of the PLS2 in an increasing order of the cell index as shown in an example in (a). Depending on the FIC data size, FIC cells may be mapped over a few symbols, as shown in (b). 
     FIC cells follow immediately after the last cell of the PLS2, and mapping continues downward until the last cell index of the last FSS. If the total number of required FIC cells exceeds the number of remaining active carriers of the last FSS, mapping proceeds to the next symbol and continues in exactly the same manner as FSS(s). The next symbol for mapping in this case is the normal data symbol which has more active carriers than a FSS. 
     If EAS messages are transmitted in the current frame, EAC precedes FIC, and FIC cells are mapped from the next cell of the EAC in an increasing order of the cell index as shown in (b). 
     After FIC mapping is completed, one or more DPs are mapped, followed by auxiliary streams, if any, and dummy cells. 
       FIG. 20  illustrates a type of DP according to an embodiment of the present invention. 
     (a) shows type 1 DP and (b) shows type 2 DP. 
     After the preceding channels, i.e., PLS, EAC and FIC, are mapped, cells of the DPs are mapped. A DP is categorized into one of two types according to mapping method: 
     Type 1 DP: DP is mapped by TDM 
     Type 2 DP: DP is mapped by FDM 
     The type of DP is indicated by DP_TYPE field in the static part of PLS2.  FIG. 20  illustrates the mapping orders of Type 1 DPs and Type 2 DPs. Type 1 DPs are first mapped in the increasing order of cell index, and then after reaching the last cell index, the symbol index is increased by one. Within the next symbol, the DP continues to be mapped in the increasing order of cell index starting from p=0. With a number of DPs mapped together in one frame, each of the Type 1 DPs are grouped in time, similar to TDM multiplexing of DPs. 
     Type 2 DPs are first mapped in the increasing order of symbol index, and then after reaching the last OFDM symbol of the frame, the cell index increases by one and the symbol index rolls back to the first available symbol and then increases from that symbol index. After mapping a number of DPs together in one frame, each of the Type 2 DPs are grouped in frequency together, similar to FDM multiplexing of DPs. 
     Type 1 DPs and Type 2 DPs can coexist in a frame if needed with one restriction; Type 1 DPs always precede Type 2 DPs. The total number of OFDM cells carrying Type 1 and Type 2 DPs cannot exceed the total number of OFDM cells available for transmission of DPs: 
         D   DP1   +D   DP2   ≦D   DP    [Math Figure 2]
 
     where D DP1  is the number of OFDM cells occupied by Type 1 DPs, D DP2  is the number of cells occupied by Type 2 DPs. Since PLS, EAC, FIC are all mapped in the same way as Type 1 DP, they all follow “Type 1 mapping rule”. Hence, overall, Type 1 mapping always precedes Type 2 mapping. 
       FIG. 21  illustrates DP mapping according to an embodiment of the present invention. 
     (a) shows an addressing of OFDM cells for mapping type 1 DPs and (b) shows an an addressing of OFDM cells for mapping for type 2 DPs. 
     Addressing of OFDM cells for mapping Type 1 DPs (0, . . . , D DP1 −1) is defined for the active data cells of Type 1 DPs. The addressing scheme defines the order in which the cells from the TIs for each of the Type 1 DPs are allocated to the active data cells. It is also used to signal the locations of the DPs in the dynamic part of the PLS2. 
     Without EAC and FIC, address 0 refers to the cell immediately following the last cell carrying PLS in the last FSS. If EAC is transmitted and FIC is not in the corresponding frame, address 0 refers to the cell immediately following the last cell carrying EAC. If FIC is transmitted in the corresponding frame, address 0 refers to the cell immediately following the last cell carrying FIC. Address 0 for Type 1 DPs can be calculated considering two different cases as shown in (a). In the example in (a), PLS, EAC and FIC are assumed to be all transmitted. Extension to the cases where either or both of EAC and FIC are omitted is straightforward. If there are remaining cells in the FSS after mapping all the cells up to FIC as shown on the left side of (a). 
     Addressing of OFDM cells for mapping Type 2 DPs (0, . . . , D DP2 −1) is defined for the active data cells of Type 2 DPs. The addressing scheme defines the order in which the cells from the TIs for each of the Type 2 DPs are allocated to the active data cells. It is also used to signal the locations of the DPs in the dynamic part of the PLS2. 
     Three slightly different cases are possible as shown in (b). For the first case shown on the left side of (b), cells in the last FSS are available for Type 2 DP mapping. For the second case shown in the middle, FIC occupies cells of a normal symbol, but the number of FIC cells on that symbol is not larger than C FSS . The third case, shown on the right side in (b), is the same as the second case except that the number of FIC cells mapped on that symbol exceeds C FSS . 
     The extension to the case where Type 1 DP(s) precede Type 2 DP(s) is straightforward since PLS, EAC and FIC follow the same “Type 1 mapping rule” as the Type 1 DP(s). 
     A data pipe unit (DPU) is a basic unit for allocating data cells to a DP in a frame. 
     A DPU is defined as a signaling unit for locating DPs in a frame. A Cell Mapper  7010  may map the cells produced by the TIs for each of the DPs. A Time interleaver  5050  outputs a series of TI-blocks and each TI-block comprises a variable number of XFECBLOCKs which is in turn composed of a set of cells. The number of cells in an XFECBLOCK, N cells , is dependent on the FECBLOCK size, N ldpc , and the number of transmitted bits per constellation symbol. A DPU is defined as the greatest common divisor of all possible values of the number of cells in a XFECBLOCK, N cells , supported in a given PHY profile. The length of a DPU in cells is defined as L DPU . Since each PHY profile supports different combinations of FECBLOCK size and a different number of bits per constellation symbol, L DPU  is defined on a PHY profile basis. 
       FIG. 22  illustrates an FEC structure according to an embodiment of the present invention. 
       FIG. 22  illustrates an FEC structure according to an embodiment of the present invention before bit interleaving. As above mentioned, Data FEC encoder may perform the FEC encoding on the input BBF to generate FECBLOCK procedure using outer coding (BCH), and inner coding (LDPC). The illustrated FEC structure corresponds to the FECBLOCK. Also, the FECBLOCK and the FEC structure have same value corresponding to a length of LDPC codeword. 
     The BCH encoding is applied to each BBF (K bch  bits), and then LDPC encoding is applied to BCH-encoded BBF (K ldpc  bits=N bch  bits) as illustrated in  FIG. 22 . 
     The value of N ldpc  is either 64800 bits (long FECBLOCK) or 16200 bits (short FECBLOCK). 
     The below table 28 and table 29 show FEC encoding parameters for a long FECBLOCK and a short FECBLOCK, respectively. 
     
       
         
           
               
               
               
               
               
               
             
               
                 TABLE 28 
               
               
                   
               
               
                   
                   
                   
                   
                 BCH error 
                   
               
               
                 LDPC 
                   
                   
                   
                 correction 
               
               
                 Rate 
                 N ldpc   
                 K ldpc   
                 K bch   
                 capability 
                 N bch  − K bch   
               
               
                   
               
             
            
               
                 5/15 
                 64800 
                 21600 
                 21408 
                 12 
                 192 
               
               
                 6/15 
                   
                 25920 
                 25728 
               
               
                 7/15 
                   
                 30240 
                 30048 
               
               
                 8/15 
                   
                 34560 
                 34368 
               
               
                 9/15 
                   
                 38880 
                 38688 
               
               
                 10/15  
                   
                 43200 
                 43008 
               
               
                 11/15  
                   
                 47520 
                 47328 
               
               
                 12/15  
                   
                 51840 
                 51648 
               
               
                 13/15  
                   
                 56160 
                 55968 
               
               
                   
               
            
           
         
       
     
     
       
         
           
               
               
               
               
               
               
             
               
                 TABLE 29 
               
               
                   
               
               
                   
                   
                   
                   
                 BCH error 
                   
               
               
                 LDPC 
                   
                   
                   
                 correction 
               
               
                 Rate 
                 N ldpc   
                 K ldpc   
                 K bch   
                 capability 
                 N bch  − K bch   
               
               
                   
               
             
            
               
                   
               
            
           
           
               
               
               
               
               
               
            
               
                 5/15 
                 16200 
                 5400 
                 5232 
                 12 
                 168 
               
               
                 6/15 
                   
                 6480 
                 6312 
               
               
                 7/15 
                   
                 7560 
                 7392 
               
               
                 8/15 
                   
                 8640 
                 8472 
               
               
                 9/15 
                   
                 9720 
                 9552 
               
               
                 10/15  
                   
                 10800 
                 10632 
               
               
                 11/15  
                   
                 11880 
                 11712 
               
               
                 12/15  
                   
                 12960 
                 12792 
               
               
                 13/15  
                   
                 14040 
                 13872 
               
               
                   
               
            
           
         
       
     
     The details of operations of the BCH encoding and LDPC encoding are as follows: 
     A 12-error correcting BCH code is used for outer encoding of the BBF. The BCH generator polynomial for short FECBLOCK and long FECBLOCK are obtained by multiplying together all polynomials. 
     LDPC code is used to encode the output of the outer BCH encoding. To generate a completed B ldpc  (FECBLOCK), P ldpc  (parity bits) is encoded systematically from each I ldpc  (BCH-encoded BBF), and appended to I ldpc . The completed B ldpc  (FECBLOCK) are expressed as follow Math figure. 
         B   ldpc   =[I   ldpc    P   ldpc   ]=[i   0   ,i   1   , . . . , i   K     ldpc     −1   , p   0   ,p   1   , . . . , p   N     ldpc     −K     ldpc     −1 ]  [Math Figure 3]
 
     The parameters for long FECBLOCK and short FECBLOCK are given in the above table 28 and 29, respectively. 
     The detailed procedure to calculate N ldpc −K ldpc  parity bits for long FECBLOCK, is as follows: 
     1) Initialize the parity bits, 
         p   0   =p   1   =p   2   = . . . =p   N     ldpc     −K     ldpc     −1 =0   [Math Figure 4]
 
     2) Accumulate the first information bit—i 0 , at parity bit addresses specified in the first row of an addresses of parity check matrix. The details of addresses of parity check matrix will be described later. For example, for rate 13/15: 
     
       
      
       p 
       983 
       =p 
       983 
       ⊕i 
       0  
       p 
       2815 
       =p 
       2815 
       ⊕i 
       0  
      
     
     
       
      
       p 
       4837 
       =p 
       4837 
       ⊕i 
       0  
       p 
       4989 
       =p 
       4989 
       ⊕i 
       0  
      
     
     
       
      
       p 
       6138 
       =p 
       6138 
       ⊕i 
       0  
       p 
       6458 
       =p 
       6458 
       ⊕i 
       0  
      
     
     
       
      
       p 
       6921 
       =p 
       6921 
       ⊕i 
       0  
       p 
       6974 
       =p 
       6974 
       ⊕i 
       0  
      
     
     
       
      
       p 
       7572 
       =p 
       7572 
       ⊕i 
       0  
       p 
       8260 
       =p 
       8260 
       ⊕i 
       0  
      
     
         p   8496   =p   8496   ⊕i   0    [Math Figure 5]
 
     3) For the next 359 information bits, i s , s=1, 2, . . . , 359 accumulate i s  at parity bit addresses using following Math figure. 
       {x+(s mod 360)×Q ldpc }mod(N ldpc −K ldpc )   [Math Figure 6]
 
     where x denotes the address of the parity bit accumulator corresponding to the first bit i 0 , and Q ldpc  is a code rate dependent constant specified in the addresses of parity check matrix. Continuing with the example, Q ldpc =24 for rate 13/15, so for information bit i 1 , the following operations are performed: 
     
       
      
       p 
       1007 
       =p 
       1007 
       ⊕i 
       1  
       p 
       2839 
       =p 
       2839 
       ⊕i 
       1  
      
     
     
       
      
       p 
       4861 
       =p 
       4861 
       ⊕i 
       1  
       p 
       5013 
       =p 
       5013 
       ⊕i 
       1  
      
     
     
       
      
       p 
       6162 
       =p 
       6162 
       ⊕i 
       1  
       p 
       6482 
       =p 
       6482 
       ⊕i 
       1  
      
     
     
       
      
       p 
       6945 
       =p 
       6945 
       ⊕i 
       1  
       p 
       6998 
       =p 
       6998 
       ⊕i 
       1  
      
     
     
       
      
       p 
       7596 
       =p 
       7596 
       ⊕i 
       1  
       p 
       8284 
       =p 
       8284 
       ⊕i 
       1  
      
     
         p   8520   =p   8520   ⊕i   1    [Math Figure 7]
 
     4) For the 361 st  information bit i 360 , the addresses of the parity bit accumulators are given in the second row of the addresses of parity check matrix. In a similar manner the addresses of the parity bit accumulators for the following 359 information bits i s , s=361, 362, . . . , 719 are obtained using the Math figure 6, where x denotes the address of the parity bit accumulator corresponding to the information bit i 360 , i.e., the entries in the second row of the addresses of parity check matrix. 
     5) In a similar manner, for every group of 360 new information bits, a new row from addresses of parity check matrixes used to find the addresses of the parity bit accumulators. 
     After all of the information bits are exhausted, the final parity bits are obtained as follows: 
     6) Sequentially perform the following operations starting with i=1 
         p   i   =p   i   ⊕p   i−1   , i= 1,2, . . . ,  N   ldpc   −K   ldpc −1   [Math Figure 8]
 
     where final content of p i , i=0, 1, . . . , N ldpc −K ldpc −1 is equal to the parity bit p i . 
     
       
         
           
               
               
               
             
               
                   
                 TABLE 30 
               
               
                   
                   
               
               
                   
                 Code Rate 
                 Q ldpc   
               
               
                   
                   
               
             
            
               
                   
               
            
           
           
               
               
               
            
               
                   
                 5/15 
                 120 
               
               
                   
                 6/15 
                 108 
               
               
                   
                 7/15 
                 96 
               
               
                   
                 8/15 
                 84 
               
               
                   
                 9/15 
                 72 
               
               
                   
                 10/15  
                 60 
               
               
                   
                 11/15  
                 48 
               
               
                   
                 12/15  
                 36 
               
               
                   
                 13/15  
                 24 
               
               
                   
                   
               
            
           
         
       
     
     This LDPC encoding procedure for a short FECBLOCK is in accordance with t LDPC encoding procedure for the long FECBLOCK, except replacing the table 30 with table 31, and replacing the addresses of parity check matrix for the long FECBLOCK with the addresses of parity check matrix for the short FECBLOCK. 
     
       
         
           
               
               
               
             
               
                   
                 TABLE 31 
               
               
                   
                   
               
               
                   
                 Code Rate 
                 Q ldpc   
               
               
                   
                   
               
             
            
               
                   
               
            
           
           
               
               
               
            
               
                   
                 5/15 
                 30 
               
               
                   
                 6/15 
                 27 
               
               
                   
                 7/15 
                 24 
               
               
                   
                 8/15 
                 21 
               
               
                   
                 9/15 
                 18 
               
               
                   
                 10/15  
                 15 
               
               
                   
                 11/15  
                 12 
               
               
                   
                 12/15  
                 9 
               
               
                   
                 13/15  
                 6 
               
               
                   
                   
               
            
           
         
       
     
       FIG. 23  illustrates a bit interleaving according to an embodiment of the present invention. 
     The outputs of the LDPC encoder are bit-interleaved, which consists of parity interleaving followed by Quasi-Cyclic Block (QCB) interleaving and inner-group interleaving. 
     (a) shows Quasi-Cyclic Block (QCB) interleaving and (b) shows inner-group interleaving. 
     The FECBLOCK may be parity interleaved. At the output of the parity interleaving, the LDPC codeword consists of 180 adjacent QC blocks in a long FECBLOCK and 45 adjacent QC blocks in a short FECBLOCK. Each QC block in either a long or short FECBLOCK consists of 360 bits. The parity interleaved LDPC codeword is interleaved by QCB interleaving. The unit of QCB interleaving is a QC block. The QC blocks at the output of parity interleaving are permutated by QCB interleaving as illustrated in  FIG. 23 , where N cells =64800/η mod  or 16200/η mod  according to the FECBLOCK length. The QCB interleaving pattern is unique to each combination of modulation type and LDPC code rate. 
     After QCB interleaving, inner-group interleaving is performed according to modulation type and order (η mod ) which is defined in the below table 32. The number of QC blocks for one inner-group, N QCB   _   IG , is also defined. 
     
       
         
           
               
               
               
               
             
               
                   
                 TABLE 32 
               
               
                   
                   
               
               
                   
                 Modulation type 
                 η mod   
                 N QCB     —     IG   
               
               
                   
                   
               
             
            
               
                   
               
            
           
           
               
               
               
               
            
               
                   
                 QAM-16 
                 4 
                 2 
               
               
                   
                 NUC-16 
                 4 
                 4 
               
               
                   
                 NUQ-64 
                 6 
                 3 
               
               
                   
                 NUC-64 
                 6 
                 6 
               
               
                   
                 NUQ-256 
                 8 
                 4 
               
               
                   
                 NUC-256 
                 8 
                 8 
               
               
                   
                 NUQ-1024 
                 10 
                 5 
               
               
                   
                 NUC-1024 
                 10 
                 10 
               
               
                   
                   
               
            
           
         
       
     
     The inner-group interleaving process is performed with N QCB   _   IG  QC blocks of the QCB interleaving output. Inner-group interleaving has a process of writing and reading the bits of the inner-group using 360 columns and N QCB   _   IG  rows. In the write operation, the bits from the QCB interleaving output are written row-wise. The read operation is performed column-wise to read out m bits from each row, where m is equal to 1 for NUC and 2 for NUQ. 
       FIG. 24  illustrates a cell-word demultiplexing according to an embodiment of the present invention. 
     (a) shows a cell-word demultiplexing for 8 and 12 bpcu MIMO and (b) shows a cell-word demultiplexing for 10 bpcu MIMO. 
     Each cell word (c 0,l , c 1,l , . . . , c nmod-1,l ) of the bit interleaving output is demultiplexed into (d 1,0,m , d 1,1,m  . . . , d 1,nmod-1,m ) and (d 2,0,m , d 2,1,m  . . . d 2,nmod-1,m ) as shown in (a), which describes the cell-word demultiplexing process for one XFECBLOCK. 
     For the 10 bpcu MIMO case using different types of NUQ for MIMO encoding, the Bit Interleaver for NUQ-1024 is re-used. Each cell word (c 0,l , c 1,l , . . . , c 9,l ) of the Bit Interleaver output is demultiplexed into (d 1,0,m , d 1,1,m  . . . , d 1,3,m ) and (d 2,0,m , d 2,1,m  . . . , d 2,5,m ), as shown in (b). 
       FIG. 25  illustrates a time interleaving according to an embodiment of the present invention. 
     (a) to (c) show examples of TI mode. 
     The time interleaver operates at the DP level. The parameters of time interleaving (TI) may be set differently for each DP. 
     The following parameters, which appear in part of the PLS2-STAT data, configure the TI: 
     DP_TI_TYPE (allowed values: 0 or 1): Represents the TI mode; ‘0’ indicates the mode with multiple TI blocks (more than one TI block) per TI group. In this case, one TI group is directly mapped to one frame (no inter-frame interleaving). ‘1’ indicates the mode with only one TI block per TI group. In this case, the TI block may be spread over more than one frame (inter-frame interleaving). 
     DP_TI_LENGTH: If DP_TI_TYPE=‘0’, this parameter is the number of TI blocks N TI  per TI group. For DP_TI_TYPE=‘1’, this parameter is the number of frames P I  spread from one TI group. 
     DP_NUM_BLOCK_MAX (allowed values: 0 to 1023): Represents the maximum number of XFECBLOCKs per TI group. 
     DP_FRAME_INTERVAL (allowed values: 1, 2, 4, 8): Represents the number of the frames I JUMP  between two successive frames carrying the same DP of a given PHY profile. 
     DP_TI_BYPASS (allowed values: 0 or 1): If time interleaving is not used for a DP, this parameter is set to ‘1’. It is set to ‘0’ if time interleaving is used. 
     Additionally, the parameter DP_NUM_BLOCK from the PLS2-DYN data is used to represent the number of XFECBLOCKs carried by one TI group of the DP. 
     When time interleaving is not used for a DP, the following TI group, time interleaving operation, and TI mode are not considered. However, the Delay Compensation block for the dynamic configuration information from the scheduler will still be required. In each DP, the XFECBLOCKs received from the SSD/MIMO encoding are grouped into TI groups. That is, each TI group is a set of an integer number of XFECBLOCKs and will contain a dynamically variable number of XFECBLOCKs. The number of XFECBLOCKs in the TI group of index n is denoted by N xBLocK   _   Group (n) and is signaled as DP_NUM_BLOCK in the PLS2-DYN data. Note that N xBLocK   _   Group (n) may vary from the minimum value of 0 to the maximum value N xBLOCK   _   Group   _   MAX  (corresponding to DP_NUM_BLOCK_MAX) of which the largest value is 1023. 
     Each TI group is either mapped directly onto one frame or spread over P I  frames. Each TI group is also divided into more than one TI blocks (N TI ), where each TI block corresponds to one usage of time interleaver memory. The TI blocks within the TI group may contain slightly different numbers of XFECBLOCKs. If the TI group is divided into multiple TI blocks, it is directly mapped to only one frame. There are three options for time interleaving (except the extra option of skipping the time interleaving) as shown in the below table 33. 
     
       
         
           
               
               
             
               
                 TABLE 33 
               
               
                   
               
               
                 Modes 
                 Descriptions 
               
               
                   
               
             
            
               
                 Option-1 
                 Each TI group contains one TI block and is mapped directly to one 
               
               
                   
                 frame as shown in (a). This option is signaled in the PLS2-STAT by 
               
               
                   
                 DP_TI_TYPE = ‘0’ and DP_TI_LENGTH = ‘1’(N TI  = 1). 
               
               
                 Option-2 
                 Each TI group contains one TI block and is mapped to more than 
               
               
                   
                 one frame. (b) shows an example, where one TI group is mapped to 
               
               
                   
                 two frames, i.e., DP_TI_LENGTH = ‘2’ (P I  = 2) and DP_FRAME_INTERVAL 
               
               
                   
                 (I JUMP  = 2). This provides greater time diversity for low data-rate 
               
               
                   
                 services. This option is signaled in the PLS2-STAT by DP_TI_TYPE = ‘1’. 
               
               
                 Option-3 
                 Each TI group is divided into multiple TI blocks and is mapped 
               
               
                   
                 directly to one frame as shown in (c). Each TI block may use full TI 
               
               
                   
                 memory, so as to provide the maximum bit-rate for a DP. This option 
               
               
                   
                 is signaled in the PLS2-STAT signaling by DP_TI_TYPE = ‘0’ and 
               
               
                   
                 DP_TI_LENGTH = N TI , while P I  = 1. 
               
               
                   
               
            
           
         
       
     
     In each DP, the TI memory stores the input XFECBLOCKs (output XFECBLOCKs from the SSD/MIMO encoding block). Assume that input XFECBLOCKs are defined as 
       (d n,s,0,0 ,d n,s,0,1 , . . . , d n,s,0,N     cells     −1 ,d n,s,1,0 ,d n,s,1,N     cells     −1 , . . . , d n,s,N     xBLOCK—TI     (n,s)−1,0 , . . . , d n,s,N     xBLOCK—TI     (n,s)−1,N     cells     −1 ), 
     where d n,s,r,q  is the qth cell of the rth XFECBLOCK in the sth TI block of the nth TI group and represents the outputs of SSD and MIMO encodings as follows. 
     
       
         
           
             
               d 
               
                 n 
                 , 
                 s 
                 , 
                 r 
                 , 
                 q 
               
             
             = 
             
               { 
               
                 
                   
                     
                       
                         
                           f 
                           
                             n 
                             , 
                             s 
                             , 
                             r 
                             , 
                             q 
                           
                         
                         , 
                       
                     
                     
                       
                         the 
                          
                         
                             
                         
                          
                         output 
                          
                         
                             
                         
                          
                         of 
                          
                         
                             
                         
                          
                         SSD⋯ 
                          
                         
                             
                         
                          
                         encoding 
                       
                     
                   
                   
                     
                       
                         
                           g 
                           
                             n 
                             , 
                             s 
                             , 
                             r 
                             , 
                             q 
                           
                         
                         , 
                       
                     
                     
                       
                         the 
                          
                         
                             
                         
                          
                         output 
                          
                         
                             
                         
                          
                         of 
                          
                         
                             
                         
                          
                         MIMO 
                          
                         
                             
                         
                          
                         encoding 
                       
                     
                   
                 
                 . 
               
             
           
         
       
     
     In addition, assume that output XFECBLOCKs from the time interleaver are defined as 
       (h n,s,0 ,h n,s,1 , . . . , h n,s,i , . . . , h n,s,N     xBLOCK—TI     (n,s)×N     cells     −1 ) 
     where h n,s,i  is the ith output cell (for i=0, . . . , N xBLOCK   _   TI (n,s)×N cells −1) in the sth TI block of the nth TI group. 
     Typically, the time interleaver will also act as a buffer for DP data prior to the process of frame building. This is achieved by means of two memory banks for each DP. The first TI-block is written to the first bank. The second TI-block is written to the second bank while the first bank is being read from and so on. 
     The TI is a twisted row-column block interleaver. For the sth TI block of the nth TI group, the number of rows N r  of a TI memory is equal to the number of cells N cells , i.e., N r =N cells  while the number of columns N c  is equal to the number N xBLOCK   _   TI (n,s). 
       FIG. 26  illustrates the basic operation of a twisted row-column block interleaver according to an embodiment of the present invention. 
     shows a writing operation in the time interleaver and (b) shows a reading operation in the time interleaver The first XFECBLOCK is written column-wise into the first column of the TI memory, and the second XFECBLOCK is written into the next column, and so on as shown in (a). Then, in the interleaving array, cells are read out diagonal-wise. During diagonal-wise reading from the first row (rightwards along the row beginning with the left-most column) to the last row, N r  cells are read out as shown in (b). In detail, assuming z n,s,i (i=0, . . . , N r N c ) as the TI memory cell position to be read sequentially, the reading process in such an interleaving array is performed by calculating the row index the R n,s,i , the column index C n,s,i , and the associated twisting parameter T n,s,i  as follows expression. 
     
       
         
           
             
               
                 
                   
                     GENERATE 
                      
                     
                       ( 
                       
                         
                           R 
                           
                             n 
                             , 
                             s 
                             , 
                             i 
                           
                         
                         , 
                         
                           C 
                           
                             n 
                             , 
                             s 
                             , 
                             i 
                           
                         
                       
                       ) 
                     
                   
                   = 
                   
                     
 
                   
                    
                   
                     { 
                     
                       
 
                     
                      
                     
                       
                         
                           R 
                           
                             n 
                             , 
                             s 
                             , 
                             i 
                           
                         
                         = 
                         
                           mod 
                            
                           
                             ( 
                             
                               i 
                               , 
                               
                                 N 
                                 r 
                               
                             
                             ) 
                           
                         
                       
                       , 
                       
                         
 
                       
                        
                       
                         
                           T 
                           
                             n 
                             , 
                             s 
                             , 
                             i 
                           
                         
                         = 
                         
                           mod 
                            
                           
                             ( 
                             
                               
                                 
                                   S 
                                   shift 
                                 
                                 × 
                                 
                                   R 
                                   
                                     n 
                                     , 
                                     s 
                                     , 
                                     i 
                                   
                                 
                               
                               , 
                               
                                 N 
                                 c 
                               
                             
                             ) 
                           
                         
                       
                       , 
                       
                         
 
                       
                        
                       
                         
                           C 
                           
                             n 
                             , 
                             s 
                             , 
                             i 
                           
                         
                         = 
                         
                           mod 
                            
                           
                             ( 
                             
                               
                                 
                                   T 
                                   
                                     n 
                                     , 
                                     s 
                                     , 
                                     i 
                                   
                                 
                                 + 
                                 
                                   ⌊ 
                                   
                                     i 
                                     
                                       N 
                                       r 
                                     
                                   
                                   ⌋ 
                                 
                               
                               , 
                               
                                 N 
                                 c 
                               
                             
                             ) 
                           
                         
                       
                     
                      
                     
                       
 
                     
                     } 
                   
                 
               
               
                 
                   [ 
                   
                     Math 
                      
                     
                         
                     
                      
                     
                       FIG 
                       . 
                       
                           
                       
                        
                       9 
                     
                   
                   ] 
                 
               
             
           
         
       
     
     where S shift  is a common shift value for the diagonal-wise reading process regardless of N xBLOCK   _   TI (n,s), and it is determined by N xBLOCK   _   TI   _   MAX  given in the PLS2-STAT as follows expression. 
     
       
         
           
             
               
                 
                   for 
                    
                   
                     { 
                     
                       
                         
                           
                             
                               
                                 
                                   N 
                                   
                                     
                                       xBLOCK 
                                       — 
                                     
                                      
                                     
                                       TI 
                                       — 
                                     
                                      
                                     MAX 
                                   
                                   ′ 
                                 
                                 = 
                                 
                                   
                                     N 
                                     
                                       
                                         xBLOCK 
                                         — 
                                       
                                        
                                       
                                         TI 
                                         — 
                                       
                                        
                                       MAX 
                                     
                                   
                                   + 
                                   1 
                                 
                               
                               , 
                             
                           
                           
                             
                               
                                 if 
                                  
                                 
                                     
                                 
                                  
                                 
                                   N 
                                   
                                     
                                       xBLOCK 
                                       — 
                                     
                                      
                                     
                                       TI 
                                       — 
                                     
                                      
                                     MAX 
                                   
                                 
                                  
                                 mod 
                                  
                                 
                                     
                                 
                                  
                                 2 
                               
                               = 
                               0 
                             
                           
                         
                         
                           
                             
                               
                                 
                                   N 
                                   
                                     
                                       xBLOCK 
                                       — 
                                     
                                      
                                     
                                       TI 
                                       — 
                                     
                                      
                                     MAX 
                                   
                                   ′ 
                                 
                                 = 
                                 
                                   N 
                                   
                                     
                                       xBLOCK 
                                       — 
                                     
                                      
                                     
                                       TI 
                                       — 
                                     
                                      
                                     MAX 
                                   
                                 
                               
                               , 
                             
                           
                           
                             
                               
                                 if 
                                  
                                 
                                     
                                 
                                  
                                 
                                   N 
                                   
                                     
                                       xBLOCK 
                                       — 
                                     
                                      
                                     
                                       TI 
                                       — 
                                     
                                      
                                     MAX 
                                   
                                 
                                  
                                 mod 
                                  
                                 
                                     
                                 
                                  
                                 2 
                               
                               = 
                               1 
                             
                           
                         
                       
                       , 
                       
                         
 
                       
                        
                       
                         
                           S 
                           shift 
                         
                         = 
                         
                           
                             
                               N 
                               
                                 
                                   xBLOCK 
                                   — 
                                 
                                  
                                 
                                   TI 
                                   — 
                                 
                                  
                                 MAX 
                               
                               ′ 
                             
                             - 
                             1 
                           
                           2 
                         
                       
                     
                   
                 
               
               
                 
                   [ 
                   
                     Math 
                      
                     
                         
                     
                      
                     
                       FIG 
                       . 
                       
                           
                       
                        
                       10 
                     
                   
                   ] 
                 
               
             
           
         
       
     
     As a result, the cell positions to be read are calculated by a coordinate as z n,s,i =N r C n,s,i +R n,s,i . 
       FIG. 27  illustrates an operation of a twisted row-column block interleaver according to another embodiment of the present invention. 
     More specifically,  FIG. 27  illustrates the interleaving array in the TI memory for each TI group, including virtual XFECBLOCKs when N xBLOCK   _   TI (0,0)=3, N xBLOCK   _   TI (1,0)=6, N xBLOCK   _   TI (2,0)=5. 
     The variable number N xBLOCK   _   TI (n,s)=N r  will be less than or equal to N′ xBLOCK   _   TI   _   MAX . Thus, in order to achieve a single-memory deinterleaving at the receiver side, regardless of N xBLOCK   _   TI (n,s), the interleaving array for use in a twisted row-column block interleaver is set to the size of N r ×N c =N cells ×N′ xBLOCK   _   TI   _   MAX  by inserting the virtual XFECBLOCKs into the TI memory and the reading process is accomplished as follow expression. 
     
       
         
           
               
             
               
                   
               
               
                 [Math FIG. 11] 
               
               
                   
               
             
            
               
                   
               
            
           
           
               
               
            
               
                   
                 p = 0; 
               
               
                   
                 for i = 0;i &lt; N cells N xBLOCK     —     TI     —     MAX   ′ ;i = i + 1 
               
               
                   
                 {GENERATE (R n,s,i , C n,s,i ); 
               
               
                   
                 V i  = N r C n,s,j  + R n,s,j   
               
            
           
           
               
               
            
               
                   
                 if V i  &lt; N cells N xBLOCK     —     TI  (n,s) 
               
               
                   
                 { 
               
            
           
           
               
               
            
               
                   
                 Z n,s,p  = V i ; p = p + 1; 
               
               
                   
                 } 
               
            
           
           
               
               
            
               
                   
                 } 
               
               
                   
                   
               
            
           
         
       
     
     The number of TI groups is set to 3. The option of time interleaver is signaled in the PLS2-STAT data by DP_TI_TYPE=‘0’, DP_FRAME_INTERVAL=‘1’, and DP_TI_LENGTH=‘1’, i.e.,N TI =1, I JUMP =1, and P I =1. The number of XFECBLOCKs, each of which has N cells =30 cells, per TI group is signaled in the PLS2-DYN data by N xBLOCK   _   TI (0,0)=3, N xBLOCK   _   TI (1,0)=6, and N xBLOCK   _   TI (2,0)=5, respectively. The maximum number of XFECBLOCK is signaled in the PLS2-STAT data by N xBLOCK   _   Group   _   MAX , which leads to └N xBLOCK   _   Group   _   MAX /N TI ┘=N xBLOCK   _   TI   _   MAX =6. 
       FIG. 28  illustrates a diagonal-wise reading pattern of a twisted row-column block interleaver according to an embodiment of the present invention. 
     More specifically  FIG. 28  shows a diagonal-wise reading pattern from each interleaving array with parameters of N′ xBLOCK   _   TI   _   MAX =7 and S shift =(7−1)/2=3. Note that in the reading process shown as pseudocode above, if V i ≧N cells N xBLOCK   _   TI (n,s), the value of V I  is skipped and the next calculated value of V I  is used. 
       FIG. 29  illustrates interlaved XFECBLOCKs from each interleaving array according to an embodiment of the present invention. 
       FIG. 29  illustrates the interleaved XFECBLOCKs from each interleaving array with parameters of N′ xBLOCK   _   TI   _   MAX =7 and S shift =3. 
       FIG. 30  is a view of a protocol stack for supporting a broadcast service according to an embodiment of the present invention. 
     The broadcast service may provide enhanced services, for example, audio/video (A/V) data and HTML5 application, interactive service, ACR service, second screen service, and personalization service. 
     Such a broadcast service may be transmitted through a physical layer (i.e., broadcast signal) such as terrestrial wave and a cable satellite. Additionally, a broadcast service according to an embodiment of the present invention may be transmitted through an internet communication network (e.g., broadband). 
     When the broadcast service is transmitted through a physical layer, i.e., a broadcast signal such as terrestrial wave and a cable satellite, a broadcast reception device may extract a fast information channel and an encapsulated IP datagram by demodulating the broadcast signal. The broadcast reception device may extract a user datagram protocol (UDP) datagram from the IP datagram. The broadcast reception device may extract signaling information from the UDP datagram. Additionally, the broadcast reception device may extract an Asynchronous Layered Coding/Layered Coding Transport (ALC/LCT) packet from the UDP datagram. The broadcast reception device may extract signaling information from the ALC/LCT packet. The broadcast reception device may extract a File Delivery over Unidirectional Transport (FLUTE) packet from the ALC/LCT packet. At this point, the FLUTE packet may include Non-Real Time (NRT) data and Electronic Service Guide (ESG) data. Additionally, According to a specific embodiment of the present invention, a broadcast transmission device may transmit real-time data, for example, AV data and enhanced data, through the ALC/LCT packet and the FLUTE packet, and a broadcast reception device may extract real-time data from the ALC/LCT packet and the FLUTE packet. Additionally, the broadcast reception device may extract a Real-time Transport Protocol (RTCP) packet and an RTP Control Protocol (RTCP) packet from the UDP datagram. The broadcast reception device may extract A/V data and enhanced data from the RTP/RTCP packet. 
     When the broadcast service is transmitted through an internet communication network (e.g., broadband), the broadcast reception device may receive an IP packet from the internet communication network. The broadcast reception device may extract a TCP packet from the IP packet. The broadcast reception device may extract an HTTP packet from the TCP packet. The broadcast reception device may extract A/V data, enhanced data, and signaling information from the HTTP packet. 
     A detailed transmission frame and transport packet transmitting broadcast service will be described with reference to  FIGS. 31 to 34 . 
       FIG. 31  is a view illustrating a broadcast transmission frame according to an embodiment of the present invention. 
     According to the embodiment of  FIG. 31 , the broadcast transmission frame includes a P1 part, an L1 part, a common PLP part, an interleaved PLP part (e.g., a scheduled &amp; interleaved PLP&#39;s part), and an auxiliary data part. 
     According to the embodiment of  FIG. 31 , the broadcast transmission device transmits information on transport signal detection through the P1 part of the transmission frame. Additionally, the broadcast transmission device may transmit turning information on broadcast signal tuning through the P1 part. 
     According to the embodiment of  FIG. 31 , the broadcast transmission device transmits a configuration of the broadcast transmission frame and characteristics of each PLP through the L1 part. At this pint, the broadcast reception device  100  decodes the L1 part on the basis of the P1 part to obtain the configuration of the broadcast transmission frame and the characteristics of each PLP. 
     According to the embodiment of  FIG. 31 , the broadcast transmission device may transmit information commonly applied to PLPs through the common PLP part. According to a specific embodiment of the present invention, the broadcast transmission frame may not include the common PLP part. 
     According to the embodiment of  FIG. 31 , the broadcast transmission device transmits a plurality of components included in broadcast service through an interleaved PLP part. At this point, the interleaved PLP part includes a plurality of PLPs. 
     Moreover, according to the embodiment of  FIG. 31 , the broadcast transmission device may signal to which PLP components configuring each broadcast service are transmitted through an L1 part or a common PLP part. However, the broadcast reception device  100  decodes all of a plurality of PLPs of an interleaved PLP part in order to obtain specific broadcast service information on broadcast service scan. 
     Unlike the embodiment of  FIG. 31 , the broadcast transmission device may transmit a broadcast transmission frame including a broadcast service transmitted through a broadcast transmission frame and an additional part that includes information on a component included in the broadcast service. At this point, the broadcast reception device  100  may instantly obtain information on the broadcast service and the components therein through the additional part. This will be described with reference to  FIG. 32 . 
       FIG. 32  is a view of a broadcast transmission frame according to another embodiment of the present invention. 
     According to the embodiment of  FIG. 32 , the broadcast transmission frame includes a P1 part, an L1 part, a fast information channel (FIC) part, an interleaved PLP part (e.g., a scheduled &amp; interleaved PLP&#39;s part), and an auxiliary data part. 
     Except the FIC part, other parts are identical to those of  FIG. 31 . 
     The broadcast transmission device transmits fast information through the FIC part. The fast information may include configuration information of a broadcast stream transmitted through a transmission frame, simple broadcast service information, and component information. The broadcast reception device  100  may scan broadcast service on the basis of the FIC part. In more detail, the broadcast reception device  100  may extract information on broadcast service from the FIC part. 
       FIG. 33  is a view illustrating a structure of a transport packet transmitting a broadcast service according to an embodiment of the present invention. 
     In the embodiment of  FIG. 33 , a transport packet transmitting a broadcast service includes a Network Protocol field, an Error Indicator field, a Stuffing Indicator field, a Pointer field, a Stuffing bytes field, and payload data. 
     The Network Protocol field represents the type of a network protocol. According to a specific embodiment of the present invention, a value of the Network Protocol field may represent the IPv4 protocol or a frame packet type. In more detail, as shown in the embodiment of  FIG. 34 , when a value of the Network Protocol field is 000, it may represent the IPv4 protocol. In more detail, as shown in the embodiment of  FIG. 35 , when a value of the Network Protocol field is 111, it may represent a frame_packet_type protocol. At this point, framed_packet_type may be a protocol defined by ATSC A/153. In more detail, framed_packet_type may represent a network packet protocol not including a field representing information on the length. According to a specific embodiment of the present invention, the Network Protocol may be a 3-bit field. 
     The Error Indicator field represents that an error is detected from a corresponding transport packet. In more detail, if a value of the Error Indicator field is 0, it represents that no error is detected from a corresponding packet and if a value of the Error Indicator field is 1, it represents that an error is detected from a corresponding packet According to a specific embodiment of the present invention, the Error Indicator field may be a 1-bit field. 
     The Stuffing Indicator field represents whether stuffing bytes are included in a corresponding transport packet. At this point, the stuffing bytes represent data included in a payload to maintain the length of a fixed packet. According to a specific embodiment of the present invention, when a value of the Stuffing Indicator field is 1, a transport packet includes a stuffing byte and when a value of the Stuffing Indicator field is 0, a transport packet includes no stuffing byte According to a specific embodiment of the present invention, the Stuffing Indicator field may be a 1-bit field. 
     The Pointer field represents a start point of a new network packet in a payload part of a corresponding transport packet. According to a specific embodiment of the present invention, when a value of the Pointer field is 0x7FF, it may represent that there is no start point of a new network packet. Additionally, According to a specific embodiment of the present invention, when a value of the Pointer field is not 0x7FF, it may represent an offset value from the last part of a transport packet header to the start point of a new network packet. According to a specific embodiment of the present invention, the Pointer field may be an 11-bit field. 
     The Stuffing Bytes field represents a stuffing byte filling between the header and the payload data to maintain a fixed packet length. 
     A configuration of a broadcast reception device for receiving broadcast service will be described with reference to 31. 
       FIG. 34  is a view illustrating a configuration of a broadcast reception device according to an embodiment of the present invention. 
     The broadcast reception device  100  of  FIG. 34  includes a broadcast reception unit  110 , an internet protocol (IP) communication unit  130 , and a control unit  150 . 
     The broadcast reception unit  110  includes a channel synchronizer  111 , a channel equalizer  113 , and a channel decoder  115 . 
     The channel synchronizer  111  synchronizes a symbol frequency with a timing in order for decoding in a baseband where a broadcast signal is received. 
     The channel equalizer  113  corrects the distortion of a synchronized broadcast signal. In more detail, the channel equalizer  113  corrects the distortion of a synchronized signal due to multipath and Doppler effects. 
     The channel decoder  115  decodes a distortion corrected broadcast signal. In more detail, the channel decoder  115  extracts a transmission frame from the distortion corrected broadcast signal. At this point, the channel decoder  115  may perform forward error correction (FEC). 
     The IP communication unit  130  receives and transmits data through internet network. 
     The control unit  150  includes a signaling decoder  151 , a transport packet interface  153 , a broadband packet interface  155 , a baseband operation control unit  157 , a common protocol stack  159 , a service map database  161 , a service signaling channel processing buffer and parser  163 , an A/V processor  165 , a broadcast service guide processor  167 , an application processor  169 , and a service guide database  171 . 
     The signaling decoder  151  decodes signaling information of a broadcast signal. 
     The transport packet interface  153  extracts a transport packet from a broadcast signal. At this point, the transport packet interface  153  may extract data such as signaling information or IP datagram from the extracted transport packet. 
     The broadcast packet interface  155  extracts an IP packet from data received from internet network. At this point, the broadcast packet interface  155  may extract an IP datagram including signaling data from the IP packet. 
     The baseband operation control unit  157  controls an operation relating to receiving broadcast information from a baseband. 
     The common protocol stack  159  extracts audio or video from a transport packet. 
     The A/V processor  547  processes audio or video. 
     The service signaling channel processing buffer and parser  163  parses and buffers signaling information that signals broadcast service. In more detail, the service signaling channel processing buffer and parser  163  parses and buffers signaling information that signals broadcast service from the IP datagram. 
     The service map database  165  stores a broadcast service list including information on broadcast services. 
     The service guide processor  167  processes terrestrial broadcast service guide data guiding programs of terrestrial broadcast service. 
     The application processor  169  extracts and processes application related information from a broadcast signal. 
     The serviced guide database  171  stores program information of a broadcast service. 
       FIG. 36  is a view when a broadcast service signaling table and broadcast service transmission path signaling information signal broadcast service and a broadcast service transmission path. 
     The broadcast service signaling table may signal broadcast service information. In more detail, the broadcast service signaling table may signal a media component that broadcast service includes. Additionally, the broadcast service signaling table may signal broadcast service and a transmission path of a media component that the broadcast service includes. For this, the broadcast service signaling table may include broadcast service transmission path signaling information. In the embodiment of  FIG. 36 , the broadcast service signaling table includes information on a plurality of broadcast services. At this point, the broadcast service signaling table includes media component signaling information signaling a plurality of media components respectively included in a plurality of broadcast services. Especially, the broadcast service signaling table includes broadcast service transmission path signaling information signaling transmission paths of a plurality of media components. For example, it is shown that the broadcast reception device  100  may transmit Video 1 in Service 0 through PLP 0 according to the signaling table. Additionally, it is shown that the broadcast reception device  100  may transmit Audio 1 in Service N through internet network according to the signaling table. At this point, the PLP is a series of logical data delivery paths identifiable on a physical layer. The PLP may be also referred to as a data pipe. 
     A broadcast service signaling table will be described with reference to  FIGS. 37 to 42 . 
       FIG. 37  is a view illustrating a broadcast service signaling table according to an embodiment of the present invention. 
     The broadcast service signaling table may include at least one among broadcast service identification information, information representing the current state of a broadcast service, the name of a broadcast service, information representing whether a protection algorithm for broadcast service is applied, category information of a broadcast service, and media component signaling information signaling a media component that a broadcast service includes. The media component signaling information signaling a media component that the broadcast service includes may include information representing whether each media component is essential to a corresponding broadcast service. Additionally, the media component signaling information signaling a media component that the broadcast service includes may include information relating to each component. 
     In more detail, as shown in the embodiment of  FIG. 37 , the broadcast service signaling table may include at least one among a table_id field, section_syntax_indicator field, a private_indicator field, a section_length field, a table_id_extension field, a version_number field, a current_next_indicator field, a section_number field, a last_section_number field, a num_services field, a service_id field, a service_status field, an SP_indicator field, a short_service_name_length field, a short_service_name field, a channel_number field, a service_category field, a num_components field, an essential_component_indicator field, a num_component_level_descriptor field, a component_level_descriptor field, a num_service_level_descriptors field, and a service_level_descriptor field. 
     The table_id field represents an identifier of a broadcast service signaling information table. At this point, a value of the table_id field may be one of reserved id values defined in ATSC N65. According to a specific embodiment of the present invention, the table_id field may be an 8-bit field. 
     The section_syntax_indicator field represents whether the broadcast service signaling information table is a private section table in a long format of MEPG-2 TS standard. According to a specific embodiment of the present invention, the section_syntax_indicator field may be a 1-bit field. 
     The private_indicator field represents whether a current table corresponds to a private section. According to a specific embodiment of the present invention, the private_indicator field may be a 1-bit field. 
     The section_length field represents the length of a section after the section_length field. According to a specific embodiment of the present invention, the section_length field may be a 12-bit field. 
     The table_id extension field represents a value for identifying a broadcast service signaling information table in combination with the table_id field. Especially, the table_id field may include an SMT_protocol_version field representing a protocol version of a service signaling information table. According to a specific embodiment of the present invention, the SMT_protocol_version field may be an 8-bit field. 
     The version_number field represents a version of a service signaling table. The broadcast reception device  100  may determine the availability of a service signaling information table on the basis of a value of the vserion_number field. In more detail, when a value of the version_number field is identical to a version of a previously received service signaling table, the information of the service signaling table may not be used. According to a specific embodiment of the present invention, the version_number field may be a 5-bit field. 
     The current_next_indicator field represents whether information of a broadcast service signaling table is currently available. In more detail, when a value of the current_next_indicator field is 1, it may represent that the information of the broadcast service signaling table is available. Moreover, when a value of the current_next_indicator field is 1, it may represent that the information of the broadcast service signaling table is available next time. According to a specific embodiment of the present invention, the current_next_indicator field may be a 1-bit field. 
     The section_number field represents a current section number. According to a specific embodiment of the present invention, the section_number field may be an 8-bit field. 
     The last_section_number field represents the last section number. When the size of a broadcast service signaling table is large, it may be divided into a plurality of sections and then transmitted. At this point, the broadcast reception device  100  determines whether all sections necessary for a broadcast service signaling table are received on the basis of the section_number field and the last_section_number field. According to a specific embodiment of the present invention, the last_section_number field may be an 8-bit field. 
     The service_id field represents a service identifier for identifying a broadcast service. According to a specific embodiment of the present invention, the service_id field may be a 16-bit field. 
     The service_status field represents the current state of a broadcast service. In more detail, it may represent whether the broadcast service is available currently. According to a specific embodiment of the present invention, when a value of the service_status field is 1, it may represent that the broadcast service is available currently. According to a specific embodiment of the present invention, the broadcast reception device  100  may determine whether to display a corresponding broadcast service in a broadcast service list and a broadcast service guide on the basis of a value of the service_status field. For example, when a corresponding broadcast service is unavailable, the broadcast reception device  100  may not display the corresponding broadcast service in a broadcast service list and a broadcast service guide. According to another specific embodiment of the present invention, the broadcast reception device  100  may limit an access to a corresponding broadcast service on the basis of a value of the service_status field. For example, when a corresponding broadcast service is unavailable, the broadcast reception device  100  may limit an access to a corresponding broadcast service through a channel up/down key. According to a specific embodiment of the present invention, the service_status field may be a 2-bit field. 
     The SP_indicator field may represent whether service protection is applied to at least one component in a corresponding broadcast service. For example, when a value of SP_indicator is 1, it may represent that service protection is applied to at least one component in a corresponding broadcast service. According to a specific embodiment of the present invention, the SP_indicator field may be a 1-bit field. 
     The short_service_name_length field represents the size of the short_service_name field. 
     The short_service_name field represents the name of a broadcast service. In more detail, the short_service_name field may be displayed by summarizing the name of a broadcast service. 
     The channel_number field displays a virtual channel number of a corresponding broadcast service. 
     The service_category field represents a category of a broadcast service. In more detail, the service_category field may represent at least one among TV service, radio service, broadcast service guide, RI service, and emergency alerting. For example, as shown in the embodiment of  FIG. 38 , in the case that a value of the service_category field is 0x01, it represents TV service. In the case that a value of the service_category field is 0x02, it represents radio service. In the case that a value of the service_category field is 0x03, it represents RI service. In the case that a value of the service_category field is 0x08, it represents service guide. In the case that a value of the service_category field is 0x09, it represents emergency alerting. According to a specific embodiment of the present invention, the service_category field may be a 6-bit field. 
     The num_component field represents the number of media components that a corresponding broadcast service includes. According to a specific embodiment of the present invention, the num_component field may be a 5-bit field. 
     The essential_component_indicator field represents whether a corresponding media component is an essential media component essential to a corresponding broadcast service presentation. According to a specific embodiment of the present invention, the essential_component_indicator field may be a 1-bit field. 
     The num_component_level_descriptor field represents the number of component_level_descriptor fields. According to a specific embodiment of the present invention, the num_component_level_descriptor field may be a 4-bit field. 
     The component_level_descriptor field includes an additional property for a corresponding component. 
     The num_service_level_descriptors field represents the number of service_level_descriptor fields. According to a specific embodiment of the present invention, the num_service_level_descriptors field may be a 4-bit field. 
     The service_level_descriptor field includes an additional property for a corresponding service. 
     The service signaling table may further include information on ensemble. When the same Forward Error Correction (FEC) is applied to at least one service and transmitted, the ensemble represents a collection of the at least one service. This will be described in more detail with reference to  FIG. 39 . 
       FIG. 39  is a view of a broadcast service signaling table according to another embodiment of the present invention. 
     In more detail, as shown in the embodiment of  FIG. 39 , the broadcast service signaling table may further include a num_ensemble_level_descriptors field and an ensemble_level_descriptor field. 
     The num_ensemble_level_descriptors field represents the number of ensemble_level_descriptor fields. According to a specific embodiment of the present invention, the num_ensemble_level_descriptors field may be a 4-bit field. 
     The ensemble_level_descriptor field includes an additional property for a corresponding ensemble. 
     Additionally, the service signaling table may further include stream identifier information for identifying a media component. This will be described in more detail with reference to  FIG. 40 . 
       FIG. 40  is a view of a stream identifier descriptor according to another embodiment of the present invention. 
     The stream identifier information includes at least one among a descriptor_tag field, a descriptor_length field, and a component_tag field. 
     The descriptor_tag field represents a descriptor including stream identifier information. According to a specific embodiment of the present invention, the descriptor_tag field may be an 8-bit field. 
     The descriptor_length field represents the length of stream identifier information after a corresponding field. According to a specific embodiment of the present invention, the descriptor_length field may be an 8-bit field. 
     The component_tag field represents a media component identifier for identifying a media component. At this point, the media component identifier may have a different unique value than a media component identifier of another media component on a corresponding signaling information table. According to a specific embodiment of the present invention, the component_tag field may be an 8-bit field. 
     An operation for transmitting/receiving a broadcast service signaling table will be described with reference to  FIGS. 41 and 42 . 
     The above broadcast service table is described as in a bitstream format but according to a specific embodiment of the present invention, a broadcast service table may be in an XML format. 
       FIG. 41  is a view illustrating an operation when a broadcast transmission device transmits a broadcast service signaling table according to an embodiment of the present invention. 
     The broadcast transmission device may include a transmission unit for transmitting a broadcast signals and a control unit for controlling operations of the broadcast transmission unit. 
     The broadcast transmission device obtains broadcast service information through the control unit in operation S 101 . At this point, the broadcast service information is information for describing broadcast service. In more detail, the broadcast service information may include at least one among broadcast service identification information, information representing the current state of a broadcast service, the name of a broadcast service, a channel number of a broadcast service, information representing whether a protection algorithm for broadcast service is applied, category information of a broadcast service, and media component signaling information signaling a media component that a broadcast service includes. The media component signaling information signaling a media component that the broadcast service includes may include information representing whether each media component is essential to a corresponding broadcast service. Additionally, the media component signaling information signaling a media component that the broadcast service includes may include information relating to each component. 
     The broadcast transmission device generates a broadcast service signaling table on the basis of broadcast service information through a control unit in operation S 103 . At this point, the broadcast service signaling table may include the above-mentioned broadcast service information. 
     The broadcast transmission device transmits a broadcast signal including a service signaling table through a transmission unit in operation S 105 . However, according to a specific embodiment of the present invention, a broadcast transmission device may transmit a service signaling table via an IP network through an IP communication unit transmitting/receiving IP data. 
       FIG. 42  is a view illustrating an operation when a broadcast reception device receives a broadcast service signaling table according to an embodiment of the present invention. 
     The broadcast reception device  100  receives a broadcast signal through the broadcast reception unit  110  in operation S 301 . 
     The broadcast reception device  100  obtains a broadcast service signaling table through the control unit  150  on the basis of the broadcast signal in operation S 303 . In more detail, the broadcast reception device  100  may obtain a broadcast service signaling table from the broadcast signal. At this point, as mentioned above, the broadcast service signaling table may include at least one of broadcast service identification information, information representing the current state of a broadcast service, the name of a broadcast service, information representing whether a protection algorithm for broadcast service is applied, category information of a broadcast service, and media component signaling information signaling a media component. The media component signaling information signaling a media component that the broadcast service includes may include information representing whether each media component is essential to a corresponding broadcast service. Additionally, the media component signaling information signaling a media component that the broadcast service includes may include information relating to each component. However, according to a specific embodiment of the present invention, the broadcast reception device  100  may obtain a broadcast service signaling table via an IP network through the IP communication unit  130 . Especially, in the case that the intensity of a broadcast signal is weak or it is difficult to receive a broadcast signal, the broadcast reception device  100  may obtain a broadcast service signaling table via an IP network. 
     The broadcast reception device  100  obtains broadcast service information on the basis of the broadcast service signaling table through the control unit  150  in operation S 305 . At this point, as mentioned above, the broadcast service information may include at least one among broadcast service identification information, information representing the current state of a broadcast service, the name of a broadcast service, a channel number of a broadcast service, information representing whether a protection algorithm for broadcast service is applied, category information of a broadcast service, and media component signaling information signaling a media component that a broadcast service includes. The media component signaling information signaling a media component that the broadcast service includes may include information representing whether each media component is essential to a corresponding broadcast service. Additionally, the media component signaling information signaling a media component that the broadcast service includes may include information relating to each component. 
     The broadcast reception device  100  generates a broadcast service list for storing information on a broadcast service on the basis of the broadcast service information through the control unit  150  in operation S 307 . At this point, the broadcast service list may include broadcast service information that the broadcast reception device  100  obtains. According to a specific embodiment of the present invention, the broadcast reception device  100  may receive a broadcast service on the basis of broadcast service information or a broadcast service list. 
       FIG. 43  is a view illustrating broadcast service transmission path signaling information according to an embodiment of the present invention. 
     The broadcast service transmission path signaling information may include information representing the type of a network transmitting a broadcast service and specific transmission information according to a broadcast transmission type. The type of a network transmitting a broadcast service may be one of a network transmitting a broadcast service through an IP stream that the same broadcaster transmits, a network transmitting a broadcast service through an IP stream that a different broadcaster transmit, a network transmitting a broadcast service through a session based protocol of the same broadcaster, for example, a FLUTE session, a network transmitting a broadcast service through a session based protocol of a different broadcaster, for example, a FLUTE session, a network transmitting a broadcast service through MPEG-2 TS of different broadcasters, a network transmitting a broadcast service through a packet based stream of a different broadcaster, a network transmitting a broadcast service through a packet based stream transmitted from an IP based broadcast network, and a network for obtaining a broadcast service through URL. 
     According to a specific embodiment of the present invention, as shown in  FIG. 43 , the broadcast service transmission path signaling information may include a descriptor_tag field, a description_length field, a delivery_network_type field, and a data_path field. 
     The descriptor_tag field represents that a corresponding descriptor includes transmission path signaling information. According to a specific embodiment of the present invention, the descriptor_tag field may be an 8-bit field. 
     The descriptor_length field represents the length of broadcast service transmission path signaling information after a corresponding field. According to a specific embodiment of the present invention, the descriptor_length field may be an 8-bit field. 
     The delivery_network_type field represents the type of a transmission network transmitting a broadcast service. According to a specific embodiment of the present invention, a value of the delivery_network_type field may represent one of a network transmitting a broadcast service through an IP stream that the same broadcaster transmits, a network transmitting a broadcast service through an IP stream that a different broadcaster transmit, a network transmitting a broadcast service through a session based protocol of the same broadcaster, for example, a FLUTE session, a network transmitting a broadcast service through a session based protocol of a different broadcaster, for example, a FLUTE session, a network transmitting a broadcast service through MPEG-2 TS of a different broadcaster, a network transmitting a broadcast service through a packet based stream of a different broadcaster, a network transmitting a broadcast service through a packet based stream transmitted from an IP based broadcast network, and a network obtaining a broadcast service through URL. For example, as shown in the embodiment of  FIG. 44 , when a value of the delivery_network_type field is 0x00, it may represent a network transmitting a broadcast service through an IP stream transmitted from the same broadcaster. Moreover, when a value of the delivery_network_type field is 0x01, it may represent a network transmitting a broadcast service through an IP stream transmitted from a different broadcaster. Moreover, when a value of the delivery_network_type field is 0x02, it may represent a network transmitting a broadcast service through a session based protocol of the same broadcaster, for example, a FLUTE session. Additionally, when a value of the delivery_network_type field is 0x03, it may represent a network transmitting a broadcast service through a session based protocol of a different broadcaster, for example, a FLUTE session. Furthermore, when a value of the delivery_network_type field is 0x04, it may represent a network transmitting a broadcast service through an MPEG-2 TS of a different broadcaster. In addition, when a value of the delivery_network_type field is 0x05, it may represent a network transmitting a broadcast service through a packet based stream of a different broadcaster. Moreover, when a value of the delivery_network_type field is 0x06, it may represent a network transmitting a broadcast service through a packet based stream transmitted from an IP based broadcast network. Furthermore, when a value of the delivery_network_type field is 0x07, it may represent a network obtaining a broadcast service through URL. 
     The data_path field includes specific transmission information according to the type of a transmission network transmitting a broadcast service. This data_path will be described in more detail with reference to  FIGS. 45 to 53 . 
       FIG. 45  is a view when broadcast service transmission path signaling information signals the transmission of a broadcast service through IP stream according to an embodiment of the present invention. 
     When a network transmitting a broadcast service is a network transmitting a broadcast service through an IP stream that the same broadcaster transmits, broadcast service transmission path signaling information may include at least one among information representing an IP version, information on whether it contains a source IP address, an source IP address, information on whether it contains a destination IP address, a destination IP address, information representing the number of UDP ports of an IP datagram flow transmitting a broadcast service, and information an UDP port number information. 
     According to a specific embodiment of the present invention, as shown in the embodiment of  FIG. 45 , the broadcast service transmission path signaling information may include at leas one among an IP_versioni_flag field, a source_IP_address_flag field, a destination_IP_address_flag field, a source_IP_address field, a port_num_count field, and a destination_UDP_port_number field. 
     The IP_versioni_flag field represents an IP address format of an IP datagram including a broadcast service. In more detail, when a value of the IP_versioni_flag field is 1, it represents that an IP datagram including a broadcast service is IPV4 format and when a value of the IP_versioni_flag field is 0, it represents that an IP datagram including a broadcast service is IPv6 format. According to a specific embodiment of the present invention, the IP_versioni_flag field may be a 1-bit field. 
     The source_IP_address_flag field represents whether an IP datagram including a broadcast service includes a source IP address. In more detail, when a value of the source_IP_address_flag field is 1, it represents that an IP datagram including a broadcast service includes a source IP address and when a value of the source_IP_address flag field is 0, it represents that an IP datagram including a broadcast service does not include a source IP address. According to a specific embodiment of the present invention, the source_IP_address_flag field may be a 1-bit field. 
     The destination_IP_address_flag field represents that an IP datagram including a broadcast service includes a destination IP address. In more detail, when a value of the destination_IP_address flag field is 1, it represents that an IP datagram including a broadcast service includes a destination IP address and when a value of the destination_IP_address_flag field is 0, it represents that an IP datagram including a broadcast service does not include a destination IP address. According to a specific embodiment of the present invention, the destination_IP_address_flag field may be a 1-bit field. 
     The source_IP_address field represents the source IP address of an IP datagram including a broadcast service. According to a specific embodiment of the present invention, the source_IP_address field may be a 32 or 128-bit field according to the IP version. 
     The destination_IP address field represents the destination IP address of an IP datagram including a broadcast service. According to a specific embodiment of the present invention, the destination_IP_address field may be a 32 or 128-bit field according to the IP version. 
     The port_num_count field represents the number of ports of an IP datagram flow including a broadcast. According to a specific embodiment of the present invention, the port_num_count field may be an 8-bit field. 
     The destination_UDP_port_number field represents the UDP port number of an IP datagram including a broadcast service. According to a specific embodiment of the present invention, the destination_UDP_port_number field may be a 16-bit field. 
       FIG. 46  is a view when broadcast service transmission path signaling information signals the transmission of a broadcast service through an IP stream of a different broadcaster according to an embodiment of the present invention. 
     When a network transmitting a broadcast service is a network transmitting a broadcast service through an IP stream that a different broadcaster transmit, unlike a network transmitting a broadcast service through an IP stream that the same broadcaster transmits, the broadcast service transmission path signaling information may further include an identifier for identifying a transport stream transmitting an IP datagram. 
     According to an embodiment of the present invention, as shown in the embodiment of  FIG. 46 , the broadcast service transmission path signaling information may include a transport_stream_id field. 
     The transport_stream_id field identifies a transport stream transmitting an IP datagram including a broadcast service. According to a specific embodiment of the present invention, the transport_stream_id field may be a 16-bit field. 
       FIG. 47  is a view when broadcast service transmission path signaling information signals the transmission of a broadcast service through a FLUTE session according to an embodiment of the present invention. 
     When a network transmitting a broadcast service is a network transmitting a broadcast service through a FLUTE session that the same broadcaster transmits, broadcast service transmission path signaling information may include at least one among information representing an IP version, information on whether it contains an IP address, a source IP address, a destination IP address, UDP port number information, and a Transport Session Identifier for identifying a FLUTE session transmitting a FLUTE packet including a broadcast service. 
     According to a specific embodiment of the present invention, as shown in the embodiment of  FIG. 47 , the broadcast service transmission path signaling information may include at leas one among an IP_versioni_flag field, a source_IP_address_flag field, a source_IP_address field, a destination_UDP_port_number field, and a flute_tsi field. 
     The IP_versioni_flag field represents an IP address format of an IP datagram transmitting a FLUTE packet including a broadcast service. In more detail, when a value of the IP_versioni_flag field is 1, it represents that an IP datagram including a broadcast service is IPV4 format and when a value of the IP_versioni_flag field is 0, it represents that an IP datagram including a broadcast service is IPv6 format. According to a specific embodiment of the present invention, the IP_versioni_flag field may be a 1-bit field. 
     The source_IP_address_flag field represents whether an IP datagram transmitting a FLUTE packet including a broadcast service includes a source IP address. In more detail, when a value of the source_IP_address_flag field is 1, it represents that an IP datagram including a broadcast service includes a source IP address and when a value of the source_IP_address_flag field is 0, it represents that an IP datagram including a broadcast service does not include a source IP address. According to a specific embodiment of the present invention, the source_IP_address_flag field may be a 1-bit field. 
     The source_IP_address field represents the source IP address of an IP datagram transmitting a FLUTE packet including a broadcast service. According to a specific embodiment of the present invention, the source_IP_address field may be a 32 or 128-bit field according to the IP version. 
     The destination_IP_address field represents the destination IP address of an IP datagram transmitting a FLUTE packet including a broadcast service. According to a specific embodiment of the present invention, the destination_IP_address field may be a 32 or 128-bit field according to the IP version. 
     The destination_UDP_port_number field represents the UDP port number of an IP datagram transmitting a FLUTE packet including a broadcast service. According to a specific embodiment of the present invention, the destination_UDP_port_number field may be a 16-bit field. 
     The flute_tsi field represents a Transport Session Identifier for identifying a FLUTE session transmitting a FLUTE packet including a broadcast service. 
       FIG. 48  is a view when broadcast service transmission path signaling information signals the transmission of a broadcast service through a FLUTE protocol of a different broadcaster according to an embodiment of the present invention. 
     When a network transmitting a broadcast service is a network transmitting a broadcast service through a FLUTE session of a different broadcaster, unlike a network transmitting a broadcast service through a FLUTE session of the same broadcaster, the broadcast service transmission path signaling information may further include an identifier for identifying a transport stream transmitting a FLUTE packet. 
     According to an embodiment of the present invention, as shown in the embodiment of  FIG. 48 , the broadcast service transmission path signaling information may include a transport_stream_id field. 
     The transport_stream_id field identifies a transport stream transmitting a FLUTE packet including a broadcast service. According to a specific embodiment of the present invention, the transport_stream_id field may be a 16-bit field. 
       FIG. 49  is a view when broadcast service transmission path signaling information signals the transmission of a broadcast service through MPEG-2 TS stream of a different broadcaster according to an embodiment of the present invention. 
     When a network transmitting a broadcast service is a network transmitting a broadcast service through MPEG-2 TS of a different broadcaster, it may include an identifier for identifying a transport stream transmitting MPEG-2 TS including a broadcast and an identifier of an MPEG-2 TS packet including a broadcast service. 
     According to a specific embodiment of the present invention, as shown in  FIG. 49 , the broadcast service transmission path signaling information may include at least one among a transport_stream_id field and a pid field. 
     The transport_stream_id field represents an identifier for identifying a transport stream transmitting MPEG-2 TS. According to a specific embodiment of the present invention, the transport_stream_id field may be a 16-bit field. 
     The pid field represents an identifier of an MPEG2-TS packet including a broadcast service. According to a specific embodiment of the present invention, the pid field may be a 13-bit field. 
       FIG. 50  is a view when broadcast service transmission path signaling information signals the transmission of a broadcast service through a packet based stream of a different broadcaster according to an embodiment of the present invention. 
     When a network transmitting a broadcast service is a network transmitting a broadcast service through a packet based stream of a different broadcaster, broadcast service transmission path signaling information may include an identifier for identifying a packet based stream including a broadcast service and an identifier of a packet including a broadcast service. 
     According to a specific embodiment of the present invention, as shown in  FIG. 50 , the broadcast service transmission path signaling information may include at least one among a transport_stream_id field and a packet_id field. 
     The transport_stream_id field represents an identifier of a packet based stream including a broadcast service. According to a specific embodiment of the present invention, the transport_stream_id field may be a 16-bit field. 
     The packet_id field represents an identifier of a packet including a broadcast service. According to a specific embodiment of the present invention, the packet_id field may be a 16-bit field. 
       FIG. 51  is a view when broadcast service transmission path signaling information signals the transmission of a broadcast service through a packet based stream of an IP based broadcast network according to an embodiment of the present invention. 
     When a network transmitting a broadcast service is a network transmitting a broadcast service through a packet based stream transmitted from an IPI based broadcast network, broadcast service transmission path signaling information may include at least one among information representing an IP version, information representing whether it contains a source IP address, a source IP address, a destination IP address, UDP port number information, and an identifier for identifying a packet including a broadcast service. 
     According to a specific embodiment of the present invention, as shown in the embodiment of  FIG. 47 , the broadcast service transmission path signaling information may include at leas one among an IP_versioni_flag field, a source_IP_address_flag field, a source_IP_address field, a destination_UDP_port_number field, and a packet_id field. 
     The IP_versioni_flag field represents an IP address format of an IP datagram transmitting a packet including a broadcast service. In more detail, when a value of the IP_versioni_flag field is 1, it represents that an IP datagram including a broadcast service is IPV4 format and when a value of the IP_versioni_flag field is 0, it represents that an IP datagram including a broadcast service is IPv6 format. According to a specific embodiment of the present invention, the IP_versioni_flag field may be a 1-bit field. 
     The source_IP_address_flag field represents whether an IP datagram transmitting a packet including a broadcast service includes a source IP address. In more detail, when a value of the source_IP_address_flag field is 1, it represents that an IP datagram including a broadcast service includes a source IP address and when a value of the source_IP_address_flag field is 0, it represents that an IP datagram including a broadcast service does not include a source IP address. According to a specific embodiment of the present invention, the source_IP_address_flag field may be a 1-bit field. 
     The source_IP_address field represents the source IP address of an IP datagram transmitting a packet including a broadcast service. According to a specific embodiment of the present invention, the source_IP_address field may be a 32 or 128-bit field according to the IP version. 
     The destination_IP_address field represents the destination IP address of an IP datagram transmitting a packet including a broadcast service. According to a specific embodiment of the present invention, the destination_IP_address field may be a 32 or 128-bit field according to the IP version. 
     The destination_UDP_port_number field represents the UDP port number of an IP datagram transmitting a packet including a broadcast service. According to a specific embodiment of the present invention, the destination_UDP_port_number field may be a 16-bit field. 
     The packet_id field represents an identifier for identifying a packet including a broadcast service. According to a specific embodiment of the present invention, the packet_id field may be a 16-bit field. 
       FIG. 52  is a view when broadcast service transmission path signaling information signals a broadcast service through URL according to an embodiment of the present invention. 
     When a network transmitting a broadcast service is a network obtaining a broadcast service through URL, broadcast service transmission path signaling information may include information representing the length of URL for receiving a broadcast service and a URL for receiving a broadcast service. 
     According to a specific embodiment of the present invention, as shown in  FIG. 52 , the broadcast service transmission path signaling information may include at least one among a URL_length field and a URI_char field. 
     The URL_length field represents the length of a URL for receiving a broadcast service. According to a specific embodiment of the present invention, the URL_length field may be an 8-bit field. 
     The URL_char field represents a URL for receiving a broadcast service. According to a specific embodiment of the present invention, the URL_char field may be an 8-bit field. 
       FIG. 52  is a view when broadcast service transmission path signaling information signals a broadcast service through URL according to an embodiment of the present invention. 
     The broadcast transmission device obtains a transmission path of a broadcast service through a control unit in operation S 501 . 
     The broadcast transmission device generates broadcast service transmission path signaling information through a control unit in operation S 503 . The broadcast transmission device may generate the broadcast service transmission path signaling information described with reference to  FIGS. 43 to 52 . 
     The broadcast transmission device transmits a broadcast signal including broadcast service transmission path signaling information through a transmission unit in operation S 505 . According to a specific embodiment of the present invention, the broadcast transmission device may transmit broadcast service transmission path signaling information via an IP network through an IP communication unit transmitting/receiving IP data. 
       FIG. 53  is a view when a broadcast transmission device transmits broadcast service transmission path signaling information according to an embodiment of the present invention. 
     The broadcast reception device  100  receives a broadcast signal through the broadcast reception unit  110  in operation S 701 . 
     The broadcast reception device  100  obtains broadcast service transmission path signaling information through the control unit  150  on the basis of the broadcast signal in operation S 703 . According to a specific embodiment of the present invention, the broadcast reception device  100  may obtain broadcast service transmission path signaling information via an IP network through the IP communication unit  130 . Especially, in the case that the intensity of a broadcast signal is weak or it is difficult to receive a broadcast signal, the broadcast reception device  100  may obtain broadcast service transmission path signaling information via an IP network. 
     The broadcast reception device  100  receives a broadcast service on the basis of the broadcast service transmission path signaling information through the control unit  150  in operation S 705 . In more detail, the broadcast reception device  100  may receive a media component of a broadcast service on the basis of the broadcast service transmission path signaling information through the control unit  150 . As described with reference to  FIGS. 43 to 52 , the broadcast reception device  100  may receive a broadcast service through at least one among a network transmitting a broadcast service through an IP stream that the same broadcaster transmits, a network transmitting a broadcast service through an IP stream that a different broadcaster transmit, a network transmitting a broadcast service through a session based protocol of the same broadcaster, for example, a FLUTE session, a network transmitting a broadcast service through a session based protocol of different broadcasters, for example, a FLUTE session, a network transmitting a broadcast service through MPEG-2 TS of a different broadcaster, a network transmitting a broadcast service through a packet based stream of a different broadcaster, a network transmitting a broadcast service through a packet based stream transmitted from an IP based broadcast network, and a network obtaining a broadcast service through URL. Especially, according to a specific embodiment of the present invention, the broadcast reception device  100  may receive a plurality of media components of a broadcast service through a plurality of networks. For example, the broadcast reception device  1100  may receive a video component of a broadcast service via a packet based stream through the broadcast reception unit  1110  and may receive an audio component of a broadcast service via an IP based broadcast network through the IP communication unit  130 . Especially, in the case that the intensity of a broadcast signal is weak or it is difficult to receive a broadcast signal, the broadcast reception device  100  may receive a media component of a broadcast service via an IP based broadcast network through the IP communication unit  130 . 
     As described above, the broadcast service signaling table may include media component signaling information signaling a media component. Especially, when a broadcast service is transmitted in the ISO Base Media File Format (ISO BMFF), the broadcast service signaling table may include media component signaling information. This will be described in more detail with reference to  FIGS. 55 to 58 . 
       FIG. 55  is a view illustrating media component signaling information signaling a media component according to an embodiment of the present invention. 
     The media component signaling information may include information representing an encoding type of a media component, information on whether a media component is encrypted, information representing the number of STKM streams including a key decrypting an encrypted media component, an identifier for identifying an STKM stream including a key for decrypting an encrypted media component, the length of a transmission parameter of a media component, a transmission parameter of a media component, and an encoding parameter according to an encoding type of a component. At this point, the transmission parameter may include at least one among a buffer model and the size of a maximum transmission unit (MTU). 
     According to a specific embodiment of the present invention, as shown in the embodiment of  FIG. 55 , media component signaling information may include at least one among a descriptor_tag field, a descriptor_length field, a component_type field, a component_encryption_flag field, a num_STKM_streams field, an STKM_stream_id field, a transport_parameter_text_length field, a transport_parameter_text field, and a component_data field. 
     The descriptor_tag field represents that a corresponding descriptor includes media component signaling information. According to a specific embodiment of the present invention, the descriptor_tag field may be an 8-bit field. 
     The descriptor_length field represents the length of broadcast service transmission path signaling information after a corresponding field. According to a specific embodiment of the present invention, the descriptor_length field may be an 8-bit field. 
     The component_type field represents an encoding type of a corresponding component. According to an embodiment of the present invention, as shown in the embodiment of  FIG. 56 , a value that the component_type field has may represent at least one among an H.264/AVC, SVC enhancement layer stream component, an HE AAC v2   stream component, a FLUTE file delivery session, an STKM stream component, an LTKM stream component, an OMA-RME DIMS stream component, and an NTP time base stream component. When a media component is transmitted through ISO BMFF, the broadcast reception device  100  needs to prepare an appropriate operation for receiving a media component. Accordingly, it is necessary to signal the fact that a media component is transmitted through ISO BMFF. In more detail, as shown in the embodiment of  FIG. 57 , the component_type field may represent that a media component of a broadcast service is transmitted through ISO BMFF. In more detail, when a value of the component_type field is 35, it may represent that a media component is an H.264/AVC component. In more detail, when a value of the component_type field is 36, it may represent that a media component is an SVC enhancement layer stream component. In more detail, when a value of the component_type field is 37, it may represent that a media component is an HE AAC v2 audio stream component. In more detail, when a value of the component_type field is 38, it may represent that a media component is transmitted through a FLUTE file transmission session. In more detail, when a value of the component_type field is 39, it may represent that a media component is an STKM stream component. In more detail, when a value of the component_type field is 40, it may represent that a media component is an LTKM stream component. In more detail, when a value of the component_type field is 41, it may represent that a media component is an OMA-RME DIMS stream component. In more detail, when a value of the component_type field is 42, it may represent that a media component is an NTP time base stream component. In more detail, when a value of the component_type field is 43, it may represent that a media component is transmitted through an ISO BMFF. According to a specific embodiment of the present invention, the component_type field may be a 7-bit field. 
     The component_encryption_flag field is a field representing whether a media component is encrypted. According to a specific embodiment of the present invention, the component_encryption_flag field may be a 1-bit field. 
     The num_STKM_streams field represents the number of STKM streams including a key for decrypting an encrypted media component. According to a specific embodiment of the present invention, the num_STKM_streams field may be an 8-bit field. 
     The STKM_stream_id field represents an identifier for identifying an STKM stream including a key for decrypting an encrypted media component. According to a specific embodiment of the present invention, the STKM_stream_id field may be an 8-bit field. 
     The transport_parameter_text_length field represents the length of the transport_parameter_text field. According to a specific embodiment of the present invention, the transport_parameter_text_length field may be an 8-bit field. 
     The transport_parameter_text field represents a transmission parameter of a media component. At this point, the transmission parameter may include at least one among a buffer model and the size of a maximum transmission unit (MTU). 
     The component_data field represents an encoding parameter of a component. A parameter that an encoding parameter includes may vary according to an encoding type of a component. In more detail, a parameter that an encoding parameter includes may vary according to a value of the component_type field. 
     When a media component is transmitted through ISO BMFF, the component_data field may include at least one among version information of ISO BMFF and profile information. 
     In more detail, as shown in the embodiment of  FIG. 58 , the component_data field may include at least one among a version field and a profile field. 
     The version field represents version information of ISO BMFF. According to a specific embodiment of the present invention, the version field may be an 8-bit field. 
     The profile field represents profile information of ISO BMFF. According to a specific embodiment of the present invention, the profile field may be an 8-bit field. 
     The above-described media components are all handled and signaled identically regardless of their contents. However, recently, an adaptive streaming service transmitting different qualities of a media component according to a communication environment receives great attentions. Accordingly, a user may select one of various qualities of media components including the same content according to a communication environment and may then view the selected one. Furthermore, a multi view service displaying a plurality of media components on one screen simultaneously is provided. Accordingly, a user may view a plurality of images or data broadcasts through one screen. For example, a user may view a game of another stadium while viewing a baseball game through an additional Picture In Picture (PIP) screen. In such a way, as a broadcast service including a plurality of media components is diversified and increased, a broadcast transmission device and a broadcast reception device may need to divide the types of a component and process them and also need to systematically define the relationship between each media component. This will be described with reference to  FIGS. 59 to 83 . 
       FIG. 59  is a view illustrating the type of a media component according to an embodiment of the present invention. 
     The media component may be divided into a content component, a simple audio component, a simple video component, a continuous component, an elementary component, a composite component, a composite audio component, a composite video component, an adaptive component, an adaptive audio component, an adaptive video component, and a complex component. 
     The content component is a component including metadata relating to one kind of media. In more detail, the content component may be one of a video track, an audio track, a subtitle, a video enhanced layer, a webpage, and a bi-directional application. 
     The simple audio component is a component including audio. In more detail, the simple audio component is the encoding of one voice sequence encoded according to specific encoding parameters. 
     The simple audio component is a component including video. In more detail, the simple video component is the encoding of one video sequence encoded according to specific encoding parameters. 
     The continuous component is a component played on a continuous stream. 
     The elementary component is a continuous component including one encoding. The elementary component may be an audio component. In more detail, the elementary component may be one encoding for voice sequence. Additionally, the elementary component may be a video component. In more detail, the elementary component may be one encoding for video sequence. The elementary component may be one subtitle track. 
     The composite component is a collection of continuous components necessary for playing one scene. In more detail, the composite component is a collection of continuous components that have the same media type, represent the same scene, and need to be played together in a predetermined combination. Accordingly, the composite component is a collection of media components combined to represent one scene. In more detail, the composite component may be music, dialogs, and special effect necessary for one complete audio. Additionally, the composite component may be the right image and the left image of a 3D image necessary for playing the 3D image. 
     The composite audio component is a collection of audio components necessary for playing voice sequence. In more detail, the composite audio component may be a collection of audio components to be mixed. 
     The composite video component is a collection of video components necessary for playing image sequence. In more detail, the composite video component may be a collection of 3D components combined for 3D video playback. Additionally, the composite video component may be base video encoding accompanying at least one enhanced encoding. 
     The adaptive component is a collection of continuous components representing one scene, which are replaced with each other. In more detail, the adaptive component is a collection of continuous components that have the same media type and represent the same scene and one of the continuous components is selected for playback. In more detail, the adaptive component is a collection of media components obtained by encoding the same content with different qualities. For example, the adaptive component may be a collection of audio components obtained by encoding the same voice sequence with different bitrates. Additionally, the adaptive component is a collection of video components obtained by encoding the same image sequence with different bitrates. Additionally, the adaptive component may be a general subtitle track and an easy reader subtitle for the same dialog. 
     The adaptive audio component is a collection of audio components, one of which is selected for playing voice sequence. In more detail, the adaptive audio component may be a collection of audio components obtained by encoding the same sound sequence with different bitrates. 
     The adaptive video component is a collection of video components, one of which is selected for playing image sequence. In more detail, the adaptive video component may be a collection of video components obtained by encoding the same video sequence with different encoding parameters. 
     The complex component represents one of the composite component or the adaptive component. The complex component will be described in more detail with reference to  FIGS. 60 to 62 . 
       FIG. 60  is a view illustrating a configuration of a complex component according to an embodiment of the present invention. 
     The complex component is not required to include only an elementary component. According to a specific embodiment of the present invention, the complex component may include a complex component. Additionally, the complex component may be a composite component or an adaptive component. In more detail, as shown in the embodiment of  FIG. 60 , the composite component may include at least one elementary component. Additionally, the composite component may include at least one complex component. Additionally, the composite component may include both an elementary component and a complex component. One adaptive component may include at least one elementary component. 
     A component of a broadcast service may be described using the term “top-level component”. A top-level audio component represents a unique voice sequence. A top-level video component represents a unique image sequence. According to a specific embodiment of the present invention, such a top-level component may be an elementary component. According to another specific embodiment of the present invention, such a top-level component may be a composite component. 
     For example, as shown in the embodiment of  FIG. 61 , the top-level video component may be a composite component including the left image and right image components of a 3D image. At this point, the left image component of the 3D image may be an adaptive component including a plurality of elementary components encoded with different bitrates. Additionally, the right image component of the 3D image may be an adaptive component including a plurality of elementary components encoded with different bitrates. 
     According to another specific embodiment of the present invention, as shown in the embodiment of  FIG. 62 , the top-level audio component may be an adaptive component including an adaptive component including a complete main audio and a composite component having mixed music, dialogs, and special effects. At this point, the adaptive component including a complete main audio may include a plurality of elementary components encoded with different bitrates. Additionally, the composite component including mixed music, dialogs, and special effects may include an adaptive component including music, an adaptive component including dialogs, and an adaptive component including special effects. That is, the adaptive component including music may include a plurality of elementary components encoded with different bitrates. 
     Distinguishing a media component in such a way may simplify the relationship between a plurality of media components. For example, when it is specified that each video program includes one complex video component, the relationship with each audio elementary component or a video elementary component does not need to be specified. 
     There may be a plurality of complex component models for one media. For example, a 3D component encoded with a plurality of bitrates may be modeled with a sub media component for a left image and a sub media component for a right image. Each sub media component may be modeled as an adaptive component including a plurality of components encoded with different bitrates. Additionally, the same 3D component may be modeled as an adaptive component including a plurality of sub media components encoded with different bitrates and each of the sub media components may be modeled as a composite component including left and right images. The number of sub media components with different bitrates in the left and right images may vary. 
     Various broadcast service models are described with reference to  FIGS. 63 to 66 . 
       FIG. 63  is a view illustrating a media component configuration of an audio service according to an embodiment of the present invention. 
     The audio service may include one or more audio components. Additionally, the audio service may include a subtitle component. Additionally, the audio component may include adjunct data service. At this point, an adjunct service may be a Non-Real-Time (NRT) service. Additionally, according to a specific embodiment of the present invention, an audio service may be transmitted through continuous stream according to a predetermined schedule. 
       FIG. 64  is a view illustrating a configuration of a broadcast service including both audio and video according to an embodiment of the present invention. 
     The broadcast service including both audio and video may include one or more main video components. At this point, the broadcast service including both audio and video may include an adjunct video component. At this point, the broadcast service including both audio and video may include an audio component. Moreover, the broadcast service including both audio and video may include a subtitle component. Furthermore, the broadcast service including both audio and video may include an adjunct service data component. 
       FIG. 65  is a view illustrating a configuration of a user request content service according to an embodiment of the present invention. 
     A Contents On Demand (CoD) service may include an application providing a user interface. Additionally, the CoD service may include a content item provided in response to a user request. Additionally, the CoD service may include a catalog of a content item. At this point, the catalog may be embedded in an application. 
       FIG. 66  is a view illustrating a configuration of a standalone data service according to an embodiment of the present invention. 
     A standalone data service may include one or more content items configuring a service. 
     A plurality of broadcast services may share a media component. In more detail, each of media components that the above-described audio service, broadcast service including both audio and video, and standalone data service include may relate to one or more other components. At this point, one or more other components may include a service encoded by another method representing the same base content. 
     Additionally, a broadcast service may include at least one among a service identifier, a service form, a description of a service, a service name, a channel number, a graphic icon, a list of components in a service, a property for broadcast service protection, a property on targeting/personalization, a contents advisory rating, and a property on broadcast service user report. At this point, the service form ma include at least one among a scheduled audio service transmitted according to a planned schedule, a service including scheduled audio and video transmitted according to a planned schedule, a user request service transmitted in response to a user request, and a scripted data service. Additionally, the channel number may include a major channel number and a minor channel number in detail. Additionally, the channel number may be displayed as a virtual channel number. Moreover, a plurality of broadcast services may use the same graphic icon. Additionally, the service identifier may have a unique value in a broadcast area where a broadcast service is broadcasted. Additionally, the service identifier may include identifiers of two categories, for example, a local identifier and a regional identifier. The local identifier may be used for services broadcasted only in one broadcast area. Accordingly, a plurality of broadcast services broadcasted in a plurality of different broadcast areas may have the same regional identifier. The local identifier may be used for broadcast service identification when the same broadcast is available in a plurality of broadcast areas. 
     In order to signal the properties of such a broadcast service, the above-described broadcast signaling table may be used. Additionally, in order to signal a graphic icon of a broadcast service, the broadcast service signaling table may include graphic icon information. Especially, the broadcast service signaling table may include graphic icon service as service level information. 
       FIG. 67  is a view illustrating graphic icon information according to an embodiment of the present invention. 
     The graphic icon information may include at least one among an icon identifier, an icon transmission mode representing an icon transmission method, information representing whether the position of an icon is specified, coordinate system information representing coordinates that are the base of an icon position, horizontal coordinates information representing the horizontal coordinates of an icon, vertical coordinates information representing the vertical coordinates of an icon, information representing the image form of an icon, URL information representing the position where an icon image is stored, and icon data itself. 
     In more detail, as shown in the embodiment of  FIG. 67 , the graphic icon information may include at least one among a descriptor_tag field, a descriptor_length field, a descriptor number field, a last_descriptor_number field, an icon_id field, an icon_transport_mode field, a position_flag field, a coordinate_system field, an icon_horizontal_origin field, an icon_vertical_origin field, an icon_type_length field, an icon_type_chars field, an icon_data_length field, an icon_data_byte field, a url_length field, a url field, and an icon_content_linkage field. 
     The descriptor_tag field represents that icon information is included. According to a specific embodiment of the present invention, the descriptor_tag field may be an 8-bit field. 
     The descriptor_length field represents the length of icon information after this field. According to a specific embodiment of the present invention, the descriptor_length field may be an 8-bit field. 
     The descriptor_number field represents the order of the current descriptor when icon information is divided into a plurality of descriptors and transmitted. According to a specific embodiment of the present invention, in the case of a descriptor transmitted first, a value of the descriptor_number field may be 0x00. According to a specific embodiment of the present invention, a value of the descriptor_number field may be increased by one. According to a specific embodiment of the present invention, the descriptor_number field may be a 4-bit field. 
     The last_descriptor_number field represents the number of the last descriptor. According to a specific embodiment of the present invention, the last_descriptor_number field may be a 4-bit field. 
     The icon_id field represents an icon identifier for identifying an icon. According to a specific embodiment of the present invention, the icon_id field may be an 8-bit field. 
     The icon_transport_mode field represents an icon transmission method. In more detail, a value of the icon_transport_mode field may represent one among when an icon image is transmitted through graphic icon information itself, when an icon image is linked through URL, and an icon image is transmitted through a session based protocol, for example, a FLUTE session. According to a specific embodiment of the present invention, as shown in the embodiment of  FIG. 68 , when a value of the icon_transport_mode field is 0x00, it represents that an icon image is transmitted through graphic icon information itself. When a value of the icon_transport_mode field is 0x01, it represents that an icon image is linked through URL. When a value of the icon_transport_mode field is 0x02, it represents that an icon image is transmitted through a FLUTE session. According to a specific embodiment of the present invention, the icon_transport_mode field may be a 2-bit field. 
     The position_flag field represents whether the position of an icon is specified. According to a specific embodiment of the present invention, the position_flag field may be a 1-bit field. 
     The coordinate_system field represents coordinates that is the base of an icon position. In more detail, when a value of the coordinate_system field may represent at least one among when a coordinate system is configured with 720×576 coordinates, when a coordinate system is configured with 1280×720 coordinates, when a coordinate system is configured with 1920×1080 coordinates, when a coordinate system is configured with 3840×2160 coordinates, and when a coordinate system is configured with 7680×4320 coordinates. According to a specific embodiment of the present invention, as shown in the embodiment of  FIG. 69 , when a value of the coordinate_system field is 0x00, it represents that a coordinate system is configured with 720×576 coordinates. When a value of the coordinate_system field is 0x01, it represents that a coordinate system is configured with 1280×720 coordinates. When a value of the coordinate_system field is 0x02, it represents that a coordinate system is configured with 1920×1080 coordinates. When a value of the coordinate_system field is 0x03, it represents that a coordinate system is configured with 3840×2160 coordinates. When a value of the coordinate_system field is 0x04, it represents that a coordinate system is configured with 7680×4320 coordinates. According to a specific embodiment of the present invention, the coordinate_system field may be a 3-bit field. 
     The icon_horizontal_origin field represents the horizontal coordinates of an icon. In more detail, a value of coordinates may be increased in a direction from a left column to a right column. According to a specific embodiment of the present invention, the icon_horizontal_origin may be a 13-bit field. 
     The icon_vertical_origin field represents the vertical coordinates of an icon. In more detail, a value of coordinates may be increased in a direction from an upper row to a lower row. According to a specific embodiment of the present invention, the icon_vertical_origin may be a 13-bit field. 
     The icon_type_length field represents the length of the icon type field. According to a specific embodiment of the present invention, the icon_type_length field may be an 8-bit field. 
     The icon_type_chars field represents the image form of an icon. In more detail, a value of the icon_type_chars field may be in a Multipurpose Internet Mail Extensions (MIME) image form defined in RFC 2045. 
     The icon_data_length field represents the length of the icon_data_byte field when an icon image is transmitted through graphic icon information. According to a specific embodiment of the present invention, the icon_data_length field may be an 8-bit field. 
     The icon_data_byte field represents data of an icon image that graphic icon information transmits. 
     The url_length field represents the length of the url field when an icon image is linked through URL. The url_length field may be an 8-bit field. 
     The url field represents a URL that an icon links. 
     The icon_content_linkage field represents a FLUTE FDT contents linkage transmitting an icon image when the icon image is transmitted through a FLUTE session. 
     Graphic icon information is described through the embodiment in which the graphic icon information is in a bit stream format, but the graphic icon information may be in another format such as an XML file format. 
     Additionally, as described above, broadcast services may include one or more media components. The service signaling table may include media component list information signaling media components that a broadcast service includes. Especially, the broadcast service signaling table may include media component list information as service level information. 
     This will be described in more detail with reference to  FIG. 70 . 
       FIG. 70  is a view illustrating media component list information according to an embodiment of the present invention. 
     The media component list information may include at least one among a component identifier for identifying a component, component type information representing the type of a media component, and media type information representing the type of media that a media component includes. 
     According to a specific embodiment of the present invention, as shown in  FIG. 70 , the media component list information may include a descriptor_tag field, a descriptor_length field, a num_component field, a component_id field, a component_type field, and a general_media_type field. 
     The descriptor_tag field represents that component list information is included. According to a specific embodiment of the present invention, the descriptor_tag field may be an 8-bit field. 
     The descriptor_length field represents the length after the descriptor_length field. According to a specific embodiment of the present invention, the descriptor_length field may be an 8-bit field. 
     The num_component field represents the number of media components that a corresponding broadcast service includes. According to a specific embodiment of the present invention, the num_component field may be an 8-bit field. 
     The component_id field represents an identifier for identifying a corresponding media component. According to a specific embodiment of the present invention, the component_id field may be an 8-bit field. 
     The component_type field represents the type of a media component. According to a specific embodiment of the present invention, a value of the component_type field may represent one among the above-described elementary component, composite component, and adaptive component. In more detail, when a value of the component_type field is 0x00, a corresponding media component represents an elementary component. When a value of the component_type field is 0x01, a corresponding media component represents a composite component. When a value of the component_type field is 0x02, a corresponding media component represents an adaptive component. According to a specific embodiment of the present invention, the component_type field may be a 4-bit field. 
     The general_media_type field represents the type of a media that a media component includes. A value of the general_media_type field may represent one among video, audio, text, application, and message. In more detail, when a value of the general_media_type field is 0x00, it represents that a media that a media component includes video. When a value of the general_media_type field is 0x01, it represents that a media that a media component includes audio. When a value of the general_media_type field is 0x02, it represents that a media that a media component includes text. When a value of the general_media_type field is 0x03, it represents that a media that a media component includes application. When a value of the general_media_type field is 0x04, it represents that a media that a media component includes message. According to a specific embodiment of the present invention, the general_media_type field may be a 4-bit field. 
     Graphic icon information is described through the embodiment in which component list information is in a bit stream format, but the graphic icon information may be in another format such as an XML file format. 
     Additionally, each media component may include at least one as a property among a component identifier for identifying a media component, the type of a component, description for a component, a targeting/personalization property, a service protection property, a target device, contents advisory rating, and related component information. At this point, a value of a component identifier may be unique between components of a broadcast service. The target device may represent one among a primary device and a companion device. Additionally, the service signaling table may include media component information signaling a property of such a media component. In more detail, the service signaling table may include media component information as component level information. This will be described with reference to  FIG. 71 . 
       FIG. 71  is a view illustrating media component information according to an embodiment of the present invention. 
     The media component information may include information representing the type of a media component, information on whether information on a target device is included, target device information representing a target device, text information describing a media component, a component encoding parameter according to the type of a media component, and information on a complex component in the case of a complex component that a media content includes. 
     The media component information may include a descriptor_tag field, a descriptor_length field, a component_type field, a target_device_flag field, a target_device field, a text_length field, a text_char field, a component_data_type field, a component_data field, and a complex_component_data field. 
     The descriptor_tag field represents that media component information is included. According to a specific embodiment of the present invention, the descriptor_tag field may be an 8-bit field. 
     The descriptor_length field represents the length after the descriptor_length field. According to a specific embodiment of the present invention, the descriptor_length field may be an 8-bit field. 
     The component_type field represents the type of a media component. According to a specific embodiment of the present invention, a value of the component_type field may represent one among the above-described elementary component, composite component, and adaptive component. In more detail, when a value of the component_type field is 0x00, a corresponding media component represents an elementary component. When a value of the component_type field is 0x01, a corresponding media component represents a composite component. When a value of the component_type field is 0x02, a corresponding media component represents an adaptive component. According to a specific embodiment of the present invention, the component_type field may be a 4-bit field. 
     The target_device_flag field represents whether the targt_device field is included. According to a specific embodiment of the present invention, the target_device_flag may be a 1-bit field. 
     The target_device field represents a target device where a corresponding component is executed. According to a specific embodiment of the present invention, a value that the target_device field has may represent whether a corresponding component is executed only in a primary device, only in a companion device, or in both primary device and a companion device. In more detail, when a value of the target_device field is 0x01, it represents that a corresponding component is executed only in a primary device. When a value of the target_device field is 0x02, it represents that a corresponding component is executed only in a companion device. When a value of the target_device field is 0x03, it represents that a corresponding component is executed in both a primary device and a companion device. 
     According to a specific embodiment of the present invention, the target_device field may be a 3-bit field. 
     The text_length field represents the length of the text_char field. According to a specific embodiment of the present invention, the text_length field may be an 8-bit field. 
     The text_char field is a text for describing a media component. 
     The component_data_type field represents an encoding type of a corresponding component. In more detail, the component_data_type field may have the same values as those in  FIGS. 55 and 56 . According to a specific embodiment of the present invention, the component_type field may be a 4-bit field. 
     The component_data field represents an encoding parameter of a component. A parameter that an encoding parameter includes may vary according to an encoding type of a component. In more detail, a parameter that an encoding parameter includes may vary according to a value of the component_type field. 
     When the type of a media component is a complex type, for example, a composite component or an adaptive component, the complex_component_data field represents information on a complex component. This will be described in more detail with reference to  FIGS. 72 and 73 . Additionally, component information is described through a bit stream format, but component information may be in another format such as an XML file format. 
       FIG. 72  is a view illustrating complex component information according to an embodiment of the present invention. 
     The complex component information may include at least one among information representing a set form of component, information on whether information on a target device is included, target device information representing a target device, the number of sub media components that a corresponding complex component includes, information on the type of a media that a sub media component includes and a role of a sub media component when a corresponding complex component is a composite component. 
     In more detail, as shown in  FIG. 72 , the complex component information may include at least one among an aggretation_type field, a num_sub_component field, a sub_component_id field, a general_mdeida_type field, and a sub_component_role field. 
     The aggretation_type field represents the type of a set that a corresponding component belongs. In more detail, a value of the aggretation_type field represents either a composite component or an adaptive component. According to a specific embodiment of the present invention, the aggretation_type field may be a 3-bit field. 
     The target_device_flag field represents whether the targt_device field is included. According to a specific embodiment of the present invention, the target_device_flag may be a 1-bit field. 
     The target_device field represents a target device where a corresponding component is executed. According to a specific embodiment of the present invention, a value that the target_device field has may represent whether a corresponding component is executed only in a primary device, only in a companion device, or in both primary device and a companion device. In more detail, when a value of the target_device field is 0x01, it represents that a corresponding component is executed only in a primary device. When a value of the target_device field is 0x02, it represents that a corresponding component is executed only in a companion device. When a value of the target_device field is 0x03, it represents that a corresponding component is executed in both a primary device and a companion device. According to a specific embodiment of the present invention, the target_device field may be a 3-bit field. 
     The num_sub_component field represents the number of sub media components that a corresponding complex component includes. According to a specific embodiment of the present invention, the num_sub_component field may be an 8-bit field. 
     The sub_component_id field represents a sub media component identifier for identifying a sub media component. According to a specific embodiment of the present invention, the sub_component_id field may be an 8-bit field. 
     When a corresponding complex component is a composite component, the general_media_type field represents the type of a media that a sub media component includes. In more detail, a value of the general_media_type field may represent one among video, audio, text, application, and message. In more detail, when a value of the general_media_type field is 0x00, it represents that a media that a sub media component includes video. When a value of the general_media_type field is 0x01, it represents that a media that a sub media component includes audio. When a value of the general_media_type field is 0x02, it represents that a media that a sub media component includes text. When a value of the general_media_type field is 0x03, it represents that a media that a sub media component includes application. When a value of the general_media_type field is 0x04, it represents that a media that a sub media component includes message. According to a specific embodiment of the present invention, the general_media_type field may be a 4-bit field. 
     The sub_component_role field represents the role of each sub media component. In more detail, a value of the sub_component_role field may represent that a sub media component is an enhancement layer for scalable video encoding. According to another specific embodiment of the present invention, a value of the sub_component_role field may represent that a sub media component is one among the right image, left image, and depth information of a 3D image. According to another specific embodiment of the present invention, a value of the sub_component_role field may represent that a sub media component is a video at a specific position of a screen divided into a plurality of areas. According to the type of a media that a sub media component includes, information that the sub_component_role field represents may vary. According to a specific embodiment of the present invention, the sub_component_role field may be an 8-bit field. 
     Such complex component information may be included in a complex component descriptor as shown in the embodiment of  FIG. 74 . Additionally, complex component information is described through a bit stream format, but the complex component information may be in another format such as an XML file format. 
     As described above, media components may have a predetermined relationship to each other. For example, one subtitle component may relate to one or more audio components. Additionally, in order to signal a relationship between such media components, the service signaling table may include related component list information. In more detail, the service signaling table may include related component list information as component level information. The related component list information will be described in more detail with reference to  FIG. 74 . 
       FIG. 74  is a view illustrating related component list information according to an embodiment of the present invention. 
     The related component list information may include at least one among a component identifier for identifying a component, information representing the type of a media component, information representing the encoding format of a media component, and information representing the type of media that a media component includes. 
     In more detail, as shown in the embodiment of  FIG. 74 , the related component list information may include at least one among a descriptor_tag field, a descriptor_length field, a num_associated_component field, a component_id field, a component_type field, a component_data_type field, and a general_media_type field. 
     The descriptor_tag field represents that related component list information is included. According to a specific embodiment of the present invention, the descriptor_tag field may be an 8-bit field. 
     The descriptor_length field represents the length after the descriptor_length field. According to a specific embodiment of the present invention, the descriptor_length field may be an 8-bit field. 
     The num_associated_component field represents the number of media components relating to a corresponding media component. According to a specific embodiment of the present invention, the num_associated_component field may be an 8-bit field. 
     The component_id field represents an identifier for identifying a related media component. According to a specific embodiment of the present invention, the component_id field may be an 8-bit field. 
     The component_type field represents the type of a media component. According to a specific embodiment of the present invention, a value of the component_type field may represent one among the above-described elementary component, composite component, and adaptive component. In more detail, when a value of the component_type field is 0x00, a related media component represents an elementary component. When a value of the component_type field is 0x01, a related media component represents a composite component. When a value of the component_type field is 0x02, a related media component represents an adaptive component. According to a specific embodiment of the present invention, the component_type field may be a 4-bit field. 
     The component_data_type field represents an encoding type of a corresponding component. In more detail, the component_data_type field may have the same values as those in  FIGS. 55 and 56 . According to a specific embodiment of the present invention, the component_type field may be an 8-bit field. 
     The general_media_type field represents the type of a media that a related media component includes. In more detail, a value of the general_media_type field may represent one among video, audio, text, application, and message. In more detail, when a value of the general_media_type field is 0x00, it represents that a media that a related media component includes video. When a value of the general_media_type field is 0x01, it represents that a media that a related media component includes audio. When a value of the general_media_type field is 0x02, it represents that a media that a related media component includes text. When a value of the general_media_type field is 0x03, it represents that a media that a related media component includes application. When a value of the general_media_type field is 0x04, it represents that a media that a related media component includes message. According to a specific embodiment of the present invention, the general_media_type field may be an 8-bit field. 
     An audio component may include at least one as a property among a component identifier for identifying a media component, the type of a component, description for a component, a targeting/personalization property, a service protection property, a target device, and related component information. At this point, a value of a component identifier may be unique between components of a broadcast service. The target device may represent one among a primary device, a companion device, and both a primary device and a companion device. 
     When the audio component is an elementary component, it may include a property for encoding format including codec, the number of channels, a bitrate, and a compression parameter. Additionally, when the audio component is an elementary component, it may include language information of audio as a property. The type of the audio component may be included as a property. At this point, the type of the audio component may be one among complete main audio, dialog, effect sound, and audio for the visually impaired, audio for the hearing-impaired, commentary, and voice over. 
     When the audio component is a complex component, it may include at least one as a property among information representing the type of a set, a list of included media components, and the role of an included component in the case of a composite component. 
     When the audio component is a top level component, it may include at least one as a property among contents advisory rating and information on a related subtitle component. 
     The subtitle component may include at least one as a property among a component identifier, the type of a component, a targeting/personalization property, a service protection property, a target device, and an audio component identifier relating to a subtitle component. At this point, a value of a component identifier may be unique between components of a broadcast service. The target device may represent one among a primary device, a companion device, and both a primary device and a companion device. 
     When the subtitle component is an elementary component, the subtitle component may include its language kind and form, as a property. In more detail, the form of a subtitle component may be one among a general subtitle or an Easy-reader subtitle. 
     When the subtitle component is an adaptive component, it may include a media component therein, as a property. 
     When the subtitle component is a top level component, it may include contents advisory rating as a property. 
     The video component may include at least one as a property among a component identifier for identifying a media component, the type of a component, a targeting/personalization property, a service protection property, the role of a video component, a target screen, and a data service relating to a video component. At this point, a value of a component identifier may be unique between components of a broadcast service. The role of a video component may be one among an alternative camera view, an alternative video component, a sign language screen, and a follow subject video. The target device may represent one among a primary device, a companion device, both a primary device and a companion device, and a Picture In Picture (PIP) screen. When the data service relating to a video component is not included, all additional data services are connected to a video component. 
     When the video component is an elementary component, it may include at least one as a property among codec, an encoding format including a compression parameter or the like, a resolution including horizontal and vertical pixel values, an aspect ratio, a scanning method representing whether it is interlace or progressive, a frame rate, and a still picture mode. 
     When the video component is a complex component, it may include an aggregation form and a media component list that the complex component includes, as a property. 
     When the video component is a composite component among complex components, it may include the role of each media component that the composite component includes, as a property. At this point, the role of a media component may represent an enhancement layer for scalable video encoding. According to another specific embodiment of the present invention, the role of a media component may represent one among the right image, left image, and depth information of a 3D image. According to another specific embodiment of the present invention, the role of a media component may represent a video at a specific position of a screen divided into a plurality of areas. 
     When the video component is a top level component among complex components, it may include at least one as a property among contents advisory rating and a related audio component. 
     The data additional service may include at least one as a property among language of additional service, a consumption mode, a list of essential capabilities, a list of non-essential capabilities, and a content item available in additional service. 
     The content item available in additional service may include at least one as a property among a triggered consumption model and a consumption model. Additionally, the content item available in additional service may include transmission availability on broadcast transmission and internet transmission. Additionally, an available content item may include at least one as a property among a service protection property, a targeting/personalization property, and contents advisory rating. 
     Additionally, each additional service may include a target screen as a property. At this point, the target screen may represent one among a primary device, a companion device, and both a primary device and a companion device. 
     According to a specific embodiment of the present invention, one media component may be shared by a plurality of broadcast services of the same broadcast stream. Additionally, a plurality of broadcast services in a different broadcast stream may share one media component. Accordingly, a method of a plurality of broadcast services to efficiently share one media component is required. For this, a broadcast transmission device may allow each media component or broadcast service to be associated with a unique resource identifier (URI). 
     This will be described in more detail with reference to  FIG. 75 . 
       FIG. 75  is a view when a media component or a broadcast service is mapped through URI in a broadcast service signaling table according to an embodiment of the present invention. 
     A broadcast service or a media component may be signaled through URI in the broadcast service signaling. At this point, information signaling broadcast service or media component through URI may be referred to as URI linkage information. The URI linkage information may include at least one among URI or private data independently defined by each broadcaster or region. 
     According to a specific embodiment of the present invention, as shown in  FIG. 75 , the URI linkage information may include a descriptor_tag field, a descriptor_length field, a uri_length field, a uri_char field, and a private_data_byte field. 
     The descriptor_tag field represents that URI linkage information is included. According to a specific embodiment of the present invention, the URI linkage information may be an 8-bit field. 
     The descriptor_length field represents the length of the URI linkage information after the descriptor_length field. According to a specific embodiment of the present invention, the descriptor length field may be an 8-bit field. 
     The uri_length field represents the length of the uri_char field. According to a specific embodiment of the present invention, the uri_length field may be an 8-bit field. 
     The uri_char field represents each character in URI character string. According to a specific embodiment of the present invention, the uri_char field may be an 8-bit field. 
     The private_data_byte field represents private data independently defined by each broadcaster or region. According to a specific embodiment of the present invention, the private_data_byte field may be an 8-bit field. 
     The broadcast reception device  100  may identify a media component or a broadcast service through URI of URI linkage information. When the URI of the URI linkage information identifies a media component, a broadcast service signaling table may include URI linkage information as component level information. When the URI of the URI linkage information identifies a broadcast service, a broadcast service signaling table may include URI linkage information as service level information. 
     The format of URI link information is described through bit stream in the embodiment of  FIG. 75  but is not limited thereto. Especially, URI link information may be in an XML file format. 
     A broadcast transmission device may transmit a broadcast service or a media component, which targets on users having a specific condition. Additionally, the broadcast reception device  100  may transmit information on a user of the broadcast reception device  100  and may receive a broadcast service or a media component proper for a user of the broadcast reception device  100 . For example, the broadcast reception device  100  may transmit information of a region where the broadcast reception device  100  is placed and may receive a broadcast service for a corresponding region. For this, required is a method of signaling information on a targeting criterion and a personalization property that a broadcast service or a media component targets. This will be described with reference to  FIG. 76 . 
       FIG. 76  is a view illustrating targeting criterion information signaling the targeting criterion of a broadcast service or a media component. 
     The broadcast service signaling table may include targeting criterion information signaling the target criterion of a broadcast service or a media component. 
     The targeting criterion information may include at least one among targeting identifier information for identifying a target criterion, targeting form information representing the form of targeting, and targeting criterion value information representing a specific targeting criterion. 
     According to a specific embodiment of the present invention, as shown in the embodiment of  FIG. 76 , the targeting criterion information may include at least one among a descriptor_tag field, a descriptor length field, a num_targeting_criteria field, a criterion_id_length field, a criterion_id field, a criterion_type_code field, a num_criterion_values field, a criterion_value_length field, and criterion value field. 
     The descriptor_tag field represents targeting criterion information. According to a specific embodiment of the present invention, the descriptor_tag field may be an 8-bit field. 
     The descriptor_length field represents the length of targeting criterion information after the descriptor_tag field. The descriptor_length field may be an 8-bit field. 
     The num_targeting_criteria field represents the number of targeting criterion information. According to an embodiment of the present invention, a targeting criterion that a broadcast service or a media component has may be in plurality. According to a specific embodiment of the present invention, the num_targeting_criteria field may be an 8-bit field. 
     The criterion_id_length field represents the length of the criterion_id field. According to a specific embodiment of the present invention, the criterion_id_length field may be an 8-bit field. 
     The criterion_id field represents a targeting criterion identifier for identifying a targeting criterion. According to a specific embodiment of the present invention, the criterion_id field may be an 8-bit field. 
     The criterion_type_code field represents the form of a targeting criterion. According to a specific embodiment of the present invention, the criterion_type_code may be a 3-bit field. 
     The num_criterion_values field represents the number of targeting criterion values. According to an embodiment of the present invention, a broadcast service or a media component may have a plurality of targeting criterion values corresponding to a targeting criterion form. According to a specific embodiment of the present invention, the num_criterion_values field may be a 5-bit field. 
     The criterion_value_length field represents the length of the criterion_value field. According to a specific embodiment of the present invention, the criterion_value_length field may be an 8-bit field. 
     The criterion_value field represents a targeting criterion value. 
     According to a specific embodiment of the present invention, when targeting criterion information signals the targeting criterion of a media component, the broadcast service signaling table may include targeting criterion information as component level information. According to a specific embodiment of the present invention, when targeting criterion information signals the targeting criterion of a broadcast service, the broadcast service signaling table may include targeting criterion information as service level information. 
     Targeting criterion information is described through a bit stream format in the embodiment of  FIG. 76  but is not limited thereto. Especially, the targeting criterion information may be in an XML file format. 
     The broadcast service signaling table may include text information for describing a broadcast service or a media component. This will be described in more detail with reference to  FIG. 77 . 
       FIG. 77  is a view illustrating text information for describing a broadcast service or a media component. 
     In more detail, the text information may include at least one among information representing the kind of text language, an identifier for identifying text information, and text information for describing a text including a broadcast service or a media component. 
     According to a specific embodiment of the present invention, as shown in the embodiment of  FIG. 77 , the text information may include a descriptor_number field, a last_descriptor_number field, a description_id field, a language_code field, a text_length field a text_char field. 
     The descriptor_number field represents the order of a descriptor. When one descriptor does not include all text information, text information is divided and included in a plurality of descriptors. At this point, the descriptor_number field represents a number of a corresponding descriptor among a plurality of descriptors. According to a specific embodiment of the present invention, the descriptor_number field may be a 4-bit field. 
     The last_descriptor_number field represents a number of the last descriptor including text information. According to a specific embodiment of the present invention, the last_descriptor_number field may be a 4-bit field. 
     The description_id field represents an identifier for identifying text information. In more detail, the broadcast reception device  100  may identify text information for a specific broadcast service or media component from text information for another media component or broadcast service, on the basis of a value of the description_id field. According to a specific embodiment of the present invention, the description_id field may be an 8-bit field. 
     The language_code field represents a language used in text information. According to a specific embodiment of the present invention, the language_code field may be a 24-bit field. 
     The text_length field represents the length of the text_char field. According to a specific embodiment of the present invention, the text_length field may be an 8-bit field. 
     The text_char field represents a character of text information. According to a specific embodiment of the present invention, the text_char field may be an 8-bit field. 
     According to a specific embodiment of the present invention, when text information signals a text for describing a media component, the broadcast service signaling table may include text information as component level information. According to a specific embodiment of the present invention, when text information signals text information for describing a broadcast service, the broadcast service signaling table may include text information as service level information. 
     The text information format is described through a bit stream format in the embodiment of  FIG. 77  but is not limited thereto. Especially, the text information may be in an XML file format. 
     A broadcast service may include a program, i.e., a temporal segment having a predetermined start time and play length. In more detail, an audio service includes an audio program. Moreover, the broadcast service including both audio and video may include a TV program. Additionally, the CoD service may include a user request program. Additionally, the standalone data service may include a data program. 
     Such a program may be divided according to a broadcast service time. Additionally, a time that an audio service is broadcasted is equal to the sum of durations of audio programs. A time that a broadcast service including both audio and video is broadcasted is equal to the sum of durations of TV programs. However, the duration of the CoD service represents both a time that a specific content is played and a time that the CoD service is available. Accordingly, a play time of each content depends on a user. However, while a contents item is provided, a start time and a length are limited according to a program. Accordingly, a contents item provided through the CoD service may be included in a catalog. At this point, the catalog may be an application providing a user interface for available service. 
     An audio program, a TV program, and a data program may include at least one among a unique identifier, a list of media components in a program, a start time and a length of a program, a text for describing a title and a program, a graphic icon, a contents advisory rating, a targeting/personalization property, and a contents protection property. Properties included in an audio program, a TV program, and a data program may be signaled through program information. This will be described with reference to  FIGS. 78 to 80 . 
       FIG. 78  is a view illustrating program information according to an embodiment of the present invention. 
     As shown in the embodiment of  FIG. 78 , the program information may include at least one among a table_id field, a section_syntax_indicator field, a private_indicator field, a section_length field, a table_id_extension field, a version_number field, a current_next_indicator field, a section_number field, a last_section_number field, a service_id field, and a program_information_block field. 
     The table_id field represents program information. According to a specific embodiment of the present invention, the table_id field may be an 8-bit field. 
     The section_syntax_indicator field represents whether program information is a private section table in the long format of MEPG-2 TS standard. According to a specific embodiment of the present invention, the section_syntax_indicator field may be a 1-bit field. 
     The private_indicator field represents whether a current table corresponds to a private section. According to a specific embodiment of the present invention, the private_indicator field may be a 1-bit field. 
     The section_length field represents the length of a section after the section_length field. According to a specific embodiment of the present invention, the section_length field may be a 12-bit field. 
     The table_id_extension field represents a value for identifying program information in combination with the table_id field. In more detail, the table_id_extension field may include at least one among the protocol_version field and the subnet_id field. The protocol_version field represents a protocol version of program information. In more detail, the protocol_version field may be an 8-bit field in which the upper four bits represent a major version number and the lower four bits represent a minor version number. When program information is transmitted through broadcast stream, the subnet_id field may represent a subnet identifier for identifying an IP subnet for transmitting program information. According to another specific embodiment of the present invention, a value of the subnet_id field may be 0. When program information is transmitted through internet network, the subnet_id field has the same value as the subnet_id field of program information transmitted through broadcast stream. According to a specific embodiment of the present invention, the subnet_id field may be an 8-bit field. 
     The version_number field represents a version of program information. The broadcast reception device  100  may determine the availability of program information on the basis of a value of the vserion_number field. In more detail, when a value of the version_number field is identical to a version of previously received service program information, the program information may not be used. According to a specific embodiment of the present invention, the version_number field may be a 5-bit field. 
     The current_next_indicator field represents whether program information is currently available. In more detail, when a value of the current_next_indicator field is 1, it may represent that program information is available. Moreover, when a value of the current_next_indicator field is 1, it may represent that the program information is available the next time. According to a specific embodiment of the present invention, the current_next_indicator field may be a 1-bit field. 
     The section_number field represents a current section number. According to a specific embodiment of the present invention, the section_number field may be an 8-bit field. 
     The last_section_number field represents the last section number. When the size of a program information table is large, the program information may be divided into a plurality of sections and then transmitted. At this point, the broadcast reception device  100  determines whether all sections necessary for program information are received on the basis of the section_number field and the last_section_number field. According to a specific embodiment of the present invention, the last_section_number field may be an 8-bit field. 
     The service_id field represents a service identifier for identifying a broadcast service relating to program information. In more detail, the service_id field may represent a service identifier for identifying a broadcast service including a program that program information signals. According to a specific embodiment of the present invention, the service_id field may be an 8-bit field. 
     The program_information_block field represents a program information block including information on the property of a program. This will be described in more detail with reference to  FIG. 79 . 
       FIG. 79  is a view illustrating a program information block according to an embodiment of the present invention. 
     The program information block may include the number of programs that the program information block signals, a program identifier for identifying a signaling program, a start time of a program, the length of a program, a text for describing a program, and a descriptor for signaling a text for describing a program and a property of a program. 
     According to a specific embodiment of the present invention, as shown in the embodiment of  FIG. 79 , the program information block may include at least one among a num_program field, a program_id field, a time_span_start field, a time_span_length field, a title_text_length field, a title_text field, a num_program_descriptors field, and a descriptor field. 
     The num_program field represents the number of programs that a program information block signals. According to a specific embodiment of the present invention, the num_program field may be an 8-bit field. 
     The program_id field represents a program identifier for identifying a corresponding program. According to a specific embodiment of the present invention, the program_id field may be an 8-bit field. 
     The time_span_start field represents a start time of a corresponding program. In more detail, the time_span_start field may represent a UTC time that elapsed from 00:00 Jan. 6, 1980. According to a specific embodiment of the present invention, the time_span_start field may be a 32-bit field. 
     The time_span_length field represents the length of a corresponding program. In more detail, a corresponding program may represent the length of a time that a corresponding program is broadcasted in minutes on the basis of a value of the time_span_start field. When a value of the time_span_length field is set once, it does not change in the future. According to a specific embodiment of the present invention, the time_span_length field may be a 16-bit field. 
     The title_text_length field represents the length of the title_text field. According to a specific embodiment of the present invention, the title_text field may be an 8-bit field. 
     The title_text field represents each character that the title of a corresponding program includes. According to a specific embodiment of the present invention, each character may be in a UTF-8 encoding format. According to a specific embodiment of the present invention, the title_text field may be an 8-bit field. 
     The num_program_descriptors field represents the number of descriptors that a program information block includes. According to a specific embodiment of the present invention, the num_program_descriptors field may be an 8-bit field. 
     The descriptor field represents a descriptor including information relating to a property of a program. For example, a descriptor that the descriptor field has may include information on a media component list. Additionally, a descriptor that the descriptor field has may include information on a contents advisory rating. Additionally, a descriptor that the descriptor field has may include information on a targeting property. Additionally, a descriptor that the descriptor field has may include information on a text for describing a program. Accordingly, the descriptor field may include at least one among the component_list_descriptor field, the targeting_descriptor field, and the text_descriptor field. However, the program information block shown in  FIG. 79  may not signal the property of a media component through component level information. Accordingly, a plurality of media components having various properties may not be signaled efficiently. A method for resolving the above issue will be described with reference to  FIG. 80 . 
       FIG. 80  is a view illustrating a program information block according to another embodiment of the present invention. 
     The program information block may include the number of media components that a corresponding program includes, a component identifier for identifying a corresponding media component, information for representing whether a corresponding media component is a media component necessary for corresponding program playback, and a component descriptor including an additional property of a media component. 
     According to a specific embodiment of the present invention, as shown in the embodiment of  FIG. 80 , the program information block may include at least one among a num_component field, a component_id field, an essential_component_indicator field, a num_component_descriptors field, and a component_descriptor field. 
     The num_component field represents the number of media components that a corresponding program includes. According to a specific embodiment of the present invention, the num_component field may be an 8-bit field. 
     The component_id field represents a component identifier for identifying a corresponding media component. According to a specific embodiment of the present invention, the component_id field may be an 8-bit field. 
     The essential_component_indicator field represents whether a corresponding media component is an essential media component essential to a corresponding broadcast service presentation. According to a specific embodiment of the present invention, the essential_component_indicator field may be a 1-bit field. 
     The num_component_descriptors field represents the number of component_descriptor fields. According to a specific embodiment of the present invention, the num_component_descriptors field may be an 8-bit field. 
     The component_descriptor field represents a component descriptor including an additional property on a corresponding component. 
     The program information and the program information block in a bit stream format are described through  FIGS. 78 to 80  but the present invention is not limited to the bit stream format. Especially, the program information and the program information block may be in an XML file format. 
       FIG. 81  is a view when a broadcast service is divided into a plurality of segments. 
     As described above, a broadcast service may include a plurality of programs. At this point, a program may include a plurality of segments. A segment is a time interval configuring a program. A segment may include a show segment broadcasting the feature content of a program and an interstitial segment broadcasting a content not relating to the feature content of the program between the feature contents of the program. At this point, the interstitial segment may include ads or public service announcement. The show segment and the interstitial segment including audio service or both audio and video may have a scheduled start time and duration. 
     The segment may include at least one as one property among a unique identifier for identifying a segment, a list of media components played during a time interval of a corresponding segment, a start time and the duration of a segment, a segment type, and a targeting/personalization property, and a contents advisory rating. As described above, the segment type may be one among a show segment and an interstitial segment. An anchored segment represents a segment relating to a specific program and having a specified start time. On the other hand, an unanchored segment represents a segment not relating to a specific program and not having a specified start time. It is necessary to efficiently signal such a segment. Signaling a segment will be described with reference to  FIGS. 82 to 84 . 
       FIG. 82  is a view illustrating segment information program information according to an embodiment of the present invention. 
     The segment information may include a segment block including a specific segment property. 
     According to a specific embodiment of the present invention, as shown in the embodiment of  FIG. 82 , the segment information may include at least one among a table_id field, a section_syntax_indicator field, a private_indicator field, a section_length field, a table_id_extension field, a version_number field, a current_next_indicator field, a section_number field, a last_section_number field, and a segment_information_block field. 
     The table_id field represents segment information is included. According to a specific embodiment of the present invention, the table_id field may be an 8-bit field. 
     The section_syntax_indicator field represents whether broadcast service segment information is a private section table in a long format of MEPG-2 TS standard. According to a specific embodiment of the present invention, the section_syntax_indicator field may be a 1-bit field. 
     The private_indicator field represents whether a current table corresponds to a private section. According to a specific embodiment of the present invention, the private_indicator field may be a 1-bit field. 
     The section_length field represents the length of a section after the section_length field. According to a specific embodiment of the present invention, the section_length field may be a 12-bit field. 
     The table_id_extension field represents a value for identifying segment information in combination with the table_id field. In more detail, the table_id_extension field may include at least one among the protocol_version field and the subnet_id field. The protocol_version field represents a protocol version of segment information. In more detail, the protocol_version field may be an 8-bit field in which the upper four bits represent a major version number and the lower four bits represent a minor version number. When segment information is transmitted through broadcast stream, the subnet_id field may represent a subnet identifier for identifying an IP subnet for transmitting segment information. According to another specific embodiment of the present invention, a value of the subnet_id field may be 0. When segment information is transmitted through internet network, the subnet_id field has the same value as the subnet_id field of segment information transmitted through broadcast stream. According to a specific embodiment of the present invention, the subnet_id field may be an 8-bit field. 
     The version_number field represents a version of segment information. The broadcast reception device  100  may determine the availability of segment information on the basis of a value of the vserion_number field. In more detail, when a value of the version_number field is identical to a version of previously received service segment information, the segment information may not be used. According to a specific embodiment of the present invention, the version_number field may be a 5-bit field. 
     The current_next_indicator field represents whether segment information is currently available. In more detail, when a value of the current_next_indicator field is 1, it may represent that segment information is available. Moreover, when a value of the current_next_indicator field is 1, it may represent that segment information is available the next time. According to a specific embodiment of the present invention, the current_next_indicator field may be a 1-bit field 
     The section_number field represents a current section number. According to a specific embodiment of the present invention, the section_number field may be an 8-bit field. 
     The last_section_number field represents the last section number. When the size of a segment information table is large, the segment information may be divided into a plurality of sections and then transmitted. At this point, the broadcast reception device  100  determines whether all sections necessary for segment information are received on the basis of the section_number field and the last_section_number field. According to a specific embodiment of the present invention, the last_section_number field may be an 8-bit field. 
     The service_id field represents a service identifier for identifying a broadcast service relating to segment information. In more detail, the service_id field may represent a service identifier for identifying a broadcast service including a segment that segment information signals. According to a specific embodiment of the present invention, the service_id field may be an 8-bit field. 
     The program_information_block field represents a segment information block including information on the property of a segment. This will be described in more detail with reference to  FIG. 83 . 
       FIG. 83  is a view illustrating a segment information block according to an embodiment of the present invention. 
     The segment information block in segment information may include at least one among a segment identifier for identifying a signaling segment, a segment type, information representing whether there is a program relating to a segment, information representing whether a start time and the duration of a segment is specified, a program identifier for identifying a program relating to a segment, a start time of a segment, the number of media components in a segment, a media component identifier for identifying a corresponding media component, the number of descriptors including a property for a corresponding media component, a descriptor including a property for a corresponding media component, the number of descriptors including a property for a corresponding segment, and a descriptor including a corresponding segment. 
     According to a specific embodiment of the present invention, as shown in the embodiment of  FIG. 83 , the segment information may include at least one among a segment_id field, a segment_type field, an associated_program_flag field, a time_included field, a program_id field, a time_span_start field, a time_span_length field, a num_component field, a component_id field, a num_component_descriptors field, a component_descriptors field, a num_descriptor field, and a descriptor field. 
     The segment_id field represents a segment identifier for identifying a corresponding segment. According to a specific embodiment of the present invention, the segment_id field may be an 8-bit field. 
     The segment_type field represents the type of a corresponding segment. In more detail, it may represent a show segment or an interstitial segment. According to a specific embodiment of the present invention, when a value of the segment_type field is 0x02, it represents a show segment and when a value of the segment_type field is a value between 0x03 to 0x07, it represents an interstitial segment According to a specific embodiment of the present invention, the segment_type field may be a 3-bit field. 
     The associated_program_flag field represents whether there is a program relating to a corresponding segment. In more detail, when a value of the associated_program_flag field is 1, it represents that there is a program relating to a corresponding segment and when a value of the associated_program_flag field is 0, it represents that there is no program relating to a corresponding segment. According to a specific embodiment of the present invention, the associated_program_flag field may be a 1-bit field. 
     The time_included field represents whether a start time and duration of a corresponding segment is specified. In more detail, when a value of the time_included field is 1, it represents that a start time and duration of a corresponding segment is specified and when a value of the time_included field is 0, it represents that a start time and duration of a corresponding segment is not specified. According to a specific embodiment of the present invention, the time_included field may be a 1-bit field. 
     The program_id field represents a program identifier for identifying a program relating to a corresponding program. According to a specific embodiment of the present invention, the program_id field may be a 16-bit field. 
     The time_span_start field represents a start time of a corresponding segment. In more detail, the time_span_start field may represent a UTC time that elapsed from 00:00 Jan. 6, 1980. According to a specific embodiment of the present invention, the time_span_start field may be a 32-bit field. 
     The time_span_length field represents the length of a corresponding segment. In more detail, a corresponding segment may represent the length of a time that a corresponding program is broadcasted in minutes on the basis of a value of the time_span_start field. When a value of the time_span_length field is set once, it does not change in the future. According to a specific embodiment of the present invention, the time_span_length field may be a 16-bit field. 
     The num_component field represents the number of media components that a corresponding segment includes. According to a specific embodiment of the present invention, the num_component field may be an 8-bit field. 
     The component_id field represents a component identifier for identifying a corresponding media component. According to a specific embodiment of the present invention, the component_id field may be an 8-bit field. 
     The num_component_descriptors field represents the number of component_descriptor fields. According to a specific embodiment of the present invention, the num_component_descriptors field may be an 8-bit field. 
     The component_descriptor field represents a component descriptor including an additional property on a corresponding component. 
     The num_descriptor field represents the number of descriptor fields. According to a specific embodiment of the present invention, the num_descriptors field may be an 8-bit field. 
     The descriptor field represents a descriptor including an additional property. For example, the descriptor may include at least one among a contents advisory rating and a targeting property. Accordingly, the descriptor field may be the targeting_descriptor field. 
     When a program is divided into a plurality of segments, even when a viewer watches the same program, another segment may be provided according to the characteristics of each viewer. Especially, segments according the characteristics of each viewer may be provided to an interstitial segment instead of the feature segment. Through this, broadcasters may provide the feature broadcast of the same content and also may provide a target advertisement to viewers according to the characteristics of each viewer. For this, it is necessary to provide a targeting segment set signaling the targeting information and property of each segment. This will be described with reference to  FIG. 84 . 
       FIG. 84  is a view illustrating a targeting segment set information according to an embodiment of the present invention. 
     The targeting segment set may signal targeting information on a plurality of segments. Especially, the targeting segment set information may signal targeting information on a plurality of segments having the same duration. According to a specific embodiment of the present invention, the targeting segment set information may signal targeting information on a plurality of segments relating to the same program. According to another specific embodiment of the present invention, targeting segment information may signal targeting information on a plurality of segments having the same start time. 
     The targeting segment set information may include at least one among a start time of a corresponding segment, the duration of a segment, the number of segments that a targeting segment set includes, a segment identifier for identifying a corresponding segment, the number of targeting criteria that targeting segment set information includes, targeting identification information for identifying a target criterion, targeting form information representing the form of targeting, and targeting criterion value information representing a specific targeting criterion. 
     According to a specific embodiment of the present invention, as shown in the embodiment of  FIG. 84 , the targeting segment set information may include at least one among a descriptor_tag field, a descriptor_length field, a time_span_start field, a time_span_length field, a num_segment field, a segment_id field, a num_targeting_criteria field, a criterion_id_length field, a criterion_id field, a criterion_type_code field, a num_criterion_values field, a criterion_value_length field, and a criterion value field. 
     The descriptor_tag field represents targeting segment set information. According to a specific embodiment of the present invention, the descriptor_tag field may be an 8-bit field. 
     The descriptor_length field represents the length of targeting segment information after the descriptor_tag field. The descriptor_length field may be an 8-bit field. 
     The time_span_start field represents a start time of a corresponding segment. In more detail, the time_span_start field may represent a UTC time that elapsed from 00:00 Jan. 6, 1980. According to a specific embodiment of the present invention, the time_span_start field may be a 32-bit field. 
     The time_span_length field represents the length of a corresponding segment. In more detail, a corresponding segment may represent the length of a time that a corresponding program is broadcasted in minutes on the basis of a value of the time_span_start field. When a value of the time_span_length field is set once, it does not change in the future. According to a specific embodiment of the present invention, the time_span_length field may be a 16-bit field. 
     The num_segments field represents the number of segments that targeting segment set information signals. According to a specific embodiment of the present invention, the num_segments field may be an 8-bit field. 
     The num_targeting_criteria field represents the number of targeting segment set information. According to an embodiment of the present invention, a targeting criterion that a broadcast service or a media component has may be in plurality. According to a specific embodiment of the present invention, the num_targeting_criteria field may be an 8-bit field. 
     The criterion_id_length field represents the length of the criterion_id field. According to a specific embodiment of the present invention, the criterion_id_length field may be an 8-bit field. 
     The criterion_id field represents a targeting criterion identifier for identifying a targeting criterion. According to a specific embodiment of the present invention, the criterion_id field may be an 8-bit field. 
     The criterion_type_code field represents the form of a targeting criterion. According to a specific embodiment of the present invention, the criterion_type_code may be a 3-bit field. 
     The num_criterion_values field represents the number of targeting criterion values. According to an embodiment of the present invention, a segment may have a plurality of targeting criterion values corresponding to a targeting criterion form. According to a specific embodiment of the present invention, the num_criterion_values field may be a 5-bit field. 
     The criterion_value_length field represents the length of the criterion_value field. According to a specific embodiment of the present invention, the criterion_value_length field may be an 8-bit field. 
     The criterion_value field represents a targeting criterion value. 
     In consideration of a broadcast reception situation or the specification of the broadcast reception device  100 , if a specific segment cannot be received, the broadcast reception device  100  may receive or play another segment on the basis of targeting segment set information. For example, if the broadcast reception device  100  does not support the playback of a 3D image, it may receive or play a segment including a 2D image on the basis of a targeting segment set instead of a segment. According to another specific embodiment of the present invention, the broadcast reception device  100  may selectively receive or play only content suitable for a user on the basis of targeting segment set information. For example, if a viewer is youth, the broadcast reception device  100  may receive or play a trailer of a youth movie instead of a trailer of an adult movie. 
     The case in which segment information, a segment information block, segment targeting set information are in a bit stream format is described above with reference to  FIGS. 82 to 84 . However, the formats of segment information, a segment information block, and segment targeting set information are not limited to the bit stream format. Especially, segment information, a segment information block, and segment targeting set information may be in an XML file format. Additionally, according to a specific embodiment of the present invention, the above-described program information may include segment information, a segment information block, and segment targeting set information. 
     Operations of a broadcast transmission device and the broadcast reception device  100  transmitting/receiving the properties of a program and a segment will be described with reference to  FIGS. 85 and 86 . 
       FIG. 85  is a view when a broadcast transmission device transmits broadcast signal including at least one among program information and segment information according to an embodiment of the present invention. 
     The broadcast transmission device obtains the property of a program that a broadcast service includes through a control unit in operation S 101 . As described above, the property of a program may include at least one among a unique identifier, a list of media components in a program, a start time and a length of a program, a text for describing a title and a program, a graphic icon, a contents advisory rating, a targeting/personalization property, and a contents protection property. 
     The broadcast transmission device generates program information signaling a program on the basis of the property of a program through a control unit in operation S 803 . The program information may include at least one among the program information and the program information block described through  FIGS. 78 and 79 . 
     The broadcast transmission device obtains the property of a segment that a program includes through a control unit in operation S 805 . As described above, the property of a segment may include at least one as one property among a unique identifier for identifying a segment, a list of media components played during a time interval of a corresponding segment, a start time and the duration of a segment, a segment type, and a targeting/personalization property, and a contents advisory rating. 
     The broadcast transmission device generates segment information on the basis of the property of a program through a control unit in operation S 807 . The segment information may include at least one among the above-mentioned segment information, segment information block, and segment targeting set information of  FIGS. 82 to 84 . 
     The broadcast transmission device transmits a broadcast signal including at least one among segment information and program information through a transmission unit in operation S 809 . According to a specific embodiment of the present invention, a broadcast transmission device may transmit at least one among segment information and program information via an IP network through an IP communication unit transmitting/receiving IP data. 
       FIG. 86  is a view when a broadcast reception device receives broadcast signal including at least one among program information and segment information according to an embodiment of the present invention. 
     The broadcast reception device  100  receives a broadcast signal through the broadcast reception unit  110  in operation S 901 . 
     The broadcast reception device  100  obtains program information on the basis of a broadcast signal through the control unit  150  in operation S 903 . In more detail, the broadcast reception device  100  may obtain broadcast information from the broadcast signal. At this point, the program information may include at least one among the program information and the program information block described through  FIGS. 78 and 79 . According to a specific embodiment of the present invention, the broadcast reception device  100  may obtain broadcast information via an IP network through the IP communication unit  130 . Especially, in the case that the intensity of a broadcast signal is weak or it is difficult to receive a broadcast signal, the broadcast reception device  100  may obtain program information via an IP network. 
     The broadcast reception device  100  obtains the property of a program on the basis of the program information through the control unit  150  in operation S 905 . As described above, the property of a program may include at least one among a unique identifier, a list of media components in a program, a start time and a length of a program, a text for describing a title and a program, a graphic icon, a contents advisory rating, a targeting/personalization property, and a contents protection property. 
     The broadcast reception device  100  obtains segment information on the basis of a broadcast signal through the control unit  150  in operation S 907 . In more detail, the broadcast reception device  100  may obtain segment information from the broadcast signal. The segment information may include at least one among the above-mentioned segment information, segment information block, and segment targeting set information of  FIGS. 82 to 84 . According to a specific embodiment of the present invention, the broadcast reception device  100  may obtain segment information via an IP network through the IP communication unit  130 . Especially, in the case that the intensity of a broadcast signal is weak or it is difficult to receive a broadcast signal, the broadcast reception device  100  may obtain segment information via an IP network. 
     The broadcast reception device  100  obtains the property of a segment on the basis of the segment information through the control unit  150  in operation S 909 . The segment information may include at least one among the above-mentioned segment information, segment information block, and segment targeting set information of  FIGS. 82 to 84 . 
     The broadcast reception device  100  generates a program guide for displaying the property of a program on the basis of at least one among the program property and the segment property in operation S 911 . According to an embodiment of the present invention, a program guide may also display the property of a segment that a program includes. 
     According to an embodiment of the present invention, provided are a broadcast transmission device, an operation method thereof, a broadcast reception device, and an operation method thereof in order to efficiently transmit/receive a plurality of media components. 
     Especially, according to an embodiment of the present invention, provided are a broadcast transmission device, an operation method thereof, a broadcast reception device, and an operation method thereof in order to efficiently broadcast information on a plurality of media components and a transmission path. 
     The present invention is not limited to the features, structures, and effects described in the above embodiments. Furthermore, the features, structures, and effects in each embodiment may be combined or modified by those skilled in the art. Accordingly, it should be interpreted that contents relating to such combinations and modifications are included in the scope of the present invention. 
     While this invention has been particularly shown and described with reference to preferred embodiments thereof, it will be understood by those skilled 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. For example, each component in an embodiment is modified and implemented. Accordingly, it should be interpreted that differences relating to such modifications and applications are included in the scope of the appended claims.