WO2017188750A1 - Method and apparatus for transmitting and receiving broadcast signal to provide high quality media - Google Patents

Abstract

The present invention proposes a method for transmitting a broadcast signal. The method for transmitting a broadcast signal according to the present invention proposes a system which can support a next-generation broadcast service in an environment supporting next-generation hybrid broadcasting using a terrestrial broadcast network and an Internet network. In addition, the present invention proposes an efficient signaling scheme which can cover both a terrestrial broadcast network and an Internet network in an environment supporting next-generation hybrid broadcasting.

Description

Broadcast signal transmission / reception method and apparatus for providing high quality media

The present invention relates to a broadcast signal transmission apparatus, a broadcast signal reception apparatus, and a broadcast signal transmission and reception method.

UHD HDR content service (HDR service) can provide a greater sense of reality by expressing the brightness that was not expressed in the existing HD content. In order to provide such an HDR service in an IP network, the DASH protocol may be used to enable more adaptive and flexible content reception.

UHD HDR content service can provide a greater sense of reality by expressing the brightness that could not be expressed unlike the existing HD content. However, the terminal expressing the existing SDR brightness may not guarantee the compatibility of the HDR stream, which may cause a malfunction when received, and may not guarantee the rendering intent.

In case of transmitting the SHVC-encoded HDR / WCG content in a file format, a method of signaling HDR / WCG-related information for each scalable layer is needed.

An embodiment of the present invention may define color gamut information and color conversion information of content in a file.

An embodiment of the present invention may define color related information corresponding to each scalable layer in a file.

According to the present invention, the HDR receiver can receive the HDR stream to perform HDR rendering and the SDR receiver can also receive the HDR stream to render the SDR video.

According to the present invention, when transmitting the SHVC-encoded HDR content based on the file format, the receiver may render the content according to the performance of the receiver by using color information corresponding to each layer.

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are incorporated in and constitute a part of this application for further understanding of the invention, illustrate embodiments of the invention, together with a detailed description that illustrates the principles of the invention.

1 is a diagram illustrating a protocol stack according to an embodiment of the present invention.

2 is a diagram illustrating a service discovery process according to an embodiment of the present invention.

3 illustrates a low level signaling (LLS) table and a service list table (SLT) according to an embodiment of the present invention.

4 is a diagram illustrating a USBD and an STSID delivered to ROUTE according to an embodiment of the present invention.

5 is a diagram illustrating a USBD delivered to MMT according to an embodiment of the present invention.

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.

9 illustrates a writing operation of a time interleaver according to an embodiment of the present invention.

FIG. 10 is a block diagram illustrating an interleaving address generator including 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.

11 illustrates a hybrid broadcast reception device according to an embodiment of the present invention.

12 is a diagram illustrating the overall operation of the DASH-based adaptive streaming model according to an embodiment of the present invention.

13 is a block diagram of a receiver according to an embodiment of the present invention.

14 is a diagram showing the structure of a media file according to an embodiment of the present invention.

FIG. 15 illustrates an HDR configuration box for providing HDR information according to an embodiment of the present invention. FIG.

16 is a diagram illustrating an HDR configuration box for providing HDR information according to another embodiment of the present invention.

17 is a diagram illustrating a method of defining HDR information in a tkhd box according to an embodiment of the present invention.

18 is a diagram illustrating a method of defining HDR information in a vmhd box according to an embodiment of the present invention.

19 is a diagram illustrating a method of defining HDR information in a trex box according to an embodiment of the present invention.

20 illustrates a method of defining HDR information in a tfhd box according to an embodiment of the present invention.

21 is a diagram illustrating a method of defining HDR information in a trun box according to an embodiment of the present invention.

FIG. 22 illustrates a scheme for defining HDR information in various flags, sample group entries, or sample entries according to an embodiment of the present invention.

FIG. 23 is a diagram illustrating a method of defining HDR information in a HEVC sample entry, an HEVC configuration box, or an HEVC decoder configuration record according to an embodiment of the present invention.

24 is a diagram illustrating a method of storing / delivering HDR information by defining an HDR information SEI box according to an embodiment of the present invention.

25 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.

FIG. 26 is a diagram illustrating an HDR configuration box according to another embodiment of the present invention. FIG.

27 is a diagram illustrating a system from production stage to rendering stage of HDR content according to an embodiment of the present invention.

28 is a diagram illustrating an ISOBMFF structure and a colr box according to an embodiment of the present invention.

29 is a diagram showing the configuration of a colour_remapping_info descriptor according to an embodiment of the present invention.

30 is a view illustrating a color conversion process according to an embodiment of the present invention.

FIG. 31 is a view illustrating a temporal layer structure of LHEVC (LayeredHEVC) or SHVC according to an embodiment of the present invention. FIG.

32 is a diagram illustrating a decoding process for reproducing a file format according to an embodiment of the present invention.

33 is a diagram showing the structure of an SHVC file format according to an embodiment of the present invention.

34 is a diagram showing the configuration of an LHEVCDecoderConfigurationRecord of a visual sample entry according to an embodiment of the present invention.

35 is a diagram showing the structure of an SHVC file format according to another embodiment of the present invention.

36 illustrates a map of a file format consisting of two tracks according to an embodiment of the present invention.

37 is a diagram showing the configuration of a scif box according to an embodiment of the present invention.

38 is a diagram showing the configuration of an onif box according to an embodiment of the present invention.

39 is a view showing the position of the colr box and the configuration of the expanded colr box according to an embodiment of the present invention.

40 is a view showing a broadcast signal transmission method according to an embodiment of the present invention.

41 is a view showing a broadcast signal receiving method according to an embodiment of the present invention.

42 is a diagram illustrating a configuration of a broadcast signal transmission apparatus according to an embodiment of the present invention.

43 is a diagram showing the configuration of a broadcast signal receiving apparatus according to an embodiment of the present invention.

Preferred embodiments of the present invention will be described in detail, examples of which are illustrated in the accompanying drawings. DETAILED DESCRIPTION The following detailed description with reference to the accompanying drawings is intended to explain preferred embodiments of the invention rather than to show only embodiments that may be implemented in accordance with embodiments of the invention. The following detailed description includes details to provide a thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced without these details.

Most of the terms used in the present invention are selected from general ones widely used in the art, but some terms are arbitrarily selected by the applicant, and their meanings are described in detail in the following description as necessary. Therefore, the present invention should be understood based on the intended meaning of the term and not the simple name or meaning of the term.

The present invention provides an apparatus and method for transmitting and receiving broadcast signals for next generation broadcast services. The next generation broadcast service according to an embodiment of the present invention includes a terrestrial broadcast service, a mobile broadcast service, a UHDTV service, and the like. According to an embodiment of the present invention, 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. 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.

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. First, 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. In this case, 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.

There may be two methods for broadcast service delivery through a broadcasting network.

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). In this case, 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). In this case, 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. In service data transmission through a broadcasting network, 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.

In hybrid service delivery, at least one or more service elements may be delivered via a broadband path. In the case of hybrid service delivery, 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.

Describe the service. 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.

Services can have many types. Firstly, the service may be a linear audio / video or audio only service that may have app-based enhancements. Secondly, the service may be an app-based service whose reproduction / configuration is controlled by the downloaded application. Third, the service may be an ESG service that provides an electronic service guide (ESG). Fourth, it may be an Emergency Alert (EA) service that provides emergency alert information.

When a linear service without app-based enhancement is delivered through the broadcasting network, the service component may be delivered by (1) one or more ROUTE sessions or (2) one or more MMTP sessions.

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. In this case, data used for app-based enhancement may be delivered through a ROUTE session in the form of NRT data or other files. In one embodiment of the invention, linear service components (streaming media components) of one service may not be allowed to be delivered using both protocols simultaneously.

When the app-based service is delivered through the broadcast network, the service component may be delivered by one or more ROUTE sessions. In this case, 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.

In addition, some service components or some NRT data, files, etc. of these services may be delivered via broadband (hybrid service delivery).

That is, in one embodiment of the present invention, the linear service components of one service may be delivered through the MMT protocol. In another embodiment of the present invention, the linear service components of one service may be delivered via a ROUTE protocol. In another embodiment of the present invention, the linear service component and NRT data (NRT service component) of one service may be delivered through the ROUTE protocol. In another embodiment of the present invention, 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. In the above embodiments, some service component or some NRT data of a service may be delivered over broadband. Here, 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. In streaming service delivery, 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.

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.

At the receiver, 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.

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. When SLS, that is, service signaling information is transmitted through ROUTE, 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. When the SLS is delivered through the MMT, the bootstrap information may include a destination IP address and destination port information of the MMTP session carrying the SLS.

In the illustrated embodiment, 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.

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. In some embodiments, this LCT channel may be an LCT channel identified by tsi = 0. In this case, 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).

Here, 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.

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. According to an embodiment, packet_id of MMTP packets carrying SLS may have a value of 00. In this case, the SLS may include a USBD / USD and / or MMT Package (MP) table.

Here, 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. According to an embodiment, the USBD of the MMT may also include reference information on the S-TSID and / or the MPD. Here, 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. Here, 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.

Other 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.

In case of ROUTE, the S-TSID, the USBD / USD, the MPD, or the LCT session carrying them may be called a service signaling channel. In the case of MMTP, USBD / UD, MMT signaling messages or packet flow carrying them may be called a service signaling channel.

Unlike the illustrated embodiment, 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).

3 illustrates a low level signaling (LLS) table and a service list table (SLT) according to an embodiment of the present invention.

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. Here, 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.

According to the value of the LLS_table_id field, 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.

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. In some embodiments, 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.

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). The repair protocol may define a FEC framework that enables such FEC protection.

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 contentAdvisoryRating 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. In hybrid service delivery, 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. In addition to the hybrid service delivery, 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, and 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.

The above-mentioned 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.

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, and 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. In addition, 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.

As a reference on the transmission side, the link layer ALP may perform an overhead reduction process on input packets and then encapsulate them into link layer packets. In addition, according to an embodiment, 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.

In the case where the illustrated IP packet is input as an input packet (t6010), the link layer may sequentially perform IP header compression, adaptation, and / or encapsulation. In some embodiments, some processes may be omitted. First, 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. Thereafter, IP packets may be encapsulated into link layer packets through an encapsulation process.

In the case where the MPEG 2 TS packet is input as an input packet, 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. In overhead reduction, 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.

First, 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. Hereinafter, 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.

Hereinafter, the adaptation will be described.

In the case of transmissions on the unidirectional link, if the receiver does not have the context information, the decompressor cannot recover the received packet headers until it receives the complete context. This can result in channel change delays and turn-on delays. Therefore, the configuration parameter and context information between the compressor / decompressor can be transmitted out of band through the adaptation function. 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.

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. After extraction, 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.

In each mode, 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. According to an embodiment, 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). Here, the RDT may be signaling information including context information (static chain and / or dynamic chain) and / or information related to header compression. According to an embodiment, the RDT may be transmitted whenever the context information changes. In some embodiments, 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.

Prior to acquiring the packet stream, 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. At this time, 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. Can start (mode 2), or start decompression from any normal compressed packet (mode 3).

Hereinafter, packet encapsulation will be described.

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. In addition, 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.

Hereinafter, link layer signaling will be described.

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. FIG.

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. In this case, 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. Here, 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.

That is, 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. As mentioned 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.

According to an embodiment, 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.

According to another embodiment, 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. In this case, the receiver may identify the PLP to know by combining LMT and other IP level signaling information. Also in this embodiment, 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. Although the LMT of the illustrated embodiment describes IP streams transmitted to one PLP for one PLP, a PLP loop may be added to the LMT according to an embodiment, so that information on a plurality of PLPs may be described. In this case, as described above, 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. In addition, the existence of the context_id field to be described later may be determined according to the value of this field. When header compression is applied (compressed_flag = 1), an RDT may exist, and the PLP ID field of the RDT may have the same value as the corresponding PLP_ID field associated with this compressed_flag field.

The SID field may indicate a sub stream ID (SID) for link layer packets carrying a corresponding transport session. These link layer packets may include an SID having the same value as this SID field in the optional header. Through this, the receiver can filter the link layer packets by using the information of the LMT and the SID information of the link layer packet header without parsing all the link layer packets.

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.

In the above-described embodiments of the signaling information / table of the present invention, 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. .

In one embodiment of the present invention, service components of one service may be delivered through a plurality of ROUTE sessions. In this case, 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. Through this, 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. For reference, one service component may be used simultaneously by a plurality of services.

In another embodiment of the present invention, bootstrapping for ESG services may be performed by a broadcast network or broadband. Through ESG acquisition through broadband, URL information of the SLT may be utilized. ESG information and the like can be requested to this URL.

In another embodiment of the present invention, 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.

In another embodiment of the present invention, 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.

In another embodiment of the present invention, through the TOI field of the LCT packets delivered to the LCT channel carrying SLS, which SLS fragments the corresponding LCT packets carry (USBD, S-TSID, MPD, etc.) Can be identified.

In another embodiment of the present invention, 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. In addition, app signaling for app-based enhancement may be performed by an application signaling table (AST) delivered with SLS. In addition, 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.

In another embodiment of the present invention, 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.

In another embodiment of the present invention, the linear service components may be delivered through a broadcasting network according to the MMT protocol. In this case, NRT data (for example, an app component) for a corresponding service may be delivered through a broadcasting network according to the ROUTE protocol. In addition, 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. In addition, the USBD may further refer to the S-TSID to allow the receiver to obtain NRT data delivered according to the ROUTE protocol. In addition, the USBD may further reference the MPD to provide a playback description for the data delivered over the broadband.

In another embodiment of the present invention, 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. In addition, the receiver may transmit information such as system time information and emergency alert information to the companion device.

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 according to an embodiment of the present invention 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.

In the input data according to an embodiment of the present invention, 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). 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.

Since QoS depends on the characteristics of the service provided by the broadcast signal transmission apparatus for the next generation broadcast service according to an embodiment of the present invention, data corresponding to each service should be processed in different ways.

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. It is observed that 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. In this case, 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. In the present invention, time interleaving using different time interleaving methods according to the PLP mode may be referred to as hybrid time interleaving.

The hybrid time interleaver may include a block interleaver (BI) and a convolution interleaver (CI). If PLP_NUM = 1, the block interleaver is not applied (block interleaver off), and only the convolutional interleaver is applied. When PLP_NUM> 1, both the block interleaver and the convolution interleaver may be applied (block interleaver on). The structure and operation of the convolutional interleaver applied when PLP_NUM> 1 may be different from the structure and operation of the convolutional interleaver applied when PLP_NUM = 1. 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), which is a pair of constellation mapper outputs, is fed to the input of the MIMO encoder, and MIMO encoder output pairs (g1, i and g2, i) Transmitted by the same carrier k and OFDM symbol l of each transmit antenna.

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. In particular, the preamble may indicate whether an emergency alert service (EAS) is provided in the current frame. 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. And 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. In addition, 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 according to an embodiment of the present invention 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, and PLS2 dynamic data is PLS2 data that changes dynamically from frame to frame.

The PLS2 data may include FIC_FLAG information. Fast Information Channel (FIC) is a dedicated channel for transmitting cross-layer information that enables fast service acquisition and channel scanning. 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. For PLS1 data only, 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 according to an embodiment of the present invention 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 according to an embodiment of the present invention 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.

The time interleaver is described below. 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. Here, 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. In general, 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). In this case, 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. In this case, the virtual XFECBLOCK must be inserted in front of the other XFECBLOCKs to achieve a single memory deinterleaving on the receiver side.

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 according to an embodiment of the present invention 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.

(a) shows a block diagram of an interleaving address generator for 8K FFT mode, (b) shows a block diagram of an interleaving address generator for 16K FFT mode, and (c) shows an interleaving address generator for 32K FFT mode. Shows a block diagram of.

The interleaving process for an OFDM symbol pair uses one interleaving sequence and is described as follows. First, the available data cells (output cells from the cell mapper) to be interleaved in one OFDM symbol Om, l are l = 0,... , Om, l = [xm, l, 0,... For Nsym-1. , xm, l, p,… , xm, l, Ndata-1]. Where xm, l, p is 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, and Ndata = CFES for the frame edge symbol. In addition, the interleaved data cells have l = 0,... , Pm, l = [vm, l, 0,... For Nsym-1. , vm, l, Ndata-1].

For OFDM symbol pairs, the interleaved OFDM symbol pairs are denoted by vm, l, Hi (p) = xm, l, p, p = 0,... For the first OFDM symbol of each pair. , Given by Ndata-1, for the second OFDM symbol of each pair, 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.

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 (s) may obtain an IP datagram from information obtained from the physical layer module. In addition, 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. In addition, 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. In addition, 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. Here, 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. In addition, 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.

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). In the case where 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.

In the case of UHD broadcasting or the like, brightness that cannot be expressed by existing contents can be expressed, thereby providing a high level of realism. With the introduction of HDR, the range of expression of the brightness of the content image is increased, and the difference in the scene-specific characteristics of the content may be larger than before. In order to effectively represent scene-specific features of the content on the display, metadata may be defined and these may be passed to the receiver. At the receiver, based on the received metadata, an image of the content may be appropriately provided as intended by the service provider.

The DASH-based adaptive streaming model according to the illustrated embodiment describes the operation between the HTTP server and the DASH client. Here, DASH (Dynamic Adaptive Streaming over HTTP) 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.

First, 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.

After acquiring the segment, 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.

Media Presentation Description (MPD) may be represented in XML form as 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. In addition, 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.

13 is a block diagram of a receiver according to an embodiment of the present invention.

The receiver according to the illustrated embodiment 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. 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.

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.

14 is a diagram showing the structure of a media file according to an embodiment of the present invention.

In order to store and transmit media data such as audio or video, a standardized media file format may be defined. According to an embodiment, 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. In addition, 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 (file type 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 (movie 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 (media data 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.

According to an embodiment, 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 (movie header 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 (track 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.

According to an embodiment, 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 (movie fragment 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 (media data 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.

According to an embodiment, the above-described moof box may further include a mfhd box and / or a traf box as a lower box.

The mfhd box (movie fragment header 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 (track fragment 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.

According to an embodiment, the above-described traf box may further include a tfhd box and / or a trun box as a lower box.

The tfhd box (track fragment header 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 (track fragment run 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. In addition, the media segment may further include a styp box and / or a sidx box.

The styp box (segment type 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. According to an embodiment, the styp box may have the same format as the ftyp box.

The sidx box (segment index 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.

According to an embodiment (t14040), 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. In this embodiment, 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.

FIG. 15 illustrates an HDR configuration box for providing HDR information according to an embodiment of the present invention. FIG.

In order to provide HDR information related to video tracks or video samples in the media file, an HDR configuration box can be defined. The HDR configuration box can be located in the media file. According to an embodiment, the HDR configuration box may be included in a moov box, a moof box or a third box. The HDR configuration box may be called an hdrc box.

The HDR configuration box may have a hdr_config field. The hdr_config field may include an OETF_type field, max_mastering_display_luminance field, min_mastering_display_luminance field, hdr_type_transition_flag field, hdr_sdr_transition_flag field, sdr_hdr_transition_flag field, sdr_compatibility_flag field, average_frame_luminance_level field and

The OETF_type field may indicate the type of the 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.

The max_mastering_display_luminance field 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.

The min_mastering_display_luminance field 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.

The hdr_type_transition_flag field may be a flag indicating whether the HDR information of the corresponding video data is changed to apply another type of HDR information.

The hdr_sdr_transition_flag field may be a flag indicating whether corresponding video data is switched from HDR to SDR.

The sdr_hdr_transition_flag field may be a flag indicating whether corresponding video data is switched from SDR to HDR.

The sdr_compatibility_flag field may be a flag indicating whether corresponding video data is compatible with an SDR decoder or an SDR display.

The average_frame_luminance_level field may indicate an average value of luminance level for one video sample. In addition, 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).

The max_frame_pixel_luminance field may indicate the maximum value of pixel luminance values for one video sample. In addition, 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 "corresponding video data" that the fields describe may be a video track, a video sample group, or respective video samples in a media file. The range described by each field may vary according to the description object. For example, the hdr_type_transition_flag field may indicate whether to switch from HDR to SDR in a corresponding video track or may indicate whether to switch from HDR to SDR within a video sample group.

16 is a diagram illustrating an HDR configuration box for providing HDR information according to another embodiment of the present invention.

In order to provide HDR information related to video tracks or video samples in the media file, an HDR configuration box can be defined. The HDR configuration box can be located in the media file. According to an embodiment, the HDR configuration box may be included in a moov box, a moof box or a third box. The HDR configuration box may be called an hdrc box. The HDR configuration box of the present embodiment may provide information about an HDR parameter set (eg, a set of EOTF, bit depth, peak luminance level, codec, metadata, etc.) associated with a video track or a sample included in the ISOBMFF. HDR-related parameters may be an Electro Optical Transfer Function (EOTF), bit depth, peak luminance level, codec, related metadata, and the like. For example, applied HDR-related parameters may be composed of a combination of EMPF, SMPTE ST2084, bit depth of 12 bits / pixel, peak luminance of 10000 nits, codec of HEVC single codec, and metadata of SMPTE ST 2086. An HDR configuration box such as d16010 may be included in the ISOBMFF to signal information about such a set of HDR related parameters.

The HDR configuration box may have at least one of an hdr_param_set field, an hdr_config_flag field, and / or an hdr_config field. The hdr_param_set field may indicate an identifier indicating a combination (set) of HDR related parameters. In an embodiment, the following values may be obtained. For example, when the hdr_param_set field is set to 1, among the HDR-related parameters, EOTF is SMPTE ST2084, bit depth is 12bit / pixel, peak luminance is 10000nit, codec is HEVC dual codec (HEVC + HEVC), and metadata is SMPTE ST. 2086, SMPTE ST 2094 may be used. When the hdr_param_set field is set to 2, it may represent that EOTF uses SMPTE ST2084, bit depth of 10 bit / pixel, peak luminance of 4000 nits, codec of HEVC single codec, metadata of SMPTE ST 2086, and SMPTE ST 2094. In addition, when the hdr_param_set field is set to 3, EOTF may indicate that BBC EOTF, bit depth is 10bit / pixel, peak luminance is 1000nit, and codec is HEVC single codec. The above combination corresponds to an embodiment, and the 8-bit hdr_param_set field may identify a combination of 256 HDR-related parameters. This hdr_config_flag field allows the ISOBMFF to indicate which HDR parameters the video track or samples it contains are associated with, and the receiver can decode or image the video track or samples contained in the ISOBMFF using any HDR parameters. You will be provided with details of what to do. The hdr_config_flag field may indicate whether to include HDRConfigration (hdr_config) including information on HDR-related detailed parameters. When the value of the hdr_config_flag field is '1', it may represent that HDRConfigration is included. When HDRConfigration is included, it may indicate that a transition (for example, HDR Type1-> HDR Type2, HDR-> SDR, SDR-> HDR) exists in a sample, a sample group, or a track to which the information is applied. have. It can also indicate whether SDR Compatibility is supported. When the value of the hdr_config_flag field is '0', it may represent that the HDR configuration including the detailed information of the HDR parameter is not included. In this case, the HDR parameter can be inferred using the hdr_parameter_set information.

The hdr_config field including the HDRConfigration information may include the OETF_type field, the max_mastering_display_luminance field, the min_mastering_display_luminance field, the average_frame_luminance_level field, the max_frame_pixel_luminance field, the hdr_type_transition_flag field, the hdr_sdr_transition_flag field, and the spat_com_flag field as in d16020. Description of each field is as described in the previous drawing.

According to another embodiment, an HDR configuration box such as d16030 may be included in the ISOBMFF to signal information about a set of HDR related parameters.

The HDR configuration box may have at least one of hdr_param_set field, hdr_type_transition_flag field, hdr_sdr_transition_flag field, sdr_hdr_transition_flag field, sdr_compatibility_flag field, hdr_config_flag field and / or hdr_config field. The hdr_param_set field may indicate an identifier indicating a combination (set) of HDR related parameters. The embodiment is as described above. The above combination corresponds to an embodiment, and the 8-bit hdr_param_set field may identify a combination of 256 HDR-related parameters. This hdr_config_flag field allows the ISOBMFF to indicate which HDR parameters the video track or samples it contains are associated with, and the receiver can decode or image the video track or samples contained in the ISOBMFF using any HDR parameters. You will be provided with information on what to do. The description of the hdr_type_transition_flag field, the hdr_sdr_transition_flag field, the sdr_hdr_transition_flag field, and the sdr_compatibility_flag field has been described above. The hdr_config_flag field may indicate whether to include HDRConfigration (hdr_config) including information on HDR-related detailed parameters. When the value of the hdr_config_flag field is '0', it may represent that HDRConfigration is not included. The hdr_config field including the HDRConfigration information may include an OETF_type field, a max_mastering_display_luminance field, a min_mastering_display_luminance field, an average_frame_luminance_level field, and / or a max_frame_pixel_luminance field, as in d16040. Description of each field is as described in the previous drawing.

17 is a diagram illustrating a method of defining HDR information in a tkhd box according to an embodiment of the present invention.

HDR information may be included in the structure of the above-described media file itself to store / transmit. In this embodiment, HDR information (parameters) may be added to the tkhd box in the above-described moov box. The added HDR information will be described below.

In the illustrated embodiment d17010, the hdr_flag field may be a flag indicating whether HDR video data is included in a corresponding video track described by the tkhd box. When the value of this field is 1, HDR video data may be included in the corresponding video track. If the value of this field is 1, there may be five flag fields to be described later. In particular, when the value of the hdr_flag field is 1, the tkhd box may include an hdr_param_set field indicating the HDR parameter combination.

Based on the hdr_flag and the flag field value to be described later, it may be determined whether or not the video decoder or the like can process the video data in the corresponding video track. For example, in case of a decoder capable of processing only SDR, it may be understood that corresponding video data cannot be processed when HDR_flag = 1 and SDR_compatibility = 0.

The hdr_param_set field may indicate an identifier indicating a set of HDR related parameters applied in the corresponding video track. As described in the previous figure, a specific HDR parameter combination may be indicated according to the value of the hdr_param_set field.

The hdr_type_transition_flag field may be a flag indicating whether HDR information (parameters) related to HDR video data in a corresponding video track have been changed. When the value of this field is 1, the HDR information for the HDR video data in the corresponding video track may be changed to other HDR information.

The hdr_sdr_transition_flag field may be a flag indicating whether video data in a corresponding video track is switched from HDR to SDR. When the value of this field is 1, it may be confirmed that corresponding video data is converted from HDR to SDR.

The sdr_hdr_transition_flag field may be a flag indicating whether video data in a corresponding video track is switched from SDR to HDR. When the value of this field is 1, it may be confirmed that video data is converted from SDR to HDR.

The sdr_compatibility_flag field may be a flag indicating whether video data in a corresponding video track is compatible with a decoder or display that supports SDR. If the value of this field is 1, it may be confirmed that the HDR video data in the corresponding video track is compatible with devices supporting SDR. When the value of this field is 1, decoder / display devices supporting SDR may determine whether to decode / display HDR video data included in a corresponding video track.

According to an embodiment, when the transition related flag is set to 1, the decoder or the like may make the data (SEI, etc.) in the video related thereto before processing video data.

According to an embodiment (d17020), the above-described HDR configuration box may be added in the tkhd box. The hdr_flag field in the present embodiment may be the same as the hdr_flag field in the above-described embodiment d17010. In this case, when the value of the hdr_flag field is 1, it may be indicated that an hdr_config box having an HDR configuration box type exists in place of the above five flags in the tkhd box.

Here, the hdr_config box may include HDR information about video data included in a corresponding video track. Since this box has the HDR configuration box type described above, the hdr_param_set field, the OETF_type field, the max_mastering_display_luminance field, the min_mastering_display_luminance field, the hdr_type_transition_flag field, the hdr_sdr_transition_flag field, the sdr_hdr_trans_field and flas_flagance field as described above can do.

The definition of these fields is as described above, but in this embodiment, since the HDR configuration box is present in the tkhd box, these fields may describe information about the corresponding video track. For example, the OETF_type field may indicate an OETF type for video data in the “corresponding video track”. In particular, the hdr_param_set field, hdr_type_transition_flag field, hdr_sdr_transition_flag field, sdr_hdr_transition_flag field, and / or sdr_compatibility_flag field may have the same meaning as the five flag fields in the above-described embodiment d17010.

According to an embodiment, the average_frame_luminance_level field in this HDR configuration box may indicate a maximum value among average values of luminance levels of each of the video samples in the corresponding video track. Also, the max_frame_pixel_luminance field may indicate the largest value among the maximum values of pixel luminance of each of the video samples in the corresponding video track.

18 is a diagram illustrating a method of defining HDR information in a vmhd box according to an embodiment of the present invention.

HDR information may be included in the structure of the above-described media file itself to store / transmit. In this embodiment, HDR information (parameters) may be added to the vmhd box in the above-described trak box. Added HDR information is shaded.

Here, the vmhd box (video media header box) is a lower box of the above-described trak box and may provide general presentation related information about the corresponding video track.

In the illustrated embodiment d18010, the hdr_flag field may be included. In addition, the hdr_param_set field, hdr_type_transition_flag field, hdr_sdr_transition_flag field, sdr_hdr_transition_flag field, and / or sdr_compatibility_flag field may be further included according to the value of the hdr_flag field. These fields may play the same role as the fields of the same name in the tkhd box described above.

In addition, in the illustrated embodiment d18020, an hdr_flag field may be included. In addition, the hdr_config box, which is an HDR configuration box, may be further included according to the value of the hdr_flag field. The hdr_flag field and the hdr_config box may play the same role as the field or box of the same name in the above-described tkhd box.

That is, in the illustrated embodiments, the HDR information in the vmhd box may provide HDR information about video data included in the corresponding video track.

According to an embodiment, HDR information may be simultaneously included in the tkhd box and the vmhd box. In this case, embodiments of the HDR information structure included in each box may be combined with each other. When the HDR information is simultaneously included in the tkhd box and the vmhd box, the values of the HDR information defined in the tkhd box may be overridden to the values of the HDR information defined in the vmhd box. That is, when the values of the HDR information defined in both are different, the value in the vmhd box may be used. If the HDR information is not included in the vmhd box, the HDR information in the tkhd box may be used.

19 is a diagram illustrating a method of defining HDR information in a trex box according to an embodiment of the present invention.

HDR information may be included in the structure of the above-described media file itself to store / transmit. In the present embodiment, HDR information (parameters) may be added to the trex box in the aforementioned mvex box. Added HDR information is shaded.

Here, the trex box (track extend box) is a lower box of the above-described mvex box, and may set default values used by each movie fragment. By providing a default value for this box, space and complexity in the traf box can be reduced.

The trex box may include a default_hdr_flag field and / or a default_sample_hdr_flag field. Depending on the value of the default_hdr_flag field, the default_hdr_config box, which is an HDR configuration box, may be further included. In addition, depending on the value of the default_sample_hdr_flag field, the default_sample_hdr_config box, which is an HDR configuration box, may be further included.

The default_hdr_flag field may be a flag indicating whether HDR video data is included in the video track fragment included in the movie fragment. When the value of this field is 1, it may be indicated that the movie fragment includes HDR video data by default. If the value of this field is 1, a default_hdr_config box, which is an HDR configuration box, may be further included.

The default_hdr_config box may include HDR information that can be commonly applied to video samples included in the corresponding video track fragment. This box is the aforementioned HDR configuration box and may include the fields of the aforementioned HDR configuration box.

Other fields except the average_frame_luminance_level field and / or the max_frame_pixel_luminance field among the fields of the box may play the same role as the fields of the same name in the HDR configuration box included in the tkhd box described above. The average_frame_luminance_level field may indicate a maximum value among average values of luminance levels of each video sample belonging to a movie fragment. The max_frame_pixel_luminance field may indicate the largest value among the maximum values of pixel luminance of each video sample belonging to the movie fragment.

The default_sample_hdr_flag field may be a flag indicating whether HDR video samples are included in a video track fragment included in a movie fragment by default. When the value of this field is 1, it may be indicated that the fragment includes HDR video samples by default. If the value of this field is 1, the default_sample_hdr_config box, which is an HDR configuration box, may be further included.

The default_sample_hdr_config box may include HDR information that can be applied to each of the video samples included in the corresponding movie fragment. This box is the aforementioned HDR configuration box and may include the fields of the aforementioned HDR configuration box.

Other fields except the average_frame_luminance_level field and / or the max_frame_pixel_luminance field among the fields of the box may play the same role as the fields of the same name in the HDR configuration box included in the tkhd box described above. The average_frame_luminance_level field may indicate an average value of luminance levels of each video sample belonging to a track fragment in a corresponding fragment. max_frame_pixel_luminance field This may indicate the maximum value of pixel luminance of each video sample belonging to the track fragment in the corresponding fragment.

20 illustrates a method of defining HDR information in a tfhd box according to an embodiment of the present invention.

HDR information may be included in the structure of the above-described media file itself to store / transmit. In this embodiment, HDR information (parameters) may be added to the tfhd box in the above-described moof box. Added HDR information is shaded.

In the illustrated embodiment d20010, the hdr_flag field may be a flag indicating whether HDR video data is included in a corresponding video track fragment described by the tfhd box. When the value of this field is 1, HDR video data may be included in the corresponding video track fragment.

When the value of the hdr_flag field is 1, the hdr_param_set field, the hdr_type_transition_flag field, the hdr_sdr_transition_flag field, the sdr_hdr_transition_flag field, and / or the sdr_compatibility_flag field may be further included. These fields may play the same role as the fields of the same name in the tkhd box described above. In this case, however, these fields may describe the video track fragment, not the entire video track.

That is, the hdr_param_set field may indicate an identifier indicating a combination of HDR-related parameters applied in a track fragment included in a movie fragment. The hdr_type_transition_flag field may indicate whether there is a change in the HDR information with respect to media data related to the track fragment in the corresponding track fragment. The hdr_sdr_transition_flag field may represent that the track fragment is switched from HDR to SDR. The sdr_hdr_transition_flag field may represent that the track fragment is switched from SDR to HDR. The sdr_compatibility_flag field may indicate whether the HDR video data of the corresponding track fragment is compatible with the SDR decoder / display.

In the illustrated embodiment d20020, the tfhd box may include the HDR configuration box described above. According to the value of the hdr_flag field, it may be indicated whether the hdr_config box, which is an HDR configuration box, is included. The hdr_config box may provide HDR information that may be commonly applied to video samples of the corresponding track fragment.

Other fields except the average_frame_luminance_level field and / or the max_frame_pixel_luminance field among the fields of the box may play the same role as the fields of the same name in the HDR configuration box included in the tkhd box described above. In this case, however, these fields may describe the video track fragment, not the entire video track.

The average_frame_luminance_level field may indicate a maximum value among average values of luminance levels of each video sample belonging to a track fragment in the corresponding fragment. max_frame_pixel_luminance field The maximum_frame_pixel_luminance field may indicate the largest value among the maximum values of pixel luminance of each video sample belonging to the track fragment in the corresponding fragment.

In the illustrated embodiment d20030, the tfhd box may further include HDR information according to the tf_flags value. tr_flags may indicate flags associated with the box. For example, when tr_flags includes a value of 0x000001, it may be indicated that the base data offset information is included in the tfhd box, and when it includes the value of 0x000002, it may be indicated that the sample description index information is included in the tfhd box.

According to an embodiment, when the tf_flags value includes a value of 0x100000, it may be indicated that a default value of HDR information for video samples included in a track fragment in the corresponding fragment exists. The tf_flags value indicating the presence of the HDR information may have a value other than the 0x100000 value in some embodiments. (0x100000: default-sample-hdr-configuration-present)

If the tf_flags value includes a value of 0x100000, the tfhd box may include a deafult_sample_hdr_config box, which is an HDR configuration box. The deafult_sample_hdr_config box may play the same role as the deafult_sample_hdr_config box in the above-described trex box.

21 is a diagram illustrating a method of defining HDR information in a trun box according to an embodiment of the present invention.

HDR information may be included in the structure of the above-described media file itself to store / transmit. In this embodiment, HDR information (parameters) may be added to the trun box in the traf box described above. Added HDR information is shaded.

In the illustrated embodiment d21010, the trun box may include an hdr_flag field. In addition, the hdr_param_set field, hdr_type_transition_flag field, hdr_sdr_transition_flag field, sdr_hdr_transition_flag field, and / or sdr_compatibility_flag field may be further included according to the value of the hdr_flag field. These fields may signal HDR related matters that may be commonly applied to video samples in the corresponding track fragment. These fields may have the same meaning as the fields of the same name in the tfhd box described above.

In some embodiments, HDR information may be simultaneously included in the tfhd box and the trun box. In this case, embodiments of the HDR information structure included in each box may be combined with each other. When the HDR information is simultaneously included in the tfhd box and the trun box, the values of the HDR information defined in the tfhd box may be overridden to the values of the HDR information defined in the trun box. That is, when the values of the HDR information defined in both are different, the value in the trun box may be used. If the HDR information is not included in the trun box, the HDR information in the tfhd box may be used.

In the illustrated embodiment d21020, the trun box may include an hdr_flag field, and may further include an hdr_config box that is an HDR configuration box according to the value of the hdr_flag field. This box may contain HDR information that can be commonly applied to video samples within the track fragment. The fields in this box may have the same meaning as the fields of the same name of the HDR configuration box in the tfhd box described above.

In the illustrated embodiment d21030, the trun box may further include HDR information according to the tf_flags value. tr_flags may indicate flags associated with the box. For example, when tr_flags includes a value of 0x000001, it may be indicated that data offset information is included in a trun box. When tr_flags includes a value of 0x000004, it may be indicated that the first sample flag information is included in a trun box.

According to an embodiment, when the tf_flags value includes a value of 0x002000, it may be indicated whether there is HDR information that can be commonly applied to video samples included in the track fragment in the corresponding fragment. The tf_flags value indicating that the HDR information is present may have a value other than the 0x002000 value in some embodiments. (0x002000: hdr-configuration-present)

When the tf_flags value includes a value of 0x002000, the trun box may include an hdr_config box, which is an HDR configuration box. The hdr_config box may play the same role as the hdr_config box in the above-described tfhd box.

In the illustrated embodiment d21040, the trun box may further include HDR information according to the tf_flags value. According to an embodiment, when the tf_flags value includes a value of 0x001000, it may be indicated whether there is HDR information that can be applied to each of the video samples included in the track fragment in the corresponding fragment. The tf_flags value indicating that the HDR information exists may have a value other than the 0x001000 value according to an embodiment. (0x001000: sample-hdr-configuration-present)

If the tf_flags value includes a value of 0x001000, the trun box may include a sample_hdr_config box, which is an HDR configuration box. The sample_hdr_config box may provide HDR information about the sample.

The meaning of the information in the sample_hdr_config box may be the same as the meaning of the information in the deafult_sample_hdr_config box of the tfhd box described above. That is, the deafult_sample_hdr_config box of the tfhd box may provide default HDR information that may be applied to each sample, and the sample_hdr_config box of the trun box may provide individual HDR information that may be applied to the sample for each sample.

However, the average_frame_luminance_level field and / or max_frame_pixel_luminance field of the sample_hdr_config box may have a different meaning from those of the default_sample_hdr_config box. The average_frame_luminance_level field may indicate an average value of the luminance level of the video sample. max_frame_pixel_luminance field This may represent the maximum value of pixel luminance of a corresponding video sample.

FIG. 22 illustrates a scheme for defining HDR information in various flags, sample group entries, or sample entries according to an embodiment of the present invention.

In the illustrated embodiment d22010, default-sample_flags in a trex box, default_sample_flags in a tfhd box, sample_flags in a trun box, and / or HDR related flags shown on first_sample_flags in a trun box may be added.

First, the hdr_flag field may be included on each flag. The hdr_flag field may be a field indicating whether each corresponding media sample in the track is an HDR video sample. When the value of this field is 1, it may be indicated that each sample in the corresponding track is an HDR video sample. According to an embodiment, existence of flag fields to be described later may be determined by the value of the hdr_flag field.

The sdr_compatibility_flag field, the hdr_type_transition_flag field, and / or the hdr_sdr_transition_flag field have the same meaning as the above-described fields of the same name, but may be different in that they are described for the corresponding media sample (HDR video sample).

That is, the sdr_compatibility_flag field may indicate whether the corresponding HDR video sample is compatible with a decoder / display supporting SDR. The hdr_type_transition_flag field may indicate that HDR information (parameter) for the corresponding HDR video sample and HDR information for the HDR video sample subsequent thereto may be different. If the value of this field is 1, the current sample is the last HDR video sample to which the existing HDR information is applied, and the following samples may indicate that other HDR information may be applied. The hdr_sdr_transition_flag field may be a flag indicating whether the current HDR video sample is the last HDR sample, and the following samples are SDR samples. If the value of this field is 1, this may indicate that the corresponding sample is the last HDR sample, followed by the SDR samples.

In the illustrated embodiment d22020, HDR information may be included in a visual sampel group entry. If the same HDR related flag can be applied to one or more video samples present in one track, HDR flags, such as the illustrated embodiment, may be further included in the visual sample group entry.

The depicted HDR related flags have the same meaning as the flags of the same name described above, but in this case, the corresponding sample group may be described. That is, the hdr_flag field may indicate whether the corresponding sample group is a group composed of HDR video samples. The hdr_param_set field may indicate an identifier indicating a combination of HDR related parameters applied in a corresponding sample group. The hdr_type_transition_flag field may indicate whether HDR information (parameter) related to HDR video samples is changed to other HDR information and applied in the corresponding HDR video sample group. The hdr_sdr_transition_flag field may indicate whether to switch from HDR to SDR in the corresponding video sample group. The sdr_hdr_transition_flag field may indicate whether HDR transition is performed in SDR within a corresponding video sample group. The sdr_compatibility_flag field may indicate whether HDR video samples in the corresponding video sample group are compatible with a decoder / display supporting SDR.

In the illustrated embodiment d22030, HDR information may be included in a visual sampel group entry. If the same HDR information (parameter) can be applied to one or more video samples present in one media file or fragment, the hdr_flag field and the HDR configuration box may be further included in the visual sample group entry as shown in the illustrated embodiment. .

Here, the hdr_flag field may have the same meaning as the hdr_flag field in the aforementioned visual sample group entry. The information in the HDR configuration box may have the same meaning as the information in the HDR configuration box described above. In this case, however, each piece of information may be described for the corresponding sample group. That is, the information in the HDR configuration box can provide default HDR information (parameters) that can be commonly applied to HDR video samples of the corresponding sample group. Here, the average_frame_luminance_level field and / or the max_frame_pixel_luminance field may have different meanings. The average_frame_luminance_level field may indicate a maximum value among average values of luminance levels of each video sample belonging to the corresponding sample group. The max_frame_pixel_luminance field may indicate the largest value among the maximum values of pixel luminance of each video sample belonging to the corresponding sample group.

In the illustrated embodiment d22040, the HDR information may be included in the visual sampel entry. As initialization information required to decode respective video samples present in one media file or fragment, HDR flag information related to the sample may be further included in the visual sample entry.

The hdr_flag field may indicate whether the associated video track or sample includes the HDR video sample. The hdr_param_set field may indicate an identifier indicating a combination of HDR related parameters applied to a video sample. The hdr_type_transition_flag field may indicate whether HDR information (parameter) for an associated video track or sample is changed and thus other HDR information is applied. The hdr_sdr_transition_flag field may be a flag indicating whether an associated video track or sample is switched from HDR to SDR. The sdr_hdr_transition_flag field may be a flag indicating whether an associated video track or sample is switched from SDR to HDR. The sdr_compatibility_flag field may be a flag indicating whether an associated video track or sample is compatible with the SDR decoder / display.

In the illustrated embodiment d22050, HDR information may be included in a visual sampel entry. As initialization information required to decode respective video samples present in one media file or fragment, HDR information (parameter) related to the sample may be further included in the visual sample entry.

The hdr_flag field may indicate whether the associated video track or sample includes the HDR video sample. The hdr_config box is an HDR configuration box and may include HDR information (parameters) about an associated video track or sample. Each of the information included in the above-described HDR configuration box may be as described above. In this case, however, each of the pieces of information may describe the associated video track or samples.

FIG. 23 is a diagram illustrating a method of defining HDR information in a HEVC sample entry, an HEVC configuration box, or an HEVC decoder configuration record according to an embodiment of the present invention.

In the illustrated embodiment d23010, the HDR information may be included in the HEVC sample entry HEVCSampleEntry. As initialization information required to decode respective HEVC samples present in the media file or fragment, HDR information related to each HEVC sample or the like may be added as shown. The added HDR information may be added in the form of the above-described HDR configuration box according to an embodiment. According to an embodiment, the HDR information may be added in the same manner as AVC sample entry (AVCSampleEntry), AVC2 sample entry (AVC2SampleEntry), SVC sample entry (SVCSampleEntry), MVC sample entry (MVCSampleEntry).

In the illustrated embodiment d23020, the HDR information may be included in the HEVC Configuration Box. As initialization information required to decode respective HEVC samples present in the media file or fragment, HDR information related to each HEVC sample or the like may be added as shown. The added HDR information may be added in the form of the above-described HDR configuration box according to an embodiment. According to an embodiment, the HDR information may be added in the same manner as in the AVC configuration box (AVCConfigurationBox), the SVC configuration box (SVCConfigurationBox), the MVC configuration box (MVCConfigurationBox), and the like.

In the illustrated embodiment d23030, the HDR information may be included in the HEVC decoder configuration record (HEVCDecoderConfigurationRecord). As initialization information required to decode respective HEVC samples present in the media file or fragment, HDR information related to each HEVC sample or the like may be added as shown. The added HDR information may be added in the form of the above-described HDR configuration box according to an embodiment. In this case, whether to add the HDR configuration box may be performed by the hdr_flag field. According to an embodiment, the HDR information may be added in the same manner as the AVC decoder configuration record (AVCDecoderConfigurationRecord), the SVC decoder configuration record (SVCDecoderConfigurationRecord), the MVC decoder configuration record (MVCDecoderConfigurationRecord), and the like.

24 is a diagram illustrating a method of storing / delivering HDR information by defining an HDR information SEI box according to an embodiment of the present invention.

The present invention defines an HDR information SEI box (HDRInformationSEIBox) (d24010). This box contains an SEI NAL unit, which may have an SEI message containing HDR related information. The HDR information SEI box may be called hisb box.

The HDR information SEI box may be included in the visual sample entry, the HEVC configuration box and / or the HEVC sample entry, as shown in the illustrated embodiments (d24020, d24030, d24040). Also, according to an embodiment, it may be included in an AVC sample entry, an MVC sample entry, and an SVC sample entry.

25 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 (ISOBMFF parser) 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 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.

If the receiver is capable of HDR display, quality enhancement may be performed on the HDR video. In this case, 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. When the scene / frame-specific metadata cannot be processed, the HDR display block of the receiver may play the received HDR video data.

When scene / frame-specific metadata can be processed, scene-by-scene HDR video quality enhancement may be performed. At this time, 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. In this case, 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.

FIG. 26 is a diagram illustrating an HDR configuration box according to another embodiment of the present invention. FIG.

One embodiment of the present invention proposes a method of signaling information about enhanced color mapping for HDR configuration. The receiver can switch the operation of the decoder and renderer by obtaining this information at the file interpretation level. This information may be defined according to a storage file format and / or a segment file format. In addition to ATSC 3.0, this information may be defined according to a DVB file format and a DECE CFF (Digital Entertainment Content Ecosystem Common File Format).

The information about the enhanced color mapping may include content color gamut information and / or color remapping information, and the broadcasting system may output desaturated color video output during display compatible color conversion through content color gamut. Color remapping information can be used to provide maximum rendering intent when converting to a different color space. The receiver may service announce that decoder initialization, renderer initialization, and color conversion are possible through the acquisition of this information at the system end. The information about enhanced color mapping can be defined according to trak, vmhd, trex, visual sample group entry, visual sample entry, avc sample entry, hevc sample entry, etc., and also within defined colr boxes defined under vhmd. have.

For example, when the content of P3 is converted into a matrix of 2020 color gamut, the original color cannot be expressed. In this case, the broadcasting system according to an embodiment of the present invention outputs video through content color gamut. This can prevent saturation and poor display.

Referring to this figure, the HDR configuration box may have an hdr_config field. The hdr_config field may further include a content color gamut type field, a number_of_primaries_minus_three field, a content_colour_gamut_primaries_x [c] field, a content_colour_gamut_primaries_y [c] field, a white_point_x field, and / or a white_point_y field.

The content color gamut type field indicates the color gamut of the content. The value of this field may use the value of colour_primaries defined in the ISO / IEC 230082 document. The value 255 of this field may represent a randomly designated coordinate value. The color gamut of the content may be represented as a coordinate value of the colors in the color space.

The number_of_primaries_minus_three field represents the number of color coordinates for expressing color gamut. For example, when the color gamut is expressed in RGB, the number of color coordinates represented by this field is three.

The content_colour_gamut_primaries_x [c] field and the content_colour_gamut_primaries_y [c] field indicate the x-axis and y-axis coordinate values of each color.

The white_point_x field and the white_point_y field indicate coordinate values of a white point.

27 is a diagram illustrating a system from production stage to rendering stage of HDR content according to an embodiment of the present invention.

In order to apply HDR to the content, the production phase converts the color and brightness range of the content into a color and brightness range suitable for the creator's intention by applying OETF, color conversion, and subsampling, and then performs a video encoding process. Can be.

When the receiver receives the HDR stream for transmitting the encoded HDR content, the receiver may perform decoding and convert the color of the HDR content. In this case, in order to render the HDR content on a specific display of the receiver while maintaining the rendering intention at the time of production of the HDR content, the receiver may perform a color conversion process, which is a process of converting the color of the HDR content. The receiver may convert the color of the content through a tone mapping algorithm as shown in this figure.

The receiver maps the color gamut of the content directly to the color gamut of the display, thereby rendering the rendering intent at the time of production rather than mapping a container color gamut or mastering color gamut to the color gamut of the display. You can convert the color of the content with less loss while keeping it better. Here, the container color gamut represents the color gamut of the transmission format for transmitting content, and the mastering color gamut represents the color gamut of the mastering display used when mastering the content.

28 is a diagram illustrating an ISOBMFF structure and a colr box according to an embodiment of the present invention.

The ISOBMFF (1449612) standard defines a general format for organizing media data, including timing and structure for organizing media files. This standard defines segment structure, transmission media file structure, RTP, MPEG2 TS encapsulation formats for transmission.

The ISOBMFF contains information in the form of a box that describes the functions and attributes of the media data. According to an embodiment of the present invention, a visual sample entry exists in a minf box in a mvhd box, and the visual sample entry may include a colr box in the form of an extension box. In addition, color related information for configuring HDR may be defined in a colr box.

The colr box may include a conent color gamut type field and / or a color remapping information field. The conent color gamut type field indicates the type of color gamut of the content, and the color remapping information field indicates color remapping information. The color remapping information indicates information necessary for converting the color space of the content to another color space. The receiver can use the above fields to render the content while maintaining the rendering intent at the time of production even in a situation different from the master color given the display property.

29 is a diagram showing the configuration of a colour_remapping_info descriptor according to an embodiment of the present invention.

The color remapping information indicated by the color remapping information field may include information included in the colour_remapping_info descriptor shown in this figure. The semantics of the colour_remapping_info descriptor are defined in ISO / IEC 230092. Furthermore, parts shown in this figure represent information for prepost tone mapping and / or remap matrix conversion.

30 is a view illustrating a color conversion process according to an embodiment of the present invention.

The color remapping information may include information for the three processes shown in this figure. In order to represent the mastered HDR content within the performance range of the display while maintaining the rendering intent, the luminance component and the color signal of the HDR content must be effectively and properly converted. The receiver maintains the intent to render the colors of the HDR content through prematrix tone mapping, color remapping matix, and / or postmatrix tone mapping, as shown in this figure. You can switch to match the display characteristics.

The free matrix tone mapping process is performed using three sampled functions defined in the standard (e.g., ST20941). At this time, these functions receive the color component value and output the color component value. The free matrix tone mapping process may use a 1D LUT (1 dimension look up table). The color remapping matrix process is performed using the matrix defined in the standard (e.g., ST20941). At this time, the element used in this matrix may have a value from 4 to 4. The post matrix tone mapping process is performed using three sampled functions defined in the standard (e.g., ST20941). At this time, these functions receive the color component value and output the color component value. The free matrix tone mapping process may use a 1D LUT (1 dimension look up table).

FIG. 31 is a view illustrating a temporal layer structure of LHEVC (LayeredHEVC) or SHVC according to an embodiment of the present invention. FIG.

One embodiment of the present invention may provide a method for signaling HDR information and / or color gamut scalable information in an LHEVC or SHVC file format environment (ISO / IEC 1449615).

The broadcast system according to an embodiment of the present invention provides a base layer for SDR and enhancement for HDR through scalable coding so that an existing SDR receiver can be used in a system that provides HDR content. A layer may be created and transmitted.

The SHVC file format can provide color primary information through visual sample entries of each track, but there is no way to provide color gamut information when providing scalability as a layer configuration. That is, the SHVC file format that provides color gamut scalability has no information indicating color gamut corresponding to each operation point.

An embodiment of the present invention may define the color gamut information in the SHVC file format to allow the receiver to recognize the SHVC stream as a stream capable of color gamut scalability when receiving the SHVC stream. The receiver can initialize the decoder and renderer with the color gamut information in the SHVC file format, and the color gamut information included at the system level can process the color gamut information before processing the media data and inform the user of the stream being viewed. Can be.

Although the standard defines a scalable type value for HDR as quality, the layer constituting HDR is a process of processing linear, which is an output of decoding, so it should have a different value. In addition, when the video compression technology for HDR is applied later, it is necessary to have a value different from the existing quality scalability to prevent a malfunction of the receiver. In the present invention, the scalable mask value for HDR is extended and the reference relationship is extended and newly defined. I would like to.

One embodiment of the present invention may provide a structure of an SHVC file format for allowing an existing SDR receiver to be used in a system for providing HDR content.

According to another embodiment of the present invention, operation point information and / or track color gamut scalability information may be added to the SHVC file format in order to use an existing SDR receiver in a system for providing HDR content.

Another embodiment of the present invention may add a new type value for the HDR service so that the existing SDR receiver can be used in the system for providing the HDR content.

LayeredHEVC can configure one or more layered collection sets to configure visual scaling such as quality, resolution, depth, frame rate, view, and depth. Visual scaling can be configured with the output set of these layers, and this configuration can be defined through constraints of profile, level and / or tier. Each layer may be referred to as a temporal id (operation point) name. When LHEVC is encapsulated in file format, it can consist of the following cases. 1) all the layers in one track, 2) each layer in its own track, 3) a hybrid, one track containing all layer, and one or more singlelayer tracks each containing a layer that can be independently coded, 4) the expected operation points each in a track (eg the HEVC base, a stereo pair, a multiview scene)

Referring to the bottom of this figure, when encoding an SVC stream capable of SDR and HDR through two layers, the base layer of the SHVC stream transmits an SDR color gamut and the enhancement layer provides a heterogeneous color providing WCG. You can send a random scalability.

32 is a diagram illustrating a decoding process for reproducing a file format according to an embodiment of the present invention.

When the media stream is received, the receiver's file format client can parse the metadata for the decoder in the file's moov box and the media data in the file's mdat box via the file parser. The file format client of the receiver may extract metadata through the box info manager and transfer the extracted metadata to the decoder and the renderer to proceed with the initialization of the decoder renderer. The file format client of the receiver may select tracks and samples by using metadata extracted through the track and sample selector and deliver them to the sample buffer according to the operation point. The media decoder may buffer and / or decode samples using decoding timing information and decoder initialization information in a moov box delivered from a box info manger. The renderer can render linear data, the output of the media doceder, using color gamut information and / or a process for HDR, delivered from the Box info manager.

33 is a diagram showing the structure of an SHVC file format according to an embodiment of the present invention.

The initialization segment may include a moov box, and the moov box may include encoding information and layer information of media data. The decoder of the receiver can initialize the decoder through the metadata in the moov box and announce the service available to the user.

The SHVC file format may include OperationPointsInformationBox (oinf box) and / or TrackContentBox (tcon box), using these boxes the profile of the scalable layer, the tier information of the scalable layer, the list of tracks and / or the list of layers Can be transmitted.

The SHVC file format includes a visual sample entry of LHEVC or SHVC. The visual sample entry may describe decoder configuration information, group samples, and define attributes of each group. On the other hand, the visual sample entry (colr box) currently defines only the color gamut for one layer and does not define the color gamut information for scalable layers.

One embodiment of the present invention provides color gamut information for scalable layers by extending LHEVCDecoderConfigurationRecord, extending a Scif box, extending a Colr box, extending an Oinf box, and / or extending an inter-track reference type 4CC value for HDR. Can be signaled.

According to one embodiment of the invention, Trak describes information about the track representing the LHEVC stream, tkhd describes Minf information about the media of the LHEVC stream, and stbl represents the frame of video transmitted by the LHEVC stream. The information on the sample is described, shv1 and IhvC describe information on a sample entry indicating one unit in the LHEVC stream, and the LHEVC config record may describe information for decoding the sample entry described by IhvC. sgpd can describe information about grouped samples, and scif can describe information about each group.

34 is a diagram showing the configuration of an LHEVCDecoderConfigurationRecord of a visual sample entry according to an embodiment of the present invention.

LHEVCDecoderConfigurationRecord can describe information about a sample through a visual sample entry (sample entry). LHEVCDecoderConfigurationRecord can provide general information for decoding of samples.

LHEVCDecoderConfigurationRecord can define extended color gamuts to provide scalability color gamuts. The LHEVCDecoderConfigurationRecord may include a colour_primaries_count field and / or an extension_colour_primaries field. The colour_primaries_count field may indicate the number of color gamuts applied to a sample. If one color gamut is applied to one layer, this field may indicate the number of layers applied to the sample. The value of the colour_primaries_count field may have the same value as the value of the num_operation_points field of the onif box. The num_operation_points field may indicate the number of operation points. The number of operation points may indicate the number of scalability layers. The extension_colour_primaries field may indicate the color gamut of each layer.

35 is a diagram showing the structure of an SHVC file format according to another embodiment of the present invention.

An embodiment of the present invention may transmit a file using two tracks (track 1 and track 2) based on the SHVC file format. The SHVC file according to an embodiment of the present invention has two tracks, and may include two trak boxes describing information about each track.

According to one embodiment of the invention, the reference relationship between two tracks can be described through the reference type of the oref box in the tref box. The receiver may identify that track 2 is a track constituting the scalability of the SHVC and has a dependency relationship with track 1 through a reference type value of the Oref box.

According to an embodiment of the present invention, since track 1 is a base tier or base stream for creating an existing SDR, the sample entry for track 1 may have the same structure as the sample entry of HEVC. . However, the sample entry for track1 may include a sgpd sample group box, and the sgpd sample group box may describe a relationship between track1, which is a corresponding track, and an enhancement track (track 2) for scalable.

36 illustrates a map of a file format consisting of two tracks according to an embodiment of the present invention.

An embodiment of the present invention may define a reference relationship with a first track by defining a 4CC reference type of an oref box in a tref box in a tkhd box of a second track.

Referring to the right side of this figure, the tref box may define an id value of a track that has a reference relationship with the track. The tref box may include a track reference type box. The track reference type box may include a reference_type field and / or a track_ID field.

The track_ID field may indicate information for identifying another track referenced by the corresponding track. This field may provide a reference relationship from the track to another track. The value of this field cannot be reused and cannot have a value of zero.

The reference_type field may indicate the type of reference relationship between the corresponding track and another track. The value of this field may have one of the following values. The value 'hint' in this field can indicate that the track referenced refers to the original media for the hint track that is the track, 'cdsc' can indicate that the track refers to the track referenced, and 'font' Can indicate that the trick uses a font defined in the track referenced or transmitted by the referenced track, and 'hind' can indicate that the track depends on the referenced hint track. Can be used when the referenced hint track is used, 'vdep' can indicate that the track contains additional depth video information for the referenced video track, and 'vplx' indicates that track Indicates that this referenced track contains subtitle, timed text, or overlay graphic information for any track in the alternate group to which the trick belongs or to which the trick belongs. There.

According to an embodiment of the present invention, the reference_type field may indicate a reference relationship between a plurality of streams such as an AVC stream + an HEVC residual stream, an HEVC stream + an HEVC residual stream, and the like. The value 'hdrb' of the reference_type field may configure the HDR video together with the track to which the track is referenced, and this track may indicate that the track is a base layer for configuring the HDR video, and the 'hdre' refers to the track. The HDR video may be configured together with the tracks, and at this time, the track may represent an enhancement layer for composing the HDR video.

37 is a diagram showing the configuration of a scif box according to an embodiment of the present invention.

The scif box may describe the samples grouped per entry point in the sample group entry. The scif box may occur when the group type has a 'scif' value indicating scalable grouping.

According to an embodiment of the present invention, the scif box may include a colp box when providing color gamut scalability, and the colp box may describe color gamut information of a corresponding group. The receiver can use the colp box to know in which color space the current content can be extended and can initialize the decoder and renderer using the information described in the colp box.

The colp box (colour_primaryBox) may include a colour_primaries_count field and / or an extension_colour_primaries field. The colour_primaries_count field may indicate the number of color gamuts applied to the corresponding group. If one color gamut is applied to one layer, this field may indicate the number of layers applied to the group. The value of the colour_primaries_count field may have the same value as the value of the num_operation_points field of the onif box. The num_operation_points field may indicate the number of operation points. The number of operation points may indicate the number of scalability layers. The extension_colour_primaries field may indicate the color gamut of each layer.

38 is a diagram showing the configuration of an onif box according to an embodiment of the present invention.

The onif box may describe the attributes of each operation point in the sample group entry. One embodiment of the present invention can describe color gamut information that can be configured in the case of providing color gamut scalability by extending color gamut information in an onif box.

According to an embodiment of the present invention, the onif box may include a scalability_mask field, the scalability_mask field may have an index value (4) indicating that scalability is color gamut scalability, and the onif box according to this value Color gamut information applied when color gamut scalability is provided can be described.

According to an embodiment of the present invention, the onif box may include as many scalable_colour_primaries fields as the number of operation points indicated by the num_operation_points field. The scalable_colour_primaries field may indicate color gamut information applied to a corresponding operation point.

According to an embodiment of the present invention, when the index value indicated by the scalability_mask field is 4, the scalability dimension may indicate colour_primaries indicating color gamut information, and the scalabilityId may be mapped to operationPointId.

39 is a view showing the position of the colr box and the configuration of the expanded colr box according to an embodiment of the present invention.

According to an embodiment of the present invention, the ISOBMFF has a minf box (Media Information Box) under the mvhd (MovieHeaderBox) box and a colr box under the minf box for describing media data.

The colr box according to an embodiment of the present invention may describe color gamuts (colour_primaries) as visual sample entries. This box can define the color gamut supported by each track level.

An embodiment of the present invention can extend the colr box to describe two or more color gamuts that can be supported in the current track when a track providing color gamut scalability occurs.

When one or more color gamut scalability is provided, an embodiment of the present invention may announce that content can be expressed in two or more color spaces through the expansion of a colr box, and two or more color gamut information The decoder and renderer can be initialized according to the method.

Referring to the bottom of this figure, an extended colr box according to an embodiment of the present invention may include a colour_primaries_count field and / or an extension_colour_primaries field. The colour_primaries_count field may indicate the number of color gamuts applied to the corresponding track. If one color gamut is applied to one layer, this field may indicate the number of scalable layers applied to the corresponding track. The value of the colour_primaries_count field may have the same value as the value of the num_operation_points field of the onif box. The num_operation_points field may indicate the number of operation points. The number of operation points may indicate the number of scalability layers. The extension_colour_primaries field may indicate the color gamut of each layer.

The colr box according to another embodiment of the present invention may be included in a HEVC file format (1449615) visual sample entry.

40 is a view showing a broadcast signal transmission method according to an embodiment of the present invention.

The broadcast signal transmission method according to an embodiment of the present invention comprises generating a layered high efficiency video codec (LHEVC) stream by encoding high dynamic range (HDR) video (SL40010), and generating a file including the LHEVC stream. Step SL40020, generating the layered coding transport (LCT) packet from the generated file (SL40030), generating an Internet Protocol (IP) packet including the LCT packet (SL40040), including the IP packet Generating a link layer packet (SL40050) and / or transmitting the link layer packet (SL40060). The LHEVC stream may include a base layer for Standard Dynamic Range (SDR) rendering and an enhancement layer for HDR rendering, the file including a decoder configuration box describing information for decoding of the LHEVC stream, The decoder configuration box may include HDR related information of the LHEVC stream.

According to another embodiment of the present invention, the HDR related information may include count information indicating the number of color gamuts applied to the LHEVC stream and information indicating color gamuts applied to the LHEVC stream.

According to another embodiment of the present invention, the LHEVC stream includes one or more visual sample entries, the file includes sample entry information describing the visual sample entry, and the decoder configuration box It may be included in the sample entry information.

According to another embodiment of the present invention, the file includes an operation point box describing information about an operation point of the LHEVC stream, and the operation point box indicates an operation indicating the number of operation points applied to the LGEVC stream. Including the point number information, the count information may have the same value as the operation point number information.

According to another embodiment of the present invention, the file includes a first track for transmitting the base layer and a second track for transmitting the enhancement layer, and the file describes information about the first track. A first track box and a second track box describing information about the second track, wherein the second track box identifies the first track and the first track in reference relation with the second track; The second track may include reference relationship type information for identifying that it is an enhancement layer for HDR rendering in relation to the first track.

According to another embodiment of the present invention, the file includes information indicating the type of color gamut used in the HDR video, information indicating the number of colors used to define the color gamut, and to define the color gamut. Information indicating a coordinate value on a color space of a used color and information indicating a coordinate value of a white point used to define the color gamut may be included.

41 is a view showing a broadcast signal receiving method according to an embodiment of the present invention.

In the broadcast signal reception method according to an embodiment of the present invention, the method includes receiving a link layer packet (SL41010), parsing an IP packet from the link layer packet (SL41020), and parsing the LCT packet from the IP packet. (SL41030), parsing a file from the LCT packet (SL41040), parsing a Layered High Efficiency Video Codec (LHEVC) stream from the file (SL41050) and / or decoding the parsed LHEVC stream (SL41060) ) May be included. The file includes a decoder configuration box that describes information for decoding a layered high efficiency video codec (LHEVC) stream that transmits high dynamic range (HDR) video, wherein the decoder configuration box contains the HDR related information of the LHEVC stream. The LHEVC stream may include a base layer for SDR (Standard Dynamic Range) rendering and an enhancement layer for HDR rendering.

42 is a diagram illustrating a configuration of a broadcast signal transmission apparatus according to an embodiment of the present invention.

The broadcast signal transmission apparatus L42010 according to an embodiment of the present invention includes an encoder L42020 for encoding a high dynamic range (HDR) video to generate a layered high efficiency video codec (LHEVC) stream, and a file including the LHEVC stream. A file generation unit (L42030) for generating a packet, an LCT packet generation unit (L42040) for generating a layered coding transport (LCT) packet, and an IP packet for generating an IP (Internet Protocol) packet including the LCT packet. It may include a generation unit (L42050), a link layer packet generation unit (L42060) for generating a link layer packet including the IP packet and / or a transmission unit (L42070) for transmitting the link layer packet. The LHEVC stream may include a base layer for Standard Dynamic Range (SDR) rendering and an enhancement layer for HDR rendering, the file including a decoder configuration box describing information for decoding of the LHEVC stream, The decoder configuration box may include HDR related information of the LHEVC stream.

43 is a diagram showing the configuration of a broadcast signal receiving apparatus according to an embodiment of the present invention.

The broadcast signal reception apparatus L43010 according to an embodiment of the present invention includes a receiver L43020 for receiving a link layer packet, a link layer packet processor L43030 for parsing an IP packet from the link layer packet, and the IP packet from the IP packet. An IP packet processor (L43040) for parsing LCT packets, an LCT packet processor (L43050) for parsing a file from the LCT packet, a file processor (L43060) for parsing a Layered High Efficiency Video Codec (LHEVC) stream from the file, and / or It may include a decoder (L43070) for decoding the parsed LHEVC stream. The file includes a decoder configuration box that describes information for decoding a layered high efficiency video codec (LHEVC) stream that transmits high dynamic range (HDR) video, wherein the decoder configuration box contains the HDR related information of the LHEVC stream. The LHEVC stream may include a base layer for SDR (Standard Dynamic Range) rendering and an enhancement layer for HDR rendering.

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. In addition, 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.

For convenience of description, each drawing is divided and described, but it is also possible to design a new embodiment by merging the embodiments described in each drawing. And, according to the needs of those skilled in the art, it is also within the scope of the present invention to design a computer-readable recording medium on which a program for executing the previously described embodiments is recorded.

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.

On the other hand, it is possible to implement the method proposed by the present invention as a processor-readable code in a processor-readable recording medium provided in a network device. 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, CDROM, 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 through 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.

In addition, although the preferred embodiment of the present invention has been shown and described above, the present invention is not limited to the above-described specific embodiment, the technical field to which the invention belongs without departing from the spirit of the invention claimed in the claims. Of course, various modifications can be made by those skilled in the art, and these modifications should not be individually understood from the technical spirit or the prospect of the present invention.

In addition, in this specification, both the object invention and the method invention are described, and description of both invention can be supplementally applied as needed.

It is understood by those skilled in the art that various changes and modifications can be made in the present invention without departing from the spirit or scope of the invention. Accordingly, it is intended that the present invention cover the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.

Reference is made herein to both apparatus and method inventions, and the descriptions of both apparatus and method inventions may be complementary to one another.

Various embodiments have been described in the best mode for carrying out the invention.

The present invention is used in the field of providing a series of broadcast signals.

It will be apparent to those skilled in the art that various changes and modifications can be made in the present invention without departing from the spirit or scope of the invention. Accordingly, it is intended that the present invention cover the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.

Claims (14)

A method of encoding a high dynamic range (HDR) video to generate a layered high efficiency video codec (LHEVC) stream, The LHEVC stream includes a base layer for SDR (Standard Dynamic Range) rendering and an enhancement layer for HDR rendering; Generating a file including the LHEVC stream, The file includes a decoder configuration box describing information for decoding the LHEVC stream, the decoder configuration box containing HDR related information of the LHEVC stream; Generating a layered coding transport (LCT) packet from the generated file; Generating an Internet Protocol (IP) packet including the LCT packet; Generating a link layer packet comprising the IP packet; And Transmitting the link layer packet; Broadcast signal transmission method comprising a. The method of claim 1, The HDR related information includes count information indicating the number of color gamuts applied to the LHEVC stream and information indicating color gamuts applied to the LHEVC stream. The method of claim 2, The LHEVC stream includes one or more visual sample entries, the file includes sample entry information describing the visual sample entry, And the decoder configuration box is included in the sample entry information. The method of claim 1, The file includes an operation point box that describes information about an operation point of the LHEVC stream, the operation point box includes operation point number information indicating the number of operation points applied to the LGEVC stream, The count information is a broadcast signal transmission method having the same value as the operation point number information. The method of claim 1, The file includes a first track for transmitting the base layer and a second track for transmitting the enhancement layer, The file includes a first track box describing information about the first track and a second track box describing information about the second track, The second track box is identification information identifying the first track that is in reference relationship with the second track and a reference relationship identifying that the second track is an enhancement layer for HDR rendering in relation to the first track. Broadcast signal transmission method comprising type information. The method of claim 1, The file includes information indicating the type of color gamut used in the HDR video, information indicating the number of colors used to define the color gamut, and a coordinate value in the color space of the color used to define the color gamut. And information representing the coordinate value of the white point used to define the color gamut. Receiving a link layer packet; Parsing an IP packet from the link layer packet; Parsing the LCT packet from the IP packet; Parsing a file from the LCT packet, The file includes a decoder configuration box that describes information for decoding a layered high efficiency video codec (LHEVC) stream that transmits high dynamic range (HDR) video, wherein the decoder configuration box contains the HDR related information of the LHEVC stream. Including; Parsing a Layered High Efficiency Video Codec (LHEVC) stream from the file, The LHEVC stream includes a base layer for SDR (Standard Dynamic Range) rendering and an enhancement layer for HDR rendering; And Decoding the parsed LHEVC stream; Broadcast signal receiving method comprising a. The method of claim 7, wherein The HDR-related information includes count information indicating the number of color gamuts applied to the LHEVC stream and information indicating color gamuts applied to the LHEVC stream. The method of claim 8, The LHEVC stream includes one or more visual sample entries, the file includes sample entry information describing the visual sample entry, And the decoder configuration box is included in the sample entry information. The method of claim 7, wherein The file includes an operation point box that describes information about an operation point of the LHEVC stream, the operation point box includes operation point number information indicating the number of operation points applied to the LGEVC stream, The count information is a broadcast signal receiving method having the same value as the operation point number information. The method of claim 7, wherein The file includes a first track for transmitting the base layer and a second track for transmitting the enhancement layer, The file includes a first track box describing information about the first track and a second track box describing information about the second track, The second track box is identification information identifying the first track that is in reference relationship with the second track and a reference relationship identifying that the second track is an enhancement layer for HDR rendering in relation to the first track. Broadcast signal receiving method comprising type information. The method of claim 7, wherein The file includes information indicating the type of color gamut used in the HDR video, information indicating the number of colors used to define the color gamut, and a coordinate value in the color space of the color used to define the color gamut. And information representing the coordinate value of the white point used to define the color gamut. An encoder that encodes high dynamic range (HDR) video to produce a layered high efficiency video codec (LHEVC) stream. The LHEVC stream includes a base layer for SDR (Standard Dynamic Range) rendering and an enhancement layer for HDR rendering; A file generator for generating a file including the LHEVC stream, The file includes a decoder configuration box describing information for decoding the LHEVC stream, the decoder configuration box containing HDR related information of the LHEVC stream; An LCT packet generator for generating a layered coding transport (LCT) packet from the generated file; An IP packet generator configured to generate an Internet Protocol (IP) packet including the LCT packet; A link layer packet generator configured to generate a link layer packet including the IP packet; And A transmitter for transmitting the link layer packet; Broadcast signal transmission apparatus comprising a. A receiver for receiving a link layer packet; A link layer packet processor parsing an IP packet from the link layer packet; An IP packet processing unit for parsing the LCT packet from the IP packet; An LCT packet processing unit for parsing a file from the LCT packet, The file includes a decoder configuration box that describes information for decoding a layered high efficiency video codec (LHEVC) stream that transmits high dynamic range (HDR) video, wherein the decoder configuration box contains the HDR related information of the LHEVC stream. Including; A file processor for parsing a layered high efficiency video codec (LHEVC) stream from the file, The LHEVC stream includes a base layer for SDR (Standard Dynamic Range) rendering and an enhancement layer for HDR rendering; And A decoder for decoding the parsed LHEVC stream; Broadcast signal receiving apparatus comprising a.

Images