WO2017122554A1 - 受信装置、送信装置、及び、データ処理方法 - Google Patents
受信装置、送信装置、及び、データ処理方法 Download PDFInfo
- Publication number
- WO2017122554A1 WO2017122554A1 PCT/JP2017/000012 JP2017000012W WO2017122554A1 WO 2017122554 A1 WO2017122554 A1 WO 2017122554A1 JP 2017000012 W JP2017000012 W JP 2017000012W WO 2017122554 A1 WO2017122554 A1 WO 2017122554A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- application
- content
- unit
- server
- signaling
- Prior art date
Links
- 230000005540 biological transmission Effects 0.000 title claims abstract description 185
- 238000003672 processing method Methods 0.000 title claims abstract description 32
- 238000000034 method Methods 0.000 claims description 302
- 230000011664 signaling Effects 0.000 claims description 197
- 238000012795 verification Methods 0.000 claims description 22
- 238000012545 processing Methods 0.000 description 202
- 230000008569 process Effects 0.000 description 164
- 238000003860 storage Methods 0.000 description 71
- 238000004891 communication Methods 0.000 description 67
- 238000005516 engineering process Methods 0.000 description 34
- 238000010586 diagram Methods 0.000 description 25
- 238000004422 calculation algorithm Methods 0.000 description 21
- 238000007726 management method Methods 0.000 description 20
- 238000009877 rendering Methods 0.000 description 18
- 239000000284 extract Substances 0.000 description 12
- 238000012546 transfer Methods 0.000 description 12
- 238000009826 distribution Methods 0.000 description 10
- 238000010304 firing Methods 0.000 description 9
- 230000004913 activation Effects 0.000 description 7
- AWSBQWZZLBPUQH-UHFFFAOYSA-N mdat Chemical compound C1=C2CC(N)CCC2=CC2=C1OCO2 AWSBQWZZLBPUQH-UHFFFAOYSA-N 0.000 description 7
- 230000006870 function Effects 0.000 description 6
- 230000007246 mechanism Effects 0.000 description 6
- 239000012634 fragment Substances 0.000 description 5
- 238000002716 delivery method Methods 0.000 description 4
- 230000003044 adaptive effect Effects 0.000 description 3
- 230000004075 alteration Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 241001125831 Istiophoridae Species 0.000 description 1
- 238000009825 accumulation Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000000153 supplemental effect Effects 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
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/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/472—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content
- H04N21/4722—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content for requesting additional data associated with the content
- H04N21/4725—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content for requesting additional data associated with the content using interactive regions of the image, e.g. hot spots
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/16—Program or content traceability, e.g. by watermarking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04H—BROADCAST COMMUNICATION
- H04H20/00—Arrangements for broadcast or for distribution combined with broadcast
- H04H20/86—Arrangements characterised by the broadcast information itself
- H04H20/91—Arrangements characterised by the broadcast information itself broadcasting computer programmes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04H—BROADCAST COMMUNICATION
- H04H20/00—Arrangements for broadcast or for distribution combined with broadcast
- H04H20/86—Arrangements characterised by the broadcast information itself
- H04H20/93—Arrangements characterised by the broadcast information itself which locates resources of other pieces of information, e.g. URL [Uniform Resource Locator]
-
- 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/09—Arrangements for device control with a direct linkage to broadcast information or to broadcast space-time; Arrangements for control of broadcast-related services
- H04H60/13—Arrangements for device control affected by the broadcast information
-
- 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/09—Arrangements for device control with a direct linkage to broadcast information or to broadcast space-time; Arrangements for control of broadcast-related services
- H04H60/14—Arrangements for conditional access to broadcast information or to broadcast-related services
-
- 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/09—Arrangements for device control with a direct linkage to broadcast information or to broadcast space-time; Arrangements for control of broadcast-related services
- H04H60/14—Arrangements for conditional access to broadcast information or to broadcast-related services
- H04H60/23—Arrangements for conditional access to broadcast information or to broadcast-related services using cryptography, e.g. encryption, authentication, key distribution
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- 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/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/435—Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream
- H04N21/4353—Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream involving decryption of additional data
-
- 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
- H04N21/44236—Monitoring of piracy processes or activities
-
- 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
- H04N21/8166—Monomedia components thereof involving executable data, e.g. software
- H04N21/8173—End-user applications, e.g. Web browser, game
-
- 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/8358—Generation of protective data, e.g. certificates involving watermark
-
- 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/85—Assembly of content; Generation of multimedia applications
- H04N21/858—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot
- H04N21/8586—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot by using a URL
-
- 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/76—Arrangements characterised by transmission systems other than for broadcast, e.g. the Internet
- H04H60/81—Arrangements characterised by transmission systems other than for broadcast, e.g. the Internet characterised by the transmission system itself
- H04H60/82—Arrangements characterised by transmission systems other than for broadcast, e.g. the Internet characterised by the transmission system itself the transmission system being the Internet
Definitions
- the present technology relates to a receiving device, a transmitting device, and a data processing method, and in particular, a receiving device, a transmitting device, and a data processing method that can flexibly operate a service using an application associated with content. About.
- AIT Application Information Table
- applications application control information
- applications application control information
- the application control information can control the activation and termination operations of the application.
- DRM Digital Rights Management
- This technology has been made in view of such a situation, and enables a service using an application attached to content to be flexibly operated.
- the receiving device is based on a receiving unit that receives content, and acquisition source information that indicates an acquisition source of an application that accompanies the content, included in control information transmitted together with the content. It is a receiving apparatus provided with the acquisition part which acquires the said application, and the control part which starts the acquired said application immediately.
- the receiving device may be an independent device, or may be an internal block constituting one device.
- the data processing method according to the first aspect of the present technology is a data processing method corresponding to the above-described receiving device according to the first aspect of the present technology.
- the acquisition destination information indicating the acquisition destination of the application associated with the content which is included in the control information that is received and transmitted together with the content Based on the above, the application is acquired, and the acquired application is immediately activated.
- the transmission device is acquisition destination information indicating an acquisition destination of an application associated with content, and includes control information including the acquisition destination information for immediately starting the acquired application. It is a transmission apparatus provided with the production
- the transmission device according to the second aspect of the present technology may be an independent device, or may be an internal block constituting one device.
- a data processing method according to the second aspect of the present technology is a data processing method corresponding to the transmission device according to the second aspect of the present technology described above.
- the acquisition destination information indicating an acquisition destination of an application associated with content, and the acquisition for immediately starting the acquired application Control information including destination information is generated, and the control information is transmitted together with the content.
- a receiving device includes a receiving unit that receives content and an application that accompanies the content, and that acquires the application protected by DRM (Digital Rights Management) of the content
- a verification unit that verifies whether the acquired application is a valid application
- a control unit that activates the application when the application is recognized as a valid application. It is.
- the receiving device may be an independent device, or may be an internal block constituting one device.
- a data processing method is a data processing method corresponding to the receiving device according to the third aspect of the present technology described above.
- content is received and the application associated with the content is protected by DRM (Digital Rights Management) of the content.
- DRM Digital Rights Management
- the acquired application is verified whether or not the acquired application is a valid application, and when the application is recognized as a valid application, the application is activated.
- a transmission device includes a protection unit that protects an application associated with content by DRM (Digital Rights Management) of the content, the content protected by a common DRM (Digital Rights Management), and And a transmission unit that transmits the application.
- DRM Digital Rights Management
- DRM Digital Rights Management
- the transmission device according to the fourth aspect of the present technology may be an independent device, or may be an internal block constituting one device.
- the data processing method according to the fourth aspect of the present technology is a data processing method corresponding to the transmission device according to the fourth aspect of the present technology described above.
- the application associated with the content is protected by the DRM (Digital Rights Management) of the content and protected by the common DRM (Digital Rights Management).
- the content and the application are transmitted.
- 10 is a flowchart illustrating a processing flow on a transmission side when application control is performed based on an MPD event method event.
- 10 is a flowchart illustrating a processing flow on the reception side when application control is performed using an MPD event method event.
- It is a figure which shows the example of arrangement
- It is a flowchart explaining the flow of a process of the transmission side in the case of performing application control by the event of an in-band event system.
- It is a flowchart explaining the flow of a process of the receiving side in the case of performing application control by the event of an in-band event system.
- First embodiment Application life cycle control (1) System configuration (2) Application control according to application URL (3) Application control according to application control event (A) MPD event method (B) In-band Event method
- Second embodiment Secure application provision (1) System configuration (2) Overview of application digest (3) Transmission method of application digest (A) Watermark storage system (B) Non-VCL-NAL unit storage system 3. Signaling example 4. Modification 5 Computer configuration
- an application URL Uniform Resource Locator
- the life cycle control of individual applications controlled by application control information such as AST and AIT is not performed, but the service (channel) itself or a specific time zone of the service (channel) (for example, a program) If one or more application URLs bound to a frame or CM frame) are described in signaling, when the application URL is described in signaling, the target application is acquired and immediately To be launched.
- application control information such as AST and AIT
- FIG. 1 is a diagram illustrating a configuration example of an embodiment (first embodiment) of a transmission system to which the present technology is applied.
- the system refers to a logical collection of a plurality of devices.
- the transmission system 1 includes a transmission side system 5, a reception side Klein, and a device 60.
- data transmitted from the transmission-side system 5 is received by the client device 60 via the transmission path 80 or the Internet 90.
- ATSC 3.0 IP transmission using IP (Internet Protocol) packets used in the field of communication for digital broadcasting, not the MPEG2-TS (Transport Stream) system, which is currently widely used as a transmission system. It is assumed that more advanced services will be provided by introducing the method.
- IP Internet Protocol
- the transmission side system 5 performs a process for transmitting data conforming to a predetermined standard such as ATSC3.0.
- the transmission side system 5 includes a DASH server 10, a signaling server 20, an application server 30, a broadcast server 40, and a communication server 50.
- the DASH server 10 is a server for providing a distribution service compatible with MPEG-DASH (Dynamic Adaptive Streaming over HTTP).
- MPEG-DASH is a streaming distribution standard according to OTT-V (Over The Top Video) and is a standard related to adaptive streaming distribution using a streaming protocol based on HTTP (Hypertext Transfer Protocol).
- This MPEG-DASH standard defines a manifest file for describing metadata, which is management information for moving image and audio files, and a file format for transmitting moving image content.
- the former manifest file is called MPD (Media Presentation Description).
- the latter file format is also called a segment format.
- the DASH server 10 receives data for generating MPD metadata, content data, and the like from the outside.
- the DASH server 10 generates MPD metadata based on data from the outside and transmits it to the signaling server 20. Further, the DASH server 10 generates a file of a content segment (hereinafter also referred to as a DASH segment) such as a program or CM based on data from the outside, and transmits the file to the broadcast server 40 or the communication server 50.
- a content segment hereinafter also referred to as a DASH segment
- Application server 30 receives data for generating an application from the outside.
- the application server 30 generates an application URL indicating an application acquisition source based on data from the outside, and transmits the application URL to the signaling server 20. Further, the application server 30 generates an application identified by the application URL based on data from the outside, and transmits the application to the broadcast server 40 or the communication server 50.
- the application is an application that accompanies content such as a program or CM.
- an application accompanying the content for example, an application developed in a markup language such as HTML5 (HyperTextperMarkup Language 5) or a script language such as JavaScript (registered trademark) can be used.
- the application server 30 generates an event for controlling the operation of the application (hereinafter referred to as an application control event) and transmits it to the DASH server 10.
- the DASH server 10 can store the application control event transmitted from the application server 30 in the MPD metadata or the DASH segment.
- the signaling server 20 receives data for generating signaling from the outside. Further, the signaling server 20 receives the MPD metadata from the DASH server 10 and the application URL from the application server 30. The signaling server 20 generates signaling based on data from the outside, MPD metadata, and application URL, and transmits the signaling to the broadcast server 40 or the communication server 50.
- LLS Link Layer Signaling
- SLS Service Layer Signaling
- LLS signaling includes metadata such as SLT (Service List).
- SLT metadata includes basic information indicating the stream and service configuration in the broadcast network, such as information necessary for channel selection (channel selection information).
- SLS signaling includes metadata such as USD (User Service Description), S-TSID (Service-based Transport Session Instance Description), and MPD (Media Presentation Description).
- USD User Service Description
- S-TSID Service-based Transport Session Instance Description
- MPD Media Presentation Description
- the USD metadata includes information such as an acquisition destination of other metadata. However, USD may be referred to as USBD (User Service Bundle Description).
- the S-TSID metadata is an extension of LSID (LCT Session Instance Description) for ATSC 3.0, and is control information for the ROUTE (Real-time Object Delivery Service Unidirectional Transport) protocol.
- ROUTE Real-time Object Delivery Service Unidirectional Transport
- FLUTE FLUTE Delivery over Unidirectional Transport
- MPD metadata is management information for video and audio files that are streamed.
- metadata such as SLT, USD, S-TSID, and MPD can be described in a markup language such as XML (Extensible Markup Language).
- the signaling server 20 generates LLS signaling including SLT metadata and SLS signaling including USD metadata, S-TSID metadata, and MPD metadata. However, the signaling server 20 processes the MPD metadata generated by the DASH server 10 as SLS signaling. In addition, the signaling server 20 includes the application URL generated by the application server 30 in metadata such as SLT, USD, S-TSID, and MPD.
- the broadcast server 40 is a transmitter capable of performing data transmission conforming to digital broadcasting standards such as ATSC 3.0.
- the broadcast server 40 receives the DASH segment transmitted from the DASH server 10, the signaling transmitted from the signaling server 20, and the application (file) transmitted from the application server 30.
- the broadcast server 40 processes the DASH segment, signaling, and application (file thereof), and transmits (broadcast broadcast) via the transmission path 80.
- the broadcast server 40 receives LCC (Locally Cached Content) content.
- LCC content is content that is once stored in the storage of the client device 60 and then played back.
- the broadcast server 40 processes the LCC content (file thereof) input thereto and transmits (broadcast broadcast) via the transmission path 80.
- the communication server 50 is a server that provides various data via the Internet 90 in response to a request from the client device 60 connected to the Internet 90.
- the communication server 50 receives the DASH segment transmitted from the DASH server 10, the signaling transmitted from the signaling server 20, and the application (file) transmitted from the application server 30.
- the communication server 50 processes the DASH segment, signaling, and application (file).
- the communication server 50 transmits various files via the Internet 90 in response to requests from the client device 60.
- the client device 60 is a receiver that can receive transmission data compliant with digital broadcasting standards such as ATSC 3.0.
- the client device 60 is a fixed receiver such as a television receiver or a set top box, or a mobile receiver such as a smartphone, a mobile phone, or a tablet computer.
- the client device 60 may be a device mounted on an automobile such as an in-vehicle television.
- the client device 60 receives and processes files such as DASH segments, signaling, and LCC content transmitted (broadcast broadcast) from the broadcast server 40 via the transmission path 80, thereby processing content such as broadcast programs. Output video and audio.
- the client device 60 can access the communication server 50 via the Internet 90 and acquire various files.
- the client device 60 receives and processes a file such as a DASH segment or MPD metadata that is transmitted (adaptive streaming distribution) from the communication server 50 via the Internet 90 to process VOD (Video On Demand). ) Output video and audio of content such as programs.
- VOD Video On Demand
- the client device 60 acquires the application distributed from the broadcast server 40 or the communication server 50 based on the application URL included in the signaling transmitted from the broadcast server 40 or the communication server 50, and immediately acquires the acquired application. To start.
- the application acquired through the broadcast or communication is executed along with the content acquired through the broadcast or communication.
- the application not only explicitly displays some information, but may operate in the non-display (in the background) (may be started without being recognized by the user).
- the client device 60 controls the operation of the application according to the application control event.
- the transmission path 80 is not limited to terrestrial (terrestrial broadcast), for example, satellite broadcasting using a broadcasting satellite (BS: Broadcasting Satellite) or communication satellite (CS: Communications Satellite), or cable. It may be cable broadcasting (CATV) using BS: Broadcasting Satellite
- BS Broadcasting Satellite
- CS Communications Satellite
- CATV cable broadcasting
- the transmission side system 5 transmits ( Digital broadcast signals to be broadcast simultaneously) can be simultaneously received by a plurality of client devices 60 via the transmission path 80.
- a plurality of transmission side systems 5 can be provided.
- Each of the plurality of transmission side systems 5 transmits a digital broadcast signal including a broadcast stream as a separate channel, for example, in a separate frequency band.
- each channel of the plurality of transmission side systems 5 is transmitted.
- the channel for receiving the broadcast stream can be selected from the list.
- the configuration of the DASH server 10, the signaling server 20, the application server 30, the broadcast server 40, and the client device 60 of the transmission side system 5 in the transmission system 1 of FIG. 1. Will be described.
- the communication server 50 has the same configuration as a general server having a communication function.
- FIG. 2 is a diagram illustrating a configuration example of the DASH server 10 of FIG.
- the DASH server 10 includes a receiving unit 101, a processing unit 102, and a transmitting unit 103.
- the receiving unit 101 receives data for streaming distribution from an external server (not shown) or the like and supplies the data to the processing unit 102.
- the receiving unit 201 supplies the application control event to the processing unit 102. Details of the application control event will be described later.
- the processing unit 102 processes the data supplied from the receiving unit 101 and supplies it to the transmitting unit 103.
- the processing unit 102 includes an MPD generation unit 111 and a DASH segment generation unit 112.
- the MPD generation unit 111 generates MPD metadata based on the data supplied from the reception unit 101. In addition, when an application control event is supplied from the receiving unit 201 (when an MPD event method described later is adopted), the MPD generation unit 111 stores the application control event in MPD metadata.
- the DASH segment generation unit 112 generates a DASH segment based on the data supplied from the reception unit 101.
- the DASH segment conforms to ISOBMFF (ISO Base Media File Format).
- ISOBMFF ISO Base Media File Format
- the DASH segment generation unit 112 stores the application control event in the DASH segment.
- the application control event may be stored in either the MPD metadata or the DASH segment.
- the DASH segment is a live content (for example, a live broadcast program such as a sports broadcast) sent from a relay location via a transmission line or a communication line, or a recorded content (for example, a drama or the like) stored in a storage.
- a live content for example, a live broadcast program such as a sports broadcast
- a recorded content for example, a drama or the like
- the transmission unit 103 transmits MPD metadata among the data supplied from the processing unit 102 to the signaling server 20 and transmits the DASH segment to the broadcast server 40 or the communication server 50.
- the data is transmitted to the broadcast server 40
- the DASH segment is distributed via communication
- the data is transmitted to the communication server 50.
- the DASH server 10 is configured as described above.
- FIG. 3 is a diagram illustrating a configuration example of the signaling server 20 of FIG.
- the signaling server 20 includes a reception unit 201, a processing unit 202, and a transmission unit 203.
- the receiving unit 201 receives signaling generation data from an external server (not shown) or the like and supplies the data to the processing unit 202.
- the receiving unit 201 receives the MPD metadata transmitted from the DASH server 10 and the application URL transmitted from the application server 30 and supplies the received application URL to the processing unit 202.
- the processing unit 202 processes the data supplied from the receiving unit 201 and supplies it to the transmitting unit 203.
- the processing unit 202 includes a signaling generation unit 211.
- the signaling generation unit 211 generates LLS signaling including SLT metadata and SLS signaling including USD metadata, S-TSID metadata, and MPD metadata based on the data supplied from the reception unit 201.
- the application URL generated by the application server 30 is included in any one of the SLT metadata, USD metadata, S-TSID metadata, and MPD metadata.
- the transmission unit 203 transmits the signaling supplied from the processing unit 202 (the signaling generation unit 211) to the broadcast server 40 or the communication server 50.
- the processing unit 202 the signaling generation unit 2111
- the data is transmitted to the broadcast server 40
- the signaling is distributed via communication
- the data is transmitted to the communication server 50.
- the signaling server 20 is configured as described above.
- FIG. 4 is a diagram illustrating a configuration example of the application server 30 of FIG.
- the application server 30 includes a receiving unit 301, a processing unit 302, and a transmitting unit 303.
- the receiving unit 301 receives application data from an external server (not shown) or the like and supplies it to the processing unit 302.
- the processing unit 302 processes the data supplied from the reception unit 301 and supplies the data to the transmission unit 303.
- the processing unit 302 includes an application URL generation unit 311, an application generation unit 312, and an application control event generation unit 313.
- the application URL generation unit 311 generates an application URL indicating an application acquisition destination based on the data supplied from the reception unit 301.
- the application generation unit 312 generates an application identified by the application URL based on the data supplied from the reception unit 301.
- the application control event generation unit 313 generates an event (application operation event) for controlling the operation of the application at a predetermined timing for causing the application to perform a predetermined operation.
- the transmission unit 303 transmits the application URL of the data supplied from the processing unit 302 to the signaling server 20 and transmits the application to the broadcast server 40 or the communication server 50.
- the application is distributed via broadcast
- the data is transmitted to the broadcast server 40
- the application is distributed via communication
- the data is transmitted to the communication server 50.
- the transmission unit 303 supplies the application operation event to the DASH server 10.
- Application server 30 is configured as described above.
- FIG. 5 is a diagram illustrating a configuration example of the broadcast server 40 of FIG.
- the broadcast server 40 includes a receiving unit 401, a processing unit 402, and a transmitting unit 403.
- the receiving unit 401 receives the DASH segment transmitted from the DASH server 10, the signaling transmitted from the signaling server 20, and the application transmitted from the application server 30, and supplies them to the processing unit 402.
- the processing unit 402 performs necessary processing on the DASH segment, signaling, and application supplied from the receiving unit 401 and supplies the processed data to the transmitting unit 403.
- processing for generating an IP / UDP packet in which data of an LCT session including DASH segment, SLS signaling, and application is stored in the payload and an IP / UDP packet in which data of LLS signaling is stored in the payload, etc. Is done.
- the transmission unit 403 transmits a broadcast wave (digital broadcast signal) including data supplied from the processing unit 402 via the transmission path 80 by the antenna 421 (simultaneous broadcast distribution).
- the broadcast server 40 is configured as described above.
- FIG. 6 is a diagram illustrating a configuration example of the client device 60 of FIG.
- the client device 60 includes a processing unit 601, an input unit 602, a receiving unit 603, a broadcast middleware 604, a DASH client 605, a decoder 606, an output unit 607, and a communication unit 608.
- the processing unit 601 performs processing for controlling the operation of each unit of the client device 60 and the like.
- the input unit 602 supplies an operation signal corresponding to a user operation to the processing unit 601.
- the processing unit 601 controls the operation of each unit of the client device 60 based on the operation signal supplied from the input unit 602.
- the receiving unit 603 receives and processes a broadcast wave (digital broadcast signal) transmitted (broadcast distribution) from the broadcast server 40 via the transmission path 80 by the antenna 621, processes the received data,
- the broadcast middleware 604 is supplied.
- the receiving unit 603 includes a tuner and the like.
- the broadcast middleware 604 processes data supplied from the receiving unit 603 and supplies the processed data to the processing unit 601 or the DASH client 605.
- MPD metadata and a DASH segment are supplied to the DASH client 605, and data such as application and signaling is supplied to the processing unit 601.
- the DASH client 605 is supplied with MPD metadata and DASH segments from the broadcast middleware 604.
- the DASH client 605 processes the DASH segment based on the MPD metadata.
- Video and audio data obtained by processing the DASH segment is supplied to the decoder 606.
- the decoder 606 decodes video and audio data supplied from the DASH client 605 in accordance with a predetermined decoding method (for example, HEVC (High Efficiency Video Coding), AAC (Advanced Audio Coding), etc.). Video and audio data obtained by this decoding is supplied to the output unit 607.
- a predetermined decoding method for example, HEVC (High Efficiency Video Coding), AAC (Advanced Audio Coding), etc.
- the output unit 607 outputs video and audio data supplied from the decoder 606.
- the client device 60 reproduces content such as programs and commercials, and outputs the video and audio.
- the communication unit 608 exchanges data with the communication server 50 via the Internet 90 in accordance with the control from the processing unit 601.
- MPD metadata and DASH segments are supplied to the DASH client 605, and data such as application and signaling is supplied to the processing unit 601. Since the processing for the data acquired via the communication is the same as the data acquired via the broadcast described above, the description thereof is omitted here.
- the processing unit 601 includes an application control unit 611 and a rendering engine 612.
- the application control unit 611 controls the operation of the application supplied from the broadcast middleware 604 or the communication unit 608.
- the rendering engine 612 controls the output unit 607 to render video, audio, and application data, thereby generating video and audio.
- the client device 60 is configured as described above.
- an application control model associated with content such as programs and commercials.
- the application URL of an application to be activated accompanying content in signaling (for example, metadata such as SLT, USD, S-TSID, MPD, etc.)
- signaling for example, metadata such as SLT, USD, S-TSID, MPD, etc.
- an application URL is generated by the application URL generation unit 311 of the application server 30.
- An application is generated by the application generation unit 312 of the application server 30.
- the application is developed in a markup language such as HTML5 or a script language such as JavaScript (registered trademark), and is composed of a plurality of files such as an HTML document file and an image file.
- the application entry (for example, index.html) is identified by the application URL.
- the entry means a page that is activated first in the application.
- an application generated by the application server 30 is transmitted to the reception-side client device 60 via the transmission path 80 (or the Internet 90) by the broadcast server 40 (or the communication server 50). Is done.
- SLT metadata or SLS signaling (for example, metadata such as USD, S-TSID, MPD, etc.) generated by the signaling server 20 (the signaling generation unit 211 thereof)
- the application URL generated by the application server 30 is included.
- the signaling generated by the signaling server 20 is transmitted to the reception-side client device 60 via the transmission path 80 (or the Internet 90) by the broadcast server 40 (or the communication server 50). Is done.
- the signaling transmitted from the transmission side system 5 on the transmission side is received and processed.
- the application URL is included in SLT metadata or SLS signaling (for example, metadata such as USD, S-TSID, and MPD).
- the client device 60 on the receiving side receives the application transmitted from the broadcast server 40 (or the communication server 50) according to the application URL included in the SLT metadata or SLS signaling. Then, the client device 60 on the receiving side starts up the received application immediately.
- the launched application may explicitly display some information, or it may be launched with a transparent background (it is launched without displaying anything and the user is notified that it has been launched. In some cases, it is not recognized.
- the timing of stopping the running application is, for example, triggered by a user operation (for example, a service switching operation by a remote controller) or a native application (embedded application) executed by the client device 60. It can be stopped when switching to another service triggered by the control.
- a user operation for example, a service switching operation by a remote controller
- a native application embedded application
- the activated application is continued without being stopped. So that In this case, the service ID or major channel number of the service to be switched to is notified to the running application so that the service switching is detected by the running application. .
- one or more application URLs can be described as a list.
- the application URLs are described as a list, for example, depending on the execution environment of the client device 60, the activation priority control or activation selection control of the applications corresponding to the application URLs is performed.
- the application control model can be implemented simply compared to the case where application control information such as AST and AIT is used for delivery lifecycle control of the application. .
- step S101 the MPD generation unit 111 generates MPD metadata.
- step S102 the DASH segment generation unit 112 processes a content (data) such as a program to generate a DASH segment whose reproduction is managed by the MPD metadata generated in the process of step S101.
- step S103 the transmission unit 103 transmits the MPD metadata generated in step S101 to the signaling server 20, and transmits the DASH segment generated in step S102 to the broadcast server 40.
- step S301 the application URL generation unit 311 generates an application URL.
- step S302 the application generation unit 312 generates an application identified by the application URL generated in the process of step S301.
- step S303 the transmission unit 303 transmits the application URL generated in the process of step S301 to the signaling server 20, and transmits the application generated in the process of step S302 to the broadcast server 40.
- the signaling server 20 receives the MPD metadata transmitted in the process of step S103 and the application URL transmitted in the process of step S303.
- step S201 the signaling generation unit 211 generates signaling.
- LLS signaling including SLT metadata and SLS signaling including USD metadata, S-TSID metadata, and MPD metadata are generated.
- the application URL generated by the application server 30 is described in SLT metadata or SLS signaling (for example, metadata such as USD, S-TSID, and MPD).
- step S202 the transmission unit 203 transmits the signaling generated in the process of step S201 to the broadcast server 40.
- the transmission unit 403 transmits the application generated by the application server 30, the signaling generated by the signaling server 20, and the DASH segment generated by the DASH server 10 via the transmission path 80 (broadcasting). (S401 to S403).
- the application, signaling, and the DASH segment are distributed via the broadcast by the broadcast server 40 in the processing on the transmission side in FIG. 8, the case where the application, signaling, and the DASH segment are distributed via the broadcast by the broadcast server 40 has been described. However, the application, signaling, and the DASH segment are all or part of them.
- the data may be distributed by the communication server 50 via communication. However, in the following description, data such as application, signaling, and DASH segment will be mainly described in the case where the broadcast server 40 distributes the data via broadcast.
- the processing shown in FIG. 9 is executed by the client device 60.
- the video / audio compatible processing executed by the DASH client 605, the decoder 606, the rendering engine 612, etc., and the application control unit 611, the rendering engine 612, etc. The flow of the application corresponding processing to be executed is shown.
- the video / audio compatible processing represents processing related to content video and audio data
- the application compatible processing represents processing related to application data
- each unit such as the processing unit 601, the broadcast middleware 604, the DASH client 605, and the decoder 606 is activated (S601, S621). , S631).
- step S602 the broadcast middleware 604 receives signaling transmitted from the broadcast server 40 via the receiving unit 603.
- step S603 the broadcast middleware 604 processes the signaling received in the process of step S602.
- LLS signaling including SLT metadata and SLS signaling including USD metadata, S-TSID metadata, and MPD metadata are processed as signaling.
- the application URL is described in SLT metadata or SLS signaling (for example, metadata such as USD, S-TSID, MPD, etc.).
- step S604 the broadcast middleware 604 notifies the DASH client 605 of the MPD metadata acquired in the process of step S603.
- step S622 the DASH client 605 processes the MPD metadata notified in the process of step S604.
- step S605 the broadcast middleware 604 receives the DASH segment transmitted from the broadcast server 40 via the receiving unit 603.
- step S606 the broadcast middleware 604 transfers the DASH segment received in the process of step S605 to the DASH client 605.
- step S623 the DASH client 605 processes the DASH segment transferred in step S606 based on the MPD metadata processing result in step S622.
- step S624 the decoder 606 decodes the video and audio data obtained by the processing in step S623.
- step S625 the rendering engine 612 renders the video and audio data obtained by the process in step S624.
- the video of the content such as a program is displayed and the sound is output via the output unit 607.
- the DASH client 605, the decoder 606, and the rendering engine 612 perform the processing in steps S622 to S625, thereby reproducing the content such as the selected program. .
- the broadcast middleware 604 performs application for signaling such as SLT metadata or SLS signaling (for example, metadata such as USD, S-TSID, MPD) based on the processing result of the signaling in step S603. Determine whether the URL is described.
- signaling such as SLT metadata or SLS signaling (for example, metadata such as USD, S-TSID, MPD)
- step S607 If it is determined in step S607 that the application URL is described in the signaling, the process proceeds to step S608.
- step S608 the broadcast middleware 604 receives an application transmitted from the broadcast server 40 via the receiving unit 603 based on the application URL described in the signaling, according to the control from the application control unit 611.
- step S609 the broadcast middleware 604 transfers the application received in step S608 to the application control unit 611.
- step S632 the application control unit 611 immediately starts the application transferred in the process of step S609.
- step S633 the rendering engine 612 renders data of the application activated in the process of step S632. Thereby, on the client device 60, the video of the application accompanying the content such as a program is displayed.
- the application control unit 611 and the rendering engine 612 perform the processing in steps S632 to S633, thereby starting the application.
- the application may be executed in the background as non-display as well as being displayed on the screen together with the video of the content such as the program.
- step S607 If it is determined in step S607 that the application URL is not described in the signaling, the processing in steps S608 to S609 is skipped. That is, in this case, the application associated with the content is not activated.
- the broadcast middleware 604 is transmitted from the broadcast server 40 via the reception unit 603.
- the switching destination service signaling is received and processed (S610).
- step S611 the broadcast middleware 604, based on the processing result of the signaling in step S610, if the application URL is described in the signaling such as SLT metadata, the application URL of the application being started Determine if it is the same as the app URL.
- step S611 If it is determined in step S611 that the application URL described in the signaling is different from the application URL of the active application, the process proceeds to step S612.
- step S612 the broadcast middleware 604 receives an application transmitted from the broadcast server 40 via the receiving unit 603 based on the application URL described in the signaling in accordance with the control from the application control unit 611.
- step S613 the broadcast middleware 604 transfers the application received in step S612 to the application control unit 611.
- step S634 the application control unit 611 stops (ends) the application that has been started in the process of step S632.
- step S635 the application control unit 611 immediately starts the new application transferred in the process of step S613.
- step S636 the rendering engine 612 renders data of the new application activated in the process of step S635.
- the video of the new application activated in the process of step S635 is displayed instead of the video of the application activated in the process of step S632.
- step S611 determines whether the application URL is described in the signaling and is the same as the application URL of the active application. If it is determined in step S611 that the application URL is described in the signaling and is the same as the application URL of the active application, the process proceeds to step S614.
- step S614 the broadcast middleware 604 notifies the application control unit 611 of the service ID or channel number (major channel number) of the switching destination service.
- the application control unit 611 recognizes the service ID or channel number of the service to be switched to the application that has been started in step S632, and the application detects that the service has switched. It can be so.
- step S611 If it is determined in step S611 that the application URL is not described in the signaling, the processing in steps S612 to S614 is skipped.
- the application itself may actively switch the service by the interaction with the user or other events.
- the application calls a service switching API (Application Programming Interface) or the like.
- service switching API Application Programming Interface
- the client device 60 when content of a certain service is being played back, when the application is explicitly stopped, control that can be interpreted by the target application using a DASH event defined in MPEG-DASH It is also possible to stop the application by a command.
- an event notification mechanism called a DASH event
- two types of event transfer methods are defined. That is, the first transfer method is an MPD event, and the second transfer method is an in-band event (in-band event signaling).
- the operation of the application is controlled using these MPD events and in-band events.
- an MPD event method a method for controlling the operation of an application using an MPD event
- an in-band event in-band event signaling
- an EventStream element is added for each period in the MPD metadata, and information about the event is described there.
- the event firing schedule and event data to be processed by the client device 60 at the firing timing of each event are described in the MPD metadata.
- the client device 60 analyzes the MPD metadata, so that processing using the event data is performed at the timing of firing a predetermined event.
- FIG. 10 is a diagram illustrating a description example of MPD metadata in the MPD event method.
- the Period element is a unit for describing the configuration of a service such as content.
- the AdaptationSet element and the Representation element are used for each stream of service components such as video, audio, and caption, and can describe the attributes of each stream.
- the availabilityStartTime attribute of the MPD element that is the root element represents the UTC time of the start of the first Period element.
- the startTime attribute of the Period element represents an offset time from the availabilityStartTime attribute of the MPD element.
- an EventStream element is added in addition to the AdaptationSet element and Representation element in which information for each stream of service components such as video and audio is described. That is, the event specified by this EventStream element is associated with the stream of the service component specified by the AdaptationSet element.
- EventStream element With this EventStream element, the event firing schedule in the unit of the Period element and the event related data to be processed by the client device 60 at the timing of each event firing (to be passed to the application activated (running) on the client device 60) Can be described.
- the event type is defined by the schemeIdUri attribute of the EventStream element, and event-related data can be described in the content part of the Event element of the EventStream element. That is, the format (what should be stored) of event-related data stored in the content part of the Event element is defined (specified) by the value of the schemeIdUri attribute (in this example, “urn: xxx”).
- Event-related data-1 in the content part of the first Event element, the duration attribute is determined from the firing time that is “0” specified by the presentationTime attribute.
- Event-related data-1 can be passed to a running application in an event that lasts for a unit time of “1000” specified by.
- Event-related data-2 in the content part of the second Event element, for example, “4000” specified by the duration attribute from the firing time “1000” specified by the presentationTime attribute.
- Event-related data-2 can be passed to a running application by an event that lasts for a unit time.
- processing of a unique protocol that can be commonly understood by the transmission side system 5 and the client device 60 of FIG. 1 is realized. can do.
- processing of the unique protocol corresponds to, for example, processing such as changing the display content of an application executed on the client device 60 or stopping execution thereof.
- the MPD event method can be applied only when the content of the Period element described in the MPD metadata can be determined before sending the MPD metadata in the transmission side system 5.
- step S311 the application control event generation unit 313 generates an application control event.
- step S312 the transmission unit 303 transmits the application control event generated in step S311 to the DASH server 10.
- steps S111 to S113 in FIG. 11 is executed by the DASH server 10. Further, the DASH server 10 receives the application control event transmitted in step S312.
- step S111 when generating the MPD metadata, the MPD generation unit 111 stores the application control event generated by the application server 30 in the MPD metadata as an MPD event.
- the EventStream element is described in the Period element, and the application control event generated by the application server 30 is described as the event related data.
- “urn: atsc: applicationPrivateEvent” is specified in the schemeIdUri attribute of the EventStream element.
- step S112 the DASH segment generation unit 112 processes a content such as a program to generate a DASH segment whose reproduction is managed by the MPD metadata generated in the process of step S111.
- step S113 the transmission unit 103 transmits the MPD metadata generated in the process of step S111 to the signaling server 20, and transmits the DASH segment generated in the process of step S112 to the broadcast server 40.
- the signaling server 20 receives the MPD metadata transmitted in the process of step S113.
- step S211 the signaling generation unit 211 generates signaling.
- LLS signaling including SLT metadata and SLS signaling including USD metadata, S-TSID metadata, and MPD metadata are generated.
- MPD metadata includes MPD events (application control events).
- step S212 the transmission unit 203 transmits the signaling generated in step S211 to the broadcast server 40.
- steps S411 to S412 in FIG. In the broadcast server 40, the DASH segment transmitted in the process of step S113 and the signaling transmitted in the process of step S212 are received.
- the transmission unit 403 transmits the signaling generated by the signaling server 20 and the DASH segment generated by the DASH server 10 via the transmission path 80 (broadcast delivery) (S411 to S412).
- the application control event is generated by the application server 30 in the processing on the transmission side in FIG. 11, a dedicated event server for generating the application control event may be provided. Further, the signaling or DASH segment may be distributed by the communication server 50 via communication.
- the broadcast middleware 604 receives and processes the signaling from the broadcast server 40, and notifies the DASH client 605 of the MPD metadata.
- step S651 the DASH client 605 processes the MPD metadata notified in the process of step S643.
- step S652 the DASH client 605 extracts an application control event stored as an MPD event from the MPD metadata based on the processing result of the MPD metadata in step S651.
- the EventStream element is described in the Period element, and the application control event is described as the event-related data, and the application control event is extracted therefrom.
- “urn: atsc: applicationPrivateEvent” is specified in the schemeIdUri attribute of the EventStream element.
- step S653 the DASH client 605 notifies the application control unit 611 of the application control event extracted in the process of step S652.
- step S661 the application control unit 611 receives the application control event notified in the process of step S653.
- step S662 the application control unit 611 performs a unique protocol process according to the application control event acquired in the process in step S661.
- the processing of the unique protocol is processing that can be commonly understood by the transmission-side system 5 and the client device 60. For example, processing such as changing the display content of an active application or stopping its execution is performed. Is called.
- steps S644 to S645 the DASH segment is received by the broadcast middleware 604 and transferred to the DASH client 605 in the same manner as steps S605 to S606 in FIG. Also, in steps S654 to S656, similar to steps S623 to S625 in FIG. 9, the DASH client 605, the decoder 606, and the rendering engine 612 perform processing related to content video and audio data, so that a program or the like is performed. The video of the content is displayed and the sound is output.
- the client device 60 can stop (end) the running application in accordance with the application control event by the processing in step S662 by performing the processing on the receiving side in FIG. Once is stopped, the application is not started until the application URL different from the application URL of the stopped application is specified in the SLS signaling of the same service (or the entry of the service in the SLT metadata). .
- Such simplification of the control model can simplify the life cycle control of the application. For example, the client device 60 can be easily mounted and tested, and the introduction cost can be reduced.
- the application control event is transmitted in the segment stream by inserting the MP4 box called DASHEventMessageBox having the box_type of “emsg” as the MP4 brand name into the DASH segment.
- DASHEventMessageBox having the box_type of “emsg” as the MP4 brand name
- emsg box a DASHEventMessageBox having a box_type of “emsg” in the DASHEventMessageBox.
- FIG. 13 is a diagram illustrating an arrangement example of an in-band event type DASHEventMessageBox.
- Event-related data-1 can be passed to a running application in an event that lasts for a unit time of “0xFFFF” arranged in the event_duration field from 1/1000 seconds later.
- Event related data-2 can be passed to the running application in an event that lasts for a unit time of “0xFFFF” arranged in the event_duration field from (x 1/1000 seconds later).
- the client device 60 executes It is possible to change the display contents of the application being executed or to stop the execution.
- the application control event is generated by the application control event generation unit 313 of the application server 30 and transmitted to the DASH server 10 in the same manner as steps S311 to S312 of FIG. 11.
- step S14 is executed by the DASH server 10. Further, the DASH server 10 receives the application control event transmitted in the process of step S322. In step S121, the MPD generation unit 111 generates MPD metadata.
- step S122 when generating the DASH segment, the DASH segment generation unit 112 stores the application control event as an in-band event in the emsg box (DASHEventMessageBox) and inserts it into the DASH segment (its box structure).
- DASHEventMessageBox an in-band event in the emsg box
- DASHEventMessageBox “urn: atsc: applicationPrivateEvent” is defined in the scheme_id_uri field, and the application control event generated by the application server 30 is arranged in the message_data field as event-related data.
- step S123 the transmission unit 103 transmits the MPD metadata generated in the process of step S121 to the signaling server 20, and transmits the DASH segment generated in the process of step S122 to the broadcast server 40.
- LLS signaling and SLS signaling are generated by the signaling generation unit 211 of the signaling server 20 and transmitted to the broadcast server 40 in the same manner as steps S211 to S212 of FIG. 11.
- step S421 to S422 in FIG. 14 the signaling generated by the signaling server 20 and the DASH segment generated by the DASH server 10 are transmitted by the transmission unit 403 of the broadcast server 40, as in steps S411 to S412 in FIG. And transmitted via the transmission path 80.
- the case where the application control event is generated by the application server 30 has been described, but a dedicated event for generating the application control event is described.
- a server may be provided.
- the signaling or DASH segment may be distributed by the communication server 50 via communication.
- the broadcast middleware 604 receives and processes the signaling from the broadcast server 40, and notifies the DASH client 605 of the MPD metadata.
- step S681 the DASH client 605 processes the MPD metadata notified in the process of step S673.
- the broadcast middleware 604 receives the DASH segment from the broadcast server 40 and transfers it to the DASH client 605.
- step S682 the DASH client 605 processes the DASH segment transferred in step S675 based on the processing result of the MPD metadata in step S681.
- step S683 the DASH client 605 extracts the application control event stored as an in-band event from the emsg box (DASHEventMessageBox) inserted in the DASH segment (box structure) based on the processing result in step S682. To do.
- DASHEventMessageBox “urn: atsc: applicationPrivateEvent” is defined in the scheme_id_uri field, and the application control event is arranged as event-related data in the message_data field. Application control events are extracted.
- step S684 the DASH client 605 notifies the application control event extracted in the process of step S683 to the application control unit 611.
- the application control unit 611 performs processing of a unique protocol corresponding to the application control event.
- the processing of the unique protocol is processing that can be commonly understood by the transmission-side system 5 and the client device 60. For example, processing such as changing the display content of an active application or stopping its execution is performed. Is called.
- steps S685 to S686 as in steps S655 to S656 in FIG. 12, processing related to content video and audio data is performed by the decoder 606 and the rendering engine 612. The video is displayed and the sound is output.
- the client device 60 can stop (end) the running application in accordance with the application control event by the processing in step S692 by performing the processing on the receiving side in FIG. Once is stopped, the application is not started until the application URL different from the application URL of the stopped application is specified in the SLS signaling of the same service (or the entry of the service in the SLT metadata). .
- Such simplification of the control model can simplify the life cycle control of the application. For example, the client device 60 can be easily mounted and tested, and the introduction cost can be reduced.
- DRM Digital Rights Management
- an application digest (FIG. 22 to be described later) including a digest value (hash value) obtained by a certain calculation procedure (algorithm) from an application using a DRM content protection mechanism.
- the application digest (app_digest_message) is stored by the following two methods.
- an application digest is inserted as a watermark into video encoded data, and then a VCL-NAL (Video Coding Layer Network Network Layer) unit is used as an ISOBMFF (ISO Base Media). It is transmitted as a sample in mdat of fragmented mp4 of (File Format).
- VCL-NAL Video Coding Layer Network Network Layer
- ISOBMFF ISO Base Media
- the application digest is directly stored in a non-VCL-NAL (Non
- this second method will be described as a non-VCL-NAL unit storage method.
- NAL Network Abstraction Layer
- VCL Video Coding Layer
- HEVC High Efficiency Video Coding
- It is a layer (network abstraction layer) provided with the lower system. Therefore, VCL and NAL have a separated structure.
- FIG. 16 is a diagram illustrating a configuration example of an embodiment (second embodiment) of a transmission system to which the present technology is applied.
- the transmission system 2 includes a transmission side system 7 and a reception side client device 60.
- the same reference numerals are given to the portions corresponding to the transmission system 1 of FIG. 1, and the description of the repeated portions will be omitted as appropriate.
- the transmission side system 7 is different from the transmission side system 5 of FIG. 1 in that a stream server 70 is newly provided in addition to the DASH server 10 to the communication server 50.
- Application server 30 generates an application digest.
- the application digest includes an application URL of the application and a digest value (hash value) generated by applying a predetermined algorithm to the application. included.
- the application server 30 transmits the application digest to the stream server 70 when the watermark storage method is adopted, and transmits the application digest to the DASH server 10 when the non-VCL-NAL unit storage method is adopted. To do.
- the stream server 70 processes a content (data) such as a program to generate a stream (baseband frame sequence). Also, the stream server 70 generates a VCL-NAL unit by encoding the baseband frame of the stream.
- the stream server 70 stores the application digest generated by the application server 30 in the watermark inserted in the baseband frame of the stream.
- the DASH server 10 processes the stream data transmitted from the stream server 70, generates a DASH segment, and transmits the DASH segment to the broadcast server 40 or the communication server 50.
- the DASH server 10 processes the DRM protected file obtained by encrypting the VCL-NAL unit including the watermark storing the application digest generated by the application server 30. , Generate a DASH segment.
- the DASH server 10 when the non-VCL-NAL unit storage method is adopted, the DASH server 10 generates a non-VCL-NAL unit that stores the application digest generated by the application server 30, and the VCL-NAL unit and the non-VCL-NAL A DASH segment is generated by processing the DRM protected file obtained by encrypting the unit.
- the broadcast server 40 or the communication server 50 distributes the DASH segment generated by the DASH server 10, the signaling generated by the signaling server 20, and the application generated by the application server 30 via the transmission path 80 or the Internet 90. To do.
- the client device 60 reproduces content and executes an application associated with the content.
- the client device 60 is different from the client device 60 of FIG. 1 in that application verification processing is performed using an application digest.
- the client device 60 when adopting the watermark storage method, the client device 60 extracts the application digest stored in the watermark included in the DRM protected file, and performs the application verification process using the application digest.
- the client device 60 when adopting the non-VCL-NAL unit storage method, the client device 60 extracts the application digest stored in the non-VCL-NAL unit included in the DRM protected file, and uses the application digest to extract the application digest. Perform verification processing.
- the configuration of the transmission system 2 in FIG. 16 is an example, and other configurations may be adopted.
- the application digest may be generated not by the application server 30 but by a dedicated server.
- a dedicated server may perform processing related to the watermark when the watermark storage method is adopted.
- the signaling server 20 has the same configuration as that shown in FIG.
- the communication server 50 also has the same configuration as that described above.
- FIG. 17 is a diagram illustrating a configuration example of the stream server 70 of FIG.
- the stream server 70 includes a reception unit 701, a processing unit 702, and a transmission unit 703.
- the processing unit 702 includes a stream generation unit 711, a watermark inserter 712, and an encoder 713.
- the receiving unit 701 receives content (data) such as a program or CM from an external server (not shown) and supplies the content to the processing unit 702.
- contents (data) such as programs and commercials are provided from the outside.
- contents (data) such as programs and commercials are accumulated by the stream server 70. May be.
- the receiving unit 701 receives the application digest transmitted from the application server 30 and supplies the received application digest to the processing unit 702 (the watermark inserter 712).
- the processing unit 702 processes content (data) such as a program supplied from the reception unit 701 and supplies the processed content to the transmission unit 703.
- the processing unit 702 is supplied from the stream generation unit 711, the watermark inserter 712, and the encoder 713.
- the stream generation unit 711 generates a video stream (baseband frame sequence) by processing content (data) such as a program supplied from the reception unit 701. Although a detailed description is omitted here, the stream generation unit 711 generates an audio stream by processing the content (data thereof).
- the application digest generated by the application server 30 is added to the watermark (watermark payload) inserted into the baseband frame of the stream generated by the stream generator 711. Is stored.
- the watermark inserter 712 operates only when the watermark storage method is adopted, and when the non-VCL-NAL unit storage method is adopted, the stream server 70 needs to operate the watermark inserter 712. There is no (it is not necessary).
- the encoder 713 encodes the baseband frame of the video stream generated by the stream generation unit 711 according to a predetermined encoding method (for example, HEVC), and generates a VCL-NAL unit. Although detailed description is omitted here, the encoder 713 also encodes the audio stream generated by the stream generation unit 711 according to a predetermined encoding method (for example, AAC).
- a predetermined encoding method for example, HEVC
- AAC predetermined encoding method
- the transmission unit 703 transmits the stream data including the VCL-NAL unit (and audio data) supplied from the processing unit 702 (the encoder 713) to the DASH server 10.
- the stream server 70 is configured as described above.
- FIG. 18 is a diagram illustrating a configuration example of the DASH server 10 of FIG.
- the same reference numerals are given to the portions corresponding to the DASH server 10 in FIG. 2, and description thereof will be omitted as appropriate.
- the DASH server 10 includes a receiving unit 101, a processing unit 102, and a transmitting unit 103.
- the processing unit 102 includes an encryption unit 113, a DRM protected file generation unit 114, and a non-VCL-NAL unit generation unit 115.
- the receiving unit 101 receives stream data transmitted from the stream server 70 and supplies the stream data to the processing unit 102.
- the processing unit 102 processes the stream data supplied from the reception unit 101, generates a DASH segment, and supplies the DASH segment to the transmission unit 103.
- the transmission unit 103 transmits the DASH segment supplied from the processing unit 102 to the broadcast server 40 or the communication server 50.
- the DASH segment is generated as follows. That is, the encryption unit 113 encrypts the VCL-NAL unit generated by the stream server 70 according to a predetermined encryption method.
- the DRM protection file generation unit 114 processes the VCL-NAL unit encrypted by the encryption unit 113 to generate a DRM protection file.
- the DRM protected file is protected according to a DRM method such as PlayReady (registered trademark).
- the DASH segment generation unit 112 processes the DRM protection file generated by the DRM protection file generation unit 114 to generate a DASH segment.
- the DASH segment is generated as follows. That is, the non-VCL-NAL unit generation unit 115 generates a non-VCL-NAL unit that stores the application digest generated by the application server 30. Also, the encryption unit 113 encrypts the VCL-NAL unit generated by the stream server 70 and the non-VCL-NAL unit generated by the non-VCL-NAL unit generation unit 115 according to a predetermined encryption method.
- the DRM protection file generation unit 114 processes the VCL-NAL unit and the non-VCL-NAL unit encrypted by the encryption unit 113 to generate a DRM protection file.
- the DRM protected file is protected according to a DRM method such as PlayReady (registered trademark).
- the DASH segment generation unit 112 processes the DRM protection file generated by the DRM protection file generation unit 114 to generate a DASH segment.
- the non-VCL-NAL unit generation unit 115 operates only when the non-VCL-NAL unit storage method is employed. When the watermark storage method is employed, the non-VCL-NAL unit generation unit 115 performs non-VCL-NAL unit generation in the DASH server 10. It is not necessary to operate the unit generator 115 (it is not necessary to provide it).
- the DASH server 10 is configured as described above.
- FIG. 19 is a diagram illustrating a configuration example of the application server 30 of FIG.
- the same reference numerals are given to the portions corresponding to the application server 30 of FIG. 4, and the description thereof will be omitted as appropriate.
- the application server 30 includes a reception unit 301, a processing unit 302, and a transmission unit 303.
- the processing unit 302 includes an application digest generation unit 314 in addition to the application URL generation unit 311, the application generation unit 312, and the application control event generation unit 313.
- the application digest generation unit 314 generates an application digest including a digest value (hash value) obtained by a certain calculation procedure (algorithm) from the application generated by the application generation unit 312, and supplies the application digest to the transmission unit 303.
- a digest value (hash value) obtained by a certain calculation procedure (algorithm) from the application generated by the application generation unit 312, and supplies the application digest to the transmission unit 303.
- algorithm calculation procedure
- the transmission unit 303 transmits the application digest supplied from the application digest generation unit 314 to the DASH server 10 or the stream server 70.
- the application digest is transmitted to the stream server 70.
- the non-VCL-NAL unit storage method is adopted, the application digest is transmitted to the DASH server 10.
- Application server 30 is configured as described above.
- FIG. 20 is a diagram illustrating a configuration example of the client device 60 of FIG.
- the same reference numerals are given to the portions corresponding to the client device 60 of FIG. 6, and description thereof will be omitted as appropriate.
- the client device 60 includes a processing unit 601, an input unit 602, a receiving unit 603, broadcast middleware 604, a DASH client 605, a decoder 606, an output unit 607, and a communication unit 608. Further, the processing unit 601 includes a watermark extractor 613 and an application digest validator 614 in addition to the application control unit 611 and the rendering engine 612, as compared with the processing unit 601 in FIG.
- the application verification process using the application digest is performed as follows. That is, the DASH client 605 (the DRM protected file processing unit) unpackages the DRM protected file obtained by processing the DASH segment.
- the DASH client 605 (decryption unit) decrypts the encrypted VCL-NAL unit obtained by unpackaging the DRM protected file according to a predetermined decryption method.
- the decoder 606 decodes the VCL-NAL unit processed by the DASH client 605 according to a predetermined decoding method (for example, HEVC).
- a predetermined decoding method for example, HEVC.
- the watermark extractor 613 extracts the watermark inserted in the baseband frame obtained by decoding the VCL-NAL unit.
- the application digest validator 614 extracts the application digest stored in the watermark extracted by the watermark extractor 613.
- the application digest validator 614 compares the application digest stored in the watermark with the application digest corresponding to the application from the broadcast middleware 604. If the application digests to be compared match, the application digest validator 614 Launch the application from 604 (immediately).
- the application verification process using the application digest is performed as follows. That is, the DASH client 605 (the DRM protected file processing unit) unpackages the DRM protected file obtained by processing the DASH segment. Further, the DASH client 605 (decryption unit) decrypts the encrypted non-VCL-NAL unit obtained by unpackaging the DRM protected file according to a predetermined decryption method.
- the app digest validator 614 extracts the app digest stored in the non-VCL-NAL unit decrypted by the DASH client 605 (decryption unit thereof).
- the application digest validator 614 compares the application digest stored in the non-VCL-NAL unit with the application digest corresponding to the application from the broadcast middleware 604, and when the comparison target application digest matches.
- the application from the broadcast middleware 604 is activated (immediately).
- the application verification process using the application digest is performed by the watermark storage method or the non-VCL-NAL unit storage method.
- the watermark extractor 613 operates only when the watermark storage method is adopted.
- the client device 60 operates the watermark extractor 613. (It is not necessary to provide it.)
- the client device 60 is configured as described above.
- the client device 60 notifies the client device 60 of the application URL of the application when the application activation control is performed as the life cycle control of the application associated with the content.
- the application (application package) identified by the application URL is acquired and activated immediately.
- the application is acquired via broadcast or communication, but there is a risk that fraudulent acts such as replacement or falsification of the application URL or the application itself will be performed on the broadcast transmission path. Need to protect this.
- An encryption method using the security technology for example, IPSec (Security Architecture for Internet Internet) is assumed.
- the digest value (hash value) of the application itself calculated by the hash function algorithm in the transmission side system 7 in order to detect fraudulent activities such as replacement or falsification of the application The client device 60 is notified as an application digest. Then, the client device 60 uses the application digest (the digest value of the application itself) notified from the transmission-side system 7 to verify whether or not an illegal act such as replacement or falsification is performed on the application. Become.
- XML Signature a method defined by an XML signature
- W3C World Wide Web Consortium
- a predetermined algorithm is applied to the application distributed to the client device 60 by the application digest generation unit 314 of the application server 30.
- an application digest including the digest value (hash value) generated is generated.
- this application digest for example, the application URL of the target application and the digest value obtained by applying a predetermined algorithm such as MD5 (Message Digest Algorithm 5), SHA-1, or SHA-256 to the application URL Can be included.
- MD5 Message Digest Algorithm 5
- SHA-1 SHA-1
- SHA-256 SHA-256
- the application generated by the application server 30 by the broadcast server 40 (or the communication server 50) is transmitted to the reception-side client device 60 via the transmission path 80 (or the Internet 90). Sent.
- the application digest generated by the application server 30 is protected by the broadcast server 40 (or the communication server 50) by the watermark storage method or the non-VCL-NAL unit storage method.
- the data is transmitted to the client device 60 on the receiving side via the transmission path 80 (or the Internet 90).
- the client device 60 on the receiving side an application transmitted from the transmitting side system 7 on the transmitting side is received.
- the client device 60 on the reception side applies the same algorithm as that of the transmission side system 7 on the transmission side to the application distributed (received) from the transmission side system 7 on the transmission side, and generates an application digest (digest value).
- the digest value is obtained by applying a predetermined algorithm such as MD5, SHA-1, or SHA-256 to the application URL of the target application.
- an application digest transmitted from the transmission-side transmission system 7 and protected by the watermark storage method or the non-VCL-NAL unit storage method is received. .
- the client device 60 on the receiving side uses the application digest (digest value) protected by the watermark storage method or the non-VCL-NAL unit storage method and the application obtained by applying the same algorithm as that of the transmission side.
- the digest (digest value) is compared to determine whether the app digests (digest value) match.
- the receiving-side client device 60 processes the application distributed from the transmitting-side transmitting-side system 7 as a legitimate application such as immediately starting the application. To do.
- the client device 60 on the receiving side determines that the application digests (digest values) do not match, the application distributed from the transmitting side system 7 on the transmitting side is unreasonable, for example, As a simple application.
- DRM digital rights management
- DRM digital rights management
- DRM for example, PlayReady (registered trademark), Marlin, Widevine, Verimatrix, and other methods can be applied, but various formats for application binding protection that can be commonly applied to any method. Should be specified. As a result, the client device 60 can verify whether the binding is with a valid application regardless of the difference in each method, regardless of which method is applied as the DRM.
- FIG. 22 is a diagram illustrating an example of syntax of an application digest (app_digest_message).
- ⁇ 8-bit uri_strlen represents the length of the URL (application URL) that identifies the target application.
- Uri_string () of 8 ⁇ uri_strlen bits represents a URL (application URL) for identifying a target application.
- 8-bit digest_type indicates the algorithm type of the cryptographic hash function. For example, as shown in FIG. 23, when “0x01” is specified as the digest_type, this indicates that the algorithm is MD5 (Message Digest Algorithm 5). For example, when “0x02” is specified as the digest_type, SHA-1 and “0x03” are specified, and SHA-256 is specified as the algorithm. SHA is an abbreviation for Secure Hash Algorithm. Also, 0x00, 0x04 to 0xFF are reserved values for future expansion (reserved).
- 8-bit digest_len represents the byte length of the digest value of the target application.
- a digest_value of 8 ⁇ digest_len bits represents the digest value of the target application.
- the application digest (app_digest_message) of FIG. 22 will be stored according to the watermark storage system mentioned above or the non-VCL-NAL unit storage system.
- the application digest is inserted into the video encoded data as a watermark, and then transmitted as a VCL-NAL unit as a sample in the mdat of fragmented mp4 of ISOBMFF.
- the application digest is stored directly in the non-VCL-NAL unit and transmitted as a sample in the mdat of fragmented mp4 of ISOBMFF.
- FIG. 24 shows an example of a segment data format corresponding to ISOBMFF.
- the media segment Media (Segment)
- the application digest is stored in the mdat among the moof and mdat constituting the Movie fragment of the sub-segment (Sub Segment).
- FIG. 25 is a diagram for explaining the outline of the watermark storage method.
- FIG. 25 schematically shows a broadcast stream transmitted from the broadcast server 40 of the transmission side system 7 to the client device 60 via the transmission path 80.
- This broadcast stream has a part encrypted by DRM (encrypted pipe) and an unencrypted part (unencrypted pipe).
- an application digest for verifying an application (App) is stored in the watermark (Watermark) by using an encryption pipe so that the application digest is protected.
- the application digest includes application identification information (for example, application URL) and an application digest value.
- the client device 60 extracts the application URL and the digest value of the application stored in the watermark by solving the DRM during the reproduction of the content such as a program, and the application specified by the application URL using the digest value is extracted. Verify whether it is a legitimate application. Here, verification is performed by comparing the digest value stored in the watermark with the digest value corresponding to the application acquired according to the application URL, and if these digest values match, the application URL identifies It is determined that the application to be executed is a valid application.
- video and audio streams of content such as programs are transmitted and protected by a secure encryption pipe by DRM, but transmitted by a ROUTE session on IP / UDP.
- the VCL-NAL unit stored in the mdat of the movie fragment of the media segment that constitutes the file (DASH segment / MP4 fragment file) of the (content) DASH to be stored stores a watermark including the application digest.
- an application digest field including an application URL and a digest value of the application is defined.
- end-to-end security is ensured by diverting the secure encryption pipe by DRM for the protection of content such as programs to the transmission of application digests.
- content such as programs to the transmission of application digests.
- DRM digital rights management
- application authentication can be performed using existing DRM without building a platform (infrastructure) for full-scale application authentication using PKI or the like. Therefore, cost reduction can be ensured.
- FIG. 26 is a diagram illustrating a method for storing an application digest using a video watermark (watermark).
- a predetermined line for example, two lines
- a predetermined line for example, two lines
- 1-bit or 2-bit information can be transmitted for each block.
- a watermark payload (Watermark ⁇ ⁇ ⁇ payload) can be transmitted using a predetermined line (for example, two lines) of video encoded data.
- the app digest message (app_digest_message ()) shown in FIG. 22 can be arranged as a WM message (wm_message ()).
- This application digest message includes uri_string () storing the application URL and digest_value storing the digest value.
- FIG. 27 is a diagram illustrating an example of the syntax of a watermark payload.
- the 16-bit run_in_pattern specifies the transmission pattern of the video watermark and the resolution of one area expressed in the range from white to black.
- this transmission pattern for example, one line or two lines are designated.
- 8 to 12 bits are designated as the resolution of one area.
- Wm_message_block () represents the message area of the watermark.
- 8-bit zero_pad represents zero padding.
- FIG. 28 is a diagram illustrating an example of the syntax of the WM message block (wm_message_block ()) of FIG.
- WM message ID is specified in 8-bit wm_message_id.
- the 8-bit wm_message_block_length specifies the WM message block length.
- the 4-bit wm_message_version specifies the WM message version.
- 2-bit fragment_number and 2-bit last_fragment information about a fragment is specified.
- wm_message () specifies a WM message corresponding to the value specified in the WM message ID. For example, as shown in FIG. 29, when “0x08” is designated as the WM message ID, an application digest message (app_digest_message ()) is arranged as the WM message. Note that the WM message includes error detection codes such as message_CRC_32 and CRC_32.
- step S351 the application URL generation unit 311 generates an application URL.
- step S352 the application generation unit 312 generates an application identified by the application URL generated in the process of step S351.
- step S353 the transmission unit 303 transmits the application URL generated in the process of step S351 to the signaling server 20, and transmits the application generated in the process of step S352 to the broadcast server 40.
- step S354 the application digest generation unit 314 generates an application digest.
- the application digest is generated by applying a predetermined algorithm (for example, MD5) to the application URL generated in the process of step S351 and the application generated in the process of step S352.
- a digest value (hash value) is included.
- step S355 the transmission unit 303 transmits the application digest generated in the process of step S354 to the stream server 70.
- step S701 the stream generation unit 711 generates a stream (baseband frame sequence) by processing content (data thereof) such as a program stored in the reception unit 701.
- step S702 the watermark inserter 712 stores the application digest generated by the application server 30 in the watermark (watermark payload) inserted into the baseband frame of the stream generated in the process of step S701.
- step S703 the encoder 713 encodes the baseband frame processed in step S702 according to a predetermined encoding method (for example, HEVC) to generate a VCL-NAL unit.
- step S704 the transmission unit 703 transmits the VCL-NAL unit generated in the process of step S703 to the DASH server 10.
- steps S151 to S156 in FIG. 30 is executed by the DASH server 10. Further, the DASH server 10 receives the VCL-NAL unit transmitted in the process of step S704.
- step S151 the MPD generation unit 111 generates MPD metadata.
- step S152 the transmission unit 103 transmits the MPD metadata generated in the process of step S151 to the signaling server 20.
- step S153 the encryption unit 113 encrypts the VCL-NAL unit generated by the stream server 70 in accordance with a predetermined encryption method.
- step S154 the DRM protection file generation unit 114 processes the VCL-NAL unit encrypted in the process of step S153 to generate a DRM protection file.
- step S155 the DASH segment generation unit 112 processes the DRM protected file generated in the process of step S154 to generate a DASH segment.
- step S156 the transmission unit 103 transmits the DASH segment generated by the process in step S155 to the broadcast server 40.
- the signaling server 20 receives the MPD metadata transmitted in the process of step S152 and the application URL transmitted in the process of step S353.
- step S251 the signaling generation unit 211 generates signaling.
- LLS signaling including SLT metadata and SLS signaling including USD metadata, S-TSID metadata, and MPD metadata are generated.
- the application URL generated by the application server 30 is described in SLT metadata or SLS signaling (for example, metadata such as USD, S-TSID, and MPD).
- step S252 the transmission unit 203 transmits the signaling generated in the process of step S251 to the broadcast server 40.
- steps S451 to S453 in FIG. In the broadcast server 40, the DASH segment transmitted in the process of step S156, the signaling transmitted in the process of step S252, and the application transmitted in the process of step S353 are received.
- the transmission unit 403 transmits the application generated by the application server 30, the signaling generated by the signaling server 20, and the DASH segment generated by the DASH server 10 via the transmission path 80 (broadcasting). (S451 to S453).
- FIG. 31 in addition to the processing executed by the broadcast middleware 604 and the DASH client 605, the video / audio compatible processing executed by the decoder 606, the rendering engine 612, the watermark extractor 613, the application control unit 611, and the rendering The flow of application corresponding processing executed by the engine 612, the application digest validator 614, and the like is shown.
- the video / audio compatible processing represents processing related to content video and audio data
- the application compatible processing represents processing related to application data
- step S801 the broadcast middleware 604 receives the signaling transmitted from the broadcast server 40 via the receiving unit 603.
- step S802 the broadcast middleware 604 processes the signaling received in the process of step S801.
- LLS signaling including SLT metadata and SLS signaling including USD metadata, S-TSID metadata, and MPD metadata are processed as signaling.
- the application URL generated by the application server 30 is described in SLT metadata or SLS signaling (for example, metadata such as USD, S-TSID, and MPD).
- step S803 the broadcast middleware 604 notifies the DASH client 605 of the MPD metadata acquired in the process of step S802, and notifies the application control unit 611 of the application URL acquired in the process of step S802.
- step S804 the broadcast middleware 604 receives the application transmitted from the broadcast server 40 via the receiving unit 603 based on the application URL described in the signaling in accordance with the control from the application control unit 611.
- step S805 the broadcast middleware 604 transfers the application received in step S804 to the application control unit 611.
- step S831 the application control unit 611 acquires the application transferred in the process of step S805.
- step S832 the application digest validator 614 generates an application digest corresponding to the application acquired in the process of step S831.
- step S832 the same algorithm (for example, MD5) as the process of step S354 (FIG. 30) of the transmission side system 7 is applied to the application acquired in the process of step S831, thereby digesting.
- a value (hash value) is generated.
- step S806 the broadcast middleware 604 receives the DASH segment transmitted from the broadcast server 40 via the receiving unit 603.
- step S ⁇ b> 807 the broadcast middleware 604 transfers the DASH segment received in step S ⁇ b> 806 to the DASH client 605.
- step S812 the DASH client 605 processes the DASH segment transferred in step S807 based on the MPD metadata processing result in step S811.
- step S813 the DASH client 605 (its DRM protection file processing unit) processes the DRM protection file obtained in step S812 and unpackages the DRM protection file.
- step S814 the DASH client 605 (decryption unit) decrypts the encrypted VCL-NAL unit obtained by the process in step S814 according to a predetermined decryption method.
- step S815 the DASH client 605 transfers the VCL-NAL unit decoded in the process of step S814 to the decoder 606.
- step S821 the decoder 606 decodes the VCL-NAL unit transferred in step S815 according to a predetermined decoding method (for example, HEVC).
- step S822 the watermark extractor 613 extracts the watermark (video watermark) inserted into the baseband frame obtained by the process in step S821.
- step S823 the application digest validator 614 extracts the application digest stored in the watermark (watermark payload) extracted in the process of step S822.
- the rendering engine 612 renders video and audio data obtained in the process of step S821, thereby outputting video and audio of content such as a program. (S824).
- step S833 the application digest validator 614 verifies the application digest by comparing the application digest generated in step S832 with the application digest extracted in step S823.
- step S834 the application digest validator 614 determines whether or not the application digests to be compared match based on the verification result in step S833.
- the application digest (digest value) extracted in the process of step S823 is generated by the process of step S354 (FIG. 30) (by the application server 30) of the transmission side system 7, and is the process of step S832. It is generated by applying the same algorithm (for example, MD5) as the application digest (digest value) generated by the processing. Therefore, if the application digests (digest values) to be compared in the determination process in step S834 match, the target application can be regarded as a valid application.
- step S834 If it is determined in step S834 that the application digests to be compared match, the process proceeds to step S835.
- step S835 the application control unit 611 starts (immediately) the application acquired in the process of step S831. That is, in this case, the client device 60 regards the received application as a legitimate application and permits its activation.
- step S836 the rendering engine 612 renders the data of the application activated in step S835. Thereby, for example, on the client device 60, the video of the application accompanying the content such as a program is displayed.
- step S834 if it is determined in step S834 that the application digests to be compared do not match, the processes in steps S835 to S836 are skipped. That is, in this case, the client device 60 regards the received application as an illegal application and rejects activation thereof. In addition, when such an unjust application is detected, other operations may be performed, for example, notification to a user or a related broadcasting station.
- FIG. 32 is a diagram for explaining the outline of the non-VCL-NAL unit storage method.
- FIG. 32 schematically illustrates a broadcast stream transmitted from the broadcast server 40 to the client device 60 via the transmission path 80, as in FIG.
- This broadcast stream has a part encrypted by DRM (encrypted pipe) and an unencrypted part (unencrypted pipe).
- the application digest (App Digest) for verifying the application (App) is stored in the Video-SEI stored in the NAL unit by using an encryption pipe. Be protected.
- the NAL (Network Abstraction Layer) unit contains various data, and can be roughly classified into VCL (Video Coding Layer) and non-VCL (Non Video Coding Layer). Can do.
- VCL Video Coding Layer
- non-VCL Non Video Coding Layer
- the VCL-NAL unit is compressed slice data (encoded data) of video.
- non-VCL-NAL unit is for storing other auxiliary information.
- non-VCL-NAL units include VPS (Video Parameter Set), SPS (Sequence Parameter Set), PPS (Picture Parameter Set), SEI (Supplemental Enhancement Information), and the like.
- the SEI message is for storing additional information that is not essential for decoding the VCL, and can include information that is defined by the user (User data ⁇ ⁇ ⁇ unregistered). Can be stored.
- this application digest includes application identification information (for example, application URL) and an application digest value.
- the client device 60 extracts the application URL and the digest value of the application stored in the non-VCL-NAL unit (SEI message) by solving the DRM during the reproduction of the content such as the program, and uses the digest value to It is verified whether or not the application specified by the URL is a valid application.
- verification is performed by comparing the digest value stored in the non-VCL-NAL unit (SEI message) with the digest value corresponding to the application acquired according to the application URL, and these digest values match
- the application specified by the application URL is determined to be a valid application.
- end-to-end security can be achieved by diverting the secure encryption pipe by DRM for protecting content such as programs to the transmission of application digests.
- DRM secure encryption pipe
- a malicious third party such as alteration or alteration of an application or alteration of the association between content and an application, can be avoided.
- application authentication can be performed using existing DRM without building a full-scale application authentication platform (infrastructure) using PKI or the like. Since it becomes possible, cost reduction can be guaranteed.
- the client device 60 must always activate the watermark extractor 613 (FIG. 20) in order to extract the application digest stored in the watermark.
- the non-VCL-NAL unit storage method when the non-VCL-NAL unit storage method is adopted, the application digest can be extracted without starting (without providing) the watermark extractor 613.
- Step 33 is executed by the application server 30.
- Steps S361 through S365 in FIG. In steps S361 to S365, as in steps S351 to S355 of FIG. 30, an application URL, an application, and an application digest are generated and transmitted to the target server.
- the application digest is transmitted to the DASH server 10 instead of the stream server 70.
- the application digest is generated by applying a predetermined algorithm (for example, MD5) to the application URL generated in the process of step S361 and the application generated in the process of step S362, for example.
- a predetermined algorithm for example, MD5
- Digest value digest value
- step S711 a stream (baseband frame sequence) is generated as in step S701 of FIG.
- step S712 the encoder 713 encodes the baseband frame generated in step S711 in accordance with a predetermined encoding method (for example, HEVC) to generate a VCL-NAL unit.
- step S713 the transmission unit 703 transmits the VCL-NAL unit generated in the process of step S712 to the DASH server 10.
- steps S161 to S167 in FIG. 33 is executed by the DASH server 10.
- the DASH server 10 receives the application digest transmitted in step S365 in addition to the VCL-NAL unit transmitted in step S713.
- MPD metadata is generated and transmitted to the signaling server 20 in the same manner as steps S151 to S152 in FIG.
- the non-VCL-NAL unit generation unit 115 generates a non-VCL-NAL unit that stores the application digest generated by the application server 30.
- an SEI message that can be uniquely defined by the user can be used as the non-VCL-NAL unit.
- step S164 the encryption unit 113 encrypts the VCL-NAL unit generated by the stream server 70 and the non-VCL-NAL unit generated in step S163 according to a predetermined encryption method.
- step S165 the DRM protected file generation unit 114 processes the VCL-NAL unit and the non-VCL-NAL unit encrypted in the process of step S164 to generate a DRM protected file.
- step S166 the DASH segment generation unit 112 processes the DRM protected file generated in the process of step S165 to generate a DASH segment.
- step S167 the transmission unit 103 transmits the DASH segment generated in the process of step S166 to the broadcast server 40.
- steps S261 to S262 in FIG. In steps S261 through S262, signaling is generated and transmitted to the broadcast server 40, as in steps S251 through S252 of FIG.
- steps S461 to S463 in FIG. the transmission unit 403 transmits the application, signaling, and DASH segment via the transmission path 80 (broadcast delivery).
- the broadcasting middleware 604 receives and processes the signaling, application, and DASH segment transmitted from the broadcast server 40.
- step S851 MPD metadata is processed by the DASH client 605 as in step S811 of FIG. Further, in steps S871 to S872, as in steps S831 to S832 of FIG. 31, the application control unit 611 acquires an application corresponding to the application URL, and the application digest validator 614 corresponds to the application. An app digest is generated.
- step S832 the same algorithm (for example, MD5) as the process of step S364 (FIG. 33) of the transmission side system 7 is applied to the application acquired in the process of step S871, thereby digesting.
- a value (hash value) is generated.
- step S852 the DASH client 605 processes the DASH segment transferred in step S847 based on the MPD metadata processing result in step S851.
- step S853 the DASH client 605 (its DRM protection file processing unit) processes the DRM protection file obtained in step S852, and unpackages the DRM protection file.
- step S854 the DASH client 605 (decryption unit thereof) decrypts the encrypted VCL-NAL unit obtained in the process of step S853 according to a predetermined decryption method.
- step S855 the DASH client 605 transfers the VCL-NAL unit decoded in step S854 to the decoder 606.
- step S861 the decoder 606 decodes the VCL-NAL unit transferred in step S855 according to a predetermined decoding method (for example, HEVC).
- step S862 the rendering engine 612 renders video and audio data obtained by the processing in step S861.
- the client device 60 outputs video and audio of content such as a program.
- step S856 the DASH client 605 (decryption unit) decrypts the encrypted non-VCL-NAL unit obtained in the process of step S853 according to a predetermined decryption method.
- step S857 the application digest validator 614 extracts the application digest stored in the non-VCL-NAL unit decoded in the process of step S856.
- step S873 the application digest validator 614 verifies the application digest by comparing the application digest generated in the process of step S872 with the application digest extracted in the process of step S857.
- step S874 the application digest validator 614 determines whether or not the application digests to be compared match based on the verification result in step S873.
- the application digest (digest value) extracted by the process of step S857 is generated by the process of step S364 (FIG. 33) (by the application server 30) of the transmission side system 7, and is the process of step S872. It is generated by applying the same algorithm (for example, MD5) as the application digest (digest value) generated by the processing. Therefore, if the application digests (digest values) to be compared in the determination process in step S874 match, the target application can be regarded as a valid application.
- step S874 If it is determined in step S874 that the application digests to be compared match, the process proceeds to step S875.
- step S874 if it is determined in step S874 that the application digests to be compared do not match, the received application is regarded as an illegal application and the application is not started.
- FIG. 35 is a diagram illustrating an example of the format of SLT metadata in XML format.
- SLT format For example, among the elements and attributes, “@” is added to the attribute. Further, the indented element and attribute are specified for the upper element. These relationships are the same in other signaling formats described later.
- the SLT element is a root element and is an upper element of the bsid attribute, sltCapabilities attribute, sltInetUrl element, and Service element.
- the broadcast stream ID is specified in the bsid attribute.
- the sltCapabilities attribute information about required functions is specified.
- the base URL for acquiring ESG (Electronic Service Guide) and SLS signaling is specified in the sltInetUrl element.
- the sltInetUrl element is an upper element of the urlType attribute.
- a file type that can be used in the base URL is specified.
- the Service element is an upper element of the serviceId attribute, sltSvcSeqNum attribute, protected attribute, majorChannelNo attribute, minorChannelNo attribute, serviceCategory attribute, shortServiceName attribute, hidden attribute, broadbandAccessRequired attribute, svcCapabilities attribute, applicationUrl attribute, BroadcastSvcSignaling element, and svcInetUrl element.
- the service ID is specified in the serviceId attribute.
- the sltSvcSeqNum attribute information related to the version of SLT metadata is specified.
- encryption information indicating protection of the service is designated.
- the major channel number is specified in the majorChannelNo attribute.
- a minor channel number is specified in the minorChannelNo attribute.
- a service category is specified in the serviceCategory attribute.
- a short service name is specified in the shortServiceName attribute.
- the hidden attribute specifies whether the service is a hidden service.
- the broadbandAccessRequired attribute specifies whether or not it is necessary to access a communication line such as the Internet 90.
- Information such as functions necessary for decoding is specified in the svcCapabilities attribute.
- a URL (application URL) indicating the application acquisition location is specified.
- the application URL is information for identifying an entry (for example, index.html) when the application is configured by a plurality of files such as an HTML document file or an image file.
- the application is acquired in accordance with the application URL and activated immediately.
- the BroadcastSvcSignaling element when SLS signaling is acquired via broadcasting, information regarding the acquisition destination of the SLS signaling is specified.
- the BroadcastSvcSignaling element is an upper element of the slsProtocol attribute, slsMajorProtocolVersion attribute, slsMinorProtocolVersion attribute, slsPlpId attribute, slsDestinationIpAddress attribute, slsDestinationUdpPort attribute, and slsSourceIpAddress attribute.
- the slsMajorProtocolVersion attribute specifies the major version number of the SLS signaling protocol.
- the slsMinorProtocolVersion attribute specifies the minor version number of the SLS signaling protocol.
- slsPlpId an ID of a PLP (Physical Layer Layer) Pipe that transmits SLS signaling is specified.
- slsDestinationIpAddress the IP address of the destination (destination) of SLS signaling is specified.
- slsDestinationUdpPort the port number of the destination (destination) of SLS signaling is specified.
- slsSourceIpAddress the IP address of the source of SLS signaling is specified.
- the URL from which the SLS signaling is acquired is specified.
- the svcInetUrl element is an upper element of the urlType attribute.
- the urlType attribute file types that can be used with this URL are specified.
- the number of occurrences (Use) is shown.
- “1” is specified, only one element or attribute is always specified.
- “0..1” is specified, Specifying the element or attribute is optional. If “1..N” is specified, one or more elements or attributes are specified. If “0..N” is specified, one or more elements or attributes are specified. It is optional.
- unsignedShort or “unsignedByte” is specified as Data Type
- String indicates that the value of the element or attribute is a character string type.
- anyURI is specified
- the value of the element or attribute is the URI. This indicates that the character string has the form of.
- boolean is specified as Data Type, it indicates that the element or attribute is a Boolean type.
- language is specified as Data Type, it indicates that the value of the element or attribute is valid as the value of the xml: lang attribute.
- dateTime is specified, the element Alternatively, the attribute value indicates a specific date and time.
- FIG. 36 is a diagram showing an example of the format of XML metadata (USBD metadata) in XML format.
- the bundleDescription element is a root element and is an upper element of the userServiceDescription element (USD element).
- the userServiceDescription element is an upper element of the globalServiceID attribute, serviceId attribute, serviceStatus attribute, fullMPDUri attribute, sTSIDUri attribute, applicationUrl attribute, name element, serviceLanguage element, capabilityCode element, and deliveryMethod element.
- Global service ID is specified in the globalServiceID attribute.
- a service ID is specified in the serviceId attribute.
- information related to the service status is specified in the serviceStatus attribute.
- a URI for referring to MPD metadata is specified in the fullMPDUri attribute.
- a URI for referring to the S-TSID metadata is specified in the sTSIDUri attribute.
- a URL (application URL) indicating the application acquisition location is specified.
- the application URL is information for identifying an entry (for example, index.html) when the application is configured by a plurality of files such as an HTML document file or an image file.
- an application is acquired according to the application URL and activated immediately.
- the name element specifies the name of the ATSC 3.0 service.
- the name element is an upper element of the lang attribute.
- the lang attribute the language of the service name of ATSC 3.0 is specified.
- the serviceLanguage element a language that can be used for an ATSC 3.0 service is specified.
- the capabilityCode element a code related to the capability is specified.
- the deliveryMethod element is an upper element of the broadcastAppService element and the unicastAppService element.
- the broadcastAppService element is an upper element of the basePattern element, and specifies information related to distribution via broadcasting.
- the unicastAppService element is an upper element of the basePattern element, and specifies information related to delivery via communication.
- FIG. 37 is a diagram illustrating an example of the format of S-TSID metadata.
- the S-TSID element is a root element and is a higher element of the serviceId attribute, applicationUrl attribute, and RS element.
- a service ID is specified in the serviceId attribute.
- a URL (application URL) indicating the application acquisition location is specified.
- the application URL is information for identifying an entry (for example, index.html) when the application is configured by a plurality of files such as an HTML document file or an image file.
- the application is acquired in accordance with the application URL and activated immediately.
- the RS element is an upper element of the bsid attribute, sIpAddr attribute, dIpAddr attribute, dport attribute, PLPID attribute, and LS element.
- the broadcast stream ID is specified in the bsid attribute.
- the IP address of the source is specified.
- the IP address of the destination is specified.
- a destination port number is specified.
- the PLPID attribute the ID of the PLP of the ROUTE session is specified.
- the LS element is an upper element of the tsi attribute, PLPID attribute, bw attribute, startTime attribute, endTime attribute, SrcFlow element, and RprFlow element.
- ⁇ TSI is specified in the tsi attribute.
- a PLP ID is specified in the PLPID attribute.
- a bandwidth is specified in the bw attribute.
- startTime attribute and endTime attribute a start date and time and an end date and time are specified.
- Source flow information is specified in the SrcFlow element.
- FIG. 38 is a diagram illustrating an example of the format of MPD metadata.
- attributes defined under the root MPD element are listed in the “attributes” frame, and elements defined under the MPD element are listed outside the “attributes” frame. ing. Among the attributes or elements defined in the MPD element, “any ## other” indicates that the area can be freely expanded, and the applicationUrl attribute or applicationUrl element should be defined here. .
- a URL (application URL) indicating the acquisition destination of the application.
- the application URL is information for identifying an entry (for example, index.html) when the application is configured by a plurality of files such as an HTML document file or an image file.
- the application is acquired in accordance with the application URL and activated immediately.
- FIG. 39 is a diagram showing an example of the format of S-TSID metadata.
- FIG. 40 shows the format of the SrcFlow element included in the S-TSID metadata of FIG.
- 40 is an upper element of the rt attribute, minBuffSize attribute, EFDT element, ContentInfo element, and Payload element.
- the minimum buffer size required by the client device 40 is specified.
- the EFDT element information related to an extended FDT (Extended FDT) is specified.
- Information related to the content is specified in the ContentInfo element.
- the Payload element is a higher-level element of the codePoint attribute, formatID attribute, frag attribute, order attribute, srcFecPayloadID attribute, and FECParams attribute, and specifies information related to the payload of the ROUTE packet that stores the source flow object.
- FIG. 41 shows the format of the EFDT element included in the SrcFlow element of FIG.
- the EFDT element in FIG. 41 is an upper element of the tsi attribute, idRef attribute, version attribute, maxExpiresDelta attribute, maxTransportSize attribute, FileTemplate attribute, and FDTParameters attribute.
- FIG. 42 shows the structure of the FDT-Instance element. That is, among the attributes defined in the FDT-Instance element, “any” (“any ## other”) represents a freely expandable area, and the ApplicationEntry attribute is defined here. be able to.
- a file URL that is, an application URL
- an application URL that is a URL of an application entry file
- the File element is defined under the FDT-Instance element. Among the attributes or elements of this File element, "any" (“any ## other") is a freely expandable area. This indicates that the ApplicationEntry attribute or ApplicationEntry element is defined here.
- the ApplicationEntry attribute is defined in the File element
- the file indicated by the Content-Location attribute (file URL (app URL)) of the File element that has this attribute (boolean value is "ture” Indicates an entry.
- an ApplicationEntry element is defined in the File element, it indicates that the file indicated by the Content-Location attribute (file URL (app URL)) of the File element in which this element exists is an application entry. Yes.
- ATSC particularly ATSC 3.0
- ATSC 3.0 which is a method adopted in the United States and the like
- ISDB Integrated (Services Digital Broadcasting)
- DVB Digital Video Broadcasting
- ATSC 3.0 in which the IP transmission method is adopted has been described as an example.
- the present invention is not limited to the IP transmission method, and is applied to other methods such as an MPEG2-TS (TransportTSStream) method, for example. You may do it.
- digital broadcasting can be applied to satellite broadcasting using broadcasting satellites (BS: Broadcasting Satellite) and communication satellites (CS: Communications Satellite), cable broadcasting such as cable TV (CATV), etc. can do.
- BS Broadcasting Satellite
- CS Communications Satellite
- CATV cable TV
- the above-mentioned names such as signaling are merely examples, and other names may be used.
- the difference between these names is a formal difference and does not differ in substantial contents such as target signaling.
- AST Application Signaling Table
- AIT Application Information Table
- LCC Location Cached Content
- NRT Non Real Time
- signaling is described in a markup language such as XML
- the names of those elements and attributes are merely examples, and other names may be adopted.
- the difference between these names is a formal difference, and the substantial contents of those elements and attributes are not different.
- the SLT metadata is described as the LLS signaling.
- the LLS signaling may include metadata such as EAT (Emergency Alerting Table) and RRT (Region Risk Rating Table).
- EAT metadata contains information about emergency information that needs to be urgently notified.
- RRT metadata includes information about ratings.
- the application is not limited to an application developed in a markup language such as HTML5 or a script language such as JavaScript (registered trademark), but may be an application developed in a programming language such as Java (registered trademark). Good.
- the content described above can include any content such as an electronic book, a game, and music.
- the present technology provides a predetermined standard (assuming that a transmission line other than a broadcast network, that is, a communication line (communication network) such as the Internet or a telephone network) is used as a transmission line.
- a predetermined standard assuming that a transmission line other than a broadcast network, that is, a communication line (communication network) such as the Internet or a telephone network) is used as a transmission line.
- the present invention can also be applied to standards other than digital broadcasting standards.
- FIG. 43 is a diagram illustrating a configuration example of hardware of a computer that executes the above-described series of processing by a program.
- a CPU Central Processing Unit
- ROM Read Only Memory
- RAM Random Access Memory
- An input / output interface 1005 is further connected to the bus 1004.
- An input unit 1006, an output unit 1007, a recording unit 1008, a communication unit 1009, and a drive 1010 are connected to the input / output interface 1005.
- the input unit 1006 includes a keyboard, a mouse, a microphone, and the like.
- the output unit 1007 includes a display, a speaker, and the like.
- the recording unit 1008 includes a hard disk, a nonvolatile memory, and the like.
- the communication unit 1009 includes a network interface or the like.
- the drive 1010 drives a removable medium 1011 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory.
- the CPU 1001 loads the program recorded in the ROM 1002 or the recording unit 1008 to the RAM 1003 via the input / output interface 1005 and the bus 1004 and executes the program. A series of processing is performed.
- the program executed by the computer 1000 can be provided by being recorded on the removable medium 1011 as a package medium, for example.
- the program can be provided via a wired or wireless transmission medium such as a local area network, the Internet, or digital satellite broadcasting.
- the program can be installed in the recording unit 1008 via the input / output interface 1005 by attaching the removable medium 1011 to the drive 1010.
- the program can be received by the communication unit 1009 via a wired or wireless transmission medium and installed in the recording unit 1008.
- the program can be installed in the ROM 1002 or the recording unit 1008 in advance.
- the processing performed by the computer according to the program does not necessarily have to be performed in chronological order in the order described as the flowchart. That is, the processing performed by the computer according to the program includes processing executed in parallel or individually (for example, parallel processing or object processing).
- the program may be processed by a single computer (processor) or may be distributedly processed by a plurality of computers.
- the present technology can take the following configurations.
- a receiving unit for receiving content An acquisition unit that acquires the application based on acquisition destination information that indicates an acquisition destination of an application that accompanies the content, included in the control information transmitted together with the content; And a control unit that immediately activates the acquired application.
- the content and the control information are transmitted by broadcast waves, The control information is signaling for providing a digital broadcasting service,
- the control unit controls the operation of the application according to an event transmitted together with the content or the control information.
- the acquisition unit acquires the application protected by DRM (Digital Rights Management) of the content
- the receiving device further includes a verification unit that verifies whether the acquired application is a valid application, The receiving device according to any one of (1) to (3), wherein when the application is recognized as a valid application, the control unit activates the application.
- the verification unit Extracting a first digest value corresponding to the application included in the content stream; Generating a second digest value according to the acquired application; The receiving apparatus according to (4), wherein the first digest value is compared with the second digest value to verify whether the acquired application is a valid application.
- the video data of the content is encoded according to a predetermined encoding method, The receiving apparatus according to (5), wherein the first digest value is stored in a watermark inserted in a baseband frame included in an encrypted VCL-NAL (Video Coding Layer-Network Abstraction Layer) unit.
- VCL-NAL Video Coding Layer-Network Abstraction Layer
- the video data of the content is encoded according to a predetermined encoding method, The receiving apparatus according to (5), wherein the first digest value is stored in an encrypted non-VCL-NAL (Non Video Coding Layer-Network Abstraction Layer) unit.
- the receiving device is Receive content, Acquiring the application based on acquisition source information indicating an acquisition destination of an application associated with the content included in the control information transmitted together with the content; A data processing method including a step of immediately starting the acquired application. (9) A generation unit for generating control information including the acquisition destination information for immediately starting the acquired application, which is acquisition destination information indicating an acquisition destination of the application accompanying the content; A transmission apparatus comprising: a transmission unit that transmits the control information together with the content.
- the transmitting device is It is acquisition destination information indicating an acquisition destination of an application accompanying the content, and generates control information including the acquisition destination information for immediately starting the acquired application, A data processing method including a step of transmitting the control information together with the content.
- a receiving unit for receiving content An acquisition unit that acquires the application that is associated with the content and protected by DRM (Digital Rights Management) of the content; A verification unit that verifies whether the acquired application is a valid application; And a control unit that activates the application when the application is recognized as a valid application.
- DRM Digital Rights Management
- the verification unit Extracting a first digest value corresponding to the application included in the content stream; Generating a second digest value according to the acquired application; The receiving apparatus according to (11), wherein the first digest value is compared with the second digest value to verify whether the acquired application is a valid application.
- the video data of the content is encoded according to a predetermined encoding method, The receiving apparatus according to (12), wherein the first digest value is stored in a watermark inserted in a baseband frame included in an encrypted VCL-NAL (Video Coding Layer-Network Abstraction Layer) unit.
- VCL-NAL Video Coding Layer-Network Abstraction Layer
- the video data of the content is encoded according to a predetermined encoding method, The receiving apparatus according to (12), wherein the first digest value is stored in an encrypted non-VCL-NAL (Non Video Coding Layer-Network Abstraction Layer) unit.
- the receiving apparatus according to (12), wherein the first digest value is transmitted by being included in a message together with identification information for identifying the application.
- the acquisition unit acquires the application based on acquisition destination information indicating an acquisition destination of the application included in control information transmitted together with the content, The receiving device according to any one of (11) to (15), wherein when the acquired application is recognized as a valid application, the control unit immediately starts the application.
- the content and the control information are transmitted by broadcast waves,
- the control information is signaling for providing a digital broadcasting service,
- the receiving device is Receive content, An application associated with the content, wherein the application is protected by DRM (Digital Rights Management) of the content; A verification unit that verifies whether the acquired application is a valid application; A data processing method including a step of starting the application when the application is recognized as a valid application.
- a protection unit that protects an application accompanying the content by DRM (Digital Rights Management) of the content A transmission apparatus comprising: a transmission unit configured to transmit the content and the application protected by a common DRM (Digital Rights Management).
- the transmitting device is Protect the application that accompanies the content by DRM (Digital Rights Management) of the content, A data processing method including a step of transmitting the content and the application protected by a common DRM (Digital Rights Management).
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Technology Law (AREA)
- Databases & Information Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Human Computer Interaction (AREA)
- Virology (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
- Circuits Of Receivers In General (AREA)
Abstract
Description
(1)システムの構成
(2)アプリURLに応じたアプリケーション制御
(3)アプリ制御イベントに応じたアプリケーション制御
(A)MPDイベント方式
(B)インバンドイベント方式
2.第2の実施の形態:アプリケーションのセキュアな提供
(1)システムの構成
(2)アプリダイジェストの概要
(3)アプリダイジェストの伝送方式
(A)ウォータマーク格納方式
(B)非VCL-NALユニット格納方式
3.シグナリングの例
4.変形例
5.コンピュータの構成
図1は、本技術を適用した伝送システムの一実施の形態(第1の実施の形態)の構成例を示す図である。なお、システムとは、複数の装置が論理的に集合したものをいう。
図2は、図1のDASHサーバ10の構成例を示す図である。
図3は、図1のシグナリングサーバ20の構成例を示す図である。
図4は、図1のアプリケーションサーバ30の構成例を示す図である。
図5は、図1の放送サーバ40の構成例を示す図である。
図6は、図1のクライアント装置60の構成例を示す図である。
まず、図8のフローチャートを参照して、アプリURLに応じたアプリケーション制御を行う場合の送信側の処理の流れを説明する。
次に、図9のフローチャートを参照して、アプリURLに応じたアプリケーション制御を行う場合の受信側の処理の流れを説明する。
図10は、MPDイベント方式のMPDメタデータの記述例を示す図である。
まず、図11のフローチャートを参照して、MPDイベント方式のイベントによるアプリケーション制御を行う場合の送信側の処理の流れを説明する。
次に、図12のフローチャートを参照して、MPDイベント方式のイベントによるアプリケーション制御を行う場合の受信側の処理の流れを説明する。
図13は、インバンドイベント方式のDASHEventMessageBoxの配置例を示す図である。
まず、図14のフローチャートを参照して、インバンドイベント方式のイベントによるアプリケーション制御を行う場合の送信側の処理の流れを説明する。
次に、図15のフローチャートを参照して、インバンドイベント方式のイベントによるアプリケーション制御を行う場合の受信側の処理の流れを説明する。
図16は、本技術を適用した伝送システムの一実施の形態(第2の実施の形態)の構成例を示す図である。
図17は、図16のストリームサーバ70の構成例を示す図である。
図18は、図16のDASHサーバ10の構成例を示す図である。なお、図18のDASHサーバ10において、図2のDASHサーバ10と対応する部分には同一の符号が付してあり、その説明は適宜省略する。
図19は、図16のアプリケーションサーバ30の構成例を示す図である。なお、図19のアプリケーションサーバ30において、図4のアプリケーションサーバ30と対応する部分には同一の符号が付してあり、その説明は適宜省略する。
図20は、図16のクライアント装置60の構成例を示す図である。なお、図20のクライアント装置60において、図6のクライアント装置60と対応する部分には同一の符号が付してあり、その説明は適宜省略する。
図22は、アプリダイジェスト(app_digest_message)のシンタックスの例を示す図である。
図25は、ウォータマーク格納方式の概要を説明する図である。
図26は、ビデオウォータマーク(ウォータマーク)を利用したアプリダイジェストの格納方法を示す図である。
図27は、ウォータマークペイロード(Watermark payload)のシンタックスの例を示す図である。
図28は、図27のWMメッセージブロック(wm_message_block())のシンタックスの例を示す図である。
まず、図30のフローチャートを参照して、ウォータマーク格納方式を採用した場合の送信側の処理の流れを説明する。なお、この送信側の処理では、アプリダイジェストがビデオウォータマークに格納される場合を説明するため、ビデオのデータに対する処理を中心に説明し、オーディオのデータに対する処理の説明については適宜省略する。
次に、図31のフローチャートを参照して、ウォータマーク格納方式を採用した場合の受信側の処理の流れを説明する。なお、この受信側の処理では、アプリダイジェストがビデオウォータマークに格納されている場合を説明するため、ビデオのデータに対する処理を中心に説明し、オーディオのデータに対する処理の説明については適宜省略する。
図32は、非VCL-NALユニット格納方式の概要を説明する図である。
まず、図33のフローチャートを参照して、非VCL-NALユニット格納方式を採用した場合の送信側の処理の流れを説明する。なお、この送信側の処理では、アプリダイジェストが非VCL-NALユニットに格納される場合を説明するため、ビデオのデータに対する処理を中心に説明し、オーディオのデータに対する処理の説明については適宜省略する。
次に、図34のフローチャートを参照して、非VCL-NALユニット格納方式を採用した場合の受信側の処理の流れを説明する。なお、この受信側の処理では、アプリダイジェストが非VCL-NALユニットに格納されている場合を説明するため、ビデオのデータに対する処理を中心に説明し、オーディオのデータに対する処理の説明については適宜省略する。
図35は、XML形式のSLTメタデータのフォーマットの例を示す図である。なお、図35において、要素と属性のうち、属性には「@」が付されている。また、インデントされた要素と属性は、その上位の要素に対して指定されたものとなる。これらの関係は、後述する他のシグナリングのフォーマットでも同様とされる。
図36は、XML形式のUSDメタデータ(USBDメタデータ)のフォーマットの例を示す図である。
図37は、S-TSIDメタデータのフォーマットの例を示す図である。
図38は、MPDメタデータのフォーマットの例を示す図である。
次に、図39乃至図42を参照して、S-TSIDにアプリケーションのエントリを明示する場合のメタデータの構造について説明する。
コンテンツを受信する受信部と、
前記コンテンツとともに伝送される制御情報に含まれる、前記コンテンツに付随するアプリケーションの取得先を示す取得先情報に基づいて、前記アプリケーションを取得する取得部と、
取得された前記アプリケーションを即時に起動する制御部と
を備える受信装置。
(2)
前記コンテンツ及び前記制御情報は、放送波により伝送され、
前記制御情報は、デジタル放送のサービスを提供するためのシグナリングであり、
前記取得先情報は、URL(Uniform Resource Locator)である
(1)に記載の受信装置。
(3)
前記制御部は、前記コンテンツ又は前記制御情報とともに伝送されるイベントに従い、前記アプリケーションの動作を制御する
(2)に記載の受信装置。
(4)
前記取得部は、前記コンテンツのDRM(Digital Rights Management)により保護された前記アプリケーションを取得し、
前記受信装置は、取得された前記アプリケーションが、正当なアプリケーションであるかどうかを検証する検証部をさらに備え、
前記制御部は、前記アプリケーションが正当なアプリケーションであると認められた場合に、当該アプリケーションを起動する
(1)乃至(3)のいずれかに記載の受信装置。
(5)
前記検証部は、
前記コンテンツのストリームに含まれる、前記アプリケーションに応じた第1のダイジェスト値を抽出し、
取得された前記アプリケーションに応じた第2のダイジェスト値を生成し、
前記第1のダイジェスト値と、前記第2のダイジェスト値とを比較することで、取得された前記アプリケーションが、正当なアプリケーションであるかどうかを検証する
(4)に記載の受信装置。
(6)
前記コンテンツのビデオデータは、所定の符号化方式に従い、符号化されており、
前記第1のダイジェスト値は、暗号化されたVCL-NAL(Video Coding Layer - Network Abstraction Layer)ユニットに含まれるベースバンドフレームに挿入されるウォータマークに格納される
(5)に記載の受信装置。
(7)
前記コンテンツのビデオデータは、所定の符号化方式に従い、符号化されており、
前記第1のダイジェスト値は、暗号化された非VCL-NAL(Non Video Coding Layer - Network Abstraction Layer)ユニットに格納される
(5)に記載の受信装置。
(8)
受信装置のデータ処理方法において、
前記受信装置が、
コンテンツを受信し、
前記コンテンツとともに伝送される制御情報に含まれる、前記コンテンツに付随するアプリケーションの取得先を示す取得先情報に基づいて、前記アプリケーションを取得し、
取得された前記アプリケーションを即時に起動する
ステップを含むデータ処理方法。
(9)
コンテンツに付随するアプリケーションの取得先を示す取得先情報であって、取得された前記アプリケーションを即時に起動させるための前記取得先情報を含む制御情報を生成する生成部と、
前記コンテンツとともに、前記制御情報を送信する送信部と
を備える送信装置。
(10)
送信装置のデータ処理方法において、
前記送信装置が、
コンテンツに付随するアプリケーションの取得先を示す取得先情報であって、取得された前記アプリケーションを即時に起動させるための前記取得先情報を含む制御情報を生成し、
前記コンテンツとともに、前記制御情報を送信する
ステップを含むデータ処理方法。
(11)
コンテンツを受信する受信部と、
前記コンテンツに付随するアプリケーションであって、前記コンテンツのDRM(Digital Rights Management)により保護された前記アプリケーションを取得する取得部と、
取得された前記アプリケーションが、正当なアプリケーションであるかどうかを検証する検証部と、
前記アプリケーションが正当なアプリケーションであると認められた場合に、当該アプリケーションを起動する制御部と
を備える受信装置。
(12)
前記検証部は、
前記コンテンツのストリームに含まれる、前記アプリケーションに応じた第1のダイジェスト値を抽出し、
取得された前記アプリケーションに応じた第2のダイジェスト値を生成し、
前記第1のダイジェスト値と、前記第2のダイジェスト値とを比較することで、取得された前記アプリケーションが、正当なアプリケーションであるかどうかを検証する
(11)に記載の受信装置。
(13)
前記コンテンツのビデオデータは、所定の符号化方式に従い、符号化されており、
前記第1のダイジェスト値は、暗号化されたVCL-NAL(Video Coding Layer - Network Abstraction Layer)ユニットに含まれるベースバンドフレームに挿入されるウォータマークに格納される
(12)に記載の受信装置。
(14)
前記コンテンツのビデオデータは、所定の符号化方式に従い、符号化されており、
前記第1のダイジェスト値は、暗号化された非VCL-NAL(Non Video Coding Layer - Network Abstraction Layer)ユニットに格納される
(12)に記載の受信装置。
(15)
前記第1のダイジェスト値は、前記アプリケーションを識別するための識別情報とともに、メッセージに含めて伝送される
(12)に記載の受信装置。
(16)
前記取得部は、前記コンテンツとともに伝送される制御情報に含まれる、前記アプリケーションの取得先を示す取得先情報に基づいて、前記アプリケーションを取得し、
前記制御部は、取得された前記アプリケーションが正当なアプリケーションであると認められた場合、当該アプリケーションを即時に起動する
(11)乃至(15)のいずれかに記載の受信装置。
(17)
前記コンテンツ及び前記制御情報は、放送波により伝送され、
前記制御情報は、デジタル放送のサービスを提供するためのシグナリングであり、
前記取得先情報は、URL(Uniform Resource Locator)である
(16)に記載の受信装置。
(18)
受信装置のデータ処理方法において、
前記受信装置が、
コンテンツを受信し、
前記コンテンツに付随するアプリケーションであって、前記コンテンツのDRM(Digital Rights Management)により保護された前記アプリケーションを取得し、
取得された前記アプリケーションが、正当なアプリケーションであるかどうかを検証する検証部と、
前記アプリケーションが正当なアプリケーションであると認められた場合、当該アプリケーションを起動する
ステップを含むデータ処理方法。
(19)
コンテンツに付随するアプリケーションを、前記コンテンツのDRM(Digital Rights Management)により保護する保護部と、
共通のDRM(Digital Rights Management)により保護された前記コンテンツ及び前記アプリケーションを送信する送信部と
を備える送信装置。
(20)
送信装置のデータ処理方法において、
前記送信装置が、
コンテンツに付随するアプリケーションを、前記コンテンツのDRM(Digital Rights Management)により保護し、
共通のDRM(Digital Rights Management)により保護された前記コンテンツ及び前記アプリケーションを送信する
ステップを含むデータ処理方法。
Claims (20)
- コンテンツを受信する受信部と、
前記コンテンツとともに伝送される制御情報に含まれる、前記コンテンツに付随するアプリケーションの取得先を示す取得先情報に基づいて、前記アプリケーションを取得する取得部と、
取得された前記アプリケーションを即時に起動する制御部と
を備える受信装置。 - 前記コンテンツ及び前記制御情報は、放送波により伝送され、
前記制御情報は、デジタル放送のサービスを提供するためのシグナリングであり、
前記取得先情報は、URL(Uniform Resource Locator)である
請求項1に記載の受信装置。 - 前記制御部は、前記コンテンツ又は前記制御情報とともに伝送されるイベントに従い、前記アプリケーションの動作を制御する
請求項2に記載の受信装置。 - 前記取得部は、前記コンテンツのDRM(Digital Rights Management)により保護された前記アプリケーションを取得し、
前記受信装置は、取得された前記アプリケーションが、正当なアプリケーションであるかどうかを検証する検証部をさらに備え、
前記制御部は、前記アプリケーションが正当なアプリケーションであると認められた場合に、当該アプリケーションを起動する
請求項1に記載の受信装置。 - 前記検証部は、
前記コンテンツのストリームに含まれる、前記アプリケーションに応じた第1のダイジェスト値を抽出し、
取得された前記アプリケーションに応じた第2のダイジェスト値を生成し、
前記第1のダイジェスト値と、前記第2のダイジェスト値とを比較することで、取得された前記アプリケーションが、正当なアプリケーションであるかどうかを検証する
請求項4に記載の受信装置。 - 前記コンテンツのビデオデータは、所定の符号化方式に従い、符号化されており、
前記第1のダイジェスト値は、暗号化されたVCL-NAL(Video Coding Layer - Network Abstraction Layer)ユニットに含まれるベースバンドフレームに挿入されるウォータマークに格納される
請求項5に記載の受信装置。 - 前記コンテンツのビデオデータは、所定の符号化方式に従い、符号化されており、
前記第1のダイジェスト値は、暗号化された非VCL-NAL(Non Video Coding Layer - Network Abstraction Layer)ユニットに格納される
請求項5に記載の受信装置。 - 受信装置のデータ処理方法において、
前記受信装置が、
コンテンツを受信し、
前記コンテンツとともに伝送される制御情報に含まれる、前記コンテンツに付随するアプリケーションの取得先を示す取得先情報に基づいて、前記アプリケーションを取得し、
取得された前記アプリケーションを即時に起動する
ステップを含むデータ処理方法。 - コンテンツに付随するアプリケーションの取得先を示す取得先情報であって、取得された前記アプリケーションを即時に起動させるための前記取得先情報を含む制御情報を生成する生成部と、
前記コンテンツとともに、前記制御情報を送信する送信部と
を備える送信装置。 - 送信装置のデータ処理方法において、
前記送信装置が、
コンテンツに付随するアプリケーションの取得先を示す取得先情報であって、取得された前記アプリケーションを即時に起動させるための前記取得先情報を含む制御情報を生成し、
前記コンテンツとともに、前記制御情報を送信する
ステップを含むデータ処理方法。 - コンテンツを受信する受信部と、
前記コンテンツに付随するアプリケーションであって、前記コンテンツのDRM(Digital Rights Management)により保護された前記アプリケーションを取得する取得部と、
取得された前記アプリケーションが、正当なアプリケーションであるかどうかを検証する検証部と、
前記アプリケーションが正当なアプリケーションであると認められた場合に、当該アプリケーションを起動する制御部と
を備える受信装置。 - 前記検証部は、
前記コンテンツのストリームに含まれる、前記アプリケーションに応じた第1のダイジェスト値を抽出し、
取得された前記アプリケーションに応じた第2のダイジェスト値を生成し、
前記第1のダイジェスト値と、前記第2のダイジェスト値とを比較することで、取得された前記アプリケーションが、正当なアプリケーションであるかどうかを検証する
請求項11に記載の受信装置。 - 前記コンテンツのビデオデータは、所定の符号化方式に従い、符号化されており、
前記第1のダイジェスト値は、暗号化されたVCL-NAL(Video Coding Layer - Network Abstraction Layer)ユニットに含まれるベースバンドフレームに挿入されるウォータマークに格納される
請求項12に記載の受信装置。 - 前記コンテンツのビデオデータは、所定の符号化方式に従い、符号化されており、
前記第1のダイジェスト値は、暗号化された非VCL-NAL(Non Video Coding Layer - Network Abstraction Layer)ユニットに格納される
請求項12に記載の受信装置。 - 前記第1のダイジェスト値は、前記アプリケーションを識別するための識別情報とともに、メッセージに含めて伝送される
請求項12に記載の受信装置。 - 前記取得部は、前記コンテンツとともに伝送される制御情報に含まれる、前記アプリケーションの取得先を示す取得先情報に基づいて、前記アプリケーションを取得し、
前記制御部は、取得された前記アプリケーションが正当なアプリケーションであると認められた場合、当該アプリケーションを即時に起動する
請求項11に記載の受信装置。 - 前記コンテンツ及び前記制御情報は、放送波により伝送され、
前記制御情報は、デジタル放送のサービスを提供するためのシグナリングであり、
前記取得先情報は、URL(Uniform Resource Locator)である
請求項16に記載の受信装置。 - 受信装置のデータ処理方法において、
前記受信装置が、
コンテンツを受信し、
前記コンテンツに付随するアプリケーションであって、前記コンテンツのDRM(Digital Rights Management)により保護された前記アプリケーションを取得し、
取得された前記アプリケーションが、正当なアプリケーションであるかどうかを検証する検証部と、
前記アプリケーションが正当なアプリケーションであると認められた場合、当該アプリケーションを起動する
ステップを含むデータ処理方法。 - コンテンツに付随するアプリケーションを、前記コンテンツのDRM(Digital Rights Management)により保護する保護部と、
共通のDRM(Digital Rights Management)により保護された前記コンテンツ及び前記アプリケーションを送信する送信部と
を備える送信装置。 - 送信装置のデータ処理方法において、
前記送信装置が、
コンテンツに付随するアプリケーションを、前記コンテンツのDRM(Digital Rights Management)により保護し、
共通のDRM(Digital Rights Management)により保護された前記コンテンツ及び前記アプリケーションを送信する
ステップを含むデータ処理方法。
Priority Applications (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA3010777A CA3010777C (en) | 2016-01-15 | 2017-01-04 | Reception device, transmission device, and data processing method |
US16/067,388 US11449583B2 (en) | 2016-01-15 | 2017-01-04 | Reception device, transmission device, and data processing method |
JP2017561587A JPWO2017122554A1 (ja) | 2016-01-15 | 2017-01-04 | 受信装置、送信装置、及び、データ処理方法 |
EP17738309.8A EP3404924B1 (en) | 2016-01-15 | 2017-01-04 | Reception device and data processing method |
KR1020187018954A KR102653289B1 (ko) | 2016-01-15 | 2017-01-04 | 수신 장치, 송신 장치 및 데이터 처리 방법 |
MX2018008395A MX2018008395A (es) | 2016-01-15 | 2017-01-04 | Dispositivo de recepcion, dispositivo de transmision y metodo de procesamiento de datos. |
US17/898,531 US20230099480A1 (en) | 2016-01-15 | 2022-08-30 | Reception device, transmission device, and data processing method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2016006375 | 2016-01-15 | ||
JP2016-006375 | 2016-01-15 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/067,388 A-371-Of-International US11449583B2 (en) | 2016-01-15 | 2017-01-04 | Reception device, transmission device, and data processing method |
US17/898,531 Continuation US20230099480A1 (en) | 2016-01-15 | 2022-08-30 | Reception device, transmission device, and data processing method |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017122554A1 true WO2017122554A1 (ja) | 2017-07-20 |
Family
ID=59310968
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2017/000012 WO2017122554A1 (ja) | 2016-01-15 | 2017-01-04 | 受信装置、送信装置、及び、データ処理方法 |
Country Status (7)
Country | Link |
---|---|
US (2) | US11449583B2 (ja) |
EP (1) | EP3404924B1 (ja) |
JP (1) | JPWO2017122554A1 (ja) |
KR (1) | KR102653289B1 (ja) |
CA (1) | CA3010777C (ja) |
MX (1) | MX2018008395A (ja) |
WO (1) | WO2017122554A1 (ja) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2021027450A (ja) * | 2019-08-02 | 2021-02-22 | 日本放送協会 | 配信システム、受信装置およびプログラム |
KR20210085572A (ko) * | 2019-12-30 | 2021-07-08 | 재단법인 경주스마트미디어센터 | Drm 콘텐츠 병렬 패키징 장치 및 이를 포함하는 drm 콘텐츠 병렬 패키징 시스템 및 drm 콘텐츠 병렬 패키징 방법 |
WO2021137633A3 (ko) * | 2019-12-30 | 2021-09-30 | 재단법인 경주스마트미디어센터 | Drm 콘텐츠 병렬 패키징 장치 및 이를 포함하는 drm 콘텐츠 병렬 패키징 시스템 및 drm 콘텐츠 병렬 패키징 방법 |
JP2022524073A (ja) * | 2019-09-30 | 2022-04-27 | テンセント・アメリカ・エルエルシー | Httpによる動的適応ストリーミングのための方法及び装置 |
EP3707908B1 (en) * | 2017-11-10 | 2023-03-08 | QUALCOMM Incorporated | Interfaces between dash aware application and dash client for service interactivity support |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA2924036C (en) * | 2014-08-01 | 2023-08-22 | Sony Corporation | Receiving device, receiving method, transmitting device, and transmitting method |
KR20200035396A (ko) * | 2017-08-10 | 2020-04-03 | 소니 주식회사 | 송신 장치, 송신 방법, 수신 장치, 및 수신 방법 |
KR102642928B1 (ko) * | 2019-03-26 | 2024-03-04 | 삼성전자주식회사 | 방송 수신 장치 및 그 동작 방법 |
US11941092B2 (en) * | 2020-02-06 | 2024-03-26 | Saturn Licensing Llc | Techniques for launching applications based on partial signature validation |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2012516643A (ja) * | 2009-01-28 | 2012-07-19 | マイクロソフト コーポレーション | ソフトウェアアプリケーションの検証 |
WO2013094110A1 (ja) * | 2011-12-21 | 2013-06-27 | ソニー株式会社 | 情報処理装置、サーバ装置、情報処理方法、サーバ処理方法およびプログラム |
WO2014027563A1 (ja) * | 2012-08-13 | 2014-02-20 | ソニー株式会社 | 受信装置、受信方法、送信装置、及び送信方法 |
WO2014080783A1 (ja) | 2012-11-23 | 2014-05-30 | ソニー株式会社 | 情報処理装置、および情報処理方法 |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6487301B1 (en) * | 1998-04-30 | 2002-11-26 | Mediasec Technologies Llc | Digital authentication with digital and analog documents |
US6243480B1 (en) * | 1998-04-30 | 2001-06-05 | Jian Zhao | Digital authentication with analog documents |
US20030217369A1 (en) * | 2002-05-17 | 2003-11-20 | Heredia Edwin Arturo | Flexible application information formulation |
JP6053323B2 (ja) * | 2011-05-20 | 2016-12-27 | 日本放送協会 | 放送送信装置、放送通信連携受信装置およびそのプログラム、ならびに、放送通信連携システム |
US20130042100A1 (en) * | 2011-08-09 | 2013-02-14 | Nokia Corporation | Method and apparatus for forced playback in http streaming |
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 |
CA2843583C (en) * | 2011-09-23 | 2016-11-01 | Lg Electronics Inc. | Method for receiving broadcast service and reception device thereof |
KR101603136B1 (ko) * | 2012-04-27 | 2016-03-14 | 후아웨이 테크놀러지 컴퍼니 리미티드 | 템플릿 모드에서의 짧은 암호 사용기간의 지원 |
HUE037479T2 (hu) * | 2013-01-17 | 2018-08-28 | Intel Ip Corp | Tartalom URL hitelesítés DASH-hoz |
WO2015167177A1 (ko) * | 2014-04-30 | 2015-11-05 | 엘지전자 주식회사 | 방송 전송 장치, 방송 수신 장치, 방송 전송 장치의 동작 방법 및 방송 수신 장치의 동작 방법 |
US10567833B2 (en) * | 2014-05-30 | 2020-02-18 | Sony Corporation | Reception apparatus, reception method, transmission apparatus and transmission method |
-
2017
- 2017-01-04 JP JP2017561587A patent/JPWO2017122554A1/ja active Pending
- 2017-01-04 US US16/067,388 patent/US11449583B2/en active Active
- 2017-01-04 MX MX2018008395A patent/MX2018008395A/es unknown
- 2017-01-04 WO PCT/JP2017/000012 patent/WO2017122554A1/ja active Application Filing
- 2017-01-04 KR KR1020187018954A patent/KR102653289B1/ko active IP Right Grant
- 2017-01-04 CA CA3010777A patent/CA3010777C/en active Active
- 2017-01-04 EP EP17738309.8A patent/EP3404924B1/en active Active
-
2022
- 2022-08-30 US US17/898,531 patent/US20230099480A1/en active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2012516643A (ja) * | 2009-01-28 | 2012-07-19 | マイクロソフト コーポレーション | ソフトウェアアプリケーションの検証 |
WO2013094110A1 (ja) * | 2011-12-21 | 2013-06-27 | ソニー株式会社 | 情報処理装置、サーバ装置、情報処理方法、サーバ処理方法およびプログラム |
WO2014027563A1 (ja) * | 2012-08-13 | 2014-02-20 | ソニー株式会社 | 受信装置、受信方法、送信装置、及び送信方法 |
WO2014080783A1 (ja) | 2012-11-23 | 2014-05-30 | ソニー株式会社 | 情報処理装置、および情報処理方法 |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3707908B1 (en) * | 2017-11-10 | 2023-03-08 | QUALCOMM Incorporated | Interfaces between dash aware application and dash client for service interactivity support |
JP2021027450A (ja) * | 2019-08-02 | 2021-02-22 | 日本放送協会 | 配信システム、受信装置およびプログラム |
JP7390816B2 (ja) | 2019-08-02 | 2023-12-04 | 日本放送協会 | 配信システム、受信装置およびプログラム |
JP2022524073A (ja) * | 2019-09-30 | 2022-04-27 | テンセント・アメリカ・エルエルシー | Httpによる動的適応ストリーミングのための方法及び装置 |
JP7246508B2 (ja) | 2019-09-30 | 2023-03-27 | テンセント・アメリカ・エルエルシー | Httpによる動的適応ストリーミングのための方法及び装置 |
KR20210085572A (ko) * | 2019-12-30 | 2021-07-08 | 재단법인 경주스마트미디어센터 | Drm 콘텐츠 병렬 패키징 장치 및 이를 포함하는 drm 콘텐츠 병렬 패키징 시스템 및 drm 콘텐츠 병렬 패키징 방법 |
KR102302755B1 (ko) * | 2019-12-30 | 2021-09-16 | 재단법인 경주스마트미디어센터 | Drm 콘텐츠 병렬 패키징 장치 및 이를 포함하는 drm 콘텐츠 병렬 패키징 시스템 및 drm 콘텐츠 병렬 패키징 방법 |
WO2021137633A3 (ko) * | 2019-12-30 | 2021-09-30 | 재단법인 경주스마트미디어센터 | Drm 콘텐츠 병렬 패키징 장치 및 이를 포함하는 drm 콘텐츠 병렬 패키징 시스템 및 drm 콘텐츠 병렬 패키징 방법 |
Also Published As
Publication number | Publication date |
---|---|
EP3404924B1 (en) | 2023-04-26 |
KR102653289B1 (ko) | 2024-04-02 |
EP3404924A1 (en) | 2018-11-21 |
US20190026444A1 (en) | 2019-01-24 |
CA3010777A1 (en) | 2017-07-20 |
JPWO2017122554A1 (ja) | 2018-11-01 |
MX2018008395A (es) | 2018-08-15 |
KR20180105641A (ko) | 2018-09-28 |
US11449583B2 (en) | 2022-09-20 |
US20230099480A1 (en) | 2023-03-30 |
CA3010777C (en) | 2024-06-04 |
EP3404924A4 (en) | 2019-05-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA3010777C (en) | Reception device, transmission device, and data processing method | |
US11368766B2 (en) | System and method for signaling security and database population | |
EP2925007B1 (en) | Information processing device and information processing method | |
JP6973454B2 (ja) | 情報処理システムおよび送受信方法 | |
KR20180088383A (ko) | 수신 장치, 송신 장치, 및 데이터 처리 방법 | |
US20140331250A1 (en) | Information processing apparatus, server apparatus, information processing method, server processing method, and program | |
US8850590B2 (en) | Systems and methods for using transport stream splicing for programming information security | |
KR102586630B1 (ko) | 수신 장치, 송신 장치, 및 데이터 처리 방법 | |
JP2019050578A (ja) | 放送通信連携受信装置及び放送通信連携システム | |
JP5350021B2 (ja) | ファイル生成装置、ファイル再生装置およびコンピュータプログラム | |
US20220201372A1 (en) | Live video streaming architecture with real-time frame and subframe level live watermarking | |
WO2004100442A1 (ja) | Mpeg-4 ipmp拡張されたisma媒体ストリームの送信装置 | |
JP2005269412A (ja) | コンテンツ配信システムおよび視聴者端末装置 |
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: 17738309 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2017561587 Country of ref document: JP Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 20187018954 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 3010777 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: MX/A/2018/008395 Country of ref document: MX |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2017738309 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2017738309 Country of ref document: EP Effective date: 20180816 |