WO2017007230A1 - Dispositif et procédé d'émission et de réception de signal de diffusion - Google Patents

Dispositif et procédé d'émission et de réception de signal de diffusion Download PDF

Info

Publication number
WO2017007230A1
WO2017007230A1 PCT/KR2016/007301 KR2016007301W WO2017007230A1 WO 2017007230 A1 WO2017007230 A1 WO 2017007230A1 KR 2016007301 W KR2016007301 W KR 2016007301W WO 2017007230 A1 WO2017007230 A1 WO 2017007230A1
Authority
WO
WIPO (PCT)
Prior art keywords
advertisement
information
service
data
receiver
Prior art date
Application number
PCT/KR2016/007301
Other languages
English (en)
Korean (ko)
Inventor
곽민성
양승률
고우석
문경수
홍성룡
Original Assignee
엘지전자(주)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자(주) filed Critical 엘지전자(주)
Publication of WO2017007230A1 publication Critical patent/WO2017007230A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/235—Processing of additional data, e.g. scrambling of additional data or processing content descriptors
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/236—Assembling of a multiplex stream, e.g. transport stream, by combining a video stream with other content or additional data, e.g. inserting a URL [Uniform Resource Locator] into a video stream, multiplexing software data into a video stream; Remultiplexing of multiplex streams; Insertion of stuffing bits into the multiplex stream, e.g. to obtain a constant bit-rate; Assembling of a packetised elementary stream
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/435—Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/45—Management operations performed by the client for facilitating the reception of or the interaction with the content or administrating data related to the end-user or to the client device itself, e.g. learning user preferences for recommending movies, resolving scheduling conflicts
    • H04N21/458—Scheduling content for creating a personalised stream, e.g. by combining a locally stored advertisement with an incoming stream; Updating operations, e.g. for OS modules ; time-related management operations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/81—Monomedia components thereof

Definitions

  • the present invention relates to a broadcast signal transmitting apparatus, a broadcast signal receiving apparatus, a broadcast signal transmitting method, and a broadcast signal receiving method.
  • the digital broadcast signal may include a larger amount of video / audio data than the analog broadcast signal, and may further include various types of additional data as well as the video / audio data.
  • the digital broadcasting system may provide high definition (HD) images, multichannel audio, and various additional services.
  • HD high definition
  • data transmission efficiency for a large amount of data transmission, robustness of a transmission / reception network, and network flexibility in consideration of a mobile receiving device should be improved.
  • the present invention proposes a target advertisement providing method of a broadcast signal receiver and a broadcast signal receiver.
  • a method of providing a target advertisement of a broadcast signal receiver including: processing media data and description information about the media data; Obtaining advertisement related information included in the description information; Determining a target advertisement using the personalized data and the filtered criteria information; Acquiring target advertisement information for playing the target advertisement; And decoding advertisement data based on the target advertisement information to provide a target advertisement.
  • the media data includes at least one content segment
  • the advertisement data includes at least one advertisement segment
  • the advertisement insertion information may be Xlink information about an advertisement.
  • the target advertisement information includes period information of the target advertisement.
  • the step of determining a target advertisement using the personalized data and the filtering criterion information may be performed by using an application running in a browser.
  • a broadcast signal receiver for providing a target advertisement may process media data and description information about the media data, obtain advertisement insertion information included in the description information, and then target the target data.
  • a client module for obtaining target advertisement information for playing an advertisement an advertisement management module for determining a target advertisement using personalization data and filtering criterion information; And a media decoder that decodes advertisement data based on the target advertisement information and provides a target advertisement.
  • the present invention can provide various broadcast services by processing data according to service characteristics to control a quality of service (QoS) for each service or service component.
  • QoS quality of service
  • the present invention can achieve transmission flexibility by transmitting various broadcast services through the same radio frequency (RF) signal bandwidth.
  • RF radio frequency
  • the present invention it is possible to provide a broadcast signal transmission and reception method and apparatus capable of receiving a digital broadcast signal without errors even when using a mobile reception device or in an indoor environment.
  • the present invention can effectively support the next generation broadcast service in an environment supporting the next generation hybrid broadcast using the terrestrial broadcast network and the Internet network.
  • FIG. 1 is a diagram illustrating a protocol stack according to an embodiment of the present invention.
  • FIG. 2 is a diagram illustrating a service discovery process according to an embodiment of the present invention.
  • LLS low level signaling
  • SLT service list table
  • FIG. 4 illustrates a USBD and an S-TSID delivered to ROUTE according to an embodiment of the present invention.
  • FIG. 5 is a diagram illustrating a USBD delivered to MMT according to an embodiment of the present invention.
  • FIG. 6 illustrates a link layer operation according to an embodiment of the present invention.
  • FIG. 7 illustrates a link mapping table (LMT) according to an embodiment of the present invention.
  • FIG. 8 shows a structure of a broadcast signal transmission apparatus for a next generation broadcast service according to an embodiment of the present invention.
  • FIG 9 illustrates a writing operation of a time interleaver according to an embodiment of the present invention.
  • FIG. 10 is a block diagram of an interleaving address generator composed of a main-PRBS generator and a sub-PRBS generator according to each FFT mode included in a frequency interleaver according to an embodiment of the present invention.
  • FIG. 11 is a diagram illustrating an advertisement providing system of a server-based model according to an embodiment of the present invention.
  • FIG. 12 illustrates an advertisement providing system of an app based model according to an embodiment of the present invention.
  • FIG 13 illustrates an advertisement providing system according to an embodiment of the present invention.
  • FIG 14 illustrates an advertisement providing system according to another embodiment of the present invention.
  • FIG 15 illustrates an advertisement providing system according to another embodiment of the present invention.
  • FIG 16 shows an advertisement providing system according to another embodiment of the present invention.
  • FIG 17 shows an advertisement providing system according to another embodiment of the present invention.
  • FIG 18 illustrates an advertisement providing system according to another embodiment of the present invention.
  • FIG 19 shows an advertisement providing system according to another embodiment of the present invention.
  • FIG 20 illustrates an advertisement providing system according to another embodiment of the present invention.
  • FIG 21 illustrates an advertisement providing system according to another embodiment of the present invention.
  • FIG 22 illustrates an advertisement providing system according to another embodiment of the present invention.
  • FIG 23 illustrates an advertisement providing system according to another embodiment of the present invention.
  • FIG 24 illustrates an advertisement providing system according to another embodiment of the present invention.
  • 26 illustrates signaling of an advertisement identifier according to an embodiment of the present invention.
  • FIG. 27 illustrates filtering criterion information according to an embodiment of the present invention.
  • FIG. 28 is a view illustrating a signaling method of filtering cryptographic information according to an embodiment of the present invention.
  • 29 is a view illustrating a signaling method of filtering cryptographic information according to an embodiment of the present invention.
  • FIG. 30 is a flowchart illustrating a method of providing a target advertisement by a broadcast signal receiver according to an embodiment of the present invention.
  • the present invention provides an apparatus and method for transmitting and receiving broadcast signals for next generation broadcast services.
  • the next generation broadcast service includes a terrestrial broadcast service, a mobile broadcast service, a UHDTV service, and the like.
  • a broadcast signal for a next generation broadcast service may be processed through a non-multiple input multiple output (MIMO) or MIMO scheme.
  • the non-MIMO scheme according to an embodiment of the present invention may include a multiple input single output (MISO) scheme, a single input single output (SISO) scheme, and the like.
  • MISO multiple input single output
  • SISO single input single output
  • the present invention proposes a physical profile (or system) that is optimized to minimize receiver complexity while achieving the performance required for a particular application.
  • FIG. 1 is a diagram illustrating a protocol stack according to an embodiment of the present invention.
  • the service may be delivered to the receiver through a plurality of layers.
  • the transmitting side can generate service data.
  • the delivery layer on the transmitting side performs processing for transmission to the service data, and the physical layer encodes it as a broadcast signal and transmits it through a broadcasting network or broadband.
  • the service data may be generated in a format according to ISO BMFF (base media file format).
  • the ISO BMFF media file may be used in broadcast network / broadband delivery, media encapsulation and / or synchronization format.
  • the service data is all data related to the service, and may include a concept including service components constituting the linear service, signaling information thereof, non real time (NRT) data, and other files.
  • the delivery layer will be described.
  • the delivery layer may provide a transmission function for service data.
  • the service data may be delivered through a broadcast network and / or broadband.
  • the first method may be to process service data into Media Processing Units (MPUs) based on MPEG Media Transport (MMT) and transmit the data using MMM protocol (MMTP).
  • MPUs Media Processing Units
  • MMT MPEG Media Transport
  • MMTP MMM protocol
  • the service data delivered through the MMTP may include service components for linear service and / or service signaling information thereof.
  • the second method may be to process service data into DASH segments based on MPEG DASH and transmit it using Real Time Object Delivery over Unidirectional Transport (ROUTE).
  • the service data delivered through the ROUTE protocol may include service components for the linear service, service signaling information and / or NRT data thereof. That is, non-timed data such as NRT data and files may be delivered through ROUTE.
  • Data processed according to the MMTP or ROUTE protocol may be processed into IP packets via the UDP / IP layer.
  • a service list table (SLT) may also be transmitted through a broadcasting network through a UDP / IP layer.
  • the SLT may be included in the LLS (Low Level Signaling) table and transmitted. The SLT and the LLS table will be described later.
  • IP packets may be treated as link layer packets at the link layer.
  • the link layer may encapsulate data of various formats delivered from an upper layer into a link layer packet and then deliver the data to the physical layer. The link layer will be described later.
  • At least one or more service elements may be delivered via a broadband path.
  • the data transmitted through the broadband may include service components in a DASH format, service signaling information and / or NRT data thereof. This data can be processed via HTTP / TCP / IP, passed through the link layer for broadband transmission, and delivered to the physical layer for broadband transmission.
  • the physical layer may process data received from a delivery layer (upper layer and / or link layer) and transmit the data through a broadcast network or a broadband. Details of the physical layer will be described later.
  • the service may be a collection of service components that are shown to the user as a whole, the components may be of different media types, the service may be continuous or intermittent, the service may be real time or non-real time, and the real time service may be a sequence of TV programs. It can be configured as.
  • the service may be a linear audio / video or audio only service that may have app-based enhancements.
  • the service may be an app-based service whose reproduction / configuration is controlled by the downloaded application.
  • the service may be an ESG service that provides an electronic service guide (ESG).
  • ESG electronic service guide
  • EA Emergency Alert
  • the service component may be delivered by (1) one or more ROUTE sessions or (2) one or more MMTP sessions.
  • the service component When a linear service with app-based enhancement is delivered through a broadcast network, the service component may be delivered by (1) one or more ROUTE sessions and (2) zero or more MMTP sessions.
  • data used for app-based enhancement may be delivered through a ROUTE session in the form of NRT data or other files.
  • linear service components (streaming media components) of one service may not be allowed to be delivered using both protocols simultaneously.
  • the service component may be delivered by one or more ROUTE sessions.
  • the service data used for the app-based service may be delivered through a ROUTE session in the form of NRT data or other files.
  • some service components or some NRT data, files, etc. of these services may be delivered via broadband (hybrid service delivery).
  • the linear service components of one service may be delivered through the MMT protocol.
  • the linear service components of one service may be delivered via a ROUTE protocol.
  • the linear service component and NRT data (NRT service component) of one service may be delivered through the ROUTE protocol.
  • linear service components of one service may be delivered through the MMT protocol, and NRT data (NRT service components) may be delivered through the ROUTE protocol.
  • some service component or some NRT data of a service may be delivered over broadband.
  • the data related to the app-based service or the app-based enhancement may be transmitted through a broadcast network according to ROUTE or through broadband in the form of NRT data.
  • NRT data may also be referred to as locally cashed data.
  • Each ROUTE session includes one or more LCT sessions that deliver, in whole or in part, the content components that make up the service.
  • an LCT session may deliver an individual component of a user service, such as an audio, video, or closed caption stream.
  • Streaming media is formatted into a DASH segment.
  • Each MMTP session includes one or more MMTP packet flows carrying an MMT signaling message or all or some content components.
  • the MMTP packet flow may carry a component formatted with an MMT signaling message or an MPU.
  • an LCT session For delivery of NRT user service or system metadata, an LCT session carries a file based content item.
  • These content files may consist of continuous (timed) or discrete (non-timed) media components of an NRT service, or metadata such as service signaling or ESG fragments.
  • Delivery of system metadata, such as service signaling or ESG fragments, can also be accomplished through the signaling message mode of the MMTP.
  • the tuner can scan frequencies and detect broadcast signals at specific frequencies.
  • the receiver can extract the SLT and send it to the module that processes it.
  • the SLT parser can parse the SLT, obtain data, and store it in the channel map.
  • the receiver may acquire bootstrap information of the SLT and deliver it to the ROUTE or MMT client. This allows the receiver to obtain and store the SLS. USBD or the like can be obtained, which can be parsed by the signaling parser.
  • FIG. 2 is a diagram illustrating a service discovery process according to an embodiment of the present invention.
  • the broadcast stream delivered by the broadcast signal frame of the physical layer may carry LLS (Low Level Signaling).
  • LLS data may be carried through the payload of an IP packet delivered to a well known IP address / port. This LLS may contain an SLT depending on its type.
  • LLS data may be formatted in the form of an LLS table. The first byte of every UDP / IP packet carrying LLS data may be the beginning of the LLS table. Unlike the illustrated embodiment, the IP stream carrying LLS data may be delivered to the same PLP along with other service data.
  • the SLT enables the receiver to generate a service list through a fast channel scan and provides access information for locating the SLS.
  • the SLT includes bootstrap information, which enables the receiver to obtain Service Layer Signaling (SLS) for each service.
  • SLS Service Layer Signaling
  • the bootstrap information may include destination IP address and destination port information of the ROUTE session including the LCT channel carrying the SLS and the LCT channel.
  • the bootstrap information may include a destination IP address and destination port information of the MMTP session carrying the SLS.
  • the SLS of service # 1 described by the SLT is delivered via ROUTE, and the SLT includes bootstrap information (sIP1, dIP1, dPort1) for the ROUTE session including the LCT channel to which the SLS is delivered. can do.
  • SLS of service # 2 described by the SLT is delivered through MMT, and the SLT may include bootstrap information (sIP2, dIP2, and dPort2) for an MMTP session including an MMTP packet flow through which the SLS is delivered.
  • the SLS is signaling information describing characteristics of a corresponding service and may include information for acquiring a corresponding service and a service component of the corresponding service, or may include receiver capability information for reproducing the corresponding service significantly. Having separate service signaling for each service allows the receiver to obtain the appropriate SLS for the desired service without having to parse the entire SLS delivered in the broadcast stream.
  • the SLS When the SLS is delivered through the ROUTE protocol, the SLS may be delivered through a dedicated LCT channel of a ROUTE session indicated by the SLT.
  • the SLS may include a user service bundle description (USBD / USD), a service-based transport session instance description (S-TSID), and / or a media presentation description (MPD).
  • USBD / USD user service bundle description
  • S-TSID service-based transport session instance description
  • MPD media presentation description
  • USBD to USD is one of the SLS fragments and may serve as a signaling hub for describing specific technical information of a service.
  • the USBD may include service identification information, device capability information, and the like.
  • the USBD may include reference information (URI reference) to other SLS fragments (S-TSID, MPD, etc.). That is, USBD / USD can refer to S-TSID and MPD respectively.
  • the USBD may further include metadata information that enables the receiver to determine the transmission mode (broadcast network / broadband). Details of the USBD / USD will be described later.
  • the S-TSID is one of the SLS fragments, and may provide overall session description information for a transport session carrying a service component of a corresponding service.
  • the S-TSID may provide transport session description information for the ROUTE session to which the service component of the corresponding service is delivered and / or the LCT channel of the ROUTE sessions.
  • the S-TSID may provide component acquisition information of service components related to one service.
  • the S-TSID may provide a mapping between the DASH Representation of the MPD and the tsi of the corresponding service component.
  • the component acquisition information of the S-TSID may be provided in the form of tsi, an identifier of an associated DASH representation, and may or may not include a PLP ID according to an embodiment.
  • the component acquisition information enables the receiver to collect audio / video components of a service and to buffer, decode, and the like of DASH media segments.
  • the S-TSID may be referenced by the USBD as described above. Details of the S-TSID will be described later.
  • the MPD is one of the SLS fragments and may provide a description of the DASH media presentation of the service.
  • the MPD may provide a resource identifier for the media segments and may provide contextual information within the media presentation for the identified resources.
  • the MPD may describe the DASH representation (service component) delivered through the broadcast network, and may also describe additional DASH representations delivered through the broadband (hybrid delivery).
  • the MPD may be referenced by the USBD as described above.
  • the SLS When the SLS is delivered through the MMT protocol, the SLS may be delivered through a dedicated MMTP packet flow of an MMTP session indicated by the SLT.
  • packet_id of MMTP packets carrying SLS may have a value of 00.
  • the SLS may include a USBD / USD and / or MMT Package (MP) table.
  • USBD is one of the SLS fragments, and may describe specific technical information of a service like that in ROUTE.
  • the USBD here may also include reference information (URI reference) to other SLS fragments.
  • the USBD of the MMT may refer to the MP table of the MMT signaling.
  • the USBD of the MMT may also include reference information on the S-TSID and / or the MPD.
  • the S-TSID may be for NRT data transmitted through the ROUTE protocol. This is because NRT data can be delivered through the ROUTE protocol even when the linear service component is delivered through the MMT protocol.
  • MPD may be for a service component delivered over broadband in hybrid service delivery. Details of the USBD of the MMT will be described later.
  • the MP table is a signaling message of the MMT for MPU components and may provide overall session description information for an MMTP session carrying a service component of a corresponding service.
  • the MP table may also contain descriptions for assets delivered via this MMTP session.
  • the MP table is streaming signaling information for MPU components, and may provide a list of assets corresponding to one service and location information (component acquisition information) of these components. Specific contents of the MP table may be in a form defined in MMT or a form in which modifications are made.
  • Asset is a multimedia data entity, which may mean a data entity associated with one unique ID and used to generate one multimedia presentation. Asset may correspond to a service component constituting a service.
  • the MP table may be used to access a streaming service component (MPU) corresponding to a desired service.
  • the MP table may be referenced by the USBD as described above.
  • MMT signaling messages may be defined. Such MMT signaling messages may describe additional information related to the MMTP session or service.
  • ROUTE sessions are identified by source IP address, destination IP address, and destination port number.
  • the LCT session is identified by a transport session identifier (TSI) that is unique within the scope of the parent ROUTE session.
  • MMTP sessions are identified by destination IP address and destination port number.
  • the MMTP packet flow is identified by a unique packet_id within the scope of the parent MMTP session.
  • the S-TSID, the USBD / USD, the MPD, or the LCT session carrying them may be called a service signaling channel.
  • the S-TSID, the USBD / USD, the MPD, or the LCT session carrying them may be called a service signaling channel.
  • the S-TSID, the USBD / USD, the MPD, or the LCT session carrying them may be called a service signaling channel.
  • the MMT signaling messages or packet flow carrying them may be called a service signaling channel.
  • one ROUTE or MMTP session may be delivered through a plurality of PLPs. That is, one service may be delivered through one or more PLPs. Unlike shown, components constituting one service may be delivered through different ROUTE sessions. In addition, according to an embodiment, components constituting one service may be delivered through different MMTP sessions. According to an embodiment, components constituting one service may be delivered divided into a ROUTE session and an MMTP session. Although not shown, a component constituting one service may be delivered through a broadband (hybrid delivery).
  • LLS low level signaling
  • SLT service list table
  • An embodiment t3010 of the illustrated LLS table may include information according to an LLS_table_id field, a provider_id field, an LLS_table_version field, and / or an LLS_table_id field.
  • the LLS_table_id field may identify a type of the corresponding LLS table, and the provider_id field may identify service providers related to services signaled by the corresponding LLS table.
  • the service provider is a broadcaster using all or part of the broadcast stream, and the provider_id field may identify one of a plurality of broadcasters using the broadcast stream.
  • the LLS_table_version field may provide version information of a corresponding LLS table.
  • the corresponding LLS table includes the above-described SLT, a rating region table (RRT) including information related to a content advisory rating, a SystemTime information providing information related to system time, and an emergency alert. It may include one of the CAP (Common Alert Protocol) message that provides information related to. According to an embodiment, other information other than these may be included in the LLS table.
  • RRT rating region table
  • CAP Common Alert Protocol
  • One embodiment t3020 of the illustrated SLT may include an @bsid attribute, an @sltCapabilities attribute, a sltInetUrl element, and / or a Service element.
  • Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
  • the @bsid attribute may be an identifier of a broadcast stream.
  • the @sltCapabilities attribute can provide the capability information required to decode and significantly reproduce all services described by the SLT.
  • the sltInetUrl element may provide base URL information used to obtain ESG or service signaling information for services of the corresponding SLT through broadband.
  • the sltInetUrl element may further include an @urlType attribute, which may indicate the type of data that can be obtained through the URL.
  • the service element may be an element including information on services described by the corresponding SLT, and a service element may exist for each service.
  • the Service element contains the @serviceId property, the @sltSvcSeqNum property, the @protected property, the @majorChannelNo property, the @minorChannelNo property, the @serviceCategory property, the @shortServiceName property, the @hidden property, the @broadbandAccessRequired property, the @svcCapabilities property, the BroadcastSvcSignaling element, and / or the svcInetUrl element. It may include.
  • the @serviceId attribute may be an identifier of a corresponding service, and the @sltSvcSeqNum attribute may indicate a sequence number of SLT information for the corresponding service.
  • the @protected attribute may indicate whether at least one service component necessary for meaningful playback of the corresponding service is protected.
  • the @majorChannelNo and @minorChannelNo attributes may indicate the major channel number and the minor channel number of the corresponding service, respectively.
  • the @serviceCategory attribute can indicate the category of the corresponding service.
  • the service category may include a linear A / V service, a linear audio service, an app-based service, an ESG service, and an EAS service.
  • the @shortServiceName attribute may provide a short name of the corresponding service.
  • the @hidden attribute can indicate whether the service is for testing or proprietary use.
  • the @broadbandAccessRequired attribute may indicate whether broadband access is required for meaningful playback of the corresponding service.
  • the @svcCapabilities attribute can provide the capability information necessary for decoding and meaningful reproduction of the corresponding service.
  • the BroadcastSvcSignaling element may provide information related to broadcast signaling of a corresponding service. This element may provide information such as a location, a protocol, and an address with respect to signaling through a broadcasting network of a corresponding service. Details will be described later.
  • the svcInetUrl element may provide URL information for accessing signaling information for a corresponding service through broadband.
  • the sltInetUrl element may further include an @urlType attribute, which may indicate the type of data that can be obtained through the URL.
  • the aforementioned BroadcastSvcSignaling element may include an @slsProtocol attribute, an @slsMajorProtocolVersion attribute, an @slsMinorProtocolVersion attribute, an @slsPlpId attribute, an @slsDestinationIpAddress attribute, an @slsDestinationUdpPort attribute, and / or an @slsSourceIpAddress attribute.
  • the @slsProtocol attribute can indicate the protocol used to deliver the SLS of the service (ROUTE, MMT, etc.).
  • the @slsMajorProtocolVersion attribute and @slsMinorProtocolVersion attribute may indicate the major version number and the minor version number of the protocol used to deliver the SLS of the corresponding service, respectively.
  • the @slsPlpId attribute may provide a PLP identifier for identifying a PLP that delivers the SLS of the corresponding service.
  • this field may be omitted, and the PLP information to which the SLS is delivered may be identified by combining information in the LMT to be described later and bootstrap information of the SLT.
  • the @slsDestinationIpAddress attribute, @slsDestinationUdpPort attribute, and @slsSourceIpAddress attribute may indicate the destination IP address, the destination UDP port, and the source IP address of the transport packet carrying the SLS of the corresponding service, respectively. They can identify the transport session (ROUTE session or MMTP session) to which the SLS is delivered. These may be included in the bootstrap information.
  • FIG. 4 illustrates a USBD and an S-TSID delivered to ROUTE according to an embodiment of the present invention.
  • One embodiment t4010 of the illustrated USBD may have a bundleDescription root element.
  • the bundleDescription root element may have a userServiceDescription element.
  • the userServiceDescription element may be an instance of one service.
  • the userServiceDescription element may include an @globalServiceID attribute, an @serviceId attribute, an @serviceStatus attribute, an @fullMPDUri attribute, an @sTSIDUri attribute, a name element, a serviceLanguage element, a capabilityCode element, and / or a deliveryMethod element.
  • Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
  • the @globalServiceID attribute is a globally unique identifier of the service and can be used to link with ESG data (Service @ globalServiceID).
  • the @serviceId attribute is a reference corresponding to the corresponding service entry of the SLT and may be the same as service ID information of the SLT.
  • the @serviceStatus attribute may indicate the status of the corresponding service. This field may indicate whether the corresponding service is active or inactive.
  • the @fullMPDUri attribute can refer to the MPD fragment of the service. As described above, the MPD may provide a reproduction description for a service component delivered through a broadcast network or a broadband.
  • the @sTSIDUri attribute may refer to the S-TSID fragment of the service.
  • the S-TSID may provide parameters related to access to the transport session carrying the service as described above.
  • the name element may provide the name of the service.
  • This element may further include an @lang attribute, which may indicate the language of the name provided by the name element.
  • the serviceLanguage element may indicate the available languages of the service. That is, this element may list the languages in which the service can be provided.
  • the capabilityCode element may indicate capability or capability group information of the receiver side necessary for significantly playing a corresponding service. This information may be compatible with the capability information format provided by the service announcement.
  • the deliveryMethod element may provide delivery related information with respect to contents accessed through a broadcasting network or a broadband of a corresponding service.
  • the deliveryMethod element may include a broadcastAppService element and / or a unicastAppService element. Each of these elements may have a basePattern element as its child element.
  • the broadcastAppService element may include transmission related information on the DASH presentation delivered through the broadcast network.
  • These DASH representations may include media components across all periods of the service media presentation.
  • the basePattern element of this element may represent a character pattern used by the receiver to match the segment URL. This can be used by the DASH client to request segments of the representation. Matching may imply that the media segment is delivered over the broadcast network.
  • the unicastAppService element may include transmission related information on the DASH representation delivered through broadband. These DASH representations may include media components across all periods of the service media presentation.
  • the basePattern element of this element may represent a character pattern used by the receiver to match the segment URL. This can be used by the DASH client to request segments of the representation. Matching may imply that the media segment is delivered over broadband.
  • An embodiment t4020 of the illustrated S-TSID may have an S-TSID root element.
  • the S-TSID root element may include an @serviceId attribute and / or an RS element.
  • Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
  • the @serviceId attribute is an identifier of a corresponding service and may refer to a corresponding service of USBD / USD.
  • the RS element may describe information on ROUTE sessions through which service components of a corresponding service are delivered. Depending on the number of such ROUTE sessions, there may be a plurality of these elements.
  • the RS element may further include an @bsid attribute, an @sIpAddr attribute, an @dIpAddr attribute, an @dport attribute, an @PLPID attribute, and / or an LS element.
  • the @bsid attribute may be an identifier of a broadcast stream through which service components of a corresponding service are delivered. If this field is omitted, the default broadcast stream may be a broadcast stream that includes a PLP that carries the SLS of the service. The value of this field may be the same value as the @bsid attribute of SLT.
  • the @sIpAddr attribute, the @dIpAddr attribute, and the @dport attribute may indicate a source IP address, a destination IP address, and a destination UDP port of the corresponding ROUTE session, respectively. If these fields are omitted, the default values may be the source IP address, destination IP address, and destination UDP port values of the current, ROUTE session carrying that SLS, that is, carrying that S-TSID. For other ROUTE sessions that carry service components of the service but not the current ROUTE session, these fields may not be omitted.
  • the @PLPID attribute may indicate PLP ID information of a corresponding ROUTE session. If this field is omitted, the default value may be the PLP ID value of the current PLP to which the corresponding S-TSID is being delivered. According to an embodiment, this field is omitted, and the PLP ID information of the corresponding ROUTE session may be confirmed by combining information in the LMT to be described later and IP address / UDP port information of the RS element.
  • the LS element may describe information on LCT channels through which service components of a corresponding service are delivered. Depending on the number of such LCT channels, there may be a plurality of these elements.
  • the LS element may include an @tsi attribute, an @PLPID attribute, an @bw attribute, an @startTime attribute, an @endTime attribute, an SrcFlow element, and / or a RepairFlow element.
  • the @tsi attribute may represent tsi information of a corresponding LCT channel. Through this, LCT channels through which a service component of a corresponding service is delivered may be identified.
  • the @PLPID attribute may represent PLP ID information of a corresponding LCT channel. In some embodiments, this field may be omitted.
  • the @bw attribute may indicate the maximum bandwidth of the corresponding LCT channel.
  • the @startTime attribute may indicate the start time of the LCT session, and the @endTime attribute may indicate the end time of the LCT channel.
  • the SrcFlow element may describe the source flow of ROUTE.
  • the source protocol of ROUTE is used to transmit the delivery object, and can establish at least one source flow in one ROUTE session. These source flows can deliver related objects as an object flow.
  • the RepairFlow element may describe the repair flow of ROUTE. Delivery objects delivered according to the source protocol may be protected according to Forward Error Correction (FEC).
  • FEC Forward Error Correction
  • the repair protocol may define a FEC framework that enables such FEC protection.
  • FIG. 5 is a diagram illustrating a USBD delivered to MMT according to an embodiment of the present invention.
  • One embodiment of the illustrated USBD may have a bundleDescription root element.
  • the bundleDescription root element may have a userServiceDescription element.
  • the userServiceDescription element may be an instance of one service.
  • the userServiceDescription element may include an @globalServiceID attribute, an @serviceId attribute, a Name element, a serviceLanguage element, a content advisoryRating element, a Channel element, an mpuComponent element, a routeComponent element, a broadbandComponent element, and / or a ComponentInfo element.
  • Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
  • the @globalServiceID attribute, the @serviceId attribute, the Name element and / or the serviceLanguage element may be the same as the corresponding fields of the USBD delivered to the above-described ROUTE.
  • the contentAdvisoryRating element may indicate the content advisory rating of the corresponding service. This information may be compatible with the content advisory rating information format provided by the service announcement.
  • the channel element may include information related to the corresponding service. The detail of this element is mentioned later.
  • the mpuComponent element may provide a description for service components delivered as an MPU of a corresponding service.
  • This element may further include an @mmtPackageId attribute and / or an @nextMmtPackageId attribute.
  • the @mmtPackageId attribute may refer to an MMT package of service components delivered as an MPU of a corresponding service.
  • the @nextMmtPackageId attribute may refer to an MMT package to be used next to the MMT package referenced by the @mmtPackageId attribute in time.
  • the MP table can be referenced through the information of this element.
  • the routeComponent element may include a description of service components of the corresponding service delivered to ROUTE. Even if the linear service components are delivered in the MMT protocol, the NRT data may be delivered according to the ROUTE protocol as described above. This element may describe information about such NRT data. The detail of this element is mentioned later.
  • the broadbandComponent element may include a description of service components of the corresponding service delivered over broadband.
  • some service components or other files of a service may be delivered over broadband. This element may describe information about these data.
  • This element may further include the @fullMPDUri attribute. This attribute may refer to an MPD that describes service components delivered over broadband.
  • the element when the broadcast signal is weakened due to driving in a tunnel or the like, the element may be needed to support handoff between the broadcast network and the broadband band. When the broadcast signal is weakened, while acquiring the service component through broadband, and when the broadcast signal is stronger, the service continuity may be guaranteed by acquiring the service component through the broadcast network.
  • the ComponentInfo element may include information on service components of a corresponding service. Depending on the number of service components of the service, there may be a plurality of these elements. This element may describe information such as the type, role, name, identifier, and protection of each service component. Detailed information on this element will be described later.
  • the aforementioned channel element may further include an @serviceGenre attribute, an @serviceIcon attribute, and / or a ServiceDescription element.
  • the @serviceGenre attribute may indicate the genre of the corresponding service
  • the @serviceIcon attribute may include URL information of an icon representing the corresponding service.
  • the ServiceDescription element provides a service description of the service, which may further include an @serviceDescrText attribute and / or an @serviceDescrLang attribute. Each of these attributes may indicate the text of the service description and the language used for that text.
  • the aforementioned routeComponent element may further include an @sTSIDUri attribute, an @sTSIDDestinationIpAddress attribute, an @sTSIDDestinationUdpPort attribute, an @sTSIDSourceIpAddress attribute, an @sTSIDMajorProtocolVersion attribute, and / or an @sTSIDMinorProtocolVersion attribute.
  • the @sTSIDUri attribute may refer to an S-TSID fragment. This field may be the same as the corresponding field of USBD delivered to ROUTE described above. This S-TSID may provide access related information for service components delivered in ROUTE. This S-TSID may exist for NRT data delivered according to the ROUTE protocol in the situation where linear service components are delivered according to the MMT protocol.
  • the @sTSIDDestinationIpAddress attribute, the @sTSIDDestinationUdpPort attribute, and the @sTSIDSourceIpAddress attribute may indicate a destination IP address, a destination UDP port, and a source IP address of a transport packet carrying the aforementioned S-TSID, respectively. That is, these fields may identify a transport session (MMTP session or ROUTE session) carrying the aforementioned S-TSID.
  • the @sTSIDMajorProtocolVersion attribute and the @sTSIDMinorProtocolVersion attribute may indicate a major version number and a minor version number of the transport protocol used to deliver the aforementioned S-TSID.
  • ComponentInfo element may further include an @componentType attribute, an @componentRole attribute, an @componentProtectedFlag attribute, an @componentId attribute, and / or an @componentName attribute.
  • the @componentType attribute may indicate the type of the corresponding component. For example, this property may indicate whether the corresponding component is an audio, video, or closed caption component.
  • the @componentRole attribute can indicate the role (role) of the corresponding component. For example, this property can indicate whether the main audio, music, commentary, etc., if the corresponding component is an audio component. If the corresponding component is a video component, it may indicate whether it is primary video. If the corresponding component is a closed caption component, it may indicate whether it is a normal caption or an easy reader type.
  • the @componentProtectedFlag attribute may indicate whether a corresponding service component is protected, for example, encrypted.
  • the @componentId attribute may represent an identifier of a corresponding service component.
  • the value of this attribute may be a value such as asset_id (asset ID) of the MP table corresponding to this service component.
  • the @componentName attribute may represent the name of the corresponding service component.
  • FIG. 6 illustrates a link layer operation according to an embodiment of the present invention.
  • the link layer may be a layer between the physical layer and the network layer.
  • the transmitter may transmit data from the network layer to the physical layer
  • the receiver may transmit data from the physical layer to the network layer (t6010).
  • the purpose of the link layer may be to compress all input packet types into one format for processing by the physical layer, to ensure flexibility and future scalability for input packet types not yet defined. have.
  • the link layer may provide an option of compressing unnecessary information in the header of the input packet, so that the input data may be efficiently transmitted. Operations such as overhead reduction and encapsulation of the link layer may be referred to as a link layer protocol, and a packet generated using the corresponding protocol may be referred to as a link layer packet.
  • the link layer may perform functions such as packet encapsulation, overhead reduction, and / or signaling transmission.
  • the link layer ALP may perform an overhead reduction process on input packets and then encapsulate them into link layer packets.
  • the link layer may encapsulate the link layer packet without performing an overhead reduction process.
  • the use of the link layer protocol can greatly reduce the overhead for data transmission on the physical layer, and the link layer protocol according to the present invention can provide IP overhead reduction and / or MPEG-2 TS overhead reduction. have.
  • the link layer may sequentially perform IP header compression, adaptation, and / or encapsulation. In some embodiments, some processes may be omitted.
  • the RoHC module performs IP packet header compression to reduce unnecessary overhead, and context information may be extracted and transmitted out of band through an adaptation process.
  • the IP header compression and adaptation process may be collectively called IP header compression.
  • IP packets may be encapsulated into link layer packets through an encapsulation process.
  • the link layer may sequentially perform an overhead reduction and / or encapsulation process for the TS packet. In some embodiments, some processes may be omitted.
  • the link layer may provide sync byte removal, null packet deletion and / or common header removal (compression).
  • Sync byte elimination can provide overhead reduction of 1 byte per TS packet. Null packet deletion can be performed in a manner that can be reinserted at the receiving end. In addition, common information between successive headers can be deleted (compressed) in a manner that can be recovered at the receiving side. Some of each overhead reduction process may be omitted. Thereafter, TS packets may be encapsulated into link layer packets through an encapsulation process.
  • the link layer packet structure for encapsulation of TS packets may be different from other types of packets.
  • IP header compression will be described.
  • the IP packet has a fixed header format, but some information required in a communication environment may be unnecessary in a broadcast environment.
  • the link layer protocol may provide a mechanism to reduce broadcast overhead by compressing the header of the IP packet.
  • IP header compression may include a header compressor / decompressor and / or adaptation module.
  • the IP header compressor (RoHC compressor) may reduce the size of each IP packet header based on the RoHC scheme.
  • the adaptation module may then extract the context information and generate signaling information from each packet stream.
  • the receiver may parse signaling information related to the packet stream and attach context information to the packet stream.
  • the RoHC decompressor can reconstruct the original IP packet by recovering the packet header.
  • IP header compression may mean only IP header compression by a header compressor, or may mean a concept in which the IP header compression and the adaptation process by the adaptation module are combined. The same is true for decompressing.
  • the adaptation function may generate link layer signaling using context information and / or configuration parameters.
  • the adaptation function may periodically send link layer signaling over each physical frame using previous configuration parameters and / or context information.
  • the context information is extracted from the compressed IP packets, and various methods may be used according to the adaptation mode.
  • Mode # 1 is a mode in which no operation is performed on the compressed packet stream, and may be a mode in which the adaptation module operates as a buffer.
  • Mode # 2 may be a mode for extracting context information (static chain) by detecting IR packets in the compressed packet stream. After extraction, the IR packet is converted into an IR-DYN packet, and the IR-DYN packet can be transmitted in the same order in the packet stream by replacing the original IR packet.
  • context information static chain
  • Mode # 3 t6020 may be a mode for detecting IR and IR-DYN packets and extracting context information from the compressed packet stream.
  • Static chains and dynamic chains can be extracted from IR packets and dynamic chains can be extracted from IR-DYN packets.
  • the IR and IR-DYN packets can be converted into regular compressed packets.
  • the switched packets can be sent in the same order within the packet stream, replacing the original IR and IR-DYN packets.
  • the remaining packets after the context information is extracted may be encapsulated and transmitted according to the link layer packet structure for the compressed IP packet.
  • the context information may be transmitted by being encapsulated according to a link layer packet structure for signaling information as link layer signaling.
  • the extracted context information may be included in the RoHC-U Description Table (RTT) and transmitted separately from the RoHC packet flow.
  • the context information may be transmitted through a specific physical data path along with other signaling information.
  • a specific physical data path may mean one of general PLPs, a PLP to which LLS (Low Level Signaling) is delivered, a dedicated PLP, or an L1 signaling path. path).
  • the RDT may be signaling information including context information (static chain and / or dynamic chain) and / or information related to header compression.
  • the RDT may be transmitted whenever the context information changes.
  • the RDT may be transmitted in every physical frame. In order to transmit the RDT in every physical frame, a previous RDT may be re-use.
  • the receiver may first select PLP to acquire signaling information such as SLT, RDT, LMT, and the like. When the signaling information is obtained, the receiver may combine these to obtain a mapping between the service-IP information-context information-PLP. That is, the receiver can know which service is transmitted to which IP streams, which IP streams are delivered to which PLP, and can also obtain corresponding context information of the PLPs. The receiver can select and decode a PLP carrying a particular packet stream. The adaptation module can parse the context information and merge it with the compressed packets. This allows the packet stream to be recovered, which can be delivered to the RoHC decompressor. Decompression can then begin.
  • signaling information such as SLT, RDT, LMT, and the like.
  • the receiver may combine these to obtain a mapping between the service-IP information-context information-PLP. That is, the receiver can know which service is transmitted to which IP streams, which IP streams are delivered to which PLP, and can also obtain corresponding context information of the PLPs.
  • the receiver detects the IR packet and starts decompression from the first received IR packet according to the adaptation mode (mode 1), or detects the IR-DYN packet to perform decompression from the first received IR-DYN packet.
  • the link layer protocol may encapsulate all types of input packets, such as IP packets and TS packets, into link layer packets. This allows the physical layer to process only one packet format independently of the protocol type of the network layer (here, consider MPEG-2 TS packet as a kind of network layer packet). Each network layer packet or input packet is transformed into a payload of a generic link layer packet.
  • Segmentation may be utilized in the packet encapsulation process. If the network layer packet is too large to be processed by the physical layer, the network layer packet may be divided into two or more segments.
  • the link layer packet header may include fields for performing division at the transmitting side and recombination at the receiving side. Each segment may be encapsulated into a link layer packet in the same order as the original position.
  • Concatenation may also be utilized in the packet encapsulation process. If the network layer packet is small enough that the payload of the link layer packet includes several network layer packets, concatenation may be performed.
  • the link layer packet header may include fields for executing concatenation. In the case of concatenation, each input packet may be encapsulated into the payload of the link layer packet in the same order as the original input order.
  • the link layer packet may include a header and a payload, and the header may include a base header, an additional header, and / or an optional header.
  • the additional header may be added depending on the chaining or splitting, and the additional header may include necessary fields according to the situation.
  • an optional header may be further added to transmit additional information.
  • Each header structure may be predefined. As described above, when the input packet is a TS packet, a link layer header structure different from other packets may be used.
  • Link layer signaling may operate at a lower level than the IP layer.
  • the receiving side can acquire the link layer signaling faster than the IP level signaling such as LLS, SLT, SLS, and the like. Therefore, link layer signaling may be obtained before session establishment.
  • Link layer signaling may include internal link layer signaling and external link layer signaling.
  • Internal link layer signaling may be signaling information generated in the link layer.
  • the above-described RDT or LMT to be described later may correspond to this.
  • the external link layer signaling may be signaling information received from an external module, an external protocol, or an upper layer.
  • the link layer may encapsulate link layer signaling into a link layer packet and deliver it.
  • a link layer packet structure (header structure) for link layer signaling may be defined, and link layer signaling information may be encapsulated according to this structure.
  • FIG. 7 illustrates a link mapping table (LMT) according to an embodiment of the present invention.
  • the LMT may provide a list of higher layer sessions carried by the PLP.
  • the LMT may also provide additional information for processing link layer packets carrying higher layer sessions.
  • the higher layer session may be called multicast.
  • Information on which IP streams and which transport sessions are being transmitted through a specific PLP may be obtained through the LMT. Conversely, information on which PLP a specific transport session is delivered to may be obtained.
  • the LMT may be delivered to any PLP identified as carrying an LLS.
  • the PLP through which the LLS is delivered may be identified by the LLS flag of the L1 detail signaling information of the physical layer.
  • the LLS flag may be a flag field indicating whether LLS is delivered to the corresponding PLP for each PLP.
  • the L1 detail signaling information may correspond to PLS2 data to be described later.
  • the LMT may be delivered to the same PLP together with the LLS.
  • Each LMT may describe the mapping between PLPs and IP address / port as described above.
  • the LLS may include an SLT, where these IP addresses / ports described by the LMT are all IP addresses associated with any service described by the SLT forwarded to the same PLP as that LMT. It can be / ports.
  • the PLP identifier information in the above-described SLT, SLS, etc. may be utilized, so that information on which PLP the specific transmission session indicated by the SLT, SLS is transmitted may be confirmed.
  • the PLP identifier information in the above-described SLT, SLS, etc. may be omitted, and the PLP information for the specific transport session indicated by the SLT, SLS may be confirmed by referring to the information in the LMT.
  • the receiver may identify the PLP to know by combining LMT and other IP level signaling information.
  • PLP information in SLT, SLS, and the like is not omitted, and may remain in the SLT, SLS, and the like.
  • the LMT according to the illustrated embodiment may include a signaling_type field, a PLP_ID field, a num_session field, and / or information about respective sessions.
  • a PLP loop may be added to the LMT according to an embodiment, so that information on a plurality of PLPs may be described.
  • the LMT may describe PLPs for all IP addresses / ports related to all services described by the SLTs delivered together, in a PLP loop.
  • the signaling_type field may indicate the type of signaling information carried by the corresponding table.
  • the value of the signaling_type field for the LMT may be set to 0x01.
  • the signaling_type field may be omitted.
  • the PLP_ID field may identify a target PLP to be described. When a PLP loop is used, each PLP_ID field may identify each target PLP. From the PLP_ID field may be included in the PLP loop.
  • the PLP_ID field mentioned below is an identifier for one PLP in a PLP loop, and the fields described below may be fields for the corresponding PLP.
  • the num_session field may indicate the number of upper layer sessions delivered to the PLP identified by the corresponding PLP_ID field. According to the number indicated by the num_session field, information about each session may be included. This information may include an src_IP_add field, a dst_IP_add field, a src_UDP_port field, a dst_UDP_port field, a SID_flag field, a compressed_flag field, a SID field, and / or a context_id field.
  • the src_IP_add field, dst_IP_add field, src_UDP_port field, and dst_UDP_port field are the source IP address, destination IP address, source UDP port, destination UDP port for the transport session among the upper layer sessions forwarded to the PLP identified by the corresponding PLP_ID field. It can indicate a port.
  • the SID_flag field may indicate whether a link layer packet carrying a corresponding transport session has an SID field in its optional header.
  • a link layer packet carrying an upper layer session may have an SID field in its optional header, and the SID field value may be the same as an SID field in an LMT to be described later.
  • the compressed_flag field may indicate whether header compression has been applied to data of a link layer packet carrying a corresponding transport session.
  • the existence of the context_id field to be described later may be determined according to the value of this field.
  • the SID field may indicate a sub stream ID (SID) for link layer packets carrying a corresponding transport session.
  • SID sub stream ID
  • These link layer packets may include an SID having the same value as this SID field in the optional header.
  • the context_id field may provide a reference to a context id (CID) in the RDT.
  • the CID information of the RDT may indicate the context ID for the corresponding compressed IP packet stream.
  • the RDT may provide context information for the compressed IP packet stream. RDT and LMT may be associated with this field.
  • each field, element, or attribute may be omitted or replaced by another field, and additional fields, elements, or attributes may be added according to an embodiment. .
  • service components of one service may be delivered through a plurality of ROUTE sessions.
  • the SLS may be obtained through the bootstrap information of the SLT.
  • the SLS's USBD allows the S-TSID and MPD to be referenced.
  • the S-TSID may describe transport session description information for other ROUTE sessions to which service components are delivered, as well as a ROUTE session to which an SLS is being delivered.
  • all service components delivered through a plurality of ROUTE sessions may be collected. This may be similarly applied when service components of a service are delivered through a plurality of MMTP sessions.
  • one service component may be used simultaneously by a plurality of services.
  • bootstrapping for ESG services may be performed by a broadcast network or broadband.
  • URL information of the SLT may be utilized. ESG information and the like can be requested to this URL.
  • one service component of one service may be delivered to the broadcasting network and one to the broadband (hybrid).
  • the S-TSID may describe components delivered to a broadcasting network, so that a ROUTE client may acquire desired service components.
  • USBD also has base pattern information, which allows you to describe which segments (which components) are to be routed to which path. Therefore, the receiver can use this to know what segment to request to the broadband server and what segment to find in the broadcast stream.
  • scalable coding for a service may be performed.
  • the USBD may have all the capability information needed to render the service. For example, when a service is provided in HD or UHD, the capability information of the USBD may have a value of “HD or UHD”.
  • the receiver may know which component should be played in order to render the UHD or HD service using the MPD.
  • app components to be used for app-based enhancement / app-based service may be delivered through a broadcast network or through broadband as an NRT component.
  • app signaling for app-based enhancement may be performed by an application signaling table (AST) delivered with SLS.
  • an event which is a signaling of an operation to be performed by the app, may be delivered in the form of an event message table (EMT) with SLS, signaled in an MPD, or in-band signaled in a box in a DASH representation. . AST, EMT, etc. may be delivered via broadband.
  • App-based enhancement may be provided using the collected app components and such signaling information.
  • a CAP message may be included in the aforementioned LLS table for emergency alerting. Rich media content for emergency alerts may also be provided. Rich media may be signaled by the CAP message, and if rich media is present it may be provided as an EAS service signaled by the SLT.
  • the linear service components may be delivered through a broadcasting network according to the MMT protocol.
  • NRT data for example, an app component
  • data on the service may be delivered through a broadcasting network according to the ROUTE protocol.
  • data on the service may be delivered through broadband.
  • the receiver can access the MMTP session carrying the SLS using the bootstrap information of the SLT.
  • the USBD of the SLS according to the MMT may refer to the MP table so that the receiver may acquire linear service components formatted with the MPU delivered according to the MMT protocol.
  • the USBD may further refer to the S-TSID to allow the receiver to obtain NRT data delivered according to the ROUTE protocol.
  • the USBD may further reference the MPD to provide a playback description for the data delivered over the broadband.
  • the receiver may transmit location URL information for obtaining a streaming component and / or a file content item (such as a file) to the companion device through a method such as a web socket.
  • An application of a companion device may request the component, data, and the like by requesting the URL through an HTTP GET.
  • the receiver may transmit information such as system time information and emergency alert information to the companion device.
  • FIG. 8 shows a structure of a broadcast signal transmission apparatus for a next generation broadcast service according to an embodiment of the present invention.
  • a broadcast signal transmission apparatus for a next generation broadcast service includes an input format block 1000, a bit interleaved coding & modulation (BICM) block 1010, and a frame building block 1020, orthogonal frequency division multiplexing (OFDM) generation block (OFDM generation block) 1030, and signaling generation block 1040. The operation of each block of the broadcast signal transmission apparatus will be described.
  • BICM bit interleaved coding & modulation
  • OFDM generation block orthogonal frequency division multiplexing
  • signaling generation block 1040 The operation of each block of the broadcast signal transmission apparatus will be described.
  • IP streams / packets and MPEG2-TS may be main input formats, and other stream types are treated as general streams.
  • the input format block 1000 can demultiplex each input stream into one or multiple data pipes to which independent coding and modulation is applied.
  • the data pipe is the basic unit for controlling robustness, which affects the quality of service (QoS).
  • QoS quality of service
  • One or multiple services or service components may be delivered by one data pipe.
  • a data pipe is a logical channel at the physical layer that carries service data or related metadata that can carry one or multiple services or service components.
  • the BICM block 1010 may include a processing block applied to a profile (or system) to which MIMO is not applied and / or a processing block of a profile (or system) to which MIMO is applied, and for processing each data pipe. It may include a plurality of processing blocks.
  • the processing block of the BICM block to which MIMO is not applied may include a data FEC encoder, a bit interleaver, a constellation mapper, a signal space diversity (SSD) encoding block, and a time interleaver.
  • the processing block of the BICM block to which MIMO is applied is distinguished from the processing block of BICM to which MIMO is not applied in that it further includes a cell word demultiplexer and a MIMO encoding block.
  • the data FEC encoder performs FEC encoding on the input BBF to generate the FECBLOCK procedure using outer coding (BCH) and inner coding (LDPC).
  • Outer coding (BCH) is an optional coding method.
  • the bit interleaver interleaves the output of the data FEC encoder to achieve optimized performance with a combination of LDPC codes and modulation schemes.
  • Constellation Mapper uses QPSK, QAM-16, non-uniform QAM (NUQ-64, NUQ-256, NUQ-1024) or non-uniform constellation (NUC-16, NUC-64, NUC-256, NUC-1024)
  • the cell word from the bit interleaver or cell word demultiplexer can then be modulated to provide a power-normalized constellation point.
  • NUQ has any shape, while QAM-16 and NUQ have a square shape. Both NUQ and NUC are specifically defined for each code rate and are signaled by the parameter DP_MOD of PLS2 data.
  • the time interleaver may operate at the data pipe level. The parameters of time interleaving can be set differently for each data pipe.
  • the time interleaver of the present invention may be located between a BICM chain block and a frame builder.
  • the time interleaver according to the present invention may selectively use a convolution interleaver (CI) and a block interleaver (BI) according to a physical layer pipe (PLP) mode, or both.
  • PLP according to an embodiment of the present invention is a physical path used in the same concept as the above-described DP, the name can be changed according to the designer's intention.
  • the PLP mode according to an embodiment of the present invention may include a single PLP mode or a multiple PLP mode according to the number of PLPs processed by the broadcast signal transmitter or the broadcast signal transmitter.
  • time interleaving using different time interleaving methods according to the PLP mode may be referred to as hybrid time interleaving.
  • the hybrid time deinterleaver may perform an operation corresponding to the reverse operation of the aforementioned hybrid time interleaver.
  • the cell word demultiplexer is used to separate a single cell word stream into a dual cell word stream for MIMO processing.
  • the MIMO encoding block can process the output of the cell word demultiplexer using the MIMO encoding scheme.
  • the MIMO encoding scheme of the present invention may be defined as full-rate spatial multiplexing (FR-SM) to provide capacity increase with a relatively small complexity increase at the receiver side.
  • MIMO processing is applied at the data pipe level. NUQ (e 1, i ), the pair of constellation mapper outputs And e 2, i are fed to the input of the MIMO encoder, the MIMO encoder output pairs g1, i and g2, i are 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.
  • the preamble may indicate whether an emergency alert service (EAS) is provided in the current frame.
  • EAS emergency alert service
  • the main purpose of the FSS is to carry PLS data. For fast synchronization and channel estimation, and fast decoding of PLS data, the FSS has a higher density pilot pattern than normal data symbols.
  • the frame building block adjusts the timing between the data pipes and the corresponding PLS data so that a delay compensation block is provided at the transmitter to ensure co-time between the data pipes and the corresponding PLS data.
  • a cell mapper and a frequency interleaver for mapping a PLS, a data pipe, an auxiliary stream, and a dummy cell to an active carrier of an OFDM symbol in a frame.
  • the frequency interleaver may provide frequency diversity by randomly interleaving data cells received from the cell mapper.
  • the frequency interleaver uses a different interleaving seed order to obtain the maximum interleaving gain in a single frame.
  • the frequency interleaver uses a single symbol or data corresponding to an OFDM symbol pair consisting of two sequential OFDM symbols. Operate on corresponding data.
  • OFDM generation block 1030 modulates the OFDM carrier, inserts pilots, and generates time-domain signals for transmission by the cells generated by the frame building block. In addition, the block sequentially inserts a guard interval and applies a PAPR reduction process to generate a final RF signal.
  • the signaling generation block 1040 may generate physical layer signaling information used for the operation of each functional block.
  • Signaling information may include PLS data.
  • PLS provides a means by which a receiver can connect to a physical layer data pipe.
  • PLS data consists of PLS1 data and PLS2 data.
  • PLS1 data is the first set of PLS data delivered to the FSS in frames with fixed size, coding, and modulation that convey basic information about the system as well as the parameters needed to decode the PLS2 data.
  • PLS1 data provides basic transmission parameters including the parameters required to enable reception and decoding of PLS2 data.
  • PLS2 data carries more detailed PLS data about the data pipes and systems and is the second set of PLS data sent to the FSS.
  • PLS2 signaling further consists of two types of parameters: PLS2 static data (PLS2-STAT data) and PLS2 dynamic data (PLS2-DYN data).
  • PLS2 static data is PLS2 data that is static during the duration of a frame group
  • PLS2 dynamic data is PLS2 data that changes dynamically from frame to frame.
  • the PLS2 data may include FIC_FLAG information.
  • FIC Fast Information Channel
  • the FIC_FLAG information is a 1-bit field and indicates whether a fast information channel (FIC) is used in the current frame group.If the value of this field is set to 1, the FIC is provided in the current frame. If the value of the field is set to 0, the FIC is not transmitted in the current frame.
  • the BICM block 1010 may include a BICM block for protecting PLS data
  • the BICM block for protecting PLS data is a PLS FEC encoder. , Bit interleaver, and constellation mapper.
  • the PLS FEC encoder performs external encoding on scrambled PLS 1,2 data using a scrambler for scrambling PLS1 data and PLS2 data, shortened BCH code for PLS protection, and a BCH for inserting zero bits after BCH encoding.
  • An encoding / zero insertion block, an LDPC encoding block for performing encoding using an LDPC code, and an LDPC parity puncturing block may be included.
  • the output bits of zero insertion can be permutated before LDPC encoding.
  • the bit interleaver interleaves the respective shortened and punctured PLS1 data and PLS2 data, and the constellation mapper bit interleaves.
  • the PLS1 data and the PLS2 data can be mapped to the constellation.
  • the broadcast signal receiving apparatus for the next generation broadcast service may perform a reverse process of the broadcast signal transmitting apparatus for the next generation broadcast service described with reference to FIG. 8.
  • An apparatus for receiving broadcast signals for a next generation broadcast service includes a synchronization and demodulation module for performing demodulation corresponding to a reverse process of a procedure executed by a broadcast signal transmitting apparatus and an input signal.
  • a frame parsing module for parsing a frame, extracting data on which a service selected by a user is transmitted, converting an input signal into bit region data, and then deinterleaving the bit region data as necessary, and transmitting efficiency
  • a demapping and decoding module for performing demapping on the mapping applied for decoding, and correcting an error occurring in a transmission channel through decoding, of various compression / signal processing procedures applied by a broadcast signal transmission apparatus.
  • Demodulated by an output processor and a synchronization and demodulation module that executes the inverse process It may include a signaling decoding module for obtaining and processing the PLS information from the signal.
  • the frame parsing module, the demapping and decoding module, and the output processor may execute the function by using the PLS data output from the signaling decoding module.
  • a time interleaving group according to an embodiment of the present invention is directly mapped to one frame or spread over P I frames.
  • Each time interleaving group is further divided into one or more (N TI ) time interleaving blocks.
  • each time interleaving block corresponds to one use of the time interleaver memory.
  • the time interleaving block in the time interleaving group may include different numbers of XFECBLOCKs.
  • the time interleaver may also act as a buffer for data pipe data prior to the frame generation process.
  • the time interleaver according to an embodiment of the present invention is a twisted row-column block interleaver.
  • the twisted row-column block interleaver according to an embodiment of the present invention writes the first XFECBLOCK in the column direction to the first column of the time interleaving memory, the second XFECBLOCK to the next column and the remaining XFECBLOCKs in the time interleaving block in the same manner. You can fill in these. And in an interleaving array, cells can be read diagonally from the first row to the last row (starting from the leftmost column to the right along the row).
  • the interleaving array for the twisted row-column block interleaver may insert the virtual XFECBLOCK into the time interleaving memory to achieve a single memory deinterleaving at the receiver side regardless of the number of XFECBLOCKs in the time interleaving block.
  • the virtual XFECBLOCK must be inserted in front of the other XFECBLOCKs to achieve a single memory deinterleaving on the receiver side.
  • FIG 9 illustrates a writing operation of a time interleaver according to an embodiment of the present invention.
  • the block shown on the left side of the figure represents a TI memory address array, and the block shown on the right side of the figure shows that virtual FEC blocks are placed at the front of the TI group for two consecutive TI groups. It represents the writing operation when two and one are inserted respectively.
  • the frequency interleaver may include an interleaving address generator for generating an interleaving address for applying to data corresponding to a symbol pair.
  • FIG. 10 is a block diagram of an interleaving address generator composed of a main-PRBS generator and a sub-PRBS generator according to each FFT mode included in a frequency interleaver according to an embodiment of the present invention.
  • the interleaving process for an OFDM symbol pair uses one interleaving sequence and is described as follows.
  • x m, l, p is the p th cell of the l th OFDM symbol in the m th frame
  • N data is the number of data cells.
  • 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 advertisement content may be provided based on Dynamic Adaptive Streaming over HTTP (DASH).
  • DASH Dynamic Adaptive Streaming over HTTP
  • real-time broadcast A / V content and data may be represented by an ISO BMFF (Base Media File Format) and the like, which may be transmitted in real time through a terrestrial broadcasting network.
  • Non-real-time content may be delivered based on IP / UDP / ROUTE.
  • the DASH protocol can be used to receive or stream content in real time over the Internet (broadband).
  • the broadcast receiver 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. .
  • the broadcast system 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.
  • 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.
  • 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.
  • 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.
  • MPD media presentation description
  • AD content advertisement content
  • a DASH client basically configures audio / video data (A / V data) through an HTTP request / response through a broadband channel. You can 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 performing 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.
  • the advertisement providing model may include an app-based model and a server-based model.
  • apps can interact with the ad server. If the dash client supports the form of MSE (Media Source Extensions), then the 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 may be within the app.
  • MSE Media Source Extensions
  • Server-based models can use the built-in DASH tool.
  • one DASH client can be used.
  • communication with the ad decision service can take place at the server.
  • MPD update minimumUpdatePeriod or MPD Validity Expiration Event
  • 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.
  • 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).
  • 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.
  • Ad break A location or point in time where one or more ads may be schdeuled for delivery.
  • Ad Decision Service A functional entity that decides which ad (s) will be shown to the user.
  • Ad Management module logical service that, for given cue data, communicates with the ad decision service to determine the ad content to be presented during the ad break described in that cue data. , communicates with the ad decision service and determines which advertisement content (if at all) should be presented during the ad break described in the cue data).
  • Cue indication of time and prameters of the upcoming ad break.
  • CDN node functional entity returning a segment on requesg from DASH client.
  • Packager A functional entity that creates a media segment suitable for a dash client and processes conditioned content, which may be referred to as a functional entity that processes contitioned content and produces media segments suitable for consumption by a DASH client. This entity is also known as fragmenter, encaptulator, or segmenter).
  • Origin A functional entity that contains media segments indicated in the MPD.
  • Splice Point A point in media content where its stream may be switched to the stream of another content.
  • MPD Generator A functional entity that returns an MPD at the request of a DASH client.
  • XLink resolver A functional entity that returns at least one remote element in response to a request from a dash client.
  • FIG. 11 is a diagram illustrating an advertisement providing system of a server-based model according to an embodiment of the present invention.
  • the system of the server-based model includes a cloud 11100 and / or a receiver, and the cloud includes an ad decision server 11110 and an MPD generator 11120. ), A packager (11130) and / or a CDN / origin (Content Delivery Network (CDN) / Origin; 11140), and the receiver is a media engine (Media Engine 11300) and / or a DASH Access Client ( 11200).
  • a cloud 11100 and / or a receiver includes an ad decision server 11110 and an MPD generator 11120.
  • a packager 11130
  • CDN / origin Content Delivery Network (CDN) / Origin
  • the receiver is a media engine (Media Engine 11300) and / or a DASH Access Client ( 11200).
  • Packager 11130 receives content and queue messages and forwards content and in-band events to CDN / origin 11140.
  • CDN / origin 11140 sends the segment to the DASH client.
  • the MPD generator 11120 may receive the queue message and transmit the MPD to the DASH client.
  • the MPD generator 11120 includes an Xlink resolver.
  • the DASH client 11200 receives the MPD and segment and sends xlink to the xlink resolver.
  • the xlink resolver communicates with the advertisement determination server 1110 to transmit a period for the determined advertisement to the DASH client 11200.
  • the DASH client 11200 transfers 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.
  • a server-based model In a server-based model, all advertisement-related information is represented through MPDs and segments, and advertisement decisions are triggered by client requests for resources described in MPDs and MPDs.
  • the server-based model is MPD centric, with all the data needed to trigger advertising decisions concentrated in MPD.
  • the ad break location is unknown at the time of MPD generation, but relies on the MPD update function.
  • FIG. 12 illustrates an advertisement providing system of an app based model according to an embodiment of the present invention.
  • the app represents an application.
  • the application may be executed at the user end device or outside the user side device.
  • An application can be a collection of documents (HTML, CSS, JavaScript, etc.) constituting a self-contained enhanced or interactive service .
  • the app may be stored in the memory of the receiver to be operated by a processor or may be operated on an app browser.
  • App-based model system is an ad decision server (ad decision server) (12010), MPD generator (MPD generator) 12020, packager (12030), Origin (12040), An application (App 12050), a dash client (main content) 12060 for main content, and a dash client (ads) 12070 for advertising.
  • the application 1250 may include an Ad Management Module.
  • a receiver can run at least one dash client and an app.
  • at least one dash client and app are included in the receiver, and other configurations may be located outside the receiver.
  • Packager 12130 receives content and queue messages and delivers content and events to origin 1204.
  • the MPD generator 12020 may receive the queue message and transmit the MPD to the DASH client.
  • Origin 12040 sends the segment and the MPD to the DASH client.
  • the dash client 12060 delivers the segment and the event to the app 1520 for the main content.
  • the dash client 12070 for advertising delivers the segment and the event to the app (12050).
  • the app 1150 may obtain the MPD or segment by passing the MPD URL to each dash client.
  • the main content dash client 12060 may receive the MPD and the segment for the main content and deliver it to the app 1250.
  • the ad dash client 12070 can receive the MPD and segment for the advertisement and deliver it to the app 1250.
  • the advertisement management module included in the app may communicate with an external advertisement determination server 12010 using the received MPD and segment. In this case, information according to SCTE 130 / VST may be transmitted and received.
  • the app may deliver the MPD URL for the determined advertisement to the ad dash client and / or main content dash client.
  • the main content dash client and the advertisement dash client may present the main content and the corresponding advertisement at an appropriate time.
  • the MPD generator 11120 includes an Xlink resolver.
  • the DASH client 11200 receives the MPD and segment and sends xlink to the xlink resolver.
  • the xlink resolver communicates with the advertisement determination server 1110 to transmit a period for the determined advertisement to the DASH client 11200.
  • the DASH client 11200 transfers 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.
  • a server-based model all communication with the dash client and the ad decision service can be performed at the server side.
  • an application running on an end device can control at least one dash client.
  • one dash client can manage one MPD associated with replaceable periods, and thus provide one presentation with a spliced advertisement.
  • the ad management module may be server side.
  • the app-based model may allow a plurality of dash clients to separately manage a plurality of MPDs for advertisements and content. And their plurality of presentations can be switched.
  • the ad management module is located at the receiver side.
  • Server-based ad insertion mechanisms can provide a more seamless / seamless transition.
  • the advertisement management module exists at the receiver side. This is because storing personal information for the target advertisement on the receiver side may have an advantage in security.
  • the target advertisement may be possible even in a broadcast-only and no broadband connection.
  • the receiver and application can identify the period for the target (dynamic) advertisement and resolve the Xlink. Receivers and applications can determine target advertisements and manage / update MPDs. Receivers and applications can control the content cache and execute splices to play media presentations.
  • FIG 13 illustrates an advertisement providing system according to an embodiment of the present invention.
  • the broadcast system for providing an advertisement includes a receiver 13100 and a broadcaster 13200.
  • the receiver 13100 may include an Ad Management Module 13110, an Ad Metadata Storage 13120, a PDI Storage (PDI) Personalization Demographic Information (PDI) 13130, a Local Xlink Resolver; 13140, a DASH Access Client 13150, a Display 13160, a Media Decoder 13170, a Buffer 13180, or a Tuner 13190. can do.
  • the broadcaster 13200 may include at least one block of an MPD generator 13210, a packer 13220, or a CDN / Origin 13230.
  • a DASH accessor client may be referred to as a dash client.
  • the MPD generator 13210 may not include an Xlink resolver communicating with an Ad Decision Server 13200.
  • the receiver 13100 may tune the tuner 13190 to receive a broadcast signal, and buffer the received signal / data in the buffer 13180.
  • the receiver 13100 may deliver the received MPD segment to the DASH access client 13150.
  • the receiver can store the S-TSID with filtering Criteria in the advertisement metadata storage 13120.
  • the receiver 13100 can deliver the content segment to the media decoder 13170 using the DASH access client 13150.
  • the media decoder 13170 may decode the received content segment and deliver it to the display 13160.
  • the receiver may not include a display 13160, and the display 13160 may correspond to an external display connected to the receiver.
  • the receiver 13150 can find the xlink for the advertisement using the DASH access client.
  • the receiver may forward a Target Ad Period (TAP) request to the local Xlink resolver 13140 using the DASH access client.
  • the receiver may transmit a TA (Target Ad) request to the advertisement management module 13100 using the local Xlink resolver 13140.
  • the advertisement management module 13110 can request filtering criteria and (7) receive filtering crypto from AD metadata storage 13120.
  • the advertisement management module 13110 may request PDI from the PDI storage 13130 and (9) receive the PDI.
  • the PDI is personalization information and may include characteristic information about a user who uses the receiver.
  • the advertisement management module 13110 may determine the target advertisement using filtering criteria and PDI.
  • the advertisement management module 13110 may deliver the determined target advertisement information to the local Xlink resolver 13140.
  • the local Xlink resolver 13140 may deliver the targeted advertisement period to the DASH access client.
  • the DASH Access Client 13150 may update the MPD (Period), and (14) the DASH Access Client 13150 may forward the advertising segment and timing information to the media decoder. Accordingly, the media decoder 13170 may switch and provide an Ad segment at a corresponding timing between the contents.
  • FIG 14 illustrates an advertisement providing system according to another embodiment of the present invention.
  • the broadcast system for providing an advertisement includes a browser 14100, a receiver 14200, and a broadcaster 14300.
  • a description overlapping with the description of FIG. 13 is not repeated.
  • the browser 14100 runs / includes an application, and the application includes an advertisement management module 14110.
  • the application running in the browser may be a web-based application or a web application.
  • 14 is characterized in that the advertisement management module included in the receiver in FIG. 13 is included in a web-based application running in a browser.
  • the mechanism of providing the target advertisement is identical to the embodiment of FIG. 13, except that the operation of the advertisement management module that is requested / processed in the receiver is performed through communication with the app of the browser.
  • an app running in a browser may be shown separately from the receiver. However, this is illustrated from a functional point of view, and the app can be executed at the receiver. That is, the receiver performs processing of the receiver, and some processing can be performed by an app running on the receiver.
  • the application may receive an Xlink for the advertisement and return targeted advertisement information using filtering criteria and personal information (PDI).
  • the target advertisement information may be link information or period information about the target advertisement.
  • FIG 15 illustrates an advertisement providing system according to another embodiment of the present invention.
  • the broadcast system for providing an advertisement includes a browser 15100, a receiver 15200, and a broadcaster 15300.
  • a browser 15100 a browser 15100
  • a receiver 15200 a broadcaster 15300.
  • FIG. 15 the description overlapping with the description of FIG. 13 or FIG. 14 will not be repeated.
  • the browser 15100 runs / includes an application, which includes an advertisement management module 15110 and a local Xlink resolver 15120.
  • the application can be a web-based application.
  • the embodiment of FIG. 15 is characterized in that the advertisement management module included in the receiver in FIG. 13 is included in a web-based app running in a browser.
  • the embodiment of FIG. 15 is characterized in that the local Xlink resolver included in the receiver in FIG. 13 is included in the web-based application.
  • the mechanism for providing the target advertisement is identical to the embodiment of FIG. 13 except that the operation with the advertisement management module that is requested / processed in the receiver is performed through communication with an external app.
  • the advertisement management module is included in the external app, and (5) when the receiver transmits the target advertisement request to the app, the receiver receives the target advertisement information from the app.
  • the local Xlink resolver is also included in the app, so (4) when the receiver sends a target advertisement request to the app, the receiver receives the target advertisement period from the app. That is, the app may receive Xlink information about an advertisement, determine a target advertisement, and provide an advertisement period for the target advertisement.
  • the target advertisement refers to Xlink and may be determined based on filtering criteria and PDI.
  • FIG 16 shows an advertisement providing system according to another embodiment of the present invention.
  • FIG. 16 is a diagram illustrating a system of a multichannel video programming distributor (MVDP) model.
  • MVDP multichannel video programming distributor
  • the broadcast system for providing an advertisement includes a browser 16100, a receiver 16200, and a broadcaster 16300.
  • the advertisement providing method has been described with reference to FIG. 14. That is, FIG. 16 illustrates an embodiment of receiving segments and recovery files based on the MVPD model, and the above description is applied to other advertisement providing methods.
  • the tuner receives WM content.
  • the WM client may receive the AV content and deliver the received AV content to the media decoder.
  • the WM client can then send the recovery file address to the HTTP client.
  • the HTTP client may send a recovery file request to the server and receive the recovery file according to the request. Thereafter, the description described with reference to FIGS. 13 and 14 may be applied to a method of processing an MPD and a segment and providing an advertisement.
  • FIG 17 shows an advertisement providing system according to another embodiment of the present invention.
  • FIG. 17 illustrates an embodiment in which an app decision server is included in a server-based model.
  • the broadcaster 17200 includes an ad decision server, an MPD generator, a packager, a CDN / origin, and a signaling encoder.
  • the receiver 17100 includes a DASH Access Client, a Tuner, a Buffer, a Signaling Parser, a Media Decoder, a Display, and a Local Xlink Resolver. ), PDI storage, and an application that can be run in the receiver.
  • the application may include an Ad Management Module.
  • the receiver 17100 may receive a broadcast signal through a tuner.
  • the receiver 17100 may set the tuner as the main MPD url.
  • the receiver 17100 may receive and store / buffer the main MPD using the main MPD url.
  • the local Xlink resolver of the receiver 17100 may transmit PDI information (PDIInfoFromXlink ()) from the Xlink to the app.
  • the Xlink information may include other parameter information necessary for determining the advertisement. That is, PDI information necessary for determining the corresponding target advertisement may be obtained from the Xlink information, and the local Xlink resolver may transmit the PDI information to the app.
  • the app can use the PDI information to determine which advertisement (AD) should be played. Although omitted in the order of the figure, the app may request PDI information received from the local Xlink resolver from the PDI storage and obtain necessary PDI information.
  • the filtering engine may set filtering based on the filtering criterion information.
  • the app may set an advertisement MPD URL (AdMPDurl ()) for the determined advertisement.
  • the app may set the MPD URL of the DASH access client as the MPD URL for the advertisement.
  • the receiver 17100 may receive the advertisement MPD (MPD (ad)) from the broadcaster 17200, and buffer / store the advertisement MPD.
  • the receiver 17100 may receive an advertisement segment for an advertisement period based on the advertisement MPD.
  • the DASH client of the receiver 17100 may receive and play the advertisement segment.
  • content data including at least one content segment and advertisement data including at least one advertisement segment may be received together and buffered or stored.
  • FIG 18 illustrates an advertisement providing system according to another embodiment of the present invention.
  • FIG. 18 is a server-based model to which a broadcaster app is added, and unlike FIG. 17, an app decision server and an Xlink resolver are not included in a broadcaster's side.
  • the broadcaster 18200 may include an MPD generator, a packager, and a CDN / origin.
  • the receiver 18300 includes a DASH Access Client, a Tuner, a Buffer, a Media Decoder, a Display, a Local Xlink Resolver, and a PDI Storage. ) May be included.
  • the application 18100 operates, and the application may include an Ad management module and Ads metadata.
  • Application 18100 may be stored in a receiver and driven by the receiver.
  • the application 18100 may be an app application running in a browser.
  • the broadcaster may not include an advertisement determination server, and the MPD generator may not include the Xlink resolver.
  • the advertisement metadata may be received as NRT, broadband or broadcast and stored in the app.
  • the receiver may receive the MPD and the segment through the tuner, and the received MPD and the segment may be delivered to the dash client.
  • the dash client can deliver the content segment to the media decoder to provide the media presentation.
  • the dash client can find Xlink information.
  • the Xlink information may be an advertisement-related Xlink.
  • the dash client may forward a Target Ad Period (TAP) request to the local Xlink resolver.
  • TAP Target Ad Period
  • the dash client can forward the TAP request to the local Xlink resolver if an advertisement related Xlink is found.
  • the local Xlink resolver may send a TA (Target Ad) request to the application.
  • TAP Target Ad Period
  • the application may send a PDI request to the receiver.
  • the application may receive the PDI stored in the PDI storage of the receiver.
  • the application may determine which advertisements to provide to the user.
  • the application may send targeted advertisement information for the determined advertisement to the receiver (local Xlink resolver).
  • the local Xlink resolver may deliver the targeted Ad Period to the dash client.
  • the dash client can update the MPD.
  • the receiver may receive the MPD and / or period for the advertisement, and (12) the dash client may deliver the received advertisement segment and timing to the media decoder to provide the advertisement.
  • the advertisement determination server is not included in the broadcaster side. Therefore, when there is no broadband connection, the local advertisement management module of the receiver may perform advertisement determination.
  • the local Xlink resolver is the interface between the application and the DASH Access Client.
  • FIG 19 shows an advertisement providing system according to another embodiment of the present invention.
  • FIG. 19 is a server-based model to which a broadcaster app is added, and unlike FIG. 18, the advertisement metadata is stored in a separate advertisement metadata server.
  • the broadcaster 19200 may include an MPD generator, a packager, and a CDN / origin.
  • the receiver 19300 includes a DASH Access Client, Tuner, Buffer, Media Decoder, Display, Local Xlink Resolver, and PDI Storage. It may include.
  • the application 19100 operates, and the application may include an ad management module.
  • the AD metadata is not included in the app, but may be included in a separate AD metadata server 19400.
  • the receiver can receive the MPD and segment through the tuner. (2) The receiver can send the advertising information to the application. (3) The dash client can deliver the content segment to the media decoder to provide the media presentation. (4) The dash client can retrieve the Xlink. The Xlink retrieved may be an advertisement-related Xlink. (5) The dash client may forward a Target Ad Period (TAP) request to the local Xlink resolver. (6) The local Xlink resolver may send a TA (Target Ad) request to the application.
  • TAP Target Ad Period
  • the local Xlink resolver may send a TA (Target Ad) request to the application.
  • the application may send a PDI request to the receiver.
  • the application may receive the PDI stored in the PDI storage of the receiver.
  • the application may send an advertisement metadata request to the advertisement metadata server.
  • the application may receive advertisement metadata from an advertisement metadata server.
  • the application may determine an advertisement to present to the user based on the PDI and the advertisement metadata.
  • the application may send the targeted advertisement information (Targeted Ad Info) for the determined advertisement to the receiver (local Xlink resolver).
  • the local Xlink resolver may deliver the targeted advertising period to the dash client.
  • the dash client can update the MPD. That is, the dash client may receive the MPD and / or period for the advertisement, and (15) the dash client may deliver the received advertisement segment and timing to the media decoder to provide the advertisement.
  • the advertisement determination server is not included in the broadcaster side. Since the local advertisement management module of the receiver makes the advertisement decision, the security of the customer can be improved.
  • the local Xlink resolver is the interface between the application and the DASH Access Client.
  • FIG 20 illustrates an advertisement providing system according to another embodiment of the present invention.
  • the broadcaster 20200 may include an MPD generator, a packager, and a CDN / origin.
  • the receiver 19300 includes a DASH Access Client, a Tuner, a Buffer, a Media Decoder, a Display, a Local Xlink Resolver, and a PDI Storage. ) May be included.
  • the application 20100 operates, and the application 20100 may include an ad management module.
  • the AD metadata is not included in the app but may be included in a separate AD metadata server 20400.
  • the MPD may not be separated into an MPD for main content and an MPD for advertisement. That is, the MPD may include at least one of period information into which an advertisement may be inserted, Xlink information about an advertisement that may be inserted into a corresponding period, or AssetIdentifier information about the advertisement. Therefore, in the embodiment of FIG. 20, the same MPD update as the above-described embodiment may be omitted.
  • the receiver can receive the MPD and segment through the tuner.
  • the dash client can retrieve the Xlink.
  • Xlink may be Xlink related to advertisement.
  • the dash client may forward a Target Ad Period (TAP) request to the local Xlink resolver.
  • TAP Target Ad Period
  • the local Xlink resolver can send a TA (Target Ad) request to the application.
  • the application may send a PDI request to the receiver.
  • the application may receive the PDI stored in the PDI storage of the receiver.
  • the application may send an advertisement metadata request to the advertisement metadata server.
  • the application may receive advertisement metadata from an advertisement metadata server.
  • the application may determine an advertisement to present to the user based on the PDI and the advertisement metadata.
  • the application may send targeted advertisement information about the determined advertisement to the receiver (local Xlink resolver).
  • the local Xlink resolver may deliver the targeted advertising period to the dash client.
  • the receiver may receive the advertising segment and deliver the received advertising segment to the dash client.
  • the dash client may deliver the received advertisement segment and timing information to the media decoder to provide an advertisement.
  • the advertisement determination server is not included in the broadcaster side. Since the local advertisement management module of the receiver makes the advertisement decision, the security of the customer can be improved.
  • the local Xlink resolver is the interface between the application and the DASH Access Client.
  • FIG 21 illustrates an advertisement providing system according to another embodiment of the present invention.
  • a broadcaster may include an MPD generator, a packager, and a CDN / origin.
  • Receiver includes DASH Access Client, Tuner, Buffer, Media Decoder, Display, Local Xlink Resolver, PDI Storage can do.
  • an application operates, and the application may include an advertisement management module and an advertisement database.
  • the AD metadata is not included in the app, but may be included in a separate AD metadata server. 21 illustrates a case in which a receiver is broadband connected. That is, the embodiment of FIG. 21 is an embodiment in which not only a browser but also a receiver side function is broadband connected.
  • the MPD generator includes an Xlink resolver.
  • the broadcaster's xlink resolver may find a default advertisement.
  • the broadcaster's xlink resolver may obtain a default advertisement ID from the advertisement metadata server.
  • the advertisement metadata server may have an advertisement ID for each advertisement and information about the advertisement.
  • the broadcaster's xlink resolver may resolve the xlink with default advertisement information.
  • the broadcaster's xlink resolver may resolve the xlink to insert xlink information about the advertisement in the MPD.
  • the receiver may receive the MPD and / or segment. (5) The receiver may receive a default advertisement period. (6) The receiver may deliver the received MPD and segment to the dash client. (7) The dash client can find Xlinks. Xlink may be Xlink related to advertisement. (8) The dash client may send default advertisement information to the application.
  • the application may send a PDI request to the receiver.
  • the receiver may transmit the requested PDI from the PDI storage to the application.
  • the application may determine the advertisement using the advertisement information and the PDI in the AD database.
  • the application may send an advertisement metadata request to the advertisement metadata server.
  • the application may receive the requested advertisement metadata from the advertisement metadata server.
  • the application may send the target advertisement information (Ad URL and Ad ID) to a receiver (local xlink resolver).
  • the local Xlink resolver may resolve the Xlink with the target advertisement information.
  • the resolved Xlink may be delivered to the dash access client.
  • the dash client can update the MPD.
  • the dash client may transmit the targeted advertisement URL and the targeted advertisement ID to the advertisement metadata server.
  • the dash client may receive the targeted advertising period from the advertising metadata server.
  • the receiver may receive the advertisement segment and the timing based on the received advertisement period, and deliver the advertisement segment and the timing to the media decoder to provide the target advertisement.
  • the advertisement determination server is not included in the broadcaster side. Since the local advertisement management module of the receiver makes the advertisement decision, the security of the customer can be improved.
  • the local Xlink resolver is the interface between the application and the DASH Access Client.
  • FIG 22 illustrates an advertisement providing system according to another embodiment of the present invention.
  • a broadcaster may include an MPD generator, a packager, and a CDN / origin.
  • Receiver includes DASH Access Client, Tuner, Buffer, Media Decoder, Display, Local Xlink Resolver, PDI Storage can do.
  • an application operates, and the application may include an advertisement management module and an advertisement database.
  • AD metadata is not included in the app, it may be included in a separate AD metadata server.
  • the embodiment of FIG. 22 illustrates a case where a receiver side function is broadband disconnected.
  • the MPD generator includes an Xlink resolver.
  • the broadcaster's xlink resolver may find a default advertisement.
  • the broadcaster's xlink resolver may obtain a default advertisement ID from the advertisement metadata server.
  • the advertisement metadata server may have an advertisement ID for each advertisement and information about the advertisement.
  • the broadcaster's xlink resolver may resolve the xlink with default advertisement information.
  • the broadcaster's xlink resolver may resolve the xlink to insert xlink information about the advertisement in the MPD.
  • the receiver may receive the MPD and / or segment.
  • the receiver may receive a default advertisement period.
  • the receiver may receive a plurality of advertisement information as well as the default advertisement period. That is, the receiver may buffer / store a plurality of advertisement information that can be inserted as well as a default advertisement period.
  • the broadcaster may transmit a plurality of advertisement information through broadcast.
  • the receiver may deliver the received MPD and segment to the dash client.
  • the dash client can find Xlinks.
  • Xlink may be Xlink related to advertisement.
  • the dash client may send default advertisement information to the application.
  • the application may send a PDI request to the receiver.
  • the receiver may transmit the requested PDI from the PDI storage to the application.
  • the application may determine the advertisement using the advertisement information and the PDI in the AD database.
  • the application may send an advertisement metadata request to the advertisement metadata server.
  • the application may receive the requested advertisement metadata from the advertisement metadata server.
  • the application may send the target advertisement information (Ad URL and Ad ID) to a receiver (local xlink resolver).
  • the local Xlink resolver may resolve the Xlink with the target advertisement information.
  • the resolved Xlink may be delivered to the dash access client.
  • the dash client may deliver the advertisement segment and timing information to the media decoder to provide the target advertisement.
  • the dash client can update the MPD.
  • the receiver may receive the advertisement segment and the timing based on the received advertisement period, and deliver the advertisement segment and the timing to the media decoder to provide the target advertisement.
  • the advertisement determination server is not included in the broadcaster side. Since the local advertisement management module of the receiver makes the advertisement decision, the security of the customer can be improved.
  • the local Xlink resolver is the interface between the application and the DASH Access Client.
  • FIG 23 illustrates an advertisement providing system according to another embodiment of the present invention.
  • a broadcaster may include an MPD generator, a packager, and a CDN / origin.
  • Receiver includes DASH Access Client, Tuner, Buffer, Media Decoder, Display, Local Xlink Resolver, PDI Storage can do.
  • an application operates, and the application may include an advertisement management module and an advertisement database.
  • the AD metadata is not included in the app, but may be included in a separate AD metadata server.
  • the embodiment of FIG. 23 illustrates a case in which the receiver is broadband disconnected and indicates received signaling information.
  • the MPD generator includes an Xlink resolver.
  • the broadcaster's xlink resolver may find a default advertisement.
  • the broadcaster's xlink resolver may obtain a default advertisement ID from the advertisement metadata server.
  • the advertisement metadata server may have an advertisement ID for each advertisement and information about the advertisement.
  • the broadcaster's xlink resolver may resolve the xlink with default advertisement information.
  • the broadcaster's xlink resolver may resolve the xlink to insert xlink information about the advertisement in the MPD.
  • the default advertisement information may be transmitted to the packager and transmitted through the CDN / origin.
  • the receiver may receive the MPD and / or segment.
  • the receiver may receive a default advertisement period.
  • the receiver may receive possible advertisement information as well as the default advertisement period. That is, the receiver can receive not only the default advertisement period but all advertisement information that can be inserted.
  • the broadcaster since the broadband connection is released, the receiver may not be able to receive additional metadata as broadband. Therefore, the broadcaster may transmit a plurality of advertisement information.
  • the receiver may deliver the received MPD and segment to the dash client.
  • the dash client can find Xlinks.
  • Xlink may be Xlink related to advertisement.
  • the dash client may send default advertisement information to the application.
  • the application may send a PDI request to the receiver.
  • the receiver may transmit the requested PDI from the PDI storage to the application.
  • the application may determine the advertisement using the advertisement information and the PDI in the AD database.
  • the application may send an advertisement metadata request to the advertisement metadata server.
  • the application may receive the requested advertisement metadata from the advertisement metadata server.
  • the application may send the target advertisement information (Ad URL and Ad ID) to a receiver (local xlink resolver).
  • the local Xlink resolver may resolve the Xlink with the target advertisement information.
  • the resolved Xlink and / or target advertisement information may be delivered to the dash access client.
  • the dash client can update the MPD.
  • the dash client may deliver the advertisement segment and timing information to the media decoder to provide the target advertisement.
  • the receiver may receive the advertisement segment and the timing based on the received advertisement period, and deliver the advertisement segment and the timing to the media decoder to provide the target advertisement.
  • FIG. 23 shows signaling information for transmitting filtering criterion information.
  • the filling criterion information may be included in the S-TSID and transmitted, and the signaling structure will be described later.
  • the advertisement determination server is not included in the broadcaster side. Since the local advertisement management module of the receiver makes the advertisement decision, the security of the customer can be improved.
  • the local Xlink resolver is the interface between the application and the DASH Access Client.
  • FIG 24 illustrates an advertisement providing system according to another embodiment of the present invention.
  • FIG. 24 is a server-based model without the broadcaster app, similar to the embodiment of FIG. 19. In the case of FIG. 24, the difference is that the operation of the application in FIG. 29 is performed by the advertisement management module included in the receiver.
  • an advertisement determination server of a broadcaster side is operated, and the MPD generator includes an Xlink resolver to communicate with the advertisement determination server.
  • the broadcaster 19200 may include an MPD generator, a packager, and a CDN / origin.
  • Receiver includes DASH Access Client, Tuner, Buffer, Media Decoder, Display, Local Xlink Resolver, PDI Storage and PDI Storage It may include a module (Ad Management Module).
  • AD metadata is not included in the app, but may be included in a separate AD metadata server 19400.
  • the receiver can receive the MPD and segment through the tuner. (2) The receiver can send the advertising information to the application. (3) The dash client can deliver the content segment to the media decoder to provide the media presentation. (4) The dash client can retrieve the Xlink. The Xlink retrieved may be an advertisement-related Xlink. (5) The dash client may forward a Target Ad Period (TAP) request to the local Xlink resolver. (6) The local Xlink resolver may send a TA (Target Ad) request to the application.
  • TAP Target Ad Period
  • the local Xlink resolver may send a TA (Target Ad) request to the application.
  • the application may send a PDI request to the receiver.
  • the application may receive the PDI stored in the PDI storage of the receiver.
  • the application may send an advertisement metadata request to the advertisement metadata server.
  • the application may receive advertisement metadata from an advertisement metadata server.
  • the application may determine an advertisement to present to the user based on the PDI and the advertisement metadata.
  • the application may send the targeted advertisement information (Targeted Ad Info) for the determined advertisement to the receiver (local Xlink resolver).
  • the local Xlink resolver may deliver the targeted advertising period to the dash client.
  • the dash client can update the MPD. That is, the dash client may receive the MPD and / or period for the advertisement, and (15) the dash client may deliver the received advertisement segment and timing to the media decoder to provide the advertisement.
  • a period is defined by a period element within the MPD element. Description of elements / attributes included in period elements included in FIG. 24 is as follows. A period element specifies a period's information.
  • @xlink href-Specifies a reference to a remote element that is empty or contains at least one top-level element.
  • @xlink actuate-specifies a processing instruction. May not exist if the @xlink: href attribute does not exist.
  • AdaptationSet @ bitstreamSwitching is set to 'true'fh for each adaptation set included in this cycle.
  • BaseURL Specifies the base URL used for the reference resolution and alternative URL selections. Can be provided by the ad management module included in the app.
  • SegmentBase Specifies default segment base information.
  • SegmentTemplate Specifies default segment teamplate information.
  • 26 illustrates signaling of an advertisement identifier according to an embodiment of the present invention.
  • the present invention proposes a method of using schemeURI information and value information of AssetIdentifer information.
  • AssetIdentifer pointing to period M1 in MPD is defined as schemeIdUri is “urn: org: dashif: asset-id: 2014” and value is “md: cid: EIDR: 10.5240% 2f0FFB-02CD-126E-8092-1E49-W”
  • @schemeIdUri: "urn: org: dashif: asset-id: 2014” can be used for DASH-IF extension for advertisement insertion
  • @value: MovieLabs ContentID URN is used for EIDR and And / or Ad-ID for the advertisement.
  • FIG. 27 illustrates filtering criterion information according to an embodiment of the present invention.
  • the filtering criterion information has one or more QxA Criterion, and the one or more Cryterions have a form of QIA, QBA, QSA, QTA or QAA according to the value form.
  • QxA cryterion represents the filter cryterion corresponding to the PDI question.
  • QxA cryterions include @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.
  • FIG. 28 is a view illustrating a signaling method of filtering cryptographic information according to an embodiment of the present invention.
  • FIG. 28 shows an ScrFlow element of the S-TSID described with reference to FIG. 4.
  • the filtering criterion information may be included as a lower element of the ScrFlow element.
  • a description of the elements included in the ScrFlow element and the ScrFlow element is as follows.
  • ScrFlow Source flow that is included in the LCT session and delivered
  • @minBuffSize Defines the minimum number of kilobytes requested in the receiver transport buffer for the LCT session.
  • EFDT Represents an Extended FDT instance.
  • ContentInfo additional information that can be mapped to an application service delivered in this transport session
  • the filtering criteria information shown in FIG. 26 may be included.
  • the filtering criterion may include an ID attribute and a Value attribute.
  • the same filtering criteria may be applied to all files transmitted within the LST session.
  • the FilteringCriteria element may be positioned as a child element of the SrcFlow element or the ContentInfo element included in the SrcFlow element.
  • 29 is a view illustrating a signaling method of filtering cryptographic information according to an embodiment of the present invention.
  • FIG. 29 shows the EFDT element described with reference to FIG. 28.
  • the filtering criterion information may be included as a subelement of the EFDT element. Description of the elements included in the EFDT element and the ScrFlow element is as follows.
  • EFDT Provides details of file delivery data in the form of txjstm, an Extended FDT that contains nominal FDT instance parameters.
  • FileTemplate Describes the means of generating a file URL.
  • the filtering criteria information shown in FIG. 26 may be included.
  • the filtering criterion may include an ID attribute (@ID) and a Value attribute (@value).
  • the EFDT may include a File element.
  • the same filtering criteria may be applied to all files transmitted within the LST session.
  • the FilteringCriteria element may be positioned as a child element of the EFDT element.
  • the FilteringCriteria element may be included as a child element of the File element of the EFDT element.
  • Xlink may be resolved into a file that is delivered to the broadcast channel.
  • Xlink may be used to replace an Xlink in an advertisement period with one or more periods for a target advertisement. This may be particularly useful if the receiver is not connected to a broadband network.
  • Xlink: href provides the URL to the xlink resolver.
  • xlink: href may consist of syntax such as ⁇ domain name part> / ⁇ directory path> [? ⁇ parameter>].
  • the ⁇ domain name part> / ⁇ directory path> may be a content location of a file delivered in a broadcast. If xlink is to be resolved to a period, xlink: href excluding the parameter may be the content location of the advertising period.
  • the value of the 'key' part can be 'fc' and the 'value' part can be one id of the pre-registered question id.
  • the value 'fc' of the key part indicates that this parameter provides a filtering criterion.
  • the xlink information may further include parameter information.
  • the application may perform various operations.
  • the application may obtain information or metadata as follows.
  • the application may obtain advertising information from the client server.
  • the application may obtain PDI information from PDI storage.
  • the application may obtain xlink information from the xlink resolver.
  • An application can set information or metadata as follows: The application can set the MPD URL to the dash client module. The application may update the MPD with the target advertisement period.
  • the application can communicate with an ad server.
  • the application may request the targeted advertisement with the PDI information (request targeted Ad Jaho PDI information).
  • the application may obtain target advertisement information (ID and period).
  • FIG. 30 is a flowchart illustrating a method of providing a target advertisement by a broadcast signal receiver according to an embodiment of the present invention.
  • the broadcast signal receiver may process media data and description information on the media data (S30010).
  • the media data includes at least one media segment.
  • the broadcast signal receiver may receive the advertisement data together with the media data.
  • Luminance data may also include at least one advertising segment.
  • the description information may include information about at least one period.
  • the description information MPD may include a period for providing an advertisement. This period may include advertisement related information about the advertisement.
  • the broadcast signal receiver may obtain advertisement related information included in the description information (S30020).
  • the description information may include advertisement related information, that is, xlink information about the advertisement.
  • the dash client module of the broadcast signal receiver may obtain xlink information about the advertisement.
  • the broadcast signal receiver may request this target advertisement from the app by resolving the xlink information.
  • the xlink information on the advertisement may further include parameter information.
  • the broadcast signal receiver may determine the target advertisement using the personalized data and the filtered criterion information (S30030).
  • the broadcast signal receiver may run an application through a browser.
  • the application may receive the target advertisement request and determine the target advertisement using at least one of the personalization data and the filtering criterion information.
  • the target advertisement request may include xlink information.
  • the application may provide target advertisement information or period information for the target advertisement.
  • the broadcast signal receiver may acquire target advertisement information for playing the target advertisement (S30040).
  • the target advertisement information may include period information of the target advertisement.
  • the dash client of the broadcast signal receiver may receive period information of the target advertisement from an application or a local Xlink resolver.
  • the broadcast signal receiver may decode the advertisement data based on the target advertisement information and provide the target advertisement (S30050).
  • the broadcast signal receiver may provide the target advertisement to the period by switching the media segment of the content period to the media segment of the target advertisement period.
  • one dash client can seamlessly provide media presentation by controlling ad segment change and decoding.
  • the target advertisement providing method according to the present invention may be performed based on one or a combination of a plurality of embodiments of FIGS. 13 to 24. In particular, some operations included in the embodiments of FIGS. 13 to 24 may be used in combination.
  • Each of the steps described in the above embodiments may be performed by hardware / processors.
  • Each module / block / unit described in the above embodiments can operate as a hardware / processor.
  • the methods proposed by the present invention can be executed as code. This code can be written to a processor readable storage medium and thus read by a processor provided by an apparatus.
  • the processor-readable recording medium includes all kinds of recording devices that store data that can be read by the processor.
  • Examples of the processor-readable recording medium include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like, and may also be implemented in the form of a carrier wave such as transmission over the Internet.
  • the processor-readable recording medium can also be distributed over network coupled computer systems so that the processor-readable code is stored and executed in a distributed fashion.
  • the present invention is used in the field of transmitting / receiving a series of broadcast signals.

Abstract

L'invention concerne un procédé par lequel un récepteur de signal de diffusion fournit une publicité cible. Le procédé pour fournir une publicité cible, selon un mode de réalisation de la présente invention, comprend les étapes consistant à : traiter des données de média et des informations de description sur les données de média; acquérir des informations associées à la publicité incluses dans les informations de description; déterminer une publicité cible en utilisant des données de personnalisation et des informations de critères de filtrage; acquérir des informations de publicité cible pour la reproduction de la publicité cible; et fournir la publicité cible par décodage de données de publicité sur la base des informations de publicité cible.
PCT/KR2016/007301 2015-07-07 2016-07-06 Dispositif et procédé d'émission et de réception de signal de diffusion WO2017007230A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201562189721P 2015-07-07 2015-07-07
US62/189,721 2015-07-07
US201562192538P 2015-07-14 2015-07-14
US62/192,538 2015-07-14

Publications (1)

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

Family

ID=57685820

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2016/007301 WO2017007230A1 (fr) 2015-07-07 2016-07-06 Dispositif et procédé d'émission et de réception de signal de diffusion

Country Status (1)

Country Link
WO (1) WO2017007230A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101940973B1 (ko) * 2018-08-14 2019-01-22 주식회사 디지캡 이벤트 기반 타겟 광고 시스템
US11418561B2 (en) * 2020-03-03 2022-08-16 Tencent America LLC Remote link validity interval in media streaming

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008199674A (ja) * 2008-05-07 2008-08-28 Sony Corp 受信装置
KR20090028897A (ko) * 2007-09-17 2009-03-20 (주)선연투웨이애드 디지털 양방향 티브이의 광고집행시스템을 활용한 영상단위 판매 기법 및 장치
KR20100017989A (ko) * 2006-05-12 2010-02-16 스트랜즈, 아이엔씨. 사용자 프로그램된 미디어 배달 서비스
KR20130056813A (ko) * 2011-11-22 2013-05-30 인스티튜트 포 인포메이션 인더스트리 디지털 텔레비전 상에서 광고에 대한 제품 정보를 디스플레이하기 위한 시스템 및 방법, 그리고 그 기록 매체
KR20140131487A (ko) * 2010-07-20 2014-11-13 한국전자통신연구원 스트리밍 컨텐츠 제공 장치 및 방법

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20100017989A (ko) * 2006-05-12 2010-02-16 스트랜즈, 아이엔씨. 사용자 프로그램된 미디어 배달 서비스
KR20090028897A (ko) * 2007-09-17 2009-03-20 (주)선연투웨이애드 디지털 양방향 티브이의 광고집행시스템을 활용한 영상단위 판매 기법 및 장치
JP2008199674A (ja) * 2008-05-07 2008-08-28 Sony Corp 受信装置
KR20140131487A (ko) * 2010-07-20 2014-11-13 한국전자통신연구원 스트리밍 컨텐츠 제공 장치 및 방법
KR20130056813A (ko) * 2011-11-22 2013-05-30 인스티튜트 포 인포메이션 인더스트리 디지털 텔레비전 상에서 광고에 대한 제품 정보를 디스플레이하기 위한 시스템 및 방법, 그리고 그 기록 매체

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101940973B1 (ko) * 2018-08-14 2019-01-22 주식회사 디지캡 이벤트 기반 타겟 광고 시스템
US11418561B2 (en) * 2020-03-03 2022-08-16 Tencent America LLC Remote link validity interval in media streaming

Similar Documents

Publication Publication Date Title
WO2017014586A1 (fr) Dispositif et procédé d'émission et de réception de signal de radiodiffusion
WO2016186407A1 (fr) Appareil et procédé d'émission ou de réception de signal de diffusion
WO2017204546A1 (fr) Dispositif et procédé d'émission/réception de signaux de diffusion
WO2016144072A1 (fr) Appareil et procédé pour émettre et recevoir un signal de radiodiffusion
WO2016140486A1 (fr) Appareil et procédé d'émission/réception de signal de diffusion
WO2017007192A1 (fr) Dispositif d'émission de signal de diffusion, dispositif de réception de signal de diffusion, procédé d'émission de signal de diffusion et procédé de réception de signal de diffusion
WO2016076623A1 (fr) Dispositif d'émission de signal de diffusion, dispositif de réception de signal de diffusion, procédé d'émission de signal de diffusion et procédé de réception de signal de diffusion
WO2016076569A1 (fr) Appareil de transmission de signaux de diffusion, appareil de réception de signaux de diffusion, procédé de transmission de signaux de diffusion, et procédé de réception de signaux de diffusion
WO2016060422A1 (fr) Dispositif et procédé d'émission de signal de diffusion, dispositif et procédé de réception de signal de diffusion
WO2016093576A1 (fr) Appareil de transmission de signal de radiodiffusion, appareil de réception de signal de radiodiffusion, procédé de transmission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2017007224A1 (fr) Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2017209514A1 (fr) Dispositif et procédé d'émission et de réception de signal de diffusion
WO2018101566A1 (fr) Dispositif et procédé d'émission/réception de signal de radiodiffusion
WO2016153241A1 (fr) Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion et procédé de réception de signal de radiodiffusion
WO2016060416A1 (fr) Dispositif d'émission d'un signal de diffusion, dispositif de réception d'un signal de diffusion, procédé d'émission d'un signal de diffusion, et procédé de réception d'un signal de diffusion
WO2017061792A1 (fr) Dispositif et procédé d'émission/réception de signal de diffusion
WO2016190720A1 (fr) Dispositif d'émission et de réception de signal de radiodiffusion, et procédé d'émission et de réception de signal de radiodiffusion
WO2016190662A1 (fr) Dispositif de transmission de signal de diffusion, dispositif de réception de signal de diffusion, procédé de transmission de signal de diffusion, et procédé de réception de signal de diffusion
WO2016129904A1 (fr) Appareil d'émission de signal de radiodiffusion, appareil de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2016114638A1 (fr) Appareil de transmission de signal de radiodiffusion, appareil de réception de signal de radiodiffusion, procédé de transmission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2016178549A1 (fr) Dispositif d'émission de signaux de diffusion, dispositif de réception de signaux de diffusion, procédé d'émission de signaux de diffusion, et procédé de réception de signaux de diffusion
WO2017026714A1 (fr) Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2017123044A1 (fr) Appareil et procédé pour émettre et recevoir un signal de diffusion
WO2017164595A1 (fr) Dispositif et procédé d'émission/réception de signal de diffusion
WO2016072725A1 (fr) Dispositif de transmission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé de transmission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion

Legal Events

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

Ref document number: 16821636

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16821636

Country of ref document: EP

Kind code of ref document: A1