WO2019131200A1

WO2019131200A1 - Decoder, decoding method, and program

Info

Publication number: WO2019131200A1
Application number: PCT/JP2018/046020
Authority: WO
Inventors: 五十嵐　卓也; 高林　和彦; 山岸　靖明
Original assignee: ソニー株式会社
Priority date: 2017-12-28
Filing date: 2018-12-14
Publication date: 2019-07-04
Also published as: TW201937938A

Abstract

The present disclosure pertains to a decoder, a decoding method, and a program with which it is possible to improve convenience when streaming delivery content. A web resource of delivery content isdistributed among a plurality of media segments, an item information entry stored in a metabox of an initialize segment that is used in the delivery content is referred to, and an object to be accessed is specified. The web resource stored in the specified media segment is accessed at random. The present technology can be applied, for example, to a service for streaming delivery content on the Internet using MPEG-DASH, MPEG-CMAF, etc.

Description

Decryption device, decryption method, and program

The present disclosure relates to a decrypting device, a decrypting method, and a program, and more particularly, to a decrypting device and a decrypting method capable of improving convenience when streaming distribution content using MPEG-DASH, MPEG-CMAF or the like. , And the program.

In recent years, MPEG-DASH (Moving Picture Experts Group-Dynamic Adaptive Streaming over HTTP) and MPEG-CMAF (Moving Picture Experts Group-Common Media Application Format for Segmented Media) have become popular as basic technologies for streaming services on the Internet. I'm starting.

Also, in streaming using MPEG-DASH or MPEG-CMAF, for example, a metabox of ISO Base Media File Format (ISOBMFF) is used to configure a Web application such as HTML5 (HyperText Markup Language 5) or JavaScript (registered trademark). A technology is used that records and distributes multiple files (Web Resources) to be stored in ISOBMFF. Here, ISOBMFF's MetaBox is disclosed in Non-Patent Document 1, and MPEG-CMAF is formulated in Non-Patent Document 2.

By the way, when the conventional ISOBMFF MetaBox is used as it is, for example, it is difficult to make random access to the required Web Resource, or the start of the application is delayed, or it may be used for bandwidth adaptive streaming. It was difficult, and it was difficult to determine the update and revocation of Web Resources. Therefore, the convenience in streaming delivery content using MPEG-DASH, MPEG-CMAF, etc. has been reduced.

The present disclosure has been made in view of such a situation, and is intended to improve convenience when streaming distribution content using MPEG-DASH, MPEG-CMAF, or the like.

The decryption apparatus according to an aspect of the present disclosure refers to the Item Information Entry stored in the MetaBox of the initialization segment in which the Web Resource of the delivery content is distributed and disposed in a plurality of media segments and used in the delivery content. And an access unit for accessing the Web Resource stored in the identified media segment to be accessed.

In the decryption method according to one aspect of the present disclosure, the decryption device is configured such that the Web Resource of the delivery content is distributed and disposed in a plurality of media segments, and Item Information stored in MetaBox of the initialization segment used in the delivery content Referencing the Entry, and accessing the Web Resource stored in the identified media segment to be accessed.

The program according to one aspect of the present disclosure is an item in which the Web Resource of the distribution content is distributed to a plurality of media segments and arranged in the computer of the decryption apparatus, and stored in the MetaBox of the initialization segment used in the distribution content. Information decryption is performed by referring to Information Entry and accessing the Web Resource stored in the identified media segment to be accessed.

In one aspect of the present disclosure, the Web Resource of the distribution content is distributed and disposed in a plurality of media segments, and the Item Information Entry stored in the MetaBox of the initialization segment used in the distribution content is referred to and accessed. The Web Resource stored in the specified media segment to be targeted is accessed.

According to one aspect of the present disclosure, it is possible to improve the convenience when streaming distribution content using MPEG-DASH or MPEG-CMAF.

In addition, the effect described here is not necessarily limited, and may be any effect described in the present disclosure.

It is a figure which shows the structural example of an ISOBMFF file and a client terminal. It is a figure which shows the example in which the Web Resource recorded on each moof is disperse | distributed and arrange | positioned. FIG. 6 is a diagram showing an example of a web application that changes the display in accordance with the playback time of A / V content. It is a figure which shows the example of a display of "index. html." It is a figure explaining an ISOBMFF file. It is a figure which shows the structure of the media segment file which is PT0S. It is a figure which shows the structure of the media segment file which is PT60S. It is a figure explaining an initialization segment. It is a figure which shows an example of the HTML file recorded as a sample of Timed Text Track. It is a figure which shows the structure of the media segment file which arrange | positioned the extent of Web Resource to several media segments. It is a figure which shows an example of the expanded Item Location Box. It is a figure which shows an example of MetaBox of the initialization segment in the structure which arrange | positioned the extent of Web Resource to several media segments. It is a figure explaining a carousel transmission. It is a figure which shows an example of the format of a Bundle Information Box. It is a figure which shows an example of the media segment containing Bundle Information Box. Fig. 18 is a diagram showing an example of an expanded ItemInfoEntry. It is a figure which shows an example of the media segment which Information Box was expanded. It is a figure explaining extension of MPD of MPEG-DASH. BRIEF DESCRIPTION OF DRAWINGS FIG. 1 is a block diagram illustrating a configuration example of an embodiment of a delivery system to which the present technology is applied. FIG. 16 is a first flowchart illustrating a process of randomly accessing Web Resource. FIG. It is a flowchart explaining an Extent read-in process. It is a 2nd flow chart explaining processing to access Web Resource at random. It is the 3rd flowchart which explains the processing which randomizes to Web Resource. Fig. 21 is a block diagram illustrating a configuration example of an embodiment of a computer to which the present technology is applied.

Hereinafter, specific embodiments to which the present technology is applied will be described in detail with reference to the drawings.

<About the ISOBMFF file>
First, with reference to FIGS. 1 to 4, a technique will be described in which Web Resource is recorded in an ISOBMFF file in the ISOBMFF standard, and A / V (Audio / Visual) content and Web application are distributed as one ISOBMFF file. For such delivery, for example, Item Information Entry ('infe') is recorded in Item Information Box (iinf) of MetaBox of ISOBMFF file, and ISOBMFF is indicated by LocationInformationBox ('iloc') of DataReferenceBox ('dref') corresponding to that. It is realized by showing Web Resource recorded in the file. In the specification, the MP4 file format means a file format defined in accordance with ISO BMFF.

FIG. 1 shows an example of the configuration of an ISOBMFF file and a client terminal.

FIG. 1 shows an example of an ISOBMFF file in which two Web Resources of “index.htm” and “image1.jpg” and “image2.jpg” are recorded in MetaBox. Note that, by using DataReferenceEntryURL instead of LocationInformationBox ('iloc') in MetaBox of the ISOBMFF file, it is also possible to reference Web Resource placed on a server of the Internet from Item Information Entry ('infe'). Thus, an ISOBMFF file containing both A / V content and a web application is distributed via, for example, the Internet, storage media, and the like.

Further, as shown in FIG. 1, the client terminal 11 is configured to include a web engine 12, an A / V player 13, an image superimposing unit 14, an audio mixing unit 15, a display 16, and a speaker 17. For example, the client terminal 11 is configured by mounting the web engine 12 and the A / V player 13 on a smartphone, a television receiver, or the like.

Then, in the client terminal 11, after an image obtained by processing the ISOBMFF file by the web engine 12 and the A / V player 13 is supplied to the image superimposing unit 14, and the respective images are superimposed in the image superimposing unit 14, It is displayed on the display 16. Similarly, in the client terminal 11, the audio obtained by processing the ISOBMFF file by the web engine 12 and the A / V player 13 is supplied to the audio mixing unit 15, and the respective sounds are mixed by the audio mixing unit 15. After that, it is outputted from the speaker 17.

In the MetaBox of the ISOBMFF file shown in FIG. 1, "index. Html" is recorded as a Primary Resource indicated by a Primary Item Box ('pitm), and an entry of a Web application started at the start of A / V content playback. Indicates that it is Page.

On the other hand, ISOBMFF files obtained by fragmenting ISOBMFF files are often used as MPEG-DASH contents. MPEG-DASH treats a group of fragments consisting of one or more MovieFragmentBox (moof) and MediaDataBox (mdat) pairs (pairs) as a media segment, and encodes a media segment encoded at multiple bit rates described by MPD. By preparing it, bandwidth adaptive streaming is realized.

FIG. 2 shows an example in which Web Resources recorded in MovieFragmentBox (moof) of each media segment are distributed and arranged.

According to the ISOBMFF standard, as shown in FIG. 2, to realize "Just In Time Delivery" by distributing and arranging Web Resources recorded in each moof, that is, Web engine 12 uses Web Resources. You can distribute the Web Resource at the same time.

For example, "index.html" and "image1.jpg" are delivered when the first playback start time (0 second), which is the beginning of A / V content, is started, and the web engine 12 Display “and“ image1.jpg ”on the display 16. After that, the second playback start time (60 seconds) is reached, and "image2.jpg" is delivered at the timing when "image2.jpg" is used, and the web engine 12 replaces "image1.jpg" with "image2 “. jpg” is displayed on the display 16. Then, the web engine 12 hides “image2.jpg” at the timing when the third reproduction start time (90 seconds) is reached. The ISOBMFF file is assumed to be used in such a web application.

As a result, it is not necessary to collectively distribute all Web Resources at the beginning of the ISOBMFF file at the start of streaming reproduction, so it is possible to speed up the start of reproduction of A / V content.

An example of the web application which changes a display according to the reproduction time of A / V content as shown in FIG. 2 is shown by FIG. 2, and FIG. 4 shows the web engine 12 of such a web application. The example of display of "index. Html" by processing is shown. That is, as shown in FIG. 4, when “image1.jpg” is displayed from the reproduction time 0 on the display 16 when it is superimposed on file.mp4 processed by the A / V player 13 and the reproduction time is 60 seconds. It is changed from "image1.jpg" to "image2.jpg" and "image2.jpg" is displayed up to 90 seconds.

By the way, according to the method as described above, processing can be efficiently performed when performing streaming reproduction continuously from the first reproduction start time (0 second) which is the head of A / V content. On the other hand, in video-on-demand services, etc., playback is performed from the second playback start time (for example, 60 seconds) other than the head of the A / V content or the third playback start time (for example, 90 seconds) Consider the case of starting In this case, since it is assumed that Web Resources placed in each media segment are sequentially accessed from the beginning along with A / V content playback, it is extremely difficult to randomly access the required Web Resources at each time. It was inefficient and it was difficult to launch Web applications at high speed and display A / V content. Therefore, in order to be able to launch a Web application at high speed, it is required to enable random access to the required Web Resource at each point in time.

In addition, when playing back A / V content with limited network bandwidth such as MPEG-DASH streaming, for example, files of still images, videos, or audio with large data size are recorded in a specific media segment. Consider the cases in which In this case, since the data amount of the media segment varies, the content bit rate changes locally, which makes it difficult to use in band adaptive streaming. Therefore, there is a need to make the bit rate as uniform as possible so that it can be facilitated in bandwidth adaptive streaming.

In addition, as seen in ATSC 3.0 standard, in uni-directional transmission such as broadcast and IP multicast, consider the case of delivering content including Web application using MPEG-DASH or MPEG-CMAF. Also in this case, it is required to make the bit rate as uniform as possible, but as a further problem, since the A / V content is divided as a media segment, the client terminal 11 plays back even during the start of channel selection. Although it is possible, it is conceivable to carry out carousel transmission by repeating the same Web Resource every few seconds so that the Web application can also be launched immediately. However, in this case, if the data size of the Web application becomes large, the start of the Web application will be delayed, or a lot of unnecessary transmission bandwidth for carousel transmission of short repetitions will be required, and the bit rate of A / V content needs to be lowered. It is not preferable because it is easy. Therefore, there is a need to accelerate Web application startup while delivering Web Resources without wasting bandwidth in carousel transmission.

In addition, we will consider the case of recording Web Resource in ISOBMFF file and distributing A / V content and Web application collectively. In this case, for example, when you want to make a bug in the web application, improve the GUI design, add functions, etc., instead of the web resource recorded in the ISOBMFF file indicated from LocationInformationBox, with the latest web resource placed on the Internet server. There was a need for the web engine 12 to use. On the other hand, DataReferenceEntryURL can refer to the Web Resource of the Internet, but since there is no information such as creation date and expiration date of Web Resource distributed as ISOBMFF file, Web Engine 12 can use either Web Resource I could not judge whether it was good.

In addition, when distributing content including Web applications using MPEG-DASH or MPEG-CMAF, etc. in one-way transmission such as broadcasting or IP multicasting, the Web Resource update date and expiration date were not known. The client terminal 11 could not efficiently perform caching of Web Resources. In other words, there is a need for the client terminal 11 to use the cached Web Resource without receiving the Web Resource that has not been updated or expired. Therefore, it is required to be able to determine whether the Web Resource recorded in the ISOBMFF file is updated or expired.

Therefore, the configuration example of the ISOBMFF file described below, as described above, enables random access, achieves uniform bit rates, and does not waste bandwidth in carousel transmission. The purpose is to realize quick start-up and enable determination of update and expiration of Web Resource recorded in the ISOBMFF file.

<Example of configuration of ISOBMFF file that enables random access>
A configuration example of an ISOBMFF file that enables random access will be described with reference to FIGS. 5 to 9.

FIG. 5 shows an example of the configuration of an ISOBMFF file that enables random access.

For example, the ISOBMFF file shown in FIG. 5 is distributed to each media segment of the ISOBMFF file used for the MPEG-DASH content, and Web Resources are arranged in “Just In Time Delivery”. Then, in the ISOBMFF file, the recording of the MetaBox is performed in the ItemLocatoinBox ('iloc') of the DataReferenceBox ('dref') corresponding thereto.

Furthermore, in the ISOBMFF file, a URL (Uniform Resource Locator) in the DataReferenceBox ('dref') of MetaBox directly refers to the Web Resource of each media segment, or an Item in the media segment at the file level as follows: Indirect reference is performed using Information Entry. As a result, the ISOBMFF file is configured such that the Web Resource of each media segment can be accessed from the Item Information Entry of the file level MetaBox.

For example, according to the ISOBMFF standard, it is possible to refer to Extent of another file by using Item Location, but in a fragmented ISOBMFF file of delivery contents such as MPEG-DASH and MPEG-CMAF, media segments are different. Because it was divided into files and handled, it was difficult to handle with byte offsets. In addition, there is a disadvantage that it is not possible to create an Item Location Entry to which reference is made unless the media segment is generated.

On the other hand, in the ISOBMFF file, as described below, the DataReferenceBox is used to directly refer to the Web Resource of each media segment in the URL, or an indirect reference using the MetaBox of the moof of each media segment is used. To be done.

For example, with reference to FIGS. 6 and 7, a method of recording Web Resource in a media segment will be described by taking MPEG-DASH content in which the media segment includes moof and mdat as an example.

FIG. 6 shows the structure of a media segment file whose Earliest Presentation Time is PT0S when the ISOBMFF file is divided into a plurality of media segment files, that is, the structure of the media segment file at the beginning of the A / V content. It is done.

For example, a MetaBox is arranged in moof, and the MetaBox records a Handler Box (hdlr), a Primary Item Box (pitm), an Information Location Box (iloc), and an Item Information Box (iinf) in addition to an Audio track.

Further, Item Information Entry is recorded in the iinf Box, and in the example shown in FIG. 6, Entry_count = 2, which indicates that two Items are recorded. The first Item Information Entry is item_id = 0, and the file name of Item can be known from item_name = index.html. The second Item Information Entry is Item_id = 1 and item_name = image1.jpg.

In addition, the storage location of the content (Extent) of the file of Item specified by each Item_ID is recorded in iloc Box, and in the example shown in FIG. 6, item_count = 2, and the locations of two items are It is shown that it is recorded. The first Item Location Entry indicates that it corresponds to index.html because item_id = 0. Also, as data_reference_index = 0, it is indicated that the Extent of this Item is recorded in the same file.

For example, in the MPEG-DASH content, assuming that segment files are divided into separate files, set the base-data-offset-present of moof Track Fragment Header Boxes to 0, set default-base_is_moof to 1, and set moof and It is offset by the relative position within the segment consisting of mdat pairs. In the example shown in FIG. 6, the byte offset B0 from the beginning of the media segment file to index.html actually recorded in mdat is specified in the extent_offset of the extent of index.html. Moreover, L0 which is a file size of index. Html is recorded in extent_length. Similarly, the byte offset B1 is specified in extent_offset of extent of image1.jpg, and L1 which is the file size of image1.jpg is recorded in extent_length.

Also, in pitm, an Item to be loaded first in the HTML web application is specified. In the example shown in FIG. 6, since the item_id = 0 of pitm, the web engine 12 loads index.html first.

FIG. 7 shows the structure of the media segment file whose Earliest Presentation Time is PT60S, that is, the structure of the media segment to be played back after 60 seconds when playback is started from the beginning of the A / V content.

In the media segment shown in FIG. 7, entry_count = 1 in Item Information Entry of iinf Box indicates that one Item is recorded. Then, iinf Box indicates item_name = image2.jpg, iloc Box indicates extent_offset = B2 and extent_length = L2, and image2.jpg is B2 bytes from the beginning of the media segment file and file size L2 It represents that it is recorded. Since web engine 12 has already processed index.html recorded in the media segment file of PT0S, no pitm is recorded in the media segment file of PT60S.

As described above, the Web Resource can be recorded in each media segment by MetaBox that can be realized by the ISOBMFF standard. Then, in the present embodiment, as described below, the MetaBox is recorded in the initialization segment (header). This enables random access to the web resource of the media segment.

In the initialization segment shown in FIG. 8, the iBox of MetaBox arranged in moov and the item of Web Resource placed in each media segment are recorded in a total of three Item Information Box Entries, and item_name is index.html, image1.jpg , Image2.jpg. In addition, the storage location of each Item is recorded in iloc, and other than 0 is specified in data reference, which arranges dinf (DataInformationBox) so that other files can be referred to indirectly by URL. Make it

And when referring indirectly to the item of MetaBox of the media segment, the initialize segment in FIG. 8 is characterized by the form of URL described in dinf, such as # presentationTime = PT0S, track_id = 1, item_name = index Format is newly defined in the URL. This is a URL meaning that it refers indirectly to an Item called index.html in which Earliest Presentation Time of the media segment of the ISOBMFF file is in Track_1 of PT0S.

Then, when referring directly to the Web Resource placed in the media segment, the initialize segment in FIG. 8 is characterized by the form of the URL described in dinf, and the form such as # presentationTime = PT0S is in the form of URL It is newly defined. This is a URL that means that Earliest Presentation Time of the media segment of the ISOBMFF file directly refers to the segment file of PT0S. In the case of direct reference, in order to specify the Extent range of the Web Resource placed in the segment file, a non-zero value is specified in extent_offset described in iloc of the Item of the corresponding Item of the MetaBox of the reference source initialization segment It will be

Thus, by newly defining the format of the URL, the web engine 12 can randomly access the web resource included in each media segment. For example, when the MPEG-DASH content uses Segment Index as in the On Demand Profile, it is possible to specify the media segment including the moof. Also, for example, when the MPEG-DASH content is such that the media segment is a separate file as in Live Profile, it is possible to identify the media segment file including the moof from the MPD. In the MPEG-CMAF file, the media segment file including the moof can be specified from the Manifest File. As a result, the web engine 12 acquires the corresponding media segment, and because the MetaBox as shown in FIG. 8 is recorded in the moof of the media segment, the web resource corresponding to track_id = 1, item_name = 1 is stored. Extents can be extracted from mdat.

Thus, even if the MPEG-DASH content uses the Segment Index like On Demand Profile, or if the media segment is a separate file like Live Profile, the web engine 12 will Random access to Web Resources included in the segment is possible.

Here, the method of referring to the Web Resource recorded in MetaBox of the media segment shown in FIG. 8 by the URL is the playback time of the playback time such as Timed text tracks and Timed metadata track specified in ISO / IEC 14496-30. It is also available as a Web Resource (called "Timed Web Assets") with timing information.

For example, as shown in FIG. 9, from an HTML file recorded as a sample of Timed Text Track, it is possible to refer to a Resource recorded in MetaBox using a URL as described with reference to FIG. It becomes.

<ISOBMFF file for uniform bit rate>
An ISOBMFF file for achieving uniform bit rates will be described with reference to FIGS. 10 to 12.

As described above, when Web Resource is recorded in the media segment of DASH content, if the file size of Web Resource is increased, the file size of only that media segment is increased, and the bit rate of DASH content is not uniform. For example, when encoded at a constant bit rate of 8 MBps for DASH content and the Segment Duration is 1 second, the media segment is 1 Mbyte. On the other hand, JPEG and PNG files for Web applications may exceed 1 Mbyte for 2k and 4K resolutions, and the file size of the media segment recorded with Web applications will be large.

In the media segment shown in FIG. 10, an example is shown in which Extent of Image2.jpg is substantially equally divided into three partial extents (division data). For example, the file size of the first portion Extent is B2-1 bytes, and Earliest Presentation Time is stored in a media segment of 60 seconds. In addition, the file size of the second portion Extent is B2-2 bytes, and is stored in a media segment whose Earliest Presentation Time is 61 seconds. Similarly, the file size of the third portion Extent is B2-3 bytes, and the Earliest Presentation Time is stored in the media segment of 62 seconds.

Further, in FIG. 10, “image2.jpg” is numbered with a # sign and a number starting with 1 so as to indicate that each item information entry corresponds to the partial extent, and becomes item_name. That is, the first part Extent is item_name = image2.jpg # 1, the second part Extent is item_name = image2.jpg # 2, and the third part Extent is item_name = image2.jpg # It is three.

In such a media segment, as shown in FIG. 11, two extended parameters of Extent_position (byte offset) and total_Size (total byte size) are added to the item entry of Item Location Box, and each Extent is a Web Resource It shows which position of Extent corresponds to. Thus, for example, after acquiring the second portion Extent (PT 61 S), it is determined that it is necessary to acquire the media segment of the previous and following Earliest Presentatin Time in order to acquire the entire Extent.

FIG. 12 shows an example of the MetaBox of the initialization segment in a configuration in which Extents of Web Resource are arranged in a plurality of media segments.

As shown in FIG. 12, the dref URL of dinf of image2.jpg is # presentationTime = PT60S, duration = PT3S, track_id = 1, item_name = image2.jpg, and the parameter “duration = PT3S” is added. . This indicates that a partial Extent of image2.jpg is recorded in the media segment of 3 seconds from PT60S.

Therefore, the web engine 12 of FIG. 1 obtains image2.jpg by acquiring extents of items including item2.name from item_name from three segments whose Earliest presentation times are 60S, 61S, and 62S. can do.

<Example of ISOBMFF file configuration to speed up startup of Web application>
An example of the configuration of an ISOBMFF file for speeding up the startup of a web application will be described with reference to FIGS. 13 to 15.

First, the delay in launching a web application will be described.

For example, as in ATSC 3.0, consider an application where MPEG-DASH content is broadcast to the client terminal 11 by one-way transmission such as broadcast or IP multicast. In this case, MPEG-DASH Live Profile is used, and each media segment will be transmitted as a separate file. Although it is possible to record the Web resource of the Web application in this media segment, random access can not be performed because of one-way transmission.

Therefore, as shown in FIG. 13, so-called carousel transmission is performed in which the same Web Resource is repeated in a fixed period.

In the example shown in FIG. 13, the unit of aggregation of index. Html, image1.jpg, image2.jpg is repeatedly transmitted. Thus, even if the client terminal 11 of FIG. 1 receives the broadcast service at any of the first to third playback start times, the index. Html of the interactive Web application linked to the broadcast service. Can be launched. In addition, for example, when the client terminal 11 starts reception from the second reproduction start time, the client terminal 11 waits until receiving the media segment including the index.html, which causes a delay in activation of the Web application. It will

By the way, according to the conventional ISOBMFF standard, a Web Resource (for example, image1.jpg) which is first loaded to the Web engine 12 and used at start-up indicated by Primary Item Box (pitm) and necessary after start-up is Web Resource (for example, There is no mechanism to distinguish it from image2.jpg). For this reason, since it can not be determined whether image2.jpg is used from index.html, if index.html and image1.jpg are received at the first reproduction start time, start index.html immediately. It can not be determined whether it is ok to wait until the image2.jpg is received and then start index.html. If both image1.jpg and image2.jpg are needed when launching index.html, image2.jpg will not be displayed correctly.

Therefore, in order to accelerate Web application startup, a Bundle Item Information Box extended Item Information Box is provided, and it is possible to explicitly indicate that items stored in the subsequent media segment are to be used collectively. Let's do it.

FIG. 14 shows the format of the Bundle Information Box.

As shown in FIG. 14, the Bundle Information Box is placed in the MetaBox together with the Item Information Box. And when using this Item Information Box, it is to be used together when the Web Resource indicated by item_name written in Bundle ItemInfoEntry is received by Item in Item Information Item of the subsequent media segment. It shows.

FIG. 15 shows an example of a media segment including a bundle information box.

As shown in FIG. 15, a segment file with an Earliest presentation time of 0 seconds has a Primary Item Box, and an Item of index.html is shown in the Primary Item Box. On the other hand, the item of image1.jpg is shown in BundleInformationBox (binf). Therefore, the web engine 12 of the client terminal 11 loads index.html after receiving image1.jpg contained in the next one-second segment file to start index.html.

As another use, for example, it is conceivable that a media segment file of MPEG-DASH is applied to a target advertisement of broadcasting. For example, when they are stored as a Web Resource in an ISOBMFF file, they have a Bundle Information Box together with Item Information including the top segment file of the segment file group corresponding to the advertisement period. Then, by listing other segment files in the item as a Bundle Information Entry, it is possible to replace the advertisement only when all segment files of the advertisement period have been received.

If the Web application displays an advertisement while all segment files can not be received, it is assumed that a significant problem occurs because the advertisement can not be displayed correctly. On the other hand, occurrence of such a problem can be avoided by using the media segment including the Bundle Information Box as described above.

<Example of configuration of ISOBMFF file that enables determination of Web Resource update and revocation>
With reference to FIGS. 16 and 17, an example of the configuration of an ISOBMFF file that enables the determination of Web Resource update and revocation will be described.

FIG. 16 shows an example of ItemInfoEntry expanded to indicate that the Web Resource stored in the ISOBMFF file has been updated if it has been updated. For example, ItemInfoEntry is extended to be able to record values equivalent to the Last_Modified and RFC-7243 Expires headers specified in RFC 7232 of the IETF.

FIG. 17 shows an example of a media segment in which the Information Box (iinf) is expanded.

In the media segment shown in FIG. 17, in iinf, last-Modifed and expires are specified for image2.jpg. Also, in iloc, in addition to Extent recorded in the file, item entry and item_entry indicating the URL of dinf are shown.

Here, in the example illustrated in FIG. 17, the URL (Reference URL) of dinf is specified as https: //example/log/image2.jpg. At this time, for example, when the web engine 12 is connected to the Internet, it is updated by specifying Last_modifed recorded in item entry info in the "If Modifed-Since" header in the HTTP GET request to the URL. You can only get files provided by other devices on the Internet. It is also possible to invalidate the cached file by notifying the web engine 12 of Expires of item entry info, and replace the cached data with a new file.

As described above, when Web Resource is stored and delivered to the media segment used in MPEG-DASH, enabling random access, achieving equalization of bit rate, bandwidth by carousel transmission, etc. The extension of the ISOBMFF standard has been described, which makes it possible to speed up the startup of a web application without wasting it, and to make it possible to judge the update and expiration of the Web Resource recorded in the ISOBMFF file.

Note that when placing a Web resource in a media segment of MPEG-DASH or a segment of MPEG-CMAF, there is a method of using Event Message Box (emsg) in addition to the method of using MetaBox described above. In that case, the Web Resource can also be placed in the emsg box, or can be placed in the mdat as described above. For example, in either case, similar effects can be obtained by writing information for accessing Web Resources corresponding to the contents described in the above-mentioned initialization segment and media segment MetaBox in the Event Message Box. . Furthermore, in the following, an embodiment will be described in which the ISOBMFF file thus expanded is used in MPD of MPEG-DASH.

That is, the MPD of MPEG-DASH is extended, and a SchemeIdUri of "urn: mpegEmbeddedEntryPageURL" is defined as EssentialProperty or SupplementalProperty so that it can be added to either Period, AdaptationSet, or Representation.

For example, in the case of supplemental property, it is indicated that the Web resource is stored in the ISOBMFF file in any of the tracks of the corresponding period. Therefore, the client terminal 11 which is a DASH player may or may not reproduce Web Resource by the Web engine 12 when reproducing the A / V content of this MPD. On the other hand, if it is an EssentialProperty, it indicates that the Web Resource must be played back to play the Period. Thus, DASH players that do not support web engine 12 need to either skip Period playback or play their entire MPD.

Thus, for example, it is possible to always start the web application and reproduce the advertising banner when reproducing the A / V content. Also, the Web Resource specified in the Primary Item Box in the MetaBox of the ISOBMFF initialization file is loaded by the Web engine 12 as an Entry Page.

The extension of the MPD of MPEG-DASH will be described with reference to FIG.

In the MPEG-DASH MPD shown in FIG. 18, the first Period indicates an example of SupplementalProperty.

Also, in the second Period, this EssentialProperty can optionally have an attribute called value, and the value shows that Web Resources other than Primary Item written in Meta Box of the initialization segment are loaded as Entry Page ing. In addition, in "# presentation_time = PT60S, track_id = 1, item_name = index2.html", the Web resource named index2.html recorded in the media segment whose Earliest Presentation Time in the media segment of Period is 60 seconds is entered It shows that it starts. For example, if a Supplemental Property of url: mpeg: EmbeddedEntrypageURL "is placed in the Adaptation Set, it is possible to change the Entry Page for each language of the Adaptation Set.

In addition, the third Period has a ScehemeIdUrl of url: mpeg: EntrypageURL "as a SupplementalProperty, which is stored in ISOBMFF and not provided by Web Resource, but is provided from an Internet Web server and is defined as Web Resource as Entry page. Even in DASH content that does not include Web Resource, Web Application can be played simultaneously with A / V content.

<Configuration Example of Network Delivery System>
An example of the configuration of a network distribution system that distributes MPEG-DASH content via a network using the ISOBMFF file as described above and the process performed in the client terminal 11 will be described with reference to FIGS. 19 to 23. .

As shown in FIG. 19, the network distribution system 21 is configured by connecting the client terminal 11 to the server device 23 via the network 22. Then, in the network distribution system 21, the distribution data generated by the distribution data generation device 24 is distributed to the client terminal 11 by the server device 23.

The client terminal 11 includes a decryption unit 31 that decrypts MPEG-DASH content. The decryption unit 31 includes the media segment identification unit 32 and the Web Resource in addition to the web engine 12 and the A / V player 13 shown in FIG. It comprises the access part 33 and is comprised.

The media segment specifying unit 32 is a media segment requested according to the playback time of the MPEG-DASH content by the web engine 12 (for example, a media segment in which a web resource to be subjected to random access by the web resource access unit 33 is arranged) Identify). The Web Resource access unit 33 accesses the Web Resource disposed in the media segment identified by the media segment identification unit 32 (for example, the media segment identified with reference to Item Information Entry stored in the MetaBox). . The processing performed by the media segment identification unit 32 and the Web Resource access unit 33 will be described with reference to the flowcharts of FIGS.

The server device 23 is configured to distribute the corresponding Web Resource at the timing when the Web engine 12 of the client terminal 11 uses the Web Resource.

The delivery data generation device 24 includes an encoding unit 41 that encodes MPEG-DASH content, and the encoding unit 41 includes a segment file generation unit 42 and a media segment processing unit 43. The segment file generation unit 42 generates a segment file as described above, and the media segment processing unit 43 divides the Web Resource into, for example, a predetermined number of divided data substantially equally, and the predetermined Earliest Presentation Time is continuous. Perform processing such as arranging in a number of media segments.

Then, the distribution data generation device 24 uploads the MPEG-DASH content, for which the segment file generation unit 42 has generated a segment file and the media segment processing unit 43 has processed the media segment, to the server device 23 and distributes it. .

Referring to the flowcharts of FIGS. 20 to 23, in the case of the On Demand profile of MPEG-DASH content, the initialization segment and the media segment are stored in one ISOBMFF file, and the segment index is used at the ISOBMFF file level. When each media segment is referred to, Web resource random access is performed when the decryption unit 31 in FIG. 19 indirectly refers to the Item referred to by the MetaBox of the initialization segment from the Item referred to by the MetaBox of the segment file. The process to be performed will be described.

For example, the decryption unit 31 starts processing when the Web engine 12 requests a Web Resource designated by a URL (for example, image2.jpg or the like) indicating item_name. Then, in step S11, the media segment identification unit 32 recognizes a URL indicating item_name of the Web Resource.

In step S12, the media segment identification unit 32 reads the MetaBox from the ISOBMFF file or the moof of the ISOBMFF file.

In step S13, the media segment identification unit 32 searches for items that match the URL recognized in step S11 from the item information entry (infe) recorded in the item information box (iinf) in the MetaBox read out in step S12. Do.

In step S14, the media segment identification unit 32 determines whether or not infe matching the URL recognized in step S11 has been detected as a result of the search in step S13.

In step S14, when the media segment identification unit 32 determines that the infe that matches the URL recognized in step S11 can not be detected, the process proceeds to step S15. Then, in step S15, the media segment identification unit 32 returns an error response code (for example, 404 Not Found) indicating no detection to the web engine 12, and the process is ended.

On the other hand, if the media segment identification unit 32 determines in step S14 that the infe matching the URL recognized in step S11 has been detected, the process proceeds to step S16.

In step S16, the Web Resource access unit 33 performs an extent reading process (see FIG. 21) for reading the extent based on the infe detected by the media segment identification unit 32 in step S13.

In step S17, the Web Resource access unit 33 causes the web engine 12 to read the data read in the Extent read process of step S16 together with the normal response code (for example, OK 200 etc.), ie, the web resource specified by the web engine 12. After returning, the process ends.

FIG. 21 is a flowchart for explaining the Extent reading process performed in step S16 of FIG.

In step S21, the Web Resource access unit 33 searches the item location box in the MetaBox for an item having an item_id that matches the Item Information Entry (infe) identified by the media segment identification unit 32.

In step S22, as a result of the search in step S21, the Web Resource access unit 33 determines whether or not an item having an item_id that matches the infe identified by the media segment identification unit 32 has been detected.

If, in step S22, the Web Resource access unit 33 determines that the item having the item_id that matches the infe specified by the media segment specification unit 32 can not be detected, the process proceeds to step S15 of FIG. Is done.

On the other hand, in step S22, when the Web Resource access unit 33 determines that the item having the item_id that matches the detected infe has been detected, the processing proceeds to step S23.

In step S23, the Web Resource access unit 33 determines whether the data_reference_index of the detected item is 0 or not.

In step S23, when the Web Resource access unit 33 determines that the data_reference_index of the detected item is 0, the process proceeds to step S24.

In step S24, the Web Resource access unit 33 reads data for extent_length from the byte position of the extent_offset of the file, and after setting it as extent, the process proceeds to step S17 in FIG. 20 and the above-described process is performed.

On the other hand, in step S23, when the Web Resource access unit 33 determines that the data_reference_index of the detected item is not 0, the processing proceeds to step S31 in FIG.

As shown in FIG. 22, in step S31, the media segment identification unit 32 reads the URL of the DataReference immediately preceding data_reference_index (data_reference_index-1) from DataInformationBox (dinf) in the MetaBox.

In step S32, the media segment identification unit 32 determines whether the URL of the DataReference read in step S31 is a reference URL including # presentation Time.

In step S32, when the media segment specifying unit 32 determines that the URL of DataReference is not a reference URL including # presentation Time, the process proceeds to step S33.

In step S33, the Web Resource access unit 33 reads the file of the DataReference URL identified by the media segment identification unit 32 from the Internet using HTTPS (Hypertext Transfer Protocol Secure). Then, the media segment identification unit 32 sets the read file as the corresponding Web Resource.

In step S34, the Web Resource access unit 33 determines whether the reading of the file in step S33 has succeeded.

In step S34, when the Web Resource access unit 33 determines that reading of the file in step S33 is successful, the process proceeds to step S17 in FIG. 20, and the above-described process is performed.

On the other hand, if the Web Resource access unit 33 determines in step S34 that the reading of the file in step S33 has not succeeded (failed), the process proceeds to step S35.

In step S35, after the media segment identification unit 32 returns an HTTP error code to the web engine 12, the process is terminated.

On the other hand, when the media segment specifying unit 32 determines that the URL of the DataReference is a reference URL including #presentationTime in step S32, the process proceeds to step S41 of FIG.

As shown in FIG. 23, in step S41, the media segment identification unit 32 refers to the segment index of the ISOBMFF file and sets it as the media segment target of the range specified by # presentation_item and duration (range information).

In step S42, the media segment identification unit 32 reads the MetaBox of the target media segment from the ISOBMFF file.

In step S43, the media segment identification unit 32 searches the Item Information Entry ('infe') of the Information Box (iinf) in the MetaBox for a item whose item_name matches the URL. At this time, the media segment identification unit 32 ignores the symbol after the # symbol of item_name.

In step S44, the media segment specifying unit 32 determines whether or not infe in which item_name matches the URL has been detected as a result of the search in step S43.

In step S44, when the media segment specifying unit 32 determines that the item in which item_name matches the URL can not be detected, the process proceeds to step S15 in FIG. 20, and the above-described process is performed.

On the other hand, if the media segment identification unit 32 determines in step S44 that the infe in which the item_name matches the URL has been detected, the process proceeds to step S45.

In step S45, the Web Resource access unit 33 performs the same extent read processing as described above with reference to FIG. 21, and sets the corresponding web resource as a partial extent.

In step S46, the media segment identification unit 32 determines whether all target media segments have been processed.

If it is determined in step S46 that the media segment identification unit 32 does not process all target media segments, the process returns to step S42, and the same process is repeated.

On the other hand, when the media segment specifying unit 32 determines in step S46 that all the target media segments have been processed, the process proceeds to step S47.

In step S47, the Web Resource access unit 33 combines the partial extents read by repeating the processing from step S42 to step S45, and after acquiring the entire extent of the Web Resource, the process proceeds to step S17 of FIG. The process proceeds as described above.

Here, in the case of a Live Profile profile of MPEG-DASH content, and the initialization segment and the media segment are separately stored and delivered, and the URLs of those files are described in the MPD, the decryption unit 31 The process of will be described.

For example, compared with the case of On Demand Profile as described with reference to FIGS. 20 to 23, in the case of Live Profile, the process of step S12 of FIG. 20 and the process of step S41 of FIG. Differently, other processing is performed similarly.

That is, in the case of the On Demand Profile, in step S12 of FIG. 20, processing for reading the MetaBox from the ISOBMFF file or the moof of the ISOBMFF file is performed. On the other hand, in the case of the Live Profile, processing is performed to read out the MetaBox of the Initization Segment file indicated by the MPD of MPEG-DASH.

Further, in the case of On Demand Profile, in step S41 of FIG. 23, processing is performed for media segments in the range designated by # presentation_item and duration with reference to Segment Index of the ISOBMFF file. On the other hand, in the case of the Live Profile, the MPD of the MPEG-DASH is referred to, the URL of the media segment file in the range designated by # presentation_item and the duration is specified, and the processing targeting these media segments is performed.

As described above, in both On Demand Profile and Live Profile for MPEG-DASH content, random access to necessary Web Resources is enabled when distributed to media segments ("Just In Time Delivery"). be able to.

<Example of computer configuration>
Note that the processes described with reference to the above-described flowchart do not necessarily have to be processed in chronological order according to the order described as the flowchart, and processes performed in parallel or individually (for example, parallel processes or objects Processing) is also included. The program may be processed by one CPU or may be distributed and processed by a plurality of CPUs.

Also, the series of processes (decoding method) described above can be performed by hardware or software. When a series of processes are executed by software, the various functions are executed by installing a computer in which a program constituting the software is incorporated in dedicated hardware or various programs. The program can be installed, for example, on a general-purpose personal computer from a program recording medium on which the program is recorded.

FIG. 24 is a block diagram showing an example of a hardware configuration of a computer that executes the series of processes described above according to a program.

In the computer, a central processing unit (CPU) 101, a read only memory (ROM) 102, and a random access memory (RAM) 103 are mutually connected by a bus 104.

Further, an input / output interface 105 is connected to the bus 104. The input / output interface 105 includes an input unit 106 including a keyboard, a mouse and a microphone, an output unit 107 including a display and a speaker, a storage unit 108 including a hard disk and a non-volatile memory, and a communication unit 109 including a network interface. A drive 110 for driving a removable medium 111 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory is connected.

In the computer configured as described above, for example, the CPU 101 loads the program stored in the storage unit 108 into the RAM 103 via the input / output interface 105 and the bus 104 and executes the program. Processing is performed.

The program executed by the computer (CPU 101) is, for example, a magnetic disk (including a flexible disk), an optical disk (CD-ROM (Compact Disc-Read Only Memory), DVD (Digital Versatile Disc), etc.), a magneto-optical disk, or a semiconductor It is recorded on a removable medium 111 which is a package medium including a memory or the like, or is provided via a wired or wireless transmission medium such as a local area network, the Internet, and digital satellite broadcasting.

The program can be installed in the storage unit 108 via the input / output interface 105 by mounting the removable media 111 in the drive 110. The program can be received by the communication unit 109 via a wired or wireless transmission medium and installed in the storage unit 108. In addition, the program can be installed in advance in the ROM 102 or the storage unit 108.

<Example of combination of configurations>
Note that the present technology can also have the following configurations.
(1)
The Web Resource of the distribution content is distributed and arranged in a plurality of media segments, and the Item Information Entry stored in the MetaBox of the initialization segment used in the distribution content is referred to, and the identified target to be accessed A decryption apparatus comprising: an access unit for accessing the Web Resource stored in a media segment.
(2)
The delivery content is an MP4 file format, and
The decryption apparatus according to (1), wherein the Item Information Entry is stored in an Information Box in the Meta Box.
(3)
The decryption apparatus according to (1) or (2), wherein the Item Information Entry includes information for indirectly referring to Item Information Entry in the MetaBox of the plurality of media segments used for the delivery content.
(4)
The decryption apparatus according to any one of (1) to (3), further comprising: a media segment identification unit that identifies the media segment in which the Web Resource to be accessed is arranged.
(5)
The decryption apparatus according to (4), wherein the access unit randomly accesses the Web Resource identified by the media segment identification unit.
(6)
In the Item Information Entry of the reference source stored in the initialization segment, the media on which the Web Resource is arranged so that the Item Information Entry stored in the MetaBox of the media segment of the reference destination can be accessed Information indicating the Earliest Presentation Time applicable to the segment is described,
The decryption apparatus according to any one of (1) to (5), wherein the access unit accesses the Web Resource using information indicating the Earliest Presentation Time.
(7)
The information indicating the Earliest Presentation Time is recorded as a URL (Uniform Resource Locator) of the DataReferenceBox in the MetaBox of the reference source,
The decryption apparatus according to (6), wherein the access unit accesses the Web Resource using the URL.
(8)
A media segment identification unit that identifies the media segment to be accessed based on the Earliest Presentation Time described in the URL and information on the delivery content,
The decryption apparatus according to (7), wherein the access unit accesses the Web Resource from a MetaBox stored in the media segment identified by the media segment identification unit.
(9)
The Web Resource is divided substantially equally into a predetermined number of divided data, and each of the divided data is arranged in a predetermined number of the media segments in which Earliest Presentation Time is continuous,
The decryption apparatus according to any one of (1) to (8), wherein the access unit acquires the entire Web Resource by collecting and combining the divided data.
(10)
In the URL for the Item Information Entry of the MetaBox referred to by the initialization segment, range information of the Earliest Presentation Time of each of the media segments in which a predetermined number of divided data pieces into which the Web Resource is divided is arranged Included,
The decoding apparatus according to (9), wherein the access unit acquires the entire Web Resource by accessing the media segment corresponding to the range information, collecting a predetermined number of pieces of divided data, and combining them.
(11)
In the case where one Web Resource is divided into a predetermined number of divided data and arranged in the media segment, each of the predetermined number of media segments is within the range in which the divided data in the Web Resource is recorded. The MetaBox indicating the byte offset and byte size in the media segment is recorded,
The decryption apparatus according to (10), wherein the access unit accesses the Web Resource using the MetaBox.
(12)
In the MetaBox, a byte offset of the divided data in the Web Resource and an entire byte size of the Web Resource are recorded to indicate which part of the Web Resource divided into a predetermined number is configured. The decoding device according to (11) above.
(13)
When the Web Resource used when launching a Web Application and the Web Resource not used when launching are recorded and transmitted in separate Media Segments,
In the Primary Item Box of the MetaBox, the Web Resource to be activated first is specified, and in the Meta Box, information indicating the other Web Resources necessary at the time of activation is listed.
The decryption unit according to any one of (1) to (12), wherein the access unit activates the Web Application after acquiring all of the plurality of Web Resources required at startup from the corresponding media segment.
(14)
Information indicating that the Web Resource has been updated or revoked is recorded in the Item Information Entry,
The decryption apparatus according to any one of (1) to (13), wherein the access unit accesses the Web Resource based on the information recorded in the Item Information Entry.
(15)
The decryption device according to (14), wherein the information indicating that the Web Resource has been updated or revoked is information corresponding to “Last Modified” and “Expires” headers defined by HTTP (Hypertext Transfer Protocol).
(16)
The access unit accesses the Web Resource provided from another device on the Internet indicated by the Reference URL corresponding to the Item Information Entry, when the Web Resource is updated or expired. Decoding device.
(17)
The decryption apparatus according to (14), wherein the access unit replaces cache data of the Web Resource with a new file when there is an update or revocation of the Web Resource.
(18)
The decryption device
The Web Resource of the distribution content is distributed and arranged in a plurality of media segments, and the Item Information Entry stored in the MetaBox of the initialization segment used in the distribution content is referred to, and the identified target to be accessed A decryption method comprising: accessing the Web Resource stored in a media segment.
(19)
To the computer of the decryption device
The Web Resource of the distribution content is distributed and arranged in a plurality of media segments, and the Item Information Entry stored in the MetaBox of the initialization segment used in the distribution content is referred to, and the identified target to be accessed A program for executing decryption processing including accessing the Web Resource stored in a media segment.
(20)
A media segment processing unit that distributes and arranges web resources of distribution content into a plurality of media segments;
A segment file generation unit which stores Item Information Entry stored in the MetaBox of an initialization segment used in the distribution content in the media segment to be specified as an access target.
(21)
The delivery content is an MP4 file format, and
The encoding apparatus according to (20), wherein the segment file generation unit stores the Item Information Entry in an Information Box in the Meta Box.
(22)
The encoding apparatus according to (20) or (21), wherein the Item Information Entry includes information for indirectly referring to Item Information Entry in a MetaBox of a plurality of media segments used for the delivery content.
(23)
The Web resource so that the segment file generation unit can access the Item Information Entry stored in the MetaBox of the media segment to be referred to in the Item Information Entry of the reference source stored in the initialization segment. The coding apparatus according to any one of the above (20) to (22), which describes information indicating Earliest Presentation Time that corresponds to the media segment in which is placed.
(24)
The encoding apparatus according to (23), wherein the segment file generation unit records the information indicating the Earliest Presentation Time as a URL (Uniform Resource Locator) of a DataReferenceBox in the MetaBox of the reference source.
(25)
The media segment processing unit arranges each of the divided data in a predetermined number of media segments in which Earliest Presentation Time is continuous such that the Web Resource is divided substantially equally into the predetermined number of divided data. The encoding apparatus as described in (20).
(26)
The segment file generation unit is configured to associate the Earliest of each of the media segments in which a predetermined number of divided data pieces into which the Web Resource is divided is arranged in the URL for the Item Information Entry of the MetaBox referred to by the initialization segment. The encoding device according to (25), including range information of Presentation Time.
(27)
The segment file generation unit records the divided data in the Web Resource in each of the predetermined number of media segments when one of the Web Resources is divided into the predetermined number of divided data and arranged in the media segment. The encoding apparatus according to (26), which records the MetaBox indicating a byte offset and a byte size in the media segment in the range.
(28)
The segment file generation unit is configured to indicate, in the MetaBox, a byte offset of the divided data in the Web Resource and an entire byte of the Web Resource to indicate which part of the Web Resource divided into a predetermined number. The encoding device according to (27), which records the size.
(29)
When the Web Resource used when launching a Web Application and the Web Resource not used when launching are recorded and transmitted in separate Media Segments,
The segment file generation unit designates, in the Primary Item Box of the MetaBox, the Web Resource to be activated first, and enumerates, in the Meta Box, information indicating the other Web Resources necessary for activation. The encoding device as described in 2.).
(30)
The encoding apparatus according to (20), wherein the segment file generation unit records, in the Item Information Entry, information indicating that the Web Resource has been updated or revoked.
(31)
The information indicating that the Web Resource has been updated or revoked is the information corresponding to the "Last Modified" and "Expires" headers defined in HTTP (Hypertext Transfer Protocol). The encoding apparatus according to (30) above .
(32)
The Web Resource of the distribution content is distributed and arranged in a plurality of media segments, and the Item Information Entry stored in the MetaBox of the initialization segment used in the distribution content is referred to, and the identified target to be accessed A server apparatus for distributing the Web Resource stored in a media segment.
(33)
The delivery content is an MP4 file format, and
The server apparatus according to (32), wherein the Item Information Entry is stored in an Information Box in the Meta Box.
(34)
Delivering the Web Resource specified with reference to the Item Information Entry including information for indirectly referencing Item Information Entry in the MetaBox of a plurality of media segments used for the delivery content described in (32) above Server device.
(35)
In the Item Information Entry of the reference source stored in the initialization segment, the media on which the Web Resource is arranged so that the Item Information Entry stored in the MetaBox of the media segment of the reference destination can be accessed Information indicating the Earliest Presentation Time applicable to the segment is described,
The server apparatus according to (32), which delivers the Web Resource specified and accessed with reference to the Item Information Entry.
(36)
The information indicating the Earliest Presentation Time is recorded as a URL (Uniform Resource Locator) of the DataReferenceBox in the MetaBox of the reference source,
The server apparatus according to (35), which delivers the Web Resource accessed using the URL.
(37)
The server apparatus according to (36), which distributes the Web Resource that is identified and accessed based on the Earliest Presentation Time described in the URL and information related to the distribution content.
(38)
The web resource is divided substantially equally into a predetermined number of divided data, and each of the divided data is arranged in a predetermined number of the media segments in which Earliest Presentation Time is continuous. Server device.
(39)
In the URL for the Item Information Entry of the MetaBox referred to by the initialization segment, range information of the Earliest Presentation Time of each of the media segments in which a predetermined number of divided data pieces into which the Web Resource is divided is arranged Included,
The server apparatus according to (38), which distributes the Web Resource accessed to the media segment corresponding to the range information.
(40)
In the case where one Web Resource is divided into a predetermined number of divided data and arranged in the media segment, each of the predetermined number of media segments is within the range in which the divided data in the Web Resource is recorded. The MetaBox indicating the byte offset and byte size in the media segment is recorded,
The server apparatus according to (39), which delivers the Web Resource accessed using the MetaBox.
(41)
In the MetaBox, a byte offset of the divided data in the Web Resource and an entire byte size of the Web Resource are recorded to indicate which part of the Web Resource divided into a predetermined number is configured. The server apparatus according to (39).
(42)
When the Web Resource used when launching a Web Application and the Web Resource not used when launching are recorded and transmitted in separate Media Segments,
In the Primary Item Box of the MetaBox, the Web Resource to be activated first is specified, and in the Meta Box, information indicating the other Web Resources necessary at the time of activation is listed.
The server apparatus according to (32), which distributes the plurality of Web Resources required at the time of startup from the corresponding media segment.
(43)
Information indicating that the Web Resource has been updated or revoked is recorded in the Item Information Entry,
The server apparatus according to (42), which distributes the Web Resource accessed based on the information recorded in the Item Information Entry.
(44)
The server device according to (43), wherein the information indicating that the Web Resource has been updated or revoked is information corresponding to “Last Modified” and “Expires” headers defined by HTTP (Hypertext Transfer Protocol).

The present embodiment is not limited to the above-described embodiment, and various modifications can be made without departing from the scope of the present disclosure. Further, the effects described in the present specification are merely examples and are not limited, and other effects may be present.

DESCRIPTION OF SYMBOLS 11 Client terminal, 12 web engine, 13 A / V player, 14 image superimposition part, 15 audio hybrid part, 16 display, 17 speaker, 21 network delivery system, 22 network, 23 server apparatus, 24 delivery data generation apparatus, 31 decoding Part, 32 Media segment identification part, 33 Web Resource access part, 41 Encoding part, 42 Segment file generator, 43 Media segment processing part

Claims

The Web Resource of the distribution content is distributed and arranged in a plurality of media segments, and the Item Information Entry stored in the MetaBox of the initialization segment used in the distribution content is referred to, and the identified target to be accessed A decryption apparatus comprising: an access unit for accessing the Web Resource stored in a media segment.
The decoding device according to claim 1, wherein the Item Information Entry is stored in an Information Box in the Meta Box.
The decryption apparatus according to claim 1, wherein the Item Information Entry includes information for indirectly referring to Item Information Entry in the MetaBox of the plurality of media segments used for the delivery content.
The decoding apparatus according to claim 1, further comprising: a media segment identification unit that identifies the media segment in which the Web resource to be accessed is arranged.
The decoding device according to claim 4, wherein the access unit randomly accesses the Web Resource identified by the media segment identification unit.
In the Item Information Entry of the reference source stored in the initialization segment, the media on which the Web Resource is arranged so that the Item Information Entry stored in the MetaBox of the media segment of the reference destination can be accessed Information indicating the Earliest Presentation Time applicable to the segment is described,
The decryption apparatus according to claim 1, wherein the access unit accesses the Web resource using information indicating the Earliest Presentation Time.
The information indicating the Earliest Presentation Time is recorded as a URL (Uniform Resource Locator) of the DataReferenceBox in the MetaBox of the reference source,
The decryption apparatus according to claim 6, wherein the access unit accesses the Web Resource using the URL.
A media segment identification unit that identifies the media segment to be accessed based on the Earliest Presentation Time described in the URL and information on the delivery content,
The decryption apparatus according to claim 7, wherein the access unit accesses the Web Resource from a MetaBox stored in the media segment identified by the media segment identification unit.
The Web Resource is divided substantially equally into a predetermined number of divided data, and each of the divided data is arranged in a predetermined number of the media segments in which Earliest Presentation Time is continuous,
The decoding apparatus according to claim 1, wherein the access unit acquires the entire Web Resource by collecting and combining the divided data.
In the URL for the Item Information Entry of the MetaBox referred to by the initialization segment, range information of the Earliest Presentation Time of each of the media segments in which a predetermined number of divided data pieces into which the Web Resource is divided is arranged Included,
The decryption apparatus according to claim 9, wherein the access unit acquires the entire Web Resource by accessing the media segment corresponding to the range information and collecting and combining a predetermined number of the divided data.
In the case where one Web Resource is divided into a predetermined number of divided data and arranged in the media segment, each of the predetermined number of media segments is within the range in which the divided data in the Web Resource is recorded. The MetaBox indicating the byte offset and byte size in the media segment is recorded,
The decryption apparatus according to claim 10, wherein the access unit accesses the Web Resource using the MetaBox.
In the MetaBox, a byte offset of the divided data in the Web Resource and an entire byte size of the Web Resource are recorded to indicate which part of the Web Resource divided into a predetermined number is configured. The decoding device according to claim 11.
When the Web Resource used when launching a Web Application and the Web Resource not used when launching are recorded and transmitted in separate Media Segments,
In the Primary Item Box of the MetaBox, the Web Resource to be activated first is specified, and in the Meta Box, information indicating the other Web Resources necessary at the time of activation is listed.
The decryption apparatus according to claim 1, wherein the access unit activates the Web Application after acquiring all of the plurality of Web Resources required at startup from the corresponding media segment.
Information indicating that the Web Resource has been updated or revoked is recorded in the Item Information Entry,
The decryption apparatus according to claim 1, wherein the access unit accesses the Web Resource based on the information recorded in the Item Information Entry.
The decryption apparatus according to claim 14, wherein the information indicating that the Web Resource has been updated or revoked is information corresponding to “Last Modified” and “Expires” headers defined by HTTP (Hypertext Transfer Protocol).
15. The decryption according to claim 14, wherein the access unit accesses the Web Resource provided from another device on the Internet indicated by the Reference URL corresponding to the Item Information Entry when there is an update or revocation of the Web Resource. apparatus.
The decryption apparatus according to claim 14, wherein the access unit replaces the cache data of the Web Resource with a new file when there is an update or revocation of the Web Resource.
The decryption device
The Web Resource of the distribution content is distributed and arranged in a plurality of media segments, and the Item Information Entry stored in the MetaBox of the initialization segment used in the distribution content is referred to, and the identified target to be accessed A decryption method comprising: accessing the Web Resource stored in a media segment.
To the computer of the decryption device
The Web Resource of the distribution content is distributed and arranged in a plurality of media segments, and the Item Information Entry stored in the MetaBox of the initialization segment used in the distribution content is referred to, and the identified target to be accessed A program for executing decryption processing including accessing the Web Resource stored in a media segment.