Point cloud data transmission device, point cloud data transmission method, point cloud data reception device, and point cloud data reception method

Abstract

A decoding method according to embodiments may comprise the steps of: decoding geometry data of point cloud data within a bitstream; and decoding attribute data of the point cloud data. The decoding method according to embodiments may comprise the steps of: encoding geometry data of point cloud data; and encoding attribute data of the point cloud data.

Description

Point cloud data transmission device, point cloud data transmission method, point cloud data reception device, and point cloud data reception method

[0001] Embodiments relate to a method and apparatus for processing point cloud content.

[0002] Point cloud content is represented as a point cloud, a collection of points within a coordinate system representing three-dimensional space. Point cloud content can represent three-dimensional media and is used to provide various services such as VR (Virtual Reality), AR (Augmented Reality), MR (Mixed Reality), and autonomous driving services. However, representing point cloud content requires tens to hundreds of thousands of point data. Therefore, a method for efficiently processing massive amounts of point data is required.

[0003] Embodiments provide devices and methods for efficiently processing point cloud data. Embodiments provide methods and devices for processing point cloud data to address latency and encoding / decoding complexity.

[0004] However, the scope of the embodiments is not limited to the technical tasks described above, and the scope of the embodiments may be expanded to other technical tasks that can be inferred by a person skilled in the art based on the entire described content.

[0005] A method for transmitting point cloud data according to embodiments may include a step of encoding point cloud data and a step of transmitting a bitstream including the point cloud data. A method for receiving point cloud data according to embodiments may include a step of receiving a bitstream including point cloud data and a step of decoding the point cloud data.

[0006] The device and method according to the embodiments can process point cloud data with high efficiency.

[0007] The device and method according to the embodiments can provide a high quality point cloud service.

[0008] The device and method according to the embodiments can provide point cloud content for providing general services such as VR services and autonomous driving services.

[0009] The drawings are included to further understand the embodiments, and the drawings illustrate the embodiments together with the description related to the embodiments. For a better understanding of the various embodiments described below, reference should be made to the following description of the embodiments in conjunction with the following drawings, in which like reference numerals correspond to corresponding parts throughout the drawings.

[0010] Figure 1 illustrates an example of a point cloud content provision system according to embodiments.

[0011] FIG. 2 is a block diagram illustrating a point cloud content provision operation according to embodiments.

[0012] FIG. 3 illustrates an example of a point cloud encoder according to embodiments.

[0013] Figure 4 illustrates examples of octree and occupancy codes according to embodiments.

[0014] Figure 5 shows an example of a point configuration by LOD according to embodiments.

[0015] Figure 6 shows an example of a point configuration by LOD according to embodiments.

[0016] Fig. 7 illustrates an example of a point cloud decoder according to embodiments.

[0017] Figure 8 is an example of a transmission device according to embodiments.

[0018] Fig. 9 is an example of a receiving device according to embodiments.

[0019] Fig. 10 shows an example of a structure that can be linked with a point cloud data transmission / reception method / device according to embodiments.

[0020] Figure 11 shows sampling of point cloud data according to embodiments.

[0021] Fig. 12 shows an encoder according to embodiments.

[0022] Figure 13 shows encoding of attribute data according to embodiments.

[0023] Fig. 14 shows a decoder according to embodiments.

[0024] Figure 15 illustrates decoding of attribute data according to embodiments.

[0025] Figure 16 illustrates LoD (Level of Detail) generation according to embodiments.

[0026] Figure 17 illustrates subsampling according to embodiments.

[0027] Figure 18 shows a bitstream according to embodiments.

[0028] Figure 19 shows a sequence parameter set (SPS) according to embodiments.

[0029] Figure 20 shows an SPS according to embodiments.

[0030] Figure 21 shows a geometry parameter set (GPS) according to embodiments.

[0031] Figure 22 shows GPS according to embodiments.

[0032] Figure 23 shows an attribute parameter set (APS) according to embodiments.

[0033] Figure 24 shows APS according to embodiments.

[0034] Figure 25 shows a tile parameter set (TPS) according to embodiments.

[0035] Figure 26 shows a TPS according to embodiments.

[0036] Figure 27 shows a geometry data header according to embodiments.

[0037] Figure 28 shows a geometry data header according to embodiments.

[0038] Figure 29 shows an attribute data header according to embodiments.

[0039] Figure 30 shows an attribute data header according to embodiments.

[0040] Figure 31 shows an encoding method according to embodiments.

[0041] Figure 32 shows a decryption method according to embodiments.

[0042] Preferred embodiments of the embodiments are described in detail, examples of which are illustrated in the accompanying drawings. The following detailed description, with reference to the accompanying drawings, is intended to illustrate preferred embodiments of the embodiments, rather than merely show embodiments that can be implemented according to the embodiments. The following detailed description includes details to provide a thorough understanding of the embodiments. However, it will be apparent to those skilled in the art that the embodiments may be practiced without these details.

[0043] While most of the terms used in the examples are commonly used in the field, some terms were arbitrarily selected by the applicant, and their meanings are described in detail in the following descriptions as needed. Therefore, the examples should be understood based on the intended meaning of the terms, not simply their names or meanings.

[0044] Figure 1 illustrates an example of a point cloud content provision system according to embodiments.

[0045] The point cloud content provision system illustrated in FIG. 1 may include a transmission device (10000) and a reception device (10004). The transmission device (10000) and the reception device (10004) are capable of wired and wireless communication to transmit and receive point cloud data.

[0046] A transmission device (10000) according to embodiments can secure, process, and transmit a point cloud video (or point cloud content). According to embodiments, the transmission device (10000) can include a fixed station, a base transceiver system (BTS), a network, an Artificial Intelligence (AI) device and / or system, a robot, an AR / VR / XR device and / or a server, etc. In addition, according to embodiments, the transmission device (10000) can include a device that performs communication with a base station and / or other wireless devices using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)), a robot, a vehicle, an AR / VR / XR device, a portable device, a home appliance, an IoT (Internet of Things) device, an AI device / server, etc.

[0047] A transmission device (10000) according to embodiments includes a point cloud video acquisition unit (Point Cloud Video Acquisition, 10001), a point cloud video encoder (Point Cloud Video Encoder, 10002), and / or a transmitter (or communication module, 10003).

[0048] A point cloud video acquisition unit (10001) according to embodiments acquires a point cloud video through a processing process such as capture, synthesis, or generation. The point cloud video is point cloud content expressed as a point cloud, which is a collection of points located in a three-dimensional space, and may be referred to as point cloud video data, etc. The point cloud video according to embodiments may include one or more frames. One frame represents a still image / picture. Therefore, the point cloud video may include a point cloud image / frame / picture, and may be referred to as any one of a point cloud image, a frame, and a picture.

[0049] A point cloud video encoder (10002) according to embodiments encodes acquired point cloud video data. The point cloud video encoder (10002) may encode point cloud video data based on point cloud compression coding. The point cloud compression coding according to embodiments may include G-PCC (Geometry-based Point Cloud Compression) coding and / or V-PCC (Video-based Point Cloud Compression) coding or next-generation coding. In addition, the point cloud compression coding according to embodiments is not limited to the above-described embodiment. The point cloud video encoder (10002) may output a bitstream including encoded point cloud video data. The bitstream may include not only encoded point cloud video data but also signaling information related to encoding of the point cloud video data.

[0050] A transmitter (10003) according to embodiments transmits a bitstream including encoded point cloud video data. The bitstream according to embodiments is encapsulated into a file or segment (e.g., streaming segment) and transmitted through various networks such as a broadcast network and / or a broadband network. Although not shown in the drawing, the transmission device (10000) may include an encapsulation unit (or an encapsulation module) that performs an encapsulation operation. In addition, the encapsulation unit may be included in the transmitter (10003) according to embodiments. According to embodiments, the file or segment may be transmitted to a receiving device (10004) through a network or may be stored in a digital storage medium (e.g., USB, SD, CD, DVD, Blu-ray, HDD, SSD, etc.). The transmitter (10003) according to embodiments may communicate with the receiving device (10004) (or receiver (10005)) via a network such as 4G, 5G, or 6G via wired / wireless communication. Additionally, the transmitter (10003) can perform data processing operations required according to a network system (e.g., a communication network system such as 4G, 5G, or 6G). Additionally, the transmission device (10000) can transmit encapsulated data in an on-demand manner.

[0051] A receiving device (10004) according to embodiments includes a receiver (Receiver) 10005, a point cloud video decoder (Point Cloud Decoder) 10006, and / or a renderer (Renderer) 10007. According to embodiments, the receiving device (10004) may include a device, robot, vehicle, AR / VR / XR device, mobile device, home appliance, IoT (Internet of Things) device, AI device / server, etc. that performs communication with a base station and / or other wireless devices using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)).

[0052] A receiver (10005) according to embodiments receives a bitstream containing point cloud video data or a file / segment in which the bitstream is encapsulated, from a network or a storage medium. The receiver (10005) may perform data processing operations required according to a network system (e.g., a communication network system such as 4G, 5G, or 6G). The receiver (10005) according to embodiments may decapsulate the received file / segment and output a bitstream. In addition, the receiver (10005) according to embodiments may include a decapsulation unit (or decapsulation module) for performing the decapsulation operation. In addition, the decapsulation unit may be implemented as a separate element (or component) from the receiver (10005).

[0053] A point cloud video decoder (10006) decodes a bitstream containing point cloud video data. The point cloud video decoder (10006) can decode the point cloud video data according to how it is encoded (e.g., the reverse process of the operation of the point cloud video encoder (10002)). Accordingly, the point cloud video decoder (10006) can decode the point cloud video data by performing point cloud decompression coding, which is the reverse process of point cloud compression. The point cloud decompression coding includes G-PCC coding.

[0054] The renderer (10007) renders decoded point cloud video data. The renderer (10007) can output point cloud content by rendering not only point cloud video data but also audio data. According to embodiments, the renderer (10007) may include a display for displaying the point cloud content. According to embodiments, the display may not be included in the renderer (10007) but may be implemented as a separate device or component.

[0055] The dotted arrows in the drawing indicate the transmission path of feedback information acquired from the receiving device (10004). The feedback information is information for reflecting the interaction with the user consuming the point cloud content, and includes information about the user (e.g., head orientation information, viewport information, etc.). In particular, when the point cloud content is content for a service requiring interaction with the user (e.g., autonomous driving service, etc.), the feedback information may be transmitted to the content transmitter (e.g., the transmitting device (10000)) and / or the service provider. Depending on the embodiments, the feedback information may be used by the receiving device (10004) as well as the transmitting device (10000), or may not be provided.

[0056] Head orientation information according to embodiments is information about the position, direction, angle, movement, etc. of the user's head. The receiving device (10004) according to embodiments can calculate viewport information based on the head orientation information. The viewport information is information about the area of ​​the point cloud video that the user is looking at. The viewpoint is the point where the user is looking at the point cloud video, and may mean the exact center point of the viewport area. In other words, the viewport is an area centered on the viewpoint, and the size, shape, etc. of the area can be determined by the FOV (Field Of View). Therefore, the receiving device (10004) can extract viewport information based on the vertical or horizontal FOV supported by the device in addition to the head orientation information. In addition, the receiving device (10004) performs gaze analysis, etc. to check the user's point cloud consumption method, the area of ​​the point cloud video that the user is looking at, the gaze time, etc. According to embodiments, the receiving device (10004) may transmit feedback information including gaze analysis results to the transmitting device (10000). The feedback information according to embodiments may be acquired during a rendering and / or display process. The feedback information according to embodiments may be acquired by one or more sensors included in the receiving device (10004). Additionally, according to embodiments, the feedback information may be acquired by a renderer (10007) or a separate external element (or device, component, etc.). The dotted line in Fig. 1 represents a transmission process of feedback information acquired by the renderer (10007). The point cloud content providing system may process (encode / decode) point cloud data based on the feedback information. Therefore, the point cloud video data decoder (10006) may perform a decoding operation based on the feedback information.Additionally, the receiving device (10004) can transmit feedback information to the transmitting device (10000). The transmitting device (10000) (or point cloud video data encoder (10002)) can perform an encoding operation based on the feedback information. Therefore, the point cloud content providing system can efficiently process necessary data (e.g., point cloud data corresponding to the user's head position) based on the feedback information without processing (encoding / decoding) all point cloud data, and provide point cloud content to the user.

[0057] According to embodiments, the transmitting device (10000) may be referred to as an encoder, a transmitting device, a transmitter, etc., and the receiving device (10004) may be referred to as a decoder, a receiving device, a receiver, etc.

[0058] Point cloud data processed (processed through a series of processes of acquisition / encoding / transmission / decoding / rendering) in the point cloud content providing system of FIG. 1 according to embodiments may be referred to as point cloud content data or point cloud video data. According to embodiments, point cloud content data may be used as a concept including metadata or signaling information related to point cloud data.

[0059] The elements of the point cloud content provision system illustrated in FIG. 1 may be implemented by hardware, software, a processor, and / or a combination thereof.

[0060] FIG. 2 is a block diagram illustrating a point cloud content provision operation according to embodiments.

[0061] The block diagram of Fig. 2 illustrates the operation of the point cloud content provision system described in Fig. 1. As described above, the point cloud content provision system can process point cloud data based on point cloud compression coding (e.g., G-PCC).

[0062] A point cloud content providing system according to embodiments (e.g., a point cloud transmission device (10000) or a point cloud video acquisition unit (10001)) can acquire a point cloud video (20000). The point cloud video is expressed as a point cloud belonging to a coordinate system representing a three-dimensional space. The point cloud video according to embodiments can include a Ply (Polygon File format or the Stanford Triangle format) file. If the point cloud video has one or more frames, the acquired point cloud video can include one or more Ply files. The Ply file includes point cloud data such as the geometry and / or attributes of points. The geometry includes the positions of points. The position of each point can be expressed as parameters (e.g., values ​​of each of the X-axis, Y-axis, and Z-axis) representing a three-dimensional coordinate system (e.g., a coordinate system composed of XYZ axes). Attributes include attributes of points (e.g., texture information of each point, color (YCbCr or RGB), reflectance (r), transparency, etc.). A point has one or more attributes (or properties). For example, a point may have one attribute, color, or two attributes, color and reflectance. According to embodiments, geometry may be referred to as positions, geometry information, geometry data, etc., and attributes may be referred to as attributes, attribute information, attribute data, etc.Additionally, a point cloud content provision system (e.g., a point cloud transmission device (10000) or a point cloud video acquisition unit (10001)) can obtain point cloud data from information related to the acquisition process of a point cloud video (e.g., depth information, color information, etc.).

[0063] A point cloud content providing system according to embodiments (e.g., a transmission device (10000) or a point cloud video encoder (10002)) can encode point cloud data (20001). The point cloud content providing system can encode point cloud data based on point cloud compression coding. As described above, point cloud data can include geometry and attributes of points. Therefore, the point cloud content providing system can perform geometry encoding to encode geometry and output a geometry bitstream. The point cloud content providing system can perform attribute encoding to encode attributes and output an attribute bitstream. According to embodiments, the point cloud content providing system can perform attribute encoding based on geometry encoding. The geometry bitstream and the attribute bitstream according to embodiments can be multiplexed and output as a single bitstream. A bitstream according to embodiments may further include signaling information related to geometry encoding and attribute encoding.

[0064] A point cloud content providing system according to embodiments (e.g., a transmission device (10000) or a transmitter (10003)) can transmit encoded point cloud data (20002). As described in FIG. 1, the encoded point cloud data can be expressed as a geometry bitstream and an attribute bitstream. In addition, the encoded point cloud data can be transmitted in the form of a bitstream together with signaling information related to encoding of the point cloud data (e.g., signaling information related to geometry encoding and attribute encoding). In addition, the point cloud content providing system can encapsulate a bitstream that transmits the encoded point cloud data and transmit it in the form of a file or segment.

[0065] A point cloud content providing system according to embodiments (e.g., a receiving device (10004) or a receiver (10005)) can receive a bitstream including encoded point cloud data. In addition, the point cloud content providing system (e.g., a receiving device (10004) or a receiver (10005)) can demultiplex the bitstream.

[0066] A point cloud content providing system (e.g., a receiving device (10004) or a point cloud video decoder (10005)) can decode encoded point cloud data (e.g., a geometry bitstream, an attribute bitstream) transmitted as a bitstream. The point cloud content providing system (e.g., a receiving device (10004) or a point cloud video decoder (10005)) can decode the point cloud video data based on signaling information related to encoding of the point cloud video data included in the bitstream. The point cloud content providing system (e.g., a receiving device (10004) or a point cloud video decoder (10005)) can decode the geometry bitstream to restore positions (geometry) of points. The point cloud content providing system can decode the attribute bitstream based on the restored geometry to restore attributes of points. A point cloud content provision system (e.g., a receiving device (10004) or a point cloud video decoder (10005)) can reconstruct a point cloud video based on positions and decoded attributes according to the reconstructed geometry.

[0067] A point cloud content providing system (e.g., a receiving device (10004) or a renderer (10007)) according to embodiments can render decoded point cloud data (20004). The point cloud content providing system (e.g., a receiving device (10004) or a renderer (10007)) can render the decoded geometry and attributes through a decoding process according to various rendering methods. Points of the point cloud content may be rendered as vertices having a certain thickness, cubes having a certain minimum size centered on the vertex position, or circles centered on the vertex position. All or a portion of the rendered point cloud content is provided to a user through a display (e.g., a VR / AR display, a general display, etc.).

[0068] A point cloud content provision system according to embodiments (e.g., a receiving device (10004)) can obtain feedback information (20005). The point cloud content provision system can encode and / or decode point cloud data based on the feedback information. The feedback information and the operation of the point cloud content provision system according to embodiments are identical to the feedback information and operation described in FIG. 1, and therefore, a detailed description thereof will be omitted.

[0069] FIG. 3 illustrates an example of a point cloud encoder according to embodiments.

[0070] FIG. 3 illustrates an example of a point cloud video encoder (10002) of FIG. 1. The point cloud encoder reconstructs point cloud data (e.g., positions and / or attributes of points) and performs an encoding operation to adjust the quality of point cloud content (e.g., lossless, lossy, near-lossless) depending on network conditions or applications. If the total size of the point cloud content is large (e.g., point cloud content of 60 Gbps at 30 fps), the point cloud content provision system may not be able to stream the content in real time. Therefore, the point cloud content provision system can reconstruct the point cloud content based on the maximum target bitrate in order to provide it according to the network environment, etc.

[0071] As described in FIGS. 1 and 2, the point cloud encoder can perform geometry encoding and attribute encoding. Geometry encoding is performed before attribute encoding.

[0072] The point cloud encoder according to the embodiments includes a coordinate system transformation unit (Transformation Coordinates, 30000), a quantization unit (Quantize and Remove Points (Voxelize), 30001), an octree analysis unit (Analyze Octree, 30002), a surface approximation analysis unit (Analyze Surface Approximation, 30003), an arithmetic encoder (Arithmetic Encode, 30004), a geometry reconstruction unit (Reconstruct Geometry, 30005), a color transformation unit (Transform Colors, 30006), an attribute transformation unit (Transfer Attributes, 30007), a RAHT transformation unit (30008), a LOD generation unit (Generated LOD, 30009), a lifting transformation unit (Lifting) (30010), and a coefficient quantization unit (Quantize Coefficients, 30011) and / or an arithmetic encoder (30012).

[0073] The coordinate system transformation unit (30000), the quantization unit (30001), the octree analysis unit (30002), the surface approximation analysis unit (30003), the arithmetic encoder (30004), and the geometry reconstruction unit (30005) can perform geometry encoding. The geometry encoding according to the embodiments can include octree geometry coding, direct coding, trisoup geometry encoding, and entropy encoding. Direct coding and trisoup geometry encoding are applied selectively or in combination. In addition, the geometry encoding is not limited to the above examples.

[0074] As illustrated in the drawing, a coordinate system conversion unit (30000) according to embodiments receives positions and converts them into coordinates. For example, the positions may be converted into position information in a three-dimensional space (e.g., a three-dimensional space expressed in an XYZ coordinate system, etc.). The position information in a three-dimensional space according to embodiments may be referred to as geometry information.

[0075] A quantization unit (30001) according to embodiments quantizes geometry. For example, the quantization unit (30001) may quantize points based on the minimum position value of all points (e.g., the minimum value on each axis for the X-axis, Y-axis, and Z-axis). The quantization unit (30001) performs a quantization operation of multiplying the difference between the minimum position value and the position value of each point by a preset quantization scale value, and then rounding down or up to find the closest integer value. Accordingly, one or more points may have the same quantized position (or position value). The quantization unit (30001) according to embodiments performs voxelization based on the quantized positions to reconstruct the quantized points. The minimum unit containing two-dimensional image / video information is a pixel, and points of point cloud content (or three-dimensional point cloud video) according to embodiments may be included in one or more voxels. A voxel is a combination of a volume and a pixel, and refers to a three-dimensional cubic space generated when a three-dimensional space is divided into units (unit=1.0) based on axes representing the three-dimensional space (e.g., X-axis, Y-axis, Z-axis). The quantization unit (40001) may match groups of points in the three-dimensional space to voxels. According to embodiments, one voxel may include only one point. According to embodiments, one voxel may include one or more points. In addition, in order to express one voxel as one point, the position of the center of the voxel may be set based on the positions of one or more points included in one voxel. In this case, the attributes of all positions contained in one voxel can be combined and assigned to the voxel.

[0076] The octree analysis unit (30002) according to the embodiments performs octree geometry coding (or octree coding) to represent voxels in an octree structure. The octree structure represents points matched to voxels based on an octree structure.

[0077] The surface approximation analysis unit (30003) according to the embodiments can analyze and approximate an octree. The octree analysis and approximation according to the embodiments is a process of analyzing and voxelizing an area including a large number of points to efficiently provide an octree and voxelization.

[0078] An arithmetic encoder (30004) according to embodiments entropy encodes an octree and / or an approximated octree. For example, the encoding method includes an arithmetic encoding method. The encoding results in a geometry bitstream.

[0079] The color conversion unit (30006), the attribute conversion unit (30007), the RAHT conversion unit (30008), the LOD generation unit (30009), the lifting conversion unit (30010), the coefficient quantization unit (30011) and / or the arithmetic encoder (30012) perform attribute encoding. As described above, one point may have one or more attributes. Attribute encoding according to embodiments is applied equally to the attributes of one point. However, when one attribute (e.g., color) includes one or more elements, independent attribute encoding is applied to each element. Attribute encoding according to embodiments may include color transform coding, attribute transform coding, RAHT (Region Adaptive Hierarchial Transform) coding, Interpolarization-based hierarchical nearest-neighbor prediction-Prediction Transform) coding, and lifting transform (interpolation-based hierarchical nearest-neighbor prediction with an update / lifting step (Lifting Transform)) coding. Depending on the point cloud content, the above-described RAHT coding, prediction transform coding, and lifting transform coding may be selectively used, or a combination of one or more codings may be used. In addition, attribute encoding according to embodiments is not limited to the above-described examples.

[0080] The color conversion unit (30006) according to the embodiments performs color conversion coding to convert color values ​​(or textures) included in attributes. For example, the color conversion unit (30006) may convert the format of color information (e.g., convert from RGB to YCbCr). The operation of the color conversion unit (30006) according to the embodiments may be optionally applied depending on the color values ​​included in the attributes.

[0081] The geometry reconstruction unit (30005) according to the embodiments reconstructs (decompresses) an octree and / or an approximated octree. The geometry reconstruction unit (30005) reconstructs an octree / voxel based on the results of analyzing the distribution of points. The reconstructed octree / voxel may be referred to as a reconstructed geometry (or restored geometry).

[0082] The attribute conversion unit (30007) according to the embodiments performs attribute conversion that converts attributes based on positions for which geometry encoding has not been performed and / or reconstructed geometry. As described above, since the attributes are dependent on the geometry, the attribute conversion unit (30007) can convert the attributes based on the reconstructed geometry information. For example, the attribute conversion unit (30007) can convert the attribute of a point at a position based on the position value of the point included in the voxel. As described above, when the position of the center point of a voxel is set based on the positions of one or more points included in the voxel, the attribute conversion unit (30007) converts the attributes of one or more points. When try-soup geometry encoding is performed, the attribute conversion unit (30007) can convert attributes based on the try-soup geometry encoding.

[0083] The attribute transformation unit (30007) can perform attribute transformation by calculating the average value of the attributes or attribute values ​​(e.g., the color or reflectance of each point) of neighboring points within a specific position / radius from the position (or position value) of the center point of each voxel. The attribute transformation unit (30007) can apply a weight according to the distance from the center point to each point when calculating the average value. Accordingly, each voxel has a position and a calculated attribute (or attribute value).

[0084] The attribute transformation unit (30007) can search for neighboring points within a specific position / radius from the position of the center point of each voxel based on the KD tree or the Moulton code. The KD tree is a binary search tree that supports a data structure that can manage points based on their positions to enable fast nearest neighbor search (NNS). The Moulton code represents the coordinate values ​​(e.g. (x, y, z)) indicating the 3D positions of all points as bit values ​​and is generated by mixing the bits. For example, if the coordinate values ​​indicating the position of a point are (5, 9, 1), the bit values ​​of the coordinate values ​​are (0101, 1001, 0001). If the bit values ​​are mixed in the order of z, y, and x according to the bit index, it is 010001000111. If this value is expressed in decimal, it becomes 1095. That is, the Moulton code value of the point with coordinate values ​​(5, 9, 1) is 1095. The attribute transformation unit (30007) can sort points based on the Moulton code value and perform nearest neighbor search (NNS) through a depth-first traversal process. After the attribute transformation operation, if nearest neighbor search (NNS) is also required in other transformation processes for attribute coding, a KD tree or Moulton code is utilized.

[0085] As shown in the drawing, the converted attributes are input to the RAHT conversion unit (30008) and / or the LOD generation unit (30009).

[0086] The RAHT transform unit (30008) according to the embodiments performs RAHT coding to predict attribute information based on reconstructed geometry information. For example, the RAHT transform unit (30008) can predict attribute information of a node at an upper level of an octree based on attribute information associated with a node at a lower level of the octree.

[0087] The LOD generation unit (30009) according to the embodiments generates a LOD (Level of Detail) to perform predictive transformation coding. The LOD according to the embodiments represents the level of detail of point cloud content. A smaller LOD value indicates lower detail of point cloud content, and a larger LOD value indicates higher detail of point cloud content. Points can be classified according to LOD.

[0088] The lifting transformation unit (30010) according to the embodiments performs lifting transformation coding that transforms attributes of a point cloud based on weights. As described above, lifting transformation coding may be applied selectively.

[0089] The coefficient quantization unit (30011) according to the embodiments quantizes attribute-coded attributes based on coefficients.

[0090] An arithmetic encoder (30012) according to embodiments encodes quantized attributes based on arithmetic coding.

[0091] The elements of the point cloud encoder of FIG. 3 may be implemented by hardware, software, firmware, or a combination thereof, including one or more processors or integrated circuits configured to communicate with one or more memories included in the point cloud providing device, although not shown in the drawing. The one or more processors may perform at least one or more of the operations and / or functions of the elements of the point cloud encoder of FIG. 3 described above. Furthermore, the one or more processors may operate or execute a set of software programs and / or instructions for performing the operations and / or functions of the elements of the point cloud encoder of FIG. 3. The one or more memories according to embodiments may include high-speed random access memory, or may include non-volatile memory (e.g., one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices).

[0092] Figure 4 illustrates examples of octree and occupancy codes according to embodiments.

[0093] As described in FIGS. 1 to 3, the point cloud content provision system (point cloud video encoder (10002)) or point cloud encoder (e.g., octree analysis unit (30002)) performs octree geometry coding (or octree coding) based on an octree structure to efficiently manage the area and / or position of a voxel.

[0094] The top of Fig. 4 shows the octree structure. The three-dimensional space of the point cloud content according to the embodiments is expressed by the axes of the coordinate system (e.g., X-axis, Y-axis, Z-axis). The octree structure has two poles (0,0,0) and (2 d , 2 d , 2 d ) is generated by recursively subdividing the cubical axis-aligned bounding box defined by . 2d can be set to a value that constitutes the smallest bounding box that encloses all points of the point cloud content (or point cloud video). d represents the depth of the octree. The value of d is determined by the following equation. In the equation below, (x int n , y int n , z int n ) represents the positions (or position values) of quantized points.

[0095] d =Ceil(Log2(Max(x_n^int,y_n^int,z_n^int,n=1,…,N)+1))

[0096] As shown in the middle of the upper part of Fig. 4, the entire three-dimensional space can be divided into eight spaces according to the division. Each divided space is expressed as a cube with six faces. As shown in the upper right of Fig. 4, each of the eight spaces is again divided based on the axes of the coordinate system (e.g., X-axis, Y-axis, Z-axis). Therefore, each space is again divided into eight smaller spaces. The divided smaller spaces are also expressed as cubes with six faces. This division method is applied until the leaf nodes of the octree become voxels.

[0097] The bottom of Fig. 4 shows the occupancy code of the octree. The occupancy code of the octree is generated to indicate whether each of the eight partitioned spaces generated by partitioning one space contains at least one point. Therefore, one occupancy code is expressed by eight child nodes. Each child node represents the occupancy of the partitioned space, and each child node has a value of 1 bit. Therefore, the occupancy code is expressed as an 8-bit code. That is, if the space corresponding to the child node contains at least one point, the node has a value of 1. If the space corresponding to the child node does not contain a point (empty), the node has a value of 0. Since the occupancy code illustrated in Fig. 4 is 00100001, it indicates that the spaces corresponding to the third and eighth child nodes among the eight child nodes each contain at least one point. As shown in the drawing, the third child node and the eighth child node each have eight child nodes, and each child node is expressed by an 8-bit occupancy code. The drawing shows that the occupancy code of the third child node is 10000111, and the occupancy code of the eighth child node is 01001111. A point cloud encoder according to embodiments (e.g., an arithmetic encoder (30004)) can entropy encode the occupancy code. In addition, the point cloud encoder can intra / inter code the occupancy code to increase compression efficiency. A receiving device according to embodiments (e.g., a receiving device (10004) or a point cloud video decoder (10006)) reconstructs an octree based on the occupancy code.

[0098] A point cloud encoder according to embodiments (e.g., the point cloud encoder of FIG. 3, or the octree analysis unit (30002)) can perform voxelization and octree coding to store the positions of points. However, points within a 3D space are not always evenly distributed, and thus, there may be specific areas where there are not many points. Therefore, performing voxelization on the entire 3D space is inefficient. For example, if there are few points in a specific area, there is no need to perform voxelization up to that area.

[0099] Therefore, the point cloud encoder according to the embodiments can perform direct coding that directly codes the positions of points included in the specific region (or nodes excluding leaf nodes of the octree) without performing voxelization for the specific region described above. The coordinates of the direct coded points according to the embodiments are referred to as a direct coding mode (DCM). In addition, the point cloud encoder according to the embodiments can perform trisoup geometry encoding that reconstructs the positions of points within the specific region (or node) on a voxel basis based on a surface model. Trisoup geometry encoding is a geometry encoding that expresses the representation of an object as a series of triangle meshes. Therefore, the point cloud decoder can generate a point cloud from the mesh surface. Direct coding and trisoup geometry encoding according to the embodiments can be selectively performed. Additionally, direct coding and tri-subtractive geometry encoding according to embodiments may be performed in combination with octree geometry coding (or octree coding).

[0100] In order to perform direct coding, the option to use direct mode for applying direct coding must be activated, the node to which direct coding is to be applied must not be a leaf node, and there must be points below a threshold within a specific node. In addition, the total number of points subject to direct coding must not exceed a preset threshold. If the above conditions are satisfied, the point cloud encoder (or arithmetic encoder (30004)) according to the embodiments can entropy code the positions (or position values) of the points.

[0101] A point cloud encoder according to embodiments (e.g., surface approximation analysis unit (30003)) can determine a specific level of an octree (when the level is smaller than the depth d of the octree) and, starting from that level, perform tri-subject geometry encoding to reconstruct the positions of points within a node region on a voxel basis using a surface model (tri-subject mode). A point cloud encoder according to embodiments can specify a level to which tri-subject geometry encoding is to be applied. For example, when the specified level is equal to the depth of the octree, the point cloud encoder does not operate in tri-subject mode. That is, a point cloud encoder according to embodiments can operate in tri-subject mode only when the specified level is smaller than the depth value of the octree. A three-dimensional cubic area of ​​nodes at a specified level according to embodiments is called a block. One block may include one or more voxels. A block or a voxel may correspond to a brick. Within each block, geometry is represented by a surface. According to embodiments, a surface may intersect each edge of the block at most once.

[0102] Since one block has 12 edges, there are at least 12 intersections within one block. Each intersection is called a vertex. A vertex existing along an edge is detected if there is at least one occupied voxel adjacent to the edge among all blocks sharing the edge. An occupied voxel according to embodiments means a voxel containing a point. The position of a vertex detected along an edge is the average position along the edge of all voxels adjacent to the edge among all blocks sharing the edge.

[0103] When a vertex is detected, the point cloud encoder according to the embodiments can entropy code the starting point (x, y, z) of the edge, the direction vector (Δx, Δy, Δz) of the edge, and the vertex position value (relative position value within the edge). When the tri-substructure geometry encoding is applied, the point cloud encoder according to the embodiments (e.g., the geometry reconstruction unit (30005)) can perform triangle reconstruction, up-sampling, and voxelization processes to generate restored geometry (reconstructed geometry).

[0104] The vertices located at the edge of a block determine the surface passing through the block. According to the embodiments, the surface is a non-planar polygon. The triangle reconstruction process reconstructs the surface represented by a triangle based on the starting point of the edge, the direction vector of the edge, and the position value of the vertex. The triangle reconstruction process is as follows. ① Calculate the centroid value of each vertex, ② Subtract the centroid value from each vertex value, and ③ Square the values, and then add up all the values ​​to obtain the value.

[0105]

[0106] The minimum of the added values ​​is found, and the projection process is performed according to the axis with the minimum value. For example, if the x element is minimum, each vertex is projected to the x-axis based on the center of the block, and then projected onto the (y, z) plane. If the value output when projected onto the (y, z) plane is (ai, bi), the θ value is found through atan2(bi, ai), and the vertices are sorted based on the θ value. The table below shows the combination of vertices to create a triangle depending on the number of vertices. The vertices are sorted in order from 1 to n. The table below shows that two triangles can be formed depending on the combination of vertices for four vertices. The first triangle can be formed by the 1st, 2nd, and 3rd vertices among the sorted vertices, and the second triangle can be formed by the 3rd, 4th, and 1st vertices among the sorted vertices.

[0107] Table 2-1. Triangles formed from vertices ordered 1,… ,n

[0108] n triangles

[0109] 3 (1,2,3)

[0110] 4 (1,2,3), (3,4,1)

[0111] 5 (1,2,3), (3,4,5), (5,1,3)

[0112] 6 (1,2,3), (3,4,5), (5,6,1), (1,3,5)

[0113] 7 (1,2,3), (3,4,5), (5,6,7), (7,1,3), (3,5,7)

[0114] 8 (1,2,3), (3,4,5), (5,6,7), (7,8,1), (1,3,5), (5,7,1)

[0115] 9 (1,2,3), (3,4,5), (5,6,7), (7,8,9), (9,1,3), (3,5,7), (7,9,3)

[0116] 10 (1,2,3), (3,4,5), (5,6,7), (7,8,9), (9,10,1), (1,3,5), (5,7,9), (9,1,5)

[0117] 11 (1,2,3), (3,4,5), (5,6,7), (7,8,9), (9,10,11), (11,1,3), (3,5,7), (7,9,11), (11,3,7)

[0118] 12 (1,2,3), (3,4,5), (5,6,7), (7,8,9), (9,10,11), (11,12,1), (1,3,5), (5,7,9), (9,11,1), (1,5,9)

[0119] The upsampling process is performed to voxelize the triangle by adding points in the middle along the edges. Additional points are generated based on the upsampling factor and the width of the block. The additional points are called refined vertices. A point cloud encoder according to embodiments can voxelize the refined vertices. The point cloud encoder can also perform attribute encoding based on the voxelized positions (or position values).

[0120] Figure 5 shows an example of a point configuration by LOD according to embodiments.

[0121] As described in FIGS. 1 to 4, the encoded geometry is reconstructed (decompressed) before attribute encoding is performed. When direct coding is applied, the geometry reconstruction operation may include changing the arrangement of direct-coded points (e.g., placing the direct-coded points at the front of the point cloud data). When trysoup geometry encoding is applied, the geometry reconstruction process includes triangle reconstruction, upsampling, and voxelization. Since attributes depend on the geometry, attribute encoding is performed based on the reconstructed geometry.

[0122] A point cloud encoder (e.g., LOD generation unit (30009)) can reorganize points by LOD. The drawing shows point cloud content corresponding to LOD. The left side of the drawing shows the original point cloud content. The second figure from the left in the drawing shows the distribution of points of the lowest LOD, and the rightmost figure in the drawing shows the distribution of points of the highest LOD. That is, points of the lowest LOD are sparsely distributed, and points of the highest LOD are densely distributed. That is, as LOD increases in the direction of the arrow indicated at the bottom of the drawing, the interval (or distance) between points becomes shorter.

[0123] Figure 6 shows an example of a point configuration by LOD according to embodiments.

[0124] As described in FIGS. 1 to 5, a point cloud content providing system, or a point cloud encoder (e.g., a point cloud video encoder (10002), the point cloud encoder of FIG. 3, or a LOD generation unit (30009)) can generate a LOD. The LOD is generated by reorganizing points into a set of refinement levels according to a set LOD distance value (or a set of Euclidean distances). The LOD generation process is performed not only in the point cloud encoder but also in the point cloud decoder.

[0125] The upper part of Fig. 6 shows examples of points (P0 to P9) of point cloud content distributed in 3D space. The original order in Fig. 6 represents the order of points P0 to P9 before LOD generation. The LOD-based order in Fig. 6 represents the order of points according to LOD generation. The points are rearranged by LOD. Additionally, a higher LOD includes points belonging to a lower LOD. As shown in Fig. 6, LOD0 includes P0, P5, P4, and P2. LOD1 includes points of LOD0 and P1, P6, and P3. LOD2 includes points of LOD0, points of LOD1, and P9, P8, and P7.

[0126] As described in FIG. 3, the point cloud encoder according to the embodiments can selectively or in combination perform predictive transform coding, lifting transform coding, and RAHT transform coding.

[0127] A point cloud encoder according to embodiments can perform predictive transformation coding to generate a predictor for points and set a predicted attribute (or predicted attribute value) for each point. That is, N predictors can be generated for N points. The predictor according to embodiments can calculate a weight (= 1 / distance) value based on the LOD value of each point, indexing information for neighboring points existing within a distance set for each LOD, and distance values ​​to the neighboring points.

[0128] According to the embodiments, the predicted attribute (or attribute value) is set as the average value of the product of the attributes (or attribute values, for example, color, reflectance, etc.) of neighboring points set in the predictor of each point and the weight (or weight value) calculated based on the distance to each neighboring point. The point cloud encoder according to the embodiments (for example, the coefficient quantization unit (30011)) can quantize and inverse quantize the residual values ​​(which may be referred to as residual attributes, residual attribute values, attribute prediction residual values, etc.) obtained by subtracting the predicted attribute (attribute value) from the attribute (attribute value) of each point. The quantization process is as shown in the following table.

[0129] graph. Attribute prediction residuals quantization pseudo code

[0130] int PCCQuantization(int value, int quantStep) {

[0131] if( value >=0) {

[0132] return floor(value / quantStep + 1.0 / 3.0);

[0133] } else {

[0134] return -floor(-value / quantStep + 1.0 / 3.0);

[0135] }

[0136] }

[0137] graph. Attribute prediction residuals inverse quantization pseudo code

[0138] int PCCInverseQuantization(int value, int quantStep) {

[0139] if( quantStep ==0) {

[0140] return value;

[0141] } else {

[0142] return value * quantStep;

[0143] }

[0144] }

[0145] A point cloud encoder according to embodiments (e.g., an arithmetic encoder (30012)) can entropy code the quantized and dequantized residuals as described above when there are neighboring points to the predictor of each point. A point cloud encoder according to embodiments (e.g., an arithmetic encoder (30012)) can entropy code the attributes of the point without performing the above-described process when there are no neighboring points to the predictor of each point.

[0146] A point cloud encoder according to embodiments (e.g., lifting transformation unit (30010)) can perform lifting transformation coding by generating a predictor for each point, setting the LOD calculated in the predictor, registering neighboring points, and setting weights according to the distance to the neighboring points. Lifting transformation coding according to embodiments is similar to the above-described predictive transformation coding, but differs in that weights are cumulatively applied to attribute values. The process of cumulatively applying weights to attribute values ​​according to embodiments is as follows.

[0147] 1) Create an array QW (QuantizationWieght) that stores the weight values ​​of each point. The initial value of all elements in QW is 1.0. Add the value obtained by multiplying the weight of the current point's predictor by the QW value of the predictor index of the neighboring node registered in the predictor.

[0148] 2) Lift prediction process: To calculate the predicted attribute value, the weighted value of the point's attribute value is multiplied and subtracted from the existing attribute value.

[0149] 3) Create temporary arrays called updateweight and update and initialize them to 0.

[0150] 4) For each predictor, the calculated weights are multiplied by the weights stored in the QW corresponding to the predictor index, and the resulting weights are cumulatively added to the update weight array as the index of the neighboring node. The update array accumulates the values ​​obtained by multiplying the calculated weights by the attribute values ​​of the indexes of the neighboring nodes.

[0151] 5) Lift update process: For each predictor, the attribute values ​​in the update array are divided by the weight values ​​in the update weight array of the predictor index, and the existing attribute values ​​are added to the divided value.

[0152] 6) For all predictors, the predicted attribute values ​​are calculated by additionally multiplying the updated attribute values ​​through the lift update process by the weights (stored in QW) updated through the lift prediction process. The point cloud encoder according to the embodiments (e.g., coefficient quantization unit (30011)) quantizes the predicted attribute values. In addition, the point cloud encoder (e.g., arithmetic encoder (30012)) entropy-codes the quantized attribute values.

[0153] A point cloud encoder according to embodiments (e.g., RAHT transform unit (30008)) can perform RAHT transform coding that predicts attributes of upper-level nodes using attributes associated with nodes at lower levels of an octree. RAHT transform coding is an example of attribute intra coding through octree backward scan. A point cloud encoder according to embodiments scans from a voxel to the entire area, and repeats the merging process up to a root node while merging voxels into larger blocks at each step. The merging process according to embodiments is performed only for occupied nodes. The merging process is not performed for empty nodes, and the merging process is performed for the node immediately above the empty node.

[0154] The following equation represents the RAHT transformation matrix. g l x, y, z represents the average attribute value of voxels at level l. g l x, y, z can be calculated from gl+1 2x, y, z and gl+1 2x+1, y, z. The weights of gl 2x, y, z and gl 2x+1, y, z are w1=wl 2x, y, z and w2=wl 2x+1, y, z.

[0155]

[0156]

[0157] *gl-1 x, y, z are low-pass values, which are used in the merging process at the next higher level. hl-1 x, y, z are high-pass coefficients, and the high-pass coefficients at each step are quantized and entropy coded (e.g., encoding of an arithmetic encoder (400012)). The weights are calculated as wl-1 x, y, z=wl 2x, y, z+wl 2x+1, y, z. The root node is the last g 1 0, 0, 0 and g 1 0, 0, 1 It is generated as follows:

[0158]

[0159] The gDC values ​​are also quantized and entropy coded, like the high-pass coefficients.

[0160] Fig. 7 illustrates an example of a point cloud decoder according to embodiments.

[0161] The point cloud decoder illustrated in FIG. 7 is an example of a point cloud decoder and can perform a decoding operation, which is the reverse process of the encoding operation of the point cloud encoder described in FIGS. 1 to 6.

[0162] As described in Figure 1, the point cloud decoder can perform geometry decoding and attribute decoding. Geometry decoding is performed before attribute decoding.

[0163] A point cloud decoder according to embodiments includes an arithmetic decoder (7000), an octree synthesizer (7001), a surface approximation synthesizer (7002), a geometry reconstructor (7003), an inverse transform coordinates (7004), an arithmetic decoder (7005), an inverse quantize (7006), a RAHT transform (7007), a LOD generator (7008), an inverse lifting (7009), and / or an inverse transform colors (7010).

[0164] The arithmetic decoder (7000), the octree synthesis unit (7001), the surface oproximation synthesis unit (7002), the geometry reconstruction unit (7003), and the coordinate system inversion unit (7004) can perform geometry decoding. Geometry decoding according to embodiments can include direct coding and trisoup geometry decoding. Direct coding and trisoup geometry decoding are applied selectively. In addition, geometry decoding is not limited to the above examples, and is performed by the reverse process of the geometry encoding described in FIGS. 1 to 6.

[0165] An arithmetic decoder (7000) according to embodiments decodes a received geometry bitstream based on arithmetic coding. The operation of the arithmetic decoder (7000) corresponds to the reverse process of the arithmetic encoder (30004).

[0166] The octree synthesis unit (7001) according to the embodiments can generate an octree by obtaining an occupancy code from a decoded geometry bitstream (or information about the geometry obtained as a result of decoding). A specific description of the occupancy code is as described in FIGS. 1 to 6.

[0167] The surface off-axis synthesis unit (7002) according to the embodiments can synthesize a surface based on the decoded geometry and / or the generated octree when the tri-sub geometry encoding is applied.

[0168] The geometry reconstruction unit (7003) according to the embodiments can regenerate geometry based on the surface and / or decoded geometry. As described in FIGS. 1 to 6, direct coding and try-soup geometry encoding are selectively applied. Therefore, the geometry reconstruction unit (7003) directly retrieves and adds position information of points to which direct coding is applied. In addition, when try-soup geometry encoding is applied, the geometry reconstruction unit (7003) can restore geometry by performing a reconstruction operation of the geometry reconstruction unit (30005), such as triangle reconstruction, up-sampling, and voxelization operations. The specific details are the same as described in FIG. 4 and are therefore omitted. The restored geometry may include a point cloud picture or frame that does not include attributes.

[0169] The coordinate system inverse transformation unit (7004) according to the embodiments can obtain the positions of points by transforming the coordinate system based on the restored geometry.

[0170] The arithmetic decoder (7005), the inverse quantization unit (7006), the RAHT transform unit (7007), the LOD generation unit (7008), the inverse lifting unit (7009), and / or the color inverse transform unit (7010) can perform the attribute decoding described in FIG. 10. The attribute decoding according to embodiments can include RAHT (Region Adaptive Hierarchial Transform) decoding, Interpolaration-based hierarchical nearest-neighbor prediction-Prediction Transform) decoding, and lifting transform (interpolation-based hierarchical nearest-neighbor prediction with an update / lifting step (Lifting Transform)) decoding. The three decodings described above can be used selectively, or a combination of one or more decodings can be used. Additionally, attribute decoding according to embodiments is not limited to the examples described above.

[0171] An arithmetic decoder (7005) according to embodiments decodes an attribute bitstream using arithmetic coding.

[0172] The inverse quantization unit (7006) according to the embodiments inverse quantizes information about the decoded attribute bitstream or the attributes obtained as a result of the decoding and outputs the inverse quantized attributes (or attribute values). The inverse quantization may be selectively applied based on the attribute encoding of the point cloud encoder.

[0173] According to embodiments, the RAHT transform unit (7007), the LOD generator (7008), and / or the inverse lifting unit (7009) may process the reconstructed geometry and the inverse quantized attributes. As described above, the RAHT transform unit (7007), the LOD generator (7008), and / or the inverse lifting unit (7009) may selectively perform a corresponding decoding operation according to the encoding of the point cloud encoder.

[0174] The color inverse transform unit (7010) according to the embodiments performs inverse transform coding to inversely transform the color values ​​(or textures) included in the decoded attributes. The operation of the color inverse transform unit (7010) may be selectively performed based on the operation of the color transform unit (30006) of the point cloud encoder.

[0175] The elements of the point cloud decoder of FIG. 7 may be implemented by hardware, software, firmware, or a combination thereof, including one or more processors or integrated circuits configured to communicate with one or more memories included in a point cloud providing device, although not shown in the drawing. The one or more processors may perform at least one or more of the operations and / or functions of the elements of the point cloud decoder of FIG. 7 described above. Furthermore, the one or more processors may operate or execute a set of software programs and / or instructions for performing the operations and / or functions of the elements of the point cloud decoder of FIG. 7.

[0176] Figure 8 is an example of a transmission device according to embodiments.

[0177] The transmission device illustrated in FIG. 8 is an example of the transmission device (10000) of FIG. 1 (or the point cloud encoder of FIG. 3). The transmission device illustrated in FIG. 8 can perform at least one or more of the same or similar operations and encoding methods as the operations and encoding methods of the point cloud encoder described in FIGS. 1 to 6. A transmission device according to embodiments may include a data input unit (8000), a quantization processing unit (8001), a voxelization processing unit (8002), an octree occupancy code generation unit (8003), a surface model processing unit (8004), an intra / inter coding processing unit (8005), an arithmetic coder (8006), a metadata processing unit (8007), a color conversion processing unit (8008), an attribute conversion processing unit (or a property conversion processing unit) (8009), a prediction / lifting / RAHT conversion processing unit (8010), an arithmetic coder (8011), and / or a transmission processing unit (8012).

[0178] The data input unit (8000) according to the embodiments receives or acquires point cloud data. The data input unit (8000) may perform operations and / or acquisition methods identical or similar to those of the point cloud video acquisition unit (10001) (or the acquisition process (20000) described in FIG. 2).

[0179] The data input unit (8000), quantization processing unit (8001), voxelization processing unit (8002), octree occupancy code generation unit (8003), surface model processing unit (8004), intra / inter coding processing unit (8005), and arithmetic coder (8006) perform geometry encoding. Since the geometry encoding according to the embodiments is the same or similar to the geometry encoding described in FIGS. 1 to 6, a detailed description thereof will be omitted.

[0180] The quantization processing unit (8001) according to the embodiments quantizes geometry (e.g., position values ​​of points or position values). The operation and / or quantization of the quantization processing unit (8001) is identical to or similar to the operation and / or quantization of the quantization unit (30001) described in FIG. 3. The specific description is the same as that described in FIGS. 1 to 6.

[0181] The voxelization processing unit (8002) according to the embodiments voxels the position values ​​of quantized points. The voxelization processing unit (80002) may perform operations and / or processes identical or similar to the operations and / or voxelization processes of the quantization unit (30001) described in FIG. 3. Specific descriptions are identical to those described in FIGS. 1 to 6.

[0182] The octree occupancy code generation unit (8003) according to the embodiments performs octree coding on the positions of voxelized points based on the octree structure. The octree occupancy code generation unit (8003) can generate an occupancy code. The octree occupancy code generation unit (8003) can perform operations and / or methods identical or similar to those of the point cloud encoder (or octree analysis unit (30002)) described in FIGS. 3 and 4. The specific description is the same as that described in FIGS. 1 to 6.

[0183] The surface model processing unit (8004) according to the embodiments can perform tri-subject geometry encoding to reconstruct the positions of points within a specific area (or node) on a voxel basis based on the surface model. The surface model processing unit (8004) can perform operations and / or methods identical or similar to those of the point cloud encoder (e.g., surface approximation analysis unit (30003)) described in FIG. 3. The specific description is the same as that described with reference to FIGS. 1 to 6.

[0184] The intra / inter coding processing unit (8005) according to embodiments can intra / inter code point cloud data. The intra / inter coding processing unit (8005) can perform coding identical to or similar to the intra / inter coding described in FIG. 7. The specific description is identical to that described in FIG. 7. According to embodiments, the intra / inter coding processing unit (8005) can be included in an arithmetic coder (8006).

[0185] An arithmetic coder (8006) according to embodiments entropy encodes an octree and / or an approximated octree of point cloud data. For example, the encoding method includes an arithmetic encoding method. The arithmetic coder (8006) performs operations and / or methods identical or similar to those of the arithmetic encoder (30004).

[0186] The metadata processing unit (8007) according to the embodiments processes metadata regarding point cloud data, such as setting values, and provides the metadata to a necessary processing step, such as geometry encoding and / or attribute encoding. In addition, the metadata processing unit (8007) according to the embodiments may generate and / or process signaling information related to geometry encoding and / or attribute encoding. The signaling information according to the embodiments may be encoded and processed separately from geometry encoding and / or attribute encoding. In addition, the signaling information according to the embodiments may be interleaved.

[0187] The color conversion processing unit (8008), the attribute conversion processing unit (8009), the prediction / lifting / RAHT conversion processing unit (8010), and the arithmetic coder (8011) perform attribute encoding. Since the attribute encoding according to the embodiments is the same as or similar to the attribute encoding described in FIGS. 1 to 6, a detailed description thereof will be omitted.

[0188] The color conversion processing unit (8008) according to the embodiments performs color conversion coding to convert the color values ​​included in the attributes. The color conversion processing unit (8008) can perform color conversion coding based on the reconstructed geometry. The description of the reconstructed geometry is the same as that described with reference to FIGS. 1 to 6. In addition, the color conversion processing unit (8008) performs the same or similar operation and / or method as that of the color conversion unit (30006) described with reference to FIG. 3. A detailed description thereof will be omitted.

[0189] The attribute transformation processing unit (8009) according to embodiments performs attribute transformation to transform attributes based on positions for which geometry encoding has not been performed and / or reconstructed geometry. The attribute transformation processing unit (8009) performs operations and / or methods that are the same as or similar to those of the attribute transformation unit (30007) described in FIG. 3. A detailed description thereof will be omitted. The prediction / lifting / RAHT transformation processing unit (8010) according to embodiments can code transformed attributes by using any one or a combination of RAHT coding, prediction transformation coding, and lifting transformation coding. The prediction / lifting / RAHT transformation processing unit (8010) performs at least one or more of operations that are the same as or similar to those of the RAHT transformation unit (30008), LOD generation unit (30009), and lifting transformation unit (30010) described in FIG. 3. In addition, the description of the prediction transformation coding, lifting transformation coding, and RAHT transformation coding is the same as that described in FIGS. 1 to 6, so a detailed description is omitted.

[0190] An arithmetic coder (8011) according to embodiments can encode coded attributes based on arithmetic coding. The arithmetic coder (8011) performs operations and / or methods identical or similar to those of the arithmetic encoder (300012).

[0191] The transmission processing unit (8012) according to embodiments may transmit each bitstream including encoded geometry and / or encoded attribute, metadata information, or may transmit the encoded geometry and / or encoded attribute, and metadata information as one bitstream. When the encoded geometry and / or encoded attribute, and metadata information according to embodiments are configured as one bitstream, the bitstream may include one or more sub-bitstreams. The bitstream according to embodiments may include signaling information including a Sequence Parameter Set (SPS) for sequence-level signaling, a Geometry Parameter Set (GPS) for signaling geometry information coding, an Attribute Parameter Set (APS) for signaling attribute information coding, and a Tile Parameter Set (TPS) for tile-level signaling, and slice data. The slice data may include information about one or more slices. One slice according to embodiments may include one geometry bitstream (Geom0). 0 ) and one or more attribute bitstreams (Attr0 0 , Attr1 0 ) may be included.

[0192] A slice is a series of syntax elements that represent all or part of a coded point cloud frame.

[0193] A TPS according to embodiments may include information about each tile (e.g., coordinate value information of a bounding box and height / size information, etc.) for one or more tiles. A geometry bitstream may include a header and a payload. The header of a geometry bitstream according to embodiments may include identification information of a parameter set included in GPS (geom_ parameter_set_id), a tile identifier (geom_tile_id), a slice identifier (geom_slice_id), and information about data included in the payload. As described above, a metadata processing unit (8007) according to embodiments may generate and / or process signaling information and transmit it to a transmission processing unit (8012). According to embodiments, elements that perform geometry encoding and elements that perform attribute encoding may share data / information with each other as indicated by a dotted line. The transmission processing unit (8012) according to the embodiments may perform operations and / or transmission methods identical or similar to those of the transmitter (10003). A detailed description thereof is omitted as it is the same as that described in FIGS. 1 and 2.

[0194] Fig. 9 is an example of a receiving device according to embodiments.

[0195] The receiving device illustrated in FIG. 9 is an example of the receiving device (10004) of FIG. 1 (or the point cloud decoder of FIGS. 10 and 11). The receiving device illustrated in FIG. 9 can perform at least one or more of the same or similar operations and decoding methods as the operations and decoding methods of the point cloud decoder described in FIGS. 1 to 11.

[0196] A receiving device according to embodiments may include a receiving unit (9000), a receiving processing unit (9001), an arithmetic decoder (9002), an occupancy code-based octree reconstruction processing unit (9003), a surface model processing unit (triangle reconstruction, up-sampling, voxelization) (9004), an inverse quantization processing unit (9005), a metadata parser (9006), an arithmetic decoder (9007), an inverse quantization processing unit (9008), a prediction / lifting / RAHT inverse transform processing unit (9009), a color inverse transform processing unit (9010), and / or a renderer (9011). Each component of the decoding according to embodiments may perform the reverse process of the component of the encoding according to embodiments.

[0197] The receiving unit (9000) according to the embodiments receives point cloud data. The receiving unit (9000) may perform operations and / or receiving methods identical or similar to those of the receiver (10005) of FIG. 1. A detailed description thereof will be omitted.

[0198] The receiving processing unit (9001) according to the embodiments can obtain a geometry bitstream and / or an attribute bitstream from the received data. The receiving processing unit (9001) can be included in the receiving unit (9000).

[0199] The arithmetic decoder (9002), the occupancy code-based octree reconstruction processing unit (9003), the surface model processing unit (9004), and the inverse quantization processing unit (9005) can perform geometry decoding. Since the geometry decoding according to the embodiments is the same or similar to the geometry decoding described in FIGS. 1 to 10, a detailed description thereof will be omitted.

[0200] An arithmetic decoder (9002) according to embodiments can decode a geometry bitstream based on arithmetic coding. The arithmetic decoder (9002) performs operations and / or coding identical to or similar to those of the arithmetic decoder (7000).

[0201] The occupancy code-based octree reconstruction processing unit (9003) according to embodiments can reconstruct an octree by obtaining an occupancy code from a decoded geometry bitstream (or information about the geometry obtained as a result of decoding). The occupancy code-based octree reconstruction processing unit (9003) performs the same or similar operations and / or methods as those of the octree synthesis unit (7001) and / or the octree generation method. The surface model processing unit (9004) according to embodiments can perform tri-sub geometry decoding and related geometry reconstructing (e.g., triangle reconstruction, up-sampling, voxelization) based on the surface model method when tri-sub geometry encoding is applied. The surface model processing unit (9004) performs the same or similar operations as those of the surface off-ratio synthesis unit (7002) and / or the geometry reconstructing unit (7003).

[0202] The inverse quantization processing unit (9005) according to the embodiments can inverse quantize the decoded geometry.

[0203] The metadata parser (9006) according to the embodiments can parse metadata, such as setting values, contained in the received point cloud data. The metadata parser (9006) can pass the metadata to geometry decoding and / or attribute decoding. A detailed description of the metadata is omitted as it is the same as described in FIG. 8.

[0204] The arithmetic decoder (9007), the inverse quantization processing unit (9008), the prediction / lifting / RAHT inverse transform processing unit (9009), and the color inverse transform processing unit (9010) perform attribute decoding. Since attribute decoding is the same or similar to the attribute decoding described in FIGS. 1 to 10, a detailed description thereof will be omitted.

[0205] An arithmetic decoder (9007) according to embodiments can decode an attribute bitstream using arithmetic coding. The arithmetic decoder (9007) can decode the attribute bitstream based on the reconstructed geometry. The arithmetic decoder (9007) performs operations and / or coding identical or similar to those of the arithmetic decoder (7005).

[0206] The inverse quantization processing unit (9008) according to the embodiments can inverse quantize the decoded attribute bitstream. The inverse quantization processing unit (9008) performs operations and / or methods identical or similar to the operations and / or inverse quantization methods of the inverse quantization unit (7006).

[0207] The prediction / lifting / RAHT inverse transform processing unit (9009) according to embodiments can process reconstructed geometry and inverse quantized attributes. The prediction / lifting / RAHT inverse transform processing unit (9009) performs at least one or more of operations and / or decodings that are identical or similar to the operations and / or decodings of the RAHT transform unit (7007), the LOD generation unit (7008), and / or the inverse lifting unit (7009). The color inverse transform processing unit (9010) according to embodiments performs inverse transform coding for inverse transforming the color value (or texture) included in the decoded attributes. The color inverse transform processing unit (9010) performs operations and / or inverse transform coding that are identical or similar to the operations and / or inverse transform coding of the color inverse transform unit (7010). A renderer (9011) according to embodiments can render point cloud data.

[0208] Fig. 10 shows an example of a structure that can be linked with a point cloud data transmission / reception method / device according to embodiments.

[0209] The structure of FIG. 10 represents a configuration in which at least one of a server (1060), a robot (1010), an autonomous vehicle (1020), an XR device (1030), a smartphone (1040), a home appliance (1050), and / or an HMD (1070) is connected to a cloud network (1010). The robot (1010), the autonomous vehicle (1020), the XR device (1030), the smartphone (1040), or the home appliance (1050) are referred to as devices. In addition, the XR device (1030) may correspond to or be linked with a point cloud data (PCC) device according to embodiments.

[0210] A cloud network (1000) may refer to a network that constitutes part of a cloud computing infrastructure or exists within the cloud computing infrastructure. Here, the cloud network (1000) may be configured using a 3G network, a 4G or LTE (Long Term Evolution) network, or a 5G network.

[0211] The server (1060) is connected to at least one of a robot (1010), an autonomous vehicle (1020), an XR device (1030), a smartphone (1040), a home appliance (1050), and / or an HMD (1070) through a cloud network (1000), and can assist in at least part of the processing of the connected devices (1010 to 1070).

[0212] The HMD (Head-Mount Display) (1070) represents one of the types in which the XR device and / or the PCC device according to the embodiments can be implemented. The HMD type device according to the embodiments includes a communication unit, a control unit, a memory unit, an I / O unit, a sensor unit, and a power supply unit.

[0213] Below, various embodiments of devices (1010 to 1050) to which the above-described technology is applied are described. Here, the devices (1010 to 1050) illustrated in FIG. 10 can be linked / combined with point cloud data transmission / reception devices according to the above-described embodiments.

[0214] <PCC+XR>

[0215] The XR / PCC device (1030) may be implemented as a HMD (Head-Mount Display), a HUD (Head-Up Display) equipped in a vehicle, a television, a mobile phone, a smart phone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a fixed robot, a mobile robot, etc., by applying PCC and / or XR (AR+VR) technology.

[0216] The XR / PCC device (1030) can obtain information about surrounding space or real objects by analyzing 3D point cloud data or image data acquired through various sensors or from external devices to generate location data and attribute data for 3D points, and can render and output an XR object to be output. For example, the XR / PCC device (1030) can output an XR object including additional information about a recognized object in correspondence with the recognized object.

[0217] <PCC+XR+모바일폰>

[0218] The XR / PCC device (1030) can be implemented as a mobile phone (1040) or the like by applying PCC technology.

[0219] The mobile phone (1040) can decode and display point cloud content based on PCC technology.

[0220] <PCC+자율주행+XR>

[0221] Autonomous vehicles (1020) can be implemented as mobile robots, vehicles, unmanned aerial vehicles, etc. by applying PCC technology and XR technology.

[0222] An autonomous vehicle (1020) to which XR / PCC technology is applied may refer to an autonomous vehicle equipped with a means for providing XR images, or an autonomous vehicle that is the subject of control / interaction within an XR image. In particular, an autonomous vehicle (1020) that is the subject of control / interaction within an XR image is distinct from an XR device (1030) and can be linked with each other.

[0223] An autonomous vehicle (1020) equipped with a means for providing XR / PCC images can obtain sensor information from sensors including cameras and output XR / PCC images generated based on the obtained sensor information. For example, the autonomous vehicle (1020) can be equipped with a HUD to output XR / PCC images, thereby providing passengers with XR / PCC objects corresponding to real objects or objects on a screen.

[0224] At this time, when the XR / PCC object is output to the HUD, at least a part of the XR / PCC object may be output so as to overlap with an actual object toward which the passenger's gaze is directed. On the other hand, when the XR / PCC object is output to a display provided inside the autonomous vehicle, at least a part of the XR / PCC object may be output so as to overlap with an object on the screen. For example, the autonomous vehicle (1220) may output XR / PCC objects corresponding to objects such as a lane, another vehicle, a traffic light, a traffic sign, a two-wheeled vehicle, a pedestrian, a building, etc.

[0225] VR (Virtual Reality) technology, AR (Augmented Reality) technology, MR (Mixed Reality) technology and / or PCC (Point Cloud Compression) technology according to the embodiments can be applied to various devices.

[0226] In other words, VR technology is a display technology that provides only CG images of objects or backgrounds in the real world. On the other hand, AR technology refers to a technology that shows a virtually created CG image on top of an image of an actual object. Furthermore, MR technology is similar to the aforementioned AR technology in that it mixes and combines virtual objects in the real world. However, in AR technology, the distinction between real objects and virtual objects created with CG images is clear, and virtual objects are used in a form that complements real objects, whereas in MR technology, virtual objects are considered to have the same characteristics as real objects. A more specific example is the hologram service, which is an application of the aforementioned MR technology.

[0227] However, recently, rather than clearly distinguishing between VR, AR, and MR technologies, they are often referred to as XR (extended reality) technologies. Therefore, embodiments of the present invention are applicable to all VR, AR, MR, and XR technologies. These technologies can be applied to encoding / decoding based on PCC, V-PCC, and G-PCC technologies.

[0228] The PCC method / device according to the embodiments can be applied to a vehicle providing an autonomous driving service.

[0229] Vehicles providing autonomous driving services are connected to PCC devices to enable wired / wireless communication.

[0230] A point cloud data (PCC) transmission and reception device according to embodiments, when connected to a vehicle to enable wired / wireless communication, can receive / process content data related to AR / VR / PCC services that can be provided together with autonomous driving services and transmit the same to the vehicle. In addition, when the point cloud data transmission and reception device is mounted on a vehicle, the point cloud transmission and reception device can receive / process content data related to AR / VR / PCC services and provide the same to a user according to a user input signal input through a user interface device. A vehicle or a user interface device according to embodiments can receive a user input signal. The user input signal according to embodiments can include a signal instructing an autonomous driving service.

[0231] The encoding method and device according to the embodiments may include and perform the transmitting device (10000) of FIG. 1, the point cloud video encoder (10002), the transmitter (10003), the acquisition-encoding-transmission (20000-20001-20002) of FIG. 2, the encoder of FIG. 3, the transmitting device of FIG. 8, the device of FIG. 10, the encoders of FIGS. 12 to 13 and FIGS. 16 to 17, the bitstream and syntax generation of FIGS. 18 to 30, and the encoding method of FIG. 31.

[0232] The decoding method and device according to the embodiments may include and perform the receiving device (10004), receiver (10005), point cloud video decoder (10006) of FIG. 1, transmission-decoding-rendering (20002-20003-20004) of FIG. 2, decoder of FIG. 7, receiving device of FIG. 9, device of FIG. 10, decoders of FIGS. 14 to 15 and FIGS. 16 to 17, bitstream and syntax parsing of FIGS. 18 to 30, encoding method of FIG. 32, etc.

[0233] The encoding / decoding method according to the embodiments includes a sampling method for LOD generation.

[0234] The embodiments relate to a method for improving the compression efficiency of attributes of Geometry-based Point Cloud Compression (G-PCC) for compressing 3D point cloud data, and include a sampling method for improving the attribute compression efficiency when generating a level of detail (hereinafter referred to as LOD) during a G-PCC attribute encoding and decoding process.

[0235] For example, it includes 1) sampling method, 2) sampling period calculation method, 3) signaling method, etc.

[0236] The embodiments include a method for improving the compression efficiency of G-PCC for compressing 3D point cloud data. Hereinafter, the terms "encoder" and "decoder" may be used interchangeably, and the terms "decoder" and "decoder" may be used interchangeably.

[0237] A point cloud consists of a collection of points, each of which can have geometry and attribute information. Geometry information includes 3D positional (XYZ) information, while attribute information includes color (RGB, YUV, etc.) and / or reflectance values.

[0238] The G-PCC encoding process can be comprised of dividing a point cloud into tiles by region, dividing each tile into slices for parallel processing, compressing geometry for each slice, and compressing attribute information based on the reconstructed geometry (decoded geometry) based on the positional information changed through compression.

[0239] The G-PCC decoding process can be composed of a process of receiving an encoded slice unit geometry bitstream and an attribute bitstream, decoding the geometry, and decoding attribute information based on the geometry reconstructed through the decoding process.

[0240] Octree-based, predictive tree-based, or trisoup-based compression techniques can be used to compress geometry information.

[0241] For attribute information compression, compression techniques based on predicting transform, lifting transform, or RAHT transform can be used.

[0242] Embodiments include a method for obtaining high compression efficiency by generating a Level Of Detail (LOD) more suitable for point cloud content in generating a LOD of a lifting transformation used for compressing the properties of point cloud content.

[0243] Figure 11 shows sampling of point cloud data according to embodiments.

[0244] The encoding method according to the embodiments (the transmitting device (10000) of FIG. 1, the point cloud video encoder (10002), the transmitter (10003), the acquisition-encoding-transmission (20000-20001-20002) of FIG. 2, the encoder of FIG. 3, the transmitting device of FIG. 8, the device of FIG. 10, the encoder of FIGS. 12 to 13 and 16 to 17, the bitstream and syntax generation of FIGS. 18 to 30, and the encoding method of FIG. 31) can encode attribute data of point cloud data based on LoD.

[0245] The decoding method according to the embodiments (receiving device (10004), receiver (10005), point cloud video decoder (10006) of FIG. 1, transmission-decoding-rendering (20002-20003-20004) of FIG. 2, decoder of FIG. 7, receiving device of FIG. 9, device of FIG. 10, decoder of FIGS. 14 to 15 and 16 to 17, bitstream and syntax parsing of FIGS. 18 to 30, encoding method of FIG. 32) can decode attribute data of point cloud data based on LoD.

[0246] The LOD generation method for encoding and decoding can include three methods. For example, it can include 1) a distance-based LoD generation method, 2) a sampling-based LoD generation method, and 3) an octree-based LoD generation method.

[0247] 1) Distance-based method refers to a method of classifying LOD based on the distance between points.

[0248] 2) The sampling-based method means sorting the points by Morton code and classifying every Xth corresponding point into a coarse LOD that can be a candidate for the neighbor set.

[0249] 3) The octree-based method is a method of constructing an octree for points and selecting points close to the center according to the node level of the octree to classify them into a coarse LOD.

[0250] The LOD generation method based on the Molton order-based sampling method described above may result in non-uniform sampling of the point cloud acquired through the spinning lidar.

[0251] Figure 11 illustrates an example of Molton order-based sampling of spinning lidar content. Points identified as 1100 in Figure 11 represent sampled points.

[0252] As shown in the example in Fig. 11, when generating a Moulton code for a geometry converted to angular mode and sorting it using the Moulton code, consecutive points may have different laser indices. In this case, points with different laser indices are relatively farther away from the orthogonal coordinate system than points with the same laser index, and are more likely to have different reflectance values, which may reduce the prediction efficiency during lifting conversion.

[0253] Therefore, the embodiments can improve compression efficiency by complementing the shortcomings of the LOD generation method based on the Molton order-based sampling method in spinning lidar content.

[0254] For example, when generating LOD, the attribute compression efficiency can be increased through more uniform sampling than other methods by sampling at each sampling cycle according to the LOD level value in the order of points sorted based on azimuth and classifying them into lower LODs.

[0255] The embodiments may be modified and combined. The terms used in this document may be understood based on their intended meaning, within the scope widely used in the relevant field. The sampling-based LOD generation method according to the embodiments can be performed and applied in both PCC encoders and decoders.

[0256] The sampling-based LoD generation method may include 1) periodic sampling-based LoD generation, 2) periodic sampling-based LoD generation based on a different order (alternative order), and / or 3) a sampling period acquisition method.

[0257] 1) LOD generation method based on periodic sampling

[0258] The method according to the embodiments may include a lifting transformation method for attribute encoding / decoding. At this time, LOD may be generated before the lifting transformation in order to perform the lifting transformation. LOD may be generated through a periodic sampling method with a fixed sampling period of low complexity, reflecting the low-latency characteristic of the lidar point cloud. At this time, the sampling-based LOD generation method may sample points belonging to the current point group (LoD level index N) to sample points to be included in the point group (LoD level index N+1). The remaining points that were not sampled may be included in the current point group (LoD level index N).

[0259] At this time, all points may be sorted based on the Molton code order. Therefore, sampling can be performed according to the sampling period value based on the order. For example, if the sampling period is 4, 1 out of 4 points can be sampled. At this time, the last point among the 4 can be sampled. In addition, periodic sampling can be performed recursively for points included in the lower point group. In other words, sampling can be performed for each level of LOD, and sampling can be performed up to the maximum LOD level.

[0260] 2) Other order-based periodic sampling-based LOD generation methods

[0261] As another embodiment of periodic sampling for LOD generation, periodic sampling can be performed based on a different order than the currently sorted point order. For example, if the current point cloud is sorted by Moulton code, periodic sampling can be performed based on the order before being sorted by Moulton code. In this case, the point order before being sorted by Moulton code can be the same as the order output by the geometry decoder. When this is referred to as the standard order, an index according to the standard point order can be stored separately and used for sampling. Conversely, if the current point cloud is not sorted by Moulton code, an index according to the Moulton code-based order can be stored for each point and used for sampling.

[0262] As another example, the ordering can be re-arranged based on criteria other than the existing sorted order, and periodic sampling can be performed based on the corresponding index. For example, all current points can be ordered based on azimuth, and the indices based on the order can be stored and used for sampling. In this case, if the azimuth is the same, the ordering can be determined based on other values ​​among the geometry values. For example, the radius and the laser index can be the second and third criteria, respectively. Alternatively, the laser index and the radius can be the second and third criteria, respectively.

[0263] In another embodiment, if a criterion other than the existing sorted order is used, the criterion may be changed depending on the laser ID. For example, a specific laser ID group may use an azimuth-based ordering, while another laser ID group may use a radius-based ordering for sampling. Here, a laser ID group may include one or more laser IDs. Alternatively, the ordering criterion may be used adaptively based on the value of one of the three channels of geometry information.

[0264] As another embodiment, the "alt_order_lod_subsampling_type", which indicates the type of sampling method for LOD generation, can be transmitted from the encoder to the decoder via high-level information. Here, the type can include a Moulton code order, a standard order, an azimuth order, a radial order, a laser order, etc.

[0265] 3) How to obtain sampling period

[0266] A sampling period can be used to sample sub-level points at each LOD level. Different values ​​for the sampling period can be used for each LOD level. The sampling period for each level can be included in High Level Syntax (HLS), such as Sequence Parameter Set (SPS), Geometry Parameter Set (GPS), and Tile Parameter Set (TPS), and transmitted from the encoder to the decoder.

[0267] As another method of obtaining a sampling period, the transmitted level-specific sampling period value may be information expressed as an exponent value of 2. That is, the sampling period may be determined as one of the powers of 2.

[0268] Another way to obtain the sampling period is to use the product of all the period values ​​of the received level-specific sampling period values ​​lower than the current level as the sampling period. For example, if the LOD can be divided into four levels and the values ​​4, 4, 4, 4 are received, the sampling periods for each level can be determined as 4, 16, 64, and 256.

[0269] As another method of obtaining a sampling period, the sum of all period values ​​of levels lower than the current level among the transmitted sampling period values ​​can be used as the sampling period.

[0270] Fig. 12 shows an encoder according to embodiments.

[0271] Figure 12 is a block diagram of a PCC data encoder. Each component may correspond to hardware, software, a processor, and / or a combination thereof. PCC data may be input to the encoder and encoded to output a geometry information bitstream and an attribute information bitstream. The encoder in Figure 12 may be configured with a memory and / or at least one processor connected to the memory. At least one processor may be configured to perform the operations of each component in Figure 12.

[0272] The data input section can read and set input data (e.g., ply, configuration file, etc.).

[0273] The coordinate system transformation unit can support coordinate system changes, such as changing the xyz axes or converting from the xyz rectangular coordinate system to the spherical coordinate system.

[0274] The geometry information transformation quantization processing unit can adjust the scale by multiplying the geometry location x, y, and z values ​​of the point cloud point by the scale according to the scale (scale = geometry quantization value) setting.

[0275] The spatial partition can be divided into tiles or slices for area-specific access or parallel processing of content.

[0276] The geometry encoding unit can encode spatially divided geometry information to generate a geometry information bitstream.

[0277] The color conversion processor can support attribute type conversion, such as changing RGB color to YUV.

[0278] The color rescaling unit can predict attribute values ​​appropriate for the changed location when the geometry is scaled and the location information values ​​are changed.

[0279] The attribute information encoding unit can receive color-resized original attribute information, restored geometry information, and a reference frame as input and perform encoding to generate an attribute information bitstream.

[0280] The reference frame generation unit can store restored geometry and restored attribute information in a reference frame buffer and transfer reference frame data from the reference frame to other modules.

[0281] Figure 13 shows encoding of attribute data according to embodiments.

[0282] Figure 13 is a block diagram of an attribute data encoding unit included in the Figure 12 encoder. Each component may correspond to hardware, software, a processor, and / or a combination thereof.

[0283] The LOD generation unit can receive segmented point cloud data and generate LODs, and determine point-by-point neighbors used in lifting transformation and prediction transformation. At this time, the LOD generation unit can be performed when LOD parameters are present.

[0284] The lifting transform unit can generate transform coefficients by performing frequency transformation on attribute information through LOD level-specific prediction and update processes using the generated LOD. The generated transform coefficients can be quantized and transmitted to the attribute information entropy encoding unit. Additionally, an internal inverse transformation can be performed to output restored attribute information.

[0285] Predictive transformation can be performed to predict the current point using neighboring points determined during the LOD generation process. The predicted attribute information and the original attribute information can be converted into differential values ​​called transform coefficients, which can be quantized and passed to the attribute information entropy encoding unit. Furthermore, attribute information can be restored and output through inverse quantization and predictive inverse transformation.

[0286] RAHT can be performed without LOD parameters. It receives segmented point cloud data and performs Region Adaptive Hierarchical Transform (RAHT) to transform it into the frequency domain, generating transform coefficients. These transform coefficients are then quantized and passed to the attribute information entropy encoding unit.

[0287] Fig. 14 shows a decoder according to embodiments.

[0288] The decoder of Fig. 14 can follow the reverse process of the operation of the encoder of Fig. 12. Fig. 14 is a block diagram of a PCC data encoder. Each component can correspond to hardware, software, a processor, and / or a combination thereof. The input of the decoder is an encoded geometry information bitstream and an attribute information bitstream, and the decoded and restored PCC data can be output.

[0289] The geometry information decoding unit can receive a geometry information bitstream and decode it to restore the geometry information.

[0290] The coordinate system inversion unit can restore the changed xyz axes or inversely transform the transformed coordinate system into the xyz orthogonal coordinate system.

[0291] The geometry information conversion dequantization processing unit can restore the signaled scale (scale = geometry quantization value) and apply it to the geometry location x, y, and z values ​​of the restored point.

[0292] Attribute residual information entropy decoding can entropy decode attribute bitstreams.

[0293] The attribute information decryption unit can receive an attribute information bitstream and decrypt it to restore the attribute information.

[0294] The color inversion processing unit can restore the converted attributes to RGB colors.

[0295] The reference frame generation unit can store restored geometry and restored attribute information in a reference frame buffer and transfer reference frame data from the reference frame to other modules.

[0296] Figure 15 illustrates decoding of attribute data according to embodiments.

[0297] Figure 15 is a block diagram of an attribute data decoding unit included in the Figure 14 decoder. Each component may correspond to hardware, software, a processor, and / or a combination thereof.

[0298] The attribute information entropy decoding unit can receive an attribute information bitstream, decode it, and restore the transform coefficients.

[0299] The LOD generation unit can generate LODs by receiving restored geometry information, and can determine point-by-point neighbors used in lifting transformation and prediction transformation. At this time, the LOD generation unit can be performed when LOD parameters are present.

[0300] The lifting inverse transform can restore attribute information by inversely transforming the input transform coefficients and performing frequency inverse transform through the generated LOD and LOD level-by-LOD level update and prediction process.

[0301] Predictive inverse transformation can restore attributes by combining the current point with the predicted value and the inverse transformation value of the input transformation coefficient using the neighboring points determined during the LOD generation process.

[0302] Inverse RAHT can restore attribute information by performing the reverse process of RAHT by inputting restored geometry information and transformation coefficients.

[0303] Figure 16 illustrates LoD (Level of Detail) generation according to embodiments.

[0304] The encoder and decoder of FIGS. 12 to 15 can further perform a method of generating LoD as in FIG. 16 for attribute encoding and decoding.

[0305] The LOD generation unit can input restored geometry information and output a multi-layer LOD.

[0306] The Moulton code calculation unit can calculate the Moulton code by inputting restored geometry information.

[0307] The order storage unit can store indices based on the current point order in the form of a list.

[0308] The Molton code-based sorting unit can sort and output an index list based on the Molton code calculated based on geometry information. This sorting unit can be performed or omitted based on a flag indicating whether to use canonical order in the attribute. Canonical order refers to the order of points decoded from a slice according to the decoding and parsing process specified in the standard.

[0309] The sub-sampling unit can perform sub-sampling on the index list to distinguish the current points by LOD.

[0310] The nearest neighbor search unit can find one or more neighboring points for each point based on geometry and store the index of the point in order to predict and update the lifting transformation for points classified by LOD.

[0311] Figure 17 illustrates subsampling according to embodiments.

[0312] Fig. 17 illustrates a subsampling operation included in the LoD generation method of Fig. 16. The method and device according to the embodiments can restore geometry data, calculate a Moulton code for the restored geometry data, and generate a point order of the geometry data as a list based on the index of the point. If a canonical order is not used in the process of encoding and decoding attribute data, points can be sorted based on the Moulton code. Subsampling can be performed on points sorted based on the Moulton code. If a canonical order is used in the process of encoding and decoding attribute data, subsampling can be performed on points without sorting based on the Moulton code.

[0313] The specific method of subsampling is as follows:

[0314] If periodic sampling method is not used, distance-based sampling or octree-based sampling can be performed.

[0315] The distance-based sampling unit can input a list of ordered indices and perform sampling based on the distances between points in the list.

[0316] The octree-based sampling unit receives an ordered index list as input, constructs an octree based on the geometry information of the points in the list, and samples points close to the center of each depth node.

[0317] The sampling period calculation unit can calculate the sampling period using the value transmitted through HLS (high level syntax: syntax element in the bitstream).

[0318] The standard order-based periodic subsampling part can be performed when the standard order sampling flag is 1 or alt_order_lod_subsampling_enabled is 0. The standard order-based periodic subsampling part can perform sampling based on the order of the restored geometry, or if the Molton code is aligned, sampling can be performed based on the Molton code order. In other words, it can correspond to the existing method as the standard order-based periodic sampling method of the attribute part / decoder.

[0319] Here the standard order sampling flag or alt_order_lod_subsampling_enabled can be determined via the flag of one of the flags such as aps_extension_present, geom_tree_type, attr_canpnical_order_enabled.

[0320] aps_extension_present, geom_tree_type, and attr_canonical_order_enabled can mean the attribute parameter set extension flag, the type of geometry compression method, and a flag for whether to use the geometry canonical order throughout attribute compression, respectively.

[0321] If aps_extension_present is 1, geom_tree_type is 1 (the geometry compression method uses predictive trees), and attr_canonical_order_enabled is 0, the canonical order sampling flag can be set to 0 or alt_order_lod_subsampling_enabled can be set to 1.

[0322] If the standard order sampling flag is 0 or alt_order_lod_subsampling_enabled is 1, a different point order acquisition part can be performed.

[0323] Other point order acquisition units can store the index of the order in a list with different criteria than the current point order.

[0324] Other order-based periodic subsampling can perform periodic sampling by inputting a list of indices of different order.

[0325] Figure 18 shows a bitstream according to embodiments.

[0326] The encoding method and device according to the embodiments (the transmitting device (10000), the point cloud video encoder (10002), the transmitter (10003) of FIG. 1, the acquisition-encoding-transmission (20000-20001-20002) of FIG. 2, the encoder of FIG. 3, the transmitting device of FIG. 8, the device of FIG. 10, the encoders of FIGS. 12 to 13 and FIGS. 16 to 17, the bitstream and syntax generation of FIGS. 18 to 30, the encoding method of FIG. 31, etc.) can encode point cloud data and generate parameter information (which may be referred to as signaling information or syntax elements). A bitstream of FIG. 18 including the encoded point cloud data and the parameter information can be generated and transmitted.

[0327] The decoding method and device according to the embodiments (receiving device (10004), receiver (10005), point cloud video decoder (10006) of FIG. 1, transmission-decoding-rendering (20002-20003-20004) of FIG. 2, decoder of FIG. 7, receiving device of FIG. 9, device of FIG. 10, decoders of FIGS. 14 to 15 and FIGS. 16 to 17, bitstream and syntax parsing of FIGS. 18 to 30, encoding method of FIG. 32, etc.) can receive the bitstream of FIG. 18 and decode point cloud data based on parameter information.

[0328] In order to add / perform embodiments, related information can be signaled within the bitstream as shown in Fig. 18. Signaling information according to embodiments can be used at a transmitter (encoder) or a receiver (decoder), etc.

[0329] The encoded point cloud configuration is as follows. A point cloud data encoder that performs geometry encoding and / or attribute encoding processes can generate the encoded point cloud (or bitstream including the point cloud) as follows. In addition, signaling information regarding the point cloud data can be generated and processed by the metadata processing unit of the point cloud data transmission device and included in the point cloud as follows.

[0330] Each abbreviation stands for the following. Each abbreviation may be referred to by other terms within the same meaning: SPS (Sequence Parameter Set), GPS (Geometry Parameter Set), APS (Attribute Parameter Set), TPS (Tile Parameter Set), Geometry (Geometry bitstream = geometry slice header + [geometry PU header + Geometry PU data] | geometry slice data), Attribute (Attr) (Attribute bitstream = attribute data unit header + [attribute PU header + attribute PU data] | attribute data unit data).

[0331] Other order-based subsampling related optional information can be added and signaled in SPS, GPS, and TPS.

[0332] Other order-based subsampling related options information can be signaled by adding them to the TPS or the Geometry header / attribute header for each Slice.

[0333] Tiles or slices are provided to allow point clouds to be divided and processed by region.

[0334] When dividing by region, you can set different options for generating neighboring point sets for each region, providing a choice between low complexity and somewhat lower reliability, or conversely, high complexity but high reliability. These settings can vary depending on the receiver's processing capacity.

[0335] Therefore, when a point cloud is divided into tiles, different options can be applied to each tile.

[0336] When a point cloud is divided into slices, different options can be applied to each slice.

[0337] Figure 19 shows a sequence parameter set (SPS) according to embodiments.

[0338] Figure 19 illustrates the syntax of an SPS within the bitstream of Figure 18. The method according to the embodiments can signal other order-based sub-sampling-related option information by adding it to the Sequence Parameter Set.

[0339] Profile (profile_idc): Indicates that the bitstream conforms to a profile.

[0340] Profile Compatibility Flags (profile_compatibility_flags): If this value is 1, it indicates that the bitstream complies with the profile whose profile_idc is j.

[0341] Number of attribute sets (sps_num_attribute_sets): Indicates the number of coded attributes in the bitstream. The sps_num_attribute_sets value ranges from 0 to 63.

[0342] Attribute dimension (attribute_dimension[ i ]): Indicates the number of components of the i-th attribute.

[0343] Attribute instance ID (attribute_instance_id[ i ]): Represents the instance ID of the i-th attribute.

[0344] Enable alternative order based LoD subsampling (sps_alt_order_lod_subsampling_enabled): Indicates whether to use alternative order based subsampling for all sequences referencing the current SPS.

[0345] Figure 20 shows an SPS according to embodiments.

[0346] The method according to the embodiments can additionally define other order-based sub-sampling related option information in the SPS, as in FIG. 19 and FIG. 20. For example, referring to FIG. 20, other order-based sub-sampling related option information can be added to the Sequence Parameter Set.

[0347] Profile (profile_idc): Indicates that the bitstream conforms to a profile.

[0348] Profile Compatibility Flags (profile_compatibility_flags): If this value is 1, it indicates that the bitstream complies with the profile whose profile_idc is j.

[0349] Number of attribute sets (sps_num_attribute_sets): Indicates the number of coded attributes in the bitstream. The sps_num_attribute_sets value ranges from 0 to 63.

[0350] Attribute dimension (attribute_dimension[ i ]): Indicates the number of components of the i-th attribute.

[0351] Attribute instance ID (attribute_instance_id[ i ]): Represents the instance ID of the i-th attribute.

[0352] Enable Alternative Order LoD Subsampling (sps_alt_order_lod_subsampling_enabled): Indicates whether to use alternative order-based subsampling for all sequences referencing the current SPS.

[0353] Alternative order LoD subsampling type (sps_alt_order_lod_subsampling_type): Indicates whether a different order-based subsampling type will be used for all sequences referencing the current SPS. If sps_alt_order_lod_subsampling_type is not signaled, it can be set to 0.

[0354] Figure 21 shows a geometry parameter set (GPS) according to embodiments.

[0355] Figure 21 illustrates the syntax of GPS within the Figure 18 bitstream. Additional order-based sub-sampling-related optional information can be added to the Geometry Parameter Set during the geometry information encoding / decoding process.

[0356] Geometry parameter set ID (gps_geom_parameter_set_id): Provides a GPS identifier that other syntax elements can reference. The gps_seq_parameter_set_id value ranges from 0 to 15 (inclusive).

[0357] Sequence Parameter Set ID (gps_seq_parameter_set_id): Indicates the sps_seq_parameter_set_id value for the active SPS. gps_seq_parameter_set_id values ​​range from 0 to 15 (inclusive).

[0358] Geometry Tree Type (geom_tree_type): If geom_tree_type is 0, it indicates that the location information is coded using an Octree (which can also be referred to as an Accupancy Tree). If geom_tree_type is 1, it indicates that the location information is coded using a Predictive Tree.

[0359] Enable Alternative Order LoD Subsampling (gps_alt_order_lod_subsampling_enabled): Indicates whether to use alternative order-based subsampling for all frames referencing the current GPS. If the gps_alt_order_lod_subsampling_enabled value is 0, it can be derived from the sps_alt_order_lod_subsampling_enabled value.

[0360] Figure 22 shows GPS according to embodiments.

[0361] The method according to the embodiments can additionally define other order-based sub-sampling related option information in the SPS, as in FIG. 21 and FIG. 22. For example, referring to FIG. 22, other order-based sub-sampling related option information can be added to the Sequence Parameter Set.

[0362] Geometry parameter set ID (gps_geom_parameter_set_id): Provides a GPS identifier that other syntax elements can reference. The gps_seq_parameter_set_id value ranges from 0 to 15 (inclusive).

[0363] Sequence Parameter Set ID (gps_seq_parameter_set_id): Indicates the sps_seq_parameter_set_id value for the active SPS. gps_seq_parameter_set_id values ​​range from 0 to 15 (inclusive).

[0364] Geometry Tree Type (geom_tree_type): If geom_tree_type is 0, it indicates that the location information is coded using an Octree (meaning an accumpancy tree). If geom_tree_type is 1, it indicates that the location information is coded using a predictive tree.

[0365] Enable Alternative Order LoD Subsampling (gps_alt_order_lod_subsampling_enabled): Indicates whether to use alternative order-based subsampling for all frames referencing the current GPS. If the value of gps_alt_order_lod_subsampling_enabled is 0, it can be derived from the value of sps_alt_order_lod_subsampling_enabled.

[0366] Alternative Order LoD Subsampling Type (gps_alt_order_lod_subsampling_type): Indicates whether a different order-based subsampling type should be used for all frames referencing the current GPS. If gps_alt_order_lod_subsampling_type is not signaled, it can be set to 0.

[0367] Figure 23 shows an attribute parameter set (APS) according to embodiments.

[0368] Figure 23 illustrates the syntax of APS within the Figure 18 bitstream. Additional order-based sub-sampling-related optional information can be added to the Attribute Parameter Set during the attribute information encoding / decoding process.

[0369] Attribute Parameter Set ID (aps_attr_parameter_set_id): Provides an APS identifier that can be referenced by other syntax elements. The aps_attr_parameter_set_id value ranges from 0 to 15 (inclusive).

[0370] Sequence Parameter Set ID (aps_seq_parameter_set_id): Indicates the sps_seq_parameter_set_id value for the active SPS. aps_seq_parameter_set_id values ​​range from 0 to 15 (inclusive).

[0371] Lifting_num_pred_nearest_neighbours: The maximum number of nearest neighbors to use for prediction. The lifting_num_pred_nearest_neighbours value ranges from 1 to xx (inclusive).

[0372] The maximum number of direct predictors (lifting_max_num_direct_predictors) indicates the maximum number of predictors to use for direct prediction. The value of lifting_max_num_direct_predictors ranges from 0 to lifting_num_pred_nearest_neighbours. The value of the MaxNumPredictors variable used in the decoding process is as follows: MaxNumPredictors = lift_max_num_direct_predicots + 1

[0373] Enable Alternative Order LoD Subsampling (aps_alt_order_lod_subsampling_enabled): Indicates whether to use alternative order-based subsampling for all attributes referencing the current APS. If the value of aps_alt_order_lod_subsampling_enabled is 0, it can be derived from the value of gps_alt_order_lod_subsampling_enabled or sps_alt_order_lod_subsampling_enabled.

[0374] Figure 24 shows APS according to embodiments.

[0375] The method according to the embodiments can additionally define other order-based sub-sampling-related option information in the APS, as in FIG. 23 and FIG. 24. For example, referring to FIG. 24, other order-based sub-sampling-related option information can be added to the APS.

[0376] Attribute Parameter Set ID (aps_attr_parameter_set_id): Provides an APS identifier that can be referenced by other syntax elements. The aps_attr_parameter_set_id value ranges from 0 to 15 (inclusive).

[0377] Sequence Parameter Set ID (aps_seq_parameter_set_id): Indicates the sps_seq_parameter_set_id value for the active SPS. aps_seq_parameter_set_id values ​​range from 0 to 15 (inclusive).

[0378] Lifting_num_pred_nearest_neighbours: The maximum number of nearest neighbors to use for prediction. The lifting_num_pred_nearest_neighbours value ranges from 1 to xx (inclusive).

[0379] Lifting_max_num_direct_predictors: Indicates the maximum number of predictors to use for direct prediction. The value of lifting_max_num_direct_predictors ranges from 0 to lifting_num_pred_nearest_neighbours. The value of the MaxNumPredictors variable used in the decoding process is as follows: MaxNumPredictors = lift_max_num_direct_predicots + 1

[0380] Enable Alternative Order LoD Subsampling (aps_alt_order_lod_subsampling_enabled): Indicates whether to use alternative order-based subsampling for all attributes referencing the current APS. If the value of aps_alt_order_lod_subsampling_enabled is 0, it can be derived from the value of gps_alt_order_lod_subsampling_enabled or sps_alt_order_lod_subsampling_enabled.

[0381] Alternative order LoD subsampling type (aps_alt_order_lod_subsampling_type): Indicates whether a different order-based subsampling type is used for all attributes referencing the current APS. If aps_alt_order_lod_subsampling_type is not signaled, it can be set to 0.

[0382] Figure 25 shows a tile parameter set (TPS) according to embodiments.

[0383] Figure 25 illustrates the syntax of a TPS within the bitstream of Figure 18. Additional order-based sub-sampling-related optional information can be added to the TPS during the encoding / decoding process.

[0384] Enable Alternative Order LoD Subsampling (tps_alt_order_lod_subsampling_enabled): Indicates whether to apply alternative order-based subsampling to all tiles referencing the current TPS. If tile_alt_order_lod_subsampling_enabled is 0, it can be derived from gps_alt_order_lod_subsampling_enabled or sps_alt_order_lod_subsampling_enabled.

[0385] tile_bounding_box_offset_x[ i ]: The x-offset of the ith tile in Cartesian coordinates. If this value is missing, the value of tile_bounding_box_offset_x

[0000] is inferred to be sps_bounding_box_offset_x.

[0386] The tile bounding box offset y (tile_bounding_box_offset_y[ i ]) represents the y-offset of the ith tile in Cartesian coordinates. If this value is missing, the value of tile_bounding_box_offset_y

[0000] is inferred to be sps_bounding_box_offset_y.

[0387] Tile bounding box offset z (tile_bounding_box_offset_z[ i ]): Indicates the z-offset of the ith tile in Cartesian coordinates. If this value is missing, the value of tile_bounding_box_offset_z

[0000] is inferred to be sps_bounding_box_offset_z.

[0388] Reference Frame Sampling Enabled (reference_frame_sampling_enabled): Indicates whether reference frame sampling is used for the tile.

[0389] Reference sampling threshold (reference_sampling_threshold): Indicates the reference frame sampling threshold applied to the tile (see the description of the other order-based periodic sampling-based LoD generation method described above, 2).

[0390] Reference sampling scale enabled (reference_sampling_scale_enabled): Indicates whether the reference frame sampling attribute coordinate system scale value applied to the tile is applied.

[0391] Enable alternative order LoD subsampling (tile_alt_order_lod_subsampling_enabled[ i ]): Indicates whether to apply alternative order-based subsampling for the current tile. If the value of tile_alt_order_lod_subsampling_enabled[ i ] is 0, it can be derived from one of the values ​​of tps_alt_order_lod_subsampling_enabled, gps_alt_order_lod_subsampling_enabled, or sps_alt_order_lod_subsampling_enabled.

[0392] Figure 26 shows a TPS according to embodiments.

[0393] The method according to the embodiments can additionally define other order-based sub-sampling related option information to the TPS, as in FIG. 25 and FIG. 26.

[0394] Enable Alternative Order LoD Subsampling (tps_alt_order_lod_subsampling_enabled): Indicates whether to apply alternative order-based subsampling to all tiles referencing the current TPS. If tile_alt_order_lod_subsampling_enabled is 0, it can be derived from gps_alt_order_lod_subsampling_enabled or sps_alt_order_lod_subsampling_enabled.

[0395] Alternative order LoD subsampling type (tps_alt_order_lod_subsampling_type): Indicates whether a different order-based subsampling type should be applied to all tiles referencing the current TPS. If tps_alt_order_lod_subsampling_type is not signaled, it can be set to 0.

[0396] Tile bounding box offset x (tile_bounding_box_offset_x[ i ]): Indicates the x-offset of the ith tile in Cartesian coordinates. If this value is missing, the value of tile_bounding_box_offset_x

[0000] is inferred to be sps_bounding_box_offset_x.

[0397] Tile bounding box offset y (tile_bounding_box_offset_y[ i ]) represents the y-offset of the ith tile in Cartesian coordinates. If this value is missing, the value of tile_bounding_box_offset_y

[0000] is inferred as sps_bounding_box_offset_y.

[0398] Tile bounding box offset z (tile_bounding_box_offset_z[ i ]) represents the z-offset of the ith tile in Cartesian coordinates. If this value is missing, the value of tile_bounding_box_offset_z

[0000] is inferred as sps_bounding_box_offset_z.

[0399] Reference Frame Sampling Enabled (reference_frame_sampling_enabled): Indicates whether reference frame sampling is used for the tile.

[0400] Reference sampling enable (reference_sampling_threshold): Indicates the reference frame sampling threshold applied to the tile (see 2) Other order-based periodic sampling-based LoD generation methods described above).

[0401] Reference sampling scale enabled (reference_sampling_scale_enabled): Indicates whether the reference frame sampling attribute coordinate system scale value applied to the tile is applied.

[0402] Enable Tile Alternate Order LoD Subsampling (tile_alt_order_lod_subsampling_enabled[ i ]): Indicates whether to apply alternative order-based subsampling for the current tile. If the value of tile_alt_order_lod_subsampling_enabled[ i ] is 0, it can be derived from one of the values ​​of tps_alt_order_lod_subsampling_enabled, gps_alt_order_lod_subsampling_enabled, or sps_alt_order_lod_subsampling_enabled.

[0403] Tile Alternative Order LoD Subsampling Type (tile_alt_order_lod_subsampling_type[ i ]): Indicates whether to apply some type of alternative order-based subsampling for the current tile. If tile_alt_order_lod_subsampling_type[ i ] is not signaled, it can be derived as 0.

[0404] Figure 27 shows a geometry data header according to embodiments.

[0405] Figure 27 illustrates optional information related to alternative order-based subsampling within the geometry slice header within the Figure 18 bitstream. A slice is an encoding / decoding unit and may be referred to as a data unit or simply data. The slice header may be referred to as a data unit header or data header.

[0406] Geometry parameter set ID (gsh_geometry_parameter_set_id): Indicates the gps_geom_parameter_set_id value of the active GPS.

[0407] Tile ID (gsh_tile_id): Indicates the tile ID value referenced in GSH. The gsh_tile_id value ranges from 0 to XX.

[0408] Slice ID (gsh_slice_id): Identifies the slice header that other syntax elements will reference. The gsh_slice_id value ranges from 0 to XX.

[0409] Enable alternative order LoD subsampling (gsh_alt_order_lod_subsampling_enabled): Indicates whether to use alternative order-based subsampling for the current slice. If gsh_alt_order_lod_subsampling_enabled is 0, it can be derived from one of the values ​​of tile_alt_order_lod_subsampling_enabled[ i ], tps_alt_order_lod_subsampling_enabled, gps_alt_order_lod_subsampling_enabled, or sps_alt_order_lod_subsampling_enabled.

[0410] Figure 28 shows a geometry data header according to embodiments.

[0411] Figure 28 shows the syntax of the geometry data header, as in Figure 27.

[0412] Geometry parameter set ID (gsh_geometry_parameter_set_id): Indicates the gps_geom_parameter_set_id value of the active GPS.

[0413] Tile ID (gsh_tile_id): Indicates the tile ID value referenced in GSH. The gsh_tile_id value ranges from 0 to XX.

[0414] Slice ID (gsh_slice_id): Identifies the slice header that other syntax elements will reference. The gsh_slice_id value ranges from 0 to XX.

[0415] Enable alternative order LoD subsampling (gsh_alt_order_lod_subsampling_enabled): Indicates whether to use alternative order-based subsampling for the current slice. If gsh_alt_order_lod_subsampling_enabled is 0, it can be derived from one of the values ​​of tile_alt_order_lod_subsampling_enabled[ i ], tps_alt_order_lod_subsampling_enabled, gps_alt_order_lod_subsampling_enabled, or sps_alt_order_lod_subsampling_enabled.

[0416] Alternative Order LoD gsh_alt_order_lod_subsampling_type: Indicates whether to use a different type of order-based subsampling for the current slice. If gsh_alt_order_lod_subsampling_type is not signaled, it can be set to 0.

[0417] Figure 29 shows an attribute data header according to embodiments.

[0418] Figure 29 illustrates optional information related to alternative order-based subsampling of the attribute data header in the bitstream of Figure 18. The attribute data header may be referred to as an attribute slice header, an attribute data unit header, etc.

[0419] Attribute parameter set ID (abh_attr_parameter_set_id): Indicates the abh_attr_parameter_set_id value of the active APS.

[0420] Attribute Sequence Parameter Attribute Index (abh_attr_sps_attr_idx): Indicates the attribute set of the active SPS. The abh_attr_sps_attr_idx value ranges from 0 to sps_num_attribute_sets in the active SPS.

[0421] Attribute Geometry Slice ID (abh_attr_geom_slice_id): Indicates the gsh_slice_id value of the active geometry slice header.

[0422] Enable Alternative Order LoD Subsampling (abh_alt_order_lod_subsampling_enabled): Indicates whether to use alternative order based subsampling for the current slice. If abh_alt_order_lod_subsampling_enabled is 0, it can be derived from one of the following values: gsh_alt_order_lod_subsampling_enabled, tile_alt_order_lod_subsampling_enabled[ i ], tps_alt_order_lod_subsampling_enabled, gps_alt_order_lod_subsampling_enabled, sps_alt_order_lod_subsampling_enabled.

[0423] Figure 30 shows an attribute data header according to embodiments.

[0424] Fig. 30, like Fig. 29, shows the syntax of the alternative order time subsampling related option information of the attribute data header in Fig. 18.

[0425] Attribute parameter set ID (abh_attr_parameter_set_id): Indicates the abh_attr_parameter_set_id value of the active APS.

[0426] Attribute Sequence Parameter Set Attribute Index (abh_attr_sps_attr_idx): Indicates the attribute set of the active SPS. The abh_attr_sps_attr_idx value ranges from 0 to sps_num_attribute_sets in the active SPS.

[0427] Attribute Geometry Slice ID (abh_attr_geom_slice_id): Indicates the gsh_slice_id value of the active geometry slice header.

[0428] Enable Alternative Order LoD Subsampling (abh_alt_order_lod_subsampling_enabled): Indicates whether to use alternative order based subsampling for the current slice. If abh_alt_order_lod_subsampling_enabled is 0, it can be derived from one of the following values: gsh_alt_order_lod_subsampling_enabled, tile_alt_order_lod_subsampling_enabled[ i ], tps_alt_order_lod_subsampling_enabled, gps_alt_order_lod_subsampling_enabled, sps_alt_order_lod_subsampling_enabled.

[0429] Alternative order LoD subsampling type (abh_alt_order_lod_subsampling_type: Indicates which type of alternative order based subsampling to use for the current slice. If abh_alt_order_lod_subsampling_type is not signaled, it can be derived as 0.

[0430] Figure 31 shows an encoding method according to embodiments.

[0431] The encoding method according to the embodiments includes a step of encoding geometry data of point cloud data (S3100); and / or a step of encoding attribute data of point cloud data (S3110).

[0432] Referring to FIGS. 12 and 13, the step of encoding attribute data (S3110) includes: generating a level of detail (LoD) based on points of point cloud data, wherein a second level of LoD can be generated by subsampling one or more points of a first level. Here, a level index of the second level can have a larger value than a level index of the first level. The first level can mean a finer level than the second level.

[0433] With respect to Figure 13 and LoD generation, the first level may contain one or more points based on a canonical order with respect to the geometry data.

[0434] Referring to FIG. 13 and the periodic sampling LoD generation, the first level includes one or more points based on a Moulton code, and one or more points can be subsampled based on a sampling period.

[0435] The encoding method can be performed by an encoding device (encoder). The encoding device includes a memory; and at least one processor connected to the memory; and the at least one processor can be configured to: encode geometry data of point cloud data; and encode attribute data of the point cloud data.

[0436] The embodiments further include a computer-readable storage medium storing a bitstream generated by the method according to FIG. 31.

[0437] Embodiments further include a method comprising: obtaining a bitstream for point cloud data, the bitstream being generated based on a step of encoding geometry data of the point cloud data; and a step of encoding attribute data of the point cloud data; and transmitting data including the bitstream.

[0438] Figure 32 shows a decryption method according to embodiments.

[0439] A decoding method according to embodiments includes a step of decoding geometry data of point cloud data in a bitstream (S3200); and / or a step of decoding attribute data of point cloud data (S3210).

[0440] Referring to FIGS. 14 and 15 together, in relation to attribute decoding and LoD generation, the step (S3210) of decoding attribute data includes: generating a LoD (level of Detail) based on a point of point cloud data, wherein a second level of LoD can be generated by subsampling one or more points of a first level. Here, a level index of the second level can have a larger value than a level index of the first level. The first level can mean a finer level than the second level.

[0441] Referring to Fig. 16, in relation to LoD generation, points of a fine level of LoD are subsampled to generate a coarser level, and one or more points may be subsampled based on a list of canonical orders of geometric data. Points are subsampled based on the values ​​of a list in which the order (index) of points is stored according to the canonical order of geometric data.

[0442]

[0443] Referring to FIG. 17 and the periodic sampling LoD generation, the first level includes one or more points based on a Moulton code, and one or more points can be subsampled based on a sampling period.

[0444] Referring to FIG. 17 and other sequence-based periodic sampling, the subsampling step includes: subsampling one or more points based on a standard order and sampling period other than a Morton code, wherein the standard order may not be a sort order with respect to the Morton code of the points of the current level of the LoD. In terms of not being a Morton code-based sort order, the standard order refers to the order of points output by decoding the geometry data. In addition, one or more points may be subsampled based on index information about the points with respect to the standard order. Accordingly, the attribute decoder (or encoder, if applicable) can generate the LoD through subsampling and generate levels based on the reconstructed geometry (points). Here, the points have a current sorted order, and the attribute decoder (or encoder, which is the same) according to the embodiment can subsample the points at each sampling period based on an order other than the current sorted order of the points (which is called a canonical order). The canonical order can mean the order of the points output by the geometry decoding (or geometry decoder). The attribute decoder (or encoder, which is the same) can generate the LoD based on the sampling period in the canonical order output by the geometry decoding (decoder) without reordering the points of the restored geometry data based on the Moulton code.

[0445] Referring to Fig. 17 and the sampling period, one or more points are subsampled based on the sampling period in the LoD, and the bitstream may include information about the sampling period. In addition, the sampling period may be derived based on a value about the sampling period of a LoD (e.g., LvI-1) having an index that is smaller than the index of the current LoD (e.g., LvI). For example, the sampling period may be derived by multiplying the sampling period of a LoD (e.g., LvI-1) having an index that is smaller than the index of the current LoD (e.g., LvI) by the sampling period of the current LoD. For example, if there are four LoD levels, the sampling periods for levels 1 through 4 may be received from the encoder to the decoder as values ​​of 4, 4, 4, 4. The decoder can derive the sampling period for level 1 as 4, the sampling period for level 2 as 4*4=16, the sampling period for level 3 as 4*4*4=64, and the sampling period for level 4 as 4*4*4*4=256.

[0446] Referring to alt_order_lod_subsampling_enabled in Fig. 20, the bitstream may include information indicating whether subsampling is performed based on a standard order.

[0447] The decryption method may be performed by a decryption device (decoder). The decryption device includes a memory; and at least one processor connected to the memory; and the at least one processor may be configured to: decode geometry data of point cloud data in a bitstream; and decode attribute data of the point cloud data.

[0448] The method and device according to the embodiments provide the following technical effects.

[0449] Applying a uniform sampling method to spinning lidar point clouds can improve the compression efficiency of the lifting transform. Specifically, uniform LOD generation improves inter-LOD prediction performance. This improved prediction performance generates relatively small residual signals, enabling point cloud compression with fewer bits for the same error.

[0450] Accordingly, the transmission method / device according to the embodiments can efficiently compress point cloud data to transmit the data, and by transmitting signaling information for this, the reception method / device according to the embodiments can also efficiently decode / restore point cloud data.

[0451] The embodiments have been described in terms of methods and / or devices, and the descriptions of methods and devices may be applied complementarily.

[0452] For the convenience of explanation, each drawing has been described separately, but it is also possible to design a new embodiment by combining the embodiments described in each drawing. In addition, designing a computer-readable recording medium having a program recorded thereon for executing the previously described embodiments, as needed by a person skilled in the art, also falls within the scope of the embodiments. The devices and methods according to the embodiments are not limited to the configurations and methods of the embodiments described above, but the embodiments may be configured by selectively combining all or part of the embodiments so that various modifications can be made. Although preferred embodiments of the embodiments have been illustrated and described, the embodiments are not limited to the specific embodiments described above, and various modifications can be made by a person skilled in the art to which the present invention pertains without departing from the gist of the embodiments claimed in the claims, and such modifications should not be understood individually from the technical idea or prospect of the embodiments.

[0453] The various components of the devices of the embodiments may be implemented by hardware, software, firmware, or a combination thereof. The various components of the embodiments may be implemented by a single chip, for example, a single hardware circuit. According to embodiments, the components according to the embodiments may be implemented by separate chips. According to embodiments, at least one of the components of the devices of the embodiments may be configured with one or more processors capable of executing one or more programs, and the one or more programs may perform, or include instructions for performing, one or more of the operations / methods according to the embodiments. The executable instructions for performing the methods / operations of the devices of the embodiments may be stored in non-transitory CRMs or other computer program products configured to be executed by one or more processors, or may be stored in temporary CRMs or other computer program products configured to be executed by one or more processors. In addition, the memory according to the embodiments may be used as a concept including not only volatile memory (e.g., RAM, etc.), but also non-volatile memory, flash memory, PROM, etc. Additionally, it may be implemented in the form of a carrier wave, such as transmission via the Internet. Furthermore, the processor-readable recording medium may be distributed across network-connected computer systems, allowing the processor-readable code to be stored and executed in a distributed manner.

[0454] In this document, “ / ” and “,” are interpreted as “and / or”. For example, “A / B” is interpreted as “A and / or B”, and “A, B” is interpreted as “A and / or B”. Additionally, “A / B / C” means “at least one of A, B, and / or C”. Also, “A, B, C” means “at least one of A, B, and / or C”. Additionally, “or” in this document is interpreted as “and / or”. For example, “A or B” can mean 1) “A” only, 2) “B” only, or 3) “A and B”. In other words, “or” in this document can mean “additionally or alternatively”.

[0455] Terms such as "first," "second," etc. may be used to describe various components of the embodiments. However, the various components according to the embodiments should not be interpreted as limited by these terms. These terms are merely used to distinguish one component from another. For example, a first user input signal may be referred to as a "second user input signal." Similarly, a second user input signal may be referred to as a "first user input signal." The use of these terms should be interpreted as not departing from the scope of the various embodiments. Although "first user input signal" and "second user input signal" are both user input signals, they do not mean the same user input signals unless the context clearly indicates otherwise.

[0456] The terminology used to describe the embodiments is for the purpose of describing particular embodiments and is not intended to be limiting of the embodiments. As used in the description of the embodiments and in the claims, the singular is intended to include the plural unless the context clearly dictates otherwise. The expressions “and / or” are used to mean all possible combinations of terms. The expression “includes” describes the presence of features, numbers, steps, elements, and / or components, but does not mean that additional features, numbers, steps, elements, and / or components are not included. Conditional expressions such as “if” or “when” used to describe the embodiments are not intended to be limited to only optional cases. When a specific condition is satisfied, a related action is performed in response to a specific condition, or a related definition is intended to be interpreted.

[0457] Additionally, the operations according to the embodiments described in this document may be performed by a transceiver device including a memory and / or a processor according to the embodiments. The memory may store programs for processing / controlling the operations according to the embodiments, and the processor may control various operations described in this document. The processor may be referred to as a controller, etc. The operations according to the embodiments may be performed by firmware, software, and / or a combination thereof, and the firmware, software, and / or a combination thereof may be stored in the processor or in the memory.

[0458] Meanwhile, the operations according to the embodiments described above may be performed by a transmitting device and / or a receiving device according to the embodiments. The transmitting / receiving device may include a transmitting / receiving unit for transmitting and receiving media data, a memory for storing instructions (program code, algorithm, flowchart, and / or data) for a process according to the embodiments, and a processor for controlling the operations of the transmitting / receiving device.

[0459] The processor may be referred to as a controller or the like, and may correspond to, for example, hardware, software, and / or a combination thereof. The operations according to the above-described embodiments may be performed by the processor. Furthermore, the processor may be implemented as an encoder / decoder or the like for the operations of the above-described embodiments.

[0460] As described above, the relevant contents have been described in the best form for carrying out the embodiments.

[0461] As described above, the embodiments may be applied in whole or in part to a point cloud data transmission and reception device and system.

[0462] Those skilled in the art may make various changes or modifications to the embodiments within the scope of the embodiments.

[0463] Embodiments may include modifications / changes, which do not depart from the scope of the claims and their equivalents.

Claims

1. A step of decoding geometry data of point cloud data in a bitstream; and A step of decoding attribute data of the above point cloud data; comprising; How to decrypt.

2. In paragraph 1, The steps to decode the above attribute data are: Including generating LoD (level of Detail) based on points of the above point cloud data, The second level of the above LoD is generated by subsampling one or more points of the first level. How to decrypt.

3. In paragraph 2, wherein said one or more points are subsampled based on a list of canonical orders for said geometry data; How to decrypt.

4. In paragraph 2, The above first level includes one or more points based on the Molton code, Based on the sampling period, one or more of the above points are subsampled based on the sampling period. How to decrypt.

5. In paragraph 2, The above subsampling steps are: comprising subsampling one or more of said points based on a standard order and sampling period other than the Moulton code; The above standard order is not a sort order with respect to the Molton code of the points of the current level of the LoD. The above standard order is the order of points output by decoding the above geometry data. wherein said one or more points are subsampled based on index information about said points in said standard order; How to decrypt.

6. In paragraph 2, The above one or more points are subsampled based on a sampling period in the LoD, The bitstream contains information about the sampling period, or The above sampling period is derived based on the value of the sampling period of the LoD having an index smaller than the index of the current LoD. How to decrypt.

7. In paragraph 5, The bitstream includes information indicating whether the subsampling is performed based on the standard order. How to decrypt.

8. Memory; and At least one processor connected to the memory; wherein the at least one processor comprises: Decoding geometry data of point cloud data in the bitstream; and Decoding attribute data of the above point cloud data; configured to do so; Decryption device.

9. A step of encoding the geometry data of the point cloud data; and A step of encoding attribute data of the above point cloud data; comprising; Encoding method.

10. In paragraph 9, The steps for encoding the above attribute data are: Including generating LoD (level of Detail) based on points of the above point cloud data, The second level of the above LoD is generated by subsampling one or more points of the first level. Encoding method.

11. In paragraph 10, The first level above includes one or more points based on a canonical order with respect to the geometry data. Encoding method.

12. In paragraph 10, The above first level includes one or more points based on the Molton code, Based on the sampling period, one or more of the above points are subsampled based on the sampling period. Encoding method.

13. Memory; and At least one processor connected to the memory; wherein the at least one processor comprises: Encoding the geometry data of point cloud data; and Encoding attribute data of the above point cloud data; configured to do so; Encoding device.

14. A computer-readable storage medium storing a bitstream generated by the method according to Article 9.

15. Step of obtaining bitstream for point cloud data; The bitstream is generated based on the steps of encoding geometry data of the point cloud data; and encoding attribute data of the point cloud data; and A method comprising the step of transmitting data including the bitstream.

Images