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

Abstract

A mesh data decoding method according to embodiments may comprise the steps of: receiving a bitstream including mesh data; and decoding the mesh data. A mesh data encoding method according to embodiments may comprise the steps of: encoding mesh data; and transmitting a bitstream including the mesh data.

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 Point Cloud content to provide users with various services such as Virtual Reality (VR), Augmented Reality (AR), Mixed Reality (MR), and autonomous driving services.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0026] Figure 15 shows a bitstream structure according to embodiments.

[0027] Figure 16 shows a V-DMC (Video-based dynamic mesh coding) extension of the V3C (Visual volumetric video-based coding) parameter set according to embodiments.

[0028] Figure 17 illustrates scalable geometry video information according to embodiments.

[0029] Figure 18 shows the maximum value of the LoD (Level of Detail) number according to embodiments.

[0030] Figure 19 illustrates scalable geometry video information according to embodiments.

[0031] Figure 20 shows the number of packed LoDs according to embodiments.

[0032] Figure 21 shows an extension of the V3C parameter set according to embodiments.

[0033] Figure 22 shows an atlas sequence parameter set according to embodiments.

[0034] Figure 23 illustrates a dynamic mesh content receiver according to embodiments.

[0035] Figure 24 shows a mesh data encoding method according to embodiments.

[0036] Figure 25 shows a mesh data decryption method according to embodiments.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0068] The encoding process of Fig. 1 is as follows.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0133]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0166] A point cloud data transmission device and method according to embodiments can encode mesh data and transmit a bitstream including the encoded mesh data. A point cloud data reception device and method according to embodiments can receive a bitstream including mesh data and decode the mesh data. The point cloud data transmission and reception method / device according to embodiments may be abbreviated as method / device according to embodiments. The point cloud data transmission and reception method / device according to embodiments may also be referred to as mesh data transmission and reception method / device according to embodiments.

[0167] The encoding / decoding method according to the embodiments includes a scalable coding method of geometric information of dynamic mesh data (Geometry Scalable Coding Method of Dynamic Mesh Data).

[0168] The encoding / decoding method according to the embodiments includes a method for defining scalable coding signaling HLS (High Level Syntax, HLS) for dynamic mesh data.

[0169] The encoding / decoding method according to the embodiments includes a scalable coding scheme for dynamic mesh data, and among them, a scheme for defining a scalable coding HLS for geometry information.

[0170] Dynamic mesh content receivers may be required to decode / render dynamic mesh content in various configurations depending on resources such as memory, decoder performance, display, or producer's intent, and content producers may encode / decode dynamic mesh content by applying scalable coding according to predefined and / or newly defined criteria such as Level of Detail (LoD) taking these factors into consideration.

[0171] Since a dynamic mesh content receiver must decode each piece of data contained in such dynamic mesh content to know whether scalable coding has been applied, a dynamic content receiver with restrictions related to scalable coding may experience unnecessary or abnormal behavior and inefficient resource management.

[0172] To address this, embodiments include a syntax capable of signaling information encoded with scalable coding for geometry data among the data constituting dynamic mesh content. The embodiments include a scalable coded geometry data type, scalable coding codec ID signaling, and scalable coding general information signaling scheme.

[0173] Figure 15 shows a bitstream structure according to embodiments.

[0174] Dynamic mesh content can be encoded with a bitstream structure such as that in Fig. 15. The sample stream data unit used when encoding V3C content in Fig. 15 and the V3C codec specification (ISO / IEC 23090-5) can be used.

[0175] Definitions of terms according to embodiments are as follows: VPS: V3C / V-DMC Parameter Set, AD: Atlas Data, BMD: Base Mesh Data, DD: Displacement Data (if displacement data is encoded with arithmetic coding), GVD: Geometry Video Data (if displacement data is encoded using a video codec), AVD: Attribute Video Data (video coding).

[0176] Referring to FIG. 15, a bitstream may be configured in a sample stream format. The bitstream may include a sample stream data unit header and a sample stream data unit payload. The sample stream data unit header may include common information regarding the sample stream data unit payload. The sample stream data unit payload may include parameter set information such as VPS. The sample stream data unit payload may include atlas data, basemesh data, displacement data, geometry video data, and attribute video data, respectively.

[0177] The structure of the payload of the data unit included in the bitstream is as follows.

[0178] v3c_unit_payload( numBytesInV3CPayload ) {if( vuh_unit_type == V3C_VPS )v3c_parameter_set( numBytesInV3CPayload )else if( vuh_unit_type == V3C_AD)atlas_sub_bitstream( numBytesInV3CPayload ) / * Syntax and semantics omitted below * / }

[0179] The above V3C unit payload syntax can follow the standard ISO / IEC 23090-5.

[0180] The header of a data unit may contain a payload type (vuh_unit_type).

[0181] Depending on the payload type (vuh_unit_type), the V3C unit payload may contain a VPS or an atlas sub-bitstream.

[0182] The embodiments relate to a method for applying scalable coding to geometry (or displacement) data encoded using a video codec, when the V3C content format is GVD (Geometry Video Data).

[0183] According to the embodiments, geometry, geometry information, geometry data, displacement (displacement), displacement information, displacement data, etc. are interpreted as having the same meaning.

[0184] The encoding / decoding method according to the embodiments can generate a scalable coded geometry data type. Geometry data compressed using scalable video coding can be included in a V3C unit corresponding to geometry video data (GVD) and transmitted / received. In this case, the unit type can be V3C_GVD. Alternatively, it can be defined as a data type corresponding to encoded geometry data newly defined in V-DMC.

[0185] The V3C unit payload of scalable coded geometry data using a video codec can use the form of a video sub-bitstream (video_sub_bitstream) and can have a NAL unit structure coded with HEVC (SHVC) or VVC (multi-layer VVC).

[0186] The encoding / decoding method according to the embodiments includes a method for signaling a scalable coding codec ID. The codec used for scalable coding can be signaled through the profile codec group idc (ptl_profile_codec_group_idc) field of the profile tier level (profile_tier_level) transmitted in the V3C parameter set defined in the V3C codec specification (ISO / IEC 23090-5).

[0187] The definition of the ptl_profile_codec_group_idc value related to this is as follows:

[0188] CodecGroupptl_profile_codec_group_idc4CC codeAVC Progressive High0'avc3'HEVC Main101'hev1'HEVC4442'hev1'VVC Main103'vvi1'HEVC Main4'hev1'HEVC Scalable Main105'hev1' (or new 4CC definition)VVC Multilayer Main106'vv1' (or new 4CC definition)Reserved5..126-MP4RA127provided by component codec mapping SEI message

[0189] The encoding / decoding method according to the embodiments includes the above codec group and can encode / decode mesh data according to the codec group.

[0190] The encoding method according to the embodiments may generate a codec group value, such as HEVC Scalable Main10 and / or VVC Multilayer Main10.

[0191] The profile_codec_group_idc value can be set to 127, which corresponds to MP4RA, and signaled using the component codec mapping SEI message of the V3C codec specification (ISO / IEC 23090-5). That is, the ccm_codec_id value can be assigned (e.g., 0xA), and ccm_codec_4cc can be specified as the value of 'shv1' (HEVC Scalable Main 10) or 'mvv1' (VVC Multilayer Main 10). The newly defined ccm_codec_4cc value needs to be registered in MP4RA according to the method specified in Annex D of ISO / IEC 14496-12.

[0192] The component codec mapping SEI message syntax is as follows:

[0193] component_codec_mapping( payloadSize ) {Descriptorccm_component_codec_cancel_flagu(1)if( !ccm_component_codec_cancel_flag ) {ccm_codec_mappings_count_minus1u(8)for( i = 0; i <= ccm_codec_mappings_count_minus1; i++ ) {ccm_codec_idu(8)ccm_codec_4cc[ ccm_codec_id ]st(v)}}}

[0194] The component codec cancel flag (ccm_component_codec_cancel_flag) indicates whether the component codec mapping should be reset to the default mapping defined in the CodecGroup profile type of the bitstream. If ccm_component_codec_cancel_flag is 1, it indicates that the component codec mapping should be reset to the default mapping defined in the CodecGroup profile type of the bitstream. If ccm_component_codec_cancel_flag is 0, it indicates that the component codec mapping for some components may be updated.

[0195] Number of codec mappings (ccm_codec_mappings_count_minus1): Adding 1 to this value indicates the number of codec mappings listed in this SEI message.

[0196] The codec ID (ccm_codec_id) is the codec ID to be mapped to a specific 4CC codec. This codec ID may be associated with one or more sub-bitstreams of a V3C bitstream, as specified within the active VPS.

[0197] ccm_codec_4cc[j] is the four-digit code (4CC) of the codec mapped to the codec ID of value j. The codec code is an MP4RA registration code according to ISO / IEC 14496-12.

[0198] Figure 16 shows a V-DMC (Video-based dynamic mesh coding) extension of the V3C (Visual volumetric video-based coding) parameter set according to embodiments.

[0199] The encoding / decoding method according to the embodiments can signal scalable coding general information. When encoding geometry data with scalable coding, information on how to map geometry (displacement) data to fit a scalable layer can be signaled. Such signaling information can be added as an extension to the V3C parameter set syntax and / or can be added as an extension to the atlas sequence parameter set syntax. The V3C parameter set syntax extension method and the atlas sequence parameter set syntax extension method are described below.

[0200] The basemesh data substream codec ID (vps_ext_bmesh_data_substream_codec_id[j]) indicates the identifier of the codec used to compress the basemesh data for the atlas with atlas ID j. This codec may be identified via the profile of the component codec mapping SEI message or by means external to this document.

[0201] The basemesh data attribute count (vps_ext_bmesh_data_attribute_count[j]) represents the number of basemesh attributes for the atlas with atlas ID j. vps_ext_mesh_data_attribute_count[j] is in the range 0 to N.

[0202] If the basemesh scalable geometry video presence flag (vps_ext_bmesh_scalable_geometry_video_present_flag[j]) is 1, it indicates that scalable video information is present, and if the value is 0, it indicates that scalable video information is not present.

[0203] Figure 17 illustrates scalable geometry video information according to embodiments.

[0204] Figure 17 illustrates scalable coding information for geometry data. It is generated by an encoder according to embodiments and decoded by a decoder.

[0205] The scalable displacement video presence flag (scalable_displacement_video_present_flag) indicates whether scalable coding is supported for mesh coding of the geometry.

[0206] The scalable displacement information present flag (scalable_displacement_information_present_flag) indicates whether scalable coded displacement information is present.

[0207] The maximum spatial layer ID (max_layer_id_spat) indicates the maximum layer_id for spatially scalable coding. The number of layers for spatially scalable coding is max_layer_id_spat + 1. A max_layer_id_spat of 0 indicates no spatially scalable coding.

[0208] The maximum temporal layer ID (max_layer_id_temp) indicates the maximum layer_id for temporally scalable coding. The number of layers for spatially scalable coding is max_layer_id_temp + 1. A max_layer_id_temp of 0 indicates no temporally scalable coding.

[0209] The displacement mapping idc (displacement_mapping_idc) indicates how displacement (geometry) data is encoded in a scalable manner. This information provides information about the geometry (displacement) data mapping for each scalable layer, or the mapping of each LoD to a scalable layer. A value of '0' indicates that the number of layers is equal to the number of LoDs, and that each layer contains a single LoD. A value of '1' indicates that the number of layers is not equal to the number of LoDs, and that the mapping of each LoD to a scalable layer is specified separately.

[0210] The maximum LoD number (max_lod_num[k]) indicates the largest LoD number contained in the kth scalable layer. Geometry data belonging to the same LoD number cannot be contained in other scalable layers. The receiving device (decoder) can use this information to determine which layer to decode based on the geometric details required for a specific application.

[0211] Figure 18 shows the maximum value of the LoD (Level of Detail) number according to embodiments.

[0212] For example, Fig. 18 shows the LoD and interlayer inclusion relationship when the displacement mapping idc (displacement_mapping_idc) is 1 and the maximum spatial layer ID (max_layer_id_spat) is 2. Since the displacement mapping idc (displacement_mapping_idc) is 1, the number of layers is 3, such as Layer 0 to Layer 2, and the number of LoDs is 4, such as LoD0 to LoD3. Since the maximum spatial layer ID (max_layer_id_spat) is 2, the number of layers is 3.

[0213] Since the maximum LoD number (max_lod_num[0]) of the 0th layer is 0, layer 0 contains LoD0, since the maximum LoD number (max_lod_num[1]) of the 1st layer is 1, layer 1 contains LoD1, and since the maximum LoD number (max_lod_num[2]) of the 2nd layer is 3, layer 2 contains both LoD2 and LoD3.

[0214] That is, the smaller the index number of LoD, the more data is included in LoD, so Layer 2 can create a scalable layer by including both LoD2 and LoD3.

[0215] Figure 19 illustrates scalable geometry video information according to embodiments.

[0216] The scalable geometry video information of Fig. 17 can be expressed as in Fig. 19. For the same information as Fig. 17 in Fig. 19, refer to the description of Fig. 17.

[0217] Number of Packed LoDs (num_packed_lod_minus1[k]): Adding 1 to this value indicates the number of LoDs contained in the kth scalable layer. Geometry data belonging to the same LoD number cannot be contained in another scalable layer. The receiving device (decoder) can use this information to determine which layer to decode based on the geometric details required for a particular application.

[0218] Figure 20 shows the number of packed LoDs according to embodiments.

[0219] Figure 20 illustrates an example of the number of packed LoDs (num_packed_lod_minus1[k]) described in Figure 19.

[0220] For example, if the displacement mapping idc (displacement_mapping_idc) is 1 and the maximum spatial layer id (max_layer_id_spat) is 2, the number of layers can be 3.

[0221] Since the number of packed LoDs in the 0th layer (num_packed_lod_minus1[0]) is 0, layer 0 contains LoD0, since the number of packed LoDs in the 1st layer (num_packed_lod_minus1[1]) is 0, layer 1 contains LoD1, and since the number of packed LoDs in the 2nd layer (num_packed_lod_minus1[2]) is 1, layer 2 contains both LoD2 and LoD3, which are 2 (1+1) LoDs.

[0222] Figure 21 shows an extension of the V3C parameter set according to embodiments.

[0223] The encoding / decoding method according to the embodiments can generate scalable geometry video information and add it to a separate extension level of the V3C parameter set of the V3C parameter set.

[0224] Figure 21 illustrates a method for adding scalable coding information as a separate extension, as defined in the V3C parameter set extension syntax in the V3C specification (ISO / IEC 23090-5).

[0225] When the extension type (extension_type) is VPS_EXT_VDMC_SCALE, the VPS extension (vps_extension), which is a separate extension level of the V3C parameter set, includes scalable geometry video extension information (scalable_geometry_video_extension).

[0226] Extension data byte (vps_extension_data_byte) can have any value.

[0227] The syntax of the scalable geometry video extension (scalable_geometry_video_extension) is as follows.

[0228] scalable_geometry_video_extension() {Descriptorfor(i = 0; i <= atlas_count_minus1; i++) {scalable_geometry_video_information() / * Figure 17] or Figure 19 * / }}

[0229] Scalable geometry video extension information includes scalable geometry video information (scalable_geometry_video_information). The syntax of scalable geometry video information (scalable_geometry_video_information) includes the syntax described in FIG. 17 and / or FIG. 19.

[0230] Figure 22 shows an atlas sequence parameter set according to embodiments.

[0231] The encoding / decoding method according to the embodiments can generate scalable geometry video information and add it to an atlas sequence parameter set extension.

[0232] If the extension presence flag (asps_extension_present_flag) is 1, it indicates that the syntax elements asps_vpcc_extension_present_flag, asps_miv_extension_present_flag, and asps_extension_6bits are present in the atlas_sequence_parameter_set_rbsp() syntax structure. If asps_extension_present_flag is 0, it indicates that the syntax elements asps_vpcc_extension_present_flag, asps_miv_extension_present_flag, and asps_extension_6bits are not present.

[0233] If asps_vpcc_extension_present_flag is 1, it indicates that the asps_vpcc_extension() syntax structure is present in the atlas_sequence_parameter_set_rbsp() syntax structure. If asps_vpcc_extension_present_flag is 0, it indicates that this syntax structure does not exist. If it does not exist, the value of asps_vpcc_extension_present_flag is inferred to be equal to 0.

[0234] If asps_miv_extension_present_flag is 1, it indicates that the asps_miv_extension() syntax structure is present in the atlas_sequence_parameter_set_rbsp() syntax structure. If asps_miv_extension_present_flag is 0, it indicates that this syntax structure is not present. If it is not present, the value of asps_miv_extension_present_flag is inferred to be equal to 0.

[0235] If asps_scalable_geometry_video_extension_present_flag is 1, it indicates that the scalable_geometry_video_extension() syntax structure is present in the atlas_sequence_parameter_set_rbsp() syntax structure. If asps_scalable_geometry_video_extension_flag is 0, it indicates that this syntax structure is absent. If it is not present, the value of asps_scalable_geometry_video_extension_present_flag is inferred to be equal to 0.

[0236] The syntax of scalable geometry video information (scalable_geometry_video_information) includes the syntax described in FIG. 17 and / or FIG. 19.

[0237] If extension (asps_extension_6bits) is equal to 0, this indicates that the ASPS RBSP syntax structure does not contain the asps_extension_data_flag syntax element. If present, asps_extension_6bits is equal to 0 in bitstreams conforming to this version of this document. Non-zero asps_extension_6bits values ​​are reserved for future use in ISO / IEC.

[0238] The extension data flag (asps_extension_data_flag) can have any value. Its presence and value do not affect the decoder's conformance to the profile specified in this version of this document.

[0239] Figure 23 illustrates a dynamic mesh content receiver according to embodiments.

[0240] FIG. 23 may be referred to as a mesh data decoder, decoder, mesh content receiver, etc. according to embodiments. Each component of FIG. 23 corresponds to hardware, software, a processor, and / or a combination thereof.

[0241] The mesh data decoder of the dynamic mesh content receiver of FIG. 23 can perform operations according to the embodiments described above.

[0242] When signaling scalable coding information as an extension to the V3C parameter set:

[0243] 1) The Delivery module (receiver) and / or the File Decapsulation module (decapsulator) can process the stored and / or received dynamic mesh content to generate it in a form similar to the dynamic mesh bitstream structure of FIG. 15.

[0244] 2) The bitstream parser of the mesh data decoder parses the dynamic mesh content bitstream.

[0245] 3) The bitstream parser parses the V3C unit header and V3C unit payload that make up the bitstream. It obtains data corresponding to the unit type V3C_VPS defined in Fig. 15, i.e., V3C parameter set (VPS) data.

[0246] 4) The receiver can obtain the signaled scalable codec information by parsing the profile tier level (profile_tier_level) information included in the VPS data as described in the scalable coding codec ID signaling through the VPS data obtained in step 3). Based on the obtained scalable codec information, the receiver can determine whether the receiver supports the corresponding codec, and predict and determine subsequent decoding operations.

[0247] 5) In addition, the receiver can obtain extended information, i.e., scalable coding information, signaled within the VPS data as described in FIGS. 16 to 21 through the VPS data obtained in the above process 3).

[0248] 6) The receiver obtains scalable coding information from the above process 5), that is, scalable coding information for the geometry data defined in FIG. 17 or FIG. 19, and can obtain information such as the geometry scalable coding type included in the bitstream, the number of layers, and / or the mapping of layers and LoD, as described in the scalable coding syntax.

[0249] 7) The receiver can predict and decide subsequent decoding operations by considering and / or judging the available resources of the receiver based on the geometry scalable coding information acquired in step 6).

[0250] 8) The receiver can identify geometry video data information encoded in scalable coding in the bitstream of the dynamic mesh content prior to the direct decoding process of the geometry video data through the processes 1) to 7).

[0251] When signaling scalable coding information as an extension of the atlas sequence parameter set:

[0252] 1) ~ 4) The process may be identical to the operation described above in Fig. 23.

[0253] 5) The receiver can obtain data whose unit type of the V3C unit payload corresponds to V3C_AD, i.e., atlas data, and can obtain data whose nal_unit_type of the atlas data corresponds to NAL_ASPS, i.e., atlas sequence parameter set information. Thereafter, the receiver can obtain scale coding information signaled as an extension to the atlas sequence parameter set as described above in FIG. 22.

[0254] 6) ~ 8) The process may be the same as the operation described above in Fig. 23.

[0255] FIG. 23 may be referred to as a decoding device, a decoder, a receiver, etc. The decoder may include a receiving unit corresponding to the delivery module, a file / segment decapsulator, a decoder including audio decoding and / or mesh data decoding, an audio renderer and / or a renderer including mesh data / rendering, etc. The sensing / tracking unit may provide orientation and / or viewport information to the receiver and / or transmitter. Audio may be output through speakers and / or headphones. Mesh video data may be displayed.

[0256] Figure 24 shows a mesh data encoding method according to embodiments.

[0257] The mesh data encoding method according to the embodiments may include a step (S2400) of encoding mesh data.

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

[0259] The bitstream generated in step S2400 may include a parameter set regarding mesh data, atlas data regarding mesh data, basemesh data regarding mesh data, displacement data of mesh data or geometry data of displacement data, or attribute data regarding mesh data.

[0260] The type of a unit in the bitstream includes a value representing at least one of a parameter set or atlas data, and the type of a unit in the bitstream may further include a value representing geometry data for scalable video coding.

[0261] With respect to the scalable geometry type, the type of the unit in the bitstream includes a value indicating at least one of a parameter set or atlas data, and the type of the unit in the bitstream may further include a value indicating geometry data related to scalable video coding.

[0262] With respect to the scalable codec ID, the parameter set within the bitstream may include codec profile information regarding mesh data, and the codec profile information may include a value indicating scalable coding.

[0263] Referring to FIG. 17, with respect to scalable coding information and V-DMC extension syntax, a parameter set in a bitstream includes extension information for mesh data (vps_vdmc_extension), the extension information includes information indicating whether scalable geometry video information exists (vps_ext_bmesh_scalable_geometry_video_present_flag), and based on a value of the information indicating whether scalable geometry video information exists, the extension information includes scalable geometry video information, and the scalable geometry video information includes information indicating whether scalable coding is supported for geometry data of mesh data (scalable_displacement_video_present_flag), information indicating whether scalable coded displacement information exists (scalable_displacement_information_present_flag), information on the maximum number of layer IDs for spatial scalable coding (max_layer_id_spat), information on the maximum number of layer IDs for temporal scalable coding (max_layer_id_temp), It may include at least one of information indicating a scalable coding method for displacement information (displacement_mapping_idc) or information on the maximum number of LoDs (levels of detail) within a scalable layer (max_lod_num).

[0264] Referring to FIG. 18, when information indicating a scalable coding method for displacement information has a first value, a layer and at least one LoD can be mapped based on at least one of the maximum number information of layer IDs for spatial scalable coding or the maximum number information of LoDs (levels of detail) within a scalable layer.

[0265] Referring to FIG. 19, a parameter set in a bitstream includes extension information for mesh data, the extension information includes scalable geometry video information, and the scalable geometry video information may include at least one of information indicating whether scalable coding is supported for geometry data of the mesh data, information indicating whether scalable coded displacement information exists, information indicating a maximum number of layer IDs for spatial scalable coding, information indicating a maximum number of layer IDs for temporal scalable coding, information indicating a scalable coding method for displacement information, or information indicating a number of LoDs (levels of detail) in a scalable layer (num_packed_lod_minus1).

[0266] Referring to FIG. 20, a layer and at least one LoD can be mapped based on at least one of information indicating a scalable coding method for displacement information, information indicating a maximum number of layer IDs for spatial scalable coding, or information indicating a number of LoDs (levels of detail) within a scalable layer.

[0267] Referring to FIG. 21, a bitstream includes a VPS (V3C parameter set), and extension information (vps_extension) of the VPS includes scalable geometry video information, and the scalable geometry video information may include at least one of information indicating whether scalable coding is supported for geometry data of mesh data, information indicating whether scalable coded displacement information exists, information indicating a maximum number of layer IDs for spatial scalable coding, information indicating a maximum number of layer IDs for temporal scalable coding, or information indicating a scalable coding method for displacement information. The scalable geometry video information may further include at least one of information indicating a maximum number of LoDs (levels of detail) within a scalable layer or information indicating the number of LoDs (levels of detail) within a scalable layer.

[0268] Referring to FIG. 22, a bitstream includes an atlas sequence parameter set, and the atlas sequence parameter set includes scalable geometry video information, and the scalable geometry video information may include at least one of information indicating whether scalable coding is supported for geometry data of mesh data, information indicating whether scalable coded displacement information exists, information indicating a maximum number of layer IDs for spatial scalable coding, information indicating a maximum number of layer IDs for temporal scalable coding, or information indicating a scalable coding method for displacement information. The scalable geometry video information may further include at least one of information indicating a maximum number of LoDs (levels of detail) within a scalable layer or information indicating the number of LoDs (levels of detail) within a scalable layer.

[0269] The encoding method of Fig. 24 can be performed by an encoding device such as Fig. 1. The mesh data encoding device according to the embodiments may include an encoder that encodes mesh data; and a transmission unit that transmits a bitstream including mesh data.

[0270] Figure 25 shows a mesh data decryption method according to embodiments.

[0271] A method for decrypting mesh data according to embodiments may include a step (S2500) of receiving a bitstream including mesh data.

[0272] The mesh data decryption method according to the embodiments may further include a step (S2501) of decoding mesh data.

[0273] The decryption method of Fig. 25 can follow the reverse process of the encoding method of Fig. 24.

[0274] Referring to FIG. 15, with respect to the bitstream received in step S2500, the bitstream may include a parameter set regarding mesh data, atlas data regarding mesh data, basemesh data regarding base mesh data, displacement data of mesh data or geometry data of displacement data, or attribute data regarding mesh data.

[0275] With respect to the scalable geometry type, the type of the unit in the bitstream includes a value indicating at least one of a parameter set or atlas data, and the type of the unit in the bitstream may further include a value indicating geometry data related to scalable video coding.

[0276] With respect to the scalable codec ID, the parameter set within the bitstream may include codec profile information regarding mesh data, and the codec profile information may include a value indicating scalable coding.

[0277] Referring to FIG. 17, with respect to scalable coding information and V-DMC extension syntax, a parameter set in a bitstream includes extension information for mesh data (vps_vdmc_extension), the extension information includes information indicating whether scalable geometry video information exists (vps_ext_bmesh_scalable_geometry_video_present_flag), and based on a value of the information indicating whether scalable geometry video information exists, the extension information includes scalable geometry video information, and the scalable geometry video information includes information indicating whether scalable coding is supported for geometry data of mesh data (scalable_displacement_video_present_flag), information indicating whether scalable coded displacement information exists (scalable_displacement_information_present_flag), information on the maximum number of layer IDs for spatial scalable coding (max_layer_id_spat), information on the maximum number of layer IDs for temporal scalable coding (max_layer_id_temp), It may include at least one of information indicating a scalable coding method for displacement information (displacement_mapping_idc) or information on the maximum number of LoDs (levels of detail) within a scalable layer (max_lod_num).

[0278] Referring to FIG. 18, when information indicating a scalable coding method for displacement information has a first value, a layer and at least one LoD can be mapped based on at least one of the maximum number information of layer IDs for spatial scalable coding or the maximum number information of LoDs (levels of detail) within a scalable layer.

[0279] Referring to FIG. 19, a parameter set in a bitstream includes extension information for mesh data, the extension information includes scalable geometry video information, and the scalable geometry video information may include at least one of information indicating whether scalable coding is supported for geometry data of the mesh data, information indicating whether scalable coded displacement information exists, information indicating a maximum number of layer IDs for spatial scalable coding, information indicating a maximum number of layer IDs for temporal scalable coding, information indicating a scalable coding method for displacement information, or information indicating a number of LoDs (levels of detail) in a scalable layer (num_packed_lod_minus1).

[0280] Referring to FIG. 20, a layer and at least one LoD can be mapped based on at least one of information indicating a scalable coding method for displacement information, information indicating a maximum number of layer IDs for spatial scalable coding, or information indicating a number of LoDs (levels of detail) within a scalable layer.

[0281] Referring to FIG. 21, a bitstream includes a VPS (V3C parameter set), and extension information (vps_extension) of the VPS includes scalable geometry video information, and the scalable geometry video information may include at least one of information indicating whether scalable coding is supported for geometry data of mesh data, information indicating whether scalable coded displacement information exists, information indicating a maximum number of layer IDs for spatial scalable coding, information indicating a maximum number of layer IDs for temporal scalable coding, or information indicating a scalable coding method for displacement information. The scalable geometry video information may further include at least one of information indicating a maximum number of LoDs (levels of detail) within a scalable layer or information indicating the number of LoDs (levels of detail) within a scalable layer.

[0282] Referring to FIG. 22, a bitstream includes an atlas sequence parameter set, and the atlas sequence parameter set includes scalable geometry video information, and the scalable geometry video information may include at least one of information indicating whether scalable coding is supported for geometry data of mesh data, information indicating whether scalable coded displacement information exists, information indicating a maximum number of layer IDs for spatial scalable coding, information indicating a maximum number of layer IDs for temporal scalable coding, or information indicating a scalable coding method for displacement information. The scalable geometry video information may further include at least one of information indicating a maximum number of LoDs (levels of detail) within a scalable layer or information indicating the number of LoDs (levels of detail) within a scalable layer.

[0283] The mesh data decoding method of FIG. 25 can be performed by a mesh data decoding device such as that of FIG. 1 or FIG. 23. The mesh data decoding device can include a receiving unit that receives a bitstream including mesh data; and a decoder that decodes the mesh data.

[0284] The mesh data encoding / decoding method according to the embodiments provides the following technical effects.

[0285] The embodiments define the syntax required when applying scalable coding to geometry data that can be encoded with a video codec among data constituting dynamic mesh content according to predefined criteria and / or according to newly defined LoD values.

[0286] According to embodiments, the geometry data of the dynamic mesh content can be encoded as layer-based scalable coded displacement (geometry) data in a spatial or temporal manner, etc., according to the scalable coding syntax.

[0287] According to embodiments, scalable coding-related information such as codec information, layer information, LoD, etc. related to scalable coded geometry data can be signaled at the parameter set level of bitstream constituting dynamic mesh content.

[0288] Accordingly, the dynamic mesh content receiver can efficiently access the bitstreams that make up the dynamic mesh content, since it can determine whether there is geometry data with scalable coding applied within the content before actually decoding the geometry data encoded with the video codec.

[0289] Additionally, the dynamic mesh content receiver can effectively decode and render scalable coded geometry data in whole or in a selective manner, depending on hardware constraints such as the receiver's resources, display, etc., and / or the intent and profile definitions of the content creator, user, or receiver itself.

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

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

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

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

[0294] Terms such as first, second, etc. may be used to describe various components of the embodiments. However, the various components according to the embodiments should not be limited in their interpretation by the above 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 a first user input signal and a second user input signal are both user input signals, they do not mean the same user input signals unless the context clearly indicates otherwise.

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

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

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

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

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

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

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

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

Claims

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

2. In paragraph 1, The bitstream includes a parameter set regarding the mesh data, atlas data regarding the mesh data, basemesh data regarding the mesh data, displacement data of the mesh data or geometry data of the displacement data, or attribute data regarding the mesh data. How to decrypt mesh data.

3. In paragraph 2, The type of the unit in the bitstream includes a value representing at least one of the parameter set or the atlas data, The type of the unit in the above bitstream further includes a value representing geometry data for scalable video coding. How to decrypt mesh data.

4. In paragraph 2, The parameter set in the bitstream includes codec profile information regarding the mesh data, The above codec profile information includes a value indicating scalable coding, How to decrypt mesh data.

5. In paragraph 2, The parameter set in the bitstream includes extension information for the mesh data, The above extension information includes information indicating whether scalable geometry video information exists, Based on the value of the information indicating whether the scalable geometry video information exists, the extension information includes the scalable geometry video information, The above scalable geometry video information is Information indicating whether scalable coding is supported for the geometry data of the above mesh data; Information indicating whether scalable coded displacement information exists; Information on the maximum number of layer IDs for spatial scalable coding, Information on the maximum number of layer IDs for time-scalable coding, Information indicating a scalable coding method for the above displacement information, or Contains at least one of the maximum number of LoD (level of detail) information within a scalable layer, How to decrypt mesh data.

6. In paragraph 5, If the information indicating the scalable coding method for the above displacement information has a first value, A layer and at least one LoD are mapped based on at least one of the maximum number information of layer IDs for the above spatial scalable coding or the maximum number information of LoDs (levels of detail) within the above scalable layer. How to decrypt mesh data.

7. In paragraph 2, The parameter set in the bitstream includes extension information for the mesh data, The above extension information includes scalable geometry video information, The above scalable geometry video information is Information indicating whether scalable coding is supported for the geometry data of the above mesh data; Information indicating whether scalable coded displacement information exists; Information on the maximum number of layer IDs for spatial scalable coding, Information on the maximum number of layer IDs for time-scalable coding, Information indicating a scalable coding method for the above displacement information, or Contains at least one piece of information indicating the number of LoDs (levels of detail) within a scalable layer, How to decrypt mesh data.

8. In paragraph 7, A layer and at least one LoD are mapped based on at least one of information indicating a scalable coding method for the displacement information, information indicating a maximum number of layer IDs for the spatial scalable coding, or information indicating a number of LoDs (levels of detail) within the scalable layer. How to decrypt mesh data.

9. In paragraph 2, The above bitstream includes a VPS (V3C parameter set), and the extension information of the VPS includes scalable geometry video information. The above scalable geometry video information is Information indicating whether scalable coding is supported for the geometry data of the above mesh data; Information indicating whether scalable coded displacement information exists; Information on the maximum number of layer IDs for spatial scalable coding, Information about the maximum number of layer IDs for time-scalable coding, or Information indicating a scalable coding method for the displacement information, including at least one of: The above scalable geometry video information is At least one of information indicating the maximum number of LoDs (levels of detail) within a scalable layer or information indicating the number of LoDs (levels of detail) within a scalable layer, How to decrypt mesh data.

10. In paragraph 2, The bitstream includes an atlas sequence parameter set, and the atlas sequence parameter set includes scalable geometry video information. The above scalable geometry video information is Information indicating whether scalable coding is supported for the geometry data of the above mesh data; Information indicating whether scalable coded displacement information exists; Information on the maximum number of layer IDs for spatial scalable coding, Information about the maximum number of layer IDs for time-scalable coding, or Information indicating a scalable coding method for the displacement information, including at least one of: The above scalable geometry video information is At least one of information indicating the maximum number of LoDs (levels of detail) within a scalable layer or information indicating the number of LoDs (levels of detail) within a scalable layer, How to decrypt mesh data.

11. A receiving unit that receives a bitstream containing mesh data; and A decoder for decoding the above mesh data; comprising: Mesh data decryption device.

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

13. In paragraph 12, The bitstream includes a parameter set regarding the mesh data, atlas data regarding the mesh data, basemesh data regarding the mesh data, displacement data of the mesh data or geometry data of the displacement data, or attribute data regarding the mesh data. Mesh data encoding method.

14. In paragraph 13, The type of the unit in the bitstream includes a value representing at least one of the parameter set or the atlas data, The type of the unit in the above bitstream further includes a value representing geometry data for scalable video coding. Mesh data encoding method.

15. An encoder that encodes mesh data; and A transmission unit for transmitting a bitstream including the above mesh data; Mesh data encoding device.

Images