L connecting the User Service Bundle Description 61 and the User Service Description 62 indicates that the User Service Bundle Description 61 at the opposite side of the link L to the description "1..N" contains (or refers to) the number in the range from one to N of the User Service 5 Descriptions 62.
[0157]
Furthermore, a description "1" at the User Service Bundle Description 61 side of the link L indicates that the User Service Description 62 at the opposite side of 10 the link L to the description "1" is contained in (or referred by) a User Service Bundle Description 61.
[0158]
These are similarly applied to Fig. 15 to be described later.15
[0159]
Fig. 10 is a diagram illustrating examples of an element and an attribute of an extensible markup language (XML) which constitute a USD described in XML as thumbnail metadata.20
[0160]
A USD includes bundleDescription (element), bundleDescription/UserServiceDescription (element), bundleDescription/userServiceDescription/@serviceId (attribute), 25 bundleDescription/userServiceDescription/DeliveryMethod (element), and bundleDescription/userServiceDescription/DeliveryMethod/@sessionDescriptionURI (attribute).
[0161]30
Here, for example, the 34

bundleDescription/UserServiceDescription indicates that UserServiceDescription (element) is an element contained in the bundleDescription (element), and hereinafter is also referred to as UserServiceDescription or /UserServiceDescription.5
[0162]
Furthermore, for example, the bundleDescription/userServiceDescription/@serviceId indicates that serviceId is an attribute belonging to the /userServiceDescription, and hereinafter is also referred 10 to as serviceId or /@serviceId.
[0163]
A bundleDescription element is information on a collection of one or more services, and a UserServiceDescription element is information on an 15 individual service.A serviceId attribute is a service identifier to identify a service, and a DeliveryMethod element is information on a method for distributing content supplied by a service.
[0164]20
A sessionDescriptionURI attribute indicates information to refer to a file including information to receive content supplied by a service.
[0165]
As a file including information to receive content 25 supplied by a service, for example, an SDP (file) is adopted.
[0166]
When an SDP is adopted as a file including information to receive content supplied by a service and 30 the content is distributed by multicast, information 35

including the IP address and the port number of the multicast is adopted as information to receive content supplied by a service.Furthermore, to the sessionDescriptionURI attribute indicating information to refer to an SDP, the URI and the like of the SDP is set 5 as an attribute value.
[0167]
An USD as thumbnail metadata includes the thumbnail signaling information in addition to the above bundleDescription element, UserServiceDescription element, 10 serviceIdattribute, DeliveryMethod element, and sessionDescriptionURI attribute.
[0168]
Note that, as thumbnail metadata, instead of the above bundleDescription element, UserServiceDescription 15 element, serviceId attribute, DeliveryMethod element, sessionDescriptionURI attribute, and USD including the thumbnail signaling information, arbitrary metadata including the thumbnail signaling information and information equivalent to one or more of the 20 bundleDescription element, the UserServiceDescription element, the serviceId attribute, the DeliveryMethod element, and the sessionDescriptionURI attribute can be adopted.
[0169]25
Fig. 11 is a diagram illustrating an example of an USD described in XML as thumbnail metadata.
[0170]
A BundleDescription element 71 is equivalent to the User Service Bundle Description 61 of Fig. 9 and is a 30 root element of the USD.36

[0171]
A UserServiceDescription element 72 is equivalent to the User Service Description 62 of Fig. 9.The UserServiceDescription element 72 is contained in the bundleDescription element 71 and is equivalent to an 5 individual service.
[0172]
A /@r7:serviceClass attribute 73 belongs to the UserServiceDescription element 72.Here, "r7" in the /@r7:serviceClass attribute 73 indicates that the 10 /@r7:serviceClass attribute 73 is introduced in release 7 of the 3GPP specifications.
[0173]
With regard to the USD as thumbnail metadata, "urn:MosaicableComponents" is newly adopted as a scheme 15 identifier (class name of serviceClass) as the attribute value of the /@r7:serviceClass attribute 73.
[0174]
The new attribute value "urn:MosaicableComponents" indicates that the service (channel) which distributes 20 the video corresponding to the USD describing the /@r7:serviceClass attribute 73 to which the attribute value "urn:MosaicableComponents" is set (the video whose information is described in the USD) is a service which distributes (a video including) a thumbnail video 25 suitable for constituting a mosaic screen.
[0175]
Thus, the /@r7:serviceClass attribute 73 to which the attribute value "urn:MosaicableComponents" is set functions as the thumbnail signaling information 30 indicating that a video is the thumbnail video (serves as 37

the thumbnail signaling information).
[0176]
Note that, in the USD of Fig. 11, a /@thumbnailVideo attribute, which will be described later, in addition to the /@r7:serviceClass attribute 73 also 5 functions as the thumbnail signaling information.Thus, the /@r7:serviceClass attribute 73 as the thumbnail signaling information can be omitted.
[0177]
A /DeliveryMethod element 74 is equivalent to the 10 Delivery Method 63 of Fig. 9 and includes a /@sessionDescriptionURI attribute 75.
[0178]
To the /@sessionDescriptionURI attribute 75, a URI of an SDP 121 (information to refer to the SDP 121) 15 describing an IP address and a port number of multicast is set in order to receive the content supplied by the service whose information is described in the USD including the /@sessionDescriptionURI attribute 75.
[0179]20
Each of descriptions 80, 90, and 100 is a description in which the /r12:appServiceDescription element is the highest (hierarchy) element, and is the information on the content which is capable constituting a mosaic screen MZ and supplied by a different service 25 (channel) (broadcasting station).
[0180]
Thus, the USD includes the /r12:appServiceDescription element of each of the contents capable of constituting a mosaic screen.30
[0181]38

Here, the descriptions 80, 90, and 100 are the information on the content supplied by service ch#1, ch#2, and ch#3 respectively.
[0182]
The description 80 includes a 5 /r12:appServiceDescription element 81 contained in /the UserServiceDescription element 72.The /r12:appServiceDescription element 81 is information to signal the client 13 as to whether (a segment of) content supplied by the service ch#1 is to be distributed by 10 multicast (or to be distributed by broadcast) or to be distributed by unicast.
[0183]
The /r12:appServiceDescription element 81 includes a /@mpdURI attribute, and further includes (contains) 15 either or both of one or more /broadcast elements or/and one or more /unicast elements.
[0184]
Here, a URI of an MPD is set to the /@mpdURI attribute in order for the /r12:appServiceDescription 20 element including the /@mpdURI attribute to perform the reproduction control of content indicating a distribution method.
[0185]
The /broadcast element includes a baseURL attribute 25 indicating a URL of content whose distribution method is indicated by the /r12:appServiceDescription element including the /broadcast element, and indicates that the content whose URL is indicated by the baseURL attribute is to be distributed by multicast.30
[0186]39

The /unicast element includes a baseURL attribute indicating a URL of content whose distribution method is indicated by the /r12:appServiceDescription element including the /unicast element, and indicates that the content whose URL is indicated by the baseURL attribute 5 is to be distributed by unicast.
[0187]
In Fig. 11, the /r12:appServiceDescription element 81 in the description 80 includes a /@mpdURI attribute 82, and further includes a /broadcast element 83 and two 10 /unicast elements 86 and 87.
[0188]
The /r12:appServiceDescription element 81 includes the /broadcast element 83 and the two /unicast elements 86 and 87, and thus it is possible to recognize that 15 there is a stream to be distributed by multicast and there are two streams to be distributed by unicast as (the stream of) the content of the service ch#1 whose distribution method is indicated by the /r12:appServiceDescription element 81.20
[0189]
To the /@mpdURI attribute 82, a URI of an MPD 111 of content supplied by the service ch#1 is set.
[0190]
The /broadcast element 83 indicates that a stream 25 1311of content supplied by the service ch#1 is to be distributed by multicast, and includes a /@baseURL attribute and a /@thumbnailVideo attribute in Fig. 11
[0191]
To the /@baseURL attribute included in the 30 /broadcast element 83, the URL of the stream 1311of the 40

content indicating that the /broadcast element 83 is to be distributed by multicast, that is, AdaptasionSet/baseURL 111A of the stream 1311described in the MPD 111 of the content of the service ch#1 indicating that the /broadcast element 83 is to be 5 distributed by multicast is set.
[0192]
The /@thumbnailVideo attribute included in the /broadcast element 83 is a boolean type attribute, and functions as the thumbnail signaling information 10 indicating whether the stream 1311of the content indicating that the /broadcast element 83 is to be distributed by multicast is (the stream of) the thumbnail video.
[0193]15
In Fig. 11, the stream 1311is a stream of a thumbnail video TS#1.
[0194]
The /broadcast element 83 further includes a /association element 84, and the /association element 84 20 includes a /sessionDescription element 85.
[0195]
The /sessionDescription element 85 indicates the URI of the SDP 121 describing the IP address and the port number to which the stream 1311, of the content 25 indicating that the /broadcast element 83 is to be distributed by multicast, is to be distributed by multicast.In other words, the /sessionDescription element 85 indicates the same SDP 121 as (the URI of) the SDP 121 indicated by the /@sessionDescriptionURI 30 attribute 75.41

[0196]
The /unicast element 86 indicates that another stream (for example, a stream of a main video MS#1) of content supplied by the service ch#1 is to be distributed by unicast, and includes the /@baseURL attribute.5
[0197]
To the /@baseURL attribute included in the /unicast element 86, the URL of another stream of the content indicating that the /unicast element 86 is to be distributed by unicast, that is, AdaptasionSet/baseURL 10 111B of another stream described in the MPD 111 of the content indicating that the /unicast element 86 is to be distributed by unicast is set.
[0198]
The /unicast element 87 indicates that other stream 15 (for example, a stream of audio) of content supplied by the service ch#1 is to be distributed by unicast, and includes the /@baseURL attribute.
[0199]
To the /@baseURL attribute included in the /unicast 20 element 87, the URL of other stream of the content indicating that the /unicast element 87 is to be distributed by unicast, that is, AdaptasionSet/baseURL 111C of other stream described in the MPD 111 of the content indicating that the /unicast element 87 is to be 25 distributed by unicast is set.
[0200]
In each of the descriptions 90 and 100 in the services ch#1 and ch#2, information similar to the description 80 is included.30
[0201]42

Here, in Fig. 11, a /r12:appServiceDescription element 91 to a /unicast element 97 are similar information on the /r12:appServiceDescription element 81 to the /unicast element 87 respectively.
[0202]5
Furthermore, MPDs 112 and 113 are the MPDs of the contents supplied by the services ch#2 and ch#3 respectively.
[0203]
In the service ch#2 (similarly in the services ch#1 10 and ch#3), (a stream of) a thumbnail video TS#2 is to be distributed by multicast, and (streams of) a main video MS#2 and audio are to be distributed by unicast. In the MPD112, the AdaptasionSet/baseURLs (and the segmentURLs) of them, that is, AdaptasionSet/baseURL 112A of the 15 thumbnail video TS#2, AdaptasionSet/baseURL 112B of the main video MS#2, and AdaptasionSet/baseURL 112C of the audio are described.
[0204]
Moreover, in Fig. 11, the thumbnail video TS#1 20 supplied by the service ch#1, the thumbnail video TS#2 supplied by the service ch#2, and the thumbnail video supplied by the service ch#3 are the videos having the same image size of, for example, 480 × 270 (width × height) pixels and arranged in, for example, 4 × 4 matrix 25 on a display screen of, for example, 1920 × 1080 pixels.
[0205]
Furthermore, the stream 1311of the thumbnail video TS#1 supplied by the service ch#1, a stream 1312of the thumbnail video TS#2 supplied by the service ch#2, and a 30 stream 1313of the thumbnail video supplied by the 43

service ch#3 are collectively distributed by multicast, for example, in one FLUTE session on the MBMS bearer.
[0206]
In the SDP 121, as described above, the IP address and the port number to distribute by multicast in one 5 FLUTE session the stream 1311of the thumbnail video TS#1 supplied by the service ch#1, the stream 1312of the thumbnail video TS#2 supplied by the service ch#2, and the stream 1313of the thumbnail video supplied by the service ch#3 are described.10
[0207]
The client 13 canrecognize, by receiving the USD of Fig. 11, that the thumbnail video is to be distributed with the /@r7:serviceClass attribute 73 to which the attribute value "urn:MosaicableComponents" as the 15 thumbnail signaling information is set or the /@thumbnailVideoattribute.
[0208]
Moreover, the client 13 can recognize that there is a stream to be distributed by multicast and the stream to 20 be distributed by multicast is (the stream of) the thumbnail video with the /broadcast element 83 and the like including the /@thumbnailVideo attribute.
[0209]
Then, the client 13 receives, with the URI of the 25 SDP 121 indicated by the /broadcast element 83, the /association element 84, the /sessionDescription element 85 or the like, the SDP 121 in which the IP address and the port number, to which the thumbnail video is to be distributed by multicast, are described, and can receive, 30 based on the IP address and the port number described in 44

the SDP 121, the stream 1311of the thumbnail video TS#1 supplied by the service ch#1, the stream 1312of the thumbnail video TS#2 supplied by the service ch#2, and the stream 1313 of the thumbnail video supplied by the service ch#3 which are to be distributed by multicast in 5 one FLUTE session.
[0210]
Thus, the client 13 receives the thumbnail video TS#1 of the service ch#1, the thumbnail video TS#2 of the service ch#2, and the thumbnail video of the service ch#3 10 as the content supplied by each of the plurality of services constituting a mosaic screen MZ, and can easily generate the mosaic screenMZ using the thumbnail videos.
[0211]
Note that, in the USD of Fig. 11, although three 15 /r12:appServiceDescription elements (the /r12:appServiceDescription element 81 or 91) indicating that the content is to be distributed by multicast (or to be distributed by broadcast) or to be distributed by unicast are described, the number of 20 /r12:appServiceDescription elements described in one USD is not limited to three.
[0212]
In other words, in one USD, for example, the number of /r12:appServiceDescription elements of services which 25 supply the thumbnail videos capable of constituting a mosaic screen MZ can be described.
[0213]
As the thumbnail video capable of constituting a mosaic screen MZ, thumbnail videos having a same genre, 30 such as baseball relay broadcasting, can be adopted.45

However, the thumbnail video capable of constituting a mosaic screen MZ are not limited to thumbnail videos having a same genre.
[0214]
Furthermore, at the client 13, when a user who 5 watches the mosaic screen MZ in which the thumbnailvideo TS#1 of the service ch#1, the thumbnail video TS#2 of the service ch#2, and the thumbnail video of the service ch#3 are arranged selects a thumbnail video on the mosaic screen MZ, the user can perform channel selection to 10 switch the display screen from the mosaic screen MZ to a main video (and audio) supplied by the service which supplies the thumbnail video selected by the user.
[0215]
When, for example, the user selects the thumbnail 15 video TS#1 of the service ch#1, the client 13 can acquire (receive or recognize) the MPD 111 of the content of the service ch#1 based on the /@mpdURI attribute 82 included in the /r12:appServiceDescription element 81 about the service ch#1 (the /r12:appServiceDescription element 81 20 including the /broadcast element 83 indicating that the thumbnail video TS#1 of the service ch#1 is to be distributed by multicast).
[0216]
Furthermore, the client 13 can recognize, based on 25 the /unicast elements 86 and 87 included in the /r12:appServiceDescription element 81 about the service ch#1, that the main video MS#1 and the audio of the service ch#1 are to be distributed by unicast.
[0217]30
Then, the client 13 transmits, based on the MPD 111, 46

the HTTP request which requests the main video MS#1 and the audio of the service ch#1, and can receive and reproduce the main video MS#1 and the audio of the service ch#1 to be distributed by unicast in response to the HTTP request.5
[0218]
Note that, the main video MS#1 and the audio of the service ch#1 are not only to be distributed by unicast, but also to be distributed by multicast similarly to the thumbnail video TS#1 of the service ch#1.10
[0219]
The main video MS#1 and the audio of the service ch#1 (furthermore, a main video and audio of a service which supplies a thumbnail video capable of constituting a mosaic screen MZ) as well as the thumbnail video TS#1 15 of the service ch#1 (furthermore, a thumbnail video of another channel capable of constituting a mosaic screen MZ) can be distributed by multicast in the same FLUTE session.
[0220]20
In this case, it is possible to significantly improve the performance of the channel selection at the client 13, that is, to extremely quickly switch the mosaic screen MZ to the main video and the audio of the service which supplies the thumbnail video selected by 25 the user.
[0221]

[0222]
Fig. 12 is a diagram illustrating a summary of an 30 MPD as thumbnail metadata.47

[0223]
An MPD as thumbnail metadata is configured similarly to an MPD in the DASH.
[0224]
In other words, an MPD of acontent C has one or 5 more Periods.
[0225]
The Period indicates a section into which the content C is divided in a time direction, and a start time and the like of the section indicated by the Period 10 are described in the Period.
[0226]
The Period has thenecessary number of AdaptationSets.The AdaptationSet is prepared for each media, such as a video, audio, or subtitles, and 15 information, such as a language or codec, is described in the AdaptationSet.
[0227]
The AdaptationSet has a necessary number of Representations.The Representation is prepared for, for 20 example, each bit rate, and a bit rate, an image size, and the like are described in the Representation.
[0228]
The Representation has the necessary number of pieces of SegmentInfo, and information on a segment is 25 described in the SegmentInfo.
[0229]
Fig. 13 is a diagram illustrating examples of elements and attributes of XML which constitute an MPD described in XML as thumbnail metadata.30
[0230]48

An MPD includes MPD (element), MPD/@profile (attribute), MPD/Period (element), and MPD/@minBufferTime (attribute).
[0231]
An MPD element is a root element, and includes a 5 /@profile attribute and a /@minBufferTime attribute.
[0232]
A /Period element is information on a section, into which the content corresponding to the MPD describing the /Period element (the content whose reproduction control 10 is performed according to the MPD) is divided in a time direction, and used to assemble the segments in the section.
[0233]
The /@profile attribute indicates an operation 15 profile to which the MPD describing the /@profile attribute conforms, and the /@minBufferTime attribute indicates the minimum buffer time (a buffer amount of data) necessary to start to reproduce the content corresponding to the MPD describing the /@minBufferTime 20 attribute.
[0234]
The MPD as thumbnail metadata includes the thumbnail signaling information in addition to the above MPD element, /@profile attribute, /Period element, and 25 /@minBufferTime attribute.
[0235]
As the thumbnail signaling information included in the MPD, an MPD/Period/AdaptationSet/ViewPoint/@schemeIdURI attribute 30 in which, for example, the information indicating the 49

content whose reproduction control is performed according to the MPD is the thumbnail video is described as an attribute value can be adopted.
[0236]
Note that, as the thumbnail metadata, instead of 5 the above MPD element, /@profile attribute, /Period element, /@minBufferTime attribute, and MPD including thumbnail signaling information, arbitrary metadata including the thumbnail signaling information and information equivalent to one or more of the MPD element, 10 the /@profile attribute, the /Period element, and the /@minBufferTime attribute can be adopted.
[0237]
Fig. 14 is a diagram illustrating an example of an MPD described in XML as thumbnail metadata.15
[0238]
In other words, Fig. 14 illustrates an example of an MPD of content including a video thumbnail (for example, the thumbnail video TS#1, the main video MS#1, and the audio as the content supplied by the service20 ch#1).
[0239]
In the MPD of Fig. 14, the MPD element is a root element, and a Period element belonging to the MPD element, an AdaptationSet element belonging to the Period 25 element, and a ViewPoint element belonging to the AdaptationSet element are described.
[0240]
In Fig. 14, the AdaptationSet element in a description 141 is AdaptationSet (element) of the 30 thumbnail video, and includes a width attribute and a 50

height attribute.
[0241]
In the description 141, width = '480' height = '270' indicate that theimage size of the thumbnail is 480 × 270 pixels.5
[0242]
The information regarding the display of the thumbnail video, such as an image size, is described as an element included in an attribute belonging to the AdaptationSet element in the description 141or an 10 element included in the AdaptationSet element.
[0243]
The ViewPoint element in a description 142 includes a schemeIdURI attribute, and an attribute value "urn:thumbnailVideo" is set to the schemeIdURI attribute 15 in Fig. 14.
[0244]
The attribute value "urn:thumbnailVideo" is a new scheme identifier indicating that the content whose reproduction control is performed according to the MPD 20 (MPD/Period/AdaptationSet/ViewPoint/@schemeIdURI) including the attribute value "urn:thumbnailVideo" is the thumbnail video.
[0245]
The schemeIdURI attribute, to which the attribute 25 value "urn:thumbnailVideo" is set, belonging to the ViewPoint element functions as the thumbnail signaling information.
[0246]
Note that, when the streams having different bit 30 rates as (the stream of) the thumbnail video are prepared, 51

the AdaptationSet element in the description 141 can include the Representation element for each of the plurality of bit rates of the thumbnail video.
[0247]
According to the above described MPD, the client 13 5 specifies (a segment of) a thumbnail video, acquires the thumbnail video, and can easily generate a mosaic screen constituted of the thumbnail video.
[0248]
10
[0249]
Fig. 15 is a diagram illustrating a data model of an OMA-ESG as thumbnail metadata.
[0250]
The data model of the thumbnail metadata of Fig. 15 15 is configured similarly to a data model of an OMA-ESG.
[0251]
However, in the OMA-ESG as thumbnail metadata, the thumbnail signaling information indicating that a video of content supplied by a service whose information is 20 described in the OMA-ESG is a thumbnail video is included in Service 151.
[0252]
Moreover, in the OMA-ESG as thumbnail metadata, Access 152 includes, for example, a URI of a USD as 25 reference to the USD (Fig. 11) describing the information on the thumbnail video.
[0253]
Fig. 16 is a diagram illustrating examples elements and attributes of XML which constitute the OMA-ESG 30 described in XML as thumbnail metadata.52

[0254]
The OMA-ESG includes Access (element), Access/@id (attribute), Access/@version (attribute), Access/AccessType (element), Access/AccessType/BroadcastServiceDelivery (element), 5 Access/AccessType/BroadcastServiceDelivery/SessionDescription (element), Access/AccessType/UnicastServiceDelivery (element), Access/ServiceClass (element), and Access/AccessType/BroadcastServiceDelivery/SessionDescription/USBDRef (element).10
[0255]
The Access element is equivalent to the Access 152 of Fig. 15, and is access information which refers to service information on a service to access the service.
[0256]15
A /@id attribute is an access information identifier identifying access information (Access element), and a /@version attribute is version information indicating a version of description contents of accessinformation.20
[0257]
A /AccessType element is information indicating that a service is either of a broadcast type service or a bidirectional type service, and a /BroadcastServiceDelivery element is information 25 indicating that the service is the broadcast type service.
[0258]
A /SessionDescription element is information indicating that a session description, and a UnicastServiceDelivery element is information indicating 30 that the service is the bidirectional type service.53

[0259]
A /ServiceClass element is information indicating a class of the service, and a /USBDRef element is information to refer to the USD (Fig. 11) describing the information on the thumbnail video and including, for 5 example, the URI of the USD.
[0260]
An OMA-ESG as thumbnail metadata includes the thumbnail signaling information in addition to the above Access element, Access/@id attribute, Access/@version 10 attribute, Access/AccessType element, Access/AccessType/BroadcastServiceDelivery element, Access/AccessType/BroadcastServiceDelivery/SessionDescription element, Access/AccessType/UnicastServiceDelivery element, Access/ServiceClass element, and /USBDRef 15 element.
[0261]
As the thumbnail signaling information included in an OMA-ESG, for example, a /ServiceType element in which the information indicating that the content supplied by 20 the service corresponding to the OMA-ESG (the service whose information is described in the OMA-ESG) is the thumbnail video is described can be adopted.
[0262]
The /ServiceType element is information included in25 a Service element.The Service element is equivalent to the Service 151 of Fig. 15, and is service information regarding a service.A globalserviceId attribute as a service identifier identifying the Service element (service information) belongs to (is included in) the 30 Service element.54

[0263]
Note that, as the thumbnail metadata, instead of the above Access element, Access/@id attribute, Access/@version attribute, Access/AccessType element, Access/AccessType/BroadcastServiceDelivery element, 5 Access/AccessType/BroadcastServiceDelivery/SessionDescription element, Access/AccessType/UnicastServiceDelivery element, Access/ServiceClass element, /USBDRef element, and OMA-ESG including the thumbnail signaling information, arbitrary metadata including the thumbnail signaling 10 information and information equivalent to one or more of the Access element, the Access/@id attribute, the Access/@version attribute, the Access/AccessType element, the Access/AccessType/BroadcastServiceDelivery element, the 15 Access/AccessType/BroadcastServiceDelivery/SessionDescription element, the Access/AccessType/UnicastServiceDelivery element, the Access/ServiceClass element, and the /USBDRef element.
[0264]20
Fig. 17 is a diagram illustrating an example of an OMA-ESG described in XML as thumbnail metadata.
[0265]
A of Fig. 17 illustrates an example of a Service element of an OMA-ESG as thumbnail metadata, and B of Fig. 25 17 illustrates an example of an Access element of an OMA-ESG as thumbnail metadata.
[0266]
In the Service element of A of Fig. 17, for example, “12” as the value indicating that a video supplied by a 30 service corresponding to the OMA-ESG describing the 55

Service element is the thumbnail video is introduced as a new value of the /ServiceType element.
[0267]
Then, the new value “12” is set to the /ServiceType element.5
[0268]
The Service element of A of Fig. 17 includes a Service/globalserviceId attribute as a service identifier, and the identification (ID) as the service identifier of the Service element of A of Fig. 17 is set tothe 10 globalserviceId attribute.
[0269]
Here, when the new value “12” is set to the /ServiceType element, the content whose information is described in the Service element including the 15 /ServiceType element includes at least a thumbnail video suitable for constituting a mosaic screen.
[0270]
In the Access element of B of Fig. 17, as reference to (the bundleDescription element (Fig. 11) which is a 20 root element of) the USD describing the information on the thumbnail video supplied by the service corresponding to the OMA-ESG in which the /USBDRef element is described, for example, the information including the URI of the USD is described in the /USBDRef element.25
[0271]
Furthermore, the Access element of B of Fig. 17 includes an Access/ServiceReference element, and the /ServiceReference element includes an Access/ServiceReference/@idRef attribute.30
[0272]56

Then, to the /@idRef attribute, the value set to the globalserviceId attribute of the Service element of A of Fig. 17 is set as the ID of the Service element to be referred by the Access element in which the /@idRef attribute is described.5
[0273]
Fig. 18 is a diagram for explaining the OMA-ESG as thumbnail metadata of Fig. 17.
[0274]
When receiving the OMA-ESG as thumbnail metadata of 10 Fig. 17, the client 13 can refer to, based on the /@idRef attribute of the Access element of B of Fig. 17, the Service element of A of Fig. 17.
[0275]
By referring to the /ServiceType element in which 15 the new value “12” of the Service element of A of Fig. 17 is described, the client 13 can recognize that the video supplied by the service corresponding to the OMA-ESG describing the Service element is the thumbnail video.
[0276]20
Then, when the thumbnail video supplied by the service corresponding to the OMA-ESG describing the Service element of A of Fig. 17 is needed, the client 13 recognizes the URI as the reference to (the bundleDescription element (Fig. 11) which is the root 25 element of) the USD describing the information on the thumbnail video supplied by the service corresponding to the OMA-ESG describing the /USBDRef element by referring to the /USBDRef element of the Access element of B of Fig. 17, and can acquire (receive) the USD (Fig. 11) 30 describing the information on the thumbnail video based 57

These are similarly applied to Figs. 20 and 21, and Figs. 27 to 29 which will be described later.
[0284]
In Fig. 19, the main videos MS#1 to MS#3, the audio AS#1to AS#3, and the thumbnail videos TM#1 to TM#3 may 5 be distributed by either of multicast (for example, by multicast in a multicast FLUTE session) or unicast (for example, by unicast in a unicast HTTP session).
[0285]
Then, when the main videos MS#1 to MS#3, the audio 10 AS#1 to AS#3, and the thumbnail videos TM#1 to TM#3 are to be distributed by multicast, the thumbnail videos TM#1 to TM#3 are to be distributed by multicast in one FLUTE session FS-T.
[0286]15
Furthermore, the main video MS#1 is to be distributed by multicast in one FLUTE session FS-M#1, the main video MS#2 is to be distributed by multicast in one FLUTE session FS-M#2, and the main video MS#3 is to be distributed by multicast in one FLUTE session FS-M#3.20
[0287]
Moreover, the audio AS#1 is to be distributed by multicast in one FLUTE session FS-A#1, the audio AS#2 is to be distributed by multicast in one FLUTE session FS-A#2, and the audio AS#3 is to be distributed by multicast 25 in one FLUTE session FS-A#3.
[0288]
Note that, an MPD#1 of content of the channel ch#1 includes the AdaptationSet (element) of each of the main video MS#1, the audio AS#1, and the thumbnail video TM#1.30 Moreover, the AdaptationSet of the thumbnail video TM#1 59

of the MPD#1 includes a ViewPoint/@schemeIdURI attribute to whichan attribute value "urn:thumbnailVideo" as the thumbnail signaling information signaling that (the video of) the AdaptationSet is the thumbnail video is set.Note that, as an element to which a /@schemeIdURI 5 attribute to set an attribute value "urn:thumbnailVideo" and the like belongs, an element having the same configuration similar to the ViewPoint element, such as a Role element, an EssentialProperty element, and a SupplementalProperty element in addition to the ViewPoint 10 element can be adopted.
[0289]
This is similarly applied to the MPD of the content of each of the channels ch#2 and ch#3.
[0290]15
Fig. 20 is a diagram illustrating a second example of a method for distributing content including a thumbnail video.
[0291]
In Fig. 20, similarly to Fig. 19, the main videos 20 MS#1 to MS#3, the audio AS#1 to AS#3, and the thumbnail videos TM#1 to TM#3 may be distributed by either of multicast or unicast.
[0292]
Then, when the main videos MS#1 to MS#3, the audio 25 AS#1 to AS#3, and the thumbnail videos TM#1 to TM#3 are to be distributed by multicast, the thumbnail videos TM#1 to TM#3 are to be distributed by multicast in one FLUTE session FS-T similarly to Fig. 19.
[0293]30
Furthermore, the main video MS#1 and the audio AS#1 60

are to be distributed by multicast in one FLUTE session FS#1, the main video MS#2 and the audio AS#2 are to be distributed by multicast in one FLUTE session FS#2, and the main video MS#3 and the audio AS#3 are to be distributed by multicast in one FLUTE session FS#3.5
[0294]
Note that, the MPD#1 of the content of the channel ch#1, the MPD of the content of the channel ch#2, and the MPD of the content of the channel ch#3 are configured similarly to the case of Fig. 19.10
[0295]
Fig. 21 is a diagram illustrating a third example of a method for distributing content including a thumbnail video.
[0296]15
In Fig. 21, similarly to Fig. 19, the main videos MS#1 to MS#3, the audio AS#1 to AS#3, and the thumbnail videos TM#1 to TM#3 may be distributed by either of multicast or unicast.
[0297]20
Then, when the main videos MS#1 to MS#3, the audio AS#1 to AS#3, and the thumbnail videos TM#1 to TM#3 are to be distributed by multicast, all of the main videos MS#1 to MS#3, the audio AS#1 to AS#3, and the thumbnail videos TM#1 to TM#3 are to be distributed by multicast in 25 one FLUTE session FS.
[0298]
Note that, the MPD#1 of the content of the channel ch#1, the MPD of the content of the channel ch#2, and the MPD of the content of the channel ch#3 are configured 30 similarly to the case of Fig. 19.61

[0299]

[0300]
Fig. 22 is a diagram illustrating a display example of a mosaic screen at the client 13.5
[0301]
As described above, the client 13 can receive thumbnail videos based on a combination of an MPD, an SDP, and a USD as thumbnail metadata or a combination of an OMA-ESG in addition to them, and display a mosaic screen 10 in which the thumbnail videos are arranged in lattice shape.
[0302]
A of Fig. 22 illustrates an example of a mosaic screen in which sixteen thumbnail videos are arranged in 15 4 × 4 matrix, and B of Fig. 22 illustrates an example of a mosaic screen in which four thumbnail videos are arranged in 2 × 2 matrix.
[0303]
Now, when the client 13 receives sixteen thumbnail 20 videos and in the case where the image size of each thumbnail video is, for example, 480 × 270 pixels, and the display screen size of the client 13 is, for example, 1920 × 1080 pixels (or more), a mosaic screen in which all of the sixteen thumbnail videos received by the 25 client 13 are arranged in 4 × 4 matrixcan be displayed as illustrated in A of Fig. 22.
[0304]
However, in the case where the display screen size of the client 13 is smaller than 1920 × 1080 pixels, for 30 example, is 960 × 540 pixels, although the client 13 62

receives sixteen thumbnail videos, the number of thumbnail videos to be displayed as a mosaic screen is limited to four as illustrated in B of Fig. 22.
[0305]
As described above, when the display screen size of 5 the client 13 is small and the number of thumbnail videos to be displayed as a mosaic screen is limited to the smaller number than the number of thumbnail videos received by the client 13, it is possible to display all of the thumbnail videos received by the client 13 on a 10 mosaic screen by, for example, processing the image size of thethumbnail video into a smaller size according to the display screen size of the client 13.
[0306]
In other words, by processing a thumbnail video 15 having 480 × 270 pixels into a thumbnail video having 240 × 135 pixels, it is possible to display all of sixteen thumbnail videos as a mosaic screen on a display screen having 960 × 540 pixels.
[0307]20
However, in this case, the client 13 is required to process the image size of the thumbnail video, and the process load of the client 13 increases.Moreover, when a mosaic screen is constituted (generated) by processing the image size of the thumbnail video into the smaller 25 image size, the thumbnail video may be difficult to be watched.
[0308]
Incidentally, as described above, when the number of thumbnail videos to be displayed as a mosaic screen is 30 not limited as well as when the number of thumbnail 63

The description "urn:thumbnailVideo" before the colon (:) in the attribute value "urn:thumbnailVideo:dic" is, as described in Fig. 14, a new scheme identifier indicating that the content is the thumbnail video, and according to the scheme identifier "urn:thumbnailVideo", 5 the client 13 can recognize that (the video of) the content is the thumbnail video.
[0315]
The description "dic" after the colon in the attribute value "urn:thumbnailVideo:dic" isinformation 10 to specify a dictionary defining a constituent element of a value attribute, which will be described later, (dictionary definition).
[0316]
The ViewPoint element in the description 201 15 includes, in addition to the above schemeIdURI attribute,a value attribute which is a new attribute.
[0317]
The value attribute is content description metadata describing the contents of the content whose reproduction 20 control is performed according to the MPD (MPD/Period/AdaptationSet/ViewPoint) including the value attribute, and the item indicating the contents of the content is set to the value attribute as an attribute value.25
[0318]
In Fig. 23, an attribute value "X, Y, Z, ..." is described in the value attribute.
[0319]
One or more items can be described as an attribute 30 value in the value attribute, and when a plurality of 65

items is set to the value attribute as an attribute value, the plurality of items X, Y, Z, ... is, for example, described by being separated by commas (,) as illustrated in Fig. 23.
[0320]5
The item which is the constituent element constituting the attribute value set to the value attribute is, as described above, defined by the dictionary specified by the description "dic" after the colon in the attribute value "urn:thumbnailVideo:dic".10
[0321]
Thus, the client 13 can recognize, based on the dictionary specified by the description "dic" after the colon in the attribute value "urn:thumbnailVideo:dic", the definition (meaning contents) of each item of the 15 attribute value set to the value attribute.
[0322]
For example, now it is assumed that it is defined that the first, second, and third items of the attribute value set to the value attribute are genre identification 20 information indicating a genre, country identification information indicating a country, and region identification information indicating a region respectively in the dictionary specified by the description "dic" after the colon in the attribute value 25 "urn:thumbnailVideo:dic".
[0323]
In this case, for example, when the genre of(the thumbnail video of) the content is "baseball (baseball relay broadcasting)" which relays a baseball game and a 30 host country which hosts the baseball game is "US 66

(America) " and a host region which hosts the baseball game is "CA (California)", the attribute value "baseball, US, CA" is set to (encoded in) the value attribute in (the metadata generator 32 (Fig. 3) of) the aggregation server 12.5
[0324]
The client 13 can recognize, from the attribute value "baseball, US, CA" set to the value attribute based on the dictionary specified by the description "dic" after the colon in the attribute value 10 "urn:thumbnailVideo:dic", that the genre of the content is baseball relay broadcasting and the baseball game is hosted by California in America.
[0325]
Fig. 24 is a diagram schematically illustrating an 15 example of (a stream of) a plurality of thumbnail videos to be distributed by multicast in one FLUTE session.
[0326]
For example, it is assumed that the attribute value "urn:thumbnailVideo:dic" similar to the Fig. 23 is set to 20 the schemeIdURI attribute which is the attribute belongs to the ViewPoint element included in the AdaptationSet element of the thumbnail video in the MPDs (describing the AdaptationSet) of sixteen thumbnail videos when the sixteen thumbnail videos having the same image size of 25 480 × 270 pixels are distributed by multicast in one FLUTE session.
[0327]
Moreover, it is assumed that the attribute value illustrated in Fig. 24 is set to a value attribute for 30 each thumbnail video.67

[0328]
In this case, when the display screen size of the client 13 is, for example, 1920 × 1080 pixels (or more), the client 13 can display, as illustrated in A of Fig. 22, a mosaic screen in which all of the sixteen thumbnail 5 videos distributed in one FLUTE session and have the image size of 480 × 270 pixels are arranged in 4 × 4 matrix.
[0329]
On the other hand, when the display screen size of 10 the client 13 is smaller than 1920 × 1080 pixels, for example, is 960 × 540 pixels, the number of thumbnail videos to be displayed as a mosaic screen at the client 13 is limited to four arranged in 2 × 2 matrix among the sixteen thumbnail videos as illustrated in B of Fig. 22.15
[0330]
Thus, in this case, four thumbnail videos to be displayed on the mosaic screen need to be selectedfrom the sixteen thumbnail videos.
[0331]20
Thus, the client 13 performs filtering to select four thumbnail videos (to constitute a mosaic screen) to be displayed on a mosaic screen (hereinafter, referred to as thumbnail filtering) using (the attribute value set to) the value attribute of the thumbnail video.25
[0332]
The thumbnail filtering can be performed based on, for example, preference information and the like indicating preference of the user of the client 13.
[0333]30
In other words, for example, whena user frequently 68

views relay broadcasting hosted by California (CA) in America (US), when the place where a user is located (the location of the client 13) is at California in America, or the like, the thumbnail video in which the country identification information among the attribute values set 5 to the value attribute is "US" indicating America and the region identification information is "CA" indicating California is selected from the sixteen thumbnail videos as the thumbnail video to be displayed on a mosaic screen in the thumbnail filtering.10
[0334]
Note that, when the number of thumbnail videos selected in the thumbnail filtering is larger than the number of thumbnail videos which can be displayed on the mosaic screen, the client 13 can select the number of 15 thumbnail videos which can be displayed on a mosaic screen, for example, randomly from, for example, the thumbnail videos selected in the thumbnail filtering.Alternatively, a mosaic screen having a larger size than the display screen size of the client 13 is generated, 20 and the mosaic screen can be scrolled according to a user’s operation or the like.
[0335]
As described above, by adding, to an MPD, a value attribute as an index capable of dynamically being 25 changed in order to perform the thumbnail filtering to the thumbnail video at the client 13, it is possible to achieve an efficient service selection process (channel selection) on a mosaic screen according to a display screen size as restriction in the device rendering 30 environment of the client 13.69

according to the scheme identifier "urn:thumbnailVideo".
[0342]
Moreover, as described in Fig. 23, the description "dic" or "JapaneseParameters" after the colon in the attribute value "urn:thumbnailVideo:dic" or 5 "urn:thumbnailVideo:JapaneseParameters" is information to specify the dictionary defining the constituent element of the value attribute (dictionary definition).
[0343]
Now, it is assumed that it is defined that, for 10 example, the first, second and third items of the attribute value set to the value attribute are genre identification information indicating a genre, country identification information indicating a country, and region identification information indicating a region 15 respectively in the dictionary specified by the descriptions "dic" and "JapaneseParameters".
[0344]
However, it is ruled (defined) that the language of the genre identification information, the country 20 identification information, and the region identification information is, for example, English in the dictionary specified by the description "dic" (hereinafter, referred to as a "dic" dictionary), and it is ruled that the language of the genre identification information, the 25 country identification information, and the region identification information is, for example, Japanese which is the different language from English in the dictionary specified by the description "JapaneseParameters" (hereinafter, referred to as a 30 "JapaneseParameters" dictionary).71

[0351]
The ViewPoint element in the description 221 includes, similarly to the ViewPoint element in the description 201 of Fig. 23, the schemeIdURI attribute, and the value attribute as content description metadata.5
[0352]
In the description 211, an attribute value "http://baseballAuthority.com/thumbnailVideoGenre" is set to the schemeIdURI attribute.
[0353]10
The attribute value "http://baseballAuthority.com/thumbnailVideoGenre" serves as a scheme identifier indicating that the content is the thumbnail video and as information to specify a dictionary defining a constituent element of a value 15 attribute (dictionary definition).
[0354]
Thus, the client 13 can recognize that (the video of) the content is the thumbnail video with the attribute value "http://baseballAuthority.com/thumbnailVideoGenre".20
[0355]
Moreover, the attribute value "http://baseballAuthority.com/thumbnailVideoGenre" is an http URL, and the http URL indicates the address of the dictionary defining the constituent element (item) of the 25 value attribute.
[0356]
As the described above, when the dictionary defining the constituent element of the value attribute is specified by the http URL, it is possible to arrange 30 the dictionary defining the constituent element of the 73

ch#1 to ch#3 are to be distributed.
[0362]
Furthermore, in Figs. 27 to 29, similarly to the cases of Figs. 19 to 21 respectively, the MPD#1 of the content of the channel ch#1 includes the AdaptationSet 5 (element) of each of the main video MS#1, the audio AS#1, and the thumbnail video TM#1, and the AdaptationSet of the thumbnail video TM#1 of the MPD#1 includes a ViewPoint/@schemeIdURI attribute to which, for example, an attribute value "urn:thumbnailVideo" as the thumbnail 10 signaling information to signal that (the video of) the AdaptationSet is the thumbnail video is set.
[0363]
Moreover, in Figs. 27 to 29, the AdaptationSet of the thumbnail video TM#1 of the MPD#1 includes the value 15 attribute as content description metadata (and the information to specify the dictionary defining the constituent element of the value attribute), and this point is different form the cases of Figs. 19 to 21.
[0364]20
As described above, Figs. 27 to 29 are similar to Figs. 19 to 21 respectively except that the AdaptationSet of the thumbnail video TM#1 of the MPD#1 (similar to the MPD of the content of each of the channelsch#2 and ch#3) includes the value attribute as content description 25 metadata, and the description is omitted.
[0365]

[0366]
Fig. 30 is a flowchart for explaining an example of 30 a process to display a mosaic screen at the client 13.75

[0367]
In step S101, the middleware 41 (Fig. 4) collects a USD of a thumbnail video by receiving the USD or by receiving an OMA-ESG and then receiving the USD based on the OMA-ESG, and the process proceeds to step S102.5
[0368]
In step S102, the middleware 41 receives, based on the USD of the thumbnail video, the MPD of the thumbnail video and supplies (passes) the MPD to the DASH client 42 (Fig. 4), and the process proceeds to step S103.10
[0369]
In step S103, the DASH client 42 issues, based on the MPD of the thumbnail video from the middleware 41, an HTTP request which requests (the segment of) the thumbnail video to the middleware 41, and the process 15 proceeds to step S104.
[0370]
In step S104, the middleware 41 determines, based on the USD or the OMA-ESG, whether the thumbnail video requested by the HTTP request by the DASH client 42 has 20 been distributed by multicast.
[0371]
In step S104, when it is determined that the thumbnail video has been distributed by multicast, the processproceeds to step S105. The middleware 41 25 receives the thumbnail video distributed by multicast and supplies the thumbnail video to the DASH client 42, and the process proceeds to step S107.
[0372]
On the other hand, when it is determined that the 30 thumbnail video has not been distributed by multicast in 76

step S104, the process proceeds to step S106, and the middleware 41 issues the HTTP request from the DASH client 42 on the network 10.Moreover, the middleware 41 receives, in response to the HTTP request, the thumbnail video distributed by unicast from the channel server 11 5 (or the aggregation server 12) and supplies the thumbnail video to the DASH client 42, and the process proceeds to step S107.
[0373]
In step S107, the reception unit 40 (Fig. 4) 10 determines whether the thumbnail filtering has been ON.
[0374]
Here, whether the ON and OFF of the thumbnail filtering is performed or not, that is, whether the thumbnail filtering is performed or not can be set by, 15 for example, operating the client 13.
[0375]
In step S107, when it is determined that the thumbnail filtering has been ON, the process proceeds to step S108. The DASH client 42 performs the thumbnail 20 filtering to the thumbnail videos supplied from the middleware 41 using the value attribute as content description metadata described in the MPD of the thumbnail video, selects thumbnail videos constituting a mosaic screen from the thumbnail videos supplied from the 25 middleware 41, and supplies the selected thumbnail videos to the reproduction unit 43 (Fig. 4).
[0376]
Here, when the number of thumbnail videos selected in the thumbnail filtering is larger than the number of 30 thumbnail videos which can be displayed on the mosaic 77

screen, the client 13 can select (equal to or smaller than) the number of thumbnail videos which can be displayed on the mosaic screen, for example, randomly from, for example, the thumbnail videos selected in the thumbnail filtering.5
[0377]
On the other hand, in step S107, when it is determined that the thumbnail filtering has notbeen ON, the process proceeds to step S109. The DASH client 42 selects the number of thumbnail videos which can be 10 displayed on a mosaic screen from the thumbnail videos supplied from the middleware 41, for example, randomly, and supplies the selected thumbnail videos to the reproduction unit 43.
[0378]15
After steps S108 and S109, the process proceeds to step S110. The reproduction unit 43 constructs and displays the mosaic screen in which the thumbnail videos from the DASH client 42 are arranged, and the process to display the mosaic screen is terminated.20
[0379]

[0380]
Next, the above series of processes can be 25 performed by hardware or by software.When the series of processes is performed by software, a program constituting the software is installed in a general-purpose computer or the like.
[0381]30
Thus, Fig. 31 illustrates a configuration example 78

of an embodiment of a computer in which the program to execute the above series of processes is installed.
[0382]
The program can be recorded in advance in a hard disk 405 or a ROM403 as a recording medium incorporated 5 in the computer.
[0383]
Alternatively, the program can be stored (recorded) in a removable recording medium 411.Such removable recording medium 411 can be supplied as so-called package 10 software.Here, the removable recording medium 411 is, for example, a flexible disk, a compact disc read only memory (CD-ROM), a magneto optical (MO) disc, a digital versatile disc (DVD), a magnetic disk, a semiconductor memory, or the like.15
[0384]
Note that, the program can be installed in the computer from the above described removable recording medium 411, and also installed in the incorporating hard disk 405 after being downloaded in the computer via a 20 communication network or a broadcasting network.In other words, the program can be wirelessly transferred to the computer from, for example, a download site via an artificial satellite for digital satellite broadcast, or wiredly transferred to the computer via a network, such 25 as a local area network (LAN) or the internet.
[0385]
The computer incorporates a central processing unit (CPU) 402, and an input/output interface 410 is connected to the CPU 402 via a bus 401.30
[0386]79

When a user operates an input unit 407 via the input/output interface 410 and a command is supplied, the CPU 402 executes, according to the command, the program stored in the read only memory (ROM) 403.Alternatively, the CPU 402 loads the program stored in the hard disk 405 5 to a random access memory (RAM) 404 and executes the program.
[0387]
Thus, the CPU 402 performs the process according to the above described flowchart or the process performed by 10 the configurations of the above described block diagrams.Then, the CPU 402, for example, outputs the process result from an output unit 406, transmits the process result from a communication unit 408, or records the process result in the hard disk 405 via the input/output 15 interface 410 as needed.
[0388]
Note that, the input unit 407 is constituted of a keyboard, a mouse, a microphone, and the like.Furthermore, the output unit 406 is constituted of a 20 liquid crystal display (LCD), a speaker, and the like.
[0389]
Here, the process performed by the computer according to the program in the present specification is not necessarily performed in time series according to the 25 order described as the flowchart.In other words, the process performed by the computer according to the program includes a process to be executed in parallel or independently (including, for example, a parallel process or a process by objects).30
[0390]80

Furthermore, the program may be performed by one computer (processor) or may be dispersedly performed by a plurality of computers.Moreover, the program may be transferred to a distant computer and executed.
[0391]5
Moreover, in the present specification, a system means a collection of a plurality of constituent elements (apparatuses, modules (parts), and the like), and all constituent elements are not necessarily in a same casing.Thus, both of a plurality of apparatuses stored in 10 separated casings and connected with each other via a network, and an apparatus having a plurality of modules in a casing are a system.
[0392]
Note that, embodiments of the present technology 15 are not limited to the above described embodiments, and can be variously modified without departing from the scope of the present technology.
[0393]
For example, the present technology can be a 20 configuration of cloud computing in which a function isshared/cooperatively processed shared by a plurality of apparatuses via a network.
[0394]
Furthermore, each step described in the above 25 described flowchart can be performed by one apparatus, and shared and performed by a plurality of apparatuses.
[0395]
Moreover, when a step includes a plurality of processes, the plurality of process included in the step 30 can be performed by an apparatus, and shared and 81

performed by a plurality of apparatuses.
[0396]
Furthermore, the present technology can be applied to content distribution other than the DASH.
[0397]5
Furthermore, the effects described in the present specification are merely exemplified and not limited, and there may be other effects.
[0398]
Note that, the present technology may have the 10 following configurations.
[0399]
<1>
A transmission apparatus includes a distribution unit configured to distribute metadata of content, the 15 metadata being described using an attribute and an attribute value and including signaling information indicating that a video is a thumbnail video suitable for constituting a mosaic screen, and the attribute indicating information to refer to a file including 20 information to receive content supplied by a service.
<2>
The transmission apparatus according to <1>, in which the information to receive the content supplied by the service includes an IP address and a port number of 25 multicast.
<3>
The transmission apparatus according to <1> or <2>, in which the file is a session description protocol (SDP) file.30
<4>82

The transmission apparatus according to any one of <1> to <3>, in which the metadata further includes one or more pieces of:
information on a collection of one or more services;5
information on an individual service;
a service identifier which is the attribute to identify a service; and
information on a method for distributing content supplied by a service.10
<5>
The transmission apparatus according to <4>, in which the metadata is a user service description (USD) of a multimedia broadcast multicast service (MBMS) and includes:15
a bundleDescription element which is the information on the one or more services;
a bundleDescription/UserServiceDescription element which is the information on the individual service;
a 20 bundleDescription/userServiceDescription/@serviceId attribute which is the service identifier;
a bundleDescription/userServiceDescription/DeliveryMethod element which is the information on the method for 25 distributing the content supplied by the service;
a bundleDescription/userServiceDescription/DeliveryMethod/@sessionDescriptionURI attribute which is the attribute indicating the information to refer to the file including 30 the information to receive the content supplied by the 83

service; and
a bundleDescription/userServiceDescription/@r7:serviceClass attribute whichis the signaling information.
<6>5
The transmission apparatus according to <5>, in which the USD further includes an r12:appServiceDescription element indicating that the content supplied by the service is to be distributed by either distribution method of multicast or unicast.10
<7>
The transmission apparatus according to <6>, in which
the r12:appServiceDescription element includes either or both of a broadcast element or/and a unicast 15 element,
the broadcast element and the unicast element each incudesa baseURL attribute indicating a uniform resource locator (URL) of the content supplied by the service,
the broadcast element indicates that the content 20 whose URL is indicated by the baseURL attribute included in the broadcast element is to be distributed by multicast, and
the unicast element indicates that the content whose URL is indicated by the baseURL attribute included 25 in the unicast element is to be distributed by unicast.
<8>
The transmission apparatus according to <7>, in which the broadcast element includes, as the signaling information, a thumbnailVideo attribute indicating 30 whether the content whose URL is indicated by the baseURL 84

attribute included in the broadcast element is the thumbnail video.
<9>
The transmission apparatus according to<8>, in which the USD includes the /r12:appServiceDescription 5 element of each of a plurality of contents capable of constituting a mosaic screen.
<10>
The transmission apparatus according to any one of <7> to <9>, in which the broadcast element includesa 10 seccionDescription element indicating information to refer to a session description protocol (SDP) file including an IP address and a port number of multicast by which the content whose URL is indicated by the baseURL attribute included in the broadcastelement is to be 15 distributed.
<11>
The transmission apparatus according to any one of <6> to <10>, in which the r12:appServiceDescription element includes an mpdURI attribute indicating a uniform 20 resource identifier (URI) of a media presentation description (MPD) of moving picture experts group-dynamic adaptive streaming over HTTP (MPEG-DASH) which is metadata to perform reproduction control of the content whose distribution method is indicated by the 25 r12:appServiceDescription element.
<12>
A transmission method includes the step of distributing metadata of content, the metadata being described using an attribute and an attribute value and 30 including signaling information indicating that a video 85

is a thumbnail video suitable for constituting a mosaic screen, and the attribute indicating information to refer to a file including information to receive content supplied by a service.
<13>5
A reception apparatus includes a reception unit configured to receive metadata of content, the metadata being described using an attribute and an attribute value and including signaling information indicating that a video is a thumbnail video suitable for constituting a 10 mosaic screen, and the attribute indicating information to refer to a file including information to receive content supplied by a service.
<14>
The reception apparatus according to <13>, in which 15 the information to receive the content supplied by the service includes an IP address and a port number of multicast.
<15>
The reception apparatus according to <13> or <14>, 20 in which the file is a session description protocol (SDP) file.
<16>
The reception apparatus according to any one of <13> to <15>, in which the metadata further includes one 25 or more pieces of:
information on a collection of one or more services;
information on an individual service;
a service identifier which is the attribute to 30 identify a service; and86

information on a method for distributing content supplied by a service.
<17>
The reception apparatus according to <16>, in which the metadata is a user service description (USD) of a 5 multimedia broadcast multicast service (MBMS) and includes:
a bundleDescription element which is the information on the one or more services;
a bundleDescription/UserServiceDescription element 10 which is the information on the individual service;
a bundleDescription/userServiceDescription/@serviceId attribute which is the service identifier;
a 15 bundleDescription/userServiceDescription/DeliveryMethod element which is the information on the method for distributing the content supplied by the service;
a bundleDescription/userServiceDescription/DeliveryMethod/@20 sessionDescriptionURI attribute which is the attribute indicating the information to refer to the file including the information to receive the content supplied by the service; and
a 25 bundleDescription/userServiceDescription/@r7:serviceClass attribute which is the signaling information.
<18>
The reception apparatus according to <17>, in which the USD further includes an r12:appServiceDescription 30 element indicating that the content supplied by the 87

service is to be distributed by either distribution method of multicast or unicast.
<19>
The reception apparatus according to <18>, in which
the r12:appServiceDescription element includes 5 either or both of a broadcast element or/and a unicast element,
the broadcast element and the unicast element each incudes a baseURL attribute indicating a uniform resource locator (URL) of the content supplied by the service,10
the broadcast element indicates that the content whose URL is indicated by the baseURL attribute included in the broadcast element is to be distributed by multicast, and
the unicast element indicates that the content 15 whose URL is indicated by the baseURL attribute included in the unicast element is to be distributed by unicast.
<20>
The reception apparatus according to <19>, in which the broadcast element includes, as the signaling 20 information, a thumbnailVideo attribute indicating whether the content whose URL is indicated by the baseURL attribute included in the broadcast element is the thumbnail video.
<21>25
The reception apparatus according to <20>, in which the USD includes the /r12:appServiceDescription element of each of a plurality of contents capable of constituting a mosaic screen.
<22>30
The reception apparatus according to any one of 88

<19> to <21>, in which the broadcast element includes a seccionDescription element indicating information to refer to a session description protocol (SDP) file including an IP address and a port number of multicast by which the content whose URL is indicated by the baseURL 5 attribute included in the broadcast element is to be distributed.
<23>
The reception apparatus according to any one of <18> to <22>, in which the r12:appServiceDescription 10 element includes an mpdURI attribute indicating a uniform resource identifier (URI) of a media presentation description (MPD) of moving picture experts group-dynamic adaptive streaming over HTTP (MPEG-DASH) which is metadata to perform reproduction control of the content 15 whosedistribution method is indicated by the r12:appServiceDescription element.
<24>
A reception method includes the step of receiving metadata of content, the metadata being described using 20 an attribute and an attribute value and including signaling information indicating that a video is a thumbnail video suitable for constituting a mosaic screen, and the attribute indicating information to refer to a file including information to receive content supplied by 25 a service.
<25>
A transmission apparatus includes a distribution unit configured to distribute metadata of content, the metadata being described using an attribute and an 30 attribute value and including signaling information 89

indicating that a video is a thumbnail video suitable for constituting a mosaic screen, and information to refer to a user service description (USD).
<26>
The transmission apparatus according to <25>, in 5 which the metadata further includes:
service information on a service; and
access information which refers to the service information to access a service.
<27>10
The transmission apparatus according to <26>, in which the service information includes a service identifier which is the attribute to identify the service information.
<28>15
The transmission apparatus according to <27>, in which
the access information includes the information to refer to the USD and further includes one or more pieces of;20
an access information identifier which is the attribute to identify the access information;
version information which is the attribute indicating a version of description contents of the access information;25
information indicating that a service is either of a broadcast type service or a bidirectional type service;
information indicating that a service is a broadcast type service;
information indicating a session description;30
information indicating that a service is a 90

bidirectional type service; and
information indicating a class of a service.
<29>
The transmission apparatus according to <28>, in which the metadata is an open mobile alliance-electronic 5 service guide (OMA-ESG) and includes:
a Service element which is the service information;
a Service/@globalserviceId attribute which is the service identifier;
an Access element which is the access information;10
an Access/@id attribute which is the access information identifier;
an Access/@version attribute which is the version information;
an Access/AccessType element which is information 15 indicating whether the service is either of a broadcast type service or a bidirectional typeservice;
an Access/AccessType/BroadcastServiceDelivery element which is information indicating that the service is a broadcast type service;20
an Access/AccessType/BroadcastServiceDelivery/SessionDescription element which is information indicating the session description;
an Access/AccessType/UnicastServiceDelivery element 25 which is information indicating that the service is a bidirectional type service;
an Access/ServiceClass element which is information indicating a class of the service; and
an 30 Access/AccessType/BroadcastServiceDelivery/SessionDescrip91

tion/USBDRef element which is information to refer to the USD.
<30>
The transmission apparatus according to <29>, in which the OMA-ESG includes, as the signaling information, 5 a Service/ServiceType elementin which the information indicating that the content supplied by the service is the thumbnail video.
<31>
A transmission method includes the step of 10 distributing metadata of content, the metadata being described using an attribute and an attribute valueand including signaling information indicating that a video is a thumbnail video suitable for constituting a mosaic screen, and information to refer to a user service 15 description (USD).
<32>
A reception apparatus includes a reception unit configured to receive metadata of content, the metadata being described using an attribute and an attribute value 20 and including signaling information indicating that a video is a thumbnail video suitable for constituting a mosaic screen, and information to refer to a user service description (USD).
<33>25
The reception apparatus according to <32>, in which the metadata further includes:
service information on a service; and
access information which refers to the service information to access a service.30
<34>92

The reception apparatus according to <33>, in which the service information includes a service identifier which is the attribute to identify the service information.
<35>5
The reception apparatus according to <34>, in which
the access information includes the information to refer to the USD and further includes one or more pieces of;
an access information identifier which is the 10 attribute to identify the access information;
version information which is the attribute indicating a version of description contents of the access information;
information indicating that a service is either of 15 a broadcast type service or a bidirectional type service;
information indicating that a service is a broadcast type service;
information indicating a session description;
information indicating that a service is a 20 bidirectional type service; and
information indicating a class of a service.
<36>
The reception apparatus according to <35>, in which the metadata is an open mobile alliance-electronic 25 service guide (OMA-ESG) and includes:
a Service element which is the service information;
a Service/@globalserviceId attribute which is the service identifier;
an Access element which is the access information;30
an Access/@id attribute which is the access 93

information identifier;
an Access/@version attribute which is the version information;
an Access/AccessType element which is information indicating whether the service is either of a broadcast 5 type service or a bidirectional type service;
an Access/AccessType/BroadcastServiceDelivery element which is information indicating that the service is a broadcast type service;
an 10 Access/AccessType/BroadcastServiceDelivery/SessionDescription element which is information indicating the session description;
an Access/AccessType/UnicastServiceDelivery element which is information indicating that the service is a 15 bidirectional type service;
an Access/ServiceClass element which is information indicating a class of the service; and
an Access/AccessType/BroadcastServiceDelivery/SessionDescrip20 tion/USBDRef element which is information to refer to the USD.
<37>
The reception apparatus according to <36>, in which the OMA-ESG includes, as the signaling information, a 25 Service/ServiceType element in which the information indicating that the content supplied by the service is the thumbnail video.
<38>
A reception method includes the step of receiving 30 metadata of content, the metadata being described using 94

an attribute and an attribute value and including signaling information indicating that a videois a thumbnail video suitable for constituting a mosaic screen, and information to refer to a user service description (USD).5
REFERENCE SIGNS LIST
[0400]
11channel server
12aggregation server10
13client
14NTP server
21content management server
22segment streamer
23MPD server15
31stream aggregator
32metadata generator
33FLUTE streamer
34multicast server
35web server20
410reception unit
41middleware
42DASH client
43reproduction unit
401bus25
402CPU
403ROM
404RAM
405hard disk
406output unit30
407input unit95

408communication unit
409drive
140input/output interface
411removable recording medium
5 96

CLAIMS
1.A transmission apparatus comprising:
a distribution unit configured to distribute metadata of content, the metadata being described using 5 anattribute and an attribute value and including signaling information indicating that a video is a thumbnail video suitable for constituting a mosaic screen, and the attribute indicating information to refer to a file including information to receive content supplied by 10 a service, wherein
the information to receive the content supplied by the service includes an IP address and a port number of multicast.
15
2.The transmission apparatus according to claim 1, wherein the file is a session description protocol(SDP) file.
3.The transmission apparatus according to claim 2, 20 wherein the metadata further includes one or more pieces of:
information on a collection of one or more services;
information on an individual service;25
a service identifier which is the attribute to identify a service; and
information on a method for distributing content supplied by a service.
30
4.The transmission apparatus according to claim 3, 97

wherein the metadata is a user service description (USD) of a multimedia broadcast multicast service (MBMS) and includes:
a bundleDescription element which is the information on the one or more services;5
a bundleDescription/UserServiceDescription element which is the information on the individual service;
a bundleDescription/userServiceDescription/@serviceId attribute which is the service identifier;10
a bundleDescription/userServiceDescription/DeliveryMethod element which is the information on the method for distributing the content supplied by the service;
a 15 bundleDescription/userServiceDescription/DeliveryMethod/@sessionDescriptionURI attribute which is the attribute indicating the information to refer to the file including the information to receive the content supplied by the service; and20
a bundleDescription/userServiceDescription/@r7:serviceClass attribute which is the signaling information.
5.The transmission apparatus according to claim 4, 25 wherein the USD further includes an r12:appServiceDescription element indicating that the content supplied by the service is to be distributed by either distribution method of multicast or unicast.
30
6.The transmission apparatus according to claim 5, 98

wherein
the r12:appServiceDescription element includes either or both of a broadcast element or/and a unicast element,
the broadcast element and the unicast element each 5 incudes a baseURL attribute indicating a uniform resource locator (URL) of the content supplied by the service,
the broadcast element indicates that the content whose URL is indicated by the baseURL attribute included in the broadcast element is to be distributed by 10 multicast, and
the unicast element indicates that the content whose URL is indicated by the baseURL attribute included in the unicast element is to be distributed by unicast.
15
7.The transmission apparatus according to claim 6, wherein the broadcast element includes, as the signaling information, a thumbnailVideo attribute indicating whether the content whose URL is indicated by the baseURL attribute included in the broadcast element is the 20 thumbnail video.
8.The transmissionapparatus according to claim 7, wherein the USD includes the /r12:appServiceDescription element of each of a plurality of contents capable of 25 constituting a mosaic screen.
9.The transmission apparatus according to claim 8, wherein the broadcast element includes a sessionDescription element indicating information to 30 refer to a session description protocol (SDP) file 99

including an IP address and a port number of multicast by which the content whose URL is indicated by the baseURL attribute included in the broadcast element is to be distributed.
5
10.The transmission apparatus according to claim 8, wherein the r12:appServiceDescription element includes an mpdURI attribute indicating a uniform resource identifier (URI) of a media presentation description (MPD)of moving picture experts group-dynamic adaptive streaming over 10 HTTP (MPEG-DASH) which is metadata to perform reproduction control of the content whose distribution method is indicated by the r12:appServiceDescription element.
15
11.A transmission method comprising the step of:
distributing metadata of content, the metadata being described using an attribute and an attribute value and including signaling information indicating that a video is a thumbnail video suitable for constituting a 20 mosaic screen, andthe attribute indicating information to refer to a file including information to receive content supplied by a service, wherein
the information to receive the content supplied by the service includes an IP address and a port number of 25 multicast.
12.A reception apparatus comprising:
a reception unit configured to receive metadata of content, the metadata being described using an attribute 30 and an attribute value and including signaling 100

information indicating that a video is a thumbnail video suitable forconstituting a mosaic screen, and the attribute indicating information to refer to a file including information to receive content supplied by a service, wherein5
the information to receive the content supplied by the service includes an IP address and a port number of multicast.
13.The reception apparatus according to claim 12, 10 wherein the file is a session description protocol (SDP) file.
14.The reception apparatus according to claim 13, wherein the metadata further includes one or more pieces 15 of:
information on a collection of one or more services;
information on an individual service;
a service identifier which is the attribute to 20 identify a service; and
information on a method for distributing content supplied by a service.
15.The reception apparatus according to claim 14, 25 wherein the metadata is a user service description (USD) of a multimedia broadcast multicast service (MBMS) and includes:
a bundleDescription element which is the information on the collection of the one or more 30 services;101

a bundleDescription/UserServiceDescription element which is the information on the individual service;
a bundleDescription/userServiceDescription/@serviceId attribute which is the service identifier;5
a bundleDescription/userServiceDescription/DeliveryMethod element which is the information on the method for distributing the content supplied by the service;
a 10 bundleDescription/userServiceDescription/DeliveryMethod/@sessionDescriptionURI attribute which is the attribute indicating the information to refer to the file including the information to receive the content supplied by the service; and15
a bundleDescription/userServiceDescription/@r7:serviceClass attribute which is the signaling information.
16.The reception apparatus according to claim 15, 20 whereinthe USD further includes an r12:appServiceDescription element indicating that the content supplied by the service is to be distributed by either distribution method of multicast or unicast.
25
17.The reception apparatus according to claim 16, wherein
the r12:appServiceDescription element includes either or both of a broadcast element or/and a unicast element,30
the broadcast element and the unicast element each 102

incudes a baseURL attribute indicating a uniform resource locator (URL) of the content supplied by the service,
the broadcast element indicates that the content whose URL is indicated by the baseURL attribute included in the broadcast element is to be distributed by 5 multicast, and
the unicast element indicates that the content whose URL is indicatedby the baseURL attribute included in the unicast element is to be distributed by unicast.
10
18.The reception apparatus according to claim 17, wherein the broadcast element includes thumbnailVideo attribute indicating whether content whose URL is indicatedby the baseURL attribute included in the broadcast element is the thumbnail video as the signaling 15 information.
19.The reception apparatus according to claim 18, wherein the USD includes the /r12:appServiceDescription element of each of a plurality of contents capable of 20 constituting a mosaic screen.
20.The reception apparatus according to claim 19, wherein the broadcast element includes a sessionDescription element indicating information to 25 refer to a session description protocol (SDP) file including an IP address and a port number of multicast by which the content whose URL is indicated by the baseURL attribute included in the broadcast element is to be distributed.30 103

21.The reception apparatus according to claim 19, wherein the r12:appServiceDescription element includes an mpdURI attribute indicating a uniform resource identifier (URI) of a media presentation description (MPD) of moving picture experts group-dynamic adaptive streaming over 5 HTTP (MPEG-DASH) which is metadata to perform reproduction control of the content whose distribution method is indicated by the r12:appServiceDescription element.
10
22.A reception method comprising a step of:
receiving metadata of content, the metadata being metadata to be described using an attribute and an attribute value and including signaling information indicating that a video is a thumbnail video suitable for 15 constituting a mosaic screen, and the attribute indicating information to refer to a file including information to receive content supplied by a service,wherein
the information to receive the content supplied by 20 the service includes an IP address and a port number of multicast.
23.A transmission apparatus comprising:
a distribution unit configured to distribute 25 metadata of content, the metadata being described using an attribute and an attribute value and including signaling information indicating that a video is a thumbnail video suitable for constituting a mosaic screen, and information to refer to a user service description 30 (USD), wherein104

the metadata further includes:
service information on a service; and
access information which refers to the service information to access a service.
5
24.The transmission apparatus according to claim 23, wherein the service information includes a service identifier which is the attribute to identify the service information.
10
25.The transmission apparatus according to claim 24, wherein
the access information includes the information to refer to the USD and further includes one or more pieces of;15
an access information identifier which is the attribute to identify the access information;
version information which is the attribute indicating a version of description contents of the access information;20
information indicating that a service is either of a broadcast type service or a bidirectional type service;
information indicating that a service is a broadcast type service;
information indicating a session description;25
information indicating that a service is a bidirectional type service; and
information indicating a class of a service.
26.The transmission apparatus according to claim 25, 30 wherein the metadata is an open mobile alliance-105

electronic service guide (OMA-ESG) and includes:
a Service element which is the service information;
a Service/@globalserviceId attribute which is the service identifier;
an Access element which is the access information;5
an Access/@id attribute which is the access information identifier;
an Access/@version attribute which is the version information;
an Access/AccessType element which is information 10 indicating whether the service is either of a broadcast type service or a bidirectional type service;
an Access/AccessType/BroadcastServiceDelivery element which is information indicating that the service is a broadcast type service;15
an Access/AccessType/BroadcastServiceDelivery/SessionDescription element which is information indicating the session description;
an Access/AccessType/UnicastServiceDelivery element 20 which is information indicating that the service is a bidirectional type service;
an Access/ServiceClass element which is information indicating a class of the service; and
an 25 Access/AccessType/BroadcastServiceDelivery/SessionDescription/USBDRef element which is information to refer to the USD.
27.The transmission apparatus according to claim 26, 30 wherein the OMA-ESG includes, as the signaling 106

information, a Service/ServiceType element in which the information indicating that the content supplied by the service is the thumbnail video.
28.A transmission method comprising the step of:5
distributing metadata of content, the metadata being metadata to be described using an attribute and an attribute value and including signaling information indicating that a video is a thumbnail video suitable for constituting a mosaic screen, and information to refer to 10 a user service description (USD), wherein
the metadata further includes:
service information on a service; and
access information which refers to the service information to access a service.15
29.A reception apparatus comprising:
a reception unit configured to receive metadata of content, the metadata being described using an attribute and an attribute value and including signaling 20 information indicating that a video is a thumbnail video suitable for constituting a mosaic screen, and information to refer to a user service description (USD), wherein
the metadata further includes:25
service information on a service; and
access information which refers to the service information to access a service.
30.The reception apparatus according to claim 29, 30 wherein the service information includes a service 107

identifier which is the attribute to identify the service information.
31.The reception apparatus according to claim 30, wherein5
the access information includes the information to refer to the USD and further includes one or more pieces of;
access information identifier which is the attribute to identify the access information;10
version information which is the attribute indicating a version of description contents of the access information;
information indicating that a service is either a broadcast type service or a bidirectional type service;15
information indicating that a service is the broadcast type service;
information indicating a session description;
information indicating that a service is the bidirectional type service; and20
information indicating a class of a service.
32.The reception apparatus according to claim 31, in which the metadata is an open mobile alliance-electronic service guide (OMA-ESG) and includes:25
a Service element which is the service information;
a Service/@globalserviceId attribute which is the service identifier;
an Access element which is the access information;
an Access/@id attribute which is the access 30 information identifier;108

an Access/@version attribute which is the version information;
an Access/AccessType element which is information indicating whether the service is either of a broadcast type service or a bidirectional type service;5
an Access/AccessType/BroadcastServiceDeliveryelement which is information indicating that the service is a broadcast type service;
an Access/AccessType/BroadcastServiceDelivery/SessionDescrip10 tion element which is information indicating the session description;
an Access/AccessType/UnicastServiceDelivery element which is information indicating that the service is a bidirectional type service;15
an Access/ServiceClass element which is information indicating a class of the service; and
an Access/AccessType/BroadcastServiceDelivery/SessionDescription/USBDRef element which is information to refer to the 20 USD.
33.The reception apparatus according to claim 32, wherein the OMA-ESG includes, as the signaling information, a Service/ServiceType element in which the 25 information indicating that the content supplied by the service is the thumbnail video.
34.A reception method comprising the step of:
receiving metadata of content, the metadata being 30 described using an attribute and an attribute value and 109