WO2017090457A1 - 受信装置、送信装置、及び、データ処理方法 - Google Patents
受信装置、送信装置、及び、データ処理方法 Download PDFInfo
- Publication number
- WO2017090457A1 WO2017090457A1 PCT/JP2016/083467 JP2016083467W WO2017090457A1 WO 2017090457 A1 WO2017090457 A1 WO 2017090457A1 JP 2016083467 W JP2016083467 W JP 2016083467W WO 2017090457 A1 WO2017090457 A1 WO 2017090457A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- resource
- content
- signaling
- service
- cache
- Prior art date
Links
- 230000005540 biological transmission Effects 0.000 title claims abstract description 89
- 238000003672 processing method Methods 0.000 title claims abstract description 18
- 230000011664 signaling Effects 0.000 claims description 115
- 238000000034 method Methods 0.000 claims description 75
- 238000005516 engineering process Methods 0.000 abstract description 28
- 238000004891 communication Methods 0.000 description 89
- 230000006854 communication Effects 0.000 description 89
- 238000012545 processing Methods 0.000 description 68
- 230000008569 process Effects 0.000 description 46
- 238000003780 insertion Methods 0.000 description 40
- 230000037431 insertion Effects 0.000 description 32
- 230000002085 persistent effect Effects 0.000 description 16
- 238000010586 diagram Methods 0.000 description 15
- 230000004044 response Effects 0.000 description 12
- VKALYYFVKBXHTF-UHFFFAOYSA-N 4-(methylsulfanyl)-m-cresol Chemical compound CSC1=CC=C(O)C=C1C VKALYYFVKBXHTF-UHFFFAOYSA-N 0.000 description 10
- 238000012546 transfer Methods 0.000 description 10
- 230000008439 repair process Effects 0.000 description 9
- 238000012384 transportation and delivery Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 8
- 238000002716 delivery method Methods 0.000 description 4
- 230000003044 adaptive effect Effects 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 3
- 238000012217 deletion Methods 0.000 description 3
- 230000037430 deletion Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 239000011800 void material Substances 0.000 description 3
- 230000007175 bidirectional communication Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000002688 persistence Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000013467 fragmentation Methods 0.000 description 1
- 238000006062 fragmentation reaction Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000035945 sensitivity Effects 0.000 description 1
- 239000007787 solid Substances 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/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/433—Content storage operation, e.g. storage operation in response to a pause request, caching operations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/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/434—Disassembling of a multiplex stream, e.g. demultiplexing audio and video streams, extraction of additional data from a video stream; Remultiplexing of multiplex streams; Extraction or processing of SI; Disassembling of packetised elementary stream
- H04N21/4348—Demultiplexing of additional data and video streams
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/236—Assembling of a multiplex stream, e.g. transport stream, by combining a video stream with other content or additional data, e.g. inserting a URL [Uniform Resource Locator] into a video stream, multiplexing software data into a video stream; Remultiplexing of multiplex streams; Insertion of stuffing bits into the multiplex stream, e.g. to obtain a constant bit-rate; Assembling of a packetised elementary stream
- H04N21/2362—Generation or processing of Service Information [SI]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
-
- 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/27—Arrangements for recording or accumulating broadcast information or broadcast-related information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/236—Assembling of a multiplex stream, e.g. transport stream, by combining a video stream with other content or additional data, e.g. inserting a URL [Uniform Resource Locator] into a video stream, multiplexing software data into a video stream; Remultiplexing of multiplex streams; Insertion of stuffing bits into the multiplex stream, e.g. to obtain a constant bit-rate; Assembling of a packetised elementary stream
- H04N21/23614—Multiplexing of additional data and video streams
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/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/433—Content storage operation, e.g. storage operation in response to a pause request, caching operations
- H04N21/4331—Caching operations, e.g. of an advertisement for later insertion during playback
-
- 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/434—Disassembling of a multiplex stream, e.g. demultiplexing audio and video streams, extraction of additional data from a video stream; Remultiplexing of multiplex streams; Extraction or processing of SI; Disassembling of packetised elementary stream
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/434—Disassembling of a multiplex stream, e.g. demultiplexing audio and video streams, extraction of additional data from a video stream; Remultiplexing of multiplex streams; Extraction or processing of SI; Disassembling of packetised elementary stream
- H04N21/4345—Extraction or processing of SI, e.g. extracting service information from an MPEG 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/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/61—Network physical structure; Signal processing
- H04N21/6106—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network
- H04N21/6112—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network involving terrestrial transmission, e.g. DVB-T
-
- 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/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/61—Network physical structure; Signal processing
- H04N21/6106—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network
- H04N21/6125—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network involving transmission via Internet
-
- 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/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/643—Communication protocols
- H04N21/64322—IP
-
- 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/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/65—Transmission of management data between client and server
- H04N21/654—Transmission by server directed to the client
- H04N21/6543—Transmission by server directed to the client for forcing some client operations, e.g. recording
-
- 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/812—Monomedia components thereof involving advertisement 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/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/845—Structuring of content, e.g. decomposing content into time segments
- H04N21/8456—Structuring of content, e.g. decomposing content into time segments by decomposing the content in the time domain, e.g. in time segments
Definitions
- the present technology relates to a receiving device, a transmitting device, and a data processing method, and particularly to a receiving device, a transmitting device, and a data processing method that can share resources that are reused in a plurality of services.
- ATSC Advanced Television Systems Systems Committee
- a file system such as On Memory or SSD (Solid State Drive) or a special database is used.
- Files in these local caches are kept in the cache for a limited period of time and then deleted based on the HTTP (Hypertext Transfer Protocol) header cache control header (Cache Control Header) parameters attached to the file.
- HTTP Hypertext Transfer Protocol
- cache Control Header cache Control Header
- entity mode which is a kind of distribution mode of the ROUTE (Real-time Object-Delivery-over-Unidirectional Transport) protocol, is used.
- Patent Document 1 a technique for realizing data distribution via broadcasting or communication.
- This technology has been made in view of such a situation, and enables a resource reused in a plurality of services to be shared.
- the receiving device is a receiving unit that receives content and control information transmitted together with the content, and whether or not the resource of the content is a resource shared by a plurality of services
- a control unit that controls storage of the resource in the storage device so that the resource of the content is shared by a plurality of services based on the control information including resource sharing information indicating .
- 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.
- control information transmitted together with the content is received, and the resource of the content is shared by a plurality of services
- the storage of the resource in the storage device is controlled so that the resource of the content is shared by a plurality of services.
- the transmission device includes: a generation unit that generates control information including resource sharing information indicating whether a resource of content is a resource shared by a plurality of services; And a transmission unit that transmits control information.
- 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.
- control information including resource sharing information indicating whether a resource of content is a resource shared by a plurality of services is generated,
- the control information is transmitted together with the content.
- resources that are reused in a plurality of services can be shared.
- FIG. 1 It is a figure showing the composition of the 1 embodiment of the transmission system to which this art is applied. It is a figure which shows the example of the protocol stack of the IP transmission system of this technique. It is a figure which shows the structure of ROUTE / FLUTE. It is a figure which shows the detailed structure of ROUTE. It is a figure which shows the outline
- FIG. 1 is a diagram illustrating a configuration of an 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 an Ad / DASH server 10, a broadcast server 20, a communication server 30, and a client device 40.
- the Ad / DASH server 10 is a server for performing a delivery 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 Ad / DASH server 10 generates a file of a program content segment (hereinafter also referred to as a DASH segment) or an advertisement content segment (hereinafter also referred to as an Ad segment), and transmits the file to the broadcast server 20 or the communication server 30. To do. Further, the Ad / DASH server 10 generates MPD metadata and transmits it to the broadcast server 20 or the communication server 30.
- a DASH segment program content segment
- Ad segment advertisement content segment
- the Ad / DASH server 10 generates an application and transmits it to the broadcast server 20 or the communication server 30.
- a script application capable of executing a script (Script) is included.
- the script application may be an application developed in a markup language such as HTML5 (HyperTextperMarkup Language 5) or a script language such as JavaScript (registered trademark).
- the broadcast server 20 is a transmitter capable of performing data transmission conforming to digital broadcasting standards such as ATSC 3.0.
- the broadcast server 20 processes the DASH segment, Ad segment, MPD metadata, and application files transmitted from the Ad / DASH server 10 and transmits them via the transmission path 80 (simultaneous broadcast distribution) together with signaling.
- NRT content is input to the broadcast server 20.
- the NRT content is content transmitted by NRT (Non Real Time) broadcasting, and is reproduced after being once stored in the storage of the client device 40.
- the broadcast server 20 processes the NRT content file input thereto, and transmits (broadcast broadcast) via the transmission path 80.
- the communication server 30 is a server that provides various data via the Internet 90 in response to a request from the client device 40 connected to the Internet 90.
- the communication server 30 processes the DASH segment, Ad segment, MPD metadata, and application file transmitted from the Ad / DASH server 10.
- the communication server 30 transmits various files via the Internet 90 in response to a request from the client device 40.
- the client device 40 is a receiver that can receive transmission data compliant with digital broadcasting standards such as ATSC 3.0.
- the client device 40 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 40 may be a device mounted on an automobile such as an in-vehicle television.
- the client device 40 receives and processes files such as DASH segment, Ad segment, signaling, MPD metadata, application, and NRT content transmitted (broadcast delivery) from the broadcast server 20 via the transmission path 80. By doing so, video and audio of content such as broadcast programs and advertisements are output.
- files such as DASH segment, Ad segment, signaling, MPD metadata, application, and NRT content transmitted (broadcast delivery) from the broadcast server 20 via the transmission path 80.
- the client device 40 can access the communication server 30 via the Internet 90 and acquire various files.
- the client device 40 receives and processes a file such as a DASH segment, an Ad segment, and MPD metadata that is transmitted (adaptive streaming delivery) from the communication server 30 via the Internet 90, thereby processing VOD ( Video (On Demand) Outputs video and audio for content such as programs and advertisements.
- VOD Video (On Demand) Outputs video and audio for content such as programs and advertisements.
- 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
- ATSC 3.0 is the next generation broadcasting standard in the United States that is currently being developed.
- ATSC 3.0 instead of the currently widely used MPEG2-TS (Transport Stream) method, the IP transmission method that uses IP (Internet Protocol) packets used in the field of communication for digital broadcasting is used. By introducing it, it is expected to provide more advanced services.
- MPEG2-TS Transport Stream
- IP Internet Protocol
- FIG. 2 is a diagram illustrating an example of a protocol stack of the IP transmission scheme of the present technology.
- the lowest hierarchy is a physical layer.
- IP transmission system such as ATSC3.0
- the physical layer corresponds to the frequency band of the broadcast wave allocated for the service (channel).
- the upper layer of the physical layer is the IP layer.
- the IP layer corresponds to a network layer in a communication hierarchical model, and an IP packet is specified by an IP address.
- the upper layer adjacent to the IP layer is a UDP (User Datagram Protocol) layer that corresponds to the transport layer in the communication layer model, and the upper layer is ROUTE (Real-time Object Delivery Service Unidirectional Transport) or MMTP. (MPEG-Media-Transport-Protocol).
- SLT metadata is stored and transmitted in the upper layer of the UDP layer, that is, the IP packet including the UDP packet.
- the SLS metadata is LLS (Link Layer Signaling) signaling including basic information indicating a stream and a service configuration in a broadcast network, such as information necessary for channel selection (channel selection information). Note that the LLS signaling is signaling acquired prior to SLS (Service Layer Signaling) signaling, and the SLS signaling is acquired according to information included in the LLS signaling.
- LLS Link Layer Signaling
- ROUTE is a protocol for transferring streaming files and extends FLUTE (FileFLDelivery over Unidirectional Transport). The detailed contents of ROUTE will be described later with reference to FIGS.
- SLS Session Specific signaling
- metadata such as USBD (User Service Bundle Description), S-TSID (Service-based Transport Session Instance Description), MPD (Media Presentation Description), AST (Application Signaling Table), etc. Is included.
- S-TSID metadata is an extension of LSID (LCT Session Instance Description) for ATSC 3.0, and is ROUTE protocol control information.
- LSID LCT Session Instance Description
- MPD metadata is management information of a moving image or audio file that is streamed.
- AST is application control information.
- the NRT content is an example of content transmitted in the ROUTE session.
- content such as an application or an electronic service guide (ESG) may be transmitted in the ROUTE session.
- ESG electronic service guide
- the upper layer adjacent to the DASH segment is a DASH player / decoder.
- the stream data of service components video, audio, subtitles, etc.
- ISO BMFF ISO Base Media File Format
- MMTP is a protocol for transferring streaming files.
- some layers are set to signaling (MMTP (specific Signaling).
- This signaling includes, for example, metadata such as USBD (User Service Bundle Description) and MPT (MMT Package Table).
- the layer other than signaling is MPU (Media Processing Unit) (ISO BMFF).
- MPU Media Processing Unit
- the upper layer adjacent to the MPU is a DASH player / decoder.
- the stream data of service components video, audio, subtitles, etc.
- ISO BMFF ISO Base Media File Format
- the upper layer of the physical layer is an IP layer corresponding to the network layer.
- an upper layer adjacent to the IP layer is a TCP (Transmission Control Protocol) layer corresponding to the transport layer
- an upper layer adjacent to the TCP layer is an HTTP layer corresponding to the application layer. That is, a protocol such as TCP / IP operating on a network such as the Internet 90 is implemented by these layers.
- TCP Transmission Control Protocol
- NRT content NRT Files
- This signaling includes all signaling such as signaling transmitted by the above-described ROUTE and MMTP.
- the NRT content is an example of content acquired via communication, and for example, content such as an application may be transmitted.
- the layers other than the layers described above are DASH segments (ISO BMFF), and the upper layers adjacent to this DASH segment (ISO BMFF) are the DASH player / decoder. Is done.
- the stream data of service components video, audio, subtitles, etc.
- the stream data of service components that make up content such as VOD programs must be transmitted in DASH segment units according to the ISO BMFF standard. become.
- Applications can be transmitted by using protocols such as ROUTE and MMTP for one-way broadcasting and TCP / IP protocol for two-way communication.
- this application can be an application developed by HTML5, JS (JavaScript (registered trademark)), or the like.
- the HTTP proxy (HTTP ⁇ Proxy) is described as part of ROUTE, which is implemented in the client device 40 when a DASH segment (ISO BMFF) file is acquired by an application.
- DASH segment ISO BMFF
- the broadcast middleware is supposed to be implemented as an HTTP server.
- EME / CENC Encrypted Media Extension-/ Common Encryption Scheme
- W3C World Wide Web Consortium
- MPEG Motion Picture Experts Group
- EME / CENC is described in part of DASH segment (ISO ⁇ ⁇ ⁇ ⁇ BMFF) and MPU (ISO BMFF).
- SLT metadata as LLS signaling and metadata such as USBD, S-TSID, MPD, and AST as SLS signaling are described in a markup language such as XML (Extensible Markup Language).
- a one-way broadcasting layer and a part of a two-way communication layer become a common protocol, so Can transmit the stream data of the service components that make up the content in units of DASH segments according to the ISO BMFF standard. For this reason, in the case of performing both one-way broadcast streaming distribution and two-way communication streaming distribution, the higher-layer protocol is shared. For example, in the broadcast server 20 and the client device 40, Mounting burden and processing burden can be reduced.
- FIG. 3 shows the structure of ROUTE. However, FIG. 3 also describes FLUTE for comparison with ROUTE.
- FLUTE is composed of a scalable file object multicast protocol called ALC (Asynchronous Layered Coding), specifically a combination of its building blocks, LCT (Layered Coding Transport) and FEC (Forward Error Correction) components.
- ALC Asynchronous Layered Coding
- LCT Layered Coding Transport
- FEC Forward Error Correction
- ALC is a protocol suitable for multicast transmission of arbitrary binary files in one direction.
- ALC was developed as a highly reliable asynchronous one-to-many broadcast type protocol, but uses LCT and FEC, and applies the FEC to the target file and stores it in the LCT packet.
- LCT low-density convergence protocol
- FEC FEC-Fi Protected Access
- a transport session in FLUTE is identified by a unique TSI (Transport Session Identifier) in the scope of the source IP address.
- TSI Transaction Session Identifier
- the FEC method can be changed for each transport session or for each file.
- FLUTE has introduced transfer control information in XML format called FDT (File Delivery Table) transferred for each transport session.
- the FDT defines the mapping between the identifier of the target file and the LCT packet sequence that stores the corresponding FEC encoding symbol sequence. Furthermore, the MIME type and size of each file, the transfer encoding method, the message digest, and the FEC Parameters necessary for decoding can be stored. Note that FEC can also be applied to the FDT itself, and its own FEC parameters and the like are transmitted separately in the LCT layer.
- ROUTE is an extension of FLUTE, but the difference can mainly include object bundles and media-aware fragmentation.
- FIG. 4 shows the detailed structure of ROUTE.
- the feature of object bundle in ROUTE is that a stream of video and audio consisting of source blocks of different sizes is bundled and configured as one super object, and an FEC repair stream is generated based on that, a source stream, It is in the place of supporting the repair stream related notification at the protocol level.
- an audio stream or the like has a small source object size compared to a video stream because the data amount per unit time (data object) is small.
- data object data amount per unit time
- a source block is cut out from a plurality of source streams with different rates to form a super object, and a repair stream can be configured by FEC repair symbols generated based on the super object. That is, a repair stream is generated across different types of source streams.
- a source stream composed of source symbols, a repair stream composed of repair symbols, and another LCT session in the ROUTE session can be transferred.
- control information on how to create a FEC stream from a source block cut out from multiple source streams is described in S-TSID metadata that extends LSID (FDT) Is done.
- S-TSID metadata that extends LSID (FDT) Is done.
- a broadcast stream is a model in which all the streams constituting a service are multiplexed and transmitted on the transmitter side, and streams necessary for the broadcast stream are selected on the receiver side. Therefore, it is possible to apply a processing model in which a super-object consisting of all the streams constituting the service is configured on the transmitter side, the super-object is restored on the receiver side, and then the necessary streams are selected.
- the FEC configuration method realized by ROUTE is effective.
- the client device 40 in order to improve the performance of access to an application associated with a specific service such as a broadcast program, it is necessary to cache a necessary file in a local cache in advance.
- a model is assumed in which every file acquired via broadcast or communication is temporarily stored in a local cache on a local file system in the client device 40 and provided to a stream renderer or application. Has been.
- the client device 40 cannot cache all receivable broadcast wave files due to limitations of tuners and storage resources, only the file group necessary for the currently selected service is stored.
- the service channel
- an operation of immediately releasing the storage resource is assumed.
- FIG. 5 is a diagram showing an outline of a cache quota domain.
- the cache quota domain is a domain (group) for sharing resources to be reused.
- FIG. 5 illustrates a case where service A, service B, and service C belong to the quota domain 1, and service X and service Y belong to the quota domain 2. Note that the storage area of the local cache in FIG. 5 corresponds to a permanent cache 404B of the local cache 404 in FIG.
- files such as applications and DASH segments shared by the services A to C belonging to the quota domain 1 are cached in a storage area allocated to the quota domain 1 of the local cache. That is, since the file shared by the service belonging to the quota domain 1 is cached in the storage area of the local cache identified by the quota domain 1 (the quota domain identifier thereof), in the service belonging to the quota domain 1, the storage area Files can be acquired and processed (played back).
- files shared by the services X and Y belonging to the quota domain 2 and files such as DASH segments and period files are cached in a storage area allocated to the quota domain 2 of the local cache. That is, since the file shared by the service belonging to the quota domain 2 is cached in the storage area of the local cache identified by the quota domain 2 (the quota domain identifier thereof), the storage area of the service belonging to the quota domain 2 Files can be acquired and processed (played back).
- each service cannot access resources of other quota domains across the quota domain to which it belongs. For example, services A to C belonging to the quota domain 1 cannot access the resources of the quota domain 2, and services X and Y belonging to the quota domain 2 cannot access the resources of the quota domain 1.
- a service belonging to each quota domain can share (use) resources within the quota domain to which it belongs.
- a plurality of services provided by a single broadcasting station or a plurality of services provided by a federation of broadcasting stations organized by a plurality of broadcasting stations belong to the same cash quota domain, so that For each domain, multiple services share resources (files).
- FIG. 6 is a diagram illustrating an arrangement example of quota domain identifiers.
- the quota domain identifier for identifying the cache quota domain can be transmitted by signaling transmitted in each layer of the broadcast wave. That is, in the signaling, by adding an attribute (or element) that can specify the quota domain identifier of the cache quota domain to which the target service belongs, the client device 40 can perform the same operation based on the quota domain identifier included in the signaling. Resources (files) can be shared by services belonging to the cache quota domain.
- the quota domain identifier is SLS metadata that is LLS signaling stored in the payload of the IP / UDP packet or SLS transmitted in the LCT session that is stored in the payload of the IP / UDP packet.
- SLS metadata LLS signaling stored in the payload of the IP / UDP packet or SLS transmitted in the LCT session that is stored in the payload of the IP / UDP packet.
- the SLT metadata can specify attributes of multiple services.
- an attribute an attribute (or element) that can specify a quota domain identifier is added.
- the quotaDomain attribute in the service element of the SLT metadata it becomes possible to specify the quota domain identifier of the cache quota domain to which the target service belongs.
- the SLT metadata specifies the quota domain identifier of the quota domain 1 (FIG. 5) as the quotaDomain attribute of the service element in which the service IDs of the services A to C are specified. So that In the SLT metadata, the quota domain identifier of the quota domain 2 (FIG. 5) is designated as the quotaDomain attribute of the service element in which the service IDs of the services X and Y are designated.
- the target service is defined by defining the quotaDomain attribute in the USD element of the USBD metadata. It is possible to specify the quota domain identifier of the cache quota domain to which it belongs.
- the quota domain identifier of the quota domain 1 (FIG. 5) is specified as the quotaDomain attribute of the USD element in the USBD metadata of the services A to C.
- the quota domain identifier of the quota domain 2 (FIG. 5) is specified as the quotaDomain attribute of the USD element.
- SLT metadata As described above, by expanding SLT metadata, USBD metadata, S-TSID metadata, or AST metadata and specifying a quota domain identifier, service units, LCTs can be created within the same cache quota domain.
- Resources Files
- each service is composed of one or a plurality of LCT sessions, and in each LCT session, for example, a DASH segment, an application file, an arbitrary file, and the like are transmitted.
- the service entry (basic attribute for each service) of SLT metadata is extended, or the attribute for each service of USBD metadata.
- a quotaDomain attribute For a file transmitted by the target service, a quota domain identifier for identifying a storage area of a local cache in which the file is stored is designated by a quotaDomain attribute of SLT metadata or USBD metadata. It corresponds to a character string.
- the file in this case is, for example, a file such as a DASH segment, a period file, or an application, and includes not only a file acquired via broadcasting but also a file acquired via communication.
- a cache quota domain for example, quota domain 1
- quota domain 1 a cache quota domain 1
- all files transmitted in the LCT session belonging to the target service When the cache is instructed to be cached in the local cache (permanent cache thereof), all files are cached in the storage area allocated to the cache quota domain (eg, quota domain 1) of the local cache (see FIG. 8 A (B)).
- SLS signaling location information is specified in the service element of the SLT metadata.
- This location information is specified by the BroadcastSvcSignaling element when SLS signaling is acquired via broadcasting, and is specified by the SvcInetUrl element when SLS signaling is acquired via communication.
- the USBD metadata is acquired via broadcast or communication according to the location information of the service element of SLT metadata.
- the attributes for each LCT session in the S-TSID metadata are extended and the quotaDomain attribute is defined. That is, for the files transmitted in the target LCT session, the quota domain identifier for identifying the storage area of the local cache where these files are stored is the character specified by the quotaDomain attribute of the S-TSID metadata. It corresponds to a column.
- the file in this case is, for example, a file such as a DASH segment, a period file, or an application.
- a cache quota domain for example, quota domain 1
- the service to which the target LCT session belongs is changed to the cache quota domain (for example, It is recognized that it belongs to the quota domain 1).
- the files are It is cached in the storage area of the cache quota domain (for example, quota domain 1) of the cache (C1 in FIG. 8).
- the LCT session belongs to the same service as the LCT session for which the cache quota domain (for example, quota domain 1) is specified, the LCT session for which the cache quota domain (for example, quota domain 1) is not specified Is excluded from the target of the persistent cache (C2 in FIG. 8).
- the STSIDUri attribute of the USD element of the USBD metadata contains a URI (Uniform Resource Identifier) indicating the acquisition source of the S-TSID metadata. It is specified. And according to this URI, S-TSID metadata is acquired.
- URI Uniform Resource Identifier
- the attribute for each application of the AST metadata is extended and the quotaDomain attribute is defined.
- the quota domain identifier for identifying the storage area of the local cache where the application file to be described in the target AST metadata is stored corresponds to the character string specified by the quotaDomain attribute of the AST metadata. become.
- a cache quota domain for example, quota domain 1
- the service to which the target application belongs is assigned to the cache quota domain (for example, quota domain 1). Is recognized as belonging to.
- the files of the application for which the cache quota domain (for example, quota domain 1) is designated in the local cache (permanent cache thereof)
- the files are stored in the cache quota of the local cache. It is cached in a storage area of a domain (for example, quota domain 1) (D in FIG. 8).
- a domain for example, quota domain 1
- the application for which the cache quota domain (for example, quota domain 1) is not specified is persistent. Not eligible for caching.
- the concept of the cache quota domain is introduced, and the quota domain identifier (resource sharing information) that identifies the cache quota domain is included in metadata (control information) such as SLT, USBD, S-TSID, and AST.
- metadata control information
- the files (resources) included in the service belonging to the same cache quota domain are held in the local cache (permanent cache), and are transmitted in units of services, units of LCT sessions, or applications. It becomes possible to share by unit.
- FIGS. 9 to 14 a case where a cache quota domain is implemented in a system that inserts second content (advertisement) by an application transmitted together with first content (broadcast program). explain. Since the application performs advertisement insertion control (Ad-Insertion) by executing a script (Script), the application is hereinafter referred to as a script application (Script ⁇ App).
- a script application Script ⁇ App
- FIG. 9 is a diagram for explaining the flow of advertisement insertion.
- FIG. 9 shows an example in which an advertisement (TV2_Ad) suitable for the user is inserted in the client device 40 instead of the default advertisement (TV1_Ad) reproduced during the broadcast program (BP1, BP2). ing.
- TV2_Ad an advertisement suitable for the user is inserted in the client device 40 instead of the default advertisement (TV1_Ad) reproduced during the broadcast program (BP1, BP2). ing.
- time t2 to time t2 between time t1 to time t2 at which the broadcast program BP1 is reproduced and time t3 to time t4 at which the broadcast program BP2 is reproduced.
- the advertisement Ad1 that is acquired in real time is usually played back.
- the advertisement Ad2 is displayed when the broadcast program BP1-1 is played from time t1 to time t2. That is, it is acquired via broadcasting or communication before the advertisement insertion interval and cached in a local cache (permanent cache).
- the client device 40 when the scene of the broadcast program BP1-2 is reached, a question for the user is superimposed on the video. And the client apparatus 40 displays the advertisement suitable for the said user according to the user's answer with respect to a question. For example, in the client device 40, when the user answers the question, the advertisement Ad2 for insertion corresponding to the answer is read from the local cache (permanent cache thereof), and the default advertisement Ad1 is It will be replaced with the advertisement Ad2 suitable for the user.
- an advertisement that is likely to be viewed by the user is cached in the local cache (permanent cache) of the client device 40, and the advertisement adapted to the user is used using the cached advertisement. Can be displayed.
- advertisement insertion in FIG. 9 an example in which the content of an advertisement suitable for the user is selected in accordance with the input operation of the user is shown.
- information exchange with such a user In addition to the interaction, for example, the user can select the content of the advertisement by using information on the user's preset characteristics such as the user's preference and profile (for example, gender, age, residential area, etc.) Also good.
- a file including a Period element corresponding to an advertisement insertion section of MPD metadata is prepared in advance, and a Period element that specifies a segment corresponding to a stream of advertisement content is set to a user characteristic (for example, , A system that dynamically changes according to user preferences, etc.).
- a client device 40 corresponding to such advertisement insertion control is shown in FIG.
- the client device 40 has an application / codec function, a DASH client function, and a transport stack / HTTP server function.
- the transport stack / HTTP server function includes an XLink resolver (XLink Resolver) and an HTTP proxy cache (HTTP Proxy Cache).
- XLink Resolver XLink Resolver
- HTTP Proxy Cache HTTP Proxy Cache
- the HTTP server of the communication server 30 may have the function of the XLink resolver.
- the MPD metadata transmitted as SLS signaling is received in the client device 40
- the MPD metadata is acquired by the HTTP proxy cache and notified to the DASH client (S51).
- a URL Uniform Resource Locator
- XLink resolver operating on the HTTP server of the client device 40 or the communication server 30
- A1 (Ad Break # 1), M1 (Main Program), A2 (Ad Break # 2), M2 (Main Program) which are Period elements described in the MPD metadata , A3 (Ad Break # 3), M3 (Main Program) If you focus on the Period element that is A1 (Ad Break # 1), the URL of the xlink: href attribute is "http://adservice.com/ adp-1? user $ groupID $ "is described.
- A2 AdBreak # 2
- A3 Ad Break ⁇ # 3
- the XLink resolver of the client device 40 or the communication server 30 is generated for a specific user (for example, a user of class A) specified by the groupID when the URL in which the groupID value is inserted is notified from the DASH client.
- a Period element file including the URL (hereinafter referred to as a period file) is returned to the DASH client (S53).
- the URL included in the Period element is a segment URL (segment URL) distributed by the ROUTE protocol in the case of unidirectional broadcasting or the HTTP protocol in the case of bidirectional communication.
- the DASH client and the HTTP proxy cache exchange segment requests and deliveries according to the Period element of the period file acquired in the process of Step S53, so that the Period element A segment corresponding to the segment URL is acquired (S54).
- the content of the advertisement corresponding to the segment acquired in this way is reproduced in the advertisement insertion section (for example, the section from time t2 to time t3 in FIG. 9).
- M1 Mainn Program
- M2 Mainn Program
- M3 Mainn Program
- A1 Ad Break
- # 1) is inserted
- A2 Ad Break # 2
- A3 Ad Break # 3
- A1 Ad Break # 1
- user characteristics for example, user preferences
- A2 Ad Break # 2
- A3 Ad Break # 3
- FIG. 10 an example in which the XLink resolver is operated on the client device 40 or the HTTP server of the communication server 30 has been described. However, in the client device 40, the script application plays a role of the XLink resolver. can do.
- the DASH client when the DASH client detects the URL of the xlink: href attribute of the Period element for advertisement insertion by parsing the MPD metadata (syntactic analysis), it immediately sends an HTTP request to the XLink that runs on the HTTP server. Instead of sending it to the resolver, notify the script application of the URL.
- the script application is based on the information for identifying the advertisement insertion section reflected in the path part of the URL or the query string.
- the advertisement content (Ad segment) that matches the target user is selected from the insertion candidates for the advertisement content (Ad segment) corresponding to the section.
- the script application generates a period file including a Period element corresponding to the selected advertisement content (Ad segment), and responds to the DASH client.
- the Period element of this period file contains a URL generated for a specific user (for example, a user of class A) specified by groupID, and when playing an Ad segment group based on this list of segment URLs, The content of the advertisement will be played.
- the selection of advertisement content suitable for the user is performed depending on, for example, the user preference managed by the client device 40, or the exchange of information with the user (interaction). May be performed according to information acquired at any time.
- an advertisement content suitable for the user is selected according to the input operation of the user.
- the content of the advertisement (Ad segment) acquired via broadcasting or communication is temporally before the advertisement insertion section by the script application in the local cache (permanent cache).
- the certainty of advertisement insertion by advertisement insertion control can be ensured. For example, when acquiring advertisement content (Ad segment) via communication, it is assumed that the advertisement content (Ad segment) cannot be acquired depending on the communication status of the Internet 90, etc. Thus, the certainty of advertisement insertion by advertisement insertion control can be improved.
- the concept of the cache quota domain is introduced, and the client device 40 can share files of advertisement contents (Ad segments) that are reused in a plurality of services. It is possible to increase the reusability of the candidate advertisement content (Ad segment) cached in the persistent cache), and to perform the advertisement insertion by the advertisement insertion control more reliably.
- 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.
- ⁇ Period element of the main part describes information for managing the reproduction of the main part contents (MP4 format video file).
- EIDR Entertainment Identifier Registry
- schemeIdUri attribute and the value attribute of the AssetIdentifier element are assigned to the schemeIdUri attribute and the value attribute of the AssetIdentifier element.
- the URL is described in the xlink: href attribute of the Period element together with information for managing the playback of the default advertisement content (MP4 format video file) ( A) in the figure.
- This URL is notified to the XLink resolver operating on the HTTP server of the communication server 30, whereby the insertion advertisement is acquired, and the default advertisement is replaced with the insertion advertisement.
- ⁇ Period element of the main part describes information for managing the reproduction of the main part contents (MP4 format video file).
- the URL is described in the xlink: href attribute of the Period element together with information for managing the playback of the default advertisement content (MP4 format video file) ( A) in the figure.
- the URL in which the value of the groupID is inserted is notified to the XLink resolver operating on the HTTP server of the client device 40, so that an advertisement suitable for the specific user specified by the groupID is acquired.
- the advertisement is replaced with an advertisement suitable for the user.
- “urn: atsc: ad-insertion” indicates that the solution for advertisement insertion control must be requested to a script (script application) executed locally (client device 40). However, the detailed contents thereof will be described later.
- the advertisement content is described as an example, and the file of the advertisement content (Ad segment) can be shared by multiple services using the cache quota domain. It can also be applied to other content.
- a file is an example of a content resource, and any data can be used as long as it can be processed by the client device 40.
- FIG. 15 is a diagram illustrating an example of the format of SLT metadata in the XML format.
- SLT format SLT format
- FIG. 15 among the elements and attributes, “@” is added to the attribute. Further, the indented element and attribute are specified for the upper element.
- 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 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, quotaDomain 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.
- the quota domain identifier of the cache quota domain to which the target service belongs is specified. Services that belong to the same cache quota domain share resources (files) cached in local memory.
- 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 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. 16 is a diagram illustrating an example of the format of the USB format metadata in the 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, quotaDomain 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.
- the quota domain identifier of the cache quota domain to which the target service belongs is specified. Services that belong to the same cache quota domain share resources (files) cached in local memory.
- 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. 17 is a diagram illustrating an example of a format of S-TSID metadata.
- the S-TSID element is a root element and is a higher element of the serviceId attribute and RS element.
- a service ID is specified in the serviceId attribute.
- 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. Details of the SrcFlow element will be described later with reference to FIG. Repair flow information is specified in the RprFlow element.
- FIG. 18 is a diagram illustrating an example of the format of the SrcFlow element included in the S-TSID metadata of FIG.
- the SrcFlow element is an upper element of the rt attribute, minBuffSize attribute, EFDT element, ContentInfo element, and Payload element.
- minBuffSize attribute the minimum buffer size required by the client device 40 is specified.
- the EFDT element information related to the extended FDT (Extended ⁇ FDT) is specified.
- Information related to the content is specified in the ContentInfo element.
- the ContentInfo element is an upper element of the quotaDomain attribute.
- the quota domain identifier of the cache quota domain to which the service including the target LCT session belongs is specified. Services that belong to the same cache quota domain share resources (files) cached in local memory.
- 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.
- (AST format) 19 to 21 are diagrams showing examples of the format of AST metadata.
- ApplicationList element is a root element and is an upper element of Application element and ApplicationReference element.
- the Application element is an upper element of the appName element, applicationIdentifier element, applicationDescriptor element, applicationUsageDescriptor element, applicationBoundary element, applicationTransport element, applicationLocation element, and applicationSpecificDescriptor element.
- the appName element is an upper element of the Language attribute and specifies the name of the application.
- the applicationIdentifier element is an upper element of the orgID element and appID, and specifies the application ID of the application.
- the applicationDescriptor element is a high-level element of the type element, controlCode element, visibility element, serviceBound element, priority element, version element, icon element, and storageCapabilities element, and specifies information related to the properties of the target application.
- the applicationUsageDescriptor element is an upper element of the ApplicationUsage element, and specifies information related to the application usage type.
- information related to the application boundary is specified.
- Information related to the transport protocol of the application is specified in the applicationTransport element.
- URLBase element and URLExtension element are arranged and URL is specified.
- An extension URL is specified in the URLExtension element.
- atsc ROUTESessionInfo element (including LCTSession element, tsi attribute, plpID attribute), broadcastStreamId attribute, plpID attribute, sourceIpAddress attribute, destinationIpAddress attribute, and destinationPort attribute are arranged, Information about the ROUTE session is specified.
- application location information is specified.
- applicationSpecificDescriptor element an application descriptor is arranged.
- dvbDescriptor corresponding to DVB (Digital Video Broadcasting) htmlDescriptor corresponding to HTML (HyperText Markup Language), atscDescriptor corresponding to ATSC, or otherDescriptor corresponding to other standards are selectively arranged. .
- the atsc: atscDescriptor element is a higher level element of the quotaDomain attribute, size element, requiredCapabilities element, icon element, ApplicationRecordingDescriptor element, timeSlotInfo element, contentLinkage element, contentItem element, and graphicConstraintsDescriptor, and specifies information related to ATSC (ATSC3.0) Is done.
- the quota domain identifier of the cache quota domain to which the service including the target application belongs is specified. Services that belong to the same cache quota domain share resources (files) cached in local memory.
- the icon element includes a filename attribute, a size attribute, and an aspectRatio attribute.
- the ApplicationRecordingDescriptor element includes a scheduled_recording_flag element, a trick_mode_aware_flag element, a time_shift_flag element, a dynamic_flag element, an av_synced_flag element, an initializing_replay_flag element, and a storage_properties element.
- the timeSlotInfo element includes a timeslot_type element, a timeslot_start element, a timeslot_length element, an acquisition_time element, and a repeat_period element.
- the contentItem element includes a location attribute, a contentLinkage attribute, an updatesAvailable attribute, a size attribute, and a timeSlotInfo element.
- This timeSlotInfo element includes a timeslot_type element, a timeslot_start element, a timeslot_length element, an acquisition_time element, and a repeat_period element.
- the graphicConstraintsDescriptor element includes a can_run_without_visible_ui element, a handles_configuration_changed element, a handles_externally_controlled_video element, a graphics_configuration_byte element, and a screenPosition element.
- SLT metadata, USBD metadata, S-TSID, and AST metadata are examples. For example, other elements and attributes are added. You may make it employ
- the SLT metadata, USBD metadata, S-TSID, and AST metadata are not limited to the XML format, and may be described in other markup languages or may be in a section format.
- the quota domain identifier specified by the quotaDomain attribute added by extending signaling such as SLT metadata, USBD metadata, S-TSID, and AST metadata should be included in one type of metadata. It may be included in a plurality of types of metadata. Further, when a plurality of services are provided, a quota domain identifier specified by the quotaDomain attribute may be described in different types of metadata for each service. Furthermore, in the example of the format of each metadata described above, the case where the quota domain identifier is specified by the quotaDomain attribute has been described as an example. However, the quota domain identifier is not limited to the attribute, and is described as an element or text, for example. It may be specified by the information etc.
- FIG. 22 is a diagram illustrating a configuration example of the Ad / DASH server 10 of FIG.
- the Ad / DASH server 10 includes a reception unit 101, an Ad / DASH segment generation unit 102, a script application generation unit 103, an MPD generation unit 104, a processing unit 105, and a transmission unit 106.
- the receiving unit 101 receives streaming distribution data from an external server (not shown) or the like and supplies the data to the Ad / DASH segment generation unit 102, the script application generation unit 103, and the MPD generation unit 104.
- the Ad / DASH segment generation unit 102 generates an Ad segment and a DASH segment based on the data supplied from the reception unit 101 and supplies the generated Ad segment and DASH segment to the processing unit 105.
- the Ad segment is a segment file obtained by processing the content of the advertisement.
- 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 communication line, or a recorded content (for example, a drama) stored in a storage.
- This is a segment file obtained by processing content such as a pre-recorded program.
- the Ad segment can be said to be a kind of DASH segment, here, for convenience of explanation, the Ad segment and the DASH segment will be described separately.
- the script application generation unit 103 generates a script application based on the data supplied from the reception unit 101 and supplies the script application to the processing unit 105.
- the script application is an application that can execute a script.
- This script application may be an application developed in a markup language such as HTML5 or a script language such as JavaScript (registered trademark).
- the MPD generation unit 104 generates MPD metadata based on the data supplied from the reception unit 101 and supplies it to the processing unit 105.
- MPD metadata a Period element corresponding to content such as a program or an advertisement is described, and details thereof will be described later.
- the processing unit 105 applies the Ad segment and DASH segment supplied from the Ad / DASH segment generation unit 102, the script application supplied from the script application generation unit 103, and the MPD metadata supplied from the MPD generation unit 104. Then, necessary processing is performed and the data is supplied to the transmission unit 106.
- the transmission unit 106 transmits the data supplied from the processing unit 105 to the broadcast server 20 or the communication server 30.
- data distributed via broadcasting is transmitted to the broadcast server 20, and data distributed via communication is It is transmitted to the communication server 30.
- the Ad / DASH server 10 is configured as described above.
- FIG. 23 is a diagram illustrating a configuration example of the broadcast server 20 of FIG.
- the broadcast server 20 includes a reception unit 201, a signaling generation unit 202, a processing unit 203, and a transmission unit 204.
- the receiving unit 201 receives the Ad segment, the DASH segment, the script application, and the MPD metadata transmitted from the Ad / DASH server 10 and supplies them to the processing unit 203. However, not all of the Ad segment, DASH segment, script application, and MPD metadata are provided from the Ad / DASH server 10, but only data (files) distributed via broadcasting are provided here. And received by the receiving unit 201.
- the receiving unit 201 receives NRT content data (file) from an external server (not shown) or the like and supplies it to the processing unit 203.
- the signaling generation unit 202 generates signaling and supplies it to the processing unit 203.
- the signaling includes LLS signaling such as SLT metadata, and SLS signaling such as USBD metadata, S-TSID metadata, and AST metadata.
- LLS signaling such as SLT metadata
- SLS signaling such as USBD metadata, S-TSID metadata, and AST metadata.
- the quota domain attribute defined in the SLT metadata, USBD metadata, S-TSID metadata, or AST metadata is set to the target cache quota domain.
- a quota domain identifier will be specified.
- the processing unit 203 performs necessary processing on the Ad segment and DASH segment, script application, MPD metadata, and NRT content supplied from the receiving unit 201 and the signaling supplied from the signaling generation unit 202, and transmits To the unit 204.
- an IP / UDP packet in which LCT session data including Ad segment and DASH segment, script application, NRT content, and SLS signaling (USBD metadata, MPD metadata, etc.) are stored in the payload
- SLS signaling Processing for generating an IP / UDP packet in which data (SLT metadata or the like) is stored in the payload is performed.
- the transmission unit 204 transmits a broadcast wave (digital broadcast signal) corresponding to the data supplied from the processing unit 203 via the transmission path 80 by the antenna 211 (simultaneous broadcast distribution).
- Broadcast server 20 is configured as described above.
- FIG. 24 is a diagram illustrating a configuration example of the communication server 30 of FIG.
- the communication server 30 includes a reception unit 301, a period file generation unit 302, a processing unit 303, and a communication unit 304.
- the receiving unit 301 receives the Ad segment, the DASH segment, the script application, and the MPD metadata transmitted from the Ad / DASH server 10 and supplies them to the processing unit 303. However, not all of the Ad segment, DASH segment, script application, and MPD metadata are provided from the Ad / DASH server 10, but only data (files) distributed via communication are provided here. And is received by the receiving unit 301.
- the processing unit 303 processes data supplied from the reception unit 301 in response to a request (XLink resolution request) from the client device 40 received by the communication unit 304 and supplies the processed data to the communication unit 304.
- the communication unit 304 transmits data (at least one of Ad segment, DASH segment, script application, and MPD metadata) supplied from the processing unit 303 to the Internet 90.
- data at least one of Ad segment, DASH segment, script application, and MPD metadata supplied from the processing unit 303 to the Internet 90.
- the processing unit 303 requests the period file generation unit 302 to generate a period file.
- the period file generation unit 302 In response to a request from the processing unit 303, the period file generation unit 302 generates a period file including a Period element corresponding to (a characteristic of) the user using the client device 40 and supplies the period file to the processing unit 303.
- the processing unit 303 processes the period file supplied from the period file generation unit 302 and supplies it to the communication unit 304.
- the communication unit 304 transmits the period file supplied from the processing unit 303 to the requesting client device 40 of the XLink resolution request via the Internet 90.
- the communication server 30 is configured as described above.
- FIG. 25 is a diagram illustrating a configuration example of the client device 40 of FIG.
- the client device 40 includes a control unit 401, a reception unit 402, broadcast middleware 403, a local cache 404, a browser 405, an output unit 406, and a communication unit 407.
- the control unit 401 controls the operation of each unit of the client device 40.
- the receiving unit 402 receives and processes a broadcast wave (digital broadcast signal) transmitted (broadcast broadcast) from the broadcast server 20 via the transmission path 80 by the antenna 411, processes the received data,
- the broadcast middleware 403 is supplied.
- the receiving unit 402 includes a tuner and the like.
- the broadcast middleware 403 processes data supplied from the receiving unit 402 and supplies the processed data to the control unit 401 or the local cache 404.
- the Ad segment, the DASH segment, the script application, and the MPD metadata are supplied to the local cache 404. Further, the signaling is supplied to the control unit 401.
- the control unit 401 includes a cache control unit 401A and a reproduction control unit 401B.
- the cache control unit 401A controls the local cache 404 based on signaling supplied from the broadcast middleware 403, a request from the browser 405, and the like.
- the playback control unit 401B controls the browser 405 based on signaling supplied from the broadcast middleware 403.
- the local cache 404 is realized, for example, on a local file system such as on-memory or SSD (solid-state drive).
- a local file system such as on-memory or SSD (solid-state drive).
- the local cache 404 caches data (file) supplied from the broadcast middleware 403 according to the control from the cache control unit 401A.
- data such as an Ad segment, a DASH segment, a script application, and MPD metadata are cached.
- the local cache 404 includes a normal cache 404A and a permanent cache 404B.
- the normal cache 404A is a normal cache, and the data cached therein is erased after an appropriate time (not so long) has elapsed.
- the persistent cache 404B is a special cache, and the data cached therein has priority persistence and will be cached for a longer time than the data cached in the normal cache 404A.
- the cache control unit 401A uses the quota (of the cache quota domain) in the signaling from the broadcast middleware 403 (quotaDomain attribute defined in SLT metadata, USBD metadata, S-TSID metadata, or AST metadata included in).
- quotaDomain attribute defined in SLT metadata, USBD metadata, S-TSID metadata, or AST metadata included in.
- file groups such as Ad segments and DASH segments cached in the persistent cache 404B are linked by the quota domain identifier, so in a plurality of services belonging to the same cache quota domain, Ad segments, DASH segments, etc. File can be shared.
- the browser 405 is a browser that supports HTML5, JavaScript (registered trademark), and the like.
- the browser 405 processes the data (file) read from the local cache 404 according to the control from the playback control unit 401B.
- the browser 405 includes a script execution unit 405A and a DASH client 405B.
- the script execution unit 405A can execute a script described in a script language such as JavaScript (registered trademark). For example, the script execution unit 405A can read a script application from the local cache 404 (the normal cache 404A or the permanent cache 404B) and execute the script application.
- a script language such as JavaScript (registered trademark).
- the script execution unit 405A can read a script application from the local cache 404 (the normal cache 404A or the permanent cache 404B) and execute the script application.
- the script execution unit 405A executes control of the local cache 404 by the cache control unit 401A by executing CacheStorage API (Application Programming Interface) described in the script application. Details of the CacheStorage API will be described later. Further, the script execution unit 405A generates a period file according to the user preference or the like in response to the XLink resolution request from the DASH client 405B, and responds to the DASH client 405B.
- CacheStorage API Application Programming Interface
- the DASH client 405B reads (parses) MPD metadata (file) from the local cache 404 (ordinary cache 404A).
- the DASH client 405B reads and reproduces the Ad segment or the DASH segment (file thereof) from the local cache 404 (the normal cache 404A or the permanent cache 404B) according to the analysis result of the MPD metadata.
- the data of the Ad segment or DASH segment reproduced by the DASH client 405B is supplied to the output unit 406.
- the output unit 406 outputs data supplied from the DASH client 405B in accordance with control from the playback control unit 401B. Thereby, contents such as broadcast programs and advertisements are reproduced, and the video and audio are output.
- the communication unit 407 exchanges data with the communication server 30 via the Internet 90 according to the control from the control unit 401.
- the Ad segment, the DASH segment, the script application, and the MPD metadata are supplied to the local cache 404. Further, the signaling is supplied to the control unit 401. 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.
- the client device 40 is configured as described above.
- steps S101 to S106 are executed by the Ad / DASH server 10
- the processes of steps S201 to S205 are executed by the broadcast server 20
- the processes of steps S301 to S302 are executed by the communication server 30. Executed.
- step S101 the Ad / DASH segment generation unit 102 of the Ad / DASH server 10 generates an Ad segment and a DASH segment.
- step S102 the transmission unit 106 of the Ad / DASH server 10 transmits the Ad segment and the DASH segment generated in the process of step S101 to the broadcast server 20.
- the Ad segment is a segment file obtained by processing the content of the advertisement.
- the DASH segment is a segment file obtained by processing broadcast program content.
- the Ad segment and the DASH segment are generated at the same time. However, these segments may be generated at different timings.
- step S201 the signaling generation unit 202 of the broadcast server 20 generates signaling.
- step S202 the transmission unit 204 of the broadcast server 20 transmits (simultaneous broadcast delivery) the signaling generated in the process of step S201 via the transmission path 80.
- LLS signaling such as SLT metadata and SLS signaling such as USBD metadata are generated as signaling.
- the quota domain attribute defined in the SLT metadata, USBD metadata, S-TSID metadata, or AST metadata is set to the target cache quota domain.
- a quota domain identifier will be specified.
- the Ad segment and the DASH segment transmitted in the process of step S202 are received by the receiving unit 201.
- the transmission unit 204 of the broadcast server 20 transmits the Ad segment and the DASH segment generated by the Ad / DASH server 10 via the transmission path 80 (simultaneous broadcast distribution).
- step S103 the script application generation unit 103 of the Ad / DASH server 10 generates a script application.
- step S104 the transmission unit 106 of the Ad / DASH server 10 transmits the script application generated in the process of step S103 to the broadcast server 20.
- step S ⁇ b> 104 the script application transmitted in step S ⁇ b> 104 is received by the receiving unit 201.
- step S204 the transmission unit 204 of the broadcast server 20 transmits the script application generated by the Ad / DASH server 10 via the transmission path 80 (simultaneous broadcast distribution).
- step S105 the MPD generation unit 104 of the Ad / DASH server 10 generates MPD metadata.
- step S106 the transmission unit 106 of the Ad / DASH server 10 transmits the MPD metadata generated in the process of step S105 to the broadcast server 20.
- the Period element of the broadcast program and the advertisement is described.
- the Period element of the advertisement as the xlink: href attribute, “urn: atsc: ad-insertion: abc: 1234” URL that is is described.
- “urn: atsc: ad-insertion” indicates that the script (script application) executed locally (client device 40) must be requested to resolve advertisement insertion control. To do.
- the client device 40 is allowed to describe the URL consisting of a character string starting from the usual “http:” in the xlink: href attribute of the Period element of the MPD metadata.
- URN Uniform Resource Name
- XLink resolution Period element resolution
- the MPD metadata transmitted in step S ⁇ b> 106 is received by the receiving unit 201.
- the transmission unit 204 of the broadcast server 20 transmits the MPD metadata generated by the Ad / DASH server 10 via the transmission path 80 (simultaneous broadcast distribution).
- steps S202 to S205 it has been described that signaling, Ad segment and DASH segment, script application, and MPD metadata are transmitted at different timings. It will be included in the stream and transmitted.
- the XLink resolution request transmitted from the client device 40 via the Internet 90 is received by the communication unit 304.
- the period file generation unit 302 of the communication server 30 generates a period file.
- the communication unit 304 of the communication server 30 transmits the period file generated in the process of step S301 to the client device 40 that is the transmission source of the XLink resolution request via the Internet 90.
- the XLink resolution request is transmitted from the client device 40 to the communication server 30 because the URL including the character string starting from “http:” is the period element of the MPD metadata. This is when it is described in the xlink: href attribute.
- the processing in steps S401 to S408 is executed by the broadcast middleware 403, and the processing in steps S421 to S423 and the processing in steps S441 to S443 are performed in accordance with the local cache 404 (normal cache 404A, permanent). This is executed by the cache control unit 401A that controls the cache 404B). Further, the processing of steps S461 to S466 is executed by the script execution unit 405A of the browser 405, and the processing of steps S481 to S490 is executed by the DASH client 405B of the browser 405.
- step S 401 the broadcast middleware 403 receives signaling transmitted from the broadcast server 20 via the transmission path 80 via the receiving unit 402.
- step S402 the broadcast middleware 403 processes the signaling received in the process of step S401.
- LLS signaling such as SLT metadata and SLS signaling such as USBD metadata are processed as signaling.
- the quota domain attribute defined in the SLT metadata, USBD metadata, S-TSID metadata, or AST metadata is set to the target cache quota domain. Since the quota domain identifier is designated, services belonging to this cache quota domain are recognized.
- step S403 the broadcast middleware 403 receives the Ad segment and the DASH segment transmitted from the broadcast server 20 via the transmission path 80 via the receiving unit 402.
- step S404 the broadcast middleware 403 transfers the Ad segment and DASH segment received in the process of step S403 to the local cache 404.
- step S421 the cache control unit 401A caches the Ad segment and the DASH segment (file) transferred in the process of step S404 in the normal cache 404A of the local cache 404.
- the Ad segment and the DASH segment (files thereof) are normally cached in the cache 404A. Therefore, if this state continues, the Ad segment and the DASH segment will be deleted after an appropriate time (not so long). become.
- the Ad segment and the DASH segment (file) are cached at the same time is explained, but these segments (files) are cached at different timings. Also good.
- step S405 the broadcast middleware 403 receives a script application transmitted from the broadcast server 20 via the transmission path 80 via the receiving unit 402.
- step S406 the broadcast middleware 403 transfers the script application received in the process of step S405 to the local cache 404.
- step S422 the cache control unit 401A caches the script application transferred in step S406 in the normal cache 404A of the local cache 404. In this case, since the script application is normally cached in the cache 404A, if the state as it is is continued, the script application is deleted after an appropriate time (not so long).
- step S461 the script execution unit 405A acquires the script application cached in the normal cache 404A in the process of step S422 from the local cache 404, and executes the script application.
- step S462 the script execution unit 405A requests the cache control unit 401A to pull the Ad segment into the permanent cache 404B in accordance with the execution of the script application (the process in step S461).
- the instruction to pull the Ad segment into the persistent cache 404B is performed by executing the following CacheStorage API described in the script application, for example.
- the fetchPeriod method is used for an instruction to pull into the persistent cache 404B.
- the segment file (Ad segment file) specified by the segment URL described in the Period element specified by the xmlElement that is the argument of the fetchPeriod method is the target file stored in the persistent cache 404B.
- the fetchFile method is used for an instruction to pull into the persistent cache 404B.
- the segment file (Ad segment file) specified by the url that is the argument of the fetchFile method is the target file stored in the persistent cache 404B.
- step S441 the cache control unit 401A pulls the Ad segment (file) of the insertion candidate from the normal cache 404A of the local cache 404 into the permanent cache 404B in response to the pull-in request of step S462.
- the Ad segment (file) drawn from the normal cache 404A is cached in the permanent cache 404B of the local cache 404 (S442).
- the file group distributed via the broadcast via the transmission path 80 is normally stored in the normal cache 404A (HTTP proxy cache (file system)) of the local cache 404 after the ROUTE protocol is terminated by the broadcast middleware 403. It is unpacked and erased after a certain amount of time (not too long).
- the file is deleted after a time determined by the cache expiration date described in the HTTP header added at the time of ROUTE entity mode file transfer.
- the persistent cache 404B of the local cache 404 is handled as a special area in the HTTP proxy cache.
- the file group expanded in the permanent cache 404B has preferential persistence over the other file group cached in the normal cache 404A, and even if the above “appropriate time” elapses.
- the file is cached until it reaches a quota (quota) allocated in advance in the local cache 404 without being erased.
- the service to which the file group cached in the persistent cache 404B belongs is linked by the quota domain identifier specified in the quotaDomain attribute defined in the SLT metadata, USBD metadata, S-TSID metadata, or AST metadata. Therefore, a specific file (in this example, an Ad segment file) can be shared among a plurality of services belonging to the same cache quota domain.
- step S407 the broadcast middleware 403 receives MPD metadata transmitted from the broadcast server 20 via the transmission path 80 via the receiving unit 402.
- step S408 the broadcast middleware 403 transfers the MPD metadata received in step S407 to the local cache 404.
- step S423 the cache control unit 401A caches the MPD metadata transferred in the process of step S408 in the normal cache 404A of the local cache 404.
- the MPD metadata is normally cached in the cache 404A, the MPD metadata is deleted after an appropriate time (not so long).
- step S481 the DASH client 405B acquires the MPD metadata cached in the normal cache 404A in the process of step S423 from the local cache 404, and parses (parses) the MPD metadata.
- step S482 the DASH client 405B acquires the DASH segment acquired according to the processing results (metadata processing results of SLT, USBD, S-TSID, MPD, etc.) in steps S402 and S481, and cached in the normal cache 404A. , Obtained from the local cache 404.
- step S483 the DASH client 405B plays back the DASH segment acquired in step S482 according to the control from the playback control unit 401B. As a result, the content of the broadcast program is reproduced on the client device 40.
- step S484 the DASH client 405B determines whether to insert an advertisement. If it is determined in step S484 that the advertisement is not inserted, the process returns to step S482, and the processes of steps S482 to S484 are repeated. In this case, the reproduction of the content of the broadcast program is continued. On the other hand, if it is determined in step S484 that an advertisement is to be inserted, the process proceeds to step S485.
- step S485 the DASH client 405B requests the script execution unit 405A to resolve the XLink included in the MPD metadata according to the processing result in step S481.
- the URN consisting of a character string starting from “urn: atsc: ad-insertion” is detected from the URL specified in the xlink: href attribute of the Period element of the MPD metadata by the processing in step S481.
- an event that prompts XLink resolution (Period element resolution) is issued to the script application simultaneously executed by the script execution unit 405A.
- step S463 the script execution unit 405A acquires the user preference according to the logic in the script of the script application being executed in response to the XLink resolution request of the process in step S485.
- step S464 the script execution unit 405A generates a period file based on the user preference acquired in the process of step S463.
- the script execution unit 405A is inserted into the MPD metadata based on the URL notified by the event from the DASH client 405B (for example, the URL “urn: atsc: ad-insertion: abc: 1234”).
- PDI Preference-Demographic-and-Interest
- This PDI is a mechanism that reproduces (accumulates) only content that matches a user's preference by generating information indicating a user's answer to a question provided from a specific server.
- step S465 the script execution unit 405A responds to the DASH client 405B with the period file generated by the process in step S464.
- step S486 the DASH client 405B acquires the period file returned in the process of step S465, and parses (syntactically analyzes) the period file.
- step S487 the DASH client 405B acquires the Ad segment cached in the permanent cache 404B of the local cache 404 according to the processing result in step S486.
- the URL of the target Ad segment is obtained by parsing the Period element in the process of step S486, the Ad segment of the persistent cache 404B is acquired according to the URL.
- the Ad segment file is a file shared by a plurality of services belonging to the same cache quota domain, the Ad segment file can be reused.
- step S488 the DASH client 405B reproduces the Ad segment acquired in step S487 according to the control from the reproduction control unit 401B. Thereby, in the client device 40, the content to be reproduced is switched from the broadcast program to the advertisement (the advertisement is inserted).
- step S489 the DASH client 405B determines whether reproduction of the Ad segment (processing in step S488) has been completed. If it is determined in step S489 that the playback of the Ad segment has not been completed, the process returns to step S488, and the playback of the Ad segment is continued.
- step S489 if it is determined in step S489 that the playback of the Ad segment has been completed, the process proceeds to step S490.
- step S490 the DASH client 405B notifies the script execution unit 405A of completion of playback of the Ad segment.
- step S466 in response to the Ad segment playback completion notification in step S490, the script execution unit 405A deletes the playback completion Ad segment from the permanent cache 404B to the cache control unit 401A by the script application being executed. Request.
- deletion instruction of the Ad segment from the persistent cache 404B is performed by executing the following CacheStorage API described in the script application, for example.
- the deleteFile method is used for a deletion instruction from the persistent cache 404B.
- the segment file (Ad segment file) specified by the url that is an argument of the deleteFile method becomes a file to be deleted from the persistent cache 404B.
- step S443 the cache control unit 401A deletes the reproduction completed Ad segment (file thereof) from the permanent cache 404B of the local cache 404 in response to the processing deletion request in step S466.
- the reproduced content is switched from the advertisement to the broadcast program.
- 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
- a cache quota domain (Cache Quota Domain) may be referred to by other names having similar nuances such as a cache quota group (Cache Quota Group).
- AST Application Signaling Table
- AIT Application Information Table
- NRT Non Real Time
- LCC Locally Cached Content
- 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 announced.
- 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. 29 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.
- the control unit distinguishes the shared resource that is a shared resource from other resources.
- the receiving device according to (1).
- the content and the control information are transmitted by broadcast waves, The service is a digital broadcast service, The receiving apparatus according to (1) or (2), wherein the control information is signaling for providing the service.
- the signaling is first signaling that can specify attributes of a plurality of services, The receiving apparatus according to (3), wherein the first signaling includes the resource sharing information specified in service units.
- the signaling is second signaling that can specify attributes for each service, The receiving apparatus according to (3), wherein the second signaling includes the resource sharing information specified in a predetermined unit within a target service.
- the content resource is a file of a predetermined format, The control unit stores the file of the shared resource in a second storage area different from the first storage area in which the file of the other resource is stored according to the operation of the application transmitted together with the content.
- the receiving device according to any one of (6).
- the receiving device (8) The receiving device according to (7), wherein the control unit deletes the file of the shared resource stored in the second storage area according to the operation of the application.
- the broadcast wave is a broadcast wave corresponding to an IP (Internet Protocol) transmission method, The receiving device according to any one of (3) to (8), wherein data of the content resource file is stored and transmitted in an IP packet including a UDP (User Datagram Protocol) packet.
- the receiving device is Receive content, Based on the control information, which is control information transmitted together with the content, the resource information indicating whether the resource of the content is a resource shared by a plurality of services, the resource of the content is: A data processing method including a step of controlling storage of the resource in a storage device so as to be shared by a plurality of services. (12) A generating unit that generates control information including resource sharing information indicating whether the resource of the content is a resource shared by a plurality of services; A transmission apparatus comprising: a transmission unit that transmits the control information together with the content.
- the content and the control information are transmitted by broadcast waves,
- the service is a digital broadcast service,
- the signaling is first signaling that can specify attributes of a plurality of services,
- the signaling is second signaling that can specify attributes for each service,
- the transmission apparatus according to (13), wherein the second signaling includes the resource sharing information designated in a predetermined unit within a target service.
- the transmission apparatus according to (15), wherein the resource sharing information is specified in service units, session units, or application units.
- the transmission device according to any one of (12) to (16), wherein the content resource is a file in a predetermined format.
- the broadcast wave is a broadcast wave corresponding to the IP transmission method,
- the content resource file data is transmitted by being stored in an IP packet including a UDP packet (13) to (17).
- the content includes advertising content,
- the transmission device according to any one of (12) to (18), wherein the resource sharing information is identification information for identifying a group to which a plurality of services that share the content resource of the advertisement belongs.
- the transmitting device is Generate control information including resource sharing information that indicates whether the content resource is a resource shared by multiple services, A data processing method including a step of transmitting the control information together with the content.
- Ad / DASH server 10 Ad / DASH server, 20 broadcast server, 30 communication server, 40 client device, 80 transmission path, 90 Internet, 101 reception unit, 102 Ad / DASH segment generation unit, 103 script application generation unit, 104 MPD generation Unit, 105 processing unit, 106 transmission unit, 201 reception unit, 202 signaling generation unit, 203 processing unit, 204 transmission unit, 301 reception unit, 302 period file generation unit, 303 processing unit, 304 communication unit, 401 control unit, 401A Cache control unit, 401B playback control unit, 402 reception unit, 403 broadcast middleware, 404 local cache, 404A normal cache, 404B permanent cache Gerhard, 405 browser, 405A script execution unit, 405B DASH client, 406 output unit, 407 communication unit, 1000 Computer, 1001 CPU
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- Marketing (AREA)
- Information Transfer Between Computers (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
2.キャッシュクォータドメインの概要
3.アプリケーションの応用例
4.シグナリングの例
5.各装置の構成
6.各装置で実行される処理の流れ
7.変形例
8.コンピュータの構成
図1は、本技術を適用した伝送システムの一実施の形態の構成を示す図である。なお、システムとは、複数の装置が論理的に集合したものをいう。
図2は、本技術のIP伝送方式のプロトコルスタックの例を示す図である。
図3は、ROUTEの構造を示す図である。ただし、図3には、ROUTEとの比較のため、FLUTEについても記述している。
図5は、キャッシュクォータドメインの概要を示す図である。
図6は、クォータドメイン識別子の配置例を示す図である。
キャッシュクォータドメインのクォータドメイン識別子が、SLTメタデータの拡張により指定される場合、SLTメタデータは、複数のサービスの属性を指定可能であるので、対象のサービスの属性として、クォータドメイン識別子を指定可能な属性(又は要素)を追加することになる。ここでは、例えば、SLTメタデータのservice要素に、quotaDomain属性を定義することで、対象のサービスが属するキャッシュクォータドメインのクォータドメイン識別子を指定することが可能となる。
キャッシュクォータドメインのクォータドメイン識別子が、USBDメタデータの拡張により指定される場合、USBDメタデータのUSD要素に、quotaDomain属性を定義することで、対象のサービスが属するキャッシュクォータドメインのクォータドメイン識別子を指定することが可能となる。
キャッシュクォータドメインのクォータドメイン識別子が、S-TSIDメタデータの拡張により指定される場合、S-TSIDメタデータのRS要素のLS要素のsrcFlow要素のContentInfo要素に、quotaDomain属性を定義することで、対象のLCTセッションが属するキャッシュクォータドメインのクォータドメイン識別子を指定することが可能となる。
キャッシュクォータドメインのクォータドメイン識別子が、ASTメタデータの拡張により指定される場合、ASTメタデータのApplication要素のapplicationSpecificDescriptor要素のatsc:atscDescriptor要素に、quotaDomain属性を定義することで、対象のアプリケーションが属するキャッシュクォータドメインのクォータドメイン識別子を指定することが可能となる。
図9は、広告挿入の流れを説明する図である。
次に、図13及び図14を参照して、XML形式のMPDメタデータの記述例について説明する。
図15は、XML形式のSLTメタデータのフォーマットの例を示す図である。なお、図15において、要素と属性のうち、属性には「@」が付されている。また、インデントされた要素と属性は、その上位の要素に対して指定されたものとなる。これらの関係は、後述する他のシグナリングのフォーマットでも同様とされる。
図16は、XML形式のUSBDメタデータのフォーマットの例を示す図である。
図17は、S-TSIDメタデータのフォーマットの例を示す図である。
図18は、図17のS-TSIDメタデータに含まれるSrcFlow要素のフォーマットの例を示す図である。
図19乃至図21は、ASTメタデータのフォーマットの例を示す図である。
図22は、図1のAd/DASHサーバ10の構成例を示す図である。
図23は、図1の放送サーバ20の構成例を示す図である。
図24は、図1の通信サーバ30の構成例を示す図である。
図25は、図1のクライアント装置40の構成例を示す図である。
まず、図26のフローチャートを参照して、送信側のAd/DASHサーバ10、放送サーバ20、及び、通信サーバ30により実行される処理の流れを説明する。
次に、図27及び図28のフローチャートを参照して、受信側のクライアント装置40により実行される処理の流れを説明する。
Promise<void> fetchPeriod(xmlElement);
}
Promise<void> fetchFile(url);
}
Promise<void> deleteFile(url);
}
コンテンツを受信する受信部と、
前記コンテンツとともに伝送される制御情報であって、前記コンテンツのリソースが、複数のサービスで共有されるリソースであるかどうかを示すリソース共有情報を含む前記制御情報に基づいて、前記コンテンツのリソースが、複数のサービスで共有されるように、前記リソースの記憶装置への記憶を制御する制御部と
を備える受信装置。
(2)
前記制御部は、前記制御情報に含まれる前記リソース共有情報が、複数のサービスで共有されるリソースであることを示している場合、共有されるリソースである共有リソースを、他のリソースと区別して記憶させる
(1)に記載の受信装置。
(3)
前記コンテンツ及び前記制御情報は、放送波により伝送され、
前記サービスは、デジタル放送のサービスであり、
前記制御情報は、前記サービスを提供するためのシグナリングである
(1)又は(2)に記載の受信装置。
(4)
前記シグナリングは、複数のサービスの属性を指定可能な第1のシグナリングであり、
前記第1のシグナリングは、サービス単位で指定された前記リソース共有情報を含む
(3)に記載の受信装置。
(5)
前記シグナリングは、サービスごとの属性を指定可能な第2のシグナリングであり、
前記第2のシグナリングは、対象のサービス内の所定の単位で指定された前記リソース共有情報を含む
(3)に記載の受信装置。
(6)
前記リソース共有情報は、サービス単位、セッション単位、又はアプリケーション単位で指定される
(5)に記載の受信装置。
(7)
前記コンテンツのリソースは、所定の形式のファイルであり、
前記制御部は、前記コンテンツとともに伝送されるアプリケーションの動作に応じて、共有リソースのファイルを、他のリソースのファイルが記憶される第1の記憶領域とは異なる第2の記憶領域に記憶させる
(2)乃至(6)のいずれかに記載の受信装置。
(8)
前記制御部は、前記アプリケーションの動作に応じて、前記第2の記憶領域に記憶された共有リソースのファイルを消去する
(7)に記載の受信装置。
(9)
前記放送波は、IP(Internet Protocol)伝送方式に対応した放送波であり、
前記コンテンツのリソースのファイルのデータは、UDP(User Datagram Protocol)パケットを含むIPパケットに格納されて伝送される
(3)乃至(8)のいずれかに記載の受信装置。
(10)
前記コンテンツは、広告のコンテンツを含み、
前記リソース共有情報は、前記広告のコンテンツのリソースを共有する複数のサービスが属するグループを識別するための識別情報である
(1)乃至(9)のいずれかに記載の受信装置。
(11)
受信装置のデータ処理方法において、
前記受信装置が、
コンテンツを受信し、
前記コンテンツとともに伝送される制御情報であって、前記コンテンツのリソースが、複数のサービスで共有されるリソースであるかどうかを示すリソース共有情報を含む前記制御情報に基づいて、前記コンテンツのリソースが、複数のサービスで共有されるように、前記リソースの記憶装置への記憶を制御する
ステップを含むデータ処理方法。
(12)
コンテンツのリソースが、複数のサービスで共有されるリソースであるかどうかを示すリソース共有情報を含む制御情報を生成する生成部と、
前記コンテンツとともに、前記制御情報を送信する送信部と
を備える送信装置。
(13)
前記コンテンツ及び前記制御情報は、放送波により伝送され、
前記サービスは、デジタル放送のサービスであり、
前記制御情報は、前記サービスを提供するためのシグナリングである
(12)に記載の送信装置。
(14)
前記シグナリングは、複数のサービスの属性を指定可能な第1のシグナリングであり、
前記第1のシグナリングは、サービス単位で指定された前記リソース共有情報を含む
(13)に記載の送信装置。
(15)
前記シグナリングは、サービスごとの属性を指定可能な第2のシグナリングであり、
前記第2のシグナリングは、対象のサービス内の所定の単位で指定された前記リソース共有情報を含む
(13)に記載の送信装置。
(16)
前記リソース共有情報は、サービス単位、セッション単位、又はアプリケーション単位で指定される
(15)に記載の送信装置。
(17)
前記コンテンツのリソースは、所定の形式のファイルである
(12)乃至(16)のいずれかに記載の送信装置。
(18)
前記放送波は、IP伝送方式に対応した放送波であり、
前記コンテンツのリソースのファイルのデータは、UDPパケットを含むIPパケットに格納されて伝送される
(13)乃至(17)のいずれかに記載の送信装置。
(19)
前記コンテンツは、広告のコンテンツを含み、
前記リソース共有情報は、前記広告のコンテンツのリソースを共有する複数のサービスが属するグループを識別するための識別情報である
(12)乃至(18)のいずれかに記載の送信装置。
(20)
送信装置のデータ処理方法において、
前記送信装置が、
コンテンツのリソースが、複数のサービスで共有されるリソースであるかどうかを示すリソース共有情報を含む制御情報を生成し、
前記コンテンツとともに、前記制御情報を送信する
ステップを含むデータ処理方法。
Claims (20)
- コンテンツを受信する受信部と、
前記コンテンツとともに伝送される制御情報であって、前記コンテンツのリソースが、複数のサービスで共有されるリソースであるかどうかを示すリソース共有情報を含む前記制御情報に基づいて、前記コンテンツのリソースが、複数のサービスで共有されるように、前記リソースの記憶装置への記憶を制御する制御部と
を備える受信装置。 - 前記制御部は、前記制御情報に含まれる前記リソース共有情報が、複数のサービスで共有されるリソースであることを示している場合、共有されるリソースである共有リソースを、他のリソースと区別して記憶させる
請求項1に記載の受信装置。 - 前記コンテンツ及び前記制御情報は、放送波により伝送され、
前記サービスは、デジタル放送のサービスであり、
前記制御情報は、前記サービスを提供するためのシグナリングである
請求項2に記載の受信装置。 - 前記シグナリングは、複数のサービスの属性を指定可能な第1のシグナリングであり、
前記第1のシグナリングは、サービス単位で指定された前記リソース共有情報を含む
請求項3に記載の受信装置。 - 前記シグナリングは、サービスごとの属性を指定可能な第2のシグナリングであり、
前記第2のシグナリングは、対象のサービス内の所定の単位で指定された前記リソース共有情報を含む
請求項3に記載の受信装置。 - 前記リソース共有情報は、サービス単位、セッション単位、又はアプリケーション単位で指定される
請求項5に記載の受信装置。 - 前記コンテンツのリソースは、所定の形式のファイルであり、
前記制御部は、前記コンテンツとともに伝送されるアプリケーションの動作に応じて、共有リソースのファイルを、他のリソースのファイルが記憶される第1の記憶領域とは異なる第2の記憶領域に記憶させる
請求項3に記載の受信装置。 - 前記制御部は、前記アプリケーションの動作に応じて、前記第2の記憶領域に記憶された共有リソースのファイルを消去する
請求項7に記載の受信装置。 - 前記放送波は、IP(Internet Protocol)伝送方式に対応した放送波であり、
前記コンテンツのリソースのファイルのデータは、UDP(User Datagram Protocol)パケットを含むIPパケットに格納されて伝送される
請求項3に記載の受信装置。 - 前記コンテンツは、広告のコンテンツを含み、
前記リソース共有情報は、前記広告のコンテンツのリソースを共有する複数のサービスが属するグループを識別するための識別情報である
請求項1に記載の受信装置。 - 受信装置のデータ処理方法において、
前記受信装置が、
コンテンツを受信し、
前記コンテンツとともに伝送される制御情報であって、前記コンテンツのリソースが、複数のサービスで共有されるリソースであるかどうかを示すリソース共有情報を含む前記制御情報に基づいて、前記コンテンツのリソースが、複数のサービスで共有されるように、前記リソースの記憶装置への記憶を制御する
ステップを含むデータ処理方法。 - コンテンツのリソースが、複数のサービスで共有されるリソースであるかどうかを示すリソース共有情報を含む制御情報を生成する生成部と、
前記コンテンツとともに、前記制御情報を送信する送信部と
を備える送信装置。 - 前記コンテンツ及び前記制御情報は、放送波により伝送され、
前記サービスは、デジタル放送のサービスであり、
前記制御情報は、前記サービスを提供するためのシグナリングである
請求項12に記載の送信装置。 - 前記シグナリングは、複数のサービスの属性を指定可能な第1のシグナリングであり、
前記第1のシグナリングは、サービス単位で指定された前記リソース共有情報を含む
請求項13に記載の送信装置。 - 前記シグナリングは、サービスごとの属性を指定可能な第2のシグナリングであり、
前記第2のシグナリングは、対象のサービス内の所定の単位で指定された前記リソース共有情報を含む
請求項13に記載の送信装置。 - 前記リソース共有情報は、サービス単位、セッション単位、又はアプリケーション単位で指定される
請求項15に記載の送信装置。 - 前記コンテンツのリソースは、所定の形式のファイルである
請求項12に記載の送信装置。 - 前記放送波は、IP伝送方式に対応した放送波であり、
前記コンテンツのリソースのファイルのデータは、UDPパケットを含むIPパケットに格納されて伝送される
請求項13に記載の送信装置。 - 前記コンテンツは、広告のコンテンツを含み、
前記リソース共有情報は、前記広告のコンテンツのリソースを共有する複数のサービスが属するグループを識別するための識別情報である
請求項12に記載の送信装置。 - 送信装置のデータ処理方法において、
前記送信装置が、
コンテンツのリソースが、複数のサービスで共有されるリソースであるかどうかを示すリソース共有情報を含む制御情報を生成し、
前記コンテンツとともに、前記制御情報を送信する
ステップを含むデータ処理方法。
Priority Applications (11)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020187013711A KR102637023B1 (ko) | 2015-11-25 | 2016-11-11 | 수신 장치, 송신 장치, 및 데이터 처리 방법 |
US15/766,850 US10986397B2 (en) | 2015-11-25 | 2016-11-11 | Reception apparatus, transmission apparatus, and data processing method |
KR1020247004799A KR20240025698A (ko) | 2015-11-25 | 2016-11-11 | 수신 장치, 송신 장치, 및 데이터 처리 방법 |
AU2016360190A AU2016360190A1 (en) | 2015-11-25 | 2016-11-11 | Reception device, transmission device and data processing method |
JP2017552356A JPWO2017090457A1 (ja) | 2015-11-25 | 2016-11-11 | 受信装置、送信装置、及び、データ処理方法 |
CA3003683A CA3003683A1 (en) | 2015-11-25 | 2016-11-11 | Reception apparatus, transmission apparatus, and data processing method |
MX2018006174A MX2018006174A (es) | 2015-11-25 | 2016-11-11 | Aparato de recepcion, aparato de transmision y metodo de procesamiento de datos. |
CN201680067759.9A CN108293148B (zh) | 2015-11-25 | 2016-11-11 | 接收装置、发送装置以及数据处理方法 |
EP16868405.8A EP3383054B1 (en) | 2015-11-25 | 2016-11-11 | Reception device, transmission device and data processing method |
US17/189,827 US11575961B2 (en) | 2015-11-25 | 2021-03-02 | Reception apparatus, transmission apparatus, and data processing method |
AU2021202436A AU2021202436B2 (en) | 2015-11-25 | 2021-04-21 | Reception appartus, transmission apparatus, and data processing method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2015229769 | 2015-11-25 | ||
JP2015-229769 | 2015-11-25 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/766,850 A-371-Of-International US10986397B2 (en) | 2015-11-25 | 2016-11-11 | Reception apparatus, transmission apparatus, and data processing method |
US17/189,827 Continuation US11575961B2 (en) | 2015-11-25 | 2021-03-02 | Reception apparatus, transmission apparatus, and data processing method |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017090457A1 true WO2017090457A1 (ja) | 2017-06-01 |
Family
ID=58763199
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2016/083467 WO2017090457A1 (ja) | 2015-11-25 | 2016-11-11 | 受信装置、送信装置、及び、データ処理方法 |
Country Status (9)
Country | Link |
---|---|
US (2) | US10986397B2 (ja) |
EP (1) | EP3383054B1 (ja) |
JP (1) | JPWO2017090457A1 (ja) |
KR (2) | KR102637023B1 (ja) |
CN (1) | CN108293148B (ja) |
AU (2) | AU2016360190A1 (ja) |
CA (1) | CA3003683A1 (ja) |
MX (1) | MX2018006174A (ja) |
WO (1) | WO2017090457A1 (ja) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2021108441A (ja) * | 2019-12-27 | 2021-07-29 | 株式会社インフォシティ | 放送サービス通信ネットワーク配信装置および方法 |
US11368730B2 (en) | 2019-08-27 | 2022-06-21 | Electronics And Telecommunications Research Institute | Apparatus and method for transmitting broadcast content based on ATSC 3.0, and apparatus and method for receiving broadcast content based ATSC 3.0 |
JP2023008952A (ja) * | 2021-06-30 | 2023-01-19 | レモン インコーポレイテッド | 事前選択の目的のシグナリング |
US11985333B2 (en) | 2021-06-30 | 2024-05-14 | Lemon Inc. | Indicating which video data units represent a target picture-in-picture region |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
AU2016360190A1 (en) * | 2015-11-25 | 2018-04-19 | Sony Corporation | Reception device, transmission device and data processing method |
US11044294B2 (en) | 2018-01-03 | 2021-06-22 | Sony Group Corporation | ATSC 3.0 playback using MPEG media transport protocol (MMTP) |
US11606528B2 (en) | 2018-01-03 | 2023-03-14 | Saturn Licensing Llc | Advanced television systems committee (ATSC) 3.0 latency-free display of content attribute |
US11109115B2 (en) * | 2018-11-06 | 2021-08-31 | At&T Intellectual Property I, L.P. | Inserting advertisements in ATSC content |
EP3884676A1 (en) * | 2018-11-22 | 2021-09-29 | Telefonaktiebolaget Lm Ericsson (Publ) | Media descriptor file comprising a reference to other streaming media content |
US10743069B2 (en) | 2018-12-10 | 2020-08-11 | Sony Corporation | Delivery of information related to digital rights management (DRM) in a terrestrial broadcast system |
US11706465B2 (en) | 2019-01-15 | 2023-07-18 | Sony Group Corporation | ATSC 3.0 advertising notification using event streams |
US11831702B2 (en) | 2019-10-04 | 2023-11-28 | Eexpway | Method for broadcasting DASH/HLS hybrid multimedia streams |
US11960507B2 (en) * | 2020-01-17 | 2024-04-16 | International Business Machines Corporation | Hierarchical data |
DE202020104113U1 (de) * | 2020-07-16 | 2021-10-20 | WAGO Verwaltungsgesellschaft mit beschränkter Haftung | Elektronikeinrichtung für eine industrielle elektrische Anlage sowie Kommunikationsmodul |
US11451872B1 (en) * | 2021-05-27 | 2022-09-20 | Sling TV L.L.C. | System, device, and processes for intelligent start playback of program content |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001197381A (ja) * | 1999-11-05 | 2001-07-19 | Dentsu Inc | 蓄積情報の放送方法及びそのためのテレビジョン装置 |
JP2002101056A (ja) * | 2000-07-17 | 2002-04-05 | Matsushita Electric Ind Co Ltd | 放送装置、放送方法、プログラム記録媒体、プログラム |
JP2003032653A (ja) * | 2001-07-16 | 2003-01-31 | Funai Electric Co Ltd | 双方向テレビシステムおよび双方向テレビ受信装置 |
JP2006099698A (ja) * | 2004-09-30 | 2006-04-13 | Toshiba Corp | 配信情報再生装置、プログラム及び方法 |
JP2008017207A (ja) * | 2006-07-06 | 2008-01-24 | Kddi Corp | 映像信号受信装置 |
JP2014057227A (ja) | 2012-09-13 | 2014-03-27 | Sony Corp | コンテンツ供給装置、コンテンツ供給方法、プログラム、およびコンテンツ供給システム |
Family Cites Families (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8300534B2 (en) * | 2000-05-24 | 2012-10-30 | Alcatel Lucent | Programmable packet processor with flow resolution logic |
US7096482B2 (en) | 2000-07-17 | 2006-08-22 | Matsushita Electric Industrial Co., Ltd. | Broadcasting apparatus, broadcasting method, program recording medium, and program |
US7073178B2 (en) * | 2002-01-18 | 2006-07-04 | Mobitv, Inc. | Method and system of performing transactions using shared resources and different applications |
US7721306B2 (en) | 2006-02-15 | 2010-05-18 | Sony Corporation | Bandwidth sharing |
US20080098420A1 (en) * | 2006-10-19 | 2008-04-24 | Roundbox, Inc. | Distribution and display of advertising for devices in a network |
JP4973246B2 (ja) * | 2007-03-09 | 2012-07-11 | 日本電気株式会社 | アクセス権管理システム、サーバ及びアクセス権管理プログラム |
US9027100B2 (en) | 2010-01-05 | 2015-05-05 | Yahoo! Inc. | Client-side ad caching for lower ad serving latency |
US8307134B2 (en) * | 2010-01-15 | 2012-11-06 | Apple Inc. | Multiple communication interfaces on a portable storage device |
US8832750B2 (en) * | 2012-05-10 | 2014-09-09 | Time Warner Cable Enterprises Llc | Media synchronization within home network using set-top box as gateway |
KR20140029733A (ko) * | 2012-08-29 | 2014-03-11 | 주식회사 팬택 | 어플리케이션 관리 기능을 갖는 디바이스 및 이를 위한 어플리케이션 관리 방법 |
US20140229580A1 (en) * | 2013-02-12 | 2014-08-14 | Sony Corporation | Information processing device, information processing method, and information processing system |
JP5865551B2 (ja) * | 2013-04-16 | 2016-02-17 | パナソニック インテレクチュアル プロパティ コーポレーション オブアメリカPanasonic Intellectual Property Corporation of America | コンテンツ表示方法、プログラム及びコンテンツ表示システム |
EP3062521B1 (en) * | 2013-10-25 | 2018-07-04 | Sony Corporation | Reception apparatus, reception method, transmission apparatus, and transmission method for services transmitted on a broadcast wave using ip packets |
EP2922303A1 (en) * | 2014-03-04 | 2015-09-23 | LG Electronics Inc. | Display device for managing a plurality of time source data and method for controlling the same |
US9386027B2 (en) * | 2014-08-11 | 2016-07-05 | Indiana University Research & Technology Corporation | Detection of pileup vulnerabilities in mobile operating systems |
AU2016360190A1 (en) * | 2015-11-25 | 2018-04-19 | Sony Corporation | Reception device, transmission device and data processing method |
-
2016
- 2016-11-11 AU AU2016360190A patent/AU2016360190A1/en not_active Abandoned
- 2016-11-11 EP EP16868405.8A patent/EP3383054B1/en active Active
- 2016-11-11 CN CN201680067759.9A patent/CN108293148B/zh active Active
- 2016-11-11 JP JP2017552356A patent/JPWO2017090457A1/ja active Pending
- 2016-11-11 MX MX2018006174A patent/MX2018006174A/es unknown
- 2016-11-11 WO PCT/JP2016/083467 patent/WO2017090457A1/ja active Application Filing
- 2016-11-11 KR KR1020187013711A patent/KR102637023B1/ko active IP Right Grant
- 2016-11-11 CA CA3003683A patent/CA3003683A1/en active Pending
- 2016-11-11 US US15/766,850 patent/US10986397B2/en active Active
- 2016-11-11 KR KR1020247004799A patent/KR20240025698A/ko active Application Filing
-
2021
- 2021-03-02 US US17/189,827 patent/US11575961B2/en active Active
- 2021-04-21 AU AU2021202436A patent/AU2021202436B2/en active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001197381A (ja) * | 1999-11-05 | 2001-07-19 | Dentsu Inc | 蓄積情報の放送方法及びそのためのテレビジョン装置 |
JP2002101056A (ja) * | 2000-07-17 | 2002-04-05 | Matsushita Electric Ind Co Ltd | 放送装置、放送方法、プログラム記録媒体、プログラム |
JP2003032653A (ja) * | 2001-07-16 | 2003-01-31 | Funai Electric Co Ltd | 双方向テレビシステムおよび双方向テレビ受信装置 |
JP2006099698A (ja) * | 2004-09-30 | 2006-04-13 | Toshiba Corp | 配信情報再生装置、プログラム及び方法 |
JP2008017207A (ja) * | 2006-07-06 | 2008-01-24 | Kddi Corp | 映像信号受信装置 |
JP2014057227A (ja) | 2012-09-13 | 2014-03-27 | Sony Corp | コンテンツ供給装置、コンテンツ供給方法、プログラム、およびコンテンツ供給システム |
Non-Patent Citations (1)
Title |
---|
See also references of EP3383054A4 |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11368730B2 (en) | 2019-08-27 | 2022-06-21 | Electronics And Telecommunications Research Institute | Apparatus and method for transmitting broadcast content based on ATSC 3.0, and apparatus and method for receiving broadcast content based ATSC 3.0 |
JP2021108441A (ja) * | 2019-12-27 | 2021-07-29 | 株式会社インフォシティ | 放送サービス通信ネットワーク配信装置および方法 |
JP2021108440A (ja) * | 2019-12-27 | 2021-07-29 | 株式会社インフォシティ | 放送サービス通信ネットワーク配信装置および方法 |
JP7058039B2 (ja) | 2019-12-27 | 2022-04-21 | 株式会社インフォシティ | 放送サービス通信ネットワーク配信装置および方法 |
JP2022095777A (ja) * | 2019-12-27 | 2022-06-28 | 株式会社インフォシティ | 放送サービス通信ネットワーク配信装置および方法 |
JP7125692B2 (ja) | 2019-12-27 | 2022-08-25 | 株式会社インフォシティ | 放送サービス通信ネットワーク配信装置および方法 |
JP7477116B2 (ja) | 2019-12-27 | 2024-05-01 | 株式会社インフォシティ | 放送サービス通信ネットワーク配信装置および方法 |
JP2023008952A (ja) * | 2021-06-30 | 2023-01-19 | レモン インコーポレイテッド | 事前選択の目的のシグナリング |
JP7460693B2 (ja) | 2021-06-30 | 2024-04-02 | レモン インコーポレイテッド | 事前選択の目的のシグナリング |
US11985333B2 (en) | 2021-06-30 | 2024-05-14 | Lemon Inc. | Indicating which video data units represent a target picture-in-picture region |
Also Published As
Publication number | Publication date |
---|---|
US20210266629A1 (en) | 2021-08-26 |
AU2021202436A1 (en) | 2021-05-13 |
CN108293148A (zh) | 2018-07-17 |
KR102637023B1 (ko) | 2024-02-16 |
US20180288468A1 (en) | 2018-10-04 |
CN108293148B (zh) | 2022-07-26 |
US10986397B2 (en) | 2021-04-20 |
KR20180088383A (ko) | 2018-08-03 |
EP3383054A1 (en) | 2018-10-03 |
EP3383054A4 (en) | 2019-01-09 |
KR20240025698A (ko) | 2024-02-27 |
AU2021202436B2 (en) | 2023-03-16 |
US11575961B2 (en) | 2023-02-07 |
JPWO2017090457A1 (ja) | 2018-09-13 |
CA3003683A1 (en) | 2017-06-01 |
AU2016360190A1 (en) | 2018-04-19 |
MX2018006174A (es) | 2018-08-01 |
EP3383054B1 (en) | 2021-07-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
AU2021202436B2 (en) | Reception appartus, transmission apparatus, and data processing method | |
CN103081507B (zh) | 集成并处理到视频流中相关视频内容的嵌入式链接以提供广告信息 | |
KR102443060B1 (ko) | 정보 처리 장치 및 정보 처리 방법 | |
US10469919B2 (en) | Broadcast signal transmission apparatus, broadcast signal reception apparatus, broadcast signal transmission method, and broadcast signal reception method | |
WO2018034172A1 (ja) | 情報処理装置、クライアント装置、及び、データ処理方法 | |
JPWO2016174960A1 (ja) | 受信装置、送信装置、およびデータ処理方法 | |
US11336957B2 (en) | Reception apparatus, transmission apparatus, and data processing method | |
WO2016067987A1 (ja) | 受信装置、送信装置、およびデータ処理方法 | |
KR102491466B1 (ko) | 수신 장치, 송신 장치, 및 데이터 처리 방법 | |
KR102600762B1 (ko) | Atsc 3.0 기반의 방송 콘텐츠 전송 장치 및 방법과, 방송 콘텐츠 수신 장치 및 방법 | |
WO2018012315A1 (ja) | 情報処理装置、及び、情報処理方法 | |
WO2017212932A1 (ja) | 受信装置、送信装置、及び、データ処理方法 | |
JP2012257231A (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: 16868405 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15766850 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 2017552356 Country of ref document: JP Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2016360190 Country of ref document: AU Date of ref document: 20161111 Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 3003683 Country of ref document: CA |
|
ENP | Entry into the national phase |
Ref document number: 20187013711 Country of ref document: KR Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: MX/A/2018/006174 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: 2016868405 Country of ref document: EP |