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

By encoding and decoding point cloud data, combined with the inter-frame attribute compression technology of prediction tree and laser ID, the problem of low point cloud data transmission efficiency is solved and the quality of virtual reality and self-driving services is improved.

CN118975255APending Publication Date: 2024-11-15LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380031450.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-11-02
Filing Date
2023-03-02
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

The prior art is difficult to efficiently process and transmit large amounts of point cloud data, resulting in high latency and encoding/decoding complexity, affecting the quality of services such as virtual reality, augmented reality and self-driving.

Method used

A method is adopted to encode point cloud data and send bit streams, decode the receiver, and use prediction tree and laser ID to compress inter-frame attributes to improve the transmission efficiency of point cloud data.

Benefits of technology

It realizes efficient processing and transmission of point cloud data, reduces latency and coding complexity, and improves the quality of services such as virtual reality and self-driving.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118975255A_ABST
    Figure CN118975255A_ABST
Patent Text Reader

Abstract

A point cloud data transmission method according to an embodiment may comprise the steps of: encoding point cloud data; and transmitting the bit stream including the point cloud data. A point cloud data receiving method according to an embodiment may comprise the steps of: receiving a bitstream including point cloud data; and decoding the point cloud data.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] Point cloud content is represented by a point cloud, which is a collection of points belonging to a coordinate system representing three-dimensional space. Point cloud content can express media configured in three dimensions and is used to provide various services such as virtual reality (VR), augmented reality (AR), mixed reality (MR), and self-driving services. However, tens to hundreds of thousands of points of data are required to represent point cloud content. Therefore, a method for efficiently processing large amounts of point data is needed. Summary of the Invention

[0003] Technical issues

[0004] Embodiments provide an apparatus and method for efficiently processing point cloud data. Embodiments provide a method and apparatus for processing point cloud data to address latency and encoding / decoding complexity.

[0005] The technical scope of the embodiments is not limited to the above-mentioned technical objectives, and may encompass other technical objectives that can be inferred by those skilled in the art based on the entire content disclosed herein.

[0006] Technical Solution

[0007] To achieve these objectives and other advantages, and in accordance with the purposes of the present disclosure, as embodied and broadly described herein, a method for transmitting point cloud data may include the steps of: encoding the point cloud data; and transmitting a bitstream containing the point cloud data. In another aspect of the present disclosure, a method for receiving point cloud data may include the steps of: receiving a bitstream containing the point cloud data; and decoding the point cloud data.

[0008] Beneficial effects

[0009] The apparatus and method according to the embodiment can efficiently process point cloud data.

[0010] The apparatus and method according to the embodiment can provide high-quality point cloud services.

[0011] The apparatus and method according to the embodiment may provide point cloud content for providing general services such as VR services and self-driving services. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings are included to provide a further understanding of the present disclosure and are incorporated into and constitute a part of this application. The drawings illustrate embodiments of the present disclosure and, together with the description, serve to illustrate the principles of the present disclosure. 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 accompanying drawings. The same reference numerals will be used throughout the drawings to represent the same or similar parts. In the drawings:

[0013] Figure 1 An exemplary point cloud content providing system according to an embodiment is shown.

[0014] Figure 2 is a block diagram illustrating a point cloud content providing operation according to an embodiment.

[0015] Figure 3 An exemplary process for capturing point cloud video according to an embodiment is illustrated.

[0016] Figure 4 An exemplary point cloud encoder according to an embodiment is illustrated.

[0017] Figure 5 An example of a voxel according to an embodiment is shown.

[0018] Figure 6 Examples of octrees and occupancy codes are shown, according to an embodiment.

[0019] Figure 7 An example of a neighbor node pattern according to an embodiment is shown.

[0020] Figure 8 An example of point configuration in each LOD according to an embodiment is illustrated.

[0021] Figure 9 An example of point configuration in each LOD according to an embodiment is illustrated.

[0022] Figure 10 A point cloud decoder according to an embodiment is illustrated.

[0023] Figure 11 A point cloud decoder according to an embodiment is illustrated.

[0024] Figure 12 A transmitting device according to an embodiment is illustrated.

[0025] Figure 13 A receiving device according to an embodiment is illustrated.

[0026] Figure 14 An exemplary structure that can operate in conjunction with the point cloud data transmitting / receiving method / apparatus according to an embodiment is illustrated.

[0027] Figure 15 A method for generating a prediction tree structure according to an embodiment is illustrated;

[0028] Figure 16 Illustrate inter-frame encoding / decoding according to an embodiment;

[0029] Figure 17 A method for selecting a predictor node in a reference frame based on a laser ID (laserID) according to an embodiment is illustrated;

[0030] Figure 18 A point cloud data transmitting device according to an embodiment is illustrated;

[0031] Figure 19 A point cloud data receiving device according to an embodiment is illustrated;

[0032] Figure 20 illustrates a bitstream containing a point cloud and parameters according to an embodiment;

[0033] Figure 21 illustrates a sequence parameter set according to an embodiment;

[0034] Figure 22 illustrates a tile parameter set according to an embodiment;

[0035] Figure 23 illustrates a geometry parameter set, an attribute parameter set, and a geometry slice header according to an embodiment;

[0036] Figure 24 A method of transmitting point cloud data according to an embodiment is illustrated;

[0037] Figure 25 A method of receiving point cloud data according to an embodiment is illustrated. DETAILED DESCRIPTION

[0038] Reference will now be made in detail to preferred embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. The detailed description given below with reference to the accompanying drawings is intended to illustrate exemplary embodiments of the present disclosure and is not intended to illustrate the only embodiments that can be implemented according to the present disclosure. The following detailed description includes specific details in order to provide a thorough understanding of the present disclosure. However, it will be apparent to those skilled in the art that the present disclosure can be practiced without these specific details.

[0039] Although most of the terms used in this disclosure are selected from common terms widely used in the art, some terms are arbitrarily selected by the applicant and their meanings are explained in detail in the following description as needed. Therefore, this disclosure should be understood based on the intended meaning of the terms rather than their simple names or meanings.

[0040] Figure 1An exemplary point cloud content providing system according to an embodiment is shown.

[0041] Figure 1 The illustrated point cloud content providing system may include a transmitting device 10000 and a receiving device 10004. The transmitting device 10000 and the receiving device 10004 may be capable of wired or wireless communication to transmit and receive point cloud data.

[0042] According to an embodiment, the point cloud data transmitting device 10000 can obtain and process point cloud video (or point cloud content) and transmit it. According to an embodiment, the transmitting device 10000 may 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. According to an embodiment, the transmitting device 10000 may include a device configured to communicate with a base station and / or other wireless devices using a radio access technology (e.g., 5G New RAT (NR), Long Term Evolution (LTE)), a robot, a vehicle, an AR / VR / XR device, a portable device, a home appliance, an Internet of Things (IoT) device, and an AI device / server.

[0043] According to an embodiment, the sending device 10000 includes a point cloud video acquirer 10001, a point cloud video encoder 10002 and / or a transmitter (or communication module) 10003.

[0044] The point cloud video acquirer 10001 according to an embodiment acquires a point cloud video through a process such as capture, synthesis, or generation. A point cloud video is point cloud content represented by a point cloud. A point cloud is a collection of points located in 3D space and can be referred to as point cloud video data. A point cloud video according to an embodiment may include one or more frames. A frame represents a still image / screen. Therefore, a point cloud video may include point cloud images / frames / screens and may be referred to as a point cloud image, frame, or screen.

[0045] The point cloud video encoder 10002 according to an embodiment encodes the acquired point cloud video data. The point cloud video encoder 10002 may encode the point cloud video data based on point cloud compression coding. The point cloud compression coding according to an embodiment may include geometry-based point cloud compression (G-PCC) coding and / or video-based point cloud compression (V-PCC) coding or next-generation coding. The point cloud compression coding according to an embodiment is not limited to the above-mentioned embodiment. The point cloud video encoder 10002 may output a bit stream containing the encoded point cloud video data. The bit stream may include not only the encoded point cloud video data but also signaling information related to the encoding of the point cloud video data.

[0046] According to an embodiment, the transmitter 10003 transmits a bitstream containing encoded point cloud video data. According to an embodiment, the bitstream is encapsulated in a file or segment (e.g., a stream segment) and transmitted via various networks such as a broadcast network and / or a broadband network. Although not shown in the figure, the transmitting device 10000 may include an encapsulator (or encapsulation module) configured to perform an encapsulation operation. According to an embodiment, the encapsulator may be included in the transmitter 10003. According to an embodiment, the file or segment may be transmitted to the receiving device 10004 via a network or stored in a digital storage medium (e.g., USB, SD, CD, DVD, Blu-ray, HDD, SSD, etc.). According to an embodiment, the transmitter 10003 is capable of wired / wireless communication with the receiving device 10004 (or receiver 10005) via a 4G, 5G, 6G, etc. network. In addition, the transmitter may perform necessary data processing operations according to the network system (e.g., a 4G, 5G, or 6G communication network system). The transmitting device 10000 may transmit the encapsulated data on demand.

[0047] The receiving device 10004 according to an embodiment includes a receiver 10005, a point cloud video decoder 10006, and / or a renderer 10007. According to an embodiment, the receiving device 10004 may include a device configured to communicate with a base station and / or other wireless devices using a radio access technology (e.g., 5G New RAT (NR), Long Term Evolution (LTE)), a robot, a vehicle, an AR / VR / XR device, a portable device, a home appliance, an Internet of Things (IoT) device, and an AI device / server.

[0048] The receiver 10005 according to the embodiment receives a bitstream containing point cloud video data or a file / segment encapsulated with a bitstream from a network or a storage medium. The receiver 10005 may perform necessary data processing according to a network system (e.g., a communication network system of 4G, 5G, 6G, etc.). The receiver 10005 according to the embodiment may decapsulate the received file / segment and output a bitstream. According to the embodiment, the receiver 10005 may include a decapsulator (or decapsulation module) configured to perform a decapsulation operation. The decapsulator may be implemented as an element (or component) separate from the receiver 10005.

[0049] The point cloud video decoder 10006 decodes the bitstream containing the point cloud video data. The point cloud video decoder 10006 can decode the point cloud video data according to the method by which the point cloud video data was encoded (e.g., by performing the inverse process of the operation of the point cloud video encoder 10002). Therefore, the point cloud video decoder 10006 can decode the point cloud video data by performing point cloud decompression encoding (the inverse process of point cloud compression). Point cloud decompression encoding includes G-PCC encoding.

[0050] The renderer 10007 renders the decoded point cloud video data. The renderer 10007 may output the point cloud content by rendering not only the point cloud video data but also the audio data. Depending on the embodiment, the renderer 10007 may include a display configured to display the point cloud content. Depending on the embodiment, the display may be implemented as a separate device or component rather than being included in the renderer 10007.

[0051] The arrow indicated by the dotted line in the figure represents the transmission path of the feedback information obtained by the receiving device 10004. Feedback information is information reflecting the interactivity with the user consuming the point cloud content, and includes information about the user (e.g., head orientation information, viewport information, etc.). Specifically, when the point cloud content is content for a service that requires interaction with the user (e.g., a self-driving service, etc.), the feedback information can be provided to the content sender (e.g., the sending device 10000) and / or the service provider. Depending on the embodiment, the feedback information may be used in the receiving device 10004 and the sending device 10000, or may not be provided.

[0052] According to an embodiment, head orientation information refers to information regarding the user's head position, orientation, angle, movement, and the like. According to an embodiment, the receiving device 10004 may calculate viewport information based on the head orientation information. Viewport information may be information regarding the area of ​​the point cloud video being viewed by the user. The viewpoint is the point through which the user views the point cloud video and may refer to the center point of the viewport area. That is, the viewport is the area centered on the viewpoint, and the size and shape of the area may be determined by the field of view (FOV). Therefore, in addition to head orientation information, the receiving device 10004 may also extract viewport information based on the vertical or horizontal FOV supported by the device. Furthermore, the receiving device 10004 may perform gaze analysis, etc., to examine how the user consumes the point cloud, the area within the point cloud video the user is gazing at, the duration of the gaze, and other factors. According to an embodiment, the receiving device 10004 may transmit feedback information including the gaze analysis results to the sending device 10000. According to an embodiment, the feedback information may be obtained during the rendering and / or display process. According to an embodiment, the feedback information may be acquired by one or more sensors included in the receiving device 10004. Depending on the implementation, the feedback information may be obtained by the renderer 10007 or a separate external element (or device, component, etc.). Figure 1The dotted line in represents the process of sending the feedback information obtained by the renderer 10007. The point cloud content providing system can process (encode / decode) the point cloud data based on the feedback information. Therefore, the point cloud video data decoder 10006 can perform a decoding operation based on the feedback information. The receiving device 10004 can send the feedback information to the sending device 10000. The sending device 10000 (or the 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 (for example, point cloud data corresponding to the user's head position) based on the feedback information instead of processing (encoding / decoding) the entire point cloud data, and provide the point cloud content to the user.

[0053] Depending on the embodiment, 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.

[0054] According to the embodiment Figure 1 Point cloud data processed in a point cloud content providing system (through a series of processes such as acquisition / encoding / transmission / decoding / rendering) may be referred to as point cloud content data or point cloud video data. Depending on the embodiment, point cloud content data may be used as a concept that encompasses metadata or signaling information related to point cloud data.

[0055] Figure 1 The elements of the illustrated point cloud content providing system may be implemented by hardware, software, a processor, and / or a combination thereof.

[0056] Figure 2 is a block diagram illustrating a point cloud content providing operation according to an embodiment.

[0057] Figure 2 The block diagram shows Figure 1 The point cloud content providing system described in

[0045] As described above, the point cloud content providing system may process point cloud data based on point cloud compression coding (eg, G-PCC).

[0058] According to an embodiment, a point cloud content providing system (e.g., a point cloud sending device 10000 or a point cloud video acquirer 10001) can acquire a point cloud video (20000). The point cloud video is represented by a point cloud belonging to a coordinate system for expressing a 3D space. According to an embodiment, a point cloud video may include a Ply (Polygon file format or Stanford Triangle format) file. When a point cloud video has one or more frames, the acquired point cloud video may include one or more Ply files. The Ply file contains point cloud data such as point geometry and / or attributes. Geometry includes the position of a point. The position of each point can be represented by parameters (e.g., X, Y, and Z axis values) representing a three-dimensional coordinate system (e.g., a coordinate system consisting of X, Y, and Z axes). Attributes include attributes of the point (e.g., information about the texture, color (YCbCr or RGB), reflectivity r, transparency, etc. of each point). A point has one or more attributes. For example, a point may have a color attribute or two attributes, color and reflectivity. Depending on the embodiment, geometry may be referred to as position, geometry information, geometry data, etc., and attribute may be referred to as attribute, attribute information, attribute data, etc. The point cloud content providing system (e.g., the point cloud transmitting device 10000 or the point cloud video acquirer 10001) may obtain point cloud data from information related to the point cloud video acquisition process (e.g., depth information, color information, etc.).

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

[0060] The point cloud content providing system according to the embodiment (eg, the transmitting device 10000 or the transmitter 10003) may transmit the encoded point cloud data (20002). Figure 1 As shown, the encoded point cloud data can be represented by a geometry bitstream and an attribute bitstream. In addition, the encoded point cloud data can be sent in the form of a bitstream together with signaling information related to the encoding of the point cloud data (e.g., signaling information related to geometry encoding and attribute encoding). The point cloud content providing system can encapsulate the bitstream carrying the encoded point cloud data and send it in the form of a file or fragment.

[0061] According to an embodiment, a point cloud content providing system (e.g., receiving device 10004 or receiver 10005) may receive a bitstream containing encoded point cloud data. In addition, the point cloud content providing system (e.g., receiving device 10004 or receiver 10005) may demultiplex the bitstream.

[0062] The point cloud content providing system (e.g., the receiving device 10004 or the point cloud video decoder 10005) can decode the encoded point cloud data (e.g., geometry bitstream, attribute bitstream) sent in the bitstream. The point cloud content providing system (e.g., the receiving device 10004 or the point cloud video decoder 10005) can decode the point cloud video data based on the signaling information related to the encoding of the point cloud video data contained in the bitstream. The point cloud content providing system (e.g., the receiving device 10004 or the point cloud video decoder 10005) can decode the geometry bitstream to reconstruct the position (geometry) of the point. The point cloud content providing system can reconstruct the attributes of the point by decoding the attribute bitstream based on the reconstructed geometry. The point cloud content providing system (e.g., the receiving device 10004 or the point cloud video decoder 10005) can reconstruct the point cloud video based on the position according to the reconstructed geometry and the decoded attributes.

[0063] According to an embodiment, a point cloud content providing system (e.g., receiving device 10004 or renderer 10007) can render the decoded point cloud data (20004). The point cloud content providing system (e.g., receiving device 10004 or renderer 10007) can use various rendering methods to render the geometry and attributes decoded by the decoding process. Points in the point cloud content can be rendered as vertices with a specific thickness, cubes with a specific minimum size centered at the corresponding vertex position, or circles centered at the corresponding vertex position. All or part of the rendered point cloud content is provided to the user via a display (e.g., a VR / AR display, a general display, etc.).

[0064] According to an embodiment, the point cloud content providing system (e.g., receiving device 10004) may obtain feedback information (20005). The point cloud content providing system may encode and / or decode the point cloud data based on the feedback information. Figure 1 The feedback information and operations described are the same, so their detailed description is omitted.

[0065] Figure 3 An exemplary process of capturing point cloud video according to an embodiment is shown.

[0066] Figure 3 Show reference Figure 1 and Figure 2 An exemplary point cloud video capture process of a point cloud content providing system is described.

[0067] Point cloud content includes point cloud videos (images and / or videos) representing objects and / or environments located in various 3D spaces (e.g., 3D spaces representing real environments, 3D spaces representing virtual environments, etc.). Therefore, a point cloud content providing system according to an embodiment may use one or more cameras (e.g., an infrared camera capable of obtaining depth information, an RGB camera capable of extracting color information corresponding to the depth information, etc.), a projector (e.g., an infrared pattern projector that obtains depth information), LiDAR, etc. to capture point cloud videos. A point cloud content providing system according to an embodiment may extract a geometric shape composed of points in a 3D space from the depth information and extract attributes of each point from the color information to obtain point cloud data. Images and / or videos according to an embodiment may be captured based on at least one of an inward-facing technique and an outward-facing technique.

[0068] Figure 3 The left portion of FIG shows an inward-facing technique. Inward-facing techniques refer to techniques for capturing images of a central object using one or more cameras (or camera sensors) positioned around the central object. Inward-facing techniques can be used to generate point cloud content that provides a 360-degree image of a key object to the user (e.g., VR / AR content that provides a 360-degree image of an object (e.g., a key object such as a character, player, object, or actor) to the user).

[0069] Figure 3 The right side of the figure shows outward-facing techniques. Outward-facing techniques utilize one or more cameras (or camera sensors) positioned around a central object to capture the surroundings of the central object rather than an image of the central object. Outward-facing techniques can be used to generate point cloud content that provides the surrounding environment as it appears from the user's perspective (e.g., content representing the external environment that can be provided to a user of a self-driving vehicle).

[0070] As shown in the figure, point cloud content may be generated based on a capture operation of one or more cameras. In this case, the coordinate system may be different between the cameras, so the point cloud content providing system may calibrate one or more cameras to set a global coordinate system before the capture operation. In addition, the point cloud content providing system may generate point cloud content by synthesizing arbitrary images and / or videos with the images and / or videos captured by the above-mentioned capture technology. The point cloud content providing system may not perform a point cloud operation when generating point cloud content representing a virtual space. Figure 3 The point cloud content providing system according to an embodiment may perform post-processing on the captured image and / or video. In other words, the point cloud content providing system may remove unwanted areas (e.g., background), identify the space to which the captured image and / or video is connected, and, when there is a space hole, perform an operation to fill the space hole.

[0071] The point cloud content providing system generates a piece of point cloud content by performing coordinate transformation on points in point cloud videos acquired from various cameras. The point cloud content providing system performs coordinate transformation on the points based on the position coordinates of each camera. This allows the point cloud content providing system to generate content representing a wide range or point cloud content with a high point density.

[0072] Figure 4 An exemplary point cloud encoder is shown according to an embodiment.

[0073] Figure 4 Show Figure 1 An example of a point cloud video encoder 10002 is provided. The point cloud encoder reconstructs and encodes point cloud data (e.g., the position and / or attributes of points) to adjust the quality of the point cloud content (e.g., lossless, lossy, or near-lossless) according to network conditions or applications. When the total size of the point cloud content is large (e.g., 60 Gbps of point cloud content for 30 fps), the point cloud content providing system may not be able to stream the content in real time. Therefore, the point cloud content providing system may reconstruct the point cloud content based on the maximum target bit rate to provide the point cloud content according to the network environment, etc.

[0074] As reference Figure 1 and Figure 2 As described above, the point cloud encoder can perform both geometry encoding and attribute encoding. Geometry encoding is performed before attribute encoding.

[0075] *The point cloud encoder according to an embodiment includes a coordinate transformer (transforming coordinates) 40000, a quantizer (quantizing and removing points (voxelization)) 40001, an octree analyzer (analyzing octree) 40002 and a surface approximation analyzer (analyzing surface approximation) 40003, an arithmetic encoder (arithmetic coding) 40004, a geometry reconstructor (reconstructing geometry) 40005, a color transformer (transforming color) 40006, an attribute transformer (transforming attributes) 40007, a RAHT transformer (RAHT) 40008, an LOD generator (generating LOD) 40009, a lifting transformer (lifting) 40010, a coefficient quantizer (quantizing coefficients) 40011 and / or an arithmetic encoder (arithmetic coding) 40012.

[0076] The coordinate transformer 40000, quantizer 40001, octree analyzer 40002, surface approximation analyzer 40003, arithmetic encoder 40004, and geometry reconstructor 40005 may perform geometry coding. Geometric coding according to embodiments may include octree geometry coding, direct coding, triplet geometry coding, and entropy coding. Direct coding and triplet geometry coding may be applied selectively or in combination. Geometric coding is not limited to the above examples.

[0077] As shown in the figure, the coordinate converter 40000 according to an embodiment receives a position and converts it into coordinates. For example, the position can be converted into position information in a three-dimensional space (e.g., a three-dimensional space represented by an XYZ coordinate system). The position information in the three-dimensional space according to an embodiment can be referred to as geometric information.

[0078] The quantizer 40001 according to an embodiment quantizes the geometry. For example, the quantizer 40001 may quantize the points based on the minimum position value of all points (e.g., the minimum value on each of the X, Y, and Z axes). The quantizer 40001 performs a quantization operation by multiplying the difference between the minimum position value and the position value of each point by a preset quantization scaling value, and then finding the nearest integer value by rounding the value obtained by the multiplication. Therefore, one or more points may have the same quantized position (or position value). The quantizer 40001 according to an embodiment performs voxelization based on the quantized position to reconstruct the quantized points. As in the case of a pixel (the smallest unit containing 2D image / video information), the points of the point cloud content (or 3D point cloud video) according to an embodiment may be included in one or more voxels. As a composite of volume and pixel, the term voxel refers to a 3D cubic space generated when a 3D space is divided into units (unit = 1.0) based on the axes representing the 3D space (e.g., the X, Y, and Z axes). Quantizer 40001 can match point groups in 3D space to voxels. Depending on the embodiment, a voxel may include only one point. Depending on the embodiment, a voxel may include one or more points. To represent a voxel as a point, the position of the voxel's center can be set based on the positions of one or more points included in the voxel. In this case, the attributes of all positions included in a voxel can be combined and assigned to the voxel.

[0079] The octree analyzer 40002 according to an embodiment performs octree geometry encoding (or octree encoding) to represent voxels in an octree structure. The octree structure represents points that are matched to voxels based on an octal tree structure.

[0080] The surface approximation analyzer 40003 according to an embodiment may analyze and approximate an octree. The octree analysis and approximation according to an embodiment is a process of analyzing a region including a plurality of points to efficiently provide an octree and voxelization.

[0081] According to an embodiment, the arithmetic encoder 40004 performs entropy coding on the octree and / or approximate octree. For example, the coding scheme includes arithmetic coding. As a result of the coding, a geometry bitstream is generated.

[0082] The color converter 40006, attribute converter 40007, RAHT converter 40008, LOD generator 40009, lifting converter 40010, coefficient quantizer 40011, and / or arithmetic encoder 40012 perform attribute coding. As described above, a point may have one or more attributes. Attribute coding according to an embodiment is also applied to the attributes of a point. However, when an attribute (e.g., color) includes one or more elements, attribute coding is applied independently to each element. Attribute coding according to an embodiment includes color transform coding, attribute transform coding, region adaptive hierarchical transform (RAHT) coding, interpolation-based hierarchical nearest neighbor prediction (prediction transform) coding, and interpolation-based hierarchical nearest neighbor prediction (lifting transform) coding with an update / lifting step. Depending on the point cloud content, the above-mentioned RAHT coding, prediction transform coding, and lifting transform coding can be selectively used, or a combination of one or more coding schemes can be used. Attribute coding according to an embodiment is not limited to the above examples.

[0083] Color converter 40006 according to an embodiment performs color conversion encoding to convert the color value (or texture) included in the attribute. For example, color converter 40006 may convert the format of color information (e.g., from RGB to YCbCr). Alternatively, the operation of color converter 40006 according to an embodiment may be applied based on the color value included in the attribute.

[0084] The geometry reconstructor 40005 according to an embodiment reconstructs (decompresses) an octree and / or an approximate octree. The geometry reconstructor 40005 reconstructs the octree / voxel based on the result of analyzing the point distribution. The reconstructed octree / voxel may be referred to as reconstructed geometry (restored geometry).

[0085] The attribute converter 40007 according to an embodiment performs attribute conversion to convert attributes based on reconstructed geometry and / or locations where geometry encoding is not performed. As described above, since attributes depend on geometry, the attribute converter 40007 can convert attributes based on reconstructed geometry information. For example, based on the position value of a point included in a voxel, the attribute converter 40007 can convert the attributes of the point at that position. As described above, when the center position of a voxel is set based on the positions of one or more points included in the voxel, the attribute converter 40007 converts the attributes of one or more points. When triplet geometry encoding is performed, the attribute converter 40007 can convert attributes based on the triplet geometry encoding.

[0086] The attribute converter 40007 can perform attribute conversion by calculating the average of the attributes or attribute values ​​(e.g., the color or reflectivity of each point) of neighboring points within a specific position / radius from the center position (or position value) of each voxel. The attribute converter 40007 can apply weights based on the distance from the center to each point when calculating the average. Thus, each voxel has a position and a calculated attribute (or attribute value).

[0087] The attribute converter 40007 can search for neighboring points within a specific position / radius from the center position of each voxel based on a KD tree or a Morton code. The KD tree is a binary search tree and supports a data structure capable of managing points based on position, so that a nearest neighbor search (NNS) can be performed quickly. The Morton code is generated by presenting the coordinates (e.g., (x, y, z)) representing the 3D positions of all points as bit values ​​and mixing the bits. For example, when the coordinates representing the point position are (5, 9, 1), the bit values ​​of the coordinates are (0101, 1001, 0001). Mixing the bit values ​​in the order of z, y, and x according to the bit index produces 010001000111. This value is represented as a decimal number 1095. That is, the Morton code value of the point with coordinates (5, 9, 1) is 1095. The attribute converter 40007 can sort the points based on the Morton code value and perform NNS through a depth-first traversal process. After the attribute transformation operation, KD tree or Morton code is used when NNS is needed in another transformation process for attribute encoding.

[0088] As shown, the transformed attributes are input to the RAHT transformer 40008 and / or the LOD generator 40009.

[0089] The RAHT transformer 40008 according to an embodiment performs RAHT encoding for predicting attribute information based on the reconstructed geometric information. For example, the RAHT transformer 40008 may predict attribute information of a higher-level node in the octree based on attribute information associated with a lower-level node in the octree.

[0090] According to an embodiment, LOD generator 40009 generates a level of detail (LOD) to perform predictive transform coding. According to an embodiment, LOD is the degree of detail of the point cloud content. As the LOD value decreases, the detail of the point cloud content degrades. As the LOD value increases, the detail of the point cloud content increases. Points can be categorized by LOD.

[0091] The lifting transformer 40010 according to an embodiment performs lifting transform coding that transforms point cloud attributes based on weights. As described above, lifting transform coding can be optionally applied.

[0092] The coefficient quantizer 40011 according to the embodiment quantizes the attribute of the attribute encoding based on the coefficient.

[0093] The arithmetic encoder 40012 according to the embodiment encodes quantized properties based on arithmetic coding.

[0094] Although not shown in the figure, Figure 4 The elements of the point cloud encoder 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. The one or more processors may perform the above Figure 4 In addition, one or more processors may be operable or executable to perform at least one of the operations and / or functions of the elements of the point cloud encoder. Figure 4 The one or more memories of the embodiment 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).

[0095] Figure 5 An example of a voxel according to an embodiment is shown.

[0096] Figure 5 The voxels are shown in a 3D space represented by a coordinate system consisting of three axes (X axis, Y axis and Z axis). Figure 4 As described above, the point cloud encoder (e.g., quantizer 40001) may perform voxelization. A voxel refers to a 3D cubic space generated by dividing a 3D space into units (unit=1.0) based on axes representing the 3D space (e.g., X-axis, Y-axis, and Z-axis). Figure 5 An example of voxels generated by an octree structure is shown, where the voxels are generated by two extreme points (0,0,0) and (2 d ,2 d ,2 d ) is recursively subdivided. A voxel consists of at least one point. The spatial coordinates of a voxel can be estimated from its positional relationship with the voxel group. As mentioned above, a voxel has properties similar to pixels in a 2D image / video (e.g., color or reflectivity). The details of the voxel are similar to those of the reference Figure 4 Those described are the same, so their description is omitted.

[0097] Figure 6 Examples of octrees and occupancy codes are shown, according to an embodiment.

[0098] As reference Figures 1 to 4As described, the point cloud content providing system (point cloud video encoder 10002) or the point cloud encoder (e.g., octree analyzer 40002) performs octree geometry encoding (or octree encoding) based on the octree structure to efficiently manage the area and / or position of voxels.

[0099] Figure 6 The upper part of FIG shows the octree structure. The 3D space of the point cloud content according to the embodiment is represented by the axes (eg, X-axis, Y-axis, and Z-axis) of the coordinate system. The octree structure is represented by the two poles (0,0,0) and (2 d ,2 d ,2 d ) to create an octree structure. Here, 2 d It can be set to the value of the minimum bounding box that surrounds all points of the point cloud content (or point cloud video). Here, d represents the depth of the octree. The value of d is determined in the following formula. In the following formula, (x int n ,y int n ,z int n ) represents the position (or position value) of the quantized point.

[0100]

[0101] like Figure 6 As shown in the middle of the upper part of , the entire 3D space can be divided into eight spaces according to the partition. Each divided space is represented by a cube with six faces. Figure 6 As shown in the upper right portion of the octree, each of the eight spaces is further divided based on the axes of the coordinate system (e.g., X-axis, Y-axis, and Z-axis). Thus, each space is divided into eight smaller spaces. Each of the divided smaller spaces is also represented by a cube with six faces. This partitioning scheme is applied until the leaf nodes of the octree become voxels.

[0102] Figure 6 The lower part shows the octree occupancy code. The occupancy code of the octree is generated to indicate whether each of the eight divided spaces generated by dividing one space contains at least one point. Therefore, a single occupancy code is represented by eight child nodes. Each child node represents the occupancy of the divided space, and the child node has a 1-bit value. Therefore, the occupancy code is represented as an 8-bit code. That is, when the space corresponding to the child node contains at least one point, the node is assigned a value of 1. When the space corresponding to the child node does not contain a point (the space is empty), the node is assigned a value of 0. Since Figure 6The occupancy code shown is 00100001, indicating 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 figure, each of the third and eighth child nodes has eight child nodes, and the child nodes are represented by 8-bit occupancy codes. The accompanying figure shows that the occupancy code of the third child node is 10000111, and the occupancy code of the eighth child node is 01001111. The point cloud encoder according to the embodiment (e.g., the arithmetic encoder 40004) may perform entropy coding on the occupancy code. In order to increase compression efficiency, the point cloud encoder may perform intra-frame / inter-frame coding on the occupancy code. The receiving device according to the embodiment (e.g., the receiving device 10004 or the point cloud video decoder 10006) reconstructs the octree based on the occupancy code.

[0103] According to an embodiment of the point cloud encoder (e.g., Figure 4 The point cloud encoder or octree analyzer 40002 may perform voxelization and octree encoding to store point locations. However, points are not always evenly distributed in 3D space, so there may be specific areas with fewer points. Therefore, performing voxelization on the entire 3D space is inefficient. For example, when a specific area contains very few points, voxelization does not need to be performed in that specific area.

[0104] Therefore, for the above-mentioned specific area (or nodes other than the leaf nodes of the octree), the point cloud encoder according to the embodiment may skip voxelization and perform direct encoding to directly encode the point positions included in the specific area. The coordinates of the directly encoded points according to the embodiment are called direct coding mode (DCM). The point cloud encoder according to the embodiment may also perform triplet geometry encoding based on the surface model, which is to reconstruct the point positions in the specific area (or node) based on voxels. Triplet geometry encoding is a geometry encoding that represents an object as a series of triangular meshes. Therefore, the point cloud decoder can generate a point cloud from the mesh surface. Direct encoding and triplet geometry encoding according to the embodiment can be performed selectively. In addition, direct encoding and triplet geometry encoding according to the embodiment can be performed in combination with octree geometry encoding (or octree encoding).

[0105] To perform direct encoding, the option to use direct mode to apply direct encoding should be enabled. The node to which direct encoding is to be applied is not a leaf node, and there should be less than a threshold number of points within the specific node. In addition, the total number of points to which direct encoding is to be applied should not exceed a preset threshold. When the above conditions are met, the point cloud encoder (or arithmetic encoder 40004) according to the embodiment can perform entropy encoding on the point position (or position value).

[0106] A point cloud encoder according to an embodiment (e.g., a surface approximation analyzer 40003) may determine a specific level of the octree (a level less than the depth d of the octree), and may use a surface model starting from this level to perform triplet geometry encoding to reconstruct the point positions in the node area based on voxels (triplet mode). A point cloud encoder according to an embodiment may specify the level to which triplet geometry encoding is to be applied. For example, when the specific level is equal to the depth of the octree, the point cloud encoder does not operate in triplet mode. In other words, the point cloud encoder according to an embodiment may operate in triplet mode only when the specified level is less than the depth value of the octree. A 3D cubic area of ​​a node at a specified level according to an embodiment is called a block. A block may include one or more voxels. A block or voxel may correspond to a block. The geometry is represented as a surface within each block. A surface according to an embodiment may intersect each edge of the block at most once.

[0107] A block has 12 edges, so there are at least 12 intersections within a block. Each intersection is called a vertex. Vertices along an edge are detected when there is at least one occupied voxel adjacent to the edge across all blocks that share the edge. An occupied voxel, according to embodiments, refers to a voxel containing a point. The vertex position detected along an edge is the average position of all voxels adjacent to the edge across all blocks along the edge.

[0108] Once the vertex is detected, the point cloud encoder according to an embodiment may perform entropy encoding on the edge start point (x, y, z), the edge direction vector (Δx, Δy, Δz), and the vertex position value (relative position value within the edge). When triplet geometry encoding is applied, the point cloud encoder according to an embodiment (e.g., geometry reconstructor 40005) may generate recovered geometry (reconstructed geometry) by performing triangle reconstruction, upsampling, and voxelization processes.

[0109] Vertices located at the edges of a block define a surface that passes through the block. The surface according to an embodiment is a non-planar polygon. During triangle reconstruction, the surface represented by the triangles is reconstructed based on the starting points of the edges, the direction vectors of the edges, and the position values ​​of the vertices. The triangle reconstruction process is performed by i) calculating the centroid value of each vertex, ii) subtracting the centroid value from each vertex value, and iii) estimating the sum of the squares of the values ​​obtained by the subtraction.

[0110]

[0111] The minimum value of the sum is estimated, and the projection process is performed along the axis with the minimum value. For example, when the element x is the smallest, each vertex is projected onto the x-axis relative to the center of the block and onto the (y,z) plane. When the value obtained by projection onto the (y,z) plane is (ai,bi), the value of θ is estimated by atan2(bi,ai), and the vertices are sorted based on the value of θ. The following table shows the vertex combinations that create triangles based on the number of vertices. The vertices are sorted from 1 to n. The following table shows that for four vertices, two triangles can be constructed based on the vertex combinations. The first triangle can be composed of vertices 1, 2, and 3 among the sorted vertices, and the second triangle can be composed of vertices 3, 4, and 1 among the sorted vertices.

[0112] Table 2-1. Triangles formed from vertices sorted 1,…,n

[0113] n triangle

[0114] 3(1,2,3)

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

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

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

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

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

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

[0121] 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)

[0122] 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)

[0123] 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)

[0124] An upsampling process is performed to add points in the middle along the edges of the triangle, and voxelization is performed. The added points are generated based on the upsampling factor and the width of the block. The added points are called refinement vertices. The point cloud encoder according to an embodiment may voxelize the refinement vertices. In addition, the point cloud encoder may perform attribute encoding based on the voxelized positions (or position values).

[0125] Figure 7 An example of a neighbor node pattern according to an embodiment is shown.

[0126] In order to increase the compression efficiency of the point cloud video, the point cloud encoder according to an embodiment may perform entropy encoding based on context-adaptive arithmetic coding.

[0127] As reference Figures 1 to 6 As described, the point cloud content providing system or point cloud encoder (eg, point cloud video encoder 10002, Figure 4 The point cloud encoder or arithmetic encoder 40004) may immediately perform entropy coding on the occupancy code. In addition, the point cloud content providing system or the point cloud encoder may perform entropy coding (intra-frame coding) based on the occupancy code of the current node and the occupancy of the neighboring nodes, or perform entropy coding (inter-frame coding) based on the occupancy code of the previous frame. The frame representation according to the embodiment is a collection of point cloud videos generated simultaneously. The compression efficiency of the intra-frame coding / inter-frame coding according to the embodiment may depend on the number of neighboring nodes referenced. When the number of bits increases, the operation becomes complicated, but the coding can be biased to one side, which can increase the compression efficiency. For example, when a 3-bit context is given, 2 bits need to be used. 3 = 8 ways to perform encoding. The division of parts for encoding affects the implementation complexity. Therefore, it is necessary to meet the appropriate level of compression efficiency and complexity.

[0128] Figure 7 The process of obtaining an occupancy pattern based on the occupancy of neighbor nodes is shown. According to an embodiment, a point cloud encoder determines the occupancy of neighbor nodes of each node of an octree and obtains the value of a neighbor pattern. The neighbor node pattern is used to infer the occupancy pattern of the node. Figure 7 The upper portion of the diagram shows the cube corresponding to the node (the middle cube) and the six cubes (neighboring nodes) that share at least one face with it. The nodes shown in the diagram are at the same depth. The numbers in the diagram represent the weights associated with the six nodes (1, 2, 4, 8, 16, and 32), respectively. Weights are assigned sequentially based on the positions of neighboring nodes.

[0129] Figure 7 The lower part shows the neighbor node pattern value. The neighbor node pattern value is the sum of the values ​​multiplied by the weights of the occupied neighbor nodes (neighbor nodes with points). Therefore, the neighbor node pattern value is 0 to 63. When the neighbor node pattern value is 0, it indicates that there is no node with a point among the neighbor nodes of the node (no occupied node). When the neighbor node pattern value is 63, it indicates that all neighbor nodes are occupied nodes. As shown in the figure, since the neighbor nodes assigned with weights 1, 2, 4 and 8 are occupied nodes, the neighbor node pattern value is 15 (the sum of 1, 2, 4 and 8). The point cloud encoder can perform encoding according to the neighbor node pattern value (for example, when the neighbor node pattern value is 63, 64 types of encoding can be performed). According to an embodiment, the point cloud encoder can reduce the encoding complexity by changing the neighbor node pattern value (for example, based on a table that changes 64 to 10 or 6).

[0130] Figure 8 An example of point configuration in each LOD according to an embodiment is shown.

[0131] As reference Figures 1 to 7 As described, the encoded geometry is reconstructed (decompressed) before attribute encoding is performed. When direct encoding is applied, the geometry reconstruction operation may include changing the placement of directly encoded points (e.g., placing directly encoded points in front of the point cloud data). When triplet geometry encoding is applied, the geometry reconstruction process is performed through triangle reconstruction, upsampling, and voxelization. Since attributes depend on the geometry, attribute encoding is performed based on the reconstructed geometry.

[0132] The point cloud encoder (e.g., LOD generator 40009) can classify (reorganize) points by LOD. The figure shows the point cloud content corresponding to the LOD. The leftmost frame in the figure shows the original point cloud content. The second frame from the left in the figure shows the point distribution in the lowest LOD, and the rightmost frame in the figure shows the point distribution in the highest LOD. In other words, the points in the lowest LOD are sparsely distributed, while the points in the highest LOD are densely distributed. In other words, as the LOD increases in the direction indicated by the arrow at the bottom of the figure, the space (or distance) between points becomes narrower.

[0133] Figure 9 An example of point configuration for each LOD is shown according to an embodiment.

[0134] As reference Figures 1 to 8 As described, the point cloud content providing system or point cloud encoder (eg, point cloud video encoder 10002, Figure 4The point cloud encoder or LOD generator 40009 can generate LODs. LODs are generated by reorganizing points into a set of refinement levels based on a set LOD distance value (or Euclidean distance set). The LOD generation process is performed not only by the point cloud encoder but also by the point cloud decoder.

[0135] Figure 9 The upper part of shows examples of points (P0 to P9) of point cloud contents distributed in 3D space. Figure 9 In , the original order represents the order of points P0 to P9 before LOD generation. Figure 9 In the LOD-based order, the order of points generated according to the LOD is shown. Points are reorganized by LOD. In addition, higher LODs contain points belonging to lower LODs. Figure 9 As shown, LOD0 contains P0, P5, P4, and P2. LOD1 contains the points of LOD0, P1, P6, and P3. LOD2 contains the points of LOD0, LOD1, P9, P8, and P7.

[0136] As reference Figure 4 As described, the point cloud encoder according to the embodiment may selectively or in combination perform predictive transform coding, lifting transform coding, and RAHT transform coding.

[0137] The point cloud encoder according to an embodiment may generate a predictor for each point to perform predictive transform coding for setting a predicted attribute (or predicted attribute value) for each point. That is, N predictors may be generated for N points. The predictor according to an embodiment may calculate a weight (=1 / distance) based on the LOD value of each point, index information about neighboring points within a set distance of each LOD, and the distance to the neighboring point.

[0138] The predicted attribute (or attribute value) according to the embodiment is set to the average of the values ​​obtained by multiplying the attribute (or attribute value) (e.g., color, reflectivity, etc.) of the neighboring points set in the predictor of each point by the weight (or weight value) calculated based on the distance to each neighboring point. The point cloud encoder (e.g., coefficient quantizer 40011) according to the embodiment can quantize and inverse quantize the residual (which may be referred to as residual attribute, residual attribute value, or attribute prediction residual) obtained by subtracting the predicted attribute (attribute value) from the attribute (attribute value) of each point. The quantization process is configured as shown in the following table.

[0139] Table. Pseudocode for attribute prediction residual quantization

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

[0141] if(value>=0){

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

[0143] }else{

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

[0145] }

[0146] }

[0147] Table. Pseudocode for inverse quantization of attribute prediction residuals

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

[0149] if(quantStep==0){

[0150] return value;

[0151] }else{

[0152] return value*quantStep;

[0153] }

[0154] }

[0155] When the predictor of each point has neighboring points, the point cloud encoder (e.g., the arithmetic encoder 40012) according to an embodiment may perform entropy encoding on the quantized and inverse quantized residual values ​​as described above. When the predictor of each point has no neighboring points, the point cloud encoder (e.g., the arithmetic encoder 40012) according to an embodiment may perform entropy encoding on the attributes of the corresponding point without performing the above operation.

[0156] The point cloud encoder (e.g., lifting transformer 40010) according to an embodiment may generate a predictor for each point, set the calculated LOD, register neighboring points in the predictor, and set weights according to the distances to the neighboring points to perform lifting transform encoding. The lifting transform encoding according to an embodiment is similar to the above-described predictive transform encoding, but differs in that weights are cumulatively applied to attribute values. The process of cumulatively applying weights to attribute values ​​according to an embodiment is configured as follows.

[0157] 1) Create an array called quantized weight (QW) to store the weight values ​​for each point. The initial value of all elements of QW is 1.0. Multiply the QW value of the predictor index of the neighboring node registered in the predictor by the weight of the predictor for the current point, and add the values ​​obtained by the multiplication.

[0158] 2) Boosting prediction process: The value obtained by multiplying the attribute value of the point by the weight is subtracted from the existing attribute value to calculate the predicted attribute value.

[0159] 3) Create temporary arrays called updateweight and update, and initialize the temporary arrays to zero.

[0160] 4) The weight calculated by multiplying the weight calculated for all predictors by the weight stored in the QW corresponding to the predictor index is added to the updateweight array as the index of the neighbor node. The value obtained by multiplying the attribute value of the neighbor node index by the calculated weight is added to the update array.

[0161] 5) Boosting update process: Divide the attribute values ​​of the update array of all predictors by the weight value of the updateweight array of the predictor index, and add the existing attribute value to the value obtained by division.

[0162] 6) For all predictors, the predicted attribute is calculated by multiplying the attribute value updated by the lifting update process by the weight (stored in QW) updated by the lifting prediction process. The point cloud encoder (e.g., coefficient quantizer 40011) according to an embodiment quantizes the predicted attribute value. In addition, the point cloud encoder (e.g., arithmetic encoder 40012) performs entropy encoding on the quantized attribute value.

[0163] A point cloud encoder according to an embodiment (e.g., RAHT transformer 40008) may perform RAHT transform coding, in which attributes associated with nodes at a lower level in an octree are used to predict attributes of nodes at a higher level. RAHT transform coding is an example of intra-coding of attributes by scanning backward through an octree. A point cloud encoder according to an embodiment scans the entire area starting from voxels and repeats a merging process of merging voxels into larger blocks at each step until a root node is reached. The merging process according to an embodiment is performed only on occupied nodes. The merging process is not performed on empty nodes. The merging process is performed on the upper node directly above the empty node.

[0164] The following formula represents the RAHT transformation matrix. In this formula, Represents the average attribute value of voxels at level l. Can be based on and To calculate. and The weight is and

[0165]

[0166] here, is the low-pass value and is used during the next highest level of merging. Denotes the high-pass coefficient. The high-pass coefficient of each step is quantized and subjected to entropy coding (eg, by arithmetic coder 400012). The weight is calculated as pass and Create the root node as follows.

[0167]

[0168] Figure 10 A point cloud decoder according to an embodiment is shown.

[0169] Figure 10 The point cloud decoder shown is Figure 1 An example of a point cloud video decoder 10006 described in Figure 1 The operations of the point cloud video decoder 10006 shown in FIG. 10006 are the same as or similar to those of the point cloud video decoder 10006 shown in FIG. As shown in the figure, the point cloud decoder can receive a geometry bitstream and an attribute bitstream contained in one or more bitstreams. The point cloud decoder includes a geometry decoder and an attribute decoder. The geometry decoder performs geometry decoding on the geometry bitstream and outputs decoded geometry. The attribute decoder performs attribute decoding based on the decoded geometry and attribute bitstreams and outputs decoded attributes. The decoded geometry and decoded attributes are used to reconstruct the point cloud content (decoded point cloud).

[0170] Figure 11 A point cloud decoder according to an embodiment is shown.

[0171] Figure 11 The point cloud decoder shown is Figure 10 An example of a point cloud decoder is shown, and a decoding operation can be performed, which is Figures 1 to 9 The inverse process of the encoding operation of the point cloud encoder is shown.

[0172] As reference Figure 1 and Figure 10 As described, the point cloud decoder can perform both geometry decoding and attribute decoding. Geometry decoding is performed before attribute decoding.

[0173] According to an embodiment, the point cloud decoder includes an arithmetic decoder (arithmetic decoding) 11000, an octree synthesizer (synthesize octree) 11001, a surface approximation synthesizer (synthesize surface approximation) 11002 and a geometry reconstructor (reconstruct geometry) 11003, an inverse coordinate transformer (inverse transform coordinates) 11004, an arithmetic decoder (arithmetic decoding) 11005, an inverse quantizer (inverse quantization) 11006, a RAHT transformer 11007, an LOD generator (generate LOD) 11008, an inverse lifting (inverse lifting) 11009 and / or an inverse color transformer (inverse transform color) 11010.

[0174] The arithmetic decoder 11000, the octree synthesizer 11001, the surface approximation synthesizer 11002, the geometry reconstructor 11003, and the coordinate inverse transformer 11004 may perform geometry decoding. The geometry decoding according to the embodiment may include direct decoding and triplet geometry decoding. Direct encoding and triplet geometry decoding are selectively applied. The geometry decoding is not limited to the above example, and as a reference Figures 1 to 9 The inverse process of the geometric encoding described is performed.

[0175] The arithmetic decoder 11000 according to the embodiment decodes the received geometry bitstream based on arithmetic coding. The operation of the arithmetic decoder 11000 corresponds to the inverse process of the arithmetic encoder 40004.

[0176] The octree synthesizer 11001 according to the embodiment can generate an octree by obtaining an occupancy code (or information about the geometry obtained as a result of decoding) from the decoded geometry bitstream. Figures 1 to 9 Describe the configuration in detail.

[0177] When triplet geometry encoding is applied, the surface approximation synthesizer 11002 according to an embodiment may synthesize a surface based on the decoded geometry and / or the generated octree.

[0178] The geometry reconstructor 11003 according to an embodiment may regenerate the geometry based on the surface and / or decoded geometry. Figures 1 to 9 As described, direct coding and triplet geometry coding are selectively applied. Therefore, the geometry reconstructor 11003 directly imports the position information about the points to which direct coding is applied and adds them. When triplet geometry coding is applied, the geometry reconstructor 11003 can reconstruct the geometry by performing the reconstruction operations (e.g., triangle reconstruction, upsampling, and voxelization) of the geometry reconstructor 40005. Details and References Figure 6 The reconstructed geometry may include a point cloud frame or screen that does not contain attributes.

[0179] The coordinate inverse transformer 11004 according to an embodiment may acquire a point position by transforming the coordinates based on the reconstructed geometry.

[0180] The arithmetic decoder 11005, the inverse quantizer 11006, the RAHT transformer 11007, the LOD generator 11008, the inverse lifter 11009 and / or the inverse color transformer 11010 may perform a reference Figure 10 Attribute decoding described. Attribute decoding according to an embodiment includes region adaptive hierarchical transform (RAHT) decoding, interpolation-based hierarchical nearest neighbor prediction (prediction transform) decoding, and interpolation-based hierarchical nearest neighbor prediction (lifting transform) decoding with an update / lifting step. The above three decoding schemes can be used selectively, or a combination of one or more decoding schemes can be used. Attribute decoding according to an embodiment is not limited to the above examples.

[0181] The arithmetic decoder 11005 according to the embodiment decodes the attribute bit stream through arithmetic coding.

[0182] The inverse quantizer 11006 according to an embodiment inversely quantizes information about a decoded attribute bitstream or an attribute obtained as a result of decoding, and outputs the inversely quantized attribute (or attribute value). Inverse quantization may be selectively applied based on attribute encoding of the point cloud encoder.

[0183] Depending on the embodiment, the RAHT transformer 11007, the LOD generator 11008, and / or the inverse lifter 11009 may process the reconstructed geometry and inverse quantized attributes. As described above, the RAHT transformer 11007, the LOD generator 11008, and / or the inverse lifter 11009 may selectively perform a decoding operation corresponding to the encoding of the point cloud encoder.

[0184] The color inverse converter 11010 according to an embodiment performs inverse transform encoding to inversely transform the color value (or texture) included in the decoded attribute. The operation of the color inverse converter 11010 may be selectively performed based on the operation of the color converter 40006 of the point cloud encoder.

[0185] Although not shown in the figure, Figure 11 The elements of the point cloud decoder 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. The one or more processors may execute the above Figure 11 In addition, one or more processors may be operable or executed to perform at least one or more of the operations and / or functions of the elements of the point cloud decoder. Figure 11 A software program and / or instruction set for the operation and / or functionality of the elements of the point cloud decoder.

[0186] Figure 12 A transmitting device according to an embodiment is shown.

[0187] Figure 12 The sending device shown is Figure 1 The sending device 10000 (or Figure 4 An example of a point cloud encoder. Figure 12 The sending device shown can be executed with reference to Figures 1 to 9 The transmitting apparatus according to the embodiment may include a data input unit 12000, a quantization processor 12001, a voxelization processor 12002, an octree occupancy code generator 12003, a surface model processor 12004, an intra / inter coding processor 12005, an arithmetic encoder 12006, a metadata processor 12007, a color transform processor 12008, an attribute transform processor 12009, a prediction / lifting / RAHT transform processor 12010, an arithmetic encoder 12011 and / or a transmitting processor 12012.

[0188] The data input unit 12000 according to the embodiment receives or acquires point cloud data. The data input unit 12000 may perform the same operation and / or acquisition method as the point cloud video acquirer 10001 (or refer to Figure 2 The acquisition process 20000) described above has the same or similar operations and / or acquisition methods.

[0189] The data input unit 12000, the quantization processor 12001, the voxelization processor 12002, the octree occupancy code generator 12003, the surface model processor 12004, the intra / inter coding processor 12005 and the arithmetic encoder 12006 perform geometric coding. Figures 1 to 9 The geometric encoding described is the same or similar, so its detailed description is omitted.

[0190] The quantization processor 12001 according to an embodiment quantizes geometry (e.g., position values ​​of points). The operation and / or quantization of the quantization processor 12001 are related to the reference Figure 4 The operation and / or quantization of the quantizer 40001 described above are the same or similar. Figures 1 to 9 Same as those described.

[0191] The voxelization processor 12002 according to the embodiment voxelizes the quantized position value of the point. The voxelization processor 12002 may perform the same operation as the reference. Figure 4 The operation and / or voxelization process of the quantizer 40001 described above is the same or similar to the operation and / or process described above. Figures 1 to 9 Same as those described.

[0192] The octree occupancy code generator 12003 according to the embodiment performs octree encoding on the voxelized position of the point based on the octree structure. The octree occupancy code generator 12003 can generate an occupancy code. The octree occupancy code generator 12003 can perform the octree encoding with reference to Figure 4 and Figure 6 The operations and / or methods of the point cloud encoder (or octree analyzer 40002) described herein are the same or similar to the operations and / or methods described herein. Figures 1 to 9 Same as those described.

[0193] According to an embodiment, the surface model processor 12004 may perform triplet geometry encoding based on the surface model to reconstruct the point position in a specific area (or node) based on voxels. Figure 4 The operations and / or methods of the point cloud encoder (e.g., surface approximation analyzer 40003) described herein are the same or similar to the operations and / or methods described herein. Figures 1 to 9 Same as those described.

[0194] The intra-frame / inter-frame encoding processor 12005 according to the embodiment may perform intra-frame / inter-frame encoding on the point cloud data. Figure 7 The same or similar encoding as described for intra / inter encoding. Details and references Figure 7 According to an embodiment, the intra / inter encoding processor 12005 may be included in the arithmetic encoder 12006.

[0195] According to an embodiment, arithmetic encoder 12006 performs entropy encoding on an octree and / or approximate octree of point cloud data. For example, the encoding scheme includes arithmetic coding. Arithmetic encoder 12006 performs operations and / or methods that are the same as or similar to those of arithmetic encoder 40004.

[0196] The metadata processor 12007 according to an embodiment processes metadata (e.g., set values) about the point cloud data and provides it to necessary processing processes such as geometry coding and / or attribute coding. In addition, the metadata processor 12007 according to an embodiment may generate and / or process signaling information related to geometry coding and / or attribute coding. The signaling information according to an embodiment may be encoded separately from the geometry coding and / or attribute coding. The signaling information according to an embodiment may be interleaved.

[0197] The color conversion processor 12008, the attribute conversion processor 12009, the prediction / lifting / RAHT conversion processor 12010, and the arithmetic encoder 12011 perform attribute coding. Figures 1 to 9The attribute codes described are the same or similar, so their detailed description is omitted.

[0198] The color transform processor 12008 according to an embodiment performs color transform encoding to transform the color value included in the attribute. The color transform processor 12008 may perform color transform encoding based on the reconstructed geometry. The reconstructed geometry is compared with the reference Figures 1 to 9 In addition, its execution is the same as that of reference Figure 4 The operations and / or methods of the color converter 40006 are the same as or similar to those described above, and detailed description thereof is omitted.

[0199] The attribute transformation processor 12009 according to an embodiment performs attribute transformation to transform attributes based on the reconstructed geometry and / or the location where geometry encoding is not performed. Figure 4 The operations and / or methods of the attribute converter 40007 described above are the same as or similar to those of the attribute converter 40007. Detailed description thereof is omitted. The prediction / lifting / RAHT transform processor 12010 according to the embodiment may encode the transformed attributes by any one or a combination of RAHT coding, prediction transform coding, and lifting transform coding. The prediction / lifting / RAHT transform processor 12010 performs the same as the reference. Figure 4 The operations of the RAHT transformer 40008, the LOD generator 40009 and the lifting transformer 40010 described above are identical or similar to at least one operation. In addition, the prediction transform coding, the lifting transform coding and the RAHT transform coding are the same as those of the reference Figures 1 to 9 Those described are the same, so detailed descriptions thereof are omitted.

[0200] The arithmetic encoder 12011 according to the embodiment may encode the properties of the encoding based on arithmetic coding. The arithmetic encoder 12011 performs the same or similar operations and / or methods as those of the arithmetic encoder 400012.

[0201] The transmitting processor 12012 according to the embodiment may transmit individual bitstreams containing coded geometry and / or coded attributes and metadata information, or transmit a bitstream configured with coded geometry and / or coded attributes and metadata information. When the coded geometry and / or coded attributes and metadata information according to the embodiment are configured into a bitstream, the bitstream may include one or more sub-bitstreams. The bitstream according to the embodiment may include signaling information and slice data, and the signaling information includes a sequence parameter set (SPS) for sequence level signaling, a geometry parameter set (GPS) for geometry information coding signaling, an attribute parameter set (APS) for attribute information coding signaling, and a tile parameter set (TPS) for tile level signaling. The slice data may include information about one or more slices. A slice according to the embodiment may include a geometry bitstream Geom00 and one or more attribute bitstreams Attr0 0 and Attr1 0 .

[0202] A slice is a sequence of syntactic elements that represents all or part of an encoded point cloud frame.

[0203] The TPS according to an embodiment may include information about each tile in one or more tiles (for example, coordinate information and height / size information about a bounding box). The geometry bitstream may include a header and a payload. The header of the geometry bitstream according to an embodiment may include a parameter set identifier (geom_parameter_set_id), a tile identifier (geom_tile_id) and a slice identifier (geom_slice_id) included in the GPS and information about the data contained in the payload. As described above, the metadata processor 12007 according to an embodiment may generate and / or process signaling information and send it to the transmission processor 12012. According to an embodiment, the elements that perform geometry coding and the elements that perform attribute coding may share data / information with each other as indicated by the dotted lines. The transmission processor 12012 according to an embodiment may perform operations and / or transmission methods that are the same as or similar to those of the transmitter 10003. Details and References Figure 1 and Figure 2 Those described are the same, so their description is omitted.

[0204] Figure 13 A receiving device according to an embodiment is shown.

[0205] Figure 13 The receiving device shown is Figure 1 The receiving device 10004 (or Figure 10 and Figure 11 An example of a point cloud decoder. Figure 13 The receiving device shown can execute and refer toFigures 1 to 11 One or more operations and methods that are the same or similar to those described for the point cloud decoder.

[0206] The receiving apparatus according to the embodiment may include a receiver 13000, a receiving processor 13001, an arithmetic decoder 13002, an octtree reconstruction processor based on an occupancy code 13003, a surface model processor (triangle reconstruction, upsampling, voxelization) 13004, an inverse quantization processor 13005, a metadata parser 13006, an arithmetic decoder 13007, an inverse quantization processor 13008, a prediction / lifting / RAHT inverse transform processor 13009, an inverse color transform processor 13010, and / or a renderer 13011. Each decoding element according to the embodiment may perform an inverse process of the operation of the corresponding encoding element according to the embodiment.

[0207] The receiver 13000 according to the embodiment receives point cloud data. The receiver 13000 may perform the same Figure 1 The operation and / or receiving method of the receiver 10005 are the same as or similar to the operation and / or receiving method of the receiver 10005. A detailed description thereof is omitted.

[0208] According to an embodiment, the reception processor 13001 may obtain a geometry bitstream and / or an attribute bitstream from the received data. The reception processor 13001 may be included in the receiver 13000.

[0209] The arithmetic decoder 13002, the octtree reconstruction processor 13003 based on the occupancy code, the surface model processor 13004 and the inverse quantization processor 13005 may perform geometric decoding. Figures 1 to 10 The geometric decoding described is the same or similar, so its detailed description is omitted.

[0210] The arithmetic decoder 13002 according to an embodiment may decode a geometry bitstream based on arithmetic coding. The arithmetic decoder 13002 performs operations and / or encoding that are the same as or similar to those of the arithmetic decoder 11000.

[0211] The octtree reconstruction processor 13003 based on the occupancy code according to the embodiment can reconstruct the octtree by obtaining the occupancy code from the decoded geometry bitstream (or information about the geometry obtained as a result of decoding). The octtree reconstruction processor 13003 based on the occupancy code performs the same or similar operations and / or methods as the operations of the octree synthesizer 11001 and / or the octree generation method. When triplet geometry coding is applied, the surface model processor 13004 according to the embodiment can perform triplet geometry decoding and related geometry reconstruction (e.g., triangle reconstruction, upsampling, voxelization) based on the surface model method. The surface model processor 13004 performs the same or similar operations as the operations of the surface approximation synthesizer 11002 and / or the geometry reconstructor 11003.

[0212] The inverse quantization processor 13005 according to an embodiment may inversely quantize the decoded geometry.

[0213] The metadata parser 13006 according to an embodiment may parse metadata (e.g., setting values) contained in the received point cloud data. The metadata parser 13006 may pass the metadata to the geometry decoding and / or attribute decoding. Figure 12 The metadata described are the same, so a detailed description thereof is omitted.

[0214] The arithmetic decoder 13007, the inverse quantization processor 13008, the prediction / lifting / RAHT inverse transform processor 13009 and the color inverse transform processor 13010 perform attribute decoding. Figures 1 to 10 The attribute decoding described is the same or similar, so the detailed description thereof is omitted.

[0215] According to an embodiment, the arithmetic decoder 13007 can decode the attribute bitstream through arithmetic coding. The arithmetic decoder 13007 can decode the attribute bitstream based on the reconstructed geometry. The arithmetic decoder 13007 performs the same or similar operations and / or encoding as those of the arithmetic decoder 11005.

[0216] The inverse quantization processor 13008 according to an embodiment may inversely quantize the decoded attribute bitstream. The inverse quantization processor 13008 performs the same or similar operation and / or inverse quantization method as the inverse quantizer 11006.

[0217] The prediction / lifting / RAHT inverse transform processor 13009 according to an embodiment may process the reconstructed geometry and inverse quantized attributes. The prediction / lifting / RAHT inverse transform processor 13009 performs one or more operations and / or decoding that are the same or similar to the operations and / or decoding of the RAHT converter 11007, the LOD generator 11008, and / or the inverse lifter 11009. The color inverse transform processor 13010 according to an embodiment performs inverse transform encoding to inversely transform the color values ​​(or textures) included in the decoded attributes. The color inverse transform processor 13010 performs operations and / or inverse transform encoding that are the same or similar to the operations and / or inverse transform encoding of the color inverse converter 11010. The renderer 13011 according to an embodiment may render point cloud data.

[0218] Figure 14 An exemplary structure that can be operated in conjunction with a method / apparatus for transmitting / receiving point cloud data according to an embodiment is shown.

[0219] Figure 14 The structure of 1460 represents a configuration in which at least one of the server 1460, the robot 1410, the self-driving vehicle 1420, the XR device 1430, the smartphone 1440, the home appliance 1450, and / or the head-mounted display (HMD) 1470 is connected to the cloud network 1400. The robot 1410, the self-driving vehicle 1420, the XR device 1430, the smartphone 1440, or the home appliance 1450 is referred to as a device. In addition, the XR device 1430 may correspond to a point cloud data (PCC) device according to an embodiment or may be operatively connected to a PCC device.

[0220] The cloud network 1400 may represent a network that constitutes a part of a cloud computing infrastructure or exists in a cloud computing infrastructure. Here, the cloud network 1400 may be configured using a 3G network, a 4G or Long Term Evolution (LTE) network, or a 5G network.

[0221] The server 1460 may be connected to at least one of the robot 1410 , the self-driving vehicle 1420 , the XR device 1430 , the smart phone 1440 , the home appliance 1450 , and / or the HMD 1470 via the cloud network 1400 , and may assist in at least a portion of processing of the connected devices 1410 to 1470 .

[0222] The HMD 1470 represents one of implementation types of an XR device and / or a PCC device according to an embodiment. The HMD type device according to an embodiment includes a communication unit, a control unit, a memory, an I / O unit, a sensor unit, and a power supply unit.

[0223] Hereinafter, various embodiments of devices 1410 to 1450 to which the above-described technology is applied will be described. Figure 14The illustrated devices 1410 to 1450 may be operatively connected / coupled to the point cloud data transmitting device and receiving device according to the above-described embodiments.

[0224] <PCC+XR>

[0225] The XR / PCC device 1430 may employ PCC technology and / or XR (AR+VR) technology, and may be implemented as an HMD, a head-up display (HUD) provided in a vehicle, a television, a mobile phone, a smart phone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a fixed robot, or a mobile robot.

[0226] The XR / PCC device 1430 can analyze 3D point cloud data or image data acquired through various sensors or from external devices and generate positional data and attribute data about the 3D points. Thus, the XR / PCC device 1430 can obtain information about the surrounding space or real objects and render and output XR objects. For example, the XR / PCC device 1430 can match an XR object that includes auxiliary information about the recognized object with the recognized object and output the matched XR object.

[0227] <PCC+XR+Mobile Phone>

[0228] The XR / PCC device 1430 may be implemented as a mobile phone 1440 by applying PCC technology.

[0229] The mobile phone 1440 can decode and display the point cloud content based on the PCC technology.

[0230] <PCC+Self-driving+XR>

[0231] The self-driving vehicle 1420 may be implemented as a mobile robot, a vehicle, an unmanned aerial vehicle, etc. by applying PCC technology and XR technology.

[0232] Self-driving vehicle 1420, which utilizes XR / PCC technology, may represent a self-driving vehicle equipped with a means for providing XR images, or a self-driving vehicle that serves as a control / interaction target in an XR image. Specifically, as a control / interaction target in an XR image, self-driving vehicle 1420 may be distinguished from and operatively connected to XR device 1430.

[0233] The self-driving vehicle 1420, which has a means for providing XR / PCC images, can obtain sensor information from sensors including cameras and output generated XR / PCC images based on the obtained sensor information. For example, the self-driving vehicle 1420 may have a HUD and output XR / PCC images thereto, thereby providing passengers with XR / PCC objects corresponding to real objects or objects displayed on the screen.

[0234] When an XR / PCC object is output to the HUD, at least a portion of the XR / PCC object may be output to overlap with the real object that the passenger's eyes are pointing at. On the other hand, when an XR / PCC object is output on a display provided within a self-driving vehicle, at least a portion of the XR / PCC object may be output to overlap with the object on the screen. For example, the self-driving vehicle 1220 may output XR / PCC objects corresponding to objects such as a road, another vehicle, a traffic light, a traffic sign, a two-wheeled vehicle, a pedestrian, and a building.

[0235] Virtual reality (VR) technology, augmented reality (AR) technology, mixed reality (MR) technology, and / or point cloud compression (PCC) technology according to an embodiment are applicable to various devices.

[0236] In other words, VR technology is a display technology that only provides CG images of real-world objects, backgrounds, etc. On the other hand, AR technology refers to a technology that displays a virtually created CG image on an image of a real object. MR technology is similar to the above-mentioned AR technology in that the virtual objects to be displayed are mixed and combined with the real world. However, MR technology is different from AR technology in that AR technology clearly distinguishes between real objects and virtual objects created as CG images and uses virtual objects as supplementary objects to real objects, while MR technology treats virtual objects as objects with properties equivalent to real objects. More specifically, an example of the application of MR technology is holographic services.

[0237] Recently, VR, AR, and MR technologies are often referred to as extended reality (XR) technologies, rather than being clearly distinguished from each other. Therefore, embodiments of the present disclosure are applicable to any of VR, AR, MR, and XR technologies. Encoding / decoding based on PCC, V-PCC, and G-PCC technologies are applicable to such technologies.

[0238] The PCC method / apparatus according to the embodiment may be applied to a vehicle providing a self-driving service.

[0239] Vehicles providing self-driving services are connected to the PCC device for wired / wireless communication.

[0240] When the point cloud data (PCC) transmitting / receiving device according to the embodiment is connected to the vehicle for wired / wireless communication, the device can receive / process content data related to AR / VR / PCC services (which can be provided together with self-driving services) and send it to the vehicle. When the PCC transmitting / receiving device is installed on the vehicle, the PCC transmitting / receiving device can receive / process content data related to AR / VR / PCC services and provide it to the user based on a user input signal input through a user interface device. The vehicle or the user interface device according to the embodiment can receive the user input signal. The user input signal according to the embodiment may include a signal indicating a self-driving service.

[0241] The point cloud data transmitting method / apparatus according to the embodiment will be interpreted as terms related to the following items: Figure 1 The transmitting device 10000, the point cloud video encoder 10002 and the transmitter 10003, Figure 2 Get 20000 / encode 20001 / send 20002, Figure 4 The encoder, Figure 12 The sending device, Figure 14 device, Figure 15 Prediction tree-based coding, Figure 16 Compression based on inter-frame prediction tree, Figure 17 Compression based on azimuth sorting according to laser ID, Figure 18 Intra-frame and / or inter-frame encoders, Figures 20 to 23 Bitstream generation, Figure 24 Sending method, etc.

[0242] The point cloud data receiving method / apparatus according to the embodiment is interpreted as a term related to the following items: Figure 1 The receiving device 10004, the receiver 10005 and the point cloud video decoder 10006, Figure 2 Send 20002 / decode 20003 / render 20004, Figure 10 and Figure 11 decoder, Figure 13 receiving device, Figure 14 device, Figure 15 Decoding based on prediction trees, Figure 16 Reconstruction based on inter-frame prediction tree, Figure 17 Reconstruction based on azimuth sorting according to laser ID, Figure 19 Intra-frame and / or inter-frame decoders, Figures 20 to 23 Bitstream parsing, Figure 25 Receiving method, etc.

[0243] The point cloud data transmitting / receiving method / apparatus according to the embodiment may be referred to as a method / apparatus according to the embodiment.

[0244] According to the embodiment, geometric data, geometric information, position information, etc. constituting point cloud data are interpreted as having the same meaning. Attribute data, attribute information, etc. constituting point cloud data are interpreted as having the same meaning.

[0245] A point is an element of a point cloud that contains a position in a coordinate system and zero or one or more attributes. A point cloud is a list of points. A point cloud sequence is a sequence of one or more point clouds. A point cloud frame is a point cloud within a point cloud sequence. Geometry is the position of a point associated with a set of points. Attributes are scalar or vector properties associated with each point in the point cloud. For example, they could be color, reflectivity, frame index, etc. A slice encodes the geometry and attributes of a portion or all of a point cloud frame. A tile is a set of slices.

[0246] The method / apparatus according to an embodiment may include and perform an attribute compression method for laser ID using a point cloud prediction tree.

[0247] While research has been conducted on compressing geometry using intra prediction trees, research has not yet been conducted on compressing attribute information using inter prediction tree information. Methods / apparatus according to embodiments may include and perform an inter attribute compression method using laser IDs in prediction tree information.

[0248] The method / apparatus according to an embodiment can compress 3D point cloud data using a structure that allows attribute compression based on inter-frame geometric information. In point cloud data, dynamic point clouds classified as category 3 consist of multiple point cloud frames and are primarily intended for use cases with autonomous driving data. A group of frames is called a sequence. A sequence contains frames consisting of values ​​for the same attribute. Therefore, the attribute values ​​have data characteristics such as motion or changes in attribute values ​​relative to previous or subsequent frames. In current standards, geometry-based inter-frame compression is well developed, but inter-frame attribute compression has not yet been developed.

[0249] Therefore, embodiments propose a structure and method for applying inter-frame features found in geometric information to attribute compression, achieving compression between frames in a Category 3 sequence. Inter-frame geometric compression can be broadly categorized as octree inter-frame compression and prediction tree inter-frame compression. In this embodiment, attribute compression is performed based on information used in prediction tree inter-frame compression. Furthermore, for points that are not suitable for inter-frame information, attribute compression can be performed based on intra-frame geometric information to improve compression efficiency.

[0250] Figure 15 A method of generating a prediction tree structure according to an embodiment is illustrated.

[0251] The method / apparatus according to the embodiment may generate Figure 15 The prediction tree shown.

[0252] The prediction tree structure is generated by constructing a tree structure with relationships between points from the xyz coordinates of the point cloud. To construct the prediction tree, the input points are sorted according to a certain standard, and the prediction tree structure is generated by calculating the predicted values ​​based on the neighbor nodes from the rearranged ply. The method of generating and encoding the prediction tree structure is described in Figure 15 Shown in.

[0253] refer to Figure 15 , ply data can be received by the encoder / decoder, and the data can be sorted in an order that is effective for encoding / decoding. Taking into account the characteristics between the sorted points, a predicted value close to the value of the current point is generated, and the predicted point of the current point can be represented in a tree structure. Parent points and child points can be represented by arrows. The arrow can be constructed to point from the current point to the parent (neighbor and / or predicted value) point. When the prediction relationship between points is represented in a tree structure, the residual of the predicted point relative to the current point can be generated by traversing from the root node (point) to the child point and encoded.

[0254] Figure 16 Inter-frame encoding / decoding according to an embodiment is illustrated.

[0255] Further references Figure 15 , the method / apparatus according to the embodiment can perform compression based on inter-frame prediction tree, such as Figure 16 To this end, an inter-frame structure can be used, in which one inter-frame prediction point is additionally selected from the reference frame, or two points are used as additional inter-frame prediction points.

[0256] refer to Figure 16 , a point with a smaller residual between the two points (the additional inter-frame prediction point and the inter-frame prediction point) that are candidate predictors can be used as a predictor for the current point. In order to encode or decode the current point contained in the current frame, the method / apparatus according to the embodiment can find a reference point close to the previously decoded (recovered) point in the reference frame of the current frame. The reference point can have the same laser ID and the same scaled azimuth as the previously decoded point. The next point after the reference point or the next point after the next point (whichever has the most similar geometry and / or attributes to the current point) can be used as a predictor. That is, the residual between the geometry and / or attributes of the selected predictor and the current point can be encoded and decoded.

[0257] The transmission method / device according to the embodiment compresses geometry and performs attribute compression. For example, it can use prediction / lifting / RAHT transform coding to perform intra-frame coding. For inter-frame coding / decoding, it has been proposed to use prediction / lifting / RAHT transform coding by combining the previous frame and the current frame into a single frame, but its compression efficiency is only about 5% of that of intra-frame coding. In addition, it cannot support the prediction tree structure intended for low-latency decoding. Embodiments can be provided to address the above-mentioned issues.

[0258] Whether to maintain the geometric coding order can be determined based on whether the decoder generates a prediction tree. Implementation methods can apply different encoding methods based on whether the geometric coding order is maintained. Unlike conventional techniques that simply combine two frames into one frame to be encoded, inter-frame prediction tree information can be used as decoding information for attribute compression. In intra-frame compression, the processing of Morton generation and neighbor node search overlaps with the prediction tree information generated based on geometry, thereby solving the problem of redundant execution. Existing information generated from the prediction tree based on distance can be used for attribute compression to the maximum extent possible.

[0259] The actual geometry coding order can be maintained in attribute compression, or the geometry (points) can be rearranged. Maintaining the geometry coding order can have the advantage of reducing the rearrangement time at the encoder and decoder, but can result in lower compression according to the geometry coding order. If the rearrangement is performed based on specific criteria without maintaining the geometry coding order, the execution time and memory usage of the rearrangement at the encoder and decoder may increase, but the compression rate may increase. Therefore, the time and compression rate at the encoder and decoder can determine whether the geometry coding order is maintained.

[0260] For the prediction transform, lifting transform, and RAHT currently used for attribute compression, the geometric order is changed to the Morton order to encode the attributes. However, in prediction geometry coding, a prediction tree is constructed for the parent-child relationship between neighboring points, and the attribute values ​​between points can be encoded based on the previous point. Therefore, embodiments can apply an attribute encoding method based on the prediction tree information available after the prediction tree geometry coding.

[0261] Conventional prediction tree geometry coding creates parent-child relationships between nodes and calculates a prediction value for each node. The prediction value calculation is determined by the order of the sorted points and the position values ​​of their neighboring nodes in that order. The prediction value is calculated at the current node based on the position values ​​of the parent node and the parent-parent node. Methods for calculating prediction values ​​in conventional prediction tree coding include intra-frame calculation methods (four methods) and inter-frame calculation methods (two methods).

[0262] 1. No prediction; 2. Delta prediction (p0); 3. Linear prediction (2p0-p1); 4. Parallelogram prediction (p0+p1-p2); 1. Inter-frame prediction point (p'0); 2. Additional inter-frame prediction point (p'1).

[0263] The inter-frame prediction point specifies the point in the decoded reference frame that has the same laser ID value and the most similar azimuth value as the reference point. The additional inter-frame prediction point refers to a point with a smaller azimuth value than the inter-frame prediction point and the same laser ID.

[0264] Embodiments may include a method for compressing intra / inter attributes in point cloud data using a geometry prediction tree. For inter attribute compression, embodiments provide conditions for selecting points with required geometry information for compression based on intra and inter information. Embodiments include a method for extending existing intra prediction tree geometry compression to achieve attribute compression. For example, the method may include a method for selecting prediction subnodes in a reference frame based on laser IDs, and a method for determining compression based on a set of inter / intra prediction subnodes.

[0265] When the proposed geometric attribute coding method is used within a frame, low-latency coding is achieved using geometric coding with prediction trees, but low latency cannot be achieved in attribute compression. Therefore, true low-latency coding is not possible. The proposed method also provides a method for selecting prediction subnodes in reference frames based on laser IDs, as well as a method for determining compression using inter-frame / intra-frame prediction subnode sets, to improve attribute compression performance.

[0266] refer to Figure 16 , illustrates an attribute compression method using inter-frame geometric prediction trees.

[0267] Currently, geometry compression using intra-frame prediction trees is available. The inter-frame geometry prediction tree can refer to up to two previously decoded points in the current frame, and selects a mode according to a calculation formula and delivers it to the decoder as signaling information. At this time, an inter-frame prediction point corresponding to the current point in the previous frame is selected as the point (reference point) with the closest x, y, and z geometry values. At this time, another point can be selected in the reference frame. Figure 16 As shown, an inter-frame prediction point and an additional inter-frame prediction point are selected as candidates. When selecting one of the inter-frame prediction point and the additional inter-frame prediction point as the predictor of the current point, the point with the smaller difference (to the current point predictor) can be selected. Based on the selected point in the reference frame, up to three previously decoded points in the reference frame can be selected as predictors to perform inter-frame geometric prediction coding.

[0268] Inter-frame prediction points and additional inter-frame prediction points selected from the geometry can be used for compression attributes. A point selected in the reference frame (i.e., an inter-frame prediction point or an additional inter-frame prediction point) can be determined as a prediction sub-point, or another point can be determined as a reference point. To determine the reference point, a point with a smaller Euclidean distance in x, y, and z between the current point and the prediction sub-point can be selected as the prediction sub-point.

[0269] Figure 17 A method of selecting a predicted sub-node in a reference frame based on a laser ID according to an embodiment is illustrated.

[0270] Point cloud data sending method / device according to an embodiment ( Figure 1 The transmitting device 10000, the point cloud video encoder 10002 and the transmitter 10003, Figure 2 Get 20000 / encode 20001 / send 20002, Figure 4 The encoder, Figure 12 The sending device, Figure 14 device, Figure 15 Prediction tree-based coding, Figure 16 Compression based on inter-frame prediction tree, Figure 18 Intra-frame and / or inter-frame encoders, and Figure 24 The sending method) can choose to predict the child node, such as Figure 17 shown.

[0271] Point cloud data receiving method / device according to an embodiment ( Figure 1 The receiving device 10004, the receiver 10005 and the point cloud video decoder 10006, Figure 2 Send 20002 / decode 20003 / render 20004, Figure 10 and Figure 11 decoder, Figure 13 receiving device, Figure 14 device, Figure 15 Decoding based on prediction trees, Figure 17 Reconstruction based on azimuth sorting according to laser ID, Figure 19 Intra-frame and / or inter-frame decoders, and Figure 25 The receiving method) can choose to predict the child node, such as Figure 17 shown.

[0272] In the operation of geometric compression using a prediction tree, the encoding method / device can transform the coordinate system into a spherical coordinate system using the radius, azimuth and laser ID, and search for the predicted child node. The spherical coordinate system may then not be retransformed into a Cartesian coordinate system in the prediction tree. Point information using the radius, azimuth and laser ID of the current spherical coordinate system can be divided into 0 to 63 or 0 to 127 based on the laser ID. The reason for dividing the information based on the laser ID as a reference is that when the lidar laser scans once, only one detection point is acquired and generated due to the nature of the laser. The value of the azimuth according to the laser ID can be in the range of -π to +π. When sorting is performed based on the azimuth, an azimuth value corresponding to the laser ID is generated, such as Figure 17 shown.

[0273] refer to Figure 17 In the distribution of data acquired by the laser, the central origin may be the location of the radar, and multiple circles from the circle closest to the origin to the circle with a larger radius may each have a laser ID.

[0274] A point cloud sorted by azimuth based on laser ID is generated for each of the reference frame and the current frame. To select a predictor for the current point in the reference frame, the point with the closest azimuth for the same laser ID is selected. The attribute value of the selected point can be a candidate for compressing the predictor node for the current point and can be selected using the same criteria as in the current frame.

[0275] The transmitting / receiving method / apparatus according to the embodiment may determine compression using the inter / intra prediction sub-nodes set as follows.

[0276] The actual compression can be performed using the inter / intra prediction subnode based on the laser ID. Among the attributes, due to its characteristics, the reflectivity has the value most similar to the reflectivity of the reference frame. Therefore, for compression, the candidates in the reference frame can be weighted to make the selection more favorable. The equation for weighting can be given as follows:

[0277] predEligible=predInter*weight+predIntra; or

[0278] predEligible_reflectance={predInter1*weight||predInter2*weight||predIntra1||predIntra2||predIntra3}.

[0279] predEligible_reflectance is the threshold that determines whether to apply the weight.

[0280] weight is the weight.

[0281] predInter1 is the reflectivity of the inter-frame prediction subnode.

[0282] predIntra1 is the reflectivity of the intra prediction child node.

[0283] weight is the weight, which can be passed from the encoder to the decoder via pred_weight.

[0284] When predEligible_reflectance is greater than or equal to the threshold, the transmission method / apparatus according to the embodiment uses only the prediction subnodes in the reference frame to calculate the mode and transmit the residual. When predEligible is less than the threshold, only the prediction subnodes in the current frame are used to calculate and transmit the mode and residual.

[0285] predEligible_reflectance is the predicted value of reflectivity for prediction, calculated per point for encoding. The value obtained by subtracting the predEligible (predEligible_reflectance) value from the reflectivity value of the current point is the residual of the new predictor. The encoder can select one of predInter1*weight, predInter2*weight, predIntra1, predIntra2, or predIntra3 as the mode. The decoder can decode the property value (reflectivity) of the current point by adding the residual to the predictor in the signaled mode.

[0286] The decoder can use predEligible_reflectance to determine whether to apply attribute compression on a per-unit basis. The applied unit can be an entire frame, a road / object, an individual object, or an LPU / PU. Once the encoder signals whether compression is applied, the decoder can backcompute the attribute information on a per-unit basis. In order to use the condition of predEligible_reflectance, the residuals between the reflectivity of the current point and the values ​​of predInter1, predInter2, predIntra1, predIntra2, and predIntra3 are checked respectively. Among the residuals, the residual of predInter is the value obtained by multiplying predInter by a weight. The minimum residual is signaled as the mode, and the decoder performs the inverse operation by adding the residuals using the predictor as the mode.

[0287] The mode's suitability for signaling conditions for selection from among the predictor candidates must be checked. A mode can be selected by quantizing the differences between conditions or raw attribute values, so that the candidate with the smallest difference can be selected from four or more candidates selected as predictors. The conditions used by the predictor generator become the conditions used to determine the mode's suitability, and the attribute value that provides the smallest difference, or the attribute value that does not produce the smallest difference but is most correlated with compression of differences at subsequent points, is signaled as the mode.

[0288] For methods that transmit differences based on the applicability of a mode, the conditions selected by the encoder are signaled to the decoder, and the encoder and decoder perform calculations on a per-point basis using the same conditions as the mode. In this case, differences based on the mode are transmitted. For these differences, quantized or unquantized values ​​are transmitted from the encoder. Entropy coding methods (such as exponential Golomb, context-adaptive variable-length coding, context-adaptive binary arithmetic coding, etc.) can be used to transmit the differences per point or encode the differences per point group. After performing a transform operation such as DCT, DST, SADCT, or RAHT, the differences can be transformed into a bitstream.

[0289] Based on the geometry of the current frame and the previous frame (reference frame), three candidates in the current frame (predInter1, predInter2, and predInter3) and two candidates in the reference frame (predInter1 and predInter2) can be considered.

[0290] The qualified value in the formula according to the embodiment may be used to select a mode to determine whether to consider intra-frame reflectivity or inter-frame reflectivity.

[0291] PredEligible itself is a reflectance, and a residual can be generated according to the difference from the reflectance of the current point. The mode that produces the minimum residual can be an inter mode or an intra mode, and one of these modes can be selected.

[0292] Once the encoder has selected a mode and compressed the attributes, the decoder can check the values ​​and reconstruct the attributes based on the reflectivity within the frame. When the values ​​are qualified, the point cloud can be reconstructed by applying weights to the reflectivity.

[0293] Figure 18 A point cloud data transmitting device according to an embodiment is illustrated.

[0294] Figure 18 Illustrated is a device related to a method / device for transmitting point cloud data according to an embodiment ( Figure 1 The transmitting device 10000, the point cloud video encoder 10002 and the transmitter 10003, Figure 2 Get 20000 / encode 20001 / send 20002,Figure 4 The encoder, Figure 12 The sending device, Figure 14 device, Figure 15 Prediction tree-based coding, Figure 16 Compression based on inter-frame prediction tree, Figure 17 Compression based on azimuth sorting according to laser ID, Figure 18 Intra-frame and / or inter-frame encoders, Figures 20 to 23 Bitstream generation and Figure 24 Sending method).

[0295] Figure 18 The apparatus in is an intra / inter attribute encoder for laser ID using prediction tree.

[0296] The attribute compressor can generate information (laserID_use_predtree_flag) indicating whether to use attribute compression encoding based on laser ID of prediction tree as signaling information and deliver the information. Based on the information indicating whether to use attribute compression encoding based on laser ID, the transformation required for attribute compression can be performed.

[0297] Regarding the intra / inter mode applicability, a weight can be assigned to the selection of inter compression. The weight value can be generated and signaled as prediction weight information (pred_weight). When the weighted prediction value is greater than or equal to a threshold, the mode can be selected to use inter coding. The threshold can be the predictor_inter_intra_threshold information to the decoder.

[0298] Reference Figure 18 The transmitting device according to the embodiment may be referred to as an encoder and may include a memory and / or a processor. The instructions stored in the memory may be configured to cause the processor to encode the point cloud data. Figure 18 Each component may correspond to hardware, software, a processor and / or a combination thereof.

[0299] The data input unit can acquire point cloud data. The point cloud data can be received as input by an acquisition component, a camera, a sensor, etc. The point cloud data can be referred to as a point cloud.

[0300] The coordinate transformer can transform the coordinates of the geometry in the point cloud. For example, the coordinates related to the position value of the point in the reference frame and / or the position value of the point in the current frame can be transformed.

[0301] The quantization / voxelization processor may quantize and / or voxelize the point cloud.

[0302] The prediction tree generator can present the point cloud in a prediction tree structure. It can generate a prediction tree that represents the parent / child relationship between the geometries (points) in the point cloud.

[0303] The prediction tree encoder can encode the point cloud based on the prediction tree. It can generate the predicted value of the current point based on the prediction tree. It can also generate the residual between the current point and the predicted value.

[0304] The arithmetic encoder may encode the residual and generate a geometry bitstream.

[0305] The reference and / or current frame geometry reconstructor can reconstruct the coded points to provide the geometric information about the points required for attribute compression. The geometry can be reconstructed using points contained in the current frame and / or the reference frame.

[0306] The color transform processor can transform the attributes (color) of the point cloud. It can transform the color system. It can receive the attribute values ​​of the points in the reference frame and / or the attribute values ​​of the points in the current frame as input.

[0307] The attribute transformation processor can transform the attributes. Based on the reconstructed geometry, the attributes corresponding to the geometry can be transformed into a suitable system for encoding the attributes.

[0308] The Laser ID Based Predictor Generator can generate predictors for point clouds based on the laser IDs associated with the point cloud. Figure 17 Description, etc.

[0309] The Intra and / or Inter mode suitability checker can check the Intra and / or Inter mode suitability and select the appropriate mode. Figure 17 Description, etc.

[0310] The arithmetic encoder can encode the residual between the attributes of the current point cloud and the predicted values ​​and generate an attribute bitstream.

[0311] Figure 19 A point cloud data receiving device according to an embodiment is illustrated.

[0312] Figure 19 Illustrated is a device related to a method / device for receiving point cloud data according to an embodiment ( Figure 1 The receiving device 10004, the receiver 10005 and the point cloud video decoder 10006, Figure 2 Send 20002 / decode 20003 / render 20004, Figure 10 and Figure 11 decoder, Figure 13 receiving device, Figure 14 device, Figure 15 Decoding based on prediction trees, Figure 16Reconstruction based on inter-frame prediction tree, Figure 17 Reconstruction based on azimuth sorting according to laser ID, Figure 19 Intra-frame and / or inter-frame decoders, Figures 20 to 23 Bitstream parsing and Figure 25 receiving method).

[0313] Figure 19 An intra / inter attribute decoder of Laser ID using a prediction tree is illustrated.

[0314] Before attribute decoding, laserID_use_predtree_flag may be received as parameter information contained in the received bitstream. The predictor may be generated based on the laser ID in the same manner as in the encoder.

[0315] Based on the pred_weight delivered from the encoder, weights can be applied to the intra / inter predictors. When the weighted prediction value is greater than or equal to a threshold, the mode is decoded to use inter coding. The threshold is received as predictor_inter_intra_threshold and is used to calculate the reconstruction mode and the difference reconstruction.

[0316] refer to Figure 19 The receiving device according to the embodiment may be referred to as a decoder and may include a memory and / or a processor. The instructions stored in the memory may be configured to cause the processor to decode the point cloud data. Figure 19 Each component may correspond to hardware, software, a processor and / or a combination thereof.

[0317] A receiver may receive a bitstream containing a point cloud and parameters. The bitstream may include a geometry bitstream and / or an attribute bitstream. A decoder may decode the geometry and / or attributes contained in the bitstream based on the parameters contained in the bitstream.

[0318] The operation of the decoder may correspond to the operation of the encoder, and the point cloud may be reconstructed according to the inverse process of the operation of the encoder.

[0319] The arithmetic decoder can decode the geometry contained in the geometry bitstream.

[0320] The prediction tree-based reconstruction processor can reconstruct the point cloud based on the prediction tree. The prediction tree of the point cloud can be generated in the same way as in the encoder.

[0321] The surface model processor may triangulate, upsample, and / or voxelize the surface model of the geometry.

[0322] The reference and / or current frame geometry reconstructor can reconstruct the geometry required for decoding attributes. It can reconstruct the geometry based on the reference frame and / or the current frame.

[0323] The inverse coordinate transformer can inversely transform the coordinates of the geometry to generate the position value of the point in the current frame. The Cartesian coordinate system can be used to generate the position value of the point.

[0324] The arithmetic decoder may receive an attribute bitstream and decode the attributes contained in the bitstream.

[0325] The inverse quantization processor can inverse quantize the attributes.

[0326] The Laser ID Based Predictor Generator can generate a predictor for an attribute based on the laser ID. The predictor can be used to decode the attribute. Figure 17 Description, etc.

[0327] Intra-frame and / or inter-frame mode and difference calculator can select intra-frame and / or inter-frame mode and calculate the difference. Figure 17 Description, etc.

[0328] The color inverse conversion processor can inversely convert the color (attribute). For example, it can generate the attribute value of the point with RGB in the current frame.

[0329] Figure 20 A bitstream containing a point cloud and parameters according to an embodiment is illustrated.

[0330] Figure 20 The bit stream in the point cloud data transmission method / device according to the embodiment ( Figure 1 The transmitting device 10000, the point cloud video encoder 10002 and the transmitter 10003, Figure 2 Get 20000 / encode 20001 / send 20002, Figure 4 The encoder, Figure 12 The sending device, Figure 14 device, Figure 15 Prediction tree-based coding, Figure 16 Compression based on inter-frame prediction tree, Figure 17 Compression based on azimuth sorting according to laser ID, Figure 18 Intra-frame and / or inter-frame encoders, Figures 20 to 23 Bitstream generation and Figure 24 The sending method is generated.

[0331] Figure 20 The bit stream in is obtained by the point cloud data receiving method / device according to the embodiment ( Figure 1 The receiving device 10004, the receiver 10005 and the point cloud video decoder 10006, Figure 2Send 20002 / decode 20003 / render 20004, Figure 10 and Figure 11 decoder, Figure 13 receiving device, Figure 14 device, Figure 15 Decoding based on prediction trees, Figure 16 Reconstruction based on inter-frame prediction tree, Figure 17 Reconstruction based on azimuth sorting according to laser ID, Figure 19 Intra-frame and / or inter-frame decoders, Figures 20 to 23 Bitstream parsing and Figure 25 The receiving method) is decoded.

[0332] In order to add / implement the intra / inter attribute encoding / decoding method of the laser ID using the prediction tree, the encoder may generate parameters and transmit them to the decoder as signaling information. The decoder performs decoding based on the parameters.

[0333] Hereinafter, parameters according to an embodiment (which may be referred to as metadata, signaling information, etc.) may be generated in a process of a transmitter according to an embodiment described below and delivered to a receiver according to an embodiment for use in a reconstruction process. For example, the parameters according to an embodiment may be generated in a metadata processor (or metadata generator) of a transmitting device according to an embodiment described below and acquired by a metadata parser of a receiving device according to an embodiment described below. The encoded point cloud is configured as follows.

[0334] Each abbreviation represents the following: SPS: Sequence Parameter Set, GPS: Geometry Parameter Set, APS: Attribute Parameter Set, TPS: Tile Parameter Set, Geom: Geometry Bitstream = Geometry Slice Header + Geometry Slice Data, Attr: Attribute Bitstream = Attribute Block Header + Attribute Block Data. Blocks can also be referred to as slices.

[0335] The bitstream contains parameter sets and slices, which are the unit of encoding / decoding. Each slice has geometry data and attribute data. The geometry / attribute data can include a header and data, respectively. The header can contain auxiliary information for the data.

[0336] Parameter sets can include sequence parameter sets, geometry parameter sets, attribute parameter sets, and tile parameter sets. A tile parameter set can contain information about multiple tiles. For example, it can contain the coordinates, width, height, and depth of the bounding box of tile 0, and the coordinates, width, height, and depth of the bounding box of tile n. There can be a different parameter set for each type of attribute. A slice can contain a geometry and / or zero or one or more attributes. The geometry can consist of a slice header and slice data. The geometry slice header can contain information about the geometry. For example, it can contain a geometry parameter set ID related to the geometry, a tile ID, a slice ID, position / size information about the bounding box, and information about the number of points.

[0337] The tiles or slices are provided in such a way that the point cloud can be divided into regions and processed.

[0338] When a point cloud is divided into multiple regions, each region can have a different importance.

[0339] By providing regions such that different filters or different filter units can be applied depending on importance, filtering methods with high complexity but demonstrating good result quality can be used in important regions.

[0340] By applying different filtering to individual areas (areas partitioned into tiles or slices) based on receiver capacity, rather than applying complex filtering methods to the entire point cloud data, better image quality can be ensured in areas important to the user and appropriate latency can be ensured for the system.

[0341] Therefore, when the point cloud is partitioned into tiles, different filters or different filter units can be applied to each tile.

[0342] When a point cloud is divided into slices, different filters or different filter units can be applied to each slice.

[0343] Hereinafter, syntax of parameters contained in a bitstream is described with reference to corresponding drawings.

[0344] Figure 21 A sequence parameter set according to an embodiment is illustrated.

[0345] Figure 20 The bitstream contains Figure 21 The SPS can carry information about the structure of the attribute encoding of the laser ID based on the prediction tree.

[0346] laserID_use_predtree_flag indicates whether LaserID is used to generate the predictor. For example, a flag set to TRUE indicates that LaserID is used to generate the attribute predictor, while a flag set to FALSE indicates that LaserID is not used to generate the attribute predictor.

[0347] pred_weight indicates a coefficient for weighting the intra / inter predictor.

[0348] predictor_inter_intra_threshold indicates a threshold for the calculated weight. For example, pred_weight can be used to generate intra and / or inter predictors. When the weighted predictor is greater than or equal to the threshold, only the inter predictor can be used. The difference (residual) can be generated by the predictor generation mode according to the signaling method.

[0349] SPS may also contain the following elements.

[0350] simple_profile_compatible indicates whether the bitstream is compatible with the simple profile (when equal to 1) or not (when equal to 0).

[0351] dense_profile_compliance indicates whether the bitstream complies with the dense profile (when equal to 1) or does not comply (when equal to 0).

[0352] predictive_profile_compliance indicates whether the bitstream complies with the predictive profile (when equal to 1) or does not comply (when equal to 0).

[0353] main_profile_compliant indicates whether the bitstream complies with the main profile (when equal to 1) or does not comply (when equal to 0).

[0354] slice_reordering_constraint indicates whether the bitstream is sensitive (when equal to 1) or insensitive (when equal to 0) to the reordering or removal of slices within the coded point cloud frame.

[0355] unique_point_positions_constraint equal to 1 indicates that each point should have a unique position in each encoded point cloud frame. unique_point_positions_constraint equal to 0 indicates that two or more points may have the same position in an encoded point cloud frame.

[0356] sps_seq_parameter_set_id identifies the SPS for reference by other DUs.

[0357] seq_origin_bits specifies the length in bits of each syntax element seq_origin_xyz excluding all sign bits.

[0358] seq_origin_xyz[k] and seq_origin_log2_scale together specify the XYZ origin of the sequence and the encoded coordinates of each sequence coordinate system unit from the application-specific coordinate origin.

[0359] seq_bbox_size_bits indicates the length in bits of each syntax element seq_bbox_size_minus1_xyz.

[0360] seq_bbox_size_minus1_xyz[k]+1 indicates the kth XYZ component of the coded volume dimension in the sequence coordinate system, and seq_unit_denominator_minus1 and seq_unit_is_metres together indicate the length represented by the unit vector in the sequence coordinate system.

[0361] geom_axis_order indicates the correspondence between the XYZ axes of the encoded point cloud and the STV axes according to Table 8.

[0362] num_attributes indicates the number of attributes enumerated in the SPS attribute list.

[0363] attr_components_minus1[attrIdx]+1 indicates the number of components of the identified attribute.

[0364] attr_instance_id[attrIdx] indicates the instance identifier of the identified attribute.

[0365] attr_bitdepth_minus1[attrIdx]+1 indicates the bit depth of all components of the identified attribute.

[0366] attr_label_known[attrIdx], attr_label[attrIdx], and attr_label_oid[attrIdx] together identify the type of data carried by the identified attribute. attr_label_known[attrIdx] indicates whether the attribute is the one specified in this document by the value attr_label[attrIdx] (when equal to 0) or an externally specified attribute identified by the object identifier attr_label_oid[attrIdx].

[0367] attr_property_cnt indicates the number of attribute_property syntax structures in the SPS of the attribute.

[0368] Figure 22 Tile parameter sets according to embodiments are illustrated.

[0369] Included in Figure 20 In the bitstream Figure 22 The TPS can carry information about the structure of the attribute encoding of the laser ID based on the prediction tree.

[0370] laserID_use_predtree_flag indicates whether the laser ID is used to generate the predictor. For example, a flag set to TRUE indicates that the laser ID is used to generate the attribute predictor, while a flag set to FALSE indicates that the laser ID is not used to generate the attribute predictor.

[0371] pred_weight indicates a coefficient for weighting the intra / inter predictor.

[0372] predictor_inter_intra_threshold indicates the threshold of the calculated weight. For example, pred_weight can be used to generate intra and / or inter predictors. When the weighted predictor is greater than or equal to the threshold, only the inter predictor can be used. The difference (residual) can be generated by the predictor generation mode according to the signaling method.

[0373] TPS may be referred to as a tile manifest data unit. TPS may also contain the following elements.

[0374] The tile manifest (if any) contains metadata that defines the spatial region of each enumerated tile. Each tile is identified by an implicit or explicit tile ID.

[0375] The tile list is applied in the next encoded point cloud frame following the tile list data unit.

[0376] ti_seq_parameter_set_id identifies the active SPS with sps_seq_parameter_set_id.

[0377] tile_cnt indicates the number of tiles enumerated in the tile manifest.

[0378] tile_id_bits specifies the length in bits of each syntax element tile_id. tile_id_bits equal to 0 indicates that the tile should be identified by the index tileIdx.

[0379] tile_origin_bits_minus1+1 indicates the length in bits of each syntax element tile_origin_xyz excluding all sign bits.

[0380] tile_size_bits_minus1+1 indicates the length in bits of each syntax element tile_size_minus1_xyz.

[0381] tile_id[tileIdx] indicates the identifier of the tileIdx-th tile in the tile list.

[0382] tile_origin_xyz[tileId][k] and tile_size_minus1_xyz[tileId][k] indicate the bounding box in the sequence coordinate system that contains the slice identified by slice_tag equal to tileId.

[0383] tile_origin_xyz[tileId][k] indicates the kth XYZ coordinate of the bottom corner of the tile bounding box relative to the tile list origin.

[0384] tile_size_minus1_xyz[tileId][k]+1 indicates the kth XYZ dimension of the tile bounding box.

[0385] ti_origin_xyz[k] and ti_origin_log2_scale together indicate the XYZ origin of the sequence coordinate system specified by seq_origin_xyz[k] and seq_origin_log2_scale.

[0386] Figure 23 A geometry parameter set, an attribute parameter set, and a geometry slice header according to an embodiment are illustrated.

[0387] Figure 20 The bitstream contains Figure 23 The GPS can carry information about the structure encoded in the attributes of the laser ID based on the predicted tree.

[0388] laserID_use_predtree_flag indicates whether LaserID is used to generate the predictor. For example, a flag set to TRUE indicates that LaserID is used to generate the attribute predictor, while a flag set to FALSE indicates that LaserID is not used to generate the attribute predictor.

[0389] pred_weight indicates a coefficient for weighting the intra / inter predictor.

[0390] predictor_inter_intra_threshold indicates the threshold of the calculated weight. For example, pred_weight can be used to generate intra and / or inter predictors. When the weighted predictor is greater than or equal to the threshold, only the inter predictor can be used. The difference (residual) can be generated by the predictor generation mode according to the signaling method.

[0391] GPS can also include the following elements.

[0392] gps_geom_parameter_set_id identifies the GPS for reference by other DUs.

[0393] gps_seq_parameter_set_id identifies the active SPS with sps_seq_parameter_set_id.

[0394] slice_geom_origin_scale_present indicates whether slice_geom_origin_log2_scale is present (when equal to 1) or not present (when equal to 0) in the GDU header. slice_geom_origin_scale_present equal to 0 indicates that the slice origin scale is specified by gps_geom_origin_log2_scale.

[0395] gps_geom_origin_log2_scale indicates the scaling factor used to derive the slice origin from slice_geom_origin_xyz when slice_geom_origin_scale_present is equal to 0.

[0396] geom_tree_type equal to 0 indicates that the tile geometry is encoded using occupancy trees (7.3.3.4). geom_tree_type equal to 1 indicates that the tile geometry is encoded using prediction trees (7.3.3.8).

[0397] geom_angular_enabled indicates whether the tile geometry is (when equal to 1) or not (when equal to 0) encoded based on information about the beam set positioned and rotated along the V axis of the angular origin.

[0398] slice_angular_origin_present indicates whether the slice relative angular origin is signaled (when equal to 1) or not signaled (when equal to 0) in the GDU header. slice_angular_origin_present equal to 0 indicates that the angular origin is gps_angular_origin_xyz.

[0399] gps_angular_origin_xyz[] indicates the XYZ coordinates of the angular origin in the coded coordinate system.

[0400] num_beams_minus1+1 indicates the number of beams enumerated in GPS.

[0401] beam_elevation_init and beam_elevation_diff[i] together indicate a beam elevation angle with a gradient above the ST plane.

[0402] beam_voffset_init and beam_voffset_diff[i] together indicate the V-axis offset of the enumerated beam from the angular origin. The offset is specified in units of the encoding coordinate system. The offset of the i-th beam is specified by the expression BeamOffsetV[i].

[0403] beam_steps_per_rotation_init_minus1 and beam_steps_per_rotation_diff[i] indicate the number of steps taken per rotation to rotate the beam.

[0404] ptree_ang_radius_scale_log2 indicates the factor used to scale the radial angle coordinates of a point during transformation to Cartesian coordinates.

[0405] ptree_ang_azimuth_step_minus1+1 indicates the expected change in the azimuth angle of the rotated beam between coded points.

[0406] occtree_direct_joint_coding_enabled indicates whether the direct node used to encode two points should (when equal to 1) or should not (when equal to 0) jointly encode the positions according to a specific ordering of the points.

[0407] occtree_coded_axis_list_present equal to 1 indicates that the GDU header contains the syntax element occtree_coded_axis, which is used to derive the node size of each occtree level. occtree_coded_axis_list_present equal to 0 indicates that the syntax element occtree_coded_axis is not present in the GDU syntax and the occtree indicates a cubic volume specified by the tree depth.

[0408] occtree_neigh_window_log2_minus1+1 indicates the number of occupied tree node positions that form each availability window within the tree level.

[0409] occtree_adjacent_child_enabled indicates whether the adjacent child nodes of a neighbor occupancy tree node are used (when equal to 1) or not used (when equal to 0) for bit occupancy contextualization.

[0410] occtree_intra_pred_max_nodesize_log2-1 indicates the maximum size of an occupancy tree node suitable for intra-slice occupancy prediction.

[0411] occtree_bitwise_coding indicates that the node occupancy bitmap is encoded using the syntax element occupancy_bit (when equal to 1) or using the precoded syntax element occupancy_byte (when equal to 0).

[0412] occtree_planar_enabled indicates whether the encoding of the node occupancy bitmap is performed partially by (when equal to 1) or not by (when equal to 0) signaling of occupied and unoccupied planes.

[0413] occtree_planar_threshold[i] indicates a threshold value used in part to determine axis-specific suitability for planar occupancy coding.

[0414] The presence of occtree_direct_node_rate_minus1 indicates that for every 32 eligible nodes, only occtree_direct_node_rate_minus1+1 nodes may be coded as direct nodes.

[0415] occtree_planar_buffer_disabled indicates whether to disable contextualization of each node's occupied planar position using (when equal to 1) or not using (when equal to 0) the previously encoded planar position of the node.

[0416] geom_scaling_enabled indicates whether coded geometry should be scaled (when equal to 1) or not scaled (when equal to 0) in the geometry decoding process.

[0417] geom_qp indicates the geometry QP before adding per-slice and per-node offsets.

[0418] occtree_direct_node_qp_offset indicates the offset relative to the slice geometry QP used to scale direct node code point positions.

[0419] The APS may carry information about the structure of the attribute encoding of the laser ID based on the prediction tree.

[0420] laserID_use_predtree_flag indicates whether LaserID is used to generate the predictor. For example, a flag set to TRUE indicates that LaserID is used to generate the attribute predictor, while a flag set to FALSE indicates that LaserID is not used to generate the attribute predictor.

[0421] pred_weight indicates a coefficient for weighting the intra / inter predictor.

[0422] predictor_inter_intra_threshold indicates the threshold of the calculated weight. For example, pred_weight can be used to generate intra and / or inter predictors. When the weighted predictor is greater than or equal to the threshold, only the inter predictor can be used. The difference (residual) can be generated by the predictor generation mode according to the signaling method.

[0423] Included in Figure 20 In the bitstream Figure 23 ASP can also contain the following elements

[0424] aps_attr_parameter_set_id identifies the APS to be referenced by other DUs.

[0425] aps_seq_parameter_set_id identifies the active SPS based on sps_seq_parameter_set_id.

[0426] attr_coding_type indicates the attribute coding method.

[0427] attr_secondary_qp_offset indicates the offset to be applied to the primary attribute QP to derive the QP of the secondary attribute component.

[0428] attr_qp_offsets_present indicates whether the per-slice attribute QP offset attr_qp_offset[c] is present (when equal to 1) or not present (when equal to 0) in the ADU header.

[0429] attr_coord_conv_enabled indicates whether attribute coding uses scaled angular coordinates (when equal to 1) or slice-relative STV point positions (when equal to 0).

[0430] attr_coord_conv_scale[k] indicates a scaling factor used to scale the k-th angular coordinate of a point used for attribute encoding.

[0431] raht_prediction_enabled indicates whether to predict RAHT coefficients by upsampling and converting the previous coarse transform level (when equal to 1) or not (when equal to 0).

[0432] pred_set_size_minus1+1 indicates the maximum size of the prediction subset per point.

[0433] pred_inter_lod_search_range indicates the range of indices around the search center where the search may be performed in an extended inter-lod search to include nearest neighbors within the predictor of a point.

[0434] pred_dist_bias_minus1_xyz[k]+1 indicates the factor used to weight the kth XYZ component of the distance vector between two point locations used to compute the distance between points in the predictor search for a single refined point.

[0435] pred_max_range_minus1+1 indicates the distance at which predictor candidates should be discarded during predictor set pruning for scalable attribute coding.

[0436] lod_max_levels_minus1+1 indicates the maximum number of levels of detail that can be generated by the LoD generation process.

[0437] lod_decimation_mode indicates the decimation method used to generate the level of detail.

[0438] lod_sampling_period_minus2[lvl]+2 indicates the sampling period used in LoD generation for sampling points at level of detail lvl to generate the next lower level of detail lvl+1.

[0439] lod_initial_dist_log2 indicates the block size at the finest level of detail used for LoD generation and prediction subsearch.

[0440] lod_dist_log2_offset_present indicates that the per-slice block size offset specified by lod_dist_log2_offset should (when equal to 1) or should not (when equal to 0) be present in the ADU header.

[0441] pred_direct_max_idx_plus1 indicates the maximum number of single-point predictors that can be used for direct prediction.

[0442] pred_direct_threshold indicates when a point is suitable for direct prediction.

[0443] pred_direct_avg_disabled indicates whether the point prediction subset is on average in (when equal to 1) or not in (when equal to 0) direct prediction mode.

[0444] pred_intra_lod_search_range indicates the range of indices in the refined list of LoDs where nearest neighbors to be included in the predicted subset of points have been searched.

[0445] pred_intra_min_lod indicates the finest level of detail for which intra level of detail prediction is enabled.

[0446] inter_comp_pred_enabled indicates whether the first component of a multi-component property coefficient should (when equal to 1) or should not (when equal to 0) be used to predict coefficients of subsequent components.

[0447] pred_blending_enabled indicates whether the neighbor weights used to predict the neighbor average should (when equal to 1) or should not (when equal to 0) be blended based on the relative spatial positions of the points involved.

[0448] raw_attr_width_present indicates that the raw attribute value should use the same fixed length encoding for all syntax elements (when equal to 0) or the raw attribute value should use a length per syntax element (when equal to 1).

[0449] The tile header in Geom can carry information about the structure encoded in attributes of the laser ID based on the prediction tree.

[0450] laserID_use_predtree_flag indicates whether the laser ID is used to generate the predictor. For example, a flag set to TRUE indicates that the laser ID is used to generate the attribute predictor, while a flag set to FALSE indicates that the laser ID is not used to generate the attribute predictor.

[0451] pred_weight indicates a coefficient for weighting the intra / inter predictor.

[0452] predictor_inter_intra_threshold indicates the threshold of the calculated weight. For example, pred_weight can be used to generate intra and / or inter predictors. When the weighted predictor is greater than or equal to the threshold, only the inter predictor can be used. The difference (residual) can be generated by the predictor generation mode according to the signaling method.

[0453] Figure 20 The bitstream contains Figure 23 The geometry slice header may be referred to as a geometry data unit header and may further contain the following elements.

[0454] Included in Figure 20 In the bitstream Figure 23 The GDU carries relevant slice information, such as the structure of the slice and the frame counter or slice origin. The GDU consists of a GDU header, geometry encoded using an occupancy tree (when geom_tree_type is equal to 0) or a prediction tree (when geom_tree_type is equal to 1), and a GDU footer.

[0455] gdu_geometry_parameter_set_id indicates the active GPS with gps_geom_parameter_set_id.

[0456] slice_id identifies the slice for reference by other DUs.

[0457] slice_tag identifies a slice as a member of a slice group having the same value of slice_tag.

[0458] slice_entropy_continuation equal to 1 indicates that the entropy parsing state recovery process (11.6.2.2 and 11.6.3.2) shall be applied at the beginning of the GDU and ADU of the slice. slice_entropy_continuation equal to 0 specifies that the parsing of the GDU and ADU of the slice is independent of the parsing of the GDU and ADU of other slices.

[0459] slice_geom_origin_bits_minus1+1 indicates the length in bits of each syntax element slice_geom_origin_xyz.

[0460] slice_geom_origin_xyz[k] and slice_geom_origin_log2_scale indicate the kth XYZ coordinate of the slice origin in the encoded coordinate system.

[0461] slice_angular_origin_bits_minus1+1 indicates the length in bits of each syntax element slice_angular_origin_xyz.

[0462] slice_angular_origin_xyz[k] indicates the kth XYZ coordinate relative to the angular origin in the slice coordinate system.

[0463] slice_geom_qp_offset indicates the slice geometry QP as an offset to the GPS geom_qp.

[0464] Figure 24 A method of transmitting point cloud data according to an embodiment is illustrated.

[0465] Figure 25 Illustrated is a method for executing a point cloud data transmission method / device according to an embodiment ( Figure 1 The transmitting device 10000, the point cloud video encoder 10002 and the transmitter 10003, Figure 2 Get 20000 / encode 20001 / send 20002, Figure 4 The encoder, Figure 12[[ The sending device, ​ device, ​ Prediction tree-based coding, ​ Compression based on inter-frame prediction tree, ​ Compression based on azimuth sorting according to laser ID, ​ Intra-frame and / or inter-frame encoders and ​ bitstream generation).

[0466] S2400: The method for transmitting point cloud data according to an embodiment of the present invention may include encoding the point cloud data.

[0467] In the encoding operation according to the embodiment, the point cloud data can be ​ Furthermore, the encoding operation according to an embodiment may include generating a predictor based on the laser ID when encoding the attribute, such as ​As shown. A predictor may be generated from a reference frame and / or a current frame based on the laser ID. The encoding operation according to an embodiment may include selecting a predictor from predictor candidates of the reference frame and / or the current frame, and determining the predictor by weighting and / or comparing to perform predictive encoding. Based on the determined predictor, predictive encoding may be performed to encode and transmit a residual.

[0468] S2410: The method of transmitting point cloud data according to an embodiment may further include transmitting a bit stream containing the point cloud data.

[0469] The sending operation according to an embodiment may include ​ and ​ Encode point cloud data and ​ The bit stream is generated and sent as shown.

[0470] ​ A method of receiving point cloud data according to an embodiment is illustrated.

[0471] ​ Illustrate a method for executing a point cloud data receiving method / device according to an embodiment ( ​ The receiving device 10004, the receiver 10005 and the point cloud video decoder 10006, ​ Send 20002 / decode 20003 / render 20004, ​ and ​ decoder, ​ receiving device, ​ device, ​ Decoding based on prediction trees, ​ Reconstruction based on inter-frame prediction tree, ​ Reconstruction based on azimuth sorting according to laser ID, ​ Intra-frame and / or inter-frame decoders and ​ bitstream parsing).

[0472] S2500: The method for receiving point cloud data according to an embodiment may include receiving a bit stream containing point cloud data.

[0473] In a receiving operation according to an embodiment, a bit stream (such as ​ bitstream shown).

[0474] S2510: The method for receiving point cloud data according to an embodiment may further include decoding the point cloud data.

[0475] The decoding operation according to the embodiment may include decoding the geometry bitstream and attribute bitstream contained in the point cloud data, such as ​ In addition, according to ​, point cloud data can be decoded based on the laser ID. During attribute decoding, a predictor can be generated based on the laser ID. The predictor can be generated from a reference frame and / or a current frame based on the laser ID. The encoding operation according to an embodiment may include selecting a predictor from predictor candidates of the reference frame and / or the current frame, and determining the predictor by weighting and / or comparing to perform predictive encoding. Based on the determined predictor, predictive encoding can be performed to generate a residual, which can be summed with the received residual to reconstruct the point cloud data.

[0476] refer to ​ , the method of sending point cloud data may include encoding the point cloud data, and sending a bit stream containing the point cloud data.

[0477] refer to ​ and ​ Regarding prediction tree-based geometry compression, encoding of point cloud data may include encoding the point cloud data based on a prediction tree, wherein the point cloud data may be predicted based on points included in a reference frame of a current frame including the point cloud data. The prediction tree of the point cloud data may be used to predict the geometry of the point and / or the attributes of the point. Predictor candidates for use as predictors may be generated, and a predictor having values ​​most similar to the geometry of the current point and / or the attributes of the current point may be selected.

[0478] refer to ​ Regarding the method of selecting a prediction sub-node in a reference frame based on a laser ID, encoding of point cloud data may include sorting points in the point cloud data based on an azimuth according to the laser ID. Points contained in a current frame containing point cloud data and a reference frame of the current frame may be sorted based on the laser ID and the azimuth, and a predictor of a point in the current frame may be selected from the sorted points in the current frame and the reference frame. For example, the points may be sorted in ascending order of the laser ID. Points belonging to the laser ID may be sorted in ascending order of the azimuth. Encoding of point cloud data may include encoding attributes of the point cloud data, wherein the attributes may be predicted based on the attributes and weights contained in the reference frame. The attributes may include reflectivity. From the points sorted based on the laser ID and the azimuth, a point having a similar reflectivity to the current point may be selected as a predictor of the current point. An efficient prediction mode may be selected between intra-frame prediction and / or inter-frame prediction. Regarding predEligible_reflectance, based on a value generated based on the attributes of the current frame, the attributes of the reference frame, and the weight being greater than or equal to a threshold, the attribute may be predicted based on the attributes of the reference frame. When the value generated based on the attributes of the current frame, the attributes of the reference frame, and the weight is less than the threshold, the attribute is predicted based on the attribute of the current frame. The case based on the threshold can be reversed.

[0479] refer to ​Regarding signaling information (laserID_use_predtree_flag, pred_weight, and predictor_inter_intra_threshold), the bitstream may contain information indicating whether to generate a predictor based on the laser ID, information indicating a weight, and information indicating a threshold.

[0480] A method for transmitting point cloud data can be performed by a transmitting device. The transmitting device may include: an encoder configured to encode point cloud data; and a transmitter configured to transmit a bitstream containing the point cloud data. The transmitting device, as the encoder, may include a memory storing encoding operations and a processor connected to the memory, wherein the operations cause the processor to perform the encoding operations.

[0481] The receiving method may correspond to the sending method and may include the reverse process. The receiving method may include: receiving a bit stream containing point cloud data; and decoding the point cloud data. ​ Decoding the point cloud data may include decoding the point cloud data based on a prediction tree, wherein the point cloud data may be predicted based on points included in a reference frame of the current frame containing the point cloud data. Decoding the point cloud data may include sorting the points of the point cloud data based on azimuth according to the laser ID. Points included in the current frame containing the point cloud data and the reference frame of the current frame may be sorted based on the laser ID and azimuth, and a predictor of the points in the current frame may be selected from the sorted points in the current frame and the reference frame. Decoding the point cloud data may include decoding attributes of the point cloud data, wherein the attributes may be predicted based on attributes and weights included in the reference frame. If a value generated based on the attributes of the current frame, the attributes of the reference frame, and the weights is greater than or equal to a threshold, the attributes may be predicted based on the attributes of the reference frame. If a value generated based on the attributes of the current frame, the attributes of the reference frame, and the weights is less than a threshold, the attributes may be predicted based on the attributes of the current frame. For example, the points may be sorted in ascending order of laser ID. Points belonging to the laser IDs may be sorted in ascending order of azimuth. The attributes may include reflectivity. From the points sorted by laser ID and azimuth, a point with similar reflectivity to the current point can be selected as a predictor for the current point. An efficient prediction mode can be selected between intra-frame prediction and / or inter-frame prediction. The threshold-based case can be reversed.

[0482] The method for receiving point cloud data can be performed by a receiving device. The receiving device may include: a receiver configured to receive a bit stream containing point cloud data, and a decoder configured to decode the point cloud data. The receiving device as a decoder may include a memory for storing decoding operations, and a processor connected to the memory, wherein the operation can cause the processor to perform the decoding operation. Based on the parameters contained in the bit stream, the geometry and attributes of the points in the point cloud can be reconstructed. A prediction tree can be generated to predict the geometry and attributes of the current point based on the prediction tree, and it can be summed with the residual received and decoded in the bit stream to reconstruct the geometry and attributes of the point.

[0483] Therefore, embodiments can provide inter-frame coding to improve the compression efficiency of attribute encoding during point cloud compression. Instead of using conventional Morton-based sorting, azimuth-based sorting can be performed based on the characteristics of the point cloud (one laser only acquires one point), and only the information required for attribute compression can be utilized. Therefore, the computational effort and time spent on unnecessary coordinate transformations and Morton-based sorting can be effectively reduced. Compression efficiency can be improved by searching for the correct attribute values ​​in inter-frame information. Prediction trees for inter-frame prediction can be used to compress and reconstruct points, and prediction tree techniques can be applied to both geometry and / or attributes. By sorting points based on laser ID and / or azimuth, point similarity can be further reflected, effectively finding similar points and improving compression / reconstruction performance. Furthermore, by considering both inter-frame and intra-frame modes, the most efficient mode can be effectively selected between inter-frame and intra-frame modes based on point characteristics. When the proposed geometric attribute coding method is used within a frame, geometric coding using prediction trees achieves low-latency coding, but low-latency operation is not possible with attribute compression. Therefore, true low-latency coding is not possible. In addition, the proposed method can improve the attribute compression performance by further providing a method for selecting a prediction sub-node in a reference frame based on a laser ID and a method for determining compression based on an inter-frame / intra-frame prediction sub-node set. According to an embodiment, inter-frame coding can be performed to improve the compression efficiency of attribute coding during point cloud compression. Instead of using conventional Morton-based sorting, azimuth-based sorting can be performed based on the characteristics of the point cloud (one laser only acquires one point), and only the information required for attribute compression can be utilized. Therefore, the amount of calculation and time spent on unnecessary coordinate transformations and Morton-based sorting can be effectively reduced. Further, by searching for the correct attribute value in the inter-frame information, the compression efficiency can be improved.

[0484] The embodiments have been described from the perspective of the method and / or the apparatus, and the descriptions of the method and the apparatus may be applied so as to complement each other.

[0485] Although the drawings are described separately for simplicity, new embodiments can be designed by combining the embodiments shown in the various figures. Designing a recording medium that can be read by a computer and records a program for executing the above-mentioned embodiments according to the needs of those skilled in the art also falls within the scope of the attached claims and their equivalents. The apparatus and method according to the embodiment may not be limited to the configuration and method of the above-mentioned embodiment. Various modifications can be made to the embodiment by selectively combining all or some of the embodiments. Although preferred embodiments have been described with reference to the drawings, it will be understood by those skilled in the art that various modifications and changes can be made to the embodiment without departing from the spirit or scope of the present disclosure described in the attached claims. These modifications should not be understood separately from the technical ideas or viewpoints of the embodiment.

[0486] The various elements of the device of the embodiment can be implemented by hardware, software, firmware or a combination thereof. The various elements in the embodiment can be implemented by a single chip (e.g., a single hardware circuit). According to the embodiment, the components according to the embodiment can be implemented as separate chips respectively. According to the embodiment, at least one or more components of the device according to the embodiment may include one or more processors capable of executing one or more programs. One or more programs can execute any one or more operations / methods according to the embodiment or include instructions for executing them. The executable instructions for executing the method / operation of the device according to the embodiment can be stored in a non-transitory CRM or other computer program product configured to be executed by one or more processors, or can be stored in a temporary CRM or other computer program product configured to be executed by one or more processors. In addition, the memory according to the embodiment can be used as not only covering volatile memory (e.g., RAM), but also covering the concept of non-volatile memory, flash memory and PROM. In addition, it can also be implemented in the form of a carrier wave (e.g., transmission via the Internet). In addition, the processor-readable recording medium can be distributed to computer systems connected via a network so that the processor-readable code can be stored and executed in a distributed manner.

[0487] In this specification, the terms " / " and "," should be interpreted as indicating "and / or". For example, the expression "A / B" may mean "A and / or B". In addition, "A, B" may mean "A and / or B". In addition, "A / B / C" may mean "at least one of A, B and / or C". In addition, "A / B / C" may mean "at least one of A, B and / or C". In addition, in this specification, the term "or" should be interpreted as indicating "and / or". For example, the expression "A or B" may mean 1) only A, 2) only B, or 3) both A and B. In other words, the term "or" used in this document should be interpreted as indicating "in addition or alternatively".

[0488] Terms such as first and second may be used to describe various elements of an embodiment. However, the various components according to the embodiment should not be limited by the above terms. These terms are only used to distinguish one element 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 not be interpreted without departing from the scope of the various embodiments. Both the first user input signal and the second user input signal are user input signals, but unless the context clearly dictates otherwise, they do not refer to the same user input signal.

[0489] The terms used to describe the embodiments are used to describe specific embodiments and are not intended to limit the embodiments. As used in the description of the embodiments and in the claims, unless the context clearly dictates otherwise, the singular includes the plural referents. The expression "and / or" is used to include all possible combinations of terms. Terms such as "including" or "having" are intended to indicate the presence of graphics, quantities, steps, elements and / or components, and should be understood as not excluding the possibility of additional presence of graphics, quantities, steps, elements and / or components. As used herein, conditional expressions such as "if" and "when" are not limited to optional cases, and are intended to be interpreted as performing relevant operations or interpreting relevant definitions according to specific conditions when specific conditions are met.

[0490] The operations described in this specification according to the embodiments may be performed by a transmitting / receiving 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 the various operations described in this specification. The processor may be referred to as a controller, etc. In the embodiments, the operations may be performed by firmware, software, and / or a combination thereof. The firmware, software, and / or a combination thereof may be stored in the processor or the memory.

[0491] The operations according to the above-described embodiments may be performed by a transmitting device and / or a receiving device according to the embodiments. The transmitting / receiving device includes: a transmitter / receiver configured to transmit and receive media data; a memory configured to store instructions (program code, algorithm, flow chart, and / or data) for the process according to the embodiments; and a processor configured to control the operation of the transmitting / receiving device.

[0492] The processor may be referred to as a controller, etc., 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. In addition, the processor may be implemented as an encoder / decoder for the operations of the above-described embodiments.

[0493] Invention Mode

[0494] As described above, the relevant contents are described in the best mode for carrying out the embodiment.

[0495] Industrial Applicability

[0496] As described above, the embodiments may be applied in whole or in part to a point cloud data transmitting / receiving device and system.

[0497] It is obvious to those skilled in the art that various changes or modifications can be made to the embodiments within the scope of the embodiments.

[0498] Thus, it is intended that the embodiments cover the modifications and variations of this disclosure provided they come within the scope of the appended claims and their equivalents.

Claims

1. A method for sending point cloud data, the method comprising the following steps: Encoding point cloud data; and A bitstream containing the point cloud data is sent.

2. The method according to claim 1, wherein: Encoding the point cloud data includes: Encoding the point cloud data based on a prediction tree, The point cloud data is predicted based on points included in a reference frame of a current frame including the point cloud data.

3. The method according to claim 1, wherein: Encoding the point cloud data includes: The points of the point cloud data are sorted based on azimuth according to the laser ID.

4. The method according to claim 3, wherein: sorting points contained in a current frame containing the point cloud data and a reference frame of the current frame based on the laser ID and the azimuth, Therein, a predictor for the point in the current frame is selected from the sorted points in the current frame and the reference frame.

5. The method according to claim 4, wherein: Encoding the point cloud data includes: Encoding the attributes of the point cloud data, The attribute is predicted based on the attribute and weight contained in the reference frame.

6. The method according to claim 5, predicting the attribute based on the attribute of the reference frame according to the value generated based on the attribute of the current frame, the attribute of the reference frame and the weight being greater than or equal to a threshold, in, According to the value generated based on the attribute of the current frame, the attribute of the reference frame and the weight being smaller than the threshold, the attribute is predicted based on the attribute of the current frame.

7. The method according to claim 6, wherein: The bitstream includes information indicating whether to generate a predictor based on the laser ID, information indicating the weight, and information indicating the threshold.

8. A device for sending point cloud data, the device comprising: an encoder configured to encode the point cloud data; as well as A transmitter is configured to transmit a bit stream containing the point cloud data.

9. A method for receiving point cloud data, the method comprising: receiving a bitstream containing point cloud data; as well as The point cloud data is decoded.

10. The method according to claim 9, wherein: Decoding the point cloud data includes: Decoding the point cloud data based on the prediction tree, The point cloud data is predicted based on points included in a reference frame of a current frame including the point cloud data.

11. The method according to claim 9, wherein: Decoding the point cloud data includes: The points of the point cloud data are sorted based on azimuth according to the laser ID.

12. The method according to claim 11, wherein: sorting points contained in a current frame containing the point cloud data and a reference frame of the current frame based on the laser ID and the azimuth, Therein, a predictor for the point in the current frame is selected from the sorted points in the current frame and the reference frame.

13. The method according to claim 12, wherein: Decoding the point cloud data includes: Decoding the attributes of the point cloud data, The attribute is predicted based on the attribute and weight contained in the reference frame.

14. The method according to claim 13, predicting the attribute based on the attribute of the reference frame according to the value generated based on the attribute of the current frame, the attribute of the reference frame and the weight being greater than or equal to a threshold, in, According to the value generated based on the attribute of the current frame, the attribute of the reference frame and the weight being smaller than the threshold, the attribute is predicted based on the attribute of the current frame.

15. A device for receiving point cloud data, the device comprising: a receiver configured to receive a bitstream containing point cloud data; as well as A decoder is configured to decode the point cloud data.