WO2016186391A1

WO2016186391A1 - Broadcast signal transmission device, broadcast signal reception device, broadcast signal transmission method, and broadcast signal reception method

Info

Publication number: WO2016186391A1
Application number: PCT/KR2016/005077
Authority: WO
Inventors: 윤준희; 이장원; 김진필
Original assignee: 엘지전자 주식회사
Priority date: 2015-05-15
Filing date: 2016-05-13
Publication date: 2016-11-24

Abstract

A method for transmitting a broadcast signal according to one embodiment of the present invention comprises the steps of: generating an ISO base media file format (ISOBMFF) file including data for a broadcast content provided by a broadcasting system; generating at least one segment including the generated ISOBMFF file; generating a broadcast signal including the at least one generated segment; and transmitting the broadcast signal, wherein the ISOBMFF file includes output control number information indicating the number of devices which can copy and then output a media factor expressed by the ISOBMFF file.

Description

A broadcast signal transmitting device, a broadcast signal receiving device, a broadcast signal transmitting method, and a broadcast signal receiving method

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

As analog broadcast signal transmission is terminated, various techniques for transmitting and receiving digital broadcast signals have been developed. The digital broadcast signal may include a larger amount of video / audio data than the analog broadcast signal, and may further include various types of additional data as well as the video / audio data.

That is, the digital broadcasting system may provide high definition (HD) images, multichannel audio, and various additional services. However, for digital broadcasting, data transmission efficiency for a large amount of data transmission, robustness of a transmission / reception network, and network flexibility in consideration of a mobile receiving device should be improved.

In accordance with the object of the present invention and as included and outlined herein, the present invention provides a system and an associated signaling scheme that can effectively support next-generation broadcast services in an environment that supports next-generation hybrid broadcasting using terrestrial broadcasting networks and Internet networks. Suggest.

According to the present invention, there is an effect that copy control is possible in units of broadcast service, broadcast content, component, track, sample, adaptation set, presentation, segment and / or sub-segment in the broadcast system.

According to the present invention, even if there is a hack on broadcast signaling information, since copy control on broadcast content can be performed, there is an effect that protection on broadcast content can be enhanced.

According to the present invention, there is an effect that a broadcaster can provide various broadcast viewing plans, diversify the range of copy control allowed by the corresponding viewing plan, and diversify the scope of the broadcast business.

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 illustrates a USBD and an S-TSID 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 is a block diagram of a receiver according to an embodiment of the present invention.

9 illustrates an ISO Base Media File Format (ISOBMFF) according to an embodiment of the present invention.

10 is a diagram illustrating boxes for defining extended information in an ISOBMFF according to an embodiment of the present invention.

11 illustrates a copy control box (cpcl box) according to an embodiment of the present invention.

12 is a diagram illustrating a track header box ('tkhd' box, track header box) of an ISOBMFF according to an embodiment of the present invention.

FIG. 13 illustrates a vmhd box, an smhd box, an hmhd box, and an nmhd box of an ISOBMFF according to one embodiment of the present invention. FIG.

FIG. 14 illustrates a trek box (track extends box) of an ISOBMFF according to an embodiment of the present invention. FIG.

FIG. 15 illustrates a tfhd box (track fragment header box) of an ISOBMFF according to an embodiment of the present invention. FIG.

16 illustrates a track run box of an ISOBMFF according to an embodiment of the present invention.

17 illustrates a visual sample group entry of an ISOBMFF file according to an embodiment of the present invention.

FIG. 18 illustrates a visual sample entry of an ISOBMFF file according to an embodiment of the present invention. FIG.

FIG. 19 illustrates a pssh box of a protection system specific header box (ISOBMFF) according to an embodiment of the present invention.

20 illustrates a tenc box (track encryption box) of ISOBMFF according to an embodiment of the present invention.

FIG. 21 is a diagram illustrating a senc box (sample encryption box) of ISOBMFF according to an embodiment of the present invention. FIG.

FIG. 22 illustrates CencSampleEncryptionInformationVideoGroupEntry and CencSampleEncryptionInformationGroupEntry of ISOBMFF according to an embodiment of the present invention. FIG.

23 illustrates a portion of a DASH system according to an embodiment of the present invention.

24 is a diagram showing the structure of a media presentation according to an embodiment of the present invention.

25 is a diagram illustrating a structure of a media presentation description (MPD) according to an embodiment of the present invention.

FIG. 26 illustrates a copy control element that may be defined in an MPD of MPEG-DASH according to an embodiment of the present invention.

27 is a diagram illustrating meanings of @schemeIdUri information and @value information according to an embodiment of the present invention.

FIG. 28 illustrates a common element of MPEG-DASH according to an embodiment of the present invention. FIG.

29 is a diagram illustrating an EssentialProperty element and a SupplementaryProperty element of MPEG-DASH according to an embodiment of the present invention.

30 is a diagram illustrating an accessibility element of MPEG-DASH according to an embodiment of the present invention.

FIG. 31 illustrates a Content Protection element of MPEG-DASH according to an embodiment of the present invention. FIG.

32 illustrates a SegmentEncryption element of MPEG-DASH according to an embodiment of the present invention.

33 is a view showing a ContentComponent element of MPEG-DASH according to an embodiment of the present invention.

34 illustrates a SegmentBase element of MPEG-DASH according to an embodiment of the present invention.

35 is a diagram illustrating an AdaptationSet element of MPEG-DASH according to an embodiment of the present invention.

36 illustrates a service list table (SLT) according to an embodiment of the present invention.

FIG. 37 is a view illustrating a range to which copy control information is applied according to a position where a usage rule descriptor is defined according to an embodiment of the present invention.

38 illustrates a UsageRuleInfo element included in a USBD and a copy control process using the same according to an embodiment of the present invention.

FIG. 39 is a diagram illustrating a UsageRuleInfo element included in an S-TSID and a copy control process using the same according to an embodiment of the present invention.

40 illustrates an MP table including a usage rule descriptor according to an embodiment of the present invention.

FIG. 41 is a diagram illustrating a method of transmitting a usage rule descriptor and a process of applying copy control information of a usage rule descriptor according to one embodiment of the present invention.

42 is a flowchart illustrating a method of transmitting and receiving broadcast signals according to an embodiment of the present invention.

43 is a diagram illustrating a broadcast system 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.

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. A service can be a collection of service components that are shown to the user as a whole, a component can be of multiple media types, a service can be continuous or intermittent, a service can be real or non-real time, and a real time service can 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.

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 referred to as 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).

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. According to an embodiment, 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 a destination IP address, a destination UDP port, and a source IP address of a transport packet carrying an SLS of a 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.

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.

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.

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.

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.

The present invention proposes a method of authorizing the watching right in a host such as a TV receiver. When the host (Host, eg TV, STB, PC, GateWay, etc.) is difficult to authenticate the subscriber viewing authority for viewing the service or content, the present invention authenticates the viewing authority using a method such as using a companion device. Suggest how to.

In general, to perform a CAS (Conditional Access System), an operation of transmitting CAS information to a receiver may be required. The CAS information may include key information necessary for decrypting the encrypted broadcast service or broadcast content and / or subscriber information so that only authorized subscribers can view the corresponding service / content. In this case, the subscriber information may be called viewing authority information. The broadcast content may mean a program of a broadcast service.

However, in a hybrid broadcast system, when only a broadcast network is connected and access to a broadband network is not possible, only one-way communication from a broadcast headend (H / E, Headend) to a receiver may be possible. In this case, a service provider such as a broadcaster cannot determine whether the corresponding receiver has a viewing authority with respect to a specific service or content.

Accordingly, the present invention defines a method for authenticating viewing authority in a TV receiver or the like, which is not capable of bidirectional communication. Through this, it may be determined whether the corresponding TV receiver has authority to view the corresponding service / content, and subscriber authentication may be performed. After authentication, the encrypted broadcast stream may be decrypted and provided.

The present invention provides a method for authenticating a TV receiver (host) using a companion device capable of bidirectional communication, a method of authenticating by attaching a device containing information capable of subscriber authentication and / or key information to a TV receiver, and subscriber authentication. A method of authenticating a software module including possible information and / or key information in a TV receiver is included. Through this, the TV receiver which cannot be authenticated due to the bidirectional communication with the broadcaster server and the like, can obtain the viewing authority and provide the encrypted broadcast service / content.

The receiver according to the illustrated embodiment is a Tuner, Physical Layer Controller, Physical Frame Parser, Link Layer Frame Processor, IP / UDP Datagram Filter, DTV Control Engine, Route Client, Segment Buffer Control, MMT Client, MPU reconstruction, Media Processor, Signaling Parser, DASH Client, 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.

The receiver according to the embodiment of the present invention may further include a viewing authority related control unit t8010. The viewing authority related control unit may further include an output interface and / or a CA (Conditional Access) module according to an embodiment.

The CA module may process key information and / or viewing authority information for decoding the scrambled broadcast stream. Here, the scrambled broadcast stream may mean an encrypted broadcast stream. The CA module may process information and deliver key information required for the DASH client, the ISOBMFF Parser, and / or the Media Processor. According to an embodiment, the CA module may process the license, key information, and viewing authority information and transmit the same to another module, or even decrypt the encrypted stream in the CA module itself.

The output interface can control an external interface that can be connected to an external device. The external device may include a companion device and / or a device containing other authentication information.

In a broadcasting system, a broadcasting viewing plan may vary according to a user, and a separate fee may be set according to each broadcasting viewing plan, and may be charged to the user. For example, each broadcast service providing a standard definition (SD) image, a high definition (HD) image, and an ultra high definition (UHD) image may be charged separately, and the user may select an image having a resolution of a desired resolution. In order to watch, a case may be paid. Such a fee system may include contents such as copy rights for broadcast services. For example, in a broadcast viewing plan for a predetermined fee or more, each broadcast receiver may include a right to perform a copy, for example, recording or recording of a part or all of a broadcast service.

Thus, in a broadcast system, metadata (parameters) or signaling information for copy control for some or all of the broadcast services need to be defined. As an example, signaling information and / or parameters for copy control may be defined in units of video tracks (streams), video samples (or video sample groups) and / or video sample entries. In addition, as the broadcast system uses data in the form of ISOBMFF, metadata or signaling information for copy control on the ISOBMFF data needs to be defined. To this end, the CA module described above may further process copy control information for the ISOBMFF based file format.

Meanwhile, when copy control information is added to the ISOBMFF-based file itself, copy control may be applied to the content itself. In other words, in case of copy control on content through signaling information, if hacking of signaling information occurs, protection of the corresponding content is also impossible. However, when copy control on the ISOBMFF file itself is applied. Even if there is a hack on the signaling information, since copy control on the content can be performed, the protection of the content can be enhanced.

9A illustrates an embodiment of an ISOBMFF-based file. The illustrated ISOBMFF file may include information related to the initialization of the media decoder. For example, an initialization segment defined in MPEG Dynamic Adaptive Streaming over HTTP (DASH) may have a file format as shown.

The illustrated ISOBMFF file may include a ftyp box and / or a moov box. The moov box may comprise an mvex box and / or one or more tracks.

The ftyp box may contain information indicating the type or brand to be applied to the file. The ftyp box lists major_brand information identifying the (brand), such as the codec applied to the file, minor_version information identifying the minor version of the brand identified by the major_brand information, and / or lists the brands compatible with this file. May contain compatible_brands information.

The moov box corresponds to a container that contains metadata. Metadata required for presentation of media (or content) may be included in the moov box.

The mvex box indicates that a movie fragment box (moof) may be included in this file. The movie fragment box may include sub boxes that define metadata for presentation.

A track contains media data. For example, the track may include consecutive images or sampled audio.

FIG. 9B is a diagram illustrating a media segment of MPEG DASH based on ISOBMFF. The media segment of MPEG DASH based on ISOBMFF may include a styp box, sidx box, moof box, and / or mdat box.

The styp box may contain information indicating the brand applied to the media segment.

The sidx box may include information identifying the index of the media segment.

The moof box may include sub boxes that define metadata for presentation of the media or content.

The mdat box may contain data for media or content. For example, video tracks and / or audio tracks may be included in the mdat box.

FIG. 9C is a diagram illustrating a media segment of MPEG DASH including an ISOBMFF-based movie fragment. Media segments of MPEG DASH composed of ISOBMFF based movie fragments may include styp boxes, sidx boxes, ssix boxes, moof boxes, and / or mdat boxes. The description of the styp box, sidx box, moof box, and / or mdat box is as described above.

The ssix box may include information indicating the index of the sub segment included in the media segment.

Information related to the copy control defined in the present invention may be included in the ISOBMFF file in the form as shown.

As shown, Box or FullBox can be used to define extended information in the ISOBMFF file.

The Box or FullBox may include size information, largesize information, type information, version information, and / or flags information.

The size information or largesize information may indicate the length of the box (eg, in bytes).

The type information may identify the type of the box or may include information identifying the box.

The version information may indicate the version of the box format.

The flags information may indicate a flag associated with the box.

According to the present invention, when generating an ISOBMFF-based file, copying control relating to video tracks, audio tracks, data tracks (streams), video samples, audio samples and / or data samples may be stored or signaled. You can redefine a box.

The copy control box according to the present invention may include copy_control_flag information, num_copy_control_info information, num_play_control_info information, ep_copy_control_info information, trick_mode_control_flag information, and / or num_output_control_info information.

The copy_control_flag information may indicate whether the video / audio / data (video, audio and / or data) track or sample is copy protected. For example, when the value of the copy_control_flag information is set to '0', it may indicate that copy protection is not applied to the corresponding track or sample. If it is set to '1', copy protection may be applied to the track or sample. It may indicate that it has been applied. As a default, the value of the copy_control_flag information may be set to '1'.

The num_copy_control_info information is information indicating the number of copies that can be copied to a video / audio / data track or a sample. For example, when the value of the num_copy_control_info information is set to '0x00', it may indicate that copying is not possible. When it is set to '0x01 to 0xFE', it may indicate the number of times that copying is possible and set to '0xFF'. If so, it may indicate that there is no restriction on copying.

The num_play_control_info information may correspond to information specifying the number of times a file can be played back in a device (eg, a broadcast receiver). For example, when the value of num_play_control_info information is set to '0x00', it may indicate that playback is impossible, and when it is set to '0x01 to 0xFE', it may directly indicate the number of times that the playback can be performed and set to '0xFF'. If set, it can indicate that there is no restriction on playback. The num_play_control_info information may have a default value of '0xFF'.

The ep_copy_control_info information may indicate an expiration period of recording and / or time-shift for content. When the value of the ep_copy_control_info information is set to '0x0000', it may indicate that there is no expiration period, and when it is set to '0x0001', it may indicate that an expiration period of 60 minutes is applied and is set to '0x0002' to '0xFFFF'. In this case, it may indicate that the expiration period of 2 to 65535 hours indicated by these bits applies.

The trick_mode_control_flag information may indicate whether a trick mode is possible. For example, when the value of the trick_mode_control_flag information is set to '0', it may indicate that the trick mode control is impossible, and when set to '1', it may indicate that the trick mode control is possible.

The num_output_control_info information may indicate designation of the number of output devices capable of simultaneously playing a corresponding file when the value of output_control_flag information (or copy_control_flag information) is '1'. For example, when the value of num_output_control_info information is set to '0x00', it may indicate that playback is not possible on the multi-screen, and that only the main playback device can play the file, and it is set to '0x01'. In addition, it may indicate that one device other than the main playback device can play the content of the file at the same time, and when it is set as '0x02 ~ 0Xff', it indicates that two or more devices besides the main playback device can play the content of the file at the same time. , May indicate the number of devices.

Next generation broadcast systems may provide n-screen services. By receiving a service in a broadcast system, it is possible to express the corresponding service on n screens. In this process, however, the service must be copied or retransmitted. In such an environment there is a need to be limited to allowing an unlimited number of screens to copy or retransmit the service. For example, if you have two or more televisions in one household, you can subscribe to a broadcast viewing plan to receive services for only one television, and copy or retransmit those services for the remaining televisions. A situation of watching a service on a device may occur. Since this situation is not desired by the broadcaster, the broadcaster may include the number of devices capable of providing the n-screen service in the broadcast viewing plan. In this case, the broadcast system may signal the number of output devices that a broadcaster allows and simultaneously reproduces using the num_output_control_info information.

In addition to the above-described information, the copy control box may further include the information described above or below in the present invention, and the name of the box and / or each parameter (information) may be changed.

The tkhd box may contain information describing attributes for the track (video / audio / data). The tkhd box may include creation_time information, modification_time information, track_ID information, and / or duration information. The tkhd box can be included in the moov box.

creation_time information is information indicating the time at which the track described by this box was created.

The modification_time information is information indicating the time when the track described by this box was modified.

The track_ID information is information for identifying a specific track in the entire presentation.

The duration information is information representing the duration of the track.

In addition to the above-described information, the tkhd box may include part or all of the information (copy control information) included in the above-described copy control box. That is, the tkhd box may further include copy_control_flag information, num_copy_control_info information, num_play_control_info information, ep_copy_control_info information, trick_mode_control_flag information, and / or num_output_control_info information. In this case, the copy control information can describe the contents of the copy control for the corresponding track in track units.

The vmhd box, smhd box, hmhd box and / or nmhd box may comprise part or telegram of the above-described copy control information (or copy control parameter).

The vmhd box corresponds to a video media header box and may include general presentation information for video media.

The smhd box corresponds to a sound media header box and may include general presentation information for audio media.

The hmhd box corresponds to a hint media header box, and may include general information about a hint track.

The nmhd box corresponds to a null media header box, and may include general information about streams other than video or audio streams.

If the tkhd box, vmhd box, smhd box, hmhd box, and / or nmhd box contain copy control information at the same time, the value of the copy control information defined in the track header box is the vmhd box, smhd box, hmhd box, and / or nmhd box. Can be overridden by the value of the copy control information defined in.

When the copy control information is defined in the vmhd box, the smhd box, the hmhd box, and / or the nmhd box, the copy control may be applied in the unit described by the box.

The trex box can be included in the mvex box (movie extends box).

The trex box may include information for setting default values used by a movie fragment.

The trex box may include track_ID information, default_sample_description_index information, default_sample_duration information, default_sample_size information, default_sample_flags information, default_sample_num_copy_control_flag information, default_sample_num_copy_control_info information, default_sample_ep_copy_control_info information, default_sample_info_control_fla

The track_ID information is information for identifying a track in a movie box.

The default_sample_description_index information, default_sample_duration information, default_sample_size information, and default_sample_flags information each include sample_description_index information indicating the index of the sample entry describing the sample, sample_duration information indicating the duration of the sample, sample_size information indicating the sample size, and flags set for the sample. A default value for sample_flags information indicating a value may be indicated.

The default_sample_copy_control_flag information, default_sample_num_copy_control_info information, default_sample_num_play_control_info information, default_sample_ep_copy_control_info information, default_sample_trick_mode_control_flag information, default_sample_num_out_control_info information, default_sample_num_out_control_info information, num_copy_control_info, info_control_control_info_info_control_info, The default_sample_copy_control_flag information, default_sample_num_copy_control_info information, default_sample_num_play_control_info information, default_sample_ep_copy_control_info information, default_sample_trick_mode_control_flag information, and default_sample_num_out_control_info information can be used to set default values of copy control information in a video / audio / data sample unit.

According to another embodiment of the present invention, the default_sample_flags information may include copy_control_flag information and / or trick_mode_control_flag information. Since the default_sample_flags information may include one or more flags for the samples, it may include copy_control_flag information and / or trick_mode_control_flag information related to the samples.

The tfhd box can be included in the moof box.

Each movie fragment can add zero or more fragments to each track. A track fragment may contain zero or more consecutive samples. The tfhd box contains information for setting default values and / or information used for these samples.

The tfhd box may include track_ID information, copy_control_flag information, num_copy_control_info information, num_play_control_info information, ep_copy_control_info information, trick_mode_control_flag information, num_out_control_info information, base_data_offset information, sample_description_index information, default_sample_duration information, and default_sample_size_sample_flag.

The base_data_offset information is information indicating a base offset for calculating an offset of data.

The description of the information contained in the tfhd box with the same name as the above-mentioned information is replaced with the above-mentioned description.

The trun box can be included in the track fragment box in the moof box.

The trun box contains information describing a set of samples for one track.

The trun box may include sample_count information, copy_control_flag information, num_copy_control_info information, num_play_control_info information, ep_copy_control_info information, trick_mode_control_flag information, num_out_control_info information, data_offset information, first_sample_flags information, sample_duration information, sample_size information, and sample_offset.

The sample_count information is information indicating the number of samples included in this fragment.

The description of the information contained in the trun box with the same name as the above-mentioned information is replaced with the above-mentioned description.

If all or part of the copy control information is simultaneously included in the tfhd box (Track fragment header box) and the trun box (track run box), the copy control information defined in the tfhd box is overridden by the value defined in the trun box. Can be

When copy control information is defined in a trun box, copy control may be applied in units of sets of samples.

According to another embodiment of the present invention, sample_flags information and / or first_sample_flags information may include copy_control_flag information and / or trick_mode_control_flag information. Since sample_flags information and / or first_sample_flags information may include one or more flags for samples, it may include copy_control_flag information and / or trick_mode_control_flag information related to the samples.

The visual sample group entry may include copy_control_flag information, num_copy_control_info information, num_play_control_info information, ep_copy_control_info information, trick_mode_control_flag information, and / or num_out_control_info information.

In the information included in the visual sample group entry, the description of the information having the same name as the above information is replaced with the above description.

When copy control information is included in a visual sample group entry, the same copy control information may be applied to one or more video samples existing in one file or movie fragment. That is, when defining copy control information in a visual sample group entry, it is not necessary to define or signal a plurality of copy control information for each sample, thereby saving bandwidth for data transmission. It works.

The visual sample entry may include copy_control_flag information, num_copy_control_info information, num_play_control_info information, ep_copy_control_info information, trick_mode_control_flag information, and / or num_out_control_info information.

Description of information having the same name as the above-mentioned information among the information included in the visual sample entry is replaced with the above description.

When the visual sample entry includes copy control information, the copy control information may be applied to each sample as initialization information necessary to decode each sample existing in one file or movie fragment. have.

In this case, there is an effect that copy control is possible for each sample.

Based on the above-described ISOBMFF, when generating a file for the content that can be controlled for copying, generating a DASH segment that can operate on MPEG DASH, or generating an MPU that can operate on MPEG MMT, the copy control information is included in a corresponding unit. Can be included in The receiver allows the decoder (including the DASH client, and / or MMT client) to effectively perform decoding and / or display of the corresponding content using copy control information.

Some or all of the above-described copy control information may exist simultaneously in several boxes in one ISOBMFF file or DASH segment, MMT MPU. In this case, some or all of the copy control information defined in the upper box may be overridden by values of some or all of the copy control information having the same name defined in the lower box.

The pssh box may include information required by the content protection system to play the content.

The pssh box may include copy_control_flag information, num_copy_control_info information, num_play_control_info information, ep_copy_control_info information, trick_mode_control_flag information, and / or num_out_control_info information.

In a movie box or movie fragment box, if a pssh box can exist and the pssh box contains all or part of the copy control information, the copy control information is common to the video samples included in the track fragment. Can be applied as

The tenc box may be included in the Scheme Information Box.

The tenc box contains information related to encryption common to video samples included in the track fragment.

The tenc box may include default_copy_control_flag information, default_num_copy_control_info information, default_num_play_control_info information, default_ep_copy_control_info information, default_trick_mode_control_flag information, and / or default_num_out_control_info information.

When the tenc box includes some or all of the copy control information, the copy control information may be used as a default value for copy control on video samples included in the track fragment.

The senc box may be included in a track fragment box or a track box.

The senc box contains information related to the encryption that is applied to each sample.

The senc box may include copy_control_flag information, num_copy_control_info information, num_play_control_info information, ep_copy_control_info information, trick_mode_control_flag information, and / or num_out_control_info information.

If the senc box includes some or all of the copy control information, the copy control information may be applied to each of the video samples included in the track fragment. In this case, copy control is possible for each of the video samples.

CencSampleEncryptionInformationVideoGroupEntry may include copy_control_flag information, num_copy_control_info information, num_play_control_info information, ep_copy_control_info information, trick_mode_control_flag information, and / or num_out_control_info information.

CencSampleEncryptionInformationGroupEntry may include copy_control_flag information, num_copy_control_info information, num_play_control_info information, ep_copy_control_info information, trick_mode_control_flag information, and / or num_out_control_info information.

When the handler type of the track is video ('vide'), if you want to apply the same copy control information to one or more video samples present in a file or movie fragment, all or all of the copy control information in CencSampleEncryptionInformationGroupEntry Some may be included.

If the handler's type of track indicates a type other than video, and you want to apply the same copy control information to one or more video samples that exist in a file or movie fragment, all of the copy control information in CencSampleEncryptionInformationGroupEntry or Some may be included.

Although the MPEG-DASH method can be used for the broadcast streaming method, a copy control method is not defined for the DASH file format. Therefore, when MPEG-DASH is used in a broadcast system, copy control information needs to be defined for the DASH file format for copy control. In this case, the above-described CA module may further play a role of processing copy control information included in the DASH file format.

DASH (Dynamic Adaptive Streaming over HTTP) is a scheme to support HTTP-based adaptive streaming. It supports dynamic streaming reflecting the network conditions, thereby enabling seamless A / V content playback between components of various profiles. To be. The figure shows the overall operational process for DASH-based adaptive streaming.

Media presentation description (MPD) is a file that contains detailed information for allowing a DASH client to dynamically acquire a segment, and may be expressed in XML format. The MPD may include information related to the presentation of the media.

The DASH client controller dynamically generates a command for requesting an MPD and a segment based on network conditions and controls the obtained information to be used in a media engine.

The MPD Parser parses the acquired MPD in real time and enables the DASH client controller to generate a command for acquiring the required segment.

The segment parser may parse the acquired segment in real time. The segment parser may perform a specific operation of the media engine (Media engine_) according to the contents included in the segment.

The HTTP client may request a segment required by the HTTP server and deliver the MPD and / or segment included in the HTTP response obtained from the server to the MPD parser and / or the segment parser.

The media engine displays media (content) on the screen using media information included in the segment.

The DASH client can obtain the MPD, select the appropriate representation using the information described in the MPD, and request the segment from the server using the access information on the segment included in the presentation. have. The DASH client acquires the segment and passes it to the media engine to display the media (or content) represented by the segment on the screen. The DASH client can support seamless content playback by adaptively requesting and acquiring necessary segments and delivering them to the media engine by reflecting the playing time and network conditions in real time.

Media presentation can be described by the MPD. The media presentation may include one or more periods defined with respect to time to present the media.

Each of the periods may include information such as the time, duration, such as the start of the period. The period may include base URL information used to request segments or sub-segments included in the corresponding period. Each period may include one or more adaptation sets corresponding to the components of the media (or content).

Each adaptation set may include information about each component of the media (eg, video component, audio component or caption component). Each adaptation set may include one or more presentations.

The one or more presentations include data needed to represent components corresponding to the adaptation set that includes the presentation. Each presentation is used to display the contents of the same component, but can have different profiles. For example, if the adaptation set includes descriptive information about the video component, the first presentation included in that adaptation set may include data for the video component using a bandwidth of 850 kbps, The presentation may include data for video components using a bandwidth of 1250 kbps. Here, a video component using a bandwidth of 850 kbps and a video component using a bandwidth of 1250 kbps are used to express the same content. Each presentation may include one or more segments.

A segment may correspond to a media unit or a data unit for transmitting data necessary for initial access of the media data. The segment may correspond to an initialization segment or a media segment. The initialization segment may include information necessary to access a media segment included in the media. For example, the initialization segment may be combined with the base URL of the period, and may include additional URLs used for the request of the media segment. The media segment contains data about the media itself. Each media segment may include information indicating a start time at which the media segment presents the media.

MPD includes @id information, @profile information, @type information, @availabilityStartTime information, @minBufferTime information, @suggestedPresentationDelay information, ProgramInformation (0..N) element, Location (0..N) element, Period (0..N ) Elements, and / or Metrics (0..N) elements.

@id information represents an identifier for a media presentation.

The @profile information is information that identifies a list of media presentation profiles.

The @type information is information for identifying the type of media presentation. The @type information can identify a static media presentation and a dynamic media presentation. In the case of a static media presentation, the valid start and valid end times of the segments may be the same, but in the case of dynamic media presentation, the valid times of the segments may be different.

@availabilityStartTime information may exist for a dynamic media presentation and is information that identifies an anchor for calculating the earliest valid time for a segment in the media presentation.

The @minBufferTime information is information that identifies a common duration used for the definition of the representation data rate.

@suggestedPresentationDelay information may be present for dynamic media presentation, indicating a fixed delay offset from the presentation time of each access unit, which is proposed to be used for presentation of each access unit. Information.

The ProgramInformation (0..N) element may include information describing a program. The MPD may contain zero or more ProgramInformation elements.

The Location (0..N) element may contain information identifying the location of the point at which the MPD is available. The Location element may include information identifying a location from which the MPD can be obtained. The MPD may contain zero or more Location elements.

The Period (0..N) element contains information about the period. The MPD may contain zero or more Period elements.

The Metrics (0..N) element contains information related to the DASH Metrics. The MPD may contain zero or more Metrics elements.

Periods include @id information, @start information, @duration information, AssetIdentifier (0..1) elements, EventStream (0..N) elements, AdaptationSet (0..N) elements, and / or Subset (0). ..N) may contain elements.

@id information is information for identifying a period.

The @start information is information representing the start time of the period.

The @duration information is information representing the duration of the period. The @duration information can be used to know the start time of the next period.

The AssetIdentifier (0..1) element may include information for identifying a specific asset to which a pyriod belongs.

The EventStream (0..N) element may include information related to the event stream.

The AdaptationSet (0..N) element may include information about the adaptation set. A pyriod may contain zero or more AdaptationSet elements.

The Subset (0..N) element may include information about a subset.

The adaptation set includes @id information, @group information, @min (max) Bandwidth information, @min (max) Width information, @min (max) Height information, @min (max) FrameRate information, Common element, Accessibility (0..N) elements, Role (0..N) elements, Rating (0..N) elements, Viewpoint (0..N) elements, ContentComponent (0..N) elements, and / or Representation (0 ..N) may contain elements.

The @id information is information representing an identifier for an adaptation set within the scope of the period.

The @group information is information that uniquely identifies a group within the scope of the period.

@min (max) Bandwidth information is information that identifies the minimum / maximum bandwidth allocated to all presentations in the adaptation set.

The @min (max) Width information represents the minimum / maximum width of all the presentations in the adaptation set.

The @min (max) Height information represents the minimum / maximum height of all presentations in the adaptation set.

@min (max) FrameRate information indicates the minimum / maximum frame rate at all representations in the adaptation set.

The common element may include information that is common within the scope of the adaptation set.

The Accessibility (0..N) element may contain information about an accessibility scheme.

The Role (0..N) element contains information about the role annotation scheme.

The Rating (0..N) element may include information about viewing restrictions.

The viewpoint (0..N) element may include information about a viewpoint annotation scheme.

The ContentComponent (0..N) element may include information describing an attribute of a media content component included in the adaptation set.

The Representation (0..N) element may include information about the presentation. The adaptation set may include zero or more Representation elements.

The Content Component includes @id information, @lang information, @contentType information, @par information, Accessibility (0..N) element, Role (0..N) element, Rating (0..N) element, And / or Viewpoint (0..N) elements.

@id information is information for identifying an identifier for a media component.

@lang information is information that identifies the language used for the media component.

@contentType information is information indicating the type of a media component.

@par information is information indicating a picture aspect ratio of a media component.

The Role (0..N) element contains information about the role annotation scheme.

The Rating (0..N) element may include information about viewing restrictions.

The viewpoint (0..N) element may include information about a viewpoint annotation sceme.

Representation includes @id information, @bandwidth information, @dependencyId information, Common element, BaseURL (0..N) element, SegmentBase (0..1) element, SegmentList (0..1) element, SegmentTemplate ( 0..1) elements, and / or SubRepresentation (0..N) elements.

@id information is information for identifying a presentation.

@bandwidth information is information indicating a bandwidth of a channel for transmitting a presentation, expressed in bits per second (bps).

The @dependencyId information is information for identifying other presentations that the present presentation depends on in the decoding or presentation process.

The Common element contains information that is commonly applied within the presentation.

The BaseURL (0..N) element represents the base URL.

The SegmentBase (0..1) element contains initial information about the segment base.

The SegmentList (0..1) element contains information for the segment list.

The SegmentTemplate (0..1) element contains information about the segment template.

The SubRepresentation (0..N) element includes information about the sub presentation included in the presentation.

The segment base may include @timescale information, @presentationTimeOffset information, @timeShiftBufferDepth information, @availabilityTimeOffset information, Initialization (0..1) element, and / or RepresentationIndex (0..1) element.

The @timescale information is information representing a timescale in seconds used for deriving another real time duration value in the information about a segment.

The @presentationTimeOffset information is information for identifying a presentation time offset of the presentation with respect to the start of the period.

The @timeShiftBufferDepth information is information representing the duration of a type shifting buffer for a valid presentation for dynamic media presentation.

@availabilityTimeOffset information is information indicating an offset for defining an adjusted segment availability time.

The Initialization (0..1) element may include URL information including a possible byte range for the initialization segment.

The RepresentationIndex (0..1) element may include URL information including a possible byte range for the Representation Index Segment.

Sub-representation may include @level information, @dependencyLevel information, @bandwidth information, @contentComponent information, and / or Common elements.

@level information is information for identifying the level of the sub-representation.

The @dependencyLevel information is information that identifies, within the presentation, the set of sub-representations upon which this sub-representation depends for decoding and / or presentation.

The @bandwidth information is information representing bandwidth allocated for sub-representation.

@contentComponent information is information indicating a set of media content components included in a sub-representation.

The common element may include common information defined for the sub presentation.

Common elements include @mimeType information, @width information, @height information, @sar information, @framerate information, @audiosamplingRate information, @codec information, @startWithSAP information, FramePacking (0..N) element, AudioChannelConfiguration (0..N ) Elements, ContentProtection (0..N) elements, EssentialProperty (0..N) elements, SupplementalProperty (0..N) elements, and / or InbandEventStream (0..N) elements.

The @mimeType information is information for identifying successive MIME types of the initialization segment.

The @width information is information indicating the size of the horizontal visual presentation of the video media type.

@height information is information indicating the size of vertical visual presentation of a video media type.

The @sar information is information representing a sample aspect ratio of a media medium component type.

@framerate information is information indicating an output frame rate of the video media type in the presentation.

The @audiosamplingRate information is information representing a sampling rate of an audio media component type.

The @codec information is information representing a codec used in the presentation.

The FramePacking (0..N) element may include information on a frame-packing arrangement of the media media component type.

The AudioChannelConfiguration (0..N) element may include information related to the audio channel configuration of the audio media component type.

The ContentProtection (0..N) element may contain information about the content preotection scheme used for the associated presentation.

The EssentialProperty (0..N) element may contain information about an element that is considered essential by the media presentation author in order to process the element to be included.

The SupplementalProperty (0..N) element may contain information about an element that can be used by the DASH client to optimize the processing.

The InbandEventStream (0..N) element may contain information about the presence of an inband event stream in the associated presentation.

Referring to the drawings, in the MPD, it includes information about the piriod, includes information about the adaptation set in the pyriod, includes information about the presentation in the adaptation set, and includes information about the segment in the presentation. The structure is shown. The receiver may receive the MPD and, according to the depicted structure, access segments containing data for presentation of the media. The common element may be applied to the adaptation set, the presentation and / or the sub presentation.

The copy control element may be used in the same sense as the above-described copy control information (or parameter).

The figure shows a table form and an XML syntax form for the copy control element.

The copy control element may include information for copy control in the media (or content) itself or in a component, segment, or sample unit included therein.

The copy control element may include @schemeIdUri information, @value information, and / or @id information.

The @schemeIdUri information is information representing a URI identifying a plan. The syntax of this element may be used for the plan identified by this attribute information. The @schemeIdUri information may correspond to a URN or a URL and, if a URL is used, may include a month-date in mmyyyy format.

The @value information is information representing a value for an element. The field and / or syntax in which this value is used shall be defined by the scheme identified in the @schemeIdUri information.

@id information is information representing an identifier for this descriptor. Descriptors having the same value of @id information may correspond to the same descriptor. That is, it is sufficient if only one of the descriptors having the same value of @id information is processed in the processing.

Referring to (a) of the figure, when the @schemeIdUri information has a certain URI, it may represent that a description (or an element) including the @schemeIdUri information is a copy control description.

Referring to (b) of the figure, the meaning of each information included in the copy control information according to the value of @value information is described.

The copy_control_flag information may indicate whether the video / audio / data (video, audio and / or data) track or sample is copy protected. For example, when the value of @value information for copy_control_flag information is set to '0', it may indicate that copy protection has not been applied to the corresponding track or sample, and if set to '1', the track or This may indicate that copy protection is applied to the sample. As a default, the value of the copy_control_flag information may be set to '1'.

The num_copy_control_info information is information indicating the number of copies that can be copied to a video / audio / data track or a sample. For example, when the value of the @value information for the num_copy_control_info information is set to '0', it may indicate that copying is impossible, and when it is set to '1 to 999', it may indicate the number of possible copies. When set to '1000', it may represent that there is no restriction on copying.

The num_play_control_info information may correspond to information specifying the number of times a file can be played back in a device (eg, a broadcast receiver). For example, when the value of @value information for the num_play_control_info information is set to '0', it may indicate that playback is impossible, and when it is set to '1 to 999', it may directly indicate the number of times that playback is possible. If set to '1000', this may indicate that there is no restriction on playback. The num_play_control_info information may have a default value of '1000'.

The ep_copy_control_info information may indicate an expiration period of recording and / or time-shift for content. When the value of the @value information for the ep_copy_control_info information is set to '0', it may indicate that there is no expiration period, and when set to '1', it may indicate that an expiration period of 60 minutes is applied and '2' ~ ' 100000 ', it may indicate that an expiration period of 2 to 100000 hours indicated by these bits is applied.

The trick_mode_control_flag information may indicate whether a trick mode is possible. For example, when the value of the @value information for the trick_mode_control_flag information is set to 'false', it may indicate that the trick mode control is impossible, and when set to 'true', it may indicate that the trick mode control is possible.

The num_output_control_info information may indicate designation of the number of output devices capable of simultaneously playing a corresponding file when the value of output_control_flag information (or copy_control_flag information) is '1'. For example, when the value of the @value information for the num_output_control_info information is set to '0', playback may not be possible on the multi-screen, and only the main playback device may play the file. If set to 1 ', it can indicate that one device other than the main playback device can play the content of the file at the same time. If set to' 2 ~ n ', two or more devices other than the main playback device can simultaneously display the content of the file. This indicates that playback is possible and the number of devices.

The stereo_video_control_flag information is information indicating whether stereo video can be copied. For example, if the value of the @value information for the stereo_video_control_flag information is set to '0', it may indicate that copying of stereo video is impossible and / or only mono video can be copied, and if set to '1', stereo video It can indicate that copying is possible.

The num_scalability_control_info information is information indicating the number of scalability values that can be copied to a media to which scalable coding is applied. For example, when the value of the @value information for the num_scalability_control_info information is set to '0', this may indicate that copying to the media (or a part of the data included) to which scalable coding is applied is impossible, and '1' When set to, it can indicate that one scalability can be copied, and when set to '2 ~ n', it can copy to the number of scalability indicated by the number (data transmitted to base layer and one or more copying of data transmitted to the enhancement layer).

The num_audio_channel_control_info information is information indicating the number of channels that can be copied for multichannel audio. For example, when the value of @value information for num_audio_channel_control_info information is set to '0', it indicates that copying is not possible for multichannel audio. If it is set to '1 ~ n', copying is possible in multichannel audio. It directly indicates the number of channels. Additionally, it is possible to further define information that specifies which channel of the multi-channel audio can be copied. For example, information for identifying a main audio channel that can be copied below the num_audio_channel_control_info information may be further defined to indicate that only the main channel audio can be copied among the multi-channel audio. In the case of SAOC (Spatial Audio Object Coding), this may indicate that copying is possible for a specific audio object. For example, when the audio includes a piano sound and a trumpet sound, the num_audio_channel_control_info information may indicate that only one of these objects can be copied. In this case, it is possible to identify whether the copyable object (or channel) relates to the piano sound or the trumpet sound.

The aforementioned common element may include @copy_control_flag information, @num_copy_control_info information, @num_play_control_info information, @ep_copy_control_info information, @trick_mode_control_flag information, @num_out_control_info information, @stereo_video_control_flag information, @num_scalability_control_info information, or @num_audio_channel information, or more. have.

The @copy_control_flag information, @num_copy_control_info information, @num_play_control_info information, @ep_copy_control_info information, @trick_mode_control_flag information, @num_out_control_info information, @stereo_video_control_flag information, @num_scalability_control_info information, and @num_audio_channel according to the description and the meaning of these values are assigned to the descriptions and the meanings of the corresponding information. Same as one.

When copy control information is defined in the form of a lower element of a common element, the common element may include a CopyControl element. In this case, the CopyControl element may be defined in the above-described form, or may be defined to include some or all of the copy control information.

Copy control information (description) may be signaled through the EssentialProperty element or the SupplementaryProperty element. If the same copy control information is applied to all the presentations included in the adaptation set, the EssentialProperty element or the SupplementaryProperty element may be included in the adaptation set. If different copy control information is to be applied to each presentation or sub-representation, the EssentialProperty element or SupplementaryProperty element may be included in the presentation or sub-representation.

The EssentialProperty element and / or SupplementaryProperty element may contain @copy_control_flag information, @num_copy_control_info information, @num_play_control_info information, @ep_copy_control_info information, @trick_mode_control_flag information, @num_out_control_flag information, @num_out_control_info information, @stereo_video_control_flag information, @num_scalinfo_control_info have. The description of these is as described above.

Referring to (a) of the drawing, the copy control information included in the SupplementaryProperty element is shown, and referring to (b) of the drawing, the copy control information included in the EssentialProperty element is shown.

Copy control information (description) may be signaled via the Accessibility element. If the same copy control information is applied to all the presentations included in the adaptation set, the Accessibility element may be included in the adaptation set. In other cases, an Accessibility element may be included in a Content Component element.

The Accessibility element may include @copy_control_flag information, @num_copy_control_info information, @num_play_control_info information, @ep_copy_control_info information, @trick_mode_control_flag information, @num_out_control_info information, @stereo_video_control_flag information, @num_scalability_control_info information, and / or @num_audio. The description of these is as described above.

The content protection element may include an @schemeIdUri information, a sea: SegmentEncryption element, a sea: License element, a sea: CryptoPeriod element, a sea: CryptoTimelinesea: CopyControl element, and / or a sea: CopyControl element.

The @schemeIdUri information is the URI that identifies the scheme of this element.

The sea: SegmentEncryption element may contain information identifying the encryption system used for encryption.

The sea: License element may include information about a key system and / or a method of obtaining a license used in an encryption system.

The sea: CryptoPeriod element may contain information needed to derive a key and / or information for a single cryptoperiod.

The sea: CryptoTimelinesea: CopyControl element may contain information needed to derive a key and / or information for various fixed lengths of a single cryptoperiod.

The sea: CopyControl element may contain information related to copy control.

The sea: CopyControl element may include @copy_control_flag information, @num_copy_control_info information, @num_play_control_info information, @ep_copy_control_info information, @trick_mode_control_flag information, @num_out_control_info information, @stereo_video_control_flag information, @num_scalability_control_info information, and / or audio. The description of these is as described above.

The SegmentEncryption element is an element that provides attribute information about the encryption system.

The SegmentEncryption element may include @copy_control_flag information, @num_copy_control_info information, @num_play_control_info information, @ep_copy_control_info information, @trick_mode_control_flag information, @num_out_control_info information, @stereo_video_control_flag information, @num_scalability_control_info information, and / channel information. The description of these is as described above.

The ContentComponent element is an element that provides attribute information about a content component.

ContentComponent elements include @id information, @copy_control_flag information, @num_copy_control_info information, @num_play_control_info information, @ep_copy_control_info information, @trick_mode_control_flag information, @num_out_control_info information, @stereo_video_control_flag information, @num_scalability_control_info information, @control_info channel control It may include.

The @id information is information that uniquely identifies the media component in the scope of the adaptation set.

The description of the remaining information and / or elements is as described above.

The SegmentBase element is an element that provides attribute information to a segment.

SegmentBase elements include @timescale information, @copy_control_flag information, @num_copy_control_info information, @num_play_control_info information, @ep_copy_control_info information, @trick_mode_control_flag information, @num_out_control_info information, @num_out_control_info information, @stereo_video_control_flag information, @num_scalability_control_info_control_info It may include. The description of this information and / or element is as described above.

When copy control information defined in an upper element (eg, MPD) is defined in a lower element (eg, a SegmentBase element), copy control information included in the lower element may be applied to data described by the corresponding element. .

The AdaptationSet element is an element that provides attribute information about the adaptation set.

The AdaptationSet element may include @copy_control_flag information, @num_copy_control_info information, @num_play_control_info information, @ep_copy_control_info information, @trick_mode_control_flag information, @num_out_control_info information, @stereo_video_control_flag information, @num_scalability_control_info_info, and / or audio. The description of this information is as described above.

By defining copy control information in the AdaptationSet element, the copy control information can be applied to all presentations included in the adaptation set.

A description of the service list table and information that may be included therein is as described above. According to the present embodiment, copy control information may be added to the service list table.

The service list table may include a service level descriptor (or service level element) for signaling information about a service level and / or a service list table level descriptor (or service list table level element) for signaling information about a service list table level. It may include.

As a kind of service level descriptor and / or service list table level descriptor, a usage rule descriptor can be defined.

The usage rule descriptor may include copy_control_flag information, trick_mode_control_flag information, num_copy_control_info information, num_play_control_info information, ep_copy_control_info information, num_out_control_info information, stereo_video_control_flag information, num_scalability_control_info information, and / or num_audio_channel_control. The description of this information is as described above.

The copy control information may be included directly in the service list table. That is, copy control information can be defined directly in the service list table, not in the lower element such as the usage rule descriptor.

Referring to (a) of the drawing, an embodiment of a service configuration and usage control (or copy control) application when a usage rule descriptor exists at a location of service_level_descriptor () in a service list table is illustrated.

One RF stream (Radio Frequency stream) in the present embodiment transmits two services (channels). A usage rule descriptor that conveys usage control information can be included in a loop describing service # 1. In this case, the usage control information included in the usage rule descriptor may be applied to all streams included in service # 1. The receiver can use the usage control information to control the restriction, permission, range, etc. of the copy function for the streams.

Referring to (b) of the drawing, an embodiment of applying a service configuration and usage control when a usage rule descriptor exists at a location of SLT_level_descriptor () in a service list table is illustrated.

One RF stream in this embodiment transmits two services (channels). The usage rule descriptor that conveys usage control information can be included in a loop that describes the entire service contained in the service list table. In this case, the usage control information may be applied to all streams included in all services (services # 1 and # 2) described by the service list table. The receiver can use the usage control information to control the restriction, permission, range, etc. of the copy function for the streams.

The copy control information is assigned to the corresponding channel attribute along with the attribute of the service list table, so that the copy control information may not be changed in units of programs or updated very slowly. Usage control information (or copy control information) according to the present embodiment can be applied not only when the protocol for transmitting the service component is ROUTE, but also when MMTP.

The description of the USBD and the information that may be included therein is as described above. According to this embodiment, copy control information can be added to the USBD.

The above-described service_level_descritpr () may be configured with an element or a fragment in XML format to deliver copy control information. Referring to (a) of the drawing, an embodiment in which a UsageRuleInfo element including copy control information is included in a user service bundle description (USBD) is illustrated. The UsageRuleInfo element may exist as a subelement of bundleDescription or as a subelement of USD (userServiceDescription).

The UsageRuleUnfo element may include copy_control_flag information, trick_mode_control_flag information, num_copy_control_info information, num_play_control_info information, ep_copy_control_info information, num_out_control_info information, stereo_video_control_flag information, num_scalability_control_info information, and / or num_audio_channel. The description of this information is as described above.

The application range of the copy control information delivered by the UsageRuleInfo element may vary depending on the inclusion location. For example, when the UsageRuleInfo element is included as a lower element of the USBD, the copy control information included in the UsageRuleInfo element may be applied to all services described by all USD included in the USBD. When the UsageRuleInfo element is included as a lower element of the USD, copy control information included in the UsageRuleInfo element may be applied to the service described by the USD.

The copy control information may be updated in a program unit or less in accordance with the attributes of the USBD.

According to the present embodiment, the UsageRuleInfo element may be used not only when the protocol for transmitting the service component is ROUTE but also when the MMTP is used in the service layer signaling used in the corresponding protocol.

Referring to (b) of the drawing, an example in which the service configuration and copy control is applied when the UsageRuleUnfo element is a sub-element of USD and included in the USBD is illustrated.

One RF stream in this embodiment carries two services (channels). The UsageRuleUnfo element that carries the copy control information may be included in the USD describing service # 1. In this case, the copy control information may be applied to all streams constituting the service # 1. The receiver may control the restriction, permission, range, etc. of the copy function for the corresponding streams by using the corresponding copy control information.

The description of the S-TSID and the information that may be included therein is as described above. According to this embodiment, copy control information can be added to the S-TSID.

The above-described UsageRuleUnfo element may be included in a service-based transport session instance description (S-TSID) of service layer signaling (SLS).

Referring to (a) of the drawing, the UsageRuleUnfo element may be included in the S-TSID as a lower element of a ROUTE Session (RS) element or a lower element of an LS (LCT Session) element in the S-TSID. Depending on the location where the UsageRuleUnfo element is defined, the range to which the copy control information in the UsageRuleUnfo element is applied may vary. The copy control information may be updated in a program unit or lower unit according to the attribute of the S-TSID.

Referring to (b) of the drawing, when the UsageRuleUnfo element is defined as a lower element of the RS element, an embodiment of application of service configuration and copy control information is shown.

One RF stream in this embodiment transmits two services (channels). A UsageRuleUnfo element for transmitting copy control information exists in an RS element describing RS # 2. In this case, corresponding copy control information may be applied to all streams (eg, enhance video stream) constituting RS # 2. The receiver may control the restriction, permission, range, etc. of the copy function for the corresponding streams by using the corresponding copy control information.

Referring to (c) of the drawing, when the UsageRuleUnfo element is defined as a lower element of the LS element, an embodiment of application of service configuration and copy control information is shown.

One RF stream in this embodiment transmits two services (channels). A UsageRuleUnfo element that carries copy control information exists in the LS element that describes audio (tsi-a). In this case, the copy control information can be applied to the audio stream. The receiver may control the restriction, permission, range, etc. of the copy function for the audio stream by using corresponding copy control information.

On the other hand, UsageRuleUnfo element may exist simultaneously in LLS and SLS. In this case, the receiver first applies the copy control information of the UsageRuleUnfo element existing in the SLS, and sets the value of the copy control information of the UsageRuleUnfo element existing in the LLS as the default value only when the UsageRuleUnfo element does not exist in the SLS. Can be applied to process services or components.

When MMT is used to deliver a service in a next generation broadcast system, the receiver may acquire an MP table using information included in the SLS through a process of the aforementioned signaling structure.

MP table includes table_id information, version information, length information, MP_table_mode information, MMT_package_id element, MMT_package_id_length information, MMT_package_id_byte information, MP_table_descriptors_length information, MP_table_descriptors_length information, MP_table_descriptors_byte information, number_of_asse_ information_flag information, asset_id asset_clock_relation_id information, asset_timescale_flag information, asset_timescale information, asset_location element, location_count information, MMT_general_location_info () information, asset_descriptors element, asset_descriptors_length information, and / or asset_descriptors_byte information.

The table_id information is information for identifying the MP table.

The version information is information indicating the version of the MP table.

The length information is information indicating the length from this next information to the last information / element of the MP table.

The MP_table_mode information is information indicating the mode of the MP table.

The MMT_package_id element may include information on a globally unique identifier for identifying the MMT package.

The MMT_package_id_length information is information indicating the length of MMT_package_id_byte information in the number of bytes.

The MMT_package_id_byte information includes bytes representing a globally unique identifier identifying an MMT package.

The MP_table_descriptors element may include a descriptor for an MP table.

The MP_table_descriptors_length information is information indicating the length of a descriptor included in the MP_table_descriptors element.

The MP_table_descriptors_byte information includes bytes corresponding to descriptors for the MP table.

The number_of_assets information is information indicating the number of assets signaled by the current MP table.

Identifier_mapping () information may include information for identifying an asset and / or information for connecting the asset and a packet for transmitting the asset.

The asset_type information is information indicating the type of the asset. The asset_type information may identify what kind of media component the asset transmits.

The packet_id information is information for identifying a packet for transmitting an asset or a packet included in the asset.

The asset_clock_relation_flag information is information for identifying whether the asset_clock_relation_id information exists. The asset_clock_relation_flag information is information for identifying whether an asset uses an NTP clock or another clock system as a clock reference.

The asset_clock_relation_id information is information that provides a clock relation identifier for an asset.

The asset_timescale_flag information is information for identifying whether the asset_timescale information exists.

The asset_timescale information provides information of a type unit for every typestamp used for an asset, expressed as the number of units in seconds.

The asset_location element may include information indicating the location of the asset.

The location_count information indicates the number of location information of the asset being signaled.

The MMT_general_location_info () information is information indicating the location of an asset.

The asset_descriptors element may include information about a descriptor for an asset.

The asset_descriptors_length information is information representing the length of a descriptor for an asset.

The asset_descriptors_byte information includes bytes corresponding to descriptors for an asset.

When components constituting the service are transmitted through MMT, a usage rule descriptor including the above-described copy control information may be transmitted as part of MMT signaling.

In the following, the MP table that sends information about MMT packets might contain a usage rule descriptor. In the MP table, the usage rule descriptor may exist at the location of MP_table_descrptors_bytes and / or asset_descriptors_bytes.

If the usage rule descriptor exists at the location of MP_table_descrptors_bytes, the usage rule descriptor can deliver copy control information that is applied to all assets belonging to the package described by the MP table. Alternatively, the usage rule descriptor may play a role of delivering initial values of copy control information to be applied to corresponding assets.

If the usage rule descriptor exists at the location of asset_descriptors_bytes, the usage rule descriptor may deliver copy control information applied to an individual asset (or component).

If the usage rule descriptor exists at the location of MP_table_descrptors_bytes and asset_descriptors_bytes at the same time, the receiver can prioritize between the usage rule descriptor included in MP_table_descrptors_bytes and the usage rule descriptor included in asset_descriptors_bytes, thereby processing the signaling information. can do.

For example, the receiver preferentially processes the usage rule descriptor located in asset_descriptors_bytes, and sets the value of the copy control information of the usage rule descriptor present in MP_table_descrptors_bytes as the default value only when asset_descriptors_bytes does not include the usage rule descriptor. By applying, copy control for a service or a component can be performed.

Referring to (a) of the drawing, when the usage rule descriptor exists at the position of asset_descriptors_bytes in the MP table, an embodiment of application to the copy control information of the usage rule descriptor is illustrated.

One RF stream in this embodiment transmits two services (channels). The usage rule descriptor, which carries copy control information, is a loop in the MP table that describes asset # 2 (audio). In this case, the copy control information of the usage rule descriptor may be applied to the corresponding audio stream. The receiver may control the restriction, permission, range, etc. of the copy function for the audio stream by using corresponding copy control information.

The MP table containing the usage rule descriptor is sent in one packet flow (pid-sls) of an individual MMTP session, as shown in (a) of the drawing, or (b) of the drawing, depending on how the SLS is sent. ), It can be encapsulated and transmitted to a structure such as atsc3_message_section () in one UDP / IP session (dIP / dPort # 1) that transmits SLS for all services.

The transmitter generates an ISO Base Media File Format (ISOBMFF) file including data for broadcast content provided from the broadcast system (JS42010).

The transmitter generates one or more segments including the generated ISOBMFF file (JS42020).

The transmitter generates a broadcast signal including the generated one or more segments (JS42030).

The transmitter transmits the broadcast signal (JS42040).

In this case, the broadcast signal may be replaced with a broadband signal. That is, in the broadcast system, when broadcast content or signaling information can be transmitted through broadband, the transmitter or the transmission method may generate a broadband signal and transmit all or part of the above-described data.

According to an embodiment of the present invention, the ISOBMFF file may include a moof box including metadata for presentation of the broadcast content and an mdat box including some or all of components of the broadcast content.

According to an embodiment of the present invention, the ISOBMFF file may further include output control number information indicating the number of devices capable of copying and outputting a media factor expressed by the ISOBMFF file.

Media elements represent elements of video, audio and / or data. Here, the term 'element' may be used as a term for a data set constituting video, audio, and / or data. That is, the media element may represent content, components, segments (subsegments), tracks, samples, adaptation sets, and / or presentations of video, audio, and / or data.

According to an embodiment of the present invention, the ISOBMFF file further includes copy control flag information for identifying whether copy control for the media element is applied, and copy control for indicating the number of times of copying possible for the media element. The information may further include count information.

According to an embodiment of the present invention, the ISOBMFF file may further include playback control number information indicating the number of times that the media element can be played.

According to an embodiment of the present invention, the ISOBMFF file may further include copy control expiration information indicating an expiration period of recording and / or time-shift for the media element.

According to an embodiment of the present invention, the ISOBMFF file may further include trick mode control flag information for identifying whether a trick mode is applicable to the media element.

According to an embodiment of the present invention, the ISOBMFF file includes the output control number information, the copy control flag information, the copy control number information, the reproduction control number information, the copy control expiration information, and the trick mode control flag information. It may include a copy control box including a.

According to an embodiment of the present invention, the ISOBMFF file includes a tkhd box including information describing properties of a video track, an audio track, and / or a data track of the broadcast content, wherein the tkhd box includes the output. Control number information, the copy control flag information, the copy control count information, the reproduction control count information, the copy control expiration information and the trick mode control flag information.

The broadcast system according to an embodiment of the present invention includes a transmitter J43100 and / or a receiver J43200.

The transmitter J43200 may include a data generator J43110, a signaling encoder J43120, a broadcast signal generator J43130, and / or a broadcast signal transmitter J43140.

The data generator J43110 generates an ISO Base Media File Format (ISOBMFF) file including data for broadcast content provided from a broadcast system, and generates one or more segments including the generated ISOBMFF file.

The signaling encoder J43120 encodes or generates the aforementioned signaling information. The signaling information includes low level signaling, service list table, service layer signaling, MPD, MP table, copy control information and / or metadata of ISOBMFF, as described above.

The broadcast signal generator J43130 generates a broadcast signal including the generated one or more segments.

The broadcast signal transmitter J43140 transmits the broadcast signal.

The receiver J43200 includes a signal receiver J43210, a processor J43220, and / or a display unit J43230.

The signal receiver J43210 receives a broadcast signal or a broadband signal.

The processor J43220 decodes, parses, or processes an ISO Base Media File Format (ISOBMFF) file that includes data for one or more segments and / or broadcast content provided by the broadcast system including the ISOBMFF file. The processor J43220 may decode the signaling information. The processor J43220 may perform copy control on the media element by using the above-described copy control information.

The display unit J43230 expresses broadcast content.

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, CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like, and may also be implemented in the form of a carrier wave such as transmission over the Internet. . The processor-readable recording medium can also be distributed over network coupled computer systems so that the processor-readable code is stored and executed in a distributed fashion.

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

Generating an ISO Base Media File Format (ISOBMFF) file containing data for broadcast content provided by the broadcast system;

Generating at least one segment comprising the generated ISOBMFF file;

Generating a broadcast signal including the generated one or more segments; And

Transmitting the broadcast signal;

Including;

Here, the ISOBMFF file includes a moof box including metadata for presentation of the broadcast content, and an mdat box including some or all of components of the broadcast content.

The ISOBMFF file may further include output control number information indicating a number of devices capable of copying and outputting a media factor expressed by the ISOBMFF file. .
The method of claim 1, wherein the ISOBMFF file,

Copy control flag information for identifying whether copy control for the media element is applied;

And a copy control number information indicating a number of times of copying possible for the media element.
The method of claim 2, wherein the ISOBMFF file,

And reproducing control number information indicating the number of times that the media element can be reproduced.
The method of claim 3, wherein the ISOBMFF file,

And copy control expiration information indicative of an expiration period of recording and / or time-shift for the media element.
The method of claim 4, wherein the ISOBMFF file,

And trick mode control flag information identifying whether or not a trick mode is applicable to the media element.
The method of claim 5, wherein the ISOBMFF file,

And a copy control box including the output control number information, the copy control flag information, the copy control number information, the reproduction control number information, the copy control expiration information, and the trick mode control flag information. A method of transmitting a signal.
The method of claim 5, wherein the ISOBMFF file,

A tkhd box containing information describing properties of a video track, an audio track, and / or a data track of the broadcast content;

The tkhd box includes the output control number information, the copy control flag information, the copy control number information, the reproduction control number information, the copy control expiration information, and the trick mode control flag information. How to process transmission.
A data generation unit generating an ISO Base Media File Format (ISOBMFF) file including data for broadcast content provided by a broadcasting system and generating one or more segments including the generated ISOBMFF file;

A broadcast signal generator configured to generate a broadcast signal including the generated one or more segments; And

A broadcast signal transmitter for transmitting the broadcast signal;

Including;

Here, the ISOBMFF file includes a moof box including metadata for presentation of the broadcast content, and an mdat box including some or all of components of the broadcast content.

The ISOBMFF file may further include output control number information indicating the number of devices capable of copying and outputting a media factor expressed by the ISOBMFF file. .
The method of claim 8, wherein the ISOBMFF file,

Copy control flag information for identifying whether copy control for the media element is applied;

And transmitting copy control number information indicating a number of possible copying of the media element.
The method of claim 9, wherein the ISOBMFF file,

And processing control count information indicating the number of times the media element can be played.
The method of claim 10, wherein the ISOBMFF file,

And copy control expiration information indicating an expiration period of recording and / or time-shift for the media element.
The method of claim 11, wherein the ISOBMFF file,

And trick mode control flag information for identifying whether a trick mode is applicable to the media element.
The method of claim 12, wherein the ISOBMFF file,

And a copy control box including the output control number information, the copy control flag information, the copy control number information, the reproduction control number information, the copy control expiration information, and the trick mode control flag information. Apparatus for transmitting and processing signals.
The method of claim 12, wherein the ISOBMFF file,

A tkhd box containing information describing properties of a video track, an audio track, and / or a data track of the broadcast content;

The tkhd box includes the output control number information, the copy control flag information, the copy control number information, the reproduction control number information, the copy control expiration information, and the trick mode control flag information. Transmission processing device.