WO2016121398A1 - Système de création de rapport d'utilisation de service - Google Patents

Système de création de rapport d'utilisation de service Download PDF

Info

Publication number
WO2016121398A1
WO2016121398A1 PCT/JP2016/000441 JP2016000441W WO2016121398A1 WO 2016121398 A1 WO2016121398 A1 WO 2016121398A1 JP 2016000441 W JP2016000441 W JP 2016000441W WO 2016121398 A1 WO2016121398 A1 WO 2016121398A1
Authority
WO
WIPO (PCT)
Prior art keywords
component
value
interval
content
path
Prior art date
Application number
PCT/JP2016/000441
Other languages
English (en)
Inventor
Sachin G. Deshpande
Original Assignee
Sharp Kabushiki Kaisha
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 Sharp Kabushiki Kaisha filed Critical Sharp Kabushiki Kaisha
Priority to CN202011056981.3A priority Critical patent/CN112261446B/zh
Priority to CN201680006278.7A priority patent/CN107211192B/zh
Priority to US15/545,022 priority patent/US10499108B2/en
Priority to CA2973328A priority patent/CA2973328C/fr
Publication of WO2016121398A1 publication Critical patent/WO2016121398A1/fr
Priority to US16/596,231 priority patent/US10945031B2/en
Priority to US17/164,127 priority patent/US11303959B2/en

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/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/262—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists
    • H04N21/26258—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists for generating a list of items to be played back in a given order, e.g. playlist, or scheduling item distribution according to such list
    • 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/442—Monitoring of processes or resources, e.g. detecting the failure of a recording device, monitoring the downstream bandwidth, the number of times a movie has been viewed, the storage space available from the internal hard disk
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04H—BROADCAST COMMUNICATION
    • H04H60/00—Arrangements for broadcast applications with a direct linking to broadcast information or broadcast space-time; Broadcast-related systems
    • H04H60/29—Arrangements for monitoring broadcast services or broadcast-related services
    • H04H60/31—Arrangements for monitoring the use made of the broadcast services
    • 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/239—Interfacing the upstream path of the transmission network, e.g. prioritizing client content requests
    • H04N21/2393—Interfacing the upstream path of the transmission network, e.g. prioritizing client content requests involving handling client requests
    • 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/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/254—Management at additional data server, e.g. shopping server, rights management server
    • 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/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/439—Processing of audio elementary streams
    • 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
    • H04N21/4586—Content update operation triggered locally, e.g. by comparing the version of software modules in a DVB carousel to the version stored locally
    • 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/466—Learning process for intelligent management, e.g. learning user preferences for recommending movies
    • H04N21/4667—Processing of monitored end-user data, e.g. trend analysis based on the log file of viewer selections
    • 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/47—End-user applications
    • H04N21/488—Data services, e.g. news ticker
    • H04N21/4884—Data services, e.g. news ticker for displaying subtitles
    • 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/83—Generation or processing of protective or descriptive data associated with content; Content structuring
    • H04N21/835—Generation of protective data, e.g. certificates
    • H04N21/8355—Generation of protective data, e.g. certificates involving usage data, e.g. number of copies or viewings allowed
    • H04N21/83555—Generation of protective data, e.g. certificates involving usage data, e.g. number of copies or viewings allowed using a structured language for describing usage rules of the content, e.g. REL
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N5/00—Details of television systems
    • H04N5/222—Studio circuitry; Studio devices; Studio equipment
    • H04N5/262—Studio circuits, e.g. for mixing, switching-over, change of character of image, other special effects ; Cameras specially adapted for the electronic generation of special effects
    • H04N5/278—Subtitling

Definitions

  • the present disclosure relates generally to a system for service usage reporting.
  • a video service is capable of sending audio, visual, closed caption, application, and other data content to a receiving device.
  • the receiving device typically presents one or more of the audio, visual, closed caption, application, and other data content to the viewer, such as on a television device.
  • the viewer would like to use their mobile device, such as a mobile phone, to interact with the video content.
  • how to most effectively interact with the audiovisual content on the receiving device using the mobile phone tends to be problematic due to synchronization issues.
  • the viewer may want to receive audiovisual content on a receiver such as a television device.
  • the user may want to receive adjunct associated content on a second screen, e.g. a mobile device such as a smartphone or a tablet.
  • the content received on the second screen device may be same as alternate content associated with the audiovisual content being received on the television.
  • the user may typically like these two contents be presented on the primary and second screen device in a synchronized manner.
  • the content received on the second screen device may be alternative components (e.g. alternative camera angle) not currently presented on the primary device.
  • the user may typically like these two contents be presented on the primary and second screen device in a synchronized manner.
  • the term companion device may be used for the second screen device.
  • One embodiment of the present invention discloses a method for reporting information, the method comprising: reporting the information including component; wherein the component is comprised of a component type, a component role, a component name, a component ID and time interval information, wherein the component type with a value of 0 indicates an audio component, the component type with a value of 1 indicates a video component, the component type with a value of 2 indicates a closed caption component, the component type with a value of 3 indicates an application component, and the component type with a value of 5 to 255 are reserved, the component role presents a role or kind of the component, the component name indicates a string representing a human name of the component, the component ID indicates a string representing a component identifier, and the time interval information includes a start time and an end time, wherein the start time is a date time at the beginning of the event and an interval of the start time begins when display of this content component begins and the value of the interval of the start time is not less than the value of the start time of this interval instance, and the end
  • FIG. 1 illustrates a video system.
  • FIG. 2 illustrates a data server and a receiver.
  • FIG. 3 illustrates a consumption data unit.
  • FIG. 4 illustrates a consumption data message.
  • FIG. 5 illustrates a logical structure of a consumption data message.
  • FIG. 6 illustrates a logical structure of a component element of a consumption data message.
  • FIG. 7 illustrates a component and viewing types.
  • FIG. 7A illustrates view intervals and components.
  • FIG. 7B illustrates view intervals, components, and delivery paths.
  • FIG. 8 illustrates a deviceType attribute.
  • FIG. 9 illustrates an alternative deviceType attribute.
  • FIG. 10 illustrates another alternative deviceType element.
  • FIG. 11 illustrates a deliveryPath attribute.
  • FIG. 12 illustrates an alternative deliveryPath attribute.
  • FIG. 13 illustrates another alternative deliveryPath element.
  • FIG. 14 illustrates a component element.
  • FIG. 15 illustrates a consumption data message logical structure
  • FIG. 16(1) illustrates a Java Script Object Notation (JSON) schema
  • FIG. 16(2) illustrates a Java Script Object Notation (JSON) schema
  • FIG. 16(3) illustrates a Java Script Object Notation (JSON) schema
  • FIG. 16(4) illustrates a Java Script Object Notation (JSON) schema
  • FIG. 17 illustrates a portion of XML schema
  • FIG. 18(1) illustrated a XML schema
  • FIG. 18(2) illustrated a XML schema
  • FIG. 18(3) illustrated a XML schema
  • the system includes a broadcasting system 100 that provides a source of audiovisual (video and/or audio and/or closed caption and/ or other data and/ or applications) content.
  • the audiovisual content may be provided in any suitable manner and using suitable standards, such as for example, MPEG-2, MPEG-4 or ATSC.
  • the broadcasting system may be provided from a broadcasting antenna, a cable, a network based audiovisual source, a compact disk, a hard drive, a digital video disc, and/or an Internet based audiovisual source.
  • the broadcasting system 100 may provide the content through any suitable broadcast network 110.
  • the system includes a broadband server system 105 that provides a source of audiovisual (video and/or audio and/or closed caption and/ or other data and/ or applications) content.
  • This audiovisual content may be also be provided in any suitable manner and using suitable standards, such as for example, MPEG-2, MPEG-4 or ATSC.
  • the broadband server system may be provided from an Internet or over the top or network based audiovisual source audiovisual source.
  • the broadband server system 105 may provide the content through any suitable broadband network 115.
  • a receiver 120 receives the audiovisual content together with any other data provided with the audiovisual content, such as digital data, data services, or otherwise.
  • the receiver may receive some of the content components from broadcasting system via broadcast network.
  • video component may be received in this manner from broadcasting system via broadcast network.
  • the receiver may receive some of the content components from broadband server system via broadband network.
  • audio component may be received in this manner from broadband server system via broadband network.
  • the receiver 120 generally referred to as a primary device, is preferably configured to receive the type of content being provided there to.
  • the receiver may be, for example, a television, a laptop, a tablet, a phone, or any other device suitable to present the audiovisual content to a viewer.
  • the receiver may be typically in a user’s home.
  • the receiver 120 may be a Usage Reporting-Capable Receiver.
  • the receiver may likewise communicate with another display device 130, generally referred to as a companion device, through a home network 140.
  • the companion device may communicate directly with an outside server (e.g., broadcasting system 100 or broadband server system 105) to receive audiovisual and/ or adjunct content.
  • the home network is preferably a wireless or wired type network, such as for example, WiFi, Ethernet, 3GPP, Bluetooth, infra-red, HTTP.
  • the home network may be a local area network.
  • the primary and companion devices may be inside a user’s home. In other cases, the home network may be an office environment.
  • the companion device may include, for example, a mobile phone, a mobile tablet, a laptop, a computer, or other display device.
  • the receiver may simultaneously communicate with a plurality of companion devices 130. Additionally one companion device may communicate simultaneously with multiple primary devices 120.
  • the primary device may be called a first screen device.
  • the companion device may be called a second screen device.
  • the terms primary device and first screen device and receiver may be used interchangeably.
  • the terms second companion device and second screen device may be used interchangeably.
  • the primary device 120 may be capable of providing information to the companion device 130.
  • the companion device 130 may provide information to the primary device 120.
  • the broadcasting system 100 may be capable of providing information to the receiver 120.
  • the receiver 120 may provide information to the broadcasting system 100.
  • the broadcasting system 100 may be capable of providing information to the companion device 130.
  • the companion device 130 may provide information to the broadcasting system 100.
  • the broadband server system 105 may be capable of providing information to the receiver 120.
  • the receiver 120 may provide information to the broadband server system 105.
  • the broadband server system 105 may be capable of providing information to the companion device 130.
  • the companion device 130 may provide information to the broadband server system 105.
  • the information may include, for example, audio and/or visual and/or data content and/ or closed caption and/or applications.
  • the receiver 120 and/or companion device 130 In many environments it is desirable for the receiver 120 and/or companion device 130 to monitor the usage of audio-visual content consumed by the user and provide information related to the consumption of the audio-visual content to the broadcasting system 100 and/or the broadband server system 105. In many environments it is desirable for the receiver 120 and/or companion device 130 to monitor the usage of data content by the user and provide information related to the consumption of the data content to the broadcasting system 100 and/or the broadband server system 105.
  • the broadcasting system 100 may include a broadcasting server and/or a data server.
  • the receiver 120 and/or companion device 130 may be a usage reporting capable receiver.
  • the broadband server system 105 may include a broadband server and/or a data server.
  • the system may be generalized as a service usage data server 200 that provides audio-visual content together with auxiliary data, if desired, and a usage reporting capable receiver 210 that provides data to the data server 200.
  • the receiver 210 manages functions related to service consumption data collection, storage, and/or transmission to the data server 200.
  • the data server 200 in addition to the capability of providing audio-visual-data services, include data gathering agents and usage report generation.
  • the data server 200 may include one or more individual servers, as desired.
  • each CDU 300 identifies an interval during which the channel was viewed 310.
  • Such a CDU may include, for example, a channel identifier 320, a time the viewing started 330, and a time the viewing ended 340.
  • any triggered declarative objects 350 may also record the intervals during which the TDOs are active (whether on a primary device or a “second screen” device) 360, including a TDO identifier 370, a time the TDO started being active 380, and a time it stopped being active 390.
  • a triggered declarative object may be an application.
  • a triggered declarative object may be a webpage or a resource accessed via a uniform resource locator (URL).
  • URL uniform resource locator
  • each CDU may capture an interval during which the service was selected.
  • Such a CDU may include a service identifier, a time the interval started, a time the interval ended, and identifiers of the NRT content items presented during the interval.
  • events logged into a CDU may correspond to usage intervals of no less than X seconds (or other suitable time).
  • events logged into a CDU may correspond to usage intervals of no less than Y seconds.
  • an A/V channel or NRT service remains selected for less than X seconds, as an example, that event is not reported, and if a TDO is active for less than Y seconds, as an example, that event is not reported.
  • the precision and accuracy of start times and end times in the CDUs should be within Z second(s). In an example case the value of X may be 10 seconds, value of Y may be 5 seconds and value of Z may be 1 second.
  • CDM the fundamental data structure used to transmit CDUs from the receiver 210 to the data server 200 may be referred to as a consumption data message 400, referred to herein as “CDM”.
  • a CDM may contain data for a single service, or it may contain data for multiple services in the case that data for multiple services is being reported to the same data server.
  • the CDM may be hierarchically divided into three parts to reduce the amount of data that is transmitted:
  • the first part contains a “Report Header” fields 410 that are common to all virtual channels and services and all consumption data. This part is preferably sent only once in the transmission session.
  • the second part contains “Service Identifier” fields 420 that are common to all consumption data associated with a single virtual channel or NRT service. This part is preferably sent once for each channel or service included in the report.
  • the third part contains the individual consumption data records 430. This part is preferably sent once for each time interval when an audio-visual channel is being viewed or an NRT service is selected.
  • a CDM may be an XML document containing a “CDM” root element that conforms to the definition in the XML schema that has namespace http://www.atsc.org/XMLSchemas/iss-cdm-1 (as an example).
  • a consumption data message 500 This consists of elements and attributes with their cardinality, data type used for representing the elements and attributes and their description.
  • a protocol Version field 510 contains the major and minor protocol versions of the syntax and semantics of the CDM 500, coded as hexadecimal values each in the range 0x0 to 0xF.
  • the major protocol value may be in the four most significant bits of the field.
  • a change in the major version level indicates a non-backward-compatible level of change.
  • the initial value of this field may be 0.
  • the value of this field may be incremented by one each time the structure of the CDM is changed in a non-backward compatible manner from a previous major version.
  • the second number is the file minor version, which may represent the minor version of the syntax and semantics of the CDM.
  • a change in the minor version level for each value of the first number may indicate a backward-compatible level of change within that major version.
  • the initial value is 0.
  • the value of this field may be incremented by one each time the structure of the CMD is changed in backward-compatible manner from a previous minor change (within the scope of a major revision).
  • An AVChannel element 520 contains the list of zero or more elements describing activity intervals based on content delivered continuously.
  • a channelNum 522 is a 16-bit hexBinary field that may contain major and minor channel numbers. If these numbers are not determinable, the value may be set to 0xFFFF.
  • a serviceType 524 is a value of the field service_type that is (or was - for time shifted content) present in a virtual channel table for the instance being reported.
  • a ViewInterval 530 is one or more periods of display of content for the corresponding channelNum 522.
  • a startTime 532 is a dateTime computed from a coordinated universal time (“UTC”) seconds count at the beginning of the event. An interval may begin when display of the content begins.
  • UTC coordinated universal time
  • An endTime 534 is a dateTime computed from the UTC seconds count at the end of the event.
  • An interval may end when display of the content ends.
  • An usageType 536 is an unsigned integer denoting the class of usage.
  • the usageType 536 may be defined as follows:
  • a timeShift 538 is an unsigned integer 0 or 1, with 1 indicating that the content has been time shifted.
  • a viewStartTime 540 is a dateTime computed from the UTC seconds count at the beginning of the event. An interval may end when display of the content begins.
  • a viewEndTime 542 is a dateTime computed from the UTC seconds count at the end of the event. An interval may end when display of the content ends.
  • a DOInterval 550 is the interval for each active declarative object.
  • a startTime 554 is a dateTime computed from the UTC seconds count at the beginning of the event. An interval may begin when display of the content begins. The value may not be less than the value of startTime 532 of this ViewInterval 530 instance.
  • An endTime 556 is a dateTime computed from the UTC seconds count at the end of the event. An intervals may end when display of the content ends. The value may not be greater than the value of endTime 534 of this ViewInterval 530 instance.
  • a NRTService 560 element contains the list of zero or more elements describing rendering of previously obtained files.
  • a serviceID 570 is a 16-bit hexBinary field that may contain a service_id or files, or 0xFFFF for rendering periods for any other files from any other source.
  • a NRTInterval 580 is one or more periods of display of a NRT service 560.
  • a startTime 582 is a dateTime computed from the UTC seconds count at the beginning of the event. An interval may begin when display of the content begins.
  • An endTime 584 is a dateTime computed from the UTC seconds count at the end of the event.
  • An interval may end when display of the content ends.
  • a NRTItem 586 is an interval for each item in the NRT service being rendered.
  • a contentItemId 590 is a string which may contain the contents of the content_name_text() representing the identifier for the item.
  • a startTime 592 is a dateTime computed from the UTC seconds count at the beginning of the event. An interval may begin when display of the content begins. The value may not be less than the value of startTime 582 of this ViewInterval 530 instance.
  • An endTime 590 is a dateTime computed from the UTC seconds count at the end of the event.
  • An interval may end when display of the content ends. The value may not be greater than the value of endTime 584 of this ViewInterval 530 instance.
  • the transmission of the CDMs may be performed in any suitable manner.
  • the URL to be used for transmitting CDMs may be provided by the broadcaster via suitable commands.
  • the broadcaster may decide the granularity of the destination addresses, that is, one destination address URL per service, one per a set of services, one for an RF multiplex, one for a region, and/or one for a nation. This is not necessarily explicitly signaled; rather the same URL may be repeated for each service when the scope is broader than a single service.
  • the receiver 210 When the receiver 210 is prepared to transmit a CDM to a data server 200, it may issue an HTTP PUT request to the server, with the CDM in the body of the request. In another embodiment when the receiver 210 is prepared to transmit a CDM to a data server 200, it may issue an HTTP POST request to the server, with the CDM in the body of the request. In another embodiment When the receiver 210 is prepared to transmit a CDM to a data server 200, it may issue an HTTP PATCH request to the server, with the CDM in the body of the request. In another embodiment, when the receiver 210 is prepared to transmit a CDM to a data server 200, it may use WebSOCKET protocol to communicate to the server, with the CDM in the body of the request.
  • the receiver may maintain a “date of last” time record which is accessible by TDOs for that service. If a week elapses after the last report, the URCR may transmit the CDM for that interval with the CDUs for each covered service, or when the allocated CDU storage reaches a level of 80% full, whichever occurs first.
  • a CDM If a CDM is not successfully transmitted due to a failure mode, it should remain stored, and it should be retransmitted as soon as the failure mode is rectified.
  • the receiver 210 should default to the opt-in state for usage data reporting.
  • the receiver may disclose to the consumer that generic usage data will be reported unless they opt out on a service provider by service provider basis.
  • the Usage Reporting-Capable Receiver (URCR) may report usage data for a given service provider unless the user has opted out of the usage reporting functions for that service provider.
  • the receiver should permit the user to see what services they have opted into, and to change the state of any opt-in/opt-out status.
  • the receiver may retain opt-in/opt-out choices through loss of power to the unit.
  • the user interface offering the opt-in/opt-out choice is preferably presented during the service authorization process.
  • an authorization session may be used with TDO-controlled questions and answers. The receiver preferably does not directly report any such answers, with such being reported by the TDO.
  • the system should enable service usage measurement and reporting for individual content components within a given service.
  • more particularized information may be provided to the data server, which identifies particular characteristics of the available audio, visual, closed caption, data, and application content that are selected or otherwise used by the viewer. In particular, this permits an indication of the component for which the usage report is reported.
  • the receiver may identify a particular audio component from a plurality of audio components (e.g., different languages or different tracks) to be reported to the data server.
  • the receiver may identify a particular video component from a plurality of video components (e.g., different video views) to be reported to the data server.
  • a component element 600 may be included in the CDM 500 which provides the usage reporting for individual content components.
  • a Component 600 has a content component type, role, name, ID, and time interval information.
  • a componentType 610 indicates the type of component 600.
  • the values for componentType 610 may be, for example, as follows:
  • a componentRole 620 may be a string representing the role or kind of the component’s role/ kind. The role/ kind is described further below.
  • a componentName 630 may be a string representing the human readable name of the component.
  • a componentId 640 may be a string representing component identifier. In some embodiments this might be a URL which identifies a component.
  • a startTime 650 may be a dateTime computed from the UTC seconds count at the beginning of the event. An interval may begin when display of this content component begins. The value may not be less than the value of startTime 532 of this ViewInterval 530 instance. This ViewInterval 530 instance may be the parent of this Component element.
  • An endTime 660 may be a dateTime computed from the UTC seconds count at the end of the event. An intervals may end when display of this content component ends. The value may not be greater than the value of endTime 534 of this ViewInterval 530 instance. This ViewInterval 530 instance may be the parent of this Component element.
  • the system may identify the time intervals during which a particular component is being used. As such different components may be used during different time interval inside a viewInterval’s time interval.
  • a channel/ service usage report may include a plurality of view intervals. For example, there may be a view interval from 1:45pm to 2pm, a view interval from 2pm to 3pm, and a view interval from 3pm-3:15pm.
  • a view interval from 1:45pm to 2pm there may be a plurality of components included in the usage report therewith, such as component A (i.e., Spanish Audio), such as component B (i.e., English Closed Captioning), such as component G (i.e., main video view).
  • component A i.e., Spanish Audio
  • component B i.e., English Closed Captioning
  • component G i.e., main video view
  • component B i.e., English Closed Captioning
  • component D i.e., French Audio
  • component A i.e., Spanish Audio
  • component E i.e., Spanish Closed Captioning
  • component F i.e., alternative video view
  • a channel/ service usage report may include a plurality of view intervals (View Interval 1, View Interval 2, ... View Interval N). For example, there may be a View Interval 1 from 5 PM to 6 PM. Details about other view intervals (e.g. View Interval 2, ... View Interval N) are not shown in FIG. 7A.
  • View Interval 1 from 5 PM to 6 PM there may be a plurality of components included in the usage report therewith. Also different components may be active/ used during different time intervals within the view interval of 5 PM to 6 PM. For example a component J- Audio1 (i.e., English Audio) may be used from 5PM to 5:30 PM.
  • J- Audio1 i.e., English Audio
  • the receiver may decide (e.g. at the request of the viewer) to use component L -Audio2 (i.e. Spanish Audio) from 5:31 PM to 6:00 PM.
  • component K - Video component may be used from 5:00 PM to 6:00 PM, i.e. during the entire duration of view interval (View Interval 1 which spans 5 PM to 6 PM).
  • a closed caption component may be only intermittently used during the view interval (View Interval 1 which spans 5 PM to 6 PM).
  • component M - closed caption1 i.e., English Closed Captioning
  • component N - closed caption1 i.e., English Closed Captioning
  • FIG. 7 B further describes different delivery paths may be used for a component during a view interval for a channel/ service.
  • a channel/ service usage report may include a plurality of view intervals (View Interval 1, View Interval 2, ... View Interval N).
  • View Interval 1 from 5 PM to 6 PM. Details about other view intervals (e.g. View Interval 2, ... View Interval N) are not shown in FIG. 7B.
  • Component Y may be active/ used during different time intervals within the view interval of 5 PM to 6 PM. Details about other components (e.g. Component X, ... Component Y) are not shown in FIG. 7B.
  • a component K - Video component may be used from 5:00 PM to 6:00 PM, i.e. during the entire duration of view interval (View Interval 1 which spans 5 PM to 6 PM).
  • the component K may be delivered to the receiver via different paths as shown in FIG. 7B.
  • the component K may be delivered via terrestrial broadcast delivery path to the receiver.
  • the component K may be delivered via broadband delivery path to the receiver.
  • time and time interval may be indicated by other well-known techniques.
  • the time interval may be indicated from UTC seconds count at the beginning or end of an event or from beginning or end of some other reference point.
  • Some other similar techniques may be used for time and time interval indication in the above examples and in the semantics of various elements below.
  • the componentName 630 may be an element instead of attribute and its cardinality may be 0..N and the componentName 630 may have a language attribute which can indicate the name of the component in different languages. For example this attribute when using XML representation may be “xml:lang” attribute.
  • the Component 600 element may be a sub-element of the ViewInterval 530 element.
  • Component 600 element may be sub-element of one or more other elements.
  • the role/kind of the audio component may be one or more of the following.
  • the role/kind of the video component may be one or more of the following.
  • the role/kind of the closed caption component may be one or more of the following.
  • the role/kind of the application component may be one or more of the following.
  • the data type “unsignedByte” may instead be represented by the data type “hexBinary” In some embodiments instead of values 5 to 255 being reserved values 5 to 99 (or some other number) may be reserved.
  • values 5 to 255 may be reserved.
  • values 5 to 255 may be reserved.
  • cardinality of some of the elements may be changed. For example cardinality may be changed from “1” to “1..N” or cardinality may be changed from “1” to “0..N” or cardinality may be changed from “1” to “0..1” or cardinality may be changed from “0..1” to “0..N” or cardinality may be changed from “0..N” to “0..1”.
  • some other format e.g. JSON/ CSV/ BNF/ ABNF/ EBNF may be used for representing the same information conveyed in the XML format.
  • additional namespace qualifier may be added for an xml element/ attributes/ type.
  • a different name may be used for an element or attribute.
  • the element instead of “componentRole” the element may be called “caR” or “caRole” or something else.
  • the system should enable service usage measurement and reporting for the device (e.g., viewing device) the content is being consumed on within a given service.
  • the data server which identifies a particular device (or characteristics thereof or logical role thereof) of audio-visual content (including data, applications) that are selected or otherwise used by the viewer.
  • this permits an indication of the device for which the usage report is reported.
  • a “presentation device type” which indicates if the content is consumed on a primary device (PD) or a companion device (CD). It should be noted that primary device or a companion device are logical roles.
  • one technique to indicate if the content is consumed on a primary device or a companion device is using a Boolean data type for the device type indication.
  • a deviceType value of 0 indicates content is presented on primary device.
  • a deviceType value of 1 indicates the content is presented on companion device.
  • the deviceType maybe a sub-element or attribute of an element of CDM illustrated in FIG. 5. In one embodiment the deviceType may be an attribute of ViewInterval element illustrated in FIG. 5.
  • one technique to indicate if the content is consumed on a primary device or a companion device is using an integer / unsigned byte data type for the device type indication. This can allow device types other than primary device and companion device to be indicated in future using the device type indication reserved values.
  • a deviceType value of 0 indicates content is presented on primary device.
  • a deviceType value of 1 indicates the content is presented on companion device. Values 2 to 255 may be reserved.
  • the deviceType maybe a sub-element or attribute of an element of CDM element illustrated in FIG. 5. In one embodiment the deviceType may be an attribute of ViewInterval element illustrated in FIG. 5.
  • one technique to indicate if the content is consumed on a primary device or a companion device also includes time interval information with the device type indication.
  • a DeviceType 900 indicates a device type for the content presentation.
  • a dev 910 with a value of 0 indicates content is presented on primary device.
  • a dev 910 with a value of 1 indicates the content is presented on companion device.
  • a startTime 920 includes a dateTime computed from the UTC seconds count at the beginning of the event.
  • An interval may begin when display / presentation/ consumption of the content begins on the device indicated by the value of dev attribute. The value may not be less than the value of startTime 532 of this ViewInterval 530 instance.
  • This ViewInterval 530 instance may be the parent of this Component element.
  • An endTime 930 includes a dateTime computed from the UTC seconds count at the end of the event.
  • An interval may end when display/ presentation/ consumption of the content ends on the device indicated by the value of dev attribute. The value may not be greater than the value of endTime 534 of this ViewInterval 530 instance.
  • This ViewInterval 530 instance may be the parent of this Component element.
  • the DeviceType maybe a sub-element of CDM element illustrated in FIG. 5. In one embodiment the DeviceType may be a sub-element of ViewInterval element illustrated in FIG. 5.
  • information about the device type on which content is viewed may be indicated by extending the usage type field (e.g. @usageType illustrated in FIG. 5).
  • the usage type field as illustrated in FIG. 5 may be extended.
  • the usage type has defined values which allow indication of usage of content on main screen (no picture in picture), content on main screen with picture in picture activated with no change in main frame size, content on the small picture in picture, and/or user caused content to be rendered in less than full frame of the device.
  • a viewer is watching main content or associated content on a companion device.
  • usage types may be included, if desired:
  • the system should enable service usage measurement and reporting for the delivery path and/or distribution path that content is being consumed on within a given service.
  • more particularized information may be provided to the data server, which identifies a particular delivery path and/or distribution path of audio-visual content (including data, applications) that are selected or otherwise used by the viewer.
  • this permits an indication of the delivery path and/or distribution path for which the usage report is reported.
  • the path may be broadband and/or wireless connectivity for the content being used, which may change during the usage of such content.
  • a receiver may receive video component via broadcast network.
  • the broadcast signal may waken and the receiver may switch to getting the video component via broadband network.
  • the receiver may switch back to getting the video component from the broadcast network.
  • the receiver may be getting a video component via broadcast network and getting audio component in a alternative language via broadband network.
  • the usage reporting may be related to ‘real-time’ consumption, time-shifted consumption, and/or on-demand consumption.
  • a “deliveryPath” indicator element may be included.
  • the “deliveryPath” indicator element may be a Boolean data type
  • a deliveryPath with a value of 0 indicates terrestrial broadcast delivery.
  • a deliveryPath with a value of 1 indicates broadband delivery.
  • Other name such as “broadcast delivery” or “broadcast network” may be used instead of “terrestrial broadcast delivery”.
  • the deliveryPath attribute may be an attribute of ViewInterval element as illustrated in FIG. 5.
  • the deliveryPath maybe a sub-element or attribute of an element of CDM element as illustrated in FIG. 5.
  • one technique to indicate delivery path is using an integer / unsigned byte data type for the delivery path indication. This can allow delivery paths other than terrestrial broadcast delivery and broadband delivery to be indicated in future using the device type indication reserved values.
  • a deliveryPath with a value of 0 indicates terrestrial broadcast delivery.
  • a deliveryPath value of 1 indicates broadband delivery.
  • a deliveryPath value of 2 indicates local delivery on home network.
  • a deliveryPath value of 3 to 255 may be reserved.
  • a deliveryPath with a value of 2 indicates delivery (of continuous component) from a primary device (PD) to companion device (CD) on a network.
  • the deliveryPath attribute may be an attribute of ViewInterval element as illustrated in FIG. 5.
  • the deliveryPath maybe a sub-element or attribute of an element of CDM element as illustrated in FIG. 5.
  • one technique for the delivery path indication may include time interval information with the delivery path indication. Since the delivery path may change during a view interval (viewInterval element as illustrated in FIG. 5), the time interval information may be indicated as this may be beneficial in knowing component hand off.
  • the DeliveryPath 1200 may be used for the content.
  • the pathType 1210 with a value of 0 indicates terrestrial broadcast delivery.
  • the pathType 1210 with a value of 1 indicates broadband delivery.
  • the pathType 1210 with a value of 2 indicates local delivery on the network.
  • the pathType 1210 values of 3 to 255 are reserved.
  • the pathType value of 2 indicates delivery (of continuous component) from a primary device (PD) to companion device (CD) on home network.
  • a startTime 1220 with a dateTime is computed from the UTC seconds count at the beginning of the event.
  • An interval may begin when the delivery of content begins on the path indicated by the value of pathType attribute. The value shall not be less than the value of startTime attribute of this ViewInterval instance.
  • An interval may end when the delivery of content ends on the path indicated by the value of pathType attribute. The value may not be greater than the value of endTime attribute of this ViewInterval instance.
  • DeliveryPath a sub-element of ViewInterval element as illustrated in FIG. 5.
  • the DeliveryPath maybe a sub-element of CDM element as illustrated in FIG. 5.
  • the component usage report information may be further augmented by inclusion of delivery path for each component. In this manner, it is easier to identify when different components are delivered using different paths. In one case this may be indicated as shown below.
  • a component 1300 type, role, name, ID and time interval information is a component 1300 type, role, name, ID and time interval information.
  • a componentType 1305 type of component is indicated as follows:
  • a componentRole 1310 may be a string representing the role or kind of the component.
  • a componentName 1315 may be a string representing the human readable name of the component.
  • a componentId 1320 may be a string representing component identifier.
  • this might be a URL which identifies a component.
  • a startTime 1325 may be a dateTime computed from the UTC seconds count at the beginning of the event. An interval may begin when display of this content component begins. The value may not be less than the value of startTime of this ViewInterval instance.
  • This ViewInterval 530 instance may be the parent of this Component element.
  • An endTime 1330 may be a dateTime computed from the UTC seconds count at the end of the event.
  • An interval may end when display of this content component ends. The value may not be greater than the value of endTime of this ViewInterval instance.
  • This ViewInterval 530 instance may be the parent of this Component element.
  • a DeliveryPath 1335 may be used for the content component indicated by the parent Component element.
  • a pathType 1340 may be a value of 0 indicates terrestrial broadcast delivery for the content component.
  • a pathType 1340 may be a value of 1 indicates broadband delivery for the content component.
  • a pathType 1340 may be a value of 2 indicates local delivery on network for the content component.
  • a pathType 1340 may be a value of 3 to 255, are reserved.
  • a pathType 1340 may be a value of 2 may indicate delivery (of this continuous component) from a primary device (PD) to companion device (CD) on a network.
  • a startTime 1345 may be a dateTime computed from the UTC seconds count at the beginning of the event. An interval may begin when the delivery of content component begins on the path indicated by the value of pathType attribute. The value may not be less than the value of startTime attribute of the parent Component element.
  • a startTime 1345 may be a dateTime computed from the UTC seconds count at the beginning of the event. An interval may begin when the delivery of content component begins on the path indicated by the value of pathType attribute. The value may not be less than the value of startTime attribute of this ViewInterval instance.
  • An endTime 1350 may be a dateTime computed from the UTC seconds count at the beginning of the event. An interval may end when the delivery of content component ends on the path indicated by the value of pathType attribute. The value may not be greater than the value of endTime attribute of the parent Component element. In an alternative embodiment: An endTime 1350 may be a dateTime computed from the UTC seconds count at the beginning of the event. An interval may end when the delivery of content component ends on the path indicated by the value of pathType attribute. The value may not be greater than the value of endTime attribute of this ViewInterval instance.
  • the Component element may be a sub-element of ViewInterval element as illustrated in FIG. 5.
  • the consumption data message is defined as a fundamental data structure used to transmit CDUs from a service usage data client to a service usage data server.
  • a consumption data message may be formatted as Javascript Object Notation (JSON) data instead of as XML data which tends to be more suitable for low bandwidth networks.
  • JSON Javascript Object Notation
  • a URCR may transmit a Consumption Data Message (CDM) to service usage data server as JSON data as per a defined JSON schema.
  • FIG. 15 shows a logical structure of extended consumption data message (CDM).
  • DeviceType Value of 0 indicates content is presented on a primary device. Value of 1 indicates the content is presented on a companion device. Values 2 to 255 are reserved.
  • Component Content component type, role, name, ID and time interval information.
  • componentType The type of component is indicated. Value of 0 indicates an audio component. Value of 1 indicates a video component. Value of 2 indicated a closed caption component. Value of 3 indicates an application component. Values 4 to 255 are reserved.
  • componentRole A unsigned byte representing the role or kind of the component.
  • componentRole When componentType value above is between 3 to 255, inclusive, the componentRole shall be equal to 255.
  • componentName A string representing the human readable name of the component.
  • componentId A string representing component identifier.
  • startTime the dateTime computed from the UTC seconds count at the beginning of the event. Interval shall begin when display of this content component begins. The value shall not be less than the value of startTime attribute of this ViewInterval instance.
  • endTime the dateTime computed from the UTC seconds count at the end of the event. Interval shall end when display of this content component ends. The value shall not be greater than the value of endTime attribute of this ViewInterval instance.
  • DeliveryPath Delivery path used for the content component indicated by the parent Component element.
  • pathType Value of 0 indicates terrestrial broadcast delivery for the content component. Value of 1 indicates broadband delivery for the content component. Value of 2 indicates local delivery on home network for the content component. Values 3 to 254 are reserved. Value of 255 indicates unknown delivery path.
  • startTime the dateTime computed from the UTC seconds count at the beginning of the event. Interval shall begin when the delivery of content component begins on the path indicated by the value of pathType attribute. The value shall not be less than the value of startTime attribute of the parent Component element.
  • EndTime the dateTime computed from the UTC seconds count at the beginning of the event. Interval shall end when the delivery of content component ends on the path indicated by the value of pathType attribute. The value shall not be greater than the value of endTime attribute of the parent Component element.
  • componentRole attribute may use data type of String instead of unsigned byte.
  • componentRole For audio component (when componentType value is equal to 0) allowed values of componentRole are as follows:
  • componentRole For Video (when componentType field above is equal to 1) allowed values of componentRole are as follows:
  • componentRole For Closed Caption component (when componentType field above is equal to 2) allowed values of componentRole are as follows:
  • the pathType attribute may use data type of String instead of unsigned byte.
  • the allowed values for deliveryPath are as follows: “broadcast” (indicates terrestrial broadcast delivery for the content component) “broadband” (indicates broadband delivery for the content component).
  • JSON schema part for pathType may use enumerations as shown below:
  • pathType may use a data type of String without enumerations.
  • JSON schema part for pathType is as shown below:
  • JSON schema is described for existing A/105 elements and attributes for service usage report consumption data messages (CDMs). JSON schema is also described for the proposed extensions of A/105 for service usage reporting. In the prior art XML is used for CDMs. It is noted that JSON schema does not allow attributes thus redefinition of various attributes for incorporation into JSON schema.
  • An exemplary JSON schema is shown in FIG. 16(1) through Fig. 16(4).
  • componentType and componentRole may be described in JSON schema using enumerations as shown below:
  • XML schema may be used to represent the consumption data messages and/ or service usage report.
  • component usage report information may be further augmented by inclusion of delivery path for each component.
  • XML schema for the combination of component indication and delivery path indication is as shown in FIG. 17.
  • FIG. 18(1) through Fig. 18(3) The overall XML schema including the proposed extensions is shown in FIG. 18(1) through Fig. 18(3).

Abstract

L'invention concerne un procédé pour rapporter des informations relatives à la consommation du contenu audiovisuel. Le procédé consiste à rapporter les informations comprenant le composant. Le composant comprend un type de composant, un rôle de composant, un nom de composant, un ID de composant et des informations d'intervalle de temps. Le type de composant comprend de l'audio, de la vidéo, des sous-titres, et une application. Le rôle de composant comprend un rôle ou une sorte du composant. Le nom de composant indique une chaîne représentant un nom humain du composant. L'ID de composant indique une chaîne représentant un identifiant de composant, et les informations d'intervalle de temps qui comprennent une heure de début et une heure de fin.
PCT/JP2016/000441 2015-01-30 2016-01-28 Système de création de rapport d'utilisation de service WO2016121398A1 (fr)

Priority Applications (6)

Application Number Priority Date Filing Date Title
CN202011056981.3A CN112261446B (zh) 2015-01-30 2016-01-28 上报信息的方法
CN201680006278.7A CN107211192B (zh) 2015-01-30 2016-01-28 上报信息的方法
US15/545,022 US10499108B2 (en) 2015-01-30 2016-01-28 System for service usage reporting
CA2973328A CA2973328C (fr) 2015-01-30 2016-01-28 Systeme de creation de rapport d'utilisation de service
US16/596,231 US10945031B2 (en) 2015-01-30 2019-10-08 System for service usage reporting
US17/164,127 US11303959B2 (en) 2015-01-30 2021-02-01 System for service usage reporting

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201562110284P 2015-01-30 2015-01-30
US62/110,284 2015-01-30
US201562149457P 2015-04-17 2015-04-17
US62/149,457 2015-04-17

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US15/545,022 A-371-Of-International US10499108B2 (en) 2015-01-30 2016-01-28 System for service usage reporting
US16/596,231 Continuation US10945031B2 (en) 2015-01-30 2019-10-08 System for service usage reporting

Publications (1)

Publication Number Publication Date
WO2016121398A1 true WO2016121398A1 (fr) 2016-08-04

Family

ID=56543020

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2016/000441 WO2016121398A1 (fr) 2015-01-30 2016-01-28 Système de création de rapport d'utilisation de service

Country Status (4)

Country Link
US (3) US10499108B2 (fr)
CN (2) CN107211192B (fr)
CA (2) CA2973328C (fr)
WO (1) WO2016121398A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPWO2017010312A1 (ja) * 2015-07-16 2018-05-24 ソニー株式会社 受信装置、送信装置、及び、データ処理方法
JPWO2017029990A1 (ja) 2015-08-17 2018-06-07 ソニー株式会社 受信装置、送信装置、およびデータ処理方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100262986A1 (en) * 2009-04-08 2010-10-14 Verizon Patent And Licensing Inc. Viewing history
JP2011059675A (ja) * 2009-08-11 2011-03-24 Ricoh Co Ltd 映像出力装置、映像出力システム、映像出力方法およびプログラム
WO2011112048A2 (fr) * 2010-03-12 2011-09-15 Samsung Electronics Co., Ltd. Procédé et appareil pour rapporter une mesure d'audience dans système de transmission de contenu
JP2012248999A (ja) * 2011-05-26 2012-12-13 Mitsubishi Electric Corp 視聴情報収集システムおよび視聴情報収集方法ならびにこれらに用いる視聴情報収集サーバおよびｉｐｔｖ端末
US20130332825A1 (en) * 2012-06-11 2013-12-12 Cellco Partnership D/B/A Verizon Wireless Cross-platform reporting user interface
EP2725788A1 (fr) * 2011-06-22 2014-04-30 Mitsubishi Electric Corporation Terminal de réception, système de collecte d'informations de visualisation et procédé de collecte d'informations de visualisation

Family Cites Families (65)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE69332895T2 (de) 1992-12-09 2004-02-05 Discovery Communications, Inc. Operationszentrale für Fernsehversorgungssystem
US5635978A (en) * 1994-05-20 1997-06-03 News America Publications, Inc. Electronic television program guide channel system and method
JPH10303840A (ja) * 1997-04-25 1998-11-13 Sony Corp マルチチャンネル放送システム
US6378129B1 (en) * 1998-03-30 2002-04-23 International Business Machines Corporation Video server content synchronization
US7603684B1 (en) * 1998-05-19 2009-10-13 United Video Properties, Inc. Program guide system with video-on-demand browsing
US7853664B1 (en) * 2000-07-31 2010-12-14 Landmark Digital Services Llc Method and system for purchasing pre-recorded music
JP2002112142A (ja) * 2000-09-28 2002-04-12 Pioneer Electronic Corp 番組案内装置および番組案内方法
JP3957131B2 (ja) * 2001-08-09 2007-08-15 株式会社日立製作所 番組出力方法および番組配信システム
JP2003304476A (ja) * 2002-04-09 2003-10-24 Funai Electric Co Ltd デジタル放送受信装置
US7200611B2 (en) * 2002-05-13 2007-04-03 Microsoft Corporation TV program database
CN1726489A (zh) * 2002-10-28 2006-01-25 格雷斯诺特有限公司 个人音频录制系统
KR100507808B1 (ko) * 2003-02-17 2005-08-17 삼성전자주식회사 디지털 티브이용 전자 프로그램 가이드 화면에서이티티정보 존재여부 디스플레이 제어방법
WO2005079499A2 (fr) * 2004-02-19 2005-09-01 Landmark Digital Services Llc Méthode et dispositif servant à identifier la source d’une diffusion
WO2006086556A2 (fr) * 2005-02-08 2006-08-17 Landmark Digital Services Llc Identification automatique de materiel repete dans des signaux audio
AU2006320692A1 (en) * 2005-11-29 2007-06-07 Google Inc. Detecting repeating content in broadcast media
JP4864482B2 (ja) * 2006-02-20 2012-02-01 株式会社東芝 放送記録装置及び放送記録方法
US20080066098A1 (en) * 2006-08-25 2008-03-13 Skyclix, Inc. Phone-based targeted advertisement delivery
US20080051029A1 (en) * 2006-08-25 2008-02-28 Bradley James Witteman Phone-based broadcast audio identification
US20080049704A1 (en) * 2006-08-25 2008-02-28 Skyclix, Inc. Phone-based broadcast audio identification
WO2008042953A1 (fr) * 2006-10-03 2008-04-10 Shazam Entertainment, Ltd. Procédé pour débit élevé d'identification d'un contenu de diffusion distribué
US20080271078A1 (en) * 2007-04-30 2008-10-30 Google Inc. Momentary Electronic Program Guide
US8572649B1 (en) * 2007-04-30 2013-10-29 Google Inc. Electronic program guide presentation
US8782698B2 (en) * 2007-04-30 2014-07-15 Google Inc. Customizable media channels
US8005826B1 (en) * 2007-04-30 2011-08-23 Google Inc. Identifying media content in queries
US8631440B2 (en) * 2007-04-30 2014-01-14 Google Inc. Program guide user interface
US8533761B1 (en) * 2007-04-30 2013-09-10 Google Inc. Aggregating media information
EP2034640A1 (fr) * 2007-09-07 2009-03-11 Advanced Digital Broadcast S.A. Procédé pour la programmation d'éléments de contenu et système de télévision doté d'une sélection de contenu assistée
CN101146110B (zh) * 2007-09-25 2011-06-29 深圳市迅雷网络技术有限公司 一种播放流媒体的方法
US8156520B2 (en) * 2008-05-30 2012-04-10 EchoStar Technologies, L.L.C. Methods and apparatus for presenting substitute content in an audio/video stream using text data
JP4702402B2 (ja) * 2008-06-05 2011-06-15 ソニー株式会社 信号送信装置、信号送信方法、信号受信装置及び信号受信方法
US8826443B1 (en) * 2008-09-18 2014-09-02 Symantec Corporation Selective removal of protected content from web requests sent to an interactive website
US20100205628A1 (en) * 2009-02-12 2010-08-12 Davis Bruce L Media processing methods and arrangements
US8516533B2 (en) * 2008-11-07 2013-08-20 Digimarc Corporation Second screen methods and arrangements
CN101437146B (zh) * 2008-12-04 2011-04-06 四川长虹电器股份有限公司 互动电视系统
US9521437B2 (en) * 2009-06-17 2016-12-13 Google Technology Holdings LLC Insertion of recorded secondary digital video content during playback of primary digital video content
EP2446623A4 (fr) * 2009-06-24 2014-08-20 Vidyo Inc Système et procédé pour un guide de programmation électronique vidéo actif
EP2302536A1 (fr) * 2009-09-21 2011-03-30 Thomson Licensing Système et procédé pour la vérification automatique du stockage de contenu redondant dans des équipements de communication, par comparaison de données
US8760498B2 (en) 2011-03-14 2014-06-24 Sony Corporation Disparity data transport in standard caption service
US8878913B2 (en) 2010-03-12 2014-11-04 Sony Corporation Extended command stream for closed caption disparity
US8839338B2 (en) 2012-03-28 2014-09-16 Sony Corporation Service usage reporting data transport
US8941779B2 (en) 2012-03-21 2015-01-27 Sony Corporation Non-closed caption data transport in standard caption service
KR101582436B1 (ko) * 2010-05-04 2016-01-04 샤잠 엔터테인먼트 리미티드 미디어의 동기화 방법 및 시스템
US9159338B2 (en) * 2010-05-04 2015-10-13 Shazam Entertainment Ltd. Systems and methods of rendering a textual animation
US8776121B2 (en) * 2010-11-03 2014-07-08 Google Inc. Social aspects of media guides
KR20140038359A (ko) 2011-01-04 2014-03-28 톰슨 라이센싱 대응하는 컨텐트 창작자를 나타내는 미디어 자산 용법 데이터 보고
WO2012135804A2 (fr) * 2011-04-01 2012-10-04 Mixaroo, Inc. Système et procédé de traitement, de stockage, d'indexage et de distribution en temps réel de vidéo segmentée
JP5175950B2 (ja) * 2011-04-20 2013-04-03 株式会社東芝 ビデオサーバ及び送出スタンバイ方法
JP5912294B2 (ja) * 2011-05-26 2016-04-27 シャープ株式会社 テレビ会議装置
US9554175B2 (en) 2011-07-20 2017-01-24 Sony Corporation Method, computer program, reception apparatus, and information providing apparatus for trigger compaction
US8639178B2 (en) * 2011-08-30 2014-01-28 Clear Channel Management Sevices, Inc. Broadcast source identification based on matching broadcast signal fingerprints
TWI528749B (zh) 2011-09-06 2016-04-01 Sony Corp A signal receiving device, a signal receiving method, an information processing program and an information processing system
US8930988B2 (en) 2011-12-21 2015-01-06 Sony Corporation Reception apparatus, reception method, program, and information processing system
US9113230B2 (en) 2011-12-21 2015-08-18 Sony Corporation Method, computer program, and reception apparatus for delivery of supplemental content
US9936231B2 (en) 2012-03-21 2018-04-03 Saturn Licensing Llc Trigger compaction
US8713606B2 (en) * 2012-05-14 2014-04-29 United Video Properties, Inc. Systems and methods for generating a user profile based customized media guide with user-generated content and non-user-generated content
US9326014B2 (en) * 2012-06-22 2016-04-26 Google Inc. Method and system for correlating TV broadcasting information with TV panelist status information
US9215022B2 (en) * 2012-07-18 2015-12-15 Google Inc. Logging individuals for TV measurement compliance
US9661361B2 (en) * 2012-09-19 2017-05-23 Google Inc. Systems and methods for live media content matching
US9215489B2 (en) * 2012-11-30 2015-12-15 The Nielson Company (Us), Llc Custom electronic program guides
US9781476B2 (en) * 2012-12-31 2017-10-03 Echostar Technologies L.L.C. Automatic learning channel customized to a particular viewer and method of creating same
US20140196070A1 (en) * 2013-01-07 2014-07-10 Smrtv, Inc. System and method for automated broadcast media identification
US9066132B2 (en) * 2013-05-13 2015-06-23 Rovi Guides, Inc. Systems and methods for recording content from a different source when previous content runs over
US9021518B2 (en) * 2013-05-21 2015-04-28 Richard H. Theriault System to avoid viewing commercials in real time
AU2015218353A1 (en) * 2014-02-14 2016-09-01 Pluto Inc. Methods and systems for generating and providing program guides and content
US9900632B1 (en) * 2016-12-30 2018-02-20 Echostar Technologies L.L.C. Viewing suggestions based on closed-captioned content from multiple tuners

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100262986A1 (en) * 2009-04-08 2010-10-14 Verizon Patent And Licensing Inc. Viewing history
JP2011059675A (ja) * 2009-08-11 2011-03-24 Ricoh Co Ltd 映像出力装置、映像出力システム、映像出力方法およびプログラム
WO2011112048A2 (fr) * 2010-03-12 2011-09-15 Samsung Electronics Co., Ltd. Procédé et appareil pour rapporter une mesure d'audience dans système de transmission de contenu
JP2012248999A (ja) * 2011-05-26 2012-12-13 Mitsubishi Electric Corp 視聴情報収集システムおよび視聴情報収集方法ならびにこれらに用いる視聴情報収集サーバおよびｉｐｔｖ端末
EP2725788A1 (fr) * 2011-06-22 2014-04-30 Mitsubishi Electric Corporation Terminal de réception, système de collecte d'informations de visualisation et procédé de collecte d'informations de visualisation
US20130332825A1 (en) * 2012-06-11 2013-12-12 Cellco Partnership D/B/A Verizon Wireless Cross-platform reporting user interface

Also Published As

Publication number Publication date
CA2973328C (fr) 2019-11-26
US10499108B2 (en) 2019-12-03
CN107211192B (zh) 2020-11-06
CA3057090A1 (fr) 2016-08-04
CN107211192A (zh) 2017-09-26
US10945031B2 (en) 2021-03-09
CA2973328A1 (fr) 2016-08-04
CN112261446A (zh) 2021-01-22
US11303959B2 (en) 2022-04-12
US20210160566A1 (en) 2021-05-27
US20200053421A1 (en) 2020-02-13
CN112261446B (zh) 2023-07-18
US20180014064A1 (en) 2018-01-11
CA3057090C (fr) 2023-01-03

Similar Documents

Publication Publication Date Title
KR101922554B1 (ko) 방송 시스템에서의 제어 메시지 구성 장치 및 방법
US10616297B2 (en) Content-specific identification and timing behavior in dynamic adaptive streaming over hypertext transfer protocol
US11617007B2 (en) Broadcast receiving device, method of operating broadcast receiving device, linking device for linking to broadcast receiving device, and method of operating linking device
US20220377434A1 (en) Watermark-based metadata acquisition and processing
WO2015182085A1 (fr) Dispositif de compagnie
US11303959B2 (en) System for service usage reporting
US20170105055A1 (en) Broadcast reception device and operating method thereof, and companion device interoperating with the broadcast reception device and operating method thereof
CA2960118A1 (fr) Systeme ayant un dispositif d'accompagnement et un dispositif principal
US10880603B2 (en) Method for providing a consumption data message
US11146853B2 (en) Usage reporting capable receiver, service usage data server, and method for transmitting consumption data units
WO2016082806A1 (fr) Procédé et dispositif de traitement vidéo

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: 16743002

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2973328

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 15545022

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16743002

Country of ref document: EP

Kind code of ref document: A1