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 comprises the steps of: decoding a base mesh in a bitstream; decoding displacement data in the bitstream; and decoding attribute data in the bitstream, wherein the bitstream can further include first information indicating whether scalable video coding is applied when the attribute data is encoded at a transmission side, and second information indicating whether scalable video coding is applied when video data in which the attribute data and the displacement data are packed into one frame is encoded at the transmission side.

Description

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

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

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

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

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

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

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

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

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

[0009] According to embodiments, the bitstream may further include first information indicating whether scalable video coding was applied when the attribute data was encoded at the transmitting side.

[0010] According to embodiments, the bitstream may further include second information indicating whether scalable video coding was applied when video data in which the attribute data and the displacement data are packed into one frame is encoded at the transmitting side.

[0011] According to embodiments, the first information and the second information may be signaled and received in a parameter set within the bitstream.

[0012] According to embodiments, the first information and the second information may be defined as to whether they are allowed or not in the toolset profile components, respectively.

[0013] According to embodiments, the step of decoding the attribute data may apply scalable video decoding to the attribute data or the packed video data based on at least one of the first information, the second information, or whether the first information and the second information are allowed as defined in the toolset profile components.

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

[0015] According to embodiments, the at least one processor may apply scalable video decoding to video data in which the attribute data or the attribute data and the displacement data are packed into one frame based on at least one of the first information, the second information, or the allowability of the first information and the second information defined in the toolset profile components included in the bitstream.

[0016] According to embodiments, the first information may indicate whether scalable video coding was applied when the attribute data was encoded at the transmitting side, and the second information may indicate whether scalable video coding was applied when the packed video data was encoded at the transmitting side.

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

[0018] According to embodiments, the method may further include generating first information indicating whether scalable video coding was applied when the attribute data was encoded and second information indicating whether scalable video coding was applied when video data in which the attribute data and the displacement data are packed into one frame was encoded.

[0019] According to embodiments, the method may further include defining, for each of the toolset profile components, whether the first information and the second information are allowed.

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

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

[0022] According to embodiments, a transmission method may include: obtaining a bitstream for mesh data, wherein the bitstream is generated based on: encoding a base mesh of the mesh data; encoding displacement data of the mesh data; and encoding attribute data of the mesh data; and transmitting data including the bitstream.

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

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

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

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

[0027] Figures 1(a) and 1(b) are diagrams showing examples of an encoder and a decoder according to embodiments.

[0028] FIG. 2 illustrates a system for providing dynamic mesh content according to embodiments.

[0029] Figure 3 illustrates a V-MESH compression method according to embodiments.

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

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

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

[0033] Figure 7 illustrates an encoding process of mesh data according to embodiments.

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

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

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

[0037] Figure 11 illustrates a decoding process of mesh data according to embodiments.

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

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

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

[0041] FIG. 15 is a diagram showing an example of a dynamic mesh bitstream structure transmitted from a transmitting device of the present disclosure.

[0042] FIG. 16 is a diagram showing an example of the syntax structure of profile_tier_level() included in VPS according to embodiments.

[0043] FIG. 17 is a diagram showing an example of the syntax structure of asps_vdmc_extension( ) included in the atlas sequence parameter set according to embodiments.

[0044] FIG. 18 is a diagram showing an example in which asve_attribute_scalable_coding_flag and asve_packed_video_scalable_coding_flag are used to represent V-DMC toolset profile components according to embodiments.

[0045] FIG. 19 is a diagram showing an example of the syntax structure of vps_vdmc_extension ( ) included in VPS according to embodiments.

[0046] FIG. 20 is a diagram showing an example in which vps_ext_attribute_scalable_coding_flag and vps_ext_packed_video_scalable_coding_flag are used to represent V-DMC toolset profile components according to embodiments.

[0047] FIG. 21 is a diagram showing examples of V-DMC toolset profile components according to embodiments.

[0048] FIG. 22 is a diagram showing examples of syntax element values ​​allowed for V-DMC toolset profile components according to embodiments.

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

[0050] FIG. 24 is a diagram showing examples of restoration profile components defined for V-DMC according to embodiments.

[0051] Fig. 25 is a flowchart showing an example of an encoding method according to embodiments.

[0052] Fig. 26 is a flowchart showing an example of a decoding method according to embodiments.

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

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

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

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

[0057] Figures 1(a) and 1(b) illustrate a V-DMC-based encoder and decoder according to embodiments. In particular, Figure 1(a) illustrates an encoder, and Figure 1(b) illustrates a decoder.

[0058] The basic structure of the currently in-progress V-DMC (v-mesh) is as shown in Fig. 1(a) and Fig. 1(b). The encoder according to Fig. 1(a) and the decoder according to Fig. 1(b) perform the process of encoding and decoding media representing dynamic meshes using V3C (Visual Volumetric Video-based Coding) technology. The preprocessor converts the input dynamic mesh representation into several V3C components (base mesh, displacement set, 2D representation of attributes, and atlas). The original mesh is simplified into the base mesh. The base mesh can be encoded using any mesh codec. The displacement vector can be encoded into the V3C geometry video component using any video codec, either indicated by the profile or based on the SEI (supplemental enhancement information) message. For example, depending on the profile, the displacement vector (or displacement data) can be encoded via a video codec-based encoder, a zero-run length encoder, an arithmetic encoder, etc. The attribute data can include additional attributes. For example, texture or material information can be included as additional attributes, and can be encoded based on any video codec. The atlas data includes information on how to perform inverse reconstruction, and is provided to the V3C (or v-mesh) decoding and / or rendering system of the receiving device. For example, the atlas data can include a method for performing subdivision of the base mesh, a method for applying displacement vectors to subdivided mesh vertices, a method for applying attributes to the reconstructed mesh, etc.

[0059] An encoder according to embodiments may comprise a memory and at least one processor connected to the memory. The at least one processor may be configured to perform operations such as a pre-processor, an atlas encoding unit, a basemesh encoding unit, a displacement vector encoding unit, a video encoding unit, and a multiplexer.

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

[0061] A decoder according to embodiments may comprise a memory and at least one processor connected to the memory. The at least one processor may be configured to perform operations such as a demultiplexer, an atlas decoding unit, a basemesh decoding unit, a displacement vector decoding unit, and a video decoding unit.

[0062] The atlas decoding unit decodes the atlas within the bitstream. The basemesh decoding unit decodes the basemesh within the bitstream. The displacement vector decoding unit decodes the displacement vector within the bitstream. The video decoding unit decodes the attribute within the bitstream. The decoder according to the embodiments may perform each decoding operation based on parameter information within the bitstream. In the decoder according to the embodiments, the basemesh processing unit restores the current basemesh from the decoded basemesh based on the atlas and / or parameter information. In the decoder according to the embodiments, the displacement processing unit restores the displacement vector by performing coordinate system transformation of the decoded displacement vector based on the atlas and / or parameter information. In the decoder according to the embodiments, the mesh restoration unit restores the final mesh by combining the restored basemesh and the restored displacement vector based on the atlas and / or parameter information. The restored mesh processing unit of the decoder according to the embodiments can generate and render a reconstructed dynamic mesh image by combining the decoded attribute (or texture map) with the restored final mesh. That is, the reconstructed dynamic mesh image can be displayed to the user.

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

[0064] FIG. 2 illustrates a system for providing dynamic mesh content according to embodiments.

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

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

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

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

[0069] Currently, the MPEG standards body defines the data types of dynamic mesh data as the following two types.

[0070] Category 1: Mesh data with texture maps as color information.

[0071] Category 2: Mesh data with vertex colors as color information.

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

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

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

[0075] In the above transmitting device (100), the encoder may be called a mesh video / video / picture / frame encoding device, and in the receiving device (110), the decoder may be called a mesh video / video / picture / frame decoding device. The transmitter may be included in a mesh video encoder. The receiver may be included in a mesh video decoder. The renderer (114) may include a display unit, and the renderer and / or the display unit may be configured as separate devices or external components. The transmitting device (100) and the receiving device (110) may further include separate internal or external modules / units / components for a feedback process.

[0076] Mesh data represents the surface of an object as a number of polygons. Each polygon is defined by vertices in 3D space and connection information that describes how the vertices are connected. It can also contain vertex attributes such as vertex color and normal. Mapping information that allows the surface of the mesh to be mapped to a 2D planar area can also be included in the attributes of the mesh. The mapping can be described as a set of parameter coordinates, commonly 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 texture, normal, and displacement. Here, displacement can be used interchangeably with displacement information or displacement vector.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0095] As described above, the encoding process of Fig. 2 is as follows.

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

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

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

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

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

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

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

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

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

[0105] Figure 3 illustrates a V-MESH compression method according to embodiments.

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

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

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

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

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

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

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

[0113] GoF Generation: This is the process of generating a reference structure for mesh data. If the number of vertices, the number of texture coordinates, the vertex connection information, and the texture coordinate connection information of the mesh of the previous frame and the current mesh are all the same, the previous frame can be set as the reference frame. That is, if only the vertex coordinate values ​​are different between the current input mesh and the reference input mesh, the encoder (201) can perform inter frame encoding. Otherwise, intra frame encoding is performed for the corresponding frame.

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

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

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

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

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

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

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

[0121] When a fitted subdivided mesh (hereinafter referred to as a fitted subdivided mesh) is generated, displacement is calculated using this result and a pre-compressed and decoded base mesh (hereinafter referred to as a reconstructed base mesh). That is, the reconstructed base mesh is subdivided in the same way as the fitting subdivision surface. The difference in position of each vertex between this result and the fitted subdivided mesh is the displacement for each vertex. Since the displacement represents the position difference in three-dimensional space, it is also expressed as a value in the (x, y, z) space of the 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.

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

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

[0124] An encoder and / or pre-processor according to embodiments may include 1) a subdivision unit, 2) a local coordinate system calculation unit, and 3) a displacement calculation unit. The subdivision unit may perform subdivision on a restored base mesh to generate a subdivided restored base mesh. Here, the restoration of the base mesh may be performed in the pre-processor (200) or in the encoder (201). The local coordinate system calculation unit may receive a fitted subdivision mesh and a subdivided restored base mesh, and may convert a coordinate system of the mesh into a local coordinate system based on the fitted subdivision mesh and the subdivided restored base mesh. The local coordinate system calculation operation may be optional. The displacement calculation unit may calculate a positional difference between the fitted subdivision mesh and the subdivided restored 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.

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

[0126] The V-Mesh compression (decompression) method according to the embodiments may include intra frame encoding and inter frame encoding.

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

[0128] Figure 7 illustrates a V-DMC encoding process according to embodiments.

[0129] The elements of the transmitting device illustrated in FIG. 7 may be implemented by hardware, software, a processor connected to a memory, and / or a combination thereof. That is, the elements of the transmitting device illustrated in FIG. 7 may be implemented by hardware, software, firmware, or a combination thereof, including one or more processors or integrated circuits configured to communicate with one or more memories, although not illustrated in the drawing. One or more processors may perform at least one or more of the operations and / or functions of the elements of the transmitting device illustrated in FIG. 7. In addition, one or more processors may operate or execute a set of software programs and / or instructions for performing the operations and / or functions of the elements of the transmitting device illustrated in FIG. 7. The execution order of each block in FIG. 7 may be changed, some blocks may be omitted, and some blocks may be newly added.

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

[0131] The encoding process of FIG. 7 details the encoding of the mesh video encoder (102) of FIG. 2. The encoder of FIG. 7 may include a pre-processor (200) and / or an encoder (201). The pre-processor (200) and encoder (201) of FIG. 7 may correspond to the pre-processor (200) and encoder (201) of FIG. 4.

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

[0133] The quantizer (411) of the encoder (201) can quantize the base mesh and / or the fitted subdivided mesh.

[0134] According to embodiments, the base mesh quantized in the mesh quantization unit (411) may be output to a static mesh encoder (413) or a motion vector encoder (414) through a switching unit (412). According to embodiments, the base mesh is output to a motion vector encoder (414) through the switching unit (412) when inter-encoding is performed on the corresponding mesh frame, and is output to a static mesh encoder (413) through the switching unit (412) when intra-encoding is performed on the corresponding mesh frame. The motion vector encoder (414) may be referred to as a motion encoder.

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

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

[0137] In FIG. 7, the base mesh restoration unit (415) can receive a base mesh encoded by the static mesh encoder (413) or a motion vector encoded by the motion vector encoder (414) to generate a reconstructed base mesh. The base mesh restoration unit (415) performs restoration of the base mesh according to the encoding type (inter-screen encoding or intra-screen encoding) of the current mesh. For example, the base mesh restoration unit (415) can perform static mesh decoding on the base mesh encoded by the static mesh encoder (413) to restore the base mesh. At this time, quantization can be applied before static mesh decoding, and inverse quantization can be applied by the inverse quantization unit (416) after static mesh decoding. That is, when intra-screen encoding is performed, the inverse quantization unit (416) can perform inverse quantization on the quantized base mesh through the mesh quantization unit (411) to restore the current base mesh. As another example, the base mesh restoration unit (415) can restore the base mesh based on the restored quantized reference base mesh and the motion vector encoded by the motion vector encoder (414). That is, when inter-screen encoding is performed, the current base mesh can be generated by decoding the motion vector using the motion vector decoding method and then applying (i.e., adding) the decoded motion vector to the reference restoration base mesh. At this time, when the motion vector is not quantized, the motion vector restoration process is omitted and the current base mesh can be restored using the motion vector calculated by the motion vector encoder (414). The restored base mesh is output to the displacement vector calculation unit (417) and the mesh restoration unit (425).

[0138] According to embodiments, the displacement vector calculation unit (417) can perform mesh refinement on the restored base mesh. In addition, the displacement vector calculation unit (417) can calculate a displacement vector, which is a difference value in vertex positions between the restored base mesh that has been refined and the fitted subdivision (or refined) mesh generated by the pre-processor (200). That is, the displacement vector is a difference in positions between the vertices of the two meshes so that the fitted subdivision (or refined) mesh becomes similar to the original mesh. At this time, the displacement vector can be calculated as many times as the number of vertices of the subdivision mesh. That is, the displacement vector of the number of vertices of the subdivision (refined) mesh can be calculated through the displacement vector calculation unit (417).

[0139] The lifting transformation unit (418) can perform a lifting transformation on the input displacement vector to generate a lifting coefficient (or displacement vector transformation coefficient). The quantizer (419) can quantize the lifting coefficient, i.e., the displacement vector transformation coefficient.

[0140] In the present disclosure, the displacement vector or the quantized displacement vector transform coefficient can be encoded through a 2D video codec-based encoding method, and / or a zero run length encoding method, and / or an arithmetic encoding method, etc.

[0141] If an arithmetic encoding method is used, the displacement vector or the quantized displacement vector transform coefficient is encoded based on an arithmetic codec in an arithmetic encoding unit (421) after inter prediction in an inter prediction unit (420), and if a 2D video codec-based encoding method is used, the displacement vector or the quantized displacement vector transform coefficient is encoded based on a 2D video codec in a video encoding unit (423) after image packing in an image packing unit (422) and can be output as a displacement bitstream (i.e., compressed displacement bitstream). For example, the image packing unit (422) can pack an image based on quantized lifting coefficients (i.e., displacement vector transform coefficients). The video encoding unit (423) can encode the packed image. That is, the quantized lifting coefficients are packed into one frame as a 2D image by the image packing unit (422), compressed by the video encoding unit (423), and output as a displacement bitstream (i.e., compressed displacement bitstream).

[0142] The displacement vector restoration unit (424) may include a video decoder, an image unpacking unit, an inverse quantizer, and an inverse linear lifting unit. That is, the displacement vector restoration unit (424) performs decoding on an encoded displacement vector in the video decoder, performs image unpacking in the image unpacking unit, performs inverse quantization in the inverse quantizer, and then performs inverse transformation in the inverse linear lifting unit to restore the displacement vector. The restored displacement vector is output to the mesh restoration unit (425). The mesh restoration unit (425) restores the deformed mesh based on the base mesh restored by the base mesh restoration unit (415) and the displacement vector restored by the displacement vector restoration unit (424). That is, the mesh restoration unit (425) restores the reconstructed and deformed mesh through the restored displacement output from the displacement vector restoration unit (424) and the restored base mesh (or subdivided restored base mesh) output from the inverse quantization unit (416). The present disclosure refers to the reconstructed and deformed mesh as a restored deformed mesh. The restored mesh (or restored deformed mesh) has restored vertices, connection information between vertices, texture coordinates, and connection information between texture coordinates.

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

[0144] According to embodiments, the atlas encoder (430) may encode atlas information (or atlas data) to generate a compressed atlas bitstream. Then, the atlas bitstream generated through atlas information encoding is transmitted to the multiplexer (431). In the present disclosure, the atlas may be information required in a mesh reconstruction process and may mean information such as tiles and patches. In addition, the atlas information may mean data required in processes such as 2D mapping for a 3D object, texture mapping-related information, mesh decoding, and mesh restoration, and may include additional information such as a segmentation method, a transformation method, a quantization method, and the position and size of a patch within an atlas frame. In the present disclosure, the atlas information may be encoded through Exp-Golomb coding of the atlas encoder (430), etc.

[0145] According to embodiments, the multiplexer (430) can multiplex an input compressed base mesh bitstream, a compressed displacement (or displacement vector) bitstream, a compressed attribute (or texture map) bitstream, and a compressed atlas bitstream to generate a single compressed bitstream. The multiplexed bitstream can be encapsulated into one or more tracks of a file.

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

[0147] In summary, for the base mesh, encoding can be performed in different ways depending on the base mesh type (INTRA type, INTER type, SKIP type). If the base mesh is INTRA type, it can be encoded using the static mesh encoding method. If the base mesh is INTER type, the motion field between the reference base mesh and the current base mesh can be encoded. If the current base mesh is SKIP type, the reference base mesh can be derived as the current base mesh.

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

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

[0150] Connection information can be encoded and compressed based on the edgebreaker algorithm. The edgebreaker algorithm sequentially traverses triangles according to rules, maps symbols based on the characteristics of each triangle, and then encodes the corresponding symbols.

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

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

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

[0154] Motion Field Encoding (Inter Basemesh Encoding): Inter basemesh encoding can be performed when a one-to-one correspondence exists between the reference mesh and the current input mesh, and only the vertex position information differs. When performing inter encoding, instead of compressing the base mesh, the difference between the vertices of the reference base mesh and the current base mesh, i.e. the motion field, can be calculated and this information can be encoded. The reference base mesh is the result of quantizing the already decoded base mesh data and is determined by the reference frame index.

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

[0156] Displacement Encoding: After base mesh encoding, restoration and dequantization are performed to generate a Recon. base mesh, and the displacement between the result of performing subdivision on this and the fitted subdivided mesh can be calculated. For effective encoding, a data transform process such as wavelet transform can be applied to the displacement information, and Figure 8 shows the process of transforming displacement information using lifting transform in V-Mesh. The displacement vector transform coefficients generated through the transform process are quantized, and the quantized transform coefficients can be compressed through a video codec or through arithmetic encoding depending on the compression method.

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

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

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

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

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

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

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

[0164] FIG. 8 shows a process of transforming displacement information using a lifting transform in the lifting transform unit (418) of FIG. 7. For example, a linear wavelet-based lifting transform may be performed. The transform coefficients generated through the transform process are quantized in a quantizer (419) and then packed into a 2D image through an image packing unit (422) as in FIG. 9. The transform coefficients are organized into one block for each 256 (= 16 × 16) units, and each block can be packed in a z-scan order. The horizontal number of blocks is fixed to 16, but the vertical number of blocks can be determined according to the number of vertices of the subdivided base mesh. The transform coefficients can be packed by sorting them with a Morton code within one block. The packed images generate a displacement video for each GoF unit, and this displacement video can be encoded using an existing video compression codec in a video encoding unit (423, or video encoder).

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

[0166] Referring to FIG. 9, a vertex has a transformation coefficient (also called a lifting coefficient) generated through a lifting transformation. The transformation coefficient of a vertex related to a lifting transformation can be packed into an image by an image packing unit (422) and then encoded by a video encoding unit (423).

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

[0168] According to the embodiments, FIG. 10 shows the detailed operation of the attribute transfer (426) of FIG. 7.

[0169] Encoding according to embodiments includes attribute map encoding. According to embodiments, attribute map encoding may be performed in the video encoding unit (429) of FIG. 7.

[0170] According to embodiments, in the present disclosure, the encoder compresses information about the input mesh through base mesh encoding (i.e., intra encoding), motion field encoding (i.e., inter encoding), and displacement encoding. In the encoding process, the compressed input mesh is restored through base mesh decoding (intra frame), motion field decoding (inter frame), and displacement video decoding processes, and the restored result, the reconstructed deformed mesh (hereinafter referred to as Recon. deformed mesh), is used to compress the input attribute map as shown in FIG. 7. The reconstructed deformed mesh (Recon. deformed mesh) has position information of vertices, texture coordinates, and corresponding connection information, but does not have color information corresponding to the texture coordinates. Therefore, as shown in FIG. 10, in the V-Mesh compression method, a new attribute map having color information corresponding to the texture coordinates of the restored deformed mesh is regenerated through the attribute transfer process of the attribute transfer (426).

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

[0172] A new attribute map generated through attribute transfer (426) is grouped into GoF units to form an attribute map video, which is compressed using a video codec of the video encoding unit (429).

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

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

[0175] Figure 11 illustrates a decoding process of V-Mesh technology according to embodiments.

[0176] Fig. 11 illustrates the configuration and operation of the mesh video decoder (113) of the receiving device of Fig. 2. In addition, Fig. 11 can restore mesh data by performing the reverse process of the encoding process of Fig. 7. In the present disclosure, the receiving device of Fig. 11 may be referred to as a mesh data receiving device or decoder or a decoder of the receiving device or a V-Mesh decoder or a dynamic mesh decoder.

[0177] The elements of the receiving device illustrated in FIG. 11 may be implemented by hardware, software, a processor connected to a memory, and / or a combination thereof. That is, the elements of the receiving device illustrated in FIG. 11 may be implemented by hardware, software, firmware, or a combination thereof, including one or more processors or integrated circuits configured to communicate with one or more memories, although not illustrated in the drawing. One or more processors may perform at least one or more of the operations and / or functions of the elements of the receiving device illustrated in FIG. 11. In addition, one or more processors may operate or execute a set of software programs and / or instructions for performing the operations and / or functions of the elements of the receiving device illustrated in FIG. 11. The execution order of each block in FIG. 11 may be changed, some blocks may be omitted, and some blocks may be newly added.

[0178] Fig. 11 may largely include a demultiplexer (611), an atlas decoder (612), and a decoding unit (620).

[0179] According to embodiments, a bitstream (i.e., a compressed bitstream) of mesh data received by a receiver (not shown) may be demultiplexed into a base mesh bitstream (or a base mesh substream) after file / segment decapsulation, a displacement vector bitstream (or a displacement substream), a texture map bitstream (or an attribute map substream or a texture map substream), and / or an atlas bitstream in a demultiplexer (611). If the bitstream of mesh data is not encapsulated in a file form in the transmitter, the decapsulation process is omitted in the receiver. If the current mesh has inter-encoding applied, the base mesh bitstream may be a motion vector bitstream.

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

[0181] According to embodiments, the atlas bitstream may be decoded through Exp-Golomb coding of the atlas decoder (612), etc. At this time, the atlas may be information required for the mesh reconstruction process, and may mean information such as tiles and patches. In addition, the atlas data may mean data required for the mesh decoding, mesh reconstruction, etc. processes, and may include a segmentation method, a transformation method, a quantization method, the location and size of a patch within the atlas frame, etc.

[0182] According to embodiments, the base mesh bitstream is provided to a motion vector decoder (623) via a switching unit (621) or to a static mesh decoder (622).

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

[0184] According to embodiments, the motion vector decoder (623) can perform decoding on a motion vector bitstream in units of vertices or subgroups.

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

[0186] According to embodiments, the static mesh decoder (622) can decode the base mesh bitstream to restore connection information, vertex geometry information, texture coordinates (i.e., attribute geometry information), normal information, etc. of the base mesh. That is, the static mesh decoder (622) can restore a restored quantized base mesh, for example, connection information, vertex geometry information, vertex texture coordinates, etc. of the base mesh.

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

[0188] According to embodiments, the displacement sub-bitstream is provided to the arithmetic decoding unit (625) or the video decoding unit (627) through the switching unit (624) depending on the decoding method.

[0189] For example, if the decoding method is an arithmetic codec method, the arithmetic decoding unit (625) decodes the displacement sub-stream based on the arithmetic codec, and the inverse prediction unit (626) performs the inverse process of prediction on the decoded displacement information and then outputs it to the inverse quantization unit (629). As another example, if the decoding method is a 2D video codec method, the video decoding unit (627) decodes the displacement sub-stream based on the 2D video codec, and the image unpacking unit (628) unpacks the image of the decoded displacement video and then outputs it to the inverse quantization unit (629).

[0190] The displacement information provided from the above-mentioned inverse prediction unit (626) or image unpacking unit (628) is inversely quantized in the inverse quantization unit (629) and inversely transformed in the inverse linear lifting unit (630), and then restored as displacement information for each vertex (i.e., Recon. displacements).

[0191] According to embodiments, the mesh restoration unit (632) reconstructs and restores the deformed mesh (i.e., decoded mesh) using the restored displacement output from the inverse linear lifting unit (630) and the restored base mesh output from the base mesh restoration unit (631). That is, the dequantized restored base mesh is combined with the restored displacement information to generate the final decoded mesh. In the present disclosure, the final decoded mesh is referred to as a reconstructed deformed mesh.

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

[0193] According to embodiments, the restored decoded mesh and decoded attribute map can be utilized by the receiver as final mesh data that can be utilized by the user.

[0194] To summarize Fig. 11, the base mesh sub-stream can be decoded through a static mesh decoder (622) based on MEB (MPEG EdgeBreaker) technology depending on the basemesh type, for example, if it is an INTRA type, and as a result, connection information, vertex geometry information, vertex mapping information (texture coordinates), etc. of the base mesh can be restored.

[0195] In an encoder according to embodiments, when the texture parameterization method is orthoAtlas, the decoder can derive mapping information (texture coordinates) and attribute information (texture) connection information using vertex coordinates. The process of deriving mapping information (texture coordinates) and connection information can generate mapping information (texture coordinates) and attribute information (texture) connection information by calculating a homography transform of each face and then projecting the vertex based on the homography transform.

[0196] According to embodiments, when the base mesh type is INTER, motion information can be decoded through entropy decoding and inverse prediction processes. The decoded motion information is combined with a reference base mesh that has already been reconstructed and stored in a buffer to generate a reconstructed quantized base mesh for the current frame. An inverse quantization process can be performed on the reconstructed base mesh.

[0197] That is, the motion vector decoder derives the motion field of the base mesh of the current frame through motion estimation and compensation based on the base mesh in the reference frame when the mesh data in the bitstream is encoded based on inter prediction. The static mesh decoder decodes the base mesh when the mesh data in the bitstream is encoded based on intra prediction.

[0198] The displacement sub-stream is decoded into displacement video through the decoder of the video compression codec, for example, if it is compressed through a video codec, depending on the compression method used by the encoder, and then the image unpacking process is performed.

[0199] As another example, when compressed through arithmetic coding, the displacement sub-stream can be decoded into binarized syntax elements through arithmetic decoding, a contextual probability model (CPM) can be adaptively determined according to each bin of the syntax elements, and arithmetic decoding can be performed by predicting the occurrence probability of the bin through the CPM. The binarized syntax elements can be decoded through inverse binarization. Quantized displacement vector transform coefficients can be derived from the decoded syntax elements. As another example, when the displacement information type is INTER (when inter prediction is performed), an inverse inter prediction process is performed using reference information for the quantized displacement vector transform coefficients.

[0200] The quantized displacement vector transformation coefficient is restored to displacement information for each vertex through the inverse quantization, inverse transformation, and coordinate system transformation processes.

[0201] The restored base mesh and the restored displacement information are combined to generate the final decoded mesh. The attribute map substream is decoded by the decoder of the video compression codec used by the encoder, and then reconstructed into the final attribute map through processes such as color format conversion.

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

[0203] Fig. 12 illustrates a mesh data transmission device according to embodiments.

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

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

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

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

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

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

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

[0211] The displacement calculation unit (816) can perform mesh refinement on the restored base mesh. The displacement calculation unit (816) can calculate a displacement vector, which is a difference value in the vertex positions between the restored base mesh that has been refined and the fitted subdivision (or refined) mesh generated by the pre-processor (811). At this time, the displacement vector can be calculated as many times as the number of vertices of the refined mesh. The displacement calculation unit (816) can convert the displacement vector calculated in the 3D Cartesian coordinate system into a local coordinate system based on the normal vector of each vertex.

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

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

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

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

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

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

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

[0219] Fig. 13 illustrates a mesh data receiving device according to embodiments.

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

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

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

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

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

[0225] According to embodiments, the displacement vector video decoder (917) may decode the displacement vector bitstream as a video bitstream using a video codec or decode it using an arithmetic codec. That is, if the displacement vector bitstream is encoded using a video codec, for example, depending on the encoding codec type, a depacking process may be performed after decoding using the video codec. As another example, if encoded using arithmetic coding, arithmetic decoding may be performed on the displacement vector bitstream through a displacement vector arithmetic decoding unit, and if inter-screen prediction is performed, a residual value may be added to a reference displacement vector transform coefficient through inter-screen prediction to generate a current displacement vector transform coefficient.

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

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

[0228] According to embodiments, the texture map video decoder (919) can decode the texture map bitstream as a video bitstream using a video codec to restore the texture map. The restored texture map has color information for each vertex contained in the restored mesh, and the color value of each vertex can be obtained from the texture map using the texture coordinates of each vertex.

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

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

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

[0232] In the mesh data receiving device and method according to the embodiments, that is, the dynamic mesh content receiving device and method, decoding / rendering of dynamic mesh content may be required in various configurations depending on resources such as memory, decoder performance, display or producer's intention, etc. To this end, the mesh data transmitting device and method, that is, the dynamic mesh content transmitting device and method, may encode dynamic mesh content by applying scalable coding according to predefined and / or newly defined criteria such as Level of Detail (hereinafter, LoD) in consideration of these matters.

[0233] In such cases, since the dynamic mesh content receiving device and method must decode each data included in the dynamic mesh content to know whether scalable coding is applied or not, the dynamic content receiving device and method with restrictions related to scalable coding may result in unnecessary or abnormal operation and inefficient resource management.

[0234] To address this, the present disclosure proposes a V-DMC toolset profile definition and scalable coding signaling. According to embodiments, the present disclosure utilizes a flag in a V-DMC extension as a signaling technique for scalable mesh coding in MPEG V-DMC. In addition, the present disclosure defines a V-DMC toolset profile. In the present disclosure, scalable coding may be referred to as scalable video coding, and scalable decoding may be referred to as scalable video decoding.

[0235] Hereinafter, the present disclosure describes a signaling method capable of supporting a scalable architecture and the related syntax and semantics. It also describes the operation of a transmitter and receiver applying the method.

[0236] In the present disclosure, each vertex constituting the mesh represents a position in three-dimensional space, and is expressed, for example, by x, y, z coordinates (i.e., canonical coordinate system). And, a polygon may be a triangle or a square. In the present disclosure, vertex, apex, and point may be used with the same meaning. That is, a vertex has a coordinate in three-dimensional space, and a triangular or square polygon can be created through a connection between a plurality of vertices. In addition, V-DMC referred to in the present disclosure may also be referred to as V-mesh, and the two terms are expressions used with the same meaning.

[0237] Next, in order to support the scalable structure of mesh data, the encoding process and signaling method of mesh data in the encoder of the transmitting device are described, and the process of performing scalable decoding based on signaling information in the decoder of the receiving device is described in detail.

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

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

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

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

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

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

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

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

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

[0247] The above mesh subdivision unit (11018) subdivides the base mesh simplified by the mesh simplification unit (11011). That is, the mesh subdivision unit (11018) can perform mesh subdivision on the base mesh to generate additional vertices. Depending on the subdivision method, vertex connection information, texture coordinates, and texture coordinate connection information including the added vertices can be generated. At this time, depending on the subdivision method, geometry information connection information, texture coordinate connection information, and texture coordinates can be implicitly derived and generated. According to embodiments, the mesh subdivision unit (11018) can perform subdivision through a method such as mid-edge, Loop, or Catmul&Clark.

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

[0249] According to embodiments, LoD0, LoD1, … LoDn can be defined as follows.

[0250] LoD0 = R0

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

[0252] …

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

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

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

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

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

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

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

[0260] According to embodiments, the base mesh quantized in the mesh quantization unit (11013) may be output to a motion vector encoder (11015) or a static mesh encoder (11016) via a switching unit (11014). According to embodiments, the base mesh is output to the motion vector encoder (11015) via the switching unit (11014) when inter-encoding is performed on the corresponding mesh frame, and is output to the static mesh encoder (11016) via the switching unit (11014) when intra-encoding is performed on the corresponding mesh frame. The motion vector encoder (11015) may be referred to as a motion encoder.

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

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

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

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

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

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

[0267] According to embodiments, the displacement vector encoder (11022) may perform encoding on the displacement vector or displacement vector transform coefficients output from the displacement vector calculation unit (11020) or the displacement vector coordinate system transformation unit (11021). In the present disclosure, the displacement vector encoder (11022) may perform encoding through a 2D video codec-based encoder such as H.264, HEVC, VVC, etc., and / or a zero run length encoder, and / or an arithmetic encoder, etc. In this case, the displacement vector encoder (11022) may selectively use only one of the 2D video codec-based encoding method, the zero run length encoding method, and the arithmetic encoding method, or may use one or more various combinations to encode the displacement vector or the quantized displacement vector transform coefficients. For example, when the encoding method is a video codec-based encoding, the displacement vector encoder (11022) may encode the displacement vector or the quantized displacement vector transform coefficients by packing them into a frame. That is, in the displacement vector encoder (11022), the displacement vector transform coefficients can be packed into a 2D image and then encoded using a 2D video codec (i.e., a video compression codec), or zero run-length encoded, or arithmetic encoded to generate a displacement vector video bitstream.

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

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

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

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

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

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

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

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

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

[0277] According to embodiments, the atlas encoder (11029) may generate an atlas bitstream by encoding atlas information (or atlas data). Then, the atlas bitstream generated through the atlas information encoding is transmitted to a multiplexer (not shown). In the present disclosure, the atlas may be information required in a mesh reconstruction process, and may mean information such as tiles and patches. In addition, the atlas information may mean data required in processes such as 2D mapping for a 3D object, texture mapping-related information, mesh decoding, and mesh restoration, and may include additional information such as a segmentation method, a transformation method, a quantization method, and the position and size of a patch within an atlas frame. In the present disclosure, the atlas information may be encoded through Exp-Golomb coding of the atlas encoder (11029), etc.

[0278] In the present disclosure, a basemesh bitstream output to a motion vector encoder (11015) or a static mesh encoder (11016) may be referred to as basemesh data or a basemesh sub-bitstream. In addition, a displacement vector bitstream output from a displacement vector encoder (11022) may be referred to as displacement vector data or displacement data or displacement information or a displacement vector sub-bitstream. At this time, the displacement data may be displacement data encoded based on a video codec or displacement data encoded based on an arithmetic codec. In the present disclosure, displacement data encoded based on a video codec may be referred to as video codec-based displacement data, and displacement data encoded based on an arithmetic codec may be referred to as displacement data encoded based on an arithmetic codec. Additionally, the texture map bitstream output from the texture map encoder (11027) may be referred to as texture map data, attribute data, attribute information, attribute video data, texture map sub-bitstream, or attribute sub-bitstream. In addition, the atlas bitstream output from the atlas encoder (11029) may be referred to as atlas data or atlas sub-bitstream.

[0279] According to embodiments, when an encoded texture map and encoded displacement data are packed into one frame and output as a PVD (Packed Video Data) bitstream, the PVD bitstream may be referred to as PVD data packed video data or packed video data sub-bitstream. In the present disclosure, the PVD bitstream may be generated from a texture map encoder (11027) or may be generated from a separate block / module.

[0280] According to embodiments, a multiplexer (not shown) can multiplex an input basemesh bitstream, a displacement vector bitstream, a texture map bitstream, and an atlas bitstream into one bitstream (i.e., a dynamic mesh bitstream) and transmit the multiplexed bitstream to a receiving device. According to embodiments, the multiplexed bitstream can further include a PVD bitstream and a V3C / V-DMC parameter set (VPS). In the present disclosure, a bitstream multiplexed and output by the multiplexer can be referred to as a dynamic mesh bitstream or a V-DMC bitstream. In the present disclosure, the dynamic mesh bitstream or the V-DMC bitstream may be configured in the multiplexer or may be configured in a separate block / module.

[0281] Additionally, the multiplexed bitstream may be encapsulated into one or more tracks of a file and transmitted to a receiving device. According to embodiments, the multiplexed bitstream or file may be transmitted over a network or stored in a digital storage medium. Here, the network may include a broadcasting network and / or a communication network, and the digital storage medium may include various storage media such as USB, SD, CD, DVD, Blu-ray, HDD, and SSD.

[0282] FIG. 15 is a diagram showing an example of a dynamic mesh bitstream structure transmitted from a transmitting device of the present disclosure. In the present disclosure, the dynamic mesh bitstream (referred to as a V-DMC bitstream or a bitstream of mesh data) of FIG. 15 is, as an embodiment, generated and output by one of the encoding devices / encoding methods of FIG. 1, FIG. 2, FIG. 3, FIG. 7, FIG. 12, or FIG. 14. In the present disclosure, the V-DMC bitstream can be transmitted / received in either a V3C unit stream format or a V3C sample stream format. The dynamic mesh bitstream of the present disclosure can follow the V3C bitstream structure defined in the V3C codec specification (ISO / IEC 23090-5). In this case, the existing V3C bitstream structure may be followed, but some V3C units may not be used, and some structures for V-DMC only, such as V-DMC extensions, may be followed.

[0283] That is, dynamic mesh content can be encoded into a bitstream structure as in FIG. 15 and transmitted to a receiving device. In particular, the present disclosure can use a sample stream data unit used when encoding V3C content of the V3C codec specification (ISO / IEC 23090-5) as in FIG. 15.

[0284] A bitstream (referred to as a V-DMC bitstream or dynamic mesh bitstream) transmitted from a transmitting device to a receiving device of the present disclosure may be composed of a sample stream DMC header and a plurality of sample stream DMC units. In the present disclosure, the sample stream DMC header may be referred to as a sample stream header, and the sample stream DMC unit may be referred to as a sample stream data unit.

[0285] At this time, if the sample stream DMC unit follows the V3C codec specification (ISO / IEC 23090-5), the sample stream DMC unit can be composed of V3C sample stream size information and a V3C unit. The V3C unit is again composed of a V3C unit header (V3C_unit_header) and a V3C unit payload (V3C_unit_payload).

[0286] The above V3C sample stream size information specifies the size of the subsequent V3C unit in bytes.

[0287] The above V3C unit header includes type information (vuh_unit_type) indicating the type of data carried by the corresponding V3C unit payload. The above V3C unit payload can carry one of a V3C / V-DMC parameter set (VPS), Atlas Data (AD), Base Mesh Data (BMD), Displacement Data / Geometry Video Data (DD / GVD), Attribute Video Data (AVD), and Packing Video Data (PVD) according to the type information (vuh_unit_type).

[0288] Here, VPS may include parameter set information such as decoder configuration information related to mesh encoding / decoding and sequence header. Atlas data (AD) may include additional information such as 2D mapping or texture mapping for 3D objects. Base mesh data (BMD) is compressed base mesh data for mesh encoding / decoding. Attribute video data (AVD) is attribute or texture data (or texture map information) compressed using a video codec. Packed video data (PVD) is packed texture map and displacement information compressed using a video codec. And, DD / GVD represents displacement data (or displacement information), where DD represents displacement data that is arithmetic coded, and GVD represents displacement data that is encoded using a video codec. In the present disclosure, displacement data or displacement information may mean displacement data encoded with a video codec or displacement data encoded with arithmetic coding.

[0289] The present disclosure provides, as an embodiment, a method of distinguishing between type information (vuh_unit_type) of arithmetic-coded displacement data and video codec-based coded displacement data. In this case, the V3C unit payload may carry one of VPS, atlas data (AD), base mesh data (BMD), video codec-based displacement video data (GVD), attribute video data (AVD), packed video data (PVD), and arithmetic codec-based displacement data (DD) according to the type information (vuh_unit_type). That is, the values ​​of type information (vuh_unit_type) of displacement data (GVD) compressed (i.e., encoded) using a video codec and displacement data (DD) compressed (i.e., encoded) based on arithmetic codec may be assigned differently.

[0290] That is, the V3C unit header of the present disclosure includes type information (vuh_unit_type) of the V3C unit header, and the vuh_unit_type is V3C unit type information indicating the type of data carried by the corresponding V3C unit payload. For example, if the vuh_unit_type field indicates VPS (V3C_VPS), the V3C unit payload includes VPS including overall encoding information of the bitstream, and if it indicates atlas data (V3C_AD), it includes an atlas sub-bitstream carrying the atlas data. And if it indicates attribute video data (V3C_AVD), it includes an attribute video sub-bitstream carrying the attribute video data. And if the type information (vuh_unit_type) of the V3C unit header indicates PVD (V3C_PVD), the V3C unit payload includes a packed video sub-bitstream (video_sub_bitstream()) carrying packed video data. In addition, if the vuh_unit_type field indicates displacement data (V3C_GVD / DD), the V3C unit payload may include displacement vector sub-bitstreams carrying displacement video data (or geometry video data) encoded based on a video codec or displacement data encoded based on an arithmetic codec.

[0291] In the syntax structure of the present disclosure, each syntax element may be referred to as a field. Furthermore, in the syntax structure of the present disclosure, the name "syntax element" may be omitted or referred to as a field. For example, "vuh_unit_type," the "vuh_unit_type" syntax element, and the "vuh_unit_type" field have the same meaning. The same applies to other syntax elements.

[0292] Fig. 16 is a diagram showing an example of a syntax structure of profile_tier_level() included in a VPS according to embodiments. The profile toolset constraints information carried by the profile_tier_level() syntax structure of Fig. 16 includes information on syntax elements that define or influence a V3C / V-DMC toolset profile component. In other words, this syntax structure has a direct relationship with syntax elements that are constrained to comply with specific toolset profile components of a V3C / V-DMC codec.

[0293] In Figure 16, ptl_tier_flag specifies the tile context for interpretation of ptl_level_idc.

[0294] ptl_profile_codec_group_idc represents the codec group profile component that the CVS (coded V3C sequence) follows.

[0295] ptl_profile_toolset_idc represents the toolset combination profile component that CVS follows.

[0296] ptl_profile_reconstruction_idc represents the reconstruction profile component that CVS follows.

[0297] ptl_max_decodes_idc specifies the number of sub-bitstreams that a video decoder instantiation is required to have to conform to CVS.

[0298] ptl_level_idc indicates the level that CVS follows.

[0299] ptl_num_sub_profiles represents the number of ptl_sub_profile_idc[i] syntax elements.

[0300] If ptl_extended_sub_profile_flag is 1, it specifies that the ptl_sub_profile_idc[i] syntax elements, if present, should be represented in 64 bits.

[0301] If ptl_extended_sub_profile_flag is 0, it specifies that the ptl_sub_profile_idc[i] syntax elements, if present, should be represented in 32 bits.

[0302] ptl_sub_profile_idc[i] represents the i-th interoperability metadata.

[0303] If ptl_toolset_constraints_present_flag is 1, it specifies that an additional structure, profile_toolset_constraints_information(), is present in the bitstream.

[0304] If ptl_toolset_constraints_present_flag is 0, it specifies that the additional structure profile_toolset_constraints_information() is not present in the bitstream.

[0305] FIG. 17 is a diagram showing an example of the syntax structure of asps_vdmc_extension( ) included in an atlas sequence parameter set according to embodiments. In the present disclosure, an atlas sequence parameter set (ASPS) may be included in atlas data.

[0306] According to embodiments, the present disclosure may signal information (e.g., asve_attribute_scalable_coding_flag and asve_packed_video_scalable_coding_flag) indicating whether scalable video coding is applied through asps_vdmc_extension( ). According to embodiments, the present disclosure may signal whether scalable video coding is applied to attribute data and packed video data through asps_vdmc_extension( ).

[0307] Referring to FIG. 17, asve_num_attribute_video may indicate the number of attribute video data units carrying attribute data. According to embodiments, asps_vdmc_extension() of the present disclosure may include asve_attribute_scalable_coding_flag[ i ] as many times as the value (i) of asve_num_attribute_video.

[0308] If asve_attribute_scalable_coding_flag[ i ] is equal to 1, it specifies that scalable video coding is applied to code the attribute video data unit with index i.

[0309] If asve_attribute_scalable_coding_flag[ i ] is equal to 0, it specifies that scalable coding is not used to compress the attribute video data unit with index i.

[0310] According to embodiments, asps_vdmc_extension() of the present disclosure may further include asve_packed_video_scalable_coding_flag.

[0311] If asve_packed_video_scalable_coding_flag is equal to 1, it specifies that scalable video coding is used to code the packed video data unit.

[0312] If asve_packed_video_scalable_coding_flag[ i ] is equal to 0, it specifies that scalable video coding is not used to compress the packed video data units.

[0313] In the present disclosure, when scalable video coding is used for packed video data units, information included in the packing information syntax element is applied to the base layer.

[0314] Additionally, in the present disclosure, asve_attribute_scalable_coding_flag and asve_packed_video_scalable_coding_flag can be used to indicate V-DMC toolset profile components.

[0315] FIG. 18 is a diagram showing an example of how asve_attribute_scalable_coding_flag and asve_packed_video_scalable_coding_flag are used to indicate V-DMC toolset profile components according to embodiments. That is, FIG. 18 shows an example of how the asve_attribute_scalable_coding_flag syntax element and the asve_packed_video_scalable_coding_flag syntax element can be used to indicate V-DMC toolset profile components.

[0316] Referring to FIG. 18, asve_attribute_scalable_coding_flag and asve_packed_video_scalable_coding_flag are both 0 in V-DMC main and V-DMC main still, and can be 0 or 1 in V-DMC extended and V-DMC extended still.

[0317] That is, in the V-DMC Main and V-DMC Main Still profiles, scalable video coding is not always applied, and in the V-DMC Extended and V-DMC Extended Still profiles, scalable video coding may or may not be applied. In other words, in the V-DMC Extended and V-DMC Extended Still profiles, scalable video coding can be applied selectively.

[0318] FIG. 19 is a diagram showing an example of the syntax structure of vps_vdmc_extension ( ) included in VPS according to embodiments.

[0319] According to embodiments, the present disclosure may signal information (e.g., vps_ext_attribute_scalable_coding_flag and vps_ext_packed_video_scalable_coding_flag) indicating whether scalable video coding is applied through vps_vdmc_extension ( ). According to embodiments, the present disclosure may signal whether scalable video coding is applied to attribute data and packed video data through vps_vdmc_extension ( ).

[0320] Referring to FIG. 19, ai_attribute_count represents the number of attributes associated with an atlas having an atlas ID j. According to embodiments, the vps_vdmc_extension ( ) of the present disclosure may include vps_ext_attribute_scalable_coding_flag[ j ][ i ] as many times as the value (i) of ai_attribute_count. Here, j represents an atlas ID.

[0321] If vps_ext_attribute_scalable_coding_flag[ j ][ i ] is equal to 1, it specifies that scalable video coding is applied to the attribute video data unit with index i for the atlas with atlas ID j.

[0322] If vps_ext_attribute_scalable_coding_flag[ j ][ i ] is equal to 0, it specifies that scalable video coding is not used to compress the attribute video data unit with index i for the atlas with atlas ID j.

[0323] According to embodiments, the present disclosure may further include vps_vdmc_extension () vps_ext_packed_video_scalable_coding_flag[ j ].

[0324] If vps_ext_packed_video_scalable_coding_flag[ j ] is equal to 1, it specifies that scalable video coding is used to code the packed video data units for the atlas with atlas ID j.

[0325] If vps_ext_packed_video_scalable_coding_flag[ j ] is equal to 0, it specifies that scalable video coding is not used to compress packed video data units for the atlas with atlas ID j.

[0326] In the present disclosure, when scalable video coding is used for packed video data units, information included in the packing information syntax element is applied to the base layer.

[0327] Additionally, in the present disclosure, vps_ext_attribute_scalable_coding_flag and vps_ext_packed_video_scalable_coding_flag can be used to indicate V-DMC toolset profile components.

[0328] FIG. 20 is a diagram showing an example of how vps_ext_attribute_scalable_coding_flag and vps_ext_packed_video_scalable_coding_flag are used to indicate V-DMC toolset profile components according to embodiments. That is, FIG. 20 shows an example of how the vps_ext_attribute_scalable_coding_flag syntax element and the vps_ext_packed_video_scalable_coding_flag syntax element can be used to indicate V-DMC toolset profile components.

[0329] Referring to FIG. 20, the vps_ext_attribute_scalable_coding_flag syntax element and the vps_ext_packed_video_scalable_coding_flag syntax element are both 0 in V-DMC main and V-DMC main still, and can be 0 or 1 in V-DMC extended and V-DMC extended still.

[0330] That is, in the V-DMC Main and V-DMC Main Still profiles, scalable video coding is not always applied, and in the V-DMC Extended and V-DMC Extended Still profiles, scalable video coding may or may not be applied. In other words, in the V-DMC Extended and V-DMC Extended Still profiles, scalable video coding can be applied selectively.

[0331] The following describes the definition of the V-DMC toolset profile proposed in this disclosure.

[0332] Figure 21 is a diagram illustrating examples of V-DMC toolset profile components according to embodiments. That is, Figure 21 illustrates examples of available toolset profile components. More specifically, Figure 21 defines the corresponding toolset profile components according to the ptl_profile_toolset_idc value. This table shows which profile each ptl_profile_toolset_idc value is associated with.

[0333] In Figure 21, ptl_profile_toolset_idc represents a toolset combination profile component that CVS follows. That is, ptl_profile_toolset_idc is a toolset profile identifier, and can be combined with ptc_one_v3c_frame_only_flag to uniquely distinguish each profile component.

[0334] ptc_one_v3c_frame_only_flag can identify a toolset combination profile component by combining with ptl_profile_pcc_toolset_idc, and indicates whether the identified toolset combination profile component is dynamic / static. That is, if the value of ptc_one_v3c_frame_only_flag is 0, the type of the toolset profile component is dynamic, and if it is 1, it indicates static.

[0335] For example, if the value of ptl_profile_pcc_toolset_idc is 0 and the value of ptc_one_v3c_frame_only_flag is 0, it indicates that the toolset profile component is of dynamic type V-PCC basic. If the value of ptl_profile_pcc_toolset_idc is 0 and the value of ptc_one_v3c_frame_only_flag is 1, it indicates that the toolset profile component is of static type V-PCC basic stil.

[0336] As another example, if the value of ptl_profile_pcc_toolset_idc is 128 and the value of ptc_one_v3c_frame_only_flag is 0, the toolset profile component is a dynamic type V-DMC main. If the value of ptl_profile_pcc_toolset_idc is 128 and the value of ptc_one_v3c_frame_only_flag is 1, the toolset profile component is a static type V-PCC main stil.

[0337] As another example, if the value of ptl_profile_pcc_toolset_idc is 129 and the value of ptc_one_v3c_frame_only_flag is 0, the toolset profile component is of dynamic type V-DMC extended. If the value of ptl_profile_pcc_toolset_idc is 129 and the value of ptc_one_v3c_frame_only_flag is 1, the toolset profile component is of static type V-PCC extended stil.

[0338] In embodiments, V-DMC main simplifies the operation of the atlas decoder by restricting the patch type to intra-only, and allows for the separation of V3C attribute video components from the atlas metadata by removing attribute mesh patches and limiting the number of tile attributes to 1. In addition, V-DMC extended is a profile that requires support from all atlas coding tools defined in this document.

[0339] The following describes the V-DMC main, V-DMC main still, V-DMC extended, and V-DMC extended still toolset profile components. In this disclosure, the V-DMC toolset profile components must comply with the additional constraints described in FIG. 22.

[0340] FIG. 22 is a diagram showing examples of syntax element values ​​allowed for V-DMC toolset profile components according to embodiments. That is, FIG. 22 shows examples of V-DMC toolset profile component values ​​proposed in the present disclosure.

[0341] According to embodiments, V-DMC main (ptl_profile_toolset_idc = 128 and ptc_one_v3c_frame_only_flag = 0) or V-DMC main still (ptl_profile_toolset_idc = 128 and ptc_one_v3c_frame_only_flag = 1), V-DMC extended (ptl_profile_toolset_idc = 129 and ptc_one_v3c_frame_only_flag = 0) or V-DMC extended still (ptl_profile_toolset_idc = 129 and ptc_one_v3c_frame_only_flag = 1) toolset profile components may follow syntax element restrictions as shown in FIG. 22.

[0342] Referring to Figure 22, ptl_profile_toolset_idc has a value of 128 in V-DMC Main and V-DMC Main Still, and a value of 129 in V-DMC Extended and V-DMC Extended Still. ptl_profile_toolset_idc represents the toolset combination profile component that CVS follows, and is included in VPS.

[0343] ptc_one_v3c_frame_only_flag has the value 0 for V-DMC main, and 1 for V-DMC main still, V-DMC extended, and V-DMC extended still. Here, 0 means that scalable video coding is not applied, and 1 means that scalable video coding is applied. ptc_one_v3c_frame_only_flag indicates that the profile supports only a single V3C composition unit (a single frame).

[0344] asps_vdmc_extension_present_flag has the value 1 in V-DMC main, V-DMC main still, V-DMC extended, and V-DMC extended still. When asps_vdmc_extension_present_flag is equal to 1, it specifies that the asps_vdmc_extension() syntax structure is present in the atlas_sequence_parameter_set_rbsp() syntax structure. When asps_vdmc_extension_present_flag is equal to 0, it specifies that this syntax structure does not exist. And, for V-DMC bitstream, the value of asps_vdmc_extension_present_flag is 1.

[0345] vps_packed_video_present_flag has values ​​of 0 and 1 in V-DMC main, V-DMC main still, V-DMC extended, and V-DMC extended still. Here, 0 and 1 indicate that scalable video coding can be optionally applied. If vps_packed_video_present_flag[j] is equal to 0, it indicates that the atlas with atlas ID j does not contain packed video data associated with it. And, if vps_packed_video_present_flag[j] is equal to 1, it indicates that the atlas with atlas ID j contains packed video data associated with it.

[0346] vps_map_count_minus1 has a value of 0 in V-DMC main, V-DMC main still, V-DMC extended, and V-DMC extended still. vps_map_count_minus1[j] + 1 represents the number of maps used to encode the geometry data and attribute data of the atlas with atlas ID j.

[0347] vps_occupancy_video_present_flag has a value of 0 in V-DMC main, V-DMC main still, V-DMC extended, and V-DMC extended still. If vps_occupancy_video_present_flag[j] is equal to 0, it indicates that the atlas with atlas ID j has no occupancy video data associated with it. If vps_occupancy_video_present_flag[j] is equal to 1, it indicates that the atlas with atlas ID j has occupancy video data associated with it.

[0348] vps_geometry_video_present_flag has the values ​​0 and 1 in V-DMC main, V-DMC main still, V-DMC extended, and V-DMC extended still. If vps_geometry_video_present_flag is equal to 0, it indicates that the atlas with atlas ID j has no geometry video data associated with it. If vps_geometry_video_present_flag is equal to 1, it indicates that the atlas with atlas ID j has geometry video data associated with it.

[0349] vps_attribute_video_present_flag has a value of 1 in V-DMC main, V-DMC main still, V-DMC extended, and V-DMC extended still. If vps_attribute_video_present_flag is equal to 0, it indicates that the atlas with atlas ID j has no attribute video data associated with it. If vps_attribute_video_present_flag is equal to 1, it indicates that the atlas with atlas ID j has attribute video data associated with it.

[0350] vps_atlas_count_minus1 has a value of 0 in V-DMC main, V-DMC main still, V-DMC extended, and V-DMC extended still. vps_atlas_count_minus1 + 1 represents the total number of atlases supported in the current bitstream.

[0351] afps_vdmc_extension_present_flag has the value 1 in V-DMC main, V-DMC main still, V-DMC extended, and V-DMC extended still. When afps_vdmc_extension_present_flag is equal to 1, it specifies that the afps_vdmc_extension() syntax structure exists within the atlas_frame_parameter_set_rbsp() syntax structure. When afps_vdmc_extension_present_flag is equal to 0, it specifies that this syntax structure does not exist. afps_vdmc_extension_present_flag can be 1 in the case of a V-DMC bitstream.

[0352] asve_attribute_scalable_coding_flag has the value 0 for V-DMC main and V-DMC main still, and 0 or 1 for V-DMC extended and V-DMC extended still. If asve_attribute_scalable_coding_flag[ i ] is equal to 1, it specifies that scalable video coding is applied to the attribute video data unit with index i, and if asve_attribute_scalable_coding_flag[ i ] is equal to 0, it specifies that scalable video coding is not used to compress the attribute video data unit with index i.

[0353] asve_packed_video_scalable_coding_flag has the value 0 for V-DMC main and V-DMC main still, and 0 and 1 for V-DMC extended and V-DMC extended still. If asve_packed_video_scalable_coding_flag is equal to 1, it specifies that scalable video coding is used to code the packed video data unit. If asve_packed_video_scalable_coding_flag[ i ] is equal to 0, it specifies that scalable video coding is not used to compress the packed video data unit.

[0354] vps_ext_attribute_scalable_coding_flag has the value 0 for V-DMC main and V-DMC main still, and 0 and 1 for V-DMC extended and V-DMC extended still. If vps_ext_attribute_scalable_coding_flag[ j ][ i ] is equal to 1, it specifies that scalable video coding is applied to the attribute video data unit with index i for the atlas with atlas ID j. If vps_ext_attribute_scalable_coding_flag[ j ][ i ] is equal to 0, it specifies that scalable video coding is not used to compress the attribute video data unit with index i for the atlas with atlas ID j.

[0355] vps_ext_packed_video_scalable_coding_flag has the value 0 for V-DMC main and V-DMC main still, and 0 and 1 for V-DMC extended and V-DMC extended still. If vps_ext_packed_video_scalable_coding_flag[ j ] is equal to 1, it specifies that scalable video coding is used to code the packed video data unit for the atlas with atlas ID j. If asve_packed_video_scalable_coding_flag[ j ] is equal to 0, it specifies that scalable video coding is not used to compress the packed video data unit for the atlas with atlas ID j.

[0356] FIG. 23 is a diagram showing another example of a receiving device according to embodiments. The receiving device of FIG. 23 may be referred to as a receiver or a dynamic mesh content receiving device. The receiving device of FIG. 23 may correspond to the receiving device of FIG. 1, the receiving device of FIG. 11, or the receiving device of the receiving device of FIG. 13. Therefore, parts not described in FIG. 23 will refer to the description of the receiving device of FIG. 1, the receiving device of FIG. 11, or the receiving device of FIG. 13. The elements of the receiving device illustrated in FIG. 23 may be implemented by hardware, software, a processor connected to a memory, and / or a combination thereof. That is, the elements of the receiving device of FIG. 23 may be implemented by hardware, software, firmware, or a combination thereof, including one or more processors or integrated circuits configured to communicate with one or more memories, although not illustrated in the drawing. One or more processors may perform at least one of the operations and / or functions of the elements of the receiving device of FIG. 23 described above. Furthermore, one or more processors may operate or execute a set of software programs and / or instructions for performing the operations and / or functions of the elements of the receiving device of FIG. 23.

[0357] The scalable video decoding proposed in this disclosure may correspond to the operation within the mesh data decoding module of FIG. 23, and the receiver operation according to the proposed method is as follows. In this disclosure, the mesh data decoding module may be referred to as a V-DMC decoder.

[0358] According to embodiments, a bitstream of mesh data (also referred to as a dynamic mesh bitstream or a bitstream of mesh data or a dynamic bitstream) encapsulated in a file from a transmitting device and delivered to a receiving device via a delivery module is decapsulated in a file decapsulation module. If the bitstream of mesh data is not encapsulated in a file form from the transmitting device, the decapsulation process is omitted at the receiving device.

[0359] That is, when the stored and / or received dynamic mesh content passes through the delivery module and the file / segment decapsulation module, it can be in a form similar to the V-DMC bitstream structure of FIG. 15.

[0360] And, the base mesh bitstream, atlas bitstream, displacement vector bitstream, attribute bitstream and / or packed video data bitstream within the bitstream configured as in FIG. 15 can be separated in the mesh data decoding module and then decoded through each decoder.

[0361] According to embodiments, a bitstream parser (not shown) of a mesh data decoding module may serve to parse a V-DMC bitstream (or dynamic mesh content bitstream). That is, a V3C unit header and a V3C unit payload constituting the bitstream may be parsed to obtain a base mesh bitstream, an atlas bitstream, a displacement vector bitstream, an attribute bitstream, and / or a packed video data bitstream, respectively, and may be decoded by each decoder. In addition, the bitstream parser of the mesh data decoding module may parse a V3C unit header and a V3C unit payload to obtain data in which type information (i.e., vuh_unit_type) included in the V3C unit header corresponds to V3C_VPS, i.e., VPS data.

[0362] According to embodiments, a receiver including a mesh data decoding module checks whether ptl_profile_toolset_idc in a received bitstream is 128 or 129 to confirm that the bitstream is a bitstream encoded with V-DMC. That is, the mesh data decoding module parses VPS data to check whether ptl_profile_toolset_idc is 128 or 129. If ptl_profile_toolset_idc is 128 or 129, it means that the bitstream is a bitstream encoded with V-DMC by an encoder of a transmitting device.

[0363] According to embodiments, receivers including a mesh data decoding module (or V-DMC decoder) are divided into two types: V-DMC Main profile compliant receivers capable of both video and still image playback, and V-DMC Main Still profile compliant receivers capable of only still image playback (e.g., V-DMC photo viewer, V-DMC image player).

[0364] According to embodiments, for a V-DMC Main profile compliant receiver, a function capable of decoding a V-DMC bitstream having a syntax element value corresponding to the V-DMC Main profile of FIG. 22 is supported in a mesh data decoding module. For example, in the V-DMC Main profile of FIG. 22, the ptl_profile_toolset_idc syntax element is 128, the ptc_one_v3c_frame_only_flag syntax element is 0, 1, the asps_vdmc_extension_present_flag syntax element is 1, the vps_packed_video_present_flag syntax element is 1, the vps_map_count_minus1 syntax element is 0, 1, the vps_occupancy_video_present_flag syntax element is 0, the vps_geometry_video_present_flag syntax element is 0, the vps_attribute_video_present_flag syntax element is 0, 1, and the vps_atlas_count_minus1 syntax element is 0. The afps_vdmc_extension_present_flag syntax element has a value of 1, the asve_attribute_scalable_coding_flag syntax element has a value of 0, the asve_packed_video_scalable_coding_flag syntax element has a value of 0, the vps_ext_attribute_scalable_coding_flag syntax element has a value of 0, the vps_ext_packed_video_scalable_coding_flag syntax element has a value of 0, and the vuh_unit_type syntax element allows V3C_VPS, V3C_AD, V3C_GVD, V3C_AVD, V3C_PVD, and V3C_BMD.Here, 0 indicates that the function corresponding to the syntax element is not applied (or allowed) to a V-DMC Main profile compliant receiver, 1 indicates that it is applied (or allowed), and 0,1 indicates that it is optionally applied (or allowed).

[0365] According to embodiments, for a V-DMC Main Still profile compliant receiver, a function capable of decoding a V-DMC bitstream having a syntax element value corresponding to the V-DMC Main Still profile of FIG. 22 is supported in a mesh data decoding module.

[0366] According to embodiments, a receiver including a mesh data decoding module (or V-DMC decoder) can be further classified into a V-DMC extended profile compliant receiver supporting the V-DMC Extended profile and a V-DMC extended still profile compliant receiver supporting the V-DMC Extended Still profile.

[0367] According to embodiments, for a V-DMC extended profile compliant receiver, a function capable of decoding a V-DMC bitstream having a syntax element value corresponding to the V-DMC extended profile of FIG. 22 is supported in a mesh data decoding module.

[0368] According to embodiments, for a V-DMC extended still profile compliant receiver, a function capable of decoding a V-DMC bitstream having a syntax element value corresponding to the V-DMC extended still profile of FIG. 22 is supported in a mesh data decoding module.

[0369] In FIG. 22, asve_attribute_scalable_coding_flag and asve_packed_video_scalable_coding_flag are both 0 for V-DMC main and V-DMC main still, and can be 0 or 1 for V-DMC extended and V-DMC extended still. That is, it indicates that scalable video coding is not applied (or allowed) in the V-DMC Main and V-DMC Main Still profiles, and that scalable video coding may or may not be applied (or allowed) in the V-DMC Extended and V-DMC Extended Still profiles. In other words, it indicates that scalable video coding can be selectively applied (or allowed) in the V-DMC Extended and V-DMC Extended Still profiles. This indicates that V-DMC Main profile compliant receivers and V-DMC Main Still profile compliant receivers do not support scalable video decoding, while V-DMC extended profile compliant receivers and V-DMC extended still profile compliant receivers optionally support scalable video decoding. For example, V-DMC extended profile compliant receivers and V-DMC extended still profile compliant receivers can apply scalable video decoding to the attribute video data unit with index i if the value of asve_attribute_scalable_coding_flag[ i ] is 1.As another example, V-DMC extended profile compliant receivers and V-DMC extended still profile compliant receivers can apply scalable video decoding to packed video data units if the value of asve_packed_video_scalable_coding_flag is 1. That is, the specified constraints for each toolset ensure decoding efficiency and conformance by preventing the receiver from activating unnecessary or unsupported features.

[0370] In the present disclosure, a mesh data decoding module of a V-DMC extended profile compliant receiver must be capable of decoding a bitstream encoded with the V-DMC Main profile.

[0371] According to embodiments, the syntax element values ​​corresponding to each V-DMC toolset profile shown in FIG. 22 are only one embodiment and different values ​​can be specified depending on the situation. For example, vps_packed_video_present_flag can only have a value of 0 in the V-DMC Main and V-DMC Main Still profiles, and can be constrained to have values ​​of 0 and 1 in the V-DMC Extended and V-DMC Extended Still profiles.

[0372] The following describes the reconstruction profile components for V-DMC of the present disclosure.

[0373] For V-DMC, three restoration profiles are proposed: the first one is a profile that does not include conditionally-invoked restoration processes and post-restoration processes (e.g., V-DMC Rec0), the second one is a profile that does not include post-restoration processes (e.g., V-DMC Rec1), and the last one supports all restoration and post-restoration processes (e.g., V-DMC Rec2).

[0374] FIG. 24 is a diagram showing examples of restoration profile components defined for V-DMC according to embodiments.

[0375] In Figure 24, ptl_profile_reconstruction_idc represents a reconstruction profile component that CVS is recommended to adhere to. Decoders within the mesh data decoding module may choose to use a reconstruction profile different from that indicated in the bitstream. In Figure 24, ptl_profile_reconstruction_idc is included in profile_tier_level() of VPS, as an example.

[0376] For example, if the value of ptl_profile_reconstruction_idc is 3, the reconstruction profile component represents V-DMC Rec0, if it is 4, the reconstruction profile component represents V-DMC Rec1, and if it is 5, the reconstruction profile component represents V-DMC Rec2.

[0377] At this time, as examples of supported restoration operations for each V-DMC restoration profile component, texture coordinate derivation, inverse image packing, inverse quantization, inverse transform, normal, tangent, bitangent, vertex coordinates reconstruction, and texture coordinate adaptation are ignored in V-DMC Rec0 and can be restored in V-DMC Rec1 and V-DMC Rec2. In addition, zippering is ignored in V-DMC Rec0 and V-DMC Rec1 and can be restored in V-DMC Rec2. In this way, the present disclosure can define a V-DMC profile that classifies restoration functions of a receiver.

[0378] According to the embodiments, in V-DMC, there is conformance A, which measures the conformance of the decoding part, and conformance B, which includes post-decoding and reconstruction.

[0379] For conformance A, the receiver must perform operations according to the given profile, and for conformance B, the receiver must basically support all reconstruction capabilities (up to V-DMC Rec2). However, the receiver can optionally support the V-DMC reconstruction profile signaled via the ptl_profile_reconstruction_idc syntax element (i.e., field) in the bitstream. In other words, conformance B is a recommended level signaled in the bitstream to ensure a certain level of quality, and a V-DMC receiver may provide more extended capabilities than the signaled conformance B. For example, if the ptl_profile_reconstruction_idc value in the received V-DMC bitstream is 4, the immersive video quality intended by the service provider is guaranteed even if the zippering function is not performed, but the receiver can perform the zippering function regardless to provide a higher level of video. On the other hand, the receiver may not perform the subdivision function selectively due to lack of computational resources, etc., but in this case, the quality of the final mesh video output is very likely to be low.

[0380] That is, the mesh data decoding module of the receiver parses the ptl_profile_reconstruction_idc value of the bitstream. If the value is 3, the conditional restoration process or the post-restoration process is skipped during restoration. If the value is 4, the conditional restoration process is performed but the post-restoration process is not performed. If the value is 5, all restoration and post-restoration processes can be performed. As such, the ptl_profile_reconstruction_idc value directly affects the decoder implementation complexity and resource usage. For low-end devices, a limited profile such as Rec0 or Rec1 may be advantageous, and for high-precision applications, Rec2 may be required. In other words, the mesh data decoding module of the receiver can determine which level of decoding / restoration it should perform by looking at the ptl_profile_reconstruction_idc value.

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

[0382] In the step (S31011) of encoding the base mesh of the above mesh data, if intra encoding or intra frame encoding is performed on the corresponding mesh frame, the base mesh can be encoded through a static mesh encoder. In this case, encoding can be performed on connection information, vertex geometry information, vertex texture information, normal information, etc. of the base mesh. In the step (S31011) of encoding the base mesh of the above mesh data, if inter encoding or inter frame encoding is performed on the corresponding mesh frame, a motion vector encoder can calculate a motion vector between the base mesh and the reference restored base mesh (or the restored quantized reference base mesh) and encode the value. In addition, connection information-based prediction can be performed using a previously encoded / decoded motion vector as a predictor, and a residual motion vector obtained by subtracting the predicted motion vector from the current motion vector can be encoded.

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

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

[0385] According to embodiments, the present disclosure may apply scalable video coding to mesh data. For example, the step of encoding attributes (S31013) may apply scalable video coding when encoding an attribute video data unit carrying attribute data and / or may apply scalable video coding when encoding a video data unit in which attribute data and displacement data are packed. In the present disclosure, scalable video coding may be referred to as scalable coding.

[0386] In this case, the present disclosure can transmit information indicating whether scalable video coding is applied to a receiving device as an embodiment. For example, as shown in FIG. 17, the asve_attribute_scalable_coding_flag syntax element and the asve_packed_video_scalable_coding_flag syntax element in asps_vdmc_extension( ) included in the atlas sequence parameter set can be signaled as information indicating whether scalable video coding is applied and transmitted to the receiving device.

[0387] In FIG. 17, if asve_attribute_scalable_coding_flag[ i ] is equal to 1, it specifies that scalable video coding is applied to coding the attribute video data unit having index i. And, if asve_attribute_scalable_coding_flag[ i ] is equal to 0, it specifies that scalable coding is not used to compress the attribute video data unit having index i.

[0388] Additionally, if asve_packed_video_scalable_coding_flag is equal to 1 in FIG. 17, it specifies that scalable video coding is used to code the packed video data unit. And, if asve_packed_video_scalable_coding_flag[ i ] is equal to 0, it specifies that scalable coding is not used to compress the packed video data unit. In the present disclosure, when scalable coding is used for the packed video data unit, the information included in the packing information syntax element is applied to the base layer.

[0389] And, the asve_attribute_scalable_coding_flag syntax element and the asve_packed_video_scalable_coding_flag syntax element can be used to indicate V-DMC toolset profile components as shown in FIG. 18. Referring to FIG. 18, the asve_attribute_scalable_coding_flag syntax element and the asve_packed_video_scalable_coding_flag syntax element are both 0 in V-DMC Main and V-DMC Main Still, and can be 0 or 1 in V-DMC Extended and V-DMC Extended Still. That is, the V-DMC Main and V-DMC Main Still profiles indicate that scalable video coding is not always applied, and the V-DMC Extended and V-DMC Extended Still profiles indicate that scalable video coding can be selectively applied.

[0390] In another embodiment, the present disclosure may transmit to a receiving device, as shown in FIG. 19, the vps_ext_attribute_scalable_coding_flag syntax element and the vps_ext_packed_video_scalable_coding_flag syntax element included in the VPS, as information indicating whether scalable video coding is applied.

[0391] In FIG. 19, if vps_ext_attribute_scalable_coding_flag[ j ][ i ] is equal to 1, it specifies that scalable video coding is applied to the attribute video data unit having index i for the atlas whose atlas ID is j. And, if vps_ext_attribute_scalable_coding_flag[ j ][ i ] is equal to 0, it specifies that scalable coding is not used to compress the attribute video data unit having index i for the atlas whose atlas ID is j.

[0392] Additionally, if vps_ext_packed_video_scalable_coding_flag[ j ] is equal to 1, it specifies that scalable video coding is used to code the packed video data unit for the atlas whose atlas ID is j. And, if vps_ext_packed_video_scalable_coding_flag[ j ] is equal to 0, it specifies that scalable coding is not used to compress the packed video data unit for the atlas whose atlas ID is j. In the present disclosure, when scalable coding is used for the packed video data unit, information included in the packing information syntax element is applied to the base layer.

[0393] And, the vps_ext_attribute_scalable_coding_flag syntax element and the vps_ext_packed_video_scalable_coding_flag syntax element can be used to indicate V-DMC toolset profile components. Referring to FIG. 20, the vps_ext_attribute_scalable_coding_flag syntax element and the vps_ext_packed_video_scalable_coding_flag syntax element are both 0 in V-DMC Main and V-DMC Main Still, and can be 0 or 1 in V-DMC Extended and V-DMC Extended Still. That is, it indicates that scalable video coding is not always applied in the V-DMC Main and V-DMC Main Still profiles, and that it can be selectively applied in the V-DMC Extended and V-DMC Extended Still profiles.

[0394] In addition, the present disclosure can define available toolset profile components as in FIG. 21, and define syntax element values ​​allowed for V-DMC toolset profile components as in FIG. 22. That is, the encoding method of the present disclosure can further include a step of generating signaling information (e.g., ASPS, VPS, etc.) including information indicating whether scalable video coding is applied, as in FIGS. 16 to 22, and defining toolset profile components and syntax element values ​​allowed for the toolset profile components.

[0395] The above encoding method may further include a step of transmitting a bitstream including encoded basemesh, encoded displacement data, encoded attribute data, and / or atlas data. The bitstream transmitted in the above step may be transmitted to a receiving device in a structure as shown in FIG. 15.

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

[0397] The at least one processor may apply scalable video coding during attribute encoding and / or may apply scalable video coding during encoding of packed video data. In addition, the at least one processor may signal information indicating whether scalable video coding has been applied, and may define syntax element values ​​allowed in available toolset profile components and V-DMC toolset profile components.

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

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

[0400] Fig. 26 is a flowchart showing an example of a decoding method according to embodiments. The decoding method according to embodiments may include a step of decoding a base mesh in a bitstream (S32011), a step of decoding a displacement in the bitstream (S32012), and a step of decoding an attribute in the bitstream (S32013). The decoding step of Fig. 26 may further include a step of receiving a bitstream including a base mesh, displacement data, and attribute data, or a file in which a bitstream is encapsulated. The receiving step performs a decapsulation process when a file is received to extract a bitstream, and omit the decapsulation process when a bitstream is received. The bitstream is referred to as a V-DMC bitstream or a V3C bitstream, and has a structure as shown in Fig. 15. The above receiving step can separate an atlas sub-bitstream, a basemesh sub-bitstream, a displacement sub-bitstream, and an attribute sub-bitstream (or attribute video sub-bitstream) from the bitstream according to the type information of the V3C unit header.

[0401] The step (S32011) of decoding the base mesh in the bitstream may, if the current mesh has been subjected to inter-screen encoding, use a previously decoded motion vector as a predictor to restore a final motion vector by adding it to a residual motion vector decoded from the base mesh sub-bitstream. The step (S32011) of decoding the base mesh in the bitstream may, if the current mesh has been subjected to intra-screen encoding, statically decode the base mesh sub-bitstream to restore connection information, vertex geometry information, texture coordinates, normal information, etc. of the base mesh.

[0402] The step (S32012) of decoding displacement within the above bitstream performs decoding on the displacement sub-bitstream based on the video codec if the displacement data is encoded based on a video codec, and performs decoding based on the arithmetic codec if the displacement data is encoded based on an arithmetic codec. In the present disclosure, the displacement sub-bitstream may be referred to as a displacement vector bitstream.

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

[0404] According to embodiments, the present disclosure may apply scalable video decoding to mesh data. For example, the step of decoding an attribute (S32013) may apply scalable video decoding when decoding an attribute video data unit carrying attribute data and / or may apply scalable video decoding when decoding a video data unit in which attribute data and displacement data are packed. In the present disclosure, scalable video decoding may be referred to as scalable decoding.

[0405] In the present disclosure, whether scalable decoding is applied can be determined based on information indicating whether received scalable video coding signaled as in FIG. 17 or FIG. 19 has been applied and / or syntax element values ​​allowed for available toolset profile components and V-DMC toolset profile components defined as in FIG. 18, FIG. 20, FIG. 21, or FIG. 22. For details, refer to the description of FIG. 23.

[0406] The base mesh, displacement data, and attribute data decoded in the above steps S32011-S32013 can be rendered after going through a post-processing process such as mesh restoration and reconstruction (or restoration).

[0407] The decoding method of the present disclosure can be performed by a decoding device (decoder). The decoding device includes a memory and at least one processor connected to the memory, and the at least one processor can be configured to decode a basemesh within a bitstream, decode a displacement within the bitstream, and decode an attribute within the bitstream. The at least one processor can apply scalable video decoding when decoding an attribute video data unit carrying attribute data and / or can apply scalable video decoding when decoding a video data unit in which attribute data and displacement data are packed. In the present disclosure, whether scalable decoding is applied can be determined based on information indicating whether received scalable video coding signaled as in FIG. 17 or FIG. 19 has been applied and / or syntax element values ​​allowed for available toolset profile components and V-DMC toolset profile components defined as in FIG. 18, FIG. 20, FIG. 21, or FIG. 22. For details, refer to the description of FIG. 23.

[0408] In this way, the present disclosure signals a scalable structure in signaling information for V-DMC using a simple flag (i.e., information indicating whether scalable video coding is applied), thereby enabling the receiver to efficiently compress and serve according to the user's network and specification options.

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

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

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

[0412] The devices and methods according to the embodiments are not limited to the configurations and methods of the embodiments described above, but the embodiments may be configured by selectively combining all or part of each embodiment so that various modifications can be made.

[0413] Although preferred embodiments of the embodiments have been illustrated and described, the embodiments are not limited to the specific embodiments described above, and various modifications may be made by those skilled in the art to which the present disclosure pertains without departing from the spirit or scope of the embodiments claimed in the claims, and such modifications should not be understood individually from the technical idea or prospect of the embodiments.

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

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

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

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

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

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

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

[0421] As described above, the embodiments may be applied, in whole or in part, to mesh data transmission and reception devices and systems. Those skilled in the art will appreciate that various modifications and variations may be made to the embodiments within the scope of the embodiments. The embodiments may include modifications and variations, and such modifications and variations do not depart from the scope of the claims and their equivalents.

Claims

Step of decoding the base mesh in the bitstream; A step of decoding displacement data within the bitstream; and A step of decoding attribute data within the bitstream; comprising: How to decode. In the first paragraph, A decoding method wherein the bitstream further includes first information indicating whether scalable video coding was applied when the attribute data was encoded at the transmitting side. In the second paragraph, A decoding method wherein the bitstream further includes second information indicating whether scalable video coding was applied when video data in which the attribute data and the displacement data are packed into one frame is encoded at the transmitting side. In the second paragraph, A decoding method in which the first information and the second information are signaled and received in a parameter set within the bitstream. In paragraph 4, A decoding method in which the first information and the second information are each defined as being allowed in the toolset profile components. In the fourth paragraph, the step of decoding the attribute data A decoding method for applying scalable video decoding to the attribute data or the packed video data based on at least one of the first information, the second information, or whether the first information and the second information are allowed as defined in the toolset profile components. memory; and At least one processor connected to the memory; At least one processor of the above: Decode the basemesh within the bitstream; Decoding displacement data within the bitstream; and configured to decode attribute data within the above bitstream; Decoding device. In the seventh paragraph, the at least one processor, A decoding device that applies scalable video decoding to video data in which the attribute data or the attribute data and the displacement data are packed into one frame based on at least one of the first information, the second information, or the allowability of the first information and the second information defined in the toolset profile components included in the bitstream. In paragraph 8, A decoding device in which the first information indicates whether scalable video coding was applied when the attribute data was encoded at the transmitting side, and the second information indicates whether scalable video coding was applied when the packed video data was encoded at the transmitting side. Step of encoding the base mesh of mesh data; A step of encoding displacement data of the above mesh data; and A step of encoding attribute data of the above mesh data; comprising; Encoding method. In paragraph 10, An encoding method further comprising the step of generating first information indicating whether scalable video coding was applied when the attribute data was encoded and second information indicating whether scalable video coding was applied when video data in which the attribute data and the displacement data are packed into one frame was encoded. In paragraph 11, An encoding method further comprising a step of defining, for each of the toolset profile components, whether the first information and the second information are allowed. memory; and At least one processor connected to the memory; wherein the at least one processor comprises: Encode the base mesh of mesh data; Encode displacement data of the above mesh data; and Encoding attribute data of the above mesh data; configured to do so; Encoding device. A computer-readable storage medium storing a bitstream generated by the method according to Article 10. Step of obtaining a bitstream for mesh data, The bitstream is generated based on the steps of encoding a base mesh of mesh data; encoding displacement data of the mesh data; and encoding attribute data of the mesh data; and A method comprising the step of transmitting data including the bitstream.

Images