US20160277545A1 - Method for transmitting broadcast signals, apparatus for transmitting broadcast signals, method for receiving broadcast signals and apparatus for receiving broadcast signals - Google Patents

Method for transmitting broadcast signals, apparatus for transmitting broadcast signals, method for receiving broadcast signals and apparatus for receiving broadcast signals Download PDF

Info

Publication number
US20160277545A1
US20160277545A1 US14/913,279 US201514913279A US2016277545A1 US 20160277545 A1 US20160277545 A1 US 20160277545A1 US 201514913279 A US201514913279 A US 201514913279A US 2016277545 A1 US2016277545 A1 US 2016277545A1
Authority
US
United States
Prior art keywords
information
broadcast
signaling
service
broadcast service
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US14/913,279
Other languages
English (en)
Inventor
Minsung Kwak
Sejin Oh
Kyoungsoo Moon
Jangwon Lee
Woosuk Ko
Sungryong Hong
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Priority to US14/913,279 priority Critical patent/US20160277545A1/en
Assigned to LG ELECTRONICS INC. reassignment LG ELECTRONICS INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: HONG, Sungryong, KO, WOOSUK, KWAK, Minsung, LEE, JANGWON, OH, Sejin, MOON, KYOUNGSOO
Publication of US20160277545A1 publication Critical patent/US20160277545A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N19/00—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals
    • H04N19/46—Embedding additional information in the video signal during the compression process
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0041—Arrangements at the transmitter end
    • H04L1/0042—Encoding specially adapted to other signal generation operation, e.g. in order to reduce transmit distortions, jitter, or to improve signal shape
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04H—BROADCAST COMMUNICATION
    • H04H20/00—Arrangements for broadcast or for distribution combined with broadcast
    • H04H20/10—Arrangements for replacing or switching information during the broadcast or the distribution
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04H—BROADCAST COMMUNICATION
    • H04H60/00—Arrangements for broadcast applications with a direct linking to broadcast information or broadcast space-time; Broadcast-related systems
    • H04H60/09—Arrangements for device control with a direct linkage to broadcast information or to broadcast space-time; Arrangements for control of broadcast-related services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04H—BROADCAST COMMUNICATION
    • H04H60/00—Arrangements for broadcast applications with a direct linking to broadcast information or broadcast space-time; Broadcast-related systems
    • H04H60/09—Arrangements for device control with a direct linkage to broadcast information or to broadcast space-time; Arrangements for control of broadcast-related services
    • H04H60/14—Arrangements for conditional access to broadcast information or to broadcast-related services
    • H04H60/19—Arrangements for conditional access to broadcast information or to broadcast-related services on transmission of information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0009—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0057—Block codes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0071—Use of interleaving
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0072—Error control for data other than payload data, e.g. control data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/164—Adaptation or special uses of UDP protocol
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/262—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
    • H04N21/4363—Adapting the video stream to a specific local network, e.g. a Bluetooth® network
    • H04N21/43637—Adapting the video stream to a specific local network, e.g. a Bluetooth® network involving a wireless protocol, e.g. Bluetooth, RF or wireless LAN [IEEE 802.11]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W72/005—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H04L2001/0093—Point-to-multipoint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Definitions

  • the present invention relates to a method and apparatus for transmitting and receiving broadcast signals.
  • a digital broadcast signal may include a larger amount of video/audio data than an analog broadcast signal and may further include various types of additional data.
  • a digital broadcast system can provide HD (high definition) images, multi-channel audio and various additional services.
  • HD high definition
  • data transmission efficiency for transmission of large amounts of data, robustness of transmission/reception networks and network flexibility in consideration of mobile reception equipment need to be improved for digital broadcast.
  • the object of the present invention can be achieved by providing a method for transmitting a broadcast signal including encoding a broadcast service and signaling information of a transport session for transmitting components of the broadcast service, generating the broadcast signal including the encoded broadcast service and signaling information, and transmitting the generated broadcast signal.
  • the signaling information may include service identification information for identifying the broadcast service and information on a real-time object delivery over unidirectional transport (ROUTE) session for transmitting the broadcast service identified by the service identification information.
  • service identification information for identifying the broadcast service
  • ROUTE unidirectional transport
  • the information on the ROUTE session may include source IP address information of the ROUTE session, destination IP address information of the ROUTE session and destination port number information of the ROUTE session.
  • the information on the ROUTE session may include information for identifying a physical layer pipe (PLP) for transmitting the ROUTE session.
  • PLP physical layer pipe
  • the information on the ROUTE session may include information on a layered coding transport (LCT) session for transmitting the components of the broadcast service.
  • LCT layered coding transport
  • the information on the LCT session may include information for identifying the LCT session, information for identifying a physical layer pipe for transmitting the LCT session, information on a source flow transmitted by the LCT session and information on a repair flow transmitted by the LCT session.
  • a method for receiving a broadcast signal including receiving a broadcast signal including a broadcast service and signaling information of a transport session for transmitting components of the broadcast service, parsing the broadcast service and signaling information from the received broadcast signal, and decoding the parsed broadcast service and signaling information.
  • the signaling information may include service identification information for identifying the broadcast service and information on a real-time object delivery over unidirectional transport (ROUTE) session for transmitting the broadcast service identified by the service identification information.
  • service identification information for identifying the broadcast service
  • ROUTE unidirectional transport
  • the information on the ROUTE session may include source IP address information of the ROUTE session, destination IP address information of the ROUTE session and destination port number information of the ROUTE session.
  • the information on the ROUTE session may include information for identifying a physical layer pipe (PLP) for transmitting the ROUTE session.
  • PLP physical layer pipe
  • the information on the ROUTE session may include information on a layered coding transport (LCT) session for transmitting the components of the broadcast service.
  • LCT layered coding transport
  • the information on the LCT session may include information for identifying the LCT session, information for identifying a physical layer pipe for transmitting the LCT session, information on a source flow transmitted by the LCT session and information on a repair flow transmitted by the LCT session.
  • an apparatus for transmitting a broadcast signal including an encoder configured to encode a broadcast service and signaling information of a transport session for transmitting components of the broadcast service, a broadcast signal generator configured to generate the broadcast signal including the encoded broadcast service and signaling information, and a transmitter configured to transmit the generated broadcast signal.
  • the signaling information may include service identification information for identifying the broadcast service and information on a real-time object delivery over unidirectional transport (ROUTE) session for transmitting the broadcast service identified by the service identification information.
  • service identification information for identifying the broadcast service
  • ROUTE unidirectional transport
  • an apparatus for receiving a broadcast signal including a receiver configured to receive a broadcast signal including a broadcast service and signaling information of a transport session for transmitting components of the broadcast service, a parser configured to parse the broadcast service and signaling information from the received broadcast signal, and a decoder configured to decode the parsed broadcast service and signaling information.
  • An embodiment of the present invention provides a broadcast service by controlling QoS (Quality of Service) of each service or service component and by processing data according to features of each service.
  • QoS Quality of Service
  • An embodiment of the present invention provides a transmission flexibility by transmitting various broadcast services through the same RF (radio frequency) signal bandwidth.
  • An embodiment of the present invention enhances Robustness of a broadcast signal and an efficiency of a data transmission by using MIMO (Multiple Input Multiple Output) system.
  • MIMO Multiple Input Multiple Output
  • An embodiment of the present invention provides a broadcast transmission apparatus, an operation method of the broadcast transmission apparatus, a broadcast reception apparatus, and an operation method of the broadcast reception apparatus that are capable of acquiring digital broadcast signals without errors although we are using mobile receiving apparatus or we are in door.
  • 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 block 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 a BICM block according to an embodiment of the present invention.
  • FIG. 5 illustrates a BICM block according to another embodiment of the present invention.
  • FIG. 6 illustrates a frame building block according to one embodiment of the present invention.
  • FIG. 7 illustrates an OFDM generation block according to an embodiment of the present invention.
  • FIG. 8 illustrates a structure of an apparatus for receiving broadcast signals for future broadcast services according to an embodiment of the present invention.
  • FIG. 9 illustrates a frame structure according to an embodiment of the present invention.
  • FIG. 10 illustrates a signaling hierarchy structure of the frame according to an embodiment of the present invention.
  • FIG. 11 illustrates preamble signaling data according to an embodiment of the present invention.
  • FIG. 12 illustrates PLS1 data according to an embodiment of the present invention.
  • FIG. 13 illustrates PLS2 data according to an embodiment of the present invention.
  • FIG. 14 illustrates PLS2 data according to another embodiment of the present invention.
  • FIG. 15 illustrates a logical structure of a frame according to an embodiment of the present invention.
  • FIG. 16 illustrates PLS mapping according to an embodiment of the present invention.
  • FIG. 17 illustrates EAC mapping according to an embodiment of the present invention.
  • FIG. 18 illustrates FIC mapping according to an embodiment of the present invention.
  • FIG. 19 illustrates an FEC structure according to an embodiment of the present invention.
  • FIG. 20 illustrates a time interleaving according to an embodiment of the present invention.
  • FIG. 21 illustrates the basic operation of a twisted row-column block interleaver according to an embodiment of the present invention.
  • FIG. 22 illustrates an operation of a twisted row-column block interleaver according to another embodiment of the present invention.
  • FIG. 23 illustrates a diagonal-wise reading pattern of a twisted row-column block interleaver according to an embodiment of the present invention.
  • FIG. 24 illustrates interlaved XFECBLOCKs from each interleaving array according to an embodiment of the present invention.
  • FIG. 25 illustrates signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • FIG. 26 illustrates FI schemes of FSS in signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • FIG. 27 illustrates operation of a reset mode in signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • FIG. 28 illustrates equations indicating input and output of the frequency interleaver in signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • FIG. 29 illustrates equations of a logical operation mechanism of frequency interleaving based on FI scheme #1 and FI scheme #2 in signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • FIG. 30 illustrates an example in which the number of symbols is an even number in signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • FIG. 31 illustrates an example in which the number of symbols is an even number in signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • FIG. 32 illustrates an example in which the number of symbols is an odd number in signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • FIG. 33 illustrates an example in which the number of symbols is an odd number in signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • FIG. 34 illustrates operation of the frequency deinterleaver in signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • FIG. 35 illustrates the concept of a variable bit-rate system according to an embodiment of the present invention.
  • FIG. 36 illustrates writing and reading operations of block interleaving according to an embodiment of the present invention.
  • FIG. 37 shows equations representing block interleaving according to an embodiment of the present invention.
  • FIG. 38 illustrates virtual FEC blocks according to an embodiment of the present invention.
  • FIG. 39 shows equations representing reading operation after insertion of virtual FEC blocks according to an embodiment of the present invention.
  • FIG. 40 is a flowchart illustrating a time interleaving process according to an embodiment of the present invention.
  • FIG. 41 shows equations representing a process of determining a shift value and a maximum TI block size according to an embodiment of the present invention.
  • FIG. 42 illustrates writing operation according to an embodiment of the present invention.
  • FIG. 43 illustrates reading operation according to an embodiment of the present invention.
  • FIG. 44 illustrates a result of skip operation in reading operation according to an embodiment of the present invention.
  • FIG. 45 shows a writing process of time deinterleaving according to an embodiment of the present invention.
  • FIG. 46 illustrates a writing process of time deinterleaving according to another embodiment of the present invention.
  • FIG. 47 shows equations representing reading operation of time deinterleaving according to another embodiment of the present invention.
  • FIG. 48 is a flowchart illustrating a time deinterleaving process according to an embodiment of the present invention.
  • FIG. 49 is a diagram showing a protocol stack supporting a broadcast service according to one embodiment of the present invention.
  • FIG. 50 is a diagram showing a transport layer of a broadcast service according to one embodiment of the present invention.
  • FIG. 51 is a diagram showing the configuration of a media content transmission and reception system via an IP network according to one embodiment of the present invention.
  • FIG. 52 is a diagram showing the structure of a media presentation description (MPD) according to one embodiment of the present invention.
  • MPD media presentation description
  • FIG. 53 is a diagram showing the configuration of a broadcast reception apparatus according to one embodiment of the present invention.
  • FIGS. 54 to 55 are diagrams showing the configuration of a broadcast reception apparatus according to another embodiment of the present invention.
  • FIG. 56 is a diagram showing the configuration of a broadcast reception apparatus according to another embodiment of the present invention.
  • FIG. 57 is a diagram showing a broadcast transport frame according to one embodiment of the present invention.
  • FIG. 58 is a diagram showing a broadcast transport frame according to another embodiment of the present invention.
  • FIG. 59 is a diagram showing the configuration of a transport packet according to one embodiment of the present invention.
  • FIG. 60 is a diagram showing the configuration of a service signaling message according to one embodiment of the present invention.
  • FIG. 61 is a diagram showing the configuration of a service signaling message according to one embodiment of the present invention.
  • FIG. 62 is a diagram showing the configuration of a broadcast service signaling message in a next generation broadcast system according to one embodiment of the present invention.
  • FIG. 63 is a diagram showing the meaning of the value of a timebase_transport_mode field and a signaling_transport_mode field in a service signaling message according to one embodiment of the present invention.
  • FIGS. 64 to 70 are diagrams showing the syntax of a bootstrap( ) field according to the values of the timebase_transport_mode field and the signaling_transport_mode field in one embodiment of the present invention.
  • FIG. 71 is a diagram showing a process of acquiring a timebase and a service signaling message in the embodiments of FIGS. 62 to 70 .
  • FIG. 72 is a diagram showing the configuration of a broadcast service signaling message in a next generation broadcast system according to one embodiment of the present invention.
  • FIG. 73 is a diagram showing the configuration of a broadcast service signaling message in a next generation broadcast system according to one embodiment of the present invention.
  • FIG. 74 is a diagram showing the meaning of the value of each transport mode described in FIG. 73 .
  • FIG. 75 is a diagram showing the configuration of a signaling message for signaling a component data acquisition path of a broadcast service in a next generation broadcast system.
  • FIG. 76 is a diagram showing the syntax of an app_delevery_info( ) field according to one embodiment of the present invention.
  • FIG. 77 is a diagram showing the syntax of an app_delevery_info( ) field according to another embodiment of the present invention.
  • FIG. 78 is a diagram showing component location signaling including path information capable of acquiring one or more component data configuring a broadcast service.
  • FIG. 79 is a diagram showing the configuration of the component location signaling of FIG. 78 .
  • FIG. 80 is a diagram showing other information included in signaling of a broadcast service in a next generation broadcast system in one embodiment of the present invention.
  • FIG. 81 is a diagram showing a transport mode included in service signaling of a next generation broadcast system according to one embodiment of the present invention.
  • FIG. 82 is a diagram showing information on a bootstrap included in service signaling of a next generation broadcast system according to one embodiment of the present invention.
  • FIG. 83 is a diagram showing other information included in signaling for an object flow.
  • FIG. 84 is a diagram showing a combination of information for representing a file template in one embodiment of the present invention.
  • FIG. 85 is a diagram showing an object flow included in service signaling according to one embodiment of the present invention.
  • FIG. 86 is a diagram showing other information included in signaling of a broadcast service in a next generation broadcast system in one embodiment of the present invention.
  • FIG. 87 is a diagram showing signaling information for transport session information of a session level according to one embodiment of the present invention.
  • FIG. 88 is a diagram showing signaling information for transport session information of a session level according to another embodiment of the present invention.
  • FIG. 89 is a diagram showing signaling information of a broadcast service according to another embodiment of the present invention.
  • FIG. 90 is a diagram showing FDT related information included in signaling information of a broadcast service according to another embodiment of the present invention.
  • FIG. 91 is a diagram showing the configuration of the binary format of a Service_Mapping_Table according to one embodiment of the present invention.
  • FIG. 92 is a diagram showing the configuration of the XML format of a Service_Mapping_Table according to one embodiment of the present invention.
  • FIG. 93 is a diagram showing a process of receiving service signaling information included in a service mapping table according to one embodiment of the present invention.
  • FIG. 94 is a diagram showing the configuration of service signaling according to one embodiment of the present invention.
  • FIG. 95 is a diagram showing the configuration of LSIDInfo information and DeliveryInfo information according to one embodiment of the present invention.
  • FIG. 96 is a diagram showing the configuration of service signaling according to another embodiment of the present invention.
  • FIG. 97 is a diagram showing the configuration of an LSID according to one embodiment of the present invention.
  • FIGS. 98 and 99 are diagrams showing a ROUTE session and a transmission method of an LSID according to one embodiment of the present invention.
  • FIG. 100 is a diagram showing a method for transmitting broadcast signals according to one embodiment of the present invention.
  • FIG. 101 is a diagram showing a method for receiving broadcast signals according to one embodiment of the present invention.
  • FIG. 102 is a diagram showing the configuration of an apparatus for transmitting broadcast signals according to one embodiment of the present invention.
  • FIG. 103 is a diagram showing the configuration of an apparatus for receiving broadcast signals according to one embodiment of the present invention.
  • ‘Signaling’ in this specification indicates transmitting service information provided in a broadcast system.
  • Broadcast signal in this specification indicates signals and data that are provided in terrestrial, cable, satellite, mobile, internet, broadband, communication, data and/or VOD broadcast.
  • PLP in this specification indicates a kind of unit transmitting data belong to physical layers. And, it may be called ‘data unit’ or ‘data pipe’.
  • Various contents may be provided by transmitting A/V contents and relevant enhanced data through a terrestrial channel and/or internet channel in real time.
  • the present invention provides apparatuses and methods for transmitting and receiving broadcast signals for future broadcast services.
  • Future broadcast services include a terrestrial broadcast service, a mobile broadcast service, a UHDTV service, etc.
  • 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.
  • 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.
  • FEF future extension frame
  • 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.
  • 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 10dB, but can be configured to reach below 0 dB when intended for deeper indoor reception.
  • 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.
  • 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.
  • 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 Kbch bits which form the input to one FEC encoding process (BCH and LDPC encoding)
  • 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.
  • 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 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 Ts 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.
  • 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
  • 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
  • the preamble symbol is mainly used for fast initial band scan to detect the system signal, its timing, frequency offset, and FFT-size.
  • super-frame set of eight frame repetition units
  • ztime interleaving 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
  • 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 Ncells 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 can include an input formatting block 1000 , a BICM (Bit interleaved coding & modulation) block 1010 , a frame building block 1020 , an OFDM (Orthogonal Frequency Division Multiplexing) generation block 1030 and a signaling generation block 1040 .
  • BICM Bit interleaved coding & modulation
  • OFDM Orthogonal Frequency Division Multiplexing
  • IP stream/packets and MPEG2-TS are the main input formats, other stream types are handled as General Streams.
  • 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).
  • QoS quality-of-service
  • 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).
  • the data pipe unit a basic unit for allocating data cells to a DP in a frame.
  • 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.
  • 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.
  • 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.
  • PAPR Peak-to-Average Power Reduction
  • 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).
  • BBF baseband frame
  • 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 (0x47).
  • 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.
  • 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't provide the CRC encoding, the proposed CRC encoding should be applied.
  • the 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.
  • 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).
  • 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.
  • 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).
  • 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.
  • the PLS scrambler 2030 can scramble the generated PLS data for energy dispersal.
  • 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.
  • 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.
  • CBR Constant Bit Rate
  • 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.
  • DNP deleted null-packet
  • 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.
  • the receiver For Transport Stream, the receiver has a-priori information about the sync-byte configuration (0x47) 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 a BICM block according to an embodiment of the present invention.
  • the BICM block illustrated in FIG. 4 corresponds to an embodiment of the BICM block 1010 described with reference to FIG. 1 .
  • the apparatus for transmitting broadcast signals for future broadcast services can provide a terrestrial broadcast service, mobile broadcast service, UHDTV service, etc.
  • 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.
  • 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 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 .
  • 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).
  • BCH outer coding
  • LDPC inner coding
  • 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, el.
  • 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.
  • 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.
  • 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 .
  • 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).
  • FR-SM full-rate spatial multiplexing
  • FRFD-SM full-rate full-diversity spatial multiplexing
  • 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 (e1,i and e2,i) are fed to the input of the MIMO Encoder. Paired MIMO Encoder output (g1,i and g2,i) is transmitted by the same carrier k and OFDM symbol 1 of their respective TX antennas.
  • FIG. 5 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. 5 illustrates a BICM block for protection of physical layer signaling (PLS), emergency alert channel (EAC) and fast information channel (FIC).
  • PLS physical layer signaling
  • EAC emergency alert channel
  • FIC fast information channel
  • the BICM block for protection of PLS, EAC and FIC can include a PLS FEC encoder 6000 , a bit interleaver 6010 and a constellation mapper 6020 .
  • 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.
  • the output bits of the zero insertion may be permutted before LDPC encoding.
  • the LDPC encoding block can encode the output of the BCH encoding/zero insertion block using LDPC code.
  • Cldpc, parity bits, Pldpc are encoded systematically from each zero-inserted PLS information block, Ildpc and appended after it.
  • the LDPC code parameters for PLS1 and PLS2 are as following table 4.
  • the LDPC parity punturing block can perform puncturing on the PLS1 data and PLS2 data.
  • the bit interleaver 6010 can interleave the each shortened and punctured PLS1 data and PLS2 data.
  • the constellation mapper 6020 can map the bit ineterlaeved PLS1 data and PLS2 data onto constellations.
  • FIG. 6 illustrates a frame building block according to one embodiment of the present invention.
  • the frame building block illustrated in FIG. 6 corresponds to an embodiment of the frame building block 1020 described with reference to FIG. 1 .
  • 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 5050 .
  • 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.
  • FIG. 7 illustrates an OFDM generation block according to an embodiment of the present invention.
  • the OFDM generation block illustrated in FIG. 7 corresponds to an embodiment of the OFDM 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.
  • PAPR Peak-to-Average Power Radio
  • the OFDM generation 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 .
  • IFFT Inverse Fast Fourier Transform
  • 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.
  • 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.
  • FIG. 8 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 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 can include a synchronization & demodulation module 9000 , a frame parsing module 9010 , a demapping & 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 & 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 9010 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 9010 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 9040 to restore scheduling information generated by the apparatus for transmitting broadcast signals.
  • the demapping & decoding module 9020 can convert the input signals into bit domain data and then deinterleave the same as necessary.
  • the demapping & decoding module 9020 can perform demapping for mapping applied for transmission efficiency and correct an error generated on a transmission channel through decoding.
  • the demapping & decoding module 9020 can obtain transmission parameters necessary for demapping and decoding by decoding the data output from the signaling decoding module 9040 .
  • the output processor 9030 can perform reverse procedures of various compression/signal processing procedures which are applied by the apparatus for transmitting broadcast signals to improve transmission efficiency.
  • the output processor 9030 can acquire necessary control information from data output from the signaling decoding module 9040 .
  • 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 9040 can obtain PLS information from the signal demodulated by the synchronization & demodulation module 9000 .
  • the frame parsing module 9010 , demapping & decoding module 9020 and output processor 9030 can execute functions thereof using the data output from the signaling decoding module 9040 .
  • FIG. 9 illustrates a frame structure according to an embodiment of the present invention.
  • FIG. 9 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
  • (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.
  • 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).
  • FSS frame signaling symbols
  • FES normal data symbols
  • FES frame edge symbol
  • 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.
  • the FSS 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. 10 illustrates a signaling hierarchy structure of the frame according to an embodiment of the present invention.
  • FIG. 10 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. 11 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.
  • FFT_SIZE This 2 bit field indicates the FFT size of the current frame within a frame-group, as described in below table 6.
  • GI_FRACTION This 3 bit field indicates the guard interval fraction value in the current super-frame, as described in below table 7.
  • 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.
  • EAS emergency alert service
  • 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.
  • FIG. 12 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.
  • 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.
  • 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’.
  • 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.
  • 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.
  • PLS2_MOD This 3-bit field indicates the modulation type used by the PLS2. The modulation type is signaled according to table 11.
  • PLS2_SIZE CELL This 15-bit field indicates Ctotal_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 Ctotal_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 Ctotal_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.
  • 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. 13 illustrates PLS2 data according to an embodiment of the present invention.
  • FIG. 13 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.
  • 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.
  • 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.
  • DP_COD This 4-bit field indicates the code rate used by the associated DP.
  • the code rate is signaled according to the below table 15.
  • DP_COD This 4-bit field indicates the modulation used by the associated DP. The modulation is signaled according to the below table 16.
  • 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.
  • 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.
  • 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:
  • the allowed PI values with 2-bit field are defined in the below table 18.
  • the allowed PI values with 2-bit field are defined in the below table 18.
  • DP_FRAME_INTERVAL This 2-bit field indicates the frame interval (IJUMP) 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 5050 . 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.
  • 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.
  • INBAND-PLS 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.
  • 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.
  • 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’.
  • 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’.
  • 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.
  • 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’.
  • 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.
  • 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. 14 illustrates PLS2 data according to another embodiment of the present invention.
  • FIG. 14 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.
  • 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.
  • NUM_DP 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.
  • 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
  • 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.
  • EAC_FLAG field 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.
  • 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. 15 illustrates a logical structure of a frame according to an embodiment of the present invention.
  • 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.
  • auxiliary stream or streams 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. 16 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) NFSS 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 NFSS FSS(s) in a top-down manner as shown in an example in FIG. 16 .
  • 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.
  • DPs are carried next. If EAC, FIC or both are present in the current frame, they are placed between PLS and “normal” DPs.
  • FIG. 17 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.
  • 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. 17 .
  • EAC cells may occupy a few symbols, as shown in FIG. 17 .
  • 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.
  • FIC After EAC mapping is completed, the FIC is carried next, if any exists. If FIC is not transmit (as signaled in the PLS2 field), DPs follow immediately after the last cell of the EAC.
  • FIG. 18 illustrates FIC mapping according to an embodiment of the present invention.
  • 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.
  • 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).
  • FIC cells may be mapped over a few symbols, as shown in (b).
  • 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.
  • 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).
  • one or more DPs are mapped, followed by auxiliary streams, if any, and dummy cells.
  • FIG. 19 illustrates an FEC structure according to an embodiment of the present invention.
  • FIG. 19 illustrates an FEC structure according to an embodiment of the present invention before bit interleaving.
  • Data FEC encoder may perform the FEC encoding on the input BBF to generate FECBLOCK procedure using outer coding (BCH), and inner coding (LDPC).
  • BCH outer coding
  • LDPC inner coding
  • the illustrated FEC structure corresponds 0 to the FECBLOCK.
  • the FECBLOCK and the FEC structure have same value corresponding to a length of LDPC codeword.
  • Nldpc 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.
  • 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.
  • Pldpc parity bits
  • the completed Bldpc (FECBLOCK) are expressed as follow equation.
  • the addresses of the parity bit accumulators are given in the second row of the addresses of parity check matrix.
  • This LDPC encoding procedure for a short FECBLOCK is in accordance with the 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.
  • FIG. 20 illustrates a time interleaving according to an embodiment of the present invention.
  • the time interleaver operates at the DP level.
  • the parameters of time interleaving (TI) may be set differently for each DP.
  • 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_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 IJUMP 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.
  • 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.
  • 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 NxBLOCK_Group(n) and is signaled as DP_NUM_BLOCK in the PLS2-DYN data.
  • NxBLOCK_Group(n) may vary from the minimum value of 0 to the maximum value NxBLOCK_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 PI frames.
  • Each TI group is also divided into more than one TI blocks (NTI), 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 32.
  • Each TI group contains one TI block and is mapped to more than one frame.
  • DP_TI_TYPE ‘1’.
  • DP_TI_TYPE ‘1’.
  • 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.
  • 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.
  • FIG. 21 illustrates the basic operation of a twisted row-column block interleaver according to an embodiment of the present invention.
  • FIG. 21( a ) shows a writing operation in the time interleaver and FIG. 21( 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).
  • cells are read out diagonal-wise.
  • N r cells are read out as shown in (b).
  • the reading process in such an interleaving array is performed by calculating the row index R n, s, i , the column index , and the associated twisting parameter T n, s, i as follows equation.
  • 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 equation.
  • FIG. 22 illustrates an operation of a twisted row-column block interleaver according to another embodiment of the present invention.
  • the number of TI groups is set to 3.
  • FIG. 23 illustrates a diagonal-wise reading pattern of a twisted row-column block interleaver according to an embodiment of the present invention.
  • FIG. 24 illustrates interlaved XFECBLOCKs from each interleaving array according to an embodiment of the present invention.
  • FIG. 25 illustrates signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • the frequency interleaver according to the present invention performs interleaving using different interleaving sequences in a plurality of OFDM symbols, but the frequency deinterleaver may perform single-memory deinterleaving on the received OFDM symbols.
  • the present invention proposes a method for performing single-memory deinterleaving by the frequency deinterleaver irrespective of whether the number of OFDM symbols in one frame is an even number or an odd number.
  • the above-described architecture of the frequency interleaver may operate differently depending on whether the number of OFDM symbols is an even number or an odd number.
  • signaling information related thereto may be additionally defined in the above-described preamble and/or the physical layer signal (PLS).
  • PLS physical layer signal
  • single-memory deinterleaving is not limited to a case in which the number of OFDM symbols is an even number, and may always be enabled.
  • the PLS may be transmitted in a frame starting symbol (FSS) of every frame.
  • the PLS may be transmitted in the first OFDM symbol.
  • signaling information corresponding to the PLS may be completely transmitted in the preamble.
  • signaling information corresponding to the preamble and/or the PLS may be transmitted in bootstrap information.
  • the bootstrap information may be an information part located in front of the preamble.
  • Information about, for example, a processing operation used by the frequency interleaver of the transmitter may include an FI_mode field and an N_sym field.
  • the FI_mode field may be a 1-bit field which can be located in the preamble.
  • the FI_mode field may indicate an interleaving scheme used in the FSS or the first OFDM symbol of every frame.
  • the interleaving scheme indicated as the FI_mode field may include FI scheme #1 and FI scheme #2.
  • FI scheme #1 can indicate that the frequency interleaver of the transmitter performs random writing operation and then linear reading operation on the FSS. This case may correspond to a case in which the FI_mode field value is 0.
  • the random writing or linear reading operation may be performed in or from memory using a value generated by an arbitrary random sequence generator using, for example, a pseudo-random binary sequence (PRBS).
  • PRBS pseudo-random binary sequence
  • linear reading may refer to sequentially reading operation.
  • FI scheme #2 can indicate that the transmitter performs linear writing operation and then random reading operation on the FSS. This case may correspond to a case in which the FI_mode field value is 1.
  • the linear writing or random reading operation may be performed in or from memory using a value generated by an arbitrary random sequence generator using, for example, PRBS.
  • linear writing may refer to a sequentially writing operation.
  • the FI_mode field may indicate an interleaving scheme used in a frame edge symbol (FES) or the last OFDM symbol of every frame.
  • the interleaving scheme applied to the FES may be indicated differently from the value of the N_sym field transmitted by the PLS. That is, the interleaving scheme indicated as the FI_mode field may differ depending on whether the number of OFDM symbols is an odd number or an even number. Mapping information between the two fields may be predefined as a table by the transmitter and the receiver.
  • the FI_mode field may be defined and transmitted in a part of the frame other than the preamble according to another embodiment.
  • the N_sym field may be a field which can be located in the PLS part.
  • the number of bits of the N_sym field is variable according to embodiments.
  • the N_sym field may indicate number of OFDM symbols included in one frame. As such, the receiver can acquire information about whether the number of OFDM symbols is an even number or an odd number.
  • This frequency deinterleaver may perform single-memory deinterleaving by utilizing the proposed signaling fields irrespective of whether the number of OFDM symbols is an even number or an odd number.
  • the frequency deinterleaver may perform frequency deinterleaving on the FSS using information of the FI_mode field of the preamble because the frequency interleaving scheme used in the FSS is indicated as the FI_mode.
  • the frequency deinterleaver may perform frequency deinterleaving on the FES using signaling information of the FI_mode field and signaling information of the N_sym field of the PLS.
  • the mapping information between the two fields may be acquired using the predefined table. A description of the predefined table will be given below.
  • the frequency deinterleaver may perform deinterleaving using one interleaving sequence.
  • the interleaving sequence may be an interleaving sequence used by the frequency interleaver for reading & writing.
  • the frequency deinterleaver may perform reading & writing operation inversely using the interleaving sequence.
  • the frequency deinterleaver according to the present invention may not use a ping pong architecture using double memories.
  • the frequency deinterleaver may perform deinterleaving on contiguously input OFDM symbols using a single memory. As such, the efficiency of using memory by the frequency deinterleaver may be increased.
  • FIG. 26 illustrates FI schemes of FSS in signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • An interleaving scheme applied to frequency interleaving operation may be determined using the above-described FI_mode field and the N_sym field.
  • FI scheme #1 may be performed on the FSS irrespective of the FI_mode field value.
  • FI scheme #1 When the number of OFDM symbols indicated as the N_sym field is an odd number, FI scheme #1 may be applied to the FSS if the FI_mode field has a value of 0, and FI scheme #2 may be applied to the FSS if the FI_mode field has a value of 1. That is, when the number of OFDM symbols is an odd number, FI schemes #1 and #2 may be alternately applied to the FSS symbols for frequency interleaving.
  • FIG. 27 illustrates operation of a reset mode in signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • the above-described symbol offset generator may adopt a reset mode as a new concept.
  • the reset mode may refer to a mode in which a symbol offset value generated by the symbol offset generator is ‘0’.
  • whether to use the reset mode may be determined using the above-described FI_mode field and the N_sym field.
  • the reset mode of the symbol offset generator may not operate (off) irrespective of the value of the FI_mode field.
  • the symbol offset generator may operate in the reset mode (on). Otherwise, if the value of the FI_mode field is 1, the reset mode of the symbol offset generator may not operate (off). That is, when the number of OFDM symbols is an odd number, the reset mode may be alternately turned on and off for frequency interleaving.
  • FIG. 28 illustrates equations indicating input and output of the frequency interleaver in signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • OFDM symbol pairs of memory bank-A and memory bank-B may be processed through the above-described interleaving operation.
  • interleaving a variety of different interleaving seeds generated by cyclically shifting one main interleaving seed may be used.
  • the interleaving seed may also be called an interleaving sequence.
  • the interleaving seed may also be called an interleaving address value, an address value, or an interleaving address.
  • the term “interleaving address value(s)” can be used for referring plural address values, or for referring a interleaving seed which is a singular. That is, depeding on embodiments, interleaving address value(s) can mean H(p) itself, or each addresses belong to H(p).
  • Input of frequency interleaving to be interleaved within one OFDM symbol may be indicated as Om,l (t50010).
  • data cells may be indicated as xm,l,0, xm,l,Ndata-1.
  • p may indicate a cell index
  • l may indicate an OFDM symbol index
  • m may indicate a frame index. That is, xm,l,p may indicate a p-th data cell of an l-th OFDM symbol of an m-th frame.
  • Ndata may indicate the number of data cells.
  • Nsym may indicate the number of symbols (frame signaling symbols, normal data symbols, or frame edge symbols).
  • Data cells which are interleaved based on the above-described operation may be indicated as Pm,l (t50020).
  • the interleaved data cells may be indicated as vm,l,0, vm,l,Ndata-1.
  • p, l, and m may have the above-described index values.
  • FIG. 29 illustrates equations of a logical operation mechanism of frequency interleaving based on FI scheme #1 and FI scheme #2 in signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • frequency interleaving may be performed using an interleaving sequence (interleaving address) of each memory bank.
  • Interleaving operation on an even symbol may be mathematically expressed as given by equation t51010.
  • frequency interleaving may be performed using the interleaving sequence (interleaving address) to acquire output v.
  • p-th input data x may be permuted to be identical to H(p)-th output data v.
  • the interleaving sequence (interleaving address) may be a value generated by an arbitrary random sequence generator using, for example, PRBS.
  • Interleaving operation on an odd symbol may be mathematically expressed as given by equation t51020.
  • frequency interleaving may be performed using the interleaving sequence (interleaving address) to acquire output v.
  • H(p)-th input data x may be permuted to be identical to p-th output data v. That is, compared to the interleaving process performed on the even symbol, the interleaving sequence (interleaving address) may be applied inversely.
  • the interleaving sequence (interleaving address) may be a value generated by an arbitrary random sequence generator using, for example, PRBS.
  • operation on an even/odd symbol may be performed inversely from the operation based on FI scheme #1.
  • linear writing operation may be performed and then random reading operation may be performed as given by equation t51020.
  • random writing operation may be performed and then linear reading operation may be performed as given by equation t51010.
  • a detailed description thereof is the same as that given above in relation to FI scheme #1.
  • the symbol index 1 may be indicated as 0, 1, . . . , Nsym-1
  • the cell index p may be indicated as 0, 1, . . . , Ndata-1.
  • the frequency interleaving scheme on an even symbol and the frequency interleaving scheme on an odd symbol may be switched.
  • the frequency interleaving scheme based on FI scheme #1 and the frequency interleaving scheme based on FI scheme #2 may be switched.
  • FIG. 30 illustrates an example in which the number of symbols is an even number in signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • the N_sym field may indicate that the number of OFDM symbols in one frame is an even number.
  • the current embodiment assumes that one frame includes one preamble and eight OFDM symbols.
  • bootstrap information may be further included in front of the preamble. The bootstrap information is not illustrated.
  • one frame may include one FSS and one FES.
  • the FSS and the FES have the same length.
  • the frequency deinterleaver may acquire the corresponding information after decoding the FSS.
  • the current embodiment assumes that the N_sym field is completely decoded before operation on the FES is performed.
  • the value of the symbol offset generator may be reset to 0. Accordingly, the first and second symbols may be processed using the same interleaving sequence.
  • sequence #0 may be used for operation whenever each frame starts. After that, sequences #1 and #2 may be sequentially used for operation of the frequency interleaver/deinterleaver.
  • FIG. 31 illustrates an example in which the number of symbols is an even number in signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • information about an interleaving scheme of the FSS may be acquired from the FI_mode field of the preamble.
  • the number of OFDM symbols is an even number, only FI scheme #1 may be used.
  • N_sym information indicates that the number of symbols in the current frame is an even number.
  • the acquired FI_mode information and the N_sym information may be used when the frequency deinterleaver decodes the FES. Since the number of symbols is an even number, the symbol offset generator does not operate in the above-described reset mode. That is, the reset mode may be in an off state.
  • the frequency deinterleaver may operate in the same manner. That is, the FI scheme to be used in the FSS is FI scheme #1, and the reset mode to be used in the FES may be in an off state.
  • FIG. 32 illustrates an example in which the number of symbols is an odd number in signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • the N_sym field may indicate that the number of OFDM symbols in one frame is an odd number.
  • the current embodiment assumes that one frame includes one preamble and seven OFDM symbols.
  • bootstrap information may be further included in front of the preamble. The bootstrap information is not illustrated.
  • one frame may include one FSS and one FES.
  • the FSS and the FES have the same length.
  • the frequency deinterleaver may acquire the corresponding information after decoding the FSS.
  • the current embodiment assumes that the N_sym field is completely decoded before operation on the FES is performed.
  • the value of the symbol offset generator may be reset to 0. Furthermore, in the FES of an arbitrary frame, the symbol offset generator may operate in a reset mode based on the values of the FI_mode field and the N_sym field. Accordingly, in the FES of the arbitrary frame, the value of the symbol offset generator may be reset or not reset to 0. These reset operations may be alternately performed on frames.
  • the symbol offset generator may be reset in the last symbol of the first frame, i.e., the FES. Accordingly, the interleaving sequence may be reset to sequence #0. As such, the frequency interleaver/deinterleaver may process the corresponding FES based on sequence #0 (t54010).
  • the symbol offset generator may be reset again and thus sequence #0 may be used (t54010).
  • the symbol offset generator may not be reset in the FES of the second frame (frame #1), and may be reset again in the FES of the third frame (frame #2).
  • FIG. 33 illustrates an example in which the number of symbols is an odd number in signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • FI scheme #1 and FI scheme #2 may be used. In the current embodiment, FI scheme #1 is used in the first frame.
  • the FSS may be decoded and thus N_sym information may be acquired.
  • the N_sym information indicates that the number of symbols in the current frame is an odd number.
  • the acquired FI_mode information and the N_sym information may be used when the frequency deinterleaver decodes the FES. Since the number of symbols is an odd number and FI scheme#1 is used, the FI_mode field value is 0. Since the FI_mode is 0, the symbol offset generator may operate in the above-described reset mode. That is, the reset mode may be in an on state.
  • the symbol offset generator may operate in the reset mode and thus may be reset to 0. Since the FI_mode field value is 1 in the second frame, this indicates that the FSS is processed based on FI scheme #2.
  • the N_sym field indicates that the number of symbols is an odd number. In the second frame, since the FI_mode field value is 1 and the number of symbols is an odd number, the symbol offset generator may not operate in the reset mode.
  • the FI scheme to be used in the FSS may be alternately set to FI schemes #1 and #2.
  • the reset mode to be used in the FES may be alternately set to be on and off.
  • the settings may not be changed every frame.
  • FIG. 34 illustrates operation of the frequency deinterleaver in signaling for single-memory deinterleaving irrespective of the number of symbols in a frame according to an embodiment of the present invention.
  • the frequency deinterleaver may perform frequency deinterleaving using information of the predefined FI_mode field and/or the N_sym field. As described above, the frequency deinterleaver may operate using a single memory. Basically, frequency deinterleaving may be inverse operation of the frequency interleaving operation performed by the transmitter, to restore the order of data.
  • frequency deinterleaving on the FSS may be performed based on information about the FI scheme which is acquired from the FI_mode field and the N_sym field of the preamble.
  • Frequency deinterleaving on the FES may be performed based on information indicating whether to the reset mode operates, which is acquired using the FI_mode field and the N_sym field.
  • the frequency deinterleaver may perform inverse operation of the reading/writing operation of the frequency interleaver.
  • One interleaving sequence may be used in this operation.
  • the frequency interleaver follows the ping pong architecture using double memories, but the frequency deinterleaver may perform deinterleaving using a single memory.
  • This single-memory frequency deinterleaving operation may be performed using information of the FI_mode field and the N_sym field. This information may allow single-memory frequency deinterleaving even on a frame having an odd number of OFDM symbols irrespective of the number of OFDM symbols.
  • the frequency interleaver according to the present invention may perform frequency interleaving on all data cells of the OFDM symbols.
  • the frequency interleaver may map the data cells to available data carriers of the symbols.
  • the frequency interleaver according to the present invention may operate in different interleaving modes based on FFT size. For example, when the FFT size is 32K, the frequency interleaver may perform random writing/linear reading operation on an even symbol and perform linear writing/random reading operation on an odd symbol as in FI scheme #1 described above. Alternatively, when the FFT size is 16K or 8K, the frequency interleaver may perform linear reading/random writing operation on all symbols irrespective of an even/odd number.
  • the FFT size which determines whether to switch the interleaving modes, may vary according to embodiments. That is, interleaving as in FI scheme #1 may be performed in the case of 32K and 16K, and interleaving irrespective of an even/odd number may be performed in the case of 8K. Alternatively, interleaving as in FI scheme #1 may be performed for all FFT sizes, or interleaving irrespective of an even/odd number may be performed for all FFT sizes. Otherwise, according to another embodiment, interleaving as in FI scheme #2 may be performed for a specific FFT size.
  • This frequency interleaving operation may be performed using the above-described interleaving sequence (interleaving address).
  • the interleaving sequence may be variously generated using an offset value as described above.
  • address check may be performed to generate various interleaving sequences.
  • FIG. 35 illustrates the concept of a variable bit-rate system according to an embodiment of the present invention.
  • a transport superframe shown in FIG. 35 , is composed of NTI_NUM TI groups and each TI group can include N BLOCK_TI FEC blocks.
  • TI groups may respectively include different numbers of FEC blocks.
  • the TI group according to an embodiment of the present invention can be defined as a block for performing time interleaving and can be used in the same meaning as the aforementioned TI block or IF. That is, one IF can include at least one TI block and the number of FEC blocks in the TI block is variable.
  • the present invention performs interleaving on the TI groups using one twisted row-column block interleaving rule in an embodiment. Accordingly, the receiver can perform deinterleaving using a single memory.
  • VBR variable bit-rate
  • FIG. 36 illustrates writing and reading operations of block interleaving according to an embodiment of the present invention. Detailed descriptions about this figure was described before.
  • FIG. 37 shows equations representing block interleaving according to an embodiment of the present invention.
  • the equations shown in the figure represent block interleaving applied per TI group.
  • shift values can be respectively calculated in a case in which the number of FEC blocks included in a TI group is an odd number and a case in which the number of FEC blocks included in a TI group is an even number. That is, block interleaving according to an embodiment of the present invention can calculate a shift value after making the number of FEC blocks be an odd-number.
  • a time interleaver can determine parameters related to interleaving on the basis of a TI group having a maximum number of FEC blocks in the corresponding superframe. Accordingly, the receiver can perform deinterleaving using a single memory.
  • virtual FEC blocks corresponding to a difference between the number of FEC blocks and the maximum number of FEC blocks can be added.
  • Virtual FEC blocks according to an embodiment of the present invention can be inserted before actual FEC blocks. Subsequently, the time interleaver according to an embodiment of the present invention can perform interleaving on the TI groups using one twisted row-column block interleaving rule in consideration of the virtual FEC blocks. In addition, the time interleaver according to an embodiment of the present invention can perform the aforementioned skip operation when a memory-index corresponding to virtual FEC blocks is generated during reading operation. In the following writing operation, the number of FEC blocks of input TI groups is matched to the number of FEC blocks of output TI groups. Consequently, according to time interleaving according to an embodiment of the present invention, loss of data rate of data actually transmitted may be prevented through skip operation even if virtual FEC blocks are inserted in order to perform efficient single-memory deinterleaving in the receiver.
  • FIG. 38 illustrates virtual FEC blocks according to an embodiment of the present invention.
  • the left side of the figure shows parameters indicating a maximum number of FEC blocks in a TI group, the actual number of FEC blocks included in a TI group and a difference between the maximum number of FEC blocks and the actual number of FEC blocks, and equations for deriving the number of virtual FEC blocks.
  • the right side of the figure shows an embodiment of inserting virtual FEC blocks into a TI group.
  • the virtual FEC blocks can be inserted before actual FEC blocks, as described above.
  • FIG. 39 shows equations representing reading operation after insertion of virtual FEC blocks according to an embodiment of the present invention.
  • Skip operation illustrated in the figure can skip virtual FEC blocks in reading operation.
  • FIG. 40 is a flowchart illustrating a time interleaving process according to an embodiment of the present invention.
  • a time interleaver according to an embodiment of the present invention can setup initial values (S67000).
  • the time interleaver can perform writing operation on actual FEC blocks in consideration of virtual FEC blocks (S67100).
  • the time interleaver according to an embodiment of the present invention can generate a temporal TI address (S67200).
  • the time interleaver according to an embodiment of the present invention can evaluate the availability of the generated TI reading address (S67300). Then, the time interleaver according to an embodiment of the present invention can generate a final TI reading address (S67400).
  • the time interleaver according to an embodiment of the present invention can read the actual FEC blocks (S67500).
  • FIG. 41 shows equations representing a process of determining a shift value and a maximum TI block size according to an embodiment of the present invention.
  • the figure shows an embodiment in which the number of TI groups is 2, the number of cells in a TI group is 30, the number of FEC blocks included in the first TI group is 5 and the number of FEC blocks included in the second TI block is 6. While a maximum number of FEC blocks is 6, 6 is an even number. Accordingly, a maximum number of FEC blocks, which is adjusted in order to obtain the shift value, can be 7 and the shift value can be calculated as 4.
  • FIGS. 83 to 85 illustrate a TI process of the embodiment described before.
  • FIG. 42 illustrates writing operation according to an embodiment of the present invention.
  • FIG. 42 shows writing operation for the two TI groups described before.
  • a block shown in the left side of the figure represents a TI memory address array and blocks shown in the right side of the figure illustrate writing operation when two virtual FEC blocks and one virtual FEC block are respectively inserted into two continuous TI groups. Since the adjusted maximum number of FEC blocks is 7, as described above, two virtual FEC blocks are inserted into the first TI group and one virtual FEC block is inserted into the second TI group.
  • FIG. 43 illustrates reading operation according to an embodiment of the present invention.
  • a block shown in the left side of the figure represents a TI memory address array and blocks shown in the right side of the figure illustrate reading operation when two virtual FEC blocks and one virtual FEC block are respectively inserted into two continuous TI groups.
  • reading operation can be performed on the virtual FEC blocks in the same manner as the reading operation performed on actual FEC blocks.
  • FIG. 44 illustrates a result of skip operation in reading operation according to an embodiment of the present invention.
  • virtual FEC blocks can be skipped in two TI groups.
  • FIGS. 86 to 88 illustrate time deinterleaving corresponding to a reverse of TI described before.
  • FIG. 45 illustrates time deinterleaving for the first TI group and FIG. 46 illustrates time deinterleaving for the second TI group.
  • FIG. 45 shows a writing process of time deinterleaving according to an embodiment of the present invention.
  • a left block in the figure shows a TI memory address array
  • a middle block shows the first TI group input to a time deinterleaver
  • a right block shows a writing process performed in consideration of virtual FEC blocks that are skipped with respect to the first TI group.
  • two virtual FEC blocks skipped during TI can be restored for correct reading operation in the writing process.
  • the positions and quantity of the skipped two virtual FEC blocks can be estimated through an arbitrary algorithm.
  • FIG. 46 illustrates a writing process of time deinterleaving according to another embodiment of the present invention.
  • a left block in the figure shows a TI memory address array
  • a middle block shows the second TI group input to the time deinterleaver
  • a right block shows a writing process performed in consideration of virtual FEC blocks that are skipped with respect to the second TI group.
  • one virtual FEC block skipped during TI can be restored for correct reading operation in the writing process.
  • the position and quantity of the skipped one virtual FEC block can be estimated through an arbitrary algorithm.
  • FIG. 47 shows equations representing reading operation of time deinterleaving according to another embodiment of the present invention.
  • a TDI shift value used in the receiver can be determined by a shift value used in the transmitter, and skip operation can skip virtual FEC blocks in reading operation, similarly to skip operation performed in the transmitter.
  • FIG. 48 is a flowchart illustrating a time deinterleaving process according to an embodiment of the present invention.
  • a time deinterleaver according to an embodiment of the present invention can setup initial values (S75000).
  • the time deinterleaver can perform writing operation on actual FEC blocks in consideration of virtual FEC blocks (S75100).
  • the time deinterleaver can generate a temporal TDI reading address (S75200).
  • the time deinterleaver according to an embodiment of the present invention can evaluate the availability of the generated TDI reading address (S75300). Then, the time deinterleaver according to an embodiment of the present invention can generate a final TDI reading address (S75400).
  • the time deinterleaver can read the actual FEC blocks (S75500).
  • FIG. 49 is a diagram showing a protocol stack supporting a broadcast service according to one embodiment of the present invention.
  • the broadcast service may provide not only audio/video (A/V) data but also additional services such as an HTML5 application, an interactivity service, an ACR service, a second screen service and a personalization service.
  • A/V audio/video
  • additional services such as an HTML5 application, an interactivity service, an ACR service, a second screen service and a personalization service.
  • Such a broadcast service may be transmitted via a physical layer which is a broadcast signal of a terrestrial wave, a satellite, etc.
  • the broadcast service according to one embodiment of the present invention may be transmitted via an Internet communication network (broadband).
  • a broadcast reception apparatus may demodulate a broadcast signal to extract an encapsulated MPEG-2 transport stream (TS) and an encapsulated IP datagram.
  • the broadcast reception apparatus may extract a user datagram protocol (UDP) datagram from the IP datagram.
  • the broadcast reception apparatus may extract signaling information from the UDP datagram. At this time, the signaling information may be in XML format.
  • the broadcast reception apparatus may extract an asynchronous layered coding/layered coding transport (ALC/LCT) packet from the UDP datagram.
  • ALC/LCT asynchronous layered coding/layered coding transport
  • the broadcast reception apparatus may extract a file delivery over unidirectional transport (FLUTE) packet from the ALC/LCT packet.
  • the FLUTE packet may include real-time audio/video/subtitle data, non-real time (NRT) data and electronic service guide (ESG) data.
  • the broadcast reception apparatus may extract a real-time transport protocol (RTCP) packet and an RTP control protocol (RTCP) packet from the UDP datagram.
  • the broadcast reception apparatus may extract A/V data and supplementary data from the real-time transport packet such as the RTP/RTCP packet.
  • at least one of the NRT data, the A/V data and the supplementary data may be in ISO base media file format (BMFF).
  • the broadcast reception apparatus may extract signaling information such as NRT data, A/V or PSI/PSIP from the MPEG-2 TS packet or the IP packet. At this time, the signaling information may be in XML or binary format.
  • the broadcast reception apparatus may receive an IP packet from the Internet communication network.
  • the broadcast reception apparatus may extract a TCP packet from the IP packet.
  • the broadcast reception apparatus may extract an HTTP packet from the TCP packet.
  • the broadcast reception apparatus may extract A/V, supplementary data, signaling data, etc. from the HTTP packet.
  • at least one of the A/V and the supplementary data may be in ISO BMFF.
  • the signaling information may be in XML format.
  • FIG. 50 is a diagram showing a transport layer of a broadcast service according to one embodiment of the present invention.
  • Transmission and reception of media content via the IP network is divided into transmission and reception of a transport packet including actual media content and transmission and reception of media content presentation information.
  • the broadcast reception apparatus 100 receives media content presentation information and receives a transport packet including media content.
  • the media content presentation information indicates information necessary for media content presentation.
  • the media content presentation information may include at least one of spatial information and temporal information necessary for media content presentation.
  • the broadcast reception apparatus 100 presents the media content based on the media content presentation information.
  • the media content may be transmitted and received via the IP network according to the MMT standard.
  • the content server 50 transmits a presentation information (PI) document including the media content presentation information.
  • the content server 50 transmits an MMT protocol (MMTP) packet including media content according to a request of the broadcast reception apparatus 100 .
  • the broadcast reception apparatus 100 receives a PI document.
  • the broadcast reception apparatus 100 receives a transport packet including media content.
  • the broadcast reception apparatus 100 extracts the media content from the transport packet including the media content.
  • the broadcast reception apparatus 100 presents the media content based on the PI document.
  • the media content may be transmitted and received via the IP network according to the MPEG-DASH standard.
  • the content server 50 transmits a media presentation description (MPD) including the media content presentation information.
  • the MPD may be transmitted by an external server other than the content server 50 .
  • the content server 50 transmits a segment including media content according to a request of the broadcast reception apparatus 100 .
  • the broadcast reception apparatus 100 receives the MPD.
  • the broadcast reception apparatus 100 requests the media content from the content server based on the MPD.
  • the broadcast reception apparatus 100 receives the transport packet including the media content according to the request.
  • the broadcast reception apparatus 100 presents the media content based on the MPD.
  • the broadcast reception apparatus 100 may include a DASH client in the controller 110 .
  • the DASH client may include an MPD parser for parsing the MPD, a segment parser for parsing a segment, an HTTP client for transmitting an HTTP request message and receiving an HTTP response message via an IP transmitter/receiver 130 and a media engine for presenting media.
  • FIG. 51 is a diagram showing the structure of a media presentation description (MPD) according to one embodiment of the present invention.
  • the MPD may include a period element, an adaptation set element and a representation element.
  • the period element includes information on a period.
  • the MPD may include information on a plurality of periods.
  • the period indicates a consecutive time interval of media content presentation.
  • the adaptation set element includes information on an adaptation set.
  • the MPD may include information on a plurality of adaptation sets.
  • the adaptation set is a set of media components including one or more interchangeable media content components.
  • the adaptation set may include one or more representations.
  • Each adaptation set may include audio of different languages or subtitles of different languages.
  • the representation element includes information on a representation.
  • the MPD may include information on a plurality of representations.
  • the representation is a set of one or more media components and a plurality of differently encoded representations may exist in the same media content component. Meanwhile, if bitstream switching is possible, the broadcast reception apparatus 100 may switch from a received representation to another representation based on information updated during media content presentation. In particular, the broadcast reception apparatus 100 may switch a received representation into another representation according to bandwidth environment.
  • the representation may be divided into a plurality of segments.
  • the segment is a unit of media content data.
  • the representation may be transmitted as a segment or a portion of a segment according to the request of the media content receiver 30 using an HTTP GET or HTTP partial GET method defined in HTTP 1.1 (RFC 2616).
  • the segment may include a plurality of sub segments.
  • the sub segment may mean a smallest unit indexed at a segment level.
  • the segment may include an initialization segment, a media segment, an index segment, a bitstream switching segment, etc.
  • FIG. 52 is a diagram showing a transport layer of a broadcast service according to one embodiment of the present invention.
  • a broadcast transmission apparatus 300 may transmit a broadcast service via a broadcast signal composed of a plurality of layers. Among the plurality of layers for transmitting the broadcast service, a transport layer for transmitting and receiving a raw broadcast signal via a physical medium may be referred to as a physical layer.
  • the broadcast transmission apparatus 300 may transmit a broadcast service and broadcast service related data via one or more physical layer pipes (PLPs) over one or a plurality of frequencies.
  • PLP is a series of logical data delivery paths capable of being identified on the physical layer.
  • the PLP may also be referred to as a data pipe.
  • One broadcast service may include a plurality of components. At this time, each component may be any one of audio, video and data components.
  • Each broadcaster may transmit an encapsulated broadcast service via one or a plurality of PLPs using the broadcast transmission apparatus 300 . More specifically, the broadcaster may transmit a plurality of components included in one service through a plurality of PLPs using the broadcast transmission apparatus 300 . Alternatively, the broadcaster may transmit a plurality of components included in one service via one PLP using the broadcast transmission apparatus 300 .
  • Broadcast #1 may transmit signaling information via one PLP (PLP #0) using the broadcast transmission apparatus 300 .
  • Broadcast #1 transmits Component 1 and Component 2 included in a first broadcast service via different PLPs PLP #1 and PLP #2 using the broadcast transmission apparatus 300 .
  • PLP #0 PLP
  • FIG. 52 Broadcast #1 transmits Component 1 and Component 2 included in a first broadcast service via different PLPs PLP #1 and PLP #2 using the broadcast transmission apparatus 300 .
  • Broadcast #N transmits Component 1 and Component 2 included in Services #1 via PLP #N.
  • a real-time broadcast service may be encapsulated into any one of IP, user datagram protocol (UDP) and protocol for real-time content transmission, e.g., real-time transport protocol (RTP).
  • UDP user datagram protocol
  • RTP real-time transport protocol
  • non-real-time content and non-real-time data may be encapsulated into any one packet of an IP, a user datagram protocol (UDP) and a content transmission protocol, e.g., FLUTE.
  • the physical layer frame transmitted by the broadcast transmission apparatus 300 may include a plurality of PLPs for delivering one or more components. Accordingly, the broadcast reception apparatus 100 should confirm all PLPs in order to scan the broadcast service for acquiring broadcast service connection information. Therefore, there is a need for a broadcast transmission method and a broadcast reception method for enabling the broadcast reception apparatus 100 to efficiently scan the broadcast service.
  • FIG. 53 is a diagram showing the configuration of a broadcast reception apparatus according to one embodiment of the present invention.
  • the broadcast reception apparatus 100 includes a receiver 120 and a controller 150 .
  • the receiver 120 includes a broadcast receiver 110 and an Internet protocol (IP) communication unit 130 .
  • IP Internet protocol
  • the broadcast receiver 110 includes a channel synchronizer 111 , a channel equalizer 113 and a channel decoder 115 .
  • the channel synchronizer 110 synchronizes a symbol frequency with timing in a manner that a broadcast signal received at baseband can be decoded.
  • the channel equalizer 113 compensates for distortion of the synchronized broadcast signal. More specifically, the channel equalizer 113 compensates for distortion of the synchronized broadcast signal by multipath, Dopper effect, etc.
  • the channel decoder 115 decodes the broadcast signal, distortion of which is compensated for. More specifically, the channel decoder 115 extracts a transport frame from the broadcast signal, distortion of which is compensated for. At this time, the channel decoder 115 may perform forward error correction (FEC).
  • FEC forward error correction
  • the IP communication unit 130 receives and transmits data via an Internet network.
  • the controller 150 includes a signaling decoder 151 , a transport packet interface 153 , a broadband packet interface 155 , a baseband operation controller 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 the signaling data of the broadcast signal.
  • the transport packet interface 153 extracts a transport packet from the broadcast signal. At this time, the transport packet interface 153 may extract data such as signaling information or an IP datagram from the extracted transport packet.
  • the broadband packet interface 155 extracts an IP packet from the data received from the Internet network. At this time, the broadband packet interface 155 may extract signaling information or an IP datagram from the IP packet.
  • the baseband operation controller 157 controls operation related to reception of broadcast information from the baseband.
  • the common protocol stack 159 extracts audio or video from the 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 for signaling a broadcast service. More specifically, the service signaling channel processing buffer and parser 163 may parse and buffer signaling information for signaling the 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 of the program of a terrestrial broadcast service.
  • the application processor 169 extracts and processes application related information from the broadcast signal.
  • the service guide database 171 stores program information of the broadcast service.
  • FIGS. 54 to 55 are diagrams showing the configuration of a broadcast reception apparatus according to another embodiment of the present invention.
  • the broadcast reception apparatus 100 includes a broadcast receiver 110 , an Internet protocol communication unit 130 and a controller 150 .
  • the broadcast receiver 110 may include a tuner 114 , a physical frame parser 116 and a physical layer controller 118 .
  • the tuner 114 receives a broadcast signal via a broadcast channel and extracts a physical frame.
  • the physical frame is a transmission unit of a physical layer.
  • the physical frame parser 116 parses the received physical frame and acquires a link layer frame.
  • the physical layer controller 118 controls operation of the tuner 114 and the physical frame parser 116 .
  • the physical layer controller 118 may control the tuner 114 using RF information of the broadcast channel. More specifically, when the physical layer controller 118 transmits frequency information to the tuner 114 , the tuner 114 may acquire the physical frame corresponding to the received frequency information from the broadcast signal.
  • the physical layer controller 118 may control operation of the physical layer parser 116 via the identifier of a physical layer pipe. More specifically, the physical layer controller 118 transmits identification information for identifying a specific physical layer pipe among a plurality of physical layer pipes configuring the physical layer pipe to the physical frame parser 116 . The physical frame parser 116 may identify the physical layer pipe based on the received identification information and acquire a link layer frame from the identified physical layer pipe.
  • the controller 150 includes a link layer frame parser 164 , an IP/UDP datagram filter 171 , a DTV control engine 174 , an ALC/LCT+client 172 , a timing control unit 175 , a DASH client 192 , an ISO BMFF parser 194 and a media decoder 195 .
  • the link layer frame parser 164 extracts data from the link layer frame. More specifically, the link layer frame parser 164 may acquire link layer signaling from the link layer frame. In addition, the link layer frame parser 164 may acquire an IP/UDP datagram from the link layer frame.
  • the IP/UDP datagram filter 171 filters a specific IP/UDP datagram from the IP/UDP datagram received from the link layer frame parser 164 .
  • the ALC/LCT+client 172 processes an application layer transport packet.
  • the application layer transport packet may include an ALC/LCT+packet. More specifically, the ALC/LCT+client 172 may collect a plurality of application layer transport packets and generate one or more ISO BMFF media file format objects.
  • the timing control unit 175 processes a packet including system time information.
  • the timing control unit 175 controls a system clock according to the processed result.
  • the DASH client 182 processes real-time streaming or adaptive media streaming. More specifically, the DASH client 192 may process adaptive media streaming based on the HTTP and acquires a DASH segment. At this time, the DASH segment may be in the form of an ISO BMFF object.
  • the ISO BMFF parser 194 extracts audio/video data from the ISO BMFF object received from the DASH client 192 . At this time, the ISO BMFF parser 194 may extract audio/video data in access units. In addition, the ISO BMFF 194 may acquire timing information for audio/video from the ISO BMFF object.
  • the media decoder 195 decodes the received audio and video data. In addition, the media decoder 195 presents the decoded result via a media output unit.
  • the DTV control engine 174 is an interface between modules. More specifically, the DTV control engine 174 may deliver parameters necessary for operation of each module to control operation of each module.
  • the Internet protocol communication unit 130 may include an HTTP access client 135 .
  • the HTTP access client 135 may transmit/receive a request or a response to the request to/from an HTTP server.
  • FIG. 56 is a diagram showing the configuration of a broadcast reception apparatus according to another embodiment of the present invention.
  • the broadcast reception apparatus 100 includes a broadcast receiver 110 , an Internet protocol (IP) communication unit 130 and a controller 150 .
  • IP Internet protocol
  • the broadcast receiver 110 may include one or a plurality of processors, one or a plurality of circuits and one or a plurality of hardware modules for performing a plurality of functions performed by the broadcast receiver 110 . More specifically, the broadcast receiver 110 may be a system on chip (SOC) in which several semiconductor parts are integrated. At this time, the SOC may be a semiconductor device in which various multimedia parts such as graphics, audio, video, modem, etc., a processor, and a semiconductor memory such as a DRAM are integrated.
  • the broadcast receiver 110 may include a physical layer module 119 and a physical layer IP frame module 117 .
  • the physical layer module 119 receives and processes a broadcast related signal via a broadcast channel of a broadcast network.
  • the physical layer IP frame module 117 converts a data packet of an IP datagram acquired from the physical layer module 119 into a specific frame.
  • the physical layer module 119 may convert the IP datagram, etc. into an RS frame, a GSE, etc.
  • the IP communication unit 130 may include one or a plurality of processors, one or a plurality of circuits and one or a plurality of hardware modules for performing a plurality of functions performed by the IP communication unit 130 . More specifically, the IP communication unit 130 may be a system on chip (SOC) in which several semiconductor parts are integrated. At this time, the SOC may be a semiconductor device in which various multimedia parts such as graphics, audio, video, modem, etc., a processor, and a semiconductor memory such as a DRAM are integrated.
  • the IP communication unit 130 may include an Internet access control module 131 .
  • the Internet access control module 131 controls operation of the broadcast reception apparatus 100 for acquiring at least one of a service, content and signaling data via an Internet communication network (broadband).
  • the controller 150 may include one or a plurality of processors, one or a plurality of circuits and one or a plurality of hardware modules for performing a plurality of functions performed by the controller 150 . More specifically, the controller 150 may be a system on chip (SOC) in which several semiconductor parts are integrated. At this time, the SOC may be a semiconductor device in which various multimedia parts such as graphics, audio, video, modem, etc., a processor, and a semiconductor memory such as a DRAM are integrated.
  • SOC system on chip
  • the controller 150 may include at least one of a signaling decoder 151 , a service map database 161 , a service signaling channel parser 163 , an application signaling parser 166 , an alert signaling parser 168 , a targeting signaling parser 170 , a targeting processor 173 , an A/V processor 161 , an alert processor 162 , an application processor 169 , a scheduled streaming decoder 181 , a file decoder 182 , a user request streaming decoder 183 , a file database 184 , a component synchronizer 185 , a service/content acquisition controller 187 , a redistribution module 189 , a device manager 193 and a data sharing unit 191 .
  • the service/content acquisition controller 187 controls operation of a receiver for acquiring a service, content and signaling data related to the service or content acquired via the broadcast network or the Internet communication network.
  • the signaling decoder 151 decodes the signaling information.
  • the service signaling parser 163 parses the service signaling information.
  • the application signaling parser 166 extracts and parses the signaling information related to the service.
  • the signaling information related to the service may be signaling information related to service scan.
  • the signaling information related to the service may be signaling information related to the content provided via the service.
  • the alert signaling parser 168 extracts and parses the signaling information related to alert.
  • the targeting signaling parser 170 extracts and parses information for personalization of the service or content or information for signaling targeting information.
  • the targeting processor 173 processes information for personalizing the service content.
  • the alert processor 162 processes signaling information related to alert.
  • the application processor 169 controls execution of an application and application related information. More specifically, the application processor 169 processes the state of the downloaded application and display parameters.
  • the A/V processor 161 processes operation related to rendering of audio/video based on the decoded audio or video, application data, etc.
  • the scheduled streaming decoder 181 decodes scheduled streaming which is content streamed according to the schedule previously decided by a content provider such as a broadcaster.
  • the file decoder 182 decodes the decoded file.
  • the file decoder 182 decodes the file downloaded via the Internet communication network.
  • the user request streaming decoder 183 decodes content (on demand content) provided by a user request.
  • the file database 184 stores the file. More specifically, the file database 184 may store the file downloaded via the Internet communication network.
  • the component synchronizer 185 synchronizes content or services. More specifically, the component synchronizer 185 synchronizes the presentation time of the content acquired via at least one of the scheduled streaming decoder 181 , the file decoder 182 and the user request streaming decoder 183 .
  • the service/content acquisition controller 187 controls operation of the receiver for acquiring at least one of a service, content and signaling information related to the service or content.
  • the redistribution module 189 performs operation for supporting acquisition of at least one of the service, content, information related to the service and information related to the content when the service or the content is not received via the broadcast network. More specifically, the redistribution module may request at least one of the service, the content, the information related to the service and the information related to the content from an external management device 300 . At this time, the external management device 300 may be a content server.
  • the device manager 193 manages a connectable external device. More specifically, the device manager 193 may perform at least one of addition, deletion and update of the external device. In addition, the external device may be connected to and exchange data with the broadcast reception apparatus 100 .
  • the data sharing unit 191 may perform data transmission operation between the broadcast reception apparatus 100 and the external device and processes exchange related information. More specifically, the data sharing unit 191 may transmit A/V data or signaling information to the external device. In addition, the data sharing unit 191 may receive A/V data or signaling information from the external device.
  • FIG. 57 is a diagram showing a broadcast transport frame according to one embodiment of the present invention.
  • the broadcast transport frame includes a P1 part, an L1 part, a common PLP part, an interleaved PLP (scheduled & interleaved PLP) part and an auxiliary data part.
  • the broadcast transmission apparatus transmits information on transport signal detection via the P1 part of the broadcast transport frame.
  • the broadcast transmission apparatus may transmit tuning information for broadcast signal tuning via the P1 part.
  • the broadcast transmission apparatus transmits the configuration of the broadcast transport frame and the characteristics of each PLP via the L 1 part.
  • the broadcast reception apparatus 100 may decode the L 1 part based on P1 and acquire the configuration of the broadcast transport frame and the characteristics of each PLP.
  • the broadcast transmission apparatus may transmit information commonly applied to the PLPs via the common PLP part.
  • the broadcast transmission frame may not include the common PLP part.
  • the broadcast transmission apparatus transmits a plurality of components included in a broadcast service via the interleaved PLP part.
  • the interleaved PLP part includes a plurality of PLPs.
  • the broadcast transmission apparatus may signal information on through which PLP the component configuring the broadcast service is signaled via the L1 part or the common PLP part.
  • the broadcast reception apparatus 100 should decode the plurality of PLPs of the interleaved PLP part in order to acquire the detailed broadcast service information, for broadcast service scan.
  • the broadcast transmission apparatus may transmit a broadcast transport frame including a separate part including information on the component included in the broadcast service and the broadcast service transmitted via the broadcast transport frame.
  • the broadcast reception apparatus 100 may rapidly acquire the broadcast service and information on the components included in the broadcast service via a separate part. This will be described with reference to FIG. 56 .
  • FIG. 58 is a diagram showing a broadcast transport frame according to another embodiment of the present invention.
  • the broadcast transport frame includes a P1 part, an L1 part, a fast information channel (FIC) part, an interleaved PLP (scheduled & interleaved PLP) part and an auxiliary data part.
  • FIC fast information channel
  • interleaved PLP scheduled & interleaved PLP
  • Parts other than the FIC part are equal to those of the embodiment of FIG. 57 .
  • the broadcast transmission apparatus transmits fast information via the FIC part.
  • the fast information may include configuration information of the broadcast stream transmitted via the transport frame, brief broadcast service information and service signaling related to the service/component.
  • the broadcast reception apparatus 100 may scan the broadcast service based on the FIC part. More specifically, the broadcast reception apparatus 100 may extract the information on the broadcast service from the FIC part.
  • FIG. 59 is a diagram showing the configuration of a transport packet according to one embodiment of the present invention.
  • the transport packet shown in FIG. 59 may use a transport protocol supporting reliable data transmission.
  • the reliable data transmission protocol may be asynchronous layered coding (ALC).
  • the reliable data transmission protocol may be layered coding transport (LCT).
  • the packet header according to one embodiment of the present invention may include version information of the packet. More specifically, the packet header may include version information of the transport packet which uses the transport protocol. In the embodiment, the above-described information may be a V field. In addition, the V field may have a size of 4 bits.
  • the packet header may include information associated with the length of congestion control information. More specifically, the packet header may include the length of the congestion control information and information on a multiple of the basic unit of the length of the congestion control information.
  • the above-described information may be a C field.
  • the C field may be set to 0x00.
  • the length of the congestion control information is 32 bits.
  • the C field may be set to 0x01.
  • the length of the congestion control information may be 64 bits.
  • the C field may be set to 0x02.
  • the length of the congestion control information may be 96 bits.
  • the C field may be set to 0x03. In this case, the length of the congestion control information may be 128 bits.
  • the C field may have a size of 2 bits.
  • the packet header may include information specialized for the protocol.
  • the above-described information may be a PSI field.
  • the PSI field may have a size of 2 bits.
  • the packet header may include information associated with the length of the field indicating the identification information of the transport session. More specifically, the packet header may include multiple information of the field indicating the identification information of the transport session.
  • the above-described information may be an S field.
  • the S field may have a size of 1 bit.
  • the packet header may include information associated with the length of the field indicating the identification information of the transport object. More specifically, the packet header may include multiple information multiplied with the basic unit of the length of the identification information of the transport object.
  • the above-described information may be an O field.
  • the O field may have a size of 2 bits.
  • the packet header may include additional information associated with the length of the field indicating the identification information of the transport session.
  • the packet header may include additional information associated with the length of the field indicating the identification information of the transport object.
  • the additional information may be information indicating whether half-word is added. Since the field indicating the identification information of the transport packet and the field indicating the identification information of the transport object should be present, the S field and the H field or the O field and the H field may not simultaneously indicate 0 (zero).
  • the packet header may include information indicating that the session is finished or is about to be finished.
  • the above-described information may be an A field.
  • the A field may be set to 1 in order to indicate that the session is finished or is about to be finished. Accordingly, generally, the A field may be set to 0.
  • the broadcast transmission apparatus sets the A field to 1, it is indicated that the last packet is being transmitted via the session.
  • the broadcast transmission apparatus should maintain the A field to 1 until transmission of all packets following the corresponding packet is finished.
  • the broadcast reception apparatus may recognize that the broadcast transmission apparatus is about to stop packet transmission via the session when the A field is set to 1. In other words, the broadcast reception apparatus may recognize that packet transmission is no longer performed when the A field is set to 1.
  • the A field may have a size of 1 bit.
  • the packet header may include information indicating that object transmission is finished or is about to be finished.
  • the above-described information may be a B field.
  • the broadcast transmission apparatus may set the B field to 1 when object transmission is about to be finished. Accordingly, generally, the B field may be set to 0.
  • the B field may be set to 1. This may indicate that transmission of the object in the session identified by out-of-band information is about to be finished.
  • the B field may be set to 1 when the last packet for the object is transmitted.
  • the B field may be set to 1 when the last packet for the object is transmitted for several seconds.
  • the broadcast transmission apparatus should set the B field to 1 until transmission of the packet following the corresponding packet is finished, when the B field of the packet for a specific object is set to 1.
  • the broadcast reception apparatus 100 may recognize that the broadcast transmission apparatus will stop transmission of the packet for the object when the B field is set to 1. In other words, the broadcast reception apparatus 100 may recognize that the object is no longer transmitted via the session, from the B field set to 1.
  • the B field may have a size of 1 bit.
  • the packet header according to one embodiment of the present invention may include information indicating the total length of the header.
  • the above-described information may be an HDR_LEN field.
  • the HDR_LEN field may be a multiple of 32 bits. In a detailed embodiment, when the HDR_LEN field is set to 5, the total length of the packet header may be 160 bits which is a multiple of 32. In addition, the HDR_LEN field may be 8 bits.
  • the packet header may include information related to encoding or decoding of the payload included in the corresponding packet.
  • the above-described information may be referred to as a codepoint field.
  • the codepoint field may have a size of 8 bits.
  • the packet header may include congestion control information.
  • the above-described information may be referred to as a congestion control information (hereinafter, CCI) field.
  • the CCI field may include at least one of a current time slot index (CTSI) field, a channel number field and a packet sequence number field.
  • CTSI current time slot index
  • the packet header according to one embodiment of the present invention may include information for identifying the transport session.
  • the above-described information may be a transport session identifier (hereinafter, TSI).
  • TSI transport session identifier
  • the field in the packet header including TSI information may be a TSI field.
  • the packet header according to one embodiment of the present invention may include information for identifying the object transmitted via the transport session.
  • the above-described information may be a transport object identifier (hereinafter, TOI).
  • the field in the packet header including the TOI information may be a TOI field.
  • the packet header may include information for transmitting additional information.
  • the above-described information may be referred to as a header extension field.
  • the additional information may be time information related to presentation of the transport object.
  • the additional information may be time information related to decoding of the transport object.
  • the transport packet according to one embodiment of the present invention may include payload identification information.
  • the identification information may be payload identification information associated with a forward error correction (FEC) scheme.
  • FEC is a type of the payload format defined in RFC 5109.
  • the FEC may be used in the RTP or SRTP.
  • the above-described information may be an FEC payload ID field.
  • the FEC payload ID field may include information for identifying the source block of the object.
  • the above-described information may be a source block number field.
  • the source block in the object may be numbered from 0 to N-1.
  • the FEC payload ID field may include information for identifying a specific encoding symbol.
  • the above-described information may be an encoding ID field.
  • the transport packet may include data in a payload.
  • the field including the above-described data may be an encoding symbol(s) field.
  • the broadcast reception apparatus 100 may extract the encoding symbol(s) field and reconfigure the object. More specifically, the data in the encoding symbol(s) field may be generated from the source block transmitted via the packet payload.
  • FIG. 60 is a diagram showing the configuration of a service signaling message according to one embodiment of the present invention. More specifically, FIG. 60 shows the syntax of the service signaling message header according to one embodiment of the present invention.
  • the service signaling message according to one embodiment of the present invention may include a signaling message header and a signaling message. At this time, the signaling message may be represented in binary or XML format. In addition, the service signaling message may be included in the payload of the transport protocol packet.
  • the signaling message header according to the embodiment of FIG. 60 may include the identification information for identifying the signaling message.
  • the signaling message may be in the form of a section.
  • the identification information of the signaling message may indicate the identifier (ID) of the signaling table section.
  • the field indicating the identification information of the signaling message may be signaling_id.
  • the signaling_id field may have a size of 8 bits.
  • the signaling message header according to the embodiment of FIG. 60 may include length information indicating the length of the signaling message.
  • the field indicating the length information of the signaling message may be signaling_length.
  • the signaling_length field may have a size of 12 bits.
  • the signaling message header according to the embodiment of FIG. 60 may include identifier extension information for extending the identifier of the signaling message.
  • the identifier extension information may be information for identifying signaling along with signaling identifier information.
  • the field indicating the identifier extension information of the signaling message may be signaling_id extension.
  • the identifier extension information may include protocol version information of the signaling message.
  • the field indicating the protocol version information of the signaling message may be protocol_version.
  • the protocol_version field may have a size of 8 bits.
  • the signaling message header according to the embodiment of FIG. 60 may include the version information of the signaling message.
  • the version information of the signaling message may be changed when the information included in the signaling message is changed.
  • the field indicating the version information of the signaling message may be version_number.
  • the version_number field may have a size of 5 bits.
  • the signaling message header according to the embodiment of FIG. 60 may include information indicating whether the signaling message is currently available.
  • the field indicating whether the signaling message is available may be current_next_indicator. For example, when the current_next_indicator field is 1, the current_next_indicator field may indicate that the signaling message is available. As another example, when the current_next_indicator field is 0, the current_next_indicator field may indicate that the signaling message is not available and another signaling message including the same signaling identification information, signaling identifier extension information or fragment number information is available.
  • the signaling message header according to the embodiment of FIG. 60 may include fragment number information of the signaling message.
  • One signaling message may be divided into a plurality of fragments and transmitted. Accordingly, information for identifying the plurality of fragments by the receiver may be fragment number information.
  • the field indicating the fragment number information may be a fragment_number field. In a detailed embodiment, the fragment_number field may have a size of 8 bits.
  • the signaling message header according to the embodiment of FIG. 60 may include number information of a last fragment when one signaling message is divided into a plurality of fragments. For example, when information on a last fragment number is 3, this indicates that the signaling message is divided into three fragments. In addition, this may indicate that the fragment including the fragment number of 3 includes the last data of the signaling message.
  • the field indicating the number information of the last fragment may be last_fragment_number. In a detailed embodiment, the last_fragment_number field may have a size of 8 bits.
  • FIG. 61 is a diagram showing the configuration of a service signaling message according to one embodiment of the present invention. More specifically, FIG. 61 shows the syntax of the service signaling message header according to one embodiment of the present invention.
  • the service signaling message according to one embodiment of the present invention may include a signaling message header and a signaling message. At this time, the signaling message may be represented in binary or XML format. In addition, the service signaling message may be included in the payload of the transport protocol packet.
  • the signaling message header according to the embodiment of FIG. 61 may include identifier information for identifying the signaling message.
  • the signaling message may be in the form of a section.
  • the identifier information of the signaling message may indicate the identifier (ID) of the signaling table section.
  • the field indicating the identifier information of the signaling message may be signaling_id.
  • the signaling_id field may have a size of 8 bits.
  • the signaling message header according to the embodiment of FIG. 61 may include length information indicating the length of the signaling message.
  • the field indicating the length information of the signaling message may be signaling_length.
  • the signaling_length field may have a size of 12 bits.
  • the signaling message header according to the embodiment of FIG. 61 may have identifier extension information for extending the identifier of the signaling message.
  • the identifier extension information may be information for identifying signaling along with signaling identifier information.
  • the field indicating the identifier extension information of the signaling message may be signaling_id_extension.
  • the identifier extension information may include protocol version information of the signaling message.
  • the field indicating the protocol version information of the signaling message may be protocol_version.
  • the protocol_version field may have a size of 8 bits.
  • the signaling message header according to the embodiment of FIG. 61 may include the version information of the signaling message.
  • the version information of the signaling message may be changed when the information included in the signaling message is changed.
  • the field indicating the version information of the signaling message may be version_number.
  • the version_number field may have a size of 5 bits.
  • the signaling message header according to the embodiment of FIG. 61 may include information indicating whether the signaling message is currently available.
  • the field indicating whether the signaling message is available may be current_next_indicator. For example, when the current_next_indicator field is 1, the current_next_indicator field may indicate that the signaling message is available. As another example, when the current_next_indicator field is 0, the current_next_indicator field may indicate that the signaling message is not available and another signaling message including the same signaling identification information, signaling identifier extension information or fragment number information is available.
  • the signaling message header according to the embodiment of FIG. 61 may include the format information of the signaling message included in the payload.
  • the signaling message may be represented in binary or XML format.
  • the signaling message may be represented in other formats.
  • the format information may indicate the format of the signaling message included in the payload and may indicate binary, XML, etc., for example.
  • the field indicating the format information may be a payload_format field. In a detailed embodiment, the payload_format field may have a size of 2 bits.
  • the signaling message header according to the embodiment of FIG. 61 may include valid time information of the signaling message included in the payload.
  • the valid time information of the signaling message may include information on the valid time of the signaling message. After the time defined in this field, the signaling message is no longer valid.
  • the field indicating the valid time information may be an expiration field. In a detailed embodiment, the expiration field may have a size of 32 bits.
  • the signaling message header according to the embodiment of FIG. 61 may include fragment number information of the signaling message.
  • One signaling message may be divided into a plurality of fragments and transmitted.
  • Information for identifying the plurality of fragments by the receiver may be fragment number information.
  • the field indicating the fragment number information may be a fragment_number field.
  • the fragment_number field may have a size of 8 bits.
  • the signaling message header according to the embodiment of FIG. 61 may include number information of a last fragment when one signaling message is divided into a plurality of fragments. For example, when information on a last fragment number is 3, this indicates that the signaling message is divided into three fragments. In addition, this may indicate that the fragment including the fragment number of 3 includes the last data of the signaling message.
  • the field indicating the number information of the last fragment may be last_fragment_number. In a detailed embodiment, the last_fragment_number field may have a size of 8 bits.
  • FIG. 62 is a diagram showing the configuration of a broadcast service signaling message in a next generation broadcast system according to one embodiment of the present invention.
  • the broadcast service signaling message according to one embodiment is for a broadcast service signaling method for enabling the broadcast reception apparatus 100 to receive at least one of a broadcast service and content in the next generation broadcast system.
  • the broadcast service signaling method according to the embodiment of FIG. 62 may be based on the configuration of the signaling message shown in FIG. 60 .
  • the broadcast service signaling message according to the embodiment of FIG. 62 may be transmitted via a service signaling channel.
  • the service signaling channel may be a physical layer pipe for directly transmitting the service signaling information for broadcast service scan without passing through other layers.
  • the service signaling channel may be referred to as at least one of a fast information channel (FIC), low layer signaling (LLS) and an application layer transport session.
  • FIC fast information channel
  • LLS low layer signaling
  • the broadcast service signaling message according to the embodiment of FIG. 62 may be in an XML format.
  • the service signaling message according to the embodiment of FIG. 62 may include information on the number of services included therein. More specifically, one service signaling message may include a plurality of services and include information on the number of services included therein.
  • the information on the number of services may be a num_services field. In a detailed embodiment, the num_services field may have a size of 8 bits.
  • the service signaling message according to the embodiment of FIG. 62 may include identifier information of the service.
  • the identifier information may be a service_id field.
  • the service_id field may have a size of 16 bits.
  • the service signaling message according to the embodiment of FIG. 62 may include service type information.
  • the service type information may be a service_type field.
  • the service_type field has a value of 0x00
  • the service type indicated by the signaling message may be a scheduled audio service.
  • the service type indicated by the signaling message may be a scheduled audio/video service.
  • the scheduled audio/video service may be an audio/video service broadcast according to a predetermined schedule.
  • the service type indicated by the signaling message may be an on-demand service.
  • the on-demand service may be an audio/video service presented by the request of the user.
  • the on-demand service may be a service having a concept opposed to that of the scheduled audio/video service.
  • the service type indicated by the signaling message may be an app-based service.
  • the app-based service is not a real-time broadcast service but is a non-real-time service and is provided via an application.
  • the app-based service may include at least one of a service associated with a real-time broadcast service and a service not associated with the real-time broadcast service.
  • the broadcast reception apparatus 100 may download an application and provide an app-based service.
  • the service type indicated by the signaling message may be a rights issuer service.
  • the rights issuer service may be provided to only a person who has rights to receive a service.
  • the service type indicated by the signaling message may be a service guide service.
  • the service guide service may provide information on a provided service.
  • the information on the provided service may be a broadcast schedule.
  • the service signaling message according to the embodiment of FIG. 62 may include service name information.
  • the service name information may be a short_service_name field.
  • the service signaling message according to the embodiment of FIG. 62 may include length information of the short_service_name field.
  • the length information of the short_service_name field may be a short_service_name_length field.
  • the service signaling message according to the embodiment of FIG. 62 may include may include broadcast service channel number information associated with a service.
  • the associated broadcast service channel number information may be a channel_number field.
  • the service signaling message according to the embodiment of FIG. 62 may include data necessary for the broadcast reception apparatus to acquire a timebase or a signaling message according to the transport mode.
  • the data necessary to acquire the timebase or the signaling message may be a bootstrap( ) field.
  • the transport mode may be at least one of a timebase transport mode and a signaling transmission mode.
  • the timebase transport mode may be a transport mode for timebase including metadata for a timeline used for a broadcast service.
  • the timeline is a series of time information for media content. More specifically, the timeline may be a series of reference times which is a media content presentation criterion.
  • Information on the timebase transport mode may be a timebase_transport_mode field.
  • the signaling transmission mode may be a mode for transmitting a signaling message used in a broadcast service.
  • the information on the signaling transport mode may be a signaling_transport_mode field.
  • FIG. 63 is a diagram showing the meaning of the value of a timebase_transport_mode field and a signaling_transport_mode field in a service signaling message according to one embodiment of the present invention.
  • the timebase transport mode may include a mode in which the broadcast reception apparatus 100 acquires the timebase of the broadcast service via an IP datagram in the same broadcast stream.
  • the timebase_transport_mode field may indicate that the broadcast reception apparatus may acquire the timebase of the broadcast service via the IP datagram in the same broadcast stream.
  • the signaling transport mode may include a mode in which the broadcast reception apparatus 100 acquires the signaling message used for the broadcast service via an IP datagram in the same broadcast stream.
  • the signaling_transport_mode field may indicate that the broadcast reception apparatus acquires the signaling message used for the broadcast service via the IP datagram in the same broadcast stream.
  • the same broadcast stream may mean the same broadcast stream as the broadcast stream used for the broadcast reception apparatus to receive the current service signaling message.
  • the IP datagram may be a transport unit in which the component configuring the broadcast service or content is encapsulated according to the Internet protocol.
  • the bootstrap( ) field of the timebase and the signaling message may follow the shown syntax.
  • the shown syntax may be represented in XML format.
  • FIG. 64 is a diagram showing the syntax of the bootstrap( ) field when the timebase_transport_mode field and the signaling_transport_mode field have a value of 0x00 in one embodiment of the present invention.
  • bootstrap data may include information on an IP address format of an IP datagram including the timebase or the signaling message.
  • the information on the IP address format may be an IP_version_flag field.
  • the information on the IP address format may indicate that the IP address format of the IP datagram is IPv4.
  • the information on the IP address format may indicate that the IP address format of the IP datagram is IPv4.
  • the information on the IP address format may indicate that the IP address format of the IP datagram is IPv6.
  • the information on the IP address format is 1, the information on the IP address may indicate that the IP address format of the IP datagram is IPv6.
  • the bootstrap data may include information indicating whether the IP datagram including the timebase or the signaling message includes a source IP address.
  • the source IP address may be a source address of the IP datagram.
  • Information indicating whether the IP datagram includes the source IP address may be a source_IP_address_flag field. In one embodiment, when the source_IP_address_flag field is 1, this may indicate that the IP datagram includes the source IP address.
  • the bootstrap data may include information indicating whether the IP datagram including the timebase or the signaling message includes a destination IP address.
  • the destination IP address may be a destination address of the IP datagram.
  • Information indicating whether the IP datagram includes the destination IP address may be a destination_IP_address_flag field. In one embodiment, when the destination_IP_address_flag field is 1, this may indicate that the IP datagram includes the destination IP address.
  • the bootstrap data may include source IP address information of the IP datagram including the timebase or the signaling message.
  • the source IP address information may be a source_IP_address field.
  • the bootstrap data may include destination IP address information of the IP datagram including the timebase or the signaling message.
  • the destination IP address information may be a destination_IP_address field.
  • the bootstrap data may include information on the number of flow ports of the IP datagram including the timebase or the signaling message.
  • the port may be a passage for receiving the flow of the IP datagram.
  • the information indicating the number of user datagram protocol (UDP) ports of the IP datagram may be a port_num_count field.
  • the bootstrap data may include information on a user data protocol (UDP) port number of the IP datagram including the timebase or the signaling message.
  • UDP user data protocol
  • the user datagram protocol (UDP) is a communication protocol for unidirectionally sending information via the Internet without exchanging information.
  • the timebase transport mode may include a mode in which the broadcast reception apparatus 100 acquires the timebase of the broadcast service via the IP datagram in a different broadcast stream.
  • the timebase_transport_mode field may indicate that the timebase of the broadcast service is acquired via the IP datagram in the different broadcast stream.
  • the different broadcast stream may mean the broadcast stream different from the broadcast stream for receiving the current service signaling message.
  • the signaling transmission mode may include a mode in which the broadcast reception apparatus 100 acquires the signaling message used for the broadcast service via the IP datagram in the different broadcast stream.
  • the signaling_transport_mode field may indicate that the signaling message used for the broadcast service is acquired via the IP datagram in the different broadcast stream.
  • the bootstrap( ) field of the timebase and the signaling message may follow the syntax shown in FIG. 65 .
  • the syntax shown in FIG. 65 may be represented in XML format.
  • the bootstrap data according to the embodiment of FIG. 65 may include identifier information of a broadcaster for transmitting the signaling message. More specifically, the bootstrap data may include unique identifier information of a specific broadcaster for transmitting the signaling message via a specific frequency or a transport frame.
  • the identifier information of the broadcaster may be a broadcasting_id field.
  • the identifier information of the broadcaster may be identifier information of the transport stream for transmitting the broadcast service.
  • the timebase transport mode may include a mode in which the broadcast reception apparatus 100 acquires the timebase via a session based flow in the same broadcast stream.
  • the timebase_transport_mode field when the timebase_transport_mode field has a value of 0x02, this may indicate that the timebase of the broadcast service is acquired via the session based flow in the same broadcast stream.
  • the signaling transport mode may include a mode in which the broadcast reception apparatus 100 acquires the signaling message via a session based flow in the same broadcast stream.
  • the signaling transport mode may include a mode in which the broadcast reception apparatus 100 acquires the signaling message used for the broadcast service via the session based flow in the same broadcast stream.
  • the signaling_transport_mode field When the signaling_transport_mode field has a value of 0x02, this may indicate that the signaling message used for the broadcast service is acquired via the application layer transport session based flow in the same broadcast stream.
  • the application layer transport session based flow may be any one of an asynchronous layered coding (ALC)/layered coding transport (LCT) session and a file delivery over unidirectional transport (FLUTE) session.
  • AAC asynchronous layered
  • the bootstrap( ) field of the timebase and the signaling message may follow the syntax shown in FIG. 66 .
  • the syntax shown in FIG. 66 may be represented in XML format.
  • the bootstrap data according to the embodiment of FIG. 66 may include transport session identifier information of an application layer for transmitting an application layer transport packet including the timebase or the signaling message.
  • the session for transmitting the transport packet may be any one of an ALC/LCT session and a FLUTE session.
  • the transport session identifier information of the application layer may be a tsi field.
  • the timebase transport mode may include a mode in which the broadcast reception apparatus 100 acquires the timebase via a session based flow in the different broadcast stream.
  • the timebase_transport_mode field has a value of 0x03
  • this may indicate that the timebase of the broadcast service is acquired via the session based flow in the different broadcast stream.
  • the signaling transport mode may include a mode in which the broadcast reception apparatus 100 acquires the signaling message via a session based flow in the same broadcast stream.
  • the signaling_transport_mode field has a value of 0x03, this may indicate that the signaling message used for the broadcast service is acquired via the application layer transport session based flow in the different broadcast stream.
  • the application layer transport session based flow may be any one of an asynchronous layered coding (ALC)/layered coding transport (LCT) session and a file delivery over unidirectional transport (FLUTE) session.
  • the bootstrap( ) field of the timebase and the signaling message may follow the syntax shown in FIG. 67 .
  • the syntax shown in FIG. 67 may be represented in XML format.
  • the bootstrap data according to the embodiment of FIG. 67 may include identifier information of a broadcaster for transmitting the signaling message. More specifically, the bootstrap data may include unique identifier information of a specific broadcaster for transmitting the signaling message via a specific frequency or a transport frame.
  • the identifier information of the broadcaster may be a broadcasting_id field.
  • the identifier information of the broadcaster may be identifier information of the transport stream of the broadcast service.
  • the timebase transport mode may include a mode in which the broadcast reception apparatus 100 acquires the timebase via a packet based flow in the same broadcast stream.
  • the timebase_transport_mode field has a value of 0x04, this may indicate that the timebase of the broadcast service is acquired via the packet based flow in the same broadcast stream.
  • the packet based flow may be an MPEG media transport (MMT) packet flow.
  • MMT MPEG media transport
  • the signaling transport mode may include a mode in which the broadcast reception apparatus 100 acquires the signaling message via the packet based flow in the same broadcast stream.
  • the signaling_transport_mode field has a value of 0x04, this may indicate that the signaling message used for the broadcast service is acquired via the transport packet based flow in the same broadcast stream.
  • the packet based flow may be an MMT packet flow.
  • the bootstrap( ) field of the timebase and the signaling message may follow the syntax shown in FIG. 44 .
  • the syntax shown in FIG. 44 may be represented in XML format.
  • the bootstrap data according to the embodiment of FIG. 44 may include identifier information of a transport packet for transmitting the timebase or the signaling message.
  • the identifier information of the transport packet may be a packet_id field.
  • the identifier information of the transport packet may be identifier information of the MPEG-2 transport stream.
  • the timebase transport mode may include a mode in which the broadcast reception apparatus 100 acquires the timebase via a packet based flow in the different broadcast stream.
  • the timebase_transport_mode field when the timebase_transport_mode field has a value of 0x05, this may indicate that the timebase of the broadcast service is acquired via the packet based flow in the different broadcast stream.
  • the packet based flow may be an MPEG media transport packet flow.
  • the signaling transport mode may include a mode in which the broadcast reception apparatus 100 acquires the signaling message via a packet based flow in the different broadcast stream.
  • the signaling_transport_mode field has a value of 0x05, this may indicate that the signaling message used for the broadcast service is acquired via the packet based flow in the different broadcast stream.
  • the packet based flow may be an MMT packet flow.
  • the bootstrap( ) field of the timebase and the signaling message may follow the syntax shown in FIG. 69 .
  • the syntax shown in FIG. 69 may be represented in XML format.
  • the bootstrap data according to the embodiment of FIG. 69 may include identifier information of a broadcaster for transmitting the signaling message. More specifically, the bootstrap data may include unique identifier information of a specific broadcaster for transmitting the signaling message via a specific frequency or a transport frame.
  • the identifier information of the broadcaster may be a broadcasting_id field.
  • the identifier information of the broadcaster may be identifier information of the transport stream of the broadcast service.
  • the bootstrap data according to the embodiment of FIG. 69 may include identifier information of a transport packet for transmitting the timebase or the signaling message.
  • the identifier information of the transport packet may be a packet_id field.
  • the identifier information of the transport packet may be identifier information of an MPEG-2 transport stream.
  • the timebase transport mode may include a mode in which the broadcast reception apparatus 100 acquires the timebase via a URL.
  • the timebase_transport_mode field when the timebase_transport_mode field has a value of 0x06, this may indicate that the timebase of the broadcast service is acquired via the URL.
  • the signaling transport mode may include a mode in which the broadcast reception apparatus 100 acquires the signaling message via the URL.
  • the signaling_transport_mode field has a value of 0x06, this may indicate that the signaling message used for the broadcast service is acquired via the identifier for identifying the reception address of the signaling message used for the broadcast service.
  • the identifier for identifying the reception address of the signaling message used for the broadcast service may be a URL.
  • the bootstrap( ) field of the timebase and the signaling message may follow the syntax shown in FIG. 70 .
  • the syntax shown in FIG. 70 may be represented in XML format.
  • the bootstrap data according to the embodiment of FIG. 70 may include length information of the URL where the timebase or the signaling message of the broadcast service is downloaded.
  • the URL length information may be a URL_length field.
  • the bootstrap data according to the embodiment of FIG. 70 may include actual data of the URL where the timebase or the signaling message of the broadcast service is downloaded.
  • the actual data of the URL may be a URL char_field.
  • FIG. 71 is a diagram showing a process of acquiring a timebase and a service signaling message in the embodiments of FIGS. 62 to 70 .
  • the broadcast reception apparatus 100 may acquire the timebase via a packet based transport protocol. More specifically, the broadcast reception apparatus 100 may acquire the timebase via an IP/UDP flow using a service signaling message. In addition, the broadcast reception apparatus 100 according to one embodiment of the present invention may acquire a service related signaling message via a session based transport protocol. More specifically, the broadcast reception apparatus 100 may acquire a service related signaling message via an ALC/LCT transport session.
  • FIG. 72 is a diagram showing the configuration of a broadcast service signaling message in a next generation broadcast system according to one embodiment of the present invention.
  • the broadcast service signaling message according to one embodiment is for a service signaling method for enabling the broadcast reception apparatus to receive a broadcast service and content in the next generation broadcast system.
  • the broadcast service signaling method according to the embodiment may be based on the above-described signaling message configuration.
  • the broadcast service signaling message according to the embodiment may be transmitted via a service signaling channel.
  • the service signaling channel may be a physical layer pipe for directly transmitting the service signaling information for broadcast service scan without passing through other layers.
  • the signaling channel may be referred to as at least one of a fast information channel (FIC), low layer signaling (LLS) and an application layer transport session.
  • FIC fast information channel
  • LLS low layer signaling
  • the broadcast service signaling message according to the embodiment may be represented in XML format.
  • the service signaling message according to the embodiment of FIG. 72 may include information indicating whether the service signaling message includes information necessary to acquire the timebase.
  • the timebase may include metadata for the timeline used for the broadcast service.
  • the timeline is a series of time information for media content.
  • Information indicating whether information for acquiring the timebase is included may be a timeline_transport_flag field. In one embodiment, when the timeline_transport_flag field has a value of 1, this may indicate that the service signaling message includes information for transmitting the timeline.
  • the service signaling message according to the embodiment of the present invention may include data necessary for the broadcast reception apparatus to acquire the timeline or the signaling message according to the transport mode.
  • the data for acquiring the timeline or the signaling message may be a bootstrap_data( ) field.
  • the transport mode may be at least one of a timebase transport mode and a signaling transport mode.
  • the timebase transport mode may be a transport mode for the timebase including metadata for the timeline used for the broadcast service.
  • the information on the timebase transport mode may be a timebase_transport_mode field.
  • the signaling transport mode may be a mode for transmitting the signaling message used for the broadcast service.
  • the information on the signaling transport mode may be a signaling_transport_mode field.
  • the meaning of the bootstrap_data( ) field according to the timeline_transport_mode field and the signaling_transport_mode field may be equal to the above description.
  • FIG. 73 is a diagram showing the configuration of a broadcast service signaling message in a next generation broadcast system according to one embodiment of the present invention.
  • the broadcast service signaling message according to one embodiment is a service signaling method for enabling the broadcast reception apparatus to receive a broadcast service and content in the next generation broadcast system.
  • the broadcast service signaling method according to the embodiment may be based on the above-described signaling message configuration.
  • the broadcast service signaling message according to the embodiment may be transmitted via a service signaling channel.
  • the service signaling channel may be a physical layer pipe for directly transmitting the service signaling information for broadcast service scan without passing through other layers.
  • the signaling channel may be referred to as at least one of a fast information channel (FIC), low layer signaling (LLS) and an application layer transport session.
  • FIC fast information channel
  • LLS low layer signaling
  • the broadcast service signaling message according to the embodiment of FIG. 72 may be represented in XML format.
  • the service signaling message may include information indicating whether the service signaling message includes information necessary to acquire the timebase.
  • the timebase may include metadata for the timeline used for the broadcast service.
  • the timeline is a series of time information for media content.
  • Information indicating whether information for acquiring the timebase is included may be a timeline_transport_flag field. In one embodiment, when the timeline_transport_flag field has a value of 1, this may indicate that the service signaling message includes information for transmitting the timeline.
  • the service signaling message may include information indicating whether the signaling message includes data necessary to acquire the service signaling message.
  • the signaling message may be media presentation data (MPD) used for the broadcast service or a signaling message related to an MPD URL.
  • MPD media presentation data
  • the information indicating whether the information necessary to acquire the signaling message is included may be an MPD_transport_flag field.
  • MPD_transport_flag field when the MPD_transport_flag field has a value of 1, this may indicate that the service signaling message includes MPD or information on transmission of the signaling message related to the MPD URL.
  • HTTP based adaptive media streaming may be referred to as dynamic adaptive streaming over HTTP (DASH).
  • MPD In adaptive media streaming, detailed information for enabling the broadcast reception apparatus to acquire the segment configuring the broadcast service and content may be referred to as MPD.
  • the MPD may be represented in XML format.
  • the MPD URL related signaling message may include address information capable of acquiring the MPD.
  • the service signaling message may indicate whether the service signaling message includes acquisition path information of component data.
  • the component may be the unit of content data for providing the broadcast service.
  • the information indicating whether the acquisition path information of the component data is included may be a component_location_transport_flag field.
  • the component_location_transport_flag field when the component_location_transport_flag field has a value of 1, the component_location_transport_flag field may indicate that the service signaling message includes the acquisition path information of the component data.
  • the service signaling message according to the embodiment may indicate whether information necessary to acquire an application related signaling message is included.
  • the information indicating whether the information necessary to acquire the application related signaling message is included may be an app_signaling_transport_flag field.
  • the app_signaling_transport_flag field when the app_signaling_transport_flag field has a value of 1, the app_signaling_transport_flag field may indicate that the service signaling message includes acquisition path information of the component data.
  • the service signaling message may indicate whether signaling message transmission related information is included.
  • the information indicating whether the signaling message transmission related information is included may be a signaling_transport_flag field.
  • the signaling_transport_flag field may indicate that the service signaling message includes the signaling message transmission related information.
  • the broadcast reception apparatus may acquire the MPD related signaling, component acquisition path information and application related signaling information via the signaling message transport path.
  • the service signaling message according to the embodiment may indicate a mode for transmitting the timebase used for the broadcast service.
  • the information on the mode for transmitting the timebase may be a timebase_transport_mode field.
  • the service signaling message according to the embodiment may indicate a mode for transmitting an MPD or MPD URL related signaling message used for the broadcast service.
  • the information on the mode for transmitting an MPD or MPD URL related signaling message may be an MPD_transport_mode field.
  • the service signaling message according to the embodiment may indicate a mode for transmitting a component location signaling message including the acquisition path of the component data used for the broadcast service.
  • the information on the mode for transmitting the component location signaling message including the acquisition path of the component data may be a component_location_transport_mode field.
  • the service signaling message according to the embodiment may indicate a mode for transmitting an application related signaling message used for the broadcast service.
  • the information for transmitting the application related signaling message may be an app_signaling_transport_mode field.
  • the service signaling message according to the embodiment may indicate a mode for transmitting a service related signaling message used for the broadcast service.
  • the information on the mode for transmitting the service related signaling message may be a signaling_transport_mode field.
  • FIG. 74 is a diagram showing the meaning of the value of each transport mode.
  • the X_transport_mode may include a timebase_transport_mode, an MPD_transport_mode, a component_location_transport_mode, an app_signaling_transport_mode and a signaling_transport_mode.
  • the detailed meaning of the value of each transport mode is equal to the above description.
  • the service signaling message according to the embodiment of FIG. 73 may include information necessary for the broadcast reception apparatus to acquire the timeline or the signaling message according to the value of each mode.
  • the information necessary to acquire the timebase or the signaling message may be a bootstrap_data( ) field. More specifically, the information included in the bootstrap_data( ) is equal to the above description.
  • FIG. 75 is a diagram showing the configuration of a signaling message for signaling a component data acquisition path of a broadcast service in a next generation broadcast system.
  • one broadcast service may be composed of one or more components.
  • the broadcast reception apparatus may acquire information on the acquisition path of the component data and related application in the broadcast stream.
  • the signaling message according to the embodiment may be represented in XML format.
  • the signaling message according to the embodiment may include information indicating that the signaling message is a message for signaling a component location.
  • the information indicating that the signaling message is the message for signaling the component location may be a signaling_id field.
  • the signaling_id field may have a size of 8 bits.
  • the signaling message according to the embodiment may include extension information indicating that the signaling message is a message for signaling a component location.
  • the extension information includes a protocol version of a message for signaling a component location.
  • the extension information may be a signaling_id_extension field.
  • the signaling message according to the embodiment of FIG. 50 may include version information of the message for signaling the component location.
  • the version information may indicate that the information of the message for signaling the component location has been changed.
  • the version information may be a version_number field.
  • the signaling message according to the embodiment may include identifier information of an associated broadcast service.
  • the identifier information of the associated broadcast service may be a service_id field.
  • the signaling message according to the embodiment may include the number of components associated with the broadcast service.
  • the number of associated components may be a num_component field.
  • the signaling message according to the embodiment may include the identifier of each component.
  • the component identifier may be configured by combining the MPD@id, period@id and representation@id of MPEG DASH.
  • the identifier information of each component may be a component_id field.
  • the signaling message according to the embodiment may include the length of the component_id field.
  • the length information of the component_id field may be a component_id_length field.
  • the signaling message according to the embodiment may include frequency information indicating a frequency capable of acquiring the component data.
  • the component data may include a DASH segment.
  • the frequency information capable of acquiring the component data may be a frequency_number field.
  • the signaling message according to the embodiment may include a unique identifier of a broadcaster.
  • the broadcaster may transmit component data via a transmitted transport frame or a specific frequency.
  • the unique identifier information of the broadcaster may be a broadcast_id field.
  • the signaling message according to the embodiment may include the identifier of a physical layer pipe for transmitting component data.
  • the identifier information of the physical layer pipe for transmitting the component data may be a datapipe_id field.
  • the signaling message according to the embodiment may include an IP address format of an IP datagram including component data.
  • the information on the IP address format may be an IP_version_flag field.
  • the information on the IP address format of the IP datagram may be an IP_version_flag field.
  • the signaling message may include information indicating whether the IP datagram including the component data includes a source IP address.
  • Information indicating whether the IP datagram includes the source IP address may be a source_IP_address_flag field. In one embodiment, when the source_IP_address_flag field is 1, this may indicate that the IP datagram includes the source IP address.
  • the signaling message may include information indicating whether the IP datagram including the component data includes a destination IP address.
  • Information indicating whether the IP datagram includes the destination IP address may be a destination_IP_address_flag field. In one embodiment, when the destination_IP_address_flag field is 1, this may indicate that the IP datagram includes the destination IP address.
  • the signaling message according to the embodiment may include source IP address information of the IP datagram including the component data.
  • the signaling message may include source IP address information.
  • the source IP address information may be a source_IP_address field.
  • the signaling message according to the embodiment may include destination IP address information of the IP datagram including the component data.
  • the signaling message may include destination IP address information.
  • the destination IP address information may be a destination_IP_address field.
  • the signaling message according to the embodiment may include UDP port number information of the IP datagram including the component data.
  • the UDP port number information may be a UDP_port_num field.
  • the signaling message according to the embodiment may include transport session identifier information of the application layer for transmitting the transport packet including the component data.
  • the session for transmitting the transport packet may be at least one of an ALC/LCT session and a FLUTE session.
  • the identifier information of the session may be a tsi field.
  • the signaling message according to the embodiment may include identifier information of the transport packet including the component data.
  • the identifier information of the transport packet may be a packet_id field.
  • the signaling message according to the embodiment may include the number of application signaling messages associated with the broadcast service.
  • the broadcast service may be identified according to the service_id field.
  • the information on the number of application signaling messages may be a num_app_signaling field.
  • the signaling message according to the embodiment may include identifier information of the application signaling message.
  • the identifier information of the application signaling message may be an app_signaling_id field.
  • the signaling message according to the embodiment may include length information of the app_signaling_id field.
  • the length information of the app-signaling_id_field may be an app_signaling_id_length field.
  • the signaling message according to the embodiment may include data for the path capable of acquiring the data of the application included in the signaling message associated with the identifier of the application signaling message.
  • the information on the path for acquiring the data of the application included in the signaling message associated with the identifier of the application signaling message may be an app_delivery-info( ) field.
  • FIG. 76 is a diagram showing the syntax of an app_delevery_info( ) field according to one embodiment of the present invention.
  • the data for the path capable of acquiring the data of the application included in the signaling message associated with the identifier of the application signaling message according to the embodiment may include information indicating whether the application or associated data is transmitted via different broadcast streams.
  • the information indicating whether the application or associated data is transmitted via different broadcast streams may be a broadcasting_flag field.
  • the data for the path capable of acquiring the data of the application included in the signaling message associated with the identifier of the application signaling message may include the IP address format of the IP datagram including the application or associated data.
  • the information on the IP address format of the IP datagram may be an IP_version_flag field. In one embodiment, when the IP_version_flag field is 0, this may indicate that the IP datagram including the application or associated data uses IPv4 and, when the IP_version_flag field is 1, this may indicate that the IP datagram including the application or associated data uses IPv6.
  • the data for the path capable of acquiring the data of the application included in the signaling message associated with the identifier of the application signaling message according to the embodiment may include information indicating whether the IP datagram including the application or associated data includes a source IP address.
  • the associated data may be data necessary to execute the application.
  • the information indicating whether the IP datagram including the application or associated data includes the source IP address may be a source_IP_address_flag field. In one embodiment, when the source_IP_address_flag field is 1, this may indicate that the IP datagram includes a source IP address.
  • the data for the path capable of acquiring the data of the application included in the signaling message associated with the identifier of the application signaling message may include information indicating whether the IP datagram including the application or associated data includes a destination IP address.
  • the information indicating whether the IP datagram including the application or associated data includes the destination IP address may be a destination_IP_address_flag field. In one embodiment, when the destination_IP_address_flag field is 1, this may indicate that the IP datagram includes a destination IP address.
  • the data for the path capable of acquiring the data of the application included in the signaling message associated with the identifier of the application signaling message according to the embodiment may include a unique identifier of a broadcaster for transmitting the application or associated identifier.
  • the data for the path capable of acquiring the data of the application included in the signaling message associated with the identifier of the application signaling message may include the identifier of a broadcast service transport stream.
  • the unique identifier information of the broadcaster for transmitting the application or associated data via a transmitted transport frame or a specific frequency may be a broadcast_id field.
  • the data for the path capable of acquiring the data of the application included in the signaling message associated with the identifier of the application signaling message according to the embodiment may include a source IP address of the IP datagram including the application or associated data, when the source_IP_address_flag field has a value of 1.
  • the source IP address information of the IP datagram including the application or associated data may be a source_IP_address field.
  • the data for the path capable of acquiring the data of the application included in the signaling message associated with the identifier of the application signaling message according to the embodiment may include a destination IP address of the IP datagram including the application or associated data, when the destination_IP_address_flag field has a value of 1.
  • the destination IP address information of the IP datagram including the application or associated data may be a destination_IP_address field.
  • the data for the path capable of acquiring the data of the application included in the signaling message associated with the identifier of the application signaling message according to the embodiment may include information on the number of flow ports of the IP datagram including the application or associated data.
  • the information indicating the number of flow ports of the IP datagram including the application or associated data may be a port_num_count field.
  • the data for the path capable of acquiring the data of the application included in the signaling message associated with the identifier of the application signaling message may include information on the UDP port number of the IP datagram including the application or associated data.
  • the information on the UDP port number of the IP datagram including the application or associated data may be a destination_UDP_port_number field.
  • the data for the path capable of acquiring the data of the application included in the signaling message associated with the identifier of the application signaling message may include the identifier of a transport session for transmitting the application or associated data.
  • the transport session for transmitting the application or associated data may be any one of an ALC/LCT session and a FLUTE session.
  • the identifier information of the transport session for transmitting the application or associated data may be a tsi field.
  • FIG. 77 is a diagram showing the syntax of an app_delevery_info( ) field according to another embodiment of the present invention.
  • the data for the path capable of acquiring the data of the application included in the signaling message associated with the identifier of the application signaling message may include the identifier of the transport packet for transmitting the application or associated data.
  • the transport packet for transmitting the application or associated data may follow a protocol based on a packet based transport flow.
  • the packet based transport flow may include an MPEG media transport protocol.
  • the identifier information of the transport packet for transmitting the application or associated data may be a packet_id field.
  • FIG. 78 is a diagram showing component location signaling including path information capable of acquiring one or more component data configuring a broadcast service. More specifically, FIG. 78 shows information on a path capable of acquiring component data including a DASH segment when one or more components configuring the broadcast service are represented by the DASH segment.
  • FIG. 79 is a diagram showing the configuration of the component location signaling of FIG. 78 .
  • the component location signaling according to the embodiment may include identifier information of the MPEG DASH MPD associated with the broadcast service.
  • the identifier information of the MPEG DASH MPD may be an mpdip field.
  • the component location signaling according to the embodiment may include the identifier of period attributes in the MPEG DASH MPD.
  • the identifier information of the period attributes in the MPEG DASH MPD may be a periodid field.
  • the component location signaling may include the identifier of representation attributes in the period indicated by the periodid field.
  • the identifier information of the representation attributes in the period may be a ReptnID field.
  • the component location signaling according to the embodiment may include a frequency number capable of acquiring the DASH segment included in the representation attributes in the period indicated by the ReptnID field.
  • the frequency number capable of acquiring the DASH segment may be an RF channel number.
  • the information on the frequency number capable of acquiring the DASH segment may be an RFChan field.
  • the component location signaling may include the unique identifier of the broadcaster for transmitting the DASH segment through a specific frequency or a transmitted transport frame.
  • the information on the unique identifier of the broadcaster for transmitting the DASH segment may be a Broadcastingid field.
  • the component location signaling may include the identifier of the physical layer pipe for delivering the DASH segment.
  • the physical layer pipe may be a data pipe transmitted via the physical layer.
  • the information on the identifier of the physical layer pipe for delivering the DASH segment may be a DataPipeId field.
  • the component location signaling according to the embodiment may include the destination IP address of the IP datagram including the DASH segment.
  • the destination IP address information of the IP datagram including the DASH segment may be an IPAdd field.
  • the component location signaling according to the embodiment may include the UDP port number of the IP datagram including the DASH segment.
  • the information on the UDP port number of the IP datagram including the DASH segment may be a UDPPort field.
  • the component location signaling may include the identifier of the transport session for transmitting the transport packet including the DASH segment.
  • the identifier of the session for transmitting the transport packet may be at least one of the ALC/LCT session and the FLUTE session.
  • the information on the identifier of the session for transmitting the transport packet may be a TSI field.
  • the component location signaling may include the identifier of the transport packet including the DASH segment.
  • the information on the identifier of the transport packet may be a PacketId field.
  • FIG. 80 is a diagram showing other information included in signaling of a broadcast service in a next generation broadcast system in one embodiment of the present invention.
  • the signaling of the service may include information on a service identifier (id), a service type, a service name, a channel number, a timebase location, a delivery mode, bootstrap info, MPD, an MPD signaling location, a component signaling location, an app signaling location and/or an object flow.
  • the service identifier may indicate information for identifying the service and may be expressed by id attributes.
  • the service type information may indicate the type of the service and may be expressed by serviceType attributes.
  • the service name information may indicate the name of the service and may be expressed by serviceName attributes.
  • the channel number information may indicate information on the channel number related to the service and may be expressed by channelNumber attributes.
  • the timebase location information may indicate the location where the timebase can be acquired and may be expressed by a TimebaseLocation element.
  • the timebase may indicate information indicating metadata for setting the timeline for synchronizing the components included in the service.
  • the delivery mode information included in the timebase location information may indicate the delivery mode of the timebase.
  • the bootstrap information included in the timebase location information may include the bootstrap information of the timebase according to the delivery mode.
  • the MPD may indicate the MPD associated with the service.
  • the MPD signaling location information may indicate the location where signaling related to the MPD or MPD URL can be acquired.
  • the delivery mode information included in the MPD signaling location may indicate the delivery mode of the MPD location signaling.
  • the bootstrap info information included in the MPD signaling location may include the bootstrap information of the MPD or the MPD URL according to the delivery mode.
  • the component signaling location information may indicate component location signaling information associated with the service.
  • the delivery mode information included in the component signaling location information may indicate the delivery mode of the component location signaling.
  • the bootstrap info information included in the component signaling location information may include the bootstrap information of the component location signaling according to the delivery mode.
  • the app signaling location information may indicate the location where the application signaling can be acquired.
  • the delivery mode information included in the app signaling location information may indicate the delivery mode of the application signaling.
  • the bootstrap info information included in the app signaling location information may include the bootstrap information of the application signaling according to the delivery mode.
  • the object flow information may include information on the related object flows for transmitting the components of the service.
  • FIG. 81 is a diagram showing a delivery mode included in service signaling of a next generation broadcast system according to one embodiment of the present invention.
  • the delivery mode may be included in each location element as attributes.
  • the delivery mode may be distinguished as follows according to the value thereof
  • this may indicate that IPv4/IPv6 flows are transmitted through the same broadcast or cellular network as the broadcast stream for receiving the service signaling message.
  • this may indicate that IPv4/IPv6 flows are transmitted through different broadcast networks.
  • the session-based flow may mean an ALC/LCT or FLUTE session according to the embodiment.
  • the session-based flow may mean an ALC/LCT or FLUTE session according to the embodiment.
  • the packet-based flow may mean MMT packet based transmission according to the embodiment.
  • the packet-based flow may mean MMT packet based transmission according to the embodiment.
  • this may indicate that the location is designated by the URL.
  • the values 0x07 to 0xFF of the delivery mode are not set and are used to indicate the other delivery modes.
  • the information included in the timebase location, the MPD signaling location, the component signaling location and the app signaling location element may be transmitted via the path equal to or different from that of the service signaling according to the delivery mode.
  • FIG. 82 is a diagram showing information on a bootstrap included in service signaling of a next generation broadcast system according to one embodiment of the present invention.
  • the information on the bootstrap may be expressed by the BootstrapInfo element as follows.
  • the BootstrapInfo element described in the above-described signaling message may include information for enabling a receiver to acquire timebase information, MPD or MPD URL information, component signaling information, application signaling information, etc. That is, as described above, the BootstrapInfo may be included in each location element. Therefore, the BootstrapInfo element may include information on an IP address, a port number, a transport session identifier and/or an associated packet identifier.
  • the BootstrapInfo element may include attributes such as RFchannel, broadcastID, datapipeID (PLPID), sourceIP, desitinationIP, destinationPort, tsi, URL, packetid, etc.
  • the information included in the BootstrapInfo element may be changed according to the delivery mode included in the location element to which the BootstrapInfo element belongs.
  • the RFchannel attribute may include information on a radio frequency channel carrying a broadcast stream.
  • the broadcastID attribute may indicate the identifier of the broadcaster for transmitting the broadcast stream.
  • the datapipeID (PLPID) attribute may indicate the identifier of the physical layer data pipe carrying IP datagrams.
  • the datapipeID may be expressed by PLPID and the PLPID may indicate the identifier of the physical layer pipe.
  • the sourceIP attribute may indicate the source address of the IP datagrams carrying associated data.
  • the destinationIP attribute may indicate the destination address of the IP datagrams carrying associated data.
  • the destinationPort attribute may indicate the destination port number of the IP datagrams carrying associated data.
  • the tsi attribute may indicate the identifier of the transport session for delivering transport packets carrying associated data.
  • the URL attribute may indicate the URL where associated data can be acquired.
  • the packetid attribute may indicate the identifier of the transport packets carrying associated data.
  • FIG. 83 is a diagram showing information included in signaling for an object flow.
  • Each object flow may be a flow for transmitting one or more components configuring the service. Therefore, one service may include information on one or more object flows.
  • the object flow may include id, objectFormat, contentType and/or contentEncoding attributes.
  • the object flow may include a file element and the file element may include contentLocation and/or TOI attributes.
  • the object flow may include a FileTemplate element and the FileTemplate element may include contentLocTemplate, startTOI, endTOI and/or scale attributes.
  • the object flow may include an ObjectGroup element and the ObjectGroup element may include contentLocation, startTOI and/or end TOI attributes.
  • the object flow may include the above-described Bootstrapinfo element.
  • the id may indicate the identifier of the object flow.
  • the id can be equal to a combination of the MPD identifier, the period identifier and the DASH representation identifier.
  • the objectFormat may indicate the format of the objects in this object flow as described above.
  • the contentType may indicate the media content component type for this object flow.
  • the contentEncoding may indicate the encoding method of the objects delivered via this object flow.
  • the file element may include information on the file.
  • the contentLocation of the file element may indicate the location where the file can be acquired.
  • the contentLocation may be equal to the DASH segment URL.
  • the TOI attribute of the file element is a transport object identifier and may indicate the identifier of the transport object.
  • the FileTemplate element may include information on a file template.
  • the contentLocTemplate of the FileTemplate element may indicate the template used to generate the location where the file can be acquired.
  • the startTOI of the FileTemplate element may indicate a first TOI delivered via this object flow.
  • the endTOI of the FileTemplate element may indicate a last TOI delivered via this object flow.
  • the scale attribute of the FileTemplate element may indicate information on the scale between TIO values in this object flow.
  • the ObjectGroup element may include information on the group of the transport objects delivered via this object flow.
  • the contentLocation of the ObjectGroup element may indicate the location of the content associated with this object group.
  • the startTOI of the ObjectGroup element may indicate a first TOI delivered via this object group.
  • the endTOI of the ObjectGroup element may indicate a last TOI delivered via this object group.
  • the BootstrapInfo element may include the bootstrap information of this object flow.
  • the objectFormat attributes of the information included in the signaling for the object flow according to the embodiment of FIG. 83 may include information on the format of the payload included in this object delivered via the object flow.
  • the object format attributes of the object flow may indicate that the payload included in the flow includes a generic file supporting real-time streaming.
  • the object format according to the first embodiment may be a generic file.
  • the object format attributes of the object flow may indicate that the payload included in the flow includes a data file supporting real-time streaming.
  • the object format attributes according to the second embodiment may indicate the DASH segment in the ISOBMFF.
  • the object format attributes of the object flow may indicate that the payload included in the flow includes a data file represented in the HTTP entity format in order to support real-time streaming.
  • the HTTP entity may be one entity for transmitting content according to HTTP.
  • FIG. 84 is a diagram showing a combination of information for representing a file template in one embodiment of the present invention.
  • the file template may be represented by a combination of Representation@id and segment number.
  • Representation@id and segment number may be combined to dynamically generate information on the content location of each file.
  • the broadcast reception apparatus can efficiently acquire the flow of the transport packets including a specific component according to the dynamically generated content location information.
  • FIG. 85 is a diagram showing an object flow included in service signaling according to one embodiment of the present invention.
  • the object flow may further include a default attribute @isDefault along with the object format attributes described with reference to FIG. 83 . That is, the object flow may include id, objectFormat, contentType, contentEncoding and/or isDefault attributes.
  • the object flow may include a File element and the File element may include contentLocation and/or TOI attributes.
  • the object flow may include a FileTemplate element and the FileTemplate element may include contentLocTemplate, startTOI, endTOI and/or scale attributes.
  • the object flow may include an ObjectGroup element and the ObjectGroup element may include contentLocation, startTOI and/or endTOI attributes.
  • the object flow may include the above-described BootstrapInfo element.
  • the id may indicate the identifier of this object flow.
  • the id can be equal to a combination of the MPD identifier, the period identifier and the DASH representation identifier.
  • the objectFormat may indicate the format of the objects in this object flow as described above.
  • the contentType may indicate the media content component type for this object flow.
  • the contentEncoding may indicate the encoding method of the objects delivered via this object flow.
  • the isDefault may indicate whether the payload included in the object delivered via the object flow includes component data used by default. For example, this may indicate whether the receiver basically receives and represents the component data delivered via this object flow without receiving and processing additional signaling information such as DASH MPD.
  • the file element may include information on the file.
  • the contentLocation of the file element may indicate the location where the file can be acquired.
  • the contentLocation may be equal to the DASH segment URL.
  • the TOI attribute of the file element is a transport object identifier and may indicate the identifier of the transport object.
  • the FileTemplate element may include information on a file template.
  • the contentLocTemplate of the FileTemplate element may indicate the template used to generate the location where the file can be acquired.
  • the startTOI of the FileTemplate element may indicate a first TOI delivered via this object flow.
  • the endTOI of the FileTemplate element may indicate a last TOI delivered via this object flow.
  • the scale attribute of the FileTemplate element may indicate information on the scale between TOI values in this object flow.
  • the ObjectGroup element may include information on the group of transport objects delivered via this object flow.
  • the contentLocation of the ObjectGroup element may indicate the location of the content associated with this object group.
  • the startTOI of the ObjectGroup element may indicate a first TOI delivered via this object group.
  • the endTOI of the ObjectGroup element may indicate a last TOI delivered via this object group.
  • the BootstrapInfo element may include the bootstrap information of this object flow.
  • FIG. 86 is a diagram showing other information included in signaling of a broadcast service in a next generation broadcast system in one embodiment of the present invention.
  • An existing FLUTE client may receive a file description table (FDT) and then a broadcast reception apparatus may receive a file according to the FDT.
  • FDT file description table
  • this method is not suitable for transmission and reception of the file via the real-time broadcast service.
  • the FLUTE protocol may not be suitably applied to the real-time broadcast service using a unidirectional transport protocol.
  • the service signaling may include FDT information.
  • the FDTInstance element may include an @id attribute (element).
  • the @id attribute may indicate the specific identifier of the FDT instance.
  • the broadcast reception apparatus may identify the FDT instance via the @id attribute to dynamically generate the FDT instance.
  • the broadcast reception apparatus may receive and process real-time streaming data represented in the form of the file according to the generated FDT instance (The other attributes should be described).
  • the FDTInstance element may include an @Expires attribute.
  • the @Expires attribute may include information on the expiration information of the FDTInstance. Accordingly, the broadcast reception apparatus 100 may discard the expired FDTInstance according to the @Expires attribute.
  • the FDTInstance element may include an @Complete attribute.
  • the @Complete attribute when the @Complete attribute has a true value, the @Complete attribute may indicate that the future FDTInstance to be provided in the same session does not include new data.
  • the FDTInstance element may include an @Content-Location attribute.
  • the @Content-Location attribute may be assigned a valid URI.
  • the FDTInstance element may include an @TOI attribute.
  • the @TOI attribute is necessarily assigned a valid TOI value.
  • the FDTInstance element may include an @Content-Length attribute.
  • the @Content-Length attribute may be the actual length information of the file content.
  • the FDTInstance element may include an @Transfer-Length attribute.
  • the @Transfer-Length attribute may be the transfer length of file content.
  • the FDTInstance element may include an @Content-Encoding attribute.
  • the @Content-Encoding attribute may be encoding information of file content.
  • the FDTInstance element may include an @Content-Type attribute.
  • the @Content-Type attribute may be type information of file content.
  • FIG. 87 is a diagram showing signaling information for transport session information of a session level according to one embodiment of the present invention.
  • signaling information describing the transport session information of a session level such as a TSID
  • the TSID may be transmitted via some of the signaling message using various methods such as an in-band method of transport content or an out-of-band method using a separate path.
  • the TSID is an abbreviation for transport session instance descriptor and may indicate a descriptor including detailed information on the transport session.
  • the TSID may include a tsi attribute, a PayloadFormat element transmitted via a SourceFlow and/or a RepairFlow.
  • the PayloadFormat element may include codePoint, protocol, deliveryObjectFormat, realtime, isobmff and/or packetheadersize attributes.
  • the PayloadFormat element may include EFID and/or ApplicationIdentifier elements.
  • the tsi may indicate a transport session identifier.
  • the codePoint may define what code point value is used for this payload. This value may indicate the value of the CP field of the LCT header.
  • the protocol indicates the transport protocol of this payload. That is, the protocol may define the transport protocol of each payload at a payload level.
  • Various types may exist in the LCT based transport protocol and the type may be identified by assigning an integer value to each type. For example, 0 may identify the ALC and 1 may identify ROUTE.
  • the same identification method is applicable to the other protocols and new protocols to be defined in the future.
  • the other @protocol value may be assigned in units of the LCT packet having the codepoint value equal to the value assigned to the @codepoint to transmit content using various protocols within one transport session.
  • the deliveryObjectFormat may indicate the payload format of the transport object.
  • the realtime may indicate whether the LCT packet includes component data for a real-time service.
  • this may indicate whether an extension header including NTP timestamps representing the presentation time of the transport object is included.
  • the isobmff may indicate whether the transport object is a sequence of ISOBMFF boxes, a DASH object referred to by the MPD or a sequence of ISOBMFF boxes fragmented according to a MPU mode of an MMT.
  • the packetheadersize may indicate the size of the route packet header.
  • the EFID may include detailed information of file delivered data.
  • the ApplicationIdentifier may provide additional information which can be mapped to the application which is carried in this transport session, e.g., the RepresentationID of the DASH content.
  • FIG. 88 is a diagram showing signaling information for transport session information of a session level according to another embodiment of the present invention.
  • signaling information describing the transport session information of a session level such as a TSID
  • the TSID may be transmitted via some of the signaling message using various methods such as an in-band method of transport content or an out-of-band method using a separate path.
  • the TSID may have the following structure. That is, a protocol attribute may exist at TransportSession protocol attribute and may indicate that all packets of the session having the TSI value of the tsi attribute are transmitted via the protocol corresponding to the value assigned to the protocol attribute.
  • the TSID may include a tsi attribute, a protocol attribute of a SourceFlow, a PayloadFormat element and/or a RepiarFlow of each transport session.
  • the PayloadFormat element may include codePoint, deliveryObjectFormat, realtime, isobmff and/or packetheadersize attributes.
  • the PayloadFormat element may include EFID and/or ApplicationIdentifier elements.
  • the tsi may indicate a transport session identifier.
  • the protocol indicates the transport protocol of this payload.
  • Various types may exist in the LCT based transport protocol and the type may be identified by assigning an integer value to each type. For example, 0 may identify the ALC and 1 may identify ROUTE.
  • the same identification method is applicable to the other protocols and new protocols to be defined in the future.
  • content transmission using the same protocol is possible with respect to all the packets included in one transport session.
  • the codePoint may define what code point value is used for this payload. This value may indicate the value of the CP field of the LCT header.
  • the deliveryObjectFormat may indicate the payload format of the transport object.
  • the realtime may indicate whether the LCT packet includes an extension header including NTP timestamps representing the presentation time of the transport object.
  • the isobmff may indicate whether the transport object is a sequence of ISOBMFF boxes, a DASH object referred to by the MPD or a sequence of ISOBMFF boxes fragmented according to a MPU mode of an MMT.
  • the packetheadersize may indicate the size of the route packet header.
  • the EFID may include detailed information of file delivered data.
  • the ApplicationIdentifier may provide additional information which can be mapped to the application which is carried in this transport session, e.g., the RepresentationID of the DASH content.
  • FIG. 89 is a diagram showing signaling information of a broadcast service according to another embodiment of the present invention.
  • the signaling information of the broadcast service according to one embodiment of the present invention may be referred to as user service description.
  • the signaling information of the broadcast service according to one embodiment of the present invention may include service identifier (id), service type, service name, channel number, timebase location, delivery mode, bootstrap info, MPD and/or signaling location fields.
  • the signaling location field may have the same meaning as the MPD signaling location field. The above-described fields were described above in detail.
  • FIG. 90 is a diagram showing FDT related information included in signaling information of a broadcast service according to another embodiment of the present invention.
  • the FDTInstance element according to another embodiment of the present invention may further include a version attribute in addition to the attributes included in the FDTInstance elements according to the above-described embodiment.
  • the version attribute according to one embodiment of the present invention may indicate the version information of the FDTInstance.
  • the receiver according to one embodiment of the present invention may confirm whether the currently transmitted FDTInstance is equal to the previously received FDTInstance using the received version attribute.
  • FIG. 91 is a diagram showing the configuration of the binary format of a Service_Mapping_Table according to one embodiment of the present invention.
  • One embodiment of the present invention may provide a service signaling method when a ROUTE protocol and/or an MMP protocol for transmitting a real-time object based on a session is used.
  • the service mapping table according to one embodiment of the present invention may include service signaling information in a broadcast system according to the ROUTE protocol and/or the MMT protocol.
  • the service mapping table according to one embodiment of the present invention may be referred to as user service bundle description.
  • the service mapping table may include a Signaling_id field, a Signaling_length field, a Protocol_version field, a Broadcast_id field, a Version_number field, an Ip_version_flag field, a Signaling_data_type field, an expiration field, a Fragment_number field, a Last_fragment_number field, a Num_services field, a Service_id field, a Service_name_length field, a Service_name field, a Channel_number field, a service_category field, a Service_status field, an SP_indicator field, a Num_route_sessions field, a Source_ip field, a Destination_ip field, a Port field, a Num_lsid_tsi field and an Lsid_delivery_tsi field.
  • the Signaling_id field indicates the ID indicating that this table is a service mapping table (SMT).
  • the Signaling_length field indicates the length of the section after the SMT header.
  • the Protocol_version field indicates the version information of the signaling protocol.
  • the Broadcast_id field indicates a unique ID of the broadcast.
  • the Version_number field indicates the version number of the signaling data, that is, the version information of this table.
  • the Ip_version_flag field indicates the flag information indicating the IP described in this table is v4 or v6. When the value of this field is 0 by default, the IP is v4 and, when the value of this field 1, the IP is v6.
  • the Signaling_data_type field indicates whether the type of the signaling data included in this table is binary or xml.
  • the expiration field indicates the valid period of this table.
  • the Fragment_number field indicates the fragment number of this table when all signaling data is fragmented and transmitted.
  • the fragment number may be referred to as a section number.
  • the Last_fragment_number field indicates the number of the last fragment when all signaling data is fragmented and transmitted.
  • the last fragment number may be referred to as a last section number.
  • the Num_services field indicates the number of services transmitted in the SMT.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Databases & Information Systems (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
US14/913,279 2014-08-22 2015-08-21 Method for transmitting broadcast signals, apparatus for transmitting broadcast signals, method for receiving broadcast signals and apparatus for receiving broadcast signals Abandoned US20160277545A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/913,279 US20160277545A1 (en) 2014-08-22 2015-08-21 Method for transmitting broadcast signals, apparatus for transmitting broadcast signals, method for receiving broadcast signals and apparatus for receiving broadcast signals

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201462040419P 2014-08-22 2014-08-22
PCT/KR2015/008769 WO2016028119A1 (ko) 2014-08-22 2015-08-21 방송 신호 송신 방법, 방송 신호 송신 장치, 방송 신호 수신 방법 및 방송 신호 수신 장치
US14/913,279 US20160277545A1 (en) 2014-08-22 2015-08-21 Method for transmitting broadcast signals, apparatus for transmitting broadcast signals, method for receiving broadcast signals and apparatus for receiving broadcast signals

Publications (1)

Publication Number Publication Date
US20160277545A1 true US20160277545A1 (en) 2016-09-22

Family

ID=55350986

Family Applications (4)

Application Number Title Priority Date Filing Date
US14/913,279 Abandoned US20160277545A1 (en) 2014-08-22 2015-08-21 Method for transmitting broadcast signals, apparatus for transmitting broadcast signals, method for receiving broadcast signals and apparatus for receiving broadcast signals
US14/913,639 Active 2035-12-20 US10645674B2 (en) 2014-08-22 2015-08-21 Method for transmitting broadcast signals, apparatus for transmitting broadcast signals, method for receiving broadcast signals and apparatus for receiving broadcast signals
US16/829,474 Active 2035-10-19 US11212772B2 (en) 2014-08-22 2020-03-25 Method for transmitting broadcast signals, apparatus for transmitting broadcast signals, method for receiving broadcast signals and apparatus for receiving broadcast signals
US17/523,562 Active US11678346B2 (en) 2014-08-22 2021-11-10 Method for transmitting broadcast signals, apparatus for transmitting broadcast signals, method for receiving broadcast signals and apparatus for receiving broadcast signals

Family Applications After (3)

Application Number Title Priority Date Filing Date
US14/913,639 Active 2035-12-20 US10645674B2 (en) 2014-08-22 2015-08-21 Method for transmitting broadcast signals, apparatus for transmitting broadcast signals, method for receiving broadcast signals and apparatus for receiving broadcast signals
US16/829,474 Active 2035-10-19 US11212772B2 (en) 2014-08-22 2020-03-25 Method for transmitting broadcast signals, apparatus for transmitting broadcast signals, method for receiving broadcast signals and apparatus for receiving broadcast signals
US17/523,562 Active US11678346B2 (en) 2014-08-22 2021-11-10 Method for transmitting broadcast signals, apparatus for transmitting broadcast signals, method for receiving broadcast signals and apparatus for receiving broadcast signals

Country Status (5)

Country Link
US (4) US20160277545A1 (de)
EP (1) EP3185506A4 (de)
KR (3) KR101850726B1 (de)
CN (2) CN105684392B (de)
WO (2) WO2016028119A1 (de)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10715511B2 (en) 2018-05-03 2020-07-14 Honeywell International Inc. Systems and methods for a secure subscription based vehicle data service
US10819689B2 (en) 2018-05-03 2020-10-27 Honeywell International Inc. Systems and methods for encrypted vehicle data service exchanges
US10819418B2 (en) * 2016-04-29 2020-10-27 Honeywell International Inc. Systems and methods for secure communications over broadband datalinks
US10939180B2 (en) 2016-09-13 2021-03-02 Samsung Electronics Co., Ltd. Device and method for transmitting media data across multiple frequency bands
US11032200B2 (en) * 2015-01-21 2021-06-08 Lg Electronics Inc. Apparatus for transmitting broadcast signal, apparatus for receiving broadcast signal, method for transmitting broadcast signal and method for receiving broadcast signal
US11159847B2 (en) * 2016-09-22 2021-10-26 DISH Technologies L.L.C. Apparatus, systems and methods for reducing time required for a media content event channel change
US20230043881A1 (en) * 2021-08-06 2023-02-09 Sony Group Corporation Techniques for atsc 3.0 broadcast boundary area management using complete service reception during scan to determine signal quality of frequencies carrying the duplicate service
US11848716B2 (en) 2021-08-06 2023-12-19 Sony Group Corporation Techniques for ATSC 3.0 broadcast boundary area management using signal quality and packet errors to differentiate between duplicated services on different frequencies during scan

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3185506A4 (de) 2014-08-22 2018-04-18 LG Electronics Inc. Verfahren zum senden von rundfunksignalen, vorrichtung zum senden von rundfunksignalen, verfahren zum senden von rundfunksignalen sowie verfahren zum empfangen von rundfunksignalen
CN107682113B (zh) * 2017-08-29 2020-08-14 西安空间无线电技术研究所 一种级联ldpc码在atm交换网络中的编译码方法
KR102106632B1 (ko) 2019-04-01 2020-05-04 주식회사 캐스트코아 디지털 방송신호 절체 장치 및 그 방법
KR102345314B1 (ko) 2021-07-30 2021-12-31 주식회사 캐스트코아 디지털 신호처리를 통한 주파수 변조신호 중계장치
WO2023017871A1 (ko) * 2021-08-12 2023-02-16 엘지전자 주식회사 미디어 데이터 처리 방법 및 미디어 데이터 처리 장치

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020063150A1 (en) * 2000-11-27 2002-05-30 Kaj Nygren Scalable distributed database system and method for linking codes to internet information
WO2011105803A2 (ko) * 2010-02-23 2011-09-01 엘지전자 주식회사 방송 신호 송신 장치, 방송 신호 수신 장치, 및 방송 신호 송/수신 장치에서 방송 신호 송수신 방법
US20130034032A1 (en) * 2011-08-05 2013-02-07 Nokia Corporation Accessing Service Guide Information in a Broadcast System
US20170099517A1 (en) * 2014-05-30 2017-04-06 Sony Corporation Reception apparatus, reception method, transmission apparatus and transmission method

Family Cites Families (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4316593B2 (ja) * 2006-09-04 2009-08-19 日本電気通信システム株式会社 無線装置およびそれを備えた無線通信ネットワーク
KR101461958B1 (ko) * 2007-06-29 2014-11-14 엘지전자 주식회사 디지털 방송 시스템 및 데이터 처리 방법
MX2010002029A (es) 2007-08-24 2010-03-15 Lg Electronics Inc Sistema de difusion digital y metodo de procesamiento de datos en sistema de difusion digital.
US7733819B2 (en) 2007-08-24 2010-06-08 Lg Electronics Inc. Digital broadcasting system and method of processing data in digital broadcasting system
KR101507851B1 (ko) 2008-04-13 2015-04-06 엘지전자 주식회사 송/수신 시스템 및 데이터 처리 방법
KR101294023B1 (ko) 2008-05-29 2013-08-08 한국전자통신연구원 방송/통신 데이터 송수신 방법 및 장치
US8250619B2 (en) * 2008-06-09 2012-08-21 Lg Electronics Inc. Method of receiving a broadcasting signal and receiving system for receiving a broadcasting signal
KR101172792B1 (ko) * 2008-11-26 2012-08-20 한국방송공사 방송 시스템에서 부가 정보 삽입 장치 및 방법
KR101065420B1 (ko) 2008-12-16 2011-09-16 한양대학교 산학협력단 상지거동을 위한 착용형 로봇장치
EP2207354B1 (de) 2009-01-13 2012-03-14 Alcatel-Lucent España, S.A. Verfahren und Vorrichtung zur Zuverlässigkeitssicherstellung während der Übertragung von Fernsehdaten in einem Internetprotokoll basierendem Fernsehsystem
WO2010107167A1 (en) * 2009-03-19 2010-09-23 Lg Electronics Inc. Transmitting/receiving system and method of processing data in the transmitting/receiving system
KR101652808B1 (ko) * 2009-03-19 2016-09-01 엘지전자 주식회사 송/수신 시스템 및 데이터 처리 방법
CA2818107C (en) * 2010-02-12 2017-06-27 Lg Electronics Inc. Broadcasting signal transmitter/receiver and broadcasting signal transmission/reception method
US8498272B2 (en) 2010-08-26 2013-07-30 Nokia Corporation Providing signaling information and performing a handover using the signaling information
US9348691B2 (en) * 2010-09-14 2016-05-24 Lg Electronics Inc. Apparatus for transmitting broadcast signal, apparatus for receiving broadcast signal, and method for transmitting/receiving broadcast signal through apparatus for transmitting/receiving broadcasting signal
WO2012036429A2 (ko) 2010-09-14 2012-03-22 엘지전자 주식회사 방송 신호 송신 장치, 방송 신호 수신 장치, 및 방송 신호 송/수신 장치에서 방송 신호 송수신 방법
KR20140094628A (ko) 2010-12-26 2014-07-30 엘지전자 주식회사 방송 서비스 전송 방법, 그 수신 방법 및 그 수신 장치
WO2012091371A1 (en) * 2010-12-26 2012-07-05 Lg Electronics Inc. Method for transmitting broadcast service, method for receiving the broadcasting service, and apparatus for receiving the broadcasting service
WO2012121571A2 (ko) 2011-03-10 2012-09-13 한국전자통신연구원 비실시간 스테레오스코픽 방송 서비스 송신 및 수신 장치, 그리고 송신 및 수신 방법
US9485108B2 (en) 2011-03-14 2016-11-01 Qualcomm Incorporated System and apparatus for using multichannel file delivery over unidirectional transport (“FLUTE”) protocol for delivering different classes of files in a broadcast network
WO2012125006A2 (ko) * 2011-03-16 2012-09-20 한국전자통신연구원 레프리젠테이션을 사용하는 스트리밍 콘텐츠 제공 장치 및 방법
WO2012144867A2 (ko) 2011-04-20 2012-10-26 엘지전자 주식회사 방송 서비스 전송 방법, 그 수신 방법 및 그 수신 장치
US9590814B2 (en) * 2011-08-01 2017-03-07 Qualcomm Incorporated Method and apparatus for transport of dynamic adaptive streaming over HTTP (DASH) initialization segment description fragments as user service description fragments
KR20130056829A (ko) 2011-11-22 2013-05-30 한국전자통신연구원 3dtv 방송을 위한 송수신 장치 및 그 제어 방법
MX338815B (es) * 2012-02-07 2016-05-03 Sony Corp Dispositivo de recepcion, metodo de recepcion, y programa.
EP2823627A2 (de) * 2012-03-05 2015-01-14 Interdigital Patent Holdings, Inc. Vorrichtungen und verfahren zur erkennung von vorverknüpfungen in kommunikationsnetzen
KR20130102984A (ko) 2012-03-09 2013-09-23 한국전자통신연구원 방송 시스템에서의 데이터 전송 장치 및 방법
JP6326213B2 (ja) * 2013-10-04 2018-05-16 サターン ライセンシング エルエルシーＳａｔｕｒｎ Ｌｉｃｅｎｓｉｎｇ ＬＬＣ 受信装置、受信方法、送信装置、及び、送信方法
KR101779435B1 (ko) 2014-01-03 2017-09-18 엘지전자 주식회사 방송 신호를 송신하는 장치, 방송 신호를 수신하는 장치, 방송 신호를 송신하는 방법 및 방송 신호를 수신하는 방법
US10743082B2 (en) 2014-04-11 2020-08-11 Sony Corporation Reception apparatus, reception method, transmission apparatus, and transmission method
US9645878B2 (en) * 2014-07-09 2017-05-09 Qualcomm Incorporated Error handling for files exchanged over a network
EP3185506A4 (de) 2014-08-22 2018-04-18 LG Electronics Inc. Verfahren zum senden von rundfunksignalen, vorrichtung zum senden von rundfunksignalen, verfahren zum senden von rundfunksignalen sowie verfahren zum empfangen von rundfunksignalen
US10171849B1 (en) * 2015-07-08 2019-01-01 Lg Electronics Inc. Broadcast signal transmission device, broadcast signal reception device, broadcast signal transmission method, and broadcast signal reception method

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020063150A1 (en) * 2000-11-27 2002-05-30 Kaj Nygren Scalable distributed database system and method for linking codes to internet information
WO2011105803A2 (ko) * 2010-02-23 2011-09-01 엘지전자 주식회사 방송 신호 송신 장치, 방송 신호 수신 장치, 및 방송 신호 송/수신 장치에서 방송 신호 송수신 방법
US20130291046A1 (en) * 2010-02-23 2013-10-31 Lg Electronics Inc. Broadcasting signal transmission device, broadcasting signal reception device, and method for transmitting/receiving broadcasting signal using same
US20130034032A1 (en) * 2011-08-05 2013-02-07 Nokia Corporation Accessing Service Guide Information in a Broadcast System
US20170099517A1 (en) * 2014-05-30 2017-04-06 Sony Corporation Reception apparatus, reception method, transmission apparatus and transmission method

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11032200B2 (en) * 2015-01-21 2021-06-08 Lg Electronics Inc. Apparatus for transmitting broadcast signal, apparatus for receiving broadcast signal, method for transmitting broadcast signal and method for receiving broadcast signal
US10819418B2 (en) * 2016-04-29 2020-10-27 Honeywell International Inc. Systems and methods for secure communications over broadband datalinks
US11265616B2 (en) 2016-09-13 2022-03-01 Samsung Electronics Co., Ltd. Device and method for transmitting media data across multiple frequency bands
US11671676B2 (en) 2016-09-13 2023-06-06 Samsung Electronics Co., Ltd. Device and method for transmitting media data across multiple frequency bands
US10939180B2 (en) 2016-09-13 2021-03-02 Samsung Electronics Co., Ltd. Device and method for transmitting media data across multiple frequency bands
US11159847B2 (en) * 2016-09-22 2021-10-26 DISH Technologies L.L.C. Apparatus, systems and methods for reducing time required for a media content event channel change
US11818422B2 (en) 2016-09-22 2023-11-14 DISH Technologies L.L.C. Apparatus, systems and methods for reducing time required for a media content event channel change
US10715511B2 (en) 2018-05-03 2020-07-14 Honeywell International Inc. Systems and methods for a secure subscription based vehicle data service
US11070536B2 (en) 2018-05-03 2021-07-20 Honeywell International Inc. Systems and methods for a secure subscription based vehicle data service
US11496451B2 (en) 2018-05-03 2022-11-08 Honeywell International Inc. Systems and methods for encrypted vehicle data service exchanges
US10819689B2 (en) 2018-05-03 2020-10-27 Honeywell International Inc. Systems and methods for encrypted vehicle data service exchanges
US20230043881A1 (en) * 2021-08-06 2023-02-09 Sony Group Corporation Techniques for atsc 3.0 broadcast boundary area management using complete service reception during scan to determine signal quality of frequencies carrying the duplicate service
US11838680B2 (en) * 2021-08-06 2023-12-05 Sony Group Corporation Techniques for ATSC 3.0 broadcast boundary area management using complete service reception during scan to determine signal quality of frequencies carrying the duplicate service
US11848716B2 (en) 2021-08-06 2023-12-19 Sony Group Corporation Techniques for ATSC 3.0 broadcast boundary area management using signal quality and packet errors to differentiate between duplicated services on different frequencies during scan

Also Published As

Publication number Publication date
KR20160040529A (ko) 2016-04-14
US10645674B2 (en) 2020-05-05
US11678346B2 (en) 2023-06-13
KR101783618B1 (ko) 2017-10-10
WO2016028120A1 (ko) 2016-02-25
EP3185506A4 (de) 2018-04-18
CN105830372A (zh) 2016-08-03
US11212772B2 (en) 2021-12-28
KR101850726B1 (ko) 2018-04-20
US20160295553A1 (en) 2016-10-06
CN105830372B (zh) 2019-06-14
EP3185506A1 (de) 2017-06-28
US20200229138A1 (en) 2020-07-16
US20220078750A1 (en) 2022-03-10
KR101861696B1 (ko) 2018-05-28
CN105684392B (zh) 2019-11-22
KR20170113708A (ko) 2017-10-12
WO2016028119A1 (ko) 2016-02-25
KR20160036040A (ko) 2016-04-01
CN105684392A (zh) 2016-06-15

Similar Documents

Publication Publication Date Title
US10645674B2 (en) Method for transmitting broadcast signals, apparatus for transmitting broadcast signals, method for receiving broadcast signals and apparatus for receiving broadcast signals
US20170111692A1 (en) Broadcasting transmission device, method for operating broadcasting transmission device, broadcasting reception device, and method for operating broadcasting reception device
US11323490B2 (en) Broadcast signal transmission device, broadcast signal receiving device, broadcast signal transmission method and broadcast signal receiving method
US20210360329A1 (en) Broadcast transmission device and operating method thereof, and broadcast reception device and operating method thereof
US11309982B2 (en) Broadcast signal transmission device, broadcast signal reception device, broadcast signal transmission method and broadcast signal reception method
US11019679B2 (en) Broadcast transmission apparatus, operation method of broadcast transmission apparatus, broadcast reception apparatus, and operation method of broadcast reception apparatus
EP3148196A1 (de) Verfahren und vorrichtung zum senden/empfangen eines rundfunksignals
US9866804B2 (en) Broadcast signal transmission apparatus, broadcast signal reception apparatus, broadcast signal transmission method, and broadcast signal reception method
US20170188062A1 (en) Method and apparatus for transmitting/receiving broadcast signal
US10079649B2 (en) Broadcast signal transmission apparatus, broadcast signal receiving apparatus, broadcast signal transmission method, and broadcast signal receiving method
KR101841947B1 (ko) 방송 전송 장치, 방송 전송 장치의 동작 방법, 방송 수신 장치 및 방송 수신 장치의 동작 방법

Legal Events

Date Code Title Description
AS Assignment

Owner name: LG ELECTRONICS INC., KOREA, REPUBLIC OF

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KWAK, MINSUNG;OH, SEJIN;MOON, KYOUNGSOO;AND OTHERS;SIGNING DATES FROM 20160129 TO 20160216;REEL/FRAME:037877/0236

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION