WO2017007258A1 - Dispositif de transmission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé de transmission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion - Google Patents

Dispositif de transmission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé de transmission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion Download PDF

Info

Publication number
WO2017007258A1
WO2017007258A1 PCT/KR2016/007366 KR2016007366W WO2017007258A1 WO 2017007258 A1 WO2017007258 A1 WO 2017007258A1 KR 2016007366 W KR2016007366 W KR 2016007366W WO 2017007258 A1 WO2017007258 A1 WO 2017007258A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
information
component
video
broadcast
Prior art date
Application number
PCT/KR2016/007366
Other languages
English (en)
Korean (ko)
Inventor
황수진
서종열
오세진
Original Assignee
엘지전자 주식회사
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 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Priority to JP2017553098A priority Critical patent/JP2018517329A/ja
Priority to US15/554,125 priority patent/US10171849B1/en
Priority to KR1020177023471A priority patent/KR102023018B1/ko
Publication of WO2017007258A1 publication Critical patent/WO2017007258A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • 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
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H04L47/62—Queue scheduling characterised by scheduling criteria
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/806—Broadcast or multicast traffic
    • 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/70—Media network packetisation
    • 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/04—Protocols for data compression, e.g. ROHC
    • 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
    • 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/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]

Definitions

  • the present invention relates to a broadcast signal transmission apparatus, a broadcast signal reception apparatus, and a broadcast signal transmission and reception method.
  • the digital broadcast signal may include a larger amount of video / audio data than the analog broadcast signal, and may further include various types of additional data as well as the video / audio data.
  • the digital broadcasting system may provide ultra high definition (UHD) images, multichannel audio, and various additional services.
  • UHD ultra high definition
  • data transmission efficiency for a large amount of data transmission, robustness of a transmission / reception network, and network flexibility in consideration of a mobile receiving device should be improved.
  • the present invention provides a system and an associated signaling scheme that can effectively support next-generation broadcast services in an environment that supports next-generation hybrid broadcasting using terrestrial broadcasting networks and Internet networks. Suggest.
  • the present invention can effectively support the next generation broadcast service in an environment supporting the next generation hybrid broadcast using the terrestrial broadcast network and the Internet network.
  • the present invention can support a method for providing detailed signaling for service components included in a broadcast service.
  • the present invention can support a method for efficiently providing various information such as 3D, caption, WCG, HDR, etc. in a method of delivering a broadcast service.
  • FIG. 1 is a diagram illustrating a protocol stack according to an embodiment of the present invention.
  • FIG. 2 is a diagram illustrating a service discovery process according to an embodiment of the present invention.
  • LLS low level signaling
  • SLT service list table
  • FIG. 4 illustrates a USBD and an S-TSID delivered to ROUTE according to an embodiment of the present invention.
  • FIG. 5 is a diagram illustrating a USBD delivered to MMT according to an embodiment of the present invention.
  • FIG. 6 illustrates a link layer operation according to an embodiment of the present invention.
  • FIG. 7 illustrates a link mapping table (LMT) according to an embodiment of the present invention.
  • FIG. 8 shows a structure of a broadcast signal transmission apparatus for a next generation broadcast service according to an embodiment of the present invention.
  • FIG 9 illustrates a writing operation of a time interleaver according to an embodiment of the present invention.
  • FIG. 10 is a block diagram of an interleaving address generator composed of a main-PRBS generator and a sub-PRBS generator according to each FFT mode included in a frequency interleaver according to an embodiment of the present invention.
  • FIG. 11 illustrates a hybrid broadcast reception device according to an embodiment of the present invention.
  • FIG. 12 is a diagram illustrating the overall operation of the DASH-based adaptive streaming model according to an embodiment of the present invention.
  • FIG. 13 is a block diagram of a receiver according to an embodiment of the present invention.
  • FIG. 14 is a diagram showing the structure of a media file according to an embodiment of the present invention.
  • 15 is a diagram illustrating a bootstrapping process through SLT according to an embodiment of the present invention.
  • 16 is a diagram illustrating a signaling flow based on an MMT protocol according to an embodiment of the present invention.
  • FIG. 17 illustrates a capability descriptor according to an embodiment of the present invention.
  • FIG. 18 is a diagram illustrating a capability code according to an embodiment of the present invention.
  • USBD 19 illustrates a portion of a USBD according to another embodiment of the present invention.
  • FIG. 20 illustrates a part of an MP table according to an embodiment of the present invention.
  • FIG 21 illustrates an asset group descriptor according to an embodiment of the present invention.
  • FIG. 22 illustrates accessibility information according to an embodiment of the present invention.
  • FIG. 23 illustrates ComponentInfo elements in a USBD according to an embodiment of the present invention.
  • FIG. 24 illustrates component property information according to an embodiment of the present invention.
  • FIG. 25 is a diagram illustrating component property information according to an embodiment of the present invention.
  • FIG. 26 is a diagram illustrating utilization of component property information according to an embodiment of the present invention.
  • FIG. 27 is a diagram illustrating HEVC video component description information according to an embodiment of the present invention.
  • FIG. 29 is a diagram illustrating caption information according to an embodiment of the present invention.
  • FIG. 30 is a diagram illustrating HDR information according to an embodiment of the present invention.
  • FIG. 31 is a diagram illustrating WCG information according to an embodiment of the present invention.
  • 33 illustrates signaling information related to 3D service and multiview service according to an embodiment of the present invention.
  • FIG. 34 is a diagram illustrating a media engine operation of a receiver based on HDR information processing capability according to an embodiment of the present invention.
  • 35 is a diagram illustrating a media engine operation of a receiver based on WCG information processing capability according to an embodiment of the present invention.
  • FIG. 36 illustrates a media engine operation of a receiver based on HFR information processing capability according to an embodiment of the present invention.
  • FIG. 37 illustrates a media engine operation of a receiver based on pulldown recovery information processing capability according to an embodiment of the present invention.
  • 39 may show metadata about a bar according to an embodiment of the present invention.
  • 40 may show metadata for an original source format according to an embodiment of the present invention.
  • 41 is a view illustrating a method of generating a letter box using bar data according to an embodiment of the present invention.
  • FIG. 42 is a view illustrating a method of generating a letter box using bar data according to another embodiment of the present invention.
  • FIG. 43 illustrates a method of generating a pillar box using bar data according to an embodiment of the present invention.
  • 44 is a view illustrating a method of generating a pillar box using bar data according to another embodiment of the present invention.
  • 45 is a diagram illustrating a method for transmitting a broadcast signal according to an embodiment of the present invention.
  • 46 illustrates an apparatus for transmitting a broadcast signal according to an embodiment of the present invention.
  • the present invention provides an apparatus and method for transmitting and receiving broadcast signals for next generation broadcast services.
  • the next generation broadcast service includes a terrestrial broadcast service, a mobile broadcast service, a UHDTV service, and the like.
  • a broadcast signal for a next generation broadcast service may be processed through a non-multiple input multiple output (MIMO) or MIMO scheme.
  • the non-MIMO scheme according to an embodiment of the present invention may include a multiple input single output (MISO) scheme, a single input single output (SISO) scheme, and the like.
  • MISO multiple input single output
  • SISO single input single output
  • the present invention proposes a physical profile (or system) that is optimized to minimize receiver complexity while achieving the performance required for a particular application.
  • FIG. 1 is a diagram illustrating a protocol stack according to an embodiment of the present invention.
  • the service may be delivered to the receiver through a plurality of layers.
  • the transmitting side can generate service data.
  • the delivery layer on the transmitting side performs processing for transmission to the service data, and the physical layer encodes it as a broadcast signal and transmits it through a broadcasting network or broadband.
  • the service data may be generated in a format according to ISO BMFF (base media file format).
  • the ISO BMFF media file may be used in broadcast network / broadband delivery, media encapsulation and / or synchronization format.
  • the service data is all data related to the service, and may include a concept including service components constituting the linear service, signaling information thereof, non real time (NRT) data, and other files.
  • the delivery layer will be described.
  • the delivery layer may provide a transmission function for service data.
  • the service data may be delivered through a broadcast network and / or broadband.
  • the first method may be to process service data into Media Processing Units (MPUs) based on MPEG Media Transport (MMT) and transmit the data using MMM protocol (MMTP).
  • MPUs Media Processing Units
  • MMT MPEG Media Transport
  • MMTP MMM protocol
  • the service data delivered through the MMTP may include service components for linear service and / or service signaling information thereof.
  • the second method may be to process service data into DASH segments based on MPEG DASH and transmit it using Real Time Object Delivery over Unidirectional Transport (ROUTE).
  • the service data delivered through the ROUTE protocol may include service components for the linear service, service signaling information and / or NRT data thereof. That is, non-timed data such as NRT data and files may be delivered through ROUTE.
  • Data processed according to the MMTP or ROUTE protocol may be processed into IP packets via the UDP / IP layer.
  • a service list table (SLT) may also be transmitted through a broadcasting network through a UDP / IP layer.
  • the SLT may be included in the LLS (Low Level Signaling) table and transmitted. The SLT and the LLS table will be described later.
  • IP packets may be treated as link layer packets at the link layer.
  • the link layer may encapsulate data of various formats delivered from an upper layer into a link layer packet and then deliver the data to the physical layer. The link layer will be described later.
  • At least one or more service elements may be delivered via a broadband path.
  • the data transmitted through the broadband may include service components in a DASH format, service signaling information and / or NRT data thereof. This data can be processed via HTTP / TCP / IP, passed through the link layer for broadband transmission, and delivered to the physical layer for broadband transmission.
  • the physical layer may process data received from a delivery layer (upper layer and / or link layer) and transmit the data through a broadcast network or a broadband. Details of the physical layer will be described later.
  • the service may be a collection of service components that are shown to the user as a whole, the components may be of different media types, the service may be continuous or intermittent, the service may be real time or non-real time, and the real time service may be a sequence of TV programs. It can be configured as.
  • the service may be a linear audio / video or audio only service that may have app-based enhancements.
  • the service may be an app-based service whose reproduction / configuration is controlled by the downloaded application.
  • the service may be an ESG service that provides an electronic service guide (ESG).
  • ESG electronic service guide
  • EA Emergency Alert
  • the service component may be delivered by (1) one or more ROUTE sessions or (2) one or more MMTP sessions.
  • the service component When a linear service with app-based enhancement is delivered through a broadcast network, the service component may be delivered by (1) one or more ROUTE sessions and (2) zero or more MMTP sessions.
  • data used for app-based enhancement may be delivered through a ROUTE session in the form of NRT data or other files.
  • linear service components (streaming media components) of one service may not be allowed to be delivered using both protocols simultaneously.
  • the service component may be delivered by one or more ROUTE sessions.
  • the service data used for the app-based service may be delivered through a ROUTE session in the form of NRT data or other files.
  • some service components or some NRT data, files, etc. of these services may be delivered via broadband (hybrid service delivery).
  • the linear service components of one service may be delivered through the MMT protocol.
  • the linear service components of one service may be delivered via a ROUTE protocol.
  • the linear service component and NRT data (NRT service component) of one service may be delivered through the ROUTE protocol.
  • linear service components of one service may be delivered through the MMT protocol, and NRT data (NRT service components) may be delivered through the ROUTE protocol.
  • some service component or some NRT data of a service may be delivered over broadband.
  • the data related to the app-based service or the app-based enhancement may be transmitted through a broadcast network according to ROUTE or through broadband in the form of NRT data.
  • NRT data may also be referred to as locally cashed data.
  • Each ROUTE session includes one or more LCT sessions that deliver, in whole or in part, the content components that make up the service.
  • an LCT session may deliver an individual component of a user service, such as an audio, video, or closed caption stream.
  • Streaming media is formatted into a DASH segment.
  • Each MMTP session includes one or more MMTP packet flows carrying an MMT signaling message or all or some content components.
  • the MMTP packet flow may carry a component formatted with an MMT signaling message or an MPU.
  • an LCT session For delivery of NRT user service or system metadata, an LCT session carries a file based content item.
  • These content files may consist of continuous (timed) or discrete (non-timed) media components of an NRT service, or metadata such as service signaling or ESG fragments.
  • Delivery of system metadata, such as service signaling or ESG fragments, can also be accomplished through the signaling message mode of the MMTP.
  • the tuner can scan frequencies and detect broadcast signals at specific frequencies.
  • the receiver can extract the SLT and send it to the module that processes it.
  • the SLT parser can parse the SLT, obtain data, and store it in the channel map.
  • the receiver may acquire bootstrap information of the SLT and deliver it to the ROUTE or MMT client. This allows the receiver to obtain and store the SLS. USBD or the like can be obtained, which can be parsed by the signaling parser.
  • FIG. 2 is a diagram illustrating a service discovery process according to an embodiment of the present invention.
  • the broadcast stream delivered by the broadcast signal frame of the physical layer may carry LLS (Low Level Signaling).
  • LLS data may be carried through the payload of an IP packet delivered to a well known IP address / port. This LLS may contain an SLT depending on its type.
  • LLS data may be formatted in the form of an LLS table. The first byte of every UDP / IP packet carrying LLS data may be the beginning of the LLS table. Unlike the illustrated embodiment, the IP stream carrying LLS data may be delivered to the same PLP along with other service data.
  • the SLT enables the receiver to generate a service list through a fast channel scan and provides access information for locating the SLS.
  • the SLT includes bootstrap information, which enables the receiver to obtain Service Layer Signaling (SLS) for each service.
  • SLS Service Layer Signaling
  • the bootstrap information may include destination IP address and destination port information of the ROUTE session including the LCT channel carrying the SLS and the LCT channel.
  • the bootstrap information may include a destination IP address and destination port information of the MMTP session carrying the SLS.
  • the SLS of service # 1 described by the SLT is delivered via ROUTE, and the SLT includes bootstrap information (sIP1, dIP1, dPort1) for the ROUTE session including the LCT channel to which the SLS is delivered. can do.
  • SLS of service # 2 described by the SLT is delivered through MMT, and the SLT may include bootstrap information (sIP2, dIP2, and dPort2) for an MMTP session including an MMTP packet flow through which the SLS is delivered.
  • the SLS is signaling information describing characteristics of a corresponding service and may include information for acquiring a corresponding service and a service component of the corresponding service, or may include receiver capability information for reproducing the corresponding service significantly. Having separate service signaling for each service allows the receiver to obtain the appropriate SLS for the desired service without having to parse the entire SLS delivered in the broadcast stream.
  • the SLS When the SLS is delivered through the ROUTE protocol, the SLS may be delivered through a dedicated LCT channel of a ROUTE session indicated by the SLT.
  • the SLS may include a user service bundle description (USBD / USD), a service-based transport session instance description (S-TSID), and / or a media presentation description (MPD).
  • USBD / USD user service bundle description
  • S-TSID service-based transport session instance description
  • MPD media presentation description
  • USBD to USD is one of the SLS fragments and may serve as a signaling hub for describing specific technical information of a service.
  • the USBD may include service identification information, device capability information, and the like.
  • the USBD may include reference information (URI reference) to other SLS fragments (S-TSID, MPD, etc.). That is, USBD / USD can refer to S-TSID and MPD respectively.
  • the USBD may further include metadata information that enables the receiver to determine the transmission mode (broadcast network / broadband). Details of the USBD / USD will be described later.
  • the S-TSID is one of the SLS fragments, and may provide overall session description information for a transport session carrying a service component of a corresponding service.
  • the S-TSID may provide transport session description information for the ROUTE session to which the service component of the corresponding service is delivered and / or the LCT channel of the ROUTE sessions.
  • the S-TSID may provide component acquisition information of service components related to one service.
  • the S-TSID may provide a mapping between the DASH Representation of the MPD and the tsi of the corresponding service component.
  • the component acquisition information of the S-TSID may be provided in the form of tsi, an identifier of an associated DASH representation, and may or may not include a PLP ID according to an embodiment.
  • the component acquisition information enables the receiver to collect audio / video components of a service and to buffer, decode, and the like of DASH media segments.
  • the S-TSID may be referenced by the USBD as described above. Details of the S-TSID will be described later.
  • the MPD is one of the SLS fragments and may provide a description of the DASH media presentation of the service.
  • the MPD may provide a resource identifier for the media segments and may provide contextual information within the media presentation for the identified resources.
  • the MPD may describe the DASH representation (service component) delivered through the broadcast network, and may also describe additional DASH representations delivered through the broadband (hybrid delivery).
  • the MPD may be referenced by the USBD as described above.
  • the SLS When the SLS is delivered through the MMT protocol, the SLS may be delivered through a dedicated MMTP packet flow of an MMTP session indicated by the SLT.
  • packet_id of MMTP packets carrying SLS may have a value of 00.
  • the SLS may include a USBD / USD and / or MMT Package (MP) table.
  • USBD is one of the SLS fragments, and may describe specific technical information of a service like that in ROUTE.
  • the USBD here may also include reference information (URI reference) to other SLS fragments.
  • the USBD of the MMT may refer to the MP table of the MMT signaling.
  • the USBD of the MMT may also include reference information on the S-TSID and / or the MPD.
  • the S-TSID may be for NRT data transmitted through the ROUTE protocol. This is because NRT data can be delivered through the ROUTE protocol even when the linear service component is delivered through the MMT protocol.
  • MPD may be for a service component delivered over broadband in hybrid service delivery. Details of the USBD of the MMT will be described later.
  • the MP table is a signaling message of the MMT for MPU components and may provide overall session description information for an MMTP session carrying a service component of a corresponding service.
  • the MP table may also contain descriptions for assets delivered via this MMTP session.
  • the MP table is streaming signaling information for MPU components, and may provide a list of assets corresponding to one service and location information (component acquisition information) of these components. Specific contents of the MP table may be in a form defined in MMT or a form in which modifications are made.
  • Asset is a multimedia data entity, which may mean a data entity associated with one unique ID and used to generate one multimedia presentation. Asset may correspond to a service component constituting a service.
  • the MP table may be used to access a streaming service component (MPU) corresponding to a desired service.
  • the MP table may be referenced by the USBD as described above.
  • MMT signaling messages may be defined. Such MMT signaling messages may describe additional information related to the MMTP session or service.
  • ROUTE sessions are identified by source IP address, destination IP address, and destination port number.
  • the LCT session is identified by a transport session identifier (TSI) that is unique within the scope of the parent ROUTE session.
  • MMTP sessions are identified by destination IP address and destination port number.
  • the MMTP packet flow is identified by a unique packet_id within the scope of the parent MMTP session.
  • the S-TSID, the USBD / USD, the MPD, or the LCT session carrying them may be called a service signaling channel.
  • the S-TSID, the USBD / USD, the MPD, or the LCT session carrying them may be called a service signaling channel.
  • the S-TSID, the USBD / USD, the MPD, or the LCT session carrying them may be called a service signaling channel.
  • the MMT signaling messages or packet flow carrying them may be called a service signaling channel.
  • one ROUTE or MMTP session may be delivered through a plurality of PLPs. That is, one service may be delivered through one or more PLPs. Unlike shown, components constituting one service may be delivered through different ROUTE sessions. In addition, according to an embodiment, components constituting one service may be delivered through different MMTP sessions. According to an embodiment, components constituting one service may be delivered divided into a ROUTE session and an MMTP session. Although not shown, a component constituting one service may be delivered through a broadband (hybrid delivery).
  • LLS low level signaling
  • SLT service list table
  • An embodiment t3010 of the illustrated LLS table may include information according to an LLS_table_id field, a provider_id field, an LLS_table_version field, and / or an LLS_table_id field.
  • the LLS_table_id field may identify a type of the corresponding LLS table, and the provider_id field may identify service providers related to services signaled by the corresponding LLS table.
  • the service provider is a broadcaster using all or part of the broadcast stream, and the provider_id field may identify one of a plurality of broadcasters using the broadcast stream.
  • the LLS_table_version field may provide version information of a corresponding LLS table.
  • the corresponding LLS table includes the above-described SLT, a rating region table (RRT) including information related to a content advisory rating, a SystemTime information providing information related to system time, and an emergency alert. It may include one of the CAP (Common Alert Protocol) message that provides information related to. According to an embodiment, other information other than these may be included in the LLS table.
  • RRT rating region table
  • CAP Common Alert Protocol
  • One embodiment t3020 of the illustrated SLT may include an @bsid attribute, an @sltCapabilities attribute, a sltInetUrl element, and / or a Service element.
  • Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
  • the @bsid attribute may be an identifier of a broadcast stream.
  • the @sltCapabilities attribute can provide the capability information required to decode and significantly reproduce all services described by the SLT.
  • the sltInetUrl element may provide base URL information used to obtain ESG or service signaling information for services of the corresponding SLT through broadband.
  • the sltInetUrl element may further include an @urlType attribute, which may indicate the type of data that can be obtained through the URL.
  • the service element may be an element including information on services described by the corresponding SLT, and a service element may exist for each service.
  • the Service element contains the @serviceId property, the @sltSvcSeqNum property, the @protected property, the @majorChannelNo property, the @minorChannelNo property, the @serviceCategory property, the @shortServiceName property, the @hidden property, the @broadbandAccessRequired property, the @svcCapabilities property, the BroadcastSvcSignaling element, and / or the svcInetUrl element. It may include.
  • the @serviceId attribute may be an identifier of a corresponding service, and the @sltSvcSeqNum attribute may indicate a sequence number of SLT information for the corresponding service.
  • the @protected attribute may indicate whether at least one service component necessary for meaningful playback of the corresponding service is protected.
  • the @majorChannelNo and @minorChannelNo attributes may indicate the major channel number and the minor channel number of the corresponding service, respectively.
  • the @serviceCategory attribute can indicate the category of the corresponding service.
  • the service category may include a linear A / V service, a linear audio service, an app-based service, an ESG service, and an EAS service.
  • the @shortServiceName attribute may provide a short name of the corresponding service.
  • the @hidden attribute can indicate whether the service is for testing or proprietary use.
  • the @broadbandAccessRequired attribute may indicate whether broadband access is required for meaningful playback of the corresponding service.
  • the @svcCapabilities attribute can provide the capability information necessary for decoding and meaningful reproduction of the corresponding service.
  • the BroadcastSvcSignaling element may provide information related to broadcast signaling of a corresponding service. This element may provide information such as a location, a protocol, and an address with respect to signaling through a broadcasting network of a corresponding service. Details will be described later.
  • the svcInetUrl element may provide URL information for accessing signaling information for a corresponding service through broadband.
  • the sltInetUrl element may further include an @urlType attribute, which may indicate the type of data that can be obtained through the URL.
  • the aforementioned BroadcastSvcSignaling element may include an @slsProtocol attribute, an @slsMajorProtocolVersion attribute, an @slsMinorProtocolVersion attribute, an @slsPlpId attribute, an @slsDestinationIpAddress attribute, an @slsDestinationUdpPort attribute, and / or an @slsSourceIpAddress attribute.
  • the @slsProtocol attribute can indicate the protocol used to deliver the SLS of the service (ROUTE, MMT, etc.).
  • the @slsMajorProtocolVersion attribute and @slsMinorProtocolVersion attribute may indicate the major version number and the minor version number of the protocol used to deliver the SLS of the corresponding service, respectively.
  • the @slsPlpId attribute may provide a PLP identifier for identifying a PLP that delivers the SLS of the corresponding service.
  • this field may be omitted, and the PLP information to which the SLS is delivered may be identified by combining information in the LMT to be described later and bootstrap information of the SLT.
  • the @slsDestinationIpAddress attribute, @slsDestinationUdpPort attribute, and @slsSourceIpAddress attribute may indicate the destination IP address, the destination UDP port, and the source IP address of the transport packet carrying the SLS of the corresponding service, respectively. They can identify the transport session (ROUTE session or MMTP session) to which the SLS is delivered. These may be included in the bootstrap information.
  • FIG. 4 illustrates a USBD and an S-TSID delivered to ROUTE according to an embodiment of the present invention.
  • One embodiment t4010 of the illustrated USBD may have a bundleDescription root element.
  • the bundleDescription root element may have a userServiceDescription element.
  • the userServiceDescription element may be an instance of one service.
  • the userServiceDescription element may include an @globalServiceID attribute, an @serviceId attribute, an @serviceStatus attribute, an @fullMPDUri attribute, an @sTSIDUri attribute, a name element, a serviceLanguage element, a capabilityCode element, and / or a deliveryMethod element.
  • Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
  • the @globalServiceID attribute is a globally unique identifier of the service and can be used to link with ESG data (Service @ globalServiceID).
  • the @serviceId attribute is a reference corresponding to the corresponding service entry of the SLT and may be the same as service ID information of the SLT.
  • the @serviceStatus attribute may indicate the status of the corresponding service. This field may indicate whether the corresponding service is active or inactive.
  • the @fullMPDUri attribute can refer to the MPD fragment of the service. As described above, the MPD may provide a reproduction description for a service component delivered through a broadcast network or a broadband.
  • the @sTSIDUri attribute may refer to the S-TSID fragment of the service.
  • the S-TSID may provide parameters related to access to the transport session carrying the service as described above.
  • the name element may provide the name of the service.
  • This element may further include an @lang attribute, which may indicate the language of the name provided by the name element.
  • the serviceLanguage element may indicate the available languages of the service. That is, this element may list the languages in which the service can be provided.
  • the capabilityCode element may indicate capability or capability group information of the receiver side necessary for significantly playing a corresponding service. This information may be compatible with the capability information format provided by the service announcement.
  • the deliveryMethod element may provide delivery related information with respect to contents accessed through a broadcasting network or a broadband of a corresponding service.
  • the deliveryMethod element may include a broadcastAppService element and / or a unicastAppService element. Each of these elements may have a basePattern element as its child element.
  • the broadcastAppService element may include transmission related information on the DASH presentation delivered through the broadcast network.
  • These DASH representations may include media components across all periods of the service media presentation.
  • the basePattern element of this element may represent a character pattern used by the receiver to match the segment URL. This can be used by the DASH client to request segments of the representation. Matching may imply that the media segment is delivered over the broadcast network.
  • the unicastAppService element may include transmission related information on the DASH representation delivered through broadband. These DASH representations may include media components across all periods of the service media presentation.
  • the basePattern element of this element may represent a character pattern used by the receiver to match the segment URL. This can be used by the DASH client to request segments of the representation. Matching may imply that the media segment is delivered over broadband.
  • An embodiment t4020 of the illustrated S-TSID may have an S-TSID root element.
  • the S-TSID root element may include an @serviceId attribute and / or an RS element.
  • Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
  • the @serviceId attribute is an identifier of a corresponding service and may refer to a corresponding service of USBD / USD.
  • the RS element may describe information on ROUTE sessions through which service components of a corresponding service are delivered. Depending on the number of such ROUTE sessions, there may be a plurality of these elements.
  • the RS element may further include an @bsid attribute, an @sIpAddr attribute, an @dIpAddr attribute, an @dport attribute, an @PLPID attribute, and / or an LS element.
  • the @bsid attribute may be an identifier of a broadcast stream through which service components of a corresponding service are delivered. If this field is omitted, the default broadcast stream may be a broadcast stream that includes a PLP that carries the SLS of the service. The value of this field may be the same value as the @bsid attribute of SLT.
  • the @sIpAddr attribute, the @dIpAddr attribute, and the @dport attribute may indicate a source IP address, a destination IP address, and a destination UDP port of the corresponding ROUTE session, respectively. If these fields are omitted, the default values may be the source IP address, destination IP address, and destination UDP port values of the current, ROUTE session carrying that SLS, that is, carrying that S-TSID. For other ROUTE sessions that carry service components of the service but not the current ROUTE session, these fields may not be omitted.
  • the @PLPID attribute may indicate PLP ID information of a corresponding ROUTE session. If this field is omitted, the default value may be the PLP ID value of the current PLP to which the corresponding S-TSID is being delivered. According to an embodiment, this field is omitted, and the PLP ID information of the corresponding ROUTE session may be confirmed by combining information in the LMT to be described later and IP address / UDP port information of the RS element.
  • the LS element may describe information on LCT channels through which service components of a corresponding service are delivered. Depending on the number of such LCT channels, there may be a plurality of these elements.
  • the LS element may include an @tsi attribute, an @PLPID attribute, an @bw attribute, an @startTime attribute, an @endTime attribute, an SrcFlow element, and / or a RepairFlow element.
  • the @tsi attribute may represent tsi information of a corresponding LCT channel. Through this, LCT channels through which a service component of a corresponding service is delivered may be identified.
  • the @PLPID attribute may represent PLP ID information of a corresponding LCT channel. In some embodiments, this field may be omitted.
  • the @bw attribute may indicate the maximum bandwidth of the corresponding LCT channel.
  • the @startTime attribute may indicate the start time of the LCT session, and the @endTime attribute may indicate the end time of the LCT channel.
  • the SrcFlow element may describe the source flow of ROUTE.
  • the source protocol of ROUTE is used to transmit the delivery object, and can establish at least one source flow in one ROUTE session. These source flows can deliver related objects as an object flow.
  • the RepairFlow element may describe the repair flow of ROUTE. Delivery objects delivered according to the source protocol may be protected according to Forward Error Correction (FEC).
  • FEC Forward Error Correction
  • the repair protocol may define a FEC framework that enables such FEC protection.
  • FIG. 5 is a diagram illustrating a USBD delivered to MMT according to an embodiment of the present invention.
  • One embodiment of the illustrated USBD may have a bundleDescription root element.
  • the bundleDescription root element may have a userServiceDescription element.
  • the userServiceDescription element may be an instance of one service.
  • the userServiceDescription element may include an @globalServiceID attribute, an @serviceId attribute, a Name element, a serviceLanguage element, a content advisoryRating element, a Channel element, an mpuComponent element, a routeComponent element, a broadbandComponent element, and / or a ComponentInfo element.
  • Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
  • the @globalServiceID attribute, the @serviceId attribute, the Name element and / or the serviceLanguage element may be the same as the corresponding fields of the USBD delivered to the above-described ROUTE.
  • the contentAdvisoryRating element may indicate the content advisory rating of the corresponding service. This information may be compatible with the content advisory rating information format provided by the service announcement.
  • the channel element may include information related to the corresponding service. The detail of this element is mentioned later.
  • the mpuComponent element may provide a description for service components delivered as an MPU of a corresponding service.
  • This element may further include an @mmtPackageId attribute and / or an @nextMmtPackageId attribute.
  • the @mmtPackageId attribute may refer to an MMT package of service components delivered as an MPU of a corresponding service.
  • the @nextMmtPackageId attribute may refer to an MMT package to be used next to the MMT package referenced by the @mmtPackageId attribute in time.
  • the MP table can be referenced through the information of this element.
  • the routeComponent element may include a description of service components of the corresponding service delivered to ROUTE. Even if the linear service components are delivered in the MMT protocol, the NRT data may be delivered according to the ROUTE protocol as described above. This element may describe information about such NRT data. The detail of this element is mentioned later.
  • the broadbandComponent element may include a description of service components of the corresponding service delivered over broadband.
  • some service components or other files of a service may be delivered over broadband. This element may describe information about these data.
  • This element may further include the @fullMPDUri attribute. This attribute may refer to an MPD that describes service components delivered over broadband.
  • the element when the broadcast signal is weakened due to driving in a tunnel or the like, the element may be needed to support handoff between the broadcast network and the broadband band. When the broadcast signal is weakened, while acquiring the service component through broadband, and when the broadcast signal is stronger, the service continuity may be guaranteed by acquiring the service component through the broadcast network.
  • the ComponentInfo element may include information on service components of a corresponding service. Depending on the number of service components of the service, there may be a plurality of these elements. This element may describe information such as the type, role, name, identifier, and protection of each service component. Detailed information on this element will be described later.
  • the aforementioned channel element may further include an @serviceGenre attribute, an @serviceIcon attribute, and / or a ServiceDescription element.
  • the @serviceGenre attribute may indicate the genre of the corresponding service
  • the @serviceIcon attribute may include URL information of an icon representing the corresponding service.
  • the ServiceDescription element provides a service description of the service, which may further include an @serviceDescrText attribute and / or an @serviceDescrLang attribute. Each of these attributes may indicate the text of the service description and the language used for that text.
  • the aforementioned routeComponent element may further include an @sTSIDUri attribute, an @sTSIDDestinationIpAddress attribute, an @sTSIDDestinationUdpPort attribute, an @sTSIDSourceIpAddress attribute, an @sTSIDMajorProtocolVersion attribute, and / or an @sTSIDMinorProtocolVersion attribute.
  • the @sTSIDUri attribute may refer to an S-TSID fragment. This field may be the same as the corresponding field of USBD delivered to ROUTE described above. This S-TSID may provide access related information for service components delivered in ROUTE. This S-TSID may exist for NRT data delivered according to the ROUTE protocol in the situation where linear service components are delivered according to the MMT protocol.
  • the @sTSIDDestinationIpAddress attribute, the @sTSIDDestinationUdpPort attribute, and the @sTSIDSourceIpAddress attribute may indicate a destination IP address, a destination UDP port, and a source IP address of a transport packet carrying the aforementioned S-TSID, respectively. That is, these fields may identify a transport session (MMTP session or ROUTE session) carrying the aforementioned S-TSID.
  • the @sTSIDMajorProtocolVersion attribute and the @sTSIDMinorProtocolVersion attribute may indicate a major version number and a minor version number of the transport protocol used to deliver the aforementioned S-TSID.
  • ComponentInfo element may further include an @componentType attribute, an @componentRole attribute, an @componentProtectedFlag attribute, an @componentId attribute, and / or an @componentName attribute.
  • the @componentType attribute may indicate the type of the corresponding component. For example, this property may indicate whether the corresponding component is an audio, video, or closed caption component.
  • the @componentRole attribute can indicate the role (role) of the corresponding component. For example, this property can indicate whether the main audio, music, commentary, etc., if the corresponding component is an audio component. If the corresponding component is a video component, it may indicate whether it is primary video. If the corresponding component is a closed caption component, it may indicate whether it is a normal caption or an easy reader type.
  • the @componentProtectedFlag attribute may indicate whether a corresponding service component is protected, for example, encrypted.
  • the @componentId attribute may represent an identifier of a corresponding service component.
  • the value of this attribute may be a value such as asset_id (asset ID) of the MP table corresponding to this service component.
  • the @componentName attribute may represent the name of the corresponding service component.
  • FIG. 6 illustrates a link layer operation according to an embodiment of the present invention.
  • the link layer may be a layer between the physical layer and the network layer.
  • the transmitter may transmit data from the network layer to the physical layer
  • the receiver may transmit data from the physical layer to the network layer (t6010).
  • the purpose of the link layer may be to compress all input packet types into one format for processing by the physical layer, to ensure flexibility and future scalability for input packet types not yet defined. have.
  • the link layer may provide an option of compressing unnecessary information in the header of the input packet, so that the input data may be efficiently transmitted. Operations such as overhead reduction and encapsulation of the link layer may be referred to as a link layer protocol, and a packet generated using the corresponding protocol may be referred to as a link layer packet.
  • the link layer may perform functions such as packet encapsulation, overhead reduction, and / or signaling transmission.
  • the link layer ALP may perform an overhead reduction process on input packets and then encapsulate them into link layer packets.
  • the link layer may encapsulate the link layer packet without performing an overhead reduction process.
  • the use of the link layer protocol can greatly reduce the overhead for data transmission on the physical layer, and the link layer protocol according to the present invention can provide IP overhead reduction and / or MPEG-2 TS overhead reduction. have.
  • the link layer may sequentially perform IP header compression, adaptation, and / or encapsulation. In some embodiments, some processes may be omitted.
  • the RoHC module performs IP packet header compression to reduce unnecessary overhead, and context information may be extracted and transmitted out of band through an adaptation process.
  • the IP header compression and adaptation process may be collectively called IP header compression.
  • IP packets may be encapsulated into link layer packets through an encapsulation process.
  • the link layer may sequentially perform an overhead reduction and / or encapsulation process for the TS packet. In some embodiments, some processes may be omitted.
  • the link layer may provide sync byte removal, null packet deletion and / or common header removal (compression).
  • Sync byte elimination can provide overhead reduction of 1 byte per TS packet. Null packet deletion can be performed in a manner that can be reinserted at the receiving end. In addition, common information between successive headers can be deleted (compressed) in a manner that can be recovered at the receiving side. Some of each overhead reduction process may be omitted. Thereafter, TS packets may be encapsulated into link layer packets through an encapsulation process.
  • the link layer packet structure for encapsulation of TS packets may be different from other types of packets.
  • IP header compression will be described.
  • the IP packet has a fixed header format, but some information required in a communication environment may be unnecessary in a broadcast environment.
  • the link layer protocol may provide a mechanism to reduce broadcast overhead by compressing the header of the IP packet.
  • IP header compression may include a header compressor / decompressor and / or adaptation module.
  • the IP header compressor (RoHC compressor) may reduce the size of each IP packet header based on the RoHC scheme.
  • the adaptation module may then extract the context information and generate signaling information from each packet stream.
  • the receiver may parse signaling information related to the packet stream and attach context information to the packet stream.
  • the RoHC decompressor can reconstruct the original IP packet by recovering the packet header.
  • IP header compression may mean only IP header compression by a header compressor, or may mean a concept in which the IP header compression and the adaptation process by the adaptation module are combined. The same is true for decompressing.
  • the adaptation function may generate link layer signaling using context information and / or configuration parameters.
  • the adaptation function may periodically send link layer signaling over each physical frame using previous configuration parameters and / or context information.
  • the context information is extracted from the compressed IP packets, and various methods may be used according to the adaptation mode.
  • Mode # 1 is a mode in which no operation is performed on the compressed packet stream, and may be a mode in which the adaptation module operates as a buffer.
  • Mode # 2 may be a mode for extracting context information (static chain) by detecting IR packets in the compressed packet stream. After extraction, the IR packet is converted into an IR-DYN packet, and the IR-DYN packet can be transmitted in the same order in the packet stream by replacing the original IR packet.
  • context information static chain
  • Mode # 3 t6020 may be a mode for detecting IR and IR-DYN packets and extracting context information from the compressed packet stream.
  • Static chains and dynamic chains can be extracted from IR packets and dynamic chains can be extracted from IR-DYN packets.
  • the IR and IR-DYN packets can be converted into regular compressed packets.
  • the switched packets can be sent in the same order within the packet stream, replacing the original IR and IR-DYN packets.
  • the remaining packets after the context information is extracted may be encapsulated and transmitted according to the link layer packet structure for the compressed IP packet.
  • the context information may be transmitted by being encapsulated according to a link layer packet structure for signaling information as link layer signaling.
  • the extracted context information may be included in the RoHC-U Description Table (RTT) and transmitted separately from the RoHC packet flow.
  • the context information may be transmitted through a specific physical data path along with other signaling information.
  • a specific physical data path may mean one of general PLPs, a PLP to which LLS (Low Level Signaling) is delivered, a dedicated PLP, or an L1 signaling path. path).
  • the RDT may be signaling information including context information (static chain and / or dynamic chain) and / or information related to header compression.
  • the RDT may be transmitted whenever the context information changes.
  • the RDT may be transmitted in every physical frame. In order to transmit the RDT in every physical frame, a previous RDT may be re-use.
  • the receiver may first select PLP to acquire signaling information such as SLT, RDT, LMT, and the like. When the signaling information is obtained, the receiver may combine these to obtain a mapping between the service-IP information-context information-PLP. That is, the receiver can know which service is transmitted to which IP streams, which IP streams are delivered to which PLP, and can also obtain corresponding context information of the PLPs. The receiver can select and decode a PLP carrying a particular packet stream. The adaptation module can parse the context information and merge it with the compressed packets. This allows the packet stream to be recovered, which can be delivered to the RoHC decompressor. Decompression can then begin.
  • signaling information such as SLT, RDT, LMT, and the like.
  • the receiver may combine these to obtain a mapping between the service-IP information-context information-PLP. That is, the receiver can know which service is transmitted to which IP streams, which IP streams are delivered to which PLP, and can also obtain corresponding context information of the PLPs.
  • the receiver detects the IR packet and starts decompression from the first received IR packet according to the adaptation mode (mode 1), or detects the IR-DYN packet to perform decompression from the first received IR-DYN packet.
  • the link layer protocol may encapsulate all types of input packets, such as IP packets and TS packets, into link layer packets. This allows the physical layer to process only one packet format independently of the protocol type of the network layer (here, consider MPEG-2 TS packet as a kind of network layer packet). Each network layer packet or input packet is transformed into a payload of a generic link layer packet.
  • Segmentation may be utilized in the packet encapsulation process. If the network layer packet is too large to be processed by the physical layer, the network layer packet may be divided into two or more segments.
  • the link layer packet header may include fields for performing division at the transmitting side and recombination at the receiving side. Each segment may be encapsulated into a link layer packet in the same order as the original position.
  • Concatenation may also be utilized in the packet encapsulation process. If the network layer packet is small enough that the payload of the link layer packet includes several network layer packets, concatenation may be performed.
  • the link layer packet header may include fields for executing concatenation. In the case of concatenation, each input packet may be encapsulated into the payload of the link layer packet in the same order as the original input order.
  • the link layer packet may include a header and a payload, and the header may include a base header, an additional header, and / or an optional header.
  • the additional header may be added depending on the chaining or splitting, and the additional header may include necessary fields according to the situation.
  • an optional header may be further added to transmit additional information.
  • Each header structure may be predefined. As described above, when the input packet is a TS packet, a link layer header structure different from other packets may be used.
  • Link layer signaling may operate at a lower level than the IP layer.
  • the receiving side can acquire the link layer signaling faster than the IP level signaling such as LLS, SLT, SLS, and the like. Therefore, link layer signaling may be obtained before session establishment.
  • Link layer signaling may include internal link layer signaling and external link layer signaling.
  • Internal link layer signaling may be signaling information generated in the link layer.
  • the above-described RDT or LMT to be described later may correspond to this.
  • the external link layer signaling may be signaling information received from an external module, an external protocol, or an upper layer.
  • the link layer may encapsulate link layer signaling into a link layer packet and deliver it.
  • a link layer packet structure (header structure) for link layer signaling may be defined, and link layer signaling information may be encapsulated according to this structure.
  • FIG. 7 illustrates a link mapping table (LMT) according to an embodiment of the present invention.
  • the LMT may provide a list of higher layer sessions carried by the PLP.
  • the LMT may also provide additional information for processing link layer packets carrying higher layer sessions.
  • the higher layer session may be called multicast.
  • Information on which IP streams and which transport sessions are being transmitted through a specific PLP may be obtained through the LMT. Conversely, information on which PLP a specific transport session is delivered to may be obtained.
  • the LMT may be delivered to any PLP identified as carrying an LLS.
  • the PLP through which the LLS is delivered may be identified by the LLS flag of the L1 detail signaling information of the physical layer.
  • the LLS flag may be a flag field indicating whether LLS is delivered to the corresponding PLP for each PLP.
  • the L1 detail signaling information may correspond to PLS2 data to be described later.
  • the LMT may be delivered to the same PLP together with the LLS.
  • Each LMT may describe the mapping between PLPs and IP address / port as described above.
  • the LLS may include an SLT, where these IP addresses / ports described by the LMT are all IP addresses associated with any service described by the SLT forwarded to the same PLP as that LMT. It can be / ports.
  • the PLP identifier information in the above-described SLT, SLS, etc. may be utilized, so that information on which PLP the specific transmission session indicated by the SLT, SLS is transmitted may be confirmed.
  • the PLP identifier information in the above-described SLT, SLS, etc. may be omitted, and the PLP information for the specific transport session indicated by the SLT, SLS may be confirmed by referring to the information in the LMT.
  • the receiver may identify the PLP to know by combining LMT and other IP level signaling information.
  • PLP information in SLT, SLS, and the like is not omitted, and may remain in the SLT, SLS, and the like.
  • the LMT according to the illustrated embodiment may include a signaling_type field, a PLP_ID field, a num_session field, and / or information about respective sessions.
  • a PLP loop may be added to the LMT according to an embodiment, so that information on a plurality of PLPs may be described.
  • the LMT may describe PLPs for all IP addresses / ports related to all services described by the SLTs delivered together, in a PLP loop.
  • the signaling_type field may indicate the type of signaling information carried by the corresponding table.
  • the value of the signaling_type field for the LMT may be set to 0x01.
  • the signaling_type field may be omitted.
  • the PLP_ID field may identify a target PLP to be described. When a PLP loop is used, each PLP_ID field may identify each target PLP. From the PLP_ID field may be included in the PLP loop.
  • the PLP_ID field mentioned below is an identifier for one PLP in a PLP loop, and the fields described below may be fields for the corresponding PLP.
  • the num_session field may indicate the number of upper layer sessions delivered to the PLP identified by the corresponding PLP_ID field. According to the number indicated by the num_session field, information about each session may be included. This information may include an src_IP_add field, a dst_IP_add field, a src_UDP_port field, a dst_UDP_port field, a SID_flag field, a compressed_flag field, a SID field, and / or a context_id field.
  • the src_IP_add field, dst_IP_add field, src_UDP_port field, and dst_UDP_port field are the source IP address, destination IP address, source UDP port, destination UDP port for the transport session among the upper layer sessions forwarded to the PLP identified by the corresponding PLP_ID field. It can indicate a port.
  • the SID_flag field may indicate whether a link layer packet carrying a corresponding transport session has an SID field in its optional header.
  • a link layer packet carrying an upper layer session may have an SID field in its optional header, and the SID field value may be the same as an SID field in an LMT to be described later.
  • the compressed_flag field may indicate whether header compression has been applied to data of a link layer packet carrying a corresponding transport session.
  • the existence of the context_id field to be described later may be determined according to the value of this field.
  • the SID field may indicate a sub stream ID (SID) for link layer packets carrying a corresponding transport session.
  • SID sub stream ID
  • These link layer packets may include an SID having the same value as this SID field in the optional header.
  • the context_id field may provide a reference to a context id (CID) in the RDT.
  • the CID information of the RDT may indicate the context ID for the corresponding compressed IP packet stream.
  • the RDT may provide context information for the compressed IP packet stream. RDT and LMT may be associated with this field.
  • each field, element, or attribute may be omitted or replaced by another field, and additional fields, elements, or attributes may be added according to an embodiment. .
  • service components of one service may be delivered through a plurality of ROUTE sessions.
  • the SLS may be obtained through the bootstrap information of the SLT.
  • the SLS's USBD allows the S-TSID and MPD to be referenced.
  • the S-TSID may describe transport session description information for other ROUTE sessions to which service components are delivered, as well as a ROUTE session to which an SLS is being delivered.
  • all service components delivered through a plurality of ROUTE sessions may be collected. This may be similarly applied when service components of a service are delivered through a plurality of MMTP sessions.
  • one service component may be used simultaneously by a plurality of services.
  • bootstrapping for ESG services may be performed by a broadcast network or broadband.
  • URL information of the SLT may be utilized. ESG information and the like can be requested to this URL.
  • one service component of one service may be delivered to the broadcasting network and one to the broadband (hybrid).
  • the S-TSID may describe components delivered to a broadcasting network, so that a ROUTE client may acquire desired service components.
  • USBD also has base pattern information, which allows you to describe which segments (which components) are to be routed to which path. Therefore, the receiver can use this to know what segment to request to the broadband server and what segment to find in the broadcast stream.
  • scalable coding for a service may be performed.
  • the USBD may have all the capability information needed to render the service. For example, when a service is provided in HD or UHD, the capability information of the USBD may have a value of “HD or UHD”.
  • the receiver may know which component should be played in order to render the UHD or HD service using the MPD.
  • app components to be used for app-based enhancement / app-based service may be delivered through a broadcast network or through broadband as an NRT component.
  • app signaling for app-based enhancement may be performed by an application signaling table (AST) delivered with SLS.
  • an event which is a signaling of an operation to be performed by the app, may be delivered in the form of an event message table (EMT) with SLS, signaled in an MPD, or in-band signaled in a box in a DASH representation. . AST, EMT, etc. may be delivered via broadband.
  • App-based enhancement may be provided using the collected app components and such signaling information.
  • a CAP message may be included in the aforementioned LLS table for emergency alerting. Rich media content for emergency alerts may also be provided. Rich media may be signaled by the CAP message, and if rich media is present it may be provided as an EAS service signaled by the SLT.
  • the linear service components may be delivered through a broadcasting network according to the MMT protocol.
  • NRT data for example, an app component
  • data on the service may be delivered through a broadcasting network according to the ROUTE protocol.
  • data on the service may be delivered through broadband.
  • the receiver can access the MMTP session carrying the SLS using the bootstrap information of the SLT.
  • the USBD of the SLS according to the MMT may refer to the MP table so that the receiver may acquire linear service components formatted with the MPU delivered according to the MMT protocol.
  • the USBD may further refer to the S-TSID to allow the receiver to obtain NRT data delivered according to the ROUTE protocol.
  • the USBD may further reference the MPD to provide a playback description for the data delivered over the broadband.
  • the receiver may transmit location URL information for obtaining a streaming component and / or a file content item (such as a file) to the companion device through a method such as a web socket.
  • An application of a companion device may request the component, data, and the like by requesting the URL through an HTTP GET.
  • the receiver may transmit information such as system time information and emergency alert information to the companion device.
  • FIG. 8 shows a structure of a broadcast signal transmission apparatus for a next generation broadcast service according to an embodiment of the present invention.
  • a broadcast signal transmission apparatus for a next generation broadcast service includes an input format block 1000, a bit interleaved coding & modulation (BICM) block 1010, and a frame building block 1020, orthogonal frequency division multiplexing (OFDM) generation block (OFDM generation block) 1030, and signaling generation block 1040. The operation of each block of the broadcast signal transmission apparatus will be described.
  • BICM bit interleaved coding & modulation
  • OFDM generation block orthogonal frequency division multiplexing
  • signaling generation block 1040 The operation of each block of the broadcast signal transmission apparatus will be described.
  • IP streams / packets and MPEG2-TS may be main input formats, and other stream types are treated as general streams.
  • the input format block 1000 can demultiplex each input stream into one or multiple data pipes to which independent coding and modulation is applied.
  • the data pipe is the basic unit for controlling robustness, which affects the quality of service (QoS).
  • QoS quality of service
  • One or multiple services or service components may be delivered by one data pipe.
  • a data pipe is a logical channel at the physical layer that carries service data or related metadata that can carry one or multiple services or service components.
  • the BICM block 1010 may include a processing block applied to a profile (or system) to which MIMO is not applied and / or a processing block of a profile (or system) to which MIMO is applied, and for processing each data pipe. It may include a plurality of processing blocks.
  • the processing block of the BICM block to which MIMO is not applied may include a data FEC encoder, a bit interleaver, a constellation mapper, a signal space diversity (SSD) encoding block, and a time interleaver.
  • the processing block of the BICM block to which MIMO is applied is distinguished from the processing block of BICM to which MIMO is not applied in that it further includes a cell word demultiplexer and a MIMO encoding block.
  • the data FEC encoder performs FEC encoding on the input BBF to generate the FECBLOCK procedure using outer coding (BCH) and inner coding (LDPC).
  • Outer coding (BCH) is an optional coding method.
  • the bit interleaver interleaves the output of the data FEC encoder to achieve optimized performance with a combination of LDPC codes and modulation schemes.
  • Constellation Mapper uses QPSK, QAM-16, non-uniform QAM (NUQ-64, NUQ-256, NUQ-1024) or non-uniform constellation (NUC-16, NUC-64, NUC-256, NUC-1024)
  • the cell word from the bit interleaver or cell word demultiplexer can then be modulated to provide a power-normalized constellation point.
  • NUQ has any shape, while QAM-16 and NUQ have a square shape. Both NUQ and NUC are specifically defined for each code rate and are signaled by the parameter DP_MOD of PLS2 data.
  • the time interleaver may operate at the data pipe level. The parameters of time interleaving can be set differently for each data pipe.
  • the time interleaver of the present invention may be located between a BICM chain block and a frame builder.
  • the time interleaver according to the present invention may selectively use a convolution interleaver (CI) and a block interleaver (BI) according to a physical layer pipe (PLP) mode, or both.
  • PLP according to an embodiment of the present invention is a physical path used in the same concept as the above-described DP, the name can be changed according to the designer's intention.
  • the PLP mode according to an embodiment of the present invention may include a single PLP mode or a multiple PLP mode according to the number of PLPs processed by the broadcast signal transmitter or the broadcast signal transmitter.
  • time interleaving using different time interleaving methods according to the PLP mode may be referred to as hybrid time interleaving.
  • the hybrid time deinterleaver may perform an operation corresponding to the reverse operation of the aforementioned hybrid time interleaver.
  • the cell word demultiplexer is used to separate a single cell word stream into a dual cell word stream for MIMO processing.
  • the MIMO encoding block can process the output of the cell word demultiplexer using the MIMO encoding scheme.
  • the MIMO encoding scheme of the present invention may be defined as full-rate spatial multiplexing (FR-SM) to provide capacity increase with a relatively small complexity increase at the receiver side.
  • MIMO processing is applied at the data pipe level.
  • NUQ e1, i and e2, i
  • MIMO encoder output pairs g1, i and g2, i
  • the frame building block 1020 may map data cells of an input data pipe to OFDM symbols and perform frequency interleaving for frequency domain diversity within one frame.
  • a frame according to an embodiment of the present invention is divided into a preamble, one or more frame signaling symbols (FSS), and normal data symbols.
  • the preamble is a special symbol that provides a set of basic transmission parameters for efficient transmission and reception of a signal.
  • the preamble may signal a basic transmission parameter and a transmission type of the frame.
  • the preamble may indicate whether an emergency alert service (EAS) is provided in the current frame.
  • EAS emergency alert service
  • the main purpose of the FSS is to carry PLS data. For fast synchronization and channel estimation, and fast decoding of PLS data, the FSS has a higher density pilot pattern than normal data symbols.
  • the frame building block adjusts the timing between the data pipes and the corresponding PLS data so that a delay compensation block is provided at the transmitter to ensure co-time between the data pipes and the corresponding PLS data.
  • a cell mapper and a frequency interleaver for mapping a PLS, a data pipe, an auxiliary stream, and a dummy cell to an active carrier of an OFDM symbol in a frame.
  • the frequency interleaver may provide frequency diversity by randomly interleaving data cells received from the cell mapper.
  • the frequency interleaver uses a different interleaving seed order to obtain the maximum interleaving gain in a single frame.
  • the frequency interleaver uses a single symbol or data corresponding to an OFDM symbol pair consisting of two sequential OFDM symbols. Operate on corresponding data.
  • OFDM generation block 1030 modulates the OFDM carrier, inserts pilots, and generates time-domain signals for transmission by the cells generated by the frame building block. In addition, the block sequentially inserts a guard interval and applies a PAPR reduction process to generate a final RF signal.
  • the signaling generation block 1040 may generate physical layer signaling information used for the operation of each functional block.
  • Signaling information may include PLS data.
  • PLS provides a means by which a receiver can connect to a physical layer data pipe.
  • PLS data consists of PLS1 data and PLS2 data.
  • PLS1 data is the first set of PLS data delivered to the FSS in frames with fixed size, coding, and modulation that convey basic information about the system as well as the parameters needed to decode the PLS2 data.
  • PLS1 data provides basic transmission parameters including the parameters required to enable reception and decoding of PLS2 data.
  • PLS2 data carries more detailed PLS data about the data pipes and systems and is the second set of PLS data sent to the FSS.
  • 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 is static during the duration of a frame group
  • PLS2 dynamic data is PLS2 data that changes dynamically from frame to frame.
  • the PLS2 data may include FIC_FLAG information.
  • FIC Fast Information Channel
  • the FIC_FLAG information is a 1-bit field and indicates whether a fast information channel (FIC) is used in the current frame group.If the value of this field is set to 1, the FIC is provided in the current frame. If the value of the field is set to 0, the FIC is not transmitted in the current frame.
  • the BICM block 1010 may include a BICM block for protecting PLS data
  • the BICM block for protecting PLS data is a PLS FEC encoder. , Bit interleaver, and constellation mapper.
  • the PLS FEC encoder performs external encoding on scrambled PLS 1,2 data using a scrambler for scrambling PLS1 data and PLS2 data, shortened BCH code for PLS protection, and a BCH for inserting zero bits after BCH encoding.
  • An encoding / zero insertion block, an LDPC encoding block for performing encoding using an LDPC code, and an LDPC parity puncturing block may be included.
  • the output bits of zero insertion can be permutated before LDPC encoding.
  • the bit interleaver interleaves the respective shortened and punctured PLS1 data and PLS2 data, and the constellation mapper bit interleaves.
  • the PLS1 data and the PLS2 data can be mapped to the constellation.
  • the broadcast signal receiving apparatus for the next generation broadcast service may perform a reverse process of the broadcast signal transmitting apparatus for the next generation broadcast service described with reference to FIG. 8.
  • An apparatus for receiving broadcast signals for a next generation broadcast service includes a synchronization and demodulation module for performing demodulation corresponding to a reverse process of a procedure executed by a broadcast signal transmitting apparatus and an input signal.
  • a frame parsing module for parsing a frame, extracting data on which a service selected by a user is transmitted, converting an input signal into bit region data, and then deinterleaving the bit region data as necessary, and transmitting efficiency
  • a demapping and decoding module for performing demapping on the mapping applied for decoding, and correcting an error occurring in a transmission channel through decoding, of various compression / signal processing procedures applied by a broadcast signal transmission apparatus.
  • Demodulated by an output processor and a synchronization and demodulation module that executes the inverse process It may include a signaling decoding module for obtaining and processing the PLS information from the signal.
  • the frame parsing module, the demapping and decoding module, and the output processor may execute the function by using the PLS data output from the signaling decoding module.
  • a time interleaving group according to an embodiment of the present invention is directly mapped to one frame or spread over PI frames.
  • Each time interleaving group is also divided into one or more (NTI) time interleaving blocks.
  • NTI time interleaving time interleaving block
  • each time interleaving block corresponds to one use of the time interleaver memory.
  • the time interleaving block in the time interleaving group may include different numbers of XFECBLOCKs.
  • the time interleaver may also act as a buffer for data pipe data prior to the frame generation process.
  • the time interleaver according to an embodiment of the present invention is a twisted row-column block interleaver.
  • the twisted row-column block interleaver according to an embodiment of the present invention writes the first XFECBLOCK in the column direction to the first column of the time interleaving memory, the second XFECBLOCK to the next column and the remaining XFECBLOCKs in the time interleaving block in the same manner. You can fill in these. And in an interleaving array, cells can be read diagonally from the first row to the last row (starting from the leftmost column to the right along the row).
  • the interleaving array for the twisted row-column block interleaver may insert the virtual XFECBLOCK into the time interleaving memory to achieve a single memory deinterleaving at the receiver side regardless of the number of XFECBLOCKs in the time interleaving block.
  • the virtual XFECBLOCK must be inserted in front of the other XFECBLOCKs to achieve a single memory deinterleaving on the receiver side.
  • FIG 9 illustrates a writing operation of a time interleaver according to an embodiment of the present invention.
  • the block shown on the left side of the figure represents a TI memory address array, and the block shown on the right side of the figure shows that virtual FEC blocks are placed at the front of the TI group for two consecutive TI groups. It represents the writing operation when two and one are inserted respectively.
  • the frequency interleaver may include an interleaving address generator for generating an interleaving address for applying to data corresponding to a symbol pair.
  • FIG. 10 is a block diagram of an interleaving address generator composed of a main-PRBS generator and a sub-PRBS generator according to each FFT mode included in a frequency interleaver according to an embodiment of the present invention.
  • the interleaving process for an OFDM symbol pair uses one interleaving sequence and is described as follows.
  • xm, l, p the p-th cell of the l-th OFDM symbol in the m-th frame and Ndata is the number of data cells.
  • Ndata CFSS for the frame signaling symbol
  • Ndata Cdata for the normal data
  • Ndata CFES for the frame edge symbol.
  • vm, l, p xm, l, Hi (p)
  • p 0,... Is given by Ndata-1.
  • Hl (p) is an interleaving address generated based on the cyclic shift value (symbol offset) of the PRBS generator and the sub-PRBS generator.
  • FIG. 11 illustrates a hybrid broadcast reception device according to an embodiment of the present invention.
  • the hybrid broadcasting system may transmit a broadcast signal by interworking a terrestrial broadcasting network and an internet network.
  • the hybrid broadcast reception device may receive a broadcast signal through a terrestrial broadcast network (broadcast) and an internet network (broadband).
  • the hybrid broadcast receiver includes a physical layer module, a physical layer I / F module, a service / content acquisition controller, an internet access control module, a signaling decoder, a service signaling manager, a service guide manager, an application signaling manager, an alarm signal manager, an alarm signal parser, Targeting signal parser, streaming media engine, non-real time file processor, component synchronizer, targeting processor, application processor, A / V processor, device manager, data sharing and communication unit, redistribution module, companion device and / or external modules can do.
  • the physical layer module (s) may receive and process a broadcast-related signal through a terrestrial broadcast channel, convert it into an appropriate form, and deliver the signal to a physical layer I / F module.
  • the physical layer I / F module may obtain an IP datagram from information obtained from the physical layer module.
  • the physical layer I / F module may convert the obtained IP datagram into a specific frame (eg, RS Frame, GSE, etc.).
  • the service / content acquisition controller may perform a control operation for acquiring service, content, and signaling data related thereto through broadcast and / or broadband channels.
  • the Internet Access Control Module (s) may control a receiver operation for acquiring a service, content, or the like through a broadband channel.
  • the signaling decoder may decode signaling information obtained through a broadcast channel.
  • the service signaling manager may extract, parse, and manage signaling information related to service scan and service / content from an IP datagram.
  • the service guide manager may extract announcement information from an IP datagram, manage an SG database, and provide a service guide.
  • the App Signaling Manager may extract, parse and manage signaling information related to application acquisition from an IP datagram.
  • Alert Signaling Parser can extract, parse and manage signaling information related to alerting from IP datagram.
  • Targeting Signaling Parser can extract, parse and manage signaling information related to service / content personalization or targeting from IP datagram.
  • the targeting signal parser may deliver the parsed signaling information to the targeting processor.
  • the streaming media engine can extract and decode audio / video data for A / V streaming from IP datagrams.
  • the non-real time file processor can extract, decode and manage file type data such as NRT data and applications from IP datagrams.
  • the Component Synchronizer can synchronize content and services such as streaming audio / video data and NRT data.
  • the targeting processor may process an operation related to personalization of a service / content based on the targeting signaling data received from the targeting signal parser.
  • the App Processor may process application related information, downloaded application status, and display parameters.
  • the A / V Processor may perform audio / video rendering related operations based on decoded audio, video data, and application data.
  • the device manager may perform a connection and data exchange operation with an external device.
  • the device manager may perform management operations on external devices, such as adding, deleting, and updating external devices that can be interworked.
  • the data sharing & communication unit can process information related to data transmission and exchange between the hybrid broadcast receiver and an external device.
  • the data that can be transmitted and exchanged may be signaling, A / V data, or the like.
  • the redistribution module (s) may obtain relevant information about next-generation broadcast services and contents when the broadcast receiver does not directly receive the terrestrial broadcast signal.
  • the redistribution module may support the acquisition of broadcast services and content by the next generation broadcast system when the broadcast receiver does not directly receive the terrestrial broadcast signal.
  • Companion device (s) may be connected to the broadcast receiver of the present invention to share audio, video, or signaling inclusion data.
  • the companion device may refer to an external device connected to the broadcast receiver.
  • the external module may refer to a module for providing a broadcast service / content and may be, for example, a next generation broadcast service / content server.
  • the external module may refer to an external device connected to the broadcast receiver.
  • FIG. 12 is a diagram illustrating the overall operation of the DASH-based adaptive streaming model according to an embodiment of the present invention.
  • the present invention proposes a next-generation media service providing method for providing content capable of supporting High Dynamic Range (HDR).
  • HDR content capable of expressing rich brightness is provided
  • the present invention proposes metadata and a delivery method thereof. Through this, the content may be adaptively adjusted according to various scene-specific characteristics of the content, and the content may be provided with improved image quality.
  • the DASH-based adaptive streaming model describes the operation between the HTTP server and the DASH client.
  • DASH Dynamic Adaptive Streaming over HTTP
  • DASH is a protocol for supporting HTTP-based adaptive streaming, and can dynamically support streaming according to network conditions. Accordingly, the AV content can be provided without interruption.
  • the DASH client can obtain the MPD.
  • MPD may be delivered from a service provider such as an HTTP server.
  • the MPD may be delivered according to the delivery embodiment described above.
  • the DASH client can request the segments from the server using the access information to the segment described in the MPD. In this case, the request may be performed by reflecting the network state.
  • the DASH client may process it in the media engine and display the segment on the screen.
  • the DASH client may request and acquire a required segment by adaptively reflecting a playing time and / or a network condition (Adaptive Streaming). This allows the content to be played back seamlessly.
  • Adaptive Streaming a network condition
  • MPD Media Presentation Description
  • XML form a file containing detailed information for allowing a DASH client to dynamically acquire a segment. This MPD may be the same as the MPD described above according to an embodiment.
  • the DASH Client Controller may generate a command for requesting the MPD and / or the segment reflecting the network situation.
  • the controller can control the obtained information to be used in an internal block of the media engine or the like.
  • the MPD Parser may parse the acquired MPD in real time. This allows the DASH client controller to generate a command to obtain the required segment.
  • the segment parser may parse the acquired segment in real time. Internal blocks such as the media engine may perform a specific operation according to the information included in the segment.
  • the HTTP client may request the HTTP server for necessary MPDs and / or segments.
  • the HTTP client may also pass MPD and / or segments obtained from the server to the MPD parser or segment parser.
  • the media engine may display content on the screen using media data included in the segment. At this time, the information of the MPD may be utilized.
  • FIG. 13 is a block diagram of a receiver according to an embodiment of the present invention.
  • the receiver includes a tuner, a physical layer controller, a physical frame parser, a link layer frame processor, and an IP / UDP datagram filter.
  • UDP Datagram Filter DTV Control Engine, ROUTE Client, Segment Buffer Control, MMT Client, MPU Reconstruction, Media Processor (Media Processor), Signaling Parser (Dash Client), DASH Client (DASH Client), ISO BMFF Parser (ISO BMFF Parser), Media Decoder and / or HTTP Access Client.
  • Each detailed block of the receiver may be a processor that is hardware.
  • the tuner can receive and process broadcast signals through terrestrial broadcast channels and convert them into appropriate forms (Physical Frame, etc.).
  • the physical layer controller may control operations of a tuner, a physical frame parser, etc. using RF information of a broadcast channel to be received.
  • the physical frame parser may acquire the link layer frame through parsing the received physical frame and processing related thereto.
  • the link layer frame processor may acquire link layer signaling from a link layer frame, acquire an IP / UDP datagram, and perform related operations.
  • the IP / UDP Datagram Filter may filter a specific IP / UDP datagram from the received IP / UDP datagrams.
  • the DTV Control Engine is in charge of the interface between each component and can control the operation of each component by passing parameters.
  • the Route Client can generate one or more ISO Base Media File Format (ISOBMFF) objects by processing Real-Time Object Delivery over Unidirectional Transport (ROUTE) packets that support real-time object transport, and collecting and processing multiple packets.
  • ISOBMFF ISO Base Media File Format
  • ROUTE Real-Time Object Delivery over Unidirectional Transport
  • Segment Buffer Control can control the buffer related to segment transmission between Route Client and Dash Client.
  • the MMT Client can process MPEG Media Transport (MPT) transport protocol packets that support real-time object transport and collect and process multiple packets.
  • MPU reconstruction may reconstruct a Media Processing Unit (MPU) from an MMTP packet.
  • the Media Processor can collect and process the reconstructed MPU.
  • MPEG Media Transport MPEG Media Transport
  • the Signaling Parser may acquire and parse DTV broadcast service related signaling (Link Layer / Service Layer Signaling), and generate and / or manage a channel map based on this. This configuration can handle low level signaling and service level signaling.
  • the DASH Client can process real-time streaming or adaptive streaming-related operations and acquired DASH Segments.
  • the ISO BMFF Parser may extract audio / video data and related parameters from an ISO BMFF object.
  • the media decoder may decode and / or present the received audio and video data.
  • the HTTP Access Client can request specific information from an HTTP server and process the response to the request.
  • FIG. 14 is a diagram showing the structure of a media file according to an embodiment of the present invention.
  • the media file of the present invention may have a file format based on ISO BMFF (ISO base media file format).
  • the media file according to the present invention may include at least one box.
  • the box may be a data block or an object including media data or metadata related to the media data.
  • the boxes may form a hierarchical structure with each other, such that the data may be classified so that the media file may be in a form suitable for storage and / or transmission of a large amount of media data.
  • the media file may have an easy structure for accessing the media information, such as a user moving to a specific point of the media content.
  • the media file according to the present invention may include an ftyp box, a moov box and / or an mdat box.
  • An ftyp box can provide file type or compatibility related information for a corresponding media file.
  • the ftyp box may include configuration version information about media data of a corresponding media file.
  • the decoder can identify the media file by referring to the ftyp box.
  • the moov box may be a box including metadata about media data of a corresponding media file.
  • the moov box can act as a container for all metadata.
  • the moov box may be a box of the highest layer among metadata related boxes. According to an embodiment, only one moov box may exist in a media file.
  • the mdat box may be a box containing actual media data of the media file.
  • Media data may include audio samples and / or video samples, where the mdat box may serve as a container for storing these media samples.
  • the above-described moov box may further include a mvhd box, a trak box and / or an mvex box as a lower box.
  • the mvhd box may include media presentation related information of media data included in the media file. That is, the mvhd box may include information such as media generation time, change time, time specification, duration, etc. of the media presentation.
  • the trak box can provide information related to the track of the media data.
  • the trak box may include information such as stream related information, presentation related information, and access related information for an audio track or a video track. There may be a plurality of trak boxes according to the number of tracks.
  • the trak box may further include a tkhd box (track header box) as a lower box.
  • the tkhd box may include information about the track indicated by the trak box.
  • the tkhd box may include information such as a creation time, a change time, and a track identifier of the corresponding track.
  • the mvex box (movie extend box) may indicate that the media file may have a moof box to be described later. To know all the media samples of a particular track, moof boxes may have to be scanned.
  • the media file according to the present invention may be divided into a plurality of fragments according to an embodiment (t14010). Through this, the media file may be divided and stored or transmitted.
  • the media data (mdat box) of the media file may be divided into a plurality of fragments, and each fragment may include a mdat box and a moof box. According to an embodiment, information of the ftyp box and / or the moov box may be needed to utilize the fragments.
  • the moof box may provide metadata about media data of the fragment.
  • the moof box may be a box of the highest layer among metadata-related boxes of the fragment.
  • the mdat box may contain the actual media data as described above.
  • This mdat box may include media samples of media data corresponding to each corresponding fragment.
  • the above-described moof box may further include a mfhd box and / or a traf box as a lower box.
  • the mfhd box may include information related to an association between a plurality of fragmented fragments.
  • the mfhd box may include a sequence number to indicate how many times the media data of the corresponding fragment is divided. In addition, it may be confirmed whether there is no missing data divided using the mfhd box.
  • the traf box may include information about a corresponding track fragment.
  • the traf box may provide metadata about the divided track fragments included in the fragment.
  • the traf box may provide metadata so that media samples in the track fragment can be decoded / played back. There may be a plurality of traf boxes according to the number of track fragments.
  • the above-described traf box may further include a tfhd box and / or a trun box as a lower box.
  • the tfhd box may include header information of the corresponding track fragment.
  • the tfhd box may provide information such as a basic sample size, a duration, an offset, an identifier, and the like for media samples of the track fragment indicated by the traf box described above.
  • the trun box may include corresponding track fragment related information.
  • the trun box may include information such as duration, size, and playback time of each media sample.
  • the aforementioned media file or fragments of the media file may be processed into segments and transmitted.
  • the segment may have an initialization segment and / or a media segment.
  • the file of the illustrated embodiment t14020 may be a file including information related to initialization of the media decoder except for media data. This file may correspond to the initialization segment described above, for example.
  • the initialization segment may include the ftyp box and / or moov box described above.
  • the file of the illustrated embodiment t14030 may be a file including the aforementioned fragment. This file may correspond to the media segment described above, for example.
  • the media segment may include the moof box and / or mdat box described above.
  • the media segment may further include a styp box and / or a sidx box.
  • the styp box may provide information for identifying the media data of the fragmented fragment.
  • the styp box may play the same role as the above-described ftyp box for the divided fragment.
  • the styp box may have the same format as the ftyp box.
  • the sidx box may provide information indicating an index for the divided fragment. Through this, it is possible to indicate how many fragments are the corresponding fragments.
  • the ssix box may be further included.
  • the ssix box (sub-segment index box) may provide information indicating an index of the sub-segment when the segment is further divided into sub-segments.
  • the boxes in the media file may include more extended information based on a box-to-full box form as in the illustrated embodiment t14050.
  • the size field and the largesize field may indicate the length of the corresponding box in bytes.
  • the version field may indicate the version of the box format.
  • the type field may indicate the type or identifier of the corresponding box.
  • the flags field may indicate a flag related to the box.
  • 15 is a diagram illustrating a bootstrapping process through SLT according to an embodiment of the present invention.
  • SLS bootstrapping may be performed through bootstrap information of the SLT.
  • the SLT may be processed by IP / UDP and transmitted, or may be transmitted without IP / UDP processing according to an embodiment.
  • LLS Low Level Signaling
  • SLT can be delivered by the most robust method in the transmission.
  • the receiver may access the corresponding SLS through bootstrap information of the SLT.
  • Service components of the corresponding service may be obtained using the information of the ROUTE SLS.
  • SLS and service components may be transmitted by ROUTE, UDP, and IP protocols.
  • the receiver may access the corresponding SLS through bootstrap information of the SLT.
  • Service components of the corresponding service may be obtained using the information of the MMTP SLS.
  • the MMTP SLS may include USBD and / or MMTP messages.
  • the USBD may refer to an MMTP message
  • the MPT message of the MMTP message may provide information for obtaining streaming components carried by the MMT protocol.
  • the USBD of the MMT may further refer to an S-TSID for acquiring NRT components of a corresponding service delivered through a ROUTE protocol.
  • other MMTP messages may be defined to provide other information.
  • the SLS and streaming components may be transmitted by MMT, UDP, and IP protocols.
  • the NRT components may be transmitted by ROUTE, UDP, and IP protocols.
  • the detailed bootstrapping process is as described above.
  • 16 is a diagram illustrating a signaling flow based on an MMT protocol according to an embodiment of the present invention.
  • the process of acquiring the SLT and acquiring the SLS using the same may be the same.
  • the SLS can include USBD and / or MMTP messages.
  • Information on an MMT Package associated with a corresponding service may be obtained from the USBD.
  • an MPT (MP Table) message may be obtained from a service signaling channel or the like.
  • Service components of the corresponding service may be obtained through the MPT message.
  • information on an asset for a base layer of scalable coding content and / or an asset for an enhancement layer may be obtained.
  • a path (transmission session, etc.) capable of acquiring each asset may be obtained.
  • the asset may correspond to a service component of a service.
  • MPUs can be obtained and decoded and reproduced through the corresponding path. The detailed bootstrapping process is as described above.
  • MMTP messages other than the MPT message may be defined. These messages may convey additional information about the service. For example, scalable coding related information, 3D related information, HDR related information, color ant related information, additional information about a service component, and the like may be transmitted through these messages. According to an embodiment, MPDs for service components delivered through broadband, or tables for app signaling and event information may also be delivered through this message.
  • FIG. 17 illustrates a capability descriptor according to an embodiment of the present invention.
  • the present invention proposes a method for signaling capability information of service components included in a broadcast service or a service. Signaling may be performed for a capability or a capability group for a service / service component, and capability information may be signaled according to a target device.
  • the above-described SLT may include capability information. It may be capability information of the entire service described by the SLT, or may be capability information of a service level for each service described by the SLT.
  • the aforementioned @sltCapabilities attribute or @svcCapabilities attribute may correspond to this.
  • the capability information may be included in the SLT as a descriptor of the SLT level or a descriptor of the SLS level.
  • the depicted capability descriptors represent the aforementioned capability information in the form of a descriptor.
  • the capability information may be expressed in another format such as XML.
  • information such as information in the capability descriptor illustrated according to an embodiment may be included in the @sltCapabilities attribute or the @svcCapabilities attribute of the aforementioned SLT.
  • the descriptor tag, the descriptor length information, and the like may be omitted.
  • this capability information will be described based on the descriptor.
  • the capability descriptor of the illustrated embodiment may include a descriptor_tag field, a descriptor_length field, and / or a num_capability_codes field.
  • the descriptor_tag field and the descriptor_length field may provide information for identifying that the corresponding descriptor is a capability descriptor and length information of the corresponding descriptor.
  • the num_capability_codes field may indicate the number of capability information included in the corresponding descriptor. According to an embodiment, this field may indicate the number of capability codes included in the descriptor. Detailed fields for each capability information may be further included according to the value of the num_capability_codes field.
  • the detail fields may include an essential_indicator field, capability_category field, and / or capability_code field. In some embodiments, the essential_indicator field may be omitted.
  • the essential_indicator field may indicate whether the following capability code is a capability that must be supported in reproducing the corresponding service or service component. When the value of this field is 1, it can be seen that the following capacities must be supported in playing the corresponding service or service component.
  • the capability_category field may indicate a category of the following capability information. According to an embodiment, this field may indicate an object to which the following capability information is applied.
  • the capability category information may be for classifying a category of capabilities. According to an embodiment, the capability category information may be for grouping capabilities that may be equally applied to a corresponding service or service component. Through this, capability to be applied to a component in a service or capability information applied to each component may be signaled.
  • the corresponding capability may be a capability related to a video component. That is, it can be seen that the following capability code is a capability code for video-related capability. For example, it may be followed by capability codes relating to video codecs, resolutions, video provision methods, transport protocols, FEC algorithms, target devices, and the like.
  • the corresponding capability may be a capability related to an audio component. That is, it can be seen that the following capability code is a capability code for audio related capability. For example, it may be followed by capability codes relating to audio codecs, audio channels, transport protocols, FEC algorithms, target devices, and the like.
  • the corresponding capability may be a capability related to a closed caption.
  • a capability code relating to the closed caption type, transport protocol, FEC algorithm, target device, and the like.
  • the corresponding capability may be a capability related to an application. For example, it may be followed by a capability code relating to the application type, transport protocol, FEC algorithm, target device, and the like.
  • the corresponding capability may be a capability regarding a transport protocol, an FEC algorithm, and a target device, respectively. In other words, it may not be a capability related to video / audio / closed caption / application. In this case, the matters of the transmission protocol, the FEC algorithm, and the target device indicated by the following capability code may be equally applied to all components (video / audio / closed caption / application) in the corresponding service.
  • the capability_code field may indicate a capability code indicating capability information on a corresponding service or service component.
  • the capability code may be a code value designated for each capability. This will be described later.
  • num_capability_code may have a value of 0x05.
  • the five capability_codes may have values of 0x13 (HEVC), 0x22 (ultra high definition video), 0x40 (MPEG-H audio), 0x52 (7.1 channel), and / or 0x60 (SMPTE timed text).
  • the essential_indicator field may be omitted here.
  • FIG. 18 is a diagram illustrating a capability code according to an embodiment of the present invention.
  • the capability code may be a code indicating a capability for a corresponding service or service component as described above.
  • the illustrated capability codes may be values that can be used in the capability_code field described above.
  • Each classification of the illustrated capability code (video, audio, etc.) may be values that can be used in the capability_category field described above.
  • the leading partial digits of the illustrated capability code may be used to identify the capability category.
  • the remaining digits of the corresponding capability code may be used to identify the corresponding capability within the corresponding category.
  • the capability code may include a capability code for a high quality video enhancement type. For example, when the capability code is 0xA0, it may indicate a high dynamic range (HDR), when 0xA1 is a wide color gamut (WCG), and when it is 0xA2, a high frame rate (HFR).
  • HDR high dynamic range
  • WCG wide color gamut
  • HFR high frame rate
  • USBD 19 illustrates a portion of a USBD according to another embodiment of the present invention.
  • the present invention proposes a method for signaling capability information of service components included in a broadcast service or a service.
  • the present invention proposes a method of signaling video / audio / closed caption information on a service / service component.
  • the present invention proposes a method of signaling HEVC video related information for a service / service component.
  • the present invention proposes a method of signaling information on SMPTE-TT or CEA-809 based closed caption for a service / service component.
  • the present invention proposes a method of signaling information about 3D, scalable content, component group, real-time / non-real-time content, accessibility, view configuration for a display area, and target screen for a service / service component. .
  • the present invention proposes a method for signaling high dynamic range (HDR), wide color gamut (WCG), high frame rate (HFR), and pull down recovery configuration (Pull Down Recovery Configuration) information for a service / service component.
  • HDR high dynamic range
  • WCG wide color gamut
  • HFR high frame rate
  • Pull Down Recovery Configuration pull down recovery configuration
  • the present invention proposes a method of signaling 3D audio, AC-4, MPEG-H related information for a service / service component.
  • the present invention proposes a method for signaling PIP (Picture in Picture) related information with respect to a service / service component.
  • SRD Spatial Relationship Description
  • display priority information display priority information
  • SRD signaling information between different content sources signaling information about the display area of each view
  • signaling information about the role of each view are described. May be signaled.
  • the above-described information may be included in the SLT or other service signaling information and transmitted according to an embodiment.
  • the information may be included in the USBD according to ROUTE or MMT and transmitted.
  • the information may be defined as one of the ROUTE SLS and transmitted along with other SLSs, or may be defined and included in one of the MMTP messages described above as one of the MMTP SLSs.
  • the information may be included in the MPD and transmitted. In this case, the information may be included in the essential property and / or supplemental property.
  • the information may be included in the aforementioned MPT message of the MMTP message or included in one of the separately defined MMTP messages.
  • the information may be defined and transmitted in various descriptors in XML or binary form, or may be configured as an element and included in signaling information according to ROUTE, MMT, 3GPP, and the like. This information will be described later in detail.
  • the aforementioned USBD of ROUTE or MMT may include a ComponentInfo element according to an embodiment.
  • the ComponentInfo element is as described above.
  • the ComponentInfo element may be extended to further include the fields shown.
  • the ComponentInfo element may contain @componentGroupId, @essentialIndicator, @dependentComponentID, @protocolType, @rt, @targetDevice, @componentCodec, @componentProfile, @componentLang, @width, @height, Accessibility, Capability, Rating, Targeting, It may further include ComponentDescription and / or ComponentProperty. In some embodiments, only some of these added fields may be added to the ComponentInfo element.
  • @componentGroupId may be an identifier of a component group.
  • the component group may be a collection of components.
  • Components included in a component group may be components that represent the same scene or are combined to generate a presentation. For example, service components including music, dialog, and sound effects used to provide complete audio may be grouped into a single component group.
  • service components including a left image and a right image of the 3D image may be grouped into one component group.
  • @essentialIndicator can indicate whether the component is an essential component of the service. If this field is 1, the corresponding component may be an essential component of the corresponding service.
  • @dependentComponentID may indicate identifier (s) for dependent component (s). For example, for an enhanced video component, this field may indicate the identifier (s) of the base video component (s).
  • @protocolType can indicate a transport protocol that delivers the component.
  • the ROUTE or MMT protocol may be indicated.
  • @rt can indicate whether the component is a real-time component or not.
  • @targetDevice can indicate the target device targeted by the component. For example, when the value of this field is 0, 1, 2 3, it may be indicated that the corresponding component is a component for inset of a primary device, a companion device, a primary & companion device, and a primary screen, respectively.
  • @componentCodec may provide codec information for the component.
  • @componentProfile can indicate the profile of the component.
  • @componentLang can indicate the language used in the component. This field can be used especially for audio, closed caption components.
  • @width may indicate the horizontal width of the video media presentation delivered by the corresponding video component.
  • @height may indicate the vertical height of the video media presentation delivered by the corresponding video component.
  • Accessibility can provide information about accessibility of the component. Capability can provide the capability related information of the corresponding component. Rating may provide rating related information of a corresponding component. Targeting may provide information related to targeting or personalization of a corresponding component. ComponentDescription may provide component description information of the corresponding component. This information may include codec dependent encoding parameters. ComponentProperty may provide component properties for processing the corresponding component.
  • the above-described @componentType field in the ComponentInfo element may indicate the type of the corresponding component.
  • the corresponding component may be indicated to be an audio, video, caption, and application component, respectively.
  • the @componentRole field may indicate the role of the corresponding component. This role may be indicated according to the indicated component type. In the case of an audio component, if this field has a value of 1, 2, 3, 4, 5, 6, and 7, the corresponding audio component is a complete main. ), Music, effects, dialogue, commentary, visually impaired, hearing impaired, voice over, and subset.
  • the visual / hearing impaired may mean that the corresponding audio component is an audio component for the visually and hearing impaired person.
  • Voice over may mean that a corresponding audio component plays a role of discdriving a video component.
  • the video component serves as primary video, alternate camera view, sign language, 3D left image, 3D right image, 3D video depth information, and video with caption. Can be indicated.
  • the caption component may correspond to a main, replacement, supplementary, normal, and easy reader according to the value of this field.
  • the remaining part of the above-described ROUTE or the USBD of the MMT may be changed. These changes may be combined with each other according to the number of cases.
  • the USBD may further include @providerid, @serviceCategory, @spIndicator, @serviceStatus, @shortServiceName, and / or capabilityCode.
  • @providerid can identify the service provider of the service.
  • @serviceCategory can indicate the category of the service.
  • @spIndicator may be the same as the @protected attribute described above.
  • @serviceStatus may be the same as the aforementioned @servicestatus attribute.
  • @shortServiceName may indicate a short name of the corresponding service.
  • the capabilityCode may indicate a capability or a capability group required for the receiver to provide a meaningful media presentation of the service.
  • the USBD may further include @majorChannelNo, @minorChannelNo, and / or @serviceLang in the aforementioned channel element.
  • @majorChannelNo and @minorChannelNo can indicate the major / minor channel number of the corresponding service.
  • @serviceLang can indicate the primary language of the service.
  • the USBD may further include a dashComponent element instead of the aforementioned routeComponent and broadbnadComponet.
  • the dashComponent element may include @fullMPDUri, @sTSIDUri and / or deliveryMethod elements.
  • @fullMPDUri may provide reference information to MPD for service components delivered through a broadcast network or broadband.
  • @sTSIDUri may provide transport session related information about a service component of a corresponding service.
  • deliveryMethod may provide delivery related information of service components of a corresponding service. As described above, an element and / or basePattern information for each of the components delivered through the broadcast network / broadband may be further included.
  • FIG. 20 illustrates a part of an MP table according to an embodiment of the present invention.
  • the aforementioned MPT message may carry an MP table.
  • information such as accessibility, 3D, caption, and the like may be conveyed through an MMTP message. As shown, it may be delivered as part of the MPT message, or may be delivered as MMT signaling through a separately defined MMTP message. This information and delivery form will be described later in detail.
  • descriptors may correspond to asset descriptors.
  • descriptors may be delivered together with or included in DVB SI service signaling such as SDT or EIT.
  • information about a service component may be signaled as shown. Fields to be described later may be further added to the MMTP message.
  • the service_type field may indicate the type of a corresponding service. That is, it may mean a final service that can provide a combination of at least one asset included in the MP table.
  • the corresponding field may indicate stereoscopic 3D service, multiview service, panorama service, and the like.
  • the asset_role_flag field may indicate whether role information on a corresponding service component (asset) is included.
  • the asset_target_flag field may indicate whether target screen information on the corresponding service component is included.
  • the asset_group_flag field may indicate whether a corresponding service component belongs to a specific component group. When included in a specific component group, the value of this field may be 1.
  • the rt_flag field may indicate whether a corresponding service component is transmitted in real time / non-real time. If this field value is 1, the corresponding service component may be transmitted in real time.
  • the asset_role field may indicate a role of the corresponding service component. For example, if the value of this field is 0, 1, 2, 3, 4, 5, 6, 7, the corresponding service component is the primary video, alternate camera view, other alternate video component, sign language, and follow subject video. subject video), 3D left image, 3D right image, 3D depth information, and the like.
  • the asset_target field may indicate a target device targeted by the corresponding service component. It may be the same as the definition of @targetDevice described above.
  • the asset_group_id field may provide an identifier of a component group in which a corresponding service component is included. The component group is as described above.
  • FIG 21 illustrates an asset group descriptor according to an embodiment of the present invention.
  • the asset group descriptor may describe a component group (asset group) when the service is delivered through the MMT protocol. This descriptor can be passed through the same path as described above.
  • the asset group descriptor may include an asset_group_id field for identifying a corresponding component group, a num_of_accessiblity field for indicating the number of components (assets) included in the corresponding component group, and / or asset_id () fields for identifying respective components.
  • FIG. 22 illustrates accessibility information according to an embodiment of the present invention.
  • Accessibility information may include information related to the accessibility of the service or service component.
  • the accessibility information may have the form of one of the descriptors according to the above-described embodiment or may have the form of an element.
  • accessibility information may be defined in the form of a descriptor.
  • @schemeIdUri may be a URI for identifying that the descriptor has an accessibility scheme related to accessibility information.
  • @schemeIdUri may have a value of urn: atsc3.0: accessibility: 201x.
  • @value can have values whose meaning is defined according to an accessibility scheme. This value will be described later.
  • @id may represent an identifier of the descriptor. In the case of having the same identifier, the same scheme ID, value, and parameter may be included.
  • the illustrated embodiment t25020 may represent each parameter of the aforementioned @value.
  • Visually impaired may indicate whether the corresponding service component is a service component targeting a viewer who is visually impaired or has low vision.
  • Hearing impaired may indicate whether the corresponding service component is a service component targeting a viewer who is deaf or hard of hearing.
  • enhanced-audio-intelligibility may indicate whether the corresponding audio service component is an enhanced audio service component in terms of intelligibility.
  • 3D supported may indicate whether the corresponding service component is a service component supporting 3D function. According to an embodiment, it may indicate whether a corresponding service component is a service component included in a 3D service. Normal may indicate whether the corresponding service component (mainly for the closed caption component) is a service component for general viewers.
  • the easy reader may indicate whether the corresponding service component (mainly for the closed caption component) is a service component in the form of an easy reader. Easy readers can mean closed captions that are easy to read.
  • the accessibility information may be defined in the form of an access element having each of the above-described parameters of @value as a subfield.
  • accessibility information may be defined in the form of a descriptor.
  • This descriptor may be included in the MMT signaling information and delivered as described above.
  • This descriptor may be delivered included in the aforementioned MPT message or other MMTP message.
  • This descriptor may be a kind of asset descriptor.
  • the num_of_accessiblity field may indicate the number of accessibility codes (accessiblity_code) that follow.
  • the accessiblity_code field may indicate accessibility related information. Accessibility-related information may be represented by accessibility code. For example, when the accessibility code has values of 0x00, 0x01, and 0x02, it may have meanings such as visual impaired, hearing impaired, 3D support, and the like. These accessibility information is as described above. The 0x03-0xFF value can be reserved for future use.
  • FIG. 23 illustrates ComponentInfo elements in a USBD according to an embodiment of the present invention.
  • the two service components are related to each other as service components forming one 3D video and may be grouped into the same component group.
  • This component group may have an identifier of 0x01 and this content is set to each componentInfo. Can be signaled in an element.
  • @dependentComponentID of the second component has a value of 0x01 and may indicate a component ID of the first component.
  • follow-subject metadata on another component may be signaled for a particular video component.
  • the first component may be signaled to play the role of primary video as a video component.
  • the second component may be a component that serves as follow subject metadata for the first component. This role may be signaled and @dependentComponentID may indicate the component ID of the first component.
  • the first / second component may be included in the same component group (0x01).
  • each base video component and two enhanced video components are signaled. If one enhanced video has a dependency on the base video and another enhanced video has a dependency on the first enhanced video, this relationship can be signaled using the @dependentComponentID field as shown.
  • each video component may constitute the same scene, and thus may be included in the same component group.
  • a role as a 3D component and a scalable coding aspect for two service components are signaled. These components can make up the same scene and can be included in the same component group.
  • FIG. 24 illustrates component property information according to an embodiment of the present invention.
  • the component attribute information may include information related to an attribute of a corresponding service or service component.
  • the component property information may have the form of one of the descriptors according to the above-described embodiment or may have the form of an element.
  • the component property information may be called view configuration information according to an embodiment.
  • the component property information may mean view configuration information about a video component.
  • the corresponding component may be a video component and may be part of a multi view. If the video component is part of a video array, the @role attribute of the view configuration information may indicate that the corresponding component is the ⁇ x, y> th video component of the ⁇ n, m> array.
  • the component attribute information may be defined in the form of a descriptor.
  • @schemeIdUri may be a URI for identifying that the descriptor has a component attribute scheme related to component attribute information.
  • @schemeIdUri may have a value of urn: atsc3.0: view-conf: 201x.
  • @value can have values whose meaning is defined according to the component attribute scheme. These values can be called parameters and can be distinguished by ',' respectively. This value will be described later.
  • @id may represent an identifier of the descriptor. In the case of having the same identifier, the same scheme ID, value, and parameter may be included.
  • the illustrated embodiment t27020 may represent each parameter of the aforementioned @value.
  • View_x and / or View_y may indicate the origin of the image of the video component based on the left-top of the screen. Each field may indicate an x coordinate and a y coordinate of the image origin.
  • View_width and / or View_height may indicate a width and / or height of an image of a corresponding video component.
  • View_total_width and / or View_total_height may indicate the width and / or height of the entire area where the video array is displayed based on the left-top of the screen.
  • View_display_priority may indicate the priority of an image of a corresponding video component. The priority may be a priority when the corresponding image is displayed.
  • Source_id may be an identifier for a source of a corresponding video component.
  • the component property information may be defined in the form of a component property element having each of the above-described parameters of @value as a subfield.
  • the component attribute information may be defined in the form of a descriptor.
  • This descriptor may be included in the MMT signaling information and delivered as described above.
  • This descriptor may be delivered included in the aforementioned MPT message or other MMTP message.
  • This descriptor may be a kind of asset descriptor.
  • view_x, view_y, view_width, view_height, total_width, total_height, source_id and / or view_priority may be as defined above.
  • total_width, total_height, and view_priority may be the same as view_total_width, view_total_height, view_display_priority, respectively.
  • source_id_flag may indicate the presence or absence of source_id.
  • the view_total_info_flag field may indicate whether information on a region in which the multi-view viewed simultaneously is displayed. There may be total_width and total_height according to this field.
  • the view_priority_flag field may indicate whether priority information of an image of a corresponding video component is included. View_priority may exist according to this field.
  • FIG. 25 is a diagram illustrating component property information according to an embodiment of the present invention.
  • the component attribute information may include information related to an attribute of a corresponding service or service component.
  • the component property information may have the form of one of the descriptors according to the above-described embodiment or may have the form of an element.
  • the component property information may be referred to as view position configuration information according to an embodiment.
  • the component property information may mean view position configuration information about a video component.
  • the corresponding component is a video component and may be part of a stereoscopic 3D service.
  • component attribute information may be defined in the form of a descriptor.
  • @schemeIdUri may be a URI for identifying that the descriptor has a component attribute scheme related to component attribute information.
  • @schemeIdUri may have a value of urn: atsc3.0: view-position-conf: 201x.
  • @value can have values whose meaning is defined according to the component attribute scheme. These values can be called parameters and can be distinguished by ',' respectively. This value will be described later.
  • @id may represent an identifier of the descriptor. In the case of having the same identifier, the same scheme ID, value, and parameter may be included.
  • the illustrated embodiment d25020 may represent each parameter of the aforementioned @value.
  • the right_view_flag field may indicate whether the corresponding video component is right view or left view. The value is 0 when the video component is in the left view and 1 when the video component is in the right view.
  • the view position configuration information for each video component is represented by the above component properties. Information may be signaled as d25040 using a component property element. Since each left / right video component composes one scene, it may have the same component group ID value.
  • the component property information may be referred to as view position configuration information according to an embodiment.
  • the component property information may mean view position configuration information about a video component.
  • the corresponding component is a video component and may be part of a multiview service.
  • component attribute information may be defined in the form of a descriptor.
  • @schemeIdUri may be a URI for identifying that the descriptor has a component attribute scheme related to component attribute information.
  • @schemeIdUri may have a value of urn: atsc3.0: view-position2-conf: 201x.
  • @value can have values whose meaning is defined according to the component attribute scheme. These values can be called parameters and can be distinguished by ',' respectively. This value will be described later.
  • @id may represent an identifier of the descriptor. In the case of having the same identifier, the same scheme ID, value, and parameter may be included.
  • the illustrated embodiment d25030 may represent each parameter of the aforementioned @value.
  • the view position information may mean view position information of a corresponding video component in a multiview service.
  • the view position information (view_position field) may be set to 0 with respect to the first view located at the leftmost side of the multi view.
  • the view point position information may be set to a value that is increased by one each time it is moved from the first view to the next view from left to right.
  • the multiview may be a multiview for 3D multiview or panorama.
  • the above-described view position information may include a meaning of a left view or a right view for each view.
  • view position information expressed as a number
  • the view position configuration information for each video component uses the above component property information. May be signaled as d25040.
  • Video components constituting a scene of one of the multiviews may have the same component group ID value. In addition, other video components constituting the scene may have a different component group ID value.
  • FIG. 26 is a diagram illustrating utilization of component property information according to an embodiment of the present invention.
  • one screen may be divided into two video components and delivered.
  • the view configuration information for each video component may be signaled using the componentProperty element as described above. Since they constitute a scene, they can have the same componentGroupId value.
  • the componentProperty element of the ComponentInfo element for each component may have the above-described view configuration information.
  • @value is “1920, 0, 1920, 2160, 3840, 2160”, “0, 0, 1920, 2160, 3840, 2160” respectively. It can have The parameters of @value may have a meaning according to the definition of the above-described parameters in order.
  • a video component including a separate sign language may be delivered along with a video component providing one main video.
  • the sign language video component may provide information about a location of a region where the corresponding sign language image is displayed. This information may be signaled in the form of the above view configuration information.
  • view configuration information may be provided in the same manner as in the case of sign language.
  • the sign language image or the PIP image should be displayed in front of the main video, and thus have a higher priority than the main video.
  • These components may be included in the same component group, and a sign language component or a PIP component may have an @targetDevice property indicating “inset of a primary screen”.
  • the view configuration information of the sign language component or the PIP component may have a scheme ID of urn: atsc3.0: view-conf: 201x, and the @value may have “1200, 50, 1024, 768, 3840, 2160, 0”.
  • the parameters of @value may have a meaning according to the definition of the above-described parameters in order.
  • the aforementioned capability information may also be signaled.
  • the capability information may have the form of one of the descriptors according to the above-described embodiment or may have the form of an element.
  • the capability information may also be defined according to the capability scheme ID, and values thereof may be defined. It may also be defined in the form of a capability element having each parameter of @value as a subfield.
  • the capability information may be defined in the form of a descriptor and included in the MMT signaling information to be delivered. This descriptor may be delivered included in the aforementioned MPT message or other MMTP message. This descriptor may be a kind of asset descriptor. Details of the fields, parameters, and structure of the capability information have already been described above.
  • FIG. 27 is a diagram illustrating HEVC video component description information according to an embodiment of the present invention.
  • the HEVC video component description information may include information related to HEVC video of a corresponding service or service component.
  • HEVC video component description information may be referred to as HEVC video information.
  • the HEVC video information may include a component related encoding parameter or a parameter for rendering a corresponding component.
  • the HEVC video information may have the form of one of the descriptors according to the above-described embodiment or may have the form of an element.
  • the HEVC video information may be defined in the form of a descriptor.
  • @schemeIdUri may be a URI for identifying that the descriptor has a HEVC video scheme related to HEVC video information.
  • @schemeIdUri may have a value of urn: atsc3.0: hevc: 201x.
  • @value may have values whose meaning is defined according to the HEVC video information scheme. This value will be described later.
  • @id may represent an identifier of the descriptor. In the case of having the same identifier, the same scheme ID, value, and parameter may be included.
  • the illustrated embodiment t29020 may represent each parameter of the aforementioned @value.
  • profile_space may be equal to the general_profile_space value included in the SPS of the bitstream for the HEVC video stream.
  • the HEVC temporal video subset or the HEVC temporal video sub-bitstream it may be the same as the sub_layer_profile_space value included in the SPS of the bitstream.
  • tier_flag may be equal to the general_tier_flag value included in the SPS of the bitstream for the HEVC video stream. In the case of the HEVC temporal video subset or the HEVC temporal video sub-bitstream, it may be equal to the sub_layer_tier_flag value included in the SPS of the bitstream.
  • profile_idc may be equal to the general_profile_idc value included in the SPS of the bitstream for the HEVC video stream. In the case of the HEVC temporal video subset or the HEVC temporal video sub-bitstream, it may be equal to the sub_layer_profile_idc value included in the SPS of the bitstream.
  • profile_compatibility_indication may be equal to the general_profile_compatibility_flag [i] value included in the SPS of the bitstream for the HEVC video stream.
  • the HEVC temporal video subset or the HEVC temporal video sub-bitstream it may be equal to the sub_layer_profile_compatibility_flag [i] value included in the SPS of the bitstream.
  • progressive_source_flag may be equal to the general_progressive_source_flag value included in the SPS of the bitstream for the HEVC video stream.
  • it may be equal to the sub_layer_progressive_source_flag value included in the SPS of the bitstream.
  • interlaced_source_flag may be equal to the general_interlaced_source_flag value included in the SPS of the bitstream for the HEVC video stream. In the case of the HEVC temporal video subset or the HEVC temporal video sub-bitstream, it may be equal to the sub_layer_interlaced_source_flag value included in the SPS of the bitstream.
  • non_packed_constraint_flag may be equal to the general_non_ packed_constraint_flag value included in the SPS of the bitstream for the HEVC video stream.
  • it may be equal to the sub_layer_non_packed_constraint_flag value included in the SPS of the bitstream.
  • the frame_only_constraint_flag may be equal to the general_frame_only_constraint_flag value included in the SPS of the bitstream for the HEVC video stream. In the case of the HEVC temporal video subset or the HEVC temporal video sub-bitstream, it may be equal to the sub_layer_frame_only_constraint_flag value included in the SPS of the bitstream.
  • reserved_zero_44bits may be equal to the general_reserved_zero_44bits value included in the SPS of the bitstream for the HEVC video stream. In the case of the HEVC temporal video subset or the HEVC temporal video sub-bitstream, it may be equal to the sub_layer_reserved_zero_44bits value included in the SPS of the bitstream.
  • level_idc may be equal to the general_level_idc value included in the SPS of the bitstream for the HEVC video stream. In the case of the HEVC temporal video subset or the HEVC temporal video sub-bitstream, it may be equal to the sub_layer_level_idc value included in the SPS of the bitstream.
  • HEVC_still_present_flag may indicate whether the HEVC video stream or the HEVC highest temporal sub-layer representation includes HEVC still pictures.
  • HEVC_24hr_picture_present_flag may indicate whether the HEVC video stream or the HEVC highest temporal sub-layer representation includes HEVC 24-hours pictures.
  • the temporal_id_min and / or temporal_id_max may indicate the smallest temporalId value and / or the largest temporalId value among the HEVC AUs included in the HEVC video stream.
  • the HEVC video information may be defined in the form of an HEVC video information element having each of the above-described parameters of @value as a subfield.
  • the HEVC video information may be defined in the form of a descriptor.
  • This descriptor may be included in the MMT signaling information and delivered as described above.
  • This descriptor may be delivered included in the aforementioned MPT message or other MMTP message.
  • This descriptor may be a kind of asset descriptor.
  • a value corresponding to the asset type of the MP table may be allocated to the HEVC video stream.
  • the HEVC timing & HRD information can include timing information and HRD description associated with the HEVC video stream component.
  • the HEVC timing & HRD information may have the form of one of the descriptors according to the above-described embodiment or may have the form of an element. This may be represented by the componentProperty element described above.
  • the HEVC timing & HRD information may be defined in the form of a descriptor.
  • @schemeIdUri may be a URI for identifying that the descriptor has a scheme related to HEVC timing & HRD information.
  • @schemeIdUri may have a value of urn: atsc3.0: hevc-timing: 201x.
  • @value can have values whose meaning is defined according to the scheme. This value will be described later.
  • @id may represent an identifier of the descriptor. In the case of having the same identifier, the same scheme ID, value, and parameter may be included.
  • the illustrated embodiment t30010 may represent each parameter of the aforementioned @value.
  • hrd_management_valid_flag may indicate whether a buffering period SEI and Picture Timing SEI message exist in the HEVC video stream or HEVC high temporal sub-layer representation.
  • the picture_and_timing_info_present_flag may indicate whether the 90kHz_flag and its associated parameters for accurate mapping with the 90 kHz system clock are included in the descriptor.
  • 90kHz_flag may indicate whether the frequency of the time base of the HEVC video stream is 90KHz or not.
  • N and / or K may provide N, K parameter values with respect to the time scale.
  • the frequency of the HEVC time base may be defined by the vui_time_scale element of the VUI parameter.
  • N may have a value of 1
  • K may have a value of 300.
  • 90 kHz_flag 0, the N and K values may be provided by the N and K fields.
  • num_units_in_tick may be coded in the same manner as the vui_num_units_in_tick field of the VUI parameter, and this field value may be applied to the entire HEVC video stream or HEVC high temporal sub-layer representation related to the corresponding HEVC timing & HRD description information.
  • the HEVC timing & HRD information may be defined in the form of an HEVC timing & HRD information element having the above-described parameters of @value as subfields.
  • the HEVC timing & HRD information may be defined in the form of a descriptor.
  • This descriptor may be included in the MMT signaling information and delivered as described above.
  • This descriptor may be delivered included in the aforementioned MPT message or other MMTP message.
  • This descriptor may be a kind of asset descriptor.
  • hrd_management_valid_flag, picture_and_timing_info_present_flag, 90kHz_flag, N, K, and / or num_units_in_tick may be included in the descriptor, which may be as described above.
  • FIG. 29 is a diagram illustrating caption information according to an embodiment of the present invention.
  • the caption information may include caption description information related thereto.
  • Caption information may have the form of one of the descriptors according to the above-described embodiment, or may have the form of an element. This may be represented by the componentProperty element described above.
  • caption information may be defined in the form of a descriptor.
  • @schemeIdUri may be a URI for identifying that the descriptor has a caption scheme related to caption information.
  • @schemeIdUri may have a value of urn: atsc3.0: caption: 201x.
  • @value can have values whose meaning is defined according to the caption scheme. This value will be described later.
  • @id may represent an identifier of the descriptor. In the case of having the same identifier, the same scheme ID, value, and parameter may be included.
  • the illustrated embodiment t31010 may represent each parameter of the aforementioned @value.
  • caption_codec may indicate an encoding type of a corresponding caption component. According to an embodiment, “CEA-608”, “CEA-708”, “SMPTE-TT”, etc. may be indicated.
  • lang may include language information of a corresponding caption component.
  • caption_service_number may include a service number of a corresponding caption when the type of the caption component is CEA-708.
  • easy_reader_flag may indicate whether a corresponding caption component is an easy reader type.
  • aspect_ratio may indicate a display aspect ratio of a corresponding caption component. In some embodiments, “4: 3” or “16: 9” may be indicated.
  • 3D supported may indicate whether the caption component supports 3D.
  • the caption information may be defined in the form of a caption element having the above-described parameters of @value as subfields.
  • caption information may be defined in the form of a descriptor.
  • This descriptor may be included in the MMT signaling information and delivered as described above. This descriptor may be delivered included in the aforementioned MPT message or other MMTP message.
  • an asset type of the MP table may be assigned a value corresponding to the closed caption stream.
  • the asset type of the MP table may include a descriptor shown as an asset descriptor while indicating a value corresponding to the HEVC video stream. In this case, it may appear that closed caption data is included in the HEVC video bitstream.
  • This descriptor may be a kind of asset descriptor.
  • caption_lang, caption_codec, easy_reader, wide_aspect_ratio, 3d_supported and / or caption_service_number may be included in the descriptor, and the meaning may be as described above.
  • Caption_lang, easy_reader, and wide_aspect_ratio may be the same as lang, easy_reader_flag, and aspect_ratio described above, respectively.
  • caption_codec if the value is 0x01, 0x02, 0x03, 0x04, 0x05, respectively, “CEA-608”, “CEA-708”, “SMPTE timed text”, “EBU-TT-D”, “CFF-TT” It may be indicated that the encoding type of is used.
  • the url_flag, URL_length, and URL_text fields may be the same as those in the above caption information.
  • a closed caption component contains English subtitles based on SMPTE-TT
  • the descriptor will have a scheme ID of "urn: atsc3.0: caption: 201x” and @value will each be "SMPTE-TT, ENG, , false, 4: 3, false ".
  • the parameters of @value may have a meaning according to the definition of the above-described parameters in order.
  • the closed caption related information may be signaled together by the aforementioned method together with the above-described HEVC video data related information. have.
  • FIG. 30 is a diagram illustrating HDR information according to an embodiment of the present invention.
  • the HDR information may include HDR parameter information related thereto.
  • the HDR information may have the form of one of the descriptors according to the above-described embodiment or may have the form of an element. This may be represented by the aforementioned componentProperty element or ComponentDescription element.
  • the HDR information may be defined in the form of a descriptor.
  • @schemeIdUri may be a URI for identifying that the descriptor has an HDR scheme related to the HDR information.
  • @schemeIdUri may have a value of urn: atsc3.0: hdr: 201x.
  • @value can have values whose meaning is defined according to the HDR scheme. This value will be described later.
  • @id may represent an identifier of the descriptor. In the case of having the same identifier, the same scheme ID, value, and parameter may be included.
  • the illustrated embodiment t32010 may represent each parameter of the aforementioned @value.
  • OETF_type may indicate the type of source OETF (opto-electronic transfer function) of the video data. When the value of this field is 1, 2, or 3, it may correspond to the ITU-R BT.1886, ITU-R BT.709, and ITU-R BT.2020 types, respectively. Other values can be left for future use.
  • max_mastering_display_luminance may indicate a peak luminance value of a mastering display of corresponding video data. This value can be an integer value between 100 and 1000.
  • min_mastering_display_luminance may indicate a minimum luminance value of a mastering display of corresponding video data. This value may be a fractional number value between 0 and 0.1.
  • average_frame_luminance_level may indicate an average value of luminance level for one video sample.
  • this field may indicate a maximum value among average values of luminance levels of each sample belonging to the sample group or the video track (stream).
  • max_frame_pixel_luminance may indicate the maximum value of pixel luminance values for one video sample.
  • this field may indicate the largest value among pixel luminance maximum values of each sample belonging to the sample group or the video track (stream).
  • the hdr_type_transition_flag may be a flag indicating whether the HDR information of the corresponding video data is changed to apply another type of HDR information. For example, if the HDR parameters from oeft: 3, max_lum: 100, min_lum: 0.5, max_frame_lum: 0, max_pixel_lum: 0 are changed to oeft: 1, max_lum: 1000, min_lum: 0.05, max_frame_lum: 0, max_pixel_lum: 0, This field may have a value of true.
  • the hdr_sdr_transition_flag may be a flag indicating whether corresponding video data is switched from HDR to SDR.
  • sdr_hdr_transition_flag may be a flag indicating whether corresponding video data is switched from SDR to HDR.
  • sdr_compatibility_flag may be a flag indicating whether corresponding video data is compatible with an SDR decoder or an SDR display.
  • the HDR information may be defined in the form of an HDR element having each of the above-described parameters of @value as a subfield.
  • the HDR information may be defined in the form of a descriptor.
  • This descriptor may be included in the MMT signaling information and delivered as described above.
  • This descriptor may be delivered included in the aforementioned MPT message or other MMTP message.
  • This descriptor may be a kind of asset descriptor.
  • these descriptors may be delivered together with or included in DVB SI service signaling such as SDT or EIT.
  • OETF_type max_mastering_display_luminance, min_mastering_display_luminance, average_frame_luminance_level, max_frame_pixel_luminance, hdr_type_transition_flag, hdr_sdr_transition_flag, sdr_hdr_transition_flag, and / or sdr_compatibility_flag may be included in the disc, which means that the discs can be used.
  • one or more HDRTypeTransitionFlag, HDRSDRTransitionFlag, and SDRHDRTransitionFlag may not be true at the same time.
  • the HDRSDRTransitionFlag value is true
  • the HDRTypeTransitionFlag and SDRHDRTransitionFlag values may be false.
  • FIG. 31 is a diagram illustrating WCG information according to an embodiment of the present invention.
  • the WCG information may include WCG information related thereto.
  • the WCG information may have the form of one of the descriptors according to the above-described embodiment or may have the form of an element. This may be represented by the aforementioned componentProperty element or ComponentDescription element.
  • the WCG information may be called color gamut information.
  • color gamut information There are two types of color gamut information, one is the container color gamut and the other is called the content color gamut.
  • the container color gamut may include color gamut related information used in encoding, decoding, and / or mapping decoded pixel values.
  • the content color gamut may include information on color gamut of an original source. That is, the content color gamut may represent a valid color space volume applied to the actual content.
  • the content WCG information may be defined in the form of a descriptor.
  • @schemeIdUri may be a URI for identifying that the descriptor has a content WCG scheme related to the content WCG information.
  • @schemeIdUri may have a value of urn: atsc3.0: wcg: content: 201x.
  • @value may have values whose meaning is defined according to the content WCG scheme. This value will be described later.
  • @id may represent an identifier of the descriptor. In the case of having the same identifier, the same scheme ID, value, and parameter may be included.
  • the illustrated embodiment t33010 may represent each parameter of the aforementioned @value.
  • contentColorGamutType may indicate the type of color gamut for the corresponding video data.
  • this field may indicate chromaticity coordinates of source primaries.
  • This value may be equal to the color primaries value of the video usability information (VUI). If the value of the VUI parameter does not exist, the color primary values of the VUI are unspecified and the following eight parameters may have a value.
  • contentColorPrimaryRx and contentColorPrimaryRy may each represent an x coordinate and y coordinate value for the R-color of the corresponding video source. This may be in the form of a fractional number between 0 and 1.
  • contentColorPrimaryGx and contentColorPrimaryGy may each represent an x coordinate and y coordinate value for the G-color of the corresponding video source. This may be in the form of a fractional number between 0 and 1.
  • contentColorPrimaryBx and contentColorPrimaryBy may represent x and y coordinate values for the B-color of the corresponding video source, respectively. This may be in the form of a fractional number between 0 and 1.
  • contentWhitePx and contentWhitePy may each indicate an x coordinate and y coordinate value with respect to a white point of a corresponding video source. This may be in the form of a fractional number between 0 and 1.
  • contentWCGTransition may be a flag indicating whether the content color gamut of the corresponding video data is converted from wide color gamut (WCG) to standard color gamut (SCG). According to an embodiment, it may be indicated that an end of video data supporting WCG is included in a corresponding video component.
  • contentSCGCompatibility may be a flag indicating whether the content color gamut of the corresponding WCG video is compatible with an SCG-based decoder or display.
  • the container WCG information may be defined in the form of a descriptor.
  • @schemeIdUri may be a URI for identifying that the descriptor has a container WCG scheme related to the container WCG information.
  • @schemeIdUri may have a value of urn: atsc3.0: wcg: container: 201x.
  • @value can have values whose meaning is defined according to the container WCG scheme. This value will be described later.
  • @id may represent an identifier of the descriptor. In the case of having the same identifier, the same scheme ID, value, and parameter may be included.
  • the illustrated embodiment t33020 may represent each parameter of the aforementioned @value. These parameters may be the same as the parameters for the content color gamut described above. However, these parameters can describe container color gamut.
  • containerColorGamutType may indicate the container color gamut type of the video. That is, it can refer to chromaticity coordination for color primers used at the time of encoding or at the time of decoding.
  • containerColorPrimaryRx, containerColorPrimaryRy, containerColorPrimaryGx, containerColorPrimaryGy, containerColorPrimaryBx, containerColorPrimaryBy, containerWhitePx, and containerWhitePy may each indicate an RGB color of a color primitive that can be used / used during encoding / decoding, and an x and y coordinate of a white point. That is, the coordinates of the color gamut of the container may be indicated.
  • containerWCGTransition may be a flag indicating whether a container color gamut of corresponding video data is switched from WCG to SCG. According to an embodiment, it may indicate that the end of video data supporting the WCG of the container is included in the corresponding video component.
  • containerSCGCompatibility may be a flag indicating whether the container color gamut of the corresponding WCG video is compatible with an SCG-based decoder or display.
  • the content / container WCG information may be defined in the form of a content / container WCG element having each of the above-described parameters of @value as a subfield.
  • the content / container WCG information may be defined in the form of a descriptor.
  • This descriptor may be included in the MMT signaling information and delivered as described above.
  • This descriptor may be delivered included in the aforementioned MPT message or other MMTP message.
  • a descriptor shown as an asset descriptor may be included.
  • this descriptor may be delivered by being included in the DVB SI service signaling such as SDT or EIT or together.
  • the descriptor t33030 may also include content WCG information and container WCG information.
  • the color_gamut_type may be the same as the containerColorGamutType described above.
  • the color_space_transition_flag may be a flag indicating, for video samples of the corresponding video component, whether the chromaticity coordination for color primaries used in encoding / decoding is changed to another chromaticity coordinate.
  • wcg_scg_transition_flag may be a flag indicating whether a container color gamut of video samples of a corresponding video component is switched from WCG to SCG. For example, it may indicate whether the container color gamut is changed from BT.2020 to BT.709.
  • scg_wcg_transition_flag may be a flag indicating whether a container color gamut of video samples of a corresponding video component is switched from SCG to WCG.
  • scg_compatibility_flag may be a flag indicating whether a container color gamut of video samples of a corresponding video component is compatible with an SCG based decoder or display. That is, in the case where an existing SCG decoder or display is used, it is possible to check whether this WCG video can be output without a quality problem without additional mapping information or upgrade due to this field. Therefore, this field may indicate whether the video data can be decoded even if the SCG-based decoder / display does not know the color gamut such as BT.2020.
  • the color_primary_flag may be a flag indicating whether or not there is detailed information on chromaticity coordination of color primerless that can be used in encoding / decoding video samples of the corresponding video component.
  • the color_primaryRx field, color_primaryRy field, color_primaryGx field, color_primaryGy field, color_primaryBx field, color_primaryBy field, color_whitePx field and / or color_whitePy field may be included according to the value of color_primary_flag. These fields may indicate the RGB color of the color primerless and the x and y coordinates of the white point, respectively, which may be used / used in encoding / decoding.
  • content_wcg_flag may indicate whether detailed information about content color gamut is included in a corresponding descriptor for a corresponding video component.
  • content_color_gamut_type may indicate the content color gamut type of the corresponding video stream. That is, this field may indicate chromaticity coordination with respect to the original source primary of the video data.
  • content_color_space_transition_flag may be a flag indicating, for the original source primers of video data of the corresponding video component, whether the chromaticity coordination of these changes to another chromaticity coordination.
  • content_wcg_scg_transition_flag may be a flag indicating whether content color gamut of video data of a corresponding video component is switched from WCG to SCG.
  • the content_scg_wcg_transition_flag field may be a flag indicating whether content color gamut of video data of a corresponding video component is switched from SCG to WCG.
  • the content_scg_compatibility_flag field may be a flag indicating whether the content color gamut of video data of the corresponding video component is compatible with an SCG based decoder or display. That is, when the value of this field is 1, it may represent that the effective color expression range of the corresponding video data is SCG compatible and no separate mapping is required.
  • the content_color_primary_flag field may be a flag indicating whether detailed information about the chromaticity coordination of the original source primary of video data of the corresponding video component exists.
  • the content_color_primaryRx field, content_color_primaryRy field, content_color_primaryGx field, content_color_primaryGy field, content_color_primaryBx field, content_color_primaryBy field, content_color_whitePx field and / or content_color_whitePy field may be included. These fields may indicate the RGB color of the original source primerless and the x and y coordinates of the white point, respectively.
  • color_gamut_type and / or content_color_gamut_type may have the following meanings.
  • the HFR information may include HFR information related to the corresponding video service component when it supports HFR.
  • the HFR information may have the form of one of the descriptors according to the above-described embodiment or may have the form of an element. This may be represented by the aforementioned componentProperty element or ComponentDescription element. As described above, the HFR information may be included in the MPD and the like.
  • the HFR information may be defined in the form of a descriptor.
  • @schemeIdUri may be a URI for identifying that the descriptor has an HFR scheme related to the HFR information.
  • @schemeIdUri may have a value of urn: atsc3.0: hfr: 201x.
  • @value can have values whose meaning is defined according to the HFR scheme. This value will be described later.
  • @id may represent an identifier of the descriptor. In the case of having the same identifier, the same scheme ID, value, and parameter may be included.
  • the illustrated embodiment t34010 may represent each parameter of the aforementioned @value.
  • SFRCompatibility may indicate whether a corresponding video component is compatible with a standard frame rate (SFR) or a legacy frame rate.
  • SFR_HFR_Transition may indicate whether the corresponding video component includes a transition from the general frame rate (SFR or legacy frame rate) to the HFR.
  • HFR_SFR_Transition may indicate whether the corresponding video component includes a transition from HFR to a general frame rate (SFR or legacy frame rate).
  • the pull down information may include pull down recovery configuration information on a corresponding service component.
  • Pull-down information may have the form of one of the descriptors according to the above-described embodiment, or may have the form of an element. This may be represented by the aforementioned componentProperty element or ComponentDescription element.
  • This section describes the pull-down recovery configuration.
  • the original source is film mode (e.g. 24p)
  • it can be changed to a different frame rate for encoding (e.g. 60i).
  • dirty frames may be generated.
  • the dirty frame can be generated in the following manner.
  • All original film frames can be considered to consist of two fields. One may be for odd-numbered lines of the image and the other may be for even-numbered lines of the image. Thus, there may be eight fields every four film frames. Here, four film frames may be referred to as A, B, C, and D, respectively. These eight fields can be stretched to ten fields. This can be done by repeating two fields (top, bottom).
  • a frame can be crossed across three fields (At, Ab, Ab), B frame can span two fields (Bt, Bb), C frame can span three fields, (Ct, Ct, Cb), B frames may span two fields (Dt, Db).
  • B frame can span two fields (Bt, Bb)
  • C frame can span three fields
  • B frames may span two fields (Dt, Db).
  • At may mean the top field of the A frame
  • Bb may mean the bottom field of the B frame.
  • Ab-Bt frame and Bb-Ct frame may be called dirty frames.
  • the receiver can know the original frame rate through the pull down recovery configuration.
  • the receiver can recover the original frame rate stream from the encoded / transmitted frame rate stream.
  • the recovery may be a process of eliminating dirty frames.
  • Pull down may be a term used in connection with a post production process for the delivery of film or video, such as in filmmaking / TV production.
  • the film frame rate can be converted to the broadcast frame rate by the broadcaster.
  • the system level frame rate related information may include only broadcast frame rate information. Therefore, to recover the original frame rate, system level signaling may need to be able to signal information related to the original frame rate.
  • the original frame rate (e.g. 24p) information and / or pulldown type information e.g. 3: 2 pulldown
  • the video level information of the pulled down video may request restoration to the original video.
  • the pulldown information may be defined in the form of a descriptor.
  • @schemeIdUri may be a URI for identifying that the descriptor has a pulldown scheme related to the pulldown information.
  • @schemeIdUri may have a value of urn: atsc3.0: pulldown: 201x.
  • @value can have values whose meaning is defined according to the pulldown scheme. This value will be described later.
  • @id may represent an identifier of the descriptor. In the case of having the same identifier, the same scheme ID, value, and parameter may be included.
  • the illustrated embodiment t34020 may represent each parameter of the aforementioned @value.
  • PullDownType may indicate the type of pulldown applied to the corresponding encoded video stream. Can be represented as a non-negative decimal integer. This field is 0-reserved, 1-2: 2 pull-down, 2-2: 3 pull down, 3- 3: 2 pull-down, 4-4: 4 pull-down, 5-5 : 5 pull-down, 6-6: 4 pull-down,. , Etc. can be indicated.
  • PullDownTransition may indicate whether a transition from the pulled down data to the original frame rate is included in the corresponding video component. According to an embodiment, this field may indicate whether the end of the pulled down data is included in the corresponding video component.
  • OriginalFrameRate may indicate an original frame rate (captured frame rate) of corresponding video data.
  • This field may be expressed as a non-negative decimal integer. This information can be provided to perform recovery from the encoding frame rate to the original frame rate. This field is based on its value: 0- reserved, 1- 120, 2- 120 / 1.001, 3- 100, 4- 60, 5- 60 / 1.001, 6-50, 7-30, 8-30 / 1.001, Original frame rates such as 9-25, 10-24, 11-24 / 1.001, 12-14-reserved, etc. may be indicated.
  • OriginalScanType may indicate the scanning type of the original video corresponding to the video. This field may be expressed as a non-negative decimal integer. This field may indicate a type such as 0-reserved, 1-interlaced, 2-progressive, 3-unspecified, etc. according to the value.
  • the pulldown information may be defined in the form of a pulldown element having each of the above-described parameters of @value as a subfield.
  • the HFR information & pulldown information may be defined in the form of a descriptor.
  • This descriptor may be included in the MMT signaling information and delivered as described above. This descriptor may be delivered included in the aforementioned MPT message or other MMTP message.
  • a descriptor shown as an asset descriptor may be included.
  • this descriptor may be delivered by being included in the DVB SI service signaling such as SDT or EIT or together.
  • This descriptor t34030 may include HFR information & pulldown information together.
  • sfr_compatibility_flag, sfr_hfr_transition_flag, hfr_sfr_transition_flag, pull_down_type, pull_down_transition_flag, original_framerate and / or original_scan_type may be the same as the above-described SFRCompatibility, SFR_HFR_Transition, HFR_SFR_Transition, PullDownType, OriginalDownTransition original_framerate_flag may indicate whether the original_framerate field exists in the descriptor.
  • original_scane_type_flag may indicate whether the original_scane_type field exists in the corresponding descriptor.
  • the MMT asset may include a view position descriptor (view_position_descriptor, d33010) as an asset_descriptor in the MP_table.
  • the view position descriptor (view_position_descriptor) may include stereoscopic 3D parameter information and the like. This may be included in another signaling table of MMT or SI (SDT or EIT) of DVB.
  • the view position descriptor may include at least one of the following fields.
  • the descriptor_tag field may be an identifier for the view position descriptor (view_position_descriptor).
  • the descriptor_length field may indicate the length of the view position descriptor (view_position_descriptor).
  • the right_view_flag field may indicate whether a component of the video stream is a right view component. When the field value is 0, it may represent that a component of the corresponding video stream is a left view component, and when the field value is 1, it may represent a right view component.
  • the MMT asset may include a view position descriptor (view_position2_descriptor, d33020) as an asset_descriptor in the MP_table.
  • the view position descriptor (view_position2_descriptor) may include multiview parameter information and the like.
  • the view position descriptor (view_position2_descriptor) also includes dependency information between components. This may be included in another signaling table of MMT or SI (SDT or EIT) of DVB.
  • the view position descriptor view_position2_descriptor may include at least one of the following fields.
  • the descriptor_tag field may be an identifier for the view position descriptor (view_position2_descriptor).
  • the descriptor_length field may indicate the length of the corresponding view position descriptor (view_position2_descriptor).
  • the num_of_views field may mean the total number of views included in the corresponding view position descriptor (view_position2_descriptor). That is, the total number of views provided by the multiview service may be indicated.
  • the view_position field may mean view position information of a corresponding video component.
  • the view point location information may be set to 0 with respect to the first view located at the leftmost side of the multi view.
  • the view point position information may be set to a value that is increased by one each time it is moved from the first view to the next view from left to right.
  • the view position means the order for the left-most view being equal to 0 and the value of the order increasing by 1 for next view from left to right.
  • Multiview is a 3D Multiview or Panorama It may be a multiview for the panorama.
  • the above-described view position information may include a meaning of a left view or a right view for each view. That is, from view position information expressed as a number, it may be determined whether a view included in a corresponding component is a left view or a right view for providing a 3D service.
  • FIG. 34 is a diagram illustrating a media engine operation of a receiver based on HDR information processing capability according to an embodiment of the present invention.
  • the parser of the receiver may parse ISOBMFF based media files, DASH segments and / or MMT MPUs. According to the parsing result, video samples may be delivered to a video decoder, and HDR information (metadata) may be delivered to a metadata parser.
  • the video decoder may decode video samples to obtain HDR video data. If there is HDR information acquired in this process, it can be delivered to the metadata parser.
  • the signaling processor may extract HDR metadata from them and deliver it to the metadata parser.
  • the metadata parser may parse the received HDR metadata. Control information necessary for the video decoder may be transmitted to the video decoder using the obtained metadata.
  • the metadata parser may serve as a buffer or metadata update. The update may be performed using set_number, version_number, and the like.
  • the number of cases can be divided depending on whether the receiver is capable of HDR display. If display of the HDR video is impossible, the HDR video data may be transferred to the SDR display block via HDR-SDR conversion.
  • the SDR display block is a hardware block that can receive and play the converted SDR video. At this time, the information received from the metadata parser may be used for conversion.
  • quality enhancement may be performed on the HDR video.
  • quality enhancement may be performed using common HDR information (dynamic range, transfer function, color gamut, color temperature, DR / CG mapping, viewing condition, etc.) received from the metadata parser.
  • the number of cases can be divided depending on the case where the receiver can process scene / frame metadata.
  • the HDR display block of the receiver may play the received HDR video data.
  • scene-by-scene HDR video quality enhancement may be performed.
  • quality enhancement may be performed using scene / frame HDR metadata (While levels, Black levels, frame-by-frame, DR / CG mapping, etc.) received from the metadata parser.
  • the HDR display block of the receiver can reproduce the enhanced HDR video data.
  • the HDR display block can be a hardware block.
  • the timing converter can deliver time-related information to a metadata parser, synchronizer, and the like.
  • the synchronizer may provide information necessary for the new HDR video quality enhancement operation by using information such as sync_start and sync_duration.
  • 35 is a diagram illustrating a media engine operation of a receiver based on WCG information processing capability according to an embodiment of the present invention.
  • the parser of the receiver may parse ISOBMFF based media files, DASH segments and / or MMT MPUs. According to the parsing result, WCG video samples may be delivered to a video decoder, and color gamut information (metadata) may be delivered to a metadata parser.
  • the video decoder may decode video samples to obtain WCG video data. If there is color gamut related information obtained in this process, it can be delivered to the metadata parser.
  • the signaling processor may extract color gamut metadata from these and deliver the color gamut metadata to the metadata parser.
  • the metadata parser can parse the received color gamut metadata.
  • the container / content color gamut information obtained here may be utilized in the receiver process.
  • the metadata parser may serve as a buffer or metadata update. The update may be performed using set_number, version_number, and the like.
  • the number of cases may be divided according to whether the content color gamut information is included in the received data. If the content color gamut information is not included, the receiver may determine whether the display color gamut is greater than or equal to the container color gamut. If the display color gamut is greater than or equal to the container color gamut, the receiver may provide a full WCG display. If the display color gamut is smaller than the container color gamut, the receiver may perform gamut mapping from the container color gamut to the display color gamut. The receiver may then provide an SCG display or a partial WCG display. In this process, the common container color gamut related information received from the metadata parser may be used.
  • the receiver may determine whether the display color gamut is greater than or equal to the content color gamut. If the display color gamut is greater than or equal to the content color gamut, the receiver may provide a full WCG display. If the display color gamut is smaller than the content color gamut, the receiver may perform gamut mapping from the content color gamut to the display color gamut. The receiver may then provide an SCG display or a partial WCG display. In this process, the common content color gamut related information received from the metadata parser may be used.
  • FIG. 36 illustrates a media engine operation of a receiver based on HFR information processing capability according to an embodiment of the present invention.
  • the parser of the receiver may parse ISOBMFF based media files, DASH segments and / or MMT MPUs.
  • HFR video data may be obtained according to the parsing result.
  • the signaling processor may extract HFR metadata from them and forward it to the metadata parser.
  • the metadata parser may parse the delivered HFR metadata.
  • the HFR information obtained here may be utilized in the receiver processing.
  • the metadata parser may serve as a buffer or metadata update. The update may be performed using set_number, version_number, and the like.
  • HFR video data if HFR decoding / display can be performed, the HFR video data can be passed to a video decoder.
  • the HFR video decoder can decode video samples.
  • HFR metadata if HFR metadata is obtained, it may be delivered to the metadata parser.
  • the HFR video decoder delivers the decoded data to the HFR display, which can display it.
  • HFR decoding / display cannot be performed, compatibility with SFR can be checked. If SFRCompatibility has a value of 1, it is compatible and frame rate conversion can be performed.
  • the data after conversion can be delivered to an SFR or legacy video decoder.
  • HFR metadata can be received from the metadata parser and used.
  • HFR metadata is acquired in the video decoding process, it may be delivered to the metadata parser.
  • the video decoder can pass this to the legacy display. This video data may be video data converted at the original frame rate.
  • the legacy display can display this.
  • FIG. 37 illustrates a media engine operation of a receiver based on pulldown recovery information processing capability according to an embodiment of the present invention.
  • the parser of the receiver may parse ISOBMFF based media files, DASH segments and / or MMT MPUs. Depending on the result of parsing, the video samples may be delivered to the video decoder and decoded.
  • the signaling processor may extract pull-down recovery related metadata from them and deliver the metadata to the metadata parser.
  • the metadata parser may parse the received pulldown recovery related metadata.
  • the pulldown recovery-related information obtained here may be utilized in the receiver processing.
  • the metadata parser may serve as a buffer or metadata update. The update may be performed using set_number, version_number, and the like.
  • the receiver may check PullDownFlag to check whether the decoded video is a pulled down video.
  • the receiver may recover the original FR stream using information such as a pulled down type. In this process, information related to the pull down recovery of the metadata parser may be utilized. If the video is not pulled down, this process may not be performed.
  • the recovered source FR video or decoded video data can be transferred to a display and displayed.
  • the video data may include an SEI message including metadata for supporting 3D service.
  • a compression format for reference view video and additional view video constituting content supporting 3D service may be HD or UHD.
  • the reference view video and the national view video may have the same aspect ratio with respect to the active area. If the aspect ratios of the left picture and right picture constituting the 3D service are not exactly the same, the smaller input images may be letter boxed or pillar boxed. Can be.
  • the letter box may mean adjusting the screen ratio by placing black bars or the like on the upper and lower sides of the target image.
  • the filler box may mean adjusting the screen ratio by placing black bars on the left and right sides of the target image. This operation can be performed prior to compression and can cause two views to have the same aspect ratio in the active area.
  • the presence of bars embedded in the above-described image may be indicated by an Active Format Description (AFD).
  • the presence of bars may also optionally be indicated by bar data information.
  • the frame rate of the local view video may be a value obtained by dividing the frame rate of the reference view video by an integer of 1 or more.
  • the embodiment d38010 illustrated at the top of the figure may indicate a multiview view position SEI message.
  • the SEI message may be included in the video data and transmitted together.
  • the SEI message may indicate a left view and a right view of the stereoscopic video carried by Scalable High Efficiency Video Coding (SHVC).
  • SHVC Scalable High Efficiency Video Coding
  • the multiview view position SEI message may be identified by payload type information having a value of 180.
  • a multiview view position SEI message may include a num_views_minus1 field and view_position [i] information.
  • the num_views_minus1 field may indicate the number of views included in the multiview service. According to an embodiment, the num_views_minus1 field may indicate a number less than 1 than the number of views included in the multiview service.
  • the SEI message may include view_position [i] information for each view. For a fixed & mobile hybrid 3D service, view_position [i] information in the SEI message can indicate the order of the view having the same dependency ID as i.
  • This view may be one of the views in order from left to right for display.
  • the order of views may mean values of the order in which the view located at the leftmost side is 0, and increases by 1 as one moves from there to the right.
  • view_position [0] may be 1
  • view_position [1] may be 0.
  • the base layer video having the dependency ID 0 is a right view
  • the view position information of the base layer video may be set to '1'.
  • the embodiment d38020 illustrated at the bottom of the figure may indicate a multiview scene position SEI message.
  • the SEI message may be included in the video data and transmitted together.
  • the SEI message may include min_disparity information and / or max_disparity_range information.
  • Multiview scene position SEI message may be identified by payloadType information.
  • Multiview scene position SEI messages can be used to process the decoded views prior to rendering the image to the 3D display.
  • Minimum disparity may indicate the three-dimensional location of the front-most object in the video. In order to render receiver-generated graphics ahead of the decoded views, such as on-screen display (OSD), the minimum disparity is
  • Multiview scene position may be included in the SEI message. That is, the receiver generates the receiver in front of the position where the corresponding video data is displayed by using the minimum disparity information included in the multiview scene position SEI message among the SEI messages in the video data. Can display graphical information.
  • each SEI message may further include a dependency code.
  • the information on the bar may be included in the video data as an SEI message and transmitted.
  • the information on the bar may be included in the DVB SI service signaling such as SDT or EIT or transmitted together as a separate table or descriptor.
  • the information on the bar may include at least one of the following information.
  • the top_bar_flag field may indicate whether a bar exists above the displayed screen.
  • the bottom_bar_flag field may indicate whether a bar exists at the bottom of the displayed screen.
  • the left_bar_flag field may indicate whether a bar exists on the left side of the displayed screen.
  • the right_bar_flag field may indicate whether a bar exists on the right side of the displayed screen.
  • the marker_bits field and the line_number_end_of_top_bar field may be included in the metadata of the bar.
  • the line_number_end_of_top_bar field may define the last line number of the top bar. That is, the top bar may have a size from the top of the screen to the line defined by the line_number_end_of_top_bar field.
  • the marker_bits field and the line_number_start_of_bottom_bar field may be included in the metadata of the bar.
  • the line_number_start_of_bottom_bar field may define the starting line number of the bottom bar. That is, the bottom bar may have a size from the line defined by the line_number_start_of_bottom_bar field to the bottom of the screen.
  • the left_bar_flag field is set to 1, that is, when a bar exists on the left side of the screen, the marker_bits field and the pixel_number_ end_of_left_bar field may be included in the metadata of the bar.
  • the pixel_number_end_of_left_bar field may define the last pixel number of the left bar. That is, the left bar may have a size from the left side of the screen to the pixel defined by the pixel_number_end_of_left_bar field.
  • the marker_bits field and the pixel_number_start_of_right_bar field may be included in the metadata of the bar.
  • the pixel_number_start_of_right_bar field may define the starting pixel number of the right bar. That is, the right bar may have a size from the pixel defined by the pixel_number_start_of_right_bar field to the right side of the screen.
  • additional_bar_data may be further included. Using the above-described fields, the information on the bar may describe the size of the bar displayed on the screen.
  • the size of letter box bars may be indicated by the line_number_end_of_top_bar field and the line_number_start_of_bottom_bar field as described above.
  • the size of pillar box bars may be indicated by the pixel_number_end_of_left_bar field and the pixel_number_start_of_right_bar field as described above.
  • these fields are written based on the original source format. That is, since the line and pixel values based on the format at the time of production of the video content, the meaning of the value may vary depending on the reception situation. That is, a case in which the video format transmitted from the transmitter or the video format encoded at the transmitter may be different from the original source format.
  • the video content is resized for transmission.
  • the interpretation of the information about the bar at the receiving end can be ambiguous. This is because the information for the bar is a value based on the original source format, whereas the content has a changed format.
  • Information about the original source format may be included as an SEI message in the video data and transmitted.
  • the information about the original source format may be included in a DVB SI service signaling such as SDT or EIT or transmitted together as a separate table or descriptor.
  • the information about the original source format may include at least one of the following information.
  • the identical_format_flag field may indicate whether a compression format and a production format are the same. It can be signaled as 1 if the compression flag and the production format are the same, and as 0 in other cases. In this case, the production format may mean an original source format.
  • the org_spatial_resolution field may signal the actual spatial resolution captured by the production stage.
  • the resolution according to each field value may be as follows. 0x0: unspecified; 0x1: 3840 x 2160; 0x2: 2160 x 1440; 0x3: 1920 x 1080; 0x4: 1280 x 720; 0x5: 960 x 540; 0x6: 640 x 360; 0x7: customized.
  • the org_frame_rate field may signal the actual frame rate photographed at the production stage.
  • the scanning_format field may signal whether the scanning format is interlaced or progressive.
  • the scanning format according to each field value may be as follows. 00: unspecified, 01: progressive, 10: interlaced, 11: reserved.
  • the org_horizontal_size_div_8 field and the org_vertical_size_div_8 field may signal a case where the org_horizontal_size_div_8 field is not a pre-defined format in the actual spatial resolution photographed at the production stage. In other words, rather than signaling a preset value, it represents the horizontal and vertical resolution values of the actual production format. The actual horizontal and vertical resolutions may be multiplied by 8 for each field value. In this way, the information on the original source format may be used as information that can reflect the original intent.
  • the emission format transmitted by the broadcast system is the same as the production format.
  • the resolution of the emission format ie, encoded video
  • the resolution of the production format i.e., the original source video
  • the identical_format_flag field included in the above information about the original source format may be set to 1.
  • the top_bar_flag field and the bottom_bar_flag field may be set to 1 to indicate that a letter box using an upper bar (top bar) and a lower bar (bottom bar) is generated.
  • the line_number_end_of_top_bar field may have an A value
  • the line_number_start_of_bottom_bar field may have a B value.
  • the top bar may have a vertical size of A + 1.
  • the horizontal size of the top bar can be the same as the horizontal size of the production format.
  • the bottom bar may also have a vertical size of V-B.
  • V can represent the vertical size of the production format. That is, since the production format is 3840 * 2160, V may have a value of 2160, and the bottom bar may have a vertical size of 2160-B.
  • the horizontal size of the bottom bar can be the same as the horizontal size of the emission format or the production format.
  • the broadcast reception device may apply the information included in the bar_data to the emission format as it is to calculate the letter box size and generate the letter box.
  • the area excluding the letter box generated in the display of the broadcast reception device may be an active image area.
  • the emission format transmitted by the broadcasting system is smaller than the production format (d42010).
  • the resolution of the emission format, ie, encoded video may be 1920 * 1080.
  • the resolution of the production format, i.e., the original source video may be greater than 3840 * 2160.
  • the identical_format_flag field included in the above information about the original source format may be set to zero.
  • the top_bar_flag field and the bottom_bar_flag field may be set to 1 to indicate that a letter box using an upper bar (top bar) and a lower bar (bottom bar) is generated.
  • the line_number_end_of_top_bar field may have an A value
  • the line_number_start_of_bottom_bar field may have a B value.
  • the top bar may have a vertical size of (A + 1) / R. Where R is the ratio between the emission format and the production format. In an embodiment the production format (3840 * 2160) is twice the size of the emission format (1920 * 1080), so the R value can be two.
  • R may mean a value obtained by dividing V, which is the vertical size of the production format, by the vertical size of the emission format. Also in this case, the R value is 2.
  • the horizontal size of the top bar may be the same as the horizontal size of the emission format.
  • the bottom bar can also have a vertical size of (V-B) / R.
  • V can represent the vertical size of the production format. That is, since the production format is 3840 * 2160, V may have a value of 2160, and the bottom bar may have a vertical size of (2160-B) / 2.
  • the horizontal size of the bottom bar may be the same as the horizontal size of the emission format.
  • the broadcast reception device when the production format is larger than the emission format, the broadcast reception device applies the information contained in the bar_data to the production format, and scales the bar according to the ratio between the production format and the emission format to generate the bar and generate the bar. can do. That is, the broadcast reception device may check the size of the bar in the emission format and generate the letter box through scaling by using the information on the original source format received together with the information on the bar.
  • the area excluding the letter box generated in the display of the broadcast reception device may be an active image area.
  • the emission format transmitted by the broadcasting system is larger than the production format (d42020).
  • the resolution of the emission format, ie, encoded video may be 1920 * 1080.
  • the resolution of the production format, i.e., the original source video may be less than 1280 * 720.
  • the identical_format_flag field included in the above information about the original source format may be set to zero.
  • the top_bar_flag field and the bottom_bar_flag field may be set to 1 to indicate that a letter box using an upper bar (top bar) and a lower bar (bottom bar) is generated.
  • the line_number_end_of_top_bar field may have an A value
  • the line_number_start_of_bottom_bar field may have a B value.
  • the top bar may have a vertical size of (A + 1) * F.
  • F is the ratio between the emission format and the production format.
  • the emission format 1920 * 1080 has a size 1.5 times that of the production format 1280 * 720, so the F value may be 1.5.
  • F may mean a value obtained by dividing the vertical size of the emission format by V, which is the vertical size of the production format. In this case, the F value is 1.5.
  • the horizontal size of the top bar may be the same as the horizontal size of the emission format.
  • the bottom bar can also have a vertical size of (V-B) * F.
  • V can represent the vertical size of the production format. That is, since the production format is 1280 * 720, V may have a value of 720, and the bottom bar may have a vertical size of (720-B) * 1.5.
  • the horizontal size of the bottom bar may be the same as the horizontal size of the emission format.
  • the broadcast receiving device applies the information contained in the bar_data to the production format, and scales it according to the ratio between the production format and the emission format to determine the size of the bar and generate the bar. can do.
  • the broadcast reception device may check the size of the bar in the emission format and generate the letter box through scaling by using the information on the original source format received together with the information on the bar.
  • the area excluding the letter box generated in the display of the broadcast reception device may be an active image area.
  • FIG. 43 illustrates a method of generating a pillar box using bar data according to an embodiment of the present invention.
  • the emission format transmitted by the broadcast system is the same as the production format.
  • the resolution of the emission format, ie, encoded video may be 3840 * 2160.
  • the resolution of the production format, i.e., the original source video may equally be 3840 * 2160.
  • the identical_format_flag field included in the above information about the original source format may be set to 1.
  • the left_bar_flag field and the right_bar_flag field are set to 1 in the bar information (bar_data, d43010) to indicate that the pillar box using the left bar (left bar) and the right bar (right bar) is generated.
  • the pixel_number_end_of_left_bar field may have a C value
  • the pixel_number_start_of_right_bar field may have a D value.
  • the left bar may have a horizontal size of C + 1.
  • the vertical size of the left bar may be the same as the vertical size of the production format.
  • the right bar may also have a horizontal size of H-B.
  • H can represent the horizontal size of the production format. That is, since the production format is 3840 * 2160, H may have a value of 2160, and the right bar may have a horizontal size of 2160-D.
  • the vertical size of the right bar may be the same as the vertical size of the emission format or the production format.
  • the broadcast reception apparatus may apply the information included in the bar_data to the emission format as it is to calculate the size of the pillar box and generate the pillar box.
  • An area except the pillar box generated in the display of the broadcast reception device may be an active image area.
  • the emission format transmitted by the broadcasting system is smaller than the production format (d44010).
  • the resolution of the emission format, ie, encoded video may be 1920 * 1080.
  • the resolution of the production format, i.e., the original source video may be greater than 3840 * 2160.
  • the identical_format_flag field included in the above information about the original source format may be set to zero.
  • the left_bar_flag field and the right_bar_flag field are set to 1 in the bar information (bar_data, d43010) to indicate that the pillar box using the left bar (left bar) and the right bar (right bar) is generated.
  • the pixel_number_end_of_left_bar field may have a C value
  • the pixel_number_start_of_right_bar field may have a D value.
  • the left bar may have a horizontal size of (C + 1) / R. Where R is the ratio between the emission format and the production format.
  • the production format (3840 * 2160) is twice the size of the emission format (1920 * 1080), so the R value can be two.
  • R may mean a value obtained by dividing H, which is a horizontal size of the production format, by a horizontal size of the emission format.
  • the R value is 2.
  • the vertical size of the left bar may be the same as the vertical size of the emission format.
  • the right bar may also have a horizontal size of (H-D) / R.
  • H can represent the horizontal size of the production format. That is, since the production format is 3840 * 2160, H can have a value of 3840, and the right bar can have a horizontal size of (3840-B) / 2.
  • the vertical size of the right bar may be the same as the vertical size of the emission format.
  • the broadcast receiving device applies the information contained in the bar_data to the production format, and scales the bar according to the ratio between the production format and the emission format to generate the bar and generate the bar. can do. That is, the broadcast reception device may check the size of the bar in the emission format and generate the pillar box through scaling by using the information on the original source format received together with the information on the bar.
  • An area except the pillar box generated in the display of the broadcast reception device may be an active image area.
  • the emission format transmitted by the broadcasting system is larger than the production format (d44020).
  • the resolution of the emission format, ie, encoded video may be 1920 * 1080.
  • the resolution of the production format, i.e., the original source video may be less than 1280 * 720.
  • the identical_format_flag field included in the above information about the original source format may be set to zero.
  • the left_bar_flag field and the right_bar_flag field may be set to 1 to indicate that the pillar box using the left bar (left bar) and the right bar (right bar) is generated.
  • the pixel_number_end_of_left_bar field may have a C value
  • the pixel_number_start_of_right_bar field may have a D value.
  • the left bar may have a horizontal size of (C + 1) * F.
  • F is the ratio between the emission format and the production format.
  • the emission format 1920 * 1080 has a size 1.5 times that of the production format 1280 * 720, so the F value may be 1.5.
  • F may mean a value obtained by dividing the vertical size of the emission format by the vertical size of the production format. In this case, the F value is 1.5.
  • the vertical size of the left bar may be the same as the vertical size of the emission format.
  • the right bar can also have a horizontal size of (H-D) * F.
  • H can represent the horizontal size of the production format. That is, since the production format is 1280 * 720, H may have a value of 1280, and the right bar may have a horizontal size of (1280-D) * 1.5.
  • the vertical size of the right bar may be the same as the vertical size of the emission format.
  • the broadcast receiving device applies the information contained in the bar_data to the production format, and scales it according to the ratio between the production format and the emission format to determine the size of the bar and generate the bar. can do.
  • the broadcast reception device may check the size of the bar in the emission format and generate the pillar box through scaling by using the information on the original source format received together with the information on the bar.
  • An area except the pillar box generated in the display of the broadcast reception device may be an active image area.
  • 45 is a diagram illustrating a method for transmitting a broadcast signal according to an embodiment of the present invention.
  • a method for transmitting a broadcast signal includes generating service data and service signaling information (ds45010), generating a service list table (ds45020), and processing IP packets. Step (ds45030) and / or generating a broadcast signal, and may be transmitted through the broadcast network (ds45040).
  • the service data generator d46010 of the transmitting side may generate service data of a broadcast service and / or service signaling information signaling a broadcast service.
  • the service data may be a concept in which media data, NRT data, streaming data, and the like included in the broadcast service are collectively managed.
  • the service data may include service components of the corresponding service.
  • the service signaling information may correspond to the above-described SLS.
  • the service data generator is a block that generates data related to the actual service to provide a service at the service provider, and may be a hardware element.
  • the lower level signaling generator d46020 of the transmitting side may generate a service list table.
  • the service list table may correspond to the above-described SLT.
  • the service list table may include bootstrap information identifying a transport session to which service signaling information is delivered.
  • the bootstrap information is as described above.
  • the transport session may be an MMTP session and / or a ROUTE session, depending on the embodiment.
  • the low level signaling generator is a block that manages generation of LLS (Low Level Signaling) such as SLT, and may be a hardware element.
  • LLS Low Level Signaling
  • the transport layer processor d46030 of the transmitting side may process the generated service components, service signaling information, and / or service list table as IP packets. Prior to this, the data may be processed according to UDP.
  • the transport layer processor is a block responsible for processing data of a higher layer for transmission and may be a hardware element.
  • the physical layer processor d46040 of the transmitting side processes the generated IP packets to generate a broadcast signal, and transmits the broadcast signal through a broadcast network. In this process, other operations may be performed on the above-described link layer first, and upper layer data (IP packet, etc.) may be encapsulated into a link layer packet. Thereafter, the link layer packets may be processed as broadcast signals through encoding / interleaving processes according to operations defined in the physical layer. The generated broadcast signal may be transmitted through a broadcast network. According to an embodiment, the above-described data may be transmitted by broadband.
  • the physical layer processing unit is a block in charge of the above-described link layer and / or physical layer and may be a hardware element.
  • the service signaling information may include a USBD.
  • the USBD may operate as a signaling hub for describing technical information related to a broadcast service.
  • the USBD may further include service type information.
  • the service type information may mean the type of the final service provided by combining components described in the USBD.
  • the service type information may be stereoscopic 3D or multiview.
  • the service list table or the USBD may further include capability information.
  • This may mean various capability information included in the above-described SLT to USBD.
  • the capability information may describe at least one or more capabilities required to significantly present the broadcast service.
  • the capability information may be described using a predefined capability code.
  • the capability information may be described by a capability category code indicating a category of the capability.
  • the capability information may be described by combining a capability category code and a capability code indicating what capability information specifically refers to the category.
  • the capacity information is as described above.
  • the service signaling information when service signaling information of a broadcast service is delivered by an MMT protocol, the service signaling information further includes a signaling message including caption information for the broadcast service. can do.
  • signaling information may be delivered through the MMTP message.
  • various information multiview, caption, 3D, WCG, HDR, etc.
  • one MMTP message may simultaneously include a plurality of pieces of information.
  • the MPT message or another newly defined MMTP message may further include service type information.
  • the service type information may mean a type of the final service provided by combining assets described in the MPT message or another newly defined MMTP message.
  • the service type information may be stereoscopic 3D or multiview.
  • the caption information includes language information indicating the language of the caption of the broadcast service, role information indicating the role of the caption, aspect ratio information indicating the aspect ratio of the caption, and whether the caption is an easy reader caption.
  • Easy reader information indicating and / or 3D support information indicating whether or not the caption supports 3D (3-Dimensional) may be included.
  • the caption information is as described above.
  • the multiview information may be included in the MPD.
  • the signaling message may further include 3D related information about service components of the broadcast service.
  • the signaling message may mean one of the MMTP messages.
  • the 3D related information may include minimum disparity information between a view of the corresponding service component and adjacent images of the image and / or maximum disparity information between the corresponding image and the adjacent images.
  • the 3D information is as described above.
  • the 3D related information may further include view position information indicating an order of a view of the corresponding service component.
  • the view position information may be delivered through another MMTP message or an MPD.
  • the view position information delivered through the MPD may include right view flag for each component in relation to the 3D service. This may indicate whether the corresponding component is a right view or a left view.
  • the view position information transmitted through the MPD may include view position information of each component in relation to the multi-view service.
  • the multiview service may mean 3D multiview or panoramic multiview.
  • the view position information may indicate a left view or a right view.
  • the MMT asset may include a view position descriptor as an asset _descriptor in the MP table.
  • the view position information transmitted through the view position descriptor may include right view flag for each component in relation to the 3D service. This may indicate whether the corresponding component is a right view or a left view.
  • the view position information transmitted through the MPD may include view position information of each component in relation to the multi-view service.
  • the multiview service may mean 3D multiview or panoramic multiview.
  • the view position information may indicate a left view or a right view.
  • the USBD may include component information about service components of a broadcast service.
  • the component information may be the same as described above.
  • the component information may include component type information indicating the type of the corresponding service component and / or component role information indicating the role of the corresponding service component according to the type of the corresponding service component.
  • Each information may correspond to the above-described @componentType attribute and / or @componentRole attribute.
  • the component role information may indicate whether the audio or video component of the corresponding broadcast service is a service component for the hearing or visually impaired. That is, this information may indicate whether the corresponding component is a component for hearing impaired / visually impaired.
  • the USBD when service signaling information of a broadcast service is delivered by a ROUTE protocol, the USBD may further include information for referencing the MPD.
  • the MPD may include resource identifiers for service data of a broadcast service and / or context information of a resource. As mentioned above, this MPD may include various aforementioned information about the components. According to an embodiment, the MPD may further include caption information and / or 3D related information about a broadcast service.
  • a method of receiving a broadcast signal according to an embodiment of the present invention will be described. This method is not shown in the figure.
  • the physical layer processor on the receiving side processes the broadcast signal, and obtains IP packets therefrom, and the low-level signaling processor acquires an SLT and bootstraps from it.
  • the display unit may include providing a broadcast service using the obtained service components.
  • information such as caption, 3D, HDR, WCG, multiview, and the like may be obtained from the information of the SLT and / or SLS.
  • the corresponding information can be obtained from the MPD of the SLS or the MMTP message of the SLS.
  • the physical layer processing unit, the low level signaling processing unit and / or the display unit at the receiving side may be hardware elements.
  • Methods of receiving a broadcast signal may correspond to the methods of transmitting the broadcast signal according to the embodiments of the present invention described above.
  • Methods of receiving a broadcast signal include hardware modules corresponding to modules (eg, a service data generator, a transport layer processor, a low level signaling generator, a physical layer processor, etc.) used in a method of transmitting a broadcast signal. It can be performed by.
  • the method for receiving a broadcast signal may have embodiments corresponding to the embodiments of the method for transmitting the above-described broadcast signal.
  • 46 illustrates an apparatus for transmitting a broadcast signal according to an embodiment of the present invention.
  • An apparatus for transmitting a broadcast signal may include the aforementioned service data generator, a transport layer processor, a lower level signaling generator, and / or a physical layer processor.
  • Each block, module is as described above.
  • An apparatus for transmitting a broadcast signal and an internal module / block thereof according to an embodiment of the present invention may perform the above-described embodiments of the method for transmitting a broadcast signal of the present invention.
  • An apparatus for receiving a broadcast signal may include the above-described physical layer processing unit, low level signaling processing unit and / or display unit. Each block, module is as described above.
  • An apparatus for receiving a broadcast signal and an internal module / block thereof according to an embodiment of the present invention may perform the above-described embodiments of the method for receiving a broadcast signal of the present invention.
  • the above-described blocks / modules in the device may be processors for executing consecutive processes stored in a memory, and according to embodiments, may be hardware elements located in / outside the device.
  • the above-described modules may be omitted or replaced by other modules performing similar / same operations according to the embodiment.
  • the module or unit may be processors that execute successive procedures stored in a memory (or storage unit). Each of the steps described in the above embodiments may be performed by hardware / processors. Each module / block / unit described in the above embodiments can operate as a hardware / processor.
  • the methods proposed by the present invention can be executed as code. This code can be written to a processor readable storage medium and thus read by a processor provided by an apparatus.
  • Apparatus and method according to the present invention is not limited to the configuration and method of the embodiments described as described above, the above-described embodiments may be selectively all or part of each embodiment so that various modifications can be made It may be configured in combination.
  • the processor-readable recording medium includes all kinds of recording devices that store data that can be read by the processor.
  • Examples of the processor-readable recording medium include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like, and may also be implemented in the form of a carrier wave such as transmission over the Internet.
  • the processor-readable recording medium can also be distributed over network coupled computer systems so that the processor-readable code is stored and executed in a distributed fashion.
  • the present invention is used in the field of providing a series of broadcast signals.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

L'invention concerne un procédé de transmission d'un signal de radiodiffusion. Dans ledit procédé de l'invention, un système peut prendre en charge un service de radiodiffusion de nouvelle génération dans un environnement qui prend en charge une radiodiffusion hybride de nouvelle génération utilisant un réseau de radiodiffusion terrestre et un réseau Internet. En outre, dans l'environnement prenant en charge la diffusion hybride de nouvelle génération, un schéma de signalisation efficace est mis en oeuvre, qui couvre à la fois le réseau de diffusion terrestre et le réseau Internet.
PCT/KR2016/007366 2015-07-08 2016-07-07 Dispositif de transmission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé de transmission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion WO2017007258A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2017553098A JP2018517329A (ja) 2015-07-08 2016-07-07 放送信号送信装置、放送信号受信装置、放送信号送信方法、及び放送信号受信方法
US15/554,125 US10171849B1 (en) 2015-07-08 2016-07-07 Broadcast signal transmission device, broadcast signal reception device, broadcast signal transmission method, and broadcast signal reception method
KR1020177023471A KR102023018B1 (ko) 2015-07-08 2016-07-07 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US201562189773P 2015-07-08 2015-07-08
US201562189776P 2015-07-08 2015-07-08
US62/189,773 2015-07-08
US62/189,776 2015-07-08
US201562195283P 2015-07-21 2015-07-21
US62/195,283 2015-07-21

Publications (1)

Publication Number Publication Date
WO2017007258A1 true WO2017007258A1 (fr) 2017-01-12

Family

ID=57685278

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2016/007366 WO2017007258A1 (fr) 2015-07-08 2016-07-07 Dispositif de transmission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé de transmission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion

Country Status (3)

Country Link
JP (1) JP2018517329A (fr)
KR (1) KR102023018B1 (fr)
WO (1) WO2017007258A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108833906A (zh) * 2018-06-11 2018-11-16 深圳创维数字技术有限公司 一种有线电视信号的传输方法、***、服务器和存储介质
JP2020511826A (ja) * 2017-03-14 2020-04-16 サムスン エレクトロニクス カンパニー リミテッド 電子装置及びその制御方法

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10834473B2 (en) * 2018-11-23 2020-11-10 Sony Corporation Television receiver application for TV and electronic devices

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100046411A1 (en) * 2008-08-20 2010-02-25 Samsung Electronics Co., Ltd. Method and apparatus for transmitting broadcast data, and method and apparatus for receiving broadcast data
KR20110125203A (ko) * 2009-01-28 2011-11-18 엘지전자 주식회사 방송 수신기 및 비디오 데이터 처리 방법
KR20120138319A (ko) * 2011-06-14 2012-12-26 삼성전자주식회사 멀티미디어 데이터 특징 정보를 이용하여 멀티미디어 서비스 데이터 패킷을 송신하는 방법 및 장치
KR20130120416A (ko) * 2012-04-25 2013-11-04 삼성전자주식회사 디지털 방송 시스템에서 시그널링 정보 송수신 장치 및 방법
KR20140004069A (ko) * 2010-09-01 2014-01-10 엘지전자 주식회사 3d (3-dimentional) 방송 서비스를 위한 방송 신호 처리 방법 및 장치

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080253467A1 (en) * 2007-04-13 2008-10-16 Nokia Corporation System and method for using redundant pictures for inter-layer prediction in scalable video coding
US7912006B2 (en) * 2007-08-24 2011-03-22 Lg Electronics Inc. Digital broadcasting system and method of processing data in digital broadcasting system
US8396906B2 (en) * 2007-10-10 2013-03-12 Electronics And Telecommunications Research Institute Metadata structure for storing and playing stereoscopic data, and method for storing stereoscopic content file using this metadata
JP5539146B2 (ja) * 2010-10-12 2014-07-02 キヤノン株式会社 立体映像処理装置及びその制御方法
WO2014050447A1 (fr) * 2012-09-27 2014-04-03 ソニー株式会社 Dispositif de transmission, procédé de transmission, dispositif de réception et procédé de réception

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100046411A1 (en) * 2008-08-20 2010-02-25 Samsung Electronics Co., Ltd. Method and apparatus for transmitting broadcast data, and method and apparatus for receiving broadcast data
KR20110125203A (ko) * 2009-01-28 2011-11-18 엘지전자 주식회사 방송 수신기 및 비디오 데이터 처리 방법
KR20140004069A (ko) * 2010-09-01 2014-01-10 엘지전자 주식회사 3d (3-dimentional) 방송 서비스를 위한 방송 신호 처리 방법 및 장치
KR20120138319A (ko) * 2011-06-14 2012-12-26 삼성전자주식회사 멀티미디어 데이터 특징 정보를 이용하여 멀티미디어 서비스 데이터 패킷을 송신하는 방법 및 장치
KR20130120416A (ko) * 2012-04-25 2013-11-04 삼성전자주식회사 디지털 방송 시스템에서 시그널링 정보 송수신 장치 및 방법

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2020511826A (ja) * 2017-03-14 2020-04-16 サムスン エレクトロニクス カンパニー リミテッド 電子装置及びその制御方法
JP7100052B2 (ja) 2017-03-14 2022-07-12 サムスン エレクトロニクス カンパニー リミテッド 電子装置及びその制御方法
CN108833906A (zh) * 2018-06-11 2018-11-16 深圳创维数字技术有限公司 一种有线电视信号的传输方法、***、服务器和存储介质

Also Published As

Publication number Publication date
JP2018517329A (ja) 2018-06-28
KR20170103013A (ko) 2017-09-12
KR102023018B1 (ko) 2019-09-19

Similar Documents

Publication Publication Date Title
WO2017043863A1 (fr) Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2016182371A1 (fr) Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2017030425A1 (fr) Appareil de transmission de signal de radiodiffusion, appareil de réception de signal de radiodiffusion, procédé de transmission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2017007192A1 (fr) Dispositif d'émission de signal de diffusion, dispositif de réception de signal de diffusion, procédé d'émission de signal de diffusion et procédé de réception de signal de diffusion
WO2018004291A1 (fr) Procédé et appareil d'émission de signal de diffusion et procédé et appareil de réception de signal de diffusion
WO2016204481A1 (fr) Dispositif de transmission de données multimédias, dispositif de réception de données multimédias, procédé de transmission de données multimédias et procédé de réception de données multimédias
WO2016153326A1 (fr) Dispositif d'émission de signal de diffusion, dispositif de réception de signal de diffusion, procédé d'émission de signal de diffusion et procédé de réception de signal de diffusion
WO2016093586A1 (fr) Appareil d'émission de signal de radiodiffusion, appareil de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2016111526A1 (fr) Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2016178549A1 (fr) Dispositif d'émission de signaux de diffusion, dispositif de réception de signaux de diffusion, procédé d'émission de signaux de diffusion, et procédé de réception de signaux de diffusion
WO2016089095A1 (fr) Dispositif et procédé de transmission de signal de diffusion et dispositif et procédé de réception de signal de diffusion
WO2017209514A1 (fr) Dispositif et procédé d'émission et de réception de signal de diffusion
WO2016093576A1 (fr) Appareil de transmission de signal de radiodiffusion, appareil de réception de signal de radiodiffusion, procédé de transmission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2017061796A1 (fr) Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2016153241A1 (fr) Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion et procédé de réception de signal de radiodiffusion
WO2016171518A2 (fr) Émetteur de signal de radiodiffusion, récepteur de signal de radiodiffusion, procédé d'émission d'un signal de radiodiffusion et procédé de réception d'un signal de radiodiffusion
WO2016122269A1 (fr) Dispositif de transmission de signaux de radiodiffusion, dispositif de réception de signaux de radiodiffusion, procédé de transmission de signaux de radiodiffusion et procédé de réception de signaux de radiodiffusion
WO2016064150A1 (fr) Dispositif et procédé d'émission d'un signal de diffusion, dispositif et procédé de réception d'un signal de diffusion
WO2017061792A1 (fr) Dispositif et procédé d'émission/réception de signal de diffusion
WO2016108606A1 (fr) Appareil et procédé d'émission de signal de diffusion, appareil et procédé de réception de signal de diffusion
WO2017135673A1 (fr) Dispositif d'émission de signal de diffusion, dispositif de réception de signal de diffusion, procédé d'émission de signal de diffusion et procédé de réception de signal de diffusion
WO2018101566A1 (fr) Dispositif et procédé d'émission/réception de signal de radiodiffusion
WO2017018775A1 (fr) Appareil de transmission de signal de radiodiffusion, appareil de réception de signal de radiodiffusion, procédé de transmission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2016129904A1 (fr) Appareil d'émission de signal de radiodiffusion, appareil de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2016171528A1 (fr) Appareil de transmission d'un signal de radiodiffusion, appareil de réception d'un signal de radiodiffusion, procédé de transmission d'un signal de radiodiffusion, et procédé de réception d'un signal de radiodiffusion

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16821664

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20177023471

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017553098

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16821664

Country of ref document: EP

Kind code of ref document: A1