WO2015012140A1 - Dispositif de fourniture de contenu, procédé de fourniture de contenu, programme, dispositif de terminal et système de fourniture de contenu - Google Patents

Dispositif de fourniture de contenu, procédé de fourniture de contenu, programme, dispositif de terminal et système de fourniture de contenu Download PDF

Info

Publication number
WO2015012140A1
WO2015012140A1 PCT/JP2014/068678 JP2014068678W WO2015012140A1 WO 2015012140 A1 WO2015012140 A1 WO 2015012140A1 JP 2014068678 W JP2014068678 W JP 2014068678W WO 2015012140 A1 WO2015012140 A1 WO 2015012140A1
Authority
WO
WIPO (PCT)
Prior art keywords
stream
zapping
metadata
viewing
content
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/JP2014/068678
Other languages
English (en)
Japanese (ja)
Inventor
山岸　靖明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sony Corp
Original Assignee
Sony Corp
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 Sony Corp filed Critical Sony Corp
Publication of WO2015012140A1 publication Critical patent/WO2015012140A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/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
    • 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/234—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs
    • H04N21/2343—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements
    • H04N21/23439—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements for generating different versions
    • 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 content supply device, a content supply method, a program, a terminal device, and a content supply system, and in particular, a content supply device, a content supply method, a program, a terminal device, and a content supply that enables rapid stream switching. About the 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 (20A, 20B, and 20C in this case) for supplying content, and a plurality of DASH clients 30 for receiving content.
  • the content supply device 20 and the DASH client 30 are connected via the Internet 11.
  • a CDN (Contents Delivery Network) 12 exists on the Internet 11.
  • the content supply apparatus 20A distributes a plurality of segment streams having the same content as the channel A and different bit rates. The same applies to the content supply devices 20B and 20C. However, it is assumed that the content supply apparatuses 20A, 20B, and 20C are distributing contents having different contents. Hereinafter, the content supply devices 20A, 20B, and 20C are simply referred to as the content supply device 20 when it is not necessary to distinguish them individually.
  • the content supply device 20 includes a content management server 21, a DASH segment streamer 22, and a DASH MPD server 23.
  • the content management server 21 manages source data of content to be distributed to the DASH client 30, generates a plurality of streaming data having different bit rates from the source data of the content, and outputs the streaming data to the DASH segment streamer 22.
  • the DASH segment streamer 22 temporally divides (streams) each streaming data into segments to generate a segment stream. Also, the DASH segment streamer 22 holds the segment stream as a file, and as a WEB server, responds to a request (HTTP request) from the DASH client 30 to transmit the segment stream file via the CDN 12 to the DASH client 30 of the request source. Distribute HTTP Unicast to. Furthermore, the DASH segment streamer 22 notifies the DASH MPD server 23 of the address of the source of the file of the segment stream.
  • the DASH MPD server 23 generates an MPD in which an address representing the source of the segment stream file, etc., necessary for the DASH client 30 to acquire the segment stream file is described. Further, the DASH MPD server 23, as a WEB server, responds to a request (HTTP request) from the DASH client 30 and distributes the generated MPD to the DASH client 30 of the request source via the CDN 12 via HTTP unicast.
  • HTTP request HTTP request
  • the DASH client 30 requests the MPD from the DASH MPD server 23 and receives the HTTP unicast distributed MPD accordingly. Furthermore, based on the received MPD, the DASH client 30 requests the DASH segment streamer 22 for the segment stream file, and receives and plays the HTTP unicast segment stream file accordingly.
  • the CDN 12 is provided with a cache server (not shown).
  • the cache server caches files of MPDs and segment streams that are HTTP-unicast-distributed via 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 content supply system 10 using DASH by preparing a plurality of channels (content supply devices 20A, 20B, 20C), a plurality of contents having different contents are simultaneously distributed to the receiving side. It is possible to do.
  • the user of the DASH client 30 performs the zapping phase (switching and viewing channels one after another in a short time) as in the case of watching television broadcasting. After the state of searching for the content), it is assumed to shift to the viewing phase (the state of viewing the content without zapping).
  • Switching between channels in DASH is performed in units of segments or in units of subsegments into which segments are further subdivided. In the following, switching between channels in DASH will be described as being performed on a segment basis.
  • FIGS. 2 and 3 are capable of delivering three segment streams (Representations) having the same content and different bit rates in each channel (A, B, C) of the content supply system 10 using DASH. It shows that there is.
  • the thick arrows in the figure show an example of switching transition when zapping between channels.
  • the difference in the width of the band indicating the segment stream represents the magnitude of the bit rate.
  • the segment length (time length) of the segment stream can be arbitrarily determined for each channel. Therefore, the segment lengths of the segment streams delivered by each channel do not necessarily match. Also, the reproduction start time of the first segment of the segment stream distributed by each channel is not defined to be particularly coincident.
  • FIG. 2 shows an example in which the segment lengths do not match between the channels, and the reproduction start time of the first segment of the segment stream does not match.
  • FIG. 3 shows an example of the case where the reproduction start time of the segment at the beginning of the segment stream is coincident with each other in synchronization with the NTP time axis, but the segment lengths are not coincident between the channels.
  • the actual switching timing is the segmentation of the Representation B2 segment. It is delayed to a certain T2. Thereafter, when switching to Channel C's Representation C 2 is instructed by T 3 while watching Channel B's Representation B 2, the actual switching timing is delayed to T 4 which is the segment of Representation C 2.
  • the present disclosure has been made in view of such a situation, and enables rapid zapping to be realized.
  • a content supply apparatus is a content supply apparatus that supplies, in the same channel, a plurality of streams having the same content and different bit rates according to an adaptive streaming technique.
  • a first stream generation unit that generates a zapping stream based on data, a first metadata generation unit that generates zapping metadata for receiving the zapping stream, and a source data of the content
  • a second stream generation unit that generates a viewing stream longer in minimum unit length when switching the stream than the zapping stream; and generating viewing metadata for receiving the viewing stream
  • a second metadata generation unit Comprising ring meta data, the viewing metadata, the zapping stream, and a multicast distribution unit the viewing stream for multicasting over a network.
  • the multicast distribution unit may perform FLUTE multicast distribution of the zapping metadata, the viewing metadata, the zapping stream, and the viewing stream via (e) MBMS.
  • the zapping metadata and the viewing metadata may be a combination of USD, MPD and SDP, or a combination of OMA-ESG, USD, MPD and SDP.
  • the first stream generation unit can generate a stream having a sufficiently short minimum unit length when switching streams based on source data of the content, and the first metadata generation unit Information representing that a stream corresponding to the zapping metadata can be used for zapping applications can be described in the zapping metadata.
  • the zapping stream can be generated, and the first metadata generation unit is information indicating that the stream corresponding to the zapping metadata can be used for the zapping stream, and the division of the minimum unit is NTP synchronization.
  • the zapping metadata can describe at least one of information indicating that the user is doing, or information indicating that the length of the minimum unit is the same as that of another channel.
  • the division of the minimum unit when switching the stream is in NTP synchronization, and the length of the minimum unit is the zapping stream generated by the first stream generation unit
  • the first stream data generation unit may generate the view stream for viewing that is an integral multiple of the minimum unit, and the first metadata generation unit may further generate the second stream generation unit for the zapping stream corresponding to the zapping metadata.
  • Information representing that switching that does not cause an extra delay in one direction asymmetrically in only one direction can be described in the metadata for zapping from the stream for viewing generated by the second metadata
  • the data generation unit is configured to use the first stream generation unit to generate the viewing stream corresponding to the viewing metadata. To the zapping stream to be made, it is possible to describe information indicating that it is possible to switch which does not cause asymmetrically extra delay in only one direction in the metadata for the viewing.
  • the content supply apparatus may further include a unicast distribution unit that unicasts the zapping metadata and the viewing metadata via a network.
  • a content supply method is a content supply method of a content supply apparatus for supplying, in the same channel, a plurality of streams having the same content and different bit rates according to an adaptive streaming technique.
  • the content providing apparatus generates a zapping stream based on the source data of the content, and viewing a longer minimum unit length when switching the stream than the zapping stream based on the source data of the content
  • a program based on source data of the content, provides a computer that supplies a plurality of streams having the same content and different bit rates in the same channel according to the adaptive streaming technology.
  • a first stream generation unit that generates a zapping stream, a first metadata generation unit that generates zapping metadata for receiving the zapping stream, and the zapping based on source data of the content
  • a second stream generation unit configured to generate a viewing stream longer in minimum unit length when switching the stream than a stream; and a second meta generating a viewing metadata for receiving the viewing stream
  • a zapping stream is generated based on source data of content, and zapping metadata for receiving the zapping stream is generated. Also, a viewing stream having a longer minimum unit length when switching the stream than the zapping stream is generated based on source data of the content, and viewing metadata for receiving the viewing stream is It is generated. Further, the zapping metadata, the viewing metadata, the zapping stream, and the viewing stream are distributed by multicast via a network.
  • a terminal device supplies the stream supplied from a content supply device that supplies, in the same channel, a plurality of streams having the same content and different bit rates according to adaptive streaming technology.
  • the content supply device In the terminal device for receiving, the content supply device generates a first stream generation unit that generates a zapping stream based on source data of the content, and zapping metadata for receiving the zapping stream.
  • the stream for viewing is received and reproduced based on the above.
  • zapping metadata is acquired, the zapping stream is received and reproduced based on the acquired zapping metadata, and the viewing metadata is acquired. The viewing stream is received and reproduced based on the acquired viewing metadata.
  • a content supply system receives a stream according to an adaptive streaming technique and supplies a plurality of streams having the same content and different bit rates in the same channel, and the stream
  • a content supply system including a terminal device, a first stream generation unit for generating a zapping stream based on source data of the content, and the zapping for receiving the zapping stream.
  • a first metadata generation unit for generating metadata, and a second for generating a viewing stream having a minimum unit length when switching the stream rather than the zapping stream based on the source data of the content With a stream generator A second metadata generation unit that generates viewing metadata for receiving the viewing stream, the zapping metadata, the viewing metadata, the zapping stream, and the viewing stream as a network And a multicast distribution unit that performs multicast distribution via the network. Then, the terminal device acquires the zapping metadata, receives and reproduces the zapping stream based on the acquired zapping metadata, acquires the viewing metadata, and acquires the viewing Receiving and reproducing the viewing stream based on the meta data;
  • the content supply device generates a zapping stream based on source data of the content, and zapping metadata for receiving the zapping stream is generated. Also, a viewing stream having a longer minimum unit length when switching the stream than the zapping stream is generated based on source data of the content, and viewing metadata for receiving the viewing stream is It is generated. Further, the zapping metadata, the viewing metadata, the zapping stream, and the viewing stream are distributed by multicast via a network. Also, the zapping metadata is acquired by the terminal device, and the zapping stream is received and reproduced based on the acquired zapping metadata, and the viewing metadata is acquired and acquired. The viewing stream is received and reproduced based on the viewing metadata.
  • rapid zapping can be realized.
  • FIG. 4 shows segment streams for the zapping phase (hereinafter referred to as zapping segment streams) distributed in each channel of the content supply system according to the embodiment of the present disclosure and the segment lengths thereof.
  • the thick arrows in the figure show an example of switching transition when zapping between channels.
  • the difference in the width of the band indicating the zapping segment stream indicates the magnitude of the bit rate.
  • zapping segment streams (Representations) having different bit rates are prepared for the channels A, B, and C, respectively.
  • the channels A, B, and C have the same content as the zapping segment stream, and the segment stream for the viewing phase (the segment length is longer than the zapping segment stream)
  • a plurality of viewing segment streams are also prepared. The viewing segment stream will be described later with reference to FIG.
  • the segment division of the zapping segment stream is synchronized with the NTP time axis, and the segment length of the zapping segment stream of each channel belonging to the same group is unified into a common time length. It has been decided. Furthermore, the start point (MPD / @ availabilityStartTime + Period / @ start) of the media playback time of the leading segment of the zapping segment stream is determined to coincide on the NTP time axis.
  • FIG. 5 shows the relationship between zapping segment streams and viewing segment streams prepared in each channel of the content supply system to which the present disclosure is applied.
  • the difference in width between the zapping segment stream and the viewing segment stream indicates the magnitude of the bit rate.
  • each channel prepares three zapping segment streams
  • two zapping segment streams are shown for each channel (only channel A is shown in FIG. 5).
  • 5 segment streams for viewing are prepared.
  • the number of zapping segment streams and viewing segment streams prepared by each channel is arbitrary, it is desirable to prepare one or more zapping segment streams and two or more viewing segment streams.
  • the segments of the zapping segment stream and the viewing segment stream of each channel are synchronized to the NTP time axis. Also, the segment length of the viewing segment stream is an integral multiple (3 times in the case of FIG. 5) of the segment length of the zapping segment stream of the same channel.
  • the zapping segment stream, the viewing segment stream, and the metadata such as the MPD for receiving them are defined by the mobile telephone communication network (3 GPP (3rd Generation Partnership Project) It is assumed that FLUTE multicast delivery is performed via a broadcast multicast channel of (e) MBMS (evolved Multimedia Broadcast Multicast Service). However, metadata such as MPD can be distributed via HTTP (e) MBMS interaction channel via HTTP unicast.
  • the zapping segment stream and the viewing segment stream distributed by FLUTE multicast are also referred to as a zapping FLUTE stream or a viewing FLUTE stream, respectively.
  • Metadata for zapping is acquired, and based on the metadata, it becomes a zapping phase for receiving and reproducing a FLUTE stream for zapping. Then, metadata for viewing is also acquired during the zapping phase, and it operates to prepare for transition to the viewing phase for receiving and playing the FLUTE stream for viewing.
  • FIG. 6 shows a configuration example of a content supply system according to an embodiment of the present disclosure.
  • the content supply device 60X and the terminal device 80 are connected via the network 51.
  • the network 51 includes a two-way communication network represented by the Internet, and various broadcast networks, but in the present embodiment, it is particularly assumed that (e) MBMS is defined in 3GPP. .
  • NTP server 52 that provides system time information according to the UTC time format. It is assumed that each content supply device 60 and each terminal device 80 operate by synchronizing their own system time with the NTP time axis according to the system time information provided from the NTP server 52 respectively.
  • the (e) MBMS of the network 51 has an interaction channel for two-way communication and a broadcast / multicast channel for one-way communication.
  • the MBMS interaction channel is used for HTTP unicast delivery of metadata such as MPD required to receive zapping segment streams and viewing segment streams.
  • the broadcast multicast channel of MBMS is used for FLUTE multicast distribution of metadata such as zapping segment streams and viewing segment streams, and MPD.
  • the content supply apparatus 60A corresponding to the channel A includes a channel server 61, a zapping segmenter 62, a zapping metadata generator 63, a viewing segmenter 64, a viewing metadata generator 65, a FLUTE streamer 66, a web server 67, and a multicast server. It has 68.
  • the channel servers 61 to the multicast server 68 included in the content supply apparatus 60A may be integrated and disposed, or may be distributed and disposed via the Internet or the like.
  • FIG. 7 and 8 show the flow of various data between the channel server 61 and the multicast server 68.
  • FIG. 7 is of the zapping face
  • FIG. 8 is of the viewing phase.
  • the channel server 61 manages source data of contents distributed from the channel A, and from the source data of the same contents, one or more zapping streaming data different in bit rate and two or more viewing streaming data Generate Further, the channel server 61 outputs the zapping streaming data to the zapping segmenter 62, and outputs the viewing streaming data to the viewing segmenter 64.
  • the zapping segmenter 62 divides zapping streaming data into periods in time, and further divides the zapping streaming data into segments, thereby generating a zapping segment stream such as fragmented MP 4 and outputs the zapping segment stream to the FLUTE streamer 66.
  • the segment length of the zapping segment stream is common to the zapping segment streams of other channels belonging to the same group, and is unified to a time length shorter than the segment length of the viewing segment stream described later. Since the zapping segmenter 62 operates in synchronization with the NTP time axis, the segments of the zapping segment stream are also synchronized with the NTP time axis.
  • a segment stream having a sufficiently short segment length (for example, a playback time of 2 seconds or less) may be generated. This segment stream can be used for zapping applications as it reduces the delay that can occur during switching.
  • the zapping segmenter 62 notifies the zapping metadata generator 63 of the data range of each segment in the generated zapping segment stream file.
  • the zapping metadata generator 63 generates metadata such as MPD (hereinafter referred to as zapping metadata) necessary for the terminal device 80 to receive the zapping segment stream, and sends it to the FLUTE streamer 66 and the WEB server 67. Output.
  • MPD hereinafter referred to as zapping metadata
  • Zapping metadata can be a combination of USD (User Service Description), MPD (Media Presentation Description), and SDP (Service Description Protocol), or OMA-ESG (Open Mobile Alliance-Electronic Service Guide), USD, MPD, and SDP. It consists of a combination of
  • the viewing segmenter 64 generates a viewing segment stream such as fragmented MP 4 from the viewing streaming data and outputs the segment stream to the FLUTE streamer 66. Furthermore, the viewing segmenter 64 notifies the viewing metadata generator 65 of the data range of each segment in the file of the generated viewing segment stream.
  • the viewing metadata generator 65 generates metadata such as MPD (hereinafter referred to as viewing metadata) necessary for the terminal device 80 to receive the viewing segment stream, and sends it to the FLUTE streamer 66 and the WEB server 67. Output.
  • MPD hereinafter referred to as viewing metadata
  • the viewing metadata is composed of a combination of USD, MPD, and SDP, or a combination of OMA-ESG, USD, MPD, and SDP, as with zapping metadata.
  • the FLUTE streamer 66 generates a zapping FLUTE stream by storing the zapping segment stream input from the zapping segmenter 62 in a FLUTE packet and outputs the zapping segment to the multicast server 68. Further, the FLUTE streamer 66 generates a viewing FLUTE stream by storing the viewing segment stream input from the viewing segmenter 64 in the FLUTE packet, and outputs the viewing FLUTE stream to the multicast server 68. In addition, the FLUTE streamer 66 outputs the zapping metadata input from the zapping metadata generator 63 and the viewing metadata input from the viewing metadata generator 65 to the multicast server 68.
  • the WEB server 67 In response to the request (HTTP request) from the terminal device 80, the WEB server 67 distributes the zapping metadata or the viewing metadata to the request source via the network 51 by HTTP unicast.
  • the multicast server 68 distributes FLUTE multicast of zapping metadata and viewing metadata via the network 51. Also, the multicast server 68 distributes FLUTE multicasts for the zapping FLUTE stream and the viewing FLUTE stream via the network 51.
  • the content supply device 60B corresponding to the channel B is configured in the same manner as the content supply device 60A, so the description thereof is omitted.
  • the USD is stored and delivered in (e) MBMS Service Announcement & Metadata.
  • FIG. 9 shows the arrangement of (e) Service Announcement & Metadata in MBMS.
  • Service Announcement & Metadata 91 is allocated to an (e) MBMS interaction channel and a broadcast / multicast channel.
  • the USD is HTTP unicast distributed on the interaction channel and FLUTE multicast distributed on the broadcast / multicast channel.
  • delivery of the USD may be either HTTP unicast delivery on the interaction channel or FLUTE multicast delivery on the broadcast / multicast channel.
  • the zapping FLUTE stream and the viewing FLUTE stream are stored in the Donload 3GPP file format, Binary data, Still images, Text, etc. 92 of the broadcast / multicast channel and distributed by FLUTE multicast.
  • FIG. 10 is a data model of the USD stored in the Service Announcement & Metadata 91, and this embodiment relates particularly to the User Service Bundle Description 101, the User Service Description 102, the Delivery Method 103, the Session Description 104, and the media Presentation Description 105.
  • FIG. 11 shows a first description example of the USD. This first example of description is applied when the corresponding FLUTE stream is available for zapping (the segment length is sufficiently short).
  • the class name "urn: streamType: forZapping” is defined and introduced in serviceClass as a flag attribute indicating that the FLUTE stream can be used for zapping.
  • the FLUTE stream described by this userServiceDescription metadata indicates that the segment length is sufficiently small that it can be used for zapping applications.
  • serviceClass "urn: streamType: forZapping” indicates that the corresponding FLUTE stream can be used for zapping.
  • the URL of the SDP acquisition destination is described.
  • the SDP describes the IP address and port of the corresponding FLUTE stream.
  • userServiceDescription / mediaPresentationDescription / @ mpdURI the URL of the MPD acquisition destination is described.
  • the arrangement of each segment in the corresponding FLUTE stream is described in the AdaptationSet / Representation of this MPD.
  • FIG. 13 shows a second description example of USD. This second description example is applied to the case where a plurality of corresponding FLUTE streams are each a zapping FLUTE stream and can be switched without causing an extra delay to each other (the relationship shown in FIG. 4). Be done.
  • NTPSynchronized and SegmentAligned are introduced immediately below bundleDescription.
  • the zapping segmenter 62 (of the content supply device 60) of each channel belonging to the same group operates in NTP synchronization, that is, the segment of the FLUTE stream segment of each channel is synchronized with the NTP time axis.
  • Indicates that bundleDescription / @ SegmentAligned represents that the segment lengths of the FLUTE stream segments of the respective channels are unified.
  • FIG. 14 shows an outline of a second description example of the USD in FIG.
  • the bundleDescription in which NTPSynchronized and SegmentAligned are introduced immediately below is used to group userServiceDescription groups that respectively describe two zapping streams.
  • bundleDescription / @ NTPSynchronized indicates that the segment of each FLUTE stream described in the userServiceDescription group is in NTP synchronization. Furthermore, if bundleDescription / @ SegmentAligned '(boolean type) is true, it indicates that the segment lengths of the segments of each FLUTE stream described in the userServiceDescription group are unified. In the case of the second description example, it is shown that the segment of the FLUTE stream indicated by circle 1 and the segment of the FLUTE stream indicated by circle 2 in the figure are in NTP synchronization and that the segment lengths match.
  • FIG. 15 shows a third description example of USD.
  • the corresponding zapping FLUTE streams can be switched without causing an extra delay to each other (the relationship shown in FIG. 4), and further, zapping from the corresponding viewing streams For the FLUTE stream for streams, it is applied in the case where it is the relation (the relation shown in FIG. 5) which can be switched without causing extra delay asymmetrically in only one direction.
  • unsymmetricallyAlignedGroupFrom and unsymmetricallyAlignedGroupTo are introduced into serviceDescription.
  • unsymmetricallyAlignedGroupFrom represents a relationship (group) that can be switched without causing an extra delay in one direction asymmetrically in only one direction and its switching source
  • unsymmetricallyAlignedGroupTo represents the relationship (group) and its switching destination.
  • FIG. 16 shows an outline of a third description example of the USD in FIG.
  • the portion indicated by circle 1 and the portion indicated by circle 2 indicate that they are switchable FLUTE streams for zapping that can be switched without causing an extra delay.
  • the zapping FLUTE indicated by the circle 1 it is possible to switch from the viewing stream for the circle 1 'only in one direction asymmetrically without causing an extra delay.
  • the zapping FLUTE indicated by the circle 2 it is possible to switch from the viewing stream of the circle 2 'only in one direction asymmetrically without causing an extra delay.
  • OMA-ESG and the USD are stored and delivered in (e) MBMS Service Announcement & Metadata 91. That is, OMA-ESG and USD are distributed by HTTP unicast on the (e) MBMS interaction channel, and are distributed by FLUTE multicast on the broadcast / multicast channel. However, delivery of OMA-ESG and USD may be either HTTP unicast delivery on an interaction channel or FLUTE multicast delivery on a broadcast / multicast channel.
  • FIG. 17 is a data model of OMA-ESG stored in Service Announcement & Metadata 91, and in the present embodiment, Service 111 and Access 112 are particularly concerned.
  • FIG. 18 shows a first description example of OMA-ESG
  • FIG. 18A is a description example of Service
  • FIG. 18B is a description example of Access referring to Service of FIG. This first example of description applies when the corresponding FLUTE stream is available for zapping applications.
  • a value “11” meaning Service / ServiceType “ZappingStream” is defined and introduced as a flag attribute indicating that the FLUTE stream can be used for zapping applications.
  • the FLUTE stream described by this Service metadata indicates that the segment length is sufficiently small and can be used for zapping.
  • FIG. 19 shows an outline of a first description example of the OMA-ESG of FIG. Access refers to Service and 3GPP: MBMS: bundleServiceDescrittion / userServiceDescription.
  • ⁇ ServiceType> 11 ⁇ / ServiceType> of the referenced Service indicates that the corresponding FLUTE stream is available for zapping.
  • deliveryMethod / @ sessionDescription URI of the referenced bundleServiceDescrittion / userServiceDescription the URL of the SDP acquisition destination is described.
  • the SDP describes the IP address and port of the corresponding FLUTE stream.
  • mediaPresentationDescription / @ mpdURI of the referenced bundleServiceDescrittion / userServiceDescription the URL of the MPD acquisition destination is described.
  • the arrangement of each segment in the corresponding FLUTE stream is described in the AdaptationSet / Representation of this MPD.
  • FIG. 20 shows a second description example of OMA-ESG.
  • FIG. 6A is an example of Service description corresponding to a FLapping stream for zapping indicated by a circle 1
  • FIG. 7B is an example of Access described with reference to the Service of FIG.
  • FIG. C is a description example of Service corresponding to the FLUTE stream for zapping shown by a circle 2
  • FIG. D is an description example of Access referring to Service of FIG.
  • This second example is applied to the case where a plurality of corresponding FLUTE streams are zapping FLUTE streams and can be switched without causing an extra delay to each other (the relationship shown in FIG. 4). Ru.
  • NTP Synchronized and SegmentAlignedGroupID are introduced to Access.
  • Access / NTP Synchronized belongs to the same group, ie zapping segmenter 62 of each channel (content supply device 60) of the same SegmentAlignedGroupID operates in NTP synchronization, ie the segment of FLUTE stream segment of each channel is NTP time Indicates that it is synchronized with the axis.
  • Access / SegmentAlignedGroupID represents an ID of a group in which segment lengths of FLUTE stream segments are unified.
  • FIG. 21 shows an outline of a second description example of the OMA-ESG of FIG. Access in which NTPSynchronized and SegmentAlignedGroupID are introduced is used to group Service / Access groups that describe zapping streams.
  • a of FIG. 22 is a description example of Service corresponding to the FLUTE stream for zapping shown by circle 1
  • B of FIG. 22 is a description example of Access referring to Service of A of FIG. 22C is a description example of Service corresponding to the viewing FLUTE stream indicated by a circle 1 '
  • D in FIG. 22 is an access description example referring to Service of C in FIG. 23A is a description example of Service corresponding to the FLUTE stream for zapping indicated by a circle 2
  • B in FIG. 23 is an description example of Access referring to Service of A in FIG. 23.
  • C in FIG. 23 is a description example of Service corresponding to a viewing FLUTE stream indicated by a circle 2 '
  • D in FIG. 23 is an access description example referring to Service of C in FIG.
  • This third description example is a relation (the relation shown in FIG. 4) in which the zapping FLUTE streams indicated by the circle 1 and the circle 2 can be switched without causing an extra delay to each other. From the viewing FLUTE stream indicated by the circle 1 ′ to the zapping FLUTE stream indicated by the circle 1 and from the viewing FLUTE stream indicated by the circle 2 ′ to the zapping FLUTE stream indicated by the circle 2 It applies in the case where it is a relation (the relation shown in FIG. 5) which can be switched only in one direction asymmetrically without causing an extra delay.
  • unsymmetricallyAlignedGroupFrom and unsymmetricallyAlignedGroupTo are introduced into Access.
  • unsymmetricallyAlignedGroupFrom represents a relationship (group) that can be switched without causing an extra delay in one direction asymmetrically in only one direction and its switching source
  • unsymmetricallyAlignedGroupTo represents the relationship (group) and its switching destination.
  • FIG. 24 shows an outline of a third description example of the OMA-ESG of FIG. 22 and FIG.
  • circle 1 and circle 2 are zapping FLUTE streams that can be switched without causing an extra delay to each other.
  • the FLUTE stream for zapping shown by circle 1 it can be switched asymmetrically in one direction only from the viewing FLUTE stream shown by circle 1 'without causing an extra delay.
  • the FLUTE stream for zapping shown by circle 2 it can be switched asymmetrically in one direction only from the viewing FLUTE stream shown by circle 2 'without causing an extra delay.
  • FIG. 25 is a flow chart for explaining the processing performed by each content supply device 60 for distributing content streams by FLUTE multicast.
  • step S1 the content supply device 60 synchronizes its own system time with the NTP time axis in accordance with the system time information provided by the NTP server 52.
  • the zapping segmenter 62, the viewing segmenter 64, and the like constituting the content supply device 60 operate in synchronization with the NTP time axis.
  • step S2 the channel server 61 generates zapping streaming data and viewing streaming data having different bit rates from the source data of the content. Further, the channel server 61 outputs the zapping streaming data to the zapping segmenter 62, and outputs the viewing streaming data to the viewing segmenter 64.
  • step S 3 the zapping segmenter 62 generates a zapping segment stream such as fragmented MP 4 from the zapping streaming data and outputs the zapping segment stream to the FLUTE streamer 66. Further, the zapping segmenter 62 notifies the zapping metadata generator 63 of the URL of the supply source of the generated zapping segment stream and the like. In parallel to this, the viewing segmenter 64 generates a viewing segment stream such as fragmented MP 4 from the viewing streaming data and outputs the segment stream to the FLUTE streamer 66. Also, the viewing segmenter 64 notifies the viewing metadata generator 65 of the URL and the like of the supply source of the generated viewing segment stream.
  • step S4 the FLUTE streamer 66 generates the zapping FLUTE stream by storing the zapping segment stream in the FLUTE packet and outputs the zapping FLUTE stream to the multicast server 68. Also, the FLUTE streamer 66 generates a viewing FLUTE stream by storing the viewing segment stream in a FLUTE packet and outputs the streaming FLUTE stream to the multicast server 68.
  • step S5 the zapping metadata generator 63 generates zapping metadata and outputs the zapping metadata to the FLUTE streamer 66 and the WEB server 67.
  • the viewing metadata generator 65 generates viewing metadata and outputs it to the FLUTE streamer 66 and the WEB server 67.
  • step S6 the FLUTE streamer 66 outputs the zapping metadata and the viewing metadata to the multicast server 68.
  • the multicast server 68 distributes FLUTE multicast of zapping metadata and viewing metadata via the network 51.
  • step S7 when there is a request (HTTP request) from the terminal device 80, the web server 67 distributes the zapping metadata or the viewing metadata to the request source via the network 51 in response to the request. .
  • HTTP request HyperText Transfer Protocol request
  • step S 8 the multicast server 68 distributes FLUTE multicasts for the zapping FLUTE stream and the viewing FLUTE stream via the network 51. Above, the process which each content supply apparatus 60 performs is complete
  • FIG. 26 is a flowchart illustrating a series of processes of the content supply system 50.
  • step S11 the terminal device 80 synchronizes its own system time with the NTP time axis in accordance with the system time information provided by the NTP server 52.
  • step S12 the terminal device 80 receives zapping metadata distributed by FLUTE multicast as the process of step S6 in FIG. Note that, instead of receiving the zapping metadata distributed by FLUTE multicast, the HTTP request may be transmitted to the WEB server 67 to distribute the zapping metadata by HTTP unicast, and may be received. The terminal device 80 that has received the zapping metadata is in the zapping phase.
  • step S13 the terminal device 80 receives and reproduces the zapping FLUTE stream distributed by FLUTE multicast as the process of step S8 in FIG. 25 based on the zapping metadata.
  • the terminal device 80 can switch between the zapping LUTE streams being distributed by FLUTE multicast without causing an extra delay by appropriately repeating the process of step S13.
  • the terminal device 80 obtains viewing metadata during the zapping phase. Specifically, in step S14, the terminal device 80 receives the viewing metadata distributed by FLUTE multicast as the process of step S6 in FIG. It should be noted that the HTTP request may be transmitted to the WEB server 67 to cause the HTTP metadata to be distributed for viewing metadata, and the content may be received via HTTP unicast instead of receiving the viewing metadata for FLUTE multicast distribution. .
  • the terminal device 80 that has received the viewing metadata can transition from the zapping phase to the viewing phase.
  • step S15 the terminal device 80 receives and reproduces the zapping FLUTE stream distributed by FLUTE multicast as the process of step S8 in FIG. 25 based on the viewing metadata.
  • stream switching is performed in units of segments, but may be performed in units of subsegments in which segments are further subdivided.
  • segment in the above description may be read as “sub-segment”.
  • the content supply device 60 and the terminal device 80 that execute the series of processes described above can be realized by a computer executing software, in addition to hardware configuration.
  • the computer includes, for example, a general-purpose personal computer capable of executing various functions by installing a computer incorporated in dedicated hardware and various programs.
  • FIG. 27 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.
  • a first stream generation unit that generates a zapping stream based on source data of the content;
  • a first metadata generation unit that generates zapping metadata for receiving the zapping stream;
  • a second stream generation unit configured to generate a viewing stream longer in minimum unit length when switching the stream than the zapping stream based on source data of the content;
  • a second metadata generation unit configured to generate viewing metadata for receiving the viewing stream;
  • a content supply apparatus comprising: a multicast distribution unit that multicasts the zapping metadata, the viewing metadata, the zapping stream, and the viewing stream via a network.
  • the content distribution apparatus distributes the zapping metadata, the viewing metadata, the zapping stream, and the viewing stream via (e) MBMS through the FLUTE multicast. .
  • the zapping metadata and the viewing metadata are a combination of USD, MPD, and SDP, or a combination of OMA-ESG, USD, MPD, and SDP.
  • the first stream generation unit generates a stream having a sufficiently short minimum unit length when switching the stream, based on source data of the content,
  • the first metadata generation unit describes, in the zapping metadata, information indicating that a stream corresponding to the zapping metadata can be used for zapping applications.
  • Content supply device is not limited to the content supply device.
  • the first metadata generation unit is information indicating that a stream corresponding to the zapping metadata can be used for the zapping stream, information indicating that the division of the minimum unit is NTP synchronized, or the information
  • the at least one of the information indicating that the minimum unit length is in common with other channels is described in the zapping metadata.
  • the division of the minimum unit when switching the stream is in NTP synchronization, and the length of the minimum unit is the zapping stream generated by the first stream generation unit Generating a stream for viewing that is an integral multiple of the minimum unit
  • the first metadata generation unit is asymmetrically in one direction only from the viewing stream generated by the second stream generation unit with respect to the zapping stream corresponding to the zapping metadata. Information is described in the zapping metadata indicating that switching is possible without causing extra delays.
  • the second metadata generation unit is redundant in one direction only in one direction with respect to the zapping stream generated by the first stream generation unit from the viewing stream corresponding to the viewing metadata.
  • the content providing device according to (5), wherein information representing that switching without causing delay is possible is described in the viewing metadata.
  • (7) The content supply device according to any one of (1) to (6), further comprising: a unicast distribution unit configured to unicast the zapping metadata and the viewing metadata via a network.

Landscapes

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

Abstract

La présente invention concerne un dispositif de fourniture de contenu qui permet de réaliser un zapping rapide pendant une diffusion en flux. La présente invention concerne également un procédé de fourniture de contenu, un programme, un dispositif de terminal et un système de fourniture de contenu. Le dispositif de fourniture de contenu de la présente invention génère un flux de zapping d'après des données de source de contenu, génère des métadonnées de zapping pour la réception du flux de zapping, génère, d'après les données de source de contenu, un flux audiovisuel dont la longueur de segments est supérieure à la longueur de segments du flux de zapping, et génère des métadonnées audiovisuelles pour la réception du flux audiovisuel. Les métadonnées de zapping, les métadonnées audiovisuelles, le flux de zapping et le flux audiovisuel sont ensuite distribués par diffusion groupée sur un réseau. La présente invention est applicable à un système de distribution de contenu par diffusion en flux.
PCT/JP2014/068678 2013-07-26 2014-07-14 Dispositif de fourniture de contenu, procédé de fourniture de contenu, programme, dispositif de terminal et système de fourniture de contenu Ceased WO2015012140A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2013155259 2013-07-26
JP2013-155259 2013-07-26

Publications (1)

Publication Number Publication Date
WO2015012140A1 true WO2015012140A1 (fr) 2015-01-29

Family

ID=52393184

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2014/068678 Ceased WO2015012140A1 (fr) 2013-07-26 2014-07-14 Dispositif de fourniture de contenu, procédé de fourniture de contenu, programme, dispositif de terminal et système de fourniture de contenu

Country Status (1)

Country Link
WO (1) WO2015012140A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018142947A1 (fr) * 2017-01-31 2018-08-09 ソニー株式会社 Dispositif et procédé de traitement d'informations

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009284283A (ja) * 2008-05-23 2009-12-03 Sony Corp コンテンツサーバ、情報処理装置、ネットワーク機器、コンテンツ配信方法、情報処理方法およびコンテンツ配信システム
WO2012138909A1 (fr) * 2011-04-05 2012-10-11 Qualcomm Incorporated Distribution de services de transmission en continu de diffusion ip utilisant des procédés de distribution de fichier

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009284283A (ja) * 2008-05-23 2009-12-03 Sony Corp コンテンツサーバ、情報処理装置、ネットワーク機器、コンテンツ配信方法、情報処理方法およびコンテンツ配信システム
WO2012138909A1 (fr) * 2011-04-05 2012-10-11 Qualcomm Incorporated Distribution de services de transmission en continu de diffusion ip utilisant des procédés de distribution de fichier

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
3RD GENERATION PARTNERSHIP PROJECT: "Technical Specification Group Services and System Aspects; Multimedia Broadcast/ Multicast Service (MBMS); Protocols and codecs (Release 11)", 3GPP TS 26.346 VLL.5.0, 27 June 2013 (2013-06-27), pages 24 - 31 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018142947A1 (fr) * 2017-01-31 2018-08-09 ソニー株式会社 Dispositif et procédé de traitement d'informations

Similar Documents

Publication Publication Date Title
US9942619B2 (en) Content supply device, content supply method, program, and content supply system
JP6329964B2 (ja) 送信装置、送信方法、受信装置、及び、受信方法
US10382801B2 (en) Transmission apparatus, transmission method, reception apparatus, and reception method
CN105325005B (zh) 内容供应装置、内容供应方法、存储介质、终端装置以及内容供应系统
JP6570999B2 (ja) コンテンツ供給装置、コンテンツ供給方法、プログラム、端末装置、およびコンテンツ供給システム
JP6630860B2 (ja) 端末装置および受信方法
CN105706453B (zh) 发送装置、发送方法、接收装置和接收方法
US10165035B2 (en) Content supplying device, content supplying method, program, and content supplying system
US10432989B2 (en) Transmission apparatus, transmission method, reception apparatus, receiving method, and program
WO2015041071A1 (fr) Dispositif de transmission de contenu, procédé de transmission de contenu, programme, dispositif de terminal et système de transmission de contenu
WO2014196393A1 (fr) Dispositif de fourniture de contenu, procédé de fourniture de contenu, programme, dispositif terminal, et système de fourniture de contenu
US11075855B2 (en) Content supply device, content supply method, program, terminal device, and content supply system
WO2015012140A1 (fr) Dispositif de fourniture de contenu, procédé de fourniture de contenu, programme, dispositif de terminal et système de fourniture de contenu
WO2015064384A1 (fr) Appareil et procédé de transmission et appareil et procédé de réception

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

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP