Information processing device and method

Abstract

The present disclosure relates to an information processing device and method for making it possible to play back content by utilizing a scene description corresponding to a plurality of playback methods. In a scene description, a property corresponding to a 3D data playback method is selected on the basis of an extension and is utilized for playback. Further, in a scene description, an alternatives sequence corresponding to a 3D data playback method is selected, and a property as an element of the sequence is utilized for playback. Further, a scene description file for storing an extension for identifying a property for each 3D data playback method is generated. Further, a scene description file for storing a plurality of alternatives sequences having, as elements, properties corresponding to mutually identical playback methods for 3D data is generated. The present disclosure may be applied to information processing devices, information processing methods, and the like.

Description

[Technical Field]

[0001] The present disclosure relates to an information processing device and method, and more particularly to an information processing device and method that are capable of playing back content using scene descriptions that support a plurality of playback methods. [Background technology]

[0002] Conventionally, there is glTF (The GL Transmission Format) (registered trademark) 2.0, which is a scene description format for arranging and rendering 3D (three-dimensional) objects in a three-dimensional space (see, for example, Non-Patent Document 1).

[0003] Furthermore, in the MPEG (Moving Picture Experts Group)-I Scene Description, a method has been proposed in which glTF2.0 is extended to handle dynamic content in the time direction (see, for example, Non-Patent Document 2).

[0004] Incidentally, V-PCC (Video-based Point Cloud Compression) has been proposed as a point cloud encoding method, in which a point cloud is segmented to form regions, each region is projected onto a plane, and encoded using a video codec (see, for example, Non-Patent Document 3). A point cloud is 3D data that represents the three-dimensional structure of an object using a collection of points in three-dimensional space, each of which has position information and attribute information (color, reflection, etc.).

[0005] Furthermore, a method has been studied for storing a V3C bitstream, which is made up of coded data of a point cloud coded by this V-PCC, in ISOBMFF (see, for example, Non-Patent Document 4).

[0006] In recent years, methods have been studied for using V3C bitstreams stored in ISOBMFF as the actual data for 3D objects placed within a scene. Two methods have been studied for playing back such content: one in which the 3D data is reconstructed by the MAF (Media Access Function) and the other in the PE (Presentation Engine). [Prior art documents] [Non-patent literature]

[0007] [Non-Patent Document 1] Saurabh Bhatia, Patrick Cozzi, Alexey Knyazev, Tony Parisi, "Khronos glTF2.0", https: / / github.com / KhronosGroup / glTF / tree / master / specification / 2.0, June 9, 2017 [Non-patent document 2] "Text of ISO / IEC CD 23090-14 Scene Description for MPEG Media", ISO / IEC JTC 1 / SC 29 / WG 3 N00026, 2020-11-30 [Non-patent document 3] "ISO / IEC FDIS 23090-5 Visual Volumetric Video-based Coding and Video-based Point Cloud Compression", ISO / IEC JTC 1 / SC 29 / WG 11 N19579, 2020-09-21 [Non-patent document 4] "Draft text of ISO / IEC FDIS 23090-10 Carriage of Visual Volumetric Video-based Coding Data", INTERNATIONAL ORGANIZATION FOR STANDARDIZATION ORGANISATION INTERNATIONALE DE NORMALISATION ISO / IEC JTC 1 / SC 29 / WG 03 MPEG SYSTEMS, ISO / IEC JTC 1 / SC 29 / WG 03 N0163, 19995, 2021-03-25 Summary of the Invention [Problem to be solved by the invention]

[0008] However, the structure of the scene description differs between when 3D data is reconstructed using MAF and when it is reconstructed using PE. As a result, a single scene description could not be used for both playback methods. Therefore, in order to support both playback methods, it was necessary to prepare separate scene description files for each piece of content.

[0009] The present disclosure has been made in light of such circumstances, and makes it possible to play back content using scene descriptions that support a plurality of playback methods. [Means for solving the problem]

[0010] An information processing device according to one aspect of the present technology is an information processing device that includes a file processing unit that selects a property corresponding to a playback method for 3D data based on an extension defined in a scene description, and processes the 3D data using the selected property according to the playback method.

[0011] An information processing method according to one aspect of the present technology is an information processing method that selects a property corresponding to a playback method for 3D data based on an extension defined in a scene description, and processes the 3D data using the selected property in the playback method.

[0012] An information processing device according to another aspect of the present technology is an information processing device that includes a file processing unit that selects an alternatives array corresponding to a playback method for 3D data from among alternatives arrays defined in a scene description, and processes the 3D data using the playback method by utilizing properties that are elements of the selected alternatives array.

[0013] Another aspect of the information processing method of the present technology is an information processing method that selects an alternatives array corresponding to a playback method for 3D data from among alternatives arrays defined in a scene description, and processes the 3D data using the playback method by using properties that are elements of the selected alternatives array.

[0014] An information processing device according to yet another aspect of the present technology is an information processing device including a file generation unit that generates a scene description file that stores an extension for identifying properties for each playback method of 3D data.

[0015] An information processing method according to yet another aspect of the present technology is an information processing method for generating a scene description file that stores an extension for identifying properties for each playback method of 3D data.

[0016] According to yet another aspect of the present technology, an information processing device is an information processing device including a file generation unit that generates a scene description file storing a plurality of alternatives arrays each having a property as an element corresponding to the same playback method of 3D data.

[0017] An information processing method according to yet another aspect of the present technology is an information processing method for generating a scene description file that stores a plurality of alternatives arrays, each of which has as elements a property corresponding to the same playback method of 3D data.

[0018] In an information processing device and method according to one aspect of the present technology, a property corresponding to a playback method for 3D data is selected based on an extension defined in a scene description, and the selected property is used to process the 3D data using that playback method.

[0019] In the information processing device and method according to another aspect of the present technology, an alternatives array corresponding to a playback method for 3D data is selected from the alternatives arrays defined in the scene description, and the properties that are elements of the selected alternatives array are used to process the 3D data using that playback method.

[0020] In an information processing device and method according to still another aspect of the present technology, a scene description file is generated that stores an extension for identifying properties for each playback method of 3D data.

[0021] In an information processing device and method according to still another aspect of the present technology, a scene description file is generated that stores a plurality of alternatives arrays, each of which has as elements a property corresponding to the same playback method of 3D data. [Brief explanation of the drawings]

[0022] [Figure 1] FIG. 1 is a diagram illustrating an example of the main configuration of glTF2.0. [Figure 2] FIG. 1 is a diagram illustrating an example of glTF objects and reference relationships. [Figure 3] FIG. 10 is a diagram showing an example of a scene description. [Figure 4] FIG. 10 is a diagram illustrating a method for accessing binary data. [Figure 5]FIG. 10 is a diagram showing an example of a scene description. [Figure 6] FIG. 10 is a diagram illustrating the relationship between a buffer object, a buffer view object, and an accessor object. [Figure 7] 10A and 10B are diagrams illustrating examples of descriptions of a buffer object, a buffer view object, and an accessor object. [Figure 8] FIG. 10 is a diagram illustrating an example of the configuration of a scene description object. [Figure 9] FIG. 10 is a diagram showing an example of a scene description. [Figure 10] FIG. 10 is a diagram illustrating a method for expanding an object. [Figure 11] FIG. 10 is a diagram illustrating a configuration of a client process. [Figure 12] FIG. 10 is a diagram illustrating an example of the configuration of an extension for handling timed metadata. [Figure 13] FIG. 10 is a diagram showing an example of a scene description. [Figure 14] FIG. 10 is a diagram showing an example of a scene description. [Figure 15] FIG. 10 is a diagram illustrating an example of the configuration of an extension for handling timed metadata. [Figure 16] FIG. 2 illustrates an example of the main configuration of a client. [Figure 17] 10 is a flowchart illustrating an example of the flow of a client process. [Figure 18] FIG. 1 is a diagram illustrating an overview of a V-PCC. [Figure 19] FIG. 10 is a diagram showing an example of the main configuration of a V-PCC bitstream. [Figure 20] FIG. 10 is a diagram showing an example of the structure of an ISOBMFF track in the case of a multi-track structure. [Figure 21] FIG. 10 is a diagram showing an example of MPD description in the case of a multi-track structure. [Figure 22] FIG. 10 illustrates an example of a client process. [Figure 23] FIG. 10 is a diagram showing an example of the configuration of objects in a scene description when 3D data is reconstructed using MAF. [Figure 24] FIG. 10 is a diagram showing an example of the configuration of objects in a scene description when 3D data is reconstructed by a PE. [Figure 25] FIG. 10 is a diagram showing an example of the configuration of objects in a scene description when 3D data is reconstructed by a PE. [Figure 26] FIG. 10 is a diagram showing an example of a scene description that supports multiple playback methods. [Figure 27] FIG. 10 is a diagram showing an example of an object configuration of a scene description. [Figure 28] FIG. 10 is a diagram showing an example of a scene description. [Figure 29] FIG. 10 is a diagram showing an example of an object configuration of a scene description. [Figure 30] FIG. 10 is a diagram showing an example of a scene description. [Figure 31] FIG. 10 is a diagram showing an example of an object configuration of a scene description. [Figure 32] FIG. 10 is a diagram showing an example of a scene description. [Figure 33] FIG. 10 is a diagram showing an example of an object configuration of a scene description. [Figure 34] FIG. 10 is a diagram showing an example of a scene description. [Figure 35] FIG. 10 is a diagram showing an example of a scene description that supports multiple playback methods. [Figure 36] FIG. 10 is a diagram showing an example of an object configuration of a scene description. [Figure 37] FIG. 10 is a diagram showing an example of a scene description that supports multiple playback methods. [Figure 38] FIG. 10 is a diagram showing an example of an object configuration of a scene description. [Figure 39]FIG. 2 is a block diagram illustrating an example of the main configuration of a file generation device. [Figure 40] 10 is a flowchart illustrating an example of the flow of a file generation process. [Figure 41] 10 is a flowchart illustrating an example of the flow of a file generation process. [Figure 42] FIG. 2 is a block diagram illustrating an example of the main configuration of a client device. [Figure 43] 10 is a flowchart showing an example of the flow of a playback process. [Figure 44] FIG. 1 is a block diagram illustrating an example of the main configuration of a computer. DETAILED DESCRIPTION OF THE INVENTION

[0023] Hereinafter, modes for carrying out the present disclosure (hereinafter referred to as embodiments) will be described in the following order. 1. Literature supporting technical content and technical terminology 2. MPEG-I Scene Description 3. Scene description supports multiple playback methods 4. First embodiment (file generation device) 5. Second embodiment (client device) 6. Supplementary Notes

[0024] <1. Literature supporting technical content and technical terminology> The scope of disclosure of the present technology includes not only the contents described in the embodiments but also the contents described in the following non-patent documents that were publicly known at the time of filing, as well as the contents of other documents referenced in the following non-patent documents.

[0025] Non-patent document 1: (mentioned above) Non-patent document 2: (mentioned above) Non-patent document 3: (mentioned above) Non-patent document 4: (mentioned above)

[0026] In other words, the contents of the above-mentioned non-patent documents and the contents of other documents referenced in the above-mentioned non-patent documents are also used as the basis for determining the support requirements. For example, even if syntax and terminology such as glTF2.0 and its extensions described in Non-Patent Documents 1 to 3 are not directly defined in this disclosure, they are considered to be within the scope of this disclosure and meet the support requirements of the claims. Similarly, even if technical terms such as parsing, syntax, and semantics are not directly defined in this disclosure, they are considered to be within the scope of this disclosure and meet the support requirements of the claims.

[0027] <2. MPEG-I Scene Description> <gltf2.0> Conventionally, as described in Non-Patent Document 1, for example, there is glTF (The GL Transmission Format) (registered trademark) 2.0, which is a format for placing 3D (three-dimensional) objects in a three-dimensional space. As shown in FIG. 1, for example, glTF 2.0 is composed of a JSON format file (.glTF), a binary file (.bin), and an image file (.png, .jpg, etc.). The binary file stores binary data such as geometry and animation. The image file stores data such as texture.

[0028] A JSON format file is a scene description file written in JSON (JavaScript (registered trademark) Object Notation). A scene description is metadata that describes (a description of) a scene of 3D content. The description of this scene description defines what kind of scene it is. A scene description file is a file that stores such a scene description. In this disclosure, a scene description file is also referred to as a scene description file.

[0029] The description of the JSON format file consists of a list of key and value pairs. An example of the format is shown below. “KEY”:”VALUE”

[0030] Keys consist of strings, and values ​​consist of numbers, strings, booleans, arrays, objects, or null.

[0031] Additionally, multiple key-value pairs ("KEY":"VALUE") can be grouped together using {} (curly braces). This grouping is also called a JSON object. An example of the format is shown below. “user”:{"id":1, "name":"tanaka"}

[0032] In this example, a JSON object that combines the pair "id":1 and the pair "name":"tanaka" is defined as the value corresponding to the key (user).

[0033] You can also create an array of zero or more values ​​using square brackets ([]). This array is also called a JSON array. For example, a JSON object can be applied as an element of this JSON array. An example of the format is shown below. test":["hoge", "fuga", "bar"] "users":[{"id":1, "name":"tanaka"},{"id":2,"name":"yamada"},{"id":3, "name":"sato"}]

[0034] Figure 2 shows the glTF objects that can be written at the top level of a JSON format file and the reference relationships they can have. The long circles in the tree structure shown in Figure 2 represent objects, and the arrows between those objects show the reference relationships. As shown in Figure 2, objects such as "scene", "node", "mesh", "camera", "skin", "material", and "texture" are written at the top level of a JSON format file.

[0035] An example of such a JSON format file (scene description) is shown in FIG. 3. The JSON format file 20 in FIG. 3 shows an example of a portion of the top-level description. In this JSON format file 20, all top-level objects 21 used are described at the top level. These top-level objects 21 are the glTF objects shown in FIG. 2. Furthermore, in the JSON format file 20, reference relationships between objects are shown as indicated by arrows 22. More specifically, the reference relationships are shown by specifying the index of an element in the array of the referencing object in the property of the higher-level object.

[0036] Fig. 4 is a diagram illustrating a method for accessing binary data. As shown in Fig. 4, binary data is stored in a buffer object. That is, information for accessing the binary data (for example, a uniform resource identifier (URI)) is indicated in the buffer object. In a JSON format file, as shown in Fig. 4, objects such as a mesh, camera, and skin can access the buffer object via an accessor object and a bufferView object.

[0037] That is, for objects such as mesh, camera, and skin, the accessor object to be referenced is specified. An example of a mesh object description in a JSON format file is shown in Figure 5. For example, as shown in Figure 5, in a mesh object, vertex attributes such as NORMAL, POSITION, TANGENT, and TEXCORD_0 are defined as keys, and for each attribute, the accessor object to be referenced is specified as a value.

[0038] The relationship between buffer objects, buffer view objects, and accessor objects is shown in Figure 6. An example of how these objects are written in a JSON format file is shown in Figure 7.

[0039] 6, buffer object 41 is an object that stores information (such as a URI) for accessing binary data, which is actual data, and information indicating the data length (for example, byte length) of that binary data. A in FIG. 7 shows an example of the description of buffer object 41. "bytelength":102040" shown in A in FIG. 7 indicates that the byte length of buffer object 41 is 102040 bytes, as shown in FIG. 6. Furthermore, "uri":"duck.bin" shown in A in FIG. 7 indicates that the URI of buffer object 41 is "duck.bin", as shown in FIG. 6.

[0040] 6, the buffer view object 42 is an object that stores information about a subset area of ​​binary data specified in the buffer object 41 (i.e., information about a partial area of ​​the buffer object 41). B of Fig. 7 shows an example of description of the buffer view object 42. As shown in Fig. 6 and B of Fig. 7, the buffer view object 42 stores information such as identification information of the buffer object 41 to which the buffer view object 42 belongs, an offset (e.g., a byte offset) indicating the position of the buffer view object 42 within the buffer object 41, and a length (e.g., a byte length) indicating the data length (e.g., a byte length) of the buffer view object 42.

[0041] As shown in B of Fig. 7, when there are multiple buffer view objects, information is written for each buffer view object (i.e., for each subset area). For example, information such as "buffer":0, "bytelength":25272, and "byteOffset":0 shown at the top of B of Fig. 7 is information for the first buffer view object 42 (bufferView[0]) shown in the buffer object 41 in Fig. 6. Furthermore, information such as "buffer":0, "bytelength":76768, and "byteOffset":25272 shown at the bottom of B of Fig. 7 is information for the second buffer view object 42 (bufferView[1]) shown in the buffer object 41 in Fig. 6.

[0042] "buffer":0" of the first buffer view object 42 (bufferView[0]) shown in B of FIG. 7 indicates that the identification information of the buffer object 41 to which the buffer view object 42 (bufferView[0]) belongs is "0" (Buffer[0]), as shown in FIG. 6. Also, "bytelength":25272" indicates that the byte length of the buffer view object 42 (bufferView[0]) is 25272 bytes. Furthermore, "byteOffset":0" indicates that the byte offset of the buffer view object 42 (bufferView[0]) is 0 bytes.

[0043] "buffer":0" of the second buffer view object 42 (bufferView[1]) shown in B of FIG. 7 indicates that the identification information of the buffer object 41 to which the buffer view object 42 (bufferView[0]) belongs is "0" (Buffer[0]), as shown in FIG. 6. Also, "bytelength":76768" indicates that the byte length of the buffer view object 42 (bufferView[0]) is 76768 bytes. Furthermore, "byteOffset":25272" indicates that the byte offset of the buffer view object 42 (bufferView[0]) is 25272 bytes.

[0044] 6, the accessor object 43 is an object that stores information about how to interpret data in the buffer view object 42. C in Fig. 7 shows an example of the description of the accessor object 43. As shown in Figs. 6 and 7C, the accessor object 43 stores information such as the identification information of the buffer view object 42 to which the accessor object 43 belongs, the offset (e.g., byte offset) indicating the position of the buffer view object 42 within the buffer object 41, the component type of the buffer view object 42, the number of data items stored in the buffer view object 42, and the type of data items stored in the buffer view object 42. This information is described for each buffer view object.

[0045] In the example of C in FIG. 7, information such as "bufferView":0, "byteOffset":0, "componentType":5126, "count":2106," and "type":"VEC3" is shown. "bufferView":0" indicates that the identification information of the buffer view object 42 to which the accessor object 43 belongs is "0" (bufferView[0]), as shown in FIG. 6. Furthermore, "byteOffset":0" indicates that the byte offset of the buffer view object 42 (bufferView[0]) is 0 bytes. Furthermore, "componentType":5126" indicates that the component type is FLOAT type (OpenGL macro constant). Furthermore, "count":2106" indicates that 2106 pieces of data are stored in the buffer view object 42 (bufferView[0]). Furthermore, "type":"VEC3" indicates that the data (type) stored in the buffer view object 42 (bufferView[0]) is a three-dimensional vector.

[0046] All accesses to data other than images are defined by reference to this accessor object 43 (by specifying the index of the accessor).

[0047] Next, we will explain how to specify a 3D object in a point cloud in such a glTF2.0-compliant scene description (JSON format file). A point cloud is 3D content that represents a three-dimensional structure (an object with a three-dimensional shape) as a collection of many points. Point cloud data consists of position information (also called geometry) and attribute information (also called attributes) for each point. Attributes can contain any information. For example, attributes may include color information, reflectance information, normal information, etc. for each point. As such, point clouds have a relatively simple data structure, and by using a sufficient number of points, they can represent any three-dimensional structure with sufficient accuracy.

[0048] When a point cloud does not change in the time direction (also called static), 3D objects are specified using the mesh.primitives object of glTF2.0. Figure 8 shows an example of the configuration of objects in a scene description when the point cloud is static. Figure 9 shows an example of how the scene description is written.

[0049] As shown in Figure 9, the mode of the primitives object is set to 0, which indicates that the data is treated as points in a point cloud. As shown in Figures 8 and 9, the POSITION property of the attributes object in mesh.primitives specifies an accessor to a buffer that stores the position information of the points. Similarly, the COLOR property of the attributes object specifies an accessor to a buffer that stores the color information of the points. The buffer and bufferView may be one (the data may be stored in a single file).

[0050] Next, we will explain how to extend such scene description objects. Each object in glTF 2.0 can store newly defined objects within an extension object. Figure 10 shows an example of how to specify a newly defined object (ExtensionExample). As shown in Figure 10, when using a newly defined extension, the extension object name (ExtensionExample in the example in Figure 10) is written in "extensionUsed" and "extensionRequired." This indicates that this extension is an extension that will be used, or an extension that needs to be loaded.

[0051] <Client processing> Next, we will explain the processing of a client device in MPEG-I Scene Description. The client device acquires a scene description, acquires 3D object data based on the scene description, and generates a display image using the scene description and 3D object data.

[0052] As described in Non-Patent Document 2, in a client device, a presentation engine, a media access function, and the like perform processing. For example, as shown in FIG. 11, a presentation engine 51 of a client device 50 acquires the initial value of a scene description and information for updating the scene description (hereinafter also referred to as update information), and generates a scene description for the processing time. The presentation engine 51 then analyzes the scene description and identifies the media to be played (video, audio, etc.). The presentation engine 51 then requests a media access function 52 to acquire the media via a media access API (Application Program Interface). The presentation engine 51 also sets up pipeline processing, specifies buffers, and the like.

[0053] The media access function 52 acquires various media data requested by the presentation engine 51 from the cloud, local storage, etc. The media access function 52 supplies the acquired various media data (encoded data) to a pipeline 53.

[0054] The pipeline 53 decodes various data (encoded data) of the supplied media through pipeline processing and supplies the decoding result to a buffer 54. The buffer 54 holds various data of the supplied media.

[0055] The presentation engine 51 performs rendering and the like using various data of the media held in the buffer 54.

[0056] <Application of Timed media> In recent years, for example, as shown in Non-Patent Document 2, in MPEG-I Scene Description, it has been studied to extend glTF2.0 and apply timed media as 3D object content. Timed media is media data that changes in the time axis direction, like moving images in two-dimensional images.

[0057] glTF was only applicable to still image data as media data (3D object content). That is, glTF did not support media data of moving images. When moving a 3D object, an animation (a method of switching still images along the time axis) was applied.

[0058] In MPEG-I Scene Description, it has been studied to apply its glTF2.0, apply a JSON format file as a scene description, and further extend glTF so that timed media (for example, video data) can be handled as media data. In order to handle timed media, for example, the following extensions are made.

[0059] Fig. 12 is a diagram illustrating an extension for handling timed media. In the example of Fig. 12, an MPEG media object (MPEG_media) is a glTF extension, and is an object that specifies MPEG media attributes such as video data, for example, uri, track, renderingRate, startTime, etc.

[0060] 12, an MPEG texture video object (MPEG_texture_video) is provided as an extension object of the texture object (texture). The MPEG texture video object stores information of an accessor corresponding to a buffer object to be accessed. In other words, the MPEG texture video object is an object that specifies the index of an accessor corresponding to a buffer where the texture media specified by the MPEG media object (MPEG_media) is decoded and stored.

[0061] 13 is a diagram showing an example of description of an MPEG media object (MPEG_media) and an MPEG texture video object (MPEG_texture_video) in a scene description to explain extensions for handling timed media. In the example of FIG. 13, an MPEG texture video object (MPEG_texture_video) is set as an extension object (extensions) of a texture object (texture) in the second line from the top, as shown below. Then, the accessor index ("2" in this example) is specified as the value of that MPEG video texture object.

[0062] "texture":[{"sampler":0, "source":1, "extensions":{"MPEG_texture_video ":"accessor":2}}],

[0063] 13, an MPEG media object (MPEG_media) is set as a glTF extension object (extensions) on lines 7 to 16 from the top, as shown below: The value of the MPEG media object stores various information about the MPEG media object, such as the encoding and URI of the MPEG media object.

[0064] "MPEG_media":{ "media":[ {"name":"source_1", "renderingRate":30.0, "startTime":9.0, "timeOffset":0.0, "loop":"true", "controls":"false", "alternatives":[{"mimeType":"video / mp4;codecs=\"avc1.42E01E\"", "uri":"video1.mp4", "tracks":[{"track":""#track_ID=1"}] }] } ] }

[0065] Furthermore, each frame of data is decoded and stored sequentially in a buffer. However, since the position and other information fluctuate, a mechanism is provided in the scene description to store this fluctuating information and enable a renderer to read the data. For example, as shown in FIG. 12, an MPEG buffer circular object (MPEG_buffer_circular) is provided as an extension object of a buffer object. This MPEG buffer circular object stores information for dynamically storing data in the buffer object. For example, information indicating the data length of the buffer header and information indicating the number of frames are stored in this MPEG buffer circular object. The buffer header stores information such as an index, a timestamp and data length of the frame data to be stored, etc.

[0066] Also, as shown in Fig. 12, an MPEG accessor timed object (MPEG_timed_accessor) is provided as an extension object of the accessor object. In this case, since the media data is a moving image, the buffer view object (bufferView) referenced in the time direction may change (its position may fluctuate). Therefore, information indicating the buffer view object to be referenced is stored in this MPEG accessor timed object. For example, the MPEG accessor timed object stores information indicating a reference to the buffer view object (bufferView) in which the timed accessor information header (timedAccessor information header) is written. Note that the timed accessor information header is header information that stores, for example, dynamically changing accessor objects and information in the buffer view object.

[0067] 14 is a diagram showing an example of the description of an MPEG buffer circular object (MPEG_buffer_circular) and an MPEG accessor timed object (MPEG_accessor_timed) in a scene description to explain extensions for handling timed media. In the example of Fig. 14, on the fifth line from the top, an MPEG accessor timed object (MPEG_accessor_timed) is set as an extension object (extensions) of the accessor object (accessors) as shown below. Then, as the value of the MPEG accessor timed object, parameters such as the index of the buffer view object ("1" in this example), update rate (updateRate), and immutable information (immutable) and their values ​​are specified.

[0068] "MPEG_accessor_timed":{"bufferView":1, "updateRate":25.0, "immutable":1,"}

[0069] 14, an MPEG buffer circular object (MPEG_buffer_circular) is set as an extension object (extensions) of the buffer object (buffer) on the 13th line from the top, as shown below: Then, parameters such as a buffer frame count (count), a header length (headerLength), and an update rate (updateRate) and their values ​​are specified as values ​​of the MPEG buffer circular object.

[0070] "MPEG_buffer_circular":{"count":5, "headerLength":12, "updateRate":25.0}

[0071] FIG. 15 is a diagram for explaining an extension for handling time media. In FIG. 15, an example of the relationship between an MPEG accessor time object or an MPEG buffer circular object and an accessor object, a buffer view object, and a buffer object is shown.

[0072] In the MPEG buffer circular object of the buffer object, as described above, information necessary for storing time-varying data in the buffer area indicated by the buffer object, such as buffer frame count (count), header length (headerLength), update rate (updateRate), etc., is stored. Also, in the buffer header (bufferHeader) which is the header of the buffer area, parameters such as index, timestamp, data length (length), etc. are stored.

[0073] In the MPEG accessor time object of the accessor object, as described above, information regarding the buffer view object to be referenced, such as the index (bufferView) of the buffer view object, update rate (updateRate), immutable information, etc., is stored. Also, in this MPEG accessor time object, information regarding the buffer view object in which the time-domain accessor information header to be referenced is stored is stored. The time-domain accessor information header may store a timestamp delta (timestamp_delta), update data of the accessor object, update data of the buffer view object, etc.

[0074] <Client processing when using MPEG_texture_video> A scene description is spatial layout information for arranging one or more 3D objects in a 3D space. The contents of this scene description can be updated along the time axis. In other words, the layout of 3D objects can be updated over time. This section describes the client processing performed on the client device in this case.

[0075] Fig. 16 shows an example of the main configuration of a client device related to client processing, and Fig. 17 is a flowchart showing an example of the flow of the client processing. As shown in Fig. 16, the client device has a Presentation Engine (hereinafter also referred to as PE) 51, a Media Access Function (hereinafter also referred to as MAF) 52, a Pipeline 53, and a Buffer 54. Presentation Engine (PE) 51 has a glTF analysis unit 63 and a rendering processing unit 64.

[0076] A presentation engine (PE) 51 causes a media access function 52 to acquire media, acquires the data via a buffer 54, and performs processing related to display, etc. Specifically, the processing is performed in the following manner, for example.

[0077] When client processing begins, the glTF analysis unit 63 of the presentation engine (PE) 51 begins PE processing as shown in the example of Figure 17, and in step S21, obtains the SD (glTF) file 62, which is a scene description file, and parses the scene description.

[0078] In step S22, the glTF analyzer 63 checks the media associated with the 3D object (texture), the buffer in which the media will be stored after processing, and the accessor. In step S23, the glTF analyzer 63 notifies the media access function 52 of this information as a file acquisition request.

[0079] The media access function (MAF) 52 starts MAF processing as in the example of Fig. 17, and acquires the notification in step S11. In step S12, the media access function 52 acquires media (3D object file (mp4)) based on the notification.

[0080] In step S13, the media access function 52 decodes the acquired media (3D object file (mp4)). In step S14, the media access function 52 stores the media data obtained by the decryption in the buffer 54 based on a notification from the presentation engine (PE 51).

[0081] In step S24, the rendering processing unit 64 of the presentation engine 51 reads (acquires) the data at an appropriate timing from the buffer 54. In step S25, the rendering processing unit 64 performs rendering using the acquired data to generate an image for display.

[0082] The media access function 52 executes these processes for each time (each frame) by repeating the processes of step S13 and step S14. Also, the rendering processing unit 64 of the presentation engine 51 executes these processes for each time (each frame) by repeating the processes of step S24 and step S25. When the processing for all frames is completed, the media access function 52 ends the MAF process, and the presentation engine 51 ends the PE process. That is, the client process ends.

[0083] <Overview of V-PCC> By the way, as described in Non-Patent Document 3 for example, as an encoding method for a point cloud, which is a set of points having position information and attribute information (such as color and reflection) simultaneously on a three-dimensional space, V-PCC (Video based Point Cloud Compression) has been proposed, in which the point cloud is segmented to form regions, and each region is projected onto a plane and encoded by a video codec.

[0084] In V-PCC, the geometry and attributes of the point cloud are projected onto a two-dimensional plane for each small region. In the present disclosure, this small region may be referred to as a partial region. The image obtained by projecting the geometry and attributes onto the two-dimensional plane is also referred to as a projection image. Also, the projection image for each small region (partial region) is referred to as a patch. For example, the object 71 (3D data) in A of FIG. 18 is decomposed into patches 72 (2D data) as shown in B of FIG. 18. In the case of a geometry patch, each pixel value indicates the position information of the point. However, in that case, the position information of the point is expressed as the position information (depth value) in the direction perpendicular to the projection plane (depth direction).

[0085] Then, each patch generated in this manner is arranged in a frame image (also referred to as a video frame) of a video sequence. A frame image in which geometry patches are arranged is also referred to as a geometry video frame. A frame image in which attribute patches are arranged is also referred to as an attribute video frame. For example, from an object 71 in A of FIG. 18, a geometry video frame 81 in which geometry patches 73 are arranged as shown in C of FIG. 18, and an attribute video frame 82 in which attribute patches 74 are arranged as shown in D of FIG. 18 are generated. For example, each pixel value of the geometry video frame 81 indicates the above-mentioned depth value.

[0086] These video frames are then encoded using a coding method for two-dimensional images, such as AVC (Advanced Video Coding) or HEVC (High Efficiency Video Coding). In other words, point cloud data, which is 3D data representing a three-dimensional structure, can be encoded using a codec for two-dimensional images.

[0087] An occupancy map (also called an occupancy image) can also be used. The occupancy map is map information that indicates the presence or absence of a projected image (patch) for each NxN pixel of a geometry video frame or an attribute video frame. For example, the occupancy map indicates areas (NxN pixels) in the geometry video frame or the attribute video frame where a patch exists with a value of "1" and areas (NxN pixels) in which a patch does not exist with a value of "0."

[0088] By referencing this occupancy map, the decoder can determine whether an area contains a patch, thereby suppressing the effects of noise caused by encoding and decoding and restoring 3D data more accurately. For example, even if depth values ​​change due to encoding and decoding, the decoder can ignore depth values ​​in areas where no patches exist by referencing the occupancy map. In other words, by referencing the occupancy map, the decoder can avoid processing the depth values ​​as position information for 3D data.

[0089] For example, an occupancy map 83 as shown in Fig. 18E may be generated for the geometry video frame 11 and the attribute video frame 12. In the occupancy map 83, white areas indicate a value of "1" and black areas indicate a value of "0."

[0090] Such an occupancy map can be encoded as data (video frame) separate from the geometry video frame and the attribute video frame and transmitted to the decoding side. That is, the occupancy map can also be encoded using a coding method for two-dimensional images such as AVC or HEVC, just like the geometry video frame and the attribute video frame.

[0091] The coded data (bitstream) generated by coding a geometry video frame is also called a geometry video sub-bitstream. The coded data (bitstream) generated by coding an attribute video frame is also called an attribute video sub-bitstream. The coded data (bitstream) generated by coding an occupancy map is also called an occupancy map video sub-bitstream. Note that when there is no need to distinguish between the geometry video sub-bitstream, attribute video sub-bitstream, and occupancy map video sub-bitstream, they are all called video sub-bitstreams.

[0092] Furthermore, atlas information (atlas), which is information for reconstructing a point cloud (3D data) from the patches (2D data), is encoded and transmitted to the decoding side. The encoding method (and decoding method) of the atlas information is arbitrary. The encoded data (bitstream) generated by encoding the atlas information is also called the atlas sub-bitstream.

[0093] In the following, the point cloud (objects) is assumed to be able to change in the time direction (also referred to as dynamic), like a moving image of a two-dimensional image. That is, the geometry data and attribute data have a concept in the time direction and are data sampled at predetermined times, like a moving image of a two-dimensional image. Note that, like a video frame of a two-dimensional image, the data at each sampling time is referred to as a frame. That is, the point cloud data (geometry data and attribute data) is assumed to be composed of a plurality of frames, like a moving image of a two-dimensional image. In the present disclosure, this frame of the point cloud is also referred to as a point cloud frame. In the case of V-PCC, even for such a point cloud of a moving image (a plurality of frames), by video-framing each point cloud frame to form a video sequence, it can be efficiently encoded using the encoding method of a moving image.

[0094] <Structure of V-PCC Bitstream> The encoder multiplexes the encoded data of the geometry video frame, attribute video frame, occupancy map, and atlas information as described above to generate one bitstream. This bitstream is also referred to as a V-PCC bitstream.

[0095] FIG. 19 is a diagram showing a main configuration example of a V-PCC bitstream. As shown in FIG. 19, the V-PCC bitstream 91 includes a plurality of V-PCC units 92.

[0096] The V-PCC unit 92 includes a V-PCC unit header 93 and a V-PCC unit payload 94. The V-PCC unit header 93 includes information indicating the type of information stored in the V-PCC unit payload 94. The V-PCC unit payload 94 stores a V-PCC Parameter Set 95, a Geometry Video Data sub-bitstream 96, an Attribute Video Data sub-bitstream 97, an Occupancy Video Data sub-bitstream 98, an Atlas Data sub-bitstream 99, etc., according to the type signaled by the V-PCC unit header 93. The V-PCC Parameter Set 95 stores parameters related to the V-PCC unit 92.

[0097] <Method of Storage in ISOBMFF> Also, for example, as described in Non-Patent Document 4, a method of storing a V-PCC bitstream (also referred to as a V3C bitstream) composed of the encoded data of the point cloud encoded by this V-PCC in ISOBMFF has been studied. Non-Patent Document 4 defines two types of methods for storing the V3C bitstream in ISOBMFF: a single track structure and a multi-track structure.

[0098] The single track structure is a method of storing the V3C bitstream in one track. That is, in this case, the Geometry Video Data sub-bitstream, the Attribute Video Data sub-bitstream, the Occupancy Video Data sub-bitstream, and the Atlas Data sub-bitstream are stored in the same track.

[0099] The multi-track structure is a method of storing the geometry video sub-bitstream, attribute video sub-bitstream, occupancy video sub-bitstream, and atlas sub-bitstream in individual tracks. Since each video sub-bitstream is a conventional 2D video stream, it can be stored (managed) using the same method as for 2D. An example of a file structure when the multi-track structure is applied is shown in FIG. 20. As shown in FIG. 20, in the case of the multi-track structure, one track (the V3C atlas track) stores track references, which are information used to access other tracks (also called V3C video component tracks) that store V3C bitstreams. In other words, each V3C video component track is linked to the V3C atlas track by this track reference.

[0100] When 3D object content is distributed by applying MPEG-DASH (Moving Picture Experts Group Dynamic Adaptive Streaming over HTTP (Hypertext Transfer Protocol)), a preselection element and a preselection descriptor may be stored in an MPD (Media Presentation Description), which is a control file for controlling the distribution, as information for compiling the Adaptation Sets that make up the V-PCC. An example of such a description is shown in Fig. 21. In other words, in this case, these pieces of information in the MPD associate the individual bitstreams that make up the V3C bitstream with each other.

[0101] <Client processing pattern> A client device that plays back the content (3D data) decodes the V3C bitstream and reconstructs 3D data (e.g., a point cloud) from the resulting 2D data. In this case, the client device can reconstruct the 3D data using either the MAF (Media Access Function) or the PE (Presentation Engine). The data stored in the buffer differs in each case.

[0102] For example, as shown in Figure 22, in the MAF processing performed by the MAF, a process of acquiring a V-PCC file that constitutes a 3D object and a process of decoding the V-PCC file (V3C bitstream) are performed. When 3D data is reconstructed in the MAF, after the decoding process, a reconstruction process is performed as shown by the solid arrow at the top of Figure 22, and the processing result, i.e., the 3D data, is stored in a buffer. In this case, in the PE processing performed by the PE, the 3D data stored in the buffer is read and a rendering process is performed to generate a display image.

[0103] On the other hand, when 3D data is reconstructed in the PE, in the MAF processing, the decoding processing result, i.e., 2D data, etc., is stored in a buffer as shown by the dotted arrow at the bottom of Fig. 22. In this case, in the PE processing, the 2D data, etc. stored in the buffer is read out, the 3D data is reconstructed by a reconstruction processing, and a rendering processing is performed to generate an image for display.

[0104] Therefore, when 3D data (point cloud data) is reconstructed in MAF, attributes for the 3D data are stored in the scene description, as shown in Figure 23. However, the data stored in the buffer is the reconstructed data. In contrast, the data specified by MPEG_media is the data before reconstruction. In other words, attributes are not linked one-to-one with tracks. Therefore, the MPEG_media referenced from each buffer is the V3C atlas track that compiles all component data.

[0105] On the other hand, when 3D data (point cloud data) is reconstructed in the PE, the V3C decoded V3C component stream is stored in the buffer. In other words, 2D data, etc. are stored in the buffer. Therefore, the scene description stores attributes for the V3C component (2D data).

[0106] In this case, there are two ways to link the V3C component data stored in the buffer with the track indicated by MPEG_media: For example, as shown in Fig. 24, the buffer and the V3C component track may be linked one-to-one. Alternatively, as shown in Fig. 25, each buffer may refer to a V3C atlas track that compiles all the component data.

[0107] <Applying Scene Description> As described above, the scene description configurations differ between the playback method in which 3D data is reconstructed using MAF and the playback method in which 3D data is reconstructed using PE. As a result, it was not possible to use a single scene description for both playback methods. Therefore, in order to make a single piece of content compatible with both playback methods, it was necessary to prepare a scene description file for each playback method for that piece of content.

[0108] Therefore, for example, in a device that generates a scene description file, a scene description file must be generated for each playback method, which may increase the load associated with generating the scene description files. Furthermore, in this case, each scene description file corresponds to a different playback method, but the 3D objects to be placed are the same. Therefore, generating a scene description file for each playback method can be considered redundant processing.

[0109] Furthermore, for devices that manage the generated content files and scene description files, the management can become complicated, increasing the load associated with the management. Furthermore, for devices that play 3D content using scene description files, the load associated with selecting and acquiring scene description files used for playback can increase. For example, simply acquiring a scene description file can require unnecessary processing and transmission of unnecessary information, such as confirmation of the playback method.

[0110] <3. Scene description supporting multiple playback methods> <Identification using extensions (#1)> Therefore, as shown in the top row of the table in Fig. 26, an extension for distinguishing between properties for a playback method in which 3D data is reconstructed in the MAF (also referred to as MAF reconstruction properties) and properties for a playback method in which 3D data is reconstructed in the PE (also referred to as PE reconstruction properties) may be stored in the scene description (hereinafter also referred to as SD) (#1). Then, the MAF reconstruction properties and the PE reconstruction properties may be distinguished based on the extension, and properties according to the playback method may be selected.

[0111] For example, an information processing device (e.g., a client device) is provided with a file processing unit that selects a property corresponding to a playback method for 3D data based on an extension defined in a scene description, and uses the selected property to process the 3D data using that playback method.

[0112] For example, in an information processing method, a property corresponding to a playback method for 3D data is selected based on an extension defined in a scene description, and the selected property is used to process the 3D data using that playback method.

[0113] For example, an information processing device (for example, a file generating device) may include a file generating unit that generates a scene description file that stores an extension for identifying properties for each playback method of 3D data.

[0114] For example, in the information processing method, a scene description file is generated that stores an extension for identifying properties for each playback method of 3D data.

[0115] By combining scene descriptions corresponding to each playback method into one, a scene description containing information about multiple playback methods is created. However, simply combining multiple scene description files into one (for example, connecting them in series) makes it difficult to identify which part of the scene description corresponds to which playback method. In other words, it has been difficult to create a scene description file that supports multiple playback methods.

[0116] In contrast, by using the extensions described above, the scene description can be configured so that properties can be identified for each playback method, allowing one scene description to be compatible with multiple playback methods.

[0117] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0118] For example, in a device that generates a scene description file, there is no need to generate a scene description file for each playback method for a single piece of content, so it is possible to suppress an increase in the load associated with generating scene description files, such as suppressing an increase in redundant processing.

[0119] Furthermore, in a device that manages the generated content files and scene description files, the management of the scene description files can be made easier, and an increase in the load associated with managing the scene description files can be suppressed.

[0120] Furthermore, in a device that uses a scene description file to play back 3D content, it is possible to suppress an increase in unnecessary processing and transmission of unnecessary information for playback, such as confirmation of playback method and selection of scene description file, etc. Therefore, it is possible to suppress an increase in the load related to the use of scene description files.

[0121] <Extension in Primitives> The location of this extension is arbitrary. For example, in the case of (#1), as shown in the second row from the top of the table in Fig. 26, this extension may be stored in one of the primitives of the scene description (#1-1).

[0122] <Extensions for each playback method> In the case of (#1-1), for example, as shown in the third row from the top of the table in Figure 26, a first extension that stores attribute properties for a playback method in which 3D data is reconstructed in MAF (also referred to as attribute properties for MAF reconstruction) and a second extension that stores attribute properties for a playback method in which 3D data is reconstructed in PE (also referred to as attribute properties for PE reconstruction) may be stored within one primitive of the scene description (#1-1-1).

[0123] For example, a first extension and a second extension may be defined in one primitive of a scene description, with one or more first attribute properties corresponding to a first playback method of the 3D data stored in the first extension and one or more second attribute properties corresponding to a second playback method of the 3D data stored in the second extension. Then, in an information processing device (e.g., a client device), a file processing unit may select one or more first attribute properties stored in the first extension or one or more second attribute properties stored in the second extension according to the playback method of the 3D data.

[0124] For example, in an information processing device (e.g., a file generation device), a file generation unit may define a first extension and a second extension in one primitive of a scene description file. The file generation unit may then store one or more first attribute properties corresponding to a first playback method of the 3D data in the first extension. The file generation unit may then store one or more second attribute properties corresponding to a second playback method of the 3D data in the second extension.

[0125] An example of the main configuration of objects in a scene description in this case is shown in FIG. 27. An example of the description is shown in FIG. 28. As shown in FIGS. 27 and 28, in this example, an extension (MPEG_VPCC_reconstructMAF) is defined in primitives, and MAF reconstruction attribute properties (POSITION, COLOR, etc.) are stored in this extension (inside a rectangular box 202 in FIG. 28). When reconstructing 3D data in MAF, a file processing unit of an information processing device (e.g., a client device) can supply the reconstructed data from the MAF to a PE via a buffer by using accessors associated with these MAF reconstruction attribute properties.

[0126] Furthermore, an extension (MPEG_VPCC_reconstructPE) is defined within the primitives, and PE reconstruction attribute properties (POSITION, _MPEG_ATLAS, _MPEG_ATTR, _MPEG_OCCU, etc.) are stored within the extension (in a rectangular box 201 in FIG. 28). When reconstructing 3D data in a PE, a file processing unit of an information processing device (for example, a client device) can supply pre-reconstruction data from the MAF to the PE via a buffer by using accessors associated with these PE reconstruction attribute properties.

[0127] This allows the scene description to be configured so that properties can be identified for each playback method, making it possible for one scene description to be compatible with multiple playback methods.

[0128] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0129] In this example, each extension name (e.g., MPEG_VPCC_reconstructMAF, MPEG_VPCC_reconstructPE) may be used as identification information. That is, for example, a file processing unit of an information processing device (e.g., a client device) can identify whether an extension stores attribute properties for MAF reconstruction or attribute properties for PE reconstruction based on the extension name. Therefore, the file processing unit can correctly select an extension in which desired attribute properties are stored and use the desired attribute properties.

[0130] <Extension availability> Also, in the case of (#1-1), for example, as shown in the fourth row from the top of the table in Figure 26, an extension that stores MAF reconstruction attribute properties and PE reconstruction attribute properties may be stored within one primitive of the scene description (#1-1-2).

[0131] For example, an extension may be defined within one primitive of a scene description. One or more first attribute properties corresponding to a first playback method of the 3D data may then be stored within the primitive. Furthermore, one or more second attribute properties corresponding to a second playback method of the 3D data may then be stored within the extension. Then, in an information processing device (e.g., a client device), a file processing unit may select one or more first attribute properties stored within the primitive or one or more second attribute properties stored within the extension, depending on the playback method of the 3D data.

[0132] For example, in an information processing device (e.g., a file generating device), a file generating unit may define an extension within one primitive of a scene description file. The file generating unit may then store one or more first attribute properties corresponding to a first playback method of the 3D data within the primitive. The file generating unit may then store one or more second attribute properties corresponding to a second playback method of the 3D data within the extension.

[0133] An example of the main configuration of objects in a scene description in this case is shown in FIG. 29. An example of the description is shown in FIG. 30. As shown in FIGS. 29 and 30, in this example, an extension (MPEG_VPCC_reconstructPE) is defined in primitives, and PE reconstruction attribute properties (POSITION, _MPEG_ATLAS, _MPEG_ATTR, _MPEG_OCCU, etc.) are stored in this extension (in a rectangular box 221 in FIG. 30). When reconstructing 3D data in a PE, a file processing unit of an information processing device (e.g., a client device) can supply pre-reconstruction data from the MAF to the PE via a buffer by using accessors associated with these PE reconstruction attribute properties.

[0134] Furthermore, MAF reconstruction attribute properties (POSITION, COLOR, etc.) are stored in the primitives. When reconstructing 3D data in MAF, the file processing unit of the information processing device (e.g., client device) can supply the reconstructed data from MAF to the PE via a buffer by using the accessors associated with these MAF reconstruction attribute properties.

[0135] This allows the scene description to be configured so that properties can be identified for each playback method, making it possible for one scene description to be compatible with multiple playback methods.

[0136] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0137] In this example, the presence or absence of an extension may be used as identification information. That is, for example, a file processing unit of an information processing device (e.g., a client device) can identify whether a property is an attribute property for MAF reconstruction or an attribute property for PE reconstruction based on whether it is stored in an extension. Therefore, the file processing unit can correctly select and use the desired attribute property.

[0138] <Property regulations> Note that, instead of using the Attributes property, a new property for each attribute of the V-PCC may be defined and used. For example, in the case of (#1-1), as shown in the fifth row from the top of the table in Fig. 26, a first extension that stores a property for a playback method in which 3D data is reconstructed in the MAF (also referred to as MAF reconstruction property) and a second extension that stores a property for a playback method in which 3D data is reconstructed in the PE (also referred to as PE reconstruction property) may be stored in one primitive of the scene description (#1-1-3).

[0139] For example, a first extension and a second extension may be defined within one primitive of a scene description. Then, one or more first properties corresponding to a first playback method of the 3D data may be stored within the first extension. Furthermore, one or more second properties corresponding to a second playback method of the 3D data may be stored within the second extension. Then, in an information processing device (e.g., a client device), a file processing unit may select one or more first properties stored within the first extension or one or more second properties stored within the second extension, depending on the playback method of the 3D data.

[0140] For example, in an information processing device (e.g., a file generation device), a file generation unit may define a first extension and a second extension in one primitive of a scene description file. The file generation unit may then store one or more first properties corresponding to a first playback method of the 3D data in the first extension. The file generation unit may then store one or more second properties corresponding to a second playback method of the 3D data in the second extension.

[0141] An example of the main configuration of objects in a scene description in this case is shown in FIG. 31. An example of the description is shown in FIG. 32. As shown in FIGS. 31 and 32, in this example, an extension (MPEG_VPCC_reconstructPE) is defined in primitives, and newly defined PE reconstruction properties (MPEG_VPCC_GEO, MPEG_VPCC_ATL, MPEG_VPCC_ATT, MPEG_VPCC_OCU, etc.) are stored in this extension (inside a rectangular box 241 in FIG. 32). When reconstructing 3D data in a PE, a file processing unit of an information processing device (e.g., a client device) can supply pre-reconstruction data from the MAF to the PE via a buffer by using accessors associated with these PE reconstruction properties.

[0142] Furthermore, an extension (MPEG_VPCC_reconstructMAF) is defined within the primitives, and newly defined MAF reconstruction properties (MPEG_VPCC_POS, MPEG_VPCC_COL, etc.) are stored within the extension (inside a rectangular box 242 in FIG. 32). When reconstructing 3D data in MAF, a file processing unit of an information processing device (for example, a client device) can supply the reconstructed data from the MAF to a PE via a buffer by using an accessor associated with these MAF reconstruction properties.

[0143] This allows the scene description to be configured so that properties can be identified for each playback method, making it possible for one scene description to be compatible with multiple playback methods.

[0144] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0145] In this example, each extension name (e.g., MPEG_VPCC_reconstructMAF, MPEG_VPCC_reconstructPE) may be used as identification information. That is, for example, a file processing unit of an information processing device (e.g., a client device) can identify whether an extension stores properties for MAF reconstruction or properties for PE reconstruction based on the extension name. Therefore, the file processing unit can correctly select an extension that stores a desired property and use the desired property.

[0146] This method of defining and using new properties for each attribute of a V-PCC without using the attribute property may also be applied when the presence or absence of an extension is used as identification information, as described with reference to Figures 29 and 30.

[0147] For example, in the case of (#1-1), as shown in the sixth row from the top of the table in Figure 26, a MAF reconfiguration property and an extension that stores a PE reconfiguration property may be stored within one primitive of the scene description (#1-1-4).

[0148] For example, an extension may be defined within one primitive of a scene description. One or more first properties corresponding to a first playback method of the 3D data may then be stored within the primitive. Furthermore, one or more second properties corresponding to a second playback method of the 3D data may then be stored within the extension. Then, in an information processing device (e.g., a client device), a file processing unit may select one or more first properties stored within the primitive or one or more second properties stored within the extension, depending on the playback method of the 3D data.

[0149] For example, in an information processing device (e.g., a file generation device), a file generation unit may define an extension within one primitive of a scene description file. The file generation unit may then store one or more first properties corresponding to a first playback method of the 3D data within the primitive. The file generation unit may then store one or more second properties corresponding to a second playback method of the 3D data within the extension.

[0150] This allows the scene description to be configured so that properties can be identified for each playback method, making it possible for one scene description to be compatible with multiple playback methods.

[0151] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0152] In this example, the presence or absence of an extension may be used as identification information. That is, for example, a file processing unit of an information processing device (e.g., a client device) can identify whether a property is for MAF reconfiguration or for PE reconfiguration based on whether it is stored in an extension. Therefore, the file processing unit can correctly select and use the desired property.

[0153] <Identification using alternative sequences (#2)> Although an example of identifying properties for each playback method using an extension has been described above, any method for identifying properties for each playback method may be used and is not limited to this example. For example, properties for each playback method may be identified using an alternatives array that indicates that elements of the array are used for alternatives.

[0154] For example, as shown in the bottom row of the table in Fig. 26, a first alternatives array having MAF reconfiguration attribute properties as elements and a second alternatives array having PE reconfiguration attribute properties as elements may be stored in an extension stored in one primitive of a scene description (#2).The MAF reconfiguration attribute properties and PE reconfiguration attribute properties may then be identified based on these alternatives arrays, and properties appropriate for the playback method may be selected.

[0155] For example, an information processing device (e.g., a client device) is provided with a file processing unit that selects an alternatives array corresponding to a playback method for 3D data from the alternatives arrays defined in the scene description, and processes the 3D data using that playback method by utilizing properties that are elements of the selected alternatives array.

[0156] For example, in an information processing method, an alternatives array corresponding to a playback method for 3D data is selected from the alternatives arrays defined in the scene description, and the 3D data is processed using that playback method by utilizing properties that are elements of the selected alternatives array.

[0157] For example, an information processing device (for example, a file generating device) may include a file generating unit that generates a scene description file that stores a plurality of alternatives arrays whose elements are properties corresponding to the same playback method of 3D data.

[0158] For example, in the information processing method, a scene description file is generated that stores a plurality of alternatives arrays whose elements are properties corresponding to the same playback method of 3D data.

[0159] In this way, by using the alternatives array, the scene description can be configured so that properties can be identified for each playback method, and therefore one scene description can be used for multiple playback methods.

[0160] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0161] For example, in a device that generates a scene description file, there is no need to generate a scene description file for each playback method for a single piece of content, so it is possible to suppress an increase in the load associated with generating scene description files, such as suppressing an increase in redundant processing.

[0162] Furthermore, in a device that manages the generated content files and scene description files, the management of the scene description files can be made easier, and an increase in the load associated with managing the scene description files can be suppressed.

[0163] Furthermore, in a device that uses a scene description file to play back 3D content, it is possible to suppress an increase in unnecessary processing and transmission of unnecessary information for playback, such as confirmation of playback method and selection of scene description file, etc. Therefore, it is possible to suppress an increase in the load related to the use of scene description files.

[0164] In this case, too, the alternatives array (or the extension that stores it) may be placed anywhere. For example, this alternatives array (or the extension that stores it) may be stored in one of the primitives of the scene description.

[0165] For example, an extension may be defined within one primitive of a scene description. A first alternatives array and a second alternatives array may be defined within the extension. The first alternatives array may have, as elements, one or more first properties corresponding to a first playback method of the 3D data. The second alternatives array may have, as elements, one or more second properties corresponding to a second playback method of the 3D data. In an information processing device (e.g., a client device), a file processor may select the first alternatives array and process the 3D data using the first playback method by using the one or more first properties. In a second playback method, the file processor may select the second alternatives array and process the 3D data using the second playback method by using the one or more second properties.

[0166] For example, in an information processing device (e.g., a file generation device), a file generation unit may define an extension within one primitive of a scene description file. The file generation unit may then store within the extension a first alternatives array whose elements are one or more first properties corresponding to a first playback method of the 3D data. The file generation unit may also store within the extension a second alternatives array whose elements are one or more second properties corresponding to a second playback method of the 3D data.

[0167] An example of the main configuration of objects in a scene description in this case is shown in FIG. 33. An example of the description is shown in FIG. 34. As shown in FIGS. 33 and 34, in this example, an extension (MPEG_VPCC_ClientInfo) is defined in primitives, and an alternatives array whose elements are attribute properties for PE reconstruction (POSITION, _MPEG_ATLAS, _MPEG_ATTR, _MPEG_OCCU, etc.) is stored in that extension (inside a rectangular box 261 in FIG. 34). In addition, an alternatives array whose elements are attribute properties for MAF reconstruction (POSITION, COLOR, etc.) is also stored in that extension (inside a rectangular box 262 in FIG. 34). The alternatives array is an array that indicates that the elements of that array are used as alternatives. In other words, by selecting the alternatives array to apply, attribute properties for each playback method are selected.

[0168] As shown in Figure 34, a client type (ClientType) is specified within each element of the alternatives array, and this parameter indicates which playback method (reconstruction method) the attributes corresponding to are stored in.

[0169] <Extension in Mesh Object (#3)> The extensions described above in the examples (#1) and (#2) may be defined in a mesh object of the scene description. For example, as shown in the top row of the table in Fig. 35, an extension for identifying a MAF reconfiguration (attribute) property and a PE reconfiguration (attribute) property may be stored in one mesh object of the scene description (#3).

[0170] <Extensions for each playback method> In the case of (#3), for example, as shown in the second row from the top of the table in Figure 35, a first extension that stores first primitives that store attribute properties for MAF reconstruction, and a second extension that stores second primitives that store attribute properties for PE reconstruction may be stored within one mesh object of the scene description (#3-1).

[0171] For example, a first extension and a second extension may be defined in one mesh object of the scene description. Then, one or more first attribute properties corresponding to a first playback method of the 3D data may be stored in the first extension. Furthermore, one or more second attribute properties corresponding to a second playback method of the 3D data may be stored in the second extension. Then, in an information processing device (e.g., a client device), a file processing unit may select one or more first attribute properties stored in the first extension or one or more second attribute properties stored in the second extension, depending on the playback method of the 3D data.

[0172] For example, in an information processing device (e.g., a file generating device), a file generating unit may define a first extension and a second extension in one mesh object of a scene description file. The file generating unit may then store one or more first attribute properties corresponding to a first playback method of the 3D data in the first extension. The file generating unit may also store one or more second attribute properties corresponding to a second playback method of the 3D data in the second extension.

[0173] An example of a portion of the object configuration in the scene description in this case is shown in Figure 36. As shown in Figure 36, in this example, an extension (MPEG_VPCC_reconstructPE) is defined in a mesh object (mesh), and primitives in which PE reconstruction attribute properties are stored are stored in that extension. Also, an extension (MPEG_VPCC_reconstructMAF) is defined in that mesh object (mesh), and primitives in which MAF reconstruction attribute properties are stored are stored in that extension.

[0174] For example, a file processing unit of an information processing device (e.g., a client device) can supply pre-reconstruction data from the MAF to the PE via a buffer by selecting MPEG_VPCC_reconstructPE and using an accessor associated with the PE reconstruction attribute property. Also, a file processing unit of an information processing device (e.g., a client device) can supply post-reconstruction data from the MAF to the PE via a buffer by selecting MPEG_VPCC_reconstructMAF and using an accessor associated with the MAF reconstruction attribute property.

[0175] In other words, the scene description can be configured so that properties can be identified for each playback method, allowing one scene description to be compatible with multiple playback methods.

[0176] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0177] In this example, each extension name (e.g., MPEG_VPCC_reconstructMAF, MPEG_VPCC_reconstructPE) may be used as identification information. That is, for example, a file processing unit of an information processing device (e.g., a client device) can identify whether an extension stores attribute properties for MAF reconstruction or attribute properties for PE reconstruction based on the extension name. Therefore, the file processing unit can correctly select an extension in which desired attribute properties are stored and use the desired attribute properties.

[0178] <Extension availability> Also, in the case of (#3), for example, as shown in the third row from the top of the table in Figure 35, a first primitive that stores attribute properties for MAF reconstruction and an extension that stores second primitives that store attribute properties for PE reconstruction may be stored within one mesh object of the scene description (#3-2).

[0179] For example, an extension may be defined in one mesh object of the scene description. One or more first attribute properties corresponding to a first playback method of the 3D data may be stored in the mesh object. Also, one or more second attribute properties corresponding to a second playback method of the 3D data may be stored in the extension. Then, in an information processing device (e.g., a client device), a file processing unit may select one or more first attribute properties stored in the mesh object or one or more second attribute properties stored in the extension according to the playback method of the 3D data.

[0180] For example, in an information processing device (e.g., a file generating device), a file generating unit may define an extension in one mesh object of a scene description file. The file generating unit may then store one or more first attribute properties corresponding to a first playback method of the 3D data in the primitives. The file generating unit may also store one or more second attribute properties corresponding to a second playback method of the 3D data in the extension.

[0181] This allows the scene description to be configured so that properties can be identified for each playback method, making it possible for one scene description to be compatible with multiple playback methods.

[0182] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0183] In this example, the presence or absence of an extension may be used as identification information. That is, for example, a file processing unit of an information processing device (e.g., a client device) can identify whether a property is an attribute property for MAF reconstruction or an attribute property for PE reconstruction based on whether it is stored in an extension. Therefore, the file processing unit can correctly select and use the desired attribute property.

[0184] <Property regulations> Note that, instead of using the attribute property, a new property for each attribute of the V-PCC may be defined and used. For example, in the case of (#3), as shown in the fourth row from the top of the table in Fig. 35, a first extension that stores first primitives that store MAF reconstruction properties and a second extension that stores second primitives that store PE reconstruction properties may be stored in one mesh object of the scene description (#3-3).

[0185] For example, a first extension and a second extension may be defined in one mesh object of a scene description. One or more first properties corresponding to a first playback method of the 3D data may be stored in the first extension. One or more second properties corresponding to a second playback method of the 3D data may be stored in the second extension. In an information processing device (e.g., a client device), a file processing unit may select one or more first properties stored in the first extension or one or more second properties stored in the second extension depending on the playback method of the 3D data.

[0186] For example, in an information processing device (e.g., a file generating device), a file generating unit may define a first extension and a second extension in one mesh object of a scene description file. The file generating unit may then store one or more first properties corresponding to a first playback method of the 3D data in the first extension. The file generating unit may also store one or more second properties corresponding to a second playback method of the 3D data in the second extension.

[0187] This allows the scene description to be configured so that properties can be identified for each playback method, making it possible for one scene description to be compatible with multiple playback methods.

[0188] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0189] In this example, each extension name (e.g., MPEG_VPCC_reconstructMAF, MPEG_VPCC_reconstructPE) may be used as identification information. That is, for example, a file processing unit of an information processing device (e.g., a client device) can identify whether an extension stores properties for MAF reconstruction or properties for PE reconstruction based on the extension name. Therefore, the file processing unit can correctly select an extension that stores a desired property and use the desired property.

[0190] Also, for example, in the case of (#3), as shown in the fifth row from the top of the table in Figure 35, a first primitive that stores MAF reconstruction properties and an extension that stores second primitives that store PE reconstruction properties may be stored within one mesh object of the scene description (#3-4).

[0191] For example, the extension may be defined in one mesh object of the scene description. One or more first properties corresponding to a first playback method of the 3D data may be stored in the mesh object. One or more second properties corresponding to a second playback method of the 3D data may be stored in the extension. In an information processing device (e.g., a client device), a file processing unit may select one or more first properties stored in the mesh object or one or more second properties stored in the extension according to the playback method of the 3D data.

[0192] For example, in an information processing device (e.g., a file generating device), a file generating unit may define an extension in one mesh object of a scene description file, and store one or more first properties corresponding to a first playback method of the 3D data in the mesh object. Also, the file generating unit may store one or more second properties corresponding to a second playback method of the 3D data in the extension.

[0193] This allows the scene description to be configured so that properties can be identified for each playback method, making it possible for one scene description to be compatible with multiple playback methods.

[0194] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0195] In this example, the presence or absence of an extension may be used as identification information. That is, for example, a file processing unit of an information processing device (e.g., a client device) can identify whether a property is for MAF reconfiguration or for PE reconfiguration based on whether it is stored in an extension. Therefore, the file processing unit can correctly select and use the desired property.

[0196] <Identification using alternative sequences> Also, for example, in the case of (#3), as shown in the bottom row of the table in Fig. 35, an extension stored in one mesh object of the scene description may store a first alternatives array whose elements are first primitives that store MAF reconfiguration attribute properties, and a second alternatives array whose elements are second primitives that store PE reconfiguration attribute properties (#3-5). Then, based on these alternatives arrays, the MAF reconfiguration attribute properties and the PE reconfiguration attribute properties may be identified, and properties according to the playback method may be selected.

[0197] For example, an extension may be defined within one mesh object of the scene description. A first alternatives array and a second alternatives array may be defined within the extension. The first alternatives array may have one or more first properties corresponding to a first playback method of the 3D data as elements. The second alternatives array may have one or more second properties corresponding to a second playback method of the 3D data as elements. In an information processing device (e.g., a client device), a file processor may select the first alternatives array and process the 3D data using the first playback method by utilizing the one or more first properties when applying the first playback method. The file processor may select the second alternatives array and process the 3D data using the second playback method by utilizing the one or more second properties when applying the second playback method.

[0198] For example, in an information processing device (e.g., a file generation device), a file generation unit may define an extension within one mesh object of a scene description file. The file generation unit may then store within the extension a first alternatives array whose elements are one or more first properties corresponding to a first playback method of the 3D data. The file generation unit may also store within the extension a second alternatives array whose elements are one or more second properties corresponding to a second playback method of the 3D data.

[0199] In this case as well, a client type (ClientType) is defined within the elements of each alternatives array, and this parameter indicates which playback method (reconstruction method) the properties corresponding to are stored.

[0200] In this way, by using the alternatives array, the scene description can be configured so that properties can be identified for each playback method, and therefore one scene description can be used for multiple playback methods.

[0201] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0202] <Extension in node (#4)> The extensions described above in the examples (#1) to (#3) may be defined within a node of the scene description. For example, as shown in the top row of the table in Fig. 37, an extension for distinguishing between a MAF reconfiguration (attribute) property and a PE reconfiguration (attribute) property may be stored within one node of the scene description (#4).

[0203] <Extensions for each playback method> In the case of (#4), for example, as shown in the second row from the top of the table in Figure 37, one node of the scene description may store a first extension associated with a first mesh object storing first primitives that store attribute properties for MAF reconstruction, and a second extension associated with a second mesh object that stores second primitives that store attribute properties for PE reconstruction (#4-1).

[0204] For example, a first extension and a second extension may be defined within one node of a scene description. One or more first attribute properties corresponding to a first playback method of the 3D data may be associated with the first extension. One or more second attribute properties corresponding to a second playback method of the 3D data may be associated with the second extension. In an information processing device (e.g., a client device), a file processing unit may select one or more first attribute properties associated with the first extension or one or more second attribute properties associated with the second extension according to the playback method of the 3D data.

[0205] For example, in an information processing device (e.g., a file generation device), a file generation unit may define a first extension and a second extension within one node of a scene description file. The file generation unit may then associate one or more first attribute properties corresponding to a first playback method of the 3D data with the first extension. The file generation unit may also associate one or more second attribute properties corresponding to a second playback method of the 3D data with the second extension.

[0206] An example of a portion of the object configuration in the scene description in this case is shown in Figure 38. As shown in Figure 38, in this example, an extension (MPEG_VPCC_reconstructPE) is defined in the node, and a mesh object (mesh) that stores (the primitives that store) attribute properties for PE reconstruction is associated with the extension. Also, an extension (MPEG_VPCC_reconstructMAF) is defined in the node, and a mesh object (mesh) that stores (the primitives that store) attribute properties for MAF reconstruction is associated with the extension.

[0207] Therefore, for example, a file processing unit of an information processing device (e.g., a client device) can select MPEG_VPCC_reconstructPE and use an accessor associated with that MPEG_VPCC_reconstructPE (and its associated PE reconstruction attribute properties) to supply pre-reconstruction data from the MAF to the PE via a buffer. Also, a file processing unit of an information processing device (e.g., a client device) can select MPEG_VPCC_reconstructMAF and use an accessor associated with that MPEG_VPCC_reconstructMAF (and its associated MAF reconstruction attribute properties) to supply post-reconstruction data from the MAF to the PE via a buffer.

[0208] In other words, the scene description can be configured so that properties can be identified for each playback method, allowing one scene description to be compatible with multiple playback methods.

[0209] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0210] In this example, each extension name (e.g., MPEG_VPCC_reconstructMAF, MPEG_VPCC_reconstructPE) may be used as identification information. That is, for example, a file processing unit of an information processing device (e.g., a client device) can identify whether an extension stores attribute properties for MAF reconstruction or attribute properties for PE reconstruction based on the extension name. Therefore, the file processing unit can correctly select an extension in which desired attribute properties are stored and use the desired attribute properties.

[0211] <Extension availability> In addition, in the case of (#4), for example, as shown in the third row from the top of the table in Figure 37, a first mesh object storing a first primitive that stores attribute properties for MAF reconstruction may be associated within one node of the scene description, and an extension associated with a second mesh object storing second primitives that store attribute properties for PE reconstruction may be stored (#4-2).

[0212] For example, an extension may be defined within one node of a scene description. One or more first attribute properties corresponding to a first playback method of the 3D data may then be associated with the node. One or more second attribute properties corresponding to a second playback method of the 3D data may then be associated with the extension. Then, in an information processing device (e.g., a client device), a file processing unit may select one or more first attribute properties associated with the node or one or more second attribute properties associated with the extension, depending on the playback method of the 3D data.

[0213] For example, in an information processing device (e.g., a file generating device), a file generating unit may define an extension within one node of a scene description file. The file generating unit may then associate one or more first attribute properties corresponding to a first playback method of the 3D data with the node. The file generating unit may also associate one or more second attribute properties corresponding to a second playback method of the 3D data with the extension.

[0214] This allows the scene description to be configured so that properties can be identified for each playback method, making it possible for one scene description to be compatible with multiple playback methods.

[0215] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0216] In this example, the presence or absence of an extension may be used as identification information. That is, for example, a file processing unit of an information processing device (e.g., a client device) can identify whether a property is an attribute property for MAF reconstruction or an attribute property for PE reconstruction based on whether it is stored in an extension. Therefore, the file processing unit can correctly select and use the desired attribute property.

[0217] <Property regulations> Note that, instead of using the Attributes property, a new property for each attribute of the V-PCC may be defined and used. For example, in the case of (#4), as shown in the fourth row from the top of the table in Fig. 37, a first extension associated with a first mesh object storing first primitives that store MAF reconstruction properties, and a second extension associated with a second mesh object storing second primitives that store PE reconstruction properties may be stored in one node of the scene description (#4-3).

[0218] For example, a first extension and a second extension may be defined within one node of a scene description. One or more first properties corresponding to a first playback method of the 3D data may be associated with the first extension. One or more second properties corresponding to a second playback method of the 3D data may be associated with the second extension. In an information processing device (e.g., a client device), a file processing unit may select one or more first properties associated with the first extension or one or more second properties associated with the second extension depending on the playback method of the 3D data.

[0219] For example, in an information processing device (e.g., a file generation device), a file generation unit may define a first extension and a second extension within one node of a scene description file. The file generation unit may then associate one or more first properties corresponding to a first playback method of the 3D data with the first extension. The file generation unit may also associate one or more second properties corresponding to a second playback method of the 3D data with the second extension.

[0220] This allows the scene description to be configured so that properties can be identified for each playback method, making it possible for one scene description to be compatible with multiple playback methods.

[0221] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0222] In this example, each extension name (e.g., MPEG_VPCC_reconstructMAF, MPEG_VPCC_reconstructPE) may be used as identification information. That is, for example, a file processing unit of an information processing device (e.g., a client device) can identify whether an extension stores properties for MAF reconstruction or properties for PE reconstruction based on the extension name. Therefore, the file processing unit can correctly select an extension that stores a desired property and use the desired property.

[0223] Also, for example, in the case of (#4), as shown in the fifth row from the top of the table in Figure 37, an extension may be stored within one node of the scene description, to which a first mesh object storing first primitives storing properties for MAF reconstruction and a second mesh object storing second primitives storing properties for PE reconstruction are associated (#4-4).

[0224] For example, an extension may be defined within one node of a scene description. One or more first properties corresponding to a first playback method of the 3D data may then be associated with the node. One or more second properties corresponding to a second playback method of the 3D data may then be associated with the extension. In an information processing device (e.g., a client device), a file processing unit may select one or more first properties associated with the node or one or more second properties associated with the extension, depending on the playback method of the 3D data.

[0225] For example, in an information processing device (e.g., a file generating device), a file generating unit may define an extension within one node of a scene description file. The file generating unit may then associate one or more first properties corresponding to a first playback method of the 3D data with the node. The file generating unit may also associate one or more second properties corresponding to a second playback method of the 3D data with the extension.

[0226] This allows the scene description to be configured so that properties can be identified for each playback method, making it possible for one scene description to be compatible with multiple playback methods.

[0227] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0228] In this example, the presence or absence of an extension may be used as identification information. That is, for example, a file processing unit of an information processing device (e.g., a client device) can identify whether a property is for MAF reconfiguration or for PE reconfiguration based on whether it is stored in an extension. Therefore, the file processing unit can correctly select and use the desired property.

[0229] <Identification using alternative sequences> Also, for example, in the case of (#4), as shown in the bottom row of the table in Fig. 35, a first alternatives array having elements associated with first mesh objects storing first primitives that store MAF reconfiguration attribute properties, and a second alternatives array having elements associated with second mesh objects that store second primitives that store PE reconfiguration attribute properties may be stored in the extension of one node of the scene description (#4-5). Then, the MAF reconfiguration attribute properties and the PE reconfiguration attribute properties may be identified based on these alternatives arrays, and properties according to the playback method may be selected.

[0230] For example, an extension may be defined within one node of a scene description. A first alternatives array and a second alternatives array may be defined within the extension. The first alternatives array may have elements associated with one or more first properties corresponding to a first playback method of the 3D data. The second alternatives array may have elements associated with one or more second properties corresponding to a second playback method of the 3D data. In an information processing device (e.g., a client device), a file processor may select the first alternatives array and process the 3D data using the first playback method by utilizing the one or more first properties when applying the first playback method. In a file processor may select the second alternatives array and process the 3D data using the second playback method by utilizing the one or more second properties when applying the second playback method.

[0231] For example, in an information processing device (e.g., a file generation device), a file generation unit may define an extension within one node of a scene description file. The file generation unit may then store within the extension a first alternatives array having elements associated with one or more first properties corresponding to a first playback method of the 3D data. The file generation unit may also store within the extension a second alternatives array having elements associated with one or more second properties corresponding to a second playback method of the 3D data.

[0232] In this case as well, a client type (ClientType) is defined within the elements of each alternatives array, and this parameter indicates which playback method (reconstruction method) the properties corresponding to are stored.

[0233] In this way, by using the alternatives array, the scene description can be configured so that properties can be identified for each playback method, and therefore one scene description can be used for multiple playback methods.

[0234] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0235] The present technology may be applied by appropriately combining the above-described multiple elements.

[0236] 4. First Embodiment <File generation device> The present technology described above can be applied to any device. Fig. 39 is a block diagram showing an example of the configuration of a file generation device, which is one aspect of an information processing device to which the present technology is applied. The file generation device 300 shown in Fig. 39 is a device that encodes 3D object content (e.g., 3D data such as a point cloud) and stores it in a file container such as ISOBMFF. The file generation device 300 also generates a scene description file of the 3D object content.

[0237] Note that Fig. 39 shows the main processing units, data flows, etc., and does not necessarily include everything shown in Fig. 39. In other words, file generation device 300 may have processing units that are not shown as blocks in Fig. 39, or processes or data flows that are not shown as arrows, etc. in Fig. 39.

[0238] As shown in FIG. 39 , the file generation device 300 includes a control unit 301 and a file generation processing unit 302. The control unit 301 controls the file generation processing unit 302. The file generation processing unit 302 is controlled by the control unit 301 to perform processing related to file generation. For example, the file generation processing unit 302 may acquire data of 3D object content to be stored in a file. The file generation processing unit 302 may also generate a content file by storing the acquired data of the 3D object content in a file container. The file generation processing unit 302 may also generate a scene description corresponding to the 3D object content and store it in a scene description file. The file generation processing unit 302 may output the generated file to the outside of the file generation device 300. For example, the file generation processing unit 302 may upload the generated file to a distribution server or the like.

[0239] The file generation processing unit 302 includes an input unit 311 , a preprocessing unit 312 , an encoding unit 313 , a file generation unit 314 , a recording unit 315 , and an output unit 316 .

[0240] The input unit 311 performs processing related to acquisition of 3D object content data. For example, the input unit 311 may acquire the 3D object content data from outside the file generation device 300. This 3D object content data may be any 3D data that represents the three-dimensional structure of an object. For example, it may be point cloud data. The input unit 311 may supply the acquired 3D object content data to the preprocessing unit 312.

[0241] The preprocessing unit 312 executes preprocessing related to the data of the 3D object content before encoding. For example, the preprocessing unit 312 may acquire the data of the 3D object content supplied from the input unit 311. The preprocessing unit 312 may also acquire information necessary for generating a scene description from the acquired data of the 3D object content, etc. The preprocessing unit 312 may also supply the acquired information to the file generation unit 314. The preprocessing unit 312 may also supply the data of the 3D object content to the encoding unit 313.

[0242] The encoding unit 313 executes processing related to encoding of 3D object content data. For example, the encoding unit 313 may acquire 3D object content data supplied from the preprocessing unit 312. The encoding unit 313 may also encode the acquired 3D object content data to generate the encoded data. The encoding unit 313 may also supply the generated encoded data of the 3D object content to the file generation unit 314 as a V3C bitstream.

[0243] The file generation unit 314 performs processing related to the generation of files, etc. For example, the file generation unit 314 may acquire a V3C bitstream supplied from the encoding unit 313. The file generation unit 314 may also acquire information supplied from the preprocessing unit 312. The file generation unit 314 may also generate a file container (content file) that stores the V3C bitstream supplied from the encoding unit 313. The specifications of this content file (file container) are arbitrary, and any file that can store a V3C bitstream may be used. For example, it may be ISOBMFF.

[0244] Furthermore, the file generation unit 314 may generate a scene description corresponding to the V3C bitstream using the information supplied from the preprocessing unit 312. Then, the file generation unit 314 may generate a scene description file and store the generated scene description. Furthermore, when the V3C bitstream is distributed in a format conforming to MPEG-DASH, the file generation unit 314 may generate an MPD corresponding to the V3C bitstream. Furthermore, the file generation unit 314 may supply the generated files, etc. (ISOBMFF, scene description file, MPD, etc.) to the recording unit 315.

[0245] The recording unit 315 has any recording medium, such as a hard disk or semiconductor memory, and executes processing related to recording of data. For example, the recording unit 315 may record files, etc., supplied from the file generation unit 314 on the recording medium. Furthermore, the recording unit 315 may read files, etc., recorded on the recording medium in accordance with a request from the control unit 301 or the output unit 316, or at a predetermined timing, and supply the files, etc., to the output unit 316.

[0246] The output unit 316 may acquire the file etc. supplied from the recording unit 315 and output the file etc. to an external device (such as a distribution server or a playback device) outside the file generation device 300.

[0247] In the file generation device 300 configured as above, the present technology described above in <3. Scene description supporting multiple playback methods> may be applied.

[0248] For example, the file generation unit 314 may generate a scene description file that stores an extension for identifying properties for each playback method of 3D data.

[0249] In this case, the file generator 314 may define a first extension and a second extension within one primitive of the scene description file. The file generator 314 may then store one or more first attribute properties corresponding to a first playback method of the 3D data within the first extension. The file generator 314 may also store one or more second attribute properties corresponding to a second playback method of the 3D data within the second extension.

[0250] Alternatively, the file generator 314 may define an extension within one primitive of the scene description file. The file generator 314 may then store, within the primitive, one or more first attribute properties corresponding to a first playback method for the 3D data. The file generator 314 may also store, within the extension, one or more second attribute properties corresponding to a second playback method for the 3D data.

[0251] The file generator 314 may also define a first extension and a second extension within one primitive of the scene description file. The file generator 314 may then store one or more first properties corresponding to a first playback method of the 3D data within the first extension. The file generator 314 may also store one or more second properties corresponding to a second playback method of the 3D data within the second extension.

[0252] Alternatively, the file generator 314 may define an extension within one primitive of the scene description file. The file generator 314 may then store one or more first properties corresponding to a first playback method of the 3D data within the primitive. The file generator 314 may also store one or more second properties corresponding to a second playback method of the 3D data within the extension.

[0253] The file generator 314 may also define a first extension and a second extension within one mesh object of the scene description file. The file generator 314 may then store one or more first attribute properties corresponding to a first playback method of the 3D data within the first extension. The file generator 314 may also store one or more second attribute properties corresponding to a second playback method of the 3D data within the second extension.

[0254] Alternatively, the file generator 314 may define an extension within one mesh object of the scene description file. The file generator 314 may then store, within the mesh object, one or more first attribute properties corresponding to a first playback method for the 3D data. The file generator 314 may also store, within the extension, one or more second attribute properties corresponding to a second playback method for the 3D data.

[0255] The file generator 314 may also define a first extension and a second extension within one mesh object of the scene description file. The file generator 314 may then store one or more first properties corresponding to a first playback method of the 3D data within the first extension. The file generator 314 may also store one or more second properties corresponding to a second playback method of the 3D data within the second extension.

[0256] Alternatively, the file generator 314 may define an extension within one mesh object of the scene description file. The file generator 314 may then store one or more first properties corresponding to a first playback method of the 3D data within the mesh object. The file generator 314 may also store one or more second properties corresponding to a second playback method of the 3D data within the extension.

[0257] The file generator 314 may also define a first extension and a second extension within one node of the scene description file. The file generator 314 may then associate one or more first attribute properties corresponding to a first playback method of the 3D data with the first extension. The file generator 314 may also associate one or more second attribute properties corresponding to a second playback method of the 3D data with the second extension.

[0258] The file generator 314 may also define an extension within one node of the scene description file. The file generator 314 may then associate one or more first attribute properties corresponding to a first playback method of the 3D data with the node. The file generator 314 may also associate one or more second attribute properties corresponding to a second playback method of the 3D data with the extension.

[0259] The file generator 314 may also define a first extension and a second extension within one node of the scene description file. The file generator 314 may then associate one or more first properties corresponding to a first playback method of the 3D data with the first extension. The file generator 314 may also associate one or more second properties corresponding to a second playback method of the 3D data with the second extension.

[0260] The file generator 314 may also define an extension within one node of the scene description file. The file generator 314 may then associate one or more first properties corresponding to a first playback method of the 3D data with the node. The file generator 314 may also associate one or more second properties corresponding to a second playback method of the 3D data with the extension.

[0261] Furthermore, the file generation unit 314 may generate a scene description file that stores a plurality of alternatives arrays whose elements are properties that correspond to the same playback method of 3D data.

[0262] In this case, the file generation unit 314 may define an extension within one primitive of the scene description file. Then, the file generation unit 314 may store within the extension a first alternatives array whose elements are one or more first properties corresponding to a first playback method of the 3D data. Furthermore, the file generation unit 314 may store within the extension a second alternatives array whose elements are one or more second properties corresponding to a second playback method of the 3D data.

[0263] The file generator 314 may also define an extension within one mesh object of the scene description file. The file generator 314 may then store within the extension a first alternatives array whose elements are one or more first properties corresponding to a first playback method of the 3D data. The file generator 314 may also store within the extension a second alternatives array whose elements are one or more second properties corresponding to a second playback method of the 3D data.

[0264] The file generator 314 may also define an extension within one node of the scene description file. The file generator 314 may then store within the extension a first alternatives array having elements associated with one or more first properties corresponding to a first playback method of the 3D data. The file generator 314 may also store within the extension a second alternatives array having elements associated with one or more second properties corresponding to a second playback method of the 3D data.

[0265] Of course, other techniques described above in <3. Scene description supporting multiple playback methods> may also be applied. Also, multiple techniques may be applied in appropriate combination.

[0266] With this configuration, the file generation device 300 can configure the scene description so that the properties can be identified for each playback method, allowing one scene description to be compatible with multiple playback methods.

[0267] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0268] <File generation process flow 1> An example of the flow of file generation processing executed by file generation device 300 configured as above will be described with reference to the flowchart in Fig. 40. The example in Fig. 40 shows an example of the flow of file generation processing when properties for each playback method are identified using extensions.

[0269] In this case, when the file generation process is started, the input unit 311 of the file generation device 300 acquires data of a 3D object (3D data) in step S301. For example, the input unit 311 acquires point cloud data as this 3D data.

[0270] In step S302, the preprocessing unit 312 performs preprocessing on the 3D object data acquired in step S301. For example, the preprocessing unit 312 acquires, from the 3D object data, information used to generate a scene description, which is spatial arrangement information for arranging one or more 3D objects in a 3D space.

[0271] In step S303, the file generation unit 314 uses the information to generate a scene description file that stores an extension for identifying the MAF reconstruction (attributes) property and the PE reconstruction (attributes) property. That is, the file generation unit 314 generates a scene description file that stores an extension for identifying the (attributes) property for each 3D data playback method.

[0272] In step S304, the encoding unit 313 encodes the point cloud data (3D data) acquired in step S301, and generates the encoded data (V3C bitstream).

[0273] In step S305, the file generation unit 314 generates a content file (ISOBMFF) that stores the V3C bitstream generated in step S304.

[0274] In step S306, the recording unit 315 records the generated scene description file and content file on a recording medium.

[0275] In step S307, output unit 316 reads the file or the like recorded in step S306 from the recording medium and outputs the read file to the outside of file generation device 300 at a predetermined timing. For example, output unit 316 may transmit (upload) the file or the like read from the recording medium to another device such as a distribution server or a playback device via a communication medium such as a network. Furthermore, output unit 316 may record the file or the like read from the recording medium on an external recording medium such as removable media. In this case, the output file or the like may be supplied to another device (such as a distribution server or a playback device) via the external recording medium, for example.

[0276] When the process of step S307 ends, the file generation process ends.

[0277] By performing the file generation process in this way, the scene description can be configured so that properties can be identified for each playback method, allowing one scene description to be compatible with multiple playback methods.

[0278] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0279] In step S303, the file generation unit 314 may define a first extension and a second extension in one primitive of the scene description file. Then, the file generation unit 314 may store one or more first attribute properties corresponding to a first playback method of the 3D data in the first extension. Furthermore, the file generation unit 314 may store one or more second attribute properties corresponding to a second playback method of the 3D data in the second extension.

[0280] In step S303, the file generation unit 314 may define an extension in one of the primitives of the scene description file. The file generation unit 314 may then store, in the primitive, one or more first attribute properties corresponding to a first playback method for the 3D data. The file generation unit 314 may also store, in the extension, one or more second attribute properties corresponding to a second playback method for the 3D data.

[0281] In step S303, the file generation unit 314 may define a first extension and a second extension in one primitive of the scene description file. Then, the file generation unit 314 may store one or more first properties corresponding to a first playback method of the 3D data in the first extension. Furthermore, the file generation unit 314 may store one or more second properties corresponding to a second playback method of the 3D data in the second extension.

[0282] In step S303, the file generation unit 314 may define an extension in one of the primitives of the scene description file. The file generation unit 314 may then store one or more first properties corresponding to a first playback method for the 3D data in the primitive. The file generation unit 314 may also store one or more second properties corresponding to a second playback method for the 3D data in the extension.

[0283] In step S303, the file generation unit 314 may define a first extension and a second extension in one mesh object of the scene description file. The file generation unit 314 may then store one or more first attribute properties corresponding to a first playback method of the 3D data in the first extension. The file generation unit 314 may also store one or more second attribute properties corresponding to a second playback method of the 3D data in the second extension.

[0284] In step S303, the file generation unit 314 may define an extension in one mesh object of the scene description file. The file generation unit 314 may then store one or more first attribute properties corresponding to a first playback method of the 3D data in the mesh object. The file generation unit 314 may also store one or more second attribute properties corresponding to a second playback method of the 3D data in the extension.

[0285] In step S303, the file generation unit 314 may define a first extension and a second extension in one mesh object of the scene description file. The file generation unit 314 may then store one or more first properties corresponding to a first playback method of the 3D data in the first extension. The file generation unit 314 may also store one or more second properties corresponding to a second playback method of the 3D data in the second extension.

[0286] Alternatively, the file generator 314 may define an extension within one mesh object of the scene description file. The file generator 314 may then store one or more first properties corresponding to a first playback method of the 3D data within the mesh object. The file generator 314 may also store one or more second properties corresponding to a second playback method of the 3D data within the extension.

[0287] In step S303, the file generation unit 314 may define a first extension and a second extension within one node of the scene description file. The file generation unit 314 may then associate one or more first attribute properties corresponding to a first playback method of the 3D data with the first extension. The file generation unit 314 may also associate one or more second attribute properties corresponding to a second playback method of the 3D data with the second extension.

[0288] In step S303, the file generation unit 314 may define an extension within one node of the scene description file. The file generation unit 314 may then associate one or more first attribute properties corresponding to a first playback method for the 3D data with the node. The file generation unit 314 may also associate one or more second attribute properties corresponding to a second playback method for the 3D data with the extension.

[0289] In step S303, the file generation unit 314 may define a first extension and a second extension within one node of the scene description file. The file generation unit 314 may then associate one or more first properties corresponding to a first playback method of the 3D data with the first extension. The file generation unit 314 may also associate one or more second properties corresponding to a second playback method of the 3D data with the second extension.

[0290] In step S303, the file generation unit 314 may define an extension within one node of the scene description file. The file generation unit 314 may then associate one or more first properties corresponding to a first playback method for the 3D data with the node. The file generation unit 314 may also associate one or more second properties corresponding to a second playback method for the 3D data with the extension.

[0291] Of course, other techniques described above in <3. Scene description supporting multiple playback methods> may also be applied. Also, multiple techniques may be applied in appropriate combination.

[0292] <File generation process flow 2> Next, an example of the flow of file generation processing when properties for each playback method are identified using an alternatives array will be described with reference to the flowchart in FIG.

[0293] In this case, when the file generation process is started, the processes of steps S351 and S352 are executed in the same manner as the processes of steps S301 and S302 in FIG.

[0294] In step S353, the file generation unit 314 generates a scene description file that stores an alternatives array having elements of the MAF reconstruction attribute property and the PE reconstruction attribute property. That is, the file generation unit 314 generates a scene description file that stores a plurality of alternatives arrays having elements of properties corresponding to the same playback method of 3D data.

[0295] When the process of step S353 ends, the processes of steps S354 to S357 are executed in the same manner as the processes of steps S304 to S307 in FIG.

[0296] When the process of step S357 ends, the file generation process ends.

[0297] By performing the file generation process in this way, the scene description can be configured so that properties can be identified for each playback method, allowing one scene description to be compatible with multiple playback methods.

[0298] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0299] In step S353, the file generation unit 314 may define an extension within one primitive of the scene description file. Then, the file generation unit 314 may store within the extension a first alternatives array whose elements are one or more first properties corresponding to a first playback method of the 3D data. Furthermore, the file generation unit 314 may store within the extension a second alternatives array whose elements are one or more second properties corresponding to a second playback method of the 3D data.

[0300] In step S353, the file generation unit 314 may define an extension in one mesh object of the scene description file. Then, the file generation unit 314 may store, in the extension, a first alternatives array whose elements are one or more first properties corresponding to a first playback method of the 3D data. Furthermore, the file generation unit 314 may store, in the extension, a second alternatives array whose elements are one or more second properties corresponding to a second playback method of the 3D data.

[0301] In step S353, the file generation unit 314 may define an extension within one node of the scene description file. The file generation unit 314 may then store within the extension a first alternatives array having elements associated with one or more first properties corresponding to a first playback method of the 3D data. The file generation unit 314 may also store within the extension a second alternatives array having elements associated with one or more second properties corresponding to a second playback method of the 3D data.

[0302] Of course, other techniques described above in <3. Scene description supporting multiple playback methods> may also be applied. Also, multiple techniques may be applied in appropriate combination.

[0303] 5. Second Embodiment <Client device> Fig. 42 is a block diagram showing an example of the configuration of a client device, which is one aspect of an information processing device to which the present technology is applied. The client device 400 shown in Fig. 42 is a playback device that performs playback processing of 3D object content based on a scene description. For example, the client device 400 plays back 3D object data stored in a content file generated by the file generation device 300. In doing so, the client device 400 performs processing related to the playback based on the scene description.

[0304] Note that Fig. 42 shows the main processing units, data flows, etc., and is not necessarily all that is shown in Fig. 42. In other words, in client device 400, there may be processing units that are not shown as blocks in Fig. 42, and there may be processing or data flows that are not shown as arrows, etc. in Fig. 42.

[0305] 42, the client device 400 has a control unit 401 and a playback processing unit 402. The control unit 401 performs processing related to control of the playback processing unit 402. The playback processing unit 402 performs processing related to playback of 3D object data.

[0306] The playback processing unit 402 includes a file acquisition unit 411 , a file processing unit 412 , a decoding unit 413 , a display information generation unit 414 , a display unit 415 , and a display control unit 416 .

[0307] The file acquisition unit 411 performs processing related to file acquisition. For example, the file acquisition unit 411 may acquire a file or the like supplied from outside the client device 400, such as a distribution server or the file generation device 300. The file acquisition unit 411 may also acquire a file or the like stored in a local storage (not shown). For example, the file acquisition unit 411 may acquire a scene description file. The file acquisition unit 411 may also acquire a content file. For example, the file acquisition unit 411 may supply the acquired file to the file processing unit 412. The file acquisition unit 411 may perform processing related to this file acquisition under the control of the file processing unit 412. For example, the file acquisition unit 411 may acquire a file requested by the file processing unit 412 from an external or local storage and supply it to the file processing unit 412.

[0308] The file processing unit 412 performs processing related to processing of files, etc. For example, the file processing unit 412 may have the configuration (for example, the MAF 52, the buffer 54, the PE 51, etc.) as described with reference to Fig. 16 .

[0309] The file processing unit 412 may control the file acquisition unit 411 to acquire a scene description file from outside the client device 400, from local storage, etc. Furthermore, the file processing unit 412 may control the file acquisition unit 411 based on the scene description file to acquire a V3C bitstream from a content file outside the client device 400, from local storage, etc.

[0310] The file processing unit 412 may also control the decoding unit 413 to decode the V3C bitstream. The file processing unit 412 may then reconstruct 3D data using the data obtained by the decoding. In this case, the file processing unit 412 may reconstruct the 3D data in the MAF 52 or in the PE 51.

[0311] The file processing unit 412 may also control the display information generation unit 414 to render the reconstructed 3D data and generate a display image. The file processing unit 412 may also control the display unit 415 to display the display image.

[0312] The decoding unit 413 performs processing related to decoding. For example, the decoding unit 413 may be controlled by the file processing unit 412 and may decode a V3C bitstream supplied from the file processing unit 412. The decoding unit 413 may also supply the file processing unit 412 with data obtained by the decoding.

[0313] The display information generation unit 414 performs processing related to display. For example, the display information generation unit 414 may render the 3D data supplied from the file processing unit 412 under the control of the file processing unit 412 to generate a display image or the like. In this case, the display information generation unit 414 may also follow the control of the display control unit 416 as appropriate. Furthermore, the display information generation unit 414 may supply the generated display image or the like to the file processing unit 412.

[0314] Display unit 415 has a display device and performs processing related to image display. For example, display unit 415 may display a display image (a display image generated by display information generation unit 414) supplied from file processing unit 412 under the control of file processing unit 412 using the display device.

[0315] The display control unit 416 executes processing related to the control of image display. For example, the display control unit 416 may acquire information such as a scene description supplied from the file processing unit 412. Furthermore, the display control unit 416 may control the display information generation unit 414 based on that information.

[0316] In the client device 400 configured as above, the present technology described above in <3. Scene description supporting multiple playback methods> may be applied.

[0317] For example, the file processing unit 412 may select a property corresponding to a playback method for the 3D data based on the extensions specified in the scene description, and use the selected property to process the 3D data using that playback method.

[0318] In this case, a first extension and a second extension may be defined within one primitive of the scene description. Then, one or more first attribute properties corresponding to a first playback method of the 3D data may be stored within the first extension. Also, one or more second attribute properties corresponding to a second playback method of the 3D data may be stored within the second extension. Then, the file processing unit 412 may select one or more first attribute properties stored within the first extension or one or more second attribute properties stored within the second extension, depending on the playback method of the 3D data.

[0319] Alternatively, an extension may be defined within one of the primitives of the scene description. One or more first attribute properties corresponding to a first playback method of the 3D data may be stored within the primitive. One or more second attribute properties corresponding to a second playback method of the 3D data may be stored within the extension. The file processing unit 412 may then select one or more first attribute properties stored within the primitive or one or more second attribute properties stored within the extension, depending on the playback method of the 3D data.

[0320] Furthermore, a first extension and a second extension may be defined within one primitive of the scene description. One or more first properties corresponding to a first playback method of the 3D data may be stored within the first extension. One or more second properties corresponding to a second playback method of the 3D data may be stored within the second extension. The file processing unit 412 may select one or more first properties stored within the first extension or one or more second properties stored within the second extension, depending on the playback method of the 3D data.

[0321] Alternatively, an extension may be defined within one of the primitives of the scene description. One or more first properties corresponding to a first playback method of the 3D data may be stored within the primitive. One or more second properties corresponding to a second playback method of the 3D data may be stored within the extension. The file processing unit 412 may select one or more first properties to be stored within the primitive or one or more second properties to be stored within the extension, depending on the playback method of the 3D data.

[0322] Furthermore, a first extension and a second extension may be defined within one mesh object of the scene description. One or more first attribute properties corresponding to a first playback method of the 3D data may be stored within the first extension. One or more second attribute properties corresponding to a second playback method of the 3D data may be stored within the second extension. The file processing unit 412 may then select one or more first attribute properties stored within the first extension or one or more second attribute properties stored within the second extension, depending on the playback method of the 3D data.

[0323] Alternatively, an extension may be defined within one mesh object of the scene description. One or more first attribute properties corresponding to a first playback method of the 3D data may be stored within the mesh object. One or more second attribute properties corresponding to a second playback method of the 3D data may be stored within the extension. The file processing unit 412 may then select one or more first attribute properties stored within the mesh object or one or more second attribute properties stored within the extension, depending on the playback method of the 3D data.

[0324] Furthermore, a first extension and a second extension may be defined within one mesh object of the scene description. One or more first properties corresponding to a first playback method of the 3D data may be stored within the first extension. One or more second properties corresponding to a second playback method of the 3D data may be stored within the second extension. The file processing unit 412 may select one or more first properties stored within the first extension or one or more second properties stored within the second extension, depending on the playback method of the 3D data.

[0325] Alternatively, an extension may be defined within one mesh object of the scene description. One or more first properties corresponding to a first playback method of the 3D data may be stored within the mesh object. One or more second properties corresponding to a second playback method of the 3D data may be stored within the extension. The file processing unit 412 may select one or more first properties stored within the mesh object or one or more second properties stored within the extension, depending on the playback method of the 3D data.

[0326] Furthermore, a first extension and a second extension may be defined within one node of the scene description. One or more first attribute properties corresponding to a first playback method of the 3D data may be associated with the first extension. One or more second attribute properties corresponding to a second playback method of the 3D data may be associated with the second extension. The file processing unit 412 may then select one or more first attribute properties associated with the first extension or one or more second attribute properties associated with the second extension, depending on the playback method of the 3D data.

[0327] Furthermore, an extension may be defined within one node of the scene description. One or more first attribute properties corresponding to a first playback method of the 3D data may be associated with the node. One or more second attribute properties corresponding to a second playback method of the 3D data may be associated with the extension. The file processing unit 412 may then select one or more first attribute properties associated with the node or one or more second attribute properties associated with the extension, depending on the playback method of the 3D data.

[0328] Furthermore, a first extension and a second extension may be defined within one node of the scene description. One or more first properties corresponding to a first playback method of the 3D data may be associated with the first extension. One or more second properties corresponding to a second playback method of the 3D data may be associated with the second extension. The file processing unit 412 may select one or more first properties associated with the first extension or one or more second properties associated with the second extension depending on the playback method of the 3D data.

[0329] Furthermore, an extension may be defined within one node of the scene description. One or more first properties corresponding to a first playback method of the 3D data may be associated with the node. One or more second properties corresponding to a second playback method of the 3D data may be associated with the extension. The file processing unit 412 may then select one or more first properties associated with the node or one or more second properties associated with the extension, depending on the playback method of the 3D data.

[0330] In addition, the file processing unit 412 may select an alternatives array from the alternatives arrays specified in the scene description that corresponds to the playback method of the 3D data, and process the 3D data using that playback method by using properties that are elements of the selected alternatives array.

[0331] In this case, an extension may be defined within one primitive of the scene description. A first alternatives array and a second alternatives array may be defined within the extension. The first alternatives array may have elements that are one or more first properties corresponding to a first playback method of the 3D data. The second alternatives array may have elements that are one or more second properties corresponding to a second playback method of the 3D data. When applying the first playback method, the file processing unit 412 may select the first alternatives array and process the 3D data using the first playback method, utilizing the one or more first properties. When applying the second playback method, the file processing unit 412 may select the second alternatives array and process the 3D data using the second playback method, utilizing the one or more second properties.

[0332] An extension may be defined within one mesh object of the scene description. A first alternatives array and a second alternatives array may be defined within the extension. The first alternatives array may have elements that are one or more first properties corresponding to a first playback method of the 3D data. The second alternatives array may have elements that are one or more second properties corresponding to a second playback method of the 3D data. When applying the first playback method, the file processing unit 412 may select the first alternatives array and process the 3D data using the first playback method, utilizing the one or more first properties. When applying the second playback method, the file processing unit 412 may select the second alternatives array and process the 3D data using the second playback method, utilizing the one or more second properties.

[0333] An extension may be defined within one node of the scene description. A first alternatives array and a second alternatives array may be defined within the extension. The first alternatives array may have elements associated with one or more first properties corresponding to a first playback method of the 3D data. The second alternatives array may have elements associated with one or more second properties corresponding to a second playback method of the 3D data. When applying the first playback method, the file processing unit 412 may select the first alternatives array and process the 3D data using the first playback method, utilizing the one or more first properties. When applying the second playback method, the file processing unit 412 may select the second alternatives array and process the 3D data using the second playback method, utilizing the one or more second properties.

[0334] Of course, other techniques described above in <3. Scene description supporting multiple playback methods> may also be applied. Also, multiple techniques may be applied in appropriate combination.

[0335] The client device 400 having such a configuration can identify properties for each playback method in the scene description, so that one scene description can be made compatible with multiple playback methods.

[0336] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0337] <Recycling process flow> An example of the flow of playback processing executed by the client device 400 configured as above will be described with reference to the flowchart of FIG.

[0338] When the playback process is started, the file processing unit 412 of the client device 400 controls the file acquisition unit 411 in step S401 to acquire a scene description file.

[0339] In step S402, the file processing unit 412 analyzes the scene description file acquired in step S401 and selects an attribute property (for example, an attribute property for MAF reconstruction or an attribute property for PE reconstruction) corresponding to the playback method of its own 3D object content (a method for reconstructing 3D data).

[0340] In this case, the file processing unit 412 may select a property corresponding to the playback method of the 3D data based on the extension specified in the scene description, and use the selected property to process the 3D data using that playback method.

[0341] In addition, the file processing unit 412 may select an alternatives array from the alternatives arrays specified in the scene description that corresponds to the playback method of the 3D data, and process the 3D data using that playback method by using properties that are elements of the selected alternatives array.

[0342] In step S403, the file processing unit 412 analyzes the scene description file acquired in step S401, and controls the file acquisition unit 411 in accordance with the analysis result to acquire coded data (V3C bitstream) of the 3D data.

[0343] In step S404, the file processing unit 412 controls the decoding unit 413 to decode the V3C bitstream obtained by the processing in step S402.

[0344] In step S405, the file processing unit 412 reconstructs 3D data using the data obtained by the processing in step S403, in accordance with the analysis result of the scene description file.

[0345] In step S406, the file processing unit 412 controls the display information generation unit 414 to perform rendering using the 3D data reconstructed in step S405 and generate an image for display.

[0346] In step S407, file processing unit 412 controls display unit 415 to display the display image generated in step S406. When the process of step S407 ends, the playback process ends.

[0347] By performing the playback process in this manner, the client device 400 can identify the properties in the scene description for each playback method, so that one scene description can be made to correspond to multiple playback methods.

[0348] In other words, a single scene description can support multiple playback methods for content, without the need to prepare multiple scene descriptions. This reduces the burden of processing related to scene descriptions, such as the generation, management, and use of scene description files.

[0349] Note that a first extension and a second extension may be defined within one primitive of the scene description. Then, one or more first attribute properties corresponding to a first playback method of the 3D data may be stored within the first extension. Furthermore, one or more second attribute properties corresponding to a second playback method of the 3D data may be stored within the second extension. Then, in step S402, the file processing unit 412 may select one or more first attribute properties stored within the first extension or one or more second attribute properties stored within the second extension, depending on the playback method of the 3D data.

[0350] Alternatively, an extension may be defined within one of the primitives of the scene description. One or more first attribute properties corresponding to a first playback method of the 3D data may be stored within the primitive. One or more second attribute properties corresponding to a second playback method of the 3D data may be stored within the extension. In step S402, the file processing unit 412 may select one or more first attribute properties stored within the primitive or one or more second attribute properties stored within the extension, depending on the playback method of the 3D data.

[0351] Furthermore, a first extension and a second extension may be defined within one primitive of the scene description. One or more first properties corresponding to a first playback method of the 3D data may be stored within the first extension. One or more second properties corresponding to a second playback method of the 3D data may be stored within the second extension. Then, in step S402, the file processing unit 412 may select one or more first properties stored within the first extension or one or more second properties stored within the second extension, depending on the playback method of the 3D data.

[0352] Alternatively, an extension may be defined within one of the primitives of the scene description. One or more first properties corresponding to a first playback method of the 3D data may be stored within the primitive. One or more second properties corresponding to a second playback method of the 3D data may be stored within the extension. In step S402, the file processing unit 412 may select one or more first properties to be stored within the primitive or one or more second properties to be stored within the extension, depending on the playback method of the 3D data.

[0353] Furthermore, a first extension and a second extension may be defined within one mesh object of the scene description. One or more first attribute properties corresponding to a first playback method of the 3D data may be stored within the first extension. One or more second attribute properties corresponding to a second playback method of the 3D data may be stored within the second extension. Then, in step S402, the file processing unit 412 may select one or more first attribute properties stored within the first extension or one or more second attribute properties stored within the second extension, depending on the playback method of the 3D data.

[0354] Alternatively, an extension may be defined within one mesh object of the scene description. One or more first attribute properties corresponding to a first playback method of the 3D data may be stored within the mesh object. One or more second attribute properties corresponding to a second playback method of the 3D data may be stored within the extension. In step S402, the file processing unit 412 may select one or more first attribute properties stored within the mesh object or one or more second attribute properties stored within the extension, depending on the playback method of the 3D data.

[0355] Furthermore, a first extension and a second extension may be defined within one mesh object of the scene description. One or more first properties corresponding to a first playback method of the 3D data may be stored within the first extension. One or more second properties corresponding to a second playback method of the 3D data may be stored within the second extension. Then, in step S402, the file processing unit 412 may select one or more first properties stored within the first extension or one or more second properties stored within the second extension, depending on the playback method of the 3D data.

[0356] Alternatively, an extension may be defined within one mesh object of the scene description. One or more first properties corresponding to a first playback method of the 3D data may be stored within the mesh object. One or more second properties corresponding to a second playback method of the 3D data may be stored within the extension. In step S402, the file processing unit 412 may select one or more first properties stored within the mesh object or one or more second properties stored within the extension, depending on the playback method of the 3D data.

[0357] Furthermore, a first extension and a second extension may be defined within one node of the scene description. One or more first attribute properties corresponding to a first playback method of the 3D data may be associated with the first extension. One or more second attribute properties corresponding to a second playback method of the 3D data may be associated with the second extension. Then, in step S402, the file processing unit 412 may select one or more first attribute properties associated with the first extension or one or more second attribute properties associated with the second extension, depending on the playback method of the 3D data.

[0358] Furthermore, an extension may be defined within one node of the scene description. One or more first attribute properties corresponding to a first playback method of the 3D data may be associated with the node. One or more second attribute properties corresponding to a second playback method of the 3D data may be associated with the extension. Then, in step S402, the file processing unit 412 may select one or more first attribute properties associated with the node or one or more second attribute properties associated with the extension, depending on the playback method of the 3D data.

[0359] Furthermore, a first extension and a second extension may be defined within one node of the scene description. One or more first properties corresponding to a first playback method of the 3D data may be associated with the first extension. One or more second properties corresponding to a second playback method of the 3D data may be associated with the second extension. Then, in step S402, the file processing unit 412 may select one or more first properties associated with the first extension or one or more second properties associated with the second extension, depending on the playback method of the 3D data.

[0360] Furthermore, an extension may be defined within one node of the scene description. One or more first properties corresponding to a first playback method of the 3D data may be associated with the node. One or more second properties corresponding to a second playback method of the 3D data may be associated with the extension. Then, in step S402, the file processing unit 412 may select one or more first properties associated with the node or one or more second properties associated with the extension, depending on the playback method of the 3D data.

[0361] An extension may be defined within one primitive of the scene description. A first alternatives array and a second alternatives array may be defined within the extension. The first alternatives array may have elements that are one or more first properties corresponding to a first playback method of the 3D data. The second alternatives array may have elements that are one or more second properties corresponding to a second playback method of the 3D data. In step S402, when the file processing unit 412 applies the first playback method, it may select the first alternatives array and process the 3D data using the first playback method, utilizing the one or more first properties. When the file processing unit 412 applies the second playback method, it may select the second alternatives array and process the 3D data using the second playback method, utilizing the one or more second properties.

[0362] An extension may be defined within one mesh object of the scene description. A first alternatives array and a second alternatives array may be defined within the extension. The first alternatives array may have elements that are one or more first properties corresponding to a first playback method of the 3D data. The second alternatives array may have elements that are one or more second properties corresponding to a second playback method of the 3D data. In step S402, when the file processing unit 412 applies the first playback method, it may select the first alternatives array and process the 3D data using the first playback method, utilizing the one or more first properties. When the file processing unit 412 applies the second playback method, it may select the second alternatives array and process the 3D data using the second playback method, utilizing the one or more second properties.

[0363] An extension may be defined within one node of the scene description. A first alternatives array and a second alternatives array may be defined within the extension. The first alternatives array may have elements associated with one or more first properties corresponding to a first playback method of the 3D data. The second alternatives array may have elements associated with one or more second properties corresponding to a second playback method of the 3D data. In step S402, when the file processing unit 412 applies the first playback method, it may select the first alternatives array and process the 3D data using the first playback method, utilizing the one or more first properties. When the file processing unit 412 applies the second playback method, it may select the second alternatives array and process the 3D data using the second playback method, utilizing the one or more second properties.

[0364] Of course, other techniques described above in <3. Scene description supporting multiple playback methods> may also be applied. Also, multiple techniques may be applied in appropriate combination.

[0365] <6. Notes> <Combination> Each of the above-described examples of the present technology may be applied in appropriate combination with other examples as long as no contradiction occurs. Furthermore, each of the above-described examples of the present technology may be applied in combination with other technologies other than those described above.

[0366] <Computer> The above-described series of processes can be executed by hardware or software. When the series of processes is executed by software, the programs constituting the software are installed on a computer. Here, the term "computer" includes computers built into dedicated hardware, and general-purpose personal computers, etc., that can execute various functions by installing various programs.

[0367] FIG. 44 is a block diagram showing an example of the hardware configuration of a computer that executes the above-described series of processes by a program.

[0368] In a computer 900 shown in FIG. 44, a CPU (Central Processing Unit) 901, a ROM (Read Only Memory) 902, and a RAM (Random Access Memory) 903 are interconnected via a bus 904.

[0369] An input / output interface 910 is also connected to the bus 904. To the input / output interface 910, an input unit 911, an output unit 912, a storage unit 913, a communication unit 914, and a drive 915 are connected.

[0370] The input unit 911 includes, for example, a keyboard, a mouse, a microphone, a touch panel, an input terminal, etc. The output unit 912 includes, for example, a display, a speaker, an output terminal, etc. The storage unit 913 includes, for example, a hard disk, a RAM disk, a non-volatile memory, etc. The communication unit 914 includes, for example, a network interface. The drive 915 drives removable media 921 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory.

[0371] In a computer configured as above, the CPU 901 performs the above-described series of processes by, for example, loading a program stored in the storage unit 913 into the RAM 903 via the input / output interface 910 and the bus 904 and executing the program. The RAM 903 also stores data necessary for the CPU 901 to execute various processes as appropriate.

[0372] The program executed by the computer can be applied by recording it on removable media 921 such as package media, for example. In this case, the program can be installed in storage unit 913 via input / output interface 910 by inserting removable media 921 into drive 915.

[0373] This program can also be provided via a wired or wireless transmission medium such as a local area network, the Internet, digital satellite broadcasting, etc. In this case, the program can be received by the communication unit 914 and installed in the storage unit 913.

[0374] Alternatively, this program can be installed in advance in the ROM 902 or the storage unit 913 .

[0375] <Applicable targets of this technology> This technology can be applied to any encoding / decoding method.

[0376] Furthermore, the present technology can be applied to any configuration, for example, various electronic devices.

[0377] Furthermore, for example, the present technology can also be implemented as a part of an apparatus, such as a processor (e.g., a video processor) as a system LSI (Large Scale Integration), a module (e.g., a video module) using multiple processors, a unit (e.g., a video unit) using multiple modules, or a set in which other functions are added to a unit (e.g., a video set).

[0378] Furthermore, for example, the present technology can also be applied to a network system configured with multiple devices. For example, the present technology may be implemented as cloud computing in which multiple devices share and collaborate on processing via a network. For example, the present technology may be implemented in a cloud service that provides image (video)-related services to any terminal, such as a computer, AV (Audio Visual) equipment, a portable information processing terminal, or an IoT (Internet of Things) device.

[0379] In this specification, a system refers to a collection of multiple components (devices, modules (components), etc.), regardless of whether all the components are contained in the same housing. Therefore, multiple devices housed in separate housings and connected via a network, and a single device housed in a single housing with multiple modules, are both systems.

[0380] <Fields and applications where this technology can be applied> Systems, devices, processing units, etc. to which the present technology is applied can be used in any field, such as transportation, medical care, crime prevention, agriculture, livestock farming, mining, beauty, factories, home appliances, weather, and nature monitoring. In addition, the applications thereof are also arbitrary.

[0381] For example, the present technology can be applied to systems and devices used to provide viewing content, etc. Furthermore, for example, the present technology can also be applied to systems and devices used for transportation, such as monitoring traffic conditions and controlling automatic driving. Furthermore, for example, the present technology can also be applied to systems and devices used for security. Furthermore, for example, the present technology can also be applied to systems and devices used for automatic control of machines, etc. Furthermore, for example, the present technology can also be applied to systems and devices used for agriculture and livestock farming. Furthermore, for example, the present technology can also be applied to systems and devices used to monitor natural conditions, such as volcanoes, forests, and oceans, and wildlife. Furthermore, for example, the present technology can also be applied to systems and devices used for sports.

[0382] <Other> In this specification, a "flag" refers to information for identifying multiple states, and includes not only information used to identify two states, true (1) or false (0), but also information capable of identifying three or more states. Therefore, the value that this "flag" can take may be, for example, two values, 1 / 0, or three or more values. In other words, the number of bits constituting this "flag" is arbitrary, and may be one bit or multiple bits. Furthermore, identification information (including flags) can be assumed not only to include the identification information in the bit stream, but also to include difference information of the identification information relative to certain reference information in the bit stream. Therefore, in this specification, "flag" and "identification information" include not only the information itself, but also difference information relative to the reference information.

[0383] Furthermore, various types of information (metadata, etc.) related to the coded data (bitstream) may be transmitted or recorded in any form as long as they are associated with the coded data. Here, the term "associate" means, for example, that one piece of data can be used (linked) when processing the other piece of data. In other words, data associated with each other may be combined into one piece of data or may be individual pieces of data. For example, information associated with coded data (image) may be transmitted over a transmission path separate from that of the coded data (image). Also, for example, information associated with coded data (image) may be recorded on a recording medium separate from that of the coded data (image) (or on a different recording area of ​​the same recording medium). Note that this "association" may refer to only a portion of the data, rather than the entire data. For example, an image and information corresponding to that image may be associated with each other in any unit, such as multiple frames, one frame, or a portion of a frame.

[0384] In this specification, terms such as "composite," "multiplex," "add," "integrate," "include," "store," "embed," "insert," and the like refer to combining multiple items into one, such as combining encoded data and metadata into one piece of data, and refer to one method of "associating" as described above.

[0385] Furthermore, the embodiments of the present technology are not limited to the above-described embodiments, and various modifications are possible within the scope of the gist of the present technology.

[0386] For example, a configuration described as one device (or processing unit) may be divided and configured as multiple devices (or processing units). Conversely, configurations described above as multiple devices (or processing units) may be combined and configured as one device (or processing unit). Of course, configurations other than those described above may be added to the configuration of each device (or each processing unit). Furthermore, as long as the configuration and operation of the entire system are substantially the same, part of the configuration of one device (or processing unit) may be included in the configuration of another device (or other processing unit).

[0387] Furthermore, for example, the above-described program may be executed in any device, as long as the device has the necessary functions (functional blocks, etc.) and can obtain the necessary information.

[0388] Also, for example, each step of a single flowchart may be executed by one device, or may be shared and executed by multiple devices. Furthermore, when one step includes multiple processes, the multiple processes may be executed by one device, or may be shared and executed by multiple devices. In other words, multiple processes included in one step can be executed as multiple step processes. Conversely, processes described as multiple steps can be executed collectively as one step.

[0389] For example, the steps of a program executed by a computer may be executed in chronological order in the order described herein, or may be executed in parallel or individually at the required timing, such as when a call is made. In other words, as long as no contradiction occurs, the steps may be executed in an order different from the order described above. Furthermore, the steps of this program may be executed in parallel with the processing of another program, or may be executed in combination with the processing of another program.

[0390] Furthermore, for example, multiple technologies related to the present technology can be implemented independently and independently, as long as no contradiction occurs. Of course, any multiple technologies can also be implemented in combination. For example, part or all of the present technology described in any embodiment can be implemented in combination with part or all of the present technology described in another embodiment. Furthermore, part or all of any of the above-described present technologies can be implemented in combination with other technologies not described above.

[0391] The present technology can also be configured as follows. (1) a file processing unit that selects a property corresponding to a playback method for 3D data based on an extension defined in a scene description, and processes the 3D data using the selected property in the playback method; An information processing device comprising: (2) a first extension and a second extension are defined within one primitive of the scene description; One or more first attribute properties corresponding to a first playback method of the 3D data are stored in the first extension; one or more second attribute properties corresponding to a second playback method of the 3D data are stored in the second extension; The file processing unit selects one or more of the first attribute properties stored in the first extension or one or more of the second attribute properties stored in the second extension according to a playback method of the 3D data. An information processing device according to (1). (3) the extension is defined within one primitive of the scene description; one or more first attribute properties are stored within the primitives, corresponding to a first reproduction method of the 3D data; one or more second attribute properties corresponding to a second playback method of the 3D data are stored in the extension; The file processing unit selects one or more of the first attribute properties stored in the primitives or one or more of the second attribute properties stored in the extensions according to a playback method of the 3D data. An information processing device according to (1). (4) a first extension and a second extension are defined within one primitive of the scene description; One or more first properties corresponding to a first playback method of the 3D data are stored in the first extension; one or more second properties corresponding to a second playback method of the 3D data are stored in the second extension; The file processing unit selects one or more of the first properties stored in the first extension or one or more of the second properties stored in the second extension according to a playback method of the 3D data. An information processing device according to (1). (5) the extension is defined within one primitive of the scene description; one or more first properties are stored within the primitives corresponding to a first reproduction method of the 3D data; one or more second properties corresponding to a second playback method of the 3D data are stored in the extension; The file processing unit selects one or more of the first properties stored in the primitives or one or more of the second properties stored in the extensions according to a playback method of the 3D data. An information processing device according to (1). (6) a first extension and a second extension are defined within one mesh object of the scene description; One or more first attribute properties corresponding to a first playback method of the 3D data are stored in the first extension; one or more second attribute properties corresponding to a second playback method of the 3D data are stored in the second extension; The file processing unit selects one or more of the first attribute properties stored in the first extension or one or more of the second attribute properties stored in the second extension according to a playback method of the 3D data. An information processing device according to (1). (7) the extension is defined within one mesh object of the scene description; one or more first attribute properties are stored within the mesh object corresponding to a first reproduction method of the 3D data; one or more second attribute properties corresponding to a second playback method of the 3D data are stored in the extension; The file processing unit selects one or more of the first attribute properties stored in the mesh object or one or more of the second attribute properties stored in the extension according to a playback method of the 3D data. An information processing device according to (1). (8) A first extension and a second extension are defined within one mesh object of the scene description; One or more first properties corresponding to a first playback method of the 3D data are stored in the first extension; one or more second properties corresponding to a second playback method of the 3D data are stored in the second extension; The file processing unit selects one or more of the first properties stored in the first extension or one or more of the second properties stored in the second extension according to a playback method of the 3D data. An information processing device according to (1). (9) the extension is defined within one mesh object of the scene description; one or more first properties are stored within the mesh object corresponding to a first manner of reproduction of the 3D data; one or more second properties corresponding to a second playback method of the 3D data are stored in the extension; The file processing unit selects one or more of the first properties stored in the mesh object or one or more of the second properties stored in the extension according to a playback method of the 3D data. An information processing device according to (1). (10) A first extension and a second extension are defined within one node of the scene description; one or more first attribute properties corresponding to a first playback method of the 3D data are associated with the first extension; one or more second attribute properties corresponding to a second playback method of the 3D data are associated with the second extension; The file processing unit selects one or more of the first attribute properties associated with the first extension or one or more of the second attribute properties associated with the second extension according to a playback method of the 3D data. An information processing device according to (1). (11) The extension is defined within one node of the scene description; one or more first attribute properties are associated with the node, the first attribute properties corresponding to a first reproduction method of the 3D data; the extension is associated with one or more second attribute properties corresponding to a second playback method of the 3D data; The file processing unit selects one or more of the first attribute properties associated with the node or one or more of the second attribute properties associated with the extension according to a playback method of the 3D data. An information processing device according to (1). (12) A first extension and a second extension are defined within one node of the scene description; one or more first properties corresponding to a first playback method of the 3D data are associated with the first extension; the second extension is associated with one or more second properties corresponding to a second playback method of the 3D data; The file processing unit selects one or more first properties associated with the first extension or one or more second properties associated with the second extension according to a playback method of the 3D data. An information processing device according to (1). (13) The extension is defined within one node of the scene description; one or more first properties associated with the node corresponding to a first reproduction method of the 3D data; the extension is associated with one or more second properties corresponding to a second playback method of the 3D data; The file processing unit selects one or more of the first properties associated with the node or one or more of the second properties associated with the extension according to a playback method of the 3D data. An information processing device according to (1). (14) Selecting a property corresponding to a playback method for the 3D data based on an extension defined in the scene description, and processing the 3D data using the selected property in the playback method. Information processing methods.

[0392] (21) A file processing unit that selects an alternatives array according to a playback method of 3D data from among alternatives arrays defined in a scene description, and processes the 3D data in the playback method by using properties that are elements of the selected alternatives array. An information processing device comprising: (22) An extension is defined within one of the primitives of the scene description; a first alternative sequence and a second alternative sequence are defined within the extension; the first alternatives array has one or more first properties corresponding to a first reproduction method of the 3D data as elements; the second alternatives array has one or more second properties corresponding to second playback methods of the 3D data as elements, The file processing unit when applying the first playback method, selecting the first array of alternatives and processing the 3D data in the first playback method using one or more of the first properties; When the second playback method is applied, the second alternatives array is selected and the second property or properties are used to process the 3D data in the second playback method. (21) An information processing device according to (21). (23) An extension is defined within one mesh object of the scene description; a first alternative sequence and a second alternative sequence are defined within the extension; the first alternatives array has one or more first properties corresponding to a first reproduction method of the 3D data as elements; the second alternatives array has one or more second properties corresponding to second playback methods of the 3D data as elements, The file processing unit when applying the first playback method, selecting the first array of alternatives and processing the 3D data in the first playback method using one or more of the first properties; When the second playback method is applied, the second alternatives array is selected and the second property or properties are used to process the 3D data in the second playback method. (21) An information processing device according to (21). (24) An extension is defined within one node of the scene description; a first alternative sequence and a second alternative sequence are defined within the extension; the first alternatives array has elements each associated with one or more first properties corresponding to a first way of playing the 3D data; the second alternatives array has elements each associated with one or more second properties corresponding to a second way of playing the 3D data; The file processing unit when applying the first playback method, selecting the first array of alternatives and processing the 3D data in the first playback method using one or more of the first properties; When the second playback method is applied, the second alternatives array is selected and the second property or properties are used to process the 3D data in the second playback method. (21) An information processing device according to (21). (25) Selecting an alternatives array corresponding to a playback method for 3D data from among alternatives arrays defined in a scene description, and processing the 3D data using the playback method by using properties that are elements of the selected alternatives array. Information processing methods.

[0393] (31) A file generator that generates a scene description file that stores extensions to identify properties for each playback method of 3D data. An information processing device comprising: (32) The file generation unit defining a first extension and a second extension within one primitive of the scene description file; storing, in the first extension, one or more first attribute properties corresponding to a first playback method of the 3D data; storing, in the second extension, one or more second attribute properties corresponding to a second playback method of the 3D data; (31) An information processing device according to (31). (33) The file generation unit defining the extension within one primitive of the scene description file; storing one or more first attribute properties within the primitives corresponding to a first reproduction method of the 3D data; storing, in the extension, one or more second attribute properties corresponding to a second reproduction method of the 3D data; (31) An information processing device according to (31). (34) The file generation unit defining a first extension and a second extension within one primitive of the scene description file; storing, in the first extension, one or more first properties corresponding to a first playback method of the 3D data; storing, in the second extension, one or more second properties corresponding to a second playback method of the 3D data; (31) An information processing device according to (31). (35) The file generation unit defining the extension within one primitive of the scene description file; storing within said primitives one or more first properties corresponding to a first manner of reproduction of said 3D data; storing, within the extension, one or more second properties corresponding to a second playback method of the 3D data; (31) An information processing device according to (31). (36) The file generation unit defining a first extension and a second extension within a mesh object of the scene description file; storing, in the first extension, one or more first attribute properties corresponding to a first playback method of the 3D data; storing, in the second extension, one or more second attribute properties corresponding to a second playback method of the 3D data; (31) An information processing device according to (31). (37) The file generation unit defining the extension within a mesh object of the scene description file; storing one or more first attribute properties within the mesh object corresponding to a first manner of reproduction of the 3D data; storing, in the extension, one or more second attribute properties corresponding to a second reproduction method of the 3D data; (31) An information processing device according to (31). (38) The file generation unit defining a first extension and a second extension within a mesh object of the scene description file; storing, in the first extension, one or more first properties corresponding to a first playback method of the 3D data; storing, in the second extension, one or more second properties corresponding to a second playback method of the 3D data; (31) An information processing device according to (31). (39) The file generation unit defining the extension within a mesh object of the scene description file; storing one or more first properties within the mesh object corresponding to a first manner of reproduction of the 3D data; storing, within the extension, one or more second properties corresponding to a second playback method of the 3D data; (31) An information processing device according to (31). (40) The file generation unit defining a first extension and a second extension within a node of the scene description file; Associating one or more first attribute properties with the first extension, the first attribute properties corresponding to a first playback method of the 3D data; Associating one or more second attribute properties within the second extension, the second attribute properties corresponding to a second playback method of the 3D data. (31) An information processing device according to (31). (41) The file generation unit defining the extension within a node of the scene description file; associating with the node one or more first attribute properties corresponding to a first reproduction method of the 3D data; Associating one or more second attribute properties with the extension, the second attribute properties corresponding to a second playback method of the 3D data. (31) An information processing device according to (31). (42) The file generation unit defining a first extension and a second extension within a node of the scene description file; Associating one or more first properties with the first extension, the first properties corresponding to a first playback method of the 3D data; Associating one or more second properties with the second extension, the second properties corresponding to a second playback method of the 3D data. (31) An information processing device according to (31). (43) The file generation unit defining the extension within a node of the scene description file; associating with the node one or more first properties corresponding to a first manner of reproduction of the 3D data; Associating one or more second properties with the extension, the second properties corresponding to a second playback method of the 3D data. (31) An information processing device according to (31). (44) Generate a scene description file that stores extensions to identify properties for each playback method of 3D data. Information processing methods.

[0394] (51) A file generating unit that generates a scene description file that stores a plurality of alternative arrays whose elements are properties corresponding to the same playback method of 3D data. An information processing device comprising: (52) The file generation unit defining an extension within one of the primitives of the scene description file; storing, in the extension, a first alternatives array having one or more first properties corresponding to a first reproduction method of the 3D data as elements; The extension further stores a second alternatives array having one or more second properties corresponding to a second reproduction method of the 3D data as elements. (51) An information processing device according to (51). (53) The file generation unit defining an extension within one mesh object of said scene description file; storing, in the extension, a first alternatives array having one or more first properties corresponding to a first reproduction method of the 3D data as elements; The extension further stores a second alternatives array having one or more second properties corresponding to a second reproduction method of the 3D data as elements. (51) An information processing device according to (51). (54) The file generation unit defining an extension within a node of the scene description file; storing within said extension a first alternatives array having elements each associated with one or more first properties corresponding to a first way of playing said 3D data; and storing within the extension a second alternatives array having elements each associated with one or more second properties corresponding to a second reproduction method of the 3D data. (51) An information processing device according to (51). (55) Generate a scene description file that contains multiple alternative arrays whose elements correspond to properties that correspond to the same playback methods of 3D data. Information processing device. [Explanation of symbols]

[0395] 300 file generation device, 301 control unit, 302 file generation processing unit, 311 input unit, 312 preprocessing unit, 313 encoding unit, 314 file generation unit, 315 recording unit, 316 output unit, 400 client device, 401 control unit, 402 client processing unit, 411 file acquisition unit, 412 file processing unit, 413 decoding unit, 414 display information generation unit, 415 display unit, 416 display control unit

Claims

1. a file processing unit that selects a property corresponding to a playback method for 3D data based on an extension defined in the scene description, and processes the 3D data using the selected property in the playback method; An information processing device comprising:

2. Within one primitive of the scene description, a first extension and a second extension are defined; One or more first attribute properties corresponding to a first playback method of the 3D data are stored in the first extension; one or more second attribute properties corresponding to a second playback method of the 3D data are stored in the second extension; The file processing unit selects one or more of the first attribute properties stored in the first extension or one or more of the second attribute properties stored in the second extension according to a playback method of the 3D data. The information processing device according to claim 1 .

3. the extension is defined within one primitive of the scene description; one or more first attribute properties are stored within the primitives, corresponding to a first reproduction method of the 3D data; one or more second attribute properties corresponding to a second playback method of the 3D data are stored in the extension; The file processing unit selects one or more of the first attribute properties stored in the primitives or one or more of the second attribute properties stored in the extensions according to a playback method of the 3D data. The information processing device according to claim 1 .

4. Within one primitive of the scene description, a first extension and a second extension are defined; One or more first properties corresponding to a first playback method of the 3D data are stored in the first extension; one or more second properties corresponding to a second playback method of the 3D data are stored in the second extension; The file processing unit selects one or more of the first properties stored in the first extension or one or more of the second properties stored in the second extension according to a playback method of the 3D data. The information processing device according to claim 1 .

5. the extension is defined within one primitive of the scene description; one or more first properties are stored within the primitives, corresponding to a first reproduction method of the 3D data; one or more second properties corresponding to a second playback method of the 3D data are stored in the extension; The file processing unit selects one or more of the first properties stored in the primitives or one or more of the second properties stored in the extensions according to a playback method of the 3D data. The information processing device according to claim 1 .

6. a first extension and a second extension are defined within one mesh object of the scene description; One or more first attribute properties corresponding to a first playback method of the 3D data are stored in the first extension; one or more second attribute properties corresponding to a second playback method of the 3D data are stored in the second extension; The file processing unit selects one or more of the first attribute properties stored in the first extension or one or more of the second attribute properties stored in the second extension according to a playback method of the 3D data. The information processing device according to claim 1 .

7. the extension is defined within one mesh object of the scene description; one or more first attribute properties are stored within the mesh object corresponding to a first reproduction method of the 3D data; one or more second attribute properties corresponding to a second playback method of the 3D data are stored in the extension; The file processing unit selects one or more of the first attribute properties stored in the mesh object or one or more of the second attribute properties stored in the extension according to a playback method of the 3D data. The information processing device according to claim 1 .

8. a first extension and a second extension are defined within one mesh object of the scene description; One or more first properties corresponding to a first playback method of the 3D data are stored in the first extension; one or more second properties corresponding to a second playback method of the 3D data are stored in the second extension; The file processing unit selects one or more of the first properties stored in the first extension or one or more of the second properties stored in the second extension according to a playback method of the 3D data. The information processing device according to claim 1 .

9. the extension is defined within one mesh object of the scene description; one or more first properties are stored within the mesh object corresponding to a first manner of reproduction of the 3D data; one or more second properties corresponding to a second playback method of the 3D data are stored in the extension; The file processing unit selects one or more of the first properties stored in the mesh object or one or more of the second properties stored in the extension according to a playback method of the 3D data. The information processing device according to claim 1 .

10. Within one node of the scene description, a first extension and a second extension are defined; one or more first attribute properties corresponding to a first playback method of the 3D data are associated with the first extension; one or more second attribute properties corresponding to a second playback method of the 3D data are associated with the second extension; The file processing unit selects one or more of the first attribute properties associated with the first extension or one or more of the second attribute properties associated with the second extension according to a playback method of the 3D data. The information processing device according to claim 1 .

11. the extension is defined within a node of the scene description; one or more first attribute properties associated with the node corresponding to a first reproduction method of the 3D data; the extension is associated with one or more second attribute properties corresponding to a second playback method of the 3D data; The file processing unit selects one or more of the first attribute properties associated with the node or one or more of the second attribute properties associated with the extension according to a playback method of the 3D data. The information processing device according to claim 1 .

12. Within one node of the scene description, a first extension and a second extension are defined; one or more first properties corresponding to a first playback method of the 3D data are associated with the first extension; one or more second properties corresponding to a second playback method of the 3D data are associated with the second extension; The file processing unit selects one or more of the first properties associated with the first extension or one or more of the second properties associated with the second extension according to a playback method of the 3D data. The information processing device according to claim 1 .

13. the extension is defined within a node of the scene description; one or more first properties associated with the node corresponding to a first reproduction method of the 3D data; one or more second properties are associated with the extension, the second properties corresponding to a second playback method of the 3D data; The file processing unit selects one or more of the first properties associated with the node or one or more of the second properties associated with the extension according to a playback method of the 3D data. The information processing device according to claim 1 .

14. Based on the extension defined in the scene description, a property corresponding to a playback method for the 3D data is selected, and the selected property is used to process the 3D data using the playback method. Information processing methods.

15. a file processing unit that selects an alternatives array corresponding to a playback method for 3D data from among alternatives arrays defined in a scene description, and processes the 3D data in the playback method by using properties that are elements of the selected alternatives array; An information processing device comprising:

16. An extension is defined within one of the primitives of the scene description; a first alternatives sequence and a second alternatives sequence are defined within the extension; the first alternatives array has one or more first properties corresponding to a first reproduction method of the 3D data as elements; the second alternatives array has one or more second properties corresponding to second playback methods of the 3D data as elements, The file processing unit when applying the first playback method, selecting the first array of alternatives and processing the 3D data in the first playback method using one or more of the first properties; When the second playback method is applied, the second alternatives sequence is selected and the second property or properties are used to process the 3D data in the second playback method. The information processing device according to claim 15.

17. An alternatives array corresponding to a playback method for 3D data is selected from the alternatives arrays defined in the scene description, and the 3D data is processed using the playback method by using properties that are elements of the selected alternatives array. Information processing methods.

18. A file generator that generates scene description files that store extensions to identify properties for each playback method of 3D data. An information processing device comprising:

19. The file generation unit defining a first extension and a second extension within one primitive of the scene description file; storing, in the first extension, one or more first attribute properties corresponding to a first playback method of the 3D data; storing, in the second extension, one or more second attribute properties corresponding to a second playback method of the 3D data; The information processing device according to claim 18.

20. Generates a scene description file that stores extensions to identify properties for each playback method of 3D data. Information processing methods.

Images