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

Abstract

A decoding method according to embodiments may comprise the steps of: decoding a base mesh within a bitstream; decoding displacement within the bitstream; and decoding an attribute within the bitstream. An encoding method according to embodiments may comprise the steps of: encoding a base mesh of mesh data; encoding displacement of the mesh data; and encoding an attribute of the mesh data.

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] Mesh data refers to a data format in which connectivity information between mesh vertices is added to point cloud data.

[0004] There is a problem that a lot of processing is required to transmit and receive dynamic mesh data.

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

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

[0007] 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.

[0008] To achieve the above-described purpose and other advantages, a decoding method according to embodiments may include a step of decoding a base mesh in a bitstream; a step of decoding a displacement in the bitstream; and a step of decoding an attribute in the bitstream. An encoding method according to embodiments may include a step of encoding a base mesh of mesh data; a step of encoding a displacement of the mesh data; and a step of encoding an attribute of the mesh data.

[0009] The mesh data transmission method, transmission device, mesh data reception method, and reception device according to the embodiments can provide a quality mesh service.

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

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

[0012] 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.

[0013] Figure 1 illustrates a V-DMC based encoder and decoder according to embodiments.

[0014] Figure 2 illustrates a system for providing dynamic mesh content according to embodiments.

[0015] Figure 3 shows a V-MESH compression method according to embodiments.

[0016] Figure 4 illustrates pre-processing of V-MESH compression according to embodiments.

[0017] Figure 5 illustrates a mid-edge subdivision method according to embodiments.

[0018] Figure 6 shows a displacement generation process according to embodiments.

[0019] Figure 7 shows a V-DMC encoding process according to embodiments.

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

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

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

[0023] Figure 11 illustrates a V-DMC decoding process according to embodiments.

[0024] Figure 12 illustrates a V-DMC encoding process according to embodiments.

[0025] Figure 13 illustrates a V-DMC decoding process according to embodiments.

[0026] Figure 14 illustrates the profile tier level (profile_tier_level) syntax according to embodiments.

[0027] Figure 15 illustrates the profile toolset constraints information extension (profile_toolset_constraints_information_extension) syntax according to embodiments.

[0028] Figure 16 illustrates the profile toolset constraints information V-DCM extension (profile_toolset_constraints_information_vdmc_extension) syntax according to embodiments.

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

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

[0031] 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.

[0032] 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.

[0033] Figure 1 illustrates a V-DMC based encoder and decoder according to embodiments.

[0034] The basic structure of the currently in-progress V-DMC (v-mesh) is shown in Figure 1. The encoder and decoder according to Figure 1 perform the encoding and decoding process of media representing dynamic meshes using V3C technology. The preprocessor converts the input dynamic mesh representation into several V3C components: a base mesh, a set of displacements, a 2D representation of attributes, and an atlas. The original mesh is simplified into a base mesh. The base mesh can be encoded using any mesh codec. Displacement vectors can be encoded into V3C geometric video components using any video codec, either indicated by a profile or using SEI messages. For example, depending on the profile, the displacement vectors (displacement data) can be encoded using arithmetic coding. The attribute data can include additional attributes. For example, texture or material information can be included as additional attributes and can be encoded using any video codec. The atlas data contains information on how to perform inverse reconstruction and is provided to the V3C decoding and / or rendering system. For example, atlas data may include how to perform subdivision of a base mesh, how to apply displacement vectors to subdivided mesh vertices, how to apply attributes to the reconstructed mesh, etc.

[0035] The encoder may comprise a memory and at least one processor connected to the memory. The at least one processor may be configured to perform operations such as a preprocessor, an atlas encoder, a basemesh encoder, a displacement vector encoder, a video encoder, and a multiplexer.

[0036] The atlas encoding unit encodes the atlas of mesh data to generate an atlas bitstream. The basemesh encoding unit encodes the basemesh of mesh data to generate a basemesh bitstream. The displacement vector encoding unit encodes the displacement vector of mesh data to generate a displacement vector bitstream. The video encoding unit encodes the properties (attributes) of mesh data to generate an attribute bitstream. The encoder generates parameter information (which may be referred to as signaling information, metadata, etc.) related to each encoding. The encoder may generate a bitstream including parameter information, atlas, basemesh, displacement vector, and / or attribute.

[0037] The decoder may be configured with a memory and at least one processor connected to the memory. The at least one processor may be configured to perform operations such as a demultiplexing unit, an atlas decoding unit, a basemesh decoding unit, a displacement vector decoding unit, and a video decoding unit.

[0038] The atlas decoding unit decodes the atlas within the bitstream. The basemesh decoding unit decodes the basemesh within the bitstream. The displacement vector decoding unit decodes the displacement vector within the bitstream. The video decoding unit decodes the attributes within the bitstream. The decoder can perform each decoding operation based on parameter information within the bitstream. The decoder can reconstruct dynamic mesh data based on the atlas, displacement vector, attributes, and base mesh.

[0039] Below, the operation of the V-DMC encoder and decoder of Fig. 1 is described in more detail.

[0040] Figure 2 illustrates a system for providing dynamic mesh content according to embodiments.

[0041] The system of FIG. 2 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).

[0042] The system of FIG. 2 can perform video-based dynamic mesh compression and decompression.

[0043] 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.

[0044] 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.

[0045] 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.

[0046] 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.

[0047] 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.

[0048] 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.

[0049] 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.

[0050] 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.

[0051] 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.

[0052] 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.

[0053] 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.

[0054] 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.

[0055] 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.

[0056] 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.

[0057] 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.

[0058] 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.

[0059] 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.

[0060] 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.

[0061] 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.

[0062] 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.

[0063] 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.

[0064] 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.

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

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

[0067] 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.

[0068] 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.

[0069] The encoding process of Figure 2 is as follows.

[0070] 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.

[0071] 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.

[0072] 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.).

[0073] 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.

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

[0075] 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.

[0076] 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.

[0077] 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.

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

[0079] Figure 3 shows a V-MESH compression method according to embodiments.

[0080] Fig. 3 illustrates the encoding process of Fig. 2, and the encoding process may include a pre-processing process and an encoding process. The encoder of Fig. 2 may include a pre-processor (200) and an encoder (201) as in Fig. 3. The transmitting device of Fig. 2 may be broadly referred to as an encoder, and the dynamic mesh video encoder of Fig. 2 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. 3. The pre-processor of Fig. 3 may be located in front of the encoder of Fig. 3. The pre-processor and the encoder of Fig. 3 may be referred to as a single encoder.

[0081] 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.

[0082] 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.

[0083] Figure 4 illustrates pre-processing of V-MESH compression according to embodiments.

[0084] Figure 4 shows the configuration and operation of the pre-processor of Figure 3.

[0085] 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).

[0086] Below, each step of Fig. 4 is described.

[0087] 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.

[0088] 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.

[0089] 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.

[0090] 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.

[0091] OrthoAtlas technology generates texture coordinates using orthographic projection. OrthoAtlas technology sequentially generates patches and packs them. First, adjacent triangles are divided to generate Connected Components (CCs), and then the optimal CCs are merged using a cost function to generate patches. The cost function can measure the cost based on the degree of distortion that occurs when orthogonally projecting patches in each direction. By packing the patch that minimizes the cost function into the texture domain, the texture coordinates can be ultimately calculated. In the case of orthoAtlas technology, texture coordinates and texture connection information can be derived from the base mesh decoder without compressing them during the base mesh encoding process.

[0092] 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.

[0093] This is the process of fitting a mesh that has undergone subdivision on a base mesh so that its surface resembles that of the input mesh. User-defined subdivision methods, such as the mid-edge method (Figure 5), the loop method, or the LS3 method, can be applied.

[0094] Figure 5 illustrates a mid-edge subdivision method according to embodiments.

[0095] Figure 5 illustrates the mid-edge method of the fitting subdivision surface described in Figure 4. Referring to Figure 5, 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.

[0096] 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.

[0097] Figure 6 shows a displacement generation process according to embodiments.

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

[0099] 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.

[0100] 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.

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

[0102] 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.

[0103] Figure 7 shows a V-DMC encoding process according to embodiments.

[0104] The encoding process of Fig. 7 details the encoding of Figs. 1 and 2.

[0105] 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 motion encoder can encode a motion vector for the base mesh based on inter-frame motion estimation and motion compensation for inter-prediction. The atlas encoder can encode an atlas for the vertices of the base mesh. The encoded base mesh can be reconstructed and inversely quantized through a dequantizer. The displacement calculation unit can receive the reconstructed mesh and generate displacement, which is a position difference, based on the fitted subdivided mesh. A lifting transform unit can receive displacement and generate lifting coefficients. A quantizer can quantize the lifting coefficients. Depending on an encoding method, an image packing unit can pack an image based on the quantized lifting coefficients. A video encoder can encode the packed image. Depending on the encoding method, inter-prediction can be applied to the quantized lifting coefficients, and the predicted lifting coefficients can be encoded according to an arithmetic encoding method. A mesh restoration unit restores a warped mesh using the restored displacement and the restored base mesh. Displacement data is restored, and the warped mesh is restored based on the restored displacement data and the restored base mesh, and provided to an attribute transfer unit. The attribute transfer unit receives an input mesh and / or an input attribute map, and generates an attribute map based on the restored warped mesh. A push-pull padding unit can pad data in the attribute map based on a push-pull method. The color space conversion unit can convert the space of the color component, which is an attribute. The video encoder can encode the attribute.A multiplexer can generate a bitstream by multiplexing compressed base meshes, compressed displacements, and compressed attributes.

[0106] Base Mesh Encoding: The base mesh compression method can be divided into INTRA type, INTER type, and SKIP type depending on the base mesh type, and encoding can be performed in different ways for each. If the base mesh is INTRA type, it can be encoded using the static mesh encoding method. If the base mesh is INTER type, the motion field between the reference base mesh and the current base mesh can be encoded. If the current base mesh is SKIP type, the reference base mesh can be derived as the current base mesh.

[0107] After encoding in the encoder, the decoded base mesh can be subdivided into a subdivided mesh through a subdivision process. Subdivision algorithms such as mid-point subdivision and loop subdivision can be used.

[0108] Static Basemesh Encoding (Intra Basemesh Encoding): When performing Intra encoding on the current basemesh, the base mesh generated in the preprocessing process can be encoded using static mesh compression technology after going through a quantization process. Static mesh compression applies MPEG EdgeBreaker (MEB) technology, and the vertex position information, mapping information (texture coordinates), vertex connection information, and normals of the base mesh are compressed.

[0109] Technology for compressing connection information can be encoded using the edgebreaker algorithm. The edgebreaker algorithm sequentially traverses triangles according to a rule, mapping symbols based on the characteristics of each triangle, and then encoding those symbols.

[0110] A technique for compressing vertex position information can encode the residual value, which is the difference between the current vertex and the predicted value, after obtaining the predicted value based on a prediction technique such as multiple parallelogram prediction.

[0111] A technique for compressing mapping information (texture coordinates) can encode the residual value, which is the difference between the current mapping information (texture coordinates) and the predicted value, after obtaining the predicted value based on a prediction technique such as stretch.

[0112] Techniques for compressing normals can encode residual values, which are the differences between the current normal and the predicted values, after obtaining predicted values ​​based on prediction techniques such as delta coding, multiple parallelogram prediction, and cross product-based prediction.

[0113] Motion Field Encoding (Inter Basemesh Encoding): Inter Basemesh encoding can be performed when a one-to-one correspondence exists between the reference mesh and the current input mesh, and only the vertex position information differs. When performing Inter 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, can be calculated and this information can be encoded. The reference base mesh is the result of quantizing the already decoded base mesh data and is determined by the reference frame index.

[0114] The motion field can be encoded as is, or the predicted motion field can be calculated by averaging the motion fields of the reconstructed vertices among the vertices connected to the current vertex, and the residual motion field, which is the difference between the predicted motion field value and the motion field value of the current vertex, can be encoded. This value can be encoded using entropy coding.

[0115] Displacement Encoding: After encoding the base mesh, it is restored and dequantized to generate a Recon. The base mesh is then subdivided to calculate the displacement between the results and the fitted subdivided mesh. For effective encoding, a data transform process such as the Wavelet transform can be applied to the displacement information, and Figure 7 shows the process of transforming the displacement information using the Lifting transform in V-Mesh. The transform coefficients generated through the transform process are quantized, and the quantized transform coefficients can be compressed using a video codec or through arithmetic encoding, depending on the compression method.

[0116] When compressed through a video codec, it is packed into a 2D image as shown in Figure 8. The transform coefficients are organized into one block for each N^2(N*N) unit, and each block can be packed in z-scan order. The horizontal number of blocks is fixed to N, but the vertical number of blocks can be determined according to the number of vertices of the subdivided base mesh. Within one block, the transform coefficients can be packed by sorting them with Morton code. The packed images generate a displacement video for each GoF unit, and this displacement video can be encoded using an existing video compression codec.

[0117] When compressed through arithmetic coding, inter-frame prediction can be performed on the quantized displacement vector transform coefficients. When inter-frame prediction is performed on the current quantized displacement vector transform coefficients, the residual value, which is the difference between the current displacement vector transform coefficients and the reference displacement vector transform coefficients, can be encoded, and information about the reference target can be encoded. Depending on the displacement vector type, if it is an INTRA type, the quantized displacement vector transform coefficients can be arithmetic-coded, and if it is an INTER type, the residual value can be arithmetic-coded. Arithmetic coding can be performed based on Context Adaptive Binary Arithmetic Coding (CABAC). The CABAC process can first binarize the displacement vector data and map it to a bin string. The bin string can be a binarized output of 0 and 1, and each 0 or 1 can be a bin. Each bin can be arithmetic-coded using context information selected from a context model, and a process of updating the probability can be performed.

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

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

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

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

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

[0123] Fig. 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 Fig. 9. The transform coefficients are organized into one block for every 256 (=16X16) 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 one 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.

[0124] 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.

[0125] 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.

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

[0127] Figure 10 shows the detailed operation of attribute transfer of the encoding of Figure 7.

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

[0129] 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.

[0130] 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 a texture triangle T, then the barycentric coordinate (α, α) of P(u, v) according to the triangle T is calculated. , γ) is calculated. And the 3D vertex positions of triangle T and (α, , γ) to compute the 3D coordinates M(x, y, z) of P(u, v). Find the vertex coordinates M'(x', y', z') and the triangle T' containing this point that corresponds to the most similar position to the computed M(x, y, z) in the input mesh domain. Then, in this triangle T', the center of mass coordinates (α', ', γ') are calculated. The texture coordinates corresponding to the three vertices of Triangle T' and (α', ', γ') is used to calculate the texture coordinates (u', v'), 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.

[0131] 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.

[0132] Atlas Encoding: Atlas information may be transmitted during the aforementioned process. The Atlas consists of information required for mesh decoding and / or rendering, and may include information required for subdivision, displacement decoding, base mesh decoding, tile information, patch information, and other information. Atlas data may be encoded using methods such as Exp-Golomb coding.

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

[0134] 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.

[0135] Figure 11 illustrates a VV-DMC decoding process according to embodiments.

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

[0137] The input bitstream can be separated into a basemesh sub-stream, a displacement sub-stream, an attribute map sub-stream, and an atlas sub-stream.

[0138] Atlas sub-streams can be decoded through Exp-Golomb coding, etc., and as a result, information necessary for decoding, such as tile information and patch information, can be obtained.

[0139] If the Basemesh sub-stream is of INTRA type according to the Basemesh type, it can be decoded through a static mesh decoder based on MEB (MPEG EdgeBreaker) technology, and as a result, the connection information, vertex geometry information, and vertex mapping information (texture coordinates) of the Basemesh can be restored.

[0140] When the texture parameterization method in the encoder is orthoAtlas, the decoder can derive mapping information (texture coordinates) and attribute information (texture) connection information using vertex coordinates. The process of deriving mapping information (texture coordinates) and connection information can generate mapping information (texture coordinates) and attribute information (texture) connection information by calculating the homography transform of each face and then projecting the vertices based on this.

[0141] If the Basemesh type is INTER, motion information can be decoded through entropy decoding and inverse prediction. The reconstructed motion information is combined with the reference Basemesh, which has already been reconstructed and stored in the buffer, to create a Reconstructed Quantized Basemesh for the current frame. The reconstructed Basemesh can then undergo an inverse quantization process.

[0142] If the displacement sub-stream is compressed through a video codec according to the compression method used in encoding, it is decoded into displacement video through the decoder of the video compression codec, and then the image unpacking process is performed.

[0143] When compressed through arithmetic coding, the displacement vector bitstream can decode the binarized syntax elements through arithmetic decoding, and a contextual probability model (CPM) can be adaptively determined according to each bin of the syntax elements, and the occurrence probability of the bin can be predicted through the CPM to perform arithmetic decoding. The binarized syntax elements can be decoded through inverse binarization. The quantized displacement vector transform coefficients can be derived from the decoded syntax elements. If the displacement information type is INTER, an inverse inter prediction process is performed using reference information for the quantized displacement coefficients (if inter prediction is performed).

[0144] The quantized displacement coefficient is restored as displacement information for each vertex through inverse quantization, inverse transform, and coordinate system transformation processes.

[0145] The restored base mesh and restored displacement information are combined to generate the final decoded mesh. 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.

[0146] 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.

[0147] The atlas decoder decodes the atlas data within the bitstream.

[0148] The motion decoder derives the motion field of the base mesh of the current frame through motion estimation and compensation based on the base mesh in the reference frame, if the mesh data in the bitstream is encoded based on inter prediction. The spatial decoder decodes the base mesh, if the mesh data in the bitstream is encoded based on intra prediction. Depending on the encoding method, the displacement data is decoded by applying arithmetic encoding decoding or video decoding. The video decoder decodes the attribute data in the bitstream.

[0149] The decoding method of Fig. 11 can follow the reverse process of the encoding method according to the embodiments.

[0150] Figure 12 illustrates a V-DMC encoding process according to embodiments.

[0151] Fig. 12 illustrates the configuration and operation of the encoder of the transmitting device of Figs. 1 and 2. Each component of Fig. 12 corresponds to hardware, software, a processor, and / or a combination thereof.

[0152] Figure 12 shows the encoding process of V-Mesh technology.

[0153] The mesh preprocessing unit 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 mapping information (texture coordinates) and attribute information (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 preprocessing unit 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.

[0154] The base mesh generated through the mesh preprocessing unit can perform intra encoding or inter encoding depending on the base mesh type. If the base mesh frame performs intra encoding, it 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. If the base mesh frame performs inter encoding, a motion vector encoding unit is performed, which can use the base mesh and the reference reconstruction base mesh as input to calculate the motion vector between the two meshes and encode the value. The motion vector encoding unit can perform connection information-based prediction using the previously encoded / decoded motion vector as a predictor, and can encode the residual motion vector obtained by subtracting the predicted motion vector from the current motion vector. The base mesh bitstream generated through the base mesh encoding unit is transmitted to the multiplexing unit.

[0155] The encoded base mesh bitstream can generate a restored base mesh through a base mesh restoration unit.

[0156] The displacement vector calculation unit 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 displacement vector can be calculated as many times as the number of vertices of 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.

[0157] The displacement vector processing unit can transform the displacement vector for effective encoding. The transform can be performed by a lifting transform, a wavelet transform, etc. depending on the embodiment. In addition, quantization can be performed on the transformed displacement vector value, i.e., the transform coefficient. Different quantization parameters can be applied to each axis of the transform coefficient, and the quantization parameters can be derived according to the agreement of the encoder / decoder. The quantized displacement vector transform coefficients calculated by the displacement vector processing unit can be encoded through a displacement vector video encoding unit or a displacement vector arithmetic encoding unit depending on the compression method.

[0158] The displacement vector video encoding unit can pack displacement vector information that has undergone transformation and quantization into a 2D image. The packed 2D images can be bundled for each frame to generate a displacement vector video, and the displacement vector video can be generated for each GoF (Group of Frame) unit of the input mesh. The generated displacement vector video can be encoded using a video compression codec. The generated displacement vector video bitstream is transmitted to the multiplexing unit.

[0159] The displacement vector arithmetic encoding unit can perform inter-screen prediction on the quantized displacement vector transform coefficients if the displacement vector type is INTER. The inter-screen prediction process may be a process of obtaining a residual value, which is the difference between the current transform coefficient and the reference transform coefficient. The displacement vector transform coefficient or the residual value can be encoded through an arithmetic encoding process.

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

[0161] The attribute information (texture map) of the original mesh can be regenerated as attribute information (texture map) for the restored mesh through the attribute information (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 by GoF unit to generate a texture map video.

[0162] 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.

[0163] The atlas encoding unit can encode atlases, which are additional information required for mesh decoding and rendering. The generated atlas bitstream is transmitted to the multiplexing unit.

[0164] The generated base mesh bitstream, displacement vector bitstream, texture map bitstream, and atlas bitstream can be multiplexed into a single bitstream and transmitted to a receiver via a transmitter. Alternatively, the generated base mesh bitstream, displacement vector bitstream, texture map bitstream, and atlas bitstream can be generated into a file with one or more track data or encapsulated into segments and transmitted to a receiver (decoder) via a transmitter.

[0165] The data input unit can receive an original mesh and / or an original texture map ('attribute'). The mesh preprocessing unit can simplify the original mesh to generate a base mesh and fit it to generate a refined mesh. The motion vector encoding unit can generate a motion vector (motion field) by referring to a reconstructed base mesh within a previously processed reference frame when the mesh encoding method is inter-prediction, and can encode it based on a motion estimation and compensation method. The static mesh encoding unit can encode the base mesh within the frame when the mesh encoding method is intra-prediction. The displacement vector calculation unit can calculate a displacement vector for a vertex from the fitted refined mesh based on the reconstructed base mesh. The displacement vector processing unit can process the displacement vector into a form suitable for encoding. Depending on the encoding method for the displacement vector, the displacement vector can be encoded based on a video method or an arithmetic encoding method. The displacement vector can be reconstructed and provided to the mesh restoration unit together with the reconstructed base mesh. Based on the restored mesh, the attribute (texture map) video generation unit can generate a video for encoding the texture map using the original mesh and the texture map for the original mesh. The attribute is encoded based on the video method. The atlas is encoded by the atlas encoding unit.

[0166] Figure 13 illustrates a V-DMC decoding process according to embodiments.

[0167] Fig. 13 corresponds to the decoders of Figs. 1 to 3. Each component of Fig. 13 corresponds to hardware, software, a processor, and / or a combination thereof.

[0168] The bitstream of the received Mesh is demultiplexed into a compressed base mesh bitstream, a displacement vector bitstream, an attribute information (texture map) bitstream, and an atlas bitstream after file / segment decapsulation.

[0169] 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 base mesh 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. The current base mesh can be reconstructed by adding the decoded motion vector to the reference base mesh.

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

[0171] The base mesh restoration unit can perform inverse quantization on the decoded base mesh to generate a restored base mesh.

[0172] Depending on the encoding codec type, the displacement vector bitstream may be decoded using a video codec and then subjected to a depacking process. If encoded using arithmetic coding, arithmetic decoding may be performed using a displacement vector arithmetic decoding unit. If inter-screen prediction is performed, the current displacement vector transform coefficient may be generated by adding a residual value to the reference displacement vector transform coefficient through inter-screen prediction.

[0173] The displacement vector restoration unit restores the displacement vector by performing inverse quantization and inverse transformation on the decoded displacement vector transform coefficients. 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.

[0174] 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.

[0175] 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.

[0176] The atlas bitstream can be decrypted by the atlas decryptor.

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

[0178] The decoder receives an encoded bitstream and decodes the base mesh, displacement vectors, attributes, and atlas within the bitstream based on parameter information (which may be referred to as signaling information, metadata, etc.) contained within the bitstream. The decoding process may follow the reverse process of the encoding process. Based on the decoded atlas, a mesh is reconstructed from the reconstructed base mesh and the reconstructed displacement mesh. The mesh can be rendered based on the reconstructed mesh and the reconstructed attributes.

[0179] 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.

[0180] The method and device according to the embodiments define profile toolset constraints for V-DMC (V-DMC profile toolset constraints information), and can encode and decode mesh data based on the profile toolset constraints information.

[0181] The embodiments are intended to define the syntax and semantics of profile toolset constraints information for V-DMC, which imposes constraints on the range of values ​​of key tools and syntax elements required for decoding a V-DMC bitstream and provides information that enables a decoder to determine what level of decoding capability is required.

[0182] It also serves to control the main syntax elements that define the V-DMC toolset profile, so it can serve as a configuration that can control the overall encoding function and performance through this profile toolset constraint information in the V-DMC encoder.

[0183] Embodiments include V-DMC (V-mesh), a method for compressing 3D dynamic mesh data based on a 2D video codec.

[0184] The profile toolset constraints information contained in the profile_tier_level( ) syntax structure contains information about the syntax elements that define or influence the V3C toolset profile components. That is, this syntax structure is directly related to the syntax elements that are constrained to comply with a specific toolset profile component of a V3C codec. For example, the syntax and semantics of the profile toolset constraints information according to the V3C standard address constraints on syntax elements for the V-PCC toolset profile component.

[0185] However, the currently defined profile toolset constraints address constraints related to V-PCC applications, and many of the syntax elements are not relevant to V-DMC applications. Therefore, profile toolset constraints related to V-DMC applications must be defined. Methods and devices according to the embodiments provide profile toolset constraints that can address these technical issues.

[0186] Embodiments may modify the profile toolset constraint information to include appropriate syntax elements to define relevant constraints for V-DMC.

[0187] The encoding method and device according to the embodiments may correspond to the encoder of Fig. 1, the transmitting device (100) of Fig. 2, the encoder (102), the preprocessor of Figs. 3 to 4, the encoder of Fig. 7, the encoder of Fig. 12, the syntax element generation of Figs. 14 to 16, and the encoding method of Fig. 17.

[0188] The decoding method and device according to the embodiments may correspond to the decoder of Fig. 1, the receiving device (110) of Fig. 2, the decoder (113), the decoder of Fig. 11, the decoder of Fig. 13, the syntax element acquisition of Figs. 14 to 16, the encoding method of Fig. 18, etc.

[0189] Figure 14 illustrates the profile tier level (profile_tier_level) syntax according to embodiments.

[0190] The encoding method and device (Fig. 1 encoder, Fig. 2 transmitter (100), encoder (102), Figs. 3 to 4 preprocessor, Fig. 7 encoder, Fig. 12 encoder, Fig. 17 encoding method) according to the embodiments can encode mesh data and generate parameters (syntax elements) for the mesh data. Furthermore, a bitstream including encoded mesh data and parameter information (which can be referred to as signaling information, metadata, etc.) can be generated.

[0191] The decoding method and device according to the embodiments (Fig. 1 decoder, Fig. 2 receiving device (110), decoder (113), Fig. 11 decoder, Fig. 13 decoder, Figs. 14 to 16 syntax element acquisition, Fig. 18 encoding method) can decode mesh data within a bitstream based on a syntax element from the bitstream.

[0192] Figure 14 shows the syntax of profiles, tiers, and levels within a bitstream, and the semantics of profiles, tiers, and levels are described below.

[0193] If the toolset constraints extension presence flag (ptl_toolset_constraints_extension_present_flag) is 1, it indicates the presence of a syntax structure with syntax elements ptl_toolset_constraints_extension_count_minus1, ptl_toolset_constraints_extension_type, ptl_toolset_constraints_extension_length and the associated extension with index i. If ptl_toolset_constraints_extension_present_flag is 0, it indicates the absence of these syntax elements and syntax structures.

[0194] The toolset constraints extension count (ptl_toolset_constraints_extension_count) indicates the number of profile toolset constraints information extensions present in the profile_tier_level() syntax structure. If not present, ptl_toolset_constraints_extension_count is inferred to be 0.

[0195] The toolset constraints extension type (ptl_toolset_constraints_extension_type[ i ]) indicates the profile toolset constraints information extension type for the extension with index i as specified in the table below (profile toolset constraints information extension types). Values ​​marked as reserved are reserved for future use in ISO / IEC and may not be present in a bitstream conforming to this version of this document. Decoders conforming to this version of this document ignore such reserved extensions. A particular ptl_toolset_constraints_extension_type[ i ] value must occur only once in the entire profile_tier_level( ) syntax construct, and the order of extensions is not significant.

[0196]

[0197] The toolset constraints extension length (ptl_toolset_constraints_extension_length[ i ]) represents the number of bytes used to represent the payload size of the syntax structure of the associated extension with index i. If ptl_toolset_constraints_extension_length[ i ] is 0, there is no extension payload for the extension with index i. Otherwise, the extension with index i has a payload size in bits in the range 8 * (ptl_toolset_constraints_extension_length[ i ] - 1 ) + 1 to 8 * ptl_toolset_constraints_extension_length[ i ], inclusive.

[0198] Figure 15 illustrates the profile toolset constraints information extension (profile_toolset_constraints_information_extension) syntax according to embodiments.

[0199] Figure 15 shows the Profile toolset constraints information extension syntax within a bitstream.

[0200] Figure 16 illustrates the profile toolset constraints information V-DCM extension (profile_toolset_constraints_information_vdmc_extension) syntax according to embodiments.

[0201] Methods and devices according to embodiments may provide additional information for describing the profile toolset constraint information V-DMC extension syntax and semantics as follows.

[0202] V-DMC Extension Semantics for Profile Tool Set Constraint Information According to Embodiments:

[0203] If the basemesh flag (ptc_basemesh_only_flag) is 1, afve_subdivision_enable_flag is indicated as 0. If ptc_basemesh_only_flag is 0, the constraint is not applied. If this value is absent, ptc_basemesh_only_flag is inferred to be 0.

[0204] afve_subdivision_enable_flag indicates whether subdivision is performed. ptc_basemesh_only_flag may be referred to as afve_subdivision_enable_flag. ptc_basemesh_only_flag may be referred to as ptc_no_subdivision_flag. Profile toolset constraint information of a bitstream according to embodiments may include ptc_no_subdivision_flag.

[0205] If ptc_no_subdivision_flag is 1, asve_subdivision_iteration_count, afve_subdivision_iteration_count_present_flag, mdu_subdivision_iteration_count_present_flag[ tileID ][ patchIdx ], mmdu_subdivision_iteration_count_present_flag[ tileID ][ patchIdx ], imdu_subdivision_iteration_count_present_flag[ tileID ][ patchIdx ] are all 0. If ptc_no_subdivision_only_flag is 0, the constraint is not applied. If ptc_no_subdivision_flag is not present, ptc_no_subdivision_flag is inferred to be 0.

[0206] If the displacement ascending flag (ptc_displacement_ascending_flag) is 1, the packing method (asve_packing_method) is 0. If ptc_displacement_ascending_flag is 0, the constraint is not applied. If ptc_displacement_ascending_flag is absent, 0 is inferred.

[0207] If asve_packing_method is 0, it indicates that the displacement component samples are packed in ascending order, and if asve_packing_method is 1, it indicates that the displacement component samples are packed in descending order: AspsPackingMethod = asve_packing_method.

[0208] If the displacement dimension constraint flag (ptc_displacement_dimension_constraint_flag) is 1, it indicates that asve_1d_displacement_flag is 1. If ptc_displacement_dimension_constraint_flag is 0, the constraint is not applied. If ptc_displacement_dimension_constraint_flag is not present, it is inferred to be 0.

[0209] If the 1D displacement flag (asve_1d_displacement_flag) is 1, it indicates that only a single component of the displacement exists. The other two components are inferred to be 0. If asve_1D_displacement_flag is 0, it indicates that all three components of the displacement exist. The following variables are defined: AspsDispComponents = asve_1d_displacement_flag ? 1 : 3

[0210] As a requirement for V3C bitstream conformance, if vpve_ac_displacement_present_flag[ j ] is 1, then the value of asve_1d_displacement_flag must be equal to the value of acdi_1d_displacement_flag[ j ], where j is the ID of the current atlas, if one exists.

[0211] If the displacement video flag (ptc_displacement_video_flag) is 1, it indicates that asve_displacement_id_present_flag is 0. If ptc_displacement_video_flag is 0, the constraint is not applied. If ptc_displacement_video_flag is not present, it is inferred to be 0.

[0212] If the displacement video flag (ptc_displacement_video_flag) is 1, then vpve_ac_displacement_present_flag[ j ] is set to 0 for all atlas IDs j. If ptc_displacement_video_flag is 0, the constraint is not applied. If ptc_displacement_video_flag is absent, ptc_displacement_video_flag is inferred to be 0.

[0213] If asve_displacement_id_present_flag is 1, it indicates that the displacement data ID is signaled in the mesh patch data unit and the 2D bounding box associated with the displacement is not signaled in the mesh patch data unit. If asve_displacement_id_present_flag is 0, it indicates that the displacement data ID is not signaled in the mesh patch data unit and the 2D bounding box associated with the displacement is signaled in the mesh patch data unit: AspsDisplacementIdPresentFlag = asve_displacement_id_present_flag.

[0214] If the packed video flag (ptc_no_packed_video_flag) is 1, vps_packed_video_present_flag is inferred to be 0. If ptc_no_packed_video_flag is 0, the constraint is not applied. If ptc_no_packed_video_flag is not present, it is inferred to be 0.

[0215] If the basemesh flag (ptc_basemesh_only_flag) is 1, the subdivision enable flag (afve_subdivision_enable_flag) is set to 0. The subdivision enable flag (afve_subdivision_enable_flag) being 0 means that subdivision is not performed, and therefore only the basemesh is used. The encoding method according to the embodiments encodes mesh data by considering only the basemesh, and the decoding method decodes only the basemesh without subdivision.

[0216] If the displacement ascending flag (ptc_displacement_ascending_flag) is 1, the packing method (asve_packing_method) becomes 0. What asve_packing_method means when asve_packing_method is 0, it means that the displacement component samples are packed in ascending order, and when asve_packing_method is 1, it means that the displacement component samples are packed in descending order.

[0217] If the displacement dimension constraint flag (ptc_displacement_dimension_constraint_flag) is 1, then asve_1d_displacement_flag becomes 1. If the 1D displacement flag (asve_1d_displacement_flag) is 1, it means that 1D displacement (not 3D) is used. For example, 1D displacement means that the dimension size of the displacement is 1 dimension and can mean a single component.

[0218] If the displacement video flag (ptc_displacement_video_flag) is 1, asve_displacement_id_present_flag becomes 0. If asve_displacement_id_present_flag is 0, AspsDisplacementIdPresentFlag becomes 0 (according to the specification), which means that the displacement vector is coded as video (the opposite case means that it is coded with arithmetic encoding). In the current standard, it is used as vpve_ac_displacement_present_flag for clearer meaning, but the meaning and behavior have not changed.

[0219] If ptc_no_packed_video_flag is 1, vps_packed_video_present_flag becomes 0. If vps_packed_video_present_flag is 0, it means that the packed video function is not used.

[0220] The embodiments include changes to define separate profile toolset constraints information related to V-DMC. The embodiments extend the current profile_tier_level() syntax structure to allow for extensions to profile toolset constraints information for V-DMC. Furthermore, the embodiments include an extension mechanism that can be used by other codecs that require their own profile toolset constraints information. The proposed changes are closely related to the V-DMC toolset profile definition and may impact both the V3C and V-DMC specifications.

[0221] The operation flow chart of the decryption device according to the embodiments is as follows:

[0222] 1. The receiver determines which features are enabled and which features are disabled through the profile_toolset_constraints_information_vdmc_extension information included in the profile_tier_level( ) syntax structure included in the V3C parameter set in the received V-DMC bitstream.

[0223] 2. For example, if ptc_displacement_dimension_constraint_flag is 1, it is recognized that the displacement data is compressed in 1D mode, for example, in the form of a single component, so that appropriate memory or other resource allocation can be performed during the actual decoding process.

[0224] 3. In addition, if ptc_basemesh_only_flag is 1, it can be determined in advance that only the basemesh exists in the received V-DMC bitstream, so the subdivision function does not need to be performed during the decoding process of the stream.

[0225] 4. In particular, this information can be linked to the syntax elements that define the V-DMC toolset profile to provide a priori information on how the information is restricted.

[0226] 5. Using this table, the encoder can control the values ​​of the associated syntax elements.

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

[0228] The method according to the embodiments may include a step of encoding a base mesh of mesh data (S1700); a step of encoding displacement of mesh data (S1710); and / or a step of encoding an attribute of mesh data (S1720); etc.

[0229] The step of encoding the base mesh of the mesh data (S1700), the step of encoding the displacement of the mesh data (S1710), and / or the step of encoding the attribute of the mesh data (S1720) may include the encoding operation of the mesh data described in Fig. 1 encoder, Fig. 2 transmitter (100), encoder (102), Figs. 3 to 4 preprocessor, Fig. 7 encoder, Fig. 12 encoder, Figs. 14 to 16 syntax element generation, Fig. 17 encoding method, etc.

[0230] The step of encoding the base mesh (S1700), the step of encoding the displacement (S1710), or the step of encoding the attribute (S1720) may be performed based on the profile, tier, and level.

[0231] A bitstream is generated based on a step of encoding a basemesh, a step of encoding a displacement, or a step of encoding an attribute, wherein the bitstream includes information about the profile, tier, and level, and the information about the profile, tier, and level may include: a flag indicating that subdivision for the basemesh is not performed.

[0232] The bitstream contains information about the profile, tier and level, and the information about the profile, tier and level may include: a flag indicating whether displacements are packed in ascending order.

[0233] The bitstream contains information about the profile, tier and level, and the information about the profile, tier and level may include: a flag indicating whether the displacement is a single component.

[0234] The encoding method of FIG. 17 is performed by an encoding device, and the encoding device includes a memory; and at least one processor connected to the memory; and the at least one processor can be configured to: encode a base mesh of mesh data; encode a displacement of the mesh data; and encode an attribute of the mesh data.

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

[0236] Embodiments may include a step of obtaining a bitstream for mesh data, the bitstream being generated based on a step of encoding a base mesh of the mesh data; a step of encoding a displacement of the mesh data; and a step of encoding an attribute of the mesh data; and a step of transmitting data including the bitstream.

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

[0238] The method according to the embodiments may include a step of decoding a base mesh within a bitstream (S1800); a step of decoding a displacement within a bitstream (S1810); and / or a step of decoding an attribute within a bitstream (S1820); etc.

[0239] The step of decoding the base mesh (S1800), the step of decoding the displacement in the bitstream (S1810), and the step of decoding the attribute in the bitstream (S1820) may include the decoding operation of the mesh data described in the decoder of FIG. 1, the receiving device (110) of FIG. 2, the decoder (113), the decoder of FIG. 11, the decoder of FIG. 13, the syntax element acquisition of FIGs. 14 to 16, and the decoding method of FIG. 18.

[0240] With respect to the Profile, tier, and level syntax according to the embodiments, the step of decoding the base mesh, the step of decoding the displacement, or the step of decoding the attribute may be performed based on the profile, tier, and level.

[0241] With respect to the ptc_basemesh_only_flag (or ptc_no_subdivision_flag) in Fig. 14, the bitstream includes information about the profile, tier, and level, and the information about the profile, tier, and level may include: a flag indicating that subdivision is not performed on the basemesh.

[0242] With respect to ptc_displacement_ascending_flag of the profile, tier, and level syntax of Fig. 16, the bitstream includes information about the profile, tier, and level, and the information about the profile, tier, and level may include: a flag indicating whether the displacements are packed in ascending order.

[0243] With respect to ptc_displacement_dimension_constraint_flag of the Profile, Tier, and Level syntax, the bitstream includes information about the profile, tier, and level, and the information about the profile, tier, and level may include: a flag indicating whether the displacement is a single component. A single component means a 1D displacement.

[0244] With respect to ptc_displacement_video_flag of the Profile, Tier, and Level syntax of Fig. 16, the bitstream includes information about the profile, tier, and level, and the information about the profile, tier, and level may include: information indicating whether an ID for displacement exists.

[0245] With respect to ptc_no_packed_video_flag of the Profile, tier, and level syntax of FIG. 16, the bitstream includes information about the profile, tier, and level, and the information about the profile, tier, and level may include: a flag indicating whether packed video exists.

[0246] The decoding method of FIG. 18 may be performed by a decoding device. The decoding device includes a memory; and at least one processor connected to the memory; and the at least one processor may be configured to: decode a base mesh within a bitstream; decode a displacement within the bitstream; and decode an attribute within the bitstream.

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

[0248] Based on the profile toolset constraint information according to the embodiments, efficient mesh data encoding and decoding effects can be provided for V-DMC applications as well as V-PCC applications. The embodiments enable profile configuration and efficient control of compression efficiency, image quality, and decoder complexity for the toolset. The embodiments enable efficient signaling of bandwidth requirements according to bitrate and resolution. The embodiments enable efficient signaling of constraints regarding resolution, frame rate, maximum bitrate, etc. between the encoder and decoder.

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

[0250] 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.

[0251] 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.

[0252] 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”.

[0253] 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.

[0254] 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.

[0255] 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.

[0256] 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.

[0257] 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.

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

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

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

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

Claims

1. Step of decoding the base mesh in the bitstream; A step of decoding displacement within the bitstream; and A step of decoding an attribute within the bitstream; comprising: How to decrypt.

2. In paragraph 2, The step of decoding the base mesh, the step of decoding the displacement, or the step of decoding the attribute is performed based on the profile, tier, and level. How to decrypt.

3. In paragraph 2, The above bitstream contains information about the profile, tier and level, Information about the above profiles, tiers and levels: Contains a flag indicating that no subdivision is performed on the above base mesh; How to decrypt.

4. In paragraph 2, The above bitstream contains information about the profile, tier and level, Information about the above profiles, tiers and levels: Contains a flag indicating whether the above displacements are packed in ascending order. How to decrypt.

5. In paragraph 2, The above bitstream contains information about the profile, tier and level, Information about the above profiles, tiers and levels: Contains a flag indicating whether the above displacement is a single component; How to decrypt.

6. In paragraph 2, The above bitstream contains information about the profile, tier and level, Information about the above profiles, tiers and levels: Contains information indicating whether an ID for the above displacement exists; How to decrypt.

7. In paragraph 2, The above bitstream contains information about the profile, tier and level, Information about the above profiles, tiers and levels: Contains a flag indicating whether a packed video exists. How to decrypt.

8. Memory; and At least one processor connected to the memory; wherein the at least one processor comprises: Decode the basemesh within the bitstream; Decoding displacements within the above bitstream; and configured to decode an attribute within the above bitstream; Decryption device.

9. Step of encoding the base mesh of mesh data; a step of encoding the displacement of the above mesh data; and A step of encoding attributes of the above mesh data; comprising: Encoding method.

10. In paragraph 8, The step of encoding the base mesh, the step of encoding the displacement, or the step of encoding the attribute is performed based on a profile, a tier, and a level. Encoding method.

11. In paragraph 9, A bitstream is generated based on the step of encoding the base mesh, the step of encoding the displacement, or the step of encoding the attribute, The above bitstream contains information about the profile, tier and level, Information about the above profiles, tiers and levels: Contains a flag indicating that no subdivision is performed on the above base mesh; Encoding method.

12. In paragraph 10, The above bitstream contains information about the profile, tier and level, Information about the above profiles, tiers and levels: Contains a flag indicating whether the above displacements are packed in ascending order. Encoding method.

13. Memory; and At least one processor connected to the memory; wherein the at least one processor comprises: Encode the base mesh of mesh data; Encoding the displacement of the above mesh data; and Encoding attributes of the above mesh data; configured to do so; Encoding device.

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

15. Step of obtaining bitstream for mesh data, The bitstream is generated based on the steps of encoding a base mesh of the mesh data; encoding a displacement of the mesh data; and encoding an attribute of the mesh data; and A method comprising the step of transmitting data including the bitstream.

Images