Mesh data encoding apparatus, mesh data encoding method, mesh data decoding apparatus, and mesh data decoding method

By utilizing mesh data encoding and decoding methods within the V-MESH compression standard, the system addresses the inefficiencies in point cloud data transmission and reception, achieving reduced latency and improved processing efficiency for applications such as autonomous driving and augmented reality.

WO2025135958A1PCT designated stage expired Publication Date: 2025-06-26LG ELECTRONICS INC
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2024/096473
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-12-20
Filing Date
2024-11-13
Publication Date
2025-06-26

AI Technical Summary

Technical Problem

The challenge lies in efficiently transmitting and receiving point cloud data due to its large size and complexity, which results in high processing requirements and latency issues.

Method used

The implementation of a point cloud data transmission and reception system that employs mesh data encoding and decoding methods, such as the V-MESH compression standard, to reduce data size and improve processing efficiency.

Benefits of technology

This approach enables efficient transmission and reception of point cloud data, reducing latency and encoding/decoding complexity, thereby providing a high-quality point cloud service for applications like autonomous driving and augmented reality.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024096473_26062025_PF_FP_ABST
    Figure KR2024096473_26062025_PF_FP_ABST
Patent Text Reader

Abstract

A decoding method according to embodiments may comprise the steps of: receiving a bitstream including mesh data; and decoding the mesh data. The decoding method according to embodiments may comprise the steps of: encoding mesh data; and transmitting a bitstream including the mesh data.
Need to check novelty before this filing date? Find Prior Art

Description

Mesh data encoding device, mesh data encoding method, mesh data decoding device, and mesh data decoding method

[0001] The embodiments provide a method for providing Point Cloud content to provide users with various services such as Virtual Reality (VR), Augmented Reality (AR), Mixed Reality (MR), and autonomous driving services.

[0002] A point cloud is a collection of points in 3D space. The sheer number of points in 3D space makes it difficult to generate point cloud data.

[0003] There is a problem that a lot of processing power is required to transmit and receive point cloud data.

[0004] The technical problem according to the embodiments is to provide a point cloud data transmission device, transmission method, point cloud data reception device and reception method for efficiently transmitting and receiving point clouds in order to solve the problems described above.

[0005] The technical problem according to the embodiments is to provide a point cloud data transmission device, transmission method, point cloud data reception device, and reception method for resolving latency and encoding / decoding complexity.

[0006] However, the scope of the embodiments is not limited to the aforementioned technical tasks, and the scope of the embodiments may be expanded to other technical tasks that can be inferred by a person skilled in the art based on the entire contents of this document.

[0007] In order to achieve the above-described purpose and other advantages, a decoding method according to embodiments may include a step of receiving a bitstream including mesh data; and a step of decoding the mesh data. A decoding method according to embodiments may include a step of encoding the mesh data; and a step of transmitting a bitstream including the mesh data.

[0008] The point cloud data transmission method, transmission device, point cloud data reception method, and reception device according to the embodiments can provide a high-quality point cloud service.

[0009] The point cloud data transmission method, transmission device, point cloud data reception method, and reception device according to the embodiments can achieve various video codec methods.

[0010] The point cloud data transmission method, transmission device, point cloud data reception method, and reception device according to the embodiments can provide general-purpose point cloud content such as autonomous driving services.

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

[0012] Figure 1 illustrates a system for providing dynamic mesh content according to embodiments.

[0013] Figure 2 illustrates a V-MESH compression method according to embodiments.

[0014] Figure 3 illustrates pre-processing of V-MESH compression according to embodiments.

[0015] Figure 4 illustrates a mid-edge subdivision method according to embodiments.

[0016] Figure 5 shows a displacement generation process according to embodiments.

[0017] FIG. 6 illustrates an intra-frame encoding process of a V-MESH compression method according to embodiments.

[0018] Figure 7 illustrates an inter-frame encoding process of a V-MESH compression method according to embodiments.

[0019] Figure 8 shows a lifting conversion process for displacement according to embodiments.

[0020] Figure 9 illustrates a process of packing transformation coefficients according to embodiments into a 2D image.

[0021] Fig. 10 shows an attribute transfer process of a V-MESH compression method according to embodiments.

[0022] Fig. 11 illustrates an intra-frame decoding process of a V-MESH compression method according to embodiments.

[0023] Fig. 12 shows a V-MES and Fig. 13 shows a point cloud data transmission device according to embodiments.

[0024] Fig. 13 shows a point cloud data transmission device according to embodiments.

[0025] Fig. 14 shows a point cloud data receiving device according to embodiments.

[0026] Figure 15 illustrates a valence adaptive lifting update according to embodiments.

[0027] Figure 16 shows lifting transform parameters according to embodiments.

[0028] Figure 17 shows an encoding method according to embodiments.

[0029] Figure 18 shows a decryption method according to embodiments.

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

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

[0032] Figure 1 illustrates a system for providing dynamic mesh content according to embodiments.

[0033] The system of FIG. 1 includes a point cloud data transmission device (100) and a point cloud data reception device (110) according to embodiments. The point cloud data transmission device may include a dynamic mesh video acquisition unit (101), a dynamic mesh video encoder (102), a file / segment encapsulator (103), and a transmitter (104). The point cloud data reception device (110) may include a reception unit (111), a file / segment decapsulator (112), a dynamic mesh video decoder (113), and a renderer (114). Each component of FIG. 1 may correspond to hardware, software, a processor, and / or a combination thereof. Hereinafter, the point cloud data transmission device according to embodiments may be interpreted as a term referring to the transmission device (100) or a dynamic mesh video encoder (hereinafter, referred to as an encoder) (102). The point cloud data receiving device according to the embodiments may be interpreted as a term referring to a receiving device (110) or a dynamic mesh video decoder (hereinafter, decoder) (113).

[0034] The system of Fig. 1 can perform video-based dynamic mesh compression and decompression.

[0035] Advances in 3D capture, modeling, and rendering have enabled users to consume diverse forms of 3D content, such as AR, XR, metaverse, and holograms, across multiple platforms and devices. 3D content increasingly represents objects with greater precision and realism, enabling users to enjoy immersive experiences. To achieve this, the creation and use of 3D models requires a significant amount of data. Among various types of 3D content, 3D meshes are widely used for efficient data utilization and realistic object representation. Embodiments include a series of processing steps in a system that utilizes such mesh content.

[0036] First, the method of compressing dynamic mesh data starts with the V-PCC (Video-based point cloud compression) standard technology. Point cloud data is data that contains color information at the vertex coordinates (X, Y, Z). Mesh data refers to data in which connectivity information between vertices is added to this vertex information. When creating content, it can be created in the form of mesh data from the beginning. By adding connectivity information to point cloud data, it can be converted into mesh data and used.

[0037] Currently, the MPEG standards body defines two types of dynamic mesh data: Category 1: Mesh data with texture maps as color information. Category 2: Mesh data with vertex colors as color information.

[0038] Mesh coding standards for Category 1 data are currently under development, and work on Category 2 data standards is also planned for the future. The overall process for providing mesh content services may include acquisition, encoding, transmission, decoding, rendering, and / or feedback, as shown in Figure 1.

[0039] To provide mesh content services, 3D data acquired through multiple cameras or specialized cameras can be processed into mesh data types through a series of processes and then converted into video. The generated mesh video is then transmitted through a series of processes, and the receiving end can then reprocess the received data into mesh video and render it. This allows mesh video to be presented to users, who can then interact with the mesh content according to their intended intent.

[0040] A mesh compression system may include a transmitting device and a receiving device. The transmitting device can encode mesh video to output a bitstream, which can be delivered to the receiving device via digital storage media or a network in the form of a file or streaming segment. The digital storage media may include various storage media, such as USB, SD, CD, DVD, Blu-ray, HDD, or SSD.

[0041] The transmitting device may roughly include a mesh video acquisition unit, a mesh video encoder, and a transmitting unit. The receiving device may roughly include a receiving unit, a mesh video decoder, and a renderer. The encoder may be referred to as a mesh video / video / picture / frame encoding device, and the decoder may be referred to as a mesh video / video / picture / frame decoding device. The transmitter may be included in the mesh video encoder. The receiver may be included in the mesh video decoder. The renderer may include a display unit, and the renderer and / or the display unit may be configured as separate devices or external components. The transmitting device and the receiving device may further include separate internal or external modules / units / components for a feedback process.

[0042] Mesh data represents the surface of an object as a number of polygons. Each polygon is defined by its vertices in 3D space and connection information that describes how those vertices are connected. It can also contain vertex properties such as vertex color and normal. Mapping information that allows the surface of the mesh to be mapped to a 2D planar area can also be included as a mesh property. The mapping is typically described as a set of parametric coordinates, called UV coordinates or texture coordinates, associated with the mesh vertices. Meshes contain 2D attribute maps, which can be used to store high-resolution attribute information such as textures, normals, and displacement.

[0043] The mesh video acquisition unit may include processing 3D object data acquired through a camera, etc. into a mesh data type with the properties described above through a series of processes and generating a video composed of such mesh data. The mesh video may have properties of the mesh, such as vertices, polygons, connection information between vertices, colors, normals, etc., that may change over time. A mesh video with properties and connection information that change over time can be expressed as a dynamic mesh video.

[0044] A mesh video encoder can encode an input mesh video into one or more video streams. A single video can include multiple frames, and a single frame can correspond to a still image / picture. In this document, a mesh video can include a mesh image / frame / picture, and the mesh video can be used interchangeably with the mesh image / frame / picture. A mesh video encoder can perform a Video-based Dynamic Mesh (V-Mesh) Compression procedure. A mesh video encoder can perform a series of procedures such as prediction, transformation, quantization, and entropy coding for compression and coding efficiency. The encoded data (encoded video / image information) can be output in the form of a bitstream.

[0045] The encapsulation processing unit (file / segment encapsulation module) can encapsulate encoded mesh video data and / or mesh video-related metadata in the form of a file, etc. Here, the mesh video-related metadata may be received from the metadata processing unit, etc. The metadata processing unit may be included in the mesh video encoder, or may be configured as a separate component / module. The encapsulation processing unit may encapsulate the corresponding data in a file format such as ISOBMFF, or process it in the form of other DASH segments, etc. The encapsulation processing unit may include mesh video-related metadata in the file format according to an embodiment. The mesh video metadata may be included in boxes at various levels in the ISOBMFF file format, for example, or may be included as data in a separate track within the file. According to an embodiment, the encapsulation processing unit may encapsulate mesh video-related metadata itself in a file.

[0046] The transmission processing unit can process encapsulated mesh video data for transmission according to the file format. The transmission processing unit can be included in the transmission unit, or can be configured as a separate component / module. The transmission processing unit can process mesh video data according to any transmission protocol. The processing for transmission can include processing for transmission through a broadcast network or processing for transmission through broadband. According to an embodiment, the transmission processing unit can receive not only mesh video data but also mesh video-related metadata from the metadata processing unit and process the same for transmission.

[0047] The transmission unit can transmit encoded video / image information or data output in the form of a bitstream to the receiving unit of a receiving device via a digital storage medium or network in the form of a file or streaming. The digital storage medium can include various storage media such as USB, SD, CD, DVD, Blu-ray, HDD, SSD, etc. The transmission unit can include an element for generating a media file via a predetermined file format and can include an element for transmission via a broadcasting / communication network. The receiving unit can extract the bitstream and transmit it to a decoding device.

[0048] The receiver can receive mesh video data transmitted by a mesh video transmission device. Depending on the transmission channel, the receiver can receive mesh video data via a broadcast network, via broadband, or via digital storage media.

[0049] The receiving processing unit can perform processing on the received mesh video data according to a transmission protocol. The receiving processing unit can be included in the receiving unit, or can be configured as a separate component / module. In response to the processing performed for transmission on the transmitting side, the receiving processing unit can perform the reverse process of the aforementioned transmitting processing unit. The receiving processing unit can transfer the acquired mesh video data to the decapsulation processing unit, and transfer the acquired mesh video-related metadata to a metadata parser. The mesh video-related metadata acquired by the receiving processing unit can be in the form of a signaling table.

[0050] A decapsulation processing unit (file / segment decapsulation module) can decapsulate mesh video data in file format received from a receiving processing unit. The decapsulation processing unit can decapsulate files according to ISOBMFF, etc., to obtain a mesh video bitstream or mesh video-related metadata (metadata bitstream). The obtained mesh video bitstream can be transmitted to a mesh video decoder, and the obtained mesh video-related metadata (metadata bitstream) can be transmitted to a metadata processing unit. The mesh video bitstream may include metadata (metadata bitstream). The metadata processing unit may be included in the mesh video decoder, or may be configured as a separate component / module. The mesh video-related metadata obtained by the decapsulation processing unit may be in the form of a box or track within a file format. If necessary, the decapsulation processing unit may receive metadata required for decapsulation from the metadata processing unit. Mesh video related metadata can be passed to a Mesh video decoder for use in the Mesh video decoding process, or passed to a renderer for use in the Mesh video rendering process.

[0051] A mesh video decoder can receive a bitstream and perform operations corresponding to those of a mesh video encoder to decode video / images. The decoded mesh video can be displayed via a display unit. Users can view all or part of the rendered result via a VR / AR display or a general display.

[0052] The feedback process may include a process of transmitting various feedback information that may be acquired during the rendering / display process to the transmitter or to the decoder on the receiver. Interactivity may be provided in mesh video consumption through the feedback process. Depending on the embodiment, head orientation information, viewport information indicating the area that the user is currently viewing, etc. may be transmitted during the feedback process. Depending on the embodiment, the user may interact with things implemented in the VR / AR / MR / autonomous driving environment, in which case information related to the interaction may be transmitted to the transmitter or the service provider during the feedback process. Depending on the embodiment, the feedback process may not be performed.

[0053] Head orientation information can refer to information about the user's head position, angle, and movement. Based on this information, information about the area the user is currently viewing within the mesh video, i.e. viewport information, can be calculated.

[0054] Viewport information can be information about the area the user is currently viewing in the mesh video. This can be used to perform gaze analysis to determine how the user consumes the mesh video, which area of ​​the mesh video they are gazing at, and for how long. Gaze analysis can be performed on the receiving side and transmitted to the transmitting side through a feedback channel. Devices such as VR / AR / MR displays can extract the viewport area based on the user's head position / orientation, the vertical or horizontal FOV supported by the device, etc.

[0055] Depending on the embodiment, the aforementioned feedback information may not only be transmitted to the transmitter but may also be consumed by the receiver. That is, the aforementioned feedback information may be utilized to perform decoding, rendering, and other processes on the receiver. For example, head orientation information and / or viewport information may be utilized to preferentially decode and render only the mesh video for the area currently being viewed by the user.

[0056] This document relates to dynamic mesh video compression as described above. The method / embodiment disclosed in this document can be applied to the Video-based Dynamic Mesh Compression (V-Mesh) standard of the Moving Picture Experts Group (MPEG) or the next-generation video / image coding standard. Dynamic mesh video compression is a method for processing mesh connection information and properties that change over time, and it can perform lossy and lossless compression for various applications such as real-time communication, storage, free-view video, and AR / VR.

[0057] The dynamic mesh video compression method described below is based on MPEG's V-Mesh method.

[0058] In this document, picture / frame can generally mean a unit representing one video of a specific time period.

[0059] A pixel or pel can refer to the smallest unit that constitutes a picture (or image). Additionally, the term "sample" can be used as a counterpart to a pixel. A sample can generally represent a pixel or a pixel value, and can represent only the pixel / pixel value of the luma component, only the pixel / pixel value of the chroma component, or only the pixel / pixel value of the depth component.

[0060] A unit may represent a basic unit of image processing. A unit may include at least one of a specific region of a picture and information related to the region. In some cases, the term "unit" may be used interchangeably with terms such as "block" or "area." In general, an MxN block may include a set (or array) of samples (or sample array) or transform coefficients consisting of M columns and N rows.

[0061] The encoding process of Figure 1 is as follows.

[0062] Video-based dynamic mesh compression (V-Mesh) compression methods can provide a method for compressing dynamic mesh video data based on 2D video codecs such as HEVC and VVC. The V-Mesh compression process receives the following data as input and performs compression.

[0063] Input mesh: Contains the 3D coordinates (geometry) of the vertices that make up the mesh, normal information for each vertex, mapping information that maps the mesh surface to a 2D plane, and connection information between the vertices that make up the surface. The mesh surface can be expressed as triangles or more polygons, and connection information between the vertices that make up each surface is stored according to a set shape. The input mesh can be saved in the OBJ file format.

[0064] Attribute map: (Hereinafter, texture map is also used in the same meaning): Contains information about the properties (color, normal, displacement, etc.) of the mesh, and stores data in the form of a mapping of the surface of the mesh onto a 2D image. Mapping which part (surface or vertex) of the mesh each data of this attribute map corresponds to is based on the mapping information contained in the input mesh. Since the attribute map has data for each frame of the mesh video, it can also be expressed as an attribute map video (or attribute for short). The attribute map in the V-Mesh compression method mainly contains the color information of the mesh, and is saved in an image file format (PNG, BMP, etc.).

[0065] Material Library File: Contains information about the material properties used in a mesh, particularly information that links the input mesh to its corresponding attribute map. It is saved in the Wavefront Material Template Library (MTL) file format.

[0066] In the V-Mesh compression method, the following data and information can be generated through the compression process.

[0067] Base mesh: The input mesh is simplified (decimated) through a preprocessing process to express the objects of the input mesh using the minimum number of vertices determined by the user's standards.

[0068] Displacement: This is displacement information used to express the input mesh as similarly as possible to the base mesh, and is expressed in the form of 3D coordinates.

[0069] Atlas information: This is the metadata required to reconstruct a mesh using base mesh, displacement, and attribute map information. It can be created and utilized as sub-mesh units (such as patches) that make up the mesh.

[0070] Referring to FIGS. 2 to 7, a method for encoding mesh position information (vertex) is described, and referring to FIGS. 6-10, etc., a method for encoding attribute information (attribute map) by restoring mesh position information is described.

[0071] Figure 2 illustrates a V-MESH compression method according to embodiments.

[0072] Fig. 2 illustrates the encoding process of Fig. 1, and the encoding process may include a pre-processing process and an encoding process. The encoder of Fig. 1 may include a pre-processor (200) and an encoder (201) as in Fig. 2. The transmitting device of Fig. 1 may be broadly referred to as an encoder, and the dynamic mesh video encoder of Fig. 1 may be referred to as an encoder. The V-Mesh compression method may include a pre-processing (200) and an encoding (201) process as in Fig. 2. The pre-processor of Fig. 2 may be located in front of the encoder of Fig. 2. The pre-processor and the encoder of Fig. 2 may be referred to as a single encoder.

[0073] The preprocessor can receive a static dynamic mesh and / or an attribute map. The preprocessor can generate a base mesh and / or displacement through preprocessing. The preprocessor can receive feedback information from the encoder and generate the base mesh and / or displacement based on the feedback information.

[0074] The encoder can receive a base mesh, displacement mesh, static dynamic mesh, and / or attribute map. The encoder can encode mesh-related data to generate a compressed bitstream.

[0075] Figure 3 illustrates pre-processing of V-MESH compression according to embodiments.

[0076] Figure 3 shows the configuration and operation of the pre-processor of Figure 2.

[0077] Fig. 3 shows a process of performing preprocessing on an input mesh. The preprocessing process (200) can be broadly divided into four steps: 1) Group of Frame (GoF) generation, 2) Mesh Decimation, 3) UV parameterization, and 4) Fitting subdivision surface (300). The preprocessor (200) can receive an input mesh, generate a displacement and / or base mesh, and transmit the generated displacement and / or base mesh to the encoder (201). The preprocessor (200) can transmit GoF information related to GoF generation to the encoder (201).

[0078] Below, each step of Figure 3 is described.

[0079] GoF Generation: This is the process of generating a reference structure for mesh data. If the number of vertices, number of texture coordinates, vertex connection information, and texture coordinate connection information of the mesh of the previous frame and the current mesh are all the same, the previous frame can be set as the reference frame. In other words, if only the vertex coordinate values ​​are different between the current input mesh and the reference input mesh, inter-frame encoding can be performed. Otherwise, the frame performs intra-frame encoding.

[0080] Mesh Decimation: This process simplifies the input mesh to create a simplified mesh, or base mesh. Vertices to be removed from the original mesh are selected based on user-defined criteria, and the selected vertices and the triangles connected to them can be removed.

[0081] In the process of performing mesh simplification (Mesh decimation), the input mesh (voxelized), target triangle ratio (TTR), and minimum triangle component (CCCount) information are passed as input, and the simplified mesh (decimated mesh) can be obtained as output. In this process, connected triangle components smaller than the set minimum triangle component (CCCount) can be removed.

[0082] UV parameterization: This is the process of mapping a 3D surface of a decimated mesh into a texture domain. Parameterization can be performed using the UVAtlas tool. This process generates mapping information, which indicates where each vertex of the decimated mesh can be mapped to on a 2D image. This mapping information is expressed and stored as texture coordinates, and through this process, the final base mesh is created.

[0083] Fitting subdivision surface: This is the process of performing subdivision on a simplified mesh. The subdivision method can be a user-defined method, such as the mid-edge method. The fitting process ensures that the input mesh and the subdivision mesh are similar to each other.

[0084] Figure 4 illustrates a mid-edge subdivision method according to embodiments.

[0085] Figure 4 illustrates the mid-edge method of the fitting subdivision surface described in Figure 3. Referring to Figure 4, an original mesh containing four vertices is subdivided to create a sub-mesh. A sub-mesh can be created by creating a new vertex midway between the edges between the vertices.

[0086] When a fitted subdivided mesh (hereinafter referred to as a fitted subdivided mesh) is generated, displacement is calculated using this result and a pre-compressed and decrypted base mesh (hereinafter referred to as a reconstructed base mesh). That is, the reconstructed base mesh is subdivided in the same way as the fitting subdivision surface. The difference in position of each vertex between this result and the fitted subdivided mesh is the displacement for each vertex. Since displacement represents a position difference in three-dimensional space, it is also expressed as a value in the (x, y, z) space of a Cartesian coordinate system. Depending on the user input parameters, the (x, y, z) coordinate values ​​can be converted to (normal, tangential, bi-tangential) coordinate values ​​of the local coordinate system.

[0087] Figure 5 shows a displacement generation process according to embodiments.

[0088] FIG. 5 illustrates in detail the displacement calculation method of the fitting subdivision surface (300) as described in FIG. 4.

[0089] An encoder and / or pre-processor according to embodiments may include 1) a subdivision unit, 2) a local coordinate system calculation unit, and 3) a displacement calculation unit. The subdivision unit may receive a reconstructed base mesh and generate a subdivided reconstructed base mesh. The local coordinate system calculation unit may receive a fitted subdivision mesh and a subdivided reconstructed base mesh, and transform a coordinate system of the mesh into a local coordinate system. The local coordinate system calculation operation may be optional. The displacement calculation unit may calculate a positional difference between the fitted subdivision mesh and the subdivided reconstructed base mesh. For example, a positional difference value between vertices of two input meshes may be generated. The vertex positional difference value becomes a displacement.

[0090] The method and device for transmitting point cloud data according to the embodiments can encode the point cloud as follows. The point cloud data (which may be referred to as a point cloud for short) according to the embodiments can refer to data including vertex coordinates and color information. The term "point cloud" includes mesh data, and in this document, point cloud and mesh data can be used interchangeably.

[0091] The V-Mesh compression (reconstruction) method according to the embodiments may include intra frame encoding (Fig. 6) and inter frame encoding (Fig. 7).

[0092] Based on the results of the GoF generation described above, intra-frame encoding or inter-frame encoding is performed. In the case of intra-encoding, the data to be compressed may be a base mesh, displacement, attribute map, etc. In the case of inter-encoding, the data to be compressed may be a displacement, attribute map, and a motion field between a reference base mesh and the current base mesh.

[0093] FIG. 6 illustrates an intra-frame encoding process of a V-MESH compression method according to embodiments.

[0094] The encoding process of Fig. 6 details the encoding of Fig. 1. That is, it shows the configuration of an encoder when the encoding of Fig. 1 is an intra-frame method. The encoder of Fig. 6 may include a preprocessor (200) and / or an encoder (201).

[0095] The preprocessor can receive an input mesh and perform the preprocessing described above. The preprocessing can generate a base mesh and / or a fitted subdivided mesh. The quantizer can quantize the base mesh and / or the fitted subdivided mesh. The static mesh encoder can encode the static mesh. The static mesh encoder can generate a bitstream including the encoded base mesh. The static mesh decoder can decode the encoded static mesh. The inverse quantizer can inversely quantize the quantized static mesh. The displacement calculation unit can receive the reconstructed static mesh and generate displacement, which is a position difference, based on the fitted subdivided mesh. The forward linear lifting unit can receive the displacement and generate lifting coefficients. The quantizer can quantize the lifting coefficients. The image packing unit can pack an image based on the quantized lifting coefficients. A video encoder can encode a packed image. A video decoder decodes the encoded video. An image unpacker can unpack a packed image. A dequantizer can inversely quantize an image. An inverse linear lifting unit applies inverse lifting to the image to generate a reconstructed displacement. A mesh restoration unit restores a warped mesh using the reconstructed displacement and the reconstructed base mesh. An attribute transfer unit receives an input mesh and / or an input attribute map, and generates an attribute map based on the reconstructed warped mesh. A push-pull padding unit can pad data in the attribute map based on a push-pull method. A color space transformation unit can transform the space of a color component, which is an attribute. A video encoder can encode an attribute. A multiplexer can generate a bitstream by multiplexing a compressed base mesh, compressed displacement, and compressed attributes.

[0096] Figure 7 illustrates an inter-frame encoding process of a V-MESH compression method according to embodiments.

[0097] The encoding process of Fig. 7 details the encoding of Fig. 1. That is, it shows the configuration of an encoder when the encoding of Fig. 1 is an inter-frame method. The encoder of Fig. 7 may include a preprocessor (200) and / or an encoder (201).

[0098] Among the encoding operations of Fig. 7, the corresponding configuration of the encoding operation of Fig. 6 refers to the description of Fig. 7. For the inter-frame-based encoding of Fig. 7, the motion encoder can encode motion based on the restored quantized reference base mesh. The base mesh restoration unit can restore the base mesh based on the restored quantized reference base mesh.

[0099] The encoder of Fig. 6 generates a bitstream by compressing the base mesh, displacement, and attributes within the frame, and the encoder of Fig. 7 generates a bitstream by compressing the motion, displacement, and attributes between the current frame and the reference frame.

[0100] The encoding method according to the embodiments includes base mesh encoding (intra encoding). When performing intra frame encoding on the current input mesh frame, the base mesh generated in the preprocessing process can be encoded using a static mesh compression technique after going through a quantization process. In the V-Mesh compression method, for example, Draco technology is applied, and the vertex position information, mapping information (texture coordinates), vertex connection information, etc. of the base mesh are compressed.

[0101] The encoding method according to the embodiments may include motion field encoding (inter encoding). Inter frame encoding may be performed when a one-to-one correspondence of vertices is established between a reference mesh and a current input mesh, and only the position information of the vertices is different. When performing inter frame encoding, instead of compressing the base mesh, the difference between the vertices of the reference base mesh and the current base mesh, i.e., the motion field, may be calculated and this information may be encoded. The reference base mesh is the result of quantizing the already decoded base mesh data and is determined according to the reference frame index determined in the GoF generation. The motion field may be encoded as a value. Alternatively, the predicted motion field may be calculated by averaging the motion fields of the restored vertices among the vertices connected to the current vertex, and this predicted motion field The residual motion field, which is the difference between the value and the motion field value of the current vertex, can be encoded. This value can be encoded using entropy coding. The process of encoding the displacement and attribute map, excluding the motion field encoding process of inter-frame encoding, is the same as the structure of the intra-frame encoding method except for the base mesh encoding.

[0102] Figure 8 shows a lifting conversion process for displacement according to embodiments.

[0103] Figure 9 illustrates a process of packing transformation coefficients according to embodiments into a 2D image.

[0104] Figures 8-9 show the process of converting the displacement of the encoding process of Figures 6-7 and the process of packing the conversion coefficients, respectively.

[0105] The encoding method according to the embodiments includes displacement encoding.

[0106] After encoding the base mesh through base mesh encoding and / or motion field encoding, a reconstructed base mesh is generated through restoration and dequantization, and the displacement between the result of performing subdivision on the reconstructed base mesh and the fitted subdivided mesh generated through the fitting subdivision surface can be calculated. For effective encoding, a data transform process such as wavelet transform can be applied to the displacement information.

[0107] Figure 8 shows the process of transforming displacement information using lifting transform in V-Mesh. The transform coefficients generated through the transform process are quantized and then packed into a 2D image as shown in Figure 9. The transform coefficients are organized into one block for each 256 (=16×16) units, and each block can be packed in z-scan order. The horizontal number of blocks is fixed to 16, but the vertical number of blocks can be determined according to the number of vertices of the subdivided base mesh. The transform coefficients can be packed by sorting them with Morton code within a block. The packed images generate a displacement video for each GoF unit, and this displacement video can be encoded using an existing video compression codec.

[0108] Referring to FIG. 8, the base mesh (original) may include vertices and edges for LoD0. The first subdivision mesh generated by dividing the base mesh includes vertices generated by further dividing the edges of the base mesh. The first subdivision mesh includes vertices for LoD0 and vertices for LoD1. LoD1 includes the subdivided vertices and the vertices (LoD0) of the base mesh. The first subdivision mesh may be generated by dividing the second subdivision mesh. The second subdivision mesh includes LoD2. LoD2 includes the base mesh vertices (LoD0), LoD1 including the vertices additionally generated from LoD0, and the vertices additionally divided from LoD1. LoD is a level indicating the degree of detail (Level of Detail), and as the level index increases, the distance between vertices becomes closer and the level of detail increases. LoD N includes the vertices included in the previous LoDN-1 as they are. When a vertex is further divided through subdivision, considering the previous vertices v1, v2 and the subdivided vertex v, the mesh can be encoded based on a prediction and / or update method. Instead of still encoding information about the current LoD N, a residual value between the previous LoD N-1 can be generated, and the mesh can be encoded using the residual value to reduce the size of the bitstream. The prediction process means the operation of predicting the current vertex v using the previous vertices v1, v2. Since adjacent subdivision meshes have similar data, efficient encoding can be achieved by utilizing this property. The current vertex position information is predicted as the residual for the previous vertex position information, and the previous vertex position information is updated using the residual.

[0109] Referring to Figure 9, the vertices have coefficients generated through the lifting transformation. The coefficients of the vertices related to the lifting transformation can be encoded by packing them into an image.

[0110] Fig. 10 shows an attribute transfer process of a V-MESH compression method according to embodiments.

[0111] Figure 10 shows the detailed operation of attribute transfer of encoding such as Figures 6-7.

[0112] Encoding according to embodiments includes attribute map encoding.

[0113] Information about the input mesh is compressed through base mesh encoding, motion field encoding, and displacement encoding. In the encoding process, the compressed input mesh is restored through base mesh decoding (intra frame), motion field decoding (inter frame), and displacement video decoding, and the restored result, the reconstructed deformed mesh (hereinafter referred to as Recon. deformed mesh), is used to compress the input attribute map as shown in FIGS. 6 and 7. The reconstructed deformed mesh (Recon. deformed mesh) has vertex position information, texture coordinates, and corresponding connection information, but does not have color information corresponding to the texture coordinates. Therefore, as shown in Fig. 10, in the V-Mesh compression method, a new attribute map having color information corresponding to the texture coordinates of the reconstructed deformed mesh is created through the attribute transfer process.

[0114] Attribute transfer first checks whether each point P(u, v) in the 2D texture domain belongs to a texture triangle of the reconstructed deformed mesh, and if it is in the texture triangle T, calculates the barycentric coordinate (α, β γ) of P(u, v) according to the triangle T. Then, using the 3D vertex position and (α, β γ) of triangle T, calculate the 3D coordinate M(x, y, z) of P(u, v). Find the vertex coordinate M'(x', y', z') that corresponds to the position most similar to the calculated M(x, y, z) in the input mesh domain and the triangle T' that contains this point. And in this triangle T', the center of mass coordinates (α', β', γ') of M'(x', y', z') are calculated. Using the texture coordinates corresponding to the three vertices of triangle T' and (α', β', γ'), the texture coordinates (u', v') are calculated, and the color information corresponding to these coordinates is found in the input attribute map. The color information found in this way is immediately assigned to the pixel location (u, v) of the new attribute map. If P(u, v) does not belong to any triangle, the pixel at that location in the new attribute map can be filled with a color value using a padding algorithm such as the push-pull algorithm.

[0115] The new attribute map generated through attribute transfer is grouped into GoF units to form an attribute map video, which is then compressed using a video codec.

[0116] Referring to Figure 10, the reference relationship between the input mesh, input attribute map, restored mesh, and generated attribute map can be seen.

[0117] The decoding process of Fig. 1 can perform the reverse process of the corresponding encoding process of Fig. 1. The specific decoding process is as follows.

[0118] Fig. 11 illustrates an intra-frame decoding process of a V-MESH compression method according to embodiments.

[0119] Fig. 11 shows the configuration and operation of a decoder of a receiving device such as Fig. 1.

[0120] Figure 11 illustrates the intra decoding process of V-Mesh technology. First, the input bitstream can be separated into a mesh sub-stream, a displacement sub-stream, an attribute map sub-stream, and a sub-stream containing mesh patch information, such as V3C / V-PCC.

[0121] The mesh sub-stream is decoded by the decoder of the static mesh codec used in encoding, such as Google Draco, and as a result, the connection information, vertex geometry information, vertex texture coordinates, etc. of the base mesh can be restored. The displacement sub-stream is decoded into a displacement video by the decoder of the video compression codec used in encoding, and goes through the image unpacking, inverse quantization, and inverse transform processes to restore displacement information for each vertex. Inverse quantization is applied to the restored base mesh, and this result is combined with the restored displacement information to generate the final decoded mesh.

[0122] The attribute map sub-stream is decoded through the decoder of the video compression codec used in encoding, and then restored to the final attribute map through processes such as color format conversion.

[0123] The restored decoded mesh and decoded attribute map can be utilized by the receiver as final mesh data that can be utilized by the user.

[0124] Referring to FIG. 11, the bitstream includes patch information, a mesh substream, a displacement substream, and an attribute map substream. The term "substream" is interpreted as referring to a portion of the bitstream included in the bitstream. The bitstream includes patch information (data), mesh information (data), displacement information (data), and attribute map information (data).

[0125] The decoder performs the following decoding operations within the frame. The static mesh decoder decodes the mesh to generate a reconstructed quantized base mesh, and the inverse quantizer applies the quantization parameters of the quantizer inversely to generate the reconstructed base mesh. The video decoder decodes the displacement, the unpacker unpacks the decoded video image, and the inverse quantizer inversely quantizes the quantized image. The linear lifting inverse transform applies a lifting transform in the reverse process of the encoder to generate the reconstructed displacement. The mesh restoration unit generates a warped mesh based on the base mesh and the displacement. The video decoder decodes the attribute map, and the color transformation unit transforms the color format and / or space to generate the decoded attribute map.

[0126]

[0127] Figure 12 shows the inter-frame decoding process of the V-MESH compression method.

[0128] Fig. 12 shows the configuration and operation of the decoder of the receiving device of Fig. 1.

[0129] Figure 12 illustrates the inter-decoding process of V-Mesh technology. First, the input bitstream can be separated into a motion sub-stream, a displacement sub-stream, an attribute sub-stream, and a sub-stream containing mesh patch information, such as V3C / V-PCC.

[0130] The motion sub-stream is decoded through entropy decoding and inverse prediction processes, and the reconstructed motion information is combined with the already reconstructed reference base mesh to generate a reconstructed quantized base mesh for the current frame. The result of applying inverse quantization to this is combined with the displacement information reconstructed in the same way as the intra decoding described above to generate the final decoded mesh. The attribute map sub-stream is decoded in the same way as the intra decoding. The reconstructed decoded mesh and the decoded attribute map can be utilized by the receiver as the final mesh data that can be utilized by the user.

[0131] Referring to Fig. 12, the bitstream includes motion, displacement, and attribute maps. Since inter-frame decoding is performed, a process of decoding inter-frame motion information is further included. The motion is decoded, and a restored quantized base mesh for the motion is generated based on the reference base mesh, thereby generating a restored base mesh. For a description of the operations in Fig. 12, which are identical to those in Fig. 11, refer to the description in Fig. 11.

[0132] Fig. 13 shows a point cloud data transmission device according to embodiments.

[0133] Fig. 13 corresponds to the transmitting device (100), the dynamic mesh video encoder (102), the encoder (preprocessor and encoder) of Fig. 2, and / or the transmitting encoding device corresponding thereto of Fig. 13. Each component of Fig. 13 corresponds to hardware, software, a processor, and / or a combination thereof.

[0134] The operation process of a transmitter for compressing and transmitting dynamic mesh data using V-Mesh compression technology may be as shown in Fig. 13.

[0135] The mesh preprocessor receives the original mesh as input and generates a simplified mesh (decimated mesh). Simplification can be performed based on the target number of vertices or the target number of polygons that constitute the mesh. Parameterization can be performed on the simplified mesh to generate texture coordinates and texture connection information per vertex. Additionally, quantization of floating-point mesh information into fixed-point information can be performed. This result can be encoded as a base mesh through a static mesh encoding unit. The mesh preprocessor can perform mesh subdivision on the base mesh to generate additional vertices. Depending on the subdivision method, vertex connection information, texture coordinates, and texture coordinate connection information including the added vertices can be generated. The subdivided mesh can be fitted by adjusting the vertex positions to resemble the original mesh, thereby generating a fitted subdivided mesh.

[0136] When performing intra-encoding on the corresponding mesh frame, the base mesh generated through the mesh preprocessing unit can be compressed through the static mesh encoding unit. In this case, encoding can be performed on the connection information, vertex geometry information, vertex texture information, normal information, etc. of the base mesh. The base mesh bitstream generated through encoding is transmitted to the multiplexing unit.

[0137] When performing inter encoding for the corresponding mesh frame, a motion vector encoding unit is performed, which can calculate a motion vector between the base mesh and the reference reconstruction base mesh as input and encode the value. The motion vector encoding unit can perform prediction based on connection information using a previously encoded / decoded motion vector as a predictor, and encode a residual motion vector obtained by subtracting the predicted motion vector from the current motion vector. The motion vector bitstream generated through encoding is transmitted to the multiplexing unit.

[0138] The encoded base mesh and motion vectors can be used to generate a restored base mesh through the base mesh restoration unit.

[0139] The displacement vector calculator can perform mesh refinement on the restored base mesh. The displacement vector can be calculated as the difference in vertex positions between the refined restored base mesh and the fitted subdivision mesh generated in the preprocessing unit. As a result, the number of displacement vectors can be calculated equal to the number of vertices in the refined mesh. The displacement vector calculation unit can convert the displacement vector calculated in the 3D Cartesian coordinate system into a local coordinate system based on the normal vector of each vertex.

[0140] A displacement vector video generator can transform displacement vectors for effective encoding. The transformation can be performed by a lifting transformation, a wavelet transformation, etc., depending on the embodiment. In addition, quantization can be performed on the transformed displacement vector values, i.e., the transform coefficients. Different quantization parameters can be applied to each axis of the transform coefficients, and the quantization parameters can be derived according to the promise of the encoder / decoder. The transformed and quantized displacement vector information can be packed into a 2D image. A displacement vector video can be generated by bundling the packed 2D images for each frame, and the displacement vector video can be generated for each GoF (Group of Frame) unit of the input mesh.

[0141] A displacement vector video encoder can encode the generated displacement vector video using a video compression codec. The generated displacement vector video bitstream is transmitted to a multiplexer.

[0142] The displacement vector restored through the displacement vector restorer and the base mesh restored through the base mesh restorer and refined are restored through the mesh restorer, and the restored mesh has restored vertices, connection information between vertices, texture coordinates, and connection information between texture coordinates.

[0143] The texture map of the original mesh can be regenerated as a texture map for the restored mesh through the texture map video generation unit. The color information per vertex of the texture map of the original mesh can be assigned to the texture coordinates of the restored mesh. The regenerated texture maps for each frame can be bundled into GoF units to generate a texture map video.

[0144] The generated texture map video can be encoded using a video compression codec through a texture map video encoding unit. The texture map video bitstream generated through encoding is transmitted to a multiplexing unit.

[0145] The generated motion vector bitstream, base mesh bitstream, displacement vector bitstream, and texture map bitstream may be multiplexed into a single bitstream and transmitted to a receiver via a transmitter. Alternatively, the generated motion vector bitstream, base mesh bitstream, displacement vector bitstream, and texture map bitstream may be generated as a file with one or more track data or encapsulated into segments and transmitted to a receiver via a transmitter.

[0146] Referring to FIG. 13, a transmitting device (encoder) can encode a mesh in an intra-frame or inter-frame manner. A transmitting device according to intra-encoding can generate a base mesh, a displacement vector (displacement), and a texture map (attribute map). A transmitting device according to inter-encoding can generate a motion vector (motion), a base mesh, a displacement vector (displacement), and a texture map (attribute map). A texture map obtained from a data input unit is generated and encoded based on a restored mesh. Displacement is generated and encoded through the difference in vertex positions between the base mesh and the segmented mesh. The base mesh is generated by preprocessing, simplifying, and encoding the original mesh. Motion is generated as a motion vector for the mesh of the current frame based on the reference base mesh of the previous frame.

[0147] Fig. 14 shows a point cloud data receiving device according to embodiments.

[0148] Fig. 14 corresponds to the receiving device (110), the dynamic mesh video decoder (113), the decoder of Figs. 11-12, and / or the receiving decoding device corresponding thereto of Fig. 1. Each component of Fig. 14 corresponds to hardware, software, a processor, and / or a combination thereof. The receiving (decoding) operation of Fig. 14 may follow the reverse process of the corresponding process of the transmitting (encoding) operation of Fig. 13.

[0149] The bitstream of the received Mesh is demultiplexed into a compressed motion vector bitstream or base mesh bitstream, displacement vector bitstream, and texture map bitstream after file / segment decapsulation.

[0150] If the current mesh has inter-frame encoding applied according to the frame header information, the motion vector decoding unit can perform decoding on the motion vector bitstream. The final motion vector can be reconstructed by adding the previously decoded motion vector to the residual motion vector decoded from the bitstream using the previously decoded motion vector as a predictor.

[0151] If the current mesh has been encoded within the screen according to the frame header information, the base mesh bitstream can restore the connection information, vertex geometry information, texture coordinates, normal information, etc. of the base mesh through the static mesh encoding unit.

[0152] In the base mesh restoration unit, if the current mesh has inter-frame encoding applied, the current base mesh can be restored by adding the decoded motion vector to the reference base mesh and then performing inverse quantization. If the current mesh has intra-frame encoding applied, the static mesh decoding unit can perform inverse quantization on the decoded mesh to generate a restored base mesh.

[0153] The displacement vector bitstream can be decoded as a video bitstream using a video codec in a displacement vector video decoding unit.

[0154] In the displacement vector restoration unit, displacement vector transformation coefficients are extracted from the decoded displacement vector video, and the displacement vector is restored through the inverse quantization and inverse transformation processes. If the restored displacement vector is a value in the local coordinate system, a process of inverse transformation to the Cartesian coordinate system can be performed.

[0155] The mesh restoration unit can generate additional vertices by performing subdivision on the restored base mesh. Subdivision can generate vertex connection information, texture coordinates, and texture coordinate connection information, including the added vertices. The subdivided restored base mesh can be combined with the restored displacement vector to generate the final restored mesh.

[0156] The texture map bitstream can be decoded as a video bitstream using a video codec in a texture map video decoding unit. The restored texture map contains color information for each vertex contained in the restored mesh, and the color value of each vertex can be obtained from the texture map using the texture coordinates of the corresponding vertex.

[0157] The restored mesh and texture map are displayed to the user through a rendering process using a mesh data renderer, etc.

[0158] Referring to FIG. 14, a receiving device (decoder) can decode a mesh in an intra-frame or inter-frame manner. A receiving device according to intra-decoding can receive a base mesh, a displacement vector (displacement), and a texture map (attribute map), and decode the restored mesh and the restored texture map to render the mesh data. A receiving device according to inter-decoding can receive a motion vector (motion), a base mesh, a displacement vector (displacement), and a texture map (attribute map), and decode the restored mesh and the restored texture map to render the mesh data.

[0159] A point cloud data encoding device and method according to embodiments can encode mesh data and transmit a bitstream including the encoded mesh data. A point cloud data decoding device and method according to embodiments can receive a bitstream including mesh data and decode the mesh data. The point cloud data encoding / decoding method / device according to embodiments may be referred to as the method / device according to embodiments. The point cloud data encoding / decoding method / device according to embodiments may also be referred to as the mesh data encoding / decoding method / device according to embodiments. In addition, the term encoding / decoding method / device may be used in this document for short.

[0160] Figure 15 illustrates a valence adaptive lifting update according to embodiments.

[0161] The encoding / decoding method according to the embodiments may include a valence-based adaptive lifting transform for dynamic mesh data.

[0162] The encoding / decoding method according to the embodiments can generate and parse HLS (High Level Syntax and Semantics) for performing an adaptive update process using adaptive weights through information on the current level of detail (LOD) and the number of lines connected to vertices (valence) when performing a lifting transformation between displacement vector coding of a dynamic mesh.

[0163] The embodiments include syntax and semantics information related to a method for improving lifting transformation between displacement vector coding of dynamic mesh data.

[0164] In the V-DMC standard, for dynamic mesh decoders, an update process is performed using fixed constant weights at all vertices during the lifting transformation of displacement vectors. Depending on the characteristics of the mesh data, connectivity information may vary for each vertex, but the same constant weights can be applied uniformly to all vertices. The decoder / decoder method according to the embodiments may additionally perform a transformation process that considers surrounding information for each vertex. The embodiments may improve the decoder / decoder performance by performing an adaptive update process using adaptive weights derived from the current level of detail (LOD) and the number of lines (valence) connected to the vertex when performing a lifting transformation between displacement vector coding of a dynamic mesh.

[0165] For dynamic mesh decoders in the V-DMC standard, the update process can be performed as follows using fixed constant weights at all vertices between lifting transformations of the displacement vector.

[0166] Prediction Process:

[0167]

[0168] Update process:

[0169]

[0170]

[0171] The difference between Signal(v1) and Signal(v2) is the residual value.

[0172] If the above process is a uniform update process, the encoding / decoding method according to the embodiments can perform the update process according to the embodiments by applying the above process as in the formula below. That is, the update is performed adaptively based on the balance weights connected to the mesh vertices.

[0173] Update process:

[0174]

[0175]

[0176] The definition of each parameter in the update process is as follows:

[0177] Signal(v): residual displacement

[0178] K: update constant

[0179] Wval: The valence weight, defined as 1 / (valence[v1]).

[0180] W LOD : LOD scale weight, is defined as

[0181] The above update process can apply adaptive update weights based on the valence of each vertex and the LOD of the lifting operation.

[0182] Figure 15 illustrates several examples of the update process. For example, the update process can calculate update weights by applying the LOD scale when the number of lines is 6, 3, or 7. To avoid the computational drawbacks of the division operation, a lookup table can be used, resulting in a minimal increase in computational effort.

[0183] If the number of lines connected to vertex v1 is 6, weights can be generated with K / 6*LOD_scale, if the number of lines is 3, weights can be generated with K / 3*LOD_scale, and if the number of lines is 7, weights can be generated with K / 7*LOD_scale.

[0184]

[0185] Figure 16 shows lifting transform parameters according to embodiments.

[0186] The encoding method according to the embodiments can encode mesh data to generate a bitstream, and can generate parameter information related to encoding / decoding and include it in the bitstream.

[0187] A decoding method according to embodiments may receive a bitstream and decode mesh data included in the bitstream based on parameter information included in the bitstream.

[0188] Figure 16 shows the syntax and semantics of VDMC lifting transform parameters included in a bitstream according to embodiments.

[0189] Lifting Balance Update Weight Flag (vltp_lifting_valence_update_weight_flag[ltpIndex]): If vltp_lifting_valence_update_weight_flag[ltpIndex] is 1, it indicates that balance adaptive lifting update weights are performed. If vltp_lifting_valence_update_weight_flag[ltpIndex] is 0, it indicates that balance adaptive lifting update weights are not performed.

[0190] Lifting update weight (vltp_log2_lifting_update_weight[ltpIndex]): vltp_log2_lifting_update_weight[ltpIndex] represents the weight coefficient used in the update filter of the wavelet transform of the ith LOD (Level of Detail). ltpIndex is the index of the lifting transform parameter set. If vltp_lifting_valence_update_weight_flag[ltpIndex] is 0, the update weight is calculated using vltp_log2_lifting_update_weight[ltpIndex] as follows: update_weight = pow(2, vltp_log2_lifting_update_weight[ltpIndex])

[0191] If vltp_lifting_valence_update_weight_flag[ltpIndex] is 1, the constant K for the balance update weight is calculated using vltp_log2_lifting_update_weight[ltpIndex] as follows: K = 1.0 + vltp_log2_lifting_update_weight[ltpIndex] * 0.1

[0192] According to embodiments, vltp_lifting_valence_update_weight_flag[ltpIndex] may be referred to as a balance update flag (vltp_valence_update_flag[ltpIndex]).

[0193] That is, in other words, the lifting balance update weight flag (vltp_lifting_valence_update_weight_flag[ltpIndex]) can be referred to as the balance update flag (vltp_valence_update_flag[ltpIndex]), and the lifting update weight (vltp_log2_lifting_update_weight[ltpIndex]) can be referred to as the balance update weight (vltp_valence_update_weight[ltpIndex]).

[0194] The parameters of Fig. 16 can be expressed as follows according to the embodiments.

[0195] vdmc_lifting_transform_parameters( ltpIndex, subdivisionCount ){Descriptorvltp_skip_update_flag[ ltpIndex ]u(1)for( i = 0 ; i < subdivisionCount + 1; i++ ) {if( vltp_skip_update_flag[ ltpIndex ] ) {UpdateWeight[ ltpIndex ][ i ] = 0} else {if( i == 0 ) {vltp_lod_lifting_parameter_flag[ ltpIndex ]u(1)vltp_adaptive_update_weight_flag[ ltpIndex ]u(1)vltp_valence_update_flag[ ltpIndex ]u(1)}if( vltp_lod_lifting_parameter_flag[ ltpIndex ] == 1 || i == 0) {if( vltp_adaptive_update_weight_flag[ ltpIndex ] ) {vltp_lifting_update_weight_numerator[ ltpIndex ][ i ]ue(v)vltp_lifting_update_weight_denominator_minus1[ ltpIndex ][ i ]ue(v)UpdateWeight[ ltpIndex ][ i ] =( vltp_lifting_update_weight_numerator[ ltpIndex ][ i ] ) ÷ ( vltp_lifting_update_weight_denominator_minus1[ ltpIndex ][ i ] + 1 )if ( vltp_valence_update_flag[ ltpIndex ] ) {vltp_valence_update_weight[ ltpIndex ][ i ]ue(v)UpdateWeight[ ltpIndex ][ i ] *= 1 + (vltp_valence_update_weight[ ltpIndex ][ i ] * 0.1 )}} else {if ( vltp_valence_update_flag[ ltpIndex ] ) {vltp_valence_update_weight[ ltpIndex ][ i ]ue(v)UpdateWeight[ ltpIndex ][ i ] = 1 + (vltp_valence_update_weight[ ltpIndex ][ i ] * 0.1 )} else {vltp_log2_lifting_update_weight[ ltpIndex ][ i ]ue(v)UpdateWeight[ ltpIndex ][ i ] =1 ÷ ( 1 << vltp_log2_lifting_update_weight[ ltpIndex ][ i ] )}}} else {UpdateWeight[ ltpIndex ][ i ] = UpdateWeight[ ltpIndex ][ 0 ]}}}vltp_log2_lifting_prediction_weight[ ltpIndex ]ue(v)PredictionWeight[ ltpIndex ] = 1 ÷ ( 1 << vltp_log2_lifting_prediction_weight[ ltpIndex ] )}.

[0196] If vltp_skip_update_flag[ltpIndex] is 1, it indicates that the update step of the lifting transformation applied to the displacement is skipped. If vltp_skip_update_flag[ltpIndex] is 0, it indicates that the update step of the lifting transformation applied to the displacement is not skipped. ltpIndex is the index of the lifting transformation parameter set.

[0197] If vltp_lod_lifting_parameter_flag[ltpIndex] is 1, it indicates that the lifting transformation parameter is signaled at the LoD level. If vltp_lod_lifting_parameter_flag[ltpIndex] is 0, it indicates that the lifting transformation parameter applies to the entire LoD. ltpIndex is the index of the set of lifting transformation parameters. If vltp_lod_lifting_parameter_flag[ltpIndex] is absent, its value is inferred to be equal to 0.

[0198] If vltp_adaptive_update_weight_flag[ltpIndex] is 1, it indicates that the update weight is expressed as a ratio of numerator and denominator values. If vltp_adaptive_update_weight_flag is 0, it indicates that the update weight at the ith level of detail is signaled as a single value. ltpIndex is the index of the lifting transformation parameter set.

[0199] If vltp_valence_update_flag[ltpIndex] is 1, it indicates that value-adaptive lifting weight update is performed. If vltp_lifting_valence_update_weight_flag[ltpIndex] is 0, it indicates that value-adaptive lifting weight update is not performed. ltpIndex is the index of the lifting transformation parameter set.

[0200] vltp_lifting_update_weight_numerator[ltpIndex][i] represents the numerator of the weight coefficient used in the update filter of the lifting transformation at the i-th level of detail. ltpIndex is the index of the lifting transformation parameter set.

[0201] vltp_lifting_update_weight_denominator_minus1[ltpIndex][i] plus 1 represents the denominator of the weight coefficients used in the update filter of the wavelet transform at the i-th level of detail. ltpIndex is the index of the lifting transform parameter set.

[0202] vltp_valence_update_weight[ltpIndex][i] represents the weight coefficient used for the balance adaptive lifting update of the wavelet transform at the i-th level of detail. ltpIndex is the index of the lifting transform parameter set.

[0203] vltp_log2_lifting_update_weight[ltpIndex][i] represents the weighting coefficient used in the update filter of the wavelet transform at the i-th level of detail. ltpIndex is the index of the lifting transform parameter set.

[0204] vltp_log2_lifting_prediction_weight[ltpIndex][i] is the weighting coefficient used in the prediction filter of the wavelet transform at the i-th level of detail. ltpIndex is the index of the lifting transform parameter set.

[0205] The encoding method according to the embodiments can generate UpdateWeight as described above and transmit it to the decoder. The decoder that receives UpdateWeight can perform inverse lifting based on the received UpdateWeight and reconstruct the point cloud data. In addition, the decoding method according to the embodiments can generate UpdateWeight as described above, similar to the encoder. The decoder can generate UpdateWeight, perform inverse lifting based on the generated UpdateWeight, and reconstruct the point cloud data.

[0206] Figure 17 shows an encoding method according to embodiments.

[0207] The encoding method according to the embodiments may include a step (S1700) of encoding mesh data. The encoding method according to the embodiments may further include a step (S1701) of transmitting a bitstream including mesh data.

[0208] Referring to FIG. 13 together, the step of encoding mesh data (S1700) may include: a step of encoding a base mesh of mesh data, a step of encoding a displacement vector of mesh data, and a step of encoding an attribute of mesh data.

[0209] In relation to encoding a displacement vector, the step of encoding the displacement vector may include: predicting a transform coefficient for the displacement vector, quantizing the transform coefficient for the displacement vector, and encoding the transform coefficient for the displacement vector based on at least one of a video codec method, a zero run length method, or an arithmetic coding method.

[0210] Referring to FIG. 15 together, with respect to lifting transformation, the step of encoding a displacement vector includes: transforming a transformation coefficient for the displacement vector based on a lifting method, and a displacement vector for a vertex of the mesh data is updated based on a weight related to a level of the mesh data and a weight related to the number of lines connected to the vertex, and the weight related to the level of the mesh data is generated based on a maximum value of the level, and the weight related to the number of lines connected to the vertex can be generated based on the reciprocal of the number of lines connected to the vertex.

[0211] In the step of transmitting a bitstream (S1701), the bitstream includes a lifting transformation parameter, the lifting transformation parameter includes a balance update flag and a balance update weight, the balance update flag indicates whether a balance adaptive lifting update weight is performed, and the balance update weight may indicate a weight coefficient related to a balance adaptive lifting update for a level of detail.

[0212] The encoding method can be performed by an encoding device (encoder) of Fig. 13. The encoder includes a memory; and at least one processor connected to the memory; and the at least one processor can be configured to: encode mesh data; and transmit a bitstream including the mesh data.

[0213] Figure 18 shows a decryption method according to embodiments.

[0214] A decoding method according to embodiments may include a step (S1800) of receiving a bitstream including mesh data. A decoding method according to embodiments may further include a step (S1801) of decoding the mesh data.

[0215] The decryption method of Fig. 18 can follow the reverse process of the encoding method of Fig. 17.

[0216] Referring to FIGS. 11 and 14 together, with respect to mesh decoding, the step of decoding mesh data (S1801) may include: a step of decoding a base mesh of mesh data, a step of decoding a displacement vector of mesh data, and a step of decoding an attribute of mesh data.

[0217] Referring to FIG. 14, with respect to displacement vector decoding, the step of decoding the displacement vector may include: decoding a transform coefficient for the displacement vector, inverse quantizing the displacement vector, and inverse transforming the displacement vector.

[0218] Referring to FIG. 15 together, with respect to valence and LoD-based lifting transformation, the displacement vector is inversely transformed based on the lifting method, and the displacement vector for a vertex of the mesh data can be updated based on a weight related to the level of the mesh data and a weight related to the number of lines connected to the vertex.

[0219] How to decrypt.

[0220] Referring to FIG. 15 together, with respect to valence and LoD-based lifting transformation, weights related to levels of mesh data may be generated based on the maximum value of the level, and weights related to the number of lines connected to a vertex may be generated based on the reciprocal of the number of lines connected to the vertex.

[0221] Referring to FIG. 16 together, with respect to vdmc_lifting_transform_parameters, the bitstream includes lifting transform parameters, the lifting transform parameters include a balance update flag and a balance update weight, the balance update flag indicates whether balance adaptive lifting update weights are performed, and the balance update weights may indicate weight coefficients related to balance adaptive lifting update for a level of detail.

[0222] Referring to FIG. 16 together, with respect to vltp_valence_update_flag and vltp_valence_update_weight, if the balance update flag has the first value (true or1), the update weight can be generated based on the balance update weight.

[0223] Regarding the weight update method (UpdateWeight*= 1 + (vltp_valence_update_weight * 0.1)), the update weight can be generated by the balance update weight * 0.1 + 1.

[0224] The decryption method can be performed by a decoder (decryption device) of Fig. 14. The decoder includes a memory; and at least one processor connected to the memory; and the at least one processor can be configured to: receive a bitstream including mesh data; and decode the mesh data.

[0225] The encoding / decoding method and device according to the embodiments have the following technical effects:

[0226] The lifting transformation of displacement vectors performed in V-DMC can be improved. In the case of the current dynamic mesh encoder / decoder, the update process is performed using fixed constant weights at all vertices between lifting transformations of displacement vectors, so the transformation process that considers surrounding information for each vertex is not performed. Therefore, the embodiments perform an adaptive update process using adaptive weights derived from the current level of detail (current LOD) and the number of lines connected to the vertices (valence) when performing lifting transformation between displacement vector coding of dynamic meshes, thereby improving the encoding performance. By applying the adaptive update process between lifting transformations of displacement vectors to improve the accuracy of the prediction process, the bit amount of displacement vectors is reduced and the encoding performance is improved.

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A step of receiving a bitstream containing mesh data; and A step of decoding the above mesh data; comprising: How to decrypt.

2. In paragraph 1, The steps for decoding the above mesh data are: A step of decoding the base mesh of the above mesh data, A step of decoding the displacement vector of the above mesh data, Comprising a step of decoding attributes of the above mesh data, How to decrypt.

3. In paragraph 2, The steps for decoding the above displacement vector are: Decode the transformation coefficients for the above displacement vector, Inversely quantize the above displacement vector, Including inversely transforming the above displacement vector, How to decrypt.

4. In paragraph 3, The above displacement vector is inversely transformed based on the lifting method, The displacement vector for the vertex of the above mesh data is updated based on a weight related to the level of the above mesh data and a weight related to the number of lines connected to the vertex. How to decrypt.

5. In paragraph 4, The weights related to the level of the above mesh data are generated based on the maximum value of the level, The weight related to the number of lines connected to the above vertex is generated based on the reciprocal of the number of lines connected to the above vertex. How to decrypt.

6. In paragraph 1, The above bitstream contains lifting transformation parameters, The above lifting transformation parameters include a balance update flag and a balance update weight, The above balance update flag indicates whether the balance adaptive lifting update weights are performed. The above balance update weights represent weight coefficients related to the balance adaptive lifting update for the level of detail. How to decrypt.

7. In paragraph 6, If the above balance update flag has the first value, The update weights are generated based on the above balance update weights. How to decrypt.

8. In paragraph 7, The above update weight is generated by the above balance update weight * 0.1 + 1. How to decrypt.

9. Memory; and At least one processor coupled to said memory; wherein said at least one processor comprises: Receiving a bitstream containing mesh data; and configured to decode the above mesh data; Decryption device.

10. Step of encoding mesh data; and A step of transmitting a bitstream including the above mesh data; comprising: Encoding method.

11. In paragraph 10, The steps for encoding the above mesh data are: A step of encoding the base mesh of the above mesh data, A step of encoding a displacement vector of the above mesh data, Comprising a step of encoding attributes of the above mesh data, Encoding method.

12. In paragraph 11, The steps of encoding the above displacement vector are: Predict the transformation coefficients for the above displacement vector, Quantize the transformation coefficients for the above displacement vector, Encoding the transform coefficients for the displacement vector based on at least one of a video codec method, a zero run length method, or an arithmetic coding method, Encoding method.

13. In paragraph 12, The steps of encoding the above displacement vector are: Including converting the transformation coefficient for the displacement vector based on the lifting method, A displacement vector for a vertex of the above mesh data is updated based on a weight related to a level of the above mesh data and a weight related to the number of lines connected to the vertex, The weights related to the level of the above mesh data are generated based on the maximum value of the level, The weight related to the number of lines connected to the above vertex is generated based on the reciprocal of the number of lines connected to the above vertex. Encoding method.

14. In paragraph 10, The above bitstream contains lifting transformation parameters, The above lifting transformation parameters include a balance update flag and a balance update weight, The above balance update flag indicates whether the balance adaptive lifting update weights are performed. The above balance update weights represent weight coefficients related to the balance adaptive lifting update for the level of detail. Encoding method.

15. Memory; and At least one processor coupled to said memory; wherein said at least one processor comprises: Encode mesh data; and configured to transmit a bitstream including the above mesh data; Encoding device.

Citation Information

Patent Citations

  • Method and electronic device to perform operation according to expansion direction in response to expansion

    KR1020230015025A

  • Apparatus, a method and a computer program for omnidirectional video

    US20230059516A1

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

    WO2021261865A1

  • Remeshing for efficient compression

    WO2023172457A1