WO2016190720A1

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

Info

Publication number: WO2016190720A1
Application number: PCT/KR2016/005688
Authority: WO
Inventors: 안승주; 송영훈; 문경수; 이진원; 홍성룡; 고우석
Original assignee: 엘지전자 주식회사
Priority date: 2015-05-28
Filing date: 2016-05-30
Publication date: 2016-12-01

Abstract

The present invention presents a method for transmitting a broadcast signal. The method for transmitting a broadcast signal, according to the present invention, presents a system capable of supporting a next-generation broadcast service in an environment supporting next-generation hybrid broadcast by using a terrestrial broadcast network and an Internet network. In addition, an efficient signaling plan capable of covering both the terrestrial broadcast network and the Internet network is presented in the environment supporting the next-generation hybrid broadcast.

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.

The present invention can provide a method of implementing an existing advertisement insertion method in a broadcasting system.

The present invention can provide a method for dynamically inserting AD (advertisement, advertisement) in a next generation hybrid broadcasting system.

The present invention can provide a method of playing an advertisement that matches a receiver characteristic or a user's preference.

The present invention can provide a method of playing an advertisement in accordance with a receiver characteristic or a user's preference at an appropriate time.

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 shows a structure of a broadcast signal transmission apparatus for a next generation broadcast service according to an embodiment of the present invention.

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

FIG. 10 is a block diagram of an interleaving address generator composed of a main-PRBS generator and a sub-PRBS generator according to each FFT mode included in a frequency interleaver according to an embodiment of the present invention.

11 is a diagram illustrating a hybrid broadcast reception device according to an embodiment of the present invention.

12 is a block diagram of a hybrid broadcast receiver according to an embodiment of the present invention.

13 illustrates a protocol stack of a next generation hybrid broadcast system according to an embodiment of the present invention.

14 illustrates a protocol stack for supporting hybrid broadcast service according to an embodiment of the present invention.

FIG. 15 is a diagram illustrating a configuration of a media presentation description (MPD) including @xlink for AD insertion according to an embodiment of the present invention.

16 is a diagram illustrating a process of performing advertisement insertion according to an embodiment of the present invention.

17 is a diagram illustrating a configuration of an advertisement insertion processing module of a receiver according to an embodiment of the present invention.

18 is a diagram illustrating a configuration of an MPD and an emsg box when a SCTE 35 queue message is delivered to an event or an inband event 'emsg' box of an MPD according to an embodiment of the present invention.

19 illustrates a system structure of an app based model according to an embodiment of the present invention.

20 illustrates signaling of period continuity using MPD according to an embodiment of the present invention.

FIG. 21 is a diagram illustrating the configuration of an MPD according to a single client native ad insertion according to an embodiment of the present invention.

FIG. 22 is a diagram illustrating the configuration of an Assetidentifier and an MPD according to a single client native ad insertion according to an embodiment of the present invention.

23 is a diagram illustrating a system structure of a server based model according to an embodiment of the present invention.

24 is a diagram comparing an app-based model and a server-based model according to an embodiment of the present invention.

25 is a diagram illustrating an advertisement insertion for ATSC 3.0 according to an embodiment of the present invention.

FIG. 26 is a diagram illustrating a broadcasting system when an advertisement is transmitted to a broadcasting network according to NRT broadcasting according to an embodiment of the present invention.

27 is a diagram illustrating a broadcast system when an advertisement is transmitted to a broadcasting network according to streaming broadcasting according to an embodiment of the present invention.

28 is a diagram illustrating the configuration of filtering criteria according to an embodiment of the present invention.

29 is a diagram illustrating a configuration of an S-TSID including a filtering criterion according to an embodiment of the present invention.

30 is a diagram illustrating an advertisement insertion process when an advertisement is transmitted to a broadcasting network according to NRT broadcasting according to an embodiment of the present invention.

31 is a diagram showing the structure of a broadcast system of a server-based model linked to an app in a receiver according to an embodiment of the present invention.

32 is a diagram illustrating an advertisement insertion process when an advertisement is transmitted through a broadcasting network through NRT broadcasting in a broadcasting system of a server-based model linked to an app in a receiver according to an embodiment of the present invention.

33 is a diagram illustrating an advertisement insertion process when an advertisement is transmitted through a broadcasting network through NRT broadcasting in a broadcasting system of a server-based model linked to an app in a receiver according to an embodiment of the present invention.

FIG. 34 is a diagram illustrating an advertisement insertion process when an advertisement is transmitted through a broadcasting network through NRT broadcasting in a broadcast system of a server-based model linked to an app in a receiver according to another embodiment of the present invention.

FIG. 35 is a diagram illustrating an advertisement insertion process when an advertisement is transmitted through a broadcasting network through NRT broadcasting in a broadcasting system of a server-based model linked to an app in a receiver according to another embodiment of the present invention.

36 is a diagram illustrating an advertisement insertion process when an advertisement is transmitted through a broadband network in a broadcast system of a server-based model linked to an app in a receiver according to another embodiment of the present invention.

37 is a diagram illustrating an advertisement insertion process when an advertisement is transmitted through a broadband network in a broadcast system of a server-based model linked to an app in a receiver according to another embodiment of the present invention.

38 is a view illustrating a class for acquiring demographic information of a receiver in an app according to an embodiment of the present invention.

FIG. 39 is a view showing properties of an XLinkType class used to deliver xlink information to an ad determination module of an app according to an embodiment of the present invention. FIG.

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

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

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.

A broadcast signal transmission apparatus for a next generation broadcast service according to an embodiment of the present invention includes an input format block 1000, a bit interleaved coding & modulation (BICM) block 1010, and a frame building block 1020, orthogonal frequency division multiplexing (OFDM) generation block (OFDM generation block) 1030, and signaling generation block 1040. The operation of each block of the broadcast signal transmission apparatus will be described.

In the input data according to an embodiment of the present invention, IP streams / packets and MPEG2-TS may be main input formats, and other stream types are treated as general streams.

The input format block 1000 can demultiplex each input stream into one or multiple data pipes to which independent coding and modulation is applied. The data pipe is the basic unit for controlling robustness, which affects the quality of service (QoS). One or multiple services or service components may be delivered by one data pipe. A data pipe is a logical channel at the physical layer that carries service data or related metadata that can carry one or multiple services or service components.

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

The BICM block 1010 may include a processing block applied to a profile (or system) to which MIMO is not applied and / or a processing block of a profile (or system) to which MIMO is applied, and for processing each data pipe. It may include a plurality of processing blocks.

The processing block of the BICM block to which MIMO is not applied may include a data FEC encoder, a bit interleaver, a constellation mapper, a signal space diversity (SSD) encoding block, and a time interleaver. The processing block of the BICM block to which MIMO is applied is distinguished from the processing block of BICM to which MIMO is not applied in that it further includes a cell word demultiplexer and a MIMO encoding block.

The data FEC encoder performs FEC encoding on the input BBF to generate the FECBLOCK procedure using outer coding (BCH) and inner coding (LDPC). Outer coding (BCH) is an optional coding method. The bit interleaver interleaves the output of the data FEC encoder to achieve optimized performance with a combination of LDPC codes and modulation schemes. Constellation Mapper uses QPSK, QAM-16, non-uniform QAM (NUQ-64, NUQ-256, NUQ-1024) or non-uniform constellation (NUC-16, NUC-64, NUC-256, NUC-1024) The cell word from the bit interleaver or cell word demultiplexer can then be modulated to provide a power-normalized constellation point. It is observed that NUQ has any shape, while QAM-16 and NUQ have a square shape. Both NUQ and NUC are specifically defined for each code rate and are signaled by the parameter DP_MOD of PLS2 data. The time interleaver may operate at the data pipe level. The parameters of time interleaving can be set differently for each data pipe.

The time interleaver of the present invention may be located between a BICM chain block and a frame builder. In this case, the time interleaver according to the present invention may selectively use a convolution interleaver (CI) and a block interleaver (BI) according to a physical layer pipe (PLP) mode, or both. PLP according to an embodiment of the present invention is a physical path used in the same concept as the above-described DP, the name can be changed according to the designer's intention. The PLP mode according to an embodiment of the present invention may include a single PLP mode or a multiple PLP mode according to the number of PLPs processed by the broadcast signal transmitter or the broadcast signal transmitter. In the present invention, time interleaving using different time interleaving methods according to the PLP mode may be referred to as hybrid time interleaving.

The hybrid time interleaver may include a block interleaver (BI) and a convolution interleaver (CI). If PLP_NUM = 1, the block interleaver is not applied (block interleaver off), and only the convolutional interleaver is applied. When PLP_NUM> 1, both the block interleaver and the convolution interleaver may be applied (block interleaver on). The structure and operation of the convolutional interleaver applied when PLP_NUM> 1 may be different from the structure and operation of the convolutional interleaver applied when PLP_NUM = 1. The hybrid time deinterleaver may perform an operation corresponding to the reverse operation of the aforementioned hybrid time interleaver.

The cell word demultiplexer is used to separate a single cell word stream into a dual cell word stream for MIMO processing. The MIMO encoding block can process the output of the cell word demultiplexer using the MIMO encoding scheme. The MIMO encoding scheme of the present invention may be defined as full-rate spatial multiplexing (FR-SM) to provide capacity increase with a relatively small complexity increase at the receiver side. MIMO processing is applied at the data pipe level. NUQ (e _{1, i} and e _{2, i} ), which is a pair of constellation mapper outputs, is fed to the input of the MIMO encoder, and MIMO encoder output pairs (g1, i and g2, i). Is transmitted by the same carrier k and OFDM symbol l of each transmit antenna.

The frame building block 1020 may map data cells of an input data pipe to OFDM symbols and perform frequency interleaving for frequency domain diversity within one frame.

A frame according to an embodiment of the present invention is divided into a preamble, one or more frame signaling symbols (FSS), and normal data symbols. The preamble is a special symbol that provides a set of basic transmission parameters for efficient transmission and reception of a signal. The preamble may signal a basic transmission parameter and a transmission type of the frame. In particular, the preamble may indicate whether an emergency alert service (EAS) is provided in the current frame. The main purpose of the FSS is to carry PLS data. For fast synchronization and channel estimation, and fast decoding of PLS data, the FSS has a higher density pilot pattern than normal data symbols.

The frame building block adjusts the timing between the data pipes and the corresponding PLS data so that a delay compensation block is provided at the transmitter to ensure co-time between the data pipes and the corresponding PLS data. And a cell mapper and a frequency interleaver for mapping a PLS, a data pipe, an auxiliary stream, and a dummy cell to an active carrier of an OFDM symbol in a frame.

The frequency interleaver may provide frequency diversity by randomly interleaving data cells received from the cell mapper. In addition, the frequency interleaver uses a different interleaving seed order to obtain the maximum interleaving gain in a single frame. The frequency interleaver uses a single symbol or data corresponding to an OFDM symbol pair consisting of two sequential OFDM symbols. Operate on corresponding data.

OFDM generation block 1030 modulates the OFDM carrier, inserts pilots, and generates time-domain signals for transmission by the cells generated by the frame building block. In addition, the block sequentially inserts a guard interval and applies a PAPR reduction process to generate a final RF signal.

The signaling generation block 1040 may generate physical layer signaling information used for the operation of each functional block. Signaling information according to an embodiment of the present invention may include PLS data. PLS provides a means by which a receiver can connect to a physical layer data pipe. PLS data consists of PLS1 data and PLS2 data.

PLS1 data is the first set of PLS data delivered to the FSS in frames with fixed size, coding, and modulation that convey basic information about the system as well as the parameters needed to decode the PLS2 data. PLS1 data provides basic transmission parameters including the parameters required to enable reception and decoding of PLS2 data. PLS2 data carries more detailed PLS data about the data pipes and systems and is the second set of PLS data sent to the FSS. PLS2 signaling further consists of two types of parameters: PLS2 static data (PLS2-STAT data) and PLS2 dynamic data (PLS2-DYN data). PLS2 static data is PLS2 data that is static during the duration of a frame group, and PLS2 dynamic data is PLS2 data that changes dynamically from frame to frame.

The PLS2 data may include FIC_FLAG information. Fast Information Channel (FIC) is a dedicated channel for transmitting cross-layer information that enables fast service acquisition and channel scanning. The FIC_FLAG information is a 1-bit field and indicates whether a fast information channel (FIC) is used in the current frame group.If the value of this field is set to 1, the FIC is provided in the current frame. If the value of the field is set to 0, the FIC is not transmitted in the current frame. The BICM block 1010 may include a BICM block for protecting PLS data The BICM block for protecting PLS data is a PLS FEC encoder. , Bit interleaver, and constellation mapper.

The PLS FEC encoder performs external encoding on scrambled

PLS

1,2 data using a scrambler for scrambling PLS1 data and PLS2 data, shortened BCH code for PLS protection, and a BCH for inserting zero bits after BCH encoding. An encoding / zero insertion block, an LDPC encoding block for performing encoding using an LDPC code, and an LDPC parity puncturing block may be included. For PLS1 data only, the output bits of zero insertion can be permutated before LDPC encoding. The bit interleaver interleaves the respective shortened and punctured PLS1 data and PLS2 data, and the constellation mapper bit interleaves. The PLS1 data and the PLS2 data can be mapped to the constellation.

The broadcast signal receiving apparatus for the next generation broadcast service according to an embodiment of the present invention may perform a reverse process of the broadcast signal transmitting apparatus for the next generation broadcast service described with reference to FIG. 8.

An apparatus for receiving broadcast signals for a next generation broadcast service according to an embodiment of the present invention includes a synchronization and demodulation module for performing demodulation corresponding to a reverse process of a procedure executed by a broadcast signal transmitting apparatus and an input signal. A frame parsing module for parsing a frame, extracting data on which a service selected by a user is transmitted, converting an input signal into bit region data, and then deinterleaving the bit region data as necessary, and transmitting efficiency A demapping and decoding module for performing demapping on the mapping applied for decoding, and correcting an error occurring in a transmission channel through decoding, of various compression / signal processing procedures applied by a broadcast signal transmission apparatus. Demodulated by an output processor and a synchronization and demodulation module that executes the inverse process It may include a signaling decoding module for obtaining and processing the PLS information from the signal. The frame parsing module, the demapping and decoding module, and the output processor may execute the function by using the PLS data output from the signaling decoding module.

The time interleaver is described below. A time interleaving group according to an embodiment of the present invention is directly mapped to one frame or spread over P _I frames. Each time interleaving group is further divided into one or more (N _TI ) time interleaving blocks. Here, each time interleaving block corresponds to one use of the time interleaver memory. The time interleaving block in the time interleaving group may include different numbers of XFECBLOCKs. In general, the time interleaver may also act as a buffer for data pipe data prior to the frame generation process.

The time interleaver according to an embodiment of the present invention is a twisted row-column block interleaver. The twisted row-column block interleaver according to an embodiment of the present invention writes the first XFECBLOCK in the column direction to the first column of the time interleaving memory, the second XFECBLOCK to the next column and the remaining XFECBLOCKs in the time interleaving block in the same manner. You can fill in these. And in an interleaving array, cells can be read diagonally from the first row to the last row (starting from the leftmost column to the right along the row). In this case, the interleaving array for the twisted row-column block interleaver may insert the virtual XFECBLOCK into the time interleaving memory to achieve a single memory deinterleaving at the receiver side regardless of the number of XFECBLOCKs in the time interleaving block. In this case, the virtual XFECBLOCK must be inserted in front of the other XFECBLOCKs to achieve a single memory deinterleaving on the receiver side.

The block shown on the left side of the figure represents a TI memory address array, and the block shown on the right side of the figure shows that virtual FEC blocks are placed at the front of the TI group for two consecutive TI groups. It represents the writing operation when two and one are inserted respectively.

The frequency interleaver according to an embodiment of the present invention may include an interleaving address generator for generating an interleaving address for applying to data corresponding to a symbol pair.

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

The interleaving process for an OFDM symbol pair uses one interleaving sequence and is described as follows. First, the available data cells (output cells from the cell mapper) to be interleaved in one OFDM symbol O _{m, l} are l = 0,... , O _{m, l} = [x _{m, l, 0} ,... For N _sym- 1. , x _{m, l, p} ,… , x _{m, l, Ndata-1} ] Where x _{m, l, p} is the p th cell of the l th OFDM symbol in the m th frame, and N _data is the number of data cells. Frame _data and N = C _FSS for the signaling symbols, and _data N = C _data for the normal data, the _FES Frame N = _data for the edge symbol C. In addition, the interleaved data cells have l = 0,... , P _{m, l} = [v _{m, l, 0} ,... For N _sym- 1. , v _{m, l, Ndata-1} ]

For an OFDM symbol pair, the interleaved OFDM symbol pair is given by v _{m, l, Hi (p)} = x _{m, l, p} , p = 0,... For the first OFDM symbol of each pair. , Given by N _data- 1, for the second OFDM symbol of each pair v _{m, l, p} = x _{m, l, Hi (p)} , p = 0,... Is given by N _data- 1. At this time, H _l (p) is an interleaving address generated based on the cyclic shift value (symbol offset) of the PRBS generator and the sub-PRBS generator.

The hybrid broadcasting system may transmit a broadcast signal by interworking a terrestrial broadcasting network and an internet network. The hybrid broadcast reception device may receive a broadcast signal through a terrestrial broadcast network (broadcast) and an internet network (broadband). The hybrid broadcast receiver includes a physical layer module, a physical layer I / F module, a service / content acquisition controller, an internet access control module, a signaling decoder, a service signaling manager, a service guide manager, an application signaling manager, an alarm signal manager, an alarm signal parser, Targeting signal parser, streaming media engine, non-real time file processor, component synchronizer, targeting processor, application processor, A / V processor, device manager, data sharing and communication unit, redistribution module, companion device and / or external modules can do.

The physical layer module (s) may receive and process a broadcast-related signal through a terrestrial broadcast channel, convert it into an appropriate form, and deliver the signal to a physical layer I / F module.

The physical layer I / F module (s) may obtain an IP datagram from information obtained from the physical layer module. In addition, the physical layer I / F module may convert the obtained IP datagram into a specific frame (eg, RS Frame, GSE, etc.).

The service / content acquisition controller may perform a control operation for acquiring service, content, and signaling data related thereto through broadcast and / or broadband channels.

The Internet Access Control Module (s) may control a receiver operation for acquiring a service, content, or the like through a broadband channel.

The signaling decoder may decode signaling information obtained through a broadcast channel.

The service signaling manager may extract, parse, and manage signaling information related to service scan and service / content from an IP datagram.

The service guide manager may extract announcement information from an IP datagram, manage an SG database, and provide a service guide.

The App Signaling Manager may extract, parse and manage signaling information related to application acquisition from an IP datagram.

Alert Signaling Parser can extract, parse and manage signaling information related to alerting from IP datagram.

Targeting Signaling Parser can extract, parse and manage signaling information related to service / content personalization or targeting from IP datagram. In addition, the targeting signal parser may deliver the parsed signaling information to the targeting processor.

The streaming media engine can extract and decode audio / video data for A / V streaming from IP datagrams.

The non-real time file processor can extract, decode and manage file type data such as NRT data and applications from IP datagrams.

The Component Synchronizer can synchronize content and services such as streaming audio / video data and NRT data.

The targeting processor may process an operation related to personalization of a service / content based on the targeting signaling data received from the targeting signal parser.

The App Processor may process application related information, downloaded application status, and display parameters.

The A / V Processor may perform audio / video rendering related operations based on decoded audio, video data, and application data.

The device manager may perform a connection and data exchange operation with an external device. In addition, the device manager may perform management operations on external devices, such as adding, deleting, and updating external devices that can be interworked.

The data sharing & communication unit can process information related to data transmission and exchange between the hybrid broadcast receiver and an external device. Here, the data that can be transmitted and exchanged may be signaling, A / V data, or the like.

The redistribution module (s) may obtain relevant information about next-generation broadcast services and contents when the broadcast receiver does not directly receive the terrestrial broadcast signal. In addition, the redistribution module may support the acquisition of broadcast services and content by the next generation broadcast system when the broadcast receiver does not directly receive the terrestrial broadcast signal.

Companion device (s) may be connected to the broadcast receiver of the present invention to share audio, video, or signaling inclusion data. The companion device may refer to an external device connected to the broadcast receiver.

The external module may refer to a module for providing a broadcast service / content and may be, for example, a next generation broadcast service / content server. The external module may refer to an external device connected to the broadcast receiver.

The hybrid broadcast receiver may receive a hybrid broadcast service through interlocking terrestrial broadcast and broadband in a DTV service of a next generation broadcast system. The hybrid broadcast receiver may receive broadcast audio / video (Audio / Video, A / V) content transmitted through terrestrial broadcast, and receive enhancement data or a part of broadcast A / V content related thereto in real time through broadband. . In this specification, broadcast audio / video (A / V) content may be referred to as media content.

Hybrid broadcast receivers include Physical Layer Controller (D55010), Tuner (Tuner, D55020), Physical Frame Parser (D55030), Link Layer Frame Parser (D55040), IP / UDP Datagram Filter (IP / UDP Datagram Filter, D55050), ATSC 3.0 Digital Television Control Engine (ATSC 3.0 DTV Control Engine, D55060), ALC / LCT + Client (ALC / LCT + Client, D55070), Timing Control (D55080), Signaling Signaling Parser (D55090), DASH Client (Dynamic Adaptive Streaming over HTTP Client, DASH Client, D55100), HTTP Access Client (HTTP Access Client, D55110), ISO BMFF Parser (ISO Base Media File Format Parser, ISO BMFF Parser, D55120) and / or a media decoder D55130.

The physical layer controller D55010 may control operations of the tuner D55020 and the physical frame parser D55030 using radio frequency (RF) information of a terrestrial broadcast channel intended to be received by the hybrid broadcast receiver. .

The tuner D55020 may receive and process a broadcast-related signal through a terrestrial broadcast channel and convert it to an appropriate form. For example, the tuner D55020 may convert the received terrestrial broadcast signal into a physical frame.

The physical frame parser D55030 may obtain a link layer frame through parsing the received physical frame and processing related thereto.

The link layer parser D55040 may perform a related operation for acquiring link layer signaling or the like from an link layer frame or for acquiring an IP / UDP datagram or an MPEG-2 TS. The connection layer parser D55040 may output at least one or more IP / UDP datagrams.

The IP / UDP datagram filter D55050 may filter a specific IP / UDP datagram from the received at least one IP / UDP datagram. That is, the IP / UDP datagram filter D55050 selectively selects the IP / UDP datagram selected by the ATSC 3.0 digital television control engine D55060 among at least one IP / UDP datagram output from the connection layer parser D55040. You can filter. The IP / UDP datagram filter D55050 may output an application layer transport protocol packet such as ALC / LCT +.

The ATSC 3.0 digital television control engine (D55060) may be responsible for the interface between the modules included in each hybrid broadcast receiver. In addition, the ATSC 3.0 digital television control engine (D55060) transmits the parameters required for each module to each module, thereby controlling the operation of each module. In the present invention, the ATSC 3.0 digital television control engine D55060 may deliver a media presentation description (MPD) and / or an MPD URL to the DASH client D55100. Also, in the present invention, the ATSC 3.0 digital television control engine D55060 may transmit a delivery mode and / or a transport session identifier (TSI) to the ALC / LCT + client D55070. Here, TSI may indicate an identifier of a session for transmitting a transport packet including a signaling message such as MPD or MPD URL related signaling, for example, an ALC / LCT + session or FLUTE session, which is an application layer transport protocol. In addition, the transport session identifier may correspond to an asset id of the MMT.

The ALC / LCT + client D55070 may generate one or more ISO Base Media File Format (ISOBMFF) objects by processing application layer transport protocol packets such as ALC / LCT + and collecting and processing a plurality of packets. The application layer transport protocol packet may include an ALC / LCT packet, an ALC / LCT + packet, a ROUTE packet, and / or an MMTP packet.

The timing controller D55080 may process a packet including system time information and control the system clock accordingly.

The signaling parser D55090 may acquire and parse DTV broadcast service related signaling, and generate and manage a channel map or the like based on the parsed signaling. In the present invention, the signaling parser may parse extended MPD or MPD related information from signaling information.

The DASH client D55100 may perform operations related to real-time streaming or adaptive streaming. The DASH client D55100 may receive the DASH content from the HTTP server through the HTTP connection client D55110. The DASH client D55100 may output the ISO Base Media File Format object by processing the received DASH segment. In the present invention, the DASH client D55100 may transmit the full Representation ID (Fully qualified Representation ID) or the segment URL to the ATSC 3.0 digital television control engine (D55060). Here, the entire Representation ID may mean, for example, an ID combining the MPD URL, period @ id, and representation @ id. The DASH client D55100 may also receive an MPD or MPD URL from the ATSC 3.0 digital television control engine D55060. The DASH client D55100 may receive a desired media stream or DASH segment from the HTTP server using the received MPD or MPD URL. In the present specification, the DASH client D55100 may be referred to as a processor.

The HTTP access client D55110 may request specific information from the HTTP server, and receive and process a response from the HTTP server. Here, the HTTP server may process a request received from an HTTP connection client and provide a response thereto.

The ISO BMFF parser D55120 may extract audio / video data from an ISO Base Media File Format object.

The media decoder D55130 may decode the received audio and / or video data and perform processing for presenting the decoded audio / video data.

In order for the hybrid broadcast receiver of the present invention to provide a hybrid broadcast service through interworking of a terrestrial broadcast network and a broadband, an extension or modification of the MPD is required. The above-mentioned terrestrial broadcasting system may transmit an extended or modified MPD, and the hybrid broadcast receiver may receive content through broadcast or broadband using the extended or modified MPD. That is, the hybrid broadcast receiver may receive the extended or modified MPD through terrestrial broadcasting and receive content through terrestrial broadcasting or broadband based on the MPD. The following describes elements and attributes that should be additionally included in the extended or modified MPD compared to the existing MPD. In the following, an extended or modified MPD may be described as an MPD.

MPD can be extended or modified to represent ATSC 3.0 services. The extended or modified MPD may additionally include MPD @ anchorPresentationTime, Common @ presentable, Common.Targeting, Common.TargetDevice and / or Common @ associatedTo.

The MPD @ anchorPresentationTime may indicate an anchor of the presentation time of the segments included in the MPD, that is, the time at which it is based. In the following, MPD @ anchorPresentationTime may be used as an effective time of the MPD. MPD @ anchorPresentationTime may indicate the earliest playback time point among segments included in the MPD.

The MPD may further include common attributes and elements. Common attributes and elements can be applied to AdaptionSet, Representation, SubRepresentation, etc. in MPD. Common @ presentable may indicate that the media described by the MPD is a component that can be presented.

Common.Targeting may indicate targeting properties and / or personalization properties of media described by the MPD.

Common.TargetDevice may represent a target device or target devices of the media described by the MPD.

Common @ associatedTo may indicate an adaptationSet and / or representation related to the media described by the MPD.

In addition, MPD @ id, Period @ id and AdaptationSet @ id included in the MPD may be required to specify the media content described by the MPD. That is, the DASH client may specify the content to be received based on the MPD as MPD @ id, Period @ id, and AdaptationSet @ id, and deliver the content to the ATSC 3.0 digital television control engine. The ATSC 3.0 digital television control engine can also receive the content and deliver it to the DASH client.

As shown, the next generation broadcast transmission system supporting IP-based hybrid broadcasting may encapsulate audio or video data of a broadcast service in an ISO Base Media File Format (hereinafter referred to as ISO BMFF). Here, the encapsulation may use a form such as DASH Segment or MPU (Media Processing Unit) of MMT. In addition, the next generation broadcasting system may transmit the encapsulated data to the broadcasting network and the Internet network in the same manner or differently according to the properties of each transmission network. In addition, the next generation broadcast system may transmit the encapsulated data using at least one of broadcast or broadband. In the case of a broadcast network using broadcast, the broadcast system may transmit data encapsulated in the form of ISO Base Media File (hereinafter referred to as ISO BMFF) through an application layer transport protocol packet supporting real-time object transmission. For example, a broadcast system may encapsulate a real-time object delivery over unidirectional transport (hereinafter referred to as ROUTE) or a transport packet of an MMTP. The broadcast system may generate the encapsulated data as an IP / UDP datagram and then load the encapsulated data into a broadcast signal. In the case of using broadband, the broadcasting system may deliver the encapsulated data to the receiver based on a streaming technique such as DASH.

In addition, the broadcast system may transmit signaling information of a broadcast service in the following method. In the case of a broadcast network using broadcast, the broadcast system may transmit signaling information through the next-generation broadcast transmission system and the physical layer of the broadcast network according to signaling properties. Here, the broadcast system may transmit signaling information through a specific data pipe (hereinafter referred to as DP) of a transport frame included in the broadcast signal. The signaling form transmitted through broadcast may be encapsulated into a bit stream or an IP / UDP datagram. In case of using broadband, the broadcast system may return signaling data in response to a request of a receiver and transmit the signaling data.

In addition, the broadcast system may transmit ESG or NRT content of a broadcast service in the following manner. In the case of a broadcast network using broadcast, the broadcast system may encapsulate the ESG or NRT content using an application layer transport protocol packet, for example, Real-Time Object Delivery over Unidirectional Transport (ROUTE), MMTP transport packet, and the like. In addition, the encapsulated ESG or NRT content can be generated as an IP / UDP datagram and loaded on a broadcast signal for transmission. In the case of using broadband, the broadcast system may return ESG or NRT content and the like as a response to the request of the receiver and transmit the same.

According to an embodiment of the present invention, the part labeled Broadcast and / or Broadband in this figure represents a physical layer, and the physical layer can receive a terrestrial broadcast signal and convert it into an appropriate form. In this figure, the portion labeled IP / UDP and / or IP / TCP represents an IP layer, and the IP layer obtains an IP datagram using information obtained from the physical layer, or acquires an IP datagram from a specific frame (e.g., , RS Frame, GSE, etc.). In this figure, a portion labeled MMTP and / or ROUTE represents a delivery layer and MMTP and / or ROUTE represents a delivery protocol for real time and non-real time content transmission. Signlaing Messages in this figure represent signaling information to support effective acquisition of content / service. Signlaing Messages can be expressed in binary or XML format, and can be delivered over terrestrial broadcast networks or broadband.

According to an embodiment of the present invention, real-time broadcast A / V content and data may be expressed in an ISO Base Media File Format, etc., which may be delivered in real time through a terrestrial broadcasting network. Non-real-time content may be delivered based on IP / UDP / ROUTE. Furthermore, the DASH may be used to receive or request content in real time through an internet network (broadband).

The broadcast receiver according to an embodiment of the present invention may provide various enhanced services, such as an interactive service and a second screen service, to the viewer by combining data received according to a protocol stack. .

One of the potential applications to be used in DTV service is hybrid broadcasting service through interworking with internet network. According to an embodiment of the present invention, a broadcast system transmits enhancement data or part of broadcast A / V content associated with broadcast A / V content transmitted through a terrestrial broadcasting network in real time through an internet network, thereby providing a user with the user. It can let you experience various contents.

The broadcast system according to an embodiment of the present invention may provide a method for dynamically inserting an advertisement (AD) in a next generation hybrid broadcast system.

The broadcasting system according to an embodiment of the present invention may provide a method for performing advertisement insertion in an environment supporting next generation hybrid broadcasting using a terrestrial broadcasting network and / or an internet network.

The broadcast receiver according to an embodiment of the present invention can support the next generation hybrid broadcast service and can process advertisement insertion related information.

The broadcast system according to an embodiment of the present invention provides a method for inserting an advertisement in a next generation hybrid broadcast environment. Ad insertion according to an embodiment of the present invention (AD Insertion) inserts an advertisement in a certain section while the viewer is watching the broadcast, or by replacing the advertisement other than the previously organized advertising in the AD break (AD break) Represents a service to show.

According to an embodiment of the present invention, audio / video data may be delivered in the form of ISOBMFF in a next generation hybrid broadcasting system, and various media presentation techniques may be applied to present the same. The broadcast system according to an embodiment of the present invention may provide an advertisement insertion method when MPEG DASH is used as a media presentation technology. The advertisement insertion scheme according to an embodiment of the present invention has been described under the premise of MPEG DASH, but may be applied to the case under the premise of other media presentation techniques.

According to an embodiment of the present invention, a method of performing advertisement insertion may vary according to a path (broadcast network or Internet network) through which a media presentation description (MPD) and / or advertisement content (AD content) is transmitted.

According to an embodiment of the present invention, a method of performing advertisement insertion when both the MPD and the advertisement content (AD content) are transmitted through a broadcasting network will be described below.

According to an embodiment of the present invention, a DASH client basically configures audio / video data (A / V data) through an HTTP request / response through a broadband channel. Download the segment and play it back. However, in a receiver that does not support data reception through a broadband channel, advertisement content may not be played through the DASH client. The broadcast system according to an embodiment of the present invention provides a method for handling advertisement insertion in a reception environment in which media data and the like cannot be received through a broadband channel. This will be described below.

According to an embodiment of the present invention (Example 1-1), advertisement insertion may be performed using xlink, which is an attribute of the Period element in the MPD. More specifically, when the broadband network is connected, the receiver can parse the MPD, access the URL indicated by the xlink attribute, and receive in real time the Period element about the advertisement that needs to be inserted or replaced via the xlink resolver. And receive segments that contain the advertisement.

According to an embodiment of the present invention, audio / video data in the form of ISOBMFF may be transmitted through a broadcasting network. In this case, in order for the DASH client to receive the MPD and the segment transmitted through the broadcasting network, the receiver may have an internal server. In this case, the URL indicated by the xlink may be mapped to a period transmitted to the broadcasting network, and since each period describes AD segments of the targeted AD, the number of periods exists as many as the number of individual target advertisements. can do. Here, the xlink URL may include a local host ("127.0.0.1" or "localhost") that points to an internal server, which is mapped to Period for the advertisement segment to be played. According to an embodiment of the present invention, the receiver may select a period to be played using information of a parameter of the xlink URL (tag = value pair after "?" Of the URL). For example, location information may include zip code in the xlink URL. Each period transmitted to the broadcasting network includes zip code information, so that a period can be selected according to a user destination of the receiver. As another example, when the receiver fails to receive a period corresponding to an advertisement to be played and an advertisement segment, information about default AD segments to be displayed by the receiver may be included in the xlink URL. When the receiver parses an xlink for inserting an advertisement, the receiver may access a designated path in a local host and receive a period related to the advertisement. In addition, the advertisement insertion may be performed at an appropriate time using a period relating to the advertisement. In this case, if the broadband network is not supported, the advertisement segment should be received in advance through the broadcasting network and stored in the internal server. According to an embodiment of the present invention, when a plurality of advertisements are simultaneously delivered to the receiver, the broadcasting system may include an AD decision module for selecting a specific advertisement.

This figure illustrates the configuration of an MPD including an xlink attribute for advertisement insertion. According to one embodiment shown in this figure, the xlink URL is "http://127.0.0.1/ad_insertion?time=XXX&ud=YYY" where 127.0.0.1 represents the local host and time = XXX & ud = YYY is a parameter. Indicates. The receiver may select a period corresponding to time = XXX and ud (user destination) = YYY for inserting an advertisement.

When the receiver according to an embodiment of the present invention does not receive a period for inserting an advertisement from a URL indicated by an xlink attribute of a period, the receiver may present an advertisement designated as a default. However, when a period for inserting an advertisement can be delivered, a newly delivered advertisement can be presented instead of a default advertisement.

The embodiment shown in this figure illustrates a process of performing advertisement insertion when both the MPD and the advertisement content are transmitted through the broadcasting network. This process will be described below.

1. The broadcaster transmits the MPD and the main content segment related to the main content to the receiver. 2. The receiver delivers the received MPD and segment to the internal server. 3. DASH Client requests MPD to internal server. 4. Internal Server delivers MPD to Dash Client. 5. The Dash client parses the delivered MPD. 6. The Dash client requests the Ad (AD) Period to the xlink URL in the MPD. Here, the xlink URL points to a specific address in the internal server. 7. When the advertisement period is received through the Xlink URL, the Dash client replaces the period with the received advertisement period. If there is no advertisement period, the Dash client maintains the existing period to complete the MPD parsing. 8. The Dash client makes a request to the internal server for the main content segment based on the parsed MPD. 9. The Dash client receives the segment from the internal server. 10. The internal server receives an advertisement segment to be inserted through a broadcast channel. 11. The Dash client requests the ad segment of the replaced advertising period via xlink. 12. The Dash client receives and plays the ad segment.

According to another embodiment of the present invention (Embodiment 1-2), the period and the advertisement segment for the advertisement insertion received through the xlink resolver may be stored in a separate place without being stored in the internal server. At this time, the space to be stored may be a physical space (hard disk) or may be a memory area. This-, the period for the received advertisement insertion and the URL of the advertisement segment can be delivered via signaling and can be mapped to the signaled URI. The above-described URI may be expressed in various ways. For example, the Period location for AD insertion: atsc3: // ad_insertion / location / 1, and the AD segment location for AD insertion: atsc3: // ad_insertion / segments / X. It can be expressed as mp4, where X is a number. Except for the above description, the advertisement insertion process is the same as the above-described embodiment (first embodiment). Furthermore, only the location of Period for inserting an advertisement is separately designated, and the advertisement segment is stored in an internal server so that the URL of the segment can be a local host base. Alternatively, the period for inserting the advertisement may be stored in an internal server, and only the location of the advertisement segment may be separately designated.

According to another embodiment of the present invention (Embodiment 1-3), the broadcast system may perform advertisement insertion using an inband event in the DASH segment. At this time, the configuration of an emsg box (event message box) for an inband event is as follows.

Emsg box {

string scheme_id_uri;

string value;

unsigned integer timescale;

unsigned integer presentation_time_delta;

unsigned integer event_duration

unsigned integer id;

unsigned integer message_data [];

}

Scheme_id_uri according to an embodiment of the present invention is used to distinguish inband events for advertisement insertion. (For example, scheme_id_uri = "urn: atsc: event: ad_insertion") According to an embodiment of the present invention, when an inband event is delivered using scheme_id_uri, an advertisement insertion to be delivered through an xlink resolver is transmitted to a message_data field. Period can be inserted and delivered. When the Dash client receives the inband event for inserting the advertisement, the Dash client may parse the Period for inserting the advertisement included in the message_data field to perform the insertion of the advertisement. In detail, since the DASH client may parse an inband event at the time of parsing the media segment, the event may be delivered in advance than when the advertisement is inserted. Since the start time of the corresponding period is specified in the period for inserting the advertisement, the DASH client may receive the inband event in advance and perform the insertion of the advertisement.

According to another embodiment of the present invention (Embodiment 1-4), when using the inband event for inserting an advertisement, without receiving a period for inserting an advertisement, the time at which insertion should occur and the URL of the ad segment should be performed. Can be received by inband event. At this time, the scheme_id_uri field included in the emsg box for the inband event indicates "urn: atsc: event: ad_insertion", the presentation_time_delta field indicates the time to download the ad segment, the duration field indicates the durationl of the ad segment, and message_data Field represents the URL of the ad segment. In this case, the URL of the advertisement segment may have the form of an xlink URI (or URL) of the first embodiment described above or a URI (or URL) of the second embodiment described above. According to an embodiment of the present invention, the DASH client may receive an inband event and obtain the URL of the advertisement segment delivered through the message_data field at that time with reference to the presentation_time_delta field and access the corresponding URL to perform advertisement insertion. . In this case, the URL of the advertisement segment delivered through the message_data field may be delivered in the form of templete, and may be delivered in the form of the URL of a specific advertisement segment. In the former case, the DASH client may calculate the transferred templete and subsequently make a request for segment download. In the latter case, since the URL of each advertisement segment needs to be inserted and transmitted in an inband event, an event for inserting an advertisement may occur several times. In this case, different ADs may be distinguished by using the same id of the emsg box to indicate that several events refer to one advertisement.

According to another embodiment of the present invention, a method of performing advertisement insertion when MPD is transmitted to a broadcasting network and AD content is transmitted to a broadband network will be described below.

When the receiver supports both the broadcasting network and the broadband network, the receiver may receive the main content and the MPD associated with the broadcasting network and the advertisement content through the broadband network.

According to an embodiment of the present invention (Embodiment 2-1), when the MPD is received through the broadcasting network and the advertisement content is received through the broadband network, the URL of the xlink indicates a local host (127.0.0.1) indicating an internal server. Can be. The xlink resolver according to an embodiment of the present invention may exist inside the receiver, and the receiver parses the xlink for inserting the advertisement in the MPD, accesses the designated path in the local host, and acquires a period related to the advertisement. Ad insertion can be performed at this point. At this time, the advertisement segment described inside the period (period for inserting the advertisement) with respect to the advertisement may be transmitted through broadband.

According to another embodiment of the present invention (Example 2-2), the period and the advertisement segment for the advertisement insertion received through the xlink resolver may be stored in a separate place without being stored in the internal server. At this time, the space to be stored may be a physical space (hard disk) or may be a memory area. This-, the period for the received advertisement insertion and the URL of the advertisement segment can be delivered via signaling and can be mapped to the signaled URI. The above-described URI may be expressed in various ways. For example, the period location for AD insertion: atsc3: // ad_insertion / location / 1, and the AD segment location for AD insertion may indicate a broadband URL.

According to another embodiment of the present invention (Embodiment 2-3), the broadcasting system may perform advertisement insertion using an inband event in the DASH segment. At this time, the configuration of an emsg box (event message box) for an inband event is as described above. Scheme_id_uri according to an embodiment of the present invention is used to distinguish inband events for advertisement insertion. (For example, scheme_id_uri = "urn: atsc: event: ad_insertion") According to an embodiment of the present invention, when an inband event is delivered using scheme_id_uri, an advertisement insertion to be delivered through an xlink resolver is transmitted to a message_data field. Period can be inserted and delivered. When the Dash client receives an inband event for inserting an advertisement, the Dash client parses a period for inserting an advertisement included in a message_data field, downloads an advertisement segment through a broadband network, and performs insertion. In detail, since the DASH client may parse an inband event at the time of parsing the media segment, the event may be delivered in advance than when the advertisement is inserted.

According to another embodiment of the present invention (Embodiment 2-4), the same operation as in the above-described Embodiment 1-4 except that the URL of the advertisement segment transmitted through the message_data field indicates a broadband URL. Ad insertion can be performed.

According to another embodiment of the present invention, AD content is previously received by the receiver through the NRT, and the following describes a method of performing advertisement insertion when the MPD indicates a download location of the NRT file. .

According to an embodiment of the present invention, both the advertisement content and the MPD may be transmitted through the broadcasting network, and the advertisement content may be received and downloaded in advance through the NRT to perform advertisement insertion. According to this embodiment, the broadcast system can efficiently use the effective bandwidth. For example, this embodiment can be used to efficiently use bandwidth when both main content and advertisement are provided in UHD in a next generation hybrid broadcasting system. The advertisement insertion process according to this embodiment is the same as the other embodiments described above, but in this embodiment the URL of the advertisement segment points to the NRT download location.

The broadcast system according to an embodiment of the present invention may provide a method for performing target AD insertion based on the above-described advertisement insertion method. Target advertisement insertion according to an embodiment of the present invention is an extended advertisement insertion method, which indicates a service for displaying a specific advertisement in a specific receiver. According to this embodiment, a plurality of advertisements are received at the receiver and each advertisement may have conditions indicating a target to which the advertisement is to be presented. The receiver receiving the plurality of advertisements may select and present an advertisement that matches a target condition among the advertisements.

In order to insert a target advertisement according to an embodiment of the present invention, a method of receiving a plurality of advertisements having the same presentation time and a method of selecting an advertisement that meets a target condition among the plurality of received advertisements are required.

For the target advertisement service according to an embodiment of the present invention, the receiver should be able to receive a plurality of advertisements having the same presentation time. According to an embodiment of the present invention, a plurality of advertisements having the same presentation time may be received using xlink. In detail, the xlink may include information for obtaining periods for a plurality of advertisements. Accordingly, the receiver may receive a plurality of advertisement periods by resolving xlink.

The receiver according to an embodiment of the present invention may select an advertisement to be presented from among a plurality of received advertisements. For this purpose, a condition for determining which device or user is suitable for a particular advertisement is necessary. A receiver supporting a next generation hybrid broadcasting system according to an embodiment of the present invention may include a separate personalization module in order to provide a personalization service, and through the module, the receiver may provide user's personalization information and preference. Information and the like. The transmission system according to an embodiment of the present invention may deliver personalization information or preference information conditions suitable for a target to which each advertisement is to be presented when transmitting the target advertisement to the receiver. After receiving the conditions, the receiver may communicate with the personalization module to finally select the appropriate advertisement to present at the receiver and present it to the user. According to an embodiment of the present invention, the conditions for the target advertisement service may be inserted and transmitted in the advertisement content (eg, inserted in a period for the target advertisement), and a separate targeting signaling table may be generated. Can be sent through. In addition, when an advertisement is selected, the personalization module in the receiver may access an external server to receive a condition for the target advertisement service, and may indicate information indicating which advertisement to select, or not the advertisement itself to select. May be received.

Ad insertion according to an embodiment of the present invention may include a live case and a Vod case. For live cases, accessible advertisements may be sent in broadcast streaming, broadband streaming, broadcast NRT, and / or broadband NRT, and ad break location may be predetermined or known a few seconds before the advertisement is presented. And the ad break duration can be known when the ad break location is known. In the case of a Vod case, the advertisement time location can be predetermined and the advertisement time duration is unknown.

Ad insertion according to an embodiment of the present invention may include an app-based model and a server-based model.

In the app-based model, apps can interact with the ad server. If the Dash client supports it in the form of MSE (Media Source Extensions), then a native Dash client may not be needed. At this point, the DASH event can be triggered in a browser that supports MSE. The app can start / stop / restart the DASH client. In this model, multiple DASH clients may be required, and communication with the ad decision service can be made within the app.

Server-based models can use the built-in DASH tool. In this model, one DASH client can be used. In this model, communication with the ad decision service can take place at the server. If the advertisement time location is unknown, MPD update (minimumUpdatePeriod or MPD Validity Expiration Event) may be used. The DASH client can request the advertisement after resolving the xlink.

The app-based model can reuse existing workflows in DASH. The client app may include an ad splicer module and / or a DASH client module. At this time, the advertisement splicer module may communicate with the advertisement server when a cue message is delivered. If the client app does not include a DASH client module, the native DASH client can be run within that app. DASH events can be used to send cue messages to client apps and can be included in segments (inband) or in event streams (MPDs). At this time, the cue may indicate a parameter and time of an upcoming advertisement time. The queue may indicate a transition to an advertisement time, a transition to the next advertisement within the advertisement time and / or a transition from the advertisement time to the main content.

In this diagram illustrating an app driven model according to an embodiment of the present invention, the client app includes an ad splicer module and a player, the ad splicer module receiving content and cues and The advertisement server may receive the corresponding advertisement and deliver the content and the received advertisement to the player.

In the app based model according to an embodiment of the present invention, the app may communicate with an ad decision server and obtain a separate MPD for an embedded advertisement. The app can stop the presentation of the main content and start the presentation of the inserted ad at the splice point. After presenting the ad, the app can restart the main content. The app based model can splicing advertisements with a single decoder.

In an app based model according to an embodiment of the present invention, an SCTE 35 event may be used. At this time, a cue message may be converted into a DASH event (inband 'emsg' box or an MPD event), and the cue parameter may be converted to Period @ xlink: href.

The left figure of this figure shows the configuration of the MPD when the SCTE 35 queue message is included and delivered in the event element of the MPD. Referring to this figure, the advertisement plays at 600.6 seconds after the start of the period and lasts 60 seconds.

The figures on the right of this figure show the configuration of the emsg box when the SCTE 35 queue message is included and delivered in the emsg box. The figure on the upper right shows the case where the queue message is included in binary form, and the figure on the lower right shows the case where the queue message is included in XML format. In this figure, scheme_id_uri = "urn: scte: scte35: 2013: xml" indicates that the inband event is an SCTE 35 queue message. Referring to this figure, the advertisement lasts from T + 6 to T + 66, where T represents the earliest presentation time of the segment delivering the event.

The system of the app based model according to an embodiment of the present invention follows a linear workflow (live workflow). An app based model system can handle live content and pre-recorded content. The app-based model system can perform the conversion process in the packager upon receipt of a queue message. Cue messages can be delivered to emsg.message_data [] in inband user-defined DASH events. The app based model system can support alternative implementations used in conjunction with the server based model system. App based model system can perform the conversion process in the MPD generator (MPD generator) and can generate a new MPD for client restoration. At this time, the MPD may include a remote Period for the SCTE 35 event and / or server based model. The app-based model system can perform the conversion process in the packager upon receipt of a queue message. At this time, an MPD validity expiration event may be inserted.

App based model system according to an embodiment of the present invention is an ad decision server (ad decision server), MPD generator (MPD generator), packager (Origin), DASH client (DASH client, ads) ), The main content DASH client (DASH client, main content) and / or App (App). At this time, the advertisement DASH client (DASH client, ads), the main content DASH client (DASH client, main content) and / or App (App) may be included in the receiver, other configuration may be located outside the receiver. The MPD generator generates a MPD by receiving a queue message. The packager receives the content and queue messages and sends the content and events to the origin. The packager processes the content and media segments so that they can be properly consumed by the DASH client. The origin includes all media segments described in the MPD and sends the media segments to the DASH client through the CDN node. The advertisement DASH client receives the MPD and the advertisement segment for the advertisement and delivers it to the app. The main content DASH client receives the MPD and main content segment for the main content and delivers it to the app. The ad management module included in the app communicates with an external ad decision server using the received MPD and segment. At this time, the information according to the SCTE 130 / VAST may come and go. The app passes the MPD URL for the determined advertisement to the advertisement DASH client and the main content DASH client. In addition, the advertisement DASH client and the main content DASH client can present the main content and the corresponding advertisement at an appropriate time.

The system of the server-based model according to an embodiment of the present invention may have one client. The system can use the built-in DASH tool. In this system an advertisement is represented as a Period and can be resolved by xlink (Period @ xlink: href). Remote periods can be used as queues, and cookies can be used. In this system, MPD updates can be used for ad insertion.

As a DASH tool used in a system of a server-based model according to an embodiment of the present invention, a remote element represents an element that is not described in the MPD and is referenced by the MPD. At this time, the HTTP-URL may be referenced using xlink in the MPD. The remote element may have @xlink: href and / or @xlink: actuate. @xlink: href contains the URL for the complete element. If this attribute has urn: mpeg: dash: resolve-to-zero: 2013, this attribute can be deleted. Information delivered from the DASH client to the xlink resolver (PeriodStrat, cue message, etc.) may be encoded and included in the URL of this attribute. @xlink: actuate describes the resolution model. The value of this attribute onLoad indicates that a resolution is required immediately at the time of parsing the MPD, and onRequest indicates that a deferred resolution is required at the time the XML parser accesses the remote element. A resolution process according to an embodiment of the present invention may issue an HTTP GET requesting a URL included in @xlink: href, and the obtained element may include an @xlink: href attribute for repeated resolution. have.

As a DASH tool used in a server-based model system according to an embodiment of the present invention, Period is a unit that divides a DASH media presentation on a time basis. PeriodStart is described using @start and can be calculated indirectly using the @duration of the previous period. Period duration can be calculated as PeriodStart (i + 1)-PeriodStrat (i). If the media duration of period i is slightly longer than the period itself, then the client can schedule the start of the media presentation for period i + 1 to PeriodStart (i + 1). DASH can support seamless transitions between periods using the tools defined in 23009-1: 2014 / Amd.3. AsserIdentifier may identify an asset to which a given period belongs. This allows the period to be labeled. The DASH event may be in the MPD or inband. If present in inband, the emsg box may exist before the moof box for faster event detection. The type of DASH event may include MPD Validity Expiration, MPD Patch and / or MPD Update.

Seamless transitions between periods according to one embodiment of the present invention are defined in 23009-1: 2014 / Amd.3. According to an embodiment of the present invention, two adaptation sets in one MPD may be period-continutous when the following conditions are satisfied. 1. If two adaptation sets have the same Asset Identifier for all periods (Period / AsserIdentifier) and both adaptation sets have the same @id value (AdaptationSet @ id). 2. SegmentBase @ presentationTimeOffset + duration of all Representations = satisfies @presentationTimeOffset of the next period. And / or 3. If the representations in both adaptation sets have the same @id value, the representations have the same Initialization segment. According to an embodiment of the present invention, the period-continuous between the adaptation sets is @scheme_id_URI: urn: mpeg: dash: period_continuity: 2014 of the AdaptationSet / SupplementalProperty element, and @value: @id of Period and / or the AdaptationSet / SupplementalProperty element. It may be signaled using AdaptationSet @ id having the same value in both periods.

As the DASH tool used in the system of the server-based model according to an embodiment of the present invention, the MPD update may be performed by version information provided by MPD @ publishTime. The MPD may be updated periodically by MPD @ minimumUpdatePeriod and may be triggered by the DASH event. The period for the advertisement may be inserted by on-the-fly. Session Information may be needed to know fine-grain targeting and client / server identity. The simplest way to do this is to use cookies. For tracking and reporting, server side logging of HTTP GET requests can be used. Consideration of the CDN note structure may be necessary. Different CDN notes may be used and aggregation may be needed. Tracking and reporting may be performed using a communication and / or DASH callback event with an existing tracking server (IAB VAST).

The system of the server based model according to an embodiment of the present invention may support single client native advertisement insertion. At this time, a single ad represents a single period element. The period for the content includes an explicit start time (Period @ strat), and the client can start playing the next period at the time described in the MPD. The remote period element may be resolved into one or more period elements. If no ad break has occurred, the resolved period has a duration of zero and does not have an adaptation set. MPD updates may be made by MPD Validity Expiration events, MPD Patch events and / or full-fledged MPD updates. According to the single client native ad insertion method, a live in-band queue can simply be mapped to a DASH event. One single queue may be mapped to one MPD Validity expiration event. The DASH client can request a new MPD, resolve the xlink, and download the ad segment. Additional information passed to the app may be opaque to the DASH client. MPD events can put ambiguous payloads into the MPD. In the linear workflow of single client native ad insertion, a system of sub-based model can handle live content and pre-recorded content. Referring to the queue interpretation by the MPD generator, splice_time () of the queue message may be interpreted as Period @ start, and the queue parameter may be interpreted as Period @ xlink: href. For an immediate ad decision, when a new MPD is requested and the server recognizes the client, the MPD generator may contact the ad decision server to locate the ad period without xlink. For stateful cue translation, when a new MPD is requested, the MPD generator can put a targeting parameter (eg zipcode = 60069) into the xlink URL. The cue interpretation by the package will be described below. Upon receipt of the cue message, the emsg may be inserted into the first possible segment along with the MPD Validity expiration event. Splice_time () can be interpreted as the media timeline to identify the last segment before the splice point. The packager may end the segment at the splice point. In On Demand Workflow of single client native ad insertion, the cue location and break duration can be known in advance.

Referring to this figure, the MPD is a link to the period for the advertisement to be inserted (<Period start = "PT60.6S" xlink: href = "https://adserv.com/avail.mpd?time=5405400" xlink: actuate = "onRequest" id = "A1">, <Period start = "PT60.6S" xlink: href = "https://adserv.com/avail.mpd?u=YYY" xlink: actuate = "onRequest" id Has = "A2">

Referring to this figure, AssetIdentifier pointing to Period M1 in MPD is schemeIdUri = "urn: org: dashif: asset-id: 2014" and value = "md: cid: EIDR: 10.5240% 2f0FFB-02CD-126E-8092-1E49 -W ". At this time, @schemeIdUri: "urn: org: dashif: asset-id: 2014" can be used for DASH-IF extension for advertisement insertion, and @value: MovieLabs ContentID URN can be used for EIDR and / or advertisement for content. It can represent the Ad-ID.

The system of the server-based model according to an embodiment of the present invention includes a cloud and / or a receiver, and the cloud includes an ad decision server, an MPD generator, and a packager. And / or CDN / Origin, and the receiver comprises a Media Engine and / or a DASH Access Client. The packager receives content and queue messages and forwards content and in-band events to the CDN / origin. The CDN / origin sends the segment to the DASH client. The MPD generator receives the queue message, sends the MPD to the DASH client, and includes an xlink resolver. The DASH client receives the MPD and segment and sends the xlink to the xlink resolver. The xlink resolver communicates with the ad decision server to send a period for the determined ad to the DASH client. The DASH client delivers the segment and timing information to the media engine using the period for the received advertisement. The media engine presents the received segment at the appropriate time.

According to an embodiment of the present invention, three advertisement events (Event # 1, Event # 2, Event # 3) are inserted in Period 0 having a media time of 0 to 42 in the MPD according to the App Based Model. . That is, three advertisements are included as respective events in one period. In contrast, in the MPD according to the server-based model, a total of five periods exist within a media time of 0 to 42, and Period 0, Period 2, and Period 4 represent advertisements. In other words, the advertisement and the actual media constitute each period.

According to one embodiment of the invention, advertisement insertion for ATSC 3.0 may use a server-based model. In case of static ad insertion, when using broadband network (OTT), all advertising decisions can be made during MPD generation or xlink resolution and when using broadcast network (OTA) over the air Advertisement determination may be performed by the xlink resolver of the receiver.

In the case of just-in-time ad insertion, when using a broadband network, the MPD may be updated with a new advertisement period in real time. At this time, the DASH event indicates an MPD validity expiration event. The remote period may be resolved with xlink. At this time, the resolution may be started at the playing time rather than the MPD parsing time. In the case of using the broadcasting network, as in the case of using the broadband network, the MPD update is performed by the DASH event and after the new MPD is received, the advertisement decision may be performed by the xlink resolver of the receiver.

The broadcast system according to an embodiment of the present invention includes a receiving device and / or a cloud. The cloud includes an ad decision server, an MPD generator, a packager, and / or a CDN / Origin. The receiving device includes a DASH client (DASH Access Client), an HTTP proxy server (HTTP Proxy), an ad decision module (filtering engine), an S-TSID processor and / or a media engine. do. The HTTP proxy server includes an xlink resolver, an NRT ad cache (NRT), a ROUTE receiver, a demographic processor and / or an RT cache. The description of the advertisement insertion process according to this embodiment is replaced with the description of the advertisement insertion process when the advertisement is transmitted through the broadcasting network through NRT broadcasting in a server-based model broadcasting system linked to an app in a receiver to be described later. At this time, in this embodiment, unlike the embodiment described below, the advertisement determination module is located in the receiving device, not the app. At this time, the function performed by the advertisement determination module located in the receiver device is the same as the case where it is located in the app.

According to an embodiment of the present invention, the xlink resolver may exist in the receiver, and the xlink may be resolved into one file transmitted to the broadcasting network. The xlink in the advertising period may be replaced with one or more periods for the target advertisement. This embodiment may be useful when the receiver is not connected to the broadband network.

According to one embodiment of the invention, the xlink: href attribute may provide a URL to the xlink resolver. xlink: href has the following syntax: xlinkhref: <domain name part> / <directory path> [? <parameters>]. <domain name part> / <directory path> has the same meaning as content-location of files transmitted to the broadcasting network. That is, if xlink is to be resolved to a period, xlink: href is identical to the content-location of the advertisement period except for the following parameter. Parameters are in the form of key = value pairs, separated by &. According to an embodiment of the present invention, to indicate local resolution, one of the parameters of xlink: href may have fc as a key part and a pre-registered question id as a value part. . In this case, fc represents a filtering criterion, and the pre-registered question id may mean a PDI question id registered by an external agency such as ATSC, for example, "atsc.org/PDIQ/ gender "," atsc.org/PDIQ/ZIPcode ", and the like. For example, xlink: href = indicates that xlink should be resolved based on zipcode.

According to one embodiment of the invention, the receiver may download the NRT advertising content as soon as it receives the SLS. In this case, SLS means service layer signaling and includes an S-TSID including a filtering criterion. The receiver may open an LCT session in which a component having a filtering criterion that matches a condition stored in the receiver is transmitted. For example, if the filtering criterion is for a region in which the viewer lives (eg, a zip code), the receiver may establish an LCT session in which a component having a filtering criterion with the same zip code in the receiver is transmitted. Can open

According to one embodiment of the invention, the receiver may download the NRT advertising content as soon as it resolves the xlink. The DASH client can make a request with the xlink resolver in the receiver. The xlink resolver can pass filtering information (fc, zipcode) to the filtering engine. The filtering engine can return the zip code stored in the receiver to the xlink resolver. The xlink resolver may open an LCT session that matches the filtering criteria among the LCT sessions described in the S-TSID. The xlink resolver returns the same period as the period indicated by onRequest in the xlink's actuate attribute set. This is to give enough time for the advertisement content to be downloaded at the receiver before the splice point of the advertisement. According to an embodiment of the present invention, the app of the receiver may pre-download the necessary NRT advertisement content by the advertisement determination module, and the downloaded NRT advertisement content file is not deleted in the receiver and upon the next xlink resolving. Can be used again.

The broadcast system according to an embodiment of the present invention has the same structure except that an ad cache is included instead of an NRT ad cache (NRT) in the broadcast system when the above-mentioned advertisement is transmitted through NRT broadcasting. . Description of each component of the broadcast system according to this embodiment is replaced with the description of the above-described configuration in the previous figure.

The filtering criterion according to one embodiment of the present invention has at least one QxA Criterion, and at least one Criterion has a form of QIA, QBA, QSA, QTA or QAA depending on the form of the value. QxA criterion represents a filter criterion corresponding to a PDI question. QxA criterion includes @id and / or criterionvalue. criterionvalue may include @extent and / or @lang. @id represents an identifier for a question in the PDI table. That is, it indicates the ID of the question for filtering. criterionvalue represents a value depending on the type of question. The absence of @extent indicates that criterionvalue is a specific integer value, and that criterionvalue is an integer value within a certain range. @lang indicates the language of the text when citerionvalue is a text type.

According to an embodiment of the present invention, the filtering criteria may be included in the filtering criteria element <FilteringCriteria>. The filtering criteria element may be located in the S-TSID and may be expressed as follows.

According to one embodiment of the present invention, when all data (advertising period, advertisement content, etc.) described in the EFDT have the same filtering criteria, the above-described filtering criterion element may be defined as a lower element of the EFDT element. According to this embodiment, data related to a specific advertisement (period, content, etc.) may be transmitted in one LCT session. For example, files with a value of CriterionValue 60069 are sent to an LCT session with @ tsi = 123, and files with a value of CriterionValue 60068 are sent to an LCT session with @ tsi = 345. (See left drawing)

According to an embodiment of the present invention, in the case of having different filtering criteria for each file, the above-described filtering criteria element may be defined as a lower element of the file element in the EFDT element. This embodiment is for finding the transmission location of a particular file and can be used to get a period for a target advertisement. For example, a file with a value of CriterionValue 60069 is sent to an object with @ TOI = 10 in an LCT session with @ tsi = xxx. (See right drawing)

According to an embodiment of the present invention, different advertisements may be played according to the zip code of the filtering criteria. Specifically, a receiver with zip code 60069 plays an advertisement with @ tsi = 123 and a receiver with zip code 60068 plays an advertisement with @ tsi = 345.

According to an embodiment of the present invention, (1) after the channel switching, the filtering engine uses the information included in the filtering criterion element included in the zip code (= 60069) and the S-TSID of the receiver and tsi = Open an LCT session of 123 and receive the advertisement content included in the LCT session. At this time, the received advertisement content is stored in the NRT advertisement cache. Specifically, the filtering engine parses the zip code included in the filtering criterion element in the S-TSID, and opens an LCT session for transmitting a file or files including the filtering criterion element having the same zip code as that of the receiver. Ad content can be received. (2) The DASH client requests an xlink resolution using the xlink: acutate value to obtain an ad period to prepare for advertisement playback. At this time, the xlink: acutate value may include information about the location of the xlink resolver for obtaining the corresponding advertisement period. (3) The xlink resolver may determine that the filtering criteria is a zip code by checking the filtering parameter added to the xlink url (xlink: href), and may receive information about the zip code of the receiver from the filtering engine. (4) The xlink resolver reads the advertisement period received as an NRT file in an LCT session with tsi = 123. At this time, Content-Location = of period. (5) The Xlink resolver returns an advertisement period to the DASH client.

According to an embodiment of the present invention, the content-location of the advertisement period has the same value as that of "fc = ZIPCode" of xlink: href by "ZIPCode = xxxx". The ZIPCode is a reserved name, and the receiver can select an advertisement period having the same zip code as the zip code stored in the receiver. For example, the ad period xlink: href is "http://www.abc.com/ad.period?fc=ZIPCode", and the content-location of both ad periods is "http://www.abc.com /ad.period?ZIPCode=60069 "and" ", if the receiver's zip code is 60069, then the receiver may select an advertising period with a content-location.

The broadcast system according to an embodiment of the present invention includes a receiving device, an app, and / or a cloud. The cloud includes an ad decision server, an MPD generator, a packager, and / or a CDN / Origin. The receiving device includes a DASH Access Client, an HTTP Proxy Server, a Filtering Engine, an S-TSID Processor, and / or a Media Engine. The HTTP proxy server includes an xlink resolver, an NRT ad cache (NRT) and / or an RT cache. The app includes an ad decision module.

According to an embodiment of the present invention, the app may be included inside the receiving device or may exist outside the receiving device.

According to an embodiment of the present invention, the advertisement may be transmitted to the broadband network and may be transmitted to the broadcasting network. When the advertisement is transmitted to the broadcasting network, the advertising period, the initialization segment and / or the media segment may be transmitted to the broadcasting network, and at this time, the advertising period may be transmitted to the broadband network.

According to an embodiment of the present invention, the advertisement determination module included in the app may dynamically change a path in which an advertisement is transmitted. For example, although the advertisement is originally transmitted to the broadcasting network, the advertisement may be changed to an advertisement transmitted to the broadband network at the time of xlink resolving.

According to an embodiment of the present invention, the advertisement determination module included in the app reads the advertisement period from the NRT advertisement cache and delivers the read advertisement period to the xlink resolver in the receiver.

Detailed description thereof will be described later in the drawings.

In the broadcast system of a server-based model linked to an app in a receiver according to an embodiment of the present invention, when an advertisement is transmitted through a broadcasting network through NRT broadcasting, the receiving device includes a filtering engine, an xlink resolver (local xlink resolver), and a demographic. Information processing, NRT advertisement cache, RT cache, ROUTE receiver, DASH client, media engine and / or app launcher. The app then includes an ad decision module.

Referring to this figure, the advertisement insertion process according to an embodiment of the present invention will be described below. 1. The user selects a service and the receiving device starts receiving a ROUTE packet. 2. The DASH client acquires the MPD and sends it to the RT cache. 3. The DASH client acquires the segment and sends it to the RT cache. 4. The DASH client passes the segment to the media engine. 5. The ROUTE receiver receives app signaling such as AST and passes it to the app launcher. 6. App Launcher downloads and launches the application. 7. The ad decision module included in the app reads demographic information (eg, zip code) of the receiver or user. 8. The advertisement decision module registers an event listener to handle the advertisement decision request. 9. The advertisement determination module may set a filter of the filtering engine. (Eg, zipcode = 60069) 10. The filtering engine may allow the ROUTE receiver to download NRT content having the same filtering criteria as the filtering criteria of the receiver by referring to the S-TSID. 11. The ROUTE receiver downloads the NRT content and stores it in the NRT advertisement cache. 12. The DASH client requests xlink resolution with the xlink resolver. 13. The xlink resolver invokes an event listener. 14. The advertisement determination module checks whether the advertisement NRT has been completely downloaded into the NRT advertisement cache and reads the advertisement period. 15. The ad decision module passes the read ad period to the xlink resolver. 16. The xlink resolver forwards the delivered advertising period to the DASH client. 17. The DASH client obtains an ad segment from the NRT ad cache. 18. The DASH client delivers the ad segment to the media engine.

According to another embodiment of the present invention, the advertisement determination module included in the app delivers the URL of the advertisement period to the xlink resolver in the receiver.

Detailed description thereof will be described later in the drawings.

Referring to this figure, the advertisement insertion process according to an embodiment of the present invention will be described below. 1. The user selects a service and the receiving device starts receiving a ROUTE packet. 2. The DASH client acquires the MPD and sends it to the RT cache. 3. The DASH client acquires the segment and sends it to the RT cache. 4. The DASH client passes the segment to the media engine. 5. The ROUTE receiver receives app signaling such as AST and passes it to the app launcher. 6. App Launcher downloads and launches the application. 7. The ad decision module included in the app reads demographic information (eg, zip code) of the receiver or user. 8. The advertisement decision module registers an event listener to handle the advertisement decision request. 9. The advertisement determination module may set a filter of the filtering engine. (Eg, zipcode = 60069) 10. The filtering engine may allow the ROUTE receiver to download NRT content having the same filtering criteria as the filtering criteria of the receiver by referring to the S-TSID. 11. The ROUTE receiver downloads the NRT content and stores it in the NRT advertisement cache. 12. The DASH client requests xlink resolution with the xlink resolver. 13. The xlink resolver invokes an event listener. 14. The advertisement determination module checks whether the advertisement NRT has been completely downloaded into the NRT advertisement cache. 15. The advertisement determination module passes the URL of the advertisement period to the xlink resolver. 16. The xlink resolver obtains an advertisement period from the NRT advertisement cache using the received URL. 17. The xlink resolver forwards the obtained advertising period to the DASH client. 18. The DASH client obtains an ad segment from the NRT ad cache. 19. The DASH client delivers the ad segment to the media engine.

Detailed description thereof will be described later in the drawings.

In the broadcast system of the server-based model linked to the app in the receiver according to an embodiment of the present invention, when an advertisement is transmitted through a broadband network, the receiving device includes a filtering engine, an xlink resolver (local xlink resolver), and a demographic info processor. (demographic info), NRT ad cache, RT cache, ROUTE receiver, DASH client, media engine and / or app launcher. The app then includes an ad decision module. The server includes an advertisement server.

Referring to this figure, the advertisement insertion process according to an embodiment of the present invention will be described below. 1. The user selects a service and the receiving device starts receiving a ROUTE packet. 2. The DASH client acquires the MPD and sends it to the RT cache. 3. The DASH client acquires the segment and sends it to the RT cache. 4. The DASH client passes the segment to the media engine. 5. The ROUTE receiver receives app signaling such as AST and passes it to the app launcher. 6. App Launcher downloads and launches the application. 7. The ad decision module included in the app reads demographic information (eg, zip code, cookie, etc.) of the receiver or user. 8. The advertisement decision module registers an event listener to handle the advertisement decision request. 9. The DASH client requests xlink resolution with the xlink resolver. 10. The xlink resolver invokes an event listener. 11. The advertisement determining module determines which advertisement to play and obtains an advertisement period from the advertisement server. 12. The advertisement determination module passes the advertisement period to the xlink resolver. 13. The xlink resolver forwards the delivered advertising period to the DASH client. 14. The DASH client obtains an ad segment from the ad server. 15. The DASH client delivers the ad segment to the media engine.

According to an embodiment of the present invention, if there is a personalization system and / or storage that can be referred to when the target advertisement is inserted, the class and / or API (which is used by the app to obtain personalization information of the receiver, etc.) application programming interface) may be defined.

The TargetingFeatureType class according to an embodiment of the present invention has a name property having a string type and / or a value property having a string type. The name property indicates the type of targeting feature. The calue property (for example, zipcode, age, etc.) represents the value of the targeting feature type.

The TargetingFeature class according to an embodiment of the present invention represents a set of TargetingFeatureType classes.

The TargetingFeatures GetTaegetingFeatures (Collection <string>) API according to an embodiment of the present invention delivers a set of stings as an input argument. In this case, the string may mean a name property of each TargetingFeatureType. When the API according to this embodiment is called, it is checked whether there is a targeting feature type that matches the values of the stings delivered to the puncture argument, and if present, a value in the form of TargetingFeatures may be returned with the value.

According to an embodiment of the present invention, the value value may be automatically assigned a value from a receiving device and may be directly assigned a value from a user. For example, if the zipcode of the current receiving device is 60069, if the app wants to know the value for the keyword "zipcode", the app may call the following API.

TargetingFeatures current_targeting_features = GetTargetingFeatures ("Zipcode");

In addition, the app may receive a zipcode value 60069 of the receiver as a return value of the API.

According to another embodiment of the present invention, targeting features may be designated globally unique by a specific organization or standard. In this case, the id property may be used instead of the name property among the properties of the TargetingFeatureType. Alternatively, both the name property and the id property can be used. The id property has an anyURI type and represents an ID of a targeting feature type.

The broadcast system according to an embodiment of the present invention may provide a method for setting an NRT content filter of a receiver in an app.

The void SetTargetingFeatures (TargetingFeatures) API according to an embodiment of the present invention delivers TargetingFeatures containing conditions (TargetingFeatureType) to filter as input arguments. When the API is called, the name property and value property of each TargetFeatureType in TargetingFeatures can be specified as a filtering condition. Thereafter, the filtering engine may filter the signaling information received through the designated filtering condition. For example, TargetingFeatureTypes of TargetingFeatures delivered as input arguments may be configured as follows.

Name: Zipcode / Value: 60069

Name: Gender / Value: M

When the filtering condition is specified as described above, the receiver may receive only the signaling information and the A / V data whose name is zipcode, value is 60069, name is Gender, and value is M among the signaling information received. .

According to an embodiment of the present invention, in the server-based model, the advertisement may be dynamically selected by declaring xlink in the advertisement period of the MPD. If the Xlink resolver and ad decision server are on a remote server, you can dynamically select ads with just your existing DASH tool without an app. However, if the Xlink resolver is inside the receiving device and the ad decision module is in an app running on the receiver, then the xlink information (eg For example, you need to pass an href). To do this, the app can register an event listener to receive ad decision requests from the local xlink resolver.

The broadcast system according to an embodiment of the present invention may declare a class for xlink by defining an API or may deliver individual parameters.

According to an embodiment of the present invention, the void addAdDecisionEventListener (XLinkType xlink) API and the void addAdDecisionEventListener (string href, string show, string type) API are used when the local xlink resolver receives a request for xlink resolution from a DASH client. You can pass xlink information to your app through an Ad Decision Event listener. At this time, each parameter of void addAdDecisionEventListener (string href, string show, string type) API has the same meaning as property of XLinkType.

A receiver according to an embodiment of the present invention may operate as follows. 1. The app registers an event listener for an ad decision event. 2. When the Xlink resolver receives a request from the DASH client, it passes the xlink url through the registered ad decision event listener. 3. The app uses the received xlink url to make ad decisions. 4. The app sends the Xlink resolver the URL of the ad period or ad period that results from the ad decision. 5. The xlink resolver forwards the advertisement period obtained through the received advertisement period or the URL of the advertisement period to the DASH client.

The XLinkType class according to an embodiment of the present invention has an href property, show property, and / or Type property. The href property has an anyURI type and describes a URL for obtaining the advertisement period. The show property is of type string and can have one of the following values: embed, new, replace, other, none. The Type property has a string type and can have one of simple, extended, locator, arc, resource, title, or none.

According to one embodiment of the invention, when the DASH client encounters a period (advertising period) with xlink, it requests the xlink resolver at the remote server to receive a period of content to play. However, if the xlink resolver is in the receiving device, the receiving device should be able to distinguish the content to play. Accordingly, the broadcast system according to an embodiment of the present invention can determine whether to request a period of content from an xlink URL to an xlink resolver in a remote server or to request a period of content from an xlink resolver in a receiving device. .

A broadcast system according to an embodiment of the present invention designates a domain name (or IP address) of @xlink: href as a local host or 127.0.0.1 so that @xlink: href points to an internal xlink resolver address in a receiving device. can do. For example, if @xlink: href directly points to an internal xlink resolver, it can be expressed as xlilnk: href = or xlink: href =. According to this embodiment, the same network function can be used to access the external / internal xlink resolver. In this embodiment, the HTTP server may exist inside the receiving device.

The broadcast system according to another embodiment of the present invention may define a scheme identifier for an internal xlink resolver. If the URN of @xlink: href contains a specific scheme Identifier defined (for example, xllink: href = "urn: atsc: 3.0: resolve-internal-xlink: 2015: xlink / ad /: period") xlink: href points to the internal xlink resolver. According to this embodiment, the DASH client may request a period of content to play with the internal xlink resolver rather than external when it encounters the reserved xlink: href URL.

The broadcast system according to another embodiment of the present invention may designate a protocol of @xlink: href as a specific value. For example, it may be expressed as xlink: href = "InterXlink: // xllink / ad / period? Fc = zipcode".

The broadcast signal reception apparatus L40010 according to an embodiment of the present invention includes a packet receiver L40020 for processing a packet for transmitting media data, advertisement data, and first signaling information, a segment including the media data from the packet, and Segment processing unit (L40030) for obtaining and processing second signaling information describing the reproduction information of the media data, the advertisement insertion information for requesting the reproduction information of the advertisement to be inserted using the advertisement insertion information included in the second signaling information. The processor L40040 and / or an advertisement determination module L40050 may be used to determine an advertisement to be inserted using the personalization information of the user and the condition information included in the first signaling information and to obtain playback information of the advertisement to be inserted. Can be. Here, the first signaling information may include information about the transmission of the media data and the advertisement data. Here, the first signaling information is an S-TSID, the second signaling information is an MPD, the advertisement insertion information is xlink, and the condition information represents a filtering criterion. Here, the packet receiver indicates a ROUTE receiver, a segment processor indicates a DASH client, and an advertisement insertion information processor indicates an xlink resolver.

According to another embodiment of the present invention, the condition information may include filtering criteria information for filtering the media data or the advertisement data and values for the filtering criteria information.

According to another embodiment of the present invention, the first signaling information includes an LS element that describes information about an LCT session for transmitting the media data or the advertisement data as a lower element, and the LS element includes the LCT session. And an EFDT element for describing information applied to all files transmitted to the file, wherein the EFDT element includes a File element for describing information applied to one of the files transmitted to the LCT session, and the condition information. May be included under the EFDT element or the File element.

According to another embodiment of the present invention, the advertisement determining module may be included in an application executed in the broadcast signal receiving apparatus.

According to another embodiment of the present invention, the advertisement data and the reproduction information of the advertisement to be inserted may be transmitted in real time through a broadcasting network.

According to another embodiment of the present invention, the advertisement data and the reproduction information of the advertisement to be inserted may be transmitted to the Internet.

According to another embodiment of the present invention, the advertisement insertion information may include position information of the reproduction information of the advertisement to be inserted and condition information of the advertisement to be inserted.

In a method of receiving a broadcast signal according to an embodiment of the present invention, the method may include processing a packet for transmitting media data, advertisement data, and first signaling information (SL41010), the segment including the media data from the packet, and the media data. Acquiring and processing second signaling information describing playback information (SL41020), requesting playback information of an advertisement to be inserted using advertisement insertion information included in the second signaling information (SL41030), and / or a user Determining an advertisement to be inserted using the personalization information and the condition information included in the first signaling information, and obtaining reproduction information of the advertisement to be inserted (SL41040). Here, the first signaling information may include information about the transmission of the media data and the advertisement data. Here, the first signaling information may include information about the transmission of the media data and the advertisement data. Here, the first signaling information is an S-TSID, the second signaling information is an MPD, the advertisement insertion information is xlink, and the condition information represents a filtering criterion. Here, the packet receiver indicates a ROUTE receiver, a segment processor indicates a DASH client, and an advertisement insertion information processor indicates an xlink resolver.

According to another embodiment of the present invention, the process of determining the advertisement to be inserted and obtaining the reproduction information of the advertisement to be inserted may be performed by an application executed in the broadcast signal receiving apparatus.

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

A packet receiver for processing a packet for transmitting media data, advertisement data, and first signaling information;

Wherein the first signaling information includes information on the transmission of the media data and the advertisement data;

A segment processing unit for obtaining and processing a segment including the media data and second signaling information describing playback information of the media data from the packet;

An advertisement insertion information processor requesting reproduction information of an advertisement to be inserted using advertisement insertion information included in the second signaling information; And

An advertisement determination module that determines an advertisement to be inserted using the personalization information of the user and the condition information included in the first signaling information and obtains reproduction information of the advertisement to be inserted;

Broadcast signal receiving apparatus comprising a.
The method of claim 1,

And the condition information includes a filtering criterion information for filtering the media data or the advertisement data and a value for the filtering criterion information.
The method of claim 1,

The first signaling information includes an LS element that describes information about an LCT session for transmitting the media data or the advertisement data as a lower element, and the LS element includes information applied to all files transmitted to the LCT session. Including an EFDT element for describing, wherein the EFDT element includes a File element for describing information applied to one of the files transmitted to the LCT session,

And the condition information is included under the EFDT element or the File element.
The method of claim 1,

The advertisement determining module is included in an application executed in the broadcast signal receiving apparatus.
The method of claim 1,

And the advertisement data and the reproduction information of the advertisement to be inserted are transmitted in real time through a broadcasting network.
The method of claim 1,

And a broadcast signal receiving apparatus for transmitting the advertisement data and the reproduction information of the advertisement to be inserted.
The method of claim 1,

And the advertisement insertion information includes position information of reproduction information of the advertisement to be inserted and condition information of the advertisement to be inserted.
Processing a packet for transmitting media data, advertisement data, and first signaling information;

Wherein the first signaling information includes information on the transmission of the media data and the advertisement data;

Acquiring and processing a segment including the media data and second signaling information describing reproduction information of the media data from the packet;

Requesting reproduction information of an advertisement to be inserted using advertisement insertion information included in the second signaling information; And

Determining an advertisement to be inserted using the personalization information of the user and condition information included in the first signaling information and obtaining reproduction information of the advertisement to be inserted;

Broadcast signal receiving method comprising a.
The method of claim 8,

The condition information includes a filtering criterion information for filtering the media data or the advertisement data and a value for the filtering criterion information.
The method of claim 8,

The first signaling information includes an LS element that describes information about an LCT session for transmitting the media data or the advertisement data as a lower element, and the LS element includes information applied to all files transmitted to the LCT session. Including an EFDT element for describing, wherein the EFDT element includes a File element for describing information applied to one of the files transmitted to the LCT session,

And the condition information is included under the EFDT element or the File element.
The method of claim 8,

The determining of the advertisement to be inserted and acquiring the reproduction information of the advertisement to be inserted is performed by an application executed in a broadcast signal receiving apparatus.
The method of claim 8,

The advertisement data and the reproduction information of the advertisement to be inserted are transmitted in a non-real time through a broadcasting network.
The method of claim 8,

The advertisement data and the reproduction information of the advertisement to be inserted are transmitted to the Internet network.
The method of claim 8,

The advertisement insertion information includes position information of the reproduction information of the advertisement to be inserted and condition information of the advertisement to be inserted.