Mesh data transmission apparatus, mesh data transmission method, mesh data reception apparatus, and mesh data reception method

Abstract

A mesh data decoding method, according to embodiments, may comprise the steps of: decoding a base mesh in a bitstream; decoding displacement data in the bitstream; and decoding attribute data in the bitstream, wherein the decoded base mesh may comprise one or more submeshes, each submesh may comprise one or more regions, and in the step of decoding the base mesh, inter-decoding or intra-decoding may be performed for the base mesh on a per-region basis.

Description

Mesh data transmission device, mesh data transmission method, mesh data reception device, and mesh data reception method

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

[0002] Among 3D content, point cloud data and mesh data are collections of points in 3D space. However, the sheer number of points in 3D space makes it difficult to generate point cloud or mesh data.

[0003] That is, there is a problem that a lot of processing is required to transmit and receive 3D data with a large amount of points, such as point cloud data or mesh data.

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

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

[0006] The technical problem according to the embodiments is to provide a device and method for efficiently performing encoding and decoding of a displacement vector.

[0007] The technical problem according to the embodiments is to provide a device and method for efficiently performing encoding / decoding of mesh data by dividing mesh data of sub-mesh units into smaller mesh units and encoding / decoding them.

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

[0009] 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 displacement data in the bitstream, and a step of decoding attribute data in the bitstream.

[0010] According to embodiments, the base mesh may be composed of one or more sub-meshes, and each sub-mesh may be composed of one or more regions.

[0011] According to embodiments, each submesh is divided into one or more regions based on similarity with a reference submesh, and each region may or may not have a matching region in the reference submesh.

[0012] According to embodiments, the step of decoding the base mesh may perform inter-decoding or intra-decoding on the base mesh in units of the regions based on signaling information included in the bitstream.

[0013] According to embodiments, the signaling information may include at least one of coding type information of each region constituting the current submesh or index information of each region.

[0014] According to embodiments, a decoding device includes a memory and at least one processor connected to the memory, wherein the at least one processor can be configured to decode a basemesh within a bitstream, decode displacement data within the bitstream, and decode attribute data within the bitstream.

[0015] According to embodiments, the encoding method may include a step of encoding a base mesh of mesh data, a step of encoding displacement data of the mesh data, and a step of encoding attribute data of the mesh data.

[0016] According to embodiments, the step of encoding the base mesh may include the step of dividing the base mesh into one or more sub-meshes and dividing each sub-mesh into one or more regions.

[0017] According to embodiments, the step of dividing into regions comprises dividing the current submesh into one or more regions based on the similarity between the current submesh and a reference submesh, and each region may or may not have a matching region in the reference submesh.

[0018] According to embodiments, the step of encoding the base mesh may perform inter-encoding for an area where a matching area exists in the reference sub-mesh, and intra-encoding for an area where a matching area does not exist.

[0019] According to embodiments, the step of dividing into the above regions may include dividing the current submesh into one or more regions based on a change in a motion vector, and the change in the motion vector may be obtained by estimating the motion vector through motion estimation between the current base mesh and the reference base mesh.

[0020] According to embodiments, the encoding method further includes a step of generating signaling information, wherein the signaling information may include at least one of coding type information of each region constituting the current submesh or index information of each region.

[0021] According to embodiments, the encoding device includes a memory and at least one processor connected to the memory, wherein the at least one processor can be configured to encode a base mesh of the mesh data, encode displacement data of the mesh data, and encode attribute data of the mesh data.

[0022] According to embodiments, a computer-readable storage medium can store a bitstream generated by the encoding method.

[0023] According to embodiments, a transmission method 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 displacement data of the mesh data, and a step of encoding attribute data of the mesh data, and a step of transmitting data including the bitstream.

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

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

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

[0027] The mesh data transmission method, mesh data transmission device, mesh data reception method, and mesh data reception device according to the embodiments can reduce the base mesh bit amount by dividing a region similar to a reference sub-mesh and a region dissimilar to a reference sub-mesh within the current sub-mesh into a plurality of regions and performing encoding / decoding using different encoding / decoding types for each region, even when a one-to-one correspondence relationship is not established between the current sub-mesh and the reference sub-mesh.

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

[0029] FIG. 1 illustrates a system for providing dynamic mesh content according to embodiments.

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

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

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

[0033] Figure 5 illustrates a displacement generation process according to embodiments.

[0034] Figure 6 illustrates an intra-frame encoding process of V-MESH data according to embodiments.

[0035] Figure 7 illustrates an inter-frame encoding process of V-MESH data according to embodiments.

[0036] Figure 8 illustrates a lifting conversion process for displacement according to embodiments.

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

[0038] Figure 10 illustrates an attribute transfer process of a V-MESH compression method according to embodiments.

[0039] Figure 11 illustrates an intra-frame decoding process of V-MESH data according to embodiments.

[0040] Figure 12 shows an inter-frame decoding processor of V-MESH data.

[0041] Fig. 13 is a drawing showing an example of a transmitting device according to embodiments.

[0042] Fig. 14 is a drawing showing an example of a receiving device according to embodiments.

[0043] FIG. 15 is a diagram showing an example of a dynamic mesh encoding / decoding unit according to embodiments.

[0044] Fig. 16 is a drawing showing an example of a meshlet configuration according to embodiments.

[0045] FIGS. 17(a) to 17(f) are diagrams showing an example of a base mesh coding unit according to embodiments.

[0046] FIG. 18 is a diagram showing examples of meshlet types and meshlet reference information according to embodiments.

[0047] FIGS. 19(a) to 19(f) are drawings showing other examples of meshlet configurations according to embodiments.

[0048] FIG. 20 is a diagram showing examples of meshlet types and meshlet reference information according to embodiments.

[0049] Fig. 21 is a drawing showing another example of a transmitting device according to embodiments.

[0050] FIG. 22 is a block diagram showing an example of a displacement vector encoder that encodes displacement vectors or quantized displacement vector transform coefficients according to the present disclosure based on a 2D video codec.

[0051] FIG. 23 is a block diagram illustrating an example of a displacement vector encoder that encodes a displacement vector or a quantized displacement vector transform coefficient based on a zero run length according to the present disclosure.

[0052] FIG. 24 is a block diagram showing an example of a displacement vector encoder that arithmetically encodes a displacement vector or a quantized displacement vector transform coefficient according to the present disclosure.

[0053] FIG. 25 is a block diagram showing another example of a displacement vector encoder that encodes a displacement vector or a quantized displacement vector transform coefficient based on a zero run length according to the present disclosure.

[0054] FIG. 26 is a block diagram illustrating another example of a displacement vector encoder that arithmetic-encodes a displacement vector or a quantized displacement vector transform coefficient according to the present disclosure.

[0055] Fig. 27 is a flowchart showing an example of a process for converting a displacement vector in a displacement vector conversion unit according to embodiments.

[0056] FIG. 28 is a drawing showing another example of a receiving device according to embodiments.

[0057] Fig. 29 is a detailed block diagram showing an example of a displacement vector coordinate system inverse transformation unit according to embodiments.

[0058] Fig. 30 is a detailed block diagram showing another example of a displacement vector coordinate system inverse transformation unit according to embodiments.

[0059] Fig. 31 is a detailed block diagram showing an example of a displacement vector decoder according to embodiments.

[0060] Figure 32 is a flowchart showing an example of a process of inversely transforming a displacement vector in a displacement vector inverse transform unit according to embodiments.

[0061] FIG. 33 is a diagram showing an example of the syntax structure of a base mesh submesh unit according to embodiments.

[0062] FIG. 34 is a diagram showing an example of a syntax structure of meshlet-related information of a submesh according to embodiments.

[0063] Figure 35 is a flowchart showing an example of a transmission method according to embodiments.

[0064] Figure 36 is a flowchart showing an example of a receiving method according to embodiments.

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

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

[0067] With the recent development of 3D data modeling and rendering technology, research on creating and processing 3D data is being conducted in various fields such as Virtual Reality (VR), Augmented Reality (AR), autonomous driving, Computer-Aided Design (CAD) / Computer-Aided Manufacturing (CAM), and Geographic Information Systems (GIS). 3D data can be represented as point clouds, meshes, etc., depending on the representation format. Among these, a mesh is composed of geometric information expressing the coordinate values ​​of each vertex (or point), connection information indicating the connection relationship between vertices, a texture map expressing the color information of the mesh surface as 2D image data, and texture coordinates indicating mapping information between the surface of the mesh and the texture map. In the present disclosure, a mesh is defined as a dynamic mesh if one or more of the elements that make up the mesh change over time, and a static mesh if they do not change. In other words, dynamic mesh data may refer to mesh data that has an object or movement.

[0068] Because dynamic mesh data has a large amount of data for elements that constitute the mesh compared to two-dimensional image data, technologies have been developed to efficiently compress this large amount of mesh data to store and transmit it.

[0069] FIG. 1 illustrates a system for providing dynamic mesh content according to embodiments.

[0070] The system of FIG. 1 includes a transmitting device (100) and a receiving device (110) according to embodiments. The transmitting device (100) may include a mesh video acquisition unit (101), a mesh video encoder (102), a file / segment encapsulator (103), and a transmitter (104). The receiving device (110) may include a receiving unit (111), a file / segment decapsulator (112), a 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 mesh data transmitting device according to embodiments may be interpreted as a term referring to a 3D data transmitting device or transmitting device (100), or a mesh video encoder (hereinafter, referred to as an encoder) (102). The mesh data receiving device according to the embodiments may be interpreted as a term referring to a 3D data receiving device or receiving device (110), or a mesh video decoder (hereinafter, decoder) (113).

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

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

[0073] First, the method of compressing dynamic mesh data starts from the V-PCC (Video-based point cloud compression) standard technology for point cloud data. Point cloud data is data that has color information at the coordinates (X, Y, Z) of a vertex (or point). In the present disclosure, the coordinates (i.e., position information) of a vertex are referred to as geometry information, the color information of a vertex is referred to as attribute information, and the geometry information and attribute information are referred to as vertex information or point cloud data. The vertex information to which connectivity information between vertices is added is referred to as mesh data. When creating content, it can be created in the form of mesh data from the beginning. Alternatively, it can be used by converting it into mesh data by adding connectivity information to point cloud data.

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

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

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

[0077] A mesh compression system may include a transmitting device (100) and a receiving device (110) as shown in FIG. 1. The transmitting device (100) may encode mesh video to output a bitstream, and transmit the bitstream to the receiving device (110) in the form of a file or streaming (streaming segment) via a digital storage medium or a network. The digital storage medium may include various storage media such as USB, SD, CD, DVD, Blu-ray, HDD, and SSD.

[0078] In the above transmitting device (100), the encoder may be called a mesh video / video / picture / frame encoding device, and in the receiving device (110), the decoder may be called a mesh video / video / picture / frame decoding device. The transmitter may be included in a mesh video encoder. The receiver may be included in a mesh video decoder. The renderer (114) 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 (100) and the receiving device (110) may further include separate internal or external modules / units / components for a feedback process.

[0079] Mesh data represents the surface of an object as a number of polygons. Each polygon is defined by vertices in 3D space and connection information that describes how the vertices are connected. It can also contain vertex attributes 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 in the attributes of the mesh. The mapping can be described as a set of parameter coordinates, generally 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. Here, displacement can be used interchangeably with displacement, displacement information, or displacement vectors (i.e., displacement vectors).

[0080] The mesh video acquisition unit (101) may include processing 3D object data acquired through a camera, etc. into a mesh data type having the attributes described above through a series of processes and generating a video composed of such mesh data. The mesh video may have attributes of the mesh, such as vertices, polygons, connection information between vertices, colors, normals, etc., that may change over time. A mesh video having attributes and connection information that change over time in this way may be expressed as a dynamic mesh video.

[0081] A mesh video encoder (102) can encode an input mesh video into one or more video streams. One video can include multiple frames, and one frame can correspond to a still image / picture. In this document, a mesh video can include a mesh image / frame / picture, and a mesh video can be used interchangeably with a mesh image / frame / picture. The mesh video encoder (102) can perform a Video-based Dynamic Mesh (V-Mesh) Compression procedure. The mesh video encoder (102) 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.

[0082] The file / segment encapsulator (103) 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 a metadata processing unit, etc. The metadata processing unit may be included in the mesh video encoder (102) or may be configured as a separate component / module. The file / segment encapsulator (103) can encapsulate the corresponding data in a file format such as ISOBMFF, or process it in the form of other DASH segments, etc. The file / segment encapsulator (103) 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. Depending on the embodiment, the file / segment encapsulator (103) may encapsulate the mesh video related metadata itself into a file.

[0083] 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 (104) 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 it for transmission.

[0084] The transmission unit (104) can transmit encoded video / image information or data output in the form of a bitstream to the reception unit (111) of the reception device (110) 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 (104) can include an element for generating a media file through a predetermined file format and can include an element for transmission via a broadcasting / communication network. The reception unit (111) can extract the bitstream and transmit it to a decoding device.

[0085] The receiving unit (111) can receive mesh video data transmitted by a mesh data transmission device. Depending on the channel through which it is transmitted, the receiving unit (111) can receive mesh video data through a broadcast network, through a broadband, or through a digital storage medium.

[0086] The receiving processing unit can perform processing according to the transmission protocol on the received mesh video data. The receiving processing unit can be included in the receiving unit (111) or can be configured as a separate component / module. In order to correspond to the processing performed for transmission on the transmitting side, the receiving processing unit can perform the reverse process of the aforementioned transmission processing unit. The receiving processing unit can transfer the acquired mesh video data to the file / segment decapsulator (112) and transfer the acquired mesh video-related metadata to the metadata parser. The mesh video-related metadata acquired by the receiving processing unit can be in the form of a signaling table.

[0087] The file / segment decapsulator (112) can decapsulate mesh video data in the form of a file received from a receiving processing unit. The file / segment decapsulator (112) 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 the mesh video decoder (113), and the obtained mesh video-related metadata (metadata bitstream) can be transmitted to the metadata processing unit. The mesh video bitstream may include metadata (metadata bitstream). The metadata processing unit may be included in the mesh video decoder (113) or may be configured as a separate component / module. The mesh video-related metadata obtained by the file / segment decapsulator (112) may be in the form of a box or track within a file format. The file / segment decapsulator (112) may receive metadata required for decapsulation from the metadata processing unit, if necessary. The mesh video related metadata may be passed to the mesh video decoder (113) and used in the mesh video decoding procedure, or may be passed to the renderer (114) and used in the mesh video rendering procedure.

[0088] The mesh video decoder (113) can receive a bitstream and perform a reverse operation corresponding to the operation of the mesh video encoder (102) to decode the video / image. The decoded mesh video / image can be displayed through the display unit of the renderer (114). The user can view all or part of the rendered result through a VR / AR display or a general display.

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

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

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

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

[0093] This document relates to embodiments of 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 attributes that change over time, and it can perform lossy and lossless compression for various applications such as real-time communication, storage, free-viewpoint video, and AR / VR.

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

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

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

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

[0098] As described above, the encoding process of Fig. 1 is as follows.

[0099] That is, the video-based dynamic mesh compression (V-Mesh) compression method can provide a method of compressing dynamic mesh video data based on 2D video codecs such as HEVC (High Efficiency Video Coding) and VVC (Versatile Video Coding). The V-Mesh compression process receives the following data as input and performs compression.

[0100] Input mesh: Contains the 3D coordinates 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.

[0101] Attribute map: (Hereinafter, texture map is also used in the same meaning): Contains information about the attributes of the mesh (color, normal, displacement, etc.), 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. 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.).

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

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

[0104] Base mesh: The input mesh is simplified (decimated) through a pre-processing process, thereby expressing the objects of the input mesh using the minimum number of vertices determined by the user's standards.

[0105] Displacement: 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.

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

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

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

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

[0110] The pre-processor (200) can receive a static of a dynamic mesh (M(i)) and / or an attribute map (A(i)). The pre-processor (200) can generate a base mesh (m(i)) and / or a displacement (or displacement) (d(i)) through pre-processing. The pre-processor (200) can receive feedback information from the encoder (201) and generate the base mesh and / or the displacement based on the feedback information.

[0111] The encoder (201) can receive a base mesh (m(i)), a displacement (d(i)), a static of a dynamic mesh (M(i)), and / or an attribute map (A(i)). In the present disclosure, at least one of the base mesh (m(i)), the displacement (d(i)), the static of a dynamic mesh (M(i)), and / or the attribute map (A(i)) can be referred to as mesh-related data. The encoder (201) can encode the mesh-related data to generate a compressed bitstream.

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

[0113] Fig. 3 illustrates the configuration and operation of the preprocessor of Fig. 2. In Fig. 3, the input mesh may include a static of a dynamic mesh (M(i)) and / or an attribute map (A(i)). In addition, the input mesh may include three-dimensional coordinates of vertices constituting the mesh, normal information of each vertex, mapping information for mapping the mesh surface to a 2D plane, connection information between vertices constituting the surface, etc.

[0114] Fig. 3 shows a process of performing pre-processing on an input mesh. The pre-processing process (200) may largely include four steps: 1) GoF (Group of Frame) generation, 2) Mesh Decimation, 3) UV parameterization, and 4) Fitting subdivision surface (300). According to embodiments, GoF generation may be referred to as a GoF generation process or a GoF generation unit, mesh simplification may be referred to as a mesh simplification process or a mesh simplification unit, UV parameterization may be referred to as a UV parameterization process or a UV parameterization unit, and the fitting subdivision surface may be referred to as a fitting subdivision surface process or a fitting subdivision surface unit. The pre-processor (200) can generate displacement and / or base meshes from the received input mesh and transmit them to the encoder (201). The pre-processor (200) can transmit GoF information associated with GoF generation to the encoder (201).

[0115] Below, each step of Fig. 3 is described.

[0116] GoF Generation: This is the process of generating a reference structure for mesh data. If the number of vertices, the number of texture coordinates, the vertex connection information, and the 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. That is, if only the vertex coordinate values ​​are different between the current input mesh and the reference input mesh, the encoder (201) can perform inter frame encoding. Otherwise, intra frame encoding is performed for the corresponding frame.

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

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

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

[0120] Fitting subdivision surface (300): This is a process of performing subdivision on a decimated mesh (i.e., a simplified mesh having texture coordinates). The displacement and base mesh generated through this process are output to the encoder (201). A user-defined method, such as a mid-edge method, may be applied as the subdivision method. A fitting process is performed so that the input mesh and the mesh on which the subdivision has been performed become similar to each other. In the present disclosure, the mesh on which the fitting process has been performed is referred to as a fitted subdivision mesh (or fitted subdivision mesh).

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

[0122] Figure 4 illustrates the mid-edge method of the fitting subdivision surface described in Figure 3. Referring to Figure 4, an original mesh containing four vertices is subdivided to generate a subdivision mesh. A subdivision mesh can be generated by creating a new vertex in the middle of the edge between the vertices. Then, a fitting process is performed so that the input mesh and the subdivision mesh become similar to each other, thereby generating a fitted subdivision mesh.

[0123] 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 decoded 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 the 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.

[0124] Fig. 5 illustrates a displacement generation process according to embodiments. The displacement generation process of Fig. 5 may be performed in a pre-processor (200) or in an encoder (201).

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

[0126] 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 perform subdivision on a reconstructed base mesh to generate a subdivided reconstructed base mesh. Here, the restoration of the base mesh may be performed in the pre-processor (200) or in the encoder (201). The local coordinate system calculation unit may receive a fitted subdivision mesh and a subdivided reconstructed base mesh, and may convert a coordinate system of the mesh into a local coordinate system based on the fitted subdivision mesh and the subdivided reconstructed base mesh. 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.

[0127] The mesh data transmission method and device according to the embodiments can encode mesh data as follows. Mesh data is a term including point cloud data. Point cloud data (which may be referred to as point cloud for short) according to the embodiments can refer to data including vertex coordinates (or geometry information) and color information (or attribute information). In addition, geometry images, attribute images, occupancy maps, and additional information (or patch information) generated through patch generation and packing based on vertex coordinates and color information are also referred to as point cloud data. Therefore, point cloud data including connection information can be referred to as mesh data. In this document, point cloud and mesh data can be used interchangeably.

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

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

[0130] Fig. 6 illustrates an intra-frame encoding process of a V-MESH compression method according to embodiments. Each component for the intra-frame encoding process of Fig. 6 corresponds to hardware, software, a processor, and / or a combination thereof.

[0131] The encoding process of FIG. 6 details the encoding of the mesh video encoder (102) of FIG. 1. That is, it shows the configuration of the mesh video encoder (102) when the encoding of FIG. 1 is an intra-frame method. The encoder of FIG. 6 may include a pre-processor (200) and / or an encoder (201). The pre-processor (200) and encoder (201) of FIG. 6 may correspond to the pre-processor (200) and encoder (201) of FIG. 3.

[0132] The preprocessor (200) can receive an input mesh and perform the preprocessing described above. The preprocessing can generate a base mesh and / or a fitted subdivision mesh.

[0133] The quantizer (411) of the encoder (201) can quantize the base mesh and / or the fitted subdivided mesh. The static mesh encoder (412) can encode the static mesh (i.e., the quantized base mesh) and generate a bitstream (i.e., a compressed base mesh bitstream) including the encoded base mesh. The static mesh decoder (413) can decode the encoded static mesh (i.e., the encoded base mesh). The inverse quantizer (414) can inversely quantize the quantized static mesh (i.e., the base mesh) to output a reconstructed (or restored) base mesh. The displacement calculation unit (415) can generate displacements (or displacements) based on the reconstructed static mesh (i.e., the base mesh) and the fitted subdivided mesh. According to embodiments, the displacement calculation unit (415) calculates displacement, which is the position difference between each vertex of the subdivided base mesh and the fitted subdivided mesh after subdividing (or refining) the restored base mesh. In other words, the displacement is a displacement vector, which is the position difference between the vertices of the two meshes so that the fitted subdivided (or refining) mesh becomes similar to the original mesh. The forward linear lifting unit (416) can perform lifting transformation on the input displacement to generate lifting coefficients (or transform coefficients). The quantizer (417) can quantize the lifting coefficients. The image packing unit (418) can pack an image based on the quantized lifting coefficients. The video encoder (419) can encode the packed image. That is, the quantized lifting coefficients are packed into one frame as a 2D image by the image packing unit (418), compressed through the video encoder (419), and output as a displacement bitstream (i.e., compressed displacement bitstream).

[0134] A video decoder (420) decodes a compressed displacement bitstream. An image unpacking unit (421) can perform unpacking on the decoded displacement frame to output quantized lifting coefficients. A dequantizer (422) can dequantize the quantized lifting coefficients. An inverse linear lifting unit (423) applies inverse lifting to the inverse quantized lifting coefficients to generate restored displacement. A mesh restoration unit (424) reconstructs and deforms a mesh using the restored displacement output from the inverse linear lifting unit (423) and the restored base mesh (or subdivided restored base mesh) output from the inverse quantization unit (414). The present disclosure refers to the reconstructed and deformed mesh as a restored deformed mesh.

[0135] The attribute transfer (425) receives an input mesh and / or an input attribute map, and regenerates an attribute map based on the restored deformed mesh. The attribute map refers to a texture map corresponding to attribute information among mesh data components, and in the present disclosure, the attribute map and the texture map may be used interchangeably. The push-pull padding (426) may pad data in the attribute map based on the push-pull method. The color space conversion unit (427) may convert the space of the color component of the attribute map. For example, the attribute map may be converted from an RGB color space to a YUV color space. The video encoder (428) may encode the attribute map and output it as a compressed attribute bitstream.

[0136] A multiplexer (430) can generate a compressed bitstream by multiplexing a compressed base mesh bitstream, a compressed displacement bitstream, and a compressed attribute bitstream.

[0137] In Fig. 6, the displacement calculation unit (415) may be included in the pre-processor (200). In addition, at least one of the quantizer (411), the static mesh encoder (412), the static mesh decoder (413), and the inverse quantizer (414) may be included in the pre-processor (200).

[0138] As described in FIG. 6, the intra-frame encoding method includes base mesh encoding (also called static mesh encoding). That is, when performing intra-frame encoding on the current input mesh frame, the base mesh generated in the pre-processing process of the pre-processor (200) can be encoded using a static mesh compression technology in a static mesh encoder (412) after undergoing a quantization process in a quantizer (411). In the V-Mesh compression method, for example, Draco technology is applied to base mesh encoding, and vertex position information, mapping information (texture coordinates), vertex connection information, etc. of the base mesh become compression targets.

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

[0140] Fig. 7 illustrates an inter-frame encoding process of a V-MESH compression method according to embodiments. Each component for the inter-frame encoding process of Fig. 7 corresponds to hardware, software, a processor, and / or a combination thereof.

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

[0142] For a description of the components corresponding to the encoding operation of FIG. 6 among the encoding operations of FIG. 7, refer to the description of FIG. 6. That is, the operation of the quantizer (511), displacement calculation unit (515), wavelet transformer (516), quantizer (517), image packing unit (518), video encoder (519), video decoder (520), image unpacking unit (521), inverse quantizer (522), inverse wavelet transformer (523), mesh restoration unit (524), attribute transfer (525), push-pull padding (526), ​​color space conversion unit (527), video encoder (528), and multiplexer (530) of FIG. 7 is similar to that of the quantizer (411), static mesh encoder (412), static mesh decoder (413), inverse quantizer (414), displacement calculation unit (415), forward linear lifting unit (416), quantizer (417), image Since the operations described in the packing unit (418), video encoder (419), video decoder (420), image unpacking unit (421), inverse quantizer (422), inverse linear lifting unit (423), mesh restoration unit (424), attribute transfer (425), push-pull padding (426), color space conversion unit (427), video encoder (428), and multiplexer (430) are the same or similar, a detailed description thereof is omitted in FIG. 7 to avoid redundant description.

[0143] In Fig. 7, for inter-frame based encoding, the motion encoder (512) can obtain a motion vector between the two base meshes based on the restored quantized reference base mesh and the quantized current base mesh, and then encode the motion vector to output a compressed motion bitstream. The motion encoder (512) can be referred to as a motion vector encoder. The base mesh restoration unit (513) can restore the base mesh based on the restored quantized reference base mesh and the encoded motion vector. The restored base mesh is dequantized in the dequantizer (514) and then output to the displacement calculation unit (515).

[0144] In Fig. 7, the displacement calculation unit (515) may be included in the pre-processor (200). In addition, at least one of the quantizer (511), the motion encoder (512), the base mesh restoration unit (513), and the inverse quantizer (514) may be included in the pre-processor (200).

[0145] As described in Fig. 7, the inter-frame encoding method may include motion field encoding (also called motion vector encoding). Inter-frame encoding may be performed when a one-to-one correspondence of vertices is established between a reference mesh and a current input mesh, and only the position information of the vertices is different. When performing inter-frame encoding, instead of compressing the base mesh, the difference between the vertices of the reference base mesh and the current base mesh, i.e., the motion field (also called motion vector), may be calculated and encoded to encode this information. The reference base mesh is the result of quantizing the already decoded base mesh data and is determined according to the reference frame index determined in the GoF generation. The motion field may also be encoded as a value. Alternatively, the predicted motion field can be calculated by averaging the motion fields of the restored 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 residual motion field value can be encoded using entropy coding.The process of encoding displacement and attribute maps, excluding the motion field encoding process of inter frame encoding, is the same as the structure of the intra frame encoding method except for the base mesh encoding.

[0146] Figure 8 illustrates a lifting conversion process for displacement according to embodiments.

[0147] Figure 9 illustrates a process of packing transformation coefficients (or lifting coefficients) according to embodiments into a 2D image.

[0148] Figures 8 and 9 illustrate the process of transforming displacement and packing transform coefficients of the encoding process of Figures 6 and 7, respectively.

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

[0150] After 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 (see 415 in FIG. 6 or 515 in FIG. 7). For effective encoding, a data transform process such as wavelet transform can be applied to the displacement information (see 416 in FIG. 6 or 516 in FIG. 7).

[0151] FIG. 8 shows a process of transforming displacement information using a lifting transform in the forward linear lifting unit (416) of FIG. 6 or the wavelet transformer (516) of FIG. 7. For example, a linear wavelet-based lifting transform may be performed. The transform coefficients generated through the transform process are quantized in a quantizer (417 or 517) and then packed into a 2D image through an image packing unit (418 or 518) as in FIG. 9. The transform coefficients are configured as one block for every 256 (= 16×16) units, and each block can be packed in a 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. Transform coefficients can be packed by aligning them with Morton codes within a single block. The packed images generate displacement videos for each GoF unit, and these displacement videos can be encoded using a conventional video compression codec in a video encoder (419 or 519).

[0152] Referring to FIG. 8, the base mesh (original) may include vertices and edges for LoD0. A first subdivision mesh generated by dividing (or subdividing) the base mesh includes vertices generated by further dividing (or subdividing) 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 of the base mesh (LoD0). The first subdivision mesh may be further divided (or subdivided) to generate a second subdivision mesh. The second subdivision mesh includes LoD2. LoD2 includes base mesh vertices (LoD0), LoD1 including vertices further divided (or subdivided) from LoD0, and vertices further divided (or subdivided) from LoD1. LoD is a level of detail that indicates the degree of detail of mesh data content. As the level index increases, the distance between vertices becomes closer and the level of detail increases. In other words, the smaller the LoD value, the lower the detail of the mesh data content, and the larger the LoD value, the higher the detail of the mesh data content. LoD N contains the vertices included in the previous LoDN-1 as is. When a mesh (or vertex) is further divided through subdivision, the mesh can be encoded based on a prediction and / or update method by considering the previous vertices v1, v2 and the subdivided vertex v. Instead of directly 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 and v2. Since adjacent subdivision meshes have similar data, this property can be utilized for efficient encoding.Current vertex position information is predicted as a residual of previous vertex position information, and the previous vertex position information is updated through the residual. In the present disclosure, vertex, apex, and point may be used with the same meaning. In addition, LoDs may be defined during the subdivision process of the base mesh. According to embodiments, the subdivision process of the base mesh may be performed in the pre-processor (200) or in a separate component / module.

[0153] Referring to FIG. 9, a vertex has a transform coefficient (also called a lifting coefficient) generated through a lifting transformation. The transform coefficient of a vertex related to a lifting transformation can be packed into an image by an image packing unit (418 or 518) and then encoded by a video encoder (419 or 519).

[0154] Figure 10 illustrates an attribute transfer process of a V-MESH compression method according to embodiments.

[0155] According to the embodiments, FIG. 10 shows the detailed operation of the attribute transfer (425 or 525) of the encoding of FIG. 6, FIG. 7, etc.

[0156] Encoding according to embodiments includes attribute map encoding. According to embodiments, attribute map encoding may be performed in the video encoder (428) of FIG. 6 or the video encoder (528) of FIG. 7.

[0157] According to embodiments, in the present disclosure, the encoder compresses information about the input mesh through base mesh encoding (i.e., intra encoding), motion field encoding (i.e., inter 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 processes, 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 position information of vertices, 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 regenerated through the attribute transfer process of attribute transfer (425 or 525).

[0158] According to embodiments, attribute transfer (425 or 525) first checks whether each point P(u, v) of a 2D texture domain belongs to a texture triangle of a reconstructed deformed mesh, and if it exists in a texture triangle T, the barycentric coordinate of P(u, v) according to the triangle T ( , , ) is calculated. And the 3D vertex positions of triangle T and ( , , ) is used 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 vertex that corresponds to the most similar position to the calculated M(x, y, z) in the input mesh domain. Then, the center of mass coordinates of M'(x', y', z') in this triangle T' ( ', ', ') is 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 of push-pull padding (426 or 526).

[0159] The new attribute map generated through attribute transfer (425 or 525) is grouped into GoF units to form an attribute map video, which is compressed using the video codec of the video encoder (428 or 528).

[0160] Referring to Figure 10, the reference relationship between the input mesh, the input attribute map, the reconstructed deformed mesh, and the regenerated attribute map can be seen.

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

[0162] FIG. 11 illustrates an intra-frame decoding (or intra-decoding) process of V-Mesh technology according to embodiments.

[0163] Fig. 11 illustrates the configuration and operation of the mesh video decoder (113) of the receiving device of Fig. 1. In addition, Fig. 11 can restore mesh data by performing the reverse process of the intra-frame encoding process of Fig. 6. Each component for the intra-frame decoding process of Fig. 11 corresponds to hardware, software, and / or a combination thereof.

[0164] First, the bitstream (i.e., compressed bitstream) received and input to the demultiplexer (611) of the intra frame decoding unit (610) can be separated into a mesh substream, a displacement substream, an attribute map substream, and a substream containing patch information of the mesh, such as V-PCC / V3C. The term V-PCC (Video-based Point Cloud Compression) used in this document can be used with the same meaning as V3C (Visual Volumetric Video-based Coding), and the two terms can be used interchangeably. Therefore, the term V-PCC in this document can be interpreted as the term V3C.

[0165] According to embodiments, the mesh sub-stream may be input to a static mesh decoder (612) and decoded, the displacement sub-stream may be input to a video decoder (613) and decoded, and the attribute map sub-stream may be input to a video decoder (617) and decoded.

[0166] According to embodiments, the mesh sub-stream is decoded through a decoder (612) of a static mesh codec used in encoding, such as Google Draco, and as a result, a reconstructed quantized base mesh, for example, connection information, vertex geometry information, vertex texture coordinates, etc. of the base mesh can be reconstructed.

[0167] According to embodiments, the displacement sub-stream is decoded into displacement video through a decoder (613) of a video compression codec used in encoding, and is restored as displacement information for each vertex (i.e., Recon. displacements) through an image unpacking process of an image unpacking unit (614), an inverse quantization process of an inverse quantizer (615), and an inverse transform process of an inverse linear lifting unit (616).

[0168] According to embodiments, the base mesh restored by the static mesh decoder (612) is inverse quantized by the inverse quantizer (620) and then output to the mesh restoration unit (630). The mesh restoration unit (630) reconstructs and restores the deformed mesh (i.e., decoded mesh) through the restored displacement output from the inverse linear lifting unit (616) and the restored base mesh output from the inverse quantizer (620). That is, the inverse quantized restored base mesh is combined with the restored displacement information to generate the final decoded mesh. In the present disclosure, the final decoded mesh is referred to as a reconstructed deformed mesh.

[0169] According to embodiments, an attribute map sub-stream is decoded through a decoder (617) corresponding to a video compression codec used in encoding, and then restored to a final attribute map (i.e., decoded attribute map) through a color conversion unit (640) through processes such as color format conversion and color space conversion.

[0170] According to embodiments, 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.

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

[0172] As described above, the decoder of FIG. 11 performs the following intra-frame decoding operations. The static mesh decoder (612) decodes the mesh sub-stream to generate a reconstructed quantized base mesh, and the inverse quantizer (620) applies the quantization parameters of the quantizer inversely to generate the reconstructed base mesh. The video decoder (613) decodes the displacement sub-stream, the image unpacking unit (614) unpacks the images of the decoded displacement video, and the inverse quantizer (615) inversely quantizes the quantized images. The inverse linear lifting unit (616) applies a lifting transform in the reverse process of the encoder to generate the reconstructed displacement. The mesh restoration unit (630) generates a reconstructed deformed mesh based on the reconstructed base mesh and the reconstructed displacement. The video decoder (617) decodes the attribute map sub-stream, and the color conversion unit (640) converts the color format and / or space of the decoded attribute map to generate a decoded attribute map.

[0173] Figure 12 illustrates the inter-frame decoding (or inter-decoding) process of V-Mesh technology.

[0174] Fig. 12 illustrates the configuration and operation of the mesh video decoder (113) of the receiving device of Fig. 1. In addition, Fig. 12 can restore mesh data by performing the reverse process of the inter-frame encoding process of Fig. 7. Each component for the inter-frame decoding process of Fig. 12 corresponds to hardware, software, and / or a combination thereof.

[0175] First, the bitstream received and input to the demultiplexer (711) of the intra frame decoding unit (710) can be separated into a motion sub-stream (also called a motion sub-stream or motion vector sub-stream), a displacement sub-stream, an attribute map sub-stream, and a sub-stream including patch information of a mesh such as V3C / V-PCC.

[0176] According to embodiments, a motion sub-stream may be input to a motion decoder (712) and decoded, a displacement sub-stream may be input to a video decoder (713) and decoded, and an attribute map sub-stream may be input to a video decoder (717) and decoded.

[0177] According to embodiments, a motion sub-stream is decoded through entropy decoding and inverse prediction processes in a motion decoder (712) and restored into motion information (or motion vector information). A base mesh restoration unit (718) combines the restored motion information with a reference base mesh that has already been restored and stored to generate a reconstructed quantized base mesh for the current frame. An inverse quantizer (720) applies inverse quantization to the restored quantized base mesh to generate a reconstructed base mesh. A video decoder (713) decodes a displacement sub-stream, an image unpacking unit (714) unpacks an image of the decoded displacement video, and an inverse quantizer (715) inversely quantizes a quantized image. The reverse linear lifting unit (716) applies a lifting transformation in the reverse process of the encoder to generate a restored displacement. The mesh restoration unit (730) generates a reconstructed deformed mesh, i.e., a final decoded mesh, based on the restored base mesh and the restored displacement.

[0178] According to embodiments, the video decoder (717) decodes the attribute map sub-stream in the same manner as intra decoding, and the color conversion unit (740) converts the color format and / or space of the decoded attribute map to generate a decoded attribute map. The decoded mesh and the decoded attribute map can be utilized by the receiver as final mesh data that can be utilized by the user.

[0179] Referring to Fig. 12, the bitstream includes motion information (also called motion vectors), displacement, and an attribute map. Since Fig. 12 performs inter-frame decoding, it further includes a process of decoding inter-frame motion information. The motion information is decoded, and a restored quantized base mesh for the motion information is generated based on the reference base mesh, thereby generating a restored base mesh. For a description of the operation of Fig. 12, which is identical to that of Fig. 11, refer to the description of Fig. 11.

[0180] Fig. 13 illustrates a mesh data transmission device according to embodiments.

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

[0182] The operation process of a transmitter for compressing and transmitting dynamic mesh data using V-Mesh compression technology may be as shown in Fig. 13. The transmitter of Fig. 13 may perform an intra-frame encoding (or intra-encoding or intra-screen encoding) process and / or an inter-frame encoding (or inter-encoding or inter-screen encoding) process.

[0183] The pre-processor (811) receives the original mesh as input and generates a simplified mesh (decimated mesh) (or base mesh) and a fitted decimated mesh (or subdivision). Simplification can be performed based on the target number of vertices or target number of polygons that constitute the mesh. Parameterization, which generates texture coordinates and texture connection information per vertex, can be performed on the simplified mesh. For example, parameterization is a process of mapping a 3D surface to a texture domain for the decimated mesh. If parameterization is performed using the UVAtlas tool, mapping information is generated that can identify where each vertex of the decimated mesh can be mapped on a 2D image. The mapping information is expressed and stored as texture coordinates, and the final base mesh is generated through this process. In addition, the work of quantizing the mesh information in floating-point form into fixed-point form can be performed. This result can be output as a base mesh to a motion vector encoder (813) or a static mesh encoder (814) through a switching unit (812). The pre-processor (811) 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 pre-processor (811) can generate a fitted subdivided mesh by adjusting the vertex positions so that the subdivided mesh becomes similar to the original mesh.

[0184] According to embodiments, the base mesh is output to a motion vector encoder (813) via a switching unit (812) when performing inter-encoding for the corresponding mesh frame, and is output to a static mesh encoder (814) via a switching unit (812) when performing intra-encoding for the corresponding mesh frame. The motion vector encoder (813) may be referred to as a motion encoder.

[0185] For example, when performing intra-encoding (or intra-frame encoding) on ​​the corresponding mesh frame, the base mesh can be compressed through a static mesh encoder (814). In this case, encoding can be performed on connection information, vertex geometry information, vertex texture information, normal information, etc. of the base mesh. The base mesh bitstream generated through encoding is transmitted to a multiplexer (823).

[0186] As another example, when performing inter-encoding (or inter-frame encoding) for the corresponding mesh frame, the motion vector encoder (813) can receive a base mesh and a reference reconstructed base mesh (or a reconstructed quantized reference base mesh) as input, calculate a motion vector between the two meshes, and encode the value. In addition, the motion vector encoder (813) can perform prediction based on connection information using a previously encoded / decoded motion vector as a predictor, and encode a residual motion vector obtained by subtracting the predicted motion vector from the current motion vector. The motion vector bitstream generated through encoding is transmitted to the multiplexer (823).

[0187] The base mesh restoration unit (815) can receive the base mesh encoded by the static mesh encoder (814) or the motion vector encoded by the motion vector encoder (813) and generate a reconstructed base mesh. For example, the base mesh restoration unit (815) can perform static mesh decoding on the base mesh encoded by the static mesh encoder (814) to restore the base mesh. At this time, quantization can be applied before the static mesh decoding, and inverse quantization can be applied after the static mesh decoding. As another example, the base mesh restoration unit (815) can restore the base mesh based on the reconstructed quantized reference base mesh and the motion vector encoded by the motion vector encoder (813). The reconstructed base mesh is output to the displacement calculation unit (816) and the mesh restoration unit (820).

[0188] The displacement calculation unit (816) can perform mesh refinement on the restored base mesh. The displacement calculation unit (816) can calculate a displacement vector, which is a difference value between the vertex positions of the restored base mesh and the fitted subdivision (or refined) mesh generated by the pre-processor (811). At this time, the displacement vector can be calculated as many times as the number of vertices of the refined mesh. The displacement calculation unit (816) 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.

[0189] The displacement vector video generation unit (817) may include a linear lifting unit, a quantizer, and an image packing unit. That is, in the displacement vector video generation unit (817), the linear lifting unit may transform the displacement vector for effective encoding. The transformation may be performed by a lifting transformation, a wavelet transformation, etc., according to embodiments. In addition, quantization may be performed in a quantizer on the transformed displacement vector value, i.e., the transform coefficient. At this time, a different quantization parameter may be applied to each axis of the transform coefficient, and the quantization parameter may be derived according to an encoder / decoder agreement. The transformed and quantized displacement vector information may be packed into a 2D image in the image packing unit. The displacement vector video generation unit (817) may generate a displacement vector video by bundling packed 2D images for each frame, and the displacement vector video may be generated for each GoF (Group of Frame) unit of the input mesh.

[0190] The displacement vector video encoder (818) can encode the generated displacement vector video using a video compression codec. The generated displacement vector video bitstream is transmitted to a multiplexer (823).

[0191] The displacement vector restoration unit (819) may include a video decoder, an image unpacking unit, an inverse quantizer, and an inverse linear lifting unit. That is, the displacement vector restoration unit (819) performs decoding on an encoded displacement vector in the video decoder, performs image unpacking in the image unpacking unit, performs inverse quantization in the inverse quantizer, and then performs inverse transformation in the inverse linear lifting unit to restore the displacement vector. The restored displacement vector is output to the mesh restoration unit (820). The mesh restoration unit (820) restores a deformed mesh based on the base mesh restored by the base mesh restoration unit (815) and the displacement vector restored by the displacement vector restoration unit (819). The restored mesh (or referred to as a restored deformed mesh) has restored vertices, connection information between vertices, texture coordinates, and connection information between texture coordinates.

[0192] The texture map video generation unit (821) can regenerate a texture map based on the texture map (or attribute map) of the original mesh and the restored deformed mesh output from the mesh restoration unit (820). According to embodiments, the texture map video generation unit (821) can assign color information per vertex of the texture map of the original mesh to the texture coordinates of the restored deformed mesh. According to embodiments, the texture map video generation unit (821) can generate a texture map video by grouping the regenerated texture maps by GoF unit for each frame.

[0193] The generated texture map video can be encoded using a video compression codec of a texture map video encoder (822). The texture map video bitstream generated through encoding is transmitted to a multiplexer (823).

[0194] A multiplexer (823) multiplexes a motion vector bitstream (e.g., in case of inter encoding), a base mesh bitstream (e.g., in case of intra encoding), a displacement vector bitstream, and a texture map bitstream into a single bitstream. The single bitstream can be transmitted to a receiver via a transmitter (824). Alternatively, the motion vector bitstream, the base mesh bitstream, the displacement vector bitstream, and the texture map bitstream can be generated as a file with one or more track data or encapsulated into segments and transmitted to a receiver via the transmitter (824).

[0195] Referring to FIG. 13, a transmitting device (encoder) can encode a mesh in an intra-frame or inter-frame manner. A transmitting device according to intra-encoding can generate a base mesh, a displacement vector (or referred to as displacement), and a texture map (or referred to as attribute map). A transmitting device according to inter-encoding can generate a motion vector (or referred to as motion), a displacement vector (or referred to as displacement), and a texture map (or referred to as attribute map). The texture map obtained from the data input unit is generated and encoded based on the restored mesh. Displacement is generated and encoded through the difference in vertex positions between the base mesh and the divided (or subdivided or subdivided) mesh. More specifically, the displacement is the difference in position between the fitted sub-divided mesh and the sub-divided restored base mesh, i.e., the difference in vertex positions between the two meshes. In addition, the base mesh is generated by simplifying and encoding the original mesh through pre-processing. Motion is generated as motion vectors for the mesh of the current frame based on the reference base mesh of the previous frame.

[0196] Fig. 14 illustrates a mesh data receiving device according to embodiments.

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

[0198] The bitstream of the mesh data received by the receiver (910) is demultiplexed into a compressed motion vector bitstream (e.g., inter decoding) or a base mesh bitstream (e.g., intra decoding), a displacement vector bitstream, and a texture map bitstream after file / segment decapsulation in the demultiplexer (911). For example, if the current mesh has inter-screen encoding (i.e., inter encoding) applied, the motion vector bitstream is received, demultiplexed, and then output to the motion vector decoder (913) via the switching unit (912). As another example, if the current mesh has intra-screen encoding (i.e., intra encoding) applied, the base mesh bitstream is received, demultiplexed, and then output to the static mesh decoder (914) via the switching unit (912). Here, the motion vector decoder (913) may be referred to as a motion decoder.

[0199] According to embodiments, if the current mesh has inter-screen encoding applied according to frame header information, the motion vector decoder (913) can perform decoding on the motion vector bitstream. According to embodiments, the motion vector decoder (913) can reconstruct the final motion vector by adding the previously decoded motion vector as a predictor to the residual motion vector decoded from the bitstream.

[0200] According to embodiments, if the current mesh has been subjected to in-screen encoding according to frame header information, the static mesh decoder (914) can decode the base mesh bitstream to restore connection information, vertex geometry information, texture coordinates, normal information, etc. of the base mesh.

[0201] According to embodiments, the base mesh restoration unit (915) can restore the current base mesh based on the decoded motion vector or the decoded base mesh. For example, if the current mesh has inter-screen encoding applied, the base mesh restoration unit (915) can generate a restored base mesh by adding the decoded motion vector to the reference base mesh and then performing inverse quantization. As another example, if the current mesh has intra-screen encoding applied, the base mesh restoration unit (915) can generate a restored base mesh by performing inverse quantization on the base mesh decoded through the static mesh decoder (914).

[0202] According to embodiments, the displacement vector video decoder (917) can decode the displacement vector bitstream as a video bitstream using a video codec.

[0203] According to embodiments, the displacement vector restoration unit (918) extracts displacement vector transform coefficients from the decoded displacement vector video, and restores the displacement vector by applying inverse quantization and inverse transformation processes to the extracted displacement vector transform coefficients. To this end, the displacement vector restoration unit (918) may include an image unpacking unit, an inverse quantizer, and an inverse linear lifting unit. If the restored displacement vector is a value in a local coordinate system, a process of inversely transforming it into a Cartesian coordinate system may be performed.

[0204] The mesh restoration unit (916) can generate additional vertices by performing subdivision on the restored base mesh. Through subdivision, vertex connection information including the added vertices, texture coordinates, and texture coordinate connection information can be generated. At this time, the mesh restoration unit (916) can generate a final restored mesh (or a restored deformed mesh) by combining the subdivided restored base mesh with the restored displacement vector.

[0205] According to embodiments, the texture map video decoder (919) can decode the texture map bitstream as a video bitstream using a video codec to restore the texture map. The restored texture map has 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 each vertex.

[0206] According to embodiments, the mesh restored by the mesh restoration unit (916) and the texture map restored by the texture map video decoder (919) are shown to the user through a rendering process in the mesh data renderer (920).

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

[0208] A mesh data transmission device and method according to embodiments may pre-process mesh data, encode the pre-processed mesh data, and transmit a bitstream including the encoded mesh data. A point mesh data reception device and method according to embodiments may receive a bitstream including mesh data and decode the mesh data. The mesh data transmission and reception method / device according to embodiments may be abbreviated as method / device according to embodiments. The mesh data transmission and reception method / device according to embodiments may also be referred to as 3D data transmission and reception method / device or point cloud data transmission and reception method / device.

[0209] As mentioned above, in the current V-DMC standard, the current mesh can be divided into sub-mesh units, and encoding / decoding can be performed independently for each sub-mesh unit. In addition, if a one-to-one correspondence is not established between the current sub-mesh and the reference sub-mesh, the base mesh of the current sub-mesh is static mesh encoded. That is, in the current V-DMC standard, if a one-to-one correspondence is not established between the current sub-mesh and the reference sub-mesh, the sub-mesh type is determined as I_TYPE, and the current sub-mesh is encoded through a static mesh encoder. In this case, since the sub-mesh is a unit for independent encoding / decoding, there is a need for a unit that is efficient for coding by considering the characteristics of the mesh. In other words, if a one-to-one correspondence is not established between the current sub-mesh and the reference sub-mesh, the base mesh type is determined as the intra type, and static mesh encoding is performed on the base mesh. This is because even if a one-to-one correspondence is not established for some areas of the sub-mesh, the sub-mesh is always determined as an intra type and static mesh encoding is performed, so the amount of bits of the base mesh generated accordingly is considerable. In other words, if a one-to-one correspondence is not established between the current sub-mesh and the reference sub-mesh, the current sub-mesh is compressed with vertex position information, texture coordinates, and connection information between vertices and texture coordinates through static mesh coding. At this time, a one-to-one correspondence between the current mesh and the reference mesh is established when the number of vertices, connection information, etc. of the two meshes are all the same and only the position information of the vertices is different. Therefore, even if the similarity between the two meshes is high, there are cases where the number of vertices, etc. are partially different and static mesh coding must be performed, which generates a relatively large number of bits compared to when a motion codec is used.

[0210] In this disclosure, for efficient encoding / decoding of a base mesh, a method is proposed in which a current sub-mesh is divided into smaller mesh units and encoding / decoding is performed on the divided mesh units. In this disclosure, the smaller mesh units divided from the sub-mesh are referred to as meshlets or regions. In this disclosure, the terms "meshlet" and "region" are terms defined in consideration of their functions in this disclosure, and should be understood based on the intended meaning of the terms, rather than the simple name or meaning of the terms.

[0211] According to embodiments, the present disclosure can divide a sub-mesh into efficient coding units (e.g., meshlets or regions) by considering the similarity between the current sub-mesh and the reference sub-mesh, the characteristics of the current sub-mesh, etc. Through this, mesh data is determined and coded as a different base mesh type for each meshlet unit within the sub-mesh, thereby achieving the effect of reducing the amount of base mesh bits.

[0212] That is, the present disclosure proposes a method for efficiently encoding / decoding a mesh by dividing the current sub-mesh into meshlet units and performing encoding / decoding in the divided meshlet units.

[0213] As such, the present disclosure relates to V-DMC, a method for compressing 3D dynamic mesh data using an existing 2D video codec, and proposes a meshlet unit, which is a unit for encoding / decoding by determining the coding type (I_TYPE, P_TYPE, B_TYPE, etc.) of a base mesh, and syntax and semantics information related thereto. By doing so, the present disclosure enables encoding / decoding for each meshlet coding unit, which is a lower unit within a sub-mesh, by considering the similarity between the current sub-mesh and the reference sub-mesh, etc.

[0214] More specifically, the present disclosure can divide the current sub-mesh into multiple regions (i.e., meshlets). According to embodiments, after the current sub-mesh is divided into multiple regions similar to the reference sub-mesh and dissimilar regions, the present disclosure proposes a meshlet, which is a lower coding unit of the sub-mesh, to encode / decode similar regions by determining them as P_TYPE and dissimilar regions by determining them as I_TYPE. The present disclosure can encode / decode the base mesh and displacement vector by encoding / decoding the similar regions as Inter / SKIP types and the dissimilar regions as Intra types. That is, the present disclosure can obtain a bit amount reduction effect by performing encoding / decoding on the base mesh / displacement vector by applying different types (e.g., Intra, Inter, Skip, etc.) to each meshlet unit. For example, in the present disclosure, when an inter-type meshlet exists within an intra-type sub-mesh, the base mesh / displacement vector of the meshlet can be encoded / decoded with fewer bits by encoding / decoding the base mesh / displacement vector of the meshlet into an inter-type.

[0215] In the present disclosure, geometric information (or referred to as geometry or geometric data) is one of the elements that constitute a mesh, and includes vertices (or points), edges, polygons, etc. Here, a vertex defines a position in 3D space, an edge represents connection information between vertices, and a polygon forms the surface of the mesh with a combination of edges and vertices. That is, each vertex that constitutes the mesh represents a position in 3D space, and is expressed, for example, by x, y, z coordinates (i.e., canonical coordinate system). And, a polygon may be a triangle or a square. That is, geometry forms the skeleton of a 3D model, thereby defining the shape of the model and visually expressing it when rendered.

[0216] In the present disclosure, vertex, apex, and point may be used interchangeably. That is, a vertex has coordinates in 3D space, and a triangular or quadrilateral polygon can be created through connections between multiple vertices. In addition, V-DMC referred to in the present disclosure may also be referred to as V-mesh, and the two terms are expressions used interchangeably.

[0217] The following describes a method for dividing a sub-mesh into multiple areas with high similarity and dissimilarity between the current sub-mesh and the reference sub-mesh, that is, dividing the sub-mesh into efficient coding units, thereby encoding / decoding each into different types to achieve a bit-rate reduction effect.

[0218] FIG. 15 is a diagram showing an example of a dynamic mesh encoding / decoding unit according to embodiments.

[0219] That is, in the present disclosure, the dynamic mesh encoding / decoding unit can be configured with a structure as in FIG. 15.

[0220] Referring to FIG. 15, a dynamic mesh sequence, which is an input of a dynamic mesh encoder of a transmitting device (or a dynamic mesh decoder of a receiving device), may be composed of one or more frames. In addition, one frame may be composed of one or more tiles, and one tile may be composed of one or more sub-meshes. In addition, one sub-mesh may be composed of one or more meshlets.

[0221] In the present disclosure, base meshes, motion vectors, displacement vectors, etc. can be encoded / decoded in meshlet units.

[0222] Fig. 16 is a drawing showing an example of a meshlet configuration according to embodiments.

[0223] As mentioned above, one tile may be composed of one or more sub-meshes, and one sub-mesh may be composed of one or more meshlets.

[0224] Taking Fig. 16 as an example, one tile is composed of two sub-meshes, the first sub-mesh is composed of two meshlets, and the second sub-mesh is composed of one meshlet. At this time, if the base mesh type of the first meshlet of the first sub-mesh is P_TYPE or B_TYPE, the corresponding meshlet can include motion vector and displacement vector information. If the base mesh type of the second meshlet of the second sub-mesh is I_TYPE, the corresponding meshlet can include base mesh and displacement vector information. If the base mesh type of the first meshlet of the second sub-mesh is I_TYPE, the corresponding meshlet can include base mesh and displacement vector information.

[0225] In this way, depending on the base mesh type, the meshlet may include motion vector and displacement vector information (e.g., P_TYPE) or base mesh and displacement vector information (e.g., I_TYPE).

[0226] Figures 17(a) to 17(f) are diagrams showing an example of a base mesh coding unit according to embodiments. In order to help those skilled in the art understand the present disclosure, a sub-mesh segmented from a current base mesh may be referred to as a current sub-mesh, and a meshlet segmented from the current sub-mesh may be referred to as a current meshlet. In addition, a sub-mesh segmented from a reference base mesh may be referred to as a reference sub-mesh, and a meshlet segmented from a reference sub-mesh may be referred to as a reference meshlet.

[0227] Fig. 17(a) is an example of the current base mesh, and Fig. 17(b) is an example of dividing the current base mesh into sub-mesh units. That is, Fig. 17(b) is an example of the case where the current base mesh of Fig. 17(a) is divided into two current sub-meshes (i.e., sub-mesh 0, sub-mesh 1). Fig. 17(c) is an example of dividing each sub-mesh of Fig. 17(b) into meshlet units. That is, the current sub-mesh 0 (i.e., sub-mesh 0) is divided into two current meshlets (i.e., meshlet 0, meshlet 1), and the current sub-mesh 1 (i.e., sub-mesh 1) is divided (i.e., composed) into one current meshlet (i.e., meshlet 0). Fig. 17(d) is an example of the reference base mesh, and Fig. 17(e) is an example of dividing the reference base mesh into sub-mesh units. That is, FIG. 17(e) is an example in which the reference base mesh of FIG. 17(d) is divided into two reference sub-meshes (i.e., sub-mesh 0, sub-mesh 1). FIG. 17(f) is an example in which each sub-mesh of FIG. 17(e) is divided into meshlet units. That is, reference sub-mesh 0 is divided into one reference meshlet (meshlet 0), and reference sub-mesh 1 is divided into one reference meshlet (meshlet 0). In the present disclosure, when one sub-mesh is composed of one meshlet, the sub-mesh and the meshlet have the same structure.

[0228] Fig. 18 is a diagram showing examples of meshlet types and meshlet reference information according to embodiments. That is, Fig. 18 is a diagram showing examples of meshlet types determined based on the meshlet current information and meshlet reference information of Figs. 17(a) to 17(f). In the present disclosure, for convenience of explanation, submesh 0 may be used interchangeably with the index 0 submesh or submesh index 0. The same applies to submesh 1-N. In addition, meshlet 0 may be used interchangeably with the index 0 meshlet or meshlet index 0. The same applies to meshlet 1-N.

[0229] According to the embodiments, among the current meshlets divided from the sub-mesh of sub-mesh index 0 (submesh 0) within the current base mesh, the meshlet with index 1 (meshlet 1) has a one-to-one correspondence with the meshlet with index 0 (meshlet 0) among the reference meshlets divided from the sub-mesh of sub-mesh index 0 (submesh 0) within the reference base mesh, and therefore, the meshlet type can be determined as the INTER type, as shown in FIG. 18.

[0230] According to the embodiments, since the meshlet with index 0 among the current meshlets segmented from the sub-mesh of sub-mesh index 0 within the current base mesh does not have a one-to-one correspondence with the meshlet with index 0 segmented from the sub-mesh of sub-mesh index 0 within the reference base mesh, the meshlet type may be determined as the INTRA type, as shown in FIG. 18. That is, since the meshlet with index 0 among the current meshlets segmented from the sub-mesh of sub-mesh index 0 of the current base mesh does not have a meshlet with which the one-to-one correspondence is established among the reference meshlets of the reference base mesh, the meshlet type is determined as the INTRA type.

[0231] According to the embodiments, among the current meshlets segmented from the sub-mesh of sub-mesh index 1 (submesh 1) within the current base mesh, the meshlet with index 0 (meshlet 0) has a one-to-one correspondence with the reference meshlet with index 0 (meshlet 0) segmented from the sub-mesh of sub-mesh index 1 (submesh 1) within the reference base mesh, and therefore, as shown in FIG. 18, the meshlet type can be determined as the INTER type. That is, among the current meshlets segmented from the sub-mesh of sub-mesh index 1 of the current base mesh, the meshlet with index 0 has a one-to-one correspondence with the meshlet with index 0 of the index 1 reference sub-mesh (i.e., sub-mesh index 1) among the meshlets of the reference base mesh, and therefore, the meshlet type can be determined as the INTER type.

[0232] FIGS. 19(a) to 19(f) are diagrams showing other examples of meshlet configurations according to embodiments. That is, FIG. 19(a) is an example of a current base mesh, and FIG. 19(b) is an example of dividing the current base mesh into sub-mesh units. That is, FIG. 19(b) is a case where the current base mesh of FIG. 19(a) is divided into one sub-mesh (i.e., sub-mesh 0). In other words, FIG. 19(b) is an example where the current base mesh is composed of one sub-mesh. In the present disclosure, when the base mesh is composed of one sub-mesh, the base mesh and the sub-mesh have the same structure. FIG. 19(c) is an example where the sub-mesh of FIG. 19(b) is divided into meshlet units. That is, sub-mesh 0 is divided into three current meshlets (i.e., meshlet 0, meshlet 1, and meshlet 2). Fig. 19(d) is an example of a reference base mesh, and Fig. 19(e) is an example of dividing the reference base mesh into sub-mesh units. That is, Fig. 19(e) is an example of a case where the reference base mesh of Fig. 19(d) is composed of one sub-mesh (i.e., sub-mesh 0). Fig. 19(f) is an example of dividing the sub-mesh of Fig. 19(e) into meshlet units. That is, a case where sub-mesh 0 is composed of one reference meshlet (meshlet 0). In the present disclosure, when one sub-mesh is composed of one meshlet, the sub-mesh and the meshlet have the same structure.

[0233] Fig. 20 is a diagram showing examples of meshlet types and meshlet reference information according to embodiments. That is, Fig. 20 is a diagram showing examples of meshlet types determined based on the meshlet current information and meshlet reference information of Figs. 19(a) to 19(f).

[0234] According to embodiments, among the current meshlets segmented from the sub-mesh of sub-mesh index 0 (submesh 0) within the current base mesh, the meshlet with index 1 (meshlet 1) has a one-to-one correspondence with the meshlet with index 0 (meshlet 0) among the reference meshlets segmented from the sub-mesh of sub-mesh index 0 (submesh 0) within the reference base mesh, and therefore, the meshlet type can be determined as the INTER type, as shown in FIG. 20. That is, among the current meshlets with sub-mesh index 0 of the current base mesh, the meshlet with index 1 has a one-to-one correspondence with the meshlet with index 0 of the reference sub-mesh of the index 0 reference meshlet of the reference base mesh, and therefore, the meshlet type can be determined as the INTER type.

[0235] According to the embodiments, since the meshlet with index 0 among the current meshlets segmented from the sub-mesh of sub-mesh index 0 within the current base mesh does not have a one-to-one correspondence with the meshlet with index 0 segmented from the sub-mesh of sub-mesh index 0 within the reference base mesh, the meshlet type may be determined as an INTRA type, as shown in FIG. 20. In addition, the meshlet with index 2 among the current meshlets segmented from the sub-mesh of sub-mesh index 0 within the current base mesh does not have a one-to-one correspondence with the meshlet with index 0 segmented from the sub-mesh of sub-mesh index 0 within the reference base mesh, the meshlet type may be determined as an INTRA type, as shown in FIG. 20. That is, among the current meshlets with sub-mesh index 0 of the current base mesh, there is no meshnet with which the meshlets with indices 0 and 2 have a one-to-one correspondence among the reference meshlets of the reference base mesh, so the meshlet type can be determined as INTRA type.

[0236] The following describes a process of dividing a sub-mesh into one or more meshnets as described above, and encoding / decoding mesh data for each divided meshnet unit. The mesh data may be at least one of base mesh, motion vector, or displacement vector information.

[0237] Fig. 21 illustrates a transmitting device according to embodiments. The transmitting device of Fig. 21 may be referred to as a mesh data transmitting device or an encoder or an encoder of a transmitting device or a V-Mesh encoder or a dynamic mesh encoder.

[0238] FIG. 21 corresponds to the transmitting device (100) or the mesh video encoder (102) of FIG. 1, the encoder (pre-processor and encoder) of FIG. 2, FIG. 6, or FIG. 7, the transmitting device of FIG. 13, and / or the transmitting encoding device corresponding thereto. Therefore, parts not described in FIG. 21 will refer to the description of the transmitting device (100) or the mesh video encoder (102) of FIG. 1, the encoder (pre-processor and encoder) of FIG. 2, FIG. 6, or FIG. 7, and the transmitting device of FIG. 13. The elements of the transmitting device illustrated in FIG. 21 may be implemented by hardware, software, a processor connected to a memory, and / or a combination thereof. That is, the elements of the transmitting device of FIG. 21 may be implemented by hardware, software, firmware, or a combination thereof, including one or more processors or integrated circuits configured to be able to communicate with one or more memories, although not illustrated in the drawing. One or more processors may perform at least one of the operations and / or functions of the elements of the transmitting device of FIG. 21 described above. Furthermore, one or more processors may operate or execute a set of software programs and / or instructions for performing the operations and / or functions of the elements of the transmitting device of FIG. 21. The execution order of each block in FIG. 21 may be changed, some blocks may be omitted, and some blocks may be newly added.

[0239] In the present disclosure, the operation process of a transmitter for compressing and transmitting dynamic mesh data using V-Mesh compression technology may be as shown in Fig. 21. The transmitter of Fig. 21 may support both an intra-frame encoding (or intra-encoding or intra-screen encoding) process and / or an inter-frame encoding (or inter-encoding or inter-screen encoding) process.

[0240] In Fig. 21, the mesh simplification unit (11011) simplifies the input original mesh through a mesh simplification algorithm to generate a base mesh (or simplified base mesh or simplified mesh). At this time, mesh simplification can be performed based on the number of target vertices or target polygons constituting the mesh. For example, a method such as decimation can be used as a mesh simplification algorithm that simplifies the original mesh. That is, the decimation method can be a process of selecting vertices to be removed from the original mesh using a certain reference point, and then removing the selected vertices and the triangles connected to the selected vertices.

[0241] That is, the mesh simplification unit (11011) can simplify the input mesh by the target number of vertices or the target number of faces. At this time, the simplification process can be performed through various methods such as triangle collapse and edge collapse.

[0242] According to embodiments, the base mesh simplified in the mesh simplification unit (11011) is provided to the mesh parameterization unit (11012) and the mesh refinement unit (11018).

[0243] The mesh parameterization unit (11012) performs a process of mapping a 3D surface to a texture domain for a simplified mesh (decimated mesh). That is, the mesh parameterization unit (11012) generates texture coordinates and texture connection information of the input mesh. In one embodiment, the mesh parameterization unit (11012) may perform parameterization using a UV Atlas tool. Through this process, mapping information is generated regarding which location on a 2D image each vertex of the simplified mesh (decimated mesh) can be mapped to. The mapping information is expressed and stored as texture coordinates, and through this process, the final base mesh is generated. That is, the mesh parameterization unit (11012) performs parameterization to generate texture coordinates (UV coordinates) and texture connection information per vertex of the input mesh (i.e., simplified mesh or simplified base mesh).

[0244] The final base mesh (or base mesh with texture map) generated in the above parameterization unit (11012) is input to the mesh quantization unit (11013) and quantized.

[0245] According to embodiments, the mesh quantization unit (11013) may perform a task of quantizing floating-point type mesh information (e.g., geometry information (x, y, z) or / and texture coordinates (u, v), normal information (nx, ny, nz), etc.) into fixed-point type. That is, the mesh quantization unit (11013) may quantize vertex coordinates and texture coordinates of the base mesh. According to embodiments, quantization for specific components may be omitted.

[0246] The above mesh subdivision unit (11018) subdivides the base mesh simplified by the mesh simplification unit (11011). That is, the mesh subdivision unit (11018) 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. At this time, depending on the subdivision method, geometry information connection information, texture coordinate connection information, and texture coordinates can be implicitly derived and generated. According to embodiments, the mesh subdivision unit (11018) can perform subdivision through a method such as mid-edge, Loop, or Catmul&Clark.

[0247] More specifically, in the mesh refinement unit (11018), mesh refinement can be performed n times by user parameters or a promise of the encoder (i.e., transmitting device) / decoder (i.e., receiving device). According to embodiments, the vertices of the base mesh are vertices of level 0 (R0), the vertices newly generated by performing refinement once are vertices of level 1 (R1), … the vertices newly generated by performing refinement n times are vertices of level n (R n ) can be defined as vertices of level 0 (R0). For convenience of explanation, the present disclosure refers to vertices of level 0 (R0) as level 0 vertices, vertices of level 1 (R1) as level 1 vertices, …, level n (R n ) can be called level n vertices. Also, level 0 is called the 0th level (R0), level 1 is called the 1st level (R1), … level n is called the nth level (R n ) can be called.

[0248] According to embodiments, LoD0, LoD1, … LoDn can be defined as in the following mathematical expression 1.

[0249] [Mathematical Formula 1]

[0250] LoD0 = R0

[0251] LoD1 = R0+ R1= LoD0 + R1

[0252] …

[0253] LoDn = R0+ R1+, … + R n = LoDn-1 + R n

[0254] That is, the base mesh includes vertices for LoD0. And, the first subdivision mesh generated by subdividing the base mesh once includes vertices for LoD1. That is, LoD1 includes vertices of the base mesh (i.e., R0 vertices) and vertices of a newly generated level 1 by subdividing the base mesh (i.e., R1 vertices). In addition, the second subdivision mesh generated by subdividing the first subdivision mesh again includes vertices for LoD2. That is, LoD2 includes vertices of the base mesh (i.e., R0 vertices), vertices of a newly generated level 1 by subdividing the base mesh (i.e., R1 vertices), and vertices of a newly generated level 2 by subdividing the first subdivision mesh (i.e., R2 vertices).

[0255] In this way, LoD represents the level of detail of mesh data content, and as the LoD (or level) index increases, the distance between vertices becomes closer and the level of detail increases. In other words, the smaller the LoD value, the lower the detail of the mesh data content, and the larger the LoD value, the higher the detail of the mesh data content.

[0256] According to embodiments, the mesh fitting unit (11019) can perform fitting by adjusting vertex positions so that the mesh subdivided by the mesh subdivision unit (11018) becomes similar to the original mesh, thereby generating a fitted subdivided mesh.

[0257] According to embodiments, the mesh simplification unit (11011), the mesh parameterization unit (11012), the mesh refinement unit (11018), and the mesh fitting unit (11019) may be omitted, and when these processes are omitted, the original mesh may be applied as input to the mesh quantization unit (11013).

[0258] At this time, coordinate information of the original mesh can be applied as input to the displacement vector calculation unit (11020), and according to embodiments, the displacement vector encoding process (displacement vector calculation unit (11020), displacement vector coordinate system conversion unit (11021), and displacement vector encoder (11022)) can be omitted.

[0259] The present disclosure may be referred to as a pre-processor, including a mesh simplification unit (11011), a mesh parameterization unit (11012), a mesh refinement unit (11018), and a mesh fitting unit (11019). According to embodiments, the pre-processor may further include a displacement vector calculation unit (11020).

[0260] Meanwhile, the base mesh that has passed through the mesh parameterization unit (11012) and mesh quantization unit (11013) is input to the base mesh division unit (12011).

[0261] According to embodiments, the base mesh division unit (12011) divides the input base mesh into one or more sub-meshes, and divides each sub-mesh into one or more meshlets. That is, the base mesh division unit (12011) performs a process of dividing the sub-mesh into a plurality of meshlets, which are lower units of the sub-mesh.

[0262] In the present disclosure, the method of dividing a sub-mesh into meshlets may perform the division by considering the similarity between the current sub-mesh and the reference sub-mesh, may perform the division by considering the change in the motion vector, and may also perform the division by various division algorithms.

[0263] In one embodiment, when performing segmentation by considering the similarity between the current sub-mesh and the reference sub-mesh, the matching area between the current sub-mesh and the reference sub-mesh can be searched for and segmented into a matching area (or an area with high similarity) and a non-matching area (or an area with no similarity). The matching method may perform matching using distance information between vertices based on an ICP (Iterative Closest Point method) algorithm or the like, or may perform matching based on feature points or the like, depending on the embodiment. Taking FIGS. 19(a) to 19(f) as examples, by searching for the matching area between the current sub-mesh and the reference sub-mesh, the current sub-mesh can be segmented into three meshlets, and the reference sub-mesh can be segmented into one meshlet (i.e., no segmentation is performed). At this time, the index 1 meshlet (meshlet 1) of the current sub-mesh is a region that matches the index 0 meshlet (meshlet 0) of the reference sub-mesh, and the index 0 meshlet (meshlet 0) and index 2 meshlet (meshlet 2) of the current sub-mesh do not have matching regions in the reference sub-mesh. That is, the index 1 meshlet (meshlet 1) of the current sub-mesh corresponds to a matching region (or a similar region or a region with high similarity) between the current sub-mesh and the reference sub-mesh, and the index 0 meshlet (meshlet 0) and index 2 meshlet (meshlet 2) of the current sub-mesh correspond to a non-matching region (or a non-similar region) between the current sub-mesh and the reference sub-mesh. For example, the meshlet type (or meshlet coding / decoding type) of the meshlet of the matching region may be determined as an inter type, and the meshlet type of the meshlet of the non-matching region may be determined as an intra type.

[0264] In another embodiment, when segmenting considering the change in motion vector, the sequence can be segmented into an area with a large motion change and an area with a small motion change. In the present disclosure, the motion change can estimate the motion vector through motion estimation between the current base mesh and the reference base mesh. For example, the meshlet type of the meshlet of the area with a small motion change can be determined as the inter type, and the meshlet type of the meshlet of the area with a large motion change can be determined as the intra type.

[0265] That is, in the present disclosure, the base mesh segmentation unit (12011) can determine a meshlet type by comparing the current meshlet(s) segmented from a sub-mesh within the current base mesh with the reference meshlet(s) segmented from a sub-mesh of the reference base mesh. Here, the determined meshlet type may be an inter type or an intra type for encoding / decoding the corresponding meshlet.

[0266] In the present disclosure, details of dividing a sub-mesh into one or more meshlets and details of determining a meshlet type by comparing meshlet(s) divided from a sub-mesh of a current base mesh with meshlet(s) divided from a sub-mesh of a reference base mesh are described in detail in FIGS. 15 to 20, so for parts not described herein, refer to the description of FIGS. 15 to 20.

[0267] According to embodiments, the output of the base mesh segmentation unit (12011) may be provided to a motion vector encoder (11015) via a switching unit (11014) or to a static mesh encoder (11016).

[0268] In the above motion vector encoder (11015) and / or static mesh encoder (11016), a coding unit may be one of a sequence, a frame, a tile, a submesh, or a meshlet.

[0269] The present disclosure will be described using frames or meshlets as coding units as examples. That is, the encoding process in the motion vector encoder (11015) and / or the static mesh encoder (11016) may be performed on a frame-by-frame basis or on a meshlet-by-meshlet basis. For example, if meshlet division is performed in the base mesh division unit (12011), motion encoding or static mesh encoding may be performed on a meshlet-by-meshlet basis. According to embodiments, when inter-encoding is performed on a corresponding mesh frame or a corresponding meshlet, the base mesh of the corresponding frame or the corresponding meshlet is output to the motion vector encoder (11015) through the switching unit (11014), and when intra-encoding is performed on a corresponding mesh frame or a corresponding meshlet, the base mesh of the corresponding frame or the corresponding meshlet is output to the static mesh encoder (11016) through the switching unit (11014). The motion vector encoder (11015) may be referred to as a motion encoder.

[0270] For example, when performing intra encoding for the corresponding mesh frame or the corresponding meshlet, the base mesh can be compressed through the static mesh encoder (11016). In this case, encoding can be performed on connection information, vertex geometry information, vertex texture information, normal information, etc. of the base mesh. That is, vertex coordinates, vertex connection information, texture coordinates, texture connection information, etc. of the mesh can be encoded in the static mesh encoder (11016). The base mesh bitstream generated through encoding is transmitted to a multiplexer (not shown). According to embodiments, static mesh encoding can be performed in units of meshlets.

[0271] As another example, when performing inter-encoding on the corresponding mesh frame or meshlet, the motion vector encoder (11015) can receive the current base mesh and the reference reconstructed base mesh (or the reconstructed quantized reference base mesh) as input, calculate the motion vector between the two meshes, and encode the value. In addition, the motion vector encoder (11015) can perform prediction based on connection information using the previously encoded / decoded motion vector as a predictor, and entropy-encode the differential motion vector (or residual motion vector) obtained by subtracting the predicted motion vector from the current motion vector. According to embodiments, the motion vector encoding can be performed on a vertex basis, a subgroup basis, or a meshlet basis. The motion vector bitstream generated through the motion vector encoding is transmitted to a multiplexer (not shown) as a base mesh bitstream. That is, in the case of intra-encoding, the static mesh bitstream is input to the multiplexer as a base mesh bitstream, and in the case of inter-encoding, the motion vector bitstream is input to the multiplexer as a base mesh bitstream.

[0272] In Fig. 21, the base mesh restoration unit (11017) can receive a base mesh encoded by a static mesh encoder (11016) or a motion vector encoded by a motion vector encoder (11015) to generate a reconstructed base mesh. The base mesh restoration unit (11017) performs restoration of the base mesh according to the encoding type (inter-encoding or intra-encoding) of the current mesh. For example, the base mesh restoration unit (11017) can perform static mesh decoding on the base mesh encoded by the static mesh encoder (11016) to restore the base mesh. At this time, quantization can be applied before static mesh decoding, and inverse quantization can be applied after static mesh decoding. That is, when intra-encoding is performed, inverse quantization can be performed on the base mesh quantized through the mesh quantization unit (11013) to restore the current base mesh. As another example, the base mesh restoration unit (11017) can restore the base mesh based on the restored quantized reference base mesh and the motion vector encoded by the motion vector encoder (11015). That is, when inter-encoding is performed, the current base mesh can be generated by decoding the motion vector using the motion vector decoding method and then applying (i.e., adding) the decoded motion vector to the reference restoration base mesh. At this time, when the motion vector is not quantized, the motion vector restoration process is omitted and the current base mesh can be restored using the motion vector calculated by the motion vector encoder (11015).

[0273] According to embodiments, if motion vector encoding or static mesh encoding is performed in meshlet units in the motion vector encoder (11015) and the static mesh encoder (11016), base mesh restoration may also be performed in meshlet units in the base mesh restoration unit (11017). That is, the base mesh restoration unit in the base mesh restoration unit (11017) may be a meshlet unit. In addition, if the base meshes restored in meshlet units are reversed to the meshlet division and sub-mesh division performed in the base mesh division unit (12011), the base meshes restored in meshlet units can be restored to base meshes similar to or identical to the base mesh before being divided into sub-meshes and meshlets.

[0274] Additionally, when multiple meshlets are restored, a process of filtering the boundaries between the restored meshlets may be performed. In the present disclosure, the filtering process may, depending on the embodiment, select one of the corresponding vertices between the boundaries or select the midpoint if the meshlets are subdivided with the same number of subdivisions. If the number of subdivisions is not the same, additional vertices may be created on the boundary of the meshlet with the smaller number of subdivisions, or some vertices may be removed on the boundary of the meshlet with the larger number of subdivisions.

[0275] And, the restored base mesh is output to the displacement vector calculation unit (11020) and the mesh inverse quantization unit (11024).

[0276] According to embodiments, the displacement vector calculation unit (11020) can perform mesh refinement on the restored base mesh. In addition, the displacement vector calculation unit (11020) can calculate a displacement vector, which is a difference value of vertex positions between the restored base mesh that has been refined and the fitted subdivision (or refined) mesh generated by the mesh fitting unit (11019). At this time, the displacement vector can be calculated as many times as the number of vertices of the refined mesh. That is, the displacement vector of the number of vertices of the refined mesh can be calculated through the displacement vector calculation unit (11020).

[0277] According to embodiments, the displacement vector coordinate system transformation unit (11021) can transform a vertex displacement vector calculated in a 3D Cartesian coordinate system (i.e., (x, y, z) space) into a local coordinate system (i.e., normal, tangential, bi-tangential coordinate system) based on the normal vector of each vertex. At this time, the normal vector can be calculated for each subdivided vertex based on the geometry information and connection information of the surrounding vertices. According to embodiments, only the normal component among the (normal, tangential, bi-tangential) coordinate systems can be encoded. This means that when the coordinate system transformation is applied according to the agreement between the encoder / decoder, encoding of only the normal component is always performed, or the encoder can decide to signal a 1-bit flag (onlyNormFlag).

[0278] In the present disclosure, whether or not to perform displacement vector coordinate system transformation is determined by an agreement between the encoder / decoder, or whether or not to perform coordinate system transformation is determined by transmitting a coordinate system transformation status flag (applyLocalCoord) in units such as sequence, GOF (Group of frame), frame, and sub-mesh.

[0279] According to embodiments, the displacement vector encoder (11022) can perform encoding on the displacement vector or displacement vector transformation coefficient output from the displacement vector calculation unit (11020) or the displacement vector coordinate system transformation unit (11021). In the present disclosure, the displacement vector encoder (11022) can perform encoding through a video codec-based encoder, a zero run length encoder, an arithmetic encoder, or the like. For example, when the encoding method is video codec-based encoding, the displacement vector encoder (11022) can encode the displacement vector or the displacement vector transformation coefficient by packing it into a frame. That is, in the displacement vector encoder (11022), the displacement vector transform coefficients can be packed into a 2D image and then encoded using a 2D video codec (i.e., a video compression codec), or zero run-length encoded, or arithmetic encoded to generate a displacement vector video bitstream.

[0280] According to embodiments, a displacement vector video bitstream encoded and generated by a displacement vector encoder (11022) is transmitted to a multiplexer (not shown). According to embodiments, a method for selecting encoding of the displacement vector encoder (11022) may use a displacement vector encoder promised in an encoder (i.e., a transmitting side) / decoder (i.e., a receiving side), or may analyze the characteristics of a displacement vector in an encoder on the transmitting side and transmit the type of a selected displacement vector encoder to a decoder on the receiving side.

[0281] According to embodiments, the displacement vector restoration unit (11023) can restore the displacement vector by performing the reverse process of displacement vector encoding on the displacement vector or displacement vector transform coefficient encoded by the displacement vector encoder (11022). That is, the displacement vector restoration unit (11023) can perform displacement vector depacking depending on the method of encoding the displacement vector, for example, when encoding is based on a video codec. In other words, the bitstream encoded by the 2D video encoder (i.e., the video codec-based encoder) after being packed into a 2D image / video is decoded by the 2D video decoder and depacked. In addition, the displacement vector restoration unit (11023) can additionally perform inverse quantization, inverse transformation, etc. depending on whether quantization and transformation processes are performed during the displacement vector encoding process. For example, inverse quantization is performed on the quantized transform coefficients on which inverse packing has been performed, and inverse transformation is performed to calculate the restored displacement vector.

[0282] According to embodiments, the mesh dequantization unit (11024) can dequantize vertex coordinates or texture coordinates of the restored base mesh as a reverse process of quantization. More specifically, the mesh dequantization unit (11024) performs dequantization using inputs such as restored geometry information (x, y, z) and / or texture coordinates (u, v) and / or normal information (nx, ny, nz) of the restored base mesh. According to embodiments, dequantization for a specific component may be omitted. In addition, if the quantization process is omitted in the mesh quantization unit (11013), the dequantization process is also omitted in the mesh dequantization unit (11024).

[0283] According to embodiments, the mesh restoration unit (11025) can restore a mesh based on a restored displacement vector output from the displacement vector restoration unit (11023) and a restored base mesh (or a dequantized restored base mesh) output from the mesh dequantization unit (11024). More specifically, the mesh restoration unit (11025) can perform subdivision on the restored base mesh output from the mesh dequantization unit (11024) and add the restored displacement vector from the displacement vector restoration unit (11023) to generate a reconstructed deformed mesh. That is, the mesh restoration unit (11025) performs subdivision on the restored base mesh, which is restored by performing dequantization in the mesh dequantization unit (11024), to generate subdivided vertex position information, texture coordinates, and connection information. In addition, the mesh restoration unit generates restored vertex position information by adding a restored displacement vector to the subdivided vertex position information. The mesh restored by the mesh restoration unit (11025) (or referred to as restored mesh or restored deformed mesh) has restored vertices, connection information between vertices, texture coordinates, and connection information between texture coordinates. The restored mesh (or referred to as restored mesh or restored deformed mesh) generated by the mesh restoration unit (11025) is provided to the texture map generation unit (11026).

[0284] According to embodiments, the texture map generation unit (11026) can regenerate the texture map of the current mesh based on the texture map (or attribute map) of the original mesh and the mesh restored by the mesh restoration unit (11025). That is, the texture map generation unit (11026) can generate the texture map of the restored mesh through the relationship between the texture coordinates and connection information of the restored mesh and the original mesh and the texture map of the original mesh.

[0285] According to embodiments, the texture map generation unit (11026) can assign color information per vertex of the texture map of the original mesh to the texture coordinates of the restored base mesh (or the restored deformed mesh). According to embodiments, the texture map generation unit (11026) can generate a texture map (or texture map video) by grouping the regenerated texture maps by GoF unit for each frame.

[0286] The texture map generated in the texture map generation unit (11026) may be encoded in the texture map encoder (11027). For example, the texture map encoder (11027) may encode the texture map using a 2D video codec-based encoder, a zero run length encoder, an entropy coding-based arithmetic encoder, etc. That is, the texture map generated through the texture map generation unit (11026) is stacked in the frame order of the mesh to form a texture map video, and encoding is performed on the texture map video using the 2D video encoder. In addition, the texture map encoder (11027) may further perform color space conversion of the texture map. That is, when the color space of the texture map is RGB444, encoding may be performed after conversion to a color space such as YUV420 or YUV444. Then, the texture map substream (or texture map video bitstream) generated through the texture map encoding is transmitted to a multiplexer (not shown).

[0287] According to embodiments, the type of texture map encoder (11027) may include a video encoder (e.g., VVC, HEVC, etc.), an entropy coding-based encoder, etc. In addition, a method for selecting a texture map encoder (11027) may use a texture map encoder promised in an encoder (i.e., a transmitting side) / decoder (i.e., a receiving side), or may transmit the type of texture map encoder selected by the encoder on the transmitting side to the decoder on the receiving side.

[0288] According to embodiments, a multiplexer (not shown) may multiplex an input base mesh bitstream, a displacement vector bitstream, and a texture map bitstream into a single bitstream and then transmit the multiple bitstreams to a receiving device. Alternatively, the base mesh bitstream, the displacement vector bitstream, and the texture map bitstream may be encapsulated into a file / segment and transmitted to the receiving device.

[0289] According to embodiments, the bitstream multiplexed in the multiplexer may be transmitted over a network or stored in a digital storage medium. Here, the network may include a broadcasting network and / or a communication network, and the digital storage medium may include various storage media such as a USB, SD, CD, DVD, Blu-ray, HDD, or SSD.

[0290] The following describes in detail the process of encoding a displacement vector or displacement vector transform coefficient in a displacement vector encoder (11022).

[0291] That is, the displacement vector encoder (11022) can perform transformation and quantization on the displacement vector. In addition, the displacement vector encoder (11022) can encode the displacement vector or the quantized displacement vector transform coefficients through a 2D video codec-based encoding method, and / or a zero run length encoding method, and / or an arithmetic encoding method, etc. In this case, the displacement vector encoder (11022) can encode the displacement vector or the quantized displacement vector transform coefficients by selectively using only one of the 2D video codec-based encoding method, the zero run length encoding method, and the arithmetic encoding method, or by using one or more various combinations thereof.

[0292] FIGS. 22 to 26 are diagrams showing various examples of the displacement vector encoder (11022) of the present disclosure.

[0293] In the present disclosure, the displacement vector encoder (11022) may be referred to as a displacement vector transform coefficient encoder. Each component of FIGS. 22 to 26 corresponds to hardware, software, a processor, and / or a combination thereof. As shown in FIGS. 22 to 26, the execution order of each block may be changed, some blocks may be omitted, and some blocks may be newly added.

[0294] Fig. 22 is a block diagram showing an example of a displacement vector encoder that encodes a displacement vector or a quantized displacement vector transform coefficient according to the present disclosure based on a 2D video codec. The displacement vector encoder (11022) of Fig. 22 may include a displacement vector transform unit, a displacement vector transform coefficient quantization unit, a displacement vector transform coefficient packing unit, and a displacement vector transform coefficient image / video encoding unit.

[0295] Fig. 23 is a block diagram showing an example of a displacement vector encoder that encodes a displacement vector or a quantized displacement vector transform coefficient based on a zero run length according to the present disclosure. The displacement vector encoder (11022) of Fig. 23 may include a displacement vector transform unit, a displacement vector transform coefficient quantization unit, a restored displacement vector transform coefficient level buffer, a displacement vector transform coefficient level prediction unit, and a displacement vector transform coefficient zero run length encoding unit.

[0296] Fig. 24 is a block diagram illustrating an example of a displacement vector encoder that arithmetic encodes a displacement vector or a quantized displacement vector transform coefficient according to the present disclosure. The displacement vector encoder (11022) of Fig. 24 may include a displacement vector transform unit, a displacement vector transform coefficient quantization unit, a restored displacement vector transform coefficient level buffer, a displacement vector transform coefficient level prediction unit, and a displacement vector transform coefficient arithmetic encoding unit.

[0297] Fig. 25 is a block diagram showing another example of a displacement vector encoder that encodes a displacement vector or a quantized displacement vector transform coefficient based on a zero run length according to the present disclosure. The displacement vector encoder (11022) of Fig. 25 may include a displacement vector transform unit, a restored displacement vector transform coefficient buffer, a displacement vector transform coefficient prediction unit, a displacement vector transform coefficient quantization unit, and a displacement vector transform coefficient zero run length encoding unit.

[0298] Fig. 26 is a block diagram illustrating another example of a displacement vector encoder that arithmetic encodes a displacement vector or a quantized displacement vector transform coefficient according to the present disclosure. The displacement vector encoder (11022) of Fig. 26 may include a displacement vector transform unit, a restored displacement vector transform coefficient buffer, a displacement vector transform coefficient prediction unit, a displacement vector transform coefficient quantization unit, and a displacement vector transform coefficient arithmetic encoding unit.

[0299] According to embodiments, the displacement vector encoder (11022) may perform displacement vector encoding through a 2D video encoder such as H.264, HEVC, VVC, etc. as in FIG. 22, or may perform displacement vector encoding through a zero run length encoder as in FIG. 23 or FIG. 25, or may perform displacement vector encoding through an arithmetic encoder as in FIG. 24 or FIG. 26.

[0300] According to embodiments, the displacement vector encoding method may be determined as a specific encoding method by an agreement between the encoder / decoder, or the encoding method determined by the encoder may be signaled as a flag or index (dispEncType) and transmitted to the receiving device.

[0301] In the present disclosure, the displacement vector encoding method may be various, and according to an embodiment, one of {video codec-based encoding method, zero run length encoding method}, {video codec-based encoding method, zero run length encoding method}, {video codec-based encoding method, arithmetic encoding method}, video codec-based encoding method, zero run length encoding method, and arithmetic encoding method may be determined through the dispEncType flag or index.

[0302] According to embodiments, a displacement vector encoding method may be determined according to a profile defined in an encoder / decoder, and an index (profileToolsetIdx) indicating profile information may be signaled and transmitted to a receiver, and a displacement vector decoding method may be determined according to profileToolsetIdx in a decoder of the receiver.

[0303] In FIGS. 22 to 26, the displacement vector transformation unit can perform transformation on the displacement vector of the (x, y, z) or (n, t, bt) coordinate system. Here, the transformation may be applied, for example, lifting transformation, wavelet transformation, etc., according to embodiments. In the (n, t, bt) coordinate system, n means normal, t means tangential, and bt means bi-tangential. For example, when lifting transformation is performed, the vertex R of the kth subdivision level k R as a predictor when performing prediction t(t <k 또는 t<=k)의 세분화 정점 변위 벡터를 통해 k번째 세분화 레벨의 변위 벡터 예측을 수행할 수 있다. 실시예들에 따라 변위 벡터의 예측 수행 시 현재 정점보다 세분화 레벨이 낮은 정점 중 연결정보를 기반으로 가까운 n개의 점을 평균 또는 거리 기반 가중평균예측을 수행할 수 있다. 실시예들에 따라 메쉬 세분화 단계에서 현재 정점을 생성하기 위해 사용한 n개의 정점의 변위 벡터를 기반으로 예측을 수행할 수 있다. 본 개시는 모두 인접 정점의 정보를 활용해 현재 정점의 값을 예측하고 보정하는 리프팅 변환 기법을 사용하며, 예측 가중치를 적용하는 방식이 사용될 수 있다.

[0304] And, when a lifting transformation is performed, a process of updating the displacement vector of the vertex used in the prediction can be performed through the residual signal generated by the prediction.

[0305] Taking Fig. 25 or Fig. 26 as an example, the restoration displacement vector transformation coefficient is stored in the restoration displacement vector transformation coefficient buffer according to the reference structure, and the displacement vector transformation coefficient prediction unit can perform prediction through the following mathematical expression 2 by using the restoration displacement vector transformation coefficient (refDispCoeff) of the reference mesh mapped to the current mesh vertex stored in the restoration displacement vector transformation coefficient buffer as a predictor of the current displacement vector transformation coefficient.

[0306] [Equation 2]

[0307] for(size t v = 0; v <N; v++){

[0308] for(size t v = 0; d <dim; d++){

[0309] dispCore[v][d] = curDispCoeff{v][d] - refDispCoeff[v][d]

[0310] }

[0311] }

[0312] And, the displacement vector transform coefficient quantization unit can perform quantization on the displacement vector value transformed by the displacement vector transform unit, i.e., the displacement vector or the displacement vector transform coefficient. According to embodiments, the displacement vector transform coefficient quantization unit can perform quantization on the differential displacement vector transform coefficient (dispCoeff) obtained by subtracting the predicted displacement vector transform coefficient (refDispCoeff) from the current displacement vector transform coefficient (curDispCodff).

[0313] Fig. 27 is a flowchart showing an example of a process for converting a displacement vector in a displacement vector conversion unit according to embodiments.

[0314] According to embodiments, a displacement vector in the (x,y,z) or (n,t,bt) coordinate system can be transformed through a displacement vector transformation unit.

[0315] According to embodiments, when coordinate system transformation into the (n, t, bt) coordinate system is performed in the displacement vector coordinate system transformation unit (11021), a 1D scalar displacement vector of the normal (n) component may be applied as an input to the displacement vector transformation unit of the displacement vector encoder (11022), and transformation, quantization, and encoding may be performed on the displacement value of the normal component.

[0316] At this time, the transformation may be performed by lifting transformation, wavelet transformation, etc. according to embodiments. If lifting transformation is performed, transformation of the displacement vector may be performed through the embodiment of FIG. 27.

[0317] The present disclosure can determine the number of lifting transformations using the number of mesh subdivision levels (lodCount). In the present disclosure, the lifting transformation process can be performed for each mesh subdivision level. Furthermore, a lifting transformation prediction unit and a lifting transformation update unit can be performed during the lifting transformation process.

[0318] In Fig. 27, the displacement vector transformation unit can perform lifting transformation prediction and lifting transformation update for each subdivision level.

[0319] In Fig. 27, the lifting transformation prediction part is the vertex R of the kth subdivision level. k When performing displacement vector prediction, t(t <k 또는 t≤k)번째 세분화 레벨의 정점 R t Displacement vector prediction of the kth subdivision level can be performed using the displacement vector as a predictor.

[0320] According to embodiments, when performing prediction of a displacement vector, the lifting transformation prediction unit may perform an average or distance-based weighted average prediction of n points near the current vertex based on connection information among vertices having a lower level of detail than the current vertex.

[0321] According to embodiments, the lifting transformation prediction unit can perform prediction based on displacement vectors of n vertices used to generate the current vertex in the mesh refinement step.

[0322] According to embodiments, the lifting transformation prediction unit can generate a residual signal through the difference between the displacement vector of the subdivision level and the predicted displacement vector.

[0323] In Fig. 27, the lifting transformation update unit performs a process of updating the displacement vector of the vertex used for prediction through the residual signal generated by the lifting transformation prediction unit.

[0324] According to embodiments, the lifting transformation update unit may perform an adaptive update using an adaptive weight (LODWeight) derived through a granularity level (currentLOD) at which the current transformation process is performed between update processes of the displacement vector, and may signal an update method determined by the encoder as a flag or index (vdmc_transform_adapdtive_update_flag).

[0325] In FIGS. 22 to 26, the displacement vector transform coefficient quantization unit performs quantization on the transform coefficients transformed through the displacement vector transform unit. According to embodiments, the transform coefficients may be quantized through different quantization parameters for each axis, and the quantization parameter or scaling parameter may be derived by an agreement between the encoder / decoder to determine the quantization rate for each LoD level.

[0326] Meanwhile, the transmitting device of FIG. 21 may further include an atlas encoder (not shown). According to embodiments, the atlas encoder may encode atlas information (or atlas data) into an atlas bitstream and transmit it to a receiving device. The atlas may be information required for a mesh reconstruction process and may refer to information such as tiles and patches. In addition, the atlas data may refer to data required for processes such as mesh decoding and mesh restoration and may include a segmentation method, a transformation method, a quantization method, the position and size of a patch within an atlas frame, and the like. Such atlas information may be encoded through Exp-Golomb coding of the atlas encoder, etc.

[0327] According to embodiments, signaling information in a transmitting device (or an encoder of the transmitting device) may be generated by a metadata processing unit (not shown, may be referred to as a metadata generator, etc.) and provided to corresponding blocks in the transmitting device and / or a receiving device (or a decoder of the receiving device), and a metadata parser (not shown) of the receiving device may parse the received signaling information and provide it to the corresponding blocks. According to embodiments, each block of the receiving device may perform each operation based on the parsed signaling information. In the present disclosure, the signaling information may further include meshlet-related information of a submesh. According to embodiments, the meshlet-related information of a submesh is carried through a basemesh submesh unit, and a detailed description will be described later using FIGS. 33 and 34.

[0328] Fig. 28 illustrates a receiving device according to embodiments. In the present disclosure, the receiving device of Fig. 28 may be referred to as a mesh data receiving device or decoder or decoder of a receiving device or a V-Mesh decoder or a dynamic mesh decoder.

[0329] FIG. 28 corresponds to the receiving device (110) or mesh video decoder (113) of FIG. 1, the decoder of FIG. 11 or FIG. 12, the receiving device of FIG. 14, and / or the receiving decoding device corresponding thereto. Therefore, parts not described in FIG. 28 will refer to the description of the receiving device (110) or mesh video decoder (113) of FIG. 1, the decoder of FIG. 11 or FIG. 12, and the receiving device of FIG. 14. The elements of the receiving device illustrated in FIG. 28 may be implemented by hardware, software, a processor connected to a memory, and / or a combination thereof. That is, the elements of the receiving device of FIG. 28 may be implemented by hardware, software, firmware, or a combination thereof, including one or more processors or integrated circuits configured to be able to communicate with one or more memories, although not illustrated in the drawing. One or more processors may perform at least one of the operations and / or functions of the elements of the receiving device of FIG. 28 described above. Furthermore, one or more processors may operate or execute a set of software programs and / or instructions for performing the operations and / or functions of the elements of the receiving device of FIG. 28. The execution order of each block in FIG. 28 may be changed, some blocks may be omitted, and some blocks may be newly added.

[0330] FIG. 28 may largely include a base mesh decoding unit, a displacement information decoding unit, and a texture map decoding unit. According to embodiments, the base mesh decoding unit may include a switching unit (15011), a motion vector decoder (15012), a static mesh decoder (15013), a base mesh restoration unit (15014), a mesh refinement unit (15015), and a mesh restoration unit (15016). According to embodiments, the displacement information decoding unit may include a displacement vector decoder (15017) and a displacement vector coordinate system inverse transformation unit (15020). In addition, the receiving device of FIG. 28 may further include an atlas decoder (not shown).

[0331] According to embodiments, a bitstream of mesh data received by a receiver (not shown) may be demultiplexed into a base mesh bitstream, a displacement vector bitstream, a texture map bitstream, and / or an atlas bitstream after file / segment decapsulation in a demultiplexer (not shown). If the current mesh has inter-encoding applied, the base mesh bitstream may be a motion vector bitstream.

[0332] According to embodiments, an atlas bitstream is provided to an atlas decoder. The atlas decoder can decode the atlas bitstream to restore atlas information. The restored atlas can be used in a mesh decoding process. According to embodiments, the process in which the atlas information is used may include a segmentation process, a displacement vector restoration process, etc., and may include information such as tiles and patches.

[0333] According to embodiments, the atlas bitstream may be decoded through an atlas decoder's Exp-Golomb coding process, etc. In this case, the atlas may be information required for a mesh reconstruction process, and may refer to information such as tiles and patches. In addition, the atlas data may refer to data required for processes such as mesh decoding and mesh reconstruction, and may include a segmentation method, a transformation method, a quantization method, the location and size of patches within an atlas frame, etc.

[0334] According to embodiments, the base mesh bitstream is provided to a motion vector decoder (15012) via a switching unit (15011) or to a static mesh decoder (15013).

[0335] For example, if the current mesh has inter encoding applied, the base mesh bitstream, i.e., the motion vector bitstream, is received, demultiplexed, and then output to the motion vector decoder (15012) through the switching unit (15011). As another example, if the current mesh has intra encoding applied, the base mesh bitstream is received, demultiplexed, and then output to the static mesh decoder (15013) through the switching unit (15011). Here, the motion vector decoder (15012) may be referred to as a motion decoder.

[0336] According to embodiments, the motion vector decoder (15012) can perform decoding on a motion vector bitstream at the vertex level, subgroup level, or meshlet level.

[0337] According to embodiments, the motion vector decoder (15012) can reconstruct a final motion vector by adding a differential motion vector (i.e., a residual motion vector) decoded from a bitstream using a previously decoded motion vector as a predictor. That is, the motion vector decoder (15012) decodes a differential motion vector (or a residual motion vector) in units of vertices or subgroups (or subblocks) or meshlets through a motion vector bitstream, and performs prediction based on connection information using a previously decoded motion vector as a predictor to decode the motion vector by adding it to the residual motion vector.

[0338] According to embodiments, the static mesh decoder (15013) can decode the base mesh bitstream to restore connection information, vertex geometry information, texture coordinates (i.e., attribute geometry information), normal information, etc. of the base mesh. According to embodiments, the static mesh decoder (15013) can perform decoding on the base mesh bitstream in meshlet units.

[0339] That is, in the present disclosure, the motion vector bitstream or the basemesh bitstream can be decoded in meshlet units based on meshlet-related information of the submesh. In the present disclosure, the meshlet-related information of the submesh can be carried through the basemesh submesh unit, and can include information on the number of meshlets divided from the corresponding submesh, information on the coding type of the corresponding meshlet, index information of the reference meshlet, etc. Details on the meshlet-related information of the submesh will be described later with reference to FIGS. 33 and 34.

[0340] According to embodiments, the base mesh restoration unit (15014) may restore the current base mesh based on the decoded motion vector or the decoded base mesh. For example, if the current mesh has inter-encoding applied, the base mesh restoration unit (15014) may add the decoded (or restored) motion vector to the reference base mesh and then perform inverse quantization to generate a restored base mesh (i.e., the current base mesh). As another example, if the current mesh has intra-encoding applied, the base mesh restoration unit (15014) may perform inverse quantization on the decoded (or restored) base mesh through the static mesh decoder (15012) to generate a restored base mesh (i.e., the current base mesh). According to embodiments, the inverse quantization unit may be omitted.

[0341] According to embodiments, the unit for decoding (or restoring) the base mesh in the base mesh restoration unit (15014) may be a meshlet unit. Then, by performing the reverse process of meshlet division and sub-mesh division performed in the base mesh division unit (12011) of the transmitting device based on signaling information on the base meshes restored in meshlet units, the base meshes can be restored into base meshes similar to or identical to the base mesh before being divided into sub-meshes and meshlets.

[0342] Additionally, when decoding multiple meshlets, a filtering process may be performed between meshlet boundaries. Depending on the embodiment, if the meshlets are subdivided with the same number of subdivisions, the filtering process may select one of the corresponding vertices between the boundaries or the midpoint. If the number of subdivisions is not the same, additional vertices may be created on the boundary of the meshlet with the smaller number of subdivisions, or some vertices may be removed on the boundary of the meshlet with the larger number of subdivisions.

[0343] And, the restored base mesh is output to the mesh subdivision unit (15015).

[0344] According to embodiments, the mesh subdivision unit (15015) can perform subdivision on the restored base mesh to generate additional vertices. The present disclosure can implicitly derive and generate geometry information connection information, texture coordinate connection information, and texture coordinates according to the subdivision method.

[0345] According to embodiments, the mesh refinement unit (15015) can perform refinement through methods such as mid-edge, Loop, and Catmul&Clark.

[0346] According to embodiments, mesh refinement in the mesh refinement unit (15015) may be performed n times by user parameters or a promise of the encoder / decoder. According to embodiments, vertices of the base mesh are vertices of level 0 (R0), vertices newly generated by performing refinement once are vertices of level 1 (R1), … vertices newly generated by performing refinement n times are vertices of level n (R n ) can be defined as the vertices of the 0th level (R0), level 1 as the 1st level (R1), … level n as the nth level (R n ) can be called.

[0347] According to embodiments, LoD0, LoD1, … LoDn can be defined as in the following mathematical expression 3.

[0348] [Equation 3]

[0349] LoD0 = R0

[0350] LoD1 = R0+ R1= LoD0 + R1

[0351] …

[0352] LoDn = R0+ R1+, … + R n = LoDn-1 + R n

[0353] That is, the base mesh includes vertices for LoD0. And, the first subdivision mesh generated by subdividing the base mesh once includes vertices for LoD1. That is, LoD1 includes vertices of the base mesh (i.e., R0 vertices) and vertices of a newly generated level 1 by subdividing the base mesh (i.e., R1 vertices). In addition, the second subdivision mesh generated by subdividing the first subdivision mesh again includes vertices for LoD2. That is, LoD2 includes vertices of the base mesh (i.e., R0 vertices), vertices of a newly generated level 1 by subdividing the base mesh (i.e., R1 vertices), and vertices of a newly generated level 2 by subdividing the first subdivision mesh (i.e., R2 vertices).

[0354] According to embodiments, the displacement vector decoder (15017) may perform video codec-based decoding on the demultiplexed displacement vector bitstream as a video bitstream, or perform zero run-length decoding, or perform arithmetic decoding. In the present disclosure, the displacement vector decoder may be used interchangeably with the displacement vector transform decoder.

[0355] According to embodiments, the displacement vector decoder (15017) can restore the displacement vector by decoding the displacement vector in a reverse process of the displacement vector encoding method of the transmitting side.

[0356] According to embodiments, the displacement vector coordinate system inversion unit (15020) can perform a process of inverting the displacement vector decoded by the displacement vector decoder (15017) into a Cartesian (or canonical) coordinate system (x, y, z) if the displacement vector is a value of a local coordinate system (n, t, bt). The output of the displacement vector coordinate system inversion unit (15020) is provided to the mesh restoration unit (15016).

[0357] That is, in the encoder of the transmitting device, the vertex displacement vector calculated in the (x,y,z) space can be converted to a (normal, tangential, bi-tangential) coordinate system (or local coordinate system) based on the normal vector of each vertex. At this time, the normal vector can be calculated for each subdivided vertex based on the geometric information and connection information of the surrounding vertices.

[0358] Fig. 29 is a detailed block diagram showing an example of a displacement vector coordinate system inverse transformation unit (15020) according to embodiments.

[0359] Fig. 30 is a detailed block diagram showing another example of a displacement vector coordinate system inverse transformation unit (15020) according to embodiments.

[0360] More specifically, the displacement vector coordinate system inverse transformation unit (15020) parses the coordinate system transformation flag (applyLocalCoord or asps_vmc_ext_displacement_coordinate_system) included in the signaling information in units of sequences, GoFs (group of frames), frames, or sub-mesh, and if its value is 1, it can perform inverse transformation of the inverse quantized (or inversely transformed) restored displacement vector from the local coordinate system (n, t, b) to the canonical coordinate system (x, y, z).

[0361] In addition, a normal vector per vertex is calculated based on the restoration vertex position information of the restoration base mesh, and a normal value of a newly created vertex can be assigned by interpolating the vertex normal vector of the calculated restoration base mesh for the vertex additionally created through the subdivision process (see Fig. 29).

[0362] At this time, in the case of interpolation, interpolation can be performed by averaging or distance-based weighting the normal information of the base mesh used for subdivision. Alternatively, the normal information of the base mesh can be used as is for subdivided vertices on the same plane.

[0363] According to embodiments, after performing subdivision on the restored base mesh, normal vectors can be calculated for vertices generated through the mesh subdivision unit (15015) and vertices of the base mesh (see FIG. 30).

[0364] And, through the calculated normal vector per vertex, the tangential and bi-tangential vectors orthogonal to the normal vector can be calculated and the displacement vector coordinate system inverse transformation can be performed. The following mathematical expression 4 disp n (0), disp n (1), disp n (2) refers to the results of normal, tangential, and bitangential components obtained by performing inverse transformation and inverse quantization.

[0365] [Equation 4]

[0366]

[0367] In some embodiments, coordinate system inversion can always be performed without flag transmission.

[0368] According to embodiments, the mesh restoration unit (15016) restores the mesh based on the mesh refined in the mesh refinement unit (15015) and the restored displacement vector output from the displacement vector coordinate system inverse transformation unit (15020).

[0369] According to embodiments, the received and demultiplexed texture map bitstream is input to a texture map decoder (15021). According to embodiments, the texture map decoder (15021) can decode the texture map through a 2D scalable decoder. That is, the texture map decoder (15021) can restore the texture map by applying 2D scalable decoding to the texture map. In this way, the texture map decoder (15021) receives the texture map bitstream as input and performs a process of decoding the texture map. At this time, the type of texture map decoder may include a video decoder, a zero run length decoder, an arithmetic decoder, etc. According to embodiments, the texture map decoder (15021) can perform color space conversion of the texture map.

[0370] When the base mesh bitstream, displacement vector bitstream, texture map bitstream, and / or atlas bitstream encoded by the dynamic mesh encoder of the transmitting device are transmitted in this way, the decoder of the receiving device restores the mesh by decoding each bitstream. First, the base mesh is decoded by a motion vector or static mesh decoder depending on whether it is an inter or intra frame, and geometry information is restored together with the decoded displacement vector information through subdivision. At this time, the motion vector decoding process of the base mesh or the static mesh decoding process can be performed in units of meshlets.

[0371] Fig. 31 is a detailed block diagram showing an example of a displacement vector decoder according to embodiments. The displacement vector decoder according to embodiments may include a displacement vector transform coefficient decoding unit, a displacement vector inverse quantization unit, and a displacement vector inverse transform unit. Each component of Fig. 31 corresponds to hardware, software, a processor, and / or a combination thereof. The execution order of each block in Fig. 31 may be changed, some blocks may be omitted, and some blocks may be newly added.

[0372] According to embodiments, the displacement vector transform coefficient decoding unit may perform displacement vector decoding through a 2D video decoder such as H.264, HEVC, VVC, etc., or may perform displacement vector decoding through a zero run length decoder or an arithmetic decoder, etc.

[0373] According to embodiments, in the displacement vector transform coefficient decoding unit, the displacement vector transform coefficient decoding method may be determined by a specific decoding method through an agreement between the encoder and the decoder, or may be determined by receiving an encoding method determined by the encoder as a flag or index (dispEncType).

[0374] In the present disclosure, the displacement vector transform coefficient decoding method may be various, and according to embodiments, one of {video codec-based decoding method, zero run length decoding method}, {video codec-based decoding method, zero run length decoding method}, {video codec-based decoding method, arithmetic decoding method}, video codec-based decoding method, zero run length decoding method, and arithmetic decoding method may be determined through the dispEncType flag or index.

[0375] According to embodiments, a displacement vector transformation coefficient decoding method can be determined according to a profile defined in an encoder / decoder, and an index (profileToolsetIdx) indicating profile information can be transmitted so that the decoder can determine a displacement vector decoding method according to profileToolsetIdx.

[0376] According to embodiments, a displacement vector inverse quantization unit may perform inverse quantization on a displacement vector. At this time, quantization of the transform coefficients may be performed through different quantization parameters for each axis, and a quantization rate may be determined for each LoD level by deriving a quantization parameter or a scaling parameter through an agreement between the encoder and the decoder.

[0377] According to embodiments, the displacement vector inverse transform unit performs an inverse transform of the transform performed in the encoder of the transmitting device on the inverse quantized displacement vector coefficients to output displacement vectors. According to embodiments, a lifting inverse transform, a wavelet inverse transform, etc. may be performed. If a lifting inverse transform is performed in the displacement vector inverse transform unit, a process of updating the displacement vector of a vertex used for prediction in the encoder may be performed through the parsed residual signal. That is, the displacement vector inverse transform unit performs an inverse transform of the inverse quantized displacement vector coefficients. At this time, the inverse transform may be applied to a lifting inverse transform, a wavelet inverse transform, etc. according to embodiments.

[0378] Fig. 32 is a flowchart showing an example of a process of inversely transforming a displacement vector in a displacement vector inverse transform unit according to embodiments. That is, when a lifting inverse transform is performed in the displacement vector inverse transform unit, the inverse transform of a displacement vector can be performed through the embodiments of Fig. 32. At this time, the number of lifting inverse transforms can be determined using the number of mesh subdivision levels (lodCount). In addition, the lifting inverse transform process can be performed in units of mesh subdivision levels. In addition, a lifting inverse transform prediction unit and a lifting inverse transform update unit can be performed during the lifting inverse transform process.

[0379] Figure 32 is an example of performing displacement vector inverse transformation for each LoD, and may include a lifting inverse transformation update unit and a lifting inverse transformation prediction unit.

[0380] In Fig. 32, the lifting inverse transformation prediction unit can perform inverse transformation prediction on a displacement vector for which lifting inverse transformation update has been performed in the lifting inverse transformation update unit.

[0381] According to the embodiments, the lifting inverse transform prediction unit performs the lifting inverse transform on the vertex R of the kth subdivision level. k R as a predictor when performing prediction t (t <k 또는 t<=k)의 세분화 정점 변위 벡터를 통해 k번째 세분화 레벨의 변위벡터 예측을 수행할 수 있다.

[0382] According to embodiments, when performing prediction of a displacement vector, an average or distance-based weighted average prediction can be performed on n points near the current vertex based on connection information among vertices with a lower level of detail than the current vertex.

[0383] According to embodiments, prediction can be performed based on the displacement vectors of n vertices used to generate the current vertex in the mesh refinement step.

[0384] Additionally, when the lifting inverse transformation is performed, the displacement vector of the vertex of the subdivision level can be restored through the sum between the predicted displacement vector and the parsed residual signal.

[0385] In Fig. 32, the lifting inverse transformation update unit performs a process of updating the displacement vector of the vertex used for prediction through the parsed residual signal.

[0386] According to embodiments, the lifting inverse transform update unit can perform an update using a fixed weight when the parsed vdmc_transform_adapdtive_update_flag is 0 during the update process of the displacement vector.

[0387] According to embodiments, the lifting inverse transform update unit can perform an adaptive update using an adaptive weight (LODWeight) derived through a granularity level (currentLOD) at which the current inverse transform process is performed when the parsed vdmc_transform_adapdtive_update_flag is 1 during the update process of the displacement vector.

[0388] According to embodiments, signaling information in a transmitting device (or an encoder of the transmitting device) may be generated by a metadata processing unit (not shown, may be referred to as a metadata generator, etc.) and provided to corresponding blocks in the transmitting device and / or a receiving device (or a decoder of the receiving device), and a metadata parser (not shown) of the receiving device may parse the received signaling information and provide it to the corresponding blocks. According to embodiments, each block of the receiving device may perform each operation based on the parsed signaling information. In the present disclosure, the signaling information may further include meshlet-related information of a submesh. According to embodiments, the meshlet-related information of a submesh is carried through a basemesh submesh unit, and a detailed description will be described later using FIGS. 33 and 34.

[0389] In the present disclosure, a mesh data encoding method / device (such as a transmitting device (100) of FIG. 1, a mesh video encoder (102) of FIG. 1, an encoder of FIG. 2, a preprocessor of FIG. 3, a preprocessor of FIG. 5, an encoder of FIG. 6 and FIG. 7, an encoder of FIG. 13, an encoder of FIGS. 15 to 21, an encoding method of FIG. 35) can encode mesh data and generate and transmit a bitstream including encoded mesh data and parameter information related to the mesh data. In addition, a mesh data decoding method / device (such as a receiving device (110) of FIG. 1, a mesh video decoder (113) of FIGS. 11 and 12, a decoder of FIG. 14, a decoder of FIG. 28, a decoding method of FIG. 36) according to embodiments can receive a bitstream and decode mesh data based on parameter information included in the bitstream.

[0390] A bitstream according to embodiments may include basemesh submesh unit syntax. In the present disclosure, one embodiment is that meshlet-related information (e.g., meshlet_information()) of a submesh is transmitted in the basemesh submesh unit syntax. In the present disclosure, meshlet-related information of a submesh may be referred to as meshlet information.

[0391] Fig. 33 is a syntax structure showing an example of a basemesh submesh unit (bmesh_submesh_unit(submeshID, unitSize)) of the present disclosure. In Fig. 33, submeshID is an identifier for identifying a submesh carried by the basemesh submesh unit. unitSize indicates the size of the corresponding basemesh submesh unit.

[0392] In Fig. 33, the basemesh submesh unit (bmesh_submesh_unit(submeshID, unitSize)) may include bm_intra_submesh_unit(submeshID, unitSize), bm_inter_submesh_unit(submeshID, unitSize), or bm_skip_submesh_unit( ) depending on the bmsh_type value. The bmsh_type is signaled in bmesh_submesh_header( ) and indicates the coding type of the current submesh.

[0393] More specifically, the basemesh submesh unit (bmesh_submesh_unit(submeshID, unitSize)) can contain a bm_intra_submesh_unit(submeshID, unitSize) that carries inter-related information if bmsh_type indicates I_SUBMESH. If bmsh_type indicates P_SUBMESH, it can contain a bm_inter_submesh_unit(submeshID, unitSize) that carries intra-related information. If bmsh_type indicates SKIP_SUBMESH, it can contain a bm_skip_submesh_unit( ) that carries skip-related information.

[0394] According to embodiments, the basemesh submesh unit (bmesh_submesh_unit(submeshID, unitSize)) may further include meshlet-related information of the submesh (meshlet_information(submeshID)).

[0395] Figure 34 is a syntax structure showing an example of meshlet related information (meshlet_information(submeshID)) of a sub-mesh of the present disclosure.

[0396] In Fig. 34, mi_meshlet_count_minus1 can represent the number of meshlets of the submesh identified by submeshID.

[0397] mi_meshlet_type[i] can indicate the type of the ith meshlet. That is, it can indicate the coding type of the current meshlet. For example, if the value of mi_meshlet_type[i] is 0, it can indicate that the ith meshlet is an intra type that is encoded / decoded only using the current frame (or meshlet), if it is 1, it can indicate that the ith meshlet is an inter type that is encoded / decoded using a reference frame (or reference meshlet), and if it is 2, it can indicate that the ith meshlet is a SKIP type that does not transmit reference information when using a reference frame (or reference meshlet).

[0398] mi_reference_index[i] is the reference meshlet index of the i-th meshlet, and can be signaled and transmitted to the receiving device when mi_meshlet_type[i] is INTER, SKIP, etc.

[0399] Figure 35 is a flowchart illustrating an example of an encoding method according to embodiments. The encoding method according to embodiments may include a step of encoding a base mesh of mesh data (S31011), a step of encoding a displacement of mesh data (S31012), and a step of encoding an attribute of mesh data (S31013).

[0400] The step (S31011) of encoding the base mesh of the above mesh data can divide the input base mesh into one or more sub-meshes through the base mesh division unit (12011), and can also divide one or more sub-meshes into one or more meshlets.

[0401] In the present disclosure, the method of dividing a sub-mesh into meshlets may perform the division by considering the similarity between the current sub-mesh and the reference sub-mesh, may perform the division by considering the change in the motion vector, and may also perform the division by various division algorithms.

[0402] In one embodiment, when performing segmentation by considering the similarity between the current sub-mesh and the reference sub-mesh, the matching area between the current sub-mesh and the reference sub-mesh can be searched and segmented into a matching area (or an area with high similarity) and a non-matching area (or an area with no similarity). For example, the meshlet type (or meshlet coding / decoding type) of the meshlet of the matching area can be determined as an inter type, and the meshlet type of the meshlet of the non-matching area can be determined as an intra type.

[0403] In another embodiment, when segmenting considering the change in motion vector, the sequence can be segmented into an area with a large motion change and an area with a small motion change. In the present disclosure, the motion change can estimate the motion vector through motion estimation between the current base mesh and the reference base mesh. For example, the meshlet type of the meshlet of the area with a small motion change can be determined as the inter type, and the meshlet type of the meshlet of the area with a large motion change can be determined as the intra type.

[0404] In the present disclosure, details of dividing a sub-mesh into one or more meshlets and details of determining a meshlet type by comparing meshlet(s) divided from a sub-mesh of a current base mesh with meshlet(s) divided from a sub-mesh of a reference base mesh are described in detail in FIGS. 15 to 20, so for parts not described herein, refer to the description of FIGS. 15 to 20.

[0405] The step (S31011) of encoding the base mesh of the above mesh data may perform motion vector encoding or static mesh encoding on the base mesh in meshlet units. For example, when intra encoding is performed on the corresponding meshlet, the base mesh may be compressed through a static mesh encoder (11016). In this case, encoding may be performed on connection information, vertex geometry information, vertex texture information, normal information, etc. of the base mesh. That is, vertex coordinates, vertex connection information, texture coordinates, texture connection information, etc. of the mesh may be encoded in the static mesh encoder (11016). As another example, when inter encoding is performed on the corresponding meshlet, the motion vector encoder (11015) may receive the current base mesh and the reference restored base mesh (or the restored quantized reference base mesh) as input, calculate a motion vector between the two meshes, and encode the value. Additionally, the motion vector encoder (11015) can perform prediction based on connection information using previously encoded / decoded motion vectors as predictors, and entropy encode a differential motion vector (also called a residual motion vector) obtained by subtracting the predicted motion vector from the current motion vector.

[0406] The step (S31012) of encoding the displacement of the above mesh data may perform video codec-based encoding on the displacement data or arithmetic codec-based encoding. In addition, the step (S31012) of encoding the displacement of the mesh data may convert the coordinate system of the displacement data from a three-dimensional Cartesian coordinate system to a local coordinate system before encoding the displacement data.

[0407] The step of encoding the attributes of the above mesh data (S31013) may perform encoding based on a video codec for the attribute data (or texture map).

[0408] The above encoding method may further include a step of transmitting a bitstream including an encoded basemesh, encoded displacement data, and encoded attribute data. The bitstream transmitted in the above step may be transmitted to a receiving device.

[0409] The encoding method of the present disclosure can be performed by an encoding device (encoder). The encoding device includes a memory and at least one processor connected to the memory, and the at least one processor can be configured to encode a base mesh of mesh data, encode a displacement of the mesh data, and encode an attribute of the mesh data.

[0410] Embodiments further include a computer-readable storage medium storing a bitstream generated by the method according to FIG. 35.

[0411] Embodiments further include a method comprising the steps of obtaining a bitstream for mesh data, the bitstream being generated based on the steps of encoding a basemesh of the mesh data, encoding a displacement of the mesh data, and encoding an attribute of the mesh data, and transmitting data including the bitstream.

[0412] Fig. 36 is a flowchart showing an example of a decoding method according to embodiments. The decoding method according to embodiments may include a step of decoding a base mesh within a bitstream (S32011), a step of decoding a displacement within a bitstream (S32012), and a step of decoding an attribute within a bitstream (S32013). The decoding step of Fig. 36 may further include a step of receiving a bitstream including a base mesh, displacement data, and attribute data, or a file in which a bitstream is encapsulated. The receiving step performs a decapsulation process to extract a bitstream when a file is received, and omit the decapsulation process when a bitstream is received.

[0413] The step (S32011) of decoding the base mesh in the bitstream may perform static mesh decoding or motion vector decoding on a meshlet basis based on meshlet-related information of the sub-mesh signaled to the base mesh sub-mesh unit, as shown in FIGS. 33 and 34. For example, if the current mesh has inter encoding applied, the previously decoded motion vector may be used as a predictor on a meshlet basis, and the final motion vector may be restored by adding it to the residual motion vector decoded from the base mesh sub-bitstream. The step (S32011) of decoding the base mesh in the bitstream may, if the current mesh has intra encoding applied, perform static mesh decoding of the base mesh sub-bitstream on a meshlet basis, thereby restoring connection information, vertex geometry information, texture coordinates, normal information, etc. of the base mesh.

[0414] The step (S32012) of decoding displacement in the above bitstream performs decoding on the displacement sub-bitstream based on the video codec if the displacement data is encoded based on a video codec, and performs decoding based on the arithmetic codec if the displacement data is encoded based on an arithmetic codec.

[0415] The step of decoding an attribute in the above bitstream (S32013) restores the attribute data by decoding the attribute sub-bitstream based on a video codec.

[0416] The base mesh, displacement data, and attribute data decoded in steps S32011-S32013 can be rendered after undergoing post-processing such as mesh restoration and reconstruction.

[0417] The decoding method of the present disclosure can be performed by a decoding device (decoder). The decoding device includes a memory and at least one processor connected to the memory, and the at least one processor can be configured to decode a basemesh within a bitstream, decode a displacement within the bitstream, and decode an attribute within the bitstream.

[0418] Currently, encoding / decoding of the base mesh performed in V-DMC is performed in sub-mesh units, but the sub-mesh is a division unit for independently performing encoding and decoding. In the case of the current dynamic mesh encoder / decoder, the encoding type of the base mesh is determined in sub-mesh units when encoding / decoding the base mesh. If a one-to-one correspondence is not established between the current sub-mesh and the reference sub-mesh, the base mesh type is determined as the intra type, and static mesh encoding is performed for the base mesh. This means that even if a one-to-one correspondence is not established for only some areas of the sub-mesh, the sub-mesh is always determined as the intra type, and static mesh encoding is performed, which generates a significant amount of bits.

[0419] Accordingly, in the present disclosure, even when a one-to-one correspondence between the current sub-mesh and the reference sub-mesh is not established as described above, the base mesh bit amount can be reduced by dividing the region similar to the reference sub-mesh and the region dissimilar to the current sub-mesh into multiple regions and performing encoding / decoding using different encoding / decoding types for each region.

[0420] Each of the parts, modules, or units described above may be software, processors, or hardware parts that execute sequential execution processes stored in memory (or storage units). Each of the steps described in the embodiments described above may be performed by processors, software, or hardware parts. Each of the modules / blocks / units described in the embodiments described above may operate as a processor, software, or hardware. In addition, the methods presented in the embodiments may be implemented as code. This code may be written on a processor-readable storage medium and thus may be read by a processor provided by an apparatus.

[0421] Furthermore, throughout the specification, when a part is said to "include" a component, this does not exclude other components, unless otherwise specifically stated, but rather implies the inclusion of other components. Furthermore, terms such as "part" described in the specification mean a unit that processes at least one function or operation, which may be implemented using hardware, software, or a combination of hardware and software.

[0422] For convenience of explanation, this specification has been described separately in each drawing. However, it is also possible to design new embodiments by combining the embodiments described in each drawing. Furthermore, designing a computer-readable recording medium containing a program for executing the previously described embodiments, as required by those skilled in the art, is also within the scope of the embodiments.

[0423] 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 each embodiment so that various modifications can be made.

[0424] 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 may be made by those skilled in the art to which the present disclosure pertains without departing from the spirit or scope of the embodiments claimed in the claims, and such modifications should not be understood individually from the technical idea or prospect of the embodiments.

[0425] 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. The components according to the embodiments may be implemented by separate chips. 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.

[0426] 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".

[0427] Various elements of the embodiments may be implemented by hardware, software, firmware, or a combination thereof. Various elements of the embodiments may be implemented on a single chip, such as a hardware circuit. In some embodiments, the embodiments may optionally be implemented on separate chips. In some embodiments, at least one of the elements of the embodiments may be implemented within one or more processors that include instructions for performing operations according to the embodiments.

[0428] Additionally, the operations according to the embodiments described in this document may be performed by a transceiver device including one or more memories and / or one or more processors according to the embodiments. One or more memories may store programs for processing / controlling the operations according to the embodiments, and one or more processors may control various operations described in this document. One or more processors 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 a processor or a memory.

[0429] Terms such as "first" and "second" may be used to describe various components of the embodiments. However, the various components according to the embodiments should not be interpreted in a limited manner 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 necessarily mean the same user input signals unless the context clearly indicates otherwise.

[0430] 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 the terms. The expression “comprises” or “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.

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

[0432] As described above, the embodiments may be applied, in whole or in part, to mesh data transmission and reception devices and systems. Those skilled in the art will appreciate that various modifications and variations may be made to the embodiments within the scope of the embodiments. The embodiments may include modifications and variations, and such modifications and variations 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 data within the bitstream; and A step of decoding attribute data within the bitstream; comprising: How to decode.

2. In paragraph 1, The above base mesh is composed of one or more sub-meshes, and each sub-mesh is composed of one or more regions. How to decode.

3. In paragraph 2, Each submesh is divided into one or more regions based on its similarity to a reference submesh, and each region has a matching region in the reference submesh or not. How to decode.

4. In the third paragraph, the step of decoding the base mesh Performing inter-decoding or intra-decoding on the base mesh in units of the above regions based on the signaling information included in the above bitstream. How to decode.

5. In paragraph 4, The signaling information includes at least one of coding type information of each area constituting the current submesh or index information of each area. How to decode.

6. Memory; and At least one processor connected to the memory; At least one processor of the above: Decode the basemesh within the bitstream; Decoding displacement data within the bitstream; and configured to decode attribute data within the above bitstream; Decoding device.

7. Step of encoding the base mesh of mesh data; A step of encoding displacement data of the above mesh data; and A step of encoding attribute data of the above mesh data; comprising; Encoding method.

8. In the 7th paragraph, the step of encoding the base mesh comprises: A step of dividing the base mesh into one or more sub-meshes and dividing each sub-mesh into one or more regions, Encoding method.

9. In the 8th paragraph, the step of dividing into the above areas is, Divide the current submesh into one or more regions based on the similarity between the current submesh and the reference submesh, and each region may or may not have a matching region in the reference submesh. Encoding method.

10. In the 9th paragraph, the step of encoding the base mesh Inter-encoding is performed for areas where a matching area exists in the above reference submesh, and intra-encoding is performed for areas where a matching area does not exist. Encoding method.

11. In the 8th paragraph, the step of dividing into the above areas is, The current submesh is divided into one or more regions based on the change in the motion vector, and the change in the motion vector is obtained by estimating the motion vector through motion estimation between the current base mesh and the reference base mesh. Encoding method.

12. In paragraph 7, Further comprising a step of generating signaling information, The signaling information includes at least one of coding type information of each area constituting the current submesh or index information of each area. Encoding method.

13. Memory; and At least one processor connected to the memory; At least one processor of the above: Encode the base mesh of mesh data; Encode displacement data of the above mesh data; and Encoding attribute data 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 7.

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 displacement data of the mesh data; and encoding attribute data of the mesh data; and A method comprising the step of transmitting data including the bitstream.

Images