WO2015029767A1 - プロキシサーバ装置、情報処理方法、プログラム、端末装置、およびコンテンツ供給システム - Google Patents
プロキシサーバ装置、情報処理方法、プログラム、端末装置、およびコンテンツ供給システム Download PDFInfo
- Publication number
- WO2015029767A1 WO2015029767A1 PCT/JP2014/071261 JP2014071261W WO2015029767A1 WO 2015029767 A1 WO2015029767 A1 WO 2015029767A1 JP 2014071261 W JP2014071261 W JP 2014071261W WO 2015029767 A1 WO2015029767 A1 WO 2015029767A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- content
- metafile
- stream
- unit
- terminal device
- Prior art date
Links
- 230000010365 information processing Effects 0.000 title claims abstract description 7
- 238000003672 processing method Methods 0.000 title claims abstract description 7
- 238000004458 analytical method Methods 0.000 claims abstract description 79
- 238000012544 monitoring process Methods 0.000 claims abstract description 30
- 230000003044 adaptive effect Effects 0.000 claims abstract description 19
- 230000004044 response Effects 0.000 claims abstract description 18
- 238000005516 engineering process Methods 0.000 claims abstract description 12
- 238000000034 method Methods 0.000 claims description 28
- 230000006870 function Effects 0.000 claims description 4
- 238000012217 deletion Methods 0.000 claims description 3
- 230000037430 deletion Effects 0.000 claims description 3
- 238000005457 optimization Methods 0.000 description 29
- 238000012545 processing Methods 0.000 description 27
- 230000008569 process Effects 0.000 description 22
- 230000006854 communication Effects 0.000 description 7
- 238000004891 communication Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 5
- 230000007175 bidirectional communication Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005070 sampling Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24568—Data stream processing; Continuous queries
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
- H04L65/612—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
-
- 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/21—Server components or server architectures
- H04N21/218—Source of audio or video content, e.g. local disk arrays
- H04N21/2183—Cache memory
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/239—Interfacing the upstream path of the transmission network, e.g. prioritizing client content requests
-
- 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/6156—Network physical structure; Signal processing specially adapted to the upstream path of the transmission network
- H04N21/6175—Network physical structure; Signal processing specially adapted to the upstream 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/647—Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless
- H04N21/64723—Monitoring of network processes or resources, e.g. monitoring of network load
- H04N21/64738—Monitoring network characteristics, e.g. bandwidth, congestion level
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/85—Assembly of content; Generation of multimedia applications
- H04N21/854—Content authoring
- H04N21/8543—Content authoring using a description language, e.g. Multimedia and Hypermedia information coding Expert Group [MHEG], eXtensible Markup Language [XML]
Definitions
- the present disclosure relates to a proxy server device, an information processing method, a program, a terminal device, and a content supply system, and in particular, a proxy server device, an information processing method, a program, and a terminal device capable of efficiently executing streaming distribution of content. , And a content supply system.
- MPEG-DASH Moving Picture Experts Group-Dynamic Adaptive Streaming over HTTP, hereinafter DASH, which uses HTTP unicast delivery similar to browsing of a Web site or the like as an internationally standardized video delivery protocol that can be used for video delivery via the Internet Is known (see, for example, Non-Patent Document 1).
- Adaptive streaming technology is realized in DASH. That is, the content supply side of DASH prepares a plurality of streams whose image quality, angle of view size, etc. are changed according to the communication environment of the distribution path and the capability and state of the reception side as content of the same content. It is done.
- the receiving side is configured to select, receive, and reproduce an optimal stream that can be received by itself and that is suitable for its decoding capability, among a plurality of streams prepared by the supplying side.
- MPD Media Presentation Description
- the MPD describes the address (url information) of the web server that is the supply source of the chunked content segment stream (media data such as Audio / Video / Subtitle).
- the receiving side transmits an HTTP request to the web server as a content supply source based on the url information, and in response to the HTTP request, the web server receives and reproduces a segment stream to be unicast-distributed.
- FIG. 1 shows an example of the configuration of a content supply system for distributing segment streams of content based on DASH.
- the content supply system 10 includes a plurality of content supply devices 20-1 to 20-K on the side of supplying content, and a plurality of DASH clients 30-1 to 30-N on the side of receiving content.
- the content supply devices 20-1 to 20-K will be referred to simply as the content supply device 20 if it is not necessary to distinguish them individually. The same applies to the DASH clients 30-1 to 30-N.
- the content supply device 20 and the DASH client 30 are connected to the Internet 11, respectively.
- a CDN (Contents Delivery Network) 12 is constructed.
- the content supply device 20 distributes a plurality of segment streams having the same content and different bit rates, and includes a channel streamer 21, a DASH segment streamer 22, and a DASH MPD server 23.
- the channel streamer 21 manages source data of content to be distributed to the DASH client 30, generates a plurality of streaming data having different bit rates from the source data of the content, and outputs the streaming data to the DASH segment streamer 22.
- the DASH segment streamer 22 temporally divides (streams) each streaming data into segments to generate a segment stream. Also, the DASH segment streamer 22 holds the segment stream as a file, and as a WEB server, responds to a request (HTTP request) from the DASH client 30 to transmit the segment stream file via the CDN 12 to the DASH client 30 of the request source. Distribute HTTP Unicast to. Furthermore, the DASH segment streamer 22 notifies the DASH MPD server 23 of the address of the source of the file of the segment stream.
- the DASH MPD server 23 generates an MPD in which an address representing the source of the segment stream file, etc., necessary for the DASH client 30 to acquire the segment stream file is described. Further, the DASH MPD server 23, as a WEB server, responds to a request (HTTP request) from the DASH client 30 and distributes the generated MPD to the DASH client 30 of the request source via the CDN 12 via HTTP unicast.
- HTTP request HTTP request
- the DASH client 30 requests the MPD from the DASH MPD server 23 and receives the HTTP unicast distributed MPD accordingly. Furthermore, based on the received MPD, the DASH client 30 requests the DASH segment streamer 22 for the segment stream file, and receives and reproduces the HTTP unicast segment stream file accordingly.
- the CDN 12 is provided with a proxy server 13 for caching MPDs and segment stream files that are HTTP-unicast-distributed via the CND 12.
- the proxy server 13 performs HTTP unicast delivery of a file of MPD or segment stream caching to the DASH client 30 that has sent an HTTP request, instead of the DASH MPD server 23 or DASH segment streamer 22 as a WEB server. Do.
- the response performance to the request from the DASH client 30 can be enhanced.
- the proxy server 13 can deliver the MPD and segment stream instead of the DASH MPD server 23 or the DASH segment streamer 22 as a WEB server only when it has already been cached. That is, although other DASH clients 30 request and those delivered accordingly are cached and can be responded quickly, if uncached requests are made, they can not respond.
- the present disclosure has been made in view of such circumstances, and is intended to improve the response performance to the request from the receiving side by optimizing the caching by the proxy server.
- the proxy server device receives the stream of the content transmitted from the terminal device to the content supply device distributing the content via the network according to the adaptive streaming technology.
- Monitoring unit that monitors acquisition request of metafile in which necessary information is described
- analysis unit that analyzes acquisition request of the monitored metafile
- database that stores analysis results of the analysis unit And a unit.
- the monitoring unit may further monitor a request for acquiring the stream of the content, which the terminal device has transmitted to the content supply apparatus based on the metafile, and the analyzing unit is further monitored. It is possible to analyze the acquisition request of the stream.
- the proxy server device further includes a caching unit configured to cache at least one of the metafile or the stream distributed via the network in accordance with the priority based on the stored analysis result. It can be equipped.
- the caching unit can register or deregister the caching policy in response to a request from the terminal device.
- An information processing method is an information processing method for a proxy server device, comprising: a terminal for a content supply device that distributes content via a network according to an adaptive streaming technique by the proxy server device A monitoring step of monitoring an acquisition request of a metafile transmitted by the device, wherein the terminal device describes the information necessary for receiving the stream of content, and analyzing the acquisition request of the metafile monitored And an analysis step of accumulating the analysis result.
- the program according to the first aspect of the present disclosure is a computer that, according to adaptive streaming technology, a terminal device transmits a content supply device that distributes content via a network according to adaptive streaming technology, and the terminal device transmits the content stream
- a monitoring unit monitoring a metafile acquisition request describing information necessary for reception, an analysis unit analyzing the acquisition request of the monitored metafile, and an analysis result of the analysis unit Function as a database unit
- the terminal device needs to receive the stream of content transmitted by the terminal device to a content supply device that distributes content via a network according to adaptive streaming technology.
- the acquisition request of the metafile in which the relevant information is described is monitored, the acquisition request of the monitored metafile is analyzed, and the analysis result is accumulated.
- a terminal device is information required for the terminal device to receive the stream of content with respect to a content supply device that delivers content via a network according to adaptive streaming technology.
- Sends the metafile acquisition request described therein receives the metafile distributed from the content supply apparatus in response to the metafile acquisition request, and transmits the metafile to the content supply apparatus based on the metafile
- a reception / reproduction unit that transmits an acquisition request for the content stream and receives and reproduces the stream distributed from the content supply device according to the acquisition request for the stream; and a proxy that substitutes for the operation of the content supply device The metafile or the stream for the server device
- a registration unit requesting registration of at least one caching policy, wherein the proxy server device transmits the terminal device to the content supply device distributing the content via the network according to the adaptive streaming technology.
- a monitoring unit that monitors an acquisition request for a metafile in which information necessary for the terminal device to receive the stream of the content is described; an analysis unit that analyzes the acquisition request for the metafile that is monitored; And a database unit for accumulating analysis results of the analysis unit.
- the registration unit may further request registration and deletion of the caching policy from a proxy server device acting as a proxy for the operation of the content supply device.
- the terminal device which is the second aspect of the present disclosure, requests the portal server for a script for performing setting for connecting to a proxy server optimal for itself, and executes the script provided from the portal server. It can further comprise a script request unit for setting.
- registration of a caching policy of at least one of a metafile and a stream is required of a proxy server device acting on the content providing device.
- a content supply system includes a content supply apparatus that distributes content via a network, a terminal apparatus that receives and reproduces a stream of the content, and the content supply apparatus according to adaptive streaming technology.
- a content supply system including a proxy server device provided between the terminal device and the terminal device, the proxy server device transmitting the terminal device to the content supply device, the terminal device including the content
- a monitoring unit monitoring a metafile acquisition request describing information necessary for receiving a stream; an analysis unit analyzing the acquisition request of the monitored metafile; and an analysis result of the analysis unit And a database unit for storing data; Transmitting the acquisition request for the metafile to the content supply apparatus, receiving the metafile distributed from the content supply apparatus in response to the acquisition request for the metafile, and based on the metafile
- a reception / playback unit that transmits the acquisition request for the stream of content to the content supply apparatus, and receives and reproduces the stream distributed from the content supply apparatus according to the acquisition request for the stream; and the content supply apparatus And a registration unit that requests registration of
- the terminal device transmits the stream of the content transmitted by the terminal device to the content supply device that distributes the content via the network by the proxy server device according to the adaptive streaming technology.
- a metafile acquisition request describing information necessary for reception is monitored, the acquisition request of the monitored metafile is analyzed, and the analysis result is accumulated. Further, the terminal device requests the proxy server device acting on the content providing device to register the caching policy of at least one of the meta file and the stream.
- caching can be optimized, and response performance to requests from the receiving side can be improved.
- caching by a proxy server can be optimized.
- the stream can be distributed promptly to the receiving side.
- FIG. 6 shows a configuration example of a content supply system according to an embodiment of the present disclosure.
- the content supply system 50 includes a plurality of content supply devices 60-1 to 60-K, a CDN 72 built on a network 71, and a large number of terminal devices 80-1 to 80-N.
- the content supply devices 60-1 to 60-K and the terminal devices 80-1 to 80-N are connected to the network 71.
- the content supply devices 60-1 to 60-K will be referred to simply as the content supply device 60 if it is not necessary to distinguish them individually.
- the content supply device 60 includes a channel streamer 61, a DASH segmenter 62, a FLUTE streamer 63, an MPD generator 64, a WEB server 65, and a multicast server 66.
- the channel streamers 61 to the multicast servers 66 included in the content supply apparatus 60 may be integrated and disposed, or may be distributed and disposed via the Internet or the like.
- the channel streamer 61 manages source data of content to be distributed to the terminal device 80, and generates a plurality of streaming data having different bit rates from the source data of the same content. Further, the channel streamer 61 outputs the generated streaming data to the DASH segmenter 62.
- the DASH segmenter 62 divides streaming data into periods in time, and further divides the data into segments, thereby generating a segment stream such as fragmented MP 4 and outputs it to the WEB server 65 and the FLUTE streamer 63. Further, the DASH segmenter 62 notifies the MPD generator 64 of metadata including address information of the web server 65 as a supply source of the generated segment stream file.
- the MPD generator 64 generates an MPD necessary for the terminal device 80 to receive the segment stream, and outputs the MPD to the FLUTE streamer 63 and the WEB server 65.
- the FLUTE streamer 63 generates a FLUTE stream by storing the segment stream input from the DASH segmenter 62 in a FLUTE packet, and outputs the FLUTE stream to the multicast server 66.
- the FLUTE streamer 63 also outputs the MPD input from the MPD generator 64 to the multicast server 66.
- the WEB server 65 In response to the MPD acquisition request (HTTP request) from the terminal device 80, the WEB server 65 performs HTTP unicast distribution of the MPD input from the MPD generator 64 to the request source terminal device 80 via the CDN 72. Also, the WEB server 65 HTTP unicasts the file of the segment stream input from the DASH segmenter 62 to the terminal device 80 of the request source via the CDN 72 in response to the segment stream acquisition request (HTTP request) from the terminal device 80 To deliver.
- the multicast server 66 distributes the MPD from the FLUTE streamer 63 by FLUTE multicast via the CDN 72. Also, the multicast server 66 distributes the FLUTE stream from the FLUTE streamer 63 by FLUTE multicast via the CDN 72. Note that, for example, (e) MBMS's USD, OMA-ESG, etc. are used to make portal channels of FLUTE multicast distribution known.
- the network 71 has a bidirectional communication network represented by the Internet, a unidirectional communication network such as a terrestrial broadcasting network or a satellite broadcasting network, an interaction channel for performing bidirectional communication, and a broadcast / multicast channel for performing unidirectional communication (see FIG. e) encompass mobile telephone communication networks such as MBMS.
- a bidirectional communication network represented by the Internet
- a unidirectional communication network such as a terrestrial broadcasting network or a satellite broadcasting network
- an interaction channel for performing bidirectional communication and a broadcast / multicast channel for performing unidirectional communication
- a broadcast / multicast channel for performing unidirectional communication encompass mobile telephone communication networks such as MBMS.
- a CDN 72 is constructed on the network 71.
- the CDN 72 is provided with a plurality of optimization proxy servers 73, an MPD portal server 74, and a script server 75. Furthermore, although illustration is abbreviate
- the optimization proxy server 73 monitors and analyzes the MPD acquisition request and segment stream acquisition request from the terminal device 80, thereby receiving the reception capability, decoding capability, user preference, and status of the terminal device 80 connected to itself. And the like are made into a database as statistical information (to be described later as request analysis processing).
- the optimization proxy server 73 monitors the metadata (such as OMA-ESG) in which the contents of MPD and FLUTE streams to be multicast-distributed via the CDN 72 are described, and collates with its own database to obtain priority. It is determined whether or not the value is high (the terminal device 80 connected to itself has a high possibility that an acquisition request is subsequently transmitted). Then, MPD and FLUTE streams with high priorities are cached (it will be described later as multicast pre-cache processing).
- metadata such as OMA-ESG
- the optimizing proxy server 73 monitors MPDs and segment streams which are unicast-distributed via the CDN 72, and determines whether or not the priority is high by collating with its own database. Then, MPDs and segment streams with high priorities are cached (this will be described later as unicast pre-cache processing).
- the optimizing proxy server 73 searches the MPD portal server 74 for a high priority MPD and segment stream, identifies it, requests the identified MPD and segment stream from the content supply device 60, and accordingly delivers the HTTP unicast. You can also cache what has been done.
- optimization proxy server 73 registers and cancels the policies of the multicast precache processing and the unicast precache processing based on the control from the terminal device 80 (described later as precache policy registration processing).
- the MPD portal server 74 accesses the many content supply devices 60, and searches for MPDs and segment streams that satisfy predetermined conditions.
- the script server 75 can receive the best for the terminal device 80 (for example, it can be located closest to the terminal device 80 or can not receive the multicast distribution when the terminal device 80 can not receive the multicast distribution) (Iv) Providing a script for preferentially connecting to the optimization proxy server 73 (script provision processing).
- the terminal device 80 includes a reception and reproduction unit 81, a registration unit 82, and a script request unit 83.
- the reception and reproduction unit 81 acquires the MPD, and receives and reproduces the segment stream and the FLUTE stream based on the MPD.
- the registration unit 82 executes a process of registering or deregistering the pre-cache policy of the pro-cache process in the optimization proxy server 73.
- the script request unit 83 is a script for automatically connecting the script server 75 to the optimization proxy server 73 that is optimal for itself (for example, the nearest broadcast network that can not be received, etc.). Request.
- FIG. 3 shows a detailed configuration example of the optimization proxy server 73.
- the optimization proxy server 73 includes a monitoring proxy unit 91, a holding unit 92, an analysis unit 93, an analysis result database 94, and a tuner unit 95.
- the monitoring proxy unit 91 monitors the MPD acquisition request and the segment stream acquisition request from the terminal device 80, and reads the requested MPD and segment stream from the holding unit 92 if they are cached in the holding unit 92. Unicast to the request source. Also, the monitoring agent unit 91 outputs the monitored MPD acquisition request and segment stream acquisition request to the analysis unit 93. Further, the monitoring proxy unit 91 monitors the MPD and segment stream to be HTTP-unicast-distributed and outputs the monitoring to the analysis unit 93.
- the holding unit 92 holds (caching) MPDs and segment streams determined to have high priority, which are input from the analysis unit 93. Further, the holding unit 92 holds the MPD or FLUTE stream which is input from the pre-cache unit 95 and determined to have a high priority.
- the analysis unit 93 analyzes the monitored MPD acquisition request and segment stream acquisition request. Specifically, url name of MPD, profile information described in MPD / @ profile, maximum value of segment size (value of segmentBase / @ duration or @maxSegmentDuration, @maxSubSegmentDuration), content referenced by ProgramInformation Contents of metadata describing contents (Especially, content title, outline, genre, etc. are searched and analyzed as long as the processing load permits and collected as preference information), schema referenced by Role, accessibility schema referenced by Accessibility Content (for example, if it is monitored that there is a segment acquisition request for a stream including audio commentary, the preference of the user of the terminal device 80, the degree of failure, etc.
- the analysis result database 94 is made to hold these contents as statistical information associated with the acquisition request frequency.
- the analysis unit 93 determines the priorities of the MPDs and segment streams monitored from the HTTP unicast distribution, which are input from the monitoring proxy unit 91, and causes the holding unit 92 to hold those with high priorities. In addition, the analysis unit 93 determines the priority of the FLUTE multicast-distributed MPD and FLUTE streams input from the tuner unit 95, and causes the holding unit 92 to hold the one with high priority.
- the analysis result database 94 holds clock information of the analysis result input from the analysis unit 93.
- the tuner unit 95 receives an MPD or FLUTE stream to be distributed by FLUTE multicast and metadata thereof and outputs the stream to the analysis unit 93.
- FIG. 4 is a flowchart for explaining the content distribution process by the content supply apparatus 60.
- step S1 the channel streamer 61 generates a plurality of streaming data having different bit rates from the source data of the content, and outputs the streaming data to the DASH segmenter 62 and the WEB server 65.
- step S2 the DASH segmenter 62 generates a segment stream such as fragmented MP4 from the streaming data and outputs the segment stream to the FLUTE streamer 63 and the WEB server 65. Also, the DASH segmenter 62 notifies the MPD generator 64 of the URL of the supply source of the generated segment stream and the like.
- step S 3 the FLUTE streamer 63 generates a FLUTE stream by storing the segment stream in a FLUTE packet and outputs the FLUTE stream to the multicast server 66.
- step S4 the MPD generator 64 generates an MPD and outputs it to the FLUTE streamer 63 and the WEB server 65.
- step S5 the FLUTE streamer 63 outputs the MPD to the multicast server 66.
- the multicast server 66 distributes the MPD by FLUTE multicast via the CDN 72.
- step S6 when there is an MPD acquisition request (HTTP request) from the terminal device 80, the WEB server 65 correspondingly distributes the MPD to the request source via the CDN 72 to the request source.
- HTTP request MPD acquisition request
- step S7 the multicast server 66 distributes FLUTE streams by FLUTE multicast via the CDN 72.
- step S8 when there is a segment stream acquisition request (HTTP request) from the terminal device 80, the WEB server 65 HTTP unicasts the segment stream to the request source via the CDN 72 in response. This is the end of the description of the content supply processing by the content supply apparatus 60.
- FIG. 5 is a flowchart illustrating request analysis processing by the optimization proxy server 73.
- the monitoring proxy unit 91 of the optimization proxy server 73 monitors the MPD acquisition request in step S21 to analyze the analysis unit 93.
- the analysis unit 93 analyzes the MPD acquisition request and records the result in the analysis result database 94.
- the monitoring agent unit 91 reads the MPD from the holding unit 92 and distributes the HTTTP unicast to the request source.
- FIG. 5 shows an example of the case where the MPD is not cached.
- the WEB server 65 requests the MPD corresponding to the MPD acquisition request via the CDN 72 as the request source. HTTP unicast delivery.
- step S13 when the terminal device 80 transmits a segment stream acquisition request to the WEB server 65 via the CDN 82 based on MPD, in step S23, the monitoring proxy unit 91 monitors the segment stream acquisition request and analyzes it. Output to In step S24, the analysis unit 93 analyzes the segment stream acquisition request and records the result in the analysis result database 94.
- the monitoring substitution unit 91 reads the segment stream from the holding unit 92 and makes the HTTTP unicode request source. Cast to deliver.
- FIG. 5 is an example of the case where the segment stream is not cached.
- the web server 65 transmits the segment stream corresponding to the segment stream acquisition request via the CDN 72. Distribute HTTP unicast to the request source.
- the segment stream delivered by HTTP unicast is received and reproduced by the terminal device 80 as step S14. This is the end of the request analysis process.
- FIG. 6 is a flow chart for explaining the multicast pre-cache processing by the optimization proxy server 73.
- the tuner unit 95 of the optimization proxy server 73 receives the MPD and analyzes it in step S31. Output.
- the analysis unit 93 refers to the analysis result database 94 and causes the holding unit 92 to perform caching when the MPD has a high priority.
- the tuner unit 95 receives the FLUTE stream and outputs it to the analysis unit 93 in step S32.
- the analysis unit 93 refers to the analysis result database 94 and causes the holding unit 92 to cache when the FLUTE stream has a high priority.
- the multicast pre-cache process is ended.
- MPD and FLUTE streams with high priority can be cached in the holding unit 92.
- unicast distribution is performed. Therefore, for example, even when the terminal device 80 does not have the function of receiving a FLUTE stream, these can be supplied to the terminal device 80.
- FIG. 7 is a flowchart for explaining unicast pre-cache processing by the optimization proxy server 73.
- the web server 65 When the terminal device 80 transmits the MPD acquisition request in step S41, the web server 65 performs HTTP unicast distribution of the MPD corresponding to the MPD acquisition request in step S6 of the above-described content supply process, and the terminal device 80 performs step S42. Receive HTTP unicast distributed MPD.
- step S51 the monitoring agent unit 91 of the optimization proxy server 73 monitors this HTTP unicast-delivered MPD and outputs it to the analyzing unit 93.
- the analysis unit 93 determines the priority of the MPD which has been subjected to HTTP unicast distribution, and causes the holding unit 92 to hold the one with high priority.
- the MPD acquisition request transmitted by the terminal device 80 is monitored and analyzed as described above as the request analysis process, and the result is accumulated in the analysis result database 94.
- the web server 65 HTTP unicasts the segment stream corresponding to the segment stream acquisition request as step S8 of the content supply process described above. Then, at step S42, the terminal device 80 receives and reproduces the HTTP unicast distributed segment stream.
- step S52 the monitoring agent unit 91 of the optimization proxy server 73 monitors this HTTP unicast distributed segment stream and outputs the monitored segment stream to the analyzing unit 93.
- the analysis unit 93 determines the priority of the segment stream distributed by HTTP unicast and causes the holding unit 92 to hold the one with high priority.
- the segment stream acquisition request transmitted by the terminal device 80 is monitored and analyzed as described above as the request analysis process, and the result is accumulated in the analysis result database 94.
- MPDs and segment streams with high priorities can be cached in the holding unit 92. Therefore, when these are requested from the terminal device 80, they can be distributed to the request source more quickly than the WEB server 65 performs unicast distribution.
- FIG. 8 is a flowchart for explaining the script providing process.
- step S61 the script request unit 83 of the terminal device 80 requests a PAC (Proxy Auto-Config) script for setting to enable connection to the optimization proxy server 73 most suitable for itself in WPAD (Web Proxy Auto-Discovery) This request is received by the script server 75 when it is transmitted to the CDN 72 using Protocol (Protocol) or the like.
- PAC Proxy Auto-Config
- WPAD Web Proxy Auto-Discovery
- step S71 the script server 75 specifies an optimization proxy server 73 most suitable for the terminal device 80 that has transmitted the PAC script request, and requests the script for setting to connect the optimization proxy server 73 in the terminal device 80. Provide to the original.
- step S72 the script request unit 83 of the terminal device 80 executes the provided script.
- setting is made such that connection can be made preferentially to the optimization proxy server 73 optimal for the terminal device 80. This is the end of the script providing process.
- the terminal device 80 can automatically perform the setting capable of preferentially connecting to the optimum one for the optimization proxy server 73 among the plurality of optimization proxy servers 73 existing in the CDN 72.
- the registration unit 82 of the terminal device 80 controls the registration of the precache policy in the optimization proxy server 73 using an API (Application Program Interface) required by the optimization proxy server 73.
- API Application Program Interface
- Http://dashProxy.a.com/precacheManager/subscribe in the above API indicates the address of the server-side script in the optimization proxy server 73.
- the type of codec described in the MPD to be precached is the codec dictionary entry uri “urn: a.
- Com: codecType is a codec specified by avc and the rating type is a rating dictionary item uri "rating level specified by urn: c.
- a server side script is used to control deletion of the precache policy by the optimizing proxy server 73 by using the API required by the optimizing proxy server 73 and the registering unit 82 of the terminal device 80
- the API parameter in the above API is for deregistering from the precache candidate an MPD in which the genre specified by the genre type is the genre dictionary item uri “urn: b.com: genre: sports” is described. is there.
- the precache policy registration or deregistration processing described above not only the statistical information stored in the analysis result database 94 but also direct control from the terminal device 80 can be used to register the precache policy or It is possible to unregister. Note that which of the priority based on the statistical information of the analysis result database 94 and the priority registered by the direct control from the terminal device 80 is determined as the final priority of the pre-cache processing depends on the database configuration. Can be defined by the action parameter (or API to set it).
- the optimization proxy server 73 in the CDN 72, it is possible to improve the response performance to the request from the terminal device 80.
- the content supply device 60 and the terminal device 80 that execute the series of processes described above can be realized by a computer executing software, in addition to hardware configuration.
- the computer includes, for example, a general-purpose personal computer capable of executing various functions by installing a computer incorporated in dedicated hardware and various programs.
- FIG. 9 is a block diagram showing an example of the hardware configuration of the computer described above.
- a central processing unit (CPU) 201 a read only memory (ROM) 202, and a random access memory (RAM) 203 are mutually connected by a bus 204.
- CPU central processing unit
- ROM read only memory
- RAM random access memory
- an input / output interface 205 is connected to the bus 204.
- An input unit 206, an output unit 207, a storage unit 208, a communication unit 209, and a drive 210 are connected to the input / output interface 205.
- the input unit 206 includes a keyboard, a mouse, a microphone and the like.
- the output unit 207 includes a display, a speaker, and the like.
- the storage unit 208 includes a hard disk, a non-volatile memory, and the like.
- the communication unit 209 is configured of a network interface or the like.
- the drive 210 drives removable media 211 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory.
- the CPU 201 loads the program stored in the storage unit 208 into the RAM 203 via the input / output interface 205 and the bus 204 and executes the program. A series of processing is performed.
- the program executed by the computer 200 can be provided by being recorded on, for example, a removable medium 211 as a package medium or the like. Also, 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 storage unit 208 via the input / output interface 205 by attaching the removable media 211 to the drive 210.
- the program can be received by the communication unit 209 via a wired or wireless transmission medium and installed in the storage unit 208.
- the program can be installed in advance in the ROM 202 or the storage unit 208.
- the program executed by the computer 200 may be a program that performs processing in chronological order according to the order described in the present specification, or necessary timing such as when calling is performed in parallel or in parallel.
- the program may be a program to be processed in
- a terminal device transmits to a content supply device that distributes content via a network, wherein a metafile describes information necessary for the terminal device to receive the content stream
- a monitoring unit that monitors acquisition requests, An analysis unit that analyzes the acquisition request of the monitored metafile; And a database unit that accumulates analysis results of the analysis unit.
- the monitoring unit further monitors the acquisition request for the stream of the content, which the terminal device has transmitted to the content supply apparatus based on the metafile, The analysis unit further analyzes the acquisition request of the monitored stream.
- the proxy server device according to (1).
- the proxy server according to (1) or (2) further comprising: a caching unit that caches at least one of the metafile or the stream delivered via the network according to the priority based on the accumulated analysis result apparatus.
- a caching unit that caches at least one of the metafile or the stream delivered via the network according to the priority based on the accumulated analysis result apparatus.
- the caching unit registers or deletes the caching policy in response to a request from the terminal device.
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Computational Linguistics (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
Abstract
Description
図6は、本開示の実施の形態であるコンテンツ供給システムの構成例を示している。
次に、図3は、最適化プロキシサーバ73の詳細な構成例を示している。
次に、コンテンツ供給システム50の動作について説明する。
図4は、コンテンツ供給装置60によるコンテンツ配信処理を説明するフローチャートである。
次に、図5は、最適化プロキシサーバ73による要求解析処理を説明するフローチャートである。
次に、図6は、最適化プロキシサーバ73によるマルチキャストプリキャッシュ処理を説明するフローチャートである。
次に、図7は、最適化プロキシサーバ73によるユニキャストプリキャッシュ処理を説明するフローチャートである。
次に、図8はスクリプト提供処理を説明するフローチャートである。
次に、端末装置80側からの制御により、プリキャッシュの方針を登録または登録解除する処理について説明する。
http://dashProxy.a.com/precacheManager/subscribe?codec=”urn:b.com:codecType:avc”&rating=”urn: c.com:ratingLevel:PG-13”&priority=1
http://dashProxy.a.com/precacheManager/subscribe?genre=”urn:b.com:genre:sports” &priority=2
http://dashProxy.a.com/precacheManager/unsubscribe?genre=”urn:b.com:genre:sports”
(1)
適応的ストリーミング技術に従い、コンテンツをネットワークを介して配信するコンテンツ供給装置に対して端末装置が送信した、前記端末装置が前記コンテンツのストリームを受信するために必要な情報が記述されているメタファイルの取得要求をモニタリングするモニタリング部と、
モニタリングされた前記メタファイルの前記取得要求を解析する解析部と、
前記解析部の解析結果を蓄積するデータベース部と
を備えるプロキシサーバ装置。
(2)
前記モニタリング部は、さらに、前記コンテンツ供給装置に対して前記端末装置が前記メタファイルに基づいて送信した、前記コンテンツのストリームの取得要求をモニタリングし、
前記解析部は、さらに、モニタリングされた前記ストリームの前記取得要求を解析する
前記(1)に記載のプロキシサーバ装置。
(3)
蓄積された前記解析結果に基づく優先度に従い、前記ネットワークを介して配信された前記メタファイルまたは前記ストリームの少なくとも一方をキャッシングするキャッシング部を
さらに備える前記(1)または(2)に記載のプロキシサーバ装置。
(4)
前記キャッシング部は、前記端末装置からの要求に応じ、前記キャッシングの方針を登録または登録削除する
前記(3)に記載のプロキシサーバ装置。
Claims (10)
- 適応的ストリーミング技術に従い、コンテンツをネットワークを介して配信するコンテンツ供給装置に対して端末装置が送信した、前記端末装置が前記コンテンツのストリームを受信するために必要な情報が記述されているメタファイルの取得要求をモニタリングするモニタリング部と、
モニタリングされた前記メタファイルの前記取得要求を解析する解析部と、
前記解析部の解析結果を蓄積するデータベース部と
を備えるプロキシサーバ装置。 - 前記モニタリング部は、さらに、前記コンテンツ供給装置に対して前記端末装置が前記メタファイルに基づいて送信した、前記コンテンツのストリームの取得要求をモニタリングし、
前記解析部は、さらに、モニタリングされた前記ストリームの前記取得要求を解析する
請求項1に記載のプロキシサーバ装置。 - 蓄積された前記解析結果に基づく優先度に従い、前記ネットワークを介して配信された前記メタファイルまたは前記ストリームの少なくとも一方をキャッシングするキャッシング部を
さらに備える請求項2に記載のプロキシサーバ装置。 - 前記キャッシング部は、前記端末装置からの要求に応じ、前記キャッシングの方針を登録または登録削除する
請求項3に記載のプロキシサーバ装置。 - プロキシサーバ装置の情報処理方法において、
前記プロキシサーバ装置による、
適応的ストリーミング技術に従い、コンテンツをネットワークを介して配信するコンテンツ供給装置に対して端末装置が送信した、前記端末装置が前記コンテンツのストリームを受信するために必要な情報が記述されているメタファイルの取得要求をモニタリングするモニタリングステップと、
モニタリングされた前記メタファイルの前記取得要求を解析し、その解析結果を蓄積する解析ステップと
を含む情報処理方法。 - コンピュータを、
適応的ストリーミング技術に従い、コンテンツをネットワークを介して配信するコンテンツ供給装置に対して端末装置が送信した、前記端末装置が前記コンテンツのストリームを受信するために必要な情報が記述されているメタファイルの取得要求をモニタリングするモニタリング部と、
モニタリングされた前記メタファイルの前記取得要求を解析する解析部と、
前記解析部の解析結果を蓄積するデータベース部と
して機能させるプログラム。 - 適応的ストリーミング技術に従い、コンテンツをネットワークを介して配信するコンテンツ供給装置に対して、前記端末装置が前記コンテンツのストリームを受信するために必要な情報が記述されているメタファイルの取得要求を送信し、前記メタファイルの前記取得要求に応じて前記コンテンツ供給装置から配信された前記メタファイルを受信し、前記メタファイルに基づいて前記コンテンツ供給装置に前記コンテンツのストリームの取得要求を送信し、前記ストリームの前記取得要求に応じて前記コンテンツ供給装置から配信された前記ストリームを受信、再生する受信再生部と、
前記コンテンツ供給装置の動作を代行するプロキシサーバ装置に対して、前記メタファイルまたは前記ストリームの少なくとも一方のキャッシングの方針の登録を要求する登録部と
を備え、
前記プロキシサーバ装置は、
適応的ストリーミング技術に従い、コンテンツをネットワークを介して配信するコンテンツ供給装置に対して端末装置が送信した、前記端末装置が前記コンテンツのストリームを受信するために必要な情報が記述されているメタファイルの取得要求をモニタリングするモニタリング部と、
モニタリングされた前記メタファイルの前記取得要求を解析する解析部と、
前記解析部の解析結果を蓄積するデータベース部とを備える
端末装置。 - 前記登録部は、さらに、前記コンテンツ供給装置の動作を代行するプロキシサーバ装置に対して、前記キャッシングの方針の登録削除を要求する
請求項7に記載の端末装置。 - 自身にとって最適なプロキシサーバに接続するための設定を行なうスクリプトをポータルサーバに要求し、前記ポータルサーバから提供された前記スクリプトを実行することによって前記設定を行なうスクリプト要求部を
さらに備える請求項8に記載の端末装置。 - 適応的ストリーミング技術に従い、コンテンツをネットワークを介して配信するコンテンツ供給装置と、前記コンテンツのストリームを受信、再生する端末装置と、前記コンテンツ供給装置と前記端末装置との間に設けられたプロキシサーバ装置とから成るコンテンツ供給システムおいて、
前記プロキシサーバ装置は、
前記コンテンツ供給装置に対して前記端末装置が送信した、前記端末装置が前記コンテンツのストリームを受信するために必要な情報が記述されているメタファイルの取得要求をモニタリングするモニタリング部と、
モニタリングされた前記メタファイルの前記取得要求を解析する解析部と、
前記解析部の解析結果を蓄積するデータベース部とを備え、
前記端末装置は、
前記コンテンツ供給装置に対して前記メタファイルの前記取得要求を送信し、前記メタファイルの前記取得要求に応じて前記コンテンツ供給装置から配信された前記メタファイルを受信し、前記メタファイルに基づいて前記コンテンツ供給装置に前記コンテンツのストリームの前記取得要求を送信し、前記ストリームの前記取得要求に応じて前記コンテンツ供給装置から配信された前記ストリームを受信、再生する受信再生部と、
前記コンテンツ供給装置の動作を代行する前記プロキシサーバ装置に対して、前記メタファイルまたは前記ストリームの少なくとも一方のキャッシングの方針の登録を要求する登録部と
を備える
コンテンツ供給システム。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
RU2016105847A RU2658860C2 (ru) | 2013-08-26 | 2014-08-12 | Устройство прокси-сервера, способ обработки информации, программа, оконечное устройство и система предоставления контента |
EP14838957.0A EP3041243A4 (en) | 2013-08-26 | 2014-08-12 | Proxy-server device, information processing method, program, terminal device, and content provision system |
US14/912,651 US20160219121A1 (en) | 2013-08-26 | 2014-08-12 | Proxy-server device, information processing method, program, terminal device, and content supply system |
CN201480046010.7A CN105474649B (zh) | 2013-08-26 | 2014-08-12 | 代理服务器装置、信息处理方法、程序、终端装置和内容供应系统 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2013174199A JP2015043486A (ja) | 2013-08-26 | 2013-08-26 | プロキシサーバ装置、情報処理方法、プログラム、端末装置、およびコンテンツ供給システム |
JP2013-174199 | 2013-08-26 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015029767A1 true WO2015029767A1 (ja) | 2015-03-05 |
Family
ID=52586336
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2014/071261 WO2015029767A1 (ja) | 2013-08-26 | 2014-08-12 | プロキシサーバ装置、情報処理方法、プログラム、端末装置、およびコンテンツ供給システム |
Country Status (6)
Country | Link |
---|---|
US (1) | US20160219121A1 (ja) |
EP (1) | EP3041243A4 (ja) |
JP (1) | JP2015043486A (ja) |
CN (1) | CN105474649B (ja) |
RU (1) | RU2658860C2 (ja) |
WO (1) | WO2015029767A1 (ja) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2016024226A1 (en) | 2014-08-12 | 2016-02-18 | Groupon, Inc. | Method, apparatus, and computer program product for controlling content distribution via transceivers to a display |
CN109788079B (zh) * | 2017-11-15 | 2022-03-15 | 瀚思安信(北京)软件技术有限公司 | Dga域名实时检测方法和装置 |
US20240020232A1 (en) * | 2022-07-14 | 2024-01-18 | GT Software D.B.A Adaptigent | Methods and apparatus for selectively caching mainframe data |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012109520A1 (en) * | 2011-02-11 | 2012-08-16 | Interdigital Patent Holdings, Inc. | Method and apparatus for distribution and reception of content |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6959318B1 (en) * | 1998-03-06 | 2005-10-25 | Intel Corporation | Method of proxy-assisted predictive pre-fetching with transcoding |
US20050138604A1 (en) * | 2003-12-19 | 2005-06-23 | Peter Harrison | Browser configuration |
CN100596190C (zh) * | 2007-12-12 | 2010-03-24 | 中山大学 | 一种数字家庭中vod客户端代理缓存服务器 |
CN101184021B (zh) * | 2007-12-14 | 2010-06-02 | 成都市华为赛门铁克科技有限公司 | 一种实现流媒体缓存置换的方法、设备及系统 |
US8621044B2 (en) * | 2009-03-16 | 2013-12-31 | Microsoft Corporation | Smooth, stateless client media streaming |
US9009330B2 (en) * | 2010-04-01 | 2015-04-14 | Cloudflare, Inc. | Internet-based proxy service to limit internet visitor connection speed |
US8849950B2 (en) * | 2011-04-07 | 2014-09-30 | Qualcomm Incorporated | Network streaming of video data using byte range requests |
US20130182643A1 (en) * | 2012-01-16 | 2013-07-18 | Qualcomm Incorporated | Method and system for transitions of broadcast dash service receptions between unicast and broadcast |
GB2513617A (en) * | 2013-05-01 | 2014-11-05 | Openwave Mobility Inc | Caching of content |
-
2013
- 2013-08-26 JP JP2013174199A patent/JP2015043486A/ja active Pending
-
2014
- 2014-08-12 WO PCT/JP2014/071261 patent/WO2015029767A1/ja active Application Filing
- 2014-08-12 CN CN201480046010.7A patent/CN105474649B/zh active Active
- 2014-08-12 EP EP14838957.0A patent/EP3041243A4/en not_active Withdrawn
- 2014-08-12 US US14/912,651 patent/US20160219121A1/en not_active Abandoned
- 2014-08-12 RU RU2016105847A patent/RU2658860C2/ru active
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012109520A1 (en) * | 2011-02-11 | 2012-08-16 | Interdigital Patent Holdings, Inc. | Method and apparatus for distribution and reception of content |
Non-Patent Citations (3)
Title |
---|
DIRK STAEHLE: "QoE-based traffic management for multimedia traffic in mobile networks", 28 September 2012 (2012-09-28), pages 15 - 17, XP055156940, Retrieved from the Internet <URL:http://www. vde-itg-kommunikationsnetze.de/images/stories/ Fachtagungen/zdn2012/vortraege/zdn2012-08- staehle.pdf> [retrieved on 20141023] * |
HIRABAYASHI, MITSUHIRO: "Realizing Moving Image Delivery With No Drop-outs in an Existing Web Server", NIKKEI ELECTRONICS, 19 March 2012 (2012-03-19) |
See also references of EP3041243A4 |
Also Published As
Publication number | Publication date |
---|---|
US20160219121A1 (en) | 2016-07-28 |
JP2015043486A (ja) | 2015-03-05 |
EP3041243A1 (en) | 2016-07-06 |
CN105474649A (zh) | 2016-04-06 |
RU2658860C2 (ru) | 2018-06-25 |
CN105474649B (zh) | 2020-05-15 |
RU2016105847A (ru) | 2017-08-23 |
EP3041243A4 (en) | 2017-04-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2897369B1 (en) | Content supply device, content supply method, program, and content supply system | |
US9787747B2 (en) | Optimizing video clarity | |
JP6630860B2 (ja) | 端末装置および受信方法 | |
WO2015029767A1 (ja) | プロキシサーバ装置、情報処理方法、プログラム、端末装置、およびコンテンツ供給システム | |
WO2014203745A1 (ja) | コンテンツ供給装置、コンテンツ供給方法、プログラム、端末装置、およびコンテンツ供給システム | |
WO2015029800A1 (ja) | サーバ装置、情報処理方法、プログラム、端末装置、およびコンテンツ供給システム | |
US20170155968A1 (en) | Content supply apparatus, content supply method, program terminal apparatus, and content supply system | |
US10623463B2 (en) | Content supplying apparatus, content supplying method, program, terminal device, and content supplying system | |
JP6466850B2 (ja) | コンテンツ供給装置、コンテンツ供給方法、プログラム、端末装置、およびコンテンツ供給システム | |
US20180270546A1 (en) | Content supply device, content supply method, program, terminal device, and content supply system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201480046010.7 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14838957 Country of ref document: EP Kind code of ref document: A1 |
|
REEP | Request for entry into the european phase |
Ref document number: 2014838957 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14912651 Country of ref document: US Ref document number: 2014838957 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2016105847 Country of ref document: RU Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112016003459 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 112016003459 Country of ref document: BR Kind code of ref document: A2 Effective date: 20160218 |