FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
(See section 10, rule 13)
“CONTENT SUPPLYING DEVICE, CONTENT SUPPLYING METHOD, PROGRAM, TERMINAL DEVICE, AND CONTENT SUPPLYING PROGRAM”
SONY CORPORATION, of 1-7-1, Konan, Minato-ku, Tokyo 108-0075, Japan
The following specification particularly describes the invention and the manner in which it is to be performed. 2

DESCRIPTION
CONTENT SUPPLY APPARATUS, CONTENT SUPPLY METHOD, PROGRAM, TERMINAL APPARATUS, AND CONTENT SUPPLY SYSTEM
TECHNICAL FIELD5
[0001]
The present disclosure relates to a content supply apparatus, a content supply method, a program, a terminal apparatus, and a content supply system, and more particularly to a content supply apparatus, a content supply method, a 10 program, a terminal apparatus, and a content supply system that are suited to be used when pieces of content of the same content aresupplied through a plurality of delivery paths.
BACKGROUND ART15
[0002]
In recent years, OTT-V (Over The Top Video) has become the mainstream of streaming service that uses the Internet. As an internationally standardized moving image delivery protocol that can beused for OTT-V, there is known MPEG-DASH 20 (Moving Picture Experts Group-Dynamic Adaptive Streaming over HTTP; hereinafter, referred to as DASH) that uses the same HTTP as that for browsing Web sites (see, for example, Non-Patent Document 1).
[0003]25
In DASH, an adaptive streaming technique is implemented. Specifically, a content supplier preparesand deliversa plurality of streams of the same content with different bit rates for different image qualities, different angle-of-viewsizes, etc. On the other hand, acontent receiver selects30 an optimal stream from among the plurality of streams prepared 3

by the supplier, according to a communication environment, decoding capability thereof, etc., and receivesand playsback the selected stream, and further switchesthe stream being received to another according to a change in the communication environment, etc.5
[0004]
Note that the supplier suppliesa metafile called an MPD (Media Presentation Description)to the receiver so that the receivercan adaptively select, receive, and play backa stream.10
[0005]
The MPD describes an address(url information) of a WEBserver (supply source) that suppliesfilesof segment streamswhere content streams(media data such as Audio/Video/Subtitle) arechunked, in response to arequest 15 from the receiver. Based on the url information, the receiveraccesses the WEB server serving as thecontent supply source, to requestafile of a segment stream(hereinafter, also referred to as segment file), and receives and plays back the segment file which is HTTP-unicast from the server in response 20 to the request.
[0006]
Fig. 1 shows an example of a configuration of a content supply system that streams content based on DASH.
[0007]25
This content supply system 10 is composed of a plurality of content supply apparatuses 20 that supply content; and multiple DASH clients 30 that receive and play back the content. The DASH clients 30 can be connected to the content supply apparatuses 20 through a CDN (Contents Delivery Network) 12 30 that uses Internet 11.4

[0008]
Each content supply apparatus 20 deliversa plurality of streams of content of the same content with different bit rates. The content supply apparatus 20 includes a content management server 21, a DASH segment streamer 22, and a DASH 5 MPD server 23.
[0009]
The content management server 21 manages source data of content to be delivered to the DASH clients 30, and generates a plurality of pieces of streaming data with different bit 10 rates from the source data, and outputs the plurality of pieces of streaming data to the DASH segment streamer 22.
[0010]
The DASH segment streamer 22 divides each piece of streaming data into segments in a temporal manner, and thereby 15 generates a segment stream, e.g., fragmented MP4, and converts the generated segment streaminto a fileformatand holds the file. Furthermore, in response to an HTTP request from a DASH client 30 to request a segment file, the DASH segment streamer 22 HTTP-unicasts, as a WEBserver, the segment file held therein 20 to the request source. Furthermore, the DASH segment streamer 22 notifies the DASH MPDserver 23 of metadata including an address indicating a supply source of thesegment files.
[0011]
The DASH MPD server 23 generates an MPD that describes, 25 for example,the address indicating the supply source (i.e., the DASH segment streamer 22) of the segment files. In addition, in response to an HTTP request from the DASH client 30 to request an MPD, the DASH MPD server 23 HTTP-unicasts, as a WEB server, the generated MPD to the request source.30
[0012]5

On the other hand, a DASH client 30 requests the DASH MPD server 23 for an MPD, and obtains the MPDwhich is HTTP-unicast in response to the request. Furthermore, based on the obtained MPD, the DASH client 30 requests the DASH segment streamer 22 for a segment file, and receives and plays back 5 the segment file which is HTTP-unicast in response to the request.
[0013]
Note that the CDN 12 includes a proxy server (not shown), and the proxy server caches MPDs and segment files which are 10 HTTP-unicast throughthe CDN 12. Then, in response to a request from a DASH client 30, the proxy server can HTTP-unicast a cached MPD or segment file to the request source, instead of the DASH MPD server 23 or the DASH segment streamer 22 which serves as a WEB server.15
CITATION LIST
NON-PATENT DOCUMENT
[0014]
Non-Patent Document 1: “Achieving Uninterrupted Video 20 Streaming Using Existing Web Servers”, Mitsuhiro Hirabayashi, NIKKEI ELECTRONICS 2012.3.19
SUMMARY OF THE INVENTION
PROBLEMS TO BE SOLVED BY THE INVENTION25
[0015]
As described above, in DASH, an adaptive streaming technique is implemented by HTTP-unicasting content.
[0016]
Meanwhile, if areceiver can not only receive HTTP 30 unicastthrough the Internet 11, but also receive multicast 6

through various types of networks (terrestrial broadcasting, satellite broadcasting, a cellular communication network, a wireless LAN, etc.), then it is desirable to make those networks availableas DASH delivery paths.Specifically, for example, it is assumed to perform FLUTE-multicast using a 3GPP 5 communication network.
[0017]
Meanwhile, whencontent streamsaresupplied through various delivery paths, it is desirable that instead of the receiver selecting an optimal stream simply by whether 10 reception can be performed, the receiverbe provided withpieces ofgeneral requirednetworkquality information for the case of supplying streamsthrough the respective delivery paths,and be able to select a stream based on thepieces of information.15
[0018]
Specifically, it is considered to provide, for example,description of QoS parameters which are applied to streaming servicein general, description of required receptionquality for the case of receiving broadcasting, and description of 20 required quality for the case of obtaining through a wireless LAN system.
[0019]
The present disclosure is made in view of such circumstances and is to allow, when pieces of content of the 25 same content are supplied through a plurality of different delivery paths,to provide a receiverwithpieces ofgeneral required networkquality information for the respective delivery paths.
30
SOLUTIONS TO PROBLEMS7

[0020]
A content supply apparatuswhich isafirst aspect of the present disclosure delivers streams of content through a plurality of different networks, respectively, according to an adaptive streaming technique, the content supply 5 apparatus including:a generating unit that generates metadata describing QoS parameters for the respective plurality of different networks through which the streams are delivered, and condition values of the QoS parameters; anda delivering unit that delivers the generated metadata to a receiver.10
[0021]
The generating unit may generate an extended USD as the metadata, andthe delivering unit may FLUTE-multicastthe generated extended USD.
[0022]15
The plurality of different networks may include at least one of Internet, a terrestrial broadcast network, a satellite broadcast network, a cable television broadcast network, a mobile broadcast network, and a wireless LAN.
[0023]20
The generating unit may introduce an MPDBaseMapping element in the USD, introduces a RequierdQos element in the MPDBaseMapping element, and may describe, in the RequierdQos element, the QoS parameters for the respective plurality of different networks through which the streams are delivered, 25 and the condition values of the QoS parameters.
[0024]
The generating unit may introducea RequierdQos element in DeliverMethod of the USD, and describe, in the RequierdQos element, the QoS parameters for the respective plurality of 30 different networks through which the streams are delivered, 8

and the condition values of the QoS parameters.
[0025]
A content supply method,which isthefirst aspect of the present disclosure,for a content supply apparatus that delivers streams of content through a plurality of different 5 networks, respectively, according to an adaptive streaming technique, whereinthe content supply apparatus includes:a generating unit that generates metadata describing QoS parameters for the respective plurality of different networks through which the streams are delivered, and condition values 10 of the QoS parameters; anda delivering unit that delivers the generated metadata to a receiver.
[0026]
A program which isthefirst aspect of the present disclosure causesa computer that delivers streams of content 15 through a plurality of different networks, respectively, according to an adaptive streaming technique to function as:a generating unit that generates metadata describing QoS parameters for the respective plurality of different networks through which the streams are delivered, and condition values 20 of the QoS parameters; anda delivering unit that delivers the generated metadata to a receiver.
[0027]
In the first aspect of the present disclosure, metadata that describes QoS parameters for a respective plurality of 25 different networks through which streams are delivered, and condition values of the QoS parameters is generated, and the generated metadata is delivered to a receiver.
[0028]
A terminal apparatus which isasecondaspect of the 30 present disclosure receives a stream delivered from a content 9

supply apparatus that includes:a stream delivering unit that supplies streams of content through a plurality of different networks, respectively, according to an adaptive streaming technique;a generating unit that generates metadata describing QoS parameters for the respective plurality of 5 different networks through which the streams are delivered, and condition values of the QoS parameters; anda metadata delivering unit that delivers the generated metadata to a receiver, the terminal apparatus being configured to:obtain the metadata and receive and play back the stream delivered 10 through any one of the plurality of different networks, according to a determination made based on the obtained metadata as to whether reception can be performed.
[0029]
In the second aspect of the present disclosure, metadata 15 that describes QoS parameters for a respective plurality of different networks through which streams are delivered, and condition values of the QoS parameters is obtained, and a stream delivered through any one of the plurality of different networks is received and played back, according to a 20 determination made based on the obtained metadata as to whether reception can be performed.
[0030]
A content supply system which isathirdaspect of the present disclosure includesa content supply apparatus and 25 a terminal apparatus, whereinthe content supply apparatus includes:a stream delivering unit that supplies streams of content through a plurality of different networks, respectively, according to an adaptive streaming technique;a generating unit that generates metadata describing QoS 30 parameters for the respective plurality of different networks 10

through which thestreams are delivered, and condition values of the QoS parameters; anda metadata delivering unit that delivers the generated metadata to a receiver. On the other hand,the terminal apparatus is configured to:obtain the metadata and receive and play back the stream delivered through 5 any one of the plurality of different networks, according to a determination made based on the obtained metadata as to whether reception can be performed.
[0031]
In the third aspect of the present disclosure, the 10 content supply apparatussupplies streams of content through a plurality of different networks, respectively, according to an adaptive streaming technique, generates metadata that describes QoS parameters for the respective plurality of different networks through which the streams are delivered, 15 and condition values of the QoS parameters, and delivers the generated metadata to areceiver. On the other hand, the terminal apparatusobtains the metadata and receives and plays back a stream delivered through any one of the plurality of different networks, according to a determination made based 20 on the obtained metadata as to whether reception can be performed.
EFFECTS OF THE INVENTION
[0032]25
According to the first aspect of the present disclosure, metadata that describes QoS parameters for a respective plurality of different networks through which streams of content are delivered, and condition values of the QoS parameters can be delivered.30
[0033]11

According to the second aspect of the present disclosure, a determinationas to whether reception can be performed can be made based on metadata that describes QoS parameters for a respective plurality of different networks through which streams of content are delivered, and condition values of the 5 QoS parameters.
[0034]
According to the third aspect of the present disclosure, metadata that describes QoS parameters for a respective plurality of different networks through which streams of 10 content are delivered, and condition values of the QoS parameters can be delivered to the terminal apparatus side, and the terminal apparatus side can make a determination as to whether reception can be performed, based on the metadata.
15
BRIEF DESCRIPTION OF DRAWINGS
[0035]
Fig. 1 is a block diagram showing an example of a configuration of a conventional content supply system.
Fig. 2 is a block diagram showing an exemplary 20 configuration of a content supply system to which the present disclosure is applied.
Fig. 3 is a diagram showing a protocol stack of a USD.
Fig. 4 is a diagram showing a structure of USD metadata before extension.25
Fig. 5 is a diagram showing a structure of USD metadata after extension.
Fig. 6 is a diagram showing a structure of USD metadata after extension.
Fig. 7 is a diagram showing a structure of an 30 MPDBaseUrlMapping element.12

Fig. 8 is a diagram showing another example of disposition of a requiredQoS element.
Fig. 9 is a diagram showing still another example of disposition of therequiredQoS element.
Fig. 10 is a diagram showing an example of QoS parameters 5 for DVB satellite broadcasting/cable television.
Fig. 11 is a diagram showing an example of QoS parameters for DVB cable television.
Fig. 12 is a diagram showing an example of QoS parameters for DVB satellite broadcasting.10
Fig. 13 is a diagram showing an exampleof QoS parameters for terrestrial broadcasting (DVB-T).
Fig. 14 is a diagram showing an example of QoS parameters for terrestrial broadcasting (DVB-T2).
Fig. 15 is a diagram showing an example of QoS parameters 15 for cable television (DVB-C2).
Fig. 16 isa diagram showing an example of QoS parameters for other terrestrial broadcasting.
Fig. 17 is a diagram showing an example of QoS parameters for 3G mobile phone (UTRA FDD) terminals.20
Fig. 18 is a diagram showing an example of QoS parameters for 3G mobile phone (UTRA TDD) terminals.
Fig. 19 is a diagram showing an example of QoS parameters for LTE (E-UTRA) terminals.
Fig. 20 is a diagram showing an example of Qosparameters 25 for ATSC physical layer.
Fig. 21 is a flowchart describing the operation of a content supply apparatus.
Fig. 22 is a block diagram showing an exemplary configuration of a computer.30 13

MODE FOR CARRYING OUT THE INVENTION
[0036]

Fig. 2 shows an exemplary configuration of a content supply system which is an embodiment of the present disclosure.5
[0037]
A content supply system 50 is composed of a plurality of content supply apparatuses 60 and multiple terminal apparatuses 80. The content supply apparatuses 60 and the terminal apparatuses 80 can be connected to each other through 10 a network 51.
[0038]
The network 51 includes various types of broadcast networks using terrestrial broadcast waves, satellite broadcast waves, and (e)MBMS, and wireless LANs such as Wi-Fi, 15 in addition to bidirectional communication networksrepresented by the Internet and a CDN 52 using the Internet.
[0039]
The content supply apparatuses 60 not only HTTP-unicastcontent streams, but also multicast content streams. Here, 20 the multicast includes broadcast/multicast on a point-to-point bearer, in addition to broadcast/multicast on a point-to-multipoint bearer through the network 51. Note, however, that the following description only refers to FLUTE-multicast as a representative of multicast.25
[0040]
Each content supply apparatus 60 includes a channel server 61, a segmenter 62, an MPD generator 63, a FLUTE streamer 64, a WEB server65, and a multicast server 66.
[0041]30
Note that the channel server 61 to the multicast server 14

66 of the content supply apparatus 60 may be collectively disposed at one location, or may be disposed in a distributed manner through the Internet, etc.
[0042]
The channel server 61 generates a plurality of pieces 5 of streaming data with different bit rates from source data of content to be delivered to the terminal apparatuses 80, and outputs the plurality of pieces of streaming data to the segmenter 62.
[0043]10
The segmenter 62 divides each piece of streaming data into segments in a temporal manner, and thereby generates a segment stream, e.g., fragmented MP4, and outputs the generated segment streamto the FLUTE streamer 64 and the WEB server65. In addition, the segmenter 62 notifies the MPD generator 15 63 of metadata including an address indicating a supply source of thesegment streams.
[0044]
Based on the metadata notified by the segmenter 62, the MPD generator 63 generates an MPD that describes, for example,20 an address indicating a delivery source (WEB server65) used when thesegment filesareHTTP-unicast, and outputs the MPD to the FLUTE streamer 64 and the WEB server65. The MPD describes an obtaining destination of an SDP (Session Description) that describes thedestination IP addressesof 25 FLUTE sessions ofFLUTE streams which areFLUTE-multicast and to which a segment streamto be HTTP-unicast can be switched.
[0045]
The FLUTE streamer 64 divides thesegmentstreamswhich are sequentially inputted from the segmenter 62,and stores 30 the divided portions in ALC packets and thereby converts the 15

segmentstreamsinto FLUTE streams, and outputs the FLUTE streamsto the multicast server 66. In addition, the FLUTE streamer 64 stores the MPD generated by the MPD generator 63 in an ALC packet, and outputs the ALC packet to the multicast server 66.5
[0046]
Furthermore, the FLUTE streamer 64 describes a USD (User Service Bundle Description)that includes anSDP describing address information ofFLUTE sessionsand that is extended so as to be able to further describepieces ofgeneral required 10 networkquality information for the respectivestreamswhich aredelivered through the network 51, and outputs the USD to the multicast server 66. The USD will be described in detail with reference to Fig. 3 and subsequent drawings.
[0047]15
In response to an HTTP request requesting an MPD,which is sent from a terminal apparatus 80, the WEB server65 HTTP-unicaststhe MPD inputted from the MPD generator 63, to the request source. In addition, in response to an HTTP request requesting a segment file,which is sentfrom theterminal 20 apparatus 80, the WEB server65 HTTP-unicasts the segment file held therein to the request source.
[0048]
The multicast server 66 FLUTE-multicasts the MPD and USD inputted from the FLUTE streamer 64. In addition, the 25 multicast server 66 FLUTE-multicasts the FLUTE streamsinputted from the FLUTE streamer 64.
[0049]
A terminal apparatus 80 obtains an MPD from a content supply apparatus 60 through the network 51. Specifically, 30 the terminal apparatus 80 sends anHTTP request requesting 16

an MPDand receives anMPD which is HTTP-unicast in response to the HTTP request,or receives anMPD which is FLUTE-multicast. Note that when the terminal apparatus 80 receives anMPD which is FLUTE-multicast, announcement information that describes a portal channel of the multicast server 66 that performs 5 FLUTE-multicast is referred to.
[0050]
The announcement information is announcedusing, for example, an SDP (Session Description) element of a USD which is signaling metadata. The USD is transferred through 10 FLUTE/UDP/IP (Multicast or Unicast).
[0051]
Furthermore, the terminal apparatus 80 sends an HTTP request requesting a segment streamto the WEB server65,based on the obtained MPD, and receives and plays back a segment 15 streamfile which is HTTP-multicast in response to the HTTP request.
[0052]
Moreover, the terminal apparatus 80 obtains a USD including an SDP, based on the obtainedMPDand receives and 20 plays back a FLUTE stream which is FLUTE-multicast based on the SDP.
[0053]
Note that there may be a case in which instead of the WEB server65, a proxy server present on the CDN 52 responds 25 to an HTTP request sent from the terminal apparatus 80, and the proxy server HTTP-unicasts an MPD or segment request cached therein.
[0054]
[Extension of theUSD]30
As described above, the USD is used to announcea portal 17

channel where FLUTE-multicast is performed. In addition to that, in the present embodiment, the USD is also used for an application of providing areceiver with general required networkquality information forthe respective paths through which pieces of contentare delivered.5
[0055]
Fig. 3 shows a protocol stack for the case of delivering a USD using MBMS.
[0056]
The USD is stored in Service Announcement&Metadata 91, 10 and is FLUTE-multicast through a broadcast/multicast channel.
[0057]
Next,Fig. 4 shows a structure of USD metadata before extension, and Figs. 5 and 6 show a structure of extended USD metadata. In the present embodiment, as shown in Fig. 5, 15 MPDBaseUrlMapping 101 (“r12:MPDBaseUrlMapping” in Fig. 6) is introduced as a new element under UserServiceDescription.
[0058]
The MPDBaseUrlMapping element 101 is to indicatea distinction as towhether the baseUrl of each of AdaptationSet 20 and Representation described inan MPD (an MPD that describesstreams (segment streams, etc.) to be switched toFLUTE streamsthat areannouncedby this USD) which isreferred to by MediaPresentationDescription,is multicast or unicast.
[0059]25
Next, Fig. 7 shows a structure of the MPDBaseUrlMapping element 101.
[0060]
The MPDBaseUrlMapping element 101 stores a broadcast element(list)and a unicastelement (list). The broadcast 30 elementstores a baseURL attribute indicating one that is 18

multicast (including broadcast) between the baseUrls of AdaptationSet and Representation described in a corresponding MPD. Furthermore, the broadcast element stores a sessionDescription attribute that stores a reference to sessionDescription associated with the stored baseUrl 5 attribute; and a requiredQoS element 111 that storesQoS parameters(required networkquality information) fordelivery paths.
[0061]
The unicast element stores a baseURL attribute 10 indicating one that is unicast between thebaseUrls of AdaptationSet and Representation described in the corresponding MPD.
[0062]
An MPDBaseUrlMapping/@mpdURI attribute stores a URL of 15 an MPD file to be referred to.
[0063]
Note that the disposition of the requiredQoS element 111 that stores QoS parameters (required networkquality information) fordelivery pathsis not limited to the example 20 shown in Fig. 7. For example, the requiredQoS element 111 may be disposed as shown in Fig. 8.
[0064]
Figs. 8 and 9 show an example in which the requiredQoS element 111 is disposed under a DeliveryMethod element of USD 25 metadata.
[0065]

The requiredQoS element stores a parameterURI attribute 30 that specifies a QoS parameterrequired to tune a content 19

delivery path; and a requiredValue element(“upperLimit (upper limit)”, “lowerLimit (lower limit)”, or “just (specified value)”) as a condition value of the parameterURI attribute.
[0066]
5
Exemplary description of QoS parameters will be specifically described. For example, QoE parameters applied to streaming service in generalinclude delay, delay jitter, loss (error), throughput, etc. Of them, the throughput is describedas:10
RequiredQoS/@parameterURI=urn:DownLinkThroughput (a unique identifier indicating downlink throughput), and when a lower limit thereof is specified as a condition value, the condition value is specified as:
RequiredQoS/requiredValue/@lowerLimit=“3Mbps” 15 (which means that the lower limit of the downlink throughput is 3 Mbps).
[0067]
In addition, for example, representative parameters indicating the physical layer signal quality of a broadcast 20 or a mobile phone terminal for the case of receiving a broadcast or the case of receiving a stream through a wireless LAN such as Wi-Fi, include a parameter related to radio field intensity and a parameter related to biterror rate (BER). More specifically, examples of the former include carrier-to-noise 25 ratio (CN ratio) and received signal strength indicator (RSSI). Examples of the latter include bit error rates before/after an error correction process such as Reed Solomon (RS) (which varies depending on the broadcast/communication scheme) (BER before/after RS), and transport block error rate (BLER).30
[0068]20

Of them, the CN ratio is described as:
RequiredQoS/@parameterURI=urn:CarrierToNoiseRatio (a unique identifier indicating CN ratio), and when a lower limit thereof is specified as a condition value, the condition value is described as:5
RequiredQoSParameter/requiredValue/@lowerLimit=
“10dB” (which means that the lower limit of the CN ratio is 10 dB).
[0069]
In addition, when the CN ratio is classified into some 10 classes (e.g., three classes) ascondition valuesand evaluated,
the condition values are defined as:
level 1 (specified as“urn:CNclass1”):10-3or more (bad),15
level 2 (specified as“urn:CNclass2”):10-5or moreand less than 10-3(fair), and
level 3 (specified as“urn:CNclass3”): less than 10-5(good), and then
the CN ratio is described as:20
RequiredQoS/@parameterURI=urn:CarrierToNoiseRatio (a unique identifier indicating C/N), and the condition valuesare specified as:
RequiredQoS/requiredClass/@class=“urn:CNclass2”
RequiredQoS/requiredClass/@class=“urn:CNclass3” 25 (which means that the CN ratio of class 2 or 3 is required).
[0070]
Note that, for the QoS parameters stored in the requiredQoS element, in addition to the above-described examples, parameters shown below can be described.30
[0071]21

Fig. 10 shows an example of QoS parameters for DVB satellite broadcasting/cable television. Fig. 11 shows an example of QoS parameters for DVB cable television. Fig. 12 shows an example of QoS parameters for DVB satellite broadcasting. Fig. 13 shows an example of QoS parameters for 5 terrestrial broadcasting (DVB-T). The examples of QoS parameters shown in Figs. 10 to 13 are all defined in ETSI TR 101 290 V1.2.1 (2001-05), “Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems”.
[0072]10
Fig. 14 shows an example of QoS parameters for terrestrial broadcasting (DVB-T2). Theseare defined in DVB BlueBook A14-2 (07/12), “Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems; Amendment for DVB-T2 System”.15
[0073]
Fig. 15 shows an example of QoS parameters for cable television (DVB-C2). Theseare defined in DVB BlueBook A14-3 (03/13), “Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems; Amendment for DVB-C2 System”.20
[0074]
Fig. 16 shows an example of QoS parameters for other terrestrial broadcasting. Theseare defined in NorDig Unified ver2.4.
[0075]25
Fig. 17 shows an example of QoS parameters for 3G mobile phone(UTRA FDD) terminals. Theseare defined in ETSI TS 125 215 V11.0.0 (2012-11); “Universal Mobile Telecommunications System (UMTS); Physical layer; Measurements (FDD) (3GPP TS 25.215 version 11.0.0 Release 11)”.30
[0076]22

Fig. 18 shows an example of QoS parameters for 3G mobile phone (UTRA TDD) terminals. Theseare defined in ETSI TS 125 225 V11.0.0 (2012-09); “Universal Mobile Telecommunications System (UMTS); Physical layer; Measurements (TDD) (3GPP TS 25.225 version 11.0.0 Release 11)”.5
[0077]
Fig. 19 isa diagram showing an example of QoS parameters for LTE (E-UTRA) terminals. Theseare defined in ETSI TS 136 214 V11.1.0 (2013-02); “LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements (3GPP TS 10 36.214 version 11.1.0 Release 11)”.
[0078]
Fig. 20 is a diagram showing an example of QoS parameters for ATSC physical layer. Theseare described in “Guide to the Use of the ATSC Digital Television Standard”, December 15 4, 2003.
[0079]
[Operation of the content supply system 50]
Next, the operation of the content supply system 50 will be described.20
[0080]
Fig. 21 is a flowchart describing processes performed by a content supply apparatus 60 that HTTP-unicastscontent streamsand FLUTE-multicasts content streams.
[0081]25
At step S1, the channel server 61 of the content supply apparatus 60 generates a plurality of pieces of streaming data with different bit rates from source dataof content to be delivered to theterminal apparatuses80, and outputs the plurality of pieces of streaming data to the segmenter 62. 30 At step S2, the segmenter 62 generates a segment streamsuch 23

as fragmented MP4, based on each piece of streaming data,and outputsthe generated segment streamto the FLUTE streamer 64 and the WEB server65. In addition, thesegmenter 62 notifies the MPD generator 63 of metadata including an address indicating a supply source of the segmentstreams.5
[0082]
At step S3, the FLUTE streamer 64 divides the segmentstreamswhich aresequentially inputted from the segmenter 62, andstores the divided portionsin ALC packets and thereby converts the segmentstreams into FLUTE streams, and outputs 10 the FLUTE streamsto the multicast server 66.
[0083]
At step S4, the MPD generator 63 generates an MPD based on the metadata notified by the segmenter 62, and outputs the MPD to the FLUTE streamer 64 and the WEB server65. The FLUTE 15 streamer 64 stores the MPD generated by the MPD generator 63 in an ALC packet and outputs the ALC packet to the multicast server 66. In addition, the FLUTE streamer 64 describes a USD that includes an SDP aboutFLUTE sessionsand that is extended so as to be able to further describe Qos parameters 20 forthe respective streamswhich aredelivered through the network 51, and outputs the USD to the multicast server 66.
[0084]
At step S5, the multicast server 66 FLUTE-multicasts the MPD and USD inputted from the FLUTE streamer 64.25
[0085]
At step S6, in response to an HTTP request requesting an MPD,which is sent from a terminal apparatus 80, the WEB server65 HTTP-unicasts the MPD inputted from the MPD generator 63, to the request source. At step S7, in response to an HTTP 30 request requesting a segment file based on the MPD,which is 24

sent from the terminal apparatus 80, the WEB server65 HTTP-unicasts the segment fileheld therein to the request source.
[0086]
At step S8, the multicast server 66 FLUTE-multicasts 5 theFLUTE streamsinputted from the FLUTE streamer 64. Note that FLUTE-multicasting oftheFLUTE streamscan also be performed in real time simultaneously with the generationofsegmentstreamsbased on which the FLUTE streamsaregenerated. Description of the processes of the content supply apparatus 10 60 endshere.
[0087]
On the other hand, aterminal apparatus 80 sends an HTTP request requesting an MPDand receives anMPD which is HTTP-unicast in response to the HTTP request,or receives an15 MPD which is FLUTE-multicast, and requests a segment streamfile based on the MPD, and can receive and play back the segment streamfile which is HTTP-unicast in responseto the request. In addition, a FLUTE session can be received based on an SDP of a USD which is FLUTE-multicast. Furthermore, after 20 determining,based on Qos parameters described in a requiredQoS element of the USD,whethereach stream can be appropriately received, reception and playback can be performed.
[0088]
Meanwhile, the content supply apparatuses 60 that 25 perform the above-described series of processes and the terminal apparatuses 80 each can not only be configured by hardware, but also implemented by a computer executing software. The computer includes, for example,a computerthat isincorporated in dedicated hardware and a general-purpose 30 personal computer, for example, that can perform various types 25

of functions by installing various types of programs.
[0089]
Fig. 22 is a block diagram showing an exemplary hardware configuration of the above-described computer.
[0090]5
In this computer 200, a CPU (Central Processing Unit) 201, a ROM (Read Only Memory) 202, and a RAM (Random Access Memory) 203 are connected to each other through a bus 204.
[0091]
An input/output interface 205 is further connected to 10 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.
[0092]
The input unit 206 is composed of a keyboard, a mouse, 15 a microphone, etc. The output unit 207 is composed of a display, a speaker, etc. The storage unit 208 is composed of a hard disk, a nonvolatile memory, etc. The communication unit 209 is composed of a network interface, etc. The drive 210 drives a removable medium 211 such as a magnetic disk, an optical 20 disk, a magneto-optical disk, or a semiconductor memory.
[0093]
In the computer 200 configured in the above-described manner, the above-described series of processes are performed by the CPU 201, for example, loading and executing a program 25 stored in the storage unit 208, in the RAM 203 through the input/output interface 205 and the bus 204.
[0094]
The program executed by the computer 200 (CPU 201) can be provided by, for example, being recorded in the removable 30 medium 211 serving as a package medium, etc. In addition, 26

the program can be provided through a wired or wireless transmission medium such as a local area network, the Internet, or digital satellite broadcasting.
[0095]
In the computer 200, by placing the removable medium 5 211 having recorded therein a program into the drive 210, the program can be installed on the storage unit 208 through the input/output interface 205. In addition, a program can beinstalled on the storage unit 208 by the communication unit 209 receiving the program through a wired or wireless 10 transmission medium. In additionto the above, a program can be pre-installed on the ROM 202 or the storage unit 208.
[0096]
Note that the program executed by the computer 200 may be a program that performs processes chronologically in the 15 order described in this specification, or may be a program that performs processes in parallel or at required timing suchas when a call is issued.
[0097]
The embodiment of the present disclosure is not limited 20 to the above-described one, and various changes may be made thereto without departing from the true spirit and scope of the present disclosure.
[0098]
The present disclosure can also employ configurations 25 such as those shown below.
(1)
A content supply apparatus that delivers streams of content through a plurality of different networks, respectively, according to an adaptive streaming technique, 30 the content supply apparatus including:27

a generating unit that generates metadata describing QoS parameters for the respective plurality of different networks through which the streams are delivered, and condition values of the QoS parameters; and
a delivering unit that delivers the generated metadata 5 to a receiver.
(2)
The content supply apparatus according to (1), wherein
the generating unit generates an extended USD as the metadata, and10
the delivering unit FLUTE-multicasts the generated extended USD.
(3)
The content supply apparatus according to (1) or (2), wherein the plurality of different networks include at least 15 one of Internet, a terrestrial broadcast network, a satellite broadcast network, a cable television broadcast network, a mobile broadcast network, and a wireless LAN.
(4)
The content supply apparatus according to (2) or (3), 20 wherein the generating unit introduces an MPDBaseMapping element in the USD, introduces a RequierdQos element in the MPDBaseMapping element, and describes, in the RequierdQos element, the QoS parameters for the respective plurality of different networks through which the streams are delivered, 25 and the condition values of the QoS parameters.
(5)
The content supply apparatus according to (2) or (3), wherein the generating unit introducesa RequierdQos element in DeliverMethod of the USD, and describes, in the RequierdQos 30 element, the QoS parameters for the respective plurality of 28

different networks through which the streams are delivered, and the condition values of the QoS parameters.
(6)
A content supply method for a content supply apparatus that delivers streams of content through a plurality of 5 different networks, respectively, according to an adaptive streaming technique, wherein
the content supply apparatus includes:
a generating unit that generates metadata describing QoS parameters for the respective plurality of different 10 networks through which the streams are delivered, and condition values of the QoS parameters; and
a delivering unit that delivers the generated metadata to a receiver.
(7)15
A program causing a computer that delivers streams of content through a plurality of different networks, respectively, according to an adaptive streaming technique to function as:
a generating unit that generates metadata describing 20 QoS parameters for the respective plurality of different networks through which the streams are delivered, and condition values of the QoS parameters; and
a delivering unit that delivers the generated metadata to a receiver.25
(8)
A terminal apparatus that receives a stream delivered from a content supply apparatus that includes:
a stream delivering unit that supplies streams of content through a plurality of different networks, respectively, 30 according to an adaptive streaming technique;29

a generating unit that generates metadata describing QoS parameters for the respective plurality of different networks through which the streams are delivered, and condition values of the QoS parameters; and
a metadata delivering unit that delivers the generated 5 metadata to a receiver, the terminal apparatus being configured to:
obtain the metadata and receive and play back the stream delivered through any one of the plurality of different networks, according to a determination made based on the 10 obtained metadata as to whether reception can be performed.
(9)
A content supply system including a content supply apparatus and a terminal apparatus, wherein
the content supply apparatus includes:15
a stream delivering unit that supplies streams of content through a plurality of different networks, respectively, according to an adaptive streaming technique;
a generating unit that generates metadata describing QoS parameters for the respective plurality of different 20 networks through which the streams are delivered, and condition values of the QoS parameters; and
a metadata delivering unit that delivers the generated metadata to a receiver, and
the terminal apparatus is configured to:25
obtain the metadata and receive and play back the stream delivered through any one of the plurality of different networks, according to a determination made based on the obtained metadata as to whether reception can be performed.
30
REFERENCE SIGNS LIST30

[0099]
50Content supply system
51Network
52CDN
60Content supply apparatus5
61Channel server
62Segmenter
63MPD generator
64FLUTE streamer
65WEBserver10
66Multicast server
67WEBserver
80Terminal apparatus
100Computer
101CPU15 31

CLAIMS
1.A content supply apparatus that delivers streams of content through a plurality of different networks, respectively, according to an adaptive streaming technique, 5 the content supply apparatus comprising:
a generating unit that generates metadata describing QoS parameters for the respective plurality of different networks through which the streams are delivered, and condition values of the QoS parameters; and10
a delivering unit that delivers the generated metadata to a receiver, wherein
the QoS parameters are delay, delay jitter, loss, throughput, radio field intensity, or bit error rate, and
the condition values are an upper limit, a lower limit, 15 or a specified value.
2.The content supply apparatus according to claim 1, wherein
the generating unit generates an extended USD as the 20 metadata, and
the delivering unit FLUTE-multicasts the generated extended USD.
3.The content supply apparatus according to claim 2, 25 wherein the plurality of different networks include at least one of Internet, a terrestrial broadcast network, a satellite broadcast network, a cable television broadcast network, a mobile broadcast network, and a wireless LAN.
30
4.The content supply apparatus according to claim 2, 32

wherein the generating unit introduces an MPDBaseMapping element in the USD, introduces a RequiredQos element in the MPDBaseMapping element, and describes, in the RequiredQos element, the QoS parameters for the respective plurality of different networks through which the streams are delivered, 5 and the condition values of the QoS parameters.
5.The content supply apparatus according to claim 2, wherein the generating unit introduces a RequiredQos element in DeliverMethod of the USD, and describes, in the RequiredQos 10 element, the QoS parameters for the respective plurality of different networks through which the streams are delivered, and the condition values of the QoS parameters.
6.A content supply method for a content supply apparatus 15 that delivers streams of contentthrough a plurality of different networks, respectively, according to an adaptive streaming technique, wherein
the content supply apparatus includes:
a generating unit that generates metadata describing 20 QoS parameters for the respective plurality of different networks through which the streams are delivered, and condition values of the QoS parameters; and
a delivering unit that delivers the generated metadata to a receiver,25
the QoS parameters are delay, delay jitter, loss, throughput, radio field intensity, or bit error rate, and
the condition values are an upper limit, a lower limit, or a specified value.
30
7.A program causing a computer that delivers streams of 33

content through a plurality of different networks, respectively, according to an adaptive streaming technique, to function as:
a generating unit that generates metadata describing QoS parameters for the respective plurality of different 5 networks through which the streams are delivered, and condition values of the QoS parameters; and
a delivering unit that delivers the generated metadata to a receiver, wherein
the QoS parameters are delay, delay jitter, loss, 10 throughput, radio field intensity, or bit error rate, and
the condition values are an upper limit, a lower limit, or a specified value.
8.A terminal apparatus that receives a stream delivered 15 from a content supply apparatus that includes:
a stream delivering unit that supplies streams of content through a plurality of different networks, respectively, according to an adaptive streaming technique;
a generating unit that generates metadata describing 20 QoS parameters for the respective plurality of different networks through which the streams are delivered, and condition values of the QoS parameters; and
a metadata delivering unit that delivers the generated metadata to a receiver, the terminal apparatus being configured 25 to:
obtain the metadata and receive and play back the stream delivered through any one of the plurality of different networks, according to a determination made based on the obtained metadata as to whether reception can be performed, 30 wherein34

the QoS parameters are delay, delay jitter, loss, throughput, radio field intensity, or bit error rate, and
the condition values are an upper limit, a lower limit, or a specified value.
5
9.A content supply system including a content supply apparatus and a terminal apparatus, wherein
the content supply apparatus includes:
a stream delivering unit that supplies streams of content through a plurality of different networks, respectively, 10 according to an adaptive streaming technique;
a generating unit that generates metadata describing QoS parameters for the respective plurality of different networks through which the streams are delivered, and condition values of the QoS parameters; and15
ametadata delivering unit that delivers the generated metadata to a receiver,
the terminal apparatus is configured to:
obtain the metadata and receive and play back the stream delivered through any one of the plurality of different 20 networks, according toa determination made based on the obtained metadata as to whether reception can be performed,
the QoS parameters are delay, delay jitter, loss, throughput, radio field intensity, or bit error rate, and
the condition values are an upper limit, a lower limit, 25 or a specified value.