Three dimensional data encoding method, three dimensional data decoding method, three dimensional data encoding device, and three dimensional data decoding device

Abstract

To provide a three dimensional data encoding method, a three dimensional data decoding method, a three dimensional data encoding device, and a three dimensional data decoding device for improving encoding efficiency.SOLUTION: A three dimensional data encoding method includes generating dependency relation information indicating a decoding order between encoded position information and encoded attribute information corresponding to a plurality of pieces of attribute information when generating an encoded stream by encoding position information of a three dimensional point included in a first point cloud frame including a plurality of first three dimensional points and the plurality of pieces of attribute information as the encoded position information and the encoded attribute information, respectively. The encoded stream includes encoded position information, encoded attribute information corresponding to a plurality of pieces of attribute information, and dependency information.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present disclosure relates to a three-dimensional data encoding method, a three-dimensional data decoding method, a three-dimensional data encoding device, and a three-dimensional data decoding device. [Background technology]

[0002] In the future, devices and services that utilize 3D data are expected to become widespread in a wide range of fields, including computer vision for autonomous operation of automobiles or robots, map information, surveillance, infrastructure inspection, video distribution, etc. 3D data can be acquired in a variety of ways, including distance sensors such as range finders, stereo cameras, or a combination of multiple monocular cameras.

[0003] One method of representing three-dimensional data is a point cloud, which represents the shape of a three-dimensional structure using a group of points in three-dimensional space. A point cloud stores the position and color of the points. Point clouds are expected to become the mainstream method of representing three-dimensional data, but point clouds require a very large amount of data. Therefore, when storing or transmitting three-dimensional data, data compression through encoding is essential, just as with two-dimensional video images (examples include MPEG-4 AVC or HEVC standardized by MPEG).

[0004] In addition, compression of point clouds is partially supported by public libraries that perform point cloud-related processing (Point Cloud Library).

[0005] Furthermore, a technique is known in which three-dimensional map data is used to search for and display facilities located around a vehicle (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0006] [Patent Document 1] International Publication No. 2014 / 020663 Summary of the Invention [Problem to be solved by the invention]

[0007] In the encoding process of three-dimensional data, it is desirable to be able to improve the encoding efficiency.

[0008] An object of the present disclosure is to provide a three-dimensional data encoding method, a three-dimensional data decoding method, a three-dimensional data encoding device, or a three-dimensional data decoding device that can improve encoding efficiency. [Means for solving the problem]

[0009] A three-dimensional data encoding method according to one embodiment of the present disclosure is a three-dimensional data encoding method that uses an information processing device having a processor and a memory, wherein, when the processor uses the memory to generate an encoded stream by encoding position information and multiple attribute information of three-dimensional points included in a first point cloud frame consisting of multiple first three-dimensional points as encoded position information and encoded attribute information, respectively, the processor generates dependency information indicating the decoding order between the encoded position information and encoded attribute information corresponding to the multiple attribute information, and the encoded stream includes the encoded position information, the encoded attribute information corresponding to the multiple attribute information, and the dependency information.

[0010] A three-dimensional data decoding method according to one aspect of the present disclosure is a three-dimensional data decoding method that uses an information processing device having a processor and a memory, wherein the processor, using the memory, acquires from an encoded stream encoded position information, encoded attribute information corresponding to a plurality of attribute information, and dependency information indicating a decoding order, determines a decoding order between the encoded position information and the encoded attribute information corresponding to the plurality of attribute information based on the dependency information, decodes the encoded position information according to the determined decoding order to acquire position information of a three-dimensional point, and acquires a plurality of attribute information of the three-dimensional point by decoding the encoded attribute information corresponding to the plurality of attribute information. [Effects of the Invention]

[0011] The present disclosure can provide a three-dimensional data encoding method, a three-dimensional data decoding method, a three-dimensional data encoding device, or a three-dimensional data decoding device that can improve encoding efficiency. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram showing a configuration of a three-dimensional data encoding / decoding system according to the first embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of the configuration of point cloud data according to the first embodiment. [Figure 3] FIG. 3 is a diagram showing an example of the structure of a data file in which point cloud data information according to the first embodiment is described. [Figure 4] FIG. 4 is a diagram showing types of point cloud data according to the first embodiment. [Figure 5] FIG. 5 is a diagram showing a configuration of a first encoding unit according to the first embodiment. [Figure 6] FIG. 6 is a block diagram of a first encoding unit according to the first embodiment. [Figure 7] FIG. 7 is a diagram illustrating a configuration of a first decoding unit according to the first embodiment. [Figure 8] FIG. 8 is a block diagram of a first decoding unit according to the first embodiment. [Figure 9] FIG. 9 is a diagram showing a configuration of a second encoding unit according to the first embodiment. [Figure 10] FIG. 10 is a block diagram of a second encoding unit according to the first embodiment. [Figure 11] FIG. 11 is a diagram illustrating a configuration of a second decoding unit according to the first embodiment. [Figure 12] FIG. 12 is a block diagram of a second decoding unit according to the first embodiment. [Figure 13] FIG. 13 is a diagram showing a protocol stack related to PCC encoded data according to the first embodiment. [Figure 14] FIG. 14 is a diagram illustrating a basic structure of the ISOBMFF according to the second embodiment. [Figure 15] FIG. 15 is a diagram illustrating a protocol stack according to the second embodiment. [Figure 16] FIG. 16 is a diagram illustrating the configurations of an encoding unit and a multiplexing unit according to the third embodiment. [Figure 17] FIG. 17 is a diagram illustrating an example of a structure of coded data according to the third embodiment. [Figure 18] FIG. 18 is a diagram showing an example of the structure of coded data and NAL units according to the third embodiment. [Figure 19] FIG. 19 is a diagram illustrating an example of the semantics of pcc_nal_unit_type according to the third embodiment. [Figure 20] FIG. 20 is a diagram showing an example of the transmission order of NAL units according to the third embodiment. [Figure 21] FIG. 21 is a block diagram of a first encoding unit according to the fourth embodiment. [Figure 22] FIG. 22 is a block diagram of a first decoding unit according to the fourth embodiment. [Figure 23] FIG. 23 is a block diagram of a division unit according to the fourth embodiment. [Figure 24] FIG. 24 is a diagram showing an example of division into slices and tiles according to the fourth embodiment. [Figure 25] FIG. 25 is a diagram showing an example of a division pattern of slices and tiles according to the fourth embodiment. [Figure 26] FIG. 26 is a diagram illustrating an example of a dependency relationship according to the fourth embodiment. [Figure 27] FIG. 27 is a diagram showing an example of the decoding order of data according to the fourth embodiment. [Figure 28] FIG. 28 is a flowchart of the encoding process according to the fourth embodiment. [Figure 29] FIG. 29 is a block diagram of a coupling unit according to the fourth embodiment. [Figure 30] FIG. 30 is a diagram showing an example of the structure of coded data and NAL units according to the fourth embodiment. [Figure 31]FIG. 31 is a flowchart of the encoding process according to the fourth embodiment. [Figure 32] FIG. 32 is a flowchart of the decoding process according to the fourth embodiment. [Figure 33] FIG. 33 is a flowchart of the encoding process according to the fourth embodiment. [Figure 34] FIG. 34 is a flowchart of the decoding process according to the fourth embodiment. [Figure 35] FIG. 35 is a diagram showing an image of generating a tree structure and occupancy codes from point cloud data of multiple frames according to the fifth embodiment. [Figure 36] FIG. 36 is a diagram illustrating an example of frame combination according to the fifth embodiment. [Figure 37] FIG. 37 is a diagram showing an example of combining multiple frames according to the fifth embodiment. [Figure 38] FIG. 38 is a flowchart of three-dimensional data encoding processing according to the fifth embodiment. [Figure 39] FIG. 39 is a flowchart of the encoding process according to the fifth embodiment. [Figure 40] FIG. 40 is a flowchart of three-dimensional data decoding processing according to the fifth embodiment. [Figure 41] FIG. 41 is a flowchart of the decoding and division process according to the fifth embodiment. [Figure 42] FIG. 42 is a block diagram of an encoding unit according to the fifth embodiment. [Figure 43] FIG. 43 is a block diagram of a division unit according to the fifth embodiment. [Figure 44] FIG. 44 is a block diagram of a position information encoding unit according to the fifth embodiment. [Figure 45] FIG. 45 is a block diagram of an attribute information encoding unit according to the fifth embodiment. [Figure 46] FIG. 46 is a flowchart of the encoding process of point cloud data according to the fifth embodiment. [Figure 47] FIG. 47 is a flowchart of the encoding process according to the fifth embodiment. [Figure 48] FIG. 48 is a block diagram of a decoding unit according to the fifth embodiment. [Figure 49] FIG. 49 is a block diagram of a position information decoding unit according to the fifth embodiment. [Figure 50] FIG. 50 is a block diagram of an attribute information decoding unit according to the fifth embodiment. [Figure 51] FIG. 51 is a block diagram of a combining unit according to the fifth embodiment. [Figure 52] FIG. 52 is a flowchart of the decoding process of point cloud data according to the fifth embodiment. [Figure 53] FIG. 53 is a flowchart of the decoding process according to the fifth embodiment. [Figure 54] FIG. 54 is a diagram showing an example of a frame combining pattern according to the fifth embodiment. [Figure 55] FIG. 55 is a diagram illustrating an example of a configuration of a PCC frame according to the fifth embodiment. [Figure 56] FIG. 56 is a diagram showing the structure of the encoding position information according to the fifth embodiment. [Figure 57] FIG. 57 is a diagram illustrating an example of the syntax of the header of the encoding position information according to the fifth embodiment. [Figure 58] FIG. 58 is a diagram illustrating an example of the syntax of the payload of the encoded position information according to the fifth embodiment. [Figure 59] FIG. 59 is a diagram illustrating an example of leaf node information according to the fifth embodiment. [Figure 60] FIG. 60 is a diagram illustrating an example of leaf node information according to the fifth embodiment. [Figure 61] FIG. 61 is a diagram showing an example of bitmap information according to the fifth embodiment. [Figure 62] FIG. 62 is a diagram showing the structure of the encoding attribute information according to the fifth embodiment. [Figure 63] FIG. 63 is a diagram illustrating an example of the syntax of the header of the encoding attribute information according to the fifth embodiment. [Figure 64]FIG. 64 is a diagram illustrating an example of the syntax of the payload of the encoded attribute information according to the fifth embodiment. [Figure 65] FIG. 65 is a diagram showing a structure of coded data according to the fifth embodiment. [Figure 66] FIG. 66 is a diagram showing the data transmission order and data reference relationships according to the fifth embodiment. [Figure 67] FIG. 67 is a diagram showing the data transmission order and data reference relationships according to the fifth embodiment. [Figure 68] FIG. 68 is a diagram showing the data transmission order and data reference relationships according to the fifth embodiment. [Figure 69] FIG. 69 is a diagram showing an example of decoding some frames according to the fifth embodiment. [Figure 70] FIG. 70 is a diagram showing the data transmission order and data reference relationships according to the fifth embodiment. [Figure 71] FIG. 71 is a diagram showing the data transmission order and data reference relationships according to the fifth embodiment. [Figure 72] FIG. 72 is a diagram showing the data transmission order and data reference relationships according to the fifth embodiment. [Figure 73] FIG. 73 is a diagram showing the data transmission order and data reference relationships according to the fifth embodiment. [Figure 74] FIG. 74 is a flowchart of the encoding process according to the fifth embodiment. [Figure 75] FIG. 75 is a flowchart of the decoding process according to the fifth embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0013] A three-dimensional data encoding method according to one embodiment of the present disclosure generates third point cloud data by combining first point cloud data and second point cloud data, and generates encoded data by encoding the third point cloud data, wherein the encoded data includes identification information indicating whether each of a plurality of three-dimensional points included in the third point cloud data belongs to the first point cloud data or the second point cloud data.

[0014] According to this, the three-dimensional data encoding method can improve encoding efficiency by encoding a plurality of point group data collectively.

[0015] For example, the first point cloud data and the second point cloud data may be point cloud data at different times.

[0016] For example, the first point cloud data and the second point cloud data may be point cloud data of the same object at different times.

[0017] For example, the encoded data may include position information and attribute information of each of a plurality of three-dimensional points included in the third point cloud data, and the identification information may be included in the attribute information.

[0018] For example, the encoded data may include position information in which the position of each of a plurality of three-dimensional points included in the third point cloud data is expressed using an N-ary tree (N is an integer equal to or greater than 2).

[0019] A three-dimensional data decoding method according to one embodiment of the present disclosure decodes encoded data to obtain third point cloud data generated by combining first point cloud data and second point cloud data, and identification information indicating whether each of a plurality of three-dimensional points included in the third point cloud data belongs to the first point cloud data or the second point cloud data, and then separates the first point cloud data and the second point cloud data from the third point cloud data using the identification information.

[0020] According to this, the three-dimensional data decoding method can decode coded data with improved coding efficiency by collectively coding a plurality of point cloud data.

[0021] For example, the first point cloud data and the second point cloud data may be point cloud data at different times.

[0022] For example, the first point cloud data and the second point cloud data may be point cloud data of the same object at different times.

[0023] For example, the encoded data may include position information and attribute information of each of a plurality of three-dimensional points included in the third point cloud data, and the identification information may be included in the attribute information.

[0024] For example, the encoded data may include position information in which the position of each of a plurality of three-dimensional points included in the third point cloud data is expressed using an N-ary tree (N is an integer equal to or greater than 2).

[0025] Furthermore, a three-dimensional data encoding device according to one embodiment of the present disclosure includes a processor and a memory, wherein the processor uses the memory to generate third point cloud data by combining first point cloud data and second point cloud data, and encodes the third point cloud data to generate encoded data, and the encoded data includes identification information indicating whether each of a plurality of three-dimensional points included in the third point cloud data belongs to the first point cloud data or the second point cloud data.

[0026] According to this, the three-dimensional data encoding device can improve encoding efficiency by encoding a plurality of point group data collectively.

[0027] In addition, a three-dimensional data decoding device according to one embodiment of the present disclosure includes a processor and a memory, and the processor uses the memory to decode encoded data to obtain third point cloud data generated by combining first point cloud data and second point cloud data, and identification information indicating whether each of a plurality of three-dimensional points included in the third point cloud data belongs to the first point cloud data or the second point cloud data, and separates the first point cloud data and the second point cloud data from the third point cloud data using the identification information.

[0028] According to this, the three-dimensional data decoding device can decode coded data with improved coding efficiency by collectively coding a plurality of point cloud data.

[0029] These comprehensive or specific aspects may be realized as a system, a method, an integrated circuit, a computer program, or a computer-readable recording medium such as a CD-ROM, or may be realized as any combination of a system, a method, an integrated circuit, a computer program, and a recording medium.

[0030] Hereinafter, the embodiments will be described in detail with reference to the drawings. Note that each of the embodiments described below represents a specific example of the present disclosure. The numerical values, shapes, materials, components, component placement and connection configurations, steps, and step order shown in the following embodiments are merely examples and are not intended to limit the present disclosure. Furthermore, among the components in the following embodiments, components that are not described in an independent claim that represents a superordinate concept will be described as optional components.

[0031] (Embodiment 1) When using encoded point cloud data in an actual device or service, it is desirable to transmit and receive the information required for the application in order to reduce network bandwidth. However, until now, such a function has not existed in the encoding structure of 3D data, and no encoding method for this purpose has existed.

[0032] In this embodiment, we will describe a three-dimensional data encoding method and a three-dimensional data encoding device that provide the function of transmitting and receiving information required for the purpose in encoded data of a three-dimensional point cloud, as well as a three-dimensional data decoding method and a three-dimensional data decoding device that decodes the encoded data, a three-dimensional data multiplexing method that multiplexes the encoded data, and a three-dimensional data transmission method that transmits the encoded data.

[0033] In particular, two encoding methods (encoding schemes) are currently being considered as encoding methods (encoding systems) for point cloud data; however, the structure of the encoded data and the method for storing the encoded data in a system format have not been defined, and as things stand, there is a problem that MUX processing (multiplexing) in the encoding unit, or transmission or storage, is not possible.

[0034] Furthermore, there has been no method to date that supports a format in which two codecs, a first encoding method and a second encoding method, are mixed, such as PCC (Point Cloud Compression).

[0035] In this embodiment, a description will be given of the structure of PCC encoded data in which two codecs, a first encoding method and a second encoding method, are mixed, and a method of storing the encoded data in a system format.

[0036] First, the configuration of a three-dimensional data (point cloud data) encoding / decoding system according to this embodiment will be described. Fig. 1 is a diagram showing an example of the configuration of a three-dimensional data encoding / decoding system according to this embodiment. As shown in Fig. 1, the three-dimensional data encoding / decoding system includes a three-dimensional data encoding system 4601, a three-dimensional data decoding system 4602, a sensor terminal 4603, and an external connection unit 4604.

[0037] The three-dimensional data encoding system 4601 generates encoded data or multiplexed data by encoding point cloud data, which is three-dimensional data. Note that the three-dimensional data encoding system 4601 may be a three-dimensional data encoding device realized by a single device, or may be a system realized by multiple devices. Furthermore, the three-dimensional data encoding device may include some of the multiple processing units included in the three-dimensional data encoding system 4601.

[0038] The three-dimensional data encoding system 4601 includes a point cloud data generation system 4611, a presentation unit 4612, an encoding unit 4613, a multiplexing unit 4614, an input / output unit 4615, and a control unit 4616. The point cloud data generation system 4611 includes a sensor information acquisition unit 4617 and a point cloud data generation unit 4618.

[0039] The sensor information acquisition unit 4617 acquires sensor information from the sensor terminal 4603 and outputs the sensor information to the point cloud data generation unit 4618. The point cloud data generation unit 4618 generates point cloud data from the sensor information and outputs the point cloud data to the encoding unit 4613.

[0040] The presentation unit 4612 presents the sensor information or point cloud data to the user. For example, the presentation unit 4612 displays information or an image based on the sensor information or point cloud data.

[0041] The encoding unit 4613 encodes (compresses) the point cloud data, and outputs the obtained encoded data, control information obtained in the encoding process, and other additional information to the multiplexing unit 4614. The additional information includes, for example, sensor information.

[0042] The multiplexing unit 4614 generates multiplexed data by multiplexing the coded data input from the coding unit 4613, the control information, and the additional information. The format of the multiplexed data is, for example, a file format for storage or a packet format for transmission.

[0043] The input / output unit 4615 (e.g., a communication unit or an interface) outputs the multiplexed data to the outside. Alternatively, the multiplexed data is stored in a storage unit such as an internal memory. The control unit 4616 (or application execution unit) controls each processing unit. In other words, the control unit 4616 controls encoding, multiplexing, etc.

[0044] The sensor information may be input to the encoding unit 4613 or the multiplexing unit 4614. The input / output unit 4615 may output the point cloud data or the encoded data directly to the outside.

[0045] The transmission signal (multiplexed data) output from the three-dimensional data encoding system 4601 is input to the three-dimensional data decoding system 4602 via the external connection unit 4604 .

[0046] The three-dimensional data decoding system 4602 generates point cloud data, which is three-dimensional data, by decoding the encoded data or multiplexed data. Note that the three-dimensional data decoding system 4602 may be a three-dimensional data decoding device realized by a single device, or may be a system realized by multiple devices. Furthermore, the three-dimensional data decoding device may include some of the multiple processing units included in the three-dimensional data decoding system 4602.

[0047] The three-dimensional data decoding system 4602 includes a sensor information acquisition unit 4621 , an input / output unit 4622 , a demultiplexing unit 4623 , a decoding unit 4624 , a presentation unit 4625 , a user interface 4626 , and a control unit 4627 .

[0048] The sensor information acquisition unit 4621 acquires sensor information from the sensor terminal 4603 .

[0049] The input / output unit 4622 acquires the transmission signal, decodes the multiplexed data (file format or packets) from the transmission signal, and outputs the multiplexed data to the demultiplexer 4623.

[0050] The demultiplexing unit 4623 obtains the coded data, control information, and additional information from the multiplexed data, and outputs the coded data, control information, and additional information to the decoding unit 4624.

[0051] The decoding unit 4624 reconstructs the point cloud data by decoding the encoded data.

[0052] The presentation unit 4625 presents the point cloud data to the user. For example, the presentation unit 4625 displays information or images based on the point cloud data. The user interface 4626 acquires instructions based on user operations. The control unit 4627 (or the application execution unit) controls each processing unit. In other words, the control unit 4627 controls demultiplexing, decoding, presentation, etc.

[0053] The input / output unit 4622 may acquire point cloud data or encoded data directly from the outside. The presentation unit 4625 may acquire additional information such as sensor information and present information based on the additional information. The presentation unit 4625 may perform presentation based on a user instruction acquired by the user interface 4626.

[0054] The sensor terminal 4603 generates sensor information, which is information obtained by a sensor. The sensor terminal 4603 is a terminal equipped with a sensor or a camera, and examples thereof include a moving body such as an automobile, a flying object such as an airplane, a mobile terminal, or a camera.

[0055] The sensor information that can be acquired by the sensor terminal 4603 includes, for example, (1) the distance between the sensor terminal 4603 and an object, or the reflectance of the object, obtained from a LIDAR, millimeter-wave radar, or infrared sensor, and (2) the distance between a camera and an object, or the reflectance of the object, obtained from multiple monocular camera images or stereo camera images. The sensor information may also include the attitude, direction, gyro (angular velocity), position (GPS information or altitude), speed, acceleration, etc. of the sensor. The sensor information may also include temperature, air pressure, humidity, magnetism, etc.

[0056] The external connection unit 4604 is realized by an integrated circuit (LSI or IC), an external storage unit, communication with a cloud server via the Internet, broadcasting, or the like.

[0057] Next, point cloud data will be described. Fig. 2 is a diagram showing the configuration of point cloud data. Fig. 3 is a diagram showing an example of the configuration of a data file in which information about point cloud data is written.

[0058] Point cloud data includes data on multiple points. The data on each point includes location information (three-dimensional coordinates) and attribute information for that location information. A collection of multiple points is called a point cloud. For example, a point cloud can represent the three-dimensional shape of an object.

[0059] Position information such as three-dimensional coordinates is sometimes called geometry. Data for each point may also include attribute information of multiple attribute types. Attribute types include, for example, color or reflectance.

[0060] One piece of attribute information may be associated with one piece of location information, or multiple pieces of attribute information with different attribute types may be associated with one piece of location information, or multiple pieces of attribute information of the same attribute type may be associated with one piece of location information.

[0061] The configuration example of the data file shown in FIG. 3 is an example in which there is a one-to-one correspondence between position information and attribute information, and shows the position information and attribute information of N points that make up the point cloud data.

[0062] The position information is, for example, information on the three axes x, y, and z. The attribute information is, for example, RGB color information. A typical data file is a ply file.

[0063] Next, the types of point cloud data will be explained. Fig. 4 is a diagram showing the types of point cloud data. As shown in Fig. 4, point cloud data includes static objects and dynamic objects.

[0064] A static object is 3D point cloud data at any time (a certain time). A dynamic object is 3D point cloud data that changes over time. Hereinafter, 3D point cloud data at a certain time will be referred to as a PCC frame, or simply a frame.

[0065] The object may be a point cloud with a certain area restriction, such as ordinary video data, or a large-scale point cloud with no area restriction, such as map information.

[0066] Furthermore, there may be point cloud data of various densities, such as sparse point cloud data and dense point cloud data.

[0067] Each processing unit will be described in detail below. Sensor information is acquired by various methods, such as a distance sensor such as a LIDAR or a range finder, a stereo camera, or a combination of multiple monocular cameras. The point cloud data generation unit 4618 generates point cloud data based on the sensor information acquired by the sensor information acquisition unit 4617. The point cloud data generation unit 4618 generates position information as point cloud data, and adds attribute information for the position information to the position information.

[0068] The point cloud data generation unit 4618 may process the point cloud data when generating position information or adding attribute information. For example, the point cloud data generation unit 4618 may reduce the amount of data by deleting point clouds with overlapping positions. In addition, the point cloud data generation unit 4618 may convert (position shift, rotation, normalization, etc.) the position information or render the attribute information.

[0069] In FIG. 1, the point cloud data generation system 4611 is included in the three-dimensional data encoding system 4601, but it may be provided independently outside the three-dimensional data encoding system 4601.

[0070] The encoding unit 4613 generates encoded data by encoding the point cloud data based on a predetermined encoding method. There are two main types of encoding methods: the first is an encoding method that uses position information, and this encoding method will be referred to as the first encoding method hereinafter; and the second is an encoding method that uses a video codec, and this encoding method will be referred to as the second encoding method hereinafter.

[0071] The decoding unit 4624 decodes the coded data based on a predetermined coding method to decode the point group data.

[0072] The multiplexing unit 4614 generates multiplexed data by multiplexing the encoded data using an existing multiplexing method. The generated multiplexed data is transmitted or stored. In addition to the PCC encoded data, the multiplexing unit 4614 multiplexes other media such as video, audio, subtitles, applications, and files, or reference time information. The multiplexing unit 4614 may also multiplex attribute information related to sensor information or point cloud data.

[0073] Multiplexing methods or file formats include ISOBMFF, MPEG-DASH, which is an ISOBMFF-based transmission method, MMT, MPEG-2 TS Systems, and RMP.

[0074] The demultiplexer 4623 extracts PCC encoded data, other media, time information, and the like from the multiplexed data.

[0075] The input / output unit 4615 transmits the multiplexed data using a method suited to the transmission medium or storage medium, such as broadcasting or communication. The input / output unit 4615 may communicate with other devices via the Internet, or may communicate with a storage unit such as a cloud server.

[0076] The communication protocol used may be http, ftp, TCP, UDP, etc. A PULL type communication method or a PUSH type communication method may be used.

[0077] Either wired or wireless transmission may be used. For wired transmission, Ethernet (registered trademark), USB, RS-232C, HDMI (registered trademark), coaxial cable, etc. are used. For wireless transmission, wireless LAN, Wi-Fi (registered trademark), Bluetooth (registered trademark), millimeter waves, etc. are used.

[0078] As a broadcasting system, for example, DVB-T2, DVB-S2, DVB-C2, ATSC3.0, or ISDB-S3 is used.

[0079] Fig. 5 is a diagram showing the configuration of a first encoding unit 4630, which is an example of the encoding unit 4613 that performs encoding using the first encoding method. Fig. 6 is a block diagram of the first encoding unit 4630. The first encoding unit 4630 generates encoded data (encoded stream) by encoding point cloud data using the first encoding method. This first encoding unit 4630 includes a position information encoding unit 4631, an attribute information encoding unit 4632, an additional information encoding unit 4633, and a multiplexing unit 4634.

[0080] The first encoding unit 4630 is characterized in that it performs encoding taking into consideration a three-dimensional structure. The first encoding unit 4630 is also characterized in that the attribute information encoding unit 4632 performs encoding using information obtained from the position information encoding unit 4631. The first encoding method is also called GPCC (Geometry based PCC).

[0081] The point cloud data is PCC point cloud data such as a PLY file, or PCC point cloud data generated from sensor information, and includes position information (Position), attribute information (Attribute), and other additional information (MetaData). The position information is input to a position information encoder 4631, the attribute information is input to an attribute information encoder 4632, and the additional information is input to an additional information encoder 4633.

[0082] The position information encoding unit 4631 encodes the position information to generate encoded position information (Compressed Geometry), which is encoded data. For example, the position information encoding unit 4631 encodes the position information using an N-ary tree structure such as an octree. Specifically, in an octree, the target space is divided into eight nodes (subspaces), and 8-bit information (occupancy code) indicating whether or not a point cloud is included in each node is generated. Furthermore, the node including the point cloud is further divided into eight nodes, and 8-bit information indicating whether or not a point cloud is included in each of the eight nodes is generated. This process is repeated until the number of point clouds included in a predetermined layer or node falls below a threshold.

[0083] The attribute information encoding unit 4632 generates encoded attribute information (Compressed Attribute) that is encoded data by encoding using the configuration information generated by the position information encoding unit 4631. For example, the attribute information encoding unit 4632 determines a reference point (reference node) to be referenced when encoding a target point (target node) to be processed, based on the octree structure generated by the position information encoding unit 4631. For example, the attribute information encoding unit 4632 references a peripheral node or adjacent node whose parent node in the octree is the same as that of the target node. Note that the method of determining the reference relationship is not limited to this.

[0084] Furthermore, the encoding process of the attribute information may include at least one of a quantization process, a prediction process, and an arithmetic coding process. In this case, the reference means using a reference node to calculate a predicted value of the attribute information, or using the state of the reference node (e.g., occupancy information indicating whether the reference node includes a point group) to determine an encoding parameter. For example, the encoding parameter is a quantization parameter in a quantization process, or a context in an arithmetic coding process.

[0085] The additional information encoding unit 4633 generates encoded additional information (Compressed MetaData) that is encoded data by encoding compressible data from the additional information.

[0086] The multiplexing unit 4634 multiplexes the encoding position information, the encoding attribute information, the encoding additional information, and other additional information to generate a compressed stream, which is encoded data. The generated compressed stream is output to a processing unit in a system layer (not shown).

[0087] Next, a first decoding unit 4640, which is an example of the decoding unit 4624 that performs decoding using the first encoding method, will be described. FIG. 7 is a diagram showing the configuration of the first decoding unit 4640. FIG. 8 is a block diagram of the first decoding unit 4640. The first decoding unit 4640 generates point cloud data by decoding, using the first encoding method, coded data (coded stream) coded using the first coding method. The first decoding unit 4640 includes a demultiplexing unit 4641, a position information decoding unit 4642, an attribute information decoding unit 4643, and an additional information decoding unit 4644.

[0088] A coded stream (compressed stream) that is coded data is input to the first decoding unit 4640 from a processing unit in a system layer (not shown).

[0089] The demultiplexer 4641 separates the encoded position information (Compressed Geometry), the encoded attribute information (Compressed Attribute), the encoded additional information (Compressed MetaData), and other additional information from the encoded data.

[0090] The position information decoding unit 4642 generates position information by decoding the encoded position information. For example, the position information decoding unit 4642 restores the position information of a point group represented by three-dimensional coordinates from the encoded position information represented by an N-ary tree structure such as an octree.

[0091] The attribute information decoding unit 4643 decodes the encoded attribute information based on the configuration information generated by the position information decoding unit 4642. For example, the attribute information decoding unit 4643 determines a reference point (reference node) to be referenced in decoding the target point (target node) to be processed based on the octree structure obtained by the position information decoding unit 4642. For example, the attribute information decoding unit 4643 references a peripheral node or adjacent node whose parent node in the octree is the same as that of the target node. Note that the method of determining the reference relationship is not limited to this.

[0092] Furthermore, the attribute information decoding process may include at least one of an inverse quantization process, a prediction process, and an arithmetic decoding process. In this case, the reference means using a reference node to calculate a predicted value of the attribute information, or using the state of the reference node (e.g., occupancy information indicating whether the reference node includes a point group) to determine a decoding parameter. For example, the decoding parameter is a quantization parameter in an inverse quantization process, or a context in an arithmetic decoding process.

[0093] The additional information decoding unit 4644 generates additional information by decoding the encoded additional information. The first decoding unit 4640 uses the additional information necessary for decoding the position information and attribute information during decoding, and outputs the additional information necessary for the application to the outside.

[0094] Next, a description will be given of second encoding unit 4650, which is an example of encoding unit 4613 that performs encoding using the second encoding method. Fig. 9 is a diagram showing the configuration of second encoding unit 4650. Fig. 10 is a block diagram of second encoding unit 4650.

[0095] The second encoding unit 4650 generates encoded data (encoded stream) by encoding the point cloud data using a second encoding method. The second encoding unit 4650 includes an additional information generation unit 4651, a position image generation unit 4652, an attribute image generation unit 4653, a video encoding unit 4654, an additional information encoding unit 4655, and a multiplexing unit 4656.

[0096] The second encoding unit 4650 has a feature of generating a position image and an attribute image by projecting a three-dimensional structure onto a two-dimensional image, and encoding the generated position image and attribute image using an existing video encoding method. The second encoding method is also called VPCC (Video based PCC).

[0097] The point cloud data is PCC point cloud data such as a PLY file or PCC point cloud data generated from sensor information, and includes position information (Position), attribute information (Attribute), and other additional information (MetaData).

[0098] The additional information generating unit 4651 generates map information of a plurality of two-dimensional images by projecting a three-dimensional structure onto the two-dimensional images.

[0099] The position image generation unit 4652 generates a position image (Geometry Image) based on the position information and the map information generated by the additional information generation unit 4651. This position image is, for example, a distance image in which distance (Depth) is indicated as a pixel value. Note that this distance image may be an image in which multiple point clouds are viewed from a single viewpoint (an image in which multiple point clouds are projected onto a single two-dimensional plane), or may be multiple images in which multiple point clouds are viewed from multiple viewpoints, or may be a single image in which these multiple images are integrated.

[0100] The attribute image generation unit 4653 generates an attribute image based on the attribute information and the map information generated by the additional information generation unit 4651. This attribute image is, for example, an image in which attribute information (for example, color (RGB)) is represented as pixel values. Note that this image may be an image in which multiple point clouds are viewed from one viewpoint (an image in which multiple point clouds are projected onto one two-dimensional plane), or multiple images in which multiple point clouds are viewed from multiple viewpoints, or a single image in which these multiple images are integrated.

[0101] The video encoding unit 4654 generates an encoded position image (Compressed Geometry Image) and an encoded attribute image (Compressed Attribute Image), which are encoded data, by encoding the position image and the attribute image using a video encoding method. Note that any known encoding method may be used as the video encoding method. For example, the video encoding method is AVC, HEVC, or the like.

[0102] The additional information encoding unit 4655 generates encoded additional information (Compressed MetaData) by encoding the additional information, map information, and the like included in the point cloud data.

[0103] The multiplexing unit 4656 multiplexes the encoding position image, the encoding attribute image, the encoding additional information, and other additional information to generate an encoded stream (Compressed Stream) that is encoded data. The generated encoded stream is output to a processing unit in a system layer (not shown).

[0104] Next, a second decoding unit 4660, which is an example of the decoding unit 4624 that performs decoding using the second encoding method, will be described. FIG. 11 is a diagram showing the configuration of the second decoding unit 4660. FIG. 12 is a block diagram of the second decoding unit 4660. The second decoding unit 4660 generates point cloud data by decoding, using the second encoding method, coded data (coded stream) coded using the second coding method. The second decoding unit 4660 includes a demultiplexing unit 4661, a video decoding unit 4662, an additional information decoding unit 4663, a position information generation unit 4664, and an attribute information generation unit 4665.

[0105] A coded stream (compressed stream) that is coded data is input to the second decoding unit 4660 from a processing unit in a system layer (not shown).

[0106] The demultiplexer 4661 separates the encoded position image (Compressed Geometry Image), the encoded attribute image (Compressed Attribute Image), the encoded additional information (Compressed MetaData), and other additional information from the encoded data.

[0107] The video decoding unit 4662 generates a position image and an attribute image by decoding the encoded position image and the encoded attribute image using a video encoding method. Note that any known encoding method may be used as the video encoding method. For example, the video encoding method is AVC or HEVC.

[0108] The additional information decoding unit 4663 decodes the encoded additional information to generate additional information including map information and the like.

[0109] The position information generating unit 4664 generates position information using the position image and map information. The attribute information generating unit 4665 generates attribute information using the attribute image and map information.

[0110] The second decoding unit 4660 uses the additional information necessary for decoding during decoding, and outputs the additional information necessary for the application to the outside.

[0111] The following describes the problems with the PCC encoding method. Fig. 13 is a diagram showing a protocol stack related to PCC encoded data. Fig. 13 shows an example in which other media data such as video (e.g., HEVC) or audio is multiplexed onto the PCC encoded data and transmitted or stored.

[0112] Multiplexing methods and file formats have the function of multiplexing various coded data and transmitting or storing them. To transmit or store coded data, the coded data must be converted into the format of the multiplexing method. For example, HEVC specifies a technology that stores coded data in a data structure called a NAL unit and stores the NAL unit in ISOBMFF.

[0113] On the other hand, currently, a first encoding method (Codec1) and a second encoding method (Codec2) are being considered as methods for encoding point cloud data, but the structure of the encoded data and the method for storing the encoded data in a system format have not been defined, which poses the problem that, as it stands, it is not possible to perform MUX processing (multiplexing) in the encoding unit, transmission, or storage.

[0114] In the following description, unless a specific encoding method is specified, it refers to either the first encoding method or the second encoding method.

[0115] (Embodiment 2) In this embodiment, a method for storing NAL units in an ISOBMFF file will be described.

[0116] ISOBMFF (ISO based media file format) is a file format standard defined in ISO / IEC 14496-12. ISOBMFF is a media-independent standard that defines a format that can store multiplexed media such as video, audio, and text.

[0117] This section explains the basic structure (file) of ISOBMFF. The basic unit in ISOBMFF is a box. A box consists of type, length, and data, and a file is a collection of boxes of various types.

[0118] 14 is a diagram showing the basic structure (file) of ISOBMFF. An ISOBMFF file mainly includes boxes such as ftyp, which indicates the brand of the file using 4CC (four-character code), moov, which stores metadata such as control information, and mdat, which stores data.

[0119] Storing methods for each media type in ISOBMFF files are specified separately. For example, storage methods for AVC video and HEVC video are specified in ISO / IEC 14496-15. While it is conceivable to extend and use the functions of ISOBMFF to store or transmit PCC encoded data, there are no regulations yet for storing PCC encoded data in ISOBMFF files. Therefore, in this embodiment, a method for storing PCC encoded data in an ISOBMFF file will be described.

[0120] 15 is a diagram showing a protocol stack when NAL units common to PCC codecs are stored in an ISOBMFF file. Here, NAL units common to PCC codecs are stored in an ISOBMFF file. Although NAL units are common to PCC codecs, multiple PCC codecs are stored in the NAL unit, so it is desirable to define a storage method (Carriage of Codec1, Carriage of Codec2) according to each codec.

[0121] (Embodiment 3) In this embodiment, the types of coded data (position information (Geometry), attribute information (Attribute), additional information (Metadata)) generated by the first coding unit 4630 or the second coding unit 4650 described above, a method for generating the additional information (Metadata), and multiplexing processing in the multiplexing unit will be described. Note that the additional information (Metadata) may also be referred to as a parameter set or control information.

[0122] In this embodiment, the dynamic object (three-dimensional point cloud data that changes over time) described in Figure 4 will be used as an example, but a similar method may also be used in the case of a static object (three-dimensional point cloud data at any time).

[0123] 16 is a diagram showing the configurations of an encoding unit 4801 and a multiplexing unit 4802 included in the three-dimensional data encoding device according to this embodiment. The encoding unit 4801 corresponds to, for example, the first encoding unit 4630 or the second encoding unit 4650 described above. The multiplexing unit 4802 corresponds to the multiplexing unit 4634 or 46456 described above.

[0124] The encoding unit 4801 encodes point cloud data of multiple PCC (Point Cloud Compression) frames, and generates encoded data (Multiple Compressed Data) of multiple pieces of position information, attribute information, and additional information.

[0125] The multiplexing unit 4802 converts data of multiple data types (position information, attribute information, and additional information) into NAL units, thereby converting the data into a data structure that takes into account data access in the decoding device.

[0126] 17 is a diagram showing an example of the structure of coded data generated by coding unit 4801. Arrows in the diagram indicate dependencies related to the decoding of coded data, with the source of the arrow depending on the data at the end of the arrow. In other words, the decoding device decodes the data at the end of the arrow and uses the decoded data to decode the data at the end of the arrow. In other words, dependency means that the data on which the dependency is based is referenced (used) in the processing (encoding, decoding, etc.) of the data on which the dependency is based.

[0127] First, the process of generating encoded data of position information will be described. The encoding unit 4801 generates encoded position data (compressed geometry data) for each frame by encoding the position information of each frame. The encoded position data is represented by G(i), where i indicates the frame number, the time of the frame, etc.

[0128] The encoding unit 4801 also generates a position parameter set (GPS(i)) corresponding to each frame. The position parameter set includes parameters that can be used to decode the encoded position data. The encoded position data for each frame depends on the corresponding position parameter set.

[0129] Furthermore, encoded position data consisting of multiple frames is defined as a position sequence (Geometry Sequence). The encoding unit 4801 generates a position sequence parameter set (Geometry Sequence PS: also referred to as position SPS) that stores parameters commonly used in decoding processes for multiple frames in the position sequence. The position sequence depends on the position SPS.

[0130] Next, the process of generating coded data of attribute information will be described. The coding unit 4801 generates coded attribute data (Compressed Attribute Data) for each frame by coding the attribute information of each frame. The coded attribute data is represented by A(i). Also, Fig. 17 shows an example in which attribute X and attribute Y exist, and the coded attribute data of attribute X is represented by AX(i) and the coded attribute data of attribute Y is represented by AY(i).

[0131] The encoding unit 4801 also generates an attribute parameter set (APS(i)) corresponding to each frame. The attribute parameter set for attribute X is represented as AXPS(i), and the attribute parameter set for attribute Y is represented as AYPS(i). The attribute parameter set includes parameters that can be used to decode encoded attribute information. The encoded attribute data depends on the corresponding attribute parameter set.

[0132] Furthermore, encoded attribute data consisting of multiple frames is defined as an attribute sequence. The encoding unit 4801 generates an attribute sequence parameter set (Attribute Sequence PS: also referred to as attribute SPS) that stores parameters commonly used in decoding processes for multiple frames in the attribute sequence. The attribute sequence depends on the attribute SPS.

[0133] Furthermore, in the first encoding method, the encoded attribute data depends on the encoded position data.

[0134] 17 shows an example in which two types of attribute information (attribute X and attribute Y) exist. When there are two types of attribute information, for example, two encoding units generate respective data and metadata. Also, for example, an attribute sequence is defined for each type of attribute information, and an attribute SPS is generated for each type of attribute information.

[0135] 17 shows an example in which there is one type of position information and two types of attribute information, but the present invention is not limited to this, and there may be one type of attribute information, or three or more types. In this case, encoded data can be generated using a similar method. Furthermore, in the case of point cloud data that does not have attribute information, the attribute information may not be necessary. In this case, the encoding unit 4801 does not need to generate a parameter set related to the attribute information.

[0136] Next, the process of generating additional information (metadata) will be described. The encoding unit 4801 generates a PCC Stream PS (also referred to as stream PS), which is a parameter set for the entire PCC stream. The encoding unit 4801 stores, in the stream PS, parameters that can be used in common for decoding processes for one or more position sequences and one or more attribute sequences. For example, the stream PS includes identification information indicating the codec for the point cloud data, information indicating the algorithm used for encoding, and the like. The position sequence and attribute sequence depend on the stream PS.

[0137] Next, the access unit and GOF will be explained. In this embodiment, the concepts of the access unit (AU) and GOF (Group of Frame) are newly introduced.

[0138] An access unit is a basic unit for accessing data during decoding, and is composed of one or more pieces of data and one or more pieces of metadata. For example, an access unit is composed of position information at the same time and one or more pieces of attribute information. A GOF is a random access unit and is composed of one or more access units.

[0139] The encoding unit 4801 generates an access unit header (AU Header) as identification information indicating the beginning of an access unit. The encoding unit 4801 stores parameters related to the access unit in the access unit header. For example, the access unit header includes the configuration or information of the coded data included in the access unit. The access unit header also includes parameters commonly used for the data included in the access unit, such as parameters related to decoding of the coded data.

[0140] Instead of an access unit header, the encoding unit 4801 may generate an access unit delimiter that does not include parameters related to the access unit. This access unit delimiter is used as identification information indicating the start of the access unit. The decoding device identifies the start of the access unit by detecting the access unit header or the access unit delimiter.

[0141] Next, the generation of identification information for the start of a GOF will be described. The encoding unit 4801 generates a GOF header as identification information that indicates the start of a GOF. The encoding unit 4801 stores parameters related to the GOF in the GOF header. For example, the GOF header includes the configuration or information of the coded data included in the GOF. The GOF header also includes parameters commonly used for the data included in the GOF, such as parameters related to the decoding of the coded data.

[0142] Instead of a GOF header, the encoding unit 4801 may generate a GOF delimiter that does not include parameters related to the GOF. This GOF delimiter is used as identification information that indicates the beginning of the GOF. The decoding device identifies the beginning of the GOF by detecting the GOF header or the GOF delimiter.

[0143] In PCC encoded data, for example, an access unit is defined as a PCC frame unit, and a decoding device accesses a PCC frame based on identification information at the beginning of the access unit.

[0144] Also, for example, GOF is defined as one random access unit. A decoding device accesses the random access unit based on the identification information at the beginning of the GOF. For example, if PCC frames are not dependent on each other and can be decoded independently, the PCC frames may be defined as the random access unit.

[0145] It should be noted that two or more PCC frames may be allocated to one access unit, and multiple random access units may be allocated to one GOF.

[0146] The encoding unit 4801 may also define and generate parameter sets or metadata other than those described above. For example, the encoding unit 4801 may generate SEI (Supplemental Enhancement Information) that stores parameters (optional parameters) that may not necessarily be used during decoding.

[0147] Next, the structure of coded data and the method of storing coded data in NAL units will be described.

[0148] For example, a data format is defined for each type of coded data. Figure 18 shows examples of coded data and NAL units.

[0149] For example, as shown in Fig. 18, the coded data includes a header and a payload. The coded data may include length information indicating the length (amount of data) of the coded data, the header, or the payload. The coded data may not include a header.

[0150] The header includes, for example, identification information for identifying the data, such as the data type or frame number.

[0151] The header includes, for example, identification information indicating a reference relationship. This identification information is stored in the header when, for example, there is a dependency relationship between data, and is information for referencing the reference destination from the reference source. For example, the header of the reference destination includes identification information for identifying the data. The header of the reference source includes identification information indicating the reference destination.

[0152] If the reference destination or the reference source can be identified or derived from other information, the identification information for specifying the data or the identification information indicating the reference relationship may be omitted.

[0153] The multiplexing unit 4802 stores the coded data in the payload of the NAL unit. The NAL unit header includes pcc_nal_unit_type, which is information identifying the coded data. Figure 19 shows an example of the semantics of pcc_nal_unit_type.

[0154] 19, when pcc_codec_type is codec 1 (Codec1: first encoding method), values ​​0 to 10 of pcc_nal_unit_type are assigned to the encoded position data (Geometry), encoded attribute X data (AttributeX), encoded attribute Y data (AttributeY), position PS (Geom.PS), attribute XPS (AttrX.PS), attribute YPS (AttrX.PS), position SPS (Geometry Sequence PS), attribute XSPS (AttributeX Sequence PS), attribute YSPS (AttributeY Sequence PS), AU header (AU Header), and GOF header (GOF Header) in codec 1. Values ​​11 and above are assigned as spares for codec 1.

[0155] When pcc_codec_type is Codec2 (Codec2: second encoding method), values ​​0 to 2 of pcc_nal_unit_type are assigned to codec data A (DataA), metadata A (MetaDataA), and metadata B (MetaDataB). Values ​​3 and above are assigned as spares for Codec2.

[0156] Next, the data transmission order will be explained. The following explains the restrictions on the transmission order of NAL units.

[0157] The multiplexing unit 4802 collectively transmits NAL units in units of GOF or AU. The multiplexing unit 4802 places a GOF header at the beginning of a GOF, and places an AU header at the beginning of an AU.

[0158] The multiplexing unit 4802 may allocate a sequence parameter set (SPS) for each AU so that the decoding device can decode from the next AU even if data is lost due to packet loss or the like.

[0159] If the coded data has a dependency relationship related to decoding, the decoding device decodes the referenced data first, and then decodes the referenced data. In order to enable the decoding device to decode the data in the order in which it was received without rearranging the data, the multiplexing unit 4802 sends the referenced data first.

[0160] 20 is a diagram showing examples of the transmission order of NAL units, and shows three examples: position information priority, parameter priority, and data integration.

[0161] The sending order with priority given to location information is an example in which information related to location information and information related to attribute information are sent together. In this sending order, the sending of information related to location information is completed earlier than the sending of information related to attribute information.

[0162] For example, by using this transmission order, a decoding device that does not decode attribute information may be able to set a time during which it does not process the attribute information by ignoring the decoding of the attribute information. Also, for example, in the case of a decoding device that wants to decode position information quickly, it may be able to decode the position information more quickly by obtaining the encoded data of the position information early.

[0163] In FIG. 20, the attributes XSPS and YSPS are combined and written as the attribute SPS, but the attributes XSPS and YSPS may be arranged separately.

[0164] In the parameter set priority sending order, the parameter sets are sent first and the data is sent later.

[0165] As long as the NAL unit transmission order constraints are met as described above, the multiplexing unit 4802 may transmit NAL units in any order. For example, order identification information may be defined, and the multiplexing unit 4802 may have the function of transmitting NAL units in multiple order patterns. For example, the NAL unit order identification information may be stored in the stream PS.

[0166] The three-dimensional data decoding device may perform decoding based on the order identification information. The three-dimensional data decoding device may instruct the three-dimensional data encoding device on a desired transmission order, and the three-dimensional data encoding device (multiplexing unit 4802) may control the transmission order in accordance with the instructed transmission order.

[0167] The multiplexing unit 4802 may generate coded data that merges multiple functions, as long as the data transmission order is within the constraints of the transmission order, such as the transmission order of the integrated data. For example, as shown in Fig. 20, the GOF header and the AU header may be integrated, or the AXPS and the AYPS may be integrated. In this case, an identifier indicating that the data has multiple functions is defined in pcc_nal_unit_type.

[0168] A modified example of this embodiment will be described below. PS has levels, such as a frame-level PS, a sequence-level PS, and a PCC sequence-level PS, and if the PCC sequence level is the higher level and the frame level is the lower level, the following method may be used to store parameters.

[0169] The default PS value is indicated in the higher PS. Also, if the value of the lower PS differs from the value of the higher PS, the PS value is indicated in the lower PS. Alternatively, the PS value is not written in the higher PS, but written in the lower PS. Alternatively, information on whether the PS value is to be written in the lower PS, the higher PS, or both is written in either the lower PS or the higher PS, or both. Alternatively, the lower PS may be merged with the higher PS. Alternatively, if the lower PS and the higher PS overlap, the multiplexing unit 4802 may omit sending one of them.

[0170] The encoding unit 4801 or the multiplexing unit 4802 may divide the data into slices or tiles and transmit the divided data. The divided data includes information for identifying the divided data, and parameters used to decode the divided data are included in the parameter set. In this case, an identifier indicating that the data stores data or parameters related to tiles or slices is defined in pcc_nal_unit_type.

[0171] (Fourth embodiment) HEVC coding has data division tools such as slicing or tiling to enable parallel processing in a decoding device, but PCC (Point Cloud Compression) coding does not yet have such tools.

[0172] In PCC, various data division methods are possible depending on parallel processing, compression efficiency, and compression algorithms. This section explains the definitions of slices and tiles, the data structure, and transmission and reception methods.

[0173] 21 is a block diagram showing the configuration of a first encoding unit 4910 included in the three-dimensional data encoding device according to this embodiment. The first encoding unit 4910 generates encoded data (encoded stream) by encoding point cloud data using a first encoding method (GPCC (Geometry based PCC)). The first encoding unit 4910 includes a division unit 4911, multiple position information encoding units 4912, multiple attribute information encoding units 4913, an additional information encoding unit 4914, and a multiplexing unit 4915.

[0174] The dividing unit 4911 divides the point cloud data to generate a plurality of pieces of divided data. Specifically, the dividing unit 4911 divides the space of the point cloud data into a plurality of subspaces to generate a plurality of pieces of divided data. Here, a subspace is one of a tile and a slice, or a combination of a tile and a slice. More specifically, the point cloud data includes position information, attribute information, and additional information. The dividing unit 4911 divides the position information into a plurality of pieces of divided position information, and divides the attribute information into a plurality of pieces of divided attribute information. The dividing unit 4911 also generates additional information related to the division.

[0175] The position information encoding units 4912 encode the plurality of pieces of divided position information to generate a plurality of pieces of encoded position information. For example, the position information encoding units 4912 process the plurality of pieces of divided position information in parallel.

[0176] The attribute information encoding units 4913 encode the divided attribute information to generate the coded attribute information For example, the attribute information encoding units 4913 process the divided attribute information in parallel.

[0177] The additional information encoding unit 4914 generates encoded additional information by encoding the additional information included in the point cloud data and the additional information related to the data division generated by the division unit 4911 at the time of division.

[0178] The multiplexing unit 4915 multiplexes multiple pieces of encoding position information, multiple pieces of encoding attribute information, and encoded additional information to generate encoded data (encoded stream), and transmits the generated encoded data. The encoded additional information is also used during decoding.

[0179] 21 shows an example in which there are two position information encoders 4912 and two attribute information encoders 4913, but the number of position information encoders 4912 and two attribute information encoders 4913 may each be one, or three or more. Furthermore, multiple pieces of divided data may be processed in parallel within the same chip, like multiple cores within a CPU, or may be processed in parallel by cores on multiple chips, or may be processed in parallel by multiple cores on multiple chips.

[0180] 22 is a block diagram showing the configuration of the first decoding unit 4920. The first decoding unit 4920 restores the point cloud data by decoding coded data (coded stream) generated by coding the point cloud data using the first coding method (GPCC). The first decoding unit 4920 includes a demultiplexing unit 4921, multiple position information decoding units 4922, multiple attribute information decoding units 4923, an additional information decoding unit 4924, and a combining unit 4925.

[0181] The demultiplexing unit 4921 demultiplexes the coded data (coded stream) to generate a plurality of pieces of coding position information, a plurality of pieces of coding attribute information, and coded additional information.

[0182] The position information decoding units 4922 generate a plurality of pieces of divided position information by decoding the plurality of pieces of encoded position information. For example, the position information decoding units 4922 process the plurality of pieces of encoded position information in parallel.

[0183] The attribute information decoding units 4923 generate a plurality of pieces of divided attribute information by decoding the plurality of pieces of encoded attribute information. For example, the attribute information decoding units 4923 process the plurality of pieces of encoded attribute information in parallel.

[0184] The plurality of additional information decoders 4924 generate additional information by decoding the encoded additional information.

[0185] The combining unit 4925 generates position information by combining a plurality of pieces of divided position information using the additional information. The combining unit 4925 generates attribute information by combining a plurality of pieces of divided attribute information using the additional information.

[0186] 22 shows an example in which there are two position information decoding units 4922 and two attribute information decoding units 4923, but the number of position information decoding units 4922 and two attribute information decoding units 4923 may be one, or three or more. Furthermore, multiple pieces of divided data may be processed in parallel within the same chip, such as multiple cores within a CPU, or may be processed in parallel by cores on multiple chips, or may be processed in parallel by multiple cores on multiple chips.

[0187] Next, it will be described how the dividing unit 4911 has a configuration. Fig. 23 is a block diagram of the dividing unit 4911. The dividing unit 4911 includes a slice dividing unit 4931 (Slice Divider), a position information tile dividing unit 4932 (Geometry Tile Divider), and an attribute information tile dividing unit 4933 (Attribute Tile Divider).

[0188] The slice division unit 4931 generates a plurality of slice position information by dividing position information (Position (Geometry)) into slices. The slice division unit 4931 also generates a plurality of slice attribute information by dividing attribute information (Attribute) into slices. The slice division unit 4931 also outputs slice additional information (Slice MetaData) including information related to the slice division and information generated in the slice division.

[0189] The position information tile dividing unit 4932 divides a plurality of slice position information pieces into tiles to generate a plurality of pieces of divided position information pieces (a plurality of pieces of tile position information pieces). The position information tile dividing unit 4932 also outputs position tile additional information (Geometry Tile MetaData) including information related to the tile division of the position information pieces and information generated in the tile division of the position information pieces.

[0190] The attribute information tile dividing unit 4933 divides a plurality of slice attribute information pieces into tiles to generate a plurality of pieces of divided attribute information (a plurality of pieces of tile attribute information). The attribute information tile dividing unit 4933 also outputs attribute tile additional information (Attribute Tile MetaData) including information related to the tile division of the attribute information and information generated during the tile division of the attribute information.

[0191] The number of slices or tiles to be divided is equal to or greater than 1. In other words, division into slices or tiles does not have to be performed.

[0192] Although an example in which tile division is performed after slice division has been shown here, slice division may be performed after tile division. Furthermore, new division types may be defined in addition to slices and tiles, and division may be performed using three or more division types.

[0193] A method for dividing point cloud data will be described below. Fig. 24 is a diagram showing an example of division into slices and tiles.

[0194] First, the method of dividing into slices will be described. The dividing unit 4911 divides the three-dimensional point cloud data into arbitrary point clouds in slice units. In dividing into slices, the dividing unit 4911 does not divide the position information and attribute information that constitute a point, but divides the position information and attribute information together. In other words, the dividing unit 4911 divides into slices so that the position information and attribute information of an arbitrary point belong to the same slice. Note that, as long as this is followed, any number of divisions and any division method may be used. Furthermore, the minimum unit of division is a point. For example, the number of divisions for the position information and the attribute information is the same. For example, the three-dimensional point corresponding to the position information after dividing into slices and the three-dimensional point corresponding to the attribute information are included in the same slice.

[0195] Furthermore, the division unit 4911 generates slice additional information, which is additional information related to the number of divisions and the division method when dividing the slices. The slice additional information is the same for position information and attribute information. For example, the slice additional information includes information indicating the reference coordinate position, size, or side length of the bounding box after division. The slice additional information also includes information indicating the number of divisions, the division type, etc.

[0196] Next, a tile division method will be described. The division unit 4911 divides the data divided into slices into slice position information (G slices) and slice attribute information (A slices), and divides each of the slice position information and slice attribute information into tiles.

[0197] Although FIG. 24 shows an example of division using an octree structure, any number of divisions and any division method may be used.

[0198] Furthermore, the dividing unit 4911 may divide the position information and the attribute information using different division methods or the same division method. Furthermore, the dividing unit 4911 may divide a plurality of slices into tiles using different division methods or the same division method.

[0199] Furthermore, the dividing unit 4911 generates tile additional information related to the number of divisions and the division method when dividing tiles. The tile additional information (position tile additional information and attribute tile additional information) is independent of position information and attribute information. For example, the tile additional information includes information indicating the reference coordinate position, size, or side length of the bounding box after division. The tile additional information also includes information indicating the number of divisions, division type, etc.

[0200] Next, an example of a method for dividing point cloud data into slices or tiles will be described. The dividing unit 4911 may use a predetermined method as the method for dividing the point cloud data into slices or tiles, or may adaptively switch the method to be used depending on the point cloud data.

[0201] When dividing into slices, the dividing unit 4911 divides the three-dimensional space collectively based on the position information and attribute information. For example, the dividing unit 4911 determines the shape of an object and divides the three-dimensional space into slices according to the shape of the object. For example, the dividing unit 4911 extracts objects such as trees or buildings and divides the space into object units. For example, the dividing unit 4911 divides the space into slices so that one or more objects are entirely included in one slice. Alternatively, the dividing unit 4911 divides one object into multiple slices.

[0202] In this case, the encoding device may change the encoding method for each slice. For example, the encoding device may use a high-quality compression method for a specific object or a specific part of an object. In this case, the encoding device may store information indicating the encoding method for each slice in additional information (metadata).

[0203] Furthermore, the dividing unit 4911 may divide the image into slices based on map information or location information so that each slice corresponds to a predetermined coordinate space.

[0204] When dividing into tiles, the dividing unit 4911 divides the position information and the attribute information independently. For example, the dividing unit 4911 divides a slice into tiles according to the amount of data or the amount of processing. For example, the dividing unit 4911 determines whether the amount of data of a slice (for example, the number of three-dimensional points included in the slice) is greater than a predetermined threshold. If the amount of data of a slice is greater than the threshold, the dividing unit 4911 divides the slice into tiles. If the amount of data of a slice is less than the threshold, the dividing unit 4911 does not divide the slice into tiles.

[0205] For example, the dividing unit 4911 divides a slice into tiles so that the processing amount or processing time in the decoding device is within a certain range (a predetermined value or less). This makes the processing amount per tile in the decoding device constant, facilitating distributed processing in the decoding device.

[0206] Furthermore, when the processing amount differs between the position information and the attribute information, for example, when the processing amount of the position information is greater than the processing amount of the attribute information, the dividing unit 4911 divides the position information into a greater number of divisions than the attribute information.

[0207] Also, for example, depending on the content, if the decoding device may decode and display the position information quickly and decode and display the attribute information later slowly, the division unit 4911 may divide the position information into a larger number of parts than the attribute information. This allows the decoding device to process a larger number of pieces of position information in parallel, thereby making it possible to process the position information faster than the attribute information.

[0208] Note that the decoding device does not necessarily need to process sliced ​​or tiled data in parallel, and may determine whether to process them in parallel depending on the number or capabilities of the decoding processing units.

[0209] By dividing the data in the above manner, adaptive encoding according to the content or object can be realized. Also, parallel processing can be realized in the decoding process. This improves the flexibility of the point cloud encoding system or the point cloud decoding system.

[0210] 25 is a diagram showing examples of slice and tile division patterns. DU in the diagram is a data unit (DataUnit) and indicates tile or slice data. Each DU includes a slice index (SliceIndex) and a tile index (TileIndex). The number in the upper right corner of the DU in the diagram indicates the slice index, and the number in the lower left corner of the DU indicates the tile index.

[0211] In pattern 1, the number of divisions and the division method are the same for G slices and A slices in slice division. In tile division, the number of divisions and the division method for G slices are different from the number of divisions and the division method for A slices. Furthermore, the same number of divisions and the division method are used among multiple G slices. The same number of divisions and the division method are used among multiple A slices.

[0212] In pattern 2, the number of divisions and the division method are the same for G slices and A slices in slice division. The number of divisions and the division method for G slices are different from the number of divisions and the division method for A slices in tile division. Furthermore, the number of divisions and the division method differ between multiple G slices. The number of divisions and the division method differ between multiple A slices.

[0213] Next, a method for encoding divided data will be described. A three-dimensional data encoding device (first encoding unit 4910) encodes each of the divided data. When encoding attribute information, the three-dimensional data encoding device generates dependency information as additional information, which indicates which configuration information (position information, additional information, or other attribute information) was used for encoding. In other words, the dependency information indicates, for example, the configuration information of the reference destination (dependency destination). In this case, the three-dimensional data encoding device generates dependency information based on configuration information corresponding to the division shape of the attribute information. Note that the three-dimensional data encoding device may generate dependency information based on configuration information corresponding to a plurality of division shapes.

[0214] The dependency information may be generated by the three-dimensional data encoding device, and the generated dependency information may be sent to the three-dimensional data decoding device. Alternatively, the three-dimensional data decoding device may generate the dependency information, and the three-dimensional data encoding device may not send the dependency information. Furthermore, the dependency relationships used by the three-dimensional data encoding device may be determined in advance, and the three-dimensional data encoding device may not send the dependency information.

[0215] Figure 26 is a diagram showing an example of the dependency relationships of each data. The tip of the arrow in the diagram indicates the dependency destination, and the start of the arrow indicates the dependency source. The three-dimensional data decoding device decodes data in the order from the dependency destination to the dependency source. Furthermore, data shown by solid lines in the diagram is data that is actually sent, and data shown by dotted lines is data that is not sent.

[0216] In the figure, G indicates location information, and A indicates attribute information. s1 indicates the position information of slice number 1, and G s2indicates the position information of slice number 2. G s1t1 indicates the position information of slice number 1 and tile number 1, and G s1t2 indicates the position information of slice number 1 and tile number 2, and G s2t1 indicates the position information of slice number 2 and tile number 1, and G s2t2 indicates the position information of slice number 2 and tile number 2. Similarly, A s1 indicates the attribute information of slice number 1, and A s2 indicates the attribute information of slice number 2. s1t1 indicates the attribute information of slice number 1 and tile number 1, and A s1t2 indicates the attribute information of slice number 1 and tile number 2, and A s2t1 indicates the attribute information of slice number 2 and tile number 1, and A s2t2 indicates attribute information of slice number 2 and tile number 2.

[0217] Mslice indicates slice additional information, MGtile indicates position tile additional information, and MAtile indicates attribute tile additional information. s1t1 is attribute information A s1t1 D s2t1 is attribute information A s2t1 This shows dependency information for

[0218] Furthermore, the three-dimensional data encoding device may rearrange the data in decoding order so that rearrangement of the data is not required in the three-dimensional data decoding device. Note that the data may be rearranged in the three-dimensional data decoding device, or the data may be rearranged in both the three-dimensional data encoding device and the three-dimensional data decoding device.

[0219] FIG. 27 is a diagram showing an example of the data decoding order. In the example of FIG. 27, decoding is performed in order from the left data. When data has a dependency relationship, the three-dimensional data decoding device decodes the dependent data first. For example, the three-dimensional data encoding device rearranges the data in advance to achieve this order before sending it. Note that any order is acceptable as long as the dependent data comes first. The three-dimensional data encoding device may also send additional information and dependency information before the data.

[0220] 28 is a flowchart showing the flow of processing by the three-dimensional data encoding device. First, the three-dimensional data encoding device encodes data of multiple slices or tiles as described above (S4901). Next, the three-dimensional data encoding device rearranges the data so that the dependent data comes first, as shown in FIG. 27 (S4902). Next, the three-dimensional data encoding device multiplexes the rearranged data (into NAL units) (S4903).

[0221] Next, a description will be given of the configuration of the combining unit 4925 included in the first decoding unit 4920. Fig. 29 is a block diagram showing the configuration of the combining unit 4925. The combining unit 4925 includes a position information tile combining unit 4941 (geometry tile combiner), an attribute information tile combining unit 4942 (attribute tile combiner), and a slice combining unit (slice combiner).

[0222] The position information tile combining unit 4941 generates multiple slice position information pieces by combining multiple pieces of divided position information pieces using the position tile additional information. The attribute information tile combining unit 4942 generates multiple slice attribute information pieces by combining multiple pieces of divided attribute information pieces using the attribute tile additional information.

[0223] The slice combining unit 4943 generates position information by combining a plurality of slice position information pieces using the slice additional information. Also, the slice combining unit 4943 generates attribute information by combining a plurality of slice attribute information pieces using the slice additional information.

[0224] The number of slices or tiles to be divided is equal to or greater than 1. In other words, division into slices or tiles does not necessarily have to be performed.

[0225] Although an example in which tile division is performed after slice division has been shown here, slice division may be performed after tile division. Furthermore, new division types may be defined in addition to slices and tiles, and division may be performed using three or more division types.

[0226] Next, the structure of coded data divided into slices or tiles and a method of storing the coded data in NAL units (multiplexing method) will be described. Fig. 30 is a diagram showing the structure of coded data and a method of storing the coded data in NAL units.

[0227] The coded data (segmentation position information and segmentation attribute information) is stored in the payload of the NAL unit.

[0228] The encoded data includes a header and a payload. The header includes identification information for identifying the data included in the payload. This identification information includes, for example, the type of slice division or tile division (slice_type, tile_type), index information for identifying a slice or tile (slice_idx, tile_idx), position information of the data (slice or tile), or the address of the data. The index information for identifying a slice is also referred to as a slice index (SliceIndex). The index information for identifying a tile is also referred to as a tile index (TileIndex). The type of division may be, for example, a method based on the object shape as described above, a method based on map information or position information, or a method based on the amount of data or processing amount.

[0229] Note that all or part of the above information may be stored in either the header of the division position information or the header of the division attribute information, but not in the other. For example, if the same division method is used for the position information and the attribute information, the division type (slice_type, tile_type) and index information (slice_idx, tile_idx) are the same for the position information and the attribute information. Therefore, this information may be included in the header of either the position information or the attribute information. For example, if the attribute information depends on the position information, the position information is processed first. Therefore, this information may be included in the header of the position information, but not in the header of the attribute information. In this case, the three-dimensional data decoding device determines, for example, that the dependent attribute information belongs to the same slice or tile as the slice or tile of the dependent position information.

[0230] Furthermore, additional information related to slice division or tile division (slice additional information, position tile additional information, or attribute tile additional information), and dependency information indicating dependency relationships may be stored in an existing parameter set (GPS, APS, position SPS, attribute SPS, etc.) and transmitted. If the division method changes for each frame, information indicating the division method may be stored in a parameter set for each frame (GPS or APS, etc.). If the division method does not change within a sequence, information indicating the division method may be stored in a parameter set for each sequence (position SPS or attribute SPS). Furthermore, if the same division method is used for position information and attribute information, information indicating the division method may be stored in a parameter set of the PCC stream (stream PS).

[0231] The above information may be stored in any one of the above parameter sets, or in multiple parameter sets. Alternatively, a parameter set for tile division or slice division may be defined, and the above information may be stored in the parameter set. Alternatively, the information may be stored in a header of the encoded data.

[0232] Furthermore, the header of the encoded data includes identification information indicating a dependency relationship. That is, when there is a dependency relationship between data, the header includes identification information for referencing the dependency from the dependency source. For example, the header of the dependency data includes identification information for identifying the data. The header of the dependency source data includes identification information indicating the dependency. Note that, when the identification information for identifying data, the additional information related to slice division or tile division, and the identification information indicating the dependency relationship can be identified or derived from other information, these pieces of information may be omitted.

[0233] Next, the flow of the encoding process and decoding process of point cloud data according to this embodiment will be described. Fig. 31 is a flowchart of the encoding process of point cloud data according to this embodiment.

[0234] First, the three-dimensional data encoding device determines the division method to be used (S4911). This division method includes whether or not to perform slice division and whether or not to perform tile division. The division method may also include the number of divisions when performing slice division or tile division, and the type of division. The type of division may be a method based on the object shape as described above, a method based on map information or position information, or a method based on the amount of data or the amount of processing. The division method may be determined in advance.

[0235] If slice division is performed (Yes in S4912), the three-dimensional data encoding device generates a plurality of slice position information and a plurality of slice attribute information by dividing the position information and the attribute information together (S4913). The three-dimensional data encoding device also generates slice additional information related to the slice division. Note that the three-dimensional data encoding device may divide the position information and the attribute information independently.

[0236] If tile division is performed (Yes in S4914), the three-dimensional data encoding device generates multiple pieces of division position information and multiple pieces of division attribute information by independently dividing multiple pieces of slice position information and multiple pieces of slice attribute information (or position information and attribute information) (S4915). The three-dimensional data encoding device also generates position tile additional information and attribute tile additional information related to the tile division. Note that the three-dimensional data encoding device may divide the slice position information and slice attribute information together.

[0237] Next, the three-dimensional data encoding device generates a plurality of pieces of encoding position information and a plurality of pieces of encoding attribute information by encoding each of the plurality of pieces of division position information and the plurality of pieces of division attribute information (S4916). In addition, the three-dimensional data encoding device generates dependency relationship information.

[0238] Next, the three-dimensional data encoding device generates encoded data (encoded stream) by grouping (multiplexing) the plurality of pieces of encoding position information, the plurality of pieces of encoding attribute information, and the additional information into NAL units (S4917).The three-dimensional data encoding device also transmits the generated encoded data.

[0239] 32 is a flowchart of a decoding process of point cloud data according to this embodiment. First, the three-dimensional data decoding device determines the division method by analyzing additional information related to the division method (slice additional information, position tile additional information, and attribute tile additional information) included in the coded data (coded stream) (S4921). This division method includes whether or not to perform slice division and whether or not to perform tile division. The division method may also include the number of divisions when performing slice division or tile division, the type of division, etc.

[0240] Next, the three-dimensional data decoding device generates split position information and split attribute information by decoding the multiple pieces of coded position information and multiple pieces of coded attribute information contained in the coded data using the dependency information contained in the coded data (S4922).

[0241] If the additional information indicates that tile division has been performed (Yes in S4923), the three-dimensional data decoding device generates a plurality of slice position information and a plurality of slice attribute information by combining the plurality of pieces of division position information and the plurality of pieces of division attribute information using respective methods based on the position tile additional information and the attribute tile additional information (S4924). Note that the three-dimensional data decoding device may combine the plurality of pieces of division position information and the plurality of pieces of division attribute information using the same method.

[0242] When the additional information indicates that slice division has been performed (Yes in S4925), the three-dimensional data decoding device generates position information and attribute information by combining, based on the slice additional information, a plurality of pieces of slice position information and a plurality of pieces of slice attribute information (a plurality of pieces of division position information and a plurality of pieces of division attribute information) in the same manner (S4926). Note that the three-dimensional data decoding device may combine, using different methods, a plurality of pieces of slice position information and a plurality of pieces of slice attribute information.

[0243] As described above, the three-dimensional data encoding device according to this embodiment performs the processing shown in Fig. 34. First, the three-dimensional data encoding device divides a target space containing a plurality of three-dimensional points into a plurality of divided data (e.g., tiles) contained in a plurality of divided subspaces (e.g., slices), each containing one or more three-dimensional points (S4932). Here, the divided data is one or more data aggregates contained in a subspace and containing one or more three-dimensional points. The divided data may also be a space, and may include a space that does not contain three-dimensional points. Furthermore, one subspace may contain a plurality of divided data, or one subspace may contain a single divided data. Note that a plurality of subspaces may be set in the target space, or a single subspace may be set in the target space.

[0244] Next, the three-dimensional data encoding device generates a plurality of coded data corresponding to each of the plurality of divided data by encoding each of the plurality of divided data (S4931). The three-dimensional data encoding device generates a bitstream including the plurality of coded data and a plurality of control information (e.g., the header shown in FIG. 30) for each of the plurality of coded data (S4932). Each of the plurality of control information stores a first identifier (e.g., slice_idx) indicating a subspace corresponding to the coded data corresponding to the control information, and a second identifier (e.g., tile_idx) indicating divided data corresponding to the coded data corresponding to the control information.

[0245] This allows a three-dimensional data decoding device that decodes a bitstream generated by a three-dimensional data encoding device to easily restore the target space by combining data from the plurality of divided data using the first identifier and the second identifier, thereby reducing the amount of processing required in the three-dimensional data decoding device.

[0246] For example, the three-dimensional data encoding device encodes position information and attribute information of three-dimensional points included in each of the plurality of pieces of divided data. Each of the plurality of pieces of coded data includes coded data for the position information and coded data for the attribute information. Each of the plurality of pieces of control information includes control information for the coded data for the position information and control information for the coded data for the attribute information. The first identifier and the second identifier are stored in the control information for the coded data for the position information.

[0247] For example, in a bitstream, each of the plurality of pieces of control information is placed before the coded data corresponding to that control information.

[0248] Furthermore, a three-dimensional data encoding device may be configured such that a target space containing a plurality of three-dimensional points is set to one or more subspaces, the subspaces contain one or more divided data each containing one or more three-dimensional points, and the device generates a plurality of coded data corresponding to each of the plurality of divided data by encoding each of the divided data, and generates a bit stream including the plurality of coded data and a plurality of control information for each of the plurality of coded data, and each of the plurality of control information stores a first identifier indicating the subspace corresponding to the coded data corresponding to the control information, and a second identifier indicating the divided data corresponding to the coded data corresponding to the control information.

[0249] For example, the three-dimensional data encoding device includes a processor and a memory, and the processor performs the above-mentioned processing using the memory.

[0250] Moreover, the three-dimensional data decoding device according to this embodiment performs the processing shown in FIG. 34. First, the three-dimensional data decoding device acquires, from a bitstream including a plurality of coded data pieces generated by encoding a plurality of divided data pieces (e.g., tiles) each including one or more three-dimensional points and included in a plurality of subspaces (e.g., slices) obtained by dividing a target space including a plurality of three-dimensional points, and a plurality of control information pieces (e.g., a header shown in FIG. 30) for each of the coded data pieces, a first identifier (e.g., slice_idx) indicating a subspace corresponding to the coded data piece corresponding to the control information piece, and a second identifier (e.g., tile_idx) indicating divided data piece corresponding to the coded data piece corresponding to the control information piece, both of which are stored in the plurality of control information pieces (S4941). Next, the three-dimensional data decoding device restores a plurality of divided data pieces by decoding the plurality of coded data pieces (S4942). Next, the three-dimensional data decoding device restores the target space by combining the plurality of divided data pieces using the first identifier and the second identifier (S4943). For example, the three-dimensional data encoding device uses the second identifier to combine multiple divided data to restore multiple subspaces, and uses the first identifier to combine multiple subspaces to restore the target space (multiple three-dimensional points). Note that the three-dimensional data decoding device may use at least one of the first identifier and the second identifier to obtain coded data of a desired subspace or divided data from the bitstream, and selectively decode or preferentially decode the obtained coded data.

[0251] This allows the three-dimensional data decoding device to easily restore the target space by combining the data of the plurality of divided data using the first identifier and the second identifier, thereby reducing the amount of processing in the three-dimensional data decoding device.

[0252] For example, each of the plurality of coded data is generated by encoding position information and attribute information of a three-dimensional point included in the corresponding divided data, and includes coded data of the position information and coded data of the attribute information. Each of the plurality of control information includes control information for the coded data of the position information and control information for the coded data of the attribute information. The first identifier and the second identifier are stored in the control information of the coded data of the position information.

[0253] For example, in the bitstream, control information precedes the corresponding coded data.

[0254] For example, the three-dimensional data decoding device includes a processor and a memory, and the processor performs the above processing using the memory.

[0255] (Embodiment 5) In position information encoding using neighbor dependency, the higher the density of the point cloud, the more likely it is that encoding efficiency will improve. In this embodiment, the three-dimensional data encoding device combines point cloud data of consecutive frames to collectively encode the point cloud data of consecutive frames. At this time, the three-dimensional data encoding device generates encoded data that includes information for identifying the frame to which each leaf node included in the combined point cloud data belongs.

[0256] Here, the point cloud data of consecutive frames is likely to be similar. Therefore, the upper level of the occupancy code is likely to be the same for consecutive frames. In other words, by encoding consecutive frames together, the upper level of the occupancy code can be shared.

[0257] Furthermore, the frame to which a point group belongs is distinguished at the leaf node by encoding the frame index.

[0258] Fig. 35 is a diagram showing an image of generating a tree structure and an occupancy code from point cloud data of N PCC (Point Cloud Compression) frames. In the figure, points inside the arrows indicate points belonging to each PCC frame. First, a frame index for identifying the frame is assigned to each point belonging to each PCC frame.

[0259] Next, the points belonging to the N frames are converted into a tree structure, and an occupancy code is generated. Specifically, for each point, it is determined which leaf node in the tree structure the point belongs to. In the figure, the tree structure represents a set of nodes. Starting from the top node, it is determined which node the point belongs to. The determination result for each node is encoded as an occupancy code. The occupancy code is common to the N frames.

[0260] A node may contain points from different frames with different frame indices. If the octree resolution is small, points from the same frame with the same frame index may also exist.

[0261] In the lowest level nodes (leaf nodes), points belonging to multiple frames may be mixed (overlapped).

[0262] In the tree structure and occupancy code, the higher level tree structure and occupancy code may be a common component in all frames, while the lower level tree structure and occupancy code may be an individual component for each frame, or a mixture of common and individual components.

[0263] For example, in the lowest level nodes such as leaf nodes, zero or more points with frame indexes are generated, and information indicating the number of points and information on the frame index for each point are generated. This information can also be said to be individual information in a frame.

[0264] Fig. 36 is a diagram showing an example of frame merging. As shown in Fig. 36(a), by combining multiple frames to generate a tree structure, the density of frame points included in the same node increases. Furthermore, by sharing the tree structure, the amount of data for the occupancy code can be reduced. These features may improve the coding rate.

[0265] Furthermore, as shown in FIG. 36(b), the individual components of the occupancy code in the tree structure become denser, which increases the effectiveness of arithmetic coding, and therefore may improve the coding rate.

[0266] The following description will be given using an example of combining multiple PCC frames that are temporally different, but it can also be applied to cases where there are not multiple frames, i.e., when frames are not combined (N=1). Furthermore, the multiple point cloud data to be combined is not limited to multiple frames, i.e., point cloud data of the same object at different times. In other words, the following method can also be applied to combining multiple point cloud data that are spatially or spatiotemporally different. Furthermore, the following method can also be applied to combining point cloud data or point cloud files with different content.

[0267] Fig. 37 is a diagram showing an example of combining multiple PCC frames that are different in time. Fig. 37 shows an example of acquiring point cloud data using a sensor such as LiDAR while a car is moving. The dotted lines indicate the sensor's acquisition range for each frame, i.e., the area of ​​the point cloud data. If the sensor's acquisition range is large, the range of the point cloud data will also be large.

[0268] The method of combining and encoding point cloud data is effective for point cloud data such as the following: For example, in the example shown in Figure 37, a car is moving and frames are identified by scanning 360° around the car. That is, the next frame, Frame 2, corresponds to another 360° scan after the car has moved in the X direction.

[0269] In this case, there is a possibility that frame 1 and frame 2 contain the same point cloud data because there are overlapping areas. Therefore, there is a possibility that encoding efficiency can be improved by combining and encoding frame 1 and frame 2. It is also possible to combine more frames. However, increasing the number of frames to be combined increases the number of bits required to encode the frame index added to the leaf node.

[0270] Furthermore, point cloud data may be acquired by sensors at different positions. Thus, each point cloud data acquired from each position may be used as a frame. That is, the multiple frames may be point cloud data acquired by a single sensor, or may be point cloud data acquired by multiple sensors. Furthermore, some or all of the objects may be the same or different between the multiple frames.

[0271] Next, the flow of three-dimensional data encoding processing according to this embodiment will be described. Fig. 38 is a flowchart of the three-dimensional data encoding processing. The three-dimensional data encoding device reads point cloud data of all N frames based on the number of frames to be combined, N, which is the number of frames to be combined.

[0272] First, the three-dimensional data encoding device determines the number of combined frames N (S5401). For example, this number of combined frames N is specified by the user.

[0273] Next, the three-dimensional data encoding device acquires point cloud data (S5402), and then records the frame index of the acquired point cloud data (S5403).

[0274] If N frames have not been processed (No in S5404), the three-dimensional data encoding device specifies the next point cloud data (S5405) and performs the processes from step S5402 onwards on the specified point cloud data.

[0275] On the other hand, if N frames have already been processed (Yes in S5404), the three-dimensional data encoding device combines the N frames and encodes the combined frame (S5406).

[0276] 39 is a flowchart of the encoding process (S5406). First, the three-dimensional data encoding device generates common information common to N frames (S5411). For example, the common information includes an occupancy code and information indicating the number N of combined frames.

[0277] Next, the three-dimensional data encoding device generates individual information, which is information that is individual for each frame (S5412). For example, the individual information includes the number of points included in the leaf node and the frame index of the points included in the leaf node.

[0278] Next, the three-dimensional data encoding device combines the common information and the individual information and encodes the combined information to generate encoded data (S5413). Next, the three-dimensional data encoding device generates additional information (metadata) related to the frame combination and encodes the generated additional information (S5414).

[0279] Next, the flow of the three-dimensional data decoding process according to this embodiment will be described with reference to Fig. 40, which is a flowchart of the three-dimensional data decoding process.

[0280] First, the three-dimensional data decoding device obtains the number of spliced ​​frames N from the bitstream (S5421). Next, the three-dimensional data encoding device obtains encoded data from the bitstream (S5422). Next, the three-dimensional data decoding device obtains point cloud data and frame indices by decoding the encoded data (S5423). Finally, the three-dimensional data decoding device divides the decoded point cloud data using the frame indices (S5424).

[0281] 41 is a flowchart of the decoding and division processing (S5423 and S5424). First, the three-dimensional data decoding device decodes (obtains) the common information and individual information from the coded data (bit stream) (S5431).

[0282] Next, the 3D data decoding device determines whether to decode a single frame or multiple frames (S5432). For example, whether to decode a single frame or multiple frames may be specified externally. Here, the multiple frames may be all of the combined frames or a portion of the frames. For example, the 3D data decoding device may determine to decode specific frames required by an application and not decode frames that are not required. Alternatively, if real-time decoding is required, the 3D data decoding device may determine to decode a single frame of the combined multiple frames.

[0283] When decoding a single frame (Yes in S5432), the three-dimensional data decoding device extracts individual information corresponding to the specified single frame index from the decoded individual information, and decodes the extracted individual information to restore the point cloud data of the frame corresponding to the specified frame index (S5433).

[0284] On the other hand, when decoding multiple frames (No in S5432), the three-dimensional data decoding device extracts individual information corresponding to the frame indexes of the specified multiple frames (or all frames) and decodes the extracted individual information to restore the point cloud data of the specified multiple frames (S5434). Next, the three-dimensional data decoding device divides the decoded point cloud data (individual information) based on the frame indexes (S5435). In other words, the three-dimensional data decoding device divides the decoded point cloud data into multiple frames.

[0285] The three-dimensional data decoding device may decode the data of all the combined frames at once and divide the decoded data into individual frames, or may decode any part of all the combined frames at once and divide the decoded data into individual frames. Furthermore, the three-dimensional data decoding device may independently decode a predetermined unit frame consisting of multiple frames.

[0286] The configuration of the three-dimensional data encoding device according to this embodiment will be described below. Fig. 42 is a block diagram showing the configuration of an encoding unit 5410 included in the three-dimensional data encoding device according to this embodiment. The encoding unit 5410 generates encoded data (encoded stream) by encoding point group data (point cloud). This encoding unit 5410 includes a division unit 5411, a plurality of position information encoding units 5412, a plurality of attribute information encoding units 5413, an additional information encoding unit 5414, and a multiplexing unit 5415.

[0287] The dividing unit 5411 divides point cloud data of multiple frames to generate multiple pieces of divided data for multiple frames. Specifically, the dividing unit 5411 divides the space of the point cloud data of each frame into multiple subspaces to generate multiple pieces of divided data. Here, a subspace is one of a tile and a slice, or a combination of a tile and a slice. More specifically, the point cloud data includes position information, attribute information (color, reflectance, etc.), and additional information. In addition, a frame number is input to the dividing unit 5411. The dividing unit 5411 divides the position information of each frame into multiple pieces of divided position information and divides the attribute information of each frame into multiple pieces of divided attribute information. In addition, the dividing unit 5411 generates additional information related to the division.

[0288] For example, the dividing unit 5411 first divides the point cloud into tiles, and then further divides the obtained tiles into slices.

[0289] The multiple position information encoding units 5412 encode the multiple pieces of divided position information to generate multiple pieces of encoded position information. For example, the position information encoding unit 5412 encodes the divided position information using an N-ary tree structure such as an octree. Specifically, in an octree, the target space is divided into eight nodes (subspaces), and 8-bit information (occupancy code) indicating whether or not a point cloud is included in each node is generated. Furthermore, the node including the point cloud is further divided into eight nodes, and 8-bit information indicating whether or not the point cloud is included in each of the eight nodes is generated. This process is repeated until the number of point clouds included in a predetermined layer or node falls below a threshold. For example, the multiple position information encoding units 5412 process the multiple pieces of divided position information in parallel.

[0290] The attribute information encoding unit 4632 generates encoded attribute information, which is encoded data, by encoding using the configuration information generated by the position information encoding unit 4631. For example, the attribute information encoding unit 4632 determines a reference point (reference node) to be referenced when encoding a target point (target node) to be processed, based on the octree structure generated by the position information encoding unit 4631. For example, the attribute information encoding unit 4632 references a peripheral node or adjacent node whose parent node in the octree is the same as that of the target node. Note that the method of determining the reference relationship is not limited to this.

[0291] Furthermore, the encoding process of the position information or attribute information may include at least one of a quantization process, a prediction process, and an arithmetic coding process. In this case, the reference means using a reference node to calculate a predicted value of the attribute information, or using the state of the reference node (e.g., occupancy information indicating whether the reference node includes a point group) to determine an encoding parameter. For example, the encoding parameter is a quantization parameter in a quantization process, or a context in an arithmetic coding process.

[0292] The attribute information encoding units 5413 encode the divided attribute information to generate the coded attribute information, for example, the attribute information encoding units 5413 process the divided attribute information in parallel.

[0293] The additional information encoding unit 5414 generates encoded additional information by encoding the additional information included in the point cloud data and the additional information related to the data division generated by the division unit 5411 at the time of division.

[0294] The multiplexing unit 5415 multiplexes a plurality of pieces of encoding position information, a plurality of pieces of encoding attribute information, and a plurality of pieces of encoding additional information for a plurality of frames to generate encoded data (encoded stream), and transmits the generated encoded data. The encoded additional information is also used during decoding.

[0295] 43 is a block diagram of the dividing unit 5411. The dividing unit 5411 includes a tile dividing unit 5421 and a slice dividing unit 5422.

[0296] The tile dividing unit 5421 generates multiple pieces of tile position information by dividing each piece of position information (Position (Geometry)) of multiple frames into tiles. The tile dividing unit 5421 also generates multiple pieces of tile attribute information by dividing each piece of attribute information (Attribute) of multiple frames into tiles. The tile dividing unit 5421 also outputs tile additional information (Tile MetaData) including information related to the tile division and information generated during the tile division.

[0297] The slice division unit 5422 generates a plurality of pieces of division position information (a plurality of pieces of slice position information) by dividing a plurality of pieces of tile position information into slices. The slice division unit 5422 also generates a plurality of pieces of division attribute information (a plurality of pieces of slice attribute information) by dividing a plurality of pieces of tile attribute information into slices. The slice division unit 5422 also outputs slice additional information (Slice MetaData) including information related to the slice division and information generated in the slice division.

[0298] Furthermore, the dividing unit 5411 uses a frame number (frame index) to indicate the origin coordinates, attribute information, and the like in the dividing process.

[0299] 44 is a block diagram of the positional information encoding unit 5412. The positional information encoding unit 5412 includes a frame index generation unit 5431 and an entropy encoding unit 5432.

[0300] The frame index generating unit 5431 determines a frame index value based on the frame number and adds the determined frame index to the position information. The entropy coding unit 5432 generates coded position information by entropy coding the division position information to which the frame index has been added.

[0301] 45 is a block diagram of the attribute information encoding unit 5413. The attribute information encoding unit 5413 includes a frame index generation unit 5441 and an entropy encoding unit 5442.

[0302] The frame index generating unit 5441 determines a frame index value based on the frame number and adds the determined frame index to the attribute information. The entropy encoding unit 5442 generates encoded attribute information by entropy encoding the divided attribute information to which the frame index has been added.

[0303] Next, the flow of the encoding process and decoding process of point cloud data according to this embodiment will be described. Fig. 46 is a flowchart of the encoding process of point cloud data according to this embodiment.

[0304] First, the three-dimensional data encoding device determines the division method to be used (S5441). This division method includes whether to perform division into slices or whether to perform division into tiles. The division method may also include the number of divisions, the type of division, etc., when dividing into slices or tiles.

[0305] If tile division is to be performed (Yes in S5442), the three-dimensional data encoding device generates multiple pieces of tile position information and multiple pieces of tile attribute information by dividing the position information and the attribute information (S5443). The three-dimensional data encoding device also generates tile additional information related to the tile division.

[0306] If slice division is performed (Yes in S5444), the three-dimensional data encoding device divides the plurality of tile position information and the plurality of tile attribute information (or the position information and the attribute information) to generate a plurality of division position information and a plurality of division attribute information (S5445). In addition, the three-dimensional data encoding device generates slice additional information related to the slice division.

[0307] Next, the three-dimensional data encoding device generates a plurality of pieces of encoding position information and a plurality of pieces of encoding attribute information by encoding each of the plurality of pieces of division position information and the plurality of pieces of division attribute information with a frame index (S5446). The three-dimensional data encoding device also generates dependency relationship information.

[0308] Next, the three-dimensional data encoding device generates encoded data (encoded stream) by grouping (multiplexing) the plurality of pieces of encoding position information, the plurality of pieces of encoding attribute information, and the additional information into NAL units (S5447).The three-dimensional data encoding device also transmits the generated encoded data.

[0309] 47 is a flowchart of the encoding process (S5446). First, the three-dimensional data encoding device encodes the division position information (S5451). Next, the three-dimensional data encoding device encodes the frame index for the division position information (S5452).

[0310] If division attribute information exists (Yes in S5453), the three-dimensional data encoding device encodes the division attribute information (S5454) and encodes a frame index for the division attribute information (S5455). On the other hand, if division attribute information does not exist (No in S5453), the three-dimensional data encoding device does not encode the division attribute information or the frame index for the division attribute information. Note that the frame index may be stored in either or both of the division position information and the division attribute information.

[0311] The three-dimensional data encoding device may encode the attribute information using a frame index, or may encode the attribute information without using a frame index. In other words, the three-dimensional data encoding device may use a frame index to identify the frame to which each point belongs and encode the data for each frame, or may encode points belonging to all frames without identifying the frame.

[0312] The configuration of the three-dimensional data decoding device according to this embodiment will be described below. Fig. 48 is a block diagram showing the configuration of a decoding unit 5450. The decoding unit 5450 restores the point cloud data by decoding coded data (coded stream) generated by coding the point cloud data. The decoding unit 5450 includes a demultiplexing unit 5451, a plurality of position information decoding units 5452, a plurality of attribute information decoding units 5453, an additional information decoding unit 5454, and a combining unit 5455.

[0313] The demultiplexing unit 5451 demultiplexes the coded data (coded stream) to generate a plurality of pieces of coding position information, a plurality of pieces of coding attribute information, and coded additional information.

[0314] The position information decoding units 5452 generate a plurality of pieces of divided position information by decoding the plurality of pieces of encoded position information. For example, the position information decoding units 5452 process the plurality of pieces of encoded position information in parallel.

[0315] The attribute information decoding units 5453 generate a plurality of pieces of divided attribute information by decoding the plurality of pieces of encoded attribute information. For example, the attribute information decoding units 5453 process the plurality of pieces of encoded attribute information in parallel.

[0316] The plurality of additional information decoders 5454 generate additional information by decoding the encoded additional information.

[0317] The combining unit 5455 generates position information by combining multiple pieces of divided position information using the additional information. The combining unit 5455 generates attribute information by combining multiple pieces of divided attribute information using the additional information. The combining unit 5455 also divides the position information and attribute information into multiple frames of position information and multiple frames of attribute information using a frame index.

[0318] 49 is a block diagram of the position information decoding unit 5452. The position information decoding unit 5452 includes an entropy decoding unit 5461 and a frame index obtaining unit 5462. The entropy decoding unit 5461 generates division position information by entropy decoding the encoded position information. The frame index obtaining unit 5462 obtains a frame index from the division position information.

[0319] 50 is a block diagram of the attribute information decoding unit 5453. The attribute information decoding unit 5453 includes an entropy decoding unit 5471 and a frame index obtaining unit 5472. The entropy decoding unit 5471 generates divided attribute information by entropy decoding the encoded attribute information. The frame index obtaining unit 5472 obtains a frame index from the divided attribute information.

[0320] 51 is a diagram showing the configuration of the combining unit 5455. The combining unit 5455 generates position information by combining multiple pieces of divided position information. The combining unit 5455 generates attribute information by combining multiple pieces of divided attribute information. The combining unit 5455 also uses a frame index to divide the position information and attribute information into multiple frames of position information and multiple frames of attribute information.

[0321] 52 is a flowchart of a decoding process of point cloud data according to this embodiment. First, the three-dimensional data decoding device determines the division method by analyzing additional information (slice additional information and tile additional information) related to the division method included in the coded data (coded stream) (S5461). This division method includes whether or not to perform slice division and whether or not to perform tile division. The division method may also include the number of divisions when performing slice division or tile division, the type of division, etc.

[0322] Next, the three-dimensional data decoding device generates split position information and split attribute information by decoding the multiple pieces of coded position information and multiple pieces of coded attribute information contained in the coded data using the dependency information contained in the coded data (S5462).

[0323] If the additional information indicates that slice division has been performed (Yes in S5463), the 3D data decoding device generates multiple pieces of tile position information by combining multiple pieces of division position information, and generates multiple pieces of tile attribute information by combining multiple pieces of division attribute information, based on the slice additional information (S5464). Here, the multiple pieces of division position information, the multiple pieces of division attribute information, the multiple pieces of tile position information, and the multiple pieces of tile attribute information each include a frame index.

[0324] If the additional information indicates that tile division has been performed (Yes in S5465), the 3D data decoding device generates position information by combining multiple pieces of tile position information (multiple pieces of division position information) based on the tile additional information, and generates attribute information by combining multiple pieces of tile attribute information (multiple pieces of division attribute information) (S5466). Here, the multiple pieces of tile position information, the multiple pieces of tile attribute information, the position information, and the attribute information include a frame index.

[0325] 53 is a flowchart of the decoding process (S5464 or S5466). First, the three-dimensional data decoding device decodes the division position information (slice position information) (S5471). Next, the three-dimensional data decoding device decodes the frame index for the division position information (S5472).

[0326] If the split attribute information exists (Yes in S5473), the three-dimensional data decoding device decodes the split attribute information (S5474) and decodes the frame index for the split attribute information (S5475). On the other hand, if the split attribute information does not exist (No in S5473), the three-dimensional data decoding device does not decode the split attribute information or the frame index for the split attribute information.

[0327] The three-dimensional data decoding device may decode the attribute information using a frame index, or may decode the attribute information without using a frame index.

[0328] The coding unit for frame splicing will be described below. Figure 54 is a diagram showing an example of a frame splicing pattern. The example in the figure shows a case where, for example, PCC frames are in time series and data generation and encoding are performed in real time.

[0329] 54(a) shows a case where four frames are fixedly joined together, and the three-dimensional data encoding device waits for four frames of data to be generated before generating encoded data.

[0330] 54(b) shows a case where the number of frames changes adaptively. For example, a three-dimensional data encoding device changes the number of combined frames to adjust the amount of encoded data in rate control.

[0331] The three-dimensional data encoding device may not combine frames if there is a possibility that combining frames will not be effective. Also, the three-dimensional data encoding device may switch between combining frames and not combining frames.

[0332] Figure 54(c) shows an example where a portion of the frames to be combined overlaps with a portion of the next frames to be combined. This example is useful when real-time or low-delay processing is required, such as transmitting frames in order of encoding.

[0333] Figure 55 is a diagram showing an example of the structure of a PCC frame. The three-dimensional data encoding device may configure the frames to be combined so that they include at least data units that can be decoded independently. For example, as shown in (a) of Figure 55, if all PCC frames are intra-coded and can be decoded independently, any of the above patterns can be applied.

[0334] Also, as shown in (b) of Figure 55, when inter prediction is applied and a random access unit such as GOF (group of frames) is set, the three-dimensional data encoding device may combine data using the GOF unit as the smallest unit.

[0335] The three-dimensional data encoding device may encode the common information and the individual information together, or may encode each separately. Furthermore, the three-dimensional data encoding device may use a common data structure for the common information and the individual information, or may use different data structures.

[0336] Furthermore, the three-dimensional data encoding device may generate an occupancy code for each frame, and then compare the occupancy codes of multiple frames, determine whether there are many common parts between the occupancy codes of the multiple frames based on a predetermined criterion, and generate common information if there are many common parts. Alternatively, the three-dimensional data encoding device may determine whether to combine frames, which frames to combine, or the number of frames to combine based on whether there are many common parts.

[0337] Next, the structure of the encoded position information will be described. Figure 56 is a diagram showing the structure of the encoded position information. The encoded position information includes a header and a payload.

[0338] 57 is a diagram illustrating an example of the syntax of the header (Geometry_header) of the encoded position information. The header of the encoded position information includes a GPS index (gps_idx), offset information (offset), other information (other_geometry_information), a frame combination flag (combine_frame_flag), and the number of combined frames (number_of_combine_frame).

[0339] The GPS index indicates the identifier (ID) of the parameter set (GPS) corresponding to the coded position information. A GPS is a parameter set for coded position information of one frame or multiple frames. If a parameter set exists for each frame, the identifiers of multiple parameter sets may be indicated in the header.

[0340] The offset information indicates an offset position for acquiring the combined data. The other information indicates other information related to the position information (for example, a quantization parameter difference value (QPdelta)). The frame combining flag indicates whether the encoded data is frame combined. The number of combined frames indicates the number of combined frames.

[0341] Note that some or all of the above information may be described in the SPS or GPS. Note that the SPS is a parameter set for each sequence (multiple frames) and is a parameter set that is used in common for the coded position information and the coded attribute information.

[0342] 58 is a diagram illustrating an example of the syntax of the payload (Geometry_data) of the encoded position information. The payload of the encoded position information includes common information and leaf node information.

[0343] The common information is data combined into one or more frames, and includes an occupancy code (occupancy_Code) and the like.

[0344] The leaf node information (combine_information) is information about each leaf node. The leaf node information may be indicated for each frame as a loop of the frame number.

[0345] As a method for indicating the frame index of a point included in a leaf node, either Method 1 or Method 2 can be used. Fig. 59 is a diagram showing an example of leaf node information in the case of Method 1. The leaf node information shown in Fig. 59 includes the number of three-dimensional points (NumberOfPoints) indicating the number of points included in the node, and a frame index (FrameIndex) for each point.

[0346] FIG. 60 is a diagram showing an example of leaf node information for Method 2. In the example shown in FIG. 60, the leaf node information includes bitmap information (bitmapIsFramePointsFlag) that indicates the frame indexes of multiple points using a bitmap. FIG. 61 is a diagram showing an example of bitmap information. In this example, the bitmap indicates that the leaf node includes 3D points with frame indexes 1, 3, and 5.

[0347] Note that if the quantization resolution is low, there may be duplicate points in the same frame. In this case, the number of 3D points (NumberOfPoints) may be shared, and the number of 3D points in each frame and the total number of 3D points across multiple frames may be indicated.

[0348] Furthermore, when lossy compression is used, the three-dimensional data encoding device may delete duplicated points to reduce the amount of information. The three-dimensional data encoding device may delete duplicated points before combining frames, or may delete duplicated points after combining frames.

[0349] Next, the structure of the encoded attribute information will be described. Fig. 62 shows the structure of the encoded attribute information. The encoded attribute information includes a header and a payload.

[0350] 63 is a diagram illustrating an example of the syntax of the header (Attribute_header) of the encoding attribute information. The header of the encoding attribute information includes an APS index (aps_idx), offset information (offset), other information (other_attribute_information), a frame combination flag (combine_frame_flag), and the number of combined frames (number_of_combine_frame).

[0351] The APS index indicates the identifier (ID) of the parameter set (APS) corresponding to the coding attribute information. An APS is a parameter set of coding attribute information for one frame or multiple frames. If there is a parameter set for each frame, the identifiers of multiple parameter sets may be indicated in the header.

[0352] The offset information indicates an offset position for acquiring the combined data. The other information indicates other information related to the attribute information (for example, a quantization parameter difference value (QPdelta)). The frame combination flag indicates whether the encoded data is frame combined. The number of combined frames indicates the number of combined frames.

[0353] Note that some or all of the above information may be included in the SPS or APS.

[0354] FIG. 64 is a diagram showing an example of the syntax of the payload (Attribute_data) of the encoded attribute information. The payload of the encoded attribute information includes leaf node information (combine_information). For example, the configuration of this leaf node information is the same as that of the leaf node information included in the payload of the encoded position information. In other words, the leaf node information (frame index) may be included in the attribute information.

[0355] Furthermore, the leaf node information (frame index) may be stored in either the encoding position information or the encoding attribute information, but not in the other. In this case, the leaf node information (frame index) stored in either the encoding position information or the encoding attribute information is referenced when the other information is decoded. Furthermore, information indicating the reference destination may be included in the encoding position information or the encoding attribute information.

[0356] Next, an example of the transmission order and decoding order of coded data will be described. Figure 65 is a diagram showing the structure of coded data. Coded data includes a header and a payload.

[0357] 66 to 68 are diagrams showing the data transmission order and the data reference relationship. In the diagrams, G(1) etc. indicate encoding position information, GPS(1) etc. indicate a parameter set for encoding position information, and SPS indicates a parameter set for a sequence (multiple frames). Furthermore, the numbers in parentheses indicate the frame index values. Note that the three-dimensional data encoding device may also transmit data in decoding order.

[0358] Fig. 66 is a diagram showing an example of a transmission order when frames are not combined. Fig. 67 is a diagram showing an example when frames are combined and metadata (parameter set) is added to each PCC frame. Fig. 68 is a diagram showing an example when frames are combined and metadata (parameter set) is added to each combination unit.

[0359] The header of the frame-combined data stores the identifier of the referenced metadata to obtain the metadata for that frame. As shown in Figure 68, metadata for multiple frames may be combined. Parameters that are common to multiple frames may be combined into one. Parameters that are not common to the frames indicate values ​​for each frame.

[0360] The information for each frame (parameters not common to all frames) is, for example, a timestamp indicating the time when the frame data was generated, encoded, or decoded. The information for each frame may also include information about the sensor that acquired the frame data (sensor speed, acceleration, position information, sensor orientation, other sensor information, etc.).

[0361] Figure 69 is a diagram showing an example of decoding some frames in the example shown in Figure 67. As shown in Figure 69, if there is no dependency between frames in the frame-spliced ​​data, the three-dimensional data decoding device can decode each piece of data independently.

[0362] When the point cloud data has attribute information, the three-dimensional data encoding device may frame-combine the attribute information. The attribute information is encoded and decoded with reference to position information. The referenced position information may be the position information before frame-combine, or the position information after frame-combine. The number of frames for combining the position information and the number of frames for combining the attribute information may be the same (the same), or may be independent (different).

[0363] 70 to 73 are diagrams showing the data transmission order and data reference relationships. FIGS. 70 and 71 show examples in which position information and attribute information are combined in four frames. In FIG. 70, metadata (parameter set) is added to each PCC frame. In FIG. 71, metadata (parameter set) is added for each combination unit. In these figures, A(1) etc. indicates coding attribute information, and APS(1) etc. indicates a parameter set of the coding attribute information. Also, the numbers in parentheses indicate frame index values.

[0364] Fig. 72 shows an example in which the position information is combined in four frames, but the attribute information is not combined. As shown in Fig. 72, the position information may be combined in frames, but the attribute information may not be combined in frames.

[0365] Fig. 73 shows an example of combining frame combining and tile division. When tile division is performed as shown in Fig. 73, the header of each tile position information includes information such as a GPS index (gps_idx) and the number of combined frames (number_of_combine_frame). In addition, the header of each tile position information includes a tile index (tile_idx) for identifying the tile.

[0366] As described above, the three-dimensional data encoding device according to this embodiment performs the processing shown in Fig. 74. First, the three-dimensional data encoding device generates third point cloud data by combining the first point cloud data and the second point cloud data (S5481). Next, the three-dimensional data encoding device generates encoded data by encoding the third point cloud data (S5482). Furthermore, the encoded data includes identification information (e.g., a frame index) indicating whether each of the multiple three-dimensional points included in the third point cloud data belongs to the first point cloud data or the second point cloud data.

[0367] According to this, the three-dimensional data encoding device can improve encoding efficiency by encoding a plurality of point group data collectively.

[0368] For example, the first point cloud data and the second point cloud data are point cloud data (e.g., PCC frames) at different times. For example, the first point cloud data and the second point cloud data are point cloud data (e.g., PCC frames) of the same object at different times.

[0369] The encoded data includes position information and attribute information of each of the plurality of three-dimensional points included in the third point cloud data, and the identification information is included in the attribute information.

[0370] For example, the encoded data includes position information (for example, occupancy code) that represents the position of each of a plurality of three-dimensional points included in the third point cloud data using an N-ary tree (N is an integer equal to or greater than 2).

[0371] For example, the three-dimensional data encoding device includes a processor and a memory, and the processor performs the above-mentioned processing using the memory.

[0372] Furthermore, the three-dimensional data decoding device according to this embodiment performs the processing shown in Fig. 75. First, the three-dimensional data decoding device decodes the encoded data to obtain third point cloud data generated by combining the first point cloud data and the second point cloud data, and identification information indicating whether each of the multiple three-dimensional points included in the third point cloud data belongs to the first point cloud data or the second point cloud data (S5491). Next, the three-dimensional data decoding device separates the first point cloud data and the second point cloud data from the third point cloud data using the identification information (S5492).

[0373] According to this, the three-dimensional data decoding device can decode coded data with improved coding efficiency by collectively coding a plurality of point cloud data.

[0374] For example, the first point cloud data and the second point cloud data are point cloud data (e.g., PCC frames) at different times. For example, the first point cloud data and the second point cloud data are point cloud data (e.g., PCC frames) of the same object at different times.

[0375] The encoded data includes position information and attribute information of each of the plurality of three-dimensional points included in the third point cloud data, and the identification information is included in the attribute information.

[0376] For example, the encoded data includes position information (for example, occupancy code) that represents the position of each of a plurality of three-dimensional points included in the third point cloud data using an N-ary tree (N is an integer equal to or greater than 2).

[0377] For example, the three-dimensional data decoding device includes a processor and a memory, and the processor performs the above processing using the memory.

[0378] Although the three-dimensional data encoding device and the three-dimensional data decoding device according to the embodiments of the present disclosure have been described above, the present disclosure is not limited to these embodiments.

[0379] Furthermore, each processing unit included in the three-dimensional data encoding device and three-dimensional data decoding device according to the above embodiments is typically realized as an LSI, which is an integrated circuit. These may be individually implemented as single chips, or some or all of them may be integrated into a single chip.

[0380] Furthermore, the integration is not limited to LSI, but may be realized by dedicated circuits or general-purpose processors. FPGAs (Field Programmable Gate Arrays), which can be programmed after LSI fabrication, or reconfigurable processors, which allow the connections and settings of circuit cells within LSIs to be reconfigured, may also be used.

[0381] In each of the above embodiments, each component may be configured with dedicated hardware, or may be realized by executing a software program suitable for each component. Each component may be realized by a program execution unit such as a CPU or processor reading and executing a software program recorded on a recording medium such as a hard disk or semiconductor memory.

[0382] Furthermore, the present disclosure may be realized as a three-dimensional data encoding method or a three-dimensional data decoding method executed by a three-dimensional data encoding device, a three-dimensional data decoding device, or the like.

[0383] The division of functional blocks in the block diagram is an example, and multiple functional blocks may be realized as a single functional block, one functional block may be divided into multiple blocks, or some functions may be moved to another functional block.Furthermore, the functions of multiple functional blocks having similar functions may be processed in parallel or in time-sharing by a single piece of hardware or software.

[0384] The order in which the steps in the flowchart are executed is merely an example for specifically explaining the present disclosure, and an order other than the above may be used. Also, some of the steps may be executed simultaneously (in parallel) with other steps.

[0385] While the three-dimensional data encoding device and three-dimensional data decoding device according to one or more aspects have been described above based on the embodiments, the present disclosure is not limited to these embodiments. As long as they do not deviate from the spirit of the present disclosure, various modifications conceivable by those skilled in the art to the present embodiments, and configurations constructed by combining components of different embodiments, may also be included within the scope of one or more aspects. [Industrial Applicability]

[0386] The present disclosure is applicable to a three-dimensional data encoding device and a three-dimensional data decoding device. [Explanation of symbols]

[0387] 4601 Three-dimensional data encoding system 4602 Three-dimensional data decoding system 4603 Sensor Terminal 4604 External connection part 4611 Point Cloud Data Generation System 4612 Presentation section 4613 Encoding section 4614 Multiplexer 4615 Input / output section 4616 Control Unit 4617 Sensor information acquisition unit 4618 Point Cloud Data Generation Unit 4621 Sensor Information Acquisition Unit 4622 Input / output section 4623 Demultiplexer 4624 Decoding Unit 4625 Presentation section 4626 User Interface 4627 Control Unit 4630 First Encoding Section 4631 Location information encoder 4632 Attribute information encoder 4633 Additional information coding unit 4634 Multiplexer 4640 First Decoding Unit 4641 Demultiplexer 4642 Location Information Decoding Unit 4643 Attribute Information Decoding Unit 4644 Additional information decoding unit 4650 Second Encoding Section 4651 Additional Information Generation Unit 4652 Position image generation unit 4653 Attribute Image Generation Unit 4654 Video Encoding Unit 4655 Additional information coding unit 4656 Multiplexer 4660 Second Decoding Unit 4661 Demultiplexer 4662 Video Decoding Unit 4663 Additional Information Decoding Unit 4664 Location information generator 4665 Attribute information generation section 4801 Encoding section 4802 Multiplexer 4910 First Encoding Section 4911 Split section 4912 Location information encoder 4913 Attribute information encoder 4914 Additional information coding unit 4915 Multiplexer 4920 First Decoding Unit 4921 Demultiplexer 4922 Location Information Decoding Unit 4923 Attribute Information Decoding Unit 4924 Additional information decoding unit 4925 Joint 4931 Slice division part 4932 Location information tile division part 4933 Attribute information tile division part 4941 Location information tile joint 4942 Attribute information tile combination 4943 Slice Junction 5410 Encoding section 5411 Split section 5412 Location information encoder 5413 Attribute information encoder 5414 Additional information coding unit 5415 Multiplexer 5421 Tile division section 5422 Slice division part 5431, 5441 Frame index generation unit 5432, 5442 Entropy coding unit 5450 Decryption Unit 5451 Demultiplexer 5452 Location Information Decoding Unit 5453 Attribute Information Decoding Unit 5454 Additional information decoding unit 5455 Joint 5461, 5471 Entropy Decoding Unit 5462, 5472 Frame index acquisition section

Claims

1. A three-dimensional data encoding method using an information processing device including a processor and a memory, Using the memory, the processor: When generating an encoded stream by encoding position information and a plurality of attribute information of three-dimensional points included in a first point cloud frame configured with a plurality of first three-dimensional points as encoded position information and encoded attribute information, respectively, generating dependency relationship information indicating a decoding order between the encoding position information and encoded attribute information corresponding to the plurality of attribute information; the coded stream includes the coded position information, coded attribute information corresponding to the plurality of pieces of attribute information, and the dependency information; Three-dimensional data encoding method.

2. The dependency information is used to determine the decoding order. The three-dimensional data encoding method according to claim 1 .

3. The dependency information further includes information that enables the encoded position information and the encoded attribute information to be decoded independently or partially.

2. The three-dimensional data encoding method according to claim 1.

4. The processor further adds a frame index for identifying a frame to either or both of the encoded position information and the encoded attribute information; The dependency information indicates a dependency relationship between the encoding position information or encoding attribute information to which the frame index is added and other encoding position information or encoding attribute information to which the frame index is not added.

2. The three-dimensional data encoding method according to claim 1.

5. each of the encoding position information and the encoding attribute information includes a frame index for identifying a frame; The dependency information indicates a dependency relationship between the encoding position information and the encoding attribute information based on the frame index.

2. The three-dimensional data encoding method according to claim 1.

6. A three-dimensional data decoding method using an information processing device including a processor and a memory, Using the memory, the processor: obtaining, from the coded stream, coding position information, coding attribute information corresponding to a plurality of pieces of attribute information, and dependency relationship information indicating a decoding order; determining a decoding order between the encoding position information and encoded attribute information corresponding to the plurality of attribute information based on the dependency relationship information; obtaining position information of the three-dimensional point by decoding the encoded position information in accordance with the determined decoding order; The encoded attribute information corresponding to the plurality of pieces of attribute information is decoded to obtain the plurality of pieces of attribute information of the three-dimensional point. Three-dimensional data decoding method.

7. The dependency information is used to determine the decoding order. The three-dimensional data decoding method according to claim 6.

8. the dependency information further includes information that enables the encoded position information and the encoded attribute information to be independently or partially decodable, The processor further decodes part or all of the encoded position information and the encoded attribute information independently or partially based on the dependency information. The three-dimensional data decoding method according to claim 6.

9. the coded stream includes coding position information or coding attribute information to which a frame index for identifying a frame is added, and other coding position information or coding attribute information to which the frame index is not added, The processor further obtains a frame index from the encoding position information or the encoding attribute information to which the frame index is added; The processor recognizes, based on the frame index, a dependency relationship between the encoding position information or the encoding attribute information to which the frame index is added and other encoding position information or encoding attribute information to which the frame index is not added, and determines the decoding order. The three-dimensional data decoding method according to claim 6.

10. each of the encoding position information and the encoding attribute information includes a frame index for identifying a frame; The processor recognizes the dependency relationship between the encoding position information and the encoding attribute information based on the frame index and determines the decoding order. The three-dimensional data decoding method according to claim 6.

11. a processor; a memory; The processor uses the memory to: When generating an encoded stream by encoding position information and a plurality of attribute information of three-dimensional points included in a first point cloud frame configured with a plurality of first three-dimensional points as encoded position information and encoded attribute information, respectively, generating dependency relationship information indicating a decoding order between the encoding position information and encoded attribute information corresponding to the plurality of attribute information; the coded stream includes the coded position information, coded attribute information corresponding to the plurality of pieces of attribute information, and the dependency information; Three-dimensional data encoding device.

12. a processor; a memory; The processor uses the memory to: obtaining, from the coded stream, coding position information, coding attribute information corresponding to a plurality of pieces of attribute information, and dependency relationship information indicating a decoding order; determining a decoding order between the encoding position information and encoded attribute information corresponding to the plurality of attribute information based on the dependency relationship information; obtaining position information of the three-dimensional point by decoding the encoded position information in accordance with the determined decoding order; The encoded attribute information corresponding to the plurality of pieces of attribute information is decoded to obtain the plurality of pieces of attribute information of the three-dimensional point. Three-dimensional data decoding device.

Images