JP7070432B2 - Information processing equipment, information recording media, information processing methods, and programs - Google Patents

Description

The present disclosure relates to information processing devices, information recording media, information processing methods, and programs. More specifically, an information processing device and information recording that input MMT (MPEG Media Transport) format data, which is being standardized as a future data transmission standard for broadcast waves, etc., and record it on media so that it can be played back. Media, information processing methods, and programs.

Currently, standardization is underway to realize data transmission of high-quality images such as broadcasting of 4K images and 8K images, and one of them is a data distribution method using the MMT (MPEG Media Transport) format. Is under consideration.

The MMT format is composed of coded data that constitutes content such as image (Video), audio (Audio), and subtitle (Subtitle), and control data, attribute data, and management information that are applied to content reception and playback processing. It defines a data transfer method (transport format) for transmitting data such as control information (SI: Signaling Information) via a broadcast wave or a network.

The MMT format is scheduled to be used for broadcasting next-generation contents such as 4K images and high dynamic range (HDR) images.

The MPEG-2 TS format is often used as a transmission format for current images (Video), audio (Audio), subtitles (Subtitles), etc., or as a data recording format for media.
Further, BDMV and BDAV standards (formats) are widely used as recording / playback application standards (formats) compatible with this MPEG-2 TS format.

BDMV and BDAV are application standards for data recording and playback mainly using BD (Blu-ray (registered trademark) Disc), but these standards are not limited to BD, but other standards such as flash memory and HD. It can also be applied to data recording / playback using media other than BD.
A data recording / reproduction processing configuration using a BD is described in, for example, Patent Document 1 (Japanese Unexamined Patent Publication No. 2011-023071).

BDMV is an application standard developed for BD-ROMs in which movie contents are recorded in advance, and is mainly widely used in non-rewritable BD-ROMs such as package contents.
On the other hand, BDAV is a standard developed mainly for the purpose of applying to data recording / playback processing using a rewritable BD-RE type disc, a BD-R type disc that can be recorded only once, and the like. BDAV is used, for example, for recording / reproducing a video taken by a user with a video camera or the like, or for recording / reproducing a television broadcast.

In order to record the distributed content according to the above-mentioned MMT format on an information recording medium (media) and perform the content reproduction processing from the media using a reproduction application compatible with the BDAV format, the data recording is performed according to this BDAV format. It is necessary to do.

Currently, discussions are underway on a configuration for expanding the BDAV format to record and play back MMT format data.
For example, when an information processing device such as a television receives distribution data according to the MMT format transmitted by a broadcasting station or the like and records the received data on a recording medium such as a BD, a flash memory, or an HD (hard disk), an image, Discussions are proceeding in the direction of recording audio, subtitle data, control information (SI), and other data on the media as a packet string of packets storing data according to the MMT format.

Specifically, discussions are proceeding in the direction of recording a packet sequence of an MMTP (MMT Protocol) packet or a TLV (Type Length Value) packet, which is a higher-level packet of an MMTP packet, on a medium.

Images, sounds, subtitles, and various control information (SI: Signaling Information), which are reproduction data, are stored in the MMTP packet and the TLV packet.

For example, MMTP packets and TLV packets containing contents such as images, sounds, and subtitles are recorded on recording media such as BD (Blu-ray (registered trademark) Disc), flash memory, and HD (hard disk), and the contents from the media are recorded. In order to perform reproduction using the reproduction application corresponding to the above-mentioned BDAV format, it is necessary to record data according to this BDAV format.

The BDAV format defines database files such as playlist files and clip information files as playback control information files, and BDAV-compatible playback applications refer to these playback control information files (database files) for data playback processing. Run.
Therefore, it is necessary to perform the reproduction processing of the MMT format data by using the reproduction control information recorded in these playlist files and clip information files.

However, database files such as playlist files and clip information files specified in the BDAV format are originally specified as recording files for playback control information corresponding to MPEG-2 TS format data.
Therefore, when reproducing MMT format data whose format is different from that of the MPEG-2 TS format, normal reproduction may not be possible if the reproduction control information recorded in the playlist file or clip information file specified in the current BDAV format is applied. There is sex.

In order to record MMT format data on a recording medium such as BD and enable content playback using a BDAV format compatible application, a playlist file compatible with MMT format data or a playlist file compatible with MMT format data is used when recording MMT format data on the media. It is necessary to generate a clip information file and record it on the media.
Further, when reproducing the MMT format data recorded on the media, it is necessary to reproduce using a playlist file or a clip information file corresponding to the MMT format data.
However, the current situation is that these processes have not been materialized at this time.

Japanese Unexamined Patent Publication No. 2011-023071

The present disclosure has been made in view of the above problems, for example, and the distribution data according to the MMT format is input, recorded on a recording medium such as BD, and the MMT format data is reproduced from the recording medium. It is an object of the present invention to provide an information processing device, an information recording medium, an information processing method, and a program that enable the above.

The first aspect of this disclosure is
It has a data processing unit that inputs MMT (MPEG Media Transport) format data and generates recorded data according to BDAV format or SPAV format, which is a data recording format for information recording media.
The data processing unit
A clip AV stream file consisting of a TLV packet string that stores MMT format data as playback data, and
It is in an information processing device that generates a reproduction control information file that records control information that enables acquisition of a specific TLV packet from the clip AV stream file.

Further, the second aspect of the present disclosure is
It has a data processing unit that executes the reproduction processing of the recorded data of the information recording medium.
The information recording medium is a BDAV format of a clip AV stream file composed of a TLV packet string storing MMT (MPEG Media Transport) format data and a playback control information file storing playback control information of the clip AV stream file. , Or an information recording medium recorded according to the SPAV format.
The data processing unit
In the data reproduction process using the clip AV stream file composed of the TLV packet sequence,
It is in an information processing apparatus that acquires reproduction target data from a TLV packet and executes reproduction control according to the recorded information of the reproduction control information file.

Further, the third aspect of the present disclosure is
A clip AV stream file composed of a TLV packet string containing MMT (MPEG Media Transport) format data, and
It has a playback control information file that stores the playback control information of the clip AV stream file as recorded data.
The playback control information file is
The IP data flow identification information for extracting the target packet from the TLV packet included in the clip AV stream file and the packet identifier are included.
Information having a data recording configuration that enables a reproduction device that reproduces stored data of the clip AV stream file to acquire reproduction target data from the TLV packet string by referring to the IP data flow identification information and the packet identifier. It is on the recording medium.

Further, the fourth aspect of the present disclosure is
It is an information processing method executed in an information processing device.
The information processing device is
It has a data processing unit that inputs MMT (MPEG Media Transport) format data and generates recorded data according to BDAV format or SPAV format, which is a data recording format for information recording media.
The data processing unit
A clip AV stream file consisting of a TLV packet string that stores MMT format data as playback data, and
It is an information processing method for generating a reproduction control information file which records control information which makes it possible to acquire a specific TLV packet from the clip AV stream file.

Further, the fifth aspect of the present disclosure is
It is an information processing method executed in an information processing device.
The information processing device is
It has a data processing unit that executes the reproduction processing of the recorded data of the information recording medium.
The information recording medium is a BDAV format of a clip AV stream file composed of a TLV packet string storing MMT (MPEG Media Transport) format data and a playback control information file storing playback control information of the clip AV stream file. , Or an information recording medium recorded according to the SPAV format.
The data processing unit
In the data reproduction process using the clip AV stream file composed of the TLV packet sequence,
It is an information processing method that acquires reproduction target data from a TLV packet and executes reproduction control according to the recorded information of the reproduction control information file.

Further, the sixth aspect of the present disclosure is
It is a program that executes information processing in an information processing device.
The information processing device is
It has a data processing unit that inputs MMT (MPEG Media Transport) format data and generates recorded data according to BDAV format or SPAV format, which is a data recording format for information recording media.
The program is installed in the data processing unit.
A clip AV stream file consisting of a TLV packet string that stores MMT format data as playback data, and
The program is for generating a reproduction control information file that records control information that enables acquisition of a specific TLV packet from the clip AV stream file.

Further, the seventh aspect of the present disclosure is
It is a program that executes information processing in an information processing device.
The information processing device is
It has a data processing unit that executes the reproduction processing of the recorded data of the information recording medium.
The information recording medium is a BDAV format of a clip AV stream file composed of a TLV packet string storing MMT (MPEG Media Transport) format data and a playback control information file storing playback control information of the clip AV stream file. , Or an information recording medium recorded according to the SPAV format.
The program is installed in the data processing unit.
In the data reproduction process using the clip AV stream file composed of the TLV packet sequence,
It is in a program that acquires reproduction target data from a TLV packet and executes reproduction control according to the recorded information of the reproduction control information file.

The program of the present disclosure is, for example, a program that can be provided by a storage medium or a communication medium provided in a computer-readable format to an information processing apparatus or a computer system capable of executing various program codes. By providing such a program in a computer-readable format, processing according to the program can be realized on an information processing apparatus or a computer system.

Still other objectives, features and advantages of the present disclosure will be clarified by more detailed description based on the examples of the present disclosure and the accompanying drawings described below. In the present specification, the system is a logical set configuration of a plurality of devices, and the devices of each configuration are not limited to those in the same housing.

According to the configuration of one embodiment of the present disclosure, a configuration is realized in which MMT format data is recorded on a medium as BDAV or SPAV format data and can be played back.
Specifically, for example, a stream file composed of a TLV packet string storing MMT format data and a playback control information file are generated and recorded on a medium. The IP data flow identification information and the packet identifier are recorded together in the reproduction control information file. As the IP data flow identification information, data consisting of a source IP address or the like, or a CID or the like recorded in a compressed IP header is used. The IP data flow identification information selects a specific IP data flow, and enables selection of the only packet for which a packet identifier is set from a group of packets belonging to the selected flow.
With this configuration, a configuration is realized in which MMT format data is recorded on a medium as BDAV or SPAV format data and can be played back.
It should be noted that the effects described in the present specification are merely exemplary and not limited, and may have additional effects.

It is a figure explaining the use configuration example of the information processing apparatus which executes the process of this disclosure. It is a figure explaining the MMT format. It is a figure explaining the image data storage configuration example according to the MMT format. It is a figure explaining the BDAV format. It is a figure explaining the example of the data reproduction processing according to the BDAV format. It is a figure explaining the MPEG-2TS format. It is a figure explaining the MMT format. It is a figure explaining the SPAV format. It is a figure explaining the processing example which records the received data from a broadcasting station or the like as an MMTP packet string which is MMT format data on an information recording medium (media). It is a figure explaining the processing example which records the received data from a broadcasting station or the like as a TLV packet string storing MMTP packet which is MMT format data on an information recording medium (media). It is a figure explaining the processing example in the case of recording MMT format data as BDAV format data. It is a figure explaining the data structure of a playlist file. It is a figure explaining EP map. It is a figure explaining EP map. It is a figure explaining EP map. It is a figure explaining the CPI type recording data of a playlist file. It is a figure explaining the data structure of the play item of a playlist file. It is a figure explaining the play item record data of a playlist file. It is a figure which shows the data structure (syntax) of the MMT package table (MPT). It is a figure explaining the specific example of the asset type (asset_type) recorded in the MMT package table (MPT). It is a figure which shows the data structure (syntax) of the MPU time stamp descriptor recorded in the MMT package table (MPT). It is a figure explaining the playlist mark which is a component of a playlist file. It is a figure explaining the recorded data of the playlist mark information. It is a figure which shows the data structure (syntax) of a clip information file. It is a figure which shows the data structure (syntax) of the clip information [ClipInfo ()] of a clip information file. It is a figure explaining the recording example of the application type recorded in the clip information [ClipInfo ()] of a clip information file. It is a figure explaining the recording example of the clip stream type recorded in the clip information [ClipInfo ()] of a clip information file. It is a figure which shows the data structure (syntax) of the sequence information [SequenceInfo ()] of a clip information file. It is a figure explaining the ATC and STC recorded in the sequence information [SequenceInfo ()] of a clip information file. It is a figure which shows the data structure (syntax) of the sequence information [SequenceInfo ()] of the clip information file when the reproduction target data is MMT format data. It is a figure which shows the data structure (syntax) of the program information [ProgramInfo ()] of a clip information file. It is a figure explaining the setting example of the IP data flow of the transmission packet from a transmission device, and the setting example of a packet identifier. It is a figure explaining the setting example of the IP data flow of the transmission packet from a transmission device, and the setting example of a packet identifier. It is a figure explaining the table included in the transmission packet from a transmission apparatus, and the example of the packet identification processing using a table. It is a figure which shows the data structure (syntax) of the MMT package table (MPT). It is a figure which shows the data structure (syntax) of the MMT general position information (MMT_general_location_info) of the MMT package table (MPT). It is a figure which shows the data structure (syntax) of the MMT package table (MPT). It is a figure which shows the data structure (syntax) of the MMT general position information (MMT_general_location_info) of the MMT package table (MPT). It is a figure which shows the data structure (syntax) of the program information [ProgramInfo ()] of a clip information file. It is a figure which shows the data structure (syntax) of the TLV header which is a header of a TLV packet. It is a figure which shows the data structure (syntax) of the IP header which is the header of an IP packet. It is a figure which shows the data structure (syntax) of the IP header which is the header of an IP packet. It is a figure which shows the data structure (syntax) of the compressed IP header of an IP packet. It is a figure which shows the data structure (syntax) of the compressed IP header of an IP packet. It is a figure which shows the data structure (syntax) of the program information [ProgramInfo ()] of a clip information file. It is a figure which shows the data structure (syntax) of the program information [ProgramInfo ()] of a clip information file. It is a figure which shows an example of the data structure (syntax) of a program list table (PLT) information, and MMT package table (MPT) information. It is a figure which shows an example of the data structure (syntax) of a program list table (PLT) information, and MMT package table (MPT) information. It is a figure which shows the data structure (syntax) of stream coding information [Stream coding Info] set in the program information recording area of a clip information file. It is a figure which shows the setting example of the coding type of the image stream and the audio stream specified in BDAV format. It is a figure explaining an example of stream coding information [Stream coding Info] recording data about HEVC image data. It is a figure explaining the data recording example of the video format (video_format) of a clip information file. It is a figure explaining the data recording example of the frame rate (frame rate) of a clip information file. It is a figure explaining the data recording example of the aspect ratio (aspect_ratio) of a clip information file. It is a figure explaining the data recording example of the audio information of a clip information file. It is a figure which shows the data structure (syntax) of the CPI information [CPI ()] of a clip information file. It is a figure explaining the data structure of the EP map recorded in the CPI information [CPI ()] of a clip information file. It is a figure explaining the data structure of the EP map recorded in the CPI information [CPI ()] of the clip information file corresponding to MMT format data. It is a figure explaining the data structure of the EP map recorded in the CPI information [CPI ()] of the clip information file corresponding to MMT format data. It is a figure explaining the data structure of the EP map recorded in the CPI information [CPI ()] of a clip information file. It is a figure explaining the correspondence example of the data recorded in an EP map, and the composition packet of a clip AV stream file. It is a figure explaining the data structure of the MMTP packet and the RAP flag. It is a figure explaining the configuration example of the information processing apparatus which executes the data recording process with respect to the information recording medium (media). It is a figure which shows the flowchart explaining the processing sequence of the data recording processing with respect to the information recording medium (media). It is a figure which shows the flowchart explaining the processing sequence of the data recording processing with respect to the information recording medium (media). It is a figure which shows the flowchart explaining the processing sequence of the data recording processing with respect to the information recording medium (media). It is a figure explaining the configuration example of the information processing apparatus which executes the data reproduction processing from an information recording medium (media). It is a figure which shows the flowchart explaining the processing sequence of the data reproduction processing from an information recording medium (media). It is a figure which shows the flowchart explaining the processing sequence of the data reproduction processing from an information recording medium (media). It is a figure explaining the hardware configuration example of the information processing apparatus applied to the processing of this disclosure.

Hereinafter, the details of the information processing apparatus, the information recording medium, the information processing method, and the program of the present disclosure will be described with reference to the drawings. The explanation will be given according to the following items.
1. 1. Configuration example of communication system 2. About MMT (MPEG Media Transport) format 3. BDAV format and SPAV format 4. 4. Processing when recording MMT format data according to BDAV format. About playlist files that support MMT format data 6. Clip information files compatible with MMT format data 6-1. Clip information recorded in the clip information file 6-2. Sequence information recorded in the clip information file 6-3. Program information recorded in the clip information file 6-3-1. About the processing example of recording the IP data flow identification information in the program information of the clip information file 6-3-2. About the processing example of recording PLT information and MPT information in the program information of the clip information file 6-3-3. Stream coding information recorded in the program information of the clip information file 6-4. About CPI information recorded in the clip information file 7. 8. Configuration and processing of information processing equipment that executes data recording processing for information recording media. 9. Configuration and processing of an information processing device that executes data reproduction processing from an information recording medium. About the configuration example of the information processing device 10. Summary of the structure of this disclosure

[1. Communication system configuration example]
First, an example of a communication system, which is an example of a usage configuration of an information processing apparatus that executes the process of the present disclosure, will be described with reference to FIG.
The information processing apparatus 30 shown in FIG. 1 is equipped with media such as a BD (Blu-ray (registered trademark) Disc), a flash memory, and a hard disk (HDD), and performs data recording processing on these mounted media and from the mounted media. Executes the data playback process of.

The data recorded on the media by the information processing device 30 is, for example, transmission content provided by a transmission device 20 such as a broadcasting station (broadcast server) 21 or a data distribution server 22. Specifically, it is a broadcast program or the like provided by a television station.
These transmitted contents are transmitted from the transmitting device 20 to the information processing device 30 via a broadcast wave or a network such as the Internet.

The information processing device 30 is, for example, a BD player 31, a television 32, a PC 33, a mobile terminal 34, etc. These information processing devices are, for example, a BD (Blu-ray (registered trademark) Disc) 41, an HDD (hard disk) 42. , Various media such as a flash memory 43 are attached, and data recording processing for these media and data reproduction processing from the media are executed.

Data transmission from the transmission device 20 to the information processing device 30 is executed according to the MMT (MPEG Media Transport) format.
The MMT format is a data transfer method (transition port format) for transmitting coded data, which is content composition data, such as image (Video), audio (Audio), and subtitle (Subtitle), via a broadcast wave or a network. It is specified.

The transmission device 20 encodes the content data, generates a data file containing the coded data and the metadata of the coded data, and stores the generated coded data in an MMTP (MMT Protocol) packet defined in the MMT. Transmit via broadcast wave or network.

The data provided by the transmission device 20 to the information processing device 30 is a control composed of reproduction target data such as images, sounds, and subtitles, as well as guidance information such as a program guide, notification information, and various management information such as control messages. It is composed of information (SI: Signaling Information).

[2. About MMT (MPEG Media Transport) format]
As described above, the data transmission from the transmission device 20 to the information processing device 30 is executed according to the MMT (MPEG Media Transport) format.
The MMT (MPEG Media Transport) format will be described with reference to FIG. 2 and the following.

FIG. 2 is a diagram showing a stack model in MMT format.
In the MMT stack model shown in FIG. 2, the bottom layer has a physical layer (PHY). The physical layer is divided into a broadcast (Broadcasting) layer that performs broadcasting-related processing and a broadband (Broadband) layer that performs network-based processing.
MMT enables processing using two communication networks, a broadcasting system and a network system.

As an upper layer of the physical layer (PHY), there is a TLV (Type Length Value) layer. The TLV is a format specification layer that defines a multiplexing method for IP packets. A plurality of IP packets are multiplexed and transmitted as TLV packets. The TLV-SI is a transmission layer of control information (SI) such as a control message according to the TLV format.

The control information (SI) is composed of setting information required for receiving and playing content (program) on the information processing apparatus 30 side, guidance information such as a program guide, notification information, control information, and management information. ..
The control information (SI) stored in the TLV packet for which processing is generated in the TLV layer is TLV-SI, and is mainly composed of control information related to reception processing.
The control information (SI) stored in the MMTP packet, which is a packet generated according to the MMT protocol (MMTP), is MMT-SI shown in the uppermost layer, and is mainly composed of control information related to reproduction control.

A UDP / IP layer is set on the TLV layer.
The UDP / IP layer can be divided into an IP layer and a UDP layer in detail, but is a layer that regulates transmission in which a UDP packet is stored in the payload of the IP packet.
An MMT layer and a File delivery method layer are set on the UDP / IP layer.
The setting is such that the case where the MMTP packet is stored in the IP packet and transmitted and the method where the data is transmitted as the IP packet by using the File delivery method, which is a data transmission method that does not use the MMTP packet, can be used together.

The following layers are set on the MMT layer.
Image (Video) data, which is coded image data according to HEVC (High Efficiency Video Coding), which is an image coding standard.
Audio data, which is coded audio data according to AAC (Advanced Audio Coding), which is an audio coding standard.
Subtitle data, which is coded subtitle data according to TTML (Timed Text Markup Language), which is a subtitle coding standard.
Control information (MMT-SI) transmitted using MMTP packets,
In addition, various applications described according to HTML5 (HyperText Markup Language 5),
Each of these data is stored in an MMTP packet and transmitted.

The control information (MMT-SI) is control information (signaling information) transmitted in an MMTP packet, such as setting information required for reproducing content (program) on the information processing apparatus 30 side, a program guide, and the like. It is composed of various management information such as guidance information, notification information, and control information.

The time information (NTP: Network Time Protocol) is absolute time information, which is directly stored in a UDP packet and transmitted.
Other data services (Data service) that distribute data, content download (Contentdownload, etc.) have a configuration that can be distributed by using a file distribution method (File delivery method) different from MMT.

As shown in FIG. 2, a control information (MMT-SI) or an application composed of images, sounds, subtitles, and various management information such as various notification information and control information is transmitted by an MMTP packet.

A specific configuration example of the MMTP packet will be described with reference to FIG.
FIG. 3 shows the following four types of data configuration examples.
(A) MPU (Media Presentation Unit)
(B) MMTP payrot (c) MMTP packet (d) TLV packet

(D) The TLV packet is a packet transmitted via a broadcast wave or a network, and each header information of a UDP header, an IP header, and a TLV header is set in the TLV packet. The TLV packet is set as an individual packet for each data type.

That is, one type of data is stored in the TLV payload of one TLV packet. Specifically, for example, an image (V), an audio (A), a subtitle (S), or a control information (SI) composed of various management information is individually stored.
Regarding the control information (SI), there are control information (MMT-SI) stored in the MMTP packet and control information (TLV-SI) transmitted in the TLV packet, which are stored in different individual TLV packets. ..

An example of the TLV payrot, which is the payload of the TLV packet, is the MMTP packet shown in FIG. 3 (c).
The MMTP packet shown in FIG. 3C is composed of an MMTP header and an MMTP payload.

One type of data is stored in the MMTP payload of one MMTP packet. Specifically, for example, an image (V), an audio (A), a subtitle (S), a control information (MMT-SI) stored in an MMTP packet, and any one of these types of data are individual MMTP packets. Stored in.

3 (a) and 3 (b) show the detailed structure of the image data stored in the MMTP payload of the MMTP packet shown in FIG. 3 (c).
FIG. 3B selects and shows only the MMTP packet whose MMTP payload is image data (V) among the MMTP packets shown in FIG. 3C.
The MMTP payload shown in FIG. 3B is composed of a header and a data unit.

As shown in FIG. 3A, the data unit stores image data and various parameters as described below.
AU Delimiter (Access Unit Delimiter)
SPS (Sequence Parameter Set)
PPS (Picture Parameter Set)
SEIs (Supplemental Enhanment Information)
These parameters are parameters used for image display.

The MPU (Media Presentation Unit) shown in FIG. 3A is one data processing unit of reproduction target data such as images, sounds, and subtitles in the MMT format. The example shown in FIG. 3A is an example of an MPU of image data, which is the same unit as GOP (Group of Pictures) as a so-called coding / decoding processing unit.

In this way, for example, the image data is divided into the parameters defined in the MMT format and the image configuration data as shown in FIG. 3A, stored in the MMTP payload shown in FIG. 3B, and shown in FIG. 3 (b). It is configured as the MMTP packet shown in c).
Further, the MMTP packet is set as the payload of the TLV packet shown in FIG. 3D, and the TLV packet is transmitted via a broadcast wave or a network.

For each data such as voice and subtitles and each data of MMT-SI, MMTP packets and TLV packets for each data type are set and transmitted.
The TLV-SI is stored in the TLV packet and transmitted without being stored in the MMTP packet.

[3. About BDAV format and SPAV format]
Next, BDAV, which is a recording data format for recording and playing back distributed content according to the above-mentioned MMT format on, for example, BD (Blu-ray (registered trademark) Disc), flash memory, or HD (hard disk or other media). The format and the SPAV format will be described with reference to FIG. 4 and below.

For example, when playing content such as images, sounds, and subtitles from media such as BD (Blu-ray (registered trademark) Disc), flash memory, and HD, playback control information for performing playback processing of these contents. And index information is required. Playback control information and index information are generally called database files.
These reproduction control information and index information differ depending on the reproduction application that executes the reproduction processing of the recorded data of the media.

As described above, there are BDMV and BDAV standards (data recording formats) as current recording / playback application standards (= data recording formats). These application standards have been established mainly as data recording / playback application standards using BD (Blu-ray (registered trademark) Disc).

BDMV and BDAV are application standards for data recording and playback mainly using BD, and are data recording formats (standards), but these standards are not limited to BD, and other than BD such as flash memory. It can also be applied to data recording and playback using media.
BDMV is an application standard developed for BD-ROMs in which movie contents are recorded in advance, and is mainly widely used in non-rewritable BD-ROMs such as package contents.
On the other hand, BDAV is a standard developed mainly for the purpose of applying to data recording / playback processing using a rewritable BD-RE type disc, a BD-R type disc that can be recorded only once, and the like. BDAV is used, for example, for recording / reproducing a video taken by a user with a video camera or the like, or for recording / reproducing a television broadcast.

In order to perform the content reproduction process from the medium in which the distribution content according to the above-mentioned MMT format is recorded by using the reproduction application corresponding to the BDAV format, it is necessary to perform the data recording according to this BDAV format.
As described above, the BDAV format defines playlist files, clip information files, etc. as playback control information recording files, and BDAV-compatible playback applications record the recording information of these playback control information files (database files). Use it to execute data playback processing.

FIG. 4 is a diagram showing an example of a directory structure of data recorded on the information recording medium (media) 40 according to the BDAV format.
As shown in FIG. 4, various management information, reproduction control information, and storage files for reproduction target data are set in the directory.

The management information file is composed of, for example, an info file (info), a menu file (menu), a mark file (mark), and the like shown in FIG. These mainly store title management information and the like to be shown to the user.
Also, as a playback control information file,
Playlist file (playlist),
Clip information file (clipinf)
For example, these files are recorded.
Further, a clip AV stream file (stream) is recorded as a reproduction data storage file.

The playlist file is a file that defines the playback order and the like of the contents according to the program information of the playback program designated by the title, and has, for example, the designated information of the clip information file in which the playback position information and the like are recorded.
The clip information file is a file specified by the playlist file, and has playback position information of the clip AV stream file and the like.

The clip AV stream file is a file that stores AV stream data to be played back and management information. The clip AV stream file is composed of packets for storing management information and data such as images, sounds, and subtitles to be played back.
The management information defined in the MPEG-2 TS format and recorded in the clip AV stream file includes, for example, PSI / SI (Program Special Information / Service Information).

The conventional broadcast data and network distribution data are MPEG-2 TS format data composed of TS (Transport Stream) packets, but the data including high-definition images such as 4K and 8K images in the future are described above. It is expected to be MMT format data composed of MMTP packets.

In FIG. 4, as a clip AV stream file (stream),
A stream file (nnnnnn.m2ts) composed of MPEG-2 TS format data composed of TS packets,
MMT format data (nnnnnn.mmtv) composed of MMTP packets,
These two types of stream files are shown.

In the directory example shown in FIG. 4, when the data received by the information processing apparatus 30 is MPEG-2 TS format data, it is recorded as it is on the media as MPEG-2 TS format data, and when the received data is MMT format data, it is recorded as it is. , This is an example of a directory in the case of setting to record on media as MMT format data.

It should be noted that discussions are proceeding in the direction of recording a clip AV stream file for recording MMT format data on a medium as a packet string of a packet containing data according to the MMT format.
Specifically, discussions are proceeding in the direction of recording as a packet sequence of an MMTP (MMT Protocol) packet or a TLV (Type Length Value) packet which is a higher-level packet of the MMTP packet.
This specific example will be described in detail later.

The management information file, playlist file, clip information file, and these data files are storage files for management information applied to the reproduction processing of images, sounds, subtitles, etc., which are reproduction data stored in the clip AV stream file. These are files that store playback control information, attribute information of playback data, and the like, and are called database files.

The sequence for reproducing the content recorded on the information recording medium is as follows.
(A) First, a specific title is specified from the management information file by the playback application.
(B) The playlist associated with the specified title is selected.
(C) According to the clip information specified in the selected playlist, the AV stream or the command as the actual content data is read, and the AV stream is played back or the command is executed.

FIG. 5 shows the following data recorded on the information recording medium (media) 40, that is,
Playlist file,
Clip information file,
Clip AV stream file,
It is a figure explaining the correspondence relation of these data.

An AV stream consisting of playback target data such as images, sounds, and subtitles, which are actual playback target data, is recorded as a clip AV stream (Clip AV Stream) file, and further, as management information and playback control information files of these AV streams. , A playlist (PlayList) file and a clip information (Clip Information) file are specified.

These multiple categories of files are as shown in FIG.
Playlist layer containing playlist (PlayList) files,
A clip layer consisting of a clip AV stream file and a clip information file,
It can be divided into these two layers.

One clip AV stream (Clip AV Stream) file is associated with one clip information (Clip Information) file, and these pairs are considered as one object, and these are collectively clipped or clipped. Call it a file.
Detailed information of the data included in the clip AV stream file, for example, management information such as an EP map recording I-picture position information of MPEG data is recorded in the clip information file.

The Clip AV Stream file is composed of TS packets when it is MPEG-2 TS format data.
Further, in the case of MMT format data, it is composed of MMTP packets.

The clip information (Clip Information) file is, for example, the data position of the byte string data of the clip AV stream file and the reproduction time position such as the reproduction start point when expanded on the time axis (entry point: EP). It stores management information for acquiring the playback start position of the stored data of the clip AV stream file such as the corresponding data.

The playlist has information indicating the access point corresponding to the reproduction start position and the reproduction end position of the clip (Clip) by a time stamp which is information on the time axis.
For example, it is possible to refer to the clip information file based on the time stamp indicating the playback time elapsed position from the start point of the content, and acquire the data read position of the clip AV stream file, that is, the address as the playback start point. Become.
The clip information file (Clip Information file) is used to find the address information from which the decoding of the stream in the clip AV stream file should be started from this time stamp.

As described above, the playlist (PlayList) file has the designated information of the reproduction section for the reproducible data included in the clip (= clip information file + clip AV stream file) layer.
One or more play items (PlayItem) are set in the playlist (PlayList) file, and each play item is a playback section for playable data included in the clip (= clip information file + clip AV stream file) layer. Has the designated information of.

As described above, the clip AV stream (Clip AV Stream) file storing the data to be reproduced is composed of TS packets in the case of the conventional MPEG-2 TS format data.
Further, in the case of high-definition image data such as 4K and 8K images whose use is expected to be expanded in the future, in the case of MMT format data, it is composed of MMTP packets.
The MMT format and the MPEG-2 TS format will be described with reference to FIGS. 6 and 7.

First, the MPEG-2 TS format will be described with reference to FIG.
The MPEG-2 TS format stores coded data and management information (PSI / SI), which are content composition data such as images (Video), audio (Audio), and subtitles (Subtile), in a recording medium (media), or broadcast waves. It is a format that defines a data storage format (container format) such as coded data when transmitting via a network.

The MPEG-2 TS format is a format standardized in ISO13818-1, and is used for, for example, data recording for BD (Blu-ray (registered trademark) Disc), digital broadcasting, and the like.

6 (a) to 6 (c) are diagrams showing the structure of MPEG-2 TS format data.
FIG. 6A shown at the bottom is a diagram showing the overall configuration of the MPEG-2 TS format data.
As shown in FIG. 6A, the MPEG-2 TS format data is composed of a plurality of elementary streams.
The elementary stream is a unit set as one unit of, for example, an image, an audio, a subtitle, and the like.

As shown in FIG. 2 (b), one elementary stream (Elementary stream) is composed of one or more PES (Packetized Elementary stream) packets.
Specifically, one elementary stream is composed of one or a plurality of PES packets having a payload type (Payload_type) = 0x0 and having the same packet identifier (Packet_id).

One PES packet is composed of one or more TS packets as shown in FIG. 6 (c).
Specifically, one PES packet is composed of one or a plurality of TS packets having a payload type (Payload_type) = 0x0 and having the same packet identifier (Packet_id).
Unlike the above-mentioned MMTP packet, the TS packet has a fixed length, and the packet size of one TS packet is fixed at 188 bytes.

Next, the MMT (MPEG Media Transport) format will be described with reference to FIG. 7.
Regarding the MMT format, FIG. 3 is referred to earlier, but the explanatory diagram of the MMT format shown in FIG. 7 is a diagram that clearly explains the correspondence with the MPEG-2 TS format described with reference to FIG. be.

As described above, the MMT format is a data transfer method for transmitting coded data, which is content composition data, such as an image (Video), audio (Audio), and subtitle (Subtitle), via a broadcast wave or a network. (Transport format) is specified.
FIG. 7 is a diagram illustrating an MMT format, which is a file format defined in ISO / IEC 23008.1.

7 (a) to 7 (c) show the structure of MMT format data.
FIG. 7A shown at the bottom is a diagram showing the overall configuration of MMT format data.
As shown in FIG. 7A, the MMT format data is composed of a plurality of media presentation units (MPU: Media presentation unit).
The MPU is a unit set as one unit of, for example, an image, sound, subtitles, and the like. For example, in the case of an image, 1MPU corresponds to 1GOP (Group of picture) which is one MPEG compressed image unit.

As shown in FIG. 7 (b), one MPU is composed of one or more media fragment units (MFU: Media Fragment unit).
Specifically, one MPU is composed of one or a plurality of MFUs having a payload type (Payload_type) = 0x0 (MPU) and having the same packet identifier (Packet_id).

One MFU is composed of one or more MMTP packets as shown in FIG. 7 (c).
Specifically, one MFU is composed of one or a plurality of MMTP packets having a payload type (Payload_type) = 0x0 (MPU) and having the same packet identifier (Packet_id).
The MMTP packet has a variable length and can be set to various packet sizes.
Each MMTP packet is composed of a header (MMTP header) for storing attribute information and the like and a payload (MMTP payload) for storing actual data and the like of a coded image.

There is a SPAV format as a format similar to the BDAV format. As described above, BDMV and BDAV are application standards for data recording / reproduction mainly using BD. On the other hand, the SPAV format is an application standard for data recording and reproduction mainly for hard disks.
However, both the BDAV format and the SPAV format are formats that can be used for recording and playback using various media such as BD, flash memory, and HD.

The SPAV format data can be recorded and reproduced by the same processing as the data recording / reproduction processing in the BDAV format. However, the file name setting of the SPAV format is partially different from that of the BDAV format.
FIG. 8 shows an example of a directory structure in the SPAV format.

In the directory of the SPAV format shown in FIG. 8, various management information, reproduction control information, and storage files of reproduction target data are set as in the BDAV format described above with reference to FIG.

The management information file is composed of, for example, an info file (INFO), a menu file (MENU), a mark file (MARK), and the like shown in FIG. These mainly store title management information and the like to be shown to the user.
Also, as a playback control information file,
Playlist file (PLAYLIST),
Clip information file (CLIPINF)
For example, these files are recorded.
Further, a clip AV stream file (STREAM) is recorded as a reproduction data storage file.

As shown in FIG. 8, the setting of the directory name of the SPAV format and the extension of each file is different from the BDAV format described with reference to FIG.
However, the data stored in each file and the role of each file are the same as in the BDAV format.

In the following description of the embodiment, an example of processing for recording and reproducing MMT format data as BDAV format data will be described, but in the following embodiment, processing for recording and reproducing MMT format data as SPAV format data will be described. It is also applicable to.

[4. Processing when recording MMT format data according to BDAV format]
Next, a process for recording MMT format data according to the BDAV format will be described.

As described above, the MMT format is a data distribution format used for 4K images and the like scheduled to be distributed by broadcasting stations and the like in the future, and is a format according to the protocol stack described with reference to FIG. be.
On the other hand, the BDAV format is a data recording format for media, and as described with reference to FIG. 4, a database file including a playback control information file such as a playlist file or a clip information file is defined.
The BDAV format is a data recording format and is compatible with the data recording / playback application standard. Data playback recorded on the media according to the BDAV format is performed by using a playback application compatible with the BDAV format. To.

Therefore, in order to record the distributed content according to the MMT format on the media and perform the content reproduction processing from the recorded media by using the reproduction application corresponding to the BDAV format, it is necessary to record the data according to the BDAV format. is necessary.

As mentioned above, discussions are currently underway on provisions for extending the BDAV format to make MMT format data recordable and playable.
For example, when an information processing device such as a television receives distribution data according to the MMT format transmitted by a broadcasting station or the like, and records the received data on a medium such as a BD, a flash memory, or an HD (hard disk). Regarding data such as image, audio, subtitle data, and management information (SI), discussions are proceeding in the direction of recording the data as it is as a packet string of a packet containing data according to the MMT format.

That is, the clip AV stream file set in the BDAV format shown in FIG. 4 or the SPAV format shown in FIG. 8 [02001. In mmtv, etc.], the packet sequence of the packet storing the data according to the MMT format is recorded.
A clip AV stream file containing MMT format data [012001. Regarding the playlist file and clip information file that are playback control information files corresponding to [mmtv, etc.], the recording device generates a playlist file and clip information file in which control information corresponding to MMT format data is set and records them on the media. It will be. This process will be described later.

Discussions are proceeding in the direction of recording a clip AV stream file containing MMT format data as a packet sequence of an MMTP (MMT Protocol) packet or a TLV (Type Length Value) packet which is a higher-level packet of the MMTP packet.

A specific recording configuration example of the clip AV stream file storing the MMT format data will be described with reference to FIGS. 9 and 10.
FIG. 9 is a diagram illustrating a processing example of recording an MMTP (MMT Protocol) packet string according to the MMT format on a recording medium such as a BD, a flash memory, or an HD (hard disk).

FIG. 9 shows the following three data.
(A) TLV packet string which is broadcast distribution data (B) One TLV packet processed as received / reproduced data (C) MMTP packet string proposed as a configuration of media recording data

(A) The TLV packet sequence, which is broadcast distribution data, is a sequence of TLV packets having the MMT (MPEG Media Transport) format described above with reference to FIG. 2.
This TLV packet sequence is transmitted from a transmission device 20 such as a broadcasting station.

(B) One TLV packet processed as received / reproduced data is one TLV packet received by an information processing apparatus 30 such as a television or a recorder and subjected to reproduction processing. The detailed configuration of one TLV packet constituting the TLV packet sequence shown in (A) is shown.
It is a TLV packet having an MMT (MPEG Media Transport) format described above with reference to FIG.

(C) The MMTP packet sequence shown as the structure of the media recording data is an MMTP packet sequence currently proposed as recording data for the media.
The MMTP packet recorded on the media is an MMTP packet which is a part of the configuration data of the TLV packet, as can be understood from the dotted line showing the correspondence with FIG. 9B, and is composed of the following elements. ..
(A) MMTP packet header (MMTP_packet_header)
(B) MMTP packet data (MMTP_packet_data) (= payload)

The MMTP packet data (MMTP_packet_data) (= payload) is composed of the following elements.
(B1) MMTP payload header (MMTP_payload_header)
(B2) MMTP payload data (MMTP_payload_data)

Currently, one configuration proposed as recording data for an information recording medium (media) is to take out only the MMTP packet, which is a component of the TLV packet, as shown in FIG. 9C, and record them side by side in a row. It is a configuration to do.

FIG. 10 is a diagram illustrating a processing example of recording a packet sequence of a higher-level TLV packet storing an MMTP packet instead of an MMTP (MMT Protocol) packet on a recording medium such as a BD, a flash memory, or an HD (hard disk). Is.

Similar to FIG. 9, FIG. 10 shows the following three data.
(A) TLV packet string which is broadcast distribution data (B) One TLV packet processed as received / reproduced data (C) TLV packet string proposed as a configuration of media recording data

(A) and (B) are the same data as described with reference to FIG.
(C) The TLV packet sequence shown as the structure of the data for media recording is another example of the TLV packet sequence currently proposed as recording data for the media.
The TLV packet recorded on the media is a TLV packet including an MMTP packet, as can be understood from the dotted line showing the correspondence with FIG. 10B, and is composed of the following elements.
(A) TLV packet header (TLV_header)
(B) TLV packet data (TLV_data) (= payload)

As described above, at present, as a recording mode of MMT format data for media such as BD,
The packet sequence of the MMTP (MMT Protocol) packet described with reference to FIG. 9, or
Packet sequence of TLV (Type Length Value) packets described with reference to FIG.
Discussions are proceeding in the direction of recording as one of these packet strings.

When the MMT format data is recorded on the media with the settings shown in FIG. 9 or 10 and the reproduction process of the MMT format data is performed by using the reproduction application corresponding to the BDAV format, the reproduction control information file corresponding to the BDAV format is used. That is, the playback is performed using the playlist file and the clip information file.
The BDAV format is a data recording format and also supports a data recording / playback application standard, and playback of data recorded on a medium according to the BDAV format is executed using a playback application compatible with the BDAV format.

The BDAV format defines database files specific to the BDAV format, such as playlist files and clip information files, which are playback control information files, and BDAV-compatible playback applications record information from these playback control information files (database files). Use it to execute data playback processing.

As described above, the database files such as the playlist file and the clip information file specified in the BDAV format are originally defined as files that can be generated based on the distribution data in the MPEG-2 TS format.
Therefore, even if the distribution data according to the MMT format, which is different from the MPEG-2 TS format, is recorded as it is in the playlist file or clip information file specified in the current BDAV format, the current BDAV compatible playback application cannot be used. May be.

In order to record MMT format data on media and play back content using BDAV format compatible apps, playlist files and clips compatible with MMT format data are recorded when recording MMT format data on the media. It is necessary to generate an information file and record it on the media.
Further, when reproducing the MMT format data recorded on the media, it is necessary to reproduce using a playlist file or a clip information file corresponding to the MMT format data.

Specifically, as shown in FIG. 11, a clip information file (nnnnnn.clpi) 72 corresponding to the MMT format data storage clip AV stream file 71 and a playlist file (nnnnnn.rpls) 73 are generated to generate media (nnnnn.rpls). BD, flash memory, HDD, etc.) must be recorded and used for playback.

When playing back the MMT format data storage clip AV stream file 71 recorded on the media, the clip information file (nnnnnn.clpi) 72 corresponding to the MMT format data storage clip AV stream file 71 and the playlist file (nnnnnn. The reproduction process can be performed using rpls) 73.

However, as described above, the data distributed according to the MMT format, which is the distribution data of the broadcasting station, is not configured to include all the recording data of the playlist file and the clip information file specified in the BDAV format.
Further, the MMT format data storage clip AV stream file 71 has a data format different from that of the MPEG-2 TS format data, and is a playlist file having the same format as the MPEG-2 TS format data compatible playlist file or clip information file. Even if the clip information file is used, there is a problem that the correct playback process cannot be executed.

Therefore, in order to record this MMT format data on a medium and play back the content using the BDAV format compatible application, it is possible to control the playback of the MMT format data storage clip AV stream file 71, which is unique to the MMT format data. It is necessary to generate a playlist file or clip information file with the data format of and record it on the media.
Hereinafter, this specific process will be described.

As described above with reference to FIGS. 9 and 10, currently, as a recording mode of MMT format data for a medium such as BD, that is, as an MMT format data storage clip AV stream file 71 shown in FIG.
Packet sequence of MMTP (MMT Protocol) packets, or
Packet sequence of TLV (Type Length Value) packets,
Discussions are proceeding in the direction of recording as one of these packet strings.

In the following, the MMT format compatible playlist file and clip information file when the MMT format data storage clip AV stream file 71 is recorded as a packet string of a TLV (Type Length Value) packet described with reference to FIG. A specific configuration example will be described.

[5. About playlist files that support MMT format data]
First, a playlist file corresponding to MMT format data will be described with reference to FIGS. 12 and below.

As described above, the playlist file records information about the data to be played by applying the playlist. Specifically, it has, for example, information about a play item applied to a content reproduction process, and designated information of a clip information file in which reproduction position information and the like are recorded.

FIG. 12 is a diagram showing a data structure (syntax) of [PlayList] recorded in one playlist (PlayList) file.
In addition to the data structure (Syntax), the number of bits (No. of bits) and the data notation (Mnemonic) are shown.
In addition, "uimsbf" in the data notation means "unsigned integer most significant bit first" notation.
“Bslbf” means “a bit string, the left bit is the head (bit string, left bit first)”.

The main recorded data of [PlayList] shown in FIG. 12 will be described.
The length indicates the number of bytes from immediately after this length field to the end of the playlist file configuration data.

The PL_CPI type (PL_CPI_type) 101 is information indicating the CPI type in the clip information file referred to by the play item (PlayItem) specified in the playlist file.

The number of play items (number_of_PlayItems) 102 indicates the number of play items (PlayItems) specified in this playlist file.
The number of sub play items (number_of_SubPlayItems) 103 indicates the number of play items (PlayItems) specified in this playlist file.
In the play item information (PlayItem ()) 104, detailed information of each play item and sub play item is recorded.

As described above, the PL_CPI type (PL_CPI_type) 101 is information indicating the CPI type in the clip information file referred to by the play item (PlayItem) specified in the playlist file.
The CPI (Characteristic Point Information) is recorded data of a clip information file, and is, for example, data for acquiring a data address of a reproduction start point at which random access reproduction can be started.

As the CPI defined in the BDAV format, for example, there are EP maps (EP_map) and maps of different types of TU maps (TU_map).
Each of these maps is correspondence data between, for example, playback time information (PTS: Presence Timestamp) which is a random access point and a source packet number (SPN: Source Packet Number) which is a packet identifier of the packet at that position. , Map information that can be used to acquire the packet that stores the playback data of the random access point.

Both the EP map and the TU map are map data that record random access point information, but the EP map is map data that records more detailed random access point information, and the TU map is rougher than the EP map. Map data that records random access point information.
The BDAV format defines two types of maps, an EP map and a TU map, but the TU map is rarely used, and only the EP map is currently used.
EP_map and TU_map have address information for finding the location of the entry point (EP) in the AV stream where decoding should be started.

The EP map will be described with reference to FIGS. 13 and below.
As described above with reference to FIG. 5, the playlist has information indicating the access point corresponding to the playback start position and the playback end position of the clip by a time stamp which is information on the time axis. ..
The clip information file (Clip Information file) is used to find the address information from which the decoding of the stream in the clip AV stream file should be started from this time stamp.

Further, the clip information file (Clip Information file) has an EP map (EP_map) shown in FIG.
The EP map records access point information corresponding to a playback start position and a playback end position in which random playback can be started in the playback data stored in the clip AV stream file.
That is, in the EP map, the correspondence data between the time stamp expressing the reproduction start position on the time axis and the address information for acquiring the packet corresponding to the packet position information is recorded.

specifically,
(A) A time stamp (PTS: Presence Timestamp) expressing the access point on the time axis, and
(B) Source packet number (SPN: Source Packet Number) corresponding to the address indicating the packet position in the clip AV stream of the access point,
It has these correspondence information.

By referring to the EP map having such correspondence information, the corresponding address (SPN) is acquired based on the time stamp, and according to the address (SPN), for example, the decoding start point which is the playback start position in the AV stream, etc. Can be found.

FIG. 14 is a diagram illustrating a specific configuration and a usage example of the EP map (EP_map). In the clip AV stream (Clip AV stream) shown in FIG. 14 (A), a video stream composed of a source packet identified by a packet identifier: PID is multiplexed. The video stream is distinguished for each source packet by the PID contained in the header of the transport packet in the source packet.

The source packet of the video stream has an IPB picture constituting the MPEG data, that is, an I (Intra) picture, a P (Predictive) picture, and a B (Bidirectionalary Predictive) picture. The I-picture is picture data that can be decoded independently, and the other P-pictures and B-pictures need to refer to the previous and next I-pictures when decoding. For example, the reproduction start point by random access is set to the packet position having the I picture that can be independently decoded.

The EP map holds the position information of the I picture as the reproduction start point position information that can be randomly accessed as the corresponding data of the above-mentioned PTS and SPN. That is,
(A) A time stamp (PTS: Presence Timestamp) expressing the access point on the time axis, and
(B) Source packet number (SPN: Source Packet Number) corresponding to the address indicating the packet position in the clip AV stream of the access point,
These are the corresponding information.

By referring to the EP map set in this way, the location of the I picture, which is the playback start position that can be randomly accessed, can be obtained. The EP map (EP_map) is data included in the clip information file.

Detection of the I picture position based on the EP map will be described with reference to FIG. FIG. 14 (A) shows a clip AV stream, and each rectangle shows a 192 byte source packet.

In FIG. 14A, the source packet including the first byte of the I (Intra) picture is shown by a shaded square. White squares without diagonal lines indicate source packets that contain data that does not become a random access point, and source packets that contain data from other streams.

For example, the source packet of the source packet number X1 including the first byte of the randomly accessible I picture of the video stream distinguished by PID = x is placed at the position of PTS = pts (x1) on the time axis of the clip AV stream. Will be done. Similarly, the source packet containing the first byte of the I picture that can be randomly accessed next is regarded as the source packet of the source packet number X2, and is arranged at the position of PTS = pts (x2).

As shown in FIG. 14B, the source packet is configured by adding a 4-byte header (TP_extra_header) to a 188-byte transport packet. The transport packet part includes a header part (TP header) and a payload part.

The SPN_EP_start, which is the registration data of the EP map shown in FIG. 14 (C2), is the source packet number (SPN) of the source packet including the first byte of the access unit (Access Unit) including the I picture starting from the sequence header (SQH). Represents.
The series of numbers set for all the packets in the clip AV stream file is the source packet number (SPN). In the clip AV stream file, the source packet number of the first source packet is zero, the source packet number of the next packet is 1, and thereafter, the source packet number is incremented by 1 for each next packet.

As shown in FIG. 14 (C2), the EP map (EP_map) is
Stream PID (Stream_PID),
Number of EP entries (number_of_EP_entries),
Presentation Timestamp EP Start (PTS_EP_start), and
Source packet number EP start (SPN_EP_start),
We are recording these data.

The stream PID (Stream_PID) is a packet identifier (PID) of a transport packet that transmits a video stream.
The number of EP entries (number_of_EP_entries) is the number of entries of the pair of PTS_EP_start and SPN_EP_start included in EP_map.

Presentation Timestamp EP Start (PTS_EP_start) represents a PTS (Presentation Timestamp) of Access Unit starting with a randomly accessible I-picture.
The source packet number EP start (SPN_EP_start) represents a source packet number (SPN: Source Packet Number) including the first byte of the access unit (Access Unit) referred to by the value of PTS_EP_start.

The value of the PID (packet identifier) of the video stream is stored in the stream_PID, and EP_map (), which is table information showing the correspondence between PTS_EP_start and SPN_EP_start, is generated.
For example, in the EP map of a video stream with PID = x,
PTS = pts (x1) and source packet number (SPN) X1,
PTS = pts (x2) and source packet number (SPN) X2,
...,
PTS = pts (xk) and source packet number (SPN) Xk,
A table consisting of the corresponding data of these PTS and SPN is described.
An EP map (EP_map) containing the above table is stored in a clip information file corresponding to one clip AV stream.

An EP map (EP_map) having such data is referred to for specifying a decoding start position when performing random access, for example.
A method of calculating the address information at which the decoding of the stream should be started in the clip AV stream file by using EP_map when the playback is started from the time x on the time axis in the clip will be described with reference to FIG. ..

As shown in FIG. 15, when the playlist (PlayList) has information that specifies the start of playback from the time x on the time axis in the clip, the time stamp [PTS_EP_start [m] that is smaller than x and has the closest value. ] Is specified.
Based on the time stamp [PTS_EP_start [m]] specified according to this playlist information, the source packet number [SPN_EP_start [m] corresponding to the time stamp [PTS_EP_start [m]] is referred to in the clip information file. ]] Is specified.

In this way, using the EP map, the SPN, that is, [SPN_EP_start [m]], which is the packet position information corresponding to the PTS, is acquired from the PTS, which is the playback time information determined according to the playlist information.
This packet position [SPN_EP_start [m]] can be acquired as the playback start point in the clip AV stream file, that is, the address information at which decoding should be started, and the decoding process can be performed for reproduction.

The usage example of the EP map described with reference to FIGS. 13 to 15 is an example of packet acquisition processing corresponding to a random access point using MPEG-2 TS format data. In the MPEG-2 TS format data, in this way, from the PTS which is the reproduction time information determined according to the playlist information by using the EP map, the SPN which is the packet position information corresponding to the PTS, that is, [SPN_EP_start [SPN_EP_start [ m]] is acquired.

However, since the MMT format data has a format different from that of the MPEG-2 TS format data, it is not possible to perform the same processing as the MPEG-2 TS format data to acquire a random access point-compatible packet.
That is, when the reproduction target data is MMT format data, it is necessary to perform data processing corresponding to MMT format data different from the above-mentioned processing.

The EP map is specified in the clip information file, and it is necessary to record the EP map corresponding to the MMT format data in the clip information file corresponding to the MMT format data in order to execute the random access point acquisition process corresponding to the MMT format data. be.
That is, it is necessary to record the EP map corresponding to the MMT format data in the clip information file (nnnnnn.clpi) 72 corresponding to the MMT format data storage clip AV stream file 71 shown in FIG. A specific example of this will be described later.

In this way, the EP map corresponding to the MPEG-2 TS format data and the EP map corresponding to the MMT format data are different data.
As described with reference to FIG. 12, the PL_CPI type (PL_CPI_type) recorded in the playlist file shown in FIG. 12 is in the clip information file referred to by the play item (PlayItem) specified in the playlist file. Information indicating the CPI type.

The CPI (Characteristic Point Information) is recorded data of a clip information file, and is an area for recording data indicating a type of EP map or TU map for acquiring a data address of a playback start point (random access point).

In the conventional PL_CPI type (PL_CPI_type), identification information of an EP map or a TU map corresponding to MPEG-2 TS format data is recorded.
However, the EP map corresponding to the MMT format data is a map different from the EP map corresponding to the conventional MPEG-2 TS format data.
Therefore, it is necessary to set an identifier that distinguishes the PL_CPI type (PL_CPI_type) of the playlist file as well.

FIG. 16 shows the following CPI type recorded data.
(1) Conventional CPI type recording data (only MPEG-2 TS compatible data is recorded)
(2) New CPI type recording data (records MPEG-2TS compatible data and MMT compatible data)

The data shown in "(1) Conventional CPI type recording data (recording only MPEG-2 TS compatible data)" in FIG. 16 is data defined as the PL_CPI type (PL_CPI_type) of the conventional playlist file.
PL_CPI type (PL_CPI_type) = 1 means that the CPI type in the clip information file referred to by the play item (PlayItem) specified in this playlist file is an MPEG-2 TS compatible EP map.
PL_CPI type (PL_CPI_type) = 2 means that the CPI type in the clip information file referred to by the play item (PlayItem) specified in this playlist file is an MPEG-2 TS compatible TU map.

As described above, the conventional CPI type recording data records only the MPEG-2 TS compatible data.
“(2) New CPI type recording data (recording MPEG-2 TS compatible data and MMT compatible data)” in FIG. 16 is further added to the above settings.
PL_CPI type (PL_CPI_type) = 3
The configuration is such that the setting of this bit value = 3 is added.

PL_CPI type (PL_CPI_type) = 3 means that the CPI type in the clip information file referred to by the play item (PlayItem) specified in this playlist file is an MMT-compatible EP map.
In this way, three types of definitions of PL_CPI type (PL_CPI_type) = 1 to 3 are possible, and the three CPI types can be identified.

Next, the details (syntax) of the play item information (PlayItem ()) 104 recorded in the [PlayList] described above with reference to FIG. 12 will be described with reference to FIGS. 17 and below.
As described above, the play item information (PlayItem ()) 104 records detailed information of each play item and sub play item.

FIG. 17 is a diagram showing a data structure (syntax) of play item information (PlayItem ()) 104.
In the clip information file name (Clip_Information_file_name) 111, the file name of the clip information file applied to the reproduction process using this play item is recorded.

The reference STC identifier (ref_to_STC_id) 112 indicates the STC identifier of the STC (system time clock) continuous section to be referred to by this play item.
The STC (system time clock) is a reference clock at the time of AV stream reproduction, and one STC is used in the continuous reproduction section. For example, one STC is used in the continuous reproduction section in which one play item is reproduced, and different STCs are referred to by switching the play items.
In the reference STC identifier (ref_to_STC_id) 112, information that specifies the STC (system time clock) to be referred to by this play item is recorded.

The start time (IN_time) 113 is a recording area for the playback start time of the play item.
The end time (OUT_time) 114 is a recording area for the playback end time of the play item.
These start time and end time information are the difference time information (45 KHzh) from the start time of the STC corresponding to the play item specified by the reference STC identifier (ref_to_STC_id) 112 when the conventional MPEG-2 TS format data is to be played back. Clock) is recorded.
The 45 KHz clock is a general clock used for recording / reproducing MPEG-2 TS format data.

However, when the playback target data is MMT format data, unlike the MPEG-2TS format data, the playback target data (MMT format data) corresponding to the play item is not associated with an individual STC. ..
Therefore, the MMT format data is recorded in the play item information (PlayItem ()) of the playlist to be reproduced.
Start time (IN_time) 113 and
The end time (OUT_time) 114 is
It is necessary to make the time information unique to the MMT format data.
An example of this modification will be described with reference to FIG.

FIG. 18 shows the following data example.
(1) Conventional play item information recording data (MPEG-2 TS compatible playlist)
(2) New play item information record data (MMT compatible playlist)

In the "(1) conventional play item information recording data (MPEG-2 TS compatible playlist)" shown in FIG. 18 (1), when the playback target data is MPEG-2 TS format data, the play item information (PlayItem ()) The recorded data of the start time (IN_time) and the end time (OUT_time) recorded in is shown.

The start time (IN_time) is the playback start time information of the play item (PlayItem) playback start point, and as described above, the STC [system time clock (45 KHz clock)] applied to the playback process using this play item. ) Record the elapsed time information from the starting point. The STC is an STC identified by a reference STC identifier (ref_to_STC_id) 112 described with reference to FIG.

Further, the end time (OUT_time) is the reproduction end time information of the play item (PlayItem) reproduction end point, and as described above, the STC [system time clock (45 KHz clock) applied to the reproduction process using this play item). )]) Record the elapsed time information from the starting point. The STC is an STC identified by a reference STC identifier (ref_to_STC_id) 112 described with reference to FIG.

The "(2) new play item information recording data (MMT compatible playlist)" shown in FIG. 18 (2) is recorded in the play item information (PlayItem ()) when the playback target data is MMT format data. The recorded data of the start time (IN_time) and the end time (OUT_time) are shown.

The start time (IN_time) is the reproduction start time information of the play item (PlayItem) reproduction start point. When the data to be reproduced is MMT format data, time information according to NTP (Network Time Protocol) is recorded.
The end time (OUT_time) is the reproduction end time information of the play item (PlayItem) reproduction end point. When the data to be reproduced is MMT format data, time information according to NTP (Network Time Protocol) is recorded.

The time information according to the NTP (Network Time Protocol) is transmitted together with the MMT format data including the broadcast contents transmitted by the transmission device 20 such as the broadcast server (broadcast station) 21 shown in FIG. 1, for example.
The information processing device 30 such as the television (TV) 32 acquires time information according to NTP (Network Time Protocol) transmitted by the transmitting device 20 and records it in a playlist.

For example, the transmission device 20 transmits the reproduction time information of the MPU (Media Presentation Unit) unit, which is one data processing unit in the MMT format described above with reference to FIG. 3, for the time according to the NTP (Network Time Protocol). The control information recorded as information is transmitted together with the playback target data (program content).
A specific example will be described with reference to FIGS. 19 and below.

For example, the information processing device 30 that receives distribution content (program) from a transmission device 20 such as a broadcasting server (broadcasting station) 21 shown in FIG. 1 in MMT format data and records the received content on an information recording medium (media). It is necessary to extract various information from the received data to generate a playlist file and a clip information file.

As described above with reference to FIG. 2 and others, the MMT format data includes control information required for receiving and playing back content (program) on the information processing apparatus 30 side, and guidance information such as a program guide. It includes control information (signaling information) composed of information processing information, notification information, management information, and the like.
The control information (signaling information) defined in the MMT format includes signaling information (MMT-SI) transmitted in an MMTP packet and signaling information (TLV-SI) transmitted in a TLV packet.

The information processing apparatus 30 that receives MMT format data and records the received data on a medium extracts various information from signaling information such as TLV-SI and MMT-SI included in the MMT format, and extracts various information from the playlist file. And generate a clip information file.

One of the signaling information (MMT-SI) transmitted by the MMTP packet is the MMT package table (MPT: MMT Packet Table). The MMT package table (MPT) is a table in which data attribute information (asset descriptor) is recorded in detail for each data type (asset type) such as image, sound, subtitle, and the like.
The packet ID of the MMT package table (MPT: MMT Packet Table) is stored in the MMTP packet of the packet ID = 0x0000, and the information processing apparatus stores the stored packet of the MMT package table (MPT) based on the packet ID. It can be determined.

The configuration of the MMT package table (MPT: MMT Package Table) will be described with reference to FIG.

FIG. 19 is a diagram showing a data structure (syntax) of the MMT package table (MPT).
As described above, the MMT package table (MPT: MMT Package Table) specified in the MMT format is data attribute information (asset descriptor) for each data type (asset type) such as image, sound, subtitle, etc. There is a table that records in detail.

The MMT Package Table (MPT) contains, as shown in FIG.
Asset type (asset_type)
Asset descriptor (asset_descriptors_byte)
These data recording areas are included.

The asset type (asset_type) is an area for recording identifiers for each data type such as images, sounds, and subtitles. An asset is a unit of data processing having a common attribute, and images, sounds, subtitles, etc. are set as different assets.
FIG. 20 shows a specific example of the asset type (asset_type) recorded in the MMT package table (MPT).

As shown in FIG. 20, the asset type (asset_type) recorded in the MPT includes, for example, the following types.
hvc1: HEVC image mp4a: Audio stpp: Subtitles, etc. app: Application In the MPT asset type (asset_type) recording field shown in FIG. 19, for example, any of the above type information is recorded.

Shown at the bottom of the MPT in FIG.
Asset descriptor (asset_descriptors_byte)
In this field, various attribute information according to each asset type (for example, image, sound, subtitle) and these data types is recorded.

Reproduction time information such as images and sounds is included in one of the information recorded as this asset descriptor (asset_descriptors_byte).
The reproduction time information is recorded as time information according to NTP (Network Time Protocol).

FIG. 21 shows a data structure (syntax) of an MPU time stamp descriptor in which playback time information (time stamp) for each MPU recorded as an asset descriptor (asset_descriptors_byte) in the MMT package table (MPT) is recorded.

The MPU is an MPU (Media Presentation Unit) shown in FIG. 3A, as described above with reference to FIG. 3, and is one data processing unit in the MMT format. The example shown in FIG. 3A is an example of an MPU of image data, which is the same unit as GOP (Group of Pictures) as a so-called coding / decoding processing unit.

The MPU time stamp descriptor recorded in the MMT package table (MPT) corresponds to the reproduction time information in MPU units.
As shown in FIG. 21, the following data are recorded in the MPU time stamp descriptor.
MPU sequence number (MPU_sequenc_number)
MPU playback time (MPU_presentation_time)

The MPU identifier is recorded in the MPU sequence number (MPU_sequenc_number).
In the MPU reproduction time (MPU_presentation_time), the reproduction time (presentation time) of the MPU is recorded as time information according to NTP (Network Time Protocol).
The NTP time (NTP time stamp) is, for example, absolute time information of 64-bit data, that is, absolute time information indicating an elapsed time from a predetermined reference time. The upper 32 bits indicate time information of 1 second or more (elapsed time information), and the lower 32 bits indicate time information of 1 second or less (elapsed time information).
It is also possible to set the whole as 32 bits and use short-format NTP time information in which the upper 16 bits indicate the time information of 1 second or more and the lower 16 bits indicate the time information of 1 second or less.

As described above, in the MMT package table (MPT), the MPU time stamp, which is the reproduction time information (time stamp) of the MPU unit, is recorded as the asset descriptor (asset_descriptors_byte).

The transmission device 20 shown in FIG. 1 records the reproduction time information of the MPU (Media Presentation Unit) unit, which is one data processing unit in the MMT format, in the MMT package table (MPT) as NTP time information, and provides information on a television or the like. It is transmitted to the processing device 30.
The information processing apparatus 30 acquires this time information and records it in a playlist.

That is, when the data to be recorded as a clip AV stream file on the information recording medium (media) is MMT format data, the information processing apparatus 30 acquires the playback control information file, the playlist file, from the MMT package table (MPT). Record the NTP time information.

As described above with reference to FIG. 18 (2), the information processing apparatus 30 records a playlist file when the playback target data to be recorded as a clip AV stream file on the information recording medium (media) is MMT format data. As the start time (IN_time) and end time (OUT_time) of the play item information (PlayItem ()), time information according to NTP (network time protocol) is recorded.

Next, with reference to FIG. 22, a playlist mark (PlayListMark), which is another element recorded in the playlist file, will be described.
First, Mark will be described. Marks are data that can be recorded in playlist files and clip information files, for example, as chapter delimiters for image data stored in clip AV stream files, scene change points, bookmarks, highlights, and time specification information for characteristic scenes. be.
The recording of the mark on the playlist file and the clip information file is performed by the recording process of the time stamp indicating the time of the mark.

FIG. 22 is a diagram showing a data structure (syntax) of a playlist mark (PlayListMark) which is an element of a playlist file.
The playlist mark number (number_of_PlayList_marks) 121 indicates the number of marks stored in the playlist mark (PlayListMark).
The mark type (mark_type) 122 is a field indicating the type of the mark. For example, information indicating which type of mark each mark is, such as a representative image position of a playlist, a chapter start position, a chapter end position, a scene change position, or an edit position, is recorded.

The mark time stamp (mark_time_stamp) 123 is a field for recording a time stamp indicating a point at which the mark is set.
The elemental stream packet ID entry (entry_ES_PID) 124 is a field for recording the identifier of the packet to which the mark is set.
Duration 125 is a field that records the time interval between adjacent marks, such as the length of a chapter.

The recorded data of the playlist mark (PlayListMark) shown in FIG. 22 is also specified in the case where the conventional MPEG-2 TS format data is recorded as the clip AV stream file, but the MMT format is specified as the clip AV stream file. The case where data is recorded is not specified.
Therefore, it is necessary to specify the recorded data of the playlist mark (PlayListMark) when the MMT format data is recorded as the clip AV stream file.

FIG. 23 shows the following data example.
(1) Conventional playlist mark information recording data (MPEG-2 TS compatible playlist)
(2) New playlist mark information recording data (MMT compatible playlist)

In the "(1) conventional playlist mark information recording data (PEG-2TS compatible playlist)" shown in FIG. 23 (1), when the playback target data is the MPEG-2 TS format data, the playlist mark (PlayListMark) is displayed. Shows the recorded data to be recorded.

The mark time stamp (mark_time_stamp) is a field for recording a time stamp indicating a point at which a mark is set. When the reproduced data is MPEG-2 TS format data, the time stamp of the mark setting position is recorded here. This time stamp is recorded as 45 KHz clock data, which is a general clock used for recording / reproducing MPEG-2 TS format data.

The elementary stream packet ID entry (entry_ES_PID) is a field for recording the identifier of the marked packet. When the reproduction data is MPEG-2 TS format data, the packet ID (PID) of the TS packet at the mark setting position is recorded here.

Duration is a field that records the time interval between adjacent marks, such as the length of a chapter. When the reproduction data is MPEG-2 TS format data, the time interval between adjacent marks is recorded here as 45 KHz clock data, which is a general clock used for recording / reproduction of MPEG-2 TS format data.

“(2) New playlist mark information recording data (MMT compatible playlist)” shown in FIG. 23 indicates recorded data recorded in the playlist mark (PlayListMark) when the playback target data is MMT format data. ing.

When the data to be reproduced is MMT format data, the time stamp of the mark setting position is recorded in the mark time stamp (mark_time_stamp) as time information according to NTP (Network Time Protocol).
Time information according to NTP (Network Time Protocol) is obtained, for example, from the MPT described above with reference to FIG. 18 et al., That is, the MMT Package Table (MPT: MMT Package Table) specified in the MMT format. ..

Further, the elementary stream packet ID entry (entry_ES_PID) is a field for recording the identifier of the packet to which the mark is set, and when the reproduction data is MMT format data, the packet ID of the mark setting position is the MMT packet. Record the ID.

Duration is a field that records the time interval between adjacent marks, such as the length of a chapter. Even if the reproduced data is MMT format data, it is recorded as 45 KHz clock data in this field as in the MPEG-2 TS format data. The time interval between the marks can be calculated at the time of data recording, and is set to be recorded together with the data recording format of the conventional MPEG-2 TS format data.

[6. About clip information files that support MMT format data]
Next, a clip information file corresponding to MMT format data will be described with reference to FIGS. 24 and below.

As described above, the clip information file records information about the data to be played by applying the clip information file. Specifically, it has, for example, playback position information of a clip AV stream file.

FIG. 24 is a diagram showing a data structure (syntax) of one clip information file.
Information about the reproduction data associated with the clip information is recorded in the clip information file. As shown in FIG. 24, for example, the following information is recorded.
Clip information [ClipInfo ()] 201,
Sequence information [SequenceInfo ()] 202,
Program information [ProgramInfo ()] 203,
CPI information [CPI ()] 204

The clip information [ClipInfo ()] 201 records the attribute information of the AV stream file corresponding to the clip information file.
The sequence information [SequenceInfo ()] 202 records information regarding the reproduction sequence of the reproduction target data stored in the AV stream file corresponding to this clip information file.

The program information [ProgramInfo ()] 203 records information about a program (program) including definition information of a reproduction section and a time interval of a clip AV stream reproduced by a clip information file.

The CPI information [CPI ()] 204 is, for example, data for acquiring the data address of the reproduction start point, and EP_map and TU_map described above with reference to FIGS. 13 to 15 are recorded.
As described above with reference to FIG. 12, the CPI type (CPI_type) is recorded in the playlist file. The CPI type (CPI_type) is information indicating the CPI type in the clip information file referred to by the play item (PlayItem) specified in the playlist file.

[6-1. About clip information recorded in the clip information file]
Next, with reference to FIG. 25, the data structure (syntax) of the clip information [ClipInfo ()] 201 recorded in the clip information file will be described.
As described above, the clip information [ClipInfo ()] 201 is an area for recording the attribute information of the AV stream file corresponding to the clip information file.

As shown in FIG. 25, the following data is recorded in the clip information [ClipInfo ()] 201.
(A) Application type 211
(B) Clip stream type (Clip_stream_type) 212
(C) Transcode mode flag (transcode_mode_flag) 213
(D) TS average rate (TS_average_rate) 214,
(E) TS recording rate (TS_recording_rate) 215,
(F) Number of source packets (num_of_source_packets) 216

The application type 211 is information indicating the type of the reproduction application by this clip information file, and specifically, a normal image reproduction type, a slide show reproduction processing type, and the like are defined.

The clip stream type (Clip_stream_type) 212 is information indicating the type of data stored in the clip AV stream file, which is the data to be reproduced by this clip information file. The MPEG-2TS format data includes a stream type in which a black image is inserted between streams in addition to a normal MPEG-2TS stream, and identification information of these types is recorded.

In the transcode mode flag (transcode_mode_flag) 213, the data stored in the clip AV stream file, which is the data to be reproduced by this clip information file, that is, the reproduction target data recorded in the information recording medium (media) is received by broadcasting or the like. It is a flag indicating whether the data is recorded as it is or is recorded by performing a conversion process such as a predetermined compression process.
specifically,
Flag value = 0: No conversion at the time of recording (transpart)
Flag value = 1: With conversion at the time of recording (transcoded)
Flags for such settings are recorded.

TS average rate (TS_avage_rate) 214,
TS recording rate (TS_recording_rate) 215,
These represent the average bit rate of the transport stream of the clip AV stream file, which is the data to be reproduced by this clip information file, and the recording rate in the unit of bytes / seconds.

The number of source packets (num_of_source_packets) 216 is the file size information of the clip AV stream file which is the data to be reproduced by this clip information file, and in the case of MPEG-2 TS format data, the number of source packets is recorded.

As described above, the clip information [ClipInfo ()] 201 shown in FIG. 25 defines the following data as the data to be recorded.
(A) Application type 211
(B) Clip stream type (Clip_stream_type) 212
(C) Transcode mode flag (transcode_mode_flag) 213
(D) TS average rate (TS_average_rate) 214,
(E) TS recording rate (TS_recording_rate) 215,
(F) Number of source packets (num_of_source_packets) 216

However, these data are specified on the assumption that the data stored in the clip AV stream file, which is the data to be reproduced by this clip information file, is MPEG-2 TS format data, and are stored in the clip AV stream file. It is not assumed that the data is MMT format data.
Therefore, it is necessary to specify the data recording mode when the data stored in the clip AV stream file is MMT format data.

FIG. 26 shows the application type (Application type) 211 recorded in the clip information [ClipInfo ()] shown in FIG. 25.
(1) Conventional clip information (ClipInfo) recorded data (MPEG-2 TS compatible clip information file)
(2) New clip information (ClipInfo) recorded data (MPEG-2 TS / MMT compatible clip information file)
It is a figure which showed each of these data.

The "(1) conventional clip information (ClipInfo) recording data (MPEG-2 TS compatible clip information file)" shown in FIG. 26 (1) is clip information (ClipInfo) when the playback target data is MPEG-2 TS format data. The corresponding data of the setting value and the meaning of the application type (Application type) recorded in is shown.

When the data to be reproduced is MPEG-2 TS format data, the following settings are made.
When the application type (Application type) = 1, the type of the playback application by this clip information file is "Main TS for a main-path of Movies", that is, the playback of the main TS (transport stream) corresponding to the image main path. Indicates that it is an application.
A plurality of playback paths such as a main path and a sub path can be set as the image reproduction path, and different play items can be used for reproduction.

Further, when the application type (Application type) = 2, the type of the reproduction application by this clip information file is "Main TS for a main-path of Time based slide show", that is, the main path corresponding to the main path of the time-based slide show. Indicates that it is a TS playback application.
As described above, conventionally, the data to be reproduced is only the MPEG-2 TS format data, and the setting shown in FIG. 26 (1) has been used.

In "(2) New clip information (ClipInfo) recording data (MPEG-2TS / MMT compatible clip information file)" shown in FIG. 26 (2), the reproduction target data is MPEG-2TS format data or MMT format data. The corresponding data of the setting value and the meaning of the application type (Application type) recorded in the clip information (ClipInfo) when two different format data of the case are assumed is shown.

In this setting, in addition to the application type (Application type) = 1 and 2 described in FIG. 26 (1), the following settings are added.
Application type = 3

When the application type (Application type) = 3, the type of the playback application by this clip information file is "Main TLV / MMT for a main-path of Moves", that is, the MMT stored in the TLV packet corresponding to the image main path. Indicates that this is a format data playback application.

By adding such a setting, the playback device stores the data stored in the clip AV stream file recorded on the information recording medium (media) in the TLV packet based on the recorded data of the clip information file. It is possible to confirm that the data is in MMT format and execute a reproduction process corresponding to the MMT format data.

Next, with reference to FIG. 27, the clip stream type (Clip_stream_type) 212 recorded in the clip information [ClipInfo ()] shown in FIG. 25.
(1) Conventional clip information (ClipInfo) recorded data (MPEG-2 TS compatible clip information file)
(2) New clip information (ClipInfo) recorded data (MPEG-2 TS / MMT compatible clip information file)
Each of these data will be described.

The "(1) conventional clip information (ClipInfo) recording data (MPEG-2 TS compatible clip information file)" shown in FIG. 27 (1) is clip information (ClipInfo) when the playback target data is MPEG-2 TS format data. The corresponding data of the setting value and the meaning of the clip stream type (Clip_stream_type) recorded in is shown.

When the data to be reproduced is MPEG-2 TS format data, the following settings are made.
When the clip stream type (Clip_stream_type) = 1, the type of data stored in the clip AV stream file, which is the data to be reproduced by this clip information file, is "A Clip AV stream of BDAV MPEG-2 TS", that is, BDAV MPEG. -Indicates that it is a clip AV stream in 2TS format.

Further, when the clip stream type (Clip_stream_type) = 2, the type of the reproduction data by this clip information file is "A Bridge-Clip AV stream of BDAV MPEG-2 TS", that is, a bridge type clip of BDAV MPEG-2 TS format. Indicates that it is an AV stream.
The bridge type clip AV stream is a stream in which a black image is inserted between the streams.

As described above, conventionally, the data to be reproduced is only the MPEG-2 TS format data, and the setting shown in FIG. 27 (1) has been used.

In "(2) New clip information (ClipInfo) recording data (MPEG-2TS / MMT compatible clip information file)" shown in FIG. 27 (2), the reproduction target data is MPEG-2TS format data or MMT format data. The corresponding data of the setting value and the meaning of the clip stream type (Clip_stream_type) recorded in the clip information (ClipInfo) when two different format data of the case are assumed is shown.

In this setting, in addition to the clip stream type (Clip_stream_type) = 1 and 2 described in FIG. 27 (1), the following settings are added.
Clip stream type (Clip_stream_type) = 3

When the clip stream type (Clip_stream_type) = 3, the type of data stored in the clip AV stream file, which is the data to be reproduced by this clip information file, is "A Clip AV stream of BDAV TLV / MMT", that is, the BDAV format. Indicates that the clip AV stream is in MMT format and is stored in the TLV packet recorded according to.

By adding such a setting, the playback device stores the clip AV stream file recorded on the information recording medium (media) in the TLV packet recorded according to the BDAV format based on the recorded data of the clip information file. It is possible to confirm that the data is the MMT format data and execute the reproduction process corresponding to the MMT format data.

Up to this point, as an example of changing the data to be recorded in the clip information [ClipInfo ()] 201 shown in FIG. 25,
(A) Application type 211
(B) Clip stream type (Clip_stream_type) 212
These two data have been described.

Next, with respect to the following data to be recorded in the clip information [ClipInfo ()] 201 shown in FIG. 25, a data recording example corresponding to MMT format data will be described.
(C) Transcode mode flag (transcode_mode_flag) 213
(D) TS average rate (TS_average_rate) 214,
(E) TS recording rate (TS_recording_rate) 215,
(F) Number of source packets (num_of_source_packets) 216

As described above, the transcode mode flag (transcode_mode_flag) 213 is such that the clip AV stream file storage data, which is the data to be reproduced by this clip information file, is the one in which the received data such as broadcasting is recorded as it is, or a predetermined value. It is a flag indicating whether or not the data was recorded after being subjected to conversion processing such as compression processing.
specifically,
Flag value = 0: No conversion at the time of recording (transpart)
Flag value = 1: With conversion at the time of recording (transcoded)
Flags for such settings are recorded.
This setting can be used for MMT format data with the same setting.

TS average rate (TS_avage_rate) 214,
TS recording rate (TS_recording_rate) 215,
As described above, these represent the average bit rate of the transport stream of the clip AV stream file, which is the data to be reproduced by this clip information file, and the recording rate in units of bytes / seconds.

This bit rate information is premised on being calculated based on the TS packet, and when the reproduction target data is MMT format data stored in the TLV packet, it is necessary to record the bit rate corresponding to the TLV packet.

That is, as shown in FIG. 25.
In the field of TS average rate (TS_avage_rate) 214,
Record the TLV average rate (TLV_avage_rate).

The TLV average rate (TLV_average_rate) is calculated by the following formula.
TLV average rate (TLV_avarage_rate)
= (File size) / ((ATS of TLV packet at the end of file)-(ATS of TLV packet at the beginning of file)))
The file in the above calculation formula is a clip AV stream file composed of TLV packets.
The ATS is a time stamp (ATS: Initial Time Stamp) indicating the start timing of processing (decoding, etc.) of the data stored in the TLV packet, and can be acquired from the TLV packet or control information (SI).

The calculated value calculated by the above formula,
As the TLV average rate (TLV_avage_rate),
In the clip information [ClipInfo ()] shown in FIG. 25,
Record in the field of TS average rate (TS_avage_rate) 214.
Alternatively, if the data to be reproduced is in the MMT format, an invalid value may be recorded in this field and the average rate information may not be used.

Further, as shown in FIG. 25,
In the field of TS recording rate (TS_recording_rate) 215,
Record the TLV recording rate (TLV_recording_rate).

The TLV recording rate (TLV_recording_rate) is calculated by the following formula.
TLV recording rate (TLV_recording_rate)
= (T2-t1) / S
In addition, each parameter in the above formula has the following values.
t2: ATS of the maximum size TLV packet in the file
t1: ATS of the TLV packet following the TLV packet of the maximum size in the file
S: Size of the maximum size TLV packet in the file The file is a clip AV stream file composed of TLV packets.
The ATS is a time stamp (ATS: Initial Time Stamp) indicating the start timing of processing (decoding, etc.) of the data stored in the TLV packet, and can be acquired from the TLV packet or control information (SI).

The calculated value calculated by the above formula,
As a TLV recording rate (TLV_recording_rate),
In the clip information [ClipInfo ()] shown in FIG. 25,
Record in the field of TS recording rate (TS_recording_rate) 215.
Alternatively, if the data to be reproduced is in the MMT format, an invalid value may be recorded in this field and the recording rate information may not be used.

Further, in the clip information [ClipInfo ()] shown in FIG. 25,
The number of source packets (num_of_source_packets) 216 is the file size information of the clip AV stream file which is the data to be reproduced by this clip information file.
As described above, when the data to be reproduced is MPEG-2 TS format data, the number of source packets is recorded.

As described above with reference to FIG. 6, the TS packet has a fixed length unlike the above-mentioned MMTP packet, and the packet size of one TS packet is fixed at 188 bytes.
Therefore, there is a feature that the data size can be grasped based on the number of packets.

However, when the reproduction target data is MMT format data, as described above with reference to FIG. 7, the MMTP packet which is the constituent packet of the MMT format data and the TLV packet have variable lengths and various packets. It can be set to the size.
Therefore, even if the number of packets is recorded in the field of the number of source packets (num_of_source_packets) 216, the data size cannot be grasped.

When the data to be reproduced is in the MMT format, the file size (byte size) of the clip AV stream file composed of a plurality of TLV packets is recorded in this field.
When the data to be reproduced is in the MMT format, the file size (byte size) of the clip AV stream file composed of TLV packets is recorded as 64-bit data in this field as a setting capable of recording 64-bit data.
Alternatively, when the data to be reproduced is in the MMT format, an invalid value may be recorded in this field and used as an unused field.

[6-2. About the sequence information recorded in the clip information file]
Next, with reference to FIG. 28, the data structure (syntax) of the sequence information [SequenceInfo ()] 202 recorded in the clip information file described above with reference to FIG. 24 will be described.
As described above, the sequence information [SequenceInfo ()] 202 records information regarding the reproduction sequence of the reproduction target data stored in the AV stream file corresponding to the clip information file.

As shown in FIG. 28, the following data is recorded in the sequence information [SequenceInfo ()] 202.
(A) ATC start position SPN (SPN_ATC_start) 221
(B) Number of STC sequences (num_of_STC_sequence) 222
(C) Program clock reference packet ID (PCR_PID) 223
(D) STC start position SPN (SPN_STC_start) 224,
(E) Display start time (presentation_start_time) 225,
(F) Display end time (presentation_end_time) 226

Prior to the description of these data, a packet configuration of a clip AV stream file storing playback target data and an example of playback processing will be described with reference to FIG. 29.
FIG. 29 shows (a) a packet sequence stored in the clip AV stream file. In the case of MPEG-2 TS format data, one rectangle corresponds to one TS packet.
In the example of FIG. 29, the packet numbers 0 to nn are the configuration data of one clip AV stream file.

The packet of this one clip AV stream file is a packet sequence arranged according to one ATC (arrival time clock).
The packet sequence arranged according to this one ATC is called an ATC sequence.

Packets 0 to nn of one clip information file shown in FIG. 29 include one or more STC sequences. The example shown in FIG. 29 includes three STC sequences. STC sequences # 0 to # 2.
One STC (system time clock) is a clock defined based on one PCR (program clock reference), and source packets belonging to one STC sequence are regenerated and controlled by one STC (for example, 45 KHz). To.

The STC sequence # 0 shown in FIG. 29 is a packet sequence that can be continuously reproduced according to the STC (system time clock), which is a clock defined with reference to the PCR (program clock reference) stored in the PCR storage packet a.
The STC sequence # 1 is the PCR stored in the PCR storage packet b.
Further, the STC sequence # 2 is a packet sequence in which the PCR stored in the PCR storage packet c can be continuously reproduced according to the STC defined as a reference.

The example shown in FIG. 29 has been described as an example in which three STC sequences are included in one ATC sequence, but the number of STC sequences included in one ATC sequence can be set in various ways.

Returning to FIG. 28, the recorded data of the sequence information [SequenceInfo ()] 202 recorded in the clip information file will be described.
(A) The ATC start position SPN (SPN_ATC_start) 221 is an area for recording the SPN (source packet number) of the ATC start position of the clip AV stream file to be reproduced by this clip information file.
In the example described with reference to FIG. 29,
The ATC start position SPN (SPN_ATC_start) = 0.

(B) In the number of STC sequences (num_of_STC_sequence) 222, the number of STC sequences included in the clip AV stream file to be reproduced by this clip information file is recorded.
In the example described with reference to FIG. 29,
The number of STC sequences (num_of_STC_sequence) = 3.

(C) The program clock reference packet ID (PCR_PID) 223 is a packet containing PCR (program clock reference) corresponding to each STC sequence included in the clip AV stream file to be reproduced by this clip information file. Record the packet identifier.

(D) In the STC start position SPN (SPN_STC_start) 224, the SPN (source packet number) of the start position of each STC sequence included in the clip AV stream file to be reproduced by this clip information file is recorded.

(E) Display start time (presentation_start_time) 225,
(F) Display end time (presentation_end_time) 226
In these, the display start time and the end time of each STC sequence included in the clip AV stream file to be reproduced by this clip information file are recorded. As this time information, both STC time information (stc_id) and ATC time information (atc_id) are recorded.

The above description is an example of recorded data when the data to be reproduced by this clip information file is MPEG-2 TS format data.
Next, each recorded data when the data to be reproduced by this clip information file is MMT format data will be described.

(A) As described above, the ATC start position SPN (SPN_ATC_start) 221 is an area for recording the SPN (source packet number) of the ATC start position of the clip AV stream file to be reproduced by the clip information file.

As described above with reference to FIG. 6, the TS packet has a fixed length unlike the above-mentioned MMTP packet, and the packet size of one TS packet is fixed at 188 bytes.
Therefore, there is a feature that the data size can be grasped based on the number of packets.

However, when the reproduction target data is MMT format data, as described above with reference to FIG. 7, the MMTP packet and the TLV packet which are the constituent packets of the MMT format data have variable lengths and various packet sizes. Can be set to.
Therefore, even if the packet number is recorded in the field of the ATC start position SPN (SPN_ATC_start) 221, the data size cannot be grasped.

For these reasons, regarding the clip information file corresponding to the MMT format data set when the reproduction target data is the MMT format data stored by the TLV packet, the following recording area of the sequence information [SequenceInfo ()] shown in FIG. 28 , It is necessary to change to the data corresponding to the MMT format data and record it.
(A) ATC start position SPN (SPN_ATC_start) 221
(B) Number of STC sequences (num_of_STC_sequence) 222
(C) Program clock reference packet ID (PCR_PID) 223
(D) STC start position SPN (SPN_STC_start) 224,
(E) Display start time (presentation_start_time) 225,
(F) Display end time (presentation_end_time) 226

With reference to FIG. 30, the recorded data of the sequence information [SequenceInfo ()] when the reproduction target data is the MMT format data stored by the TLV packet will be described.

First, (a) the data to be recorded at the ATC start position SPN (SPN_ATC_start) 221 will be described.
As described above, the ATC start position SPN (SPN_ATC_start) 221 is an area for recording the SPN (source packet number) of the ATC start position of the clip AV stream file to be reproduced by this clip information file.
In the configuration example of the MPEG2-TS packet described with reference to FIG. 29,
The ATC start position SPN (SPN_ATC_start) = 0.

In the case of a clip AV stream file composed of MPEG2-TS packets, as described with reference to FIG. 29, a packet sequence arranged according to one ATC (arrival time clock) is an ATC sequence, and the ATC sequence of this ATC sequence. The SPN (source packet number) in the start position is recorded.

On the other hand, when the clip AV stream file is composed of a TLV packet string containing MMT format data,
The ATC sequence is one of the following sequences.
(1) Either a time stamp associated with an MMTP packet, a packet sequence number (packet_sequence_number), or a sequence defined by a combination of both data (TLV packet sequence), or.
(2) A sequence (TLV packet sequence) defined by a NTP transmission time stamp (transmit_timestamp),

When the clip AV stream file is composed of a TLV packet sequence containing MMT format data, any of the above sequences (1) and (2) (TLV packet sequence) is defined as an ATC sequence.

The NTP of (2) above is time information according to the network time protocol (Network Time Protocol), as described above with reference to FIG.
A transmitting device such as a broadcasting station stores NTP data containing a transmission time stamp (transmit_timestamp) in a UDP packet at regular intervals (33.04647 msec intervals) in a TLV packet containing playback data and the like, and further stores the NTP packet in the UDP packet. Store in and send.
This NTP time information transmission is mainly used for time adjustment of the receiving side device.

As described above, the ATC sequence in the clip AV stream file composed of the TLV packet sequence storing the MMT format data is defined as any of the above sequences (1) and (2) (TLV packet sequence).
According to the definition of this ATC sequence, the data to be recorded at the ATC start position SPN (SPN_ATC_start) 221 of the sequence information (SequenceInfo ()) shown in FIG. 30 is the following recorded data.
From the beginning of the clip AV stream file composed of the TLV packet string (= the beginning of the first TLV packet stored in the file), the start position of any of the above (1) and (2) ATC sequences (= valid stream). The number of bytes up to the start position) is used as the recorded data. For example, the number of bytes is recorded in 64 bits.

(B) The number of STC sequences (num_of_STC_sequence) 222 is an area for recording the number of STC sequences included in the clip AV stream file to be reproduced by this clip information file.
When the playback target data is MMT format data,
The number of STC sequences (num_of_STC_sequence) = 1.
That is, it is set that only one STC sequence is included in one ATC sequence.

(C) The program clock reference packet ID (PCR_PID) 223 is a packet of a packet containing PCR (program clock reference) corresponding to each STC sequence included in the clip AV stream file to be reproduced by this clip information file. This is the area for recording identifiers.
If the data to be reproduced is MMT format data, the data position cannot be specified from the packet identifier. Therefore, an invalid value is recorded in this field and the setting is not used.

(D) The STC start position SPN (SPN_STC_start) 224 is an area for recording the SPN (source packet number) of the start position of each STC sequence included in the clip AV stream file to be reproduced by this clip information file.

In the case of a clip AV stream file composed of MPEG2-TS packets, as described with reference to FIG. 29, a packet sequence arranged according to one STC (system time clock) is an STC sequence, and the STC sequence of this STC sequence. The SPN (source packet number) in the start position is recorded.
One STC (system time clock) is a clock defined based on one PCR (program clock reference), and a source packet belonging to one STC sequence is reproduced by one STC (for example, 45 KHz). Be controlled.

On the other hand, when the clip AV stream file is composed of a TLV packet string containing MMT format data,
The STC sequence is as follows.
(1) MPU presentation time (mpu_presentation_time) indicating MPU-compatible playback (presentation) time, which is one data processing unit of playback target data such as images, sounds, and subtitles in the MMT format, or MPU-compatible sequence identifier MPU. A sequence defined by either or both of the corresponding sequence numbers (mpu_sequence_number).

When the clip AV stream file is composed of a TLV packet string storing MMT format data, the STC sequence is the sequence shown in (1) above.

The MPU presentation time (mpu_presentation_time), the MPU-compatible sequence number (mpu_sequence_number), and these data are the data recorded in the MPU time stamp descriptor described above with reference to FIG. 21.
The MPU time stamp descriptor is recorded data in the MMT package table (MPT) described above with reference to FIG.

When using the STC sequence defined in (1) above, consider the setting of the MPU presentation time leap identifier (mpu_presentation_time_leap_indicator), which is an identifier indicating whether or not the MPU presentation time (mpu_presentation_time) includes "leap seconds". It is also necessary to do.
The MPU presentation time leap identifier (mpu_presentation_time_leap_indicator) is set to [1] when the MPU presentation time (mpu_presentation_time) includes "leap second", and [0] when it is not included.

As described above, when the data stored in the clip AV stream file is MMT format data, either the MPU presentation time (mpu_presentation_time) or the MPU-compatible sequence identifier (mpu_sequence_number), which is the MPU-compatible sequence identifier, or The sequence defined by both is used as the STC sequence.

When the data to be reproduced is MMT format data, the data shown in FIG. 30 is shown in FIG.
(D) In the field of STC start position SPN (SPN_STC_start) 224, the beginning of the clip AV stream file (= the first TLV stored in the file) is the same as (a) ATC start position SPN (SPN_ATC_start) 221 described above. The number of bytes from the beginning of the packet) to the start position of the STC sequence according to the above definition is recorded. For example, the number of bytes is recorded in 64 bits.

(E) Display start time (presentation_start_time) 225,
(F) Display end time (presentation_end_time) 226
These are areas for recording the display start time and end time of each STC sequence included in the clip AV stream file to be reproduced by this clip information file.

When the playback target data is MMT format data,
(E) In the data recording area of the display start time (presentation_start_time) 225,
The MPU presentation time (mpu_presentation_time) recorded in the first MPT (MMT package table) in the TLV packet in one STC sequence starting from "(d) STC start position SPN (SPN_STC_start)" described above is recorded. do.

The MPU presentation time (mpu_presentation_time) is data recorded in the MPU time stamp descriptor described above with reference to FIG. 21.
The MPU time stamp descriptor is recorded data in the MMT package table (MPT) described above with reference to FIG.

The time information of the MPU presentation time (mpu_presentation_time) recorded in the MPT (MMT package table) is 64-bit time information according to NTP (Network Time Protocol), and the 64-bit NTP time information is referred to as "(e). It is recorded in the data recording area of the display start time (presentation_start_time) 225.

Further, when the data to be reproduced is MMT format data,
(F) In the data recording area of the display end time (presentation_end_time) 226,
The MPU presentation time (mpu_presentation_time) recorded in the last MPT (MMT package table) in the TLV packet in one STC sequence starting from "(d) STC start position SPN (SPN_STC_start)" described above is recorded. do.
(E) As with the data of the display start time (presentation_start_time) 225, 64-bit NTP time information is recorded.

[6-3. About the program information recorded in the clip information file]
Next, with reference to FIG. 31, the data structure (syntax) of the program information [ProgramInfo ()] 203 recorded in the clip information file described above with reference to FIG. 24 will be described.
As described above, in the program information [ProgramInfo ()] 203, information about the program (program) including the definition information of the reproduction section and the time interval of the clip AV stream reproduced by the clip information file is recorded.

The main data recorded in the program information [ProgramInfo ()] shown in FIG. 31 will be described.
(A) Number of program sequences [num_of_program_sequences] 231 records the number of program sequences (program_sequence) included in the clip information file.
(B) The SPN program sequence start address [SPN_program_sequence_start [i]] 232 records the relative address of the place where the program sequence starts on the AV stream file.
(C) In the program map PID [program_map_PID [i]] 233, the storage position information of the map of the program sequence (program_sequence) is recorded.
(D) In the stream PID [Stream_PID] 234, the packet identifier (PID) of the TS packet for transmitting the stream is recorded.
(E) Stream coding information [StreamCodingInfo] 235 records coding (encoding) information of the stream to be reproduced.

The program sequence is a section in which the coding information in the AV stream included in the clip AV stream file is continuous.
For example, an image data section encoded by one image coding mode, a voice data section encoded by one voice coding mode, and the like are defined as individual program sequences.

These recorded data of the program information [ProgramInfo ()] shown in FIG. 31, that is,
(A) Number of program sequences [num_of_program_sequences] 231
(B) SPN program sequence start address [SPN_program_sequence_start [i]] 232,
(C) Program map PID [program_map_PID [i]] 233,
(D) Stream PID [Stream_PID] 234,
These data recording modes are specified when the data to be reproduced by this clip information file is in the MPEG-2 TS format, but there is no provision when the data to be reproduced is in the MMT format, and are newly specified. It is necessary to do.

(A) The number of program sequences [num_of_program_sequences] 231 is
When the data to be reproduced is in the MPEG-2 TS format or the MMT format, the number of program sequences may be recorded.

(B) For the SPN program sequence start address [SPN_program_sequence_start [i]] 232, if the playback target data is in the MPEG-2 TS format, the SPN (source packet number) at the start position of the SPN program sequence is recorded.

On the other hand, when the clip AV stream file containing the reproduction target data is composed of the TLV packet string storing the MMT format data, the beginning of the clip AV stream file (= the beginning of the first TLV packet stored in the file). To record the number of bytes from to the start of each program sequence. For example, the number of bytes is recorded in 64 bits.

(C) For the program map PID [program_map_PID [i]] 233, when the data to be reproduced is in the MPEG-2 TS format, the identifier (PID) of the packet in which the map of the program sequence (program_sequence) is stored is recorded. ..
The program map is map data in which information such as an image, sound, subtitles, and other information such as a coding mode for each program sequence unit is recorded.

On the other hand, when the clip AV stream file storing the reproduction target data is MMT format data, the information corresponding to the map data in which the information such as the coding mode of each program sequence unit such as image, sound, subtitle, etc. is recorded is described first. It is recorded in the MMT package table (MPT: MMT Package Table) described with reference to FIG.

As described above with reference to FIG. 19, the MMT package table (MPT: MMT Package Table) contains data attribute information (asset description) for each data type (asset type) such as images, sounds, and subtitles. There is a table that records the child) in detail. In the MMT format, one asset corresponds to one program sequence.

When decoding and playing back data such as images, sounds, and subtitles according to the MMT format stored in the clip AV stream file, refer to this MMT package table (MPT) for each asset unit such as images, sounds, and subtitles. It is possible to acquire attribute information such as a coding mode.

Therefore, when the clip AV stream file storing the reproduction target data is MMT format data, the packet storing the MMT package table (MPT) is stored in the recording area of the program map PID [program_map_PID [i]] 233 shown in FIG. PID (packet identifier) may be recorded.
The PID (packet identifier) applied to the identification is basically the PID of the MMTP packet, but the PID of the upper IP packet or the TLV packet can also be used.

However, the problem here is that the PID (packet identifier) may not be able to identify the packet containing the target MMT package table (MPT).
The reason for this will be described with reference to FIGS. 32 and 33.

First, with reference to FIG. 32, a packet delivery example in which a packet containing a target MMT package table (MPT) can be specified by a PID (packet identifier) will be described.
FIG. 32 shows the following figures.
(1) Transmission packet of broadcast server 21 (2) PID (packet identifier) setting example for transmission packet of broadcast server 21

The transmission packet of the broadcast server 21 shown in FIG. 32 (1) shows a packet sequence of TLV packets. The TLV packet is composed of a packet containing reproduction target data such as images, sounds, and subtitles, and various data such as control information (SI).
It is assumed that the broadcast server 21 transmits the contents of a plurality of programs corresponding to a plurality of channels, such as BS101 channel and BS102 channel, and control information.

The following packet sequence is shown in the PID (packet identifier) setting example for the transmission packet of the broadcast server 21 shown in FIG. 32 (2).
(A) Broadcast server compatible control information (SI)
(B) Channel 101 compatible data (playback data (image, audio, subtitles, etc.) + channel 101 compatible control information (SI))
(C) Channel 102 compatible data (reproduction data (image, audio, subtitles, etc.) + channel 102 compatible control information (SI))

The broadcasting server 21, for example, mixes these three series of packets (A), (B), and (C) and transmits them as one IP data flow.
Note that each packet identifier (PID) of a plurality of packets included in one IP data flow is set so as not to be duplicated.

(A) The broadcast server-compatible control information (SI) is a TLV packet string composed of a program guide of program contents of a plurality of channels transmitted by the broadcast server 21 and control information required for receiving processing of the contents of each channel. Is.
(B) Channel 101 compatible data (reproduction data (image, audio, subtitles, etc.) + channel 101 compatible control information (SI)) is used for reproduction data of the program content of channel 101 and reproduction processing of the program content of this channel. It is a TLV packet string composed of data peculiar to channel 101 such as necessary control information.
(C) Channel 102 compatible data (reproduction data (image, audio, subtitles, etc.) + channel 102 compatible control information (SI)) is used for reproduction data of the program content of channel 102 and reproduction processing of the program content of this channel. It is a TLV packet string composed of data peculiar to channel 102 such as necessary control information.

As shown in FIG. 32, (B) channel 101 compatible data (reproduction data (image, audio, subtitles, etc.) + channel 101 compatible control information (SI)) includes controls required for reproduction of the program content of channel 101. A TLV packet containing an MPT-101 storage packet, which is a packet storing an MMT package table (MPT) corresponding to channel 101 in which information is stored, is included.

Further, as shown in FIG. 32, (C) channel 102 compatible data (reproduction data (image, sound, subtitle, etc.) + channel 102 compatible control information (SI)) is required for reproduction of the program content of channel 102. A TLV packet containing an MPT-102 storage packet, which is a packet storing an MMT package table (MPT) corresponding to the channel 102 in which the control information is stored, is included.

The example shown in FIG. 32 is an example in which the broadcasting server 21 transmits the three data series (A), (B), and (C) shown in FIG. 32 (2) as one IP data flow. In this case, a unique PID (packet identifier) is set for each of all the packets included in the three data series (A), (B), and (C) shown in FIG. 32 (2).
As described above, if the PIDs unique to all the TLV packets included in the three data series (A), (B), and (C) shown in FIG. 32 (2) are set, the receiving device is set to the PID. By (packet identifier), all TLV packets included in the three data series (A), (B), and (C) can be identified based on PID (packet identification).

As a result, the MPT-101 storage packet containing the MMT package table (MPT) corresponding to the channel 101 and the MPT-102 storage packet containing the MMT package table (MPT) corresponding to the channel 102 are also used as PIDs (packet identifiers). It becomes possible to identify based on.

Next, with reference to FIG. 33, a packet delivery example in which it is impossible to specify a packet containing a target MMT package table (MPT) by a PID (packet identifier) will be described.
Similar to FIG. 32, FIG. 33 shows the following figures.
(1) Transmission packet of broadcast server 21 (2) PID (packet identifier) setting example for transmission packet of broadcast server 21

The transmission packet of the broadcast server 21 shown in FIG. 33 (1) shows a packet sequence of TLV packets. The TLV packet is composed of a packet containing reproduction target data such as images, sounds, and subtitles, and various data such as control information (SI).
It is assumed that the broadcast server 21 transmits the contents of a plurality of programs corresponding to a plurality of channels, such as CS301 channel and CS302 channel, and control information.

The PID (packet identifier) setting example for the transmission packet of the broadcast server 21 shown in FIG. 33 (2) shows the following packet sequence as in FIG. 32.
(A) Broadcast server compatible control information (SI)
(B) Channel 301 compatible data (playback data (image, audio, subtitles, etc.) + channel 301 compatible control information (SI))
(C) Channel 302 compatible data (playback data (image, audio, subtitles, etc.) + channel 302 compatible control information (SI))

The broadcasting server 21 transmits, for example, the above (A), (B), (C), these three series of packets in a mixed manner.
However, in the example shown in FIG. 33, the broadcast server 21 transmits the above (A), (B), (C) as three individual IP data flows for these three series.
As described above, each packet identifier (PID) of a plurality of packets included in one IP data flow is set so as not to be duplicated.

In the packet delivery example shown in FIG. 33, unlike FIG. 32, the broadcasting server 21 has an individual IP data flow for each of the three data sequences (A), (B), and (C) shown in FIG. 33 (2). The broadcast server 21 sets a PID (packet identifier) for each IP data flow (= each data series (A), (B), (C)) and transmits the data.
That is, the TLV packet included in the data series (A) is set with a PID (packet identifier) that does not overlap in the series (A).
A unique PID (packet identifier) in the series (B) is set in the TLV packet of the data series (B).
A PID (packet identifier) that does not overlap in the series (C) is set in the TLV packet of the data series (C).
The example shown in FIG. 33 is an example in which a unique PID (packet identifier) is set for each data series and transmitted.

However, in the example in which a plurality of IP data flows are set and a PID (packet identifier) is set and transmitted for each IP data flow unit, when the data series are different, the same PID (packet identifier) is used. May be set.
For example, the PID (packet identifier) of the MPT-301 stored packet containing the MMT package table (MPT) corresponding to the channel 301 included in the data series (B) and the same PID (packet identifier) are the data series (A) or It may be set in other packets of (C).
Similarly, the PID (packet identifier) of the MPT-302 stored packet containing the MMT package table (MPT) corresponding to the channel 302 included in the data series (C) and the same PID (packet identifier) are the data series (A). And (B) may also be set in other packets.

That is, in the PID (packet identifier) setting example shown in FIG. 33, the receiving device uses only the PID (packet identifier) to store the MPT-301 storage packet containing the MMT package table (MPT) corresponding to the channel 301, or the channel 302. It becomes impossible to identify and selectively extract the MPT-302 stored packet containing the corresponding MMT package table (MPT).

For example, Japanese broadcasting regulations allow transmission processing with one IP data flow setting shown in FIG. 32 for BS broadcasting and a plurality of IP data flow settings shown in FIG. 33 for CS broadcasting.

As shown in FIG. 33, even when overlapping PIDs (packet identifiers) are set between different IP data flows (data series), packet identification by PID (packet identifier) is possible for each data series unit. The control information for this is transmitted from the transmitting device such as the broadcasting server 21 to the receiving device.

This control information is control information included in the broadcast server-compatible control information (SI) shown in FIGS. 32 (2) (A) and 33 (2) (A), and is a package list table (PLT: Package List Table). Is called.
The package list table (PLT: Package List Table) will be described with reference to FIG. 34 and below.

FIG. 34 shows each of the following packet sequences.
(A) Broadcast server compatible control information (SI)
(B) Channel X compatible data (playback data (image, audio, subtitles, etc.) + channel X compatible control information (SI))
(C) Channel Y compatible data (playback data (image, audio, subtitles, etc.) + channel Y compatible control information (SI))
These correspond to the three data series (A), (B), and (C) described with reference to FIGS. 32 and 33.

(A) The broadcast server correspondence control information (SI) includes a package list table (PLT: Package List Table).
In the package list table (PLT), the stored packets (MPT-X, MPT-Y) of the MMT package table (MPT) corresponding to each channel included in other data series ((B), (C)) are selected and extracted. MPT identification information for this is recorded.

By referring to the MPT identification information recorded in the package list table (PLT), the receiving device refers to the stored packets (MPT-X, MPT-Y) of each data series, that is, the MMT package table (MPT) corresponding to each channel. Can be selected and extracted.
Further, a PID (packet identifier) for each asset (image, audio, subtitle, etc.) of the channel is recorded in the MMT package table (MPT) corresponding to each channel, and the receiving device is the MMT package table (MPT). It is possible to read the PID (packet identifier) of each asset (image, sound, subtitle, etc.) recorded in the channel and individually select and extract the packet containing the image, sound, and subtitle of the channel.

FIG. 35 is a diagram showing a data structure (syntax) of the package list table (PLT).
The MMT general position information (MMT_general_location_info) 241 shown in FIG. 35 is the above-mentioned MPT identification information.
That is, it is MPT identification information for selectively extracting stored packets (MPT-X, MPT-Y) of the MMT package table (MPT) corresponding to each channel.

FIG. 36 is a diagram showing a data structure (syntax) of MMT general position information (MMT_general_location_info) 241.
The packet identifier (packet_id) 242 shown in FIG. 36 is a PID (packet identifier) of the MMT package table (MPT) corresponding to each data series (each channel).
The receiving device can select and extract the stored packets (for example, MPT-X and MPT-Y in FIG. 34) of the MMT package table (MPT) corresponding to each channel by referring to this packet identifier (packet_id) 242. Become.

FIG. 37 is a diagram showing a data structure (syntax) of the MMT package table (MPT).
The MMT general position information (MMT_general_location_info) 243 shown in FIG. 37 is identification information for each asset (image, sound, subtitle, etc.).
That is, it is information for identifying a packet containing images, sounds, and subtitles corresponding to a channel belonging to one channel.

FIG. 38 is a diagram showing a data structure (syntax) of MMT general position information (MMT_general_location_info) 243 recorded in the MMT package table (MPT).
The packet identifier (packet_id) 244 shown in FIG. 38 is a PID (packet identifier) for each asset (image, sound, subtitle, etc.) described above.
The receiving device can individually select and extract a packet containing an image, audio, and subtitle corresponding to one channel by referring to the packet identifier (packet_id) 242.

As described above, the receiving device is described with reference to FIGS. 32 to 34.
(A) By referring to the package list table (PLT) included in the broadcast server correspondence control information, the MMT package table (MPT) corresponding to each channel is identified and acquired, and the recorded data of the acquired MMT package table (MPT) is obtained. Based on the above, packets containing images, sounds, subtitles, etc., which are playback data corresponding to each channel, can be selectively extracted.

However, when the receiving device records data on a medium such as a BD, for example, only the data corresponding to the channel to be recorded may be selected and recorded.
That is, for example, the data series (B) and the data series (C) described with reference to FIGS. 32 to 34, and the packets (TLV packets) belonging to the data series including these reproduction target data are selected and BD or the like is selected. May be recorded on media.
In this case, (A) broadcast server correspondence control information is not recorded on the media.
When data is recorded on the media with such a setting, (A) the package list table (PLT) included in the broadcast server correspondence control information is not recorded on the media.
Therefore, when playing back data from the media, the PID (packet identifier) of the MMT package table (MPT) corresponding to each channel is read with reference to the package list table (PLT), and the MMT package table is based on the read PID. The process of extracting the packet containing (MPT) becomes impossible.

In addition, all data series (A) to (C) are set to be recorded on the media, and all TLV packets of a plurality of data series transmitted by one broadcasting station are recorded in one clip AV stream file. And, packets with the same packet identifier set will be mixed in one clip AV stream file, and in order to identify these, a packet containing the package list table (PLT) included in the clip AV stream file. It is necessary to perform a process of extracting the packet and referring to the data of the PLT. This process is not a process that can be realized by a reproduction process according to the current BDAV format, that is, a reproduction process based on the control information recorded in the clip information file.

Therefore, even when the clip AV stream file is MMT format data, it is necessary to change the recorded information of the clip information file to be recorded in order to enable the reproduction process based on the control information recorded in the clip information file. ..

[6-3-1. About the processing example of recording the IP data flow identification information in the program information of the clip information file]
Hereinafter, when the clip AV stream file is MMT format data, the structure of the clip information file that enables smooth playback processing according to the recorded data of the clip information file will be described.

When the clip AV stream file storing the reproduction target data is MMT format data, the information processing apparatus that records the data on a medium such as BD has the program information shown in FIG. 31 in the clip information file that records the reproduction control information. In the program map PID [program_map_PID [i]] 233 recording area of [ProgramInfo ()] 203, the PID (packet identifier) of the packet storing the MMT package table (MPT) is recorded, and the MPT or MPT is used. The IP data flow identification information that makes it possible to identify the "IP data flow (corresponding to the data series (B), (C), etc. shown in FIGS. 32 to 34)" corresponding to the reproduced data to be reproduced is recorded.

This specific example will be described with reference to FIG. 39.
FIG. 39 shows the data structure (syntax) of the program information [ProgramInfo ()] 203 recorded in the clip information file, as described with reference to FIG. 31.
The data structure (syntax) of the program information [ProgramInfo ()] 203 shown in FIG. 39 is the program information [ProgramInfo ()] when the clip AV stream file to be played by applying this clip information file is MMT format data. It is a data structure of 203.

In the data structure shown in FIG. 39, the data recording area of the data 251 to 256 corresponds to the recording area of the program map PID [program_map_PID [i]] 233 described with reference to FIG. 31.
As described with reference to FIG. 31, the storage position information of the map of the program sequence (program_sequence) is recorded in the recording area of the program map PID [program_map_PID [i]] 233.

When the clip AV stream file to be played by applying the clip information file is MMT format data, as shown in FIG. 39, the following data is stored in the recording area of the original program map PID [program_map_PID [i]] 233. Record.
(1) Source IP address (src_IP_addless) 251
(2) Destination IP address (dest_IP_addless) 252
(3) Destination port (destination_port) 253
(4) Source port (source_port) 254
(5) Next header information (next_header) 255
(6) MPT storage packet identifier (MPT_PID) 256

In the above data, the data sets (1) to (5) correspond to the IP data flow identification information.
(1) Source IP address (src_IP_addless) 251
(2) Destination IP address (dest_IP_addless) 252
(3) Destination port (destination_port) 253
(4) Source port (source_port) 254
These data are IP packet correspondence information corresponding to the IP packet stored in the TLV packet. The (5) next header information (next_header) 255 is a recording area for protocol type information, and records a fixed value [00010001] indicating UDP.

The data set composed of the above five data (1) to (5) is information unique to the IP data flow. For example, when a plurality of IP data flows are mixedly transmitted from the same broadcasting server, the data sets (1) to (5) are data sets having different settings for each IP data flow, and IP data flow identification. It is data that can be used as information.
The information processing apparatus can determine the IP data flow by referring to the IP data flow identification information consisting of these five data.

Further, the information processing apparatus identifies the IP data flow based on the IP data flow identification information of (1) to (5), and then the information processing apparatus identifies the IP data flow.
(6) MPT storage packet identifier (MPT_PID) 256
This data is read, the PID that stores the MPT corresponding to a specific IP data flow (for example, a specific channel) is read, and the packet that stores the MPT corresponding to the IP data flow (for example, a specific channel) is read based on this PID. It will be possible to identify.

When the information processing apparatus records a clip AV stream file consisting of a TLV packet string in which MMT format data is stored in a medium such as BD, the program information [ProgramInfo ()] of the clip information file corresponding to the clip AV stream file is recorded. The following data is recorded in the map PID [program_map_PID [i]] recording area.
(1) Source IP address (src_IP_addless) 251
(2) Destination IP address (dest_IP_addless) 252
(3) Destination port (destination_port) 253
(4) Source port (source_port) 254
(5) Next header information (next_header) 255
(6) MPT storage packet identifier (MPT_PID) 256

By recording these data in the clip information file, the playback device that reproduces the data from the media reads the above data (1) to (6) from the clip information file, and one IP data flow and its IP data. It is possible to select a packet that stores a flow-compatible MPT.

The IP data flow identification information composed of the above data (1) to (5) is recorded in the IP header of the IP packet stored in the TLV packet, and the recording device uses the above data (from the IP header). 1) to (5) are acquired, recorded in a clip information file, and recorded on a medium such as BD.
Further, the playback device refers to the IP header of the IP packet in the TLV packet in the clip AV stream file, reads the corresponding data of the above data (1) to (5), and records the packet (TLV packet) on the media. / IP packet / MMTP packet) can be identified as the IP data flow to which it belongs.

As described above with reference to FIG. 10, a clip AV stream file composed of a packet sequence of TLV packets is recorded on a medium such as a BD. An IP packet is stored in each TLV packet, and an MMTP packet is stored in the IP packet.
Control information such as reproduction target data (image, sound, subtitle) and MMT package table (MPT) is stored as a payload of an MMTP packet.

Next, the data structure (syntax) of the TLV header, which is the header of the TLV packet, and the IP header, which is the header of the IP packet, will be described with reference to FIGS. 40 and below.
As shown in FIG. 40, a packet type (packet_type) is recorded in the TLV header set in the TLV packet.
The configuration is such that it is possible to identify which type of packet (a) to (c) below the TLV packet is, depending on the value of the packet type.

Specifically, the settings are as follows.
Packet type (packet_type) = 0x02 means that the payload of the TLV packet is an "IP (V6) packet".
Packet type (packet_type) = 0x03 means that the payload of the TLV packet is a "compressed IP packet".
Packet type (packet_type) = 0xFE means that it is a "TLV-SI packet".

“Compressed IP packet” indicates that the IP header of the IP packet stored in the TLV packet is set as compressed data.
Specifically, it is an IP packet in which an IP header that omits data such as length data is set.
In the "IP (V6) packet" and "TLV-SI packet", the IP header of the IP packet stored in the TLV packet is set as uncompressed data including length data and the like.

FIG. 41 is a diagram showing an example of data of an IP header of an IP packet stored in a TLV packet containing an uncompressed type IP packet.
Further, FIG. 42 shows a data ray of packet data bytes (packet_data_byte) in the IP header shown in FIG. 41.

As shown in FIGS. 41 and 42, the IP header of the IP packet stored in the TLV packet constitutes five data sets constituting the IP data flow identification information described above with reference to FIG. 39. 5 data are recorded.
(1) Source IP address (src_IP_addless) 251
(2) Destination IP address (dest_IP_addless) 252
(3) Destination port (destination_port) 253
(4) Source port (source_port) 254
(5) Next header information (next_header) 255

An information processing device that records received data from a transmitting device such as a broadcasting server on a medium such as BD reads, for example, the recorded information of this IP header, and stores an IP packet composed of the same IP header recording information. It is possible to generate a clip AV stream file consisting of packets and record it on media.
Further, as described above with reference to FIG. 39, the IPs of the above (1) to (5) are stored in the program map PID [program_map_PID [i]] recording area of the program information [ProgramInfo ()] of the clip information file. Record data flow identification information.

Further, the PID (packet identifier) of the MPT storage packet recorded as the clip AV stream file is also recorded in the program map PID [program_map_PID [i]] recording area of the program information [ProgramInfo ()].
The PID (packet identifier) of the MPT storage packet recorded as the clip AV stream file can be obtained from the package list table (PLT) transmitted from the transmission device described above with reference to FIGS. 35 and 36. .. Alternatively, the IP header information in the TLV packet of the clip AV stream file to be recorded on the media is referred to, and the MPT storage packet matching the IP data flow identification information of the data series (channel) to be recorded on the media is extracted and extracted. The PID (packet identifier) of the packet may be recorded.

The example of the IP header of the IP packet described with reference to FIGS. 41 and 42 is an example of data configuration of the IP header in the case of an uncompressed IP packet.
Next, an example of data configuration of the IP header in the case of a compressed IP packet will be described with reference to FIGS. 43 and 44.

As shown in FIG. 43, the compressed IP header has
Context identifier (CID),
IPv6 header information UDP header information is recorded.

As shown in FIG. 44, the IPv6 header information and the UDP header information include five data sets constituting the IP data flow identification information described above with reference to FIG. 39, similar to the IP header of the uncompressed IP packet. The following five data constituting the above are recorded.
(1) Source IP address (src_IP_addless) 251
(2) Destination IP address (dest_IP_addless) 252
(3) Destination port (destination_port) 253
(4) Source port (source_port) 254
(5) Next header information (next_header) 255

An information processing device that records received data from a transmitting device such as a broadcasting server on a medium such as BD reads, for example, the recorded information of this IP header, and stores an IP packet composed of the same IP header recording information. It is possible to generate a clip AV stream file consisting of packets and record it on media.
Further, as described above with reference to FIG. 39, the IPs of the above (1) to (5) are stored in the program map PID [program_map_PID [i]] recording area of the program information [ProgramInfo ()] of the clip information file. Record data flow identification information.
Further, the program map PID [program_map_PID [i] of the program information [ProgramInfo ()] is also obtained for the PID (packet identifier) of the MPT stored packet recorded as the clip AV stream file by the same processing as the processing of the uncompressed IP packet described above. ] Record in the recording area.

Further, when the packet string recorded in the clip AV stream file is a TLV packet string including a compressed IP packet, the above-mentioned IP data flow identification information (1) to (5) is not recorded in the clip information file. Is also possible.
Instead of the IP data flow identification information of (1) to (5) above, it is the recorded data of the IP header in the case of the compressed IP packet shown in FIG. 43.
Context identifier (CID),
May be recorded in the clip information file.

The context identifier (CID) is set as an identifier unique to the IP data flow. Specifically, the above-mentioned five data, that is,
(1) Source IP address (src_IP_addless) 251
(2) Destination IP address (dest_IP_addless) 252
(3) Destination port (destination_port) 253
(4) Source port (source_port) 254
(5) Next header information (next_header) 255
Different values are set as the values of the context identifier (CID) depending on these datasets.

Therefore, the IP data flow can be identified based on the context identifier (CID).
Determines the IP data flow to which the packet belongs based on the context identifier (CID) set in the IP header of the IP packet that is a component of the packet (TLV packet / IP packet / MMTP packet) that constitutes the clip AV stream file. It becomes possible to do.
A packet in which the same CID is set in the IP header is a packet belonging to the same one IP data flow.

As described above, when the packet string recorded in the clip AV stream file is a TLV packet string including a compressed IP packet, the context identifier is used instead of the IP data flow identification information in (1) to (5) above. (CID) may be recorded in the clip information file.

FIG. 45 shows a configuration example of this clip information file.
FIG. 45 shows the data structure (syntax) of the program information [ProgramInfo ()] 203 recorded in the clip information file shown in FIG. 24, as described above with reference to FIG. 39.
The data structure (syntax) of the program information [ProgramInfo ()] 203 shown in FIG. 45 is MMT format data in which a clip AV stream file played by applying this clip information file is stored in an IP packet having a compressed IP header. This is the data structure of the program information [ProgramInfo ()] 203 in the case of.

In the data structure shown in FIG. 45, the data recording area of the data 261 to 262 corresponds to the recording area of the program map PID [program_map_PID [i]] 233 described with reference to FIG. 31.
When the clip AV stream file to be played by applying the clip information file is MMT format data stored in an IP packet having a compressed IP header, as shown in FIG. 45, the original program map PID [program_map_PID [i] ] The following data is recorded in the recording area of 233.
(1) Context identifier (CID) 261
(2) MPT storage packet identifier (MPT_PID) 262

In the above data, (1) context identifier (CID) 261 corresponds to IP data flow identification information.
This context identifier (CID) is information recorded in the compressed IP header of the IP packet stored in the TLV packet.
As described above, the context identifier (CID) is information unique to the IP data flow. For example, when a plurality of IP data flows are mixedly transmitted from the same broadcasting server, (1) the context identifier (CID) has a different value for each IP data flow.
The information processing apparatus can determine the IP data flow by referring to the context identifier (CID).

Further, after (1) identifying the IP data flow based on the context identifier (CID),
(2) MPT storage packet identifier (MPT_PID) 262
This data is read, the PID that stores the MPT corresponding to a specific IP data flow (for example, a specific channel) is read, and the packet that stores the MPT corresponding to the IP data flow (for example, a specific channel) is read based on this PID. It will be possible to identify.

When the information processing apparatus records a clip AV stream file consisting of a TLV packet string in which MMT format data is stored in a medium such as BD, the program information [ProgramInfo ()] of the clip information file corresponding to the clip AV stream file is recorded. The following data is recorded in the map PID [program_map_PID [i]] recording area.
(1) Context identifier (CID) 261
(2) MPT storage packet identifier (MPT_PID) 262

By recording these data in the clip information file, the playback device that reproduces the data from the media reads the above data (1) and (2) from the clip information file, and one IP data flow and its IP data. It is possible to select a packet that stores a flow-compatible MPT.

The (1) context identifier (CID) 261 is recorded in the compressed IP header of the IP packet stored in the TLV packet, and the recording device obtains (1) the context identifier (CID) 261 from the compressed IP header. It is acquired, recorded in a clip information file, and recorded on a medium such as BD.
Further, the playback device refers to the compressed IP header of the IP packet in the TLV packet in the clip AV stream file, reads the context identifier (CID), and records the packet (TLV packet / IP packet / MMTP packet) on the media. ) Belongs to the IP data flow.

[6-3-2. About the processing example of recording PLT information and MPT information in the program information of the clip information file]
Next, a processing example of recording PLT information and MPT information in the program information [ProgramInfo ()] recording area of the clip information file will be described.

FIG. 46 shows a configuration example of this clip information file.
FIG. 46 shows the data structure (syntax) of the program information [ProgramInfo ()] 203 recorded in the clip information file shown in FIG. 24, as described above with reference to FIGS. 39 and 45.
The data structure (syntax) of the program information [ProgramInfo ()] 203 shown in FIG. 46 is the program information [ProgramInfo ()] when the clip AV stream file to be played by applying this clip information file is MMT format data. It is a data structure of 203.

In the data structure shown in FIG. 46, the data recording area of the data 265 to 266 corresponds to the recording area of the program map PID [program_map_PID [i]] 233 described with reference to FIG. 31.
When the clip AV stream file to be played by applying the clip information file is MMT format data, as shown in FIG. 46, the following data is stored in the recording area of the original program map PID [program_map_PID [i]] 233. Record.
(1) Program list table (PLT) information (PLTInfo) 265
(2) MMT package table (MPT) information (MPTInfo) 266

Specific examples of the above data (1) and (2) are shown in FIG. 47.
FIG. 47 shows the following two data configuration examples.
(A1) Program list table (PLT) information (A2) MMT package table (MPT) information

As shown in FIG. 47, (A1) program list table (PLT) information is composed of the following data.
IP data flow identification information 271
Program list table (PLT) Packet identification information (PLT_PID) 272

The IP data flow identification information 271 is composed of the following five data sets described above with reference to FIG. 39.
(1) Source IP address (src_IP_addless)
(2) Destination IP address (dest_IP_addless)
(3) Destination port (destination_port)
(4) Source port (source_port)
(5) Next header information (next_header)

The IP data flow identification information 271 is IP data flow identification information corresponding to an IP data flow including a packet containing a program list table (PLT).
That is, it is the IP data flow identification information that makes it possible to identify the IP data flow of (A) broadcast server correspondence control information (SI) described with reference to FIGS. 32 to 34.

The program list table (PLT) packet identification information (PLT_PID) 272 is a packet identifier (PID) set in the packet storing the program list table (PLT) included in the IP data flow identified by the IP data flow identification information 271. Is.

When playing back data from media, the information processing apparatus first refers to the IP data flow identification information 271 recorded in the clip information file, so that the IP data flow including the packet containing the program list table (PLT) is included. To determine.
moreover,
Program list table (PLT) Packet identification information (PLT_PID) 272
It is possible to read this data, check the PID of the PLT storage packet included in the determined IP data flow, and identify the program list table (PLT) storage packet of the IP data flow based on this PID. ..

After that, by referring to the program list table (PLT), the PID of the MPT corresponding to each data series (each IP data flow) can be acquired.

In the configuration of this example, further, as shown in FIGS. 46 and 47, the clip information file is added.
(A2) The configuration is such that MMT package table (MPT) information is recorded.

As shown in FIG. 47, (A2) MMT package table (MPT) information is composed of the following data.
IP data flow identification information 273
MMT Package Table (MPT) Packet Identification Information (MPT_PID) 274

The IP data flow identification information 273 is composed of the following five data sets described above with reference to FIG. 39.
(1) Source IP address (src_IP_addless)
(2) Destination IP address (dest_IP_addless)
(3) Destination port (destination_port)
(4) Source port (source_port)
(5) Next header information (next_header)

The IP data flow identification information 273 is IP data flow identification information corresponding to an IP data flow including a packet containing an MMT package table (MPT).
That is, it is the IP data flow identification information that makes it possible to identify the IP data flow of (B) or (C) described with reference to FIGS. 32 to 34.

The MMT package table (MPT) packet identification information (MPT_PID) 274 is a packet identifier (PID) set in the packet containing the MMT package table (MPT) included in the IP data flow identified by the IP data flow identification information 272. Is.

When playing back data from the media, the information processing apparatus determines the IP data flow including the packet containing the MMT package table (MPT) by referring to the IP data flow identification information 273 recorded in the clip information file. do.
moreover,
MMT Package Table (MPT) Packet Identification Information (MPT_PID) 274
This data can be read, the PID of the MPT storage packet included in the determined IP data flow can be confirmed, and the MMT package table (MPT) storage packet of the IP data flow can be specified based on this PID. ..

After that, by referring to the MMT package table (MPT), it is possible to acquire a PID for each asset (image, sound, subtitle, etc.) corresponding to one IP data flow.

When the information processing apparatus records a clip AV stream file consisting of a TLV packet string in which MMT format data is stored in a medium such as BD, the program information [ProgramInfo ()] of the clip information file corresponding to the clip AV stream file is recorded. The following information shown in FIG. 47 is recorded in the map PID [program_map_PID [i]] recording area.
(A1) Program list table (PLT) information (A2) MMT package table (MPT) information

By recording these data in the clip information file, the playback device that reproduces the data from the media reads the above data (A1) and (A2) from the clip information file.
The reproduction device determines the IP data flow of the program list table (PLT) stored packet based on these data, and the program list table (PLT) is based on the packet identifier (PID) of the program list table (PLT) stored packet. ) Can be obtained.
Further, the IP data flow of the MMT package table (MPT) stored packet can be determined, and the MMT package table (MPT) can be acquired based on the packet identifier (PID) of the MMT package table (MPT) stored packet.

FIG. 48 shows the clip information file shown in FIG. 46.
(1) Program list table (PLT) information (PLTInfo) 265
(2) MMT package table (MPT) information (MPTInfo) 266
It is a figure which shows another specific example of the said data (1), (2).

The example shown in FIG. 48 is an example of PLT information and MPT information applicable when the packet stored in the clip AV stream file is MMT format data having a compressed IP header.
FIG. 48 shows the following two data configuration examples.
(B1) Program list table (PLT) information (B2) MMT package table (MPT) information

As shown in FIG. 48, (B1) program list table (PLT) information is composed of the following data.
Context identifier (CID) 276
Program list table (PLT) Packet identification information (PLT_PID) 277

The context identifier (CID) 276 is used as IP data flow identification information as described above.
The context identifier (CID) 276 is used as IP data flow identification information corresponding to an IP data flow including a packet containing a program list table (PLT).

Further, (B2) MMT package table (MPT) information is composed of the following data.
Context identifier (CID) 278
MMT Package Table (MPT) Packet Identification Information (PLT_PID) 279
The context identifier (CID) 278 is used as IP data flow identification information corresponding to the IP data flow including the packet containing the MMT package table (MPT).

When the information processing apparatus records a clip AV stream file consisting of a TLV packet string storing MMT format data stored in an IP packet having a compressed IP header on a medium such as BD, the clip information corresponding to the clip AV stream file is recorded. The following information shown in FIG. 48 is recorded in the program map PID [program_map_PID [i]] recording area of the program information [ProgramInfo ()] of the file.
(B1) Program list table (PLT) information (B2) MMT package table (MPT) information

By recording these data in the clip information file, the playback device that reproduces the data from the media reads the above data (B1) and (B2) from the clip information file.
The reproduction device determines the IP data flow of the program list table (PLT) stored packet based on these data, and the program list table (PLT) is based on the packet identifier (PID) of the program list table (PLT) stored packet. ) Can be obtained.
Further, the IP data flow of the MMT package table (MPT) stored packet can be determined, and the MMT package table (MPT) can be acquired based on the packet identifier (PID) of the MMT package table (MPT) stored packet.

[6-3-3. Stream coding information recorded in the program information of the clip information file]
Next, the stream coding information recorded in the program information of the clip information file will be described.
As previously described with reference to FIG.
The stream coding information [Stream Coding Info] 215 recorded in the program information [Program Info ()] of the clip information file shown in FIG. 31 records the coding (encoding) information of the stream to be reproduced.

FIG. 49 is a diagram showing a data structure (syntax) of stream coding information [Stream Coding Info] set in the program information [Program Info ()] recording area of the clip information file.
The following data is recorded in the stream coding information [StreamCodingInfo].
(1) Image stream coding information 281
(2) Audio stream coding information 282,

Various types are allowed for the image stream recorded on the information recording medium (media) and the coding mode (coding type) of the audio stream, and an identifier corresponding to each coding type is given in advance for both the image and the audio. It is stipulated.
The image is associated with, for example, type identifiers = 0x01, 0x02, 0x1B, etc., depending on the coding type (encoding type).
The voice is associated with type identifiers = 0x03, 0x04, 0x0F, 0x80, 0x81 and the like according to the coding type (encoding type).

FIG. 50 shows an example of setting the coding type of the image stream and the audio stream defined by the current BDAV format.
For example, the coding type 0x01 is an MPEG-1 image stream, 0x02 is an MPEG-2 image stream, 0x03 is an MPEG-1 audio stream, and the like.

In the MMT format, HEVC coding, which is an image coding type not specified in the current BDAV format, is used.
Further, in the MMT format, MPEG-4 AAC coding and MPEG-4 ALS coding, which are audio coding types not specified in the current BDAV format, are used.
It is necessary to newly assign a coding type identifier to these coding types as well.

FIG. 50 shows a setting example of the coding type identifier of the new coded data of these MMT format data.
Coding type = 0x10 = MPEG-4 AAC coded audio data Coding type = 0x11 = MPEG-4 ALS coded audio data Coding type = 0x24 = HEVC coded image data For example, new coding used in the MMT format as described above. Set the data coding type identifier.

Returning to FIG. 49, the description of the stream coding information [StreamCodingInfo] will be continued.
(1) The information recorded as the image stream coding information 281 is the following information.
(1a) Video format (video_format)
(1b) Frame rate
(1c) Aspect ratio (aspect_ratio)

These pieces of information are information about an image recorded on an information recording medium (media). Further, when the media recorded image has a format different from the input image (original image), for example, when the input image (original image) is data obtained by performing format conversion or the like, the above image information is used. In addition, the following information is also recorded as information on the original image before conversion, that is, information on the original image input by the information processing apparatus in a broadcast wave or the like.
(1d) Original video format (original_video_format)
(1e) Original aspect ratio (original_assist_ratio)

On the other hand, the information recorded as (2) audio stream coding information 282 is the following information.
(2a) Voice type (audio_presentation_type)
(2b) Sampling_frequency

As described above with reference to FIG. 50, as the MMT format data, new encoded data which is not specified in the current BDAV format is used.
It is the following coded data described with reference to FIG.
Coding type = 0x10 = MPEG-4 AAC coded audio data Coding type = 0x11 = MPEG-4 ALS coded audio data Coding type = 0x24 = HEVC coded image data

It is also necessary to record the coding type of the new coded data used in such an MMT format in the stream coding information [Stream Coding Info] shown in FIG. 49.
FIG. 49 shows the following information recording area as the information recording area of these new coded data.
HEVC coded data related information recording area 283,
MPEG-4 AAC, ALS coded data related information recording area 284,

In this way, a new information recording area is set, and the above-mentioned information (1a) to (1e) is recorded for the image data, and the above-mentioned information (2a) to (2b) is recorded for the audio data.
As for the HEVC image data, it is preferable to further record additional information in each of the above-mentioned information (1a) to (1e).
An example of stream coding information [StreamCodingInfo] recorded data for HEVC image data will be described with reference to FIG. 51.

The information recorded as stream coding information for the HEVC image is the following information as shown in FIG. 51 (a).
(1) Video format (video_format)
(2) Frame rate
(3) Aspect ratio (aspect_ratio)
(4) Video signal transmission characteristics (video_transfer_charctics)

These pieces of information are information about an image recorded on an information recording medium (media). Further, when the media recorded image has a format different from the input image (original image), for example, when the input image (original image) is data obtained by performing format conversion or the like, the above image information is used. In addition, the following information is also recorded as information on the original image before conversion, that is, information on the original image input by the information processing apparatus in a broadcast wave or the like.
(5) Original video format (original_video_format)
(6) Original aspect ratio (original_assist_ratio)
(7) Original video signal transmission characteristics (original_video_transfer_chartactics)

FIG. 51 (b) is a diagram showing specific recording examples and meanings of video signal transmission characteristics (video_transfer_charctics).
Any value from 0 to 15 is set as the video signal transmission characteristic (video_transfer_charctics). The meaning of each set value is as follows.
0: Not specified 1: VUI transmission characteristics (transfer_charctics) = 1 (Rec. ITU-R BT.709-5)
2: VUI transmission characteristics (transfer_charctics) = 11 (IEC 61966-2-4)
3: VUI transmission characteristics (transfer_charctics) = 4 (Rec. ITU-R BT. 2020)
4: VUI transmission characteristics (transfer_charctics) = 6 (SMPTE ST 2084)
5: VUI transmission characteristics (transfer_charctics) = 8 (ARIB STD-B607)
6-15: Reserve

This video signal transmission characteristic (video_transfer_charctics) is information indicating the correspondence between the input signal value and the output signal.
Rec. ITU-R BT. 709-5, IEC 61966-2-4, Rec. ITU-R BT. 2020, SMPTE ST 2084, and ARIB STD-B607 all show input / output characteristic curves showing the correspondence between the input signal and the output signal, and each has different characteristics.
It becomes possible to know the input / output characteristics of the HEVC-encoded image according to any of 0 to 15 in the set value of the video signal transmission characteristics (video_transfer_charctics).

As described with reference to FIG. 49, the following data is recorded in the stream coding information [StreamCodingInfo] set in the program information [ProgramInfo ()] recording area of the clip information file.
(1) Image stream coding information 281
(2) Audio stream coding information 282,

(1) The information recorded as the image stream coding information 281 is the following information.
(1a) Video format (video_format)
(1b) Frame rate
(1c) Aspect ratio (aspect_ratio)
(1d) Original video format (original_video_format)
(1e) Original aspect ratio (original_assist_ratio)

The data received by the information processing apparatus, for example, in a broadcast wave or the like is MMT format data, and includes image data in a data format that has not been defined in the conventional BDAV format.
Therefore, it is necessary to change or add each of the image information (1a) to (1e) according to the image format stored in the MMT format data.
An example of this modification will be described with reference to FIGS. 52 and below.

FIG. 52 is a diagram showing an example of changing the following data recording area.
(1a) Video format (video_format)
(1d) Original video format (original_video_format)
FIG. 52 shows an example of the following recorded data.
(P) Conventional image format recording data (q) New image format recording data

(P) The conventional image format recording data has the following settings.
It is a setting in which each of the bit values 0 to 15 is associated with each image mode of 480i, 576i, 480p, 1080p, 720p, and 1080p.
Note that i means an isntalase type, p means a progressive type image output configuration, and numerical values 480, 576 and the like mean the number of pixels in the horizontal direction of the image.
1080p is a progressive image having 1080 pixels in the horizontal direction.

(Q) The new image format recording data is a setting in which the definition of a 4K image or an 8K image is further added to the above-mentioned (p) conventional image format recording data. The following additional data 286 shown in the figure has been added.
Bit value: 7 = 2160p
Bit value: 8 = 4380p
2160p is a 4K image and 4380p corresponds to the image format of an 8K image.
These are the latest image formats that may be delivered according to the MMT format.
By adding these new definition data, the correct image data format (coding information) is recorded in the stream coding information in the clip information file specified in the BDAV format even for the latest format images delivered according to the MMT format. Is possible.

FIG. 53 is a diagram showing an example of changing the following data recording area.
(1b) Frame rate
FIG. 53 shows an example of the following recorded data.
(P) Conventional frame rate recording data (q) New frame rate recording data

(P) The conventional frame rate recording data has the following settings.
It is a setting in which each image having a frame rate of 24000/1001 (23.976) to 60 Hz is associated with each of the bit values 0 to 15.
(Q) The new frame rate recording data is a setting in which definition data of a higher frame rate is added to the above-mentioned (p) conventional frame rate recording data. The following additional data 287 shown in the figure has been added.
Bit value: 9 = 120000/1001 (119.94) Hz
Bit value: 10 = 120Hz
These data are definition information of image data having a high frame rate of about 120 Hz.
These are the latest image formats that may be delivered according to the MMT format.

By adding these new definition data, the correct image data format (coding information) is recorded in the stream coding information in the clip information file specified in the BDAV format even for the latest format images delivered according to the MMT format. Is possible.

FIG. 54 is a diagram showing a recording example of the following data.
(1c) Aspect ratio (aspect_ratio)
(1e) Original aspect ratio (original_assist_ratio)
Regarding this aspect ratio, the distribution data according to the MMT format is also within the definition data range of the conventional BDAV format, and there is no particular need to change it.
As shown in FIG. 54, data having an aspect ratio of 4: 3, 16: 9, and 2.21: 2 can be recorded in each of the bit values 0 to 15.

Further, as described with reference to FIG. 49, the stream coding information [StreamCodingInfo] set in the program information [ProgramInfo ()] recording area of the clip information file includes
(2) Audio stream coding information 282,
Is recorded.

(2) The information recorded as the audio stream coding information 282 is the following information.
(2a) Voice type (audio_presentation_type)
(2b) Sampling_frequency

An example of recording each of these data will be described with reference to FIG. 55.
FIG. 55 (a) The voice type recording data has data settings capable of identifying various voice type information such as monochannel, stereo, and surround with respect to bit values 0 to 15.
FIG. 55 (b) is a data setting in which each sampling frequency of 48 to 192 kHz can be identified with respect to bit values 0 to 15.
Regarding these audio data formats, the distribution data according to the MMT format is also within the range of the definition data in the current BDAV format, and no particular change is required.

As described above, it is necessary to record the stream coding information [StreamCodingInfo] set in the program information [ProgramInfo ()] recording area in the clip information file specified in the BDAV format.
Specifically, as described with reference to FIG. 49 et al., It is required to record the following data.
(1) Image stream coding information,
(2) Audio stream coding information,
In these stream coding information, it is necessary to record information corresponding to HEVC image data newly used in MMT format data and information about MPEG-4-AAC and ALS-encoded audio data.

The information processing device can apply these stream coding information to confirm the attributes of the image data and audio data to be reproduced, and perform decoding processing and reproduction processing according to the confirmed image attributes and audio attributes. It becomes.

For example, an information processing device that receives distribution content (program) from a broadcasting station in MMT format data and records the received content on an information recording medium (media) is such that the above image attribute information is obtained from the received data according to the MMT format data. It is necessary to extract (image stream coding information) and information corresponding to audio attribute information (audio stream coding information) and generate a clip information file in which these data are recorded.

As described above with reference to FIG. 2 and others, the MMT format data includes setting information required for receiving contents (programs) on the information processing apparatus 30 side, guidance information such as a program guide, and notifications. Control information (SI) composed of information, control information, and the like is included.

The information processing apparatus 30 that receives the MMT format data and records the received data on the media has the above-mentioned image attribute information (image stream coding information) from the control information such as TLV-SI and MMT-SI included in the MMT format. And, the data corresponding to the information corresponding to the voice attribute information (voice stream coding information) is extracted, and a clip information file in which these data are recorded is generated.

[6-4. About CPI information recorded in the clip information file]
Next, the CPI information recorded in the clip information file will be described.
As described above with reference to FIG. 24, the CPI information [CPI ()] 204 is recorded in the clip information file.
The CPI information [CPI ()] 204 is, for example, data for acquiring the data address of the reproduction start point, and EP_map and TU_map described above with reference to FIGS. 13 to 15 are recorded.

As described above with reference to FIG. 12, the CPI type (CPI_type) is recorded in the playlist file. The CPI type (CPI_type) is information indicating the CPI type in the clip information file referred to by the play item (PlayItem) specified in the playlist file.
The CPI (Characteristic Point Information) is recorded data of a clip information file, and is, for example, data for acquiring a data address of a reproduction start point at which random access reproduction can be started.

The data structure (syntax) of the CPI information [CPI ()] 204 recorded in the clip information file described above with reference to FIG. 24 will be described with reference to FIG. 56.

The CPI information [CPI ()] 204 is, for example, data for acquiring the data address of the reproduction start point, and EP_map and TU_map described above with reference to FIGS. 13 to 15 are recorded.
As described above, the CPI (Characteristic Point Information) is the recorded data of the clip information file, and is, for example, the data for acquiring the data address of the reproduction start point.

As shown in FIG. 56, when the CPI type = 1, the EP map is recorded, and when the CPI type = 2, the TU map is recorded.
The example shown in FIG. 56 is an example when the data to be reproduced is MPEG-2 TS format data. As described above with reference to FIG. 16, when the reproduction target data is MPEG-2 TS format data, there is a setting of CPI type = 1 and 2, and both the EP map and the TU map are set to be usable. To.

On the other hand, when the data to be reproduced is MMT format data, the CPI type = 3 is set as described above with reference to FIG. 16, and only the EP map can be used.

As described above with reference to FIGS. 13 to 15, the EP map has access point information corresponding to a playback start position and a playback end position in which random playback can be started in the playback data stored in the clip AV stream file. It is a map that records.
That is, the EP map contains a time stamp (PTS: presentation time stamp) expressing the playback start position on the time axis and address information (SPN: source packet number) for acquiring a packet corresponding to the packet position information. Corresponding data is recorded.

By using the EP map, the playback device uses the packet number (SPN) of the packet that stores the data corresponding to the data position based on the time stamp (PTS: presentation time stamp) corresponding to the randomly accessible data position. ), And the acquired SPN setting packet can be acquired and played back.

The data structure (syntax) of the EP map will be described with reference to FIG. 57.
FIG. 57 is a diagram showing a data structure (syntax) of the EP map stored in the clip information file.
As described above with reference to FIG. 14A, the clip AV stream is a multiplexed video stream composed of a source packet identified by a packet identifier: PID. The video stream is distinguished for each source packet by the PID contained in the header of the transport packet in the source packet.

The EP map is set for each stream identified by the packet identifier (PID).
A packet identifier (PID) for stream identification is recorded in the stream PID (stream_PID [k]) recording area 289 of the EP map shown in FIG. 57.
Further, an EP map (EP_map_for_one_stream_PID) for each stream is recorded in the EP map recording area 290 of FIG. 57.

However, when the data to be reproduced by the EP map is MMT format data, that is, when the TLV packet string storing the MMT format data is stored in the clip AV stream file, the clip AV stream file has a plurality of IPs. There is a possibility that packets corresponding to the data flow may be mixed, and in this case, the packet identifier (PID) may be duplicated.

That is, as described above with reference to FIGS. 32 to 34, the packet identifier (PID) is set in units of IP data flows, and a plurality of IP data flows, for example, a plurality of data sequences shown in FIG. 34 ( Distribution processing may be performed in which A) to (C) are set as different IP data flows.
When the information processing device 30 which is a receiving device on the user side records all these data packets as one clip AV stream file on a medium such as BD, one packet having the same packet identifier (PID) is set. It will be present in the clip AV stream file.

Therefore, when the data to be reproduced by the EP map shown in FIG. 57 is MMT format data, only the packet identifier (PID) for stream identification is stored in the stream PID (stream_PID [k]) recording area 289 of the EP map shown in FIG. 57. There is a possibility that correct playback will not be performed even if the data is recorded.

In order to solve this problem, when the data to be reproduced by the EP map is MMT format data, information for identifying the IP data flow is recorded in the EP map.
FIG. 58 shows a data configuration example of the EP map corresponding to the MMT format data.

The EP map corresponding to the MMT format data shown in FIG. 58 includes
The IP data flow identification information 291 is recorded, and then the recording area of the stream PID (stream_PID) is set.
The IP data flow identification information 291 is the same IP data flow identification information as the data of the program information [ProgramInfo ()] recorded in the clip information file described above with reference to FIG. 39 and others.

The IP data flow identification information 291 is information for identifying the IP data flow to which the packet selected by the stream PID (stream_PID) recorded immediately after the IP data flow identification information 291 belongs.

The IP data flow identification information 291 is composed of the following data set.
(1) Source IP address (src_IP_addless)
(2) Destination IP address (dest_IP_addless)
(3) Destination port (destination_port)
(4) Source port (source_port)
(5) Next header information (next_header)
These data are IP packet correspondence information corresponding to the IP packet stored in the TLV packet. The next header information (next_header) is a recording area for protocol type information, and a fixed value [00010001] indicating UDP is recorded.

The data set composed of the data of (1) to (5) is information peculiar to the IP data flow. For example, when a plurality of IP data flows are mixedly transmitted from the same broadcasting server, the data sets of (1) to (5) have different settings for each IP data flow.

By referring to this data, the information processing apparatus identifies the IP data flow to which the set packet of the stream PID (stream_PID) recorded following the IP data flow identification information 291 belongs.
After this IP data flow identification, the stream PID (stream_PID) setting packet is selected to detect the packet containing the random access reproduction target data.

FIG. 59 is a data structure of an EP map when the clip AV stream file reproduced by applying this EP map is MMT format data stored in an IP packet having a compressed IP header.

When the clip AV stream file to be played by applying the clip information file is MMT format data stored in an IP packet having a compressed IP header, as shown in FIG. 59, the EP map contains
The context identifier (CID) 292 is recorded, after which the recording area of the stream PID (stream_PID) is set.
The context identifier (CID) 292 is used as IP data flow identification information, as described above with reference to FIG. 45 and others.

The information processing apparatus can determine the IP data flow by referring to the context identifier (CID).
By referring to the context identifier (CID) 292 recorded in the EP map, the information processing apparatus determines the IP data flow to which the stream PID (stream_PID) setting packet recorded following the context identifier (CID) 292 belongs. Identify.
After this IP data flow identification, the stream PID (stream_PID) setting packet is selected to detect the packet containing the random access reproduction target data.

Next, the recorded data of the EP map recording area 290 in the EP map shown in FIG. 57 will be described.
As described above, specific EP map data (EP_map_for_one_stream_PID) for each stream is recorded in the EP map recording area 290.
A data configuration example of EP map data (EP_map_for_one_stream_PID) corresponding to the MMT format will be described with reference to FIG. 60.

In the conventional EP map compatible with MPEG-2 TS format data, as described above with reference to FIG. 12 and below, the playback start position and playback in which random playback can be started in the playback data stored in the clip AV stream file are displayed. The access point information corresponding to the end position is recorded.
That is, in the conventional EP map for TS packets, a time stamp (PTS: presentation time stamp) expressing the playback start position on the time axis and address information (SPN) for packet acquisition corresponding to the packet position information are provided. : Source packet number) and the corresponding data are recorded.

By using the EP map, the playback device uses the packet number (SPN) of the packet that stores the data corresponding to the data position based on the time stamp (PTS: presentation time stamp) corresponding to the randomly accessible data position. ), And the acquired SPN setting packet can be acquired and played back.

However, the recorded data of this EP map is data applicable when the reproduction target data is MPEG-2 TS format data, and cannot be used as it is when the reproduction target data is MMT format data.
FIG. 60 shows an example of an EP map corresponding to MMT format data.

FIG. 60 shows data recorded in the EP map recording area 290 in the EP map shown in FIG. 57 when the reproduction target data is MMT format data.
As shown in FIG. 60
(A) The EP map example corresponding to MMT format data has the following fields as data recording fields.
NTP time recording area (NTP_time) 293,
TLV byte address recording area (TLV_byte_address) 294,

A 64-bit NTP (Network Time Protocol) time is recorded in the NTP time recording area (NTP_time) 293.
This time information corresponds to, for example, a time stamp (PTS: presentation time stamp) expressing the reproduction start position of the random access destination included in the reproduction data reproduced by applying this EP map on the time axis.
The time information according to NTP (Network Time Protocol) recorded in the EP map is acquired from control information (SI) such as MPT (MMT package table) described above with reference to FIG. 19 and others. To.

In the TLV byte address recording area (TLV_byte_address) 294, address information indicating the packet position of the TLV packet storing the reproduction target data to be reproduced by applying this EP map is recorded.
Specifically, the first packet (TLV packet) of the clip AV stream file in which this packet is stored as the position information of the playback target data storage packet (TLV packet) such as an image (V), an audio (A), or a subtitle. ) Record the number of bytes from the beginning position. For example, the number of bytes is recorded in 64 bits.

The playback device is
MMT byte address recording area (MMT_byte_address) 294,
Using this data, it is possible to immediately detect the packet position of the regenerated data storage packet.

For example, as shown in FIG. 61, it is assumed that a clip AV stream file composed of a TLV packet string storing MMT format data is recorded on a recording medium such as BD.
In the TLV byte address recording area (TLV_byte_address) 294, the number of bytes from the start position of the first packet (TLV packet) of the clip AV stream file in which the TLV packet containing the randomly accessible reproduction data is stored is recorded.

The TLV packet storing the randomly accessible reproduction data can be discriminated based on the setting of the RAP (random access point) flag set in the packet header of the MMTP packet in the TLV packet.

FIG. 62 is a diagram showing a data structure (syntax) of an MMTP packet constituting MMT format data transmitted from a transmission device 20 such as a broadcasting station to an information processing device 30.

As described above with reference to FIG. 3, the MMTP packet is composed of the MMTP header and the MMTP payload. One type of data is stored in the MMTP payload of one MMTP packet. Specifically, for example, image (V), audio (A), subtitle (S), control information (MMT-SI) stored in an MMTP packet, or any one of these types of data is stored in an individual MMTP packet. Will be done.

FIG. 62 shows the data structure of one MMTP packet, which is composed of a header unit 296 and a payload unit 297.
Information such as the type of data stored in the payload unit 297 is recorded in the header unit 296. A random access point information flag (RAP_flag) 298 is recorded as one of the recorded data in the header unit 296.

Random access point information flag (RAP_flag) 298
It is a flag indicating whether or not the MMTP packet is a packet that stores data that becomes a random access point.
If the packet contains data that serves as a random access point, 1.
0 if it is not a packet that stores data that will be a random access point.
Flags for this setting are recorded.

For example, a playback device that reproduces the data recorded on the media checks the random access point information flag (RAP_flag) recorded in the MMTP packet header of the packet string constituting the clip AV stream file, and confirms the random access point information flag (RAP_flag). It is possible to store possible reproduction data and detect packets.

As explained earlier with reference to FIG. 14, the EP map compatible with the MPEG-2 TS format is available.
It is a configuration in which the correspondence data between PTS (presentation time stamp) and SPN (source packet number) is recorded.
On the other hand, in the MMT format, as described with reference to FIG. 60,
Instead of PTS, use NTP (Network Time Protocol) time,
Instead of SPN, the TLV byte address is used.

The reason for replacing the data in this way is that the data transmitted from the broadcasting station or the like according to the MMT format does not have data that matches the PTS or SPN specified in the MPEG-2 TS format. Another reason is that the size of the TS packet in the MPEG-2 TS format is fixed (188 bytes), whereas the MMTP packet according to the MMT format is a variable length packet that is not fixed.

[7. Configuration and processing of information processing equipment that executes data recording processing for information recording media]
Next, the configuration and processing of the information processing apparatus that executes the data recording processing for the information recording medium will be described with reference to FIGS. 63 and below.

As described above, the information processing apparatus of the present disclosure records input data according to the MMT format as BDAV format data on an information recording medium such as BD, HD, or a flash memory.
Further, in this data recording process, control information, attribute information, etc. corresponding to MMT format data are recorded in a database file such as a playlist or a clip information file.

These information are acquired from, for example, TLV-SI, which is control information included in the input data according to the MMT format, and various information recording tables constituting the MMT-SI. The information processing apparatus acquires various information from the received data and records the information corresponding to the media recording content in a database file such as a playlist or a clip information file defined in the BDAV format.

Hereinafter, the configuration and processing sequence of the information processing apparatus that executes the generation processing of the information recording medium in which such playlists and clip information files are recorded, specifically, the data recording processing for the information recording medium such as BD, will be described. do.

FIG. 63 is a diagram showing a configuration of an information processing apparatus 300 that executes data recording processing on an information recording medium such as a BD.
The information processing apparatus 300 records a clip AV stream file and a database file such as a playlist or a clip information file on the information recording medium (recording medium) 320.

The data input unit 301 inputs MMT format data 331 for the information recording medium 320, that is, MMT format data 331 including image data, audio data, subtitle data, and the like.
The data input unit 301 is a receiving unit that transmits MMT format data 331, for example, a receiving unit that receives transmission data from a broadcasting station, a content server, or the like, or a media reading unit that reads data from a medium that records MMT format data 331. Etc.

The MMT format data 331 input from the data input unit 301 is data according to the data format described above with reference to FIG. 2, and includes high-definition image data such as a HEVC image.

The MMT format data 331 is stored in the storage unit 304 under the control of the control unit 303.
The user input unit 302 inputs, for example, a request for starting data recording to the information recording medium 320.

When a data recording start request is input from the user input unit 302, the MMT format data 331 stored in the storage unit 304 is input to the demultiplexer (DeMUX) 305 using this input as a trigger.
The demultiplexer (DeMUX) 305 uses MMT format data 331 to a packet containing data such as images, sounds, and subtitles, control information (TLV-SI, MMT-SI) containing notification information, control information, and the like. Auxiliary information is acquired, classified into packets of data type, and each packet is classified into subtitle data generation unit 311 of recorded data generation unit 306, image data generation unit 312, audio data generation unit 313, and auxiliary data according to the data type. It is input to the information generation unit 314.

The subtitle data generation unit 311 acquires subtitle data from the MMT format data 331 input by the data input unit 301 and stored in the storage unit 304, and generates stream file storage data specified in the BDAV format.
The image data generation unit 312 acquires image data from the MMT format data 331 input by the data input unit 301 and stored in the storage unit 304, and generates stream file storage data specified in the BDAV format.
The audio data generation unit 313 acquires audio data from the MMT format data 331 input by the data input unit 301 and stored in the storage unit 304, and generates stream file storage data specified in the BDAV format.

The auxiliary information generation unit 314 receives control information (TLV-SI, MMT-SI) and the like from the MMT format data 331 input by the data input unit 301 and stored in the storage unit 304, such as notification information and control information. Acquires auxiliary information and generates data to be stored in a playlist file, a clip information file, or a clip AV stream file as a database file specified in the BDAV format.

In the multiplexer (MUX) 315, the subtitle, image, and audio data converted by the subtitle data generation unit 311, the image data generation unit 312, and the audio data generation unit 313, and the auxiliary information generation unit 314 control information (MMT format data 331). Various information acquired from TLV-SI, MMT-SI), etc. is input, and a stream file containing these data is generated.

The database file generation unit 316 stores database files such as a playlist file and a clip information file that record various information acquired from the control information (TLV-SI, MMT-SI) of the MMT format data 331 by the auxiliary information generation unit 314. Generate.

The stream file data generated by the recording data generation unit 306 and the recording data 332 including the database files such as the playlist file and the clip information file are informationed by the recording unit 306 via the drive 307 under the control of the control unit 303. It is output to the recording medium 320 and recorded.

Next, a sequence of data recording processing for the information recording medium 320 executed by the information processing apparatus 300 shown in FIG. 63 will be described with reference to the flowchart shown in FIG.

The processing according to the flow shown in FIG. 64 may be executed under the control of a data processing unit (control unit) having a CPU having a program execution function, for example, according to a program stored in the storage unit of the information processing apparatus. can.
Hereinafter, the processing of each step shown in the flow of FIG. 64 will be sequentially described.

(Step S101)
First, in step S101, the information processing apparatus 300 inputs MMT format data, which is recording data, via the data input unit 301.
The recording data includes image data, audio data, subtitle data, and control information (TLV-SI, MMT-SI) storing notification information, control information, and the like.

(Step S102)
Next, in step S102, the information processing apparatus 300 performs demultiplexing processing of the input MMT format data, that is, data separation processing for each data type. Performs separation processing for images, sounds, subtitles, control information, etc.

(Step S103)
Next, in step S103, the information processing apparatus 300 stores the control information separated in step S102, for example, the control information (TLV-SI, MMT-SI) in the memory.

(Step S104)
Next, in step S104, the information processing apparatus 300 executes a re-encoding process of at least one of the image, audio, and subtitle nuclear data separated in step S102.
It should be noted that this process is a process performed when the encoding mode of the data to be recorded in the information recording medium is changed, and this re-encoding process is not necessary when the received data is recorded as it is.

(Step S105)
Next, in step S105, the information processing apparatus 300 executes a data multiplexing process including images, sounds, subtitles, reproduction control information, and the like including the encoded data in step S103. That is, the clip AV stream file generation process is executed.
The reproduction control information stored in the clip AV stream file includes, for example, the MPT (MMT package table) described with reference to FIG.

(Step S106)
Next, in step S106, the information processing apparatus 300 generates a clip information file by using the configuration data of the input MMT format data.
For example, the clip information file described above with reference to FIGS. 24 to 62, that is, the clip information file corresponding to the clip AV stream file storing the MMT format data is generated.

The detailed sequence of the clip information file generation process in step S106 will be described in detail later with reference to the flow shown in FIG. 65.

(Step S107)
Next, in step S107, the information processing apparatus 300 generates a playlist file by using the configuration data of the input MMT format data.
For example, a playlist file described above with reference to FIGS. 12 to 23, that is, a playlist file corresponding to a clip AV stream file storing MMT format data is generated.
The details of the playlist file generation process in step S107 will be described later with reference to FIG. 66.

(Step S108)
Next, in step S108, the information processing apparatus 300 uses the input MMT format data to generate other database files.

(Step S109)
Next, in step S109, the information processing apparatus 300 generates BDAV format data using the generated AV stream file and database file.

(Step S110)
Next, in step S110, the information processing apparatus 300 records the BDAV format data generated in step S109 on the information recording medium (media).

Next, a detailed sequence of the clip information file generation process executed in step S106 will be described with reference to the flowchart shown in FIG.
The flowchart shown in FIG. 65 is a clip information generation sequence used for controlling a clip AV stream file storing MMT format data.
The processing of each step of the flow shown in FIG. 65 will be sequentially described.

(Step S121)
First, in step S121, the information processing apparatus 300 confirms the RAP (random access point) flag of the MMTP packet which is the MMT format data stored in the clip AV stream file.
This process is the process described above with reference to FIG. 61.
The MMTP packet for which the RAP flag = 1 is set is data including a random access point.

(Step S122)
Next, in step S122, the information processing apparatus 300 generates an EP map based on the correspondence data between the packet position of the MMTP packet in which the RAP flag = 1 is set and the time information (NTP time).
This process is an EP map generation process corresponding to the MMT format data described above with reference to FIGS. 56 to 61. The packet position information uses the byte position from the beginning of the clip AV stream file (= the beginning of the first TLV packet stored in the file). Further, the time information uses NTP (Network Type Protocol) time.

(Step S123)
Next, in step S123, the information processing apparatus 300 sets the values of the application type (Application_type) of the clip information file and the clip stream type (Clip_stream_type) to [3].

This process is the process described above with reference to FIGS. 25 to 27, and is for making it possible to identify that the stored data of the clip AV stream file, which is the controlled data of the clip information file, is the MMT format data. It is a process to record the set value of.

(Step S124)
Next, in step S124, the information processing apparatus 300 records the recording rate (recording_rate) and the average rate (average_rate) of the clip information file.

This process is performed by the TS average rate (TS_avage_rate) 214, which has been described above with reference to FIG. 25.
TS recording rate (TS_recording_rate) 215,
These data recording processes. As described above, the average bit rate of the transport stream of the clip AV stream file, which is the data to be reproduced by this clip information file, and the recording rate are expressed in units of bytes / seconds.

This bit rate information is premised on being calculated based on the TS packet, and when the reproduction target data is MMT format data having an MMT packet or a TLV packet, the bit rate corresponding to the MMT format is calculated and recorded. .. Alternatively, if the data to be reproduced is in the MMT format, an invalid value may be recorded in this field and the bit rate information may not be used.

(Step S125)
Next, in step S125, the information processing apparatus 300 is the configuration data of the clip information file.
Clip Information (ClipInfo),
Sequence Information (SequenceInfo),
Program Information (ProgramInfo),
CPI Information (CPI),
ClipMark,
Generate each of these data.
In each of these data generation processes, when the data to be reproduced is MMT format data, for example, the time information is NTP time information, and the packet position is the first TLV packet stored in a stream file (clip AV stream file). Acquires and records the number of bytes data from the beginning of.

Further, each of the above information includes a plurality of packet identifier (PID) recording areas, but when the reproduction target data is MMT format data, the following data is recorded in the packet identifier (PID) recording area.

As described with reference to FIGS. 39 to 48, any of the following data is recorded in the packet identifier (PID) recording area (program map PID recording area) of the program information (ProgramInfo).
(A) IP data flow identification information and packet identifier (MPT_PID) of the packet stored in the MMT package table (MPT).
(B) Package list table (PLT) information and MMT package table (MPT) information

The IP data flow identification information in (a) above is composed of the following data as described above with reference to FIG. 39 and others.
(1) Source IP address (src_IP_addless)
(2) Destination IP address (dest_IP_addless)
(3) Destination port (destination_port)
(4) Source port (source_port)
(5) Next header information (next_header)

Alternatively, as described with reference to FIG. 45 et al., Recorded in the compressed IP header.
(1) Context identifier (CID),
May be recorded as IP data flow identification information.

Further, as described with reference to FIGS. 56 to 62, the packet identifier (PID) recording area (stream PID recording area) of the EP map [EP_map ()] recording area in the CPI information (CPI) is as follows. Record the data of.
(A) IP data flow identification information and packet identifier (stream_PID)

The IP data flow identification information in (a) above is composed of the following data as described above with reference to FIG. 58 and others.
(1) Source IP address (src_IP_addless)
(2) Destination IP address (dest_IP_addless)
(3) Destination port (destination_port)
(4) Source port (source_port)
(5) Next header information (next_header)

Alternatively, as described with reference to FIG. 59 et al., Recorded in the compressed IP header.
(1) Context identifier (CID),
May be recorded as IP data flow identification information.

By recording the above data in the clip information file, one IP data flow can be specified even if multiple IP data flows are mixed in the clip AV stream file and include packets with the same packet identifier. This makes it possible to reliably select the packets included in the IP data flow.

That is, by the above processing, a clip information file recording control information that enables acquisition of a specific TLV packet of interest is generated from the clip AV stream file that is a reproduction data storage file.

A clip information file corresponding to MMT format data is generated by the process according to the flow shown in FIG. 65.
If the control target is a clip AV stream file that stores MPEG-2 TS format data, the same clip information file generation process as before may be performed.

Next, a detailed sequence of the playlist file generation process executed in step S107 in the flow shown in FIG. 64 will be described with reference to the flowchart shown in FIG.
The flowchart shown in FIG. 66 is a playlist generation sequence used for controlling a clip AV stream file storing MMT format data.
The processing of each step of the flow shown in FIG. 66 will be sequentially described.

(Step S131)
First, in step S131, the information processing apparatus 300 sets the value of the CPI type (PL_CPI_type) to be recorded in the playlist file to [3].

This process corresponds to the process described above with reference to FIGS. 12 to 16.
As described with reference to "(2) New CPI type recording data (recording MPEG-2 TS compatible data and MMT compatible data)" in FIG.
PL_CPI type (PL_CPI_type) = 3 means that the CPI type in the clip information file referred to by the play item (PlayItem) specified in this playlist file is an MMT-compatible EP map.

(Step S132)
Next, in step S132, the information processing apparatus 300 records the time information (IN_time, OUT_time) of each play item to be recorded in the playlist file as NTP time information.

This process corresponds to the process described above with reference to FIGS. 17 and 18.
As shown in "(2) New play item information recording data (MMT compatible playlist)" in FIG. 18 (2).
The start time (IN_time) is the reproduction start time information of the play item (PlayItem) reproduction start point. When the data to be reproduced is MMT format data, time information according to NTP (Network Time Protocol) is recorded.
The end time (OUT_time) is the reproduction end time information of the play item (PlayItem) reproduction end point. When the data to be reproduced is MMT format data, time information according to NTP (Network Time Protocol) is recorded.

The time information according to the NTP (Network Time Protocol) is transmitted together with the MMT format data including the broadcast contents transmitted by the transmission device 20 such as the broadcast server (broadcast station) 21 shown in FIG. 1, for example.
The information processing device 30 such as the television (TV) 32 acquires time information according to NTP (Network Time Protocol) transmitted by the transmitting device 20 and records it in a playlist.

(Step S133)
Next, in step S133, the information processing apparatus 300 is the configuration data of the playlist file.
Play item (PlayItem),
Playlist mark (PlayListMark),
Generate each of these data.

In each of these data generation processes, when the data to be reproduced is MMT format data, for example, the time information is NTP time information, and the packet position is the first TLV packet stored in a stream file (clip AV stream file). Acquires and records the number of bytes data from the beginning of.

By these processes, a playlist file corresponding to MMT format data is generated.
If the control target is a clip AV stream file that stores MPEG-2 TS format data, the playlist file generation process similar to the conventional one may be performed.

The information processing apparatus 300 performs processing according to the flow described with reference to FIGS. 64 to 66, so that the input MMT format data can be converted into a playlist file, a clip information file, and a clip AV stream file according to the BDAV format. It is possible to record and play back as.

[8. Configuration and processing of information processing equipment that executes data reproduction processing from information recording media]
Next, the configuration and processing of the information processing apparatus that executes the data reproduction processing from the information recording medium will be described with reference to FIGS. 67 and below.

The information processing apparatus that executes the reproduction process reads the data recorded on the information recording medium attached to the apparatus and executes the reproduction process.

FIG. 67 is a diagram showing a configuration of an information processing apparatus 400 that executes a reproduction process of data recorded on an information recording medium 510 such as a BD.
The information processing device 400 reads the data recorded on the information recording medium (recording medium) 510 shown in FIG. 67 and outputs the data to the output device (display unit + speaker) 520. The output device 520 is, for example, a television or the like, and is a display device including a display, a speaker, and the like.
The information processing device 400 may be the same device as the information processing device 300 that performs data recording described above with reference to FIG. 63. That is, it is an information processing device having both functions of data recording and reproduction.

The information recording medium (recording medium) 510 is a recording medium in which an AV stream file generated by the processes described with reference to FIGS. 64 to 66 and a database such as a playlist and a clip information file are recorded.

For example, the control unit 401 reads the recorded data of the information recording medium 510 via the recording / playback unit 404 and the drive 403 based on the input of the reproduction instruction information from the user input unit 402, and the storage unit 405 as a data buffer. It is stored in, and the stored data is output to the reproduction processing unit 406.

Under the control of the control unit 401, the reproduction processing unit 406 acquires each data from the reproduction data read from the information recording medium 510, that is, a clip AV stream file storing each data such as images, sounds, and subtitles. To generate playback data.

The demultiplexer (DeMUX) 411 acquires a data storage packet containing each data such as an image, an audio, a subtitle, a playlist file, a clip information file, etc., classifies them into data type packets, and classifies each packet into data. Depending on the type, the data is output to the subtitle data generation unit 412, the image data generation unit 413, the audio data generation unit 414, and the auxiliary information generation unit 415.

The subtitle data generation unit 412, the image data generation unit 413, and the audio data generation unit 414 execute the decoding process of the data stored in the packet and output the decoded data to the output data generation unit 416.
The output data generation unit 416 outputs each data of subtitles, images, and voices to the output device (display unit + speaker) 520 via the input / output interface 407.

The information recording medium 510 is used as a stream file in which data to be reproduced is stored.
A stream file containing MPEG-2 TS format data and
It may have a stream file containing MMT format data.
In this case, the information processing apparatus 400 applies the playlist file and the clip information file specified in the BDAV format to reproduce the stream file storing the MPEG-2 TS format data and the stream file storing the MMT format data. The process will be executed.

The auxiliary information generation unit 415 acquires, for example, the recorded content list display data stored in the playlist file and the clip information file to generate the recorded content list, and the generated list is transmitted to the output device (display unit + speaker) 520. It is output.

The output device (display unit + speaker) 520 outputs each data such as subtitles, images, and sounds input from the information processing device 400 via the output device (display unit + speaker) 520.

The information recording medium 510 stores data in which MMT format data is recorded according to the BDAV format, and the information processing apparatus 400 records a playlist file and a clip information file which are database files specified in the BDAV format. Acquire information and execute playback control processing.

Next, the sequence of data reproduction processing from the information recording medium 510 executed by the information processing apparatus 400 shown in FIG. 67 will be described with reference to the flowchart shown in FIG. 68.

The processing according to the flow shown in FIG. 68 is executed under the control of a data processing unit (control unit) having a CPU having a program execution function, for example, according to a program stored in the storage unit of the information processing apparatus 400. Can be done.

The information processing device that executes the processing according to the flow shown in FIG. 68 is the information processing device 400 shown in FIG. 67, and an information recording medium (recording medium) 510 is attached and recorded on the attached information recording medium 510. The output data is read and output to the output device (display unit + speaker) 520. The output device 520 is, for example, a television or the like, and is a display device including a display, a speaker, and the like.

The information recording medium (recording medium) 510 is a recording medium in which an AV stream generated by the processes described with reference to FIGS. 64 to 66 and a database such as a playlist and a clip information file are recorded.
Hereinafter, the processing of each step shown in the flow of FIG. 68 will be sequentially described.

(Step S201)
First, in step S201, the control unit 401 of the information processing apparatus 400 creates a playlist file storing playback control information corresponding to the designated playback data according to, for example, the playback data designation information input by the user, as an information recording medium (media). Read from.

(Step S202)
Next, in step S202, the control unit 401 of the information processing apparatus 400 reads out the PL_CPI type (PL_CPI_type) recorded in the playlist file.
As described above with reference to FIGS. 12 to 16, the PL_CPI type (PL_CPI_type) is information indicating the CPI type in the clip information file referred to by the play item (PlayItem) specified in the playlist file. be.
The CPI (Characteristic Point Information) is recorded data of a clip information file, and is, for example, data for acquiring a data address of a reproduction start point.

As shown in FIG. 16, PL_CPI type (PL_CPI_type) = 1 means that the CPI type in the clip information file referred to by the play item (PlayItem) specified in this playlist file is an EP map compatible with MPEG-2 TS. It means that there is.
PL_CPI type (PL_CPI_type) = 2 means that the CPI type in the clip information file referred to by the play item (PlayItem) specified in this playlist file is an MPEG-2 TS compatible TU map.
PL_CPI type (PL_CPI_type) = 3 means that the CPI type in the clip information file referred to by the play item (PlayItem) specified in this playlist file is an MMT-compatible EP map.
In this way, three types of definitions of PL_CPI type (PL_CPI_type) = 1 to 3 are possible, and the three CPI types can be identified.

(Step S203)
Next, in step S203, the control unit 401 of the information processing apparatus 400 determines whether or not the set value of the PL_CPI type (PL_CPI_type) read in step S202 is [3].
That is, it is determined whether or not the CPI type in the clip information file referred to by the play item (PlayItem) specified in this playlist file is an MMT-compatible EP map.

When the PL_CPI type (PL_CPI_type) = 3, the determination in step S203 is Yes, and the process proceeds to step S205.
On the other hand, if the PL_CPI type (PL_CPI_type) is not 3, the determination in step S203 becomes No, and the process proceeds to step S204.

(Step S204)
If the PL_CPI type (PL_CPI_type) is not 3, the process of step S204 is executed.
When the PL_CPI type is other than 3, the CPI type in the clip information file referenced by the play item (PlayItem) specified in this playlist file is 1 or 2, and the playback target data is MPEG-2 TS format data. ..
In this case, the information processing apparatus 400 applies the conventional reproduction processing method to execute the reproduction processing of the MPEG-2 TS format data.

(Step S205)
On the other hand, when the PL_CPI type (PL_CPI_type) is 3, it is determined in step S205 that the reproduction target data by this playlist file is the MMT format data.

(Step S206)
Next, in step S206, the information processing apparatus 400 applies the playlist corresponding to the MMT format data and the clip information file to execute the reproduction processing of the stored data of the clip information file in which the MMT format data is stored.

Next, as a specific example of the reproduction processing of the MMT format data, a sequence of the random access reproduction processing to which the EP map corresponding to the MMT format data recorded in the clip information file is applied will be described with reference to the flowchart shown in FIG. ..

The EP map corresponding to the MMT format data is, for example, an EP map having a data structure described above with reference to FIGS. 58 to 61, and is a time information and a stream file (clip) corresponding to randomly accessible data positions. It is an EP map composed of data corresponding to byte position information from the beginning of the first TLV packet stored in the AV stream file).
The processing of each step of the flowchart shown in FIG. 69 will be described.

(Step S211)
First, in step S211 the information processing apparatus 400 reads the clip information file name (Clip_information_file_name) from the play item information of the playlist applied to the random access reproduction.

This is the data recorded in the play item (PlayItem) information in the playlist file described above with reference to FIG.

(Step S212)
Next, in step S212, the information processing apparatus 400 reads the clip information file having the clip information file name (Clip_information_file_name) read from the playlist file in step S211 from the information recording medium (media).

(Step S213)
Next, in step S213, the information processing apparatus 400 specifies ATC and STC, which are clock information to be applied to reproduction, from the sequence information (SequenceInfo) of the clip information file. Note that these time information is recorded as NTP time information when the reproduction target data is MMT format data.

The sequence information (SequenceInfo) of the clip information file has a data structure described above with reference to FIG. 30, and information on ATC (arrival time clock) and STC (system time clock) is defined here. Has been done.
The ATC (arrival time clock) and STC (system time clock) are as described above with reference to FIG. 30, and are clock information applied to data reproduction.

(Step S214)
Next, in step S214, the information processing apparatus 400 acquires a reproduction start position (SPN_STC_Start) and a reproduction start time (presentation_start_time) from the sequence information (SequenceInfo) of the clip information file.

When the reproduction target data is MMT format data, the reproduction start position information is, for example, the number of bytes from the beginning of the first TLV packet stored in the stream file (clip AV stream file), and the reproduction start time is NTP. It becomes time information. This information is recorded as sequence information (SequenceInfo) of the clip information file.

(Step S215)
Next, in step S215, the information processing apparatus 400 identifies a packet containing the MMT package table (MPT) from the information recorded in the program information (ProgramInfo) of the clip information file, and from the MMT package table (MPT). Information necessary for the reproduction process of MMT format data, for example, information such as a packet identifier and a decoding method is acquired.

As described above with reference to FIGS. 39 to 48, the packet identifier (PID) recording area (program map PID recording area) of the program information (ProgramInfo) of the clip information file includes the following (a) and ( The information of any of b) is recorded.
(A) IP data flow identification information and packet identifier (MPT_PID) of the packet stored in the MMT package table (MPT).
(B) Package list table (PLT) information and MMT package table (MPT) information

In step S215, the information processing apparatus 400 identifies a packet containing the MMT package table (MPT) from any of the above information (a) and (b) recorded in the program information (ProgramInfo) of the clip information file. do.
Further, from the specific packet, information necessary for reproduction processing of MMT format data, such as a packet identifier and information such as a decoding method, is acquired from the MMT package table (MPT).

The IP data flow identification information in (a) above is composed of the following data as described above with reference to FIG. 58 and others.
(1) Source IP address (src_IP_addless)
(2) Destination IP address (dest_IP_addless)
(3) Destination port (destination_port)
(4) Source port (source_port)
(5) Next header information (next_header)

Alternatively, as described with reference to FIG. 59 et al., Recorded in the compressed IP header.
(1) Context identifier (CID),
May be recorded as IP data flow identification information.
By referring to the IP data flow identification information recorded in the clip information file, even if multiple IP data flows are mixed in the clip AV stream file and the packet with the same packet identifier is set, one IP is included. It is possible to identify the data flow and reliably select the packets contained in the IP data flow.

(Step S216)
Next, in step S216, the information processing apparatus 400 reads the recorded information of the EP map recorded in the CPI information (CPI) of the clip information file, and acquires the information necessary for random access reproduction. For example, it executes a process of specifying a packet that stores data of a random access destination.

The packet identifier (PID) recording area (stream PID recording area) of the EP map [EP_map ()] recording area in the CPI information (CPI) is described below with reference to FIGS. 56 to 62. Data is recorded.
(A) IP data flow identification information and packet identifier (stream_PID)

The IP data flow identification information in (a) above is composed of the following data as described above with reference to FIG. 58 and others.
(1) Source IP address (src_IP_addless)
(2) Destination IP address (dest_IP_addless)
(3) Destination port (destination_port)
(4) Source port (source_port)
(5) Next header information (next_header)

Alternatively, as described with reference to FIG. 59 et al., Recorded in the compressed IP header.
(1) Context identifier (CID),
May be recorded as IP data flow identification information.

By referring to the above data recorded in the clip information file, even if multiple IP data flows are mixed in the clip AV trim file and the packets with the same packet identifier are included, one IP data flow can be obtained. It is possible to reliably select a packet based on the packet identifier (stream_PID) specified and included in the IP data flow.

(Step S217)
Next, in step S217, the information processing apparatus 400 reads the MMT format data stored in the clip AV stream file according to the recording rate (cording_rate) recorded in the clip information (ClipInfo) of the clip information file.

As described above with reference to FIG. 25, recording rate (recording_rate) information is recorded in the clip information (ClipInfo) of the clip information file, and is recorded in the information recording medium (media) according to this information. The read control of the MMT format data stored in the clip AV stream file is executed.
In FIG. 25, TS_recording_rate is described as the recording rate information, but when the reproduction target data is in the MMT format having an MMT packet, the bit rate corresponding to the MMT format is recorded here.

(Step S218)
Next, in step S218, the information processing apparatus 400 executes demultiplexing processing, decoding processing, and reproduction processing of the MMT format data stored in the clip AV stream file read from the information recording medium (media).

[9. About the configuration example of the information processing device]
Next, a hardware configuration example of an information processing device applicable as an information processing device that records data on an information recording medium and reproduces data from the information recording medium will be described with reference to FIG. 70.

The CPU (Central Processing Unit) 601 functions as a data processing unit that executes various processes according to a program stored in a ROM (Read Only Memory) 602 or a storage unit 608. For example, the process according to the sequence described in the above-described embodiment is executed. The RAM (Random Access Memory) 603 stores programs and data executed by the CPU 601. These CPU 601, ROM 602, and RAM 603 are connected to each other by a bus 604.

The CPU 601 is connected to an input / output interface 605 via a bus 604, and an input unit 606 consisting of various switches, a keyboard, a mouse, a microphone, etc., and an output unit 607 consisting of a display, a speaker, etc. are connected to the input / output interface 605. There is. The CPU 601 executes various processes in response to a command input from the input unit 606, and outputs the process results to, for example, the output unit 607.

The storage unit 608 connected to the input / output interface 605 is composed of, for example, a hard disk or the like, and stores a program executed by the CPU 601 and various data. The communication unit 609 functions as a transmission / reception unit for data communication via a network such as the Internet or a local area network, and further as a transmission / reception unit for broadcast waves, and communicates with an external device.

The drive 610 connected to the input / output interface 605 drives a removable medium 611 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory such as a memory card, and records or reads data.

[10. Summary of the structure of this disclosure]
As described above, the embodiments of the present disclosure have been described in detail with reference to the specific embodiments. However, it is self-evident that those skilled in the art may modify or substitute the examples without departing from the gist of the present disclosure. That is, the present invention has been disclosed in the form of an example and should not be construed in a limited manner. In order to judge the gist of this disclosure, the column of claims should be taken into consideration.

The technique disclosed in the present specification can have the following configuration.
(1) It has a data processing unit that inputs MMT (MPEG Media Transport) format data and generates recorded data according to the BDAV format or SPAV format, which is a data recording format for an information recording medium.
The data processing unit
A clip AV stream file consisting of a TLV packet string that stores MMT format data as playback data, and
An information processing device that generates a playback control information file that records control information that enables acquisition of a specific TLV packet from the clip AV stream file.

(2) The data processing unit is
The information processing apparatus according to (1), which generates a playlist file and a clip information file as the playback control information file.

(3) The data processing unit is
The information processing apparatus according to (1) or (2), wherein the average rate and recording rate of each TLV packet, which is a constituent packet of the clip AV stream file, are recorded in the reproduction control information file.

(4) The data processing unit is
The information processing apparatus according to any one of (1) to (3), which records the file size of the clip AV stream file composed of TLV packets in the reproduction control information file.

(5) The data processing unit is
The information processing apparatus according to any one of (1) to (4), which records NTP (Network Time Protocol) time information received together with the MMT format data as the time information to be recorded in the reproduction control information file.

(6) The data processing unit is
The information processing apparatus according to any one of (1) to (5), which records the number of bytes from the beginning of the clip AV stream file composed of a TLV packet string as data position information to be recorded in the reproduction control information file.

(7) The data processing unit is
When the packet identifier is recorded in the reproduction control information file, the IP data flow identification information that makes it possible to identify the IP data flow to which the packet specified by the packet identifier belongs is also recorded (1) to (6). The information processing device described in.

(8) The IP data flow identification information is
(A) Source IP address,
(B) Destination IP address,
(C) Destination port,
(D) Source port,
(E) Protocol type information,
The above 5 data or
The information processing apparatus according to (7), which includes at least one of context identifiers (CIDs).

(9) The information processing apparatus according to (8), wherein the context identifier (CID) is data recorded in a compressed IP header.

(10) The information processing according to any one of (7) to (9), wherein the packet identifier is an identifier of a packet storing an MMT package table (MPT) or an identifier of a packet storing random access reproduction target data. Device.

(11) It has a data processing unit that executes a reproduction process of recorded data of an information recording medium.
The information recording medium is a BDAV format of a clip AV stream file composed of a TLV packet string storing MMT (MPEG Media Transport) format data and a playback control information file storing playback control information of the clip AV stream file. , Or an information recording medium recorded according to the SPAV format.
The data processing unit
In the data reproduction process using the clip AV stream file composed of the TLV packet sequence,
An information processing device that acquires reproduction target data from a TLV packet and executes reproduction control according to the recorded information of the reproduction control information file.

(12) The data processing unit is
The information processing apparatus according to (11), wherein the playlist file and the clip information file, which are the reproduction control information files, are applied to execute the reproduction control.

(13) The data processing unit is
From the recorded data of the playback control information file,
The average rate and recording rate of each TLV packet which is a constituent packet of the clip AV stream file are acquired, and the reading control of the MMT format data from the clip AV stream file is executed (11) or according to the acquisition rate. The information processing apparatus according to (12).

(14) The data processing unit is
Recorded as data position information in the reproduction control information file,
The information processing apparatus according to any one of (11) to (13), which executes playback control using byte information from the beginning of the clip AV stream file.

(15) The data processing unit is
From the playback control information file
Read the IP data flow identification information and packet identifier,
The IP data flow is identified according to the IP data flow identification information, and the IP data flow is identified.
The information processing apparatus according to any one of (11) to (14), wherein a packet having the packet identifier is selected from a group of packets belonging to the identified IP data flow and a target packet is extracted.

(16) A clip AV stream file composed of a TLV packet string storing MMT (MPEG Media Transport) format data, and
It has a playback control information file that stores the playback control information of the clip AV stream file as recorded data.
The playback control information file is
The IP data flow identification information for extracting the target packet from the TLV packet included in the clip AV stream file and the packet identifier are included.
Information having a data recording configuration that enables a reproduction device that reproduces stored data of the clip AV stream file to acquire reproduction target data from the TLV packet string by referring to the IP data flow identification information and the packet identifier. recoding media.

(17) An information processing method executed by an information processing device.
The information processing device is
It has a data processing unit that inputs MMT (MPEG Media Transport) format data and generates recorded data according to BDAV format or SPAV format, which is a data recording format for information recording media.
The data processing unit
A clip AV stream file consisting of a TLV packet string that stores MMT format data as playback data, and
An information processing method for generating a reproduction control information file in which control information that enables acquisition of a specific TLV packet from the clip AV stream file is recorded.

(18) An information processing method executed by an information processing device.
The information processing device is
It has a data processing unit that executes the reproduction processing of the recorded data of the information recording medium.
The information recording medium is a BDAV format of a clip AV stream file composed of a TLV packet string storing MMT (MPEG Media Transport) format data and a playback control information file storing playback control information of the clip AV stream file. , Or an information recording medium recorded according to the SPAV format.
The data processing unit
In the data reproduction process using the clip AV stream file composed of the TLV packet sequence,
An information processing method for acquiring reproduction target data from a TLV packet and executing reproduction control according to the recorded information of the reproduction control information file.

(19) A program that executes information processing in an information processing device.
The information processing device is
It has a data processing unit that inputs MMT (MPEG Media Transport) format data and generates recorded data according to BDAV format or SPAV format, which is a data recording format for information recording media.
The program is installed in the data processing unit.
A clip AV stream file consisting of a TLV packet string that stores MMT format data as playback data, and
A program that generates a playback control information file that records control information that makes it possible to acquire a specific TLV packet from the clip AV stream file.

(20) A program that executes information processing in an information processing device.
The information processing device is
It has a data processing unit that executes the reproduction processing of the recorded data of the information recording medium.
The information recording medium is a BDAV format of a clip AV stream file composed of a TLV packet string storing MMT (MPEG Media Transport) format data and a playback control information file storing playback control information of the clip AV stream file. , Or an information recording medium recorded according to the SPAV format.
The program is installed in the data processing unit.
In the data reproduction process using the clip AV stream file composed of the TLV packet sequence,
A program that acquires playback target data from a TLV packet and executes playback control according to the recorded information of the playback control information file.

Further, the series of processes described in the specification can be executed by hardware, software, or a composite configuration of both. When executing processing by software, install the program that records the processing sequence in the memory in the computer built in the dedicated hardware and execute it, or execute the program on a general-purpose computer that can execute various processing. It can be installed and run. For example, the program can be pre-recorded on a recording medium. In addition to installing the program on a computer from a recording medium, the program can be received via a network such as a LAN (Local Area Network) or the Internet and installed on a recording medium such as a built-in hard disk.

The various processes described in the specification are not only executed in chronological order according to the description, but may also be executed in parallel or individually as required by the processing capacity of the device that executes the processes. Further, in the present specification, the system is a logical set configuration of a plurality of devices, and the devices having each configuration are not limited to those in the same housing.

As described above, according to the configuration of one embodiment of the present disclosure, a configuration is realized in which MMT format data is recorded on a medium as BDAV or SPAV format data and can be reproduced.
Specifically, for example, a stream file composed of a TLV packet string storing MMT format data and a playback control information file are generated and recorded on a medium. The IP data flow identification information and the packet identifier are recorded together in the reproduction control information file. As the IP data flow identification information, data consisting of a source IP address or the like, or a CID or the like recorded in a compressed IP header is used. The IP data flow identification information selects a specific IP data flow, and enables selection of the only packet for which a packet identifier is set from a group of packets belonging to the selected flow.
With this configuration, a configuration is realized in which MMT format data is recorded on a medium as BDAV or SPAV format data and can be played back.

20 Transmitter 21 Broadcast server 22 Data distribution server 30 Information processing device 31 BD player 32 TV
33 PC
34 Mobile terminal 40 Information recording medium (media)
41 BD
42 HDD
43 Flash memory 300 Information processing device 301 Data input unit 302 User input unit 303 Control unit 304 Storage unit 305 Demultiplexer 306 Recording data generation unit 307 Recording unit 308 Drive 311 Subtitle data generation unit 312 Image data generation unit 313 Audio data generation unit 314 Auxiliary information generation unit 315 multiplexer 316 database file generation unit 320 information recording medium 400 information processing device 401 control unit 402 user input unit 403 drive 404 recording / playback unit 405 storage unit 406 playback processing unit 407 input / output I / F
411 Demultiplexer 412 Subtitle data generation unit 413 Image data generation unit 414 Audio data generation unit 415 Auxiliary information generation unit 416 Output data generation unit 510 Information recording medium 520 Output device (display unit + speaker)
601 CPU
602 ROM
603 RAM
604 Bus 605 I / O interface 606 Input section 607 Output section 608 Storage section 609 Communication section 610 Drive 611 Removable media

Claims (19)

It has a data processing unit that inputs MMT (MPEG Media Transport) format data and generates recorded data according to BDAV format or SPAV format, which is a data recording format for information recording media.
The data processing unit
A clip AV stream file consisting of a TLV packet string that stores MMT format data as playback data, and
An information processing device that generates a playback control information file that records control information that enables acquisition of a specific TLV packet from the clip AV stream file. The data processing unit
The information processing apparatus according to claim 1, which generates a playlist file and a clip information file as the playback control information file. The data processing unit
The information processing apparatus according to claim 1, wherein the average rate and recording rate of each TLV packet, which is a constituent packet of the clip AV stream file, are recorded in the reproduction control information file. The data processing unit
The information processing apparatus according to claim 1, wherein the file size of the clip AV stream file composed of TLV packets is recorded in the reproduction control information file. The data processing unit
The information processing apparatus according to claim 1, wherein the NTP (Network Time Protocol) time information received together with the MMT format data is recorded as the time information to be recorded in the reproduction control information file. The data processing unit
The information processing apparatus according to claim 1, wherein the number of bytes from the beginning of the clip AV stream file composed of a TLV packet string is recorded as the data position information to be recorded in the reproduction control information file. The data processing unit
The information processing apparatus according to claim 1, wherein when the packet identifier is recorded in the reproduction control information file, the IP data flow identification information that makes it possible to identify the IP data flow to which the packet specified by the packet identifier belongs is also recorded. .. The IP data flow identification information is
(A) Source IP address,
(B) Destination IP address,
(C) Destination port,
(D) Source port,
(E) Protocol type information,
The above 5 data or
The information processing apparatus according to claim 7, which comprises at least one of the context identifiers (CIDs). The information processing apparatus according to claim 8, wherein the context identifier (CID) is data recorded in a compressed IP header. The information processing apparatus according to claim 7, wherein the packet identifier is an identifier of a packet storing an MMT package table (MPT) or an identifier of a packet storing random access reproduction target data. It has a data processing unit that executes the reproduction processing of the recorded data of the information recording medium.
The information recording medium is a BDAV format of a clip AV stream file composed of a TLV packet string storing MMT (MPEG Media Transport) format data and a playback control information file storing playback control information of the clip AV stream file. , Or an information recording medium recorded according to the SPAV format.
The data processing unit
In the data reproduction process using the clip AV stream file composed of the TLV packet sequence,
An information processing device that acquires reproduction target data from a TLV packet and executes reproduction control according to the recorded information of the reproduction control information file. The data processing unit
The information processing apparatus according to claim 11, wherein the playlist file, which is the reproduction control information file, and the clip information file are applied to execute the reproduction control. The data processing unit
From the recorded data of the playback control information file,
13. The information processing device described. The data processing unit
Recorded as data position information in the reproduction control information file,
The information processing apparatus according to claim 11, wherein the reproduction control is executed by using the byte information from the beginning of the clip AV stream file. The data processing unit
From the playback control information file
Read the IP data flow identification information and packet identifier,
The IP data flow is identified according to the IP data flow identification information, and the IP data flow is identified.
The information processing apparatus according to claim 11, wherein a packet having the packet identifier is selected from a group of packets belonging to the identified IP data flow and a target packet is extracted. It is an information processing method executed in an information processing device.
The information processing device is
It has a data processing unit that inputs MMT (MPEG Media Transport) format data and generates recorded data according to BDAV format or SPAV format, which is a data recording format for information recording media.
The data processing unit
A clip AV stream file consisting of a TLV packet string that stores MMT format data as playback data, and
An information processing method for generating a reproduction control information file in which control information that enables acquisition of a specific TLV packet from the clip AV stream file is recorded. It is an information processing method executed in an information processing device.
The information processing device is
It has a data processing unit that executes the reproduction processing of the recorded data of the information recording medium.
The information recording medium is a BDAV format of a clip AV stream file composed of a TLV packet string storing MMT (MPEG Media Transport) format data and a playback control information file storing playback control information of the clip AV stream file. , Or an information recording medium recorded according to the SPAV format.
The data processing unit
In the data reproduction process using the clip AV stream file composed of the TLV packet sequence,
An information processing method for acquiring reproduction target data from a TLV packet and executing reproduction control according to the recorded information of the reproduction control information file. It is a program that executes information processing in an information processing device.
The information processing device is
It has a data processing unit that inputs MMT (MPEG Media Transport) format data and generates recorded data according to BDAV format or SPAV format, which is a data recording format for information recording media.
The program is installed in the data processing unit.
A clip AV stream file consisting of a TLV packet string that stores MMT format data as playback data, and
A program that generates a playback control information file that records control information that makes it possible to acquire a specific TLV packet from the clip AV stream file. It is a program that executes information processing in an information processing device.
The information processing device is
It has a data processing unit that executes the reproduction processing of the recorded data of the information recording medium.
The information recording medium is a BDAV format of a clip AV stream file composed of a TLV packet string storing MMT (MPEG Media Transport) format data and a playback control information file storing playback control information of the clip AV stream file. , Or an information recording medium recorded according to the SPAV format.
The program is installed in the data processing unit.
In the data reproduction process using the clip AV stream file composed of the TLV packet sequence,
A program that acquires playback target data from a TLV packet and executes playback control according to the recorded information of the playback control information file.

Images