WO2015029800A1 - Server device, information processing method, program, terminal device, and content provision system - Google Patents

Server device, information processing method, program, terminal device, and content provision system Download PDF

Info

Publication number
WO2015029800A1
WO2015029800A1 PCT/JP2014/071466 JP2014071466W WO2015029800A1 WO 2015029800 A1 WO2015029800 A1 WO 2015029800A1 JP 2014071466 W JP2014071466 W JP 2014071466W WO 2015029800 A1 WO2015029800 A1 WO 2015029800A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
proxy server
location information
segment
unit
Prior art date
Application number
PCT/JP2014/071466
Other languages
French (fr)
Japanese (ja)
Inventor
山岸　靖明
Original Assignee
ソニー株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ソニー株式会社 filed Critical ソニー株式会社
Publication of WO2015029800A1 publication Critical patent/WO2015029800A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/258—Client or end-user data management, e.g. managing client capabilities, user preferences or demographics, processing of multiple end-users preferences to derive collaborative data
    • H04N21/25808—Management of client data
    • H04N21/25841—Management of client data involving the geographical location of the client
    • 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/222—Secondary servers, e.g. proxy server, cable television Head-end
    • 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/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
    • H04N21/23805—Controlling the feeding rate to the network, e.g. by controlling the video pump
    • 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/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
    • H04N21/2381—Adapting the multiplex stream to a specific network, e.g. an Internet Protocol [IP] network
    • 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 disclosure relates to a server device, an information processing method, a program, a terminal device, and a content supply system, and in particular, a server device, an information processing method, a program, and a terminal device capable of preferentially connecting to a proxy server optimal for the terminal device. , 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 such as Fragmented MP4. 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.
  • the proxy server 13 caches files of MPDs and segment streams to be HTTP-unicast-distributed via the CND 12. Then, instead of the DASH MPD server 23 or the DASH segment streamer 22 as a WEB server, the file of the MPD or segment stream being cached is delivered to the request source via HTTP unicast to the DASH client 30 that sent the HTTP request.
  • the proxy server 13 is not limited to the CDN 12.
  • the proxy server 13 may be implemented on the same device including the DASH client 30, or in the vicinity of the DASH client 30 (for example, in a home LAN segment to which the DASH client 30 is connected) It may be provided in).
  • the proxy server 13 may be provided in multiple stages on the CDN 12 or the like.
  • the proxy server 13 between the content supply device 20 and the DASH client 30, it is possible to enhance the response performance to the request from the DASH client 30.
  • adaptive streaming technology using HTTP unicast distribution is realized in DASH, and furthermore, multicast distribution (including broadcast distribution) of streams using terrestrial broadcasting, satellite broadcasting, mobile telephone communication networks, etc. Is also being considered. In that case, the appearance of a proxy server that also supports multicast distribution is assumed.
  • one proxy server can cache only a stream of unicast delivery
  • another proxy server can also perform caching of a stream of multicast delivery and can also perform unicast delivery, etc. It can occur.
  • one DASH client 30 can connect to a broadcast network or mobile communication network where multicast distribution is performed and wifi connected to unicast distribution, but another DASH client 30 can connect only to wifi and can not receive multicast distribution.
  • one DASH client 30 can connect to a broadcast network or mobile communication network where multicast distribution is performed and wifi connected to unicast distribution, but another DASH client 30 can connect only to wifi and can not receive multicast distribution.
  • functional differences such as
  • the DASH client 30 that can connect only to wifi connects to the latter proxy server described above via wifi, not only the stream of unicast distribution but also the stream of multicast distribution can be used.
  • the DASH client 30 if it is in a state where it can connect to the proxy server that is optimal for itself (for example, it is located at a place where it can connect to the proxy server via wifi), it preferentially connects to the proxy server. It is desirable to be able to do it.
  • proxy server connection setting is performed so that connection can be preferentially made to the proxy server. It is something that can be changed.
  • a server apparatus includes: an acquisition unit that acquires location information transmitted by a terminal apparatus that receives content distributed according to adaptive streaming technology; and a proximity of the terminal apparatus based on the location information It is determined whether there is a proxy server device to which the terminal device can connect, and if the proxy server device is present, the terminal device is preferentially connected to the proxy server device.
  • the terminal comprises: a generation unit that generates a ProxyChangeEvent including a script for changing a proxy server connection setting; and a supply unit that supplies the generated ProxyChangeEvent to the terminal device.
  • the acquisition unit can acquire the location information stored as a query parameter in a segment acquisition request transmitted for the terminal device to request unicast distribution of the segment stream of the content, and the supply unit
  • the ProxyChangeEvent may be inserted into the segment stream corresponding to the segment acquisition request and supplied to the terminal device.
  • the acquisition unit may acquire the location information stored in an XML HttpRequest, and the supply unit may supply the ProxyChange Event to the terminal device as a response to the XML Http Request.
  • the location information may be GPS location information or a cell ID.
  • the proxy server apparatus can cache segment streams of the unicast-distributed content, and can also cache a FLUTE stream of the multicast-distributed content.
  • the server device in the information processing method of a server device, acquisition is performed by the server device for acquiring location information transmitted by a terminal device that receives content distributed according to adaptive streaming technology. And determining whether there is a proxy server apparatus to which the terminal apparatus can be connected in the vicinity of the terminal apparatus based on the location information and the terminal apparatus determines the proxy server apparatus if the proxy server apparatus exists.
  • the method includes a generation step of generating a ProxyChangeEvent including a script for changing a proxy server connection setting of the terminal device to preferentially connect to a server device, and a supply step of supplying the generated ProxyChange Event to the terminal device.
  • a program includes a computer, an acquisition unit for acquiring location information transmitted by a terminal that receives content distributed according to adaptive streaming technology, and the terminal based on the location information. It is determined whether or not there is a proxy server device to which the terminal device can be connected in the vicinity of the terminal device, and when the proxy server device is present, the terminal device is preferentially connected to the proxy server device. It functions as a generation unit that generates ProxyChangeEvent including a script for changing the proxy server connection setting of the device, and a supply unit that supplies the generated ProxyChangeEvent to the terminal device.
  • location information transmitted by a terminal that receives content distributed according to adaptive streaming technology is acquired, and the terminal is connected in the vicinity of the terminal based on the location information. It is determined whether or not a possible proxy server device exists, and when the proxy server device exists, the proxy server connection setting of the terminal device is changed so that the terminal device preferentially connects to the proxy server device ProxyChangeEvent including a script to be generated is generated, and the generated ProxyChangeEvent is supplied to the terminal device.
  • a terminal device is a terminal device that receives content distributed according to an adaptive streaming technique, a transmitting unit that acquires and transmits its own location information, and transmits the location information. And a script execution unit configured to change the proxy server connection setting by executing a script included in ProxyChangeEvent supplied.
  • the transmitting unit may store and transmit the location information as a query parameter in a segment acquisition request for requesting unicast distribution of the segment stream of the content, and the script execution unit may transmit the segment acquisition request to the segment acquisition request. Accordingly, proxy server connection settings can be changed by executing the script included in the ProxyChange Event inserted in the segment stream unicasted.
  • the transmission unit can store the location information in XML Http Request and transmit it, and the script execution unit executes the script included in the ProxyChange Event transmitted as a response to the XML Http Request to set a proxy server connection. Can be changed.
  • the location information may be GPS location information or a cell ID.
  • the proxy server connection setting is changed by acquiring location information of its own and transmitting it, and executing a script included in ProxyChangeEvent supplied in response to the transmission of the location information. Ru.
  • a content supply system is a content supply system including a content supply apparatus for distributing a stream of content according to adaptive streaming technology, a terminal apparatus for receiving the stream, and a server apparatus.
  • the server device determines whether there is a proxy server device to which the terminal device can be connected in the vicinity of the terminal device based on the acquisition unit that acquires the location information transmitted by the terminal device and the location information.
  • a generation unit that generates a ProxyChange Event including a script for changing the proxy server connection setting of the terminal device so that the terminal device preferentially connects to the proxy server device when the proxy server device is present; Supply unit for supplying the proxy Change Event to the terminal device Equipped with a.
  • the terminal device performs a proxy server by executing a script included in the ProxyChange Event supplied from the server device in response to the transmission of the location information, and a transmitting unit that acquires and transmits the location information of the terminal device. And a script execution unit that changes connection settings.
  • location information transmitted by a terminal device that receives content distributed according to adaptive streaming technology is acquired by the server device, and the server device obtains the location information in the vicinity of the terminal device based on the location information. It is determined whether there is a proxy server device to which a terminal device can be connected, and if the proxy server device exists, the proxy server of the terminal device is configured to preferentially connect the terminal device to the proxy server device A ProxyChangeEvent including a script for changing a connection setting is generated, and the generated ProxyChangeEvent is supplied to the terminal device.
  • the terminal apparatus acquires and transmits its own location information, and executes a script included in ProxyChangeEvent supplied in response to the transmission of the location information, thereby changing the proxy server connection setting.
  • the proxy server connection setting of the terminal device can be changed.
  • an efficient streaming service can be provided by connecting a terminal device to an optimal proxy server.
  • Case 1 When a terminal device receives and reproduces a stream to be unicast-distributed using a mobile communication network ((e) MBMS etc.), communication is performed by connecting a number of terminal devices to the same cell of the mobile communication network Congestion may occur. In such a case, if the terminal device stops using the mobile communication network and connects to the proxy server via the wifi access point located in the vicinity, the stream can be received more efficiently.
  • the connecting proxy server may be any server that caches at least one of the unicast delivery stream and the multicast delivery stream.
  • unicast delivery is assumed when delivering a stream from a proxy server to a terminal device, this may be used when multicast delivery using wifi is generalized in the future.
  • Case 2 The terminal device receives and reproduces a stream distributed by multicast using a mobile communication network whose communication speed is stable, but can only distribute streams with a low bit rate due to the limitation of multicast resources in the mobile communication network
  • a high quality stream can be distributed by the terminal device from the proxy server by connecting to the proxy server via the wifi access point located in the vicinity.
  • the connecting proxy server may be any server that caches at least one of the unicast delivery stream and the multicast delivery stream.
  • unicast delivery is assumed when delivering a stream from a proxy server to a terminal device, this may be used when multicast delivery using wifi is generalized in the future.
  • cases A and B are assumed as a method of notifying a proxy server optimal for the terminal device.
  • the terminal device stores its own location information (for example, GPS location information and cell ID of a mobile communication network) in a stream request and transmits it.
  • the proxy server side identifies a suitable proxy server, and notifies a script that changes the proxy connection setting to connect to the proxy server.
  • DASH inband event XML Http Request, ServerSentEvent, or ATSC 2.0 trigger can be used.
  • Case B The terminal device detects and accesses the access to the wifi access point, and acquires an address of the proxy server by DHCP after the L2 authentication process. If the proxy server is caching (or possibly giving priority to caching) the stream being received or played at the terminal device, change the proxy connection setting to connect to the proxy server . In addition, even if the proxy server is not caching the stream being received or reproduced by the terminal device, the proxy server is reasonable if, for example, the cost is reasonable and the performance is higher than expected than continuing the current reception. Change the proxy connection settings to connect to the proxy server.
  • FIG. 2 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 proxy server 13 provided in a CDN 52 built on a network 51, an optimization proxy server 53, a location monitoring server 54, and a number of them. Terminal devices 70-1 to 80-N.
  • the content supply devices 60-1 to 60-K and the terminal devices 70-1 to 80-N are connected to the network 51.
  • 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 network 51 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.
  • the CDN 52 on the network 51 includes a plurality of conventional proxy servers 13, an optimization proxy server 53, and a plurality of location monitoring servers 54, respectively.
  • the optimization proxy server 53 caches MPDs and streams that are unicasted or multicasted via the CDN 52. Further, in response to the MPD acquisition request and the segment acquisition request from the terminal device 70, the optimization proxy server 53 delivers the corresponding MPD or segment stream file to the request source if it is caching. If caching is not performed, the MPD acquisition request and the segment acquisition request are relayed to the content supply device 60.
  • the optimization proxy server 53 monitors and analyzes the MPD acquisition request and segment acquisition request from the terminal device 70 to estimate the reception capability, decoding capability, user preference, status, etc. of the terminal device 70.
  • a database may be created, and MPDs and segment streams that may be requested to be obtained may be preferentially cached based on the database.
  • the optimization proxy server 53 requests the location monitoring server 54 to analyze the location information included in the segment acquisition request, inserts a Proxy Change Event into the segment response, and delivers it to the request source as necessary.
  • the location monitoring server 54 determines the position of the terminal device 70 based on the location information included in the segment acquisition request in response to a request from the optimization proxy server 53. Then, when there is an optimization proxy server 53 near the terminal device 70, a Proxy Change Event is generated to change the proxy server connection setting so as to preferentially connect to the optimization proxy server 53, and the optimization proxy server 53 is generated.
  • the optimization proxy server 53 and the location monitoring server 54 can be integrally configured.
  • 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 70, 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 FLUTE streamer 63 and the WEB server 65. 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 70 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 70, the WEB server 65 performs HTTP unicast distribution of the MPD input from the MPD generator 64 to the request source terminal device 70 via the CDN 52. In addition, the WEB server 65 distributes the file of the segment stream input from the DASH segmenter 62 to the terminal device 70 of the request source via the CDN 52 in response to the segment acquisition request (HTTP request) from the terminal device 70. Do.
  • the multicast server 66 distributes the MPD from the FLUTE streamer 63 by FLUTE multicast via the CDN 52. Also, the multicast server 66 distributes the FLUTE stream from the FLUTE streamer 63 by FLUTE multicast via the CDN 52. Note that, for example, (e) MBMS's USD, OMA-ESG, etc. are used to make portal channels of FLUTE multicast distribution known.
  • the terminal device 70 includes a reception and reproduction unit 71, a location notification unit 71, and a script execution unit 73.
  • the reception and reproduction unit 71 acquires the MPD, and receives and reproduces the segment stream and the FLUTE stream based on the MPD.
  • the location notification unit 72 acquires location information such as GPS position information and cell ID, and notifies the optimization proxy server 53 by including the acquired location information as a query parameter in the segment acquisition request. In addition, the location notification unit 72 includes the acquired location information in the XML Http Request and notifies the location monitoring server 54 of it.
  • the script execution unit 73 executes a script for changing proxy connection settings, which is notified as a Proxy Change Event.
  • FIG. 3 shows a detailed configuration example of the optimization proxy server 53.
  • the optimization proxy server 53 includes a monitoring agent unit 81, a tuner unit 82, a caching unit 83, and an analysis request unit 84.
  • the monitoring proxy unit 81 monitors the MPDs and segment streams to be unicast-distributed, and outputs them to the caching unit 83 for caching. Also, the monitoring agent unit 81 monitors the MPD acquisition request and segment acquisition request from the terminal device 70, and if the requested MPD and segment stream are cached in the caching unit 83, the caching unit 83 Read and deliver to the request source by unicast. If not cached, the MPD acquisition request and the segment acquisition request are relayed to the WEB server 65, and the MPD and segment stream to be unicast-distributed in response to this are also monitored and the caching unit 83 is made to cache. Furthermore, the monitoring agent unit 81 outputs the location information included in the monitored segment acquisition request to the analysis request unit 84.
  • the tuner unit 82 receives an MPD or FLUTE stream distributed by FLUTE multicast and outputs the stream to the caching unit 83.
  • the caching unit 83 caches the MPD and segment stream files input from the monitoring proxy unit 81.
  • the caching unit 83 also caches the MPD and FLUTE streams input from the tuner unit 82.
  • the analysis request unit 84 notifies the location monitoring server 54 of the location information included in the segment acquisition request, which is input from the monitoring proxy unit 81, and requests analysis. Also, the Proxy Change Event supplied as a result of analysis from the location monitoring server 54 is output to the monitoring agent unit 81, and the Proxy Change Event is inserted into the segment stream as a response to the segment acquisition request, and unicasted to the request source. Let it be delivered.
  • FIG. 4 is a flowchart for explaining the content distribution process by the content supply apparatus 60.
  • step S 1 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.
  • 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 52.
  • step S6 when there is an MPD acquisition request (HTTP request) from the terminal device 70, the WEB server 65 distributes the MPD to the request source via the CDN 52 in response to the request.
  • HTTP request MPD acquisition request
  • step S7 the multicast server 66 distributes FLUTE streams by FLUTE multicast via the CDN 52.
  • step S8 when there is a segment acquisition request (HTTP request) from the terminal device 70, the WEB server 65 distributes the segment stream to the request source via the CDN 52 according to the request. This is the end of the description of the content supply processing by the content supply apparatus 60.
  • FIG. 5 is a flowchart illustrating an event notification process when the terminal device 70 transmits location information using a segment acquisition request (segment request). This event processing is applied when the terminal device 70 receives and reproduces a stream of unicast distribution.
  • step S11 when the terminal device 70 transmits an MPD acquisition request, the monitoring agent unit 81 of the optimization proxy server 53 monitors the MPD acquisition request in step S21.
  • the MPD is read from the caching unit 83 and unicasted to the request source. If not cached, the MPD acquisition request is relayed to the WEB server 65, and the caching unit 83 is made to cache the MPD to be unicast-distributed in response to this.
  • the monitoring proxy unit 81 designates a description scheme uri that defines the configuration of the query parameter to be added to the segment acquisition request transmitted from the terminal device 70 later, using a query string as MPD redirection for the MPD acquisition request. Note that the description scheme uri may be specified in the MPD instead of the MPD redirection.
  • the contents of the query parameter defined in the description scheme uri are the location information of the terminal device 70 in this case.
  • step S12 the terminal device 70 receives the unicast-distributed MPD and MPD redirection.
  • FIG. 6 shows the relationship between the MPD acquisition request (MPD request), the MPD redirection therefor, the subsequent segment acquisition request (segment request), and the corresponding segment response.
  • the location notification unit 72 after receiving the MPD redirection acquires location information according to the description scheme uri, and uses the location information as a query parameter in the segment request transmitted thereafter (FIG. 6). would like to insert "geoLocation-1" etc.).
  • step S13 when the terminal device 70 transmits a segment acquisition request into which location information has been inserted as a query parameter, in step S22, the monitoring proxy unit 81 of the optimization proxy server 53 monitors the segment acquisition request and acquires a segment.
  • the location information included in the request is output to the analysis request unit 84.
  • step S23 the analysis request unit 84 notifies the location monitoring server 54 of the location information input from the monitoring agent unit 81, and requests analysis.
  • the location monitoring server 54 determines the position of the terminal device 70 based on the location information in response to a request from the analysis request unit 84 of the optimization proxy server 53, and changes it as a connection destination near the terminal device 70. If there is an optimization proxy server 53 that can do this, a Proxy Change Event for changing the proxy server connection setting so as to connect to the optimization proxy server 53 with priority is generated and supplied to the analysis request unit 84.
  • step S24 the analysis request unit 84 outputs the Proxy Change Event supplied as a result of the analysis from the location monitoring server 54 to the monitoring agent unit 81, and the Proxy Change Event is sent to the segment stream as a response to the segment acquisition request. Insert it and make it unicast to the request source. The details of the process of inserting a Proxy Change Event into the segment stream will be described later.
  • step S14 the terminal device 70 receives and reproduces the unicast transmitted segment stream.
  • the script execution unit 73 executes the Proxy Change Event script, whereby the proxy server connection setting of the terminal device 70 is optimized to be located in the vicinity thereof. It is changed to connect preferentially to the proxy server 53.
  • ProxyChangeEvent is newly introduced in the box type event notification method embedded in the fragmented MP4 segment stream adopted in DASH.
  • FIG. 7 shows an example of the format of an event message of ProxyChangeEvent using DASH inband event.
  • scheme_id_uri + value defines the format of the content of message_data [] (the event message body).
  • a scheme_id_uri of "urn: mpeg: dash: event: 2012" is defined, two types of values are defined as values, and it is defined to be used for MPD update event notification.
  • “urn: mpeg: dash: event: proxyChange” is newly introduced as scheme_id_uri so that the proxy setting change message can be expressed.
  • the DASH push event can not originally designate the terminal device 70 for event distribution, this is possible in this embodiment.
  • the terminal device 70 that is the target of event distribution can be specified only when the segment stream is being unicast-distributed.
  • a ProxyChange Event may be inserted into a segment chunk of the stream to be multicast-distributed. It is possible to simultaneously set the terminal device 70 as an event distribution target.
  • the method of event notification can also use XMLHttpRequest or WebSocket specified in W3C.
  • XMLHttpRequest the format of the script to be stored and its content itself, or the address of the proxy server to be changed may be stored in the body of the HTTP response in the json format.
  • ⁇ “pac” (javascript itself of pac) ⁇ is stored in the data field
  • ⁇ “pacUrl” (javascript acquisition destination url of pac) ⁇
  • url of the DASH proxy server to be changed it is ⁇ "proxyUrl”: (url of DASH proxy server to be changed) ⁇ .
  • FIG. 8 is a flowchart illustrating an event notification process in the case where the terminal device 70 transmits location information using XML Http Request. This event processing can be applied not only when the terminal device 70 receives and reproduces a stream of unicast distribution, but also when the stream of multicast distribution is received and reproduced.
  • step S41 the location notification unit 72 of the terminal device 70 acquires the location information of the terminal device 70, stores it in XML HttpRequest, and sends it to the location monitoring server 54.
  • step S51 the location monitoring server 54 that has received the XML Http Request determines the position of the terminal device 70 based on the location information stored in the XML Http Request, and can be changed in the vicinity of the terminal device 70 as a connection destination. If there is a Proxy Change Event for changing the proxy server connection setting so as to connect preferentially to the optimization proxy server 53, a Proxy Change Event is sent to the terminal device 70 as a response to XMLHttpRequest.
  • step S42 the script execution unit 73 of the terminal device 70 executes a script of Proxy Change Event as a response of XMLHttpRequest, whereby the proxy server connection setting of the terminal device 70 is located in the vicinity of the optimization proxy server 53 Is changed to connect preferentially to.
  • the movement of the terminal device 70 is detected based on the location information of the terminal device 70, and when there is an optimization proxy server 53 connectable at that position, the proxy is You can change the server connection settings. As a result, the terminal device 70 can efficiently use the streaming service.
  • each device of the content supply system 50 that executes the series of processes described above can be realized by a computer executing software in addition to hardware being configured.
  • 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
  • the present disclosure can also be configured as follows.
  • An acquisition unit that acquires location information transmitted by a terminal device that receives content distributed according to an adaptive streaming technique; Based on the location information, it is determined whether or not there is a proxy server device to which the terminal device can be connected in the vicinity of the terminal device, and if the proxy server device is present, the terminal device is connected to the proxy server device
  • a generation unit that generates a ProxyChangeEvent including a script for changing the proxy server connection setting of the terminal device so as to connect preferentially;
  • a supply unit that supplies the generated ProxyChangeEvent to the terminal device.
  • the acquisition unit acquires the location information stored as a query parameter in a segment acquisition request transmitted by the terminal device to request unicast distribution of the segment stream of the content.
  • the server apparatus wherein the supply unit inserts the ProxyChange Event into the segment stream corresponding to the segment acquisition request and supplies the ProxyChange Event to the terminal device.
  • the acquisition unit acquires the location information stored in XML HttpRequest, The server device according to (1), wherein the supply unit supplies the ProxyChange Event to the terminal device as a response to the XML Http Request.
  • the location information is GPS location information or a cell ID.
  • the server apparatus according to any one of (1) to (3).
  • the proxy server apparatus caches a segment stream of the content to be unicast-distributed, and also caches a FLUTE stream of the content to be multicast-distributed.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Computer Graphics (AREA)
  • Information Transfer Between Computers (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

This disclosure pertains to a server device, an information processing method, a program, a terminal device, and a content provision system that make it possible to change proxy-server connection settings so as to be able to connect to an optimal proxy server. A server device in one aspect of this disclosure is provided with the following: an acquisition unit that acquires location information transmitted by a terminal device that receives content delivered via an adaptive streaming technology; a generation unit that, on the basis of said location information, determines whether or not there is a proxy server, near the terminal device, to which said terminal device can connect, and if there is such a proxy server, generates a ProxyChangeEvent that contains a script that changes the proxy-server connection settings of the terminal device such that said terminal device preferentially connects to the aforementioned proxy server; and a supply unit that supplies the generated ProxyChangeEvent to the terminal device. This disclosure can be applied to a system that streams content.

Description

サーバ装置、情報処理方法、プログラム、端末装置、およびコンテンツ供給システムServer apparatus, information processing method, program, terminal apparatus, and content supply system
　本開示は、サーバ装置、情報処理方法、プログラム、端末装置、およびコンテンツ供給システムに関し、特に、端末装置にとって最適なプロキシサーバに優先的接続できるようにしたサーバ装置、情報処理方法、プログラム、端末装置、およびコンテンツ供給システムに関する。 The present disclosure relates to a server device, an information processing method, a program, a terminal device, and a content supply system, and in particular, a server device, an information processing method, a program, and a terminal device capable of preferentially connecting to a proxy server optimal for the terminal device. , And a content supply system.
　インターネットを介する動画配信に利用可能な国際標準化された動画配信プロトコルとして、Webサイトなどの閲覧と同様のHTTPユニキャスト配信を用いるMPEG-DASH（Moving Picture Experts Group-Dynamic Adaptive Streaming over HTTP、以下、DASHと称する）が知られている（例えば、非特許文献１を参照）。 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).
　DASHでは適応型ストリーミング技術が実現されている。すなわち、DASHにおけるコンテンツの供給側は、同一内容のコンテンツとして、配信パスの通信環境や受信側の能力や状態に応じて画質や画角サイズなどが変更されている複数のストリームを用意するようになされている。一方、受信側は、供給側が用意している複数のストリームのうち、自己が受信可能であって自己のデコード能力などに応じた最適なストリームを選択して受信、再生するようになされている。 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. On the other hand, 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.
　このように、DASHにおいては、受信側がストリームを適応的に選択して受信できるように、MPD(Media Presentation Description)と称されるメタデータが供給側から受信側に供給される。 As described above, in the DASH, metadata referred to as Media Presentation Description (MPD) is supplied from the supply side to the reception side so that the reception side can adaptively select and receive the stream.
　MPDには、チャンク化されたコンテンツのセグメントストリーム(Audio/Video/Subtitle等のメディアデータ)の供給元となるWEBサーバのアドレス(url情報)が記述されている。受信側は該url情報に基づいて、コンテンツの供給元となるWEBサーバにHTTPリクエストを送信し、このHTTPリクエストに応じてWEBサーバがユニキャスト配信するセグメントストリームを受信、再生することになる。 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.
　図１は、DASHに基づいてコンテンツのセグメントストリームを配信するコンテンツ供給システムの構成の一例を示している。 FIG. 1 shows an example of the configuration of a content supply system for distributing segment streams of content based on DASH.
　このコンテンツ供給システム１０は、コンテンツを供給する側の複数のコンテンツ供給装置２０－１乃至２０－Ｋと、コンテンツを受信する側の多数のDASHクライアント３０－１乃至３０－Ｎから構成される。以下、コンテンツ供給装置２０－１乃至２０－Ｋを個々に区別する必要がない場合、単にコンテンツ供給装置２０と称する。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. Hereinafter, 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.
　コンテンツ供給装置２０とDASHクライアント３０は、それぞれインターネット１１に接続されている。インターネット１１上には、CDN(Contents Delivery Network)１２が構築されている。 The content supply device 20 and the DASH client 30 are connected to the Internet 11, respectively. On the Internet 11, a CDN (Contents Delivery Network) 12 is constructed.
　コンテンツ供給装置２０は、同一内容のコンテンツであってビットレートが異なる複数のセグメントストリームを配信するものであり、チャネルストリーマ２１、DASHセグメントストリーマ２２、およびDASH MPDサーバ２３を有する。 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.
　チャネルストリーマ２１は、DASHクライアント３０に配信するためのコンテンツのソースデータを管理しており、コンテンツのソースデータからビットレートが異なる複数のストリーミングデータを生成してDASHセグメントストリーマ２２に出力する。 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.
　DASHセグメントストリーマ２２は、各ストリーミングデータを時間的にセグメントに分割して（チャンク化して）、Fragmented MP4などのセグメントストリームを生成する。また、DASHセグメントストリーマ２２は、セグメントストリームをファイル化して保持し、WEBサーバとして、DASHクライアント３０からの要求（HTTPリクエスト）に応じ、セグメントストリームのファイルを、CDN１２を介して要求元のDASHクライアント３０にHTTPユニキャスト配信する。さらに、DASHセグメントストリーマ２２は、セグメントストリームのファイルの供給元のアドレスをDASH MPDサーバ２３に通知する。 The DASH segment streamer 22 temporally divides (streams) each streaming data into segments to generate a segment stream such as Fragmented MP4. 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.
　DASH MPDサーバ２３は、DASHクライアント３０がセグメントストリームのファイルを取得するために必要な、セグメントストリームのファイルの供給元を表すアドレスなどが記述されたMPDを生成する。また、DASH MPDサーバ２３は、WEBサーバとして、DASHクライアント３０からの要求（HTTPリクエスト）に応じ、生成したMPDをCDN１２を介して要求元のDASHクライアント３０にHTTPユニキャスト配信する。 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.
　DASHクライアント３０は、DASH MPDサーバ２３に対してMPDを要求し、これに応じてHTTPユニキャスト配信されたMPDを受信する。さらに、DASHクライアント３０は、受信したMPDに基づき、DASHセグメントストリーマ２２にセグメントストリームのファイルを要求し、これに応じてHTTPユニキャスト配信されるセグメントストリームのファイルを受信、再生する。 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.
　CDN１２にはプロキシサーバ１３が設けられている。プロキシサーバ１３は、CND１２を介してHTTPユニキャスト配信されるMPDやセグメントストリームのファイルをキャッシングする。そして、WEBサーバとしてのDASH MPDサーバ２３またはDASHセグメントストリーマ２２に代わり、HTTPリクエストを送信したDASHクライアント３０に対してキャッシングしているMPDまたはセグメントストリームのファイルを要求元にHTTPユニキャスト配信する。 The CDN 12 is provided with a proxy server 13. The proxy server 13 caches files of MPDs and segment streams to be HTTP-unicast-distributed via the CND 12. Then, instead of the DASH MPD server 23 or the DASH segment streamer 22 as a WEB server, the file of the MPD or segment stream being cached is delivered to the request source via HTTP unicast to the DASH client 30 that sent the HTTP request.
　なお、プロキシサーバ１３は、CDN１２上に限らず、例えばDASHクライアント３０を包含する同一デバイス上に実装される場合や、DASHクライアント３０の近傍（例えば、DASHクライアント３０が接続されたホームLANセグメント内など）に設けられることもある。さらに、プロキシサーバ１３は、CDN１２上などに多段に設けられることがある。 The proxy server 13 is not limited to the CDN 12. For example, the proxy server 13 may be implemented on the same device including the DASH client 30, or in the vicinity of the DASH client 30 (for example, in a home LAN segment to which the DASH client 30 is connected) It may be provided in). Furthermore, the proxy server 13 may be provided in multiple stages on the CDN 12 or the like.
　上述したように、コンテンツ供給装置２０とDASHクライアント３０との間にプロキシサーバ１３を設けることにより、DASHクライアント３０からの要求に対する応答性能を高めることができる。 As described above, by providing the proxy server 13 between the content supply device 20 and the DASH client 30, it is possible to enhance the response performance to the request from the DASH client 30.
　ところで、DASHではHTTPユニキャスト配信を用いた適応的ストリーミング技術が実現されており、さらに地上放送、衛星放送、携帯電話通信網などを利用して、ストリームをマルチキャスト配信（ブロードキャスト配信も含む）することも検討されている。その場合、マルチキャスト配信にも対応するプロキシサーバの出現が想定される。 By the way, adaptive streaming technology using HTTP unicast distribution is realized in DASH, and furthermore, multicast distribution (including broadcast distribution) of streams using terrestrial broadcasting, satellite broadcasting, mobile telephone communication networks, etc. Is also being considered. In that case, the appearance of a proxy server that also supports multicast distribution is assumed.
　すなわち、例えば、あるプロキシサーバは、ユニキャスト配信のストリームのみをキャッシング可能であるが、別のプロキシサーバは、さらにマルチキャスト配信のストリームもキャッシングしてユニキャスト配信できるなど、プロキシサーバに機能の差が生じ得る。 That is, for example, although one proxy server can cache only a stream of unicast delivery, another proxy server can also perform caching of a stream of multicast delivery and can also perform unicast delivery, etc. It can occur.
　一方、DASHクライアント３０についても機能に差があることがある。例えば、あるDASHクライアント３０は、マルチキャスト配信が行われる放送網や携帯通信網とユニキャスト配信が行なわれるwifiに接続できるが、別のDASHクライアント３０は、wifiのみに接続できてマルチキャスト配信を受信できないなどの機能差があり得る。 On the other hand, there may be differences in the functions of the DASH client 30 as well. For example, one DASH client 30 can connect to a broadcast network or mobile communication network where multicast distribution is performed and wifi connected to unicast distribution, but another DASH client 30 can connect only to wifi and can not receive multicast distribution. There may be functional differences such as
　そのような場合、wifiのみに接続できるDASHクライアント３０が、上述した後者のプロキシサーバにwifiを介して接続すれば、ユニキャスト配信のストリームだけでなく、マルチキャスト配信のストリームも利用できることになる。このように、DASHクライアント３０が自身にとって最適なプロキシサーバに接続できる状態（例えば、wifi経由で該プロキシサーバに接続できる場所に位置しているなど）であれば、該プロキシサーバに優先的に接続できることが望ましい。 In such a case, if the DASH client 30 that can connect only to wifi connects to the latter proxy server described above via wifi, not only the stream of unicast distribution but also the stream of multicast distribution can be used. As described above, if the DASH client 30 is in a state where it can connect to the proxy server that is optimal for itself (for example, it is located at a place where it can connect to the proxy server via wifi), it preferentially connects to the proxy server. It is desirable to be able to do it.
　本開示はこのような状況に鑑みてなされたものであり、端末装置が自身にとって最適なプロキシサーバに接続できる状態にある場合、該プロキシサーバに対して優先的に接続できるようプロキシサーバ接続設定を変更できるようにするものである。 The present disclosure has been made in view of such a situation, and when a terminal device is in a state where it can connect to a proxy server that is optimal for itself, proxy server connection setting is performed so that connection can be preferentially made to the proxy server. It is something that can be changed.
　本開示の第１の側面であるサーバ装置は、適応的ストリーミング技術に従って配信されるコンテンツを受信する端末装置が送信したロケーション情報を取得する取得部と、前記ロケーション情報に基づいて前記端末装置の近傍に前記端末装置が接続可能なプロキシサーバ装置が存在するか否かを判定し、前記プロキシサーバ装置が存在する場合、前記端末装置が前記プロキシサーバ装置に優先的に接続するように前記端末装置のプロキシサーバ接続設定を変更するスクリプトを含むProxyChangeEventを生成する生成部と、生成された前記ProxyChangeEventを前記端末装置に供給する供給部とを備える。 A server apparatus according to a first aspect of the present disclosure includes: an acquisition unit that acquires location information transmitted by a terminal apparatus that receives content distributed according to adaptive streaming technology; and a proximity of the terminal apparatus based on the location information It is determined whether there is a proxy server device to which the terminal device can connect, and if the proxy server device is present, the terminal device is preferentially connected to the proxy server device. The terminal comprises: a generation unit that generates a ProxyChangeEvent including a script for changing a proxy server connection setting; and a supply unit that supplies the generated ProxyChangeEvent to the terminal device.
　前記取得部は、前記コンテンツのセグメントストリームのユニキャスト配信を前記端末装置が要求するために送信したセグメント取得要求にクエリパラメータとして格納されている前記ロケーション情報を取得することができ、前記供給部は、前記セグメント取得要求に対応する前記セグメントストリームに前記ProxyChangeEventを挿入して前記端末装置に供給することができる。 The acquisition unit can acquire the location information stored as a query parameter in a segment acquisition request transmitted for the terminal device to request unicast distribution of the segment stream of the content, and the supply unit The ProxyChangeEvent may be inserted into the segment stream corresponding to the segment acquisition request and supplied to the terminal device.
　前記取得部は、XMLHttpRequestに格納されている前記ロケーション情報を取得することができ、前記供給部は、前記XMLHttpRequestに対するレスポンスとして前記ProxyChangeEventを前記端末装置に供給することができる。 The acquisition unit may acquire the location information stored in an XML HttpRequest, and the supply unit may supply the ProxyChange Event to the terminal device as a response to the XML Http Request.
　前記ロケーション情報は、GPS位置情報またはセルＩＤとすることができる。 The location information may be GPS location information or a cell ID.
　前記プロキシサーバ装置は、ユニキャスト配信される前記コンテンツのセグメントストリームをキャッシングするとともに、マルチキャスト配信される前記コンテンツのFLUTEストリームもキャッシングすることができる。 The proxy server apparatus can cache segment streams of the unicast-distributed content, and can also cache a FLUTE stream of the multicast-distributed content.
　本開示の第１の側面である情報処理方法は、サーバ装置の情報処理方法において、前記サーバ装置による、適応的ストリーミング技術に従って配信されるコンテンツを受信する端末装置が送信したロケーション情報を取得する取得ステップと、前記ロケーション情報に基づいて前記端末装置の近傍に前記端末装置が接続可能なプロキシサーバ装置が存在するか否かを判定し、前記プロキシサーバ装置が存在する場合、前記端末装置が前記プロキシサーバ装置に優先的に接続するように前記端末装置のプロキシサーバ接続設定を変更するスクリプトを含むProxyChangeEventを生成する生成ステップと、生成された前記ProxyChangeEventを前記端末装置に供給する供給ステップとを含む。 In an information processing method according to a first aspect of the present disclosure, in the information processing method of a server device, acquisition is performed by the server device for acquiring location information transmitted by a terminal device that receives content distributed according to adaptive streaming technology. And determining whether there is a proxy server apparatus to which the terminal apparatus can be connected in the vicinity of the terminal apparatus based on the location information and the terminal apparatus determines the proxy server apparatus if the proxy server apparatus exists. The method includes a generation step of generating a ProxyChangeEvent including a script for changing a proxy server connection setting of the terminal device to preferentially connect to a server device, and a supply step of supplying the generated ProxyChange Event to the terminal device.
　本開示の第１の側面であるプログラムは、コンピュータを、適応的ストリーミング技術に従って配信されるコンテンツを受信する端末装置が送信したロケーション情報を取得する取得部と、前記ロケーション情報に基づいて前記端末装置の近傍に前記端末装置が接続可能なプロキシサーバ装置が存在するか否かを判定し、前記プロキシサーバ装置が存在する場合、前記端末装置が前記プロキシサーバ装置に優先的に接続するように前記端末装置のプロキシサーバ接続設定を変更するスクリプトを含むProxyChangeEventを生成する生成部と、生成された前記ProxyChangeEventを前記端末装置に供給する供給部として機能させる。 A program according to a first aspect of the present disclosure includes a computer, an acquisition unit for acquiring location information transmitted by a terminal that receives content distributed according to adaptive streaming technology, and the terminal based on the location information. It is determined whether or not there is a proxy server device to which the terminal device can be connected in the vicinity of the terminal device, and when the proxy server device is present, the terminal device is preferentially connected to the proxy server device. It functions as a generation unit that generates ProxyChangeEvent including a script for changing the proxy server connection setting of the device, and a supply unit that supplies the generated ProxyChangeEvent to the terminal device.
　本開示の第１の側面においては、適応的ストリーミング技術に従って配信されるコンテンツを受信する端末装置が送信したロケーション情報が取得され、前記ロケーション情報に基づいて前記端末装置の近傍に前記端末装置が接続可能なプロキシサーバ装置が存在するか否かが判定され、前記プロキシサーバ装置が存在する場合、前記端末装置が前記プロキシサーバ装置に優先的に接続するように前記端末装置のプロキシサーバ接続設定を変更するスクリプトを含むProxyChangeEventが生成され、生成された前記ProxyChangeEventが前記端末装置に供給される。 In the first aspect of the present disclosure, location information transmitted by a terminal that receives content distributed according to adaptive streaming technology is acquired, and the terminal is connected in the vicinity of the terminal based on the location information. It is determined whether or not a possible proxy server device exists, and when the proxy server device exists, the proxy server connection setting of the terminal device is changed so that the terminal device preferentially connects to the proxy server device ProxyChangeEvent including a script to be generated is generated, and the generated ProxyChangeEvent is supplied to the terminal device.
　本開示の第２の側面である端末装置は、適応的ストリーミング技術に従って配信されるコンテンツを受信する端末装置において、自身のロケーション情報を取得して送信する送信部と、前記ロケーション情報の送信に応じて供給されるProxyChangeEventに含まれるスクリプトを実行することによりプロキシサーバ接続設定を変更するスクリプト実行部とを備える。 A terminal device according to a second aspect of the present disclosure is a terminal device that receives content distributed according to an adaptive streaming technique, a transmitting unit that acquires and transmits its own location information, and transmits the location information. And a script execution unit configured to change the proxy server connection setting by executing a script included in ProxyChangeEvent supplied.
　前記送信部は、前記コンテンツのセグメントストリームのユニキャスト配信を要求するためのセグメント取得要求にクエリパラメータとして前記ロケーション情報を格納して送信することができ、前記スクリプト実行部は、前記セグメント取得要求に応じてユニキャスト配信された前記セグメントストリームに挿入されている前記ProxyChangeEventに含まれる前記スクリプトを実行することによりプロキシサーバ接続設定を変更することができる。 The transmitting unit may store and transmit the location information as a query parameter in a segment acquisition request for requesting unicast distribution of the segment stream of the content, and the script execution unit may transmit the segment acquisition request to the segment acquisition request. Accordingly, proxy server connection settings can be changed by executing the script included in the ProxyChange Event inserted in the segment stream unicasted.
　前記送信部は、前記ロケーション情報をXMLHttpRequestに格納して送信することができ、前記スクリプト実行部は、前記XMLHttpRequestに対するレスポンスとして送信された前記ProxyChangeEventに含まれる前記スクリプトを実行することによりプロキシサーバ接続設定を変更することができる。 The transmission unit can store the location information in XML Http Request and transmit it, and the script execution unit executes the script included in the ProxyChange Event transmitted as a response to the XML Http Request to set a proxy server connection. Can be changed.
　前記ロケーション情報は、GPS位置情報またはセルＩＤとすることができる。 The location information may be GPS location information or a cell ID.
　本開示の第２の側面においては、自身のロケーション情報が取得されて送信され、前記ロケーション情報の送信に応じて供給されるProxyChangeEventに含まれるスクリプトが実行されることによりプロキシサーバ接続設定が変更される。 In the second aspect of the present disclosure, the proxy server connection setting is changed by acquiring location information of its own and transmitting it, and executing a script included in ProxyChangeEvent supplied in response to the transmission of the location information. Ru.
　本開示の第３の側面であるコンテンツ供給システムは、適応的ストリーミング技術に従ってコンテンツのストリームを配信するコンテンツ供給装置と、前記ストリームを受信する端末装置と、サーバ装置とを備えるコンテンツ供給システムにおいて、前記サーバ装置が、前記端末装置が送信したロケーション情報を取得する取得部と、前記ロケーション情報に基づいて前記端末装置の近傍に前記端末装置が接続可能なプロキシサーバ装置が存在するか否かを判定し、前記プロキシサーバ装置が存在する場合、前記端末装置が前記プロキシサーバ装置に優先的に接続するように前記端末装置のプロキシサーバ接続設定を変更するスクリプトを含むProxyChangeEventを生成する生成部と、生成された前記ProxyChangeEventを前記端末装置に供給する供給部とを備える。また、前記端末装置が、自身の前記ロケーション情報を取得して送信する送信部と、前記ロケーション情報の送信に応じて前記サーバ装置から供給される前記ProxyChangeEventに含まれるスクリプトを実行することによりプロキシサーバ接続設定を変更するスクリプト実行部とを備える。 A content supply system according to a third aspect of the present disclosure is a content supply system including a content supply apparatus for distributing a stream of content according to adaptive streaming technology, a terminal apparatus for receiving the stream, and a server apparatus. The server device determines whether there is a proxy server device to which the terminal device can be connected in the vicinity of the terminal device based on the acquisition unit that acquires the location information transmitted by the terminal device and the location information. A generation unit that generates a ProxyChange Event including a script for changing the proxy server connection setting of the terminal device so that the terminal device preferentially connects to the proxy server device when the proxy server device is present; Supply unit for supplying the proxy Change Event to the terminal device Equipped with a. In addition, the terminal device performs a proxy server by executing a script included in the ProxyChange Event supplied from the server device in response to the transmission of the location information, and a transmitting unit that acquires and transmits the location information of the terminal device. And a script execution unit that changes connection settings.
　本開示の第３の側面においては、サーバ装置により、適応的ストリーミング技術に従って配信されるコンテンツを受信する端末装置が送信したロケーション情報が取得され、前記ロケーション情報に基づいて前記端末装置の近傍に前記端末装置が接続可能なプロキシサーバ装置が存在するか否かが判定され、前記プロキシサーバ装置が存在する場合、前記端末装置が前記プロキシサーバ装置に優先的に接続するように前記端末装置のプロキシサーバ接続設定を変更するスクリプトを含むProxyChangeEventが生成され、生成された前記ProxyChangeEventが前記端末装置に供給される。また、端末装置により、自身のロケーション情報が取得されて送信され、前記ロケーション情報の送信に応じて供給されるProxyChangeEventに含まれるスクリプトが実行されることによりプロキシサーバ接続設定が変更される。 In a third aspect of the present disclosure, location information transmitted by a terminal device that receives content distributed according to adaptive streaming technology is acquired by the server device, and the server device obtains the location information in the vicinity of the terminal device based on the location information. It is determined whether there is a proxy server device to which a terminal device can be connected, and if the proxy server device exists, the proxy server of the terminal device is configured to preferentially connect the terminal device to the proxy server device A ProxyChangeEvent including a script for changing a connection setting is generated, and the generated ProxyChangeEvent is supplied to the terminal device. In addition, the terminal apparatus acquires and transmits its own location information, and executes a script included in ProxyChangeEvent supplied in response to the transmission of the location information, thereby changing the proxy server connection setting.
　本開示の第１の側面によれば、端末装置のプロキシサーバ接続設定を変更することができる。 According to the first aspect of the present disclosure, the proxy server connection setting of the terminal device can be changed.
　本開示の第２の側面によれば、自身にとって最適なプロキシサーバに接続することができる。 According to the second aspect of the present disclosure, it is possible to connect to a proxy server that is optimal for itself.
　本開示の第３の側面によれば、端末装置を最適なプロキシサーバに接続させることにより、効率の高いストリーミングサービスを提供することができる。 According to the third aspect of the present disclosure, an efficient streaming service can be provided by connecting a terminal device to an optimal proxy server.
従来のコンテンツ供給システムの構成の一例を示すブロック図である。It is a block diagram which shows an example of a structure of the conventional content supply system. 本開示を適用したコンテンツ供給システムの構成例を示すブロック図である。It is a block diagram showing an example of composition of a contents supply system to which this indication is applied. 最適化プロキシサーバの構成例を示すブロック図である。It is a block diagram which shows the structural example of an optimization proxy server. コンテンツ供給装置の処理を説明するフローチャートである。It is a flow chart explaining processing of a contents supply device. セグメントリクエストを用いてロケーション情報を送信する場合のイベント通知処理を説明するフローチャートである。It is a flowchart explaining the event notification process in the case of transmitting location information using a segment request. セグメントリクエストを用いてロケーション情報を送信する処理を説明するフローチャートである。It is a flowchart explaining the process which transmits location information using a segment request. ProxyChangeEventのEventメッセージの一例を示す図である。It is a figure which shows an example of the Event message of ProxyChangeEvent. XMLHttpRequestを用いてロケーション情報を送信する場合のイベント通知処理を説明するフローチャートである。It is a flowchart explaining the event notification process in the case of transmitting location information using XMLHttpRequest. コンピュータの構成例を示すブロック図である。It is a block diagram showing an example of composition of a computer.
　以下、本開示を実施するための最良の形態（以下、実施の形態と称する）について説明するが、その前に本開示の概要について説明する。 Hereinafter, the best mode for carrying out the present disclosure (hereinafter, referred to as an embodiment) will be described, but before that, an outline of the present disclosure will be described.
　本開示は、受信側の端末装置がコンテンツのストリームを受信、再生するときに、複数存在するプロキシサーバの中から自身にとって最適なものに接続することにより、それまで受信、再生していたコンテンツと同一内容のストリームをより高効率に、または同一内容であってより高品質なストリームを受信できるようにするものである。具体的には、以下の２種類のケース１，２が想定される。 In the present disclosure, when a terminal device on the receiving side receives and plays a stream of content, the content that has been received and played so far by connecting to one that is most suitable for itself from among a plurality of proxy servers, It makes it possible to receive streams with the same content more efficiently or with the same content and higher quality. Specifically, the following two types of cases 1 and 2 are assumed.
　ケース１
　端末装置が携帯通信網((e)MBMS等)を利用してユニキャスト配信されるストリームを受信、再生しているとき、その携帯通信網の同一セルに多数の端末装置が接続することにより通信に輻輳が生じることがある。このような場合、端末装置が携帯通信網の利用を中止し、近傍に位置するwifiアクセスポイントを介してプロキシサーバに接続すれば、より高効率にストリームを受信できる。この場合、接続するプロキシサーバは、ユニキャスト配信のストリーム、またはマルチキャスト配信のストリームの少なくとも一方をキャッシングするものであればよい。なお、プロキシサーバから端末装置にストリームを配信するときにはユニキャスト配信を想定するが、今後、wifiを用いたマルチキャスト配信が一般化した場合にはこれを用いてもよい。 Case 1
When a terminal device receives and reproduces a stream to be unicast-distributed using a mobile communication network ((e) MBMS etc.), communication is performed by connecting a number of terminal devices to the same cell of the mobile communication network Congestion may occur. In such a case, if the terminal device stops using the mobile communication network and connects to the proxy server via the wifi access point located in the vicinity, the stream can be received more efficiently. In this case, the connecting proxy server may be any server that caches at least one of the unicast delivery stream and the multicast delivery stream. In addition, although unicast delivery is assumed when delivering a stream from a proxy server to a terminal device, this may be used when multicast delivery using wifi is generalized in the future.
　ケース２
　端末装置が通信速度が安定している携帯通信網を利用してマルチキャスト配信されるストリームを受信、再生しているが、携帯通信網におけるマルチキャストリソースの制限によってビットレートが低いストリームしか配信できないことがあり、このような場合、近傍に位置するwifiアクセスポイントを介してプロキシサーバに接続すれば、プロキシサーバから端末装置により高品質のストリームを配信できる。この場合、接続するプロキシサーバは、ユニキャスト配信のストリーム、またはマルチキャスト配信のストリームの少なくとも一方をキャッシングするものであればよい。なお、プロキシサーバから端末装置にストリームを配信するときにはユニキャスト配信を想定するが、今後、wifiを用いたマルチキャスト配信が一般化した場合にはこれを用いてもよい。 Case 2
The terminal device receives and reproduces a stream distributed by multicast using a mobile communication network whose communication speed is stable, but can only distribute streams with a low bit rate due to the limitation of multicast resources in the mobile communication network In such a case, a high quality stream can be distributed by the terminal device from the proxy server by connecting to the proxy server via the wifi access point located in the vicinity. In this case, the connecting proxy server may be any server that caches at least one of the unicast delivery stream and the multicast delivery stream. In addition, although unicast delivery is assumed when delivering a stream from a proxy server to a terminal device, this may be used when multicast delivery using wifi is generalized in the future.
　なお、端末装置にとって最適なプロキシサーバを通知する方法は、以下の２種類のケースＡ，Ｂが想定される。 In addition, the following two types of cases A and B are assumed as a method of notifying a proxy server optimal for the terminal device.
　ケースＡ
　端末装置が自身のロケーション情報（例えば、GPS位置情報や携帯通信網のセルＩＤ）をストリーム要求に格納して送信する。プロキシサーバ側は、最適なプロキシサーバを特定し、そのプロキシサーバに接続するようプロクシ接続設定を変更するスクリプトを通知する。スクリプトを通知する方法としては、DASH inband eventを用いたり、XMLHttpRequestを用いたり、ServerSentEventを用いたり、ATSC2.0のトリガを用いたりすることができる。 Case A
The terminal device stores its own location information (for example, GPS location information and cell ID of a mobile communication network) in a stream request and transmits it. The proxy server side identifies a suitable proxy server, and notifies a script that changes the proxy connection setting to connect to the proxy server. As a method of notifying a script, DASH inband event, XML Http Request, ServerSentEvent, or ATSC 2.0 trigger can be used.
　ケースＢ
　端末装置がwifiアクセスポイントへの接近を検知してアクセスし、Ｌ２認証処理後にDHCPなどによりプロキシサーバのアドレスを取得する。そのプロキシサーバが、端末装置で受信、再生中のストリームをキャッシングしている(または優先的にキャッシュしてくれる可能性がある)場合には、そのプロキシサーバに接続するようプロクシ接続設定を変更する。また、そのプロキシサーバが、端末装置で受信、再生中のストリームをキャッシングしていない場合でも、現在の受信を継続するよりも、例えばコスト的にリーズナブルでありパフォーマンスが期待以上であればそのプロキシサーバに接続するようプロクシ接続設定を変更する。 Case B
The terminal device detects and accesses the access to the wifi access point, and acquires an address of the proxy server by DHCP after the L2 authentication process. If the proxy server is caching (or possibly giving priority to caching) the stream being received or played at the terminal device, change the proxy connection setting to connect to the proxy server . In addition, even if the proxy server is not caching the stream being received or reproduced by the terminal device, the proxy server is reasonable if, for example, the cost is reasonable and the performance is higher than expected than continuing the current reception. Change the proxy connection settings to connect to
＜コンテンツ供給システムの構成例＞
　図２は、本開示の実施の形態であるコンテンツ供給システムの構成例を示している。 <Example of configuration of content supply system>
FIG. 2 shows a configuration example of a content supply system according to an embodiment of the present disclosure.
　このコンテンツ供給システム５０は、複数のコンテンツ供給装置６０－１乃至６０－Ｋ、ネットワーク５１上に構築されたCDN５２に設けられたプロキシサーバ１３、最適化プロキシサーバ５３、およびロケーション監視サーバ５４、並びに多数の端末装置７０－１乃至８０－Ｎから構成される。 The content supply system 50 includes a plurality of content supply devices 60-1 to 60-K, a proxy server 13 provided in a CDN 52 built on a network 51, an optimization proxy server 53, a location monitoring server 54, and a number of them. Terminal devices 70-1 to 80-N.
　コンテンツ供給装置６０－１乃至６０－Ｋと端末装置７０－１乃至８０－Ｎは、ネットワーク５１に接続されている。以下、コンテンツ供給装置６０－１乃至６０－Ｋを個々に区別する必要がない場合、単にコンテンツ供給装置６０と称する。端末装置７０－１乃至８０－Ｎについても同様とする。 The content supply devices 60-1 to 60-K and the terminal devices 70-1 to 80-N are connected to the network 51. Hereinafter, 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 same applies to the terminal devices 70-1 to 80-N.
　ネットワーク５１は、インターネットに代表される双方向通信網、地上波放送網や衛星波放送網などの片方向通信網、双方向通信を行なうインタラクションチャネルと片方向通信を行なうブロードキャスト・マルチキャストチャネルを有する(e)MBMSなどの携帯電話通信網などを包含する。 The network 51 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.
　ネットワーク５１上のCDN５２には、従来のプロキシサーバ１３、最適化プロキシサーバ５３、およびロケーション監視サーバ５４がそれぞれ複数存在する。 The CDN 52 on the network 51 includes a plurality of conventional proxy servers 13, an optimization proxy server 53, and a plurality of location monitoring servers 54, respectively.
　最適化プロキシサーバ５３は、CDN５２を介してユニキャスト配信またはマルチキャスト配信されるMPDおよびストリームをキャッシングする。また、最適化プロキシサーバ５３は、端末装置７０からのMPD取得要求およびセグメント取得要求に応じ、対応するMPDやセグメントストリームのファイルをキャッシングしている場合には、それを要求元に配信する。キャッシングしていない場合、MPD取得要求やセグメント取得要求をコンテンツ供給装置６０に中継する。 The optimization proxy server 53 caches MPDs and streams that are unicasted or multicasted via the CDN 52. Further, in response to the MPD acquisition request and the segment acquisition request from the terminal device 70, the optimization proxy server 53 delivers the corresponding MPD or segment stream file to the request source if it is caching. If caching is not performed, the MPD acquisition request and the segment acquisition request are relayed to the content supply device 60.
　なお、最適化プロキシサーバ５３にて、端末装置７０からのMPD取得要求およびセグメント取得要求をモニタリングして解析することにより、端末装置７０の受信能力、デコード能力、ユーザの嗜好、状態などを類推してデータベース化し、そのデータベースに基づいて、取得要求され得るMPDおよびセグメントストリームを優先的にキャッシングするようにしてもよい。 The optimization proxy server 53 monitors and analyzes the MPD acquisition request and segment acquisition request from the terminal device 70 to estimate the reception capability, decoding capability, user preference, status, etc. of the terminal device 70. A database may be created, and MPDs and segment streams that may be requested to be obtained may be preferentially cached based on the database.
　さらに、最適化プロキシサーバ５３は、セグメント取得要求に含まれるロケーション情報の解析をロケーション監視サーバ５４に依頼し、必要に応じて、Proxy Change Eventをセグメントレスポンスに挿入して要求元に配信する。 Furthermore, the optimization proxy server 53 requests the location monitoring server 54 to analyze the location information included in the segment acquisition request, inserts a Proxy Change Event into the segment response, and delivers it to the request source as necessary.
　ロケーション監視サーバ５４は、最適化プロキシサーバ５３からの依頼に応じ、セグメント取得要求に含まれるロケーション情報に基づいて端末装置７０の位置を判定する。そして、端末装置７０の近傍に最適化プロキシサーバ５３がある場合、その最適化プロキシサーバ５３に優先的に接続するようにプロキシサーバ接続設定を変更するProxy Change Eventを生成して最適化プロキシサーバ５３に供給する。 The location monitoring server 54 determines the position of the terminal device 70 based on the location information included in the segment acquisition request in response to a request from the optimization proxy server 53. Then, when there is an optimization proxy server 53 near the terminal device 70, a Proxy Change Event is generated to change the proxy server connection setting so as to preferentially connect to the optimization proxy server 53, and the optimization proxy server 53 is generated. Supply to
　なお、最適化プロキシサーバ５３とロケーション監視サーバ５４とは一体的に構成することができる。 The optimization proxy server 53 and the location monitoring server 54 can be integrally configured.
　コンテンツ供給装置６０は、チャネルストリーマ６１、DASHセグメンタ６２、FLUTEストリーマ６３、MPDジェネレータ６４、WEBサーバ６５、およびマルチキャストサーバ６６を備える。 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.
　チャネルストリーマ６１は、端末装置７０に配信するためのコンテンツのソースデータを管理しており、同一内容の該ソースデータからビットレートの異なる複数のストリーミングデータを生成する。さらに、チャネルストリーマ６１は、生成したストリーミングデータをDASHセグメンタ６２に出力する。 The channel streamer 61 manages source data of content to be distributed to the terminal device 70, 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.
　DASHセグメンタ６２は、ストリーミングデータを時間的にピリオドに区切り、さらにセグメント(segment)に分割することにより、fragmentedMP4などのセグメントストリームを生成してFLUTEストリーマ６３およびWEBサーバ６５に出力する。さらに、DASHセグメンタ６２は、生成したセグメントストリームのファイルの供給元となるWEBサーバ６５のアドレス情報などを含むメタデータをMPDジェネレータ６４に通知する。 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 FLUTE streamer 63 and the WEB server 65. 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.
　MPDジェネレータ６４は、端末装置７０がセグメントストリームを受信するために必要なMPDを生成してFLUTEストリーマ６３およびWEBサーバ６５に出力する。 The MPD generator 64 generates an MPD necessary for the terminal device 70 to receive the segment stream, and outputs the MPD to the FLUTE streamer 63 and the WEB server 65.
　FLUTEストリーマ６３は、DASHセグメンタ６２から入力されるセグメントストリームをFLUTEパケットに格納することによりFLUTEストリームを生成してマルチキャストサーバ６６に出力する。また、FLUTEストリーマ６３は、MPDジェネレータ６４から入力されるMPDをマルチキャストサーバ６６に出力する。 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.
　WEBサーバ６５は、端末装置７０からのMPD取得要求（HTTPリクエスト）に応じ、MPDジェネレータ６４から入力されるMPDを、CDN５２を介して要求元の端末装置７０にHTTPユニキャスト配信する。また、WEBサーバ６５は、端末装置７０からのセグメント取得要求（HTTPリクエスト）に応じ、DASHセグメンタ６２から入力されるセグメントストリームのファイルを、CDN５２を介して要求元の端末装置７０にHTTPユニキャスト配信する。 In response to the MPD acquisition request (HTTP request) from the terminal device 70, the WEB server 65 performs HTTP unicast distribution of the MPD input from the MPD generator 64 to the request source terminal device 70 via the CDN 52. In addition, the WEB server 65 distributes the file of the segment stream input from the DASH segmenter 62 to the terminal device 70 of the request source via the CDN 52 in response to the segment acquisition request (HTTP request) from the terminal device 70. Do.
　マルチキャストサーバ６６は、FLUTEストリーマ６３からのMPDを、CDN５２を介してFLUTEマルチキャスト配信する。また、マルチキャストサーバ６６は、FLUTEストリーマ６３からのFLUTEストリームを、CDN５２を介してFLUTEマルチキャスト配信する。なお、FLUTEマルチキャスト配信のポータルチャネルの周知には、例えば、(e)MBMSのUSD、OMA-ESGなどが利用される。 The multicast server 66 distributes the MPD from the FLUTE streamer 63 by FLUTE multicast via the CDN 52. Also, the multicast server 66 distributes the FLUTE stream from the FLUTE streamer 63 by FLUTE multicast via the CDN 52. Note that, for example, (e) MBMS's USD, OMA-ESG, etc. are used to make portal channels of FLUTE multicast distribution known.
　端末装置７０は、受信再生部７１、ロケーション通知部７１、およびスクリプト実行部７３を備える。 The terminal device 70 includes a reception and reproduction unit 71, a location notification unit 71, and a script execution unit 73.
　受信再生部７１は、MPDを取得し、MPDに基づいてセグメントストリームやFLUTEストリームを受信、再生する。 The reception and reproduction unit 71 acquires the MPD, and receives and reproduces the segment stream and the FLUTE stream based on the MPD.
　ロケーション通知部７２は、例えば、GPS位置情報やセルＩＤなどのロケーション情報を取得し、取得したロケーション情報をクエリパラメータとしてセグメント取得要求に含めることにより最適化プロキシサーバ５３に通知する。また、ロケーション通知部７２は、取得したロケーション情報をXMLHttpRequestに含めてロケーション監視サーバ５４に通知する。 The location notification unit 72 acquires location information such as GPS position information and cell ID, and notifies the optimization proxy server 53 by including the acquired location information as a query parameter in the segment acquisition request. In addition, the location notification unit 72 includes the acquired location information in the XML Http Request and notifies the location monitoring server 54 of it.
　スクリプト実行部７３は、Proxy Change Eventとして通知される、プロキシ接続設定を変更するためのスクリプトを実行する。 The script execution unit 73 executes a script for changing proxy connection settings, which is notified as a Proxy Change Event.
＜最適化プロキシサーバ５３の詳細な構成例＞
　次に、図３は、最適化プロキシサーバ５３の詳細な構成例を示している。 <Detailed Configuration Example of Optimization Proxy Server 53>
Next, FIG. 3 shows a detailed configuration example of the optimization proxy server 53.
　最適化プロキシサーバ５３は、モニタリング代行部８１、チューナ部８２、キャッシング部８３、および解析依頼部８４を備える。 The optimization proxy server 53 includes a monitoring agent unit 81, a tuner unit 82, a caching unit 83, and an analysis request unit 84.
　モニタリング代行部８１は、ユニキャスト配信されるMPDおよびセグメントストリームをモニタリングしてキャッシング部８３に出力してキャッシングさせる。また、モニタリング代行部８１は、端末装置７０からのMPD取得要求およびセグメント取得要求をモニタリングし、要求されていているMPDやセグメントストリームがキャッシング部８３にキャッシングされている場合、それをキャッシング部８３から読み出して要求元にユニキャスト配信する。キャッシングされていない場合、MPD取得要求やセグメント取得要求をWEBサーバ６５に中継し、これに応じてユニキャスト配信されるMPDやセグメントストリームもモニタリングしてキャッシング部８３にキャッシングさせる。さらに、モニタリング代行部８１は、モニタリングしたセグメント取得要求に含まれるロケーション情報を解析依頼部８４に出力する。 The monitoring proxy unit 81 monitors the MPDs and segment streams to be unicast-distributed, and outputs them to the caching unit 83 for caching. Also, the monitoring agent unit 81 monitors the MPD acquisition request and segment acquisition request from the terminal device 70, and if the requested MPD and segment stream are cached in the caching unit 83, the caching unit 83 Read and deliver to the request source by unicast. If not cached, the MPD acquisition request and the segment acquisition request are relayed to the WEB server 65, and the MPD and segment stream to be unicast-distributed in response to this are also monitored and the caching unit 83 is made to cache. Furthermore, the monitoring agent unit 81 outputs the location information included in the monitored segment acquisition request to the analysis request unit 84.
　チューナ部８２は、FLUTEマルチキャスト配信されるMPDやFLUTEストリームを受信してキャッシング部８３に出力する。キャッシング部８３は、モニタリング代行部８１から入力されるMPDおよびセグメントストリームのファイルをキャッシングする。また、キャッシング部８３は、チューナ部８２から入力されるMPDやFLUTEストリームをキャッシングする。 The tuner unit 82 receives an MPD or FLUTE stream distributed by FLUTE multicast and outputs the stream to the caching unit 83. The caching unit 83 caches the MPD and segment stream files input from the monitoring proxy unit 81. The caching unit 83 also caches the MPD and FLUTE streams input from the tuner unit 82.
　解析依頼部８４は、モニタリング代行部８１から入力される、セグメント取得要求に含まれていたロケーション情報をロケーション監視サーバ５４に通知して解析を依頼する。また、ロケーション監視サーバ５４から解析の結果として供給されるProxy Change Eventをモニタリング代行部８１に出力し、セグメント取得要求に対応するレスポンスとしてのセグメントストリームにProxy Change Eventを挿入させて要求元にユニキャスト配信させる。 The analysis request unit 84 notifies the location monitoring server 54 of the location information included in the segment acquisition request, which is input from the monitoring proxy unit 81, and requests analysis. Also, the Proxy Change Event supplied as a result of analysis from the location monitoring server 54 is output to the monitoring agent unit 81, and the Proxy Change Event is inserted into the segment stream as a response to the segment acquisition request, and unicasted to the request source. Let it be delivered.
＜コンテンツ供給システム５０の動作＞
　次に、コンテンツ供給システム５０の動作について説明する。 <Operation of Content Supply System 50>
Next, the operation of the content supply system 50 will be described.
＜コンテンツ配信処理の説明＞
　図４は、コンテンツ供給装置６０によるコンテンツ配信処理を説明するフローチャートである。 <Description of content distribution process>
FIG. 4 is a flowchart for explaining the content distribution process by the content supply apparatus 60.
　ステップＳ１において、チャネルストリーマ６１は、コンテンツのソースデータからビットレートの異なる複数のストリーミングデータを生成し、DASHセグメンタ６２に出力する。 In step S 1, 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.
　ステップＳ２において、DASHセグメンタ６２は、ストリーミングデータからfragmentedMP4などのセグメントストリームを生成してFLUTEストリーマ６３およびWEBサーバ６５に出力する。また、DASHセグメンタ６２は、生成したセグメントストリームの供給元のURLなどをMPDジェネレータ６４に通知する。 In 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.
　ステップＳ３において、FLUTEストリーマ６３は、セグメントストリームをFLUTEパケットに格納することによりFLUTEストリームを生成してマルチキャストサーバ６６に出力する。ステップＳ４において、MPDジェネレータ６４は、MPDを生成してFLUTEストリーマ６３およびWEBサーバ６５に出力する。 In 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. In step S4, the MPD generator 64 generates an MPD and outputs it to the FLUTE streamer 63 and the WEB server 65.
　ステップＳ５において、FLUTEストリーマ６３は、MPDをマルチキャストサーバ６６に出力する。マルチキャストサーバ６６は、MPDをCDN５２を介してFLUTEマルチキャスト配信する。 In 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 52.
　ステップＳ６において、WEBサーバ６５は、端末装置７０からMPD取得要求（HTTPリクエスト）があった場合、それに応じてMPDをCDN５２を介して要求元にHTTPユニキャスト配信する。 In step S6, when there is an MPD acquisition request (HTTP request) from the terminal device 70, the WEB server 65 distributes the MPD to the request source via the CDN 52 in response to the request.
　ステップＳ７において、マルチキャストサーバ６６は、FLUTEストリームをCDN５２を介してFLUTEマルチキャスト配信する。ステップＳ８において、WEBサーバ６５は、端末装置７０からセグメント取得要求（HTTPリクエスト）があった場合、それに応じてセグメントストリームをCDN５２を介して要求元にHTTPユニキャスト配信する。以上で、コンテンツ供給装置６０によるコンテンツ供給処理の説明を終了する。 In step S7, the multicast server 66 distributes FLUTE streams by FLUTE multicast via the CDN 52. In step S8, when there is a segment acquisition request (HTTP request) from the terminal device 70, the WEB server 65 distributes the segment stream to the request source via the CDN 52 according to the request. This is the end of the description of the content supply processing by the content supply apparatus 60.
＜イベント通知処理の説明＞
　次に、図５は、端末装置７０がセグメント取得要求（セグメントリクエスト）を用いてロケーション情報を送信する場合のイベント通知処理を説明するフローチャートである。このイベント処理は、端末装置７０がユニキャスト配信のストリームを受信、再生する場合などに適用される。 <Description of event notification process>
Next, FIG. 5 is a flowchart illustrating an event notification process when the terminal device 70 transmits location information using a segment acquisition request (segment request). This event processing is applied when the terminal device 70 receives and reproduces a stream of unicast distribution.
　ステップＳ１１として、端末装置７０がMPD取得要求を送信すると、ステップＳ２１において、最適化プロキシサーバ５３のモニタリング代行部８１が該MPD取得要求をモニタリングする。そして要求されていているMPDがキャッシング部８３にキャッシングされている場合、そのMPDをキャッシング部８３から読み出して要求元にユニキャスト配信する。キャッシングされていない場合、MPD取得要求をWEBサーバ６５に中継し、これに応じてユニキャスト配信されるMPDをキャッシング部８３にキャッシングさせる。さらに、モニタリング代行部８１は、MPD取得要求に対するMPDリダイレクションとしてのクエリストリングで、この後に端末装置７０から送信されるセグメント取得要求に付加するクエリパラメータの構成を規定するディスクリプションスキームuriを指定する。なお、MPDリダイレクションではなく、MPD内にディスクリプションスキームuriを指定するようにしてもよい。ディスクリプションスキームuriにて規定するクエリパラメータの内容は、いまの場合、端末装置７０のロケーション情報である。 In step S11, when the terminal device 70 transmits an MPD acquisition request, the monitoring agent unit 81 of the optimization proxy server 53 monitors the MPD acquisition request in step S21. When the requested MPD is cached by the caching unit 83, the MPD is read from the caching unit 83 and unicasted to the request source. If not cached, the MPD acquisition request is relayed to the WEB server 65, and the caching unit 83 is made to cache the MPD to be unicast-distributed in response to this. Furthermore, the monitoring proxy unit 81 designates a description scheme uri that defines the configuration of the query parameter to be added to the segment acquisition request transmitted from the terminal device 70 later, using a query string as MPD redirection for the MPD acquisition request. Note that the description scheme uri may be specified in the MPD instead of the MPD redirection. The contents of the query parameter defined in the description scheme uri are the location information of the terminal device 70 in this case.
　ステップＳ１２において、端末装置７０は、ユニキャスト配信されたMPDとMPDリダイレクションを受信する。 In step S12, the terminal device 70 receives the unicast-distributed MPD and MPD redirection.
　ここで、図６は、MPD取得要求（MPDリクエスト）とそれに対するMPDリダイレクション、この後のセグメント取得要求（セグメントリクエスト）とそれに対応するセグメントレスポンスの関係を示している。同図に示されるように、MPDリダイレクションを受信した後のロケーション通知部７２は、ディスクリプションスキームuriに従い、ロケーション情報を取得し、これ以降に送信されるセグメントリクエストにクエリパラメータとしてロケーション情報（図６の"geoLocation-1"など）を挿入することになる。 Here, FIG. 6 shows the relationship between the MPD acquisition request (MPD request), the MPD redirection therefor, the subsequent segment acquisition request (segment request), and the corresponding segment response. As shown in the figure, the location notification unit 72 after receiving the MPD redirection acquires location information according to the description scheme uri, and uses the location information as a query parameter in the segment request transmitted thereafter (FIG. 6). Would like to insert "geoLocation-1" etc.).
　図５に戻る。ステップＳ１３において、端末装置７０は、クエリパラメータとしてロケーション情報が挿入されたセグメント取得要求を送信すると、ステップＳ２２において、最適化プロキシサーバ５３のモニタリング代行部８１が該セグメント取得要求をモニタリングし、セグメント取得要求に含まれるロケーション情報を解析依頼部８４に出力する。ステップＳ２３において、解析依頼部８４は、モニタリング代行部８１から入力されたロケーション情報をロケーション監視サーバ５４に通知して解析を依頼する。 Return to FIG. In step S13, when the terminal device 70 transmits a segment acquisition request into which location information has been inserted as a query parameter, in step S22, the monitoring proxy unit 81 of the optimization proxy server 53 monitors the segment acquisition request and acquires a segment. The location information included in the request is output to the analysis request unit 84. In step S23, the analysis request unit 84 notifies the location monitoring server 54 of the location information input from the monitoring agent unit 81, and requests analysis.
　ステップＳ３１において、ロケーション監視サーバ５４は、最適化プロキシサーバ５３の解析依頼部８４からの依頼に応じ、ロケーション情報に基づいて端末装置７０の位置を判定し、端末装置７０の近傍に接続先として変更できる最適化プロキシサーバ５３がある場合、その最適化プロキシサーバ５３に優先的に接続するようにプロキシサーバ接続設定を変更するProxy Change Eventを生成して解析依頼部８４に供給する。 In step S31, the location monitoring server 54 determines the position of the terminal device 70 based on the location information in response to a request from the analysis request unit 84 of the optimization proxy server 53, and changes it as a connection destination near the terminal device 70. If there is an optimization proxy server 53 that can do this, a Proxy Change Event for changing the proxy server connection setting so as to connect to the optimization proxy server 53 with priority is generated and supplied to the analysis request unit 84.
　ステップＳ２４において、解析依頼部８４は、ロケーション監視サーバ５４から解析の結果として供給されたProxy Change Eventをモニタリング代行部８１に出力し、セグメント取得要求に対応するレスポンスとしてのセグメントストリームにProxy Change Eventを挿入させて要求元にユニキャスト配信させる。なお、セグメントストリームにProxy Change Eventを挿入する処理の詳細は後述する。 In step S24, the analysis request unit 84 outputs the Proxy Change Event supplied as a result of the analysis from the location monitoring server 54 to the monitoring agent unit 81, and the Proxy Change Event is sent to the segment stream as a response to the segment acquisition request. Insert it and make it unicast to the request source. The details of the process of inserting a Proxy Change Event into the segment stream will be described later.
　ステップＳ１４において、端末装置７０は、ユニキャスト送信されたセグメントストリームを受信、再生する。このとき、セグメントストリームにProxy Change Eventが含まれている場合、スクリプト実行部７３がProxy Change Eventのスクリプトを実行する、これにより、端末装置７０のプロキシサーバ接続設定が、その近傍に位置する最適化プロキシサーバ５３に対して優先的に接続するように変更される。 In step S14, the terminal device 70 receives and reproduces the unicast transmitted segment stream. At this time, if the segment stream includes a Proxy Change Event, the script execution unit 73 executes the Proxy Change Event script, whereby the proxy server connection setting of the terminal device 70 is optimized to be located in the vicinity thereof. It is changed to connect preferentially to the proxy server 53.
　以上で、端末装置７０がセグメント取得要求（セグメントリクエスト）を用いてロケーション情報を送信する場合のイベント通知処理の説明を終了する。 This is the end of the description of the event notification process when the terminal device 70 transmits location information using a segment acquisition request (segment request).
　ここで、セグメントストリームにProxy Change Eventを挿入する処理について詳述する。本実施の形態では、DASHにおいて採用されているfragmented MP4のセグメントストリームの中に埋め込むbox形式のイベント通知方法に新たにProxyChangeEventというスキームを導入する。 Here, the process of inserting a Proxy Change Event into a segment stream will be described in detail. In this embodiment, a scheme called ProxyChangeEvent is newly introduced in the box type event notification method embedded in the fragmented MP4 segment stream adopted in DASH.
　図７は、DASH inband eventを利用したProxyChangeEventのeventメッセージのフォーマットの一例を示している。 FIG. 7 shows an example of the format of an event message of ProxyChangeEvent using DASH inband event.
　図７の例において、scheme_id_uri+valueは、message_data[](イベントメッセージ本体)の内容のフォーマットを規定する。なお、現状のDASHの規格では、"urn:mpeg:dash:event:2012"というscheme_id_uriを定義して、valueとして２種類の値を規定し、MPD更新イベントの通知に用いるよう定義している。ここでは、proxy設定変更のメッセージを表せるよう、新たにscheme_id_uriとして”urn:mpeg:dash:event:proxyChange”を導入する。 In the example of FIG. 7, scheme_id_uri + value defines the format of the content of message_data [] (the event message body). In the current DASH standard, a scheme_id_uri of "urn: mpeg: dash: event: 2012" is defined, two types of values are defined as values, and it is defined to be used for MPD update event notification. Here, “urn: mpeg: dash: event: proxyChange” is newly introduced as scheme_id_uri so that the proxy setting change message can be expressed.
　このsheme_id_uriに”urn:mpeg:dash:event:proxyChange”が指定された場合は、このイベントを受信した端末装置７０は、message_data[]にプロキシサーバ接続設定の変更に関する処理手続きそのもの、または、その取得先urlが格納されていることを知ることができる。なお、例えば、value=1のときは、プロキシサーバの接続設定を変更をするjavascriptが格納されていることを意味し、value=2のときには、スクリプトのurlが格納されていることを意味し、value=3のときは新たな接続先となるプロキシサーバのアドレスのみが格納されていることを意味する。 When "urn: mpeg: dash: event: proxyChange" is specified in this sheme_id_uri, the terminal device 70 that has received this event receives the processing procedure for changing the proxy server connection setting in message_data [], or acquires it It can be known that the destination url is stored. For example, when value = 1, it means that javascript for changing the connection setting of the proxy server is stored, and when value = 2, it means that the url of the script is stored, When value = 3, it means that only the address of the proxy server that is the new connection destination is stored.
　本来、DASHのpush eventではイベント配信対象の端末装置７０を指定することができないが、本実施の形態ではこれが可能である。ただし、イベント配信対象の端末装置７０を指定できるのはセグメントストリームをユニキャスト配信している場合に限られる。尤も、共通のセルセグメントに接続する複数の端末装置７０がマルチキャスト配信されるストリームを受信しているような場合には、該マルチキャスト配信されるストリームのセグメントチャンクにProxyChangeEventを挿入すれば、これら複数の端末装置７０を同時にイベント配信対象とすることが可能である。 Although the DASH push event can not originally designate the terminal device 70 for event distribution, this is possible in this embodiment. However, the terminal device 70 that is the target of event distribution can be specified only when the segment stream is being unicast-distributed. However, when a plurality of terminal devices 70 connected to a common cell segment receive a stream to be multicast-distributed, a ProxyChange Event may be inserted into a segment chunk of the stream to be multicast-distributed. It is possible to simultaneously set the terminal device 70 as an event distribution target.
　なお、イベント通知の方法は上述したDASH inband eventを利用したProxyChangeEventを用いる方法の他、W3Cで仕様化されているXMLHttpRequest やWebSocket を利用することもできる。例えば、XMLHttpRequestを利用する場合には、HTTPレスポンスのボディに、格納されるスクリプトのフォーマットとその内容そのもの、または変更するプロキシサーバのアドレスをjson形式で格納すればよい。 In addition to the method of using ProxyChangeEvent using DASH inband event described above, the method of event notification can also use XMLHttpRequest or WebSocket specified in W3C. For example, when using XML Http Request, the format of the script to be stored and its content itself, or the address of the proxy server to be changed may be stored in the body of the HTTP response in the json format.
　例えば、pacスクリプトの場合は、{“pac”: (pacのjavascriptそのもの)}が dataフィールドに格納され、pacスクリプトのurlの場合は、{“pacUrl”: (pacのjavascript取得先url)}、変更するDASHプロキシサーバのurlの場合は、{“proxyUrl”: (変更するDASHプロキシサーバのurl)}とする。端末装置７０に対してこのイベントを取得するXMLHttpRequestの接続url(HTTTP GETするアドレス)を知らせるには、ルート要素であるMPDに新たに導入する属性MPD/@eventPortにXMLHttpRequestの接続先URLを格納するようにする。 For example, in the case of pac script, {“pac”: (javascript itself of pac)} is stored in the data field, and in the case of pac script url, {“pacUrl”: (javascript acquisition destination url of pac)}, In the case of url of the DASH proxy server to be changed, it is {"proxyUrl": (url of DASH proxy server to be changed)}. In order to notify the terminal device 70 of the connection url (the address to be HTTTP GET) of the XMLHttpRequest that acquires this event, store the connection destination URL of the XMLHttpRequest in the attribute MPD / @ eventPort to be newly introduced to the MPD which is the root element. Let's do it.
　次に、図８は、端末装置７０がXMLHttpRequestを用いてロケーション情報を送信する場合のイベント通知処理を説明するフローチャートである。このイベント処理は、端末装置７０がユニキャスト配信のストリームを受信、再生している場合のみならず、マルチキャスト配信のストリームを受信、再生している場合にも適用できる。 Next, FIG. 8 is a flowchart illustrating an event notification process in the case where the terminal device 70 transmits location information using XML Http Request. This event processing can be applied not only when the terminal device 70 receives and reproduces a stream of unicast distribution, but also when the stream of multicast distribution is received and reproduced.
　ステップＳ４１において、端末装置７０のロケーション通知部７２は、端末装置７０のロケーション情報を取得してXMLHttpRequestに格納し、ロケーション監視サーバ５４に送信する。 In step S41, the location notification unit 72 of the terminal device 70 acquires the location information of the terminal device 70, stores it in XML HttpRequest, and sends it to the location monitoring server 54.
　XMLHttpRequestを受信したロケーション監視サーバ５４は、ステップＳ５１において、XMLHttpRequestに格納されているロケーション情報に基づいて端末装置７０の位置を判定し、端末装置７０の近傍に接続先として変更できる最適化プロキシサーバ５３がある場合、その最適化プロキシサーバ５３に優先的に接続するようにプロキシサーバ接続設定を変更するProxy Change Eventを生成し、生成したProxy Change EventをXMLHttpRequestのレスポンスとして端末装置７０に送信する。 In step S51, the location monitoring server 54 that has received the XML Http Request determines the position of the terminal device 70 based on the location information stored in the XML Http Request, and can be changed in the vicinity of the terminal device 70 as a connection destination. If there is a Proxy Change Event for changing the proxy server connection setting so as to connect preferentially to the optimization proxy server 53, a Proxy Change Event is sent to the terminal device 70 as a response to XMLHttpRequest.
　ステップＳ４２において、端末装置７０のスクリプト実行部７３は、XMLHttpRequestのレスポンスとしてProxy Change Eventのスクリプトを実行する、これにより、端末装置７０のプロキシサーバ接続設定が、その近傍に位置する最適化プロキシサーバ５３に対して優先的に接続するように変更される。 In step S42, the script execution unit 73 of the terminal device 70 executes a script of Proxy Change Event as a response of XMLHttpRequest, whereby the proxy server connection setting of the terminal device 70 is located in the vicinity of the optimization proxy server 53 Is changed to connect preferentially to.
　以上で、端末装置７０がXMLHttpRequestを用いてロケーション情報を送信する場合のイベント通知処理の説明を終了する。 This is the end of the description of the event notification process in the case where the terminal device 70 transmits location information using XML Http Request.
　以上説明したように、本実施の形態では、端末装置７０のロケーション情報に基づいて端末装置７０の移動を検知し、その位置にて接続可能な最適化プロキシサーバ５３が存在する場合には、プロキシサーバ接続設定を変更させることができる。これにより、端末装置７０は、効率よくストリーミングサービスを利用することが可能となる。 As described above, in the present embodiment, the movement of the terminal device 70 is detected based on the location information of the terminal device 70, and when there is an optimization proxy server 53 connectable at that position, the proxy is You can change the server connection settings. As a result, the terminal device 70 can efficiently use the streaming service.
　ところで、上述した一連の処理を実行するコンテンツ供給システム５０の各装置は、それぞれをハードウェアにより構成する他、コンピュータがソフトウェアを実行することにより実現することもできる。このコンピュータには、専用のハードウェアに組み込まれているコンピュータや、各種のプログラムをインストールすることで、各種の機能を実行することが可能な、例えば汎用のパーソナルコンピュータなどが含まれる。 By the way, each device of the content supply system 50 that executes the series of processes described above can be realized by a computer executing software in addition to hardware being configured. 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.
　このコンピュータ２００において、CPU（Central Processing Unit）２０１，ROM（Read Only Memory）２０２，RAM（Random Access Memory）２０３は、バス２０４により相互に接続されている。 In the computer 200, 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.
　バス２０４には、さらに、入出力インタフェース２０５が接続されている。入出力インタフェース２０５には、入力部２０６、出力部２０７、記憶部２０８、通信部２０９、およびドライブ２１０が接続されている。 Further, 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.
　以上のように構成されるコンピュータ２００では、CPU２０１が、例えば、記憶部２０８に記憶されているプログラムを、入出力インタフェース２０５およびバス２０４を介して、RAM２０３にロードして実行することにより、上述した一連の処理が行われる。 In the computer 200 configured as described above, for example, 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.
　コンピュータ２００（CPU２０１）が実行するプログラムは、例えば、パッケージメディア等としてのリムーバブルメディア２１１に記録して提供することができる。また、プログラムは、ローカルエリアネットワーク、インターネット、デジタル衛星放送といった、有線または無線の伝送媒体を介して提供することができる。 The program executed by the computer 200 (CPU 201) 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.
　コンピュータ２００では、プログラムは、リムーバブルメディア２１１をドライブ２１０に装着することにより、入出力インタフェース２０５を介して、記憶部２０８にインストールすることができる。また、プログラムは、有線または無線の伝送媒体を介して、通信部２０９で受信し、記憶部２０８にインストールすることができる。その他、プログラムは、ROM２０２や記憶部２０８に、あらかじめインストールしておくことができる。 In the computer 200, 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. In addition, the program can be installed in advance in the ROM 202 or the storage unit 208.
　なお、コンピュータ２００が実行するプログラムは、本明細書で説明する順序に沿って時系列に処理が行われるプログラムであってもよいし、並列に、あるいは呼び出しが行われたとき等の必要なタイミングで処理が行われるプログラムであってもよい。 Note that 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
　本開示の実施の形態は、上述した実施の形態に限定されるものではなく、本開示の要旨を逸脱しない範囲において種々の変更が可能である。 Embodiments of the present disclosure are not limited to the above-described embodiments, and various modifications can be made without departing from the scope of the present disclosure.
　本開示は以下のような構成もとることができる。
（１）
　適応的ストリーミング技術に従って配信されるコンテンツを受信する端末装置が送信したロケーション情報を取得する取得部と、
　前記ロケーション情報に基づいて前記端末装置の近傍に前記端末装置が接続可能なプロキシサーバ装置が存在するか否かを判定し、前記プロキシサーバ装置が存在する場合、前記端末装置が前記プロキシサーバ装置に優先的に接続するように前記端末装置のプロキシサーバ接続設定を変更するスクリプトを含むProxyChangeEventを生成する生成部と、
　生成された前記ProxyChangeEventを前記端末装置に供給する供給部と
　を備えるサーバ装置。
（２）
　前記取得部は、前記コンテンツのセグメントストリームのユニキャスト配信を前記端末装置が要求するために送信したセグメント取得要求にクエリパラメータとして格納されている前記ロケーション情報を取得し、
　前記供給部は、前記セグメント取得要求に対応する前記セグメントストリームに前記ProxyChangeEventを挿入して前記端末装置に供給する
　前記（１）に記載のサーバ装置。
（３）
　前記取得部は、XMLHttpRequestに格納されている前記ロケーション情報を取得し、
　前記供給部は、前記XMLHttpRequestに対するレスポンスとして前記ProxyChangeEventを前記端末装置に供給する
　前記（１）に記載のサーバ装置。
（４）
　前記ロケーション情報は、GPS位置情報またはセルＩＤである
　前記（１）から（３）のいずれかに記載のサーバ装置。
（５）
　前記プロキシサーバ装置は、ユニキャスト配信される前記コンテンツのセグメントストリームをキャッシングするとともに、マルチキャスト配信される前記コンテンツのFLUTEストリームもキャッシングする
　前記（１）から（４）のいずれかに記載のサーバ装置。 The present disclosure can also be configured as follows.
(1)
An acquisition unit that acquires location information transmitted by a terminal device that receives content distributed according to an adaptive streaming technique;
Based on the location information, it is determined whether or not there is a proxy server device to which the terminal device can be connected in the vicinity of the terminal device, and if the proxy server device is present, the terminal device is connected to the proxy server device A generation unit that generates a ProxyChangeEvent including a script for changing the proxy server connection setting of the terminal device so as to connect preferentially;
A supply unit that supplies the generated ProxyChangeEvent to the terminal device.
(2)
The acquisition unit acquires the location information stored as a query parameter in a segment acquisition request transmitted by the terminal device to request unicast distribution of the segment stream of the content.
The server apparatus according to (1), wherein the supply unit inserts the ProxyChange Event into the segment stream corresponding to the segment acquisition request and supplies the ProxyChange Event to the terminal device.
(3)
The acquisition unit acquires the location information stored in XML HttpRequest,
The server device according to (1), wherein the supply unit supplies the ProxyChange Event to the terminal device as a response to the XML Http Request.
(4)
The location information is GPS location information or a cell ID. The server apparatus according to any one of (1) to (3).
(5)
The server apparatus according to any one of (1) to (4), wherein the proxy server apparatus caches a segment stream of the content to be unicast-distributed, and also caches a FLUTE stream of the content to be multicast-distributed.
　５０　コンテンツ供給システム，　５１　ネットワーク，　５２　CDN，　５３　最適化プロキシサーバ，　５４　ロケーション監視サーバ，　６０　コンテンツ供給装置，　６１　チャネルストリーマ，　６２　DASHセグメンタ，　６３　FLUTEストリーマ，　６４　MPDジェネータ，　６５　WEBサーバ，　６６　マルチキャストサーバ，　７１　端末装置，　７１　受信再生部，　７２　ロケーション通知部，　７３　スクリプト実行部，　８１　モニタリング代行部，　８２　チューナ部，　８３　キャッシング部，　８４　解析依頼部，　２００　コンピュータ，　２０１　CPU 50 Content Delivery System, 51 Network, 52 CDN, 53 Optimized Proxy Server, 54 Location Monitoring Server, 60 Content Delivery Device, 61 Channel Streamer, 62 DASH Segmenter, 63 FLUTE Streamer, 64 MPD Generator, 65 Web Server, 66 Multicast Server , 71 terminal device, 71 reception and reproduction unit, 72 location notification unit, 73 script execution unit, 81 monitoring agency unit, 82 tuner unit, 83 caching unit, 84 analysis request unit, 200 computer, 201 CPU

Claims (12)

  1. 　適応的ストリーミング技術に従って配信されるコンテンツを受信する端末装置が送信したロケーション情報を取得する取得部と、
    　前記ロケーション情報に基づいて前記端末装置の近傍に前記端末装置が接続可能なプロキシサーバ装置が存在するか否かを判定し、前記プロキシサーバ装置が存在する場合、前記端末装置が前記プロキシサーバ装置に優先的に接続するように前記端末装置のプロキシサーバ接続設定を変更するスクリプトを含むProxyChangeEventを生成する生成部と、
    　生成された前記ProxyChangeEventを前記端末装置に供給する供給部と
    　を備えるサーバ装置。     An acquisition unit that acquires location information transmitted by a terminal device that receives content distributed according to an adaptive streaming technique;
    Based on the location information, it is determined whether or not there is a proxy server device to which the terminal device can be connected in the vicinity of the terminal device, and if the proxy server device is present, the terminal device is connected to the proxy server device A generation unit that generates a ProxyChangeEvent including a script for changing the proxy server connection setting of the terminal device so as to connect preferentially;
    A supply unit that supplies the generated ProxyChangeEvent to the terminal device.
  2. 　前記取得部は、前記コンテンツのセグメントストリームのユニキャスト配信を前記端末装置が要求するために送信したセグメント取得要求にクエリパラメータとして格納されている前記ロケーション情報を取得し、
    　前記供給部は、前記セグメント取得要求に対応する前記セグメントストリームに前記ProxyChangeEventを挿入して前記端末装置に供給する
    　請求項１に記載のサーバ装置。     The acquisition unit acquires the location information stored as a query parameter in a segment acquisition request transmitted by the terminal device to request unicast distribution of the segment stream of the content.
    The server apparatus according to claim 1, wherein the supply unit inserts the ProxyChange Event into the segment stream corresponding to the segment acquisition request and supplies the ProxyChange Event to the terminal device.
  3. 　前記取得部は、XMLHttpRequestに格納されている前記ロケーション情報を取得し、
    　前記供給部は、前記XMLHttpRequestに対するレスポンスとして前記ProxyChangeEventを前記端末装置に供給する
    　請求項１に記載のサーバ装置。     The acquisition unit acquires the location information stored in XML HttpRequest,
    The server apparatus according to claim 1, wherein the supply unit supplies the ProxyChange Event to the terminal device as a response to the XML Http Request.
  4. 　前記ロケーション情報は、GPS位置情報またはセルＩＤである
    　請求項２に記載のサーバ装置。     The server apparatus according to claim 2, wherein the location information is GPS location information or a cell ID.
  5. 　前記プロキシサーバ装置は、ユニキャスト配信される前記コンテンツのセグメントストリームをキャッシングするとともに、マルチキャスト配信される前記コンテンツのFLUTEストリームもキャッシングする
    　請求項２に記載のサーバ装置。     The server device according to claim 2, wherein the proxy server device caches segment streams of the content to be unicast-distributed, and also caches a FLUTE stream of the content to be multicast-distributed.
  6. 　サーバ装置の情報処理方法において、
    　前記サーバ装置による、
    　　適応的ストリーミング技術に従って配信されるコンテンツを受信する端末装置が送信したロケーション情報を取得する取得ステップと、
    　　前記ロケーション情報に基づいて前記端末装置の近傍に前記端末装置が接続可能なプロキシサーバ装置が存在するか否かを判定し、前記プロキシサーバ装置が存在する場合、前記端末装置が前記プロキシサーバ装置に優先的に接続するように前記端末装置のプロキシサーバ接続設定を変更するスクリプトを含むProxyChangeEventを生成する生成ステップと、
    　　生成された前記ProxyChangeEventを前記端末装置に供給する供給ステップと
    　を含む情報処理方法。     In an information processing method of a server device,
    By the server device,
    An acquisition step of acquiring location information transmitted by a terminal device that receives content distributed according to the adaptive streaming technology;
    Based on the location information, it is determined whether or not there is a proxy server device to which the terminal device can be connected in the vicinity of the terminal device, and if the proxy server device is present, the terminal device is connected to the proxy server device Generating a ProxyChangeEvent including a script for changing a proxy server connection setting of the terminal device to connect preferentially;
    Supplying the generated ProxyChangeEvent to the terminal device.
  7. 　コンピュータを、
    　適応的ストリーミング技術に従って配信されるコンテンツを受信する端末装置が送信したロケーション情報を取得する取得部と、
    　前記ロケーション情報に基づいて前記端末装置の近傍に前記端末装置が接続可能なプロキシサーバ装置が存在するか否かを判定し、前記プロキシサーバ装置が存在する場合、前記端末装置が前記プロキシサーバ装置に優先的に接続するように前記端末装置のプロキシサーバ接続設定を変更するスクリプトを含むProxyChangeEventを生成する生成部と、
    　生成された前記ProxyChangeEventを前記端末装置に供給する供給部と
    　して機能させるプログラム。     Computer,
    An acquisition unit that acquires location information transmitted by a terminal device that receives content distributed according to an adaptive streaming technique;
    Based on the location information, it is determined whether or not there is a proxy server device to which the terminal device can be connected in the vicinity of the terminal device, and if the proxy server device is present, the terminal device is connected to the proxy server device A generation unit that generates a ProxyChangeEvent including a script for changing the proxy server connection setting of the terminal device so as to connect preferentially;
    A program that functions as a supply unit that supplies the generated ProxyChangeEvent to the terminal device.
  8. 　適応的ストリーミング技術に従って配信されるコンテンツを受信する端末装置において、
    　自身のロケーション情報を取得して送信する送信部と、
    　前記ロケーション情報の送信に応じて供給されるProxyChangeEventに含まれるスクリプトを実行することによりプロキシサーバ接続設定を変更するスクリプト実行部と
    　を備える端末装置。     In a terminal device receiving content distributed according to an adaptive streaming technique,
    A transmitter for acquiring and transmitting its own location information;
    And a script execution unit configured to change proxy server connection settings by executing a script included in ProxyChangeEvent supplied in response to the transmission of the location information.
  9. 　前記送信部は、前記コンテンツのセグメントストリームのユニキャスト配信を要求するためのセグメント取得要求にクエリパラメータとして前記ロケーション情報を格納して送信し、
    　前記スクリプト実行部は、前記セグメント取得要求に応じてユニキャスト配信された前記セグメントストリームに挿入されている前記ProxyChangeEventに含まれる前記スクリプトを実行することによりプロキシサーバ接続設定を変更する
    　請求項８に記載の端末装置。     The transmitting unit stores and transmits the location information as a query parameter in a segment acquisition request for requesting unicast distribution of the segment stream of the content.
    The script execution unit changes a proxy server connection setting by executing the script included in the ProxyChange Event inserted in the segment stream unicast-delivered in response to the segment acquisition request. Terminal equipment.
  10. 　前記送信部は、前記ロケーション情報をXMLHttpRequestに格納して送信し、
    　前記スクリプト実行部は、前記XMLHttpRequestに対するレスポンスとして送信された前記ProxyChangeEventに含まれる前記スクリプトを実行することによりプロキシサーバ接続設定を変更する
    　請求項８に記載の端末装置。     The transmission unit stores the location information in an XML Http Request and transmits it.
    The terminal device according to claim 8, wherein the script execution unit changes a proxy server connection setting by executing the script included in the ProxyChange Event transmitted as a response to the XML Http Request.
  11. 　前記ロケーション情報は、GPS位置情報またはセルＩＤである
    　請求項８に記載の端末装置。     The terminal device according to claim 8, wherein the location information is GPS location information or a cell ID.
  12. 　適応的ストリーミング技術に従ってコンテンツのストリームを配信するコンテンツ供給装置と、前記ストリームを受信する端末装置と、サーバ装置とを備えるコンテンツ供給システムにおいて、
    　前記サーバ装置は、
    　　前記端末装置が送信したロケーション情報を取得する取得部と、
    　　前記ロケーション情報に基づいて前記端末装置の近傍に前記端末装置が接続可能なプロキシサーバ装置が存在するか否かを判定し、前記プロキシサーバ装置が存在する場合、前記端末装置が前記プロキシサーバ装置に優先的に接続するように前記端末装置のプロキシサーバ接続設定を変更するスクリプトを含むProxyChangeEventを生成する生成部と、
    　　生成された前記ProxyChangeEventを前記端末装置に供給する供給部とを備え、
    　前記端末装置は、
    　　自身の前記ロケーション情報を取得して送信する送信部と、
    　　前記ロケーション情報の送信に応じて前記サーバ装置から供給される前記ProxyChangeEventに含まれるスクリプトを実行することによりプロキシサーバ接続設定を変更するスクリプト実行部とを備える
    　コンテンツ供給システム。     What is claimed is: 1. A content providing system comprising: a content providing device for delivering a stream of content according to an adaptive streaming technique; a terminal device for receiving the stream; and a server device
    The server device is
    An acquisition unit that acquires location information transmitted by the terminal device;
    Based on the location information, it is determined whether or not there is a proxy server device to which the terminal device can be connected in the vicinity of the terminal device, and if the proxy server device is present, the terminal device is connected to the proxy server device A generation unit that generates a ProxyChangeEvent including a script for changing the proxy server connection setting of the terminal device so as to connect preferentially;
    And a supply unit that supplies the generated ProxyChangeEvent to the terminal device.
    The terminal device is
    A transmitter for acquiring and transmitting the location information of its own;
    A content providing system comprising: a script execution unit that changes a proxy server connection setting by executing a script included in the ProxyChange Event supplied from the server device in response to the transmission of the location information.
PCT/JP2014/071466 2013-08-30 2014-08-15 Server device, information processing method, program, terminal device, and content provision system WO2015029800A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2013180293A JP2015049650A (en) 2013-08-30 2013-08-30 Server apparatus, information processing method, program, terminal device, and content supply system
JP2013-180293 2013-08-30

Publications (1)

Publication Number Publication Date
WO2015029800A1 true WO2015029800A1 (en) 2015-03-05

Family

ID=52586368

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2014/071466 WO2015029800A1 (en) 2013-08-30 2014-08-15 Server device, information processing method, program, terminal device, and content provision system

Country Status (2)

Country Link
JP (1) JP2015049650A (en)
WO (1) WO2015029800A1 (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018043111A1 (en) 2016-08-29 2018-03-08 ソニー株式会社 Information processing device, information processing method, and information processing system
US11184452B2 (en) * 2017-10-13 2021-11-23 Yokogawa Electric Corporation System and method for selecting proxy computer
WO2021140949A1 (en) * 2020-01-09 2021-07-15 ソニーグループ株式会社 Content delivery system, content delivery method, and program

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012011450A1 (en) * 2010-07-20 2012-01-26 シャープ株式会社 Content distribution device, content playback device, content distribution system, method for controlling a content distribution device, control program, and recording medium
US20120259946A1 (en) * 2011-04-07 2012-10-11 Qualcomm Incorporated Network streaming of video data using byte range requests

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012011450A1 (en) * 2010-07-20 2012-01-26 シャープ株式会社 Content distribution device, content playback device, content distribution system, method for controlling a content distribution device, control program, and recording medium
US20120259946A1 (en) * 2011-04-07 2012-10-11 Qualcomm Incorporated Network streaming of video data using byte range requests

Also Published As

Publication number Publication date
JP2015049650A (en) 2015-03-16

Similar Documents

Publication Publication Date Title
EP2897369B1 (en) Content supply device, content supply method, program, and content supply system
CN105210372B (en) Content supply device, Content supply method, program and contents providing system
US10165035B2 (en) Content supplying device, content supplying method, program, and content supplying system
WO2015029800A1 (en) Server device, information processing method, program, terminal device, and content provision system
US10306272B2 (en) Content supply device, content supply method, program, terminal device, and content supply system
JP6466850B2 (en) Content supply device, content supply method, program, terminal device, and content supply system
WO2015029767A1 (en) Proxy-server device, information processing method, program, terminal device, and content provision system
KR102123208B1 (en) Content supply device, content supply method, program, terminal device, and content supply system
WO2015041071A1 (en) Content provision device, content provision method, program, terminal device and content provision system
WO2017212931A1 (en) Reception device, reception method, playback device, playback method, supply device, supply method, and program
CA2919977C (en) Content supply device, content supply method, program, terminal device, and content supply system
WO2015008653A1 (en) Content provision device, content provision method, program, terminal device, and content provision system

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14840714

Country of ref document: EP

Kind code of ref document: A1