LG Patent | Point cloud data transmission device, point cloud data transmission method, point cloud data reception device, and point cloud data reception method
Publication Number: 20260261709
Publication Date: 2026-09-03
Assignee: Lg Electronics Inc
Abstract
A mesh data transmission method according to embodiments may comprise the steps of: encoding mesh data; and transmitting a bitstream including the mesh data. A mesh data transmission method according to embodiments may comprise the steps of: receiving a bitstream including mesh data; and decoding the mesh data.
Claims
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
Description
CROSS-REFERENCE TO RELATED APPLICATION(S)
This application is the National Stage filing under 35 U.S.C. 371 of International Application No. PCT/KR2023/013222, filed on Sep. 5, 2023, which claims the benefit of earlier filing date and right of priority to Korean Application No. 10-2023-0030774, filed on Mar. 8, 2023, the contents of which are all incorporated by reference herein in their entirety.
TECHNICAL FIELD
Embodiments provide a method for providing point cloud content to provide a user with various services such as virtual reality (VR), augmented reality (AR), mixed reality (MR), and self-driving services.
BACKGROUND
A point cloud is a set of points in a three-dimensional (3D) space. It is difficult to generate point cloud data because the number of points in the 3D space is large.
A large throughput is required to transmit and receive data of a point cloud.
SUMMARY
An object of the present disclosure devised to solve the above-described problems is to provide a point cloud data transmission device, a point cloud data transmission method, a point cloud data reception device, and a point cloud data reception method for efficiently transmitting and receiving a point cloud.
Another object of the present disclosure is to provide a point cloud data transmission device, a point cloud data transmission method, a point cloud data reception device, and a point cloud data reception method for addressing latency and encoding/decoding complexity.
Embodiments are not limited to the above-described objects, and the scope of the embodiments may be extended to other objects that can be inferred by those skilled in the art based on the entire contents of the present disclosure.
To achieve these objects and other advantages, a method of transmitting mesh data according to embodiments may include encoding mesh data, and transmitting a bitstream containing the mesh data.
A method of receiving mesh data according to embodiments may include receiving a bitstream containing mesh data, and decoding the mesh data.
The point cloud data transmission method, the point cloud data transmission device, the point cloud data reception method, and the reception device according to embodiments may provide a quality point cloud service.
The point cloud data transmission method, point cloud data transmission device, point cloud data reception method, and point cloud data reception device according to embodiments may achieve various video codec methods.
The point cloud data transmission method, point cloud data transmission device, point cloud data reception method, and point cloud data reception device according to embodiments may provide universal point cloud content such as an autonomous driving service.
BRIEF DESCRIPTION OF THE DRAWINGS
The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the disclosure and together with the description serve to explain the principle of the disclosure. For a better understanding of various embodiments described below, reference should be made to the description of the following embodiments in connection with the accompanying drawings. The same reference numbers will be used throughout the drawings to refer to the same or like parts. In the drawings:
FIG. 1 illustrates a system for providing dynamic mesh content according to embodiments;
FIG. 2 illustrates a V-MESH compression method according to embodiments;
FIG. 3 illustrates pre-processing in V-MESH compression according to embodiments;
FIG. 4 illustrates a mid-edge subdivision method according to embodiments;
FIG. 5 illustrates a displacement generation process according to embodiments;
FIG. 6 illustrates an intra-frame encoding process in a V-MESH compression method according to embodiments;
FIG. 7 illustrates an inter-frame encoding process for V-MESH data according to embodiments;
FIG. 8 illustrates a lifting transform process for displacements according to embodiments;
FIG. 9 illustrates a process of packing transform coefficients into a 2D image according to embodiments;
FIG. 10 illustrates an attribute transfer process in a V-MESH compression method according to embodiments;
FIG. 11 illustrates an intra-frame decoding process in a V-MESH compression method according to embodiments;
FIG. 12 illustrates V-MESH compression inter frame decoding process according to embodiments;
FIG. 13 illustrates a point cloud data transmission device according to embodiments;
FIG. 14 illustrates a point cloud data reception device according to embodiments;
FIG. 15 illustrates an atlas sequence parameter set according to embodiments;
FIG. 16 illustrates a patch data unit according to embodiments;
FIG. 17 illustrates geometry MCTS information and geometry subpicture information according to embodiments;
FIG. 18 illustrates attribute MCTS information and attribute subpicture information according to embodiments;
FIG. 19 illustrates a V-DMC transmission device according to embodiments;
FIG. 20 illustrates a V-DMC reception device according to embodiments;
FIG. 21 illustrates a method of transmitting mesh data according to embodiments;
FIG. 22 illustrates a method of receiving mash data according to embodiments.
DETAILED DESCRIPTION
Reference will now be made in detail to the preferred embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. The detailed description, which will be given below with reference to the accompanying drawings, is intended to explain exemplary embodiments of the present disclosure, rather than to show the only embodiments that can be implemented according to the present disclosure. The following detailed description includes specific details in order to provide a thorough understanding of the present disclosure. However, it will be apparent to those skilled in the art that the present disclosure may be practiced without such specific details.
Although most terms used in the present disclosure have been selected from general ones widely used in the art, some terms have been arbitrarily selected by the applicant and their meanings are explained in detail in the following description as needed. Thus, the present disclosure should be understood based upon the intended meanings of the terms rather than their simple names or meanings.
FIG. 1 illustrates a system for providing dynamic mesh content according to embodiments.
The system in FIG. 1 includes a point cloud data transmission device 100 and a point cloud data reception device 110. The point cloud data transmission device may include a dynamic mesh video acquisition unit (or part) 101, a dynamic mesh video encoder 102, a file/segment encapsulator 103, and a transmitter 104. The point cloud data reception device 110 may include a receiver 111, a file/segment decapsulator 112, a dynamic mesh video decoder 113, and a renderer 114. Each component in FIG. 1 may correspond to hardware, software, a processor, and/or a combination thereof. In the following description, a point cloud data transmission device according to embodiments may be interpreted as referring to the transmission device 100 or the dynamic mesh video encoder (hereinafter, encoder) 102. A point cloud data reception device according to embodiments may be interpreted as referring to the reception device 110 or the dynamic mesh video decoder (hereinafter, decoder) 113.
The system of FIG. 1 may perform video-based dynamic mesh compression and decompression.
With advancements in 3D capture, modeling, and rendering, users are allowed to access 3D content in various forms, such as AR, XR, metaverse, and holograms, across multiple platforms and devices. 3D content is increasingly becoming sophisticated and realistic in its representation of objects to provide immersive experiences for users. However, this requires a substantial amount of data for generation and use of 3D models. Among the 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 uses mesh content.
First, the method of compressing dynamic mesh data starts with the Video-based point cloud compression (V-PCC) standard technique. Point cloud data is data that has color information in the coordinates (X, Y, Z) of vertices. Mesh data refers to vertex information including inter-vertex connectivity information. Content may be originally created in the form of mesh data. Connectivity information may be added to point cloud data, and the point cloud data may be transformed into mesh data.
Currently, the MPEG standards group defines two data types for dynamic mesh data: Category 1 of mesh data having a texture map as color information, and Category 2 of mesh data having vertex colors as color information.
Mesh coding standards for Category 1 data are currently underway, and standardization for Category 2 data is expected to follow. The overall process for providing a mesh content service may include acquisition, encoding, transmission, decoding, rendering, and/or feedback processes, as shown in FIG. 1.
To provide mesh content services, 3D data acquired through multiple cameras or special cameras may be processed into a mesh data type through a series of steps to generate a video. The generated mesh video may be transmitted through a series of operations, and the receiving side may process the received data back into a mesh video for rendering. Through this process, the mesh video may be provided to the user, allowing the user to utilize the mesh content interactively according to their intent.
A mesh compression system may include a transmission device and a reception device. The transmission device may encode the mesh video to output a bitstream, which may be delivered to the reception device over a digital storage medium or a network in the form of file or streaming (streaming segments). The digital storage medium may include various storage media such as USB, SD, CD, DVD, Blu-ray, HDD, and SSD.
The transmission device may schematically include a mesh video acquisition unit, a mesh video encoder, and a transmitter. The reception device may schematically include a receiver, a mesh video decoder, and a renderer. The encoder may be referred to as a mesh video/image/picture/frame encoding device. The decoder may be referred to as a mesh video/image/picture/frame decoding device. A transmitter may be included in the mesh video encoder, and a receiver may be included in the mesh video decoder. The renderer may include a display, and the renderer and/or display may be configured as separate devices or external components. The transmission device and reception device may further include separate internal or external modules/units/components for the feedback process.
Mesh data represents the surface of an object using multiple polygons. Each polygon is defined by vertices in 3D space and connectivity information indicating how the vertices are connected. Additionally, vertex attributes such as color and normal vectors may be included in the data. Mapping information, which allows the surface of the mesh to be mapped onto a 2D plane, may also be included in the attributes of the mesh. The mapping is generally described using a set of parametric coordinate related to mesh vertices, referred to as UV coordinates or texture coordinates, related to the vertices of the mesh. A mesh contains a 2D attribute map, which may be used to store high-resolution attribute information such as texture, normal, and displacement.
The mesh video acquisition unit may include processing 3D object data acquired through a camera or the like into a mesh data type having the attributes described above through a series of operations and generating a video composed of the mesh data. In the mesh video, the attributes of the mesh, such as vertices, polygons, connectivity between vertices, color, and normal, may change over time. A mesh video with attributes and connectivity information that change over time is referred to as a dynamic mesh video.
The mesh video encoder may encode an input mesh video into one or more video streams. A video may contain multiple frames, each of which may correspond to a still image/picture. In the present disclosure, the mesh video may include mesh images/frames/pictures. The term “mesh video” may be used interchangeably with mesh images/frames/pictures. The mesh video encoder may perform a Video-based Dynamic Mesh (V-Mesh) compression procedure. For compression and coding efficiency, the mesh video encoder may perform a series of procedures such as prediction, transformation, quantization, and entropy coding. Encoded data (encoded video/image information) may be output in the form of a bitstream.
The encapsulation processor (file/segment encapsulation module) may encapsulate encoded mesh video data and/or mesh video-related metadata in the form of a file or the like. The mesh video-related metadata may be received from a metadata processor. The metadata processor may be included in the mesh video encoder, or may be configured as a separate component/module. The encapsulation processor may encapsulate the data into a file format such as ISOBMFF or process the same into forms such as DASH segments. According to embodiments, the encapsulation processor may include the mesh video-related metadata in the file format. For example, the mesh video metadata may be included in boxes at various levels in the ISOBMFF file format, or as data on separate tracks in the file. In some embodiments, the encapsulation processor may encapsulate the mesh video-related metadata into a file.
The transmission processor may apply processing to the encapsulated mesh video data for transmission based on the file format. The transmission processor may be included in the transmitter or implemented as a separate component/module. The transmission processor may process the mesh video data according to any transmission protocol. The processing for transmission may include processing for delivery over a broadcast network and processing for delivery over a broadband. In some embodiments, the transmission processor may receive mesh video-related metadata from the metadata processor, as well as the mesh video data, and process the same for transmission.
The transmitter may transmit the encoded video/image information or data output in bitstream form to the receiver of the reception device over a digital storage medium or network in the form of a file or streaming. The digital storage medium may include various storage media such as USB, SD, CD, DVD, Blu-ray, HDD, and SSD. The transmitter may include an element to generate a media file through a predetermined file format, and may include an element for transmission over a broadcast/communication network. The receiver may extract the bitstream and deliver the same to a decoding device.
The receiver may receive the mesh video data transmitted by the mesh video transmission device. Depending on the channel for transmission, the receiver may receive the mesh video data over a broadcast network or a broadband network, or may receive the mesh video data over a digital storage medium.
The reception processor may perform processing on the received mesh video data according to the transmission protocol. The reception processor may be included in the receiver, or may be configured as a separate component/module. To correspond to the processing performed for transmission on the transmitting side, the reception processor may perform the reverse process to the operations of the transmission processor described above. The reception processor may deliver the acquired mesh video data to the decapsulation processor and the acquired mesh video-related metadata to the metadata parser. The mesh video-related metadata acquired by the reception processor may be in the form of a signaling table.
The decapsulation processor (file/segment decapsulation module) may decapsulate mesh video data in the form of files received from the reception processor. The decapsulation processor may decapsulate the files according to ISOBMFF or the like to acquire a mesh video bitstream or mesh video-related metadata (metadata bitstream). The acquired mesh video bitstream may be delivered to the mesh video decoder, and the acquired mesh video-related metadata (metadata bitstream) may be delivered to the metadata processor. The mesh video bitstream may include metadata (metadata bitstream). The metadata processor may be included in the mesh video decoder, or may be configured as a separate component/module. The mesh video-related metadata acquired by the decapsulation processor may be in the form of boxes or tracks in the file format. The decapsulation processor may receive metadata required for decapsulation from the metadata processor, when necessary. The mesh video-related metadata may be delivered to the mesh video decoder for use in the mesh video decoding procedure, or to the renderer for use in the mesh video rendering procedure.
The mesh video decoder may receive the input bitstream and perform an operation corresponding to the operation of the mesh video encoder to decode the video/images. The decoded mesh video/images may be displayed through the display of the renderer. The user may view all or a portion of the rendered result through a VR/AR display, a general display, or the like.
The feedback process may include transmitting various kinds of feedback information that may be acquired during the rendering/display operation to the transmitting side or to the decoder on the receiving side. The feedback process may provide interactivity in consuming the mesh video. In some embodiments, the feedback process may include transmitting head orientation information, viewport information indicative of an area the user is currently viewing, and the like. In some embodiments, the user may interact with objects implemented in the VR/AR/MR/autonomous driving environment. In this case, the information related to the interaction may be delivered to the transmitting side or service provider during the feedback process. In some embodiments, the feedback process may be skipped.
The head orientation information may refer to information about the user's head position, angle, movement, etc. Based on this information, information about the area that the user is currently viewing within the mesh video, i.e., viewport information, may be calculated.
The viewport information may be information about the area in the mesh video that the user is currently viewing. Gaze analysis may be performed based on this information to determine how the user consumes the mesh video, how long the user is looking at a particular area of the mesh video, and the like. The gaze analysis may be performed on the receiving side and the result may be delivered to the transmitting side through a feedback channel. A device, such as a VR/AR/MR display, may extract a viewport area based on the user's head position/orientation, the vertical or horizontal FOV supported by the device, etc.
In some embodiments, the feedback information described above may not only be delivered to the transmitter, but may also be consumed on the receiving side. In other words, operations such as decoding and rendering may be performed on the receiving side based on the feedback information described above. For example, based on the head orientation information and/or viewport information, only the mesh video for the area currently being viewed by the user may be preferentially decoded and rendered.
The present disclosure relates to dynamic mesh video compression as described above. The methods/embodiments disclosed herein may be applied to the standard of Video-based Dynamic mesh compression (V-Mesh) of the Moving Picture Experts Group (MPEG) or any next-generation video/image coding standard. Dynamic mesh video compression is a method for processing mesh connectivity information and attributes that change over time. It may perform lossy and lossless compression for a variety of applications such as real-time communications, storage, free-viewpoint video, and AR/VR.
The dynamic mesh video compression method described below is based on the V-mesh method of the MPEG.
In the present disclosure, a picture/frame may generally refer to a unit that represents one image at a specific time.
A pixel or pel may refer to the smallest unit that constitutes a picture (or video). Additionally, the term “sample” may be used as a term corresponding to a pixel. A sample may generally indicate a pixel or the value of the pixel in general. It may indicate only the pixel/pixel value of the luma component, or may indicate only the pixel/pixel value of the chroma component, or may indicate only the pixel/pixel value of the depth component.
A unit may represent the basic unit of image processing. The unit may include at least one of a specific area of the 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 a sample array) or transform coefficients composed of M columns and N rows.
The encoding process of FIG. 1 is performed as follows.
The compression method of Video-based dynamic mesh compression (V-Mesh) may provide a method of compressing dynamic mesh video data based on 2D video codecs such as High Efficiency Video Coding (HEVC) and Versatile Video Coding (VVC). In the V-Mesh compression process, the following data is received as input and compressed.
Input mesh: Includes 3D coordinates (geometry) of the vertices comprising the mesh, normal information about each vertex, mapping information for mapping the surface of the mesh to a 2D plane, and connectivity between the vertices constituting the surface. The surface of the mesh may be represented by triangles or other polygons, and the connectivity information between the vertices constituting the surface is stored according to a predetermined shape. The input mesh may be stored in the OBJ file format.
Attribute map (Texture map is also used interchangeably hereafter): Contains information about the attributes (color, normals, displacements, etc.) of a mesh and stores the data in the form of a mapping of the surface of the mesh onto a 2D image. Mapping indicating which part (surface or vertex) of the mesh corresponds to each piece of data in the attribute map is based on the mapping information contained in the input mesh. Since the attribute map has data about each frame of the mesh video, it may also be referred to as an attribute map video (or simply as attributes). The attribute map in the V-Mesh compression method mainly contains the color information about the mesh and is stored in an image file format (PNG, BMP, etc.).
Material library file: Contains the material attribute information used in the mesh, specifically the information that links the input mesh to the corresponding attribute map. It is stored in the Wavefront Material Template Library (MTL) file format.
In the V-Mesh compression method, the following data and information may be generated through the compression process.
Base mesh: Represents the objects in the input mesh using the minimum vertices determined according to the user's criteria by decimating the input mesh through the pre-processing process.
Displacement: Displacement information used to represent the input mesh as similarly as possible using the base mesh, expressed in 3D coordinates.
Atlas information: Metadata needed to reconstruct a mesh using the base mesh, displacement, and attribute map information. It may be generated and utilized in sub-units (sub-mesh, patch, etc.) that constitute the mesh.
A method of encoding mesh position information (or vertex) is described with reference to FIGS. 2 to 7, and a method of reconstructing mesh position information to encode attribute information (attribute map) is described with reference to FIGS. 6 to 10 and the like.
FIG. 2 illustrates a V-MESH compression method according to embodiments.
FIG. 2 illustrates the encoding process of FIG. 1, wherein the encoding process may include a pre-processing process and an encoding process. The encoder of FIG. 1 may include a pre-processor 200 and an encoder 201, as shown in FIG. 2. The transmission device of FIG. 1 may be broadly referred to as an encoder, and the dynamic mesh video encoder of FIG. 1 may be referred to as an encoder. The V-Mesh compression method may include pre-processing and encoding 201, as shown in FIG. 2. The pre-processor of FIG. 2 may be positioned at the front end of the encoder of FIG. 2. The pre-processor and encoder of FIG. 2 may be referred to as a single encoder.
The pre-processor may receive a static dynamic mesh and/or an attribute map. The pre-processor may generate a base mesh and/or displacements through pre-processing. The pre-processor may receive feedback information from the encoder, and may generate the base mesh and/or displacements based on the feedback information.
The encoder may receive the base mesh, the displacements, the static dynamic mesh, and/or the attribute map. The encoder may encode the mesh-related data to generate a compressed bitstream.
FIG. 3 illustrates pre-processing in V-MESH compression according to embodiments.
FIG. 3 illustrates the configuration and operation of the pre-processor of FIG. 2.
FIG. 3 illustrates the process of performing pre-processing on the input mesh. The pre-processing 200 may include four operations: 1) Group of Frame (GoF) generation, 2) mesh decimation, 3) UV parameterization, and 4) fitting subdivision surface (300). The pre-processor 200 may receive input mesh, generate displacements and/or a base mesh, and deliver the same to the encoder 201. The pre-processor 200 may deliver GoF information related to the GoF generation to the encoder 201.
Hereinafter, each operation in FIG. 3 is described.
GoF generation: A process of generating a reference structure for the mesh data. When the mesh of the previous frame and the current mesh have the same number of vertices, same number of texture coordinates, same vertex connectivity information, and same texture coordinate connectivity information, the previous frame may be set as a reference frame. In other words, if only the vertex coordinate values are different between the current input mesh and the reference input mesh, inter frame encoding may be performed. Otherwise, the frame may be subjected to intra frame encoding.
Mesh decimation: A process of simplifying the input mesh to create a simplified mesh, called a base mesh. Vertices to remove may be selected from the original mesh based on user-defined criteria, and then the selected vertices and the triangles connected to the selected vertices may be removed.
In the process of performing mesh decimation, the voxelized input mesh, target triangle ratio (TTR), and minimum triangle component (CCCount) information may be delivered as input, and the decimated mesh may be obtained as output. In the process, connected triangle components that are smaller than the set minimum triangle component (CCCount) may be removed.
UV parameterization: A process of mapping a 3D curved surface into a texture domain for the decimated mesh. Parameterization may be performed using the UV Atlas tool. This process generates mapping information indicating where each vertex of the decimated mesh may be mapped to on the 2D image. The mapping information is expressed and stored as texture coordinates, and the final base mesh is generated through this process.
Fitting subdivision surface: An operation of performing subdivision on the decimated mesh. A user-defined method, such as the mid-edge method, may be applied as the subdivision method. A fitting process is performed such that the input mesh and the subdivided mesh become similar to each other.
FIG. 4 illustrates a mid-edge subdivision method according to embodiments.
FIG. 4 illustrates a mid-edge subdivision method for the fitting subdivision surface described with reference to FIG. 3. Referring to FIG. 4, the original mesh containing four vertices is subdivided to create sub-meshes. The sub-meshes may be created by creating new vertices in the middle of the edges between the vertices.
Once the fitted subdivided mesh is generated, the displacements are calculated based on this result and the previously compressed and decoded base mesh (hereinafter referred to as the reconstructed base mesh). In other words, the reconstructed base mesh is subdivided in the same way as the fitting subdivision surface. The difference in position between this result and each vertex in the fitted subdivided mesh is the displacement for each vertex. Since the displacement represents a difference in position in 3D space, it is expressed as values in (x, y, z) space in the Cartesian coordinate system. Depending on a user input parameter, the coordinate values of (x, y, z) may be converted to coordinate values of (normal, tangential, bi-tangential) in a local coordinate system.
FIG. 5 illustrates a displacement generation process according to embodiments.
FIG. 5 illustrates in detail how displacements are calculated for the fitting subdivision surface 300, as described with reference to FIG. 4.
The encoder and/or pre-processor according to the embodiments may include 1) a subdivider, 2) a local coordinate system calculator, and 3) a displacement vector calculator. The subdivider may receive a reconstructed base mesh and generate a subdivided reconstructed base mesh. The local coordinate system calculator may receive the fitted subdivided mesh and the subdivided reconstructed base mesh, and may transform the coordinate system related to the mesh to a local coordinate system. The local coordinate system calculation may be optional. The displacement calculator calculates the difference in position between the fitted subdivision mesh and the subdivided reconstructed base mesh. For example, it may generate the difference in position between the vertices in the two input meshes. The difference in position between the vertices is the displacement.
The point cloud data transmission method and device according to embodiments may encode the point cloud as follows. Point cloud data (which may be referred to as a point cloud for short) according to embodiments may refer to data including vertex coordinates and color information. Point cloud is a term that includes mesh data. The terms point cloud and point cloud data may be used interchangeably herein.
According to embodiments, the V-Mesh compression (reconstruction) method may include intra frame encoding (FIG. 6) and inter frame encoding (FIG. 7).
Based on the results of the GoF generation described above, intra frame encoding or inter frame encoding is performed. In the intra encoding, the data to be compressed may be a base mesh, displacements, an attribute map, and the like. In the inter encoding, the data to be compressed may be displacements, an attribute map, and a motion field between the reference base mesh and the current base mesh.
FIG. 6 illustrates an intra-frame encoding process in a V-MESH compression method according to embodiments.
The encoding process of FIG. 6 details the encoding of FIG. 1. That is, it represents the configuration of the encoder when the encoding of FIG. 1 is intra-frame encoding. The encoder of FIG. 6 may include a pre-processor 200 and/or an encoder 201.
The pre-processor may receive an input mesh and perform the pre-processing described above. A base mesh and/or a fitted subdivided mesh may be generated through the pre-processing. The quantizer may quantize the base mesh and/or the fitted subdivided mesh. The static mesh encoder may encode the static mesh. The static mesh encoder may generate a bitstream containing the encoded base mesh. The static mesh decoder may decode the encoded static mesh. The inverse quantizer may inversely quantize the quantized static mesh. The displacement calculator may receive a reconstructed static mesh, and may generate a displacement, which is the difference in position based on the fitted subdivided mesh. The forward linear lifting unit may receive the displacement and generate lifting coefficients. The quantizer may quantize the lifting coefficients. The image packer may pack the image based on the quantized lifting coefficients. The video decoder decodes the encoded video. The image unpacker may unpack the packed image. The inverse quantizer may inversely quantize the image. The inverse linear lifting unit applies inverse lifting to the image to generate a reconstructed displacement. The mesh reconstructor reconstructs a deformed mesh based on the reconstructed displacement and the reconstructed base mesh. The attribute transfer receives an input mesh and/or an input attribute map and generates an attribute map based on the reconstructed deformed mesh. The push-pull padding unit may pad data to the attribute map based on a push-pull method. The color space converter may convert the space of the color component, which is an attribute. The video encoder may encode the attribute. The multiplexer may multiplex the compressed base mesh, the compressed displacement, and the compressed attribute to generate a bitstream.
FIG. 7 illustrates an inter-frame encoding process in a V-MESH compression method according to embodiments.
The encoding process of FIG. 7 details the encoding of FIG. 1 in detail. That is, it represents the configuration of the encoder when the encoding of FIG. 1 is inter-frame encoding. The encoder of FIG. 7 may include a pre-processor 200 and/or an encoder 201.
For the components of the encoding operation of FIG. 7 that correspond to the encoding operation of FIG. 6, refers to the description of FIG. 7. For inter-frame-based encoding in FIG. 7, the motion encoder may encode a motion based on the reconstructed quantized reference base mesh. The base mesh reconstructor may reconstruct a base mesh based on the reconstructed quantized reference base mesh.
The encoder in FIG. 6 compresses the base mesh, displacement, and attributes within a frame to generate a bitstream, while the encoder in FIG. 7 compresses the motion, displacement, and attributes between the current frame and a reference frame to generate a bitstream.
The encoding method according to the embodiments includes base mesh encoding (intra encoding). When performing intra-frame encoding on a current input mesh frame, the base mesh generated during pre-processing may undergo quantization and be then encoded using a static mesh compression technique. In the V-Mesh compression method, for example, the Draco technique is applied, and the targets to be compressed include vertex position information, mapping information (texture coordinates), vertex connectivity data, etc. related to the base mesh.
The encoding method according to the embodiments may include motion field encoding (also inter encoding). Inter frame encoding may be performed when the reference mesh and the current input mesh have a one-to-one correspondence of vertices, and only the position information about the vertices differs therebetween. When inter frame encoding is performed, the base mesh may not be compressed. Instead, the difference between the vertices of the reference base mesh and the current base mesh, i.e., the motion field may be computed and encoded. The reference base mesh is the result of quantizing the decoded base mesh data and is determined by the reference frame index determined in the GoF generation. The motion field may be encoded as it is. Alternatively, a predicted motion field may be calculated by averaging the motion fields of the reconstructed vertices among the vertices connected to the current vertex, and a residual motion field, which is the difference between the value of the predicted motion field and the value of the motion field of the current vertex, may be encoded. The value of this field may be encoded using entropy coding. Except for the motion field encoding in the inter frame encoding, the process of encoding the displacements and attribute map is the same as the structure of the intra frame encoding method except for the base mesh encoding.
FIG. 8 illustrates a lifting transform process for displacements according to embodiments.
FIG. 9 illustrates a process of packing transform coefficients into a 2D image according to embodiments.
FIGS. 8 and 9 illustrate the process of transforming displacements and packing transform coefficients in the encoding process of FIGS. 6 and 7, respectively.
An encoding method according to the embodiments includes displacement encoding.
After base mesh encoding and/or motion field encoding, a reconstructed base mesh may be generated through reconstruction and inverse quantization, and a displacement may be calculated between a result of subdivision of the reconstructed base mesh and a fitted subdivided mesh generated through the fitting subdivision surface. A data transform process, such as a wavelet transform, may be applied to the displacement information for effective encoding.
FIG. 8 illustrates the process of transforming displacement information in V-Mesh using the lifting transform. The transform coefficients generated through the transform process are quantized and then packed into a 2D image. The transform coefficients may be organized into blocks, one block for every 256 (=16×16) units. Each block may be packed in a z-scan order. The number of rows in a block is fixed to 16, but the number of columns in the block may be determined by the number of vertices in the subdivided base mesh. Within a block, the transform coefficients may be sorted with the Morton code and packed. For the packed images, a displacement video may be generated per GoF. The displacement video may be encoded using a conventional video compression codec.
Referring to FIG. 8, the base mesh (original) may include vertices and edges for LoD0. A first subdivision mesh generated by splitting the base mesh includes vertices generated by further splitting the edges of the base mesh. The first subdivision mesh contains vertices for LoD0 and vertices for LoD1. LoD1 includes subdivided vertices and vertices from the base mesh (LoD0). The first subdivision mesh may be split to generate a second subdivision mesh. The second subdivision mesh contains LoD2. LoD2 includes a base mesh vertex (LoD0), LoD1 containing vertices additionally generated from LoD0, and vertices further split from LoD1. LoD is a level of detail that indicates the degree of detail. As the index of the level increases, the distance between vertices is shortened, and the level of detail rises. LoD N contains the vertices contained in LoD N-1. In the case where the vertex is further split through subdivision, the mesh may be encoded based on a prediction and/or updating method, taking into account the previous vertices v1 and v2, and the subdivided vertex v. Instead of encoding the information for the current LoD N as it is, a residual with respect to previous LoD N-1 may be generated. Thus, the mesh may be encoded using the residual to reduce the size of the bitstream. The prediction process refers to the operation of predicting the current vertex v from the previous vertices v1 and v2. Since neighboring subdivision meshes have similar data, this property may be exploited for efficient encoding. The current vertex position information is predicted from the residual for the previous vertex position information, and the previous vertex position information is updated based on the residual.
Referring to FIG. 9, a vertex has a coefficient generated through lifting transform. The coefficient of the vertex related to the lifting transform may be packed into an image and then encoded.
FIG. 10 illustrates an attribute transfer process in a V-MESH compression method according to embodiments.
FIG. 10 illustrates a detailed operation of the attribute transfer in the encoding of FIGS. 6, 7, etc.
The encoding according to the embodiments includes attribute map encoding.
Information about the input mesh is compressed through base mesh encoding, motion field encoding, and displacement encoding. The input mesh compressed in the encoding process is reconstructed through base mesh decoding (intra frame), motion field decoding (inter frame), and displacement video decoding, and the reconstructed deformed mesh (hereinafter referred to as Recon. deformed mesh), which is the result of the reconstruction, is used to compress the input attribute map, as shown in FIGS. 6 and 7. The Recon. deformed mesh has position information about vertices, texture coordinates, and corresponding connectivity 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 recon. deformed mesh is generated through the attribute transfer process.
The attribute transfer first checks, for every point P(u, v) in the 2D texture domain, whether the corresponding point is within a texture triangle of the Recon. deformed mesh. When the corresponding vertex is in the texture triangle T, the attribute transfer calculates the barycentric coordinates (α, β, γ) of P(u, v) according to the triangle T. Then, it calculates the 3D coordinates M(x, y, z) of P(u, v) based on the 3D vertex positions of the triangle T and (α, β, γ). The vertex coordinates M′(x′, y′, z′) that corresponds to the closest position to the calculated M(x, y, z) and a triangle T′ containing this point are searched for in the input mesh domain. Then, the barycentric coordinates (α′, β′, γ′) of M′(x′, y′, z′) in the triangle T′ are calculated. The texture coordinates (u′, v′) are calculated based on the texture coordinates corresponding to the three vertices of triangle T′ and (α′, β′, γ′), and the color information corresponding to the coordinates are searched for in the input attribute map. The color information found in this way is then assigned to the (u, v) pixel position in the new input attribute map. If P(u, v) does not belong to any triangle, the pixel at the position in the new input attribute map be filled with a color value using a padding algorithm, such as the push-pull algorithm.
The new attribute map generated by the attribute transfer is bundled into GoFs to construct an attribute map video, which is compressed using a video codec.
A reference relationship between the input mesh, the input attribute map, the reconstructed mesh, and the generated attribute map may be seen from FIG. 10.
The decoding process of FIG. 1 may perform the reverse of the encoding process of FIG. 1. Specifically, the decoding process is performed as disclosed below.
FIG. 11 shows the intra-frame decoding process of the V-MESH compression method according to embodiments.
FIG. 11 illustrates the configuration and operation of the decoder of the reception device of FIG. 1 and the like.
FIG. 11 shows the intra decoding process of the V-Mesh technology according to embodiments. First, the bitstream may be separated into a mesh sub-stream, a displacement sub-stream, an attribute map sub-stream, and a sub-stream containing patch information about the mesh, such as V3C/V-PCC.
The mesh sub-stream may be decoded through the decoder of a static mesh codec used in the encoding such as, for example, Google Draco. As a result, connectivity information, vertex geometry information, vertex texture coordinates, and the like related to the base mesh may be reconstructed. The displacement sub-stream may be decoded into a displacement video through the decoder of the video compression codec used in the encoding. Then, image unpacking, inverse quantization, and inverse transform are performed to reconstruct the displacement information about each vertex. Then, inverse quantization is applied to the reconstructed base mesh, and then the result thereof is combined with the reconstructed displacement information to generate a final decoded mesh.
The attribute map sub-stream is decoded by the decoder of the video compression codec used in the encoding, and then a final attribute map is reconstructed through color format transform and the like.
The reconstructed decoded mesh and decoded attribute map may be utilized at the receiving side as final mesh data that may be utilized by a user.
Referring to FIG. 11, the bitstream includes patch information, a mesh sub-stream, a displacement sub-stream, and an attribute map sub-stream. The term sub-stream is interpreted as referring to a partial bitstream included in the bitstream. The bitstream contains patch information (data), mesh information (data), displacement information (data), and attribute map information (data).
The decoder performs intra-frame decoding as follows. The static mesh decoder decodes the mesh to generate a reconstructed quantized base mesh, and the inverse quantizer applies the quantization parameters of the quantizer in reverse to generate a reconstructed base mesh. The video decoder decodes the displacement, the unpacker unpacks the decoded video image, and the inverse quantizer inversely quantizes the quantized image. The inverse linear lifting unit applies a lifting transform in the reverse process of the encoder to generate a reconstructed displacement. The mesh reconstructor 630 generates a deformed mesh based on the base mesh and the displacement. The video decoder decodes the attribute map, and the color transformer transforms the color format and/or space to generate a decoded attribute map.
FIG. 12 illustrates an inter-frame decoding process of V-MESH technology.
FIG. 12 illustrates the configuration and operation of the decoder of the reception device of FIG. 1 and the like.
FIG. 12 illustrates the inter decoding process of V-MESH technology. First, the input bitstream may be separated into a motion sub-stream, a displacement sub-stream, an attribute sub-stream, and a sub-stream containing patch information about the mesh, such as V3C/V-PCC.
The motion sub-stream is decoded through entropy decoding and inverse prediction, and the reconstructed motion information is combined with a pre-reconstructed and stored reference base mesh to generate a reconstructed quantized base mesh for the current frame. Then, inverse quantization is applied to the reconstructed quantized base mesh, and the result thereof is combined with the displacement information reconstructed using the same method as the above-described intra decoding to generate a final decoded mesh. The reconstructed decoded mesh and the decoded attribute map may be utilized at the receiving side as the final mesh data that may be utilized by the user.
Referring to FIG. 12, the bitstream contains a motion, displacements, and an attribute map. Because inter-frame decoding is performed, the process further includes decoding the inter-frame motion information. A reconstructed base mesh is generated by decoding the motion and generating a reconstructed quantized base mesh for the motion based on the reference base mesh. For the operations in FIG. 12 that are the same as those in FIG. 11, refer to the description of FIG. 11.
FIG. 13 illustrates a point cloud data transmission device according to embodiments.
FIG. 13 corresponds to the transmission device 100 or dynamic mesh video encoder 102 of FIG. 1, the encoder (pre-processor and encoder) of FIG. 2, and/or the corresponding transmission encoding device. Each component of FIG. 13 corresponds to hardware, software, a processor, and/or a combination thereof.
The process of operations at the transmitting side for compressing and transmitting dynamic mesh data using a V-Mesh compression technique may be configured as shown in FIG. 13.
The mesh pre-processor receives the original mesh and generates a decimated mesh. The decimation may be performed based on a target number of vertices or a target number of polygons constituting the mesh. Parameterization may be performed on the decimated mesh to generate texture coordinates and texture connectivity information per vertex. The mesh information in a floating-point form may be quantized to a fixed-point form. The result is the base mesh, which may be encoded by a static mesh encoder. The mesh pre-processor may perform a mesh subdivision on the base mesh to generate additional vertices. Depending on the subdivision method, vertex connectivity information including the additional vertices, texture coordinates, and connectivity information about the texture coordinates may be generated. A fitted subdivided mesh may be generated by adjusting vertex positions such that the subdivided mesh becomes similar to the original mesh.
When intra-frame encoding (intra encoding) is performed on the mesh frame, the base mesh may be compressed through the static mesh encoder. In this case, the connectivity information, vertex geometry information, vertex texture information, normal information, and the like related to the base mesh may be encoded. The base mesh bitstream generated through the encoding is transmitted to the multiplexer.
When inter-frame encoding (inter encoding) is performed on the mesh frame, the motion vector encoder may operate to receive as input a base mesh and a reference reconstructed base mesh, compute a motion vector between the two meshes, and encode the value thereof. Further, the motion vector encoder may perform connectivity information-based prediction using the previously encoded/decoded motion vector as a predictor, and encode a residual motion vector, which is obtained by subtracting the predicted motion vector from the current motion vector. The motion vector bitstream generated by the encoding is transmitted to the multiplexer.
A reconstructed base mesh may be generated from the encoded base mesh and motion vectors through the base mesh reconstructor.
The displacement vector calculator may perform mesh subdivision on the reconstructed base mesh. A vector may be calculated as a value of the difference in vertex position between the subdivided reconstructed base mesh and the fitted subdivision mesh generated by the pre-processor. As a result, displacement vectors as many as vertices in the subdivided mesh may be calculated. The displacement vector calculator may transform the displacement vectors calculated in the 3D Cartesian coordinate system to a local coordinate system based on the normal vector of each vertex.
The displacement vector video generator may transform the displacement vectors for effective encoding. According to embodiments, the transform may be lifting transform, wavelet transform, or the like. In addition, quantization may be performed on the transformed displacement vector values, i.e., the transform coefficients. In this case, different quantization parameters may be applied to the axes of the transform coefficients, respectively. The quantization parameters may be derived by an agreement between the encoder/decoder. After transform and quantization, the displacement vector information may be packed into a 2D image. A displacement vector video may be generated by grouping the packed 2D images for each frame. A displacement vector video may be generated for each group of frames (GoF) of the input mesh.
The displacement vector video encoder may encode the generated displacement vector video using a video compression codec. The generated displacement vector video bitstream is transmitted to the multiplexer.
The displacement vectors reconstructed through the displacement vector reconstructor and the base mesh reconstructed and subdivided through the base mesh reconstructor are reconstructed through the mesh reconstructor. The reconstructed mesh has reconstructed vertices, inter-vertex connectivity information, texture coordinates, and inter-texture coordinate connectivity information.
A texture map of a reconstructed mesh may re-generated from the texture map of the original mesh through the texture map video generator. The vertex-by-vertex color information in the texture map of the original mesh may be assigned to the texture coordinates of the reconstructed mesh. A texture map video may be generated by grouping the frame-level re-generated texture maps into GoFs.
The generated texture map video may be encoded by the texture map video encoder using a video compression codec. A texture map video bitstream generated through the encoding is transmitted to the multiplexer.
The generated motion vector bitstream, base mesh bitstream, displacement vector bitstream, and texture map bitstream may be multiplexed into a single bitstream to be transmitted to the receiving side through the transmitter. Alternatively, for the generated motion vector bitstream, base mesh bitstream, displacement vector bitstream, and texture map bitstream, a file with one or more track data may be generated or the bitstreams may be encapsulated into segments and transmitted to the receiving side through the transmitter.
Referring to FIG. 13, the transmitter (encoder) may encode the mesh in an intra-frame or inter-frame manner. According to intra-encoding, the transmission device may generate a base mesh, displacement vectors (or displacements), and a texture map (or attribute map). According to inter-encoding, the transmission device may generate a motion vector (or motion), a base mesh, displacement vectors (or displacements), and a texture map (or attribute map). The texture map acquired from the data input unit is generated and encoded based on the reconstructed mesh. The displacements are generated and encoded based on the differences in vertex positions between the base mesh and the subdivided mesh. The base mesh is generated by pre-processing, decimating, and encoding the original mesh. For the motion, a motion vector is generated for the mesh in the current frame based on the reference base mesh in the previous frame.
FIG. 14 illustrates a point cloud data reception device according to embodiments.
FIG. 14 corresponds to the reception device 110 or mesh video decoder 113 of FIG. 1, the decoder of FIG. 11 or 12, and/or a corresponding receiving decoding device. Each component of FIG. 14 corresponds to hardware, software, a processor, and/or a combination thereof. The reception (decoding) operation of FIG. 14 may follow a reverse process to the corresponding process of the transmission (encoding) operation of FIG. 13.
The bitstream of the received mesh is subjected to file/segment decapsulation and then demultiplexed into a compressed motion vector bitstream or base mesh bitstream, a displacement vector bitstream, and a texture map bitstream.
In the case where inter-frame encoding is applied to the current mesh based on the frame header information, the motion vector decoder may decode the motion vector bitstream. The previously decoded motion vector may be used as a predictor and add the same to the residual motion vector decoded from the bitstream to reconstruct the final motion vector.
In the case where intra-frame encoding is applied to the current mesh based on the frame header information, the static mesh decoder may decode the base mesh bitstream to reconstruct connectivity information, vertex geometry information, texture coordinates, normal information, and the like related to the base mesh.
In the case where inter-frame encoding is applied to the current mesh, the base mesh reconstructor may add the decoded motion vectors to the reference base mesh and perform inverse quantization to reconstruct the current base mesh. In the case where intra-frame encoding is applied to the current mesh, inverse quantization may be performed on the base mesh decoded by the static mesh decoder to generate a reconstructed base mesh.
The displacement vector video decoder may decode the displacement vector bitstream as a video bitstream using a video codec.
The displacement vector reconstructor extracts displacement vector transform coefficients from the decoded displacement vector video, and reconstructs displacement vectors through inverse quantization and inverse transform. If the reconstructed displacement vectors are values in a local coordinate system, inverse transform to the Cartesian coordinate system may be performed.
The mesh reconstructor may subdivide the reconstructed base mesh to generate additional vertices. Through the subdivision, vertex connectivity information including the additional vertices, texture coordinates, and connectivity information about the texture coordinates may be generated. The subdivided reconstructed base mesh may be combined with the reconstructed displacement vectors to generate a final reconstructed mesh.
The texture map video decoder may decode the texture map bitstream as a video bitstream using a video codec. The reconstructed texture map has color information about each vertex in the reconstructed mesh, and the texture coordinates of each vertex may be used to obtain the color value of the vertex from the texture map.
The reconstructed mesh and texture map are presented to the user through a rendering process using the mesh data renderer or the like.
Referring to FIG. 14, the reception device (decoder) may decode the mesh in an intra-frame or inter-frame manner. According to intra-decoding, the reception device may receive a base mesh, displacement vectors (or displacements), and a texture map (or attribute map), and decode the reconstructed mesh and reconstructed texture map to render mesh data. According to inter-decoding, the reception device may receive a motion vector (or motion), a base mesh, displacement vectors (or displacements), a texture map (or attribute map), and decode the reconstructed mesh and the reconstructed texture map to render mesh data.
A point cloud data transmission device and method according to embodiments may encode the mesh data, and transmit a bitstream containing the encoded mesh data. A point cloud data reception device and method according to embodiments may receive a bitstream containing mesh data and decode the mesh data. The point cloud data transmission/reception method/device according to embodiments may be referred to as a method/device according to embodiments. The point cloud data transmission/reception method/device may also be referred to as a mesh data transmission/reception method/device.
Methods/devices according to embodiments provide a signaling method for partial decoding of V-DMC.
Embodiments relate to video-based dynamic mesh coding (V-DMC), which is a method of compressing 3D dynamic mesh data using a 2D video codec. Embodiments provide V-DMC encoding and decoding methods that support partial access such that only specific areas of mesh content may be selectively reconstructed and utilized at the receiving side. In particular, in encoding the displacement and attribute components in V-DMC using a video codec, a signaling method for transmitting information indicating whether partial decoding is supported and information for independent decoding of partial areas is provided.
Embodiments relate to a method of independently decoding and reconstructing, by a V-DMC decoder, only a specific mesh data area specified by a user.
According to V-DMC technology, the entire input mesh content is compressed and transmitted, and the receiver decodes the entire bitstream and reconstructs the entire mesh area. However, there may be situations where the user needs only a specific area rather than the entire content when content is utilized at the device, application, or software. In such cases, receiving information about the desired area and then extracting, decoding, and reconstructing only a part of the bitstream corresponding to the area at the receiving side is a more efficient approach in terms of time and resource utilization. Such partial access and reconstruction methods are supported by video codecs and point cloud codecs and are also applied by V-DMC-based dynamic mesh codecs.
Embodiments provide a signaling method for supporting partial access and reconstruction operations in V-DMC. While V-DMC defines the concept of a submesh for partial decoding, the partial decoding methods for each component of the submesh and signaling for encoding/decoding have not been defined. In V-DMC, the information required to encode/decode a submesh is transmitted in atlas data. The atlas data carries mesh encoding information and mesh data information based on patches, which are atlas coding units that represent rectangular areas in an atlas. Embodiments provide a signaling method for partial decoding based on patches. In particular, when video compression technology is applied to the displacement and attribute components of the V-DMC compressed bitstream, independent video decoding units for partial decoding are applied. The displacement and attribute components of a submesh may be decoded independently.
Embodiments provide partial access and reconstruction functions in V-DMC to enable specific areas of a dynamic mesh to be reconstructed and utilized.
Embodiments provide a method of signaling whether partial decoding of the displacement component is enabled.
Embodiments provide a method of signaling whether partial decoding of the attribute component is enabled.
Embodiments provide a partial decoding method and signaling method for displacement video to which an independent decoding segmentation structure of a video codec is applied.
Embodiments provide a partial decoding method and signaling method for attribute video to which an independent decoding segmentation structure of a video codec is applied.
V-DMC according to embodiments may be referred to as V-Mesh in the following description. The terms are used interchangeably with the same meaning.
A transmission (encoding) method/device according to embodiments is operated as follows.
A submesh according to embodiments is a unit that constitutes the entire mesh and is independently decodable. The encoder according to embodiments encodes the base mesh and the displacement and attribute components for a submesh using corresponding methods, and configures and transmits the encoded mesh and components in a bitstream.
The V-DMC encoding method includes compressing and transmitting the displacement and attribute components using a video codec. Instead of configuring and compressing each video for each submesh, the entire mesh is compressed into video data and transmitted. Therefore, in the case where the compressed video does not support partial decoding of a partial area, the video bitstream for the entire mesh may be decoded and then only the information corresponding to the submesh area may be extracted to reconstruct the submesh. On the other hand, when partial decoding of a partial area in the compressed video bitstream is enabled, only the portion of the video bitstream corresponding to the submesh may be extracted and decoded to reconstruct the submesh data.
Currently, V-DMC does not include signaling indicating whether partial decoding is enabled for the components compressed into video data. Therefore, embodiments provide a signaling method therefor. Whether partial decoding is enabled for the displacement component may be signaled using asps_vmc_ext_displacement_independent_partial_decode_enable_flag. Whether partial decoding is enabled for the attribute component may be signaled using asps_vmc_ext_attribute_independent_partial_decode_enable_flag. Further, when each component is encoded using a video codec and partial decoding is enabled for a video bitstream thereof, the information about the employed video codec may also be signaled to enable appropriate transmission and decoding of encoding information according to the codec type. The information about the codec used to encode the displacement component may be signaled using asps_vmc_ext_displacement_codec_id, and the information about the codec used to encode the attribute component may be signaled using asps_vmc_ext_attribute_codec_id.
FIG. 15 illustrates an atlas sequence parameter set according to embodiments.
FIG. 15 illustrates the atlas sequence parameter generated by the dynamic mesh video encoder 102 of FIG. 1, the pre-processor 200 and encoder 201 of FIGS. 2 and 3, the encoder of FIG. 6, a metadata processor not illustrated in FIGS. 6, 7, and 13 but included in the encoders of FIGS. 6, 7, and 13, the submesh generator of FIG. 19, or the like. The parameter may be referred to as signaling information, metadata, or the like.
asps_vmc_ext_prevent_geometry_video_conversion_flag: Indicates whether geometry video conversion is performed.
asps_vmc_ext_prevent_attribute_video_conversion_flag: Indicates whether attribute video conversion is performed.
asps_vmc_ext_subdivision_method: Indicates the type of subdivision applied to the mesh.
asps_vmc_ext_subdivision_iteration_count: Indicates the number of iterations of subdivision.
asps_vmc_ext_displacement_coordinate_system: Indicates the coordinate system for displacement.
asps_vmc_ext_transform_method: Indicates the transform method for displacement. For example, the transform may include linear lifting.
When asps_vmc_ext_transform_method indicates linear lifting, the atlas parameter set may carry vmc_lifting_transform_parameters(0, 0).
asps_vmc_ext_displacement_independent_partial_decode_enable_flag: Indicates whether partial decoding is enabled for displacement.
asps_vmc_ext_displacement_codec_id: Specifies an ID indicating the displacement encoding codec method.
asps_vmc_ext_num_attribute_video: Indicates the number of attribute videos related to mesh data.
For each asps_vmc_ext_num_attribute_video, the following parameters are defined.
asps_vmc_ext_attribute_type_id [i]: Specifies the ID indicating the type of an attribute included in the attribute video, such as color, reflectance, or material.
asps_vmc_ext_attribute_frame_width[i]: Indicates the width of the attribute frame.
asps_vmc_ext_attribute_frame_height[i]: Indicates the height of the attribute frame.
asps_vmc_vmc_ext_attribute_transform_method[i]: Indicates the transform method applied to the attribute.
When asps_vmc_vmc_ext_attribute_transform_method[i] is linear lifting, the atlas parameter set carries vmc_lifting_transform_parameters(i+1, 0).
asps_vmc_ext_direct_attribute_projection_enabled_flag[i]: Indicates whether the attribute has been encoded by direct projection.
asps_vmc_ext_attribute_independent_partial_decode_enable_flag[i]: Indicates whether partial decoding is enabled for the attribute.
When partial decoding is enabled for the attribute, the atlas parameter set carries asps_vmc_ext_attribute_codec_id [i], which indicates the attribute encoding method.
asps_vmc_ext_packing_method: Indicates the method for packing displacement.
Table 1) asps_vmc_ext_displacement_codec_id set to 0 may indicate encoding of displacement based on the HEVC method, asps_vmc_ext_displacement_codec_id set to 1 may indicate encoding based on the VVC method, and asps_vmc_ext_displacement_codec_id set to 2 may indicate an additional encoding method for displacement. Codec methods according to each integer value may be modified and added according to embodiments.
Table 2) asps_vmc_ext_attribute_codec_id set to 0 may indicate encoding of the attribute based on the HEVC method, asps_vmc_ext_attribute_codec_id set to 1 may indicate encoding based on the VVC method, and asps_vmc_ext_attribute_codec_id set to 2 may indicate an additional encoding method for the attribute. Codec methods according to each integer value may be modified and added according to embodiments.
As shown in FIG. 15, in order to perform partial decoding on the displacement and attribute components, the encoder transmits independent video decoding area information corresponding to the displacement and attribute components for each patch. The information obtained when mapping 3D mesh to 2D image space in V-DMC is processed as atlas image information. Some rectangular areas in the atlas image may be referred to as patches. The atlas information included in one patch is defined as shown in FIG. 16. The patch information to be transmitted by the encoder for partial decoding is shown in FIG. 16.
The atlas information in FIG. 16 may be generated through the atlas parameterization operation by the pre-processor in FIG. 3.
A patch data unit carrying atlas information may be generated for each tile ID and patch index.
pdu_submesh_id[tileID][patchIdx]: Indicates the ID of the submesh included in the patch identified by the tile ID and patch index.
pdu_vertex_count_minus1[tileID][patchIdx]: Indicates the number of vertices included in the patch identified by the tile ID and patch index.
pdu_triangle_count_minus1[tileID][patchIdx]: Indicates the number of triangles included in the patch identified by the tile ID and patch index.
pdu_geometry_2d_pos_x[tileID][patchIdx]: Indicates the X-axis position information related to geometry data included in the patch identified by the tile ID and patch index.
pdu_geometry_2d_pos_y[tileID][patchIdx]: Indicates the Y-axis position information related to geometry data included in the patch identified by the tile ID and patch index.
pdu_geometry_2d_size_x_minus1[tileID][patchIdx]: Indicates the size along the X-axis of geometry data included in the patch identified by the tile ID and patch index.
pdu_geometry_2d_size_y_minus1[tileID][patchIdx]: Indicates the size along the Y-axis of geometry data included in the patch identified by the tile ID and patch index.
asps_vmc_ext_displacement_independent_partial_decode_enable_flag: Indicates whether the displacement is partially decodable independently.
When asps_vmc_ext_displacement_codec_id indicates HEVC, the patch data unit carries geometry MCTS information (pdu_geometry_mcts_info(tileID, patchIdx)).
When asps_vmc_ext_displacement_codec_id indicates VVC, the patch data unit carries geometry subpicture information (pdu_geometry_subpicture_info(tileID, patchIdx)) indicating an independent partial area (subpicture).
afps_vmc_ext_3d_offset_enable_flag: Indicates whether 3D extension offset is enabled. When 3D extension is enabled, the patch data unit carries each offset (pdu_3d_offset_u[tileID][patchIdx], pdu_3d_offset_v[tileID][patchIdx], pdu_3d_offset_d[tileID][patchIdx]).
Depending on asps_vmc_ext_num_attribute_video, the patch data unit carries the following elements.
When asps_vmc_ext_attribute_independent_partial_decode_enable_flag[i] indicates partial decoding, the patch data unit carries the following elements.
When asps_vmc_ext_attribute_codec_id [i] indicates HEVC, the patch data unit carries attribute MCTS information (pdu_attribute_mcts_info(i, tileID, patchIdx)). When asps_vmc_ext_attribute_codec_id [i] indicates VVC, the patch data unit carries attribute subpicture information (pdu_attribute_subpicture_info(i, tileID, patchIdx)).
When asps_vmc_ext_direct_attribute_projection_enabled_flag[i] indicates enabled, the patch data unit carries the following elements.
It carries Attribute position and size information (pdu_attributes_2d_pos_x[tileID][patchIdx][i], pdu_attributes_2d_pos_y[tileID][patchIdx][i], pdu_attributes_2d_size_x_minus1[tileID][patchIdx][i], and pdu_attributes_2d_size_y_minus1[tileID][patchIdx][i]). It carries pdu_projection_id[tileID][patchIdx][i] and pdu_orientation_id[tileID][patchIdx][i].
When asps_vmc_ext_displacement_independent_partial_decode_enable_flag is set to 1, and the displacement video is encoded with HEVC, motion constrained tile sets (MCTSs), which are independent decoding units supported by HEVC, may be used. The MCTS index to which the current patch belongs within the displacement image is signaled and transmitted in the geometry MCTS information (pdu_geometry_mcts_info). When the displacement video is encoded with VVC, subpictures, which are independent decoding units supported by VVC, may be used. The subpicture index to which the current patch belongs within the displacement image is signaled and transmitted in the geometry subpicture information (pdu_geometry_subpicture_info).
FIG. 17 illustrates geometry MCTS information and geometry subpicture information according to embodiments.
FIG. 17 illustrates the geometry MCTS information and geometry subpicture information included in FIG. 16 in detail.
The geometry MCTS information and geometry subpicture information may be generated for each tile ID and patch index.
The geometry MCTS information includes the following elements.
Displacement_mcts_ids as many as num_mcts_in_displacement_frame are carried.
The geometry subpicture information includes the following elements.
Displacement_subpicture_ids as many as num_subpictures_in_displacement_frame are carried.
When asps_vmc_ext_attribute_independent_partial_decode_enable_flag is set to 1, and the attribute video is encoded with HEVC, the MCTS index to which the current patch belongs within the attribute image is signaled and transmitted in the attribute MCTS information (pdu_attribute_mcts_info). When the attribute video is encoded with VVC, the subpicture index to which the current patch belongs within the attribute image is signaled and transmitted in the attribute subpicture information (pdu_attribute_subpicture_info).
FIG. 18 illustrates attribute MCTS information and attribute subpicture information according to embodiments.
FIG. 18 illustrates the attribute MCTS information and attribute subpicture information included in FIG. 16 in detail.
The attribute MCTS information carries the following elements.
It carries as many attribute_mcts_ids as num_mcts_in_attribute_frame.
The attribute subpicture information carries the following elements.
It carries as many attribute_subpicture_ids as num_subpictures_in_attribute_frame.
The reception (decoding) method/device according to embodiments is operated as follows.
A partial area within the mesh desired by a user is specified through a device, application, or software that uses and displays mesh content. The specified area is referred to as a target area. Based on the 3D position of the specified target area, the decoder may determine a corresponding target submesh. There may be one or more target submeshes, and the corresponding submesh indices may be derived based on encoded submesh-related information. In the embodiments, it is assumed that the target submesh and the corresponding submesh ID have been determined based on the user-specified target area information. Among the mesh components related to the target submesh, the displacement and attribute components are decoded. That is, in order to reconstruct the mesh components of the determined target submesh, the displacement and attribute bitstreams of the target submesh are decoded and reconstructed.
The decoder may determine whether partial decoding is enabled for the compressed displacement and attribute components based on the transmitted signal.
When asps_vmc_ext_displacement_independent_partial_decode_enable_flag is set to 1 (True), partial decoding may be performed on the displacement component for the target submesh area desired by the user. When the displacement component is compressed using a video codec such as HEVC or VVC, as indicated by asps_vmc_ext_displacement_codec_id, the embodiments may enable independent decoding for the target area within the image. To reconstruct the target submesh, patches having the corresponding submesh ID may be determined and reconstructed based on the signaled patch data for each patch.
For the patches constituting the target submesh, when the displacement component is encoded with HEVC, partial area decoding may be performed based on pdu_geometry_mcts_info. Based on displacement_mcts_id carried in the pdu geometry_mcts_info, the area information reated to the target MCTS index may be recovered from the HEVC MCTS SEI message contained in the displacement video bitstream. Based on the information, the bitstream corresponding to the image area for the target MCTS area may be decoded.
For the patches constituting the target submesh, when the displacement component is encoded with VVC, partial area decoding may be performed based on pdu_geometry_subpicture_info. Based on displacement_subpicture_id carried in the pdu geometry_subpicture_info, the bitstream corresponding to the target subpicture index may be extracted from the displacement video bitstream and decoded.
The reception method/device according to embodiments may perform image unpacking, inverse quantization, and inverse transform on the reconstructed displacement image data, and restore the data as the displacement component of the target submesh. The reconstructed data may be combined with the subdivided base mesh of the target submesh to reconstruct the mesh information related to the target submesh.
When asps_vmc_ext_attribute_independent_partial_decode_enable_flag is set to 1 (True), partial decoding may be performed on the attribute component for the target submesh area desired by the user. When the attribute component is compressed using a video codec such as HEVC or VVC, as indicated by asps_vmc_ext_attribute_codec_id, the embodiments may enable independent decoding for the target area within the image. To reconstruct the target submesh, patches having the corresponding submesh ID may be determined and reconstructed based on the signaled patch data for each patch.
For the patches constituting the target submesh, when the attribute component is encoded with HEVC, partial area decoding may be performed based on pdu_attribute_mcts_info. Based on attribute_mcts_id carried in the pdu_attribute_mcts_info, the area information reated to the target MCTS index may be recovered from the HEVC MCTS SEI message contained in the attribute video bitstream. Based on the information, the bitstream corresponding to the image area for the target MCTS area may be decoded.
For the patches constituting the target submesh, when the attribute component is encoded with VVC, partial area decoding may be performed based on pdu_attribute_subpicture_info. Based on attribute_subpicture_id carried in the pdu_attribute_subpicture_info, the bitstream corresponding to the target subpicture index may be extracted from the attribute video bitstream and decoded.
Based on the reconstructed attribute image data related to the target submesh, attribute map information related to the target submesh may be obtained. Based on the reconstructed texture coordinate information related to the target submesh, the attribute component of the target submesh area may be extracted from the reconstructed attribute map, and the attribute information related to the area may be restored.
Referring to FIG. 15, the atlas sequence parameter set extension RBSP syntax according to embodiments is configured as follows.
asps_vmc_ext_displacement_independent_partial_decode_enable_flag: Indicates whether partial decoding of the displacement components is enabled. When set to 1, it indicates that partial decoding is enabled.
asps_vmc_ext_displacement_codec_id: Indicates, when partial decoding of the displacement component is enabled, the codec used to encode the displacement component. The codecs corresponding to each value are shown in Table 1 above.
asps_vmc_ext_attribute_independent_partial_decode_enable_flag[i]: Indicates whether partial decoding of the i-th attribute component is enabled. When set to 1, it indicates that partial decoding of the i-th attribute component is enabled.
asps_vmc_ext_attribute_codec_id [i]: Indicates, when partial decoding of the i-th attribute component is enabled, the codec used to encode the i-th attribute component. The codecs corresponding to each value are shown in Table 2 above.
Referring to FIG. 16, the patch data unit syntax is configured as follows.
num_mcts_in_displacement_frame [tileID][patchIdx]: Indicates, when the displacement component is partially decodable and is encoded with HEVC, the number of HEVC MCTSs including the area in the image where the displacement component of patch patchIdx in tile tileID is positioned.
displacement_mcts_id [tileID][patchIdx][k]: Indicates, when the displacement component is partially decodable and is encoded with HEVC, the k-th MCTS index of the HEVC MCTSs including the area in the image where the displacement component of patch patchIdx in tile tileID is positioned.
num_subpictures_in_displacement_frame [tileID][patchIdx]: Indicates, when the displacement component is partially decodable and is encoded with VVC, the number of VVC subpictures including the area in the image where the displacement component of patch patchIdx in tile tileID is positioned.
displacement_subpicture_id [tileID][patchIdx][k]: Indicates, when the displacement component is partially decodable and is encoded with VVC, the k-th subpicture index of the VVC subpictures including the area in the image where the displacement component of patch patchIdx in tile tileID is positioned.
num_mcts_in_attribute_frame [i][tileID][patchIdx]: Indicates, when the i-th attribute component is partially decodable and is encoded with HEVC, the number of HEVC MCTSs including the area in the image where the attribute component of patch patchIdx in tile tileID is positioned.
attribute_mcts_id [i][tileID][patchIdx][k]: Indicates, when the i-th attribute component is partially decodable and is encoded with HEVC, the k-th MCTS index of the HEVC MCTSs including the area in the image where the attribute component of patch patchIdx in tile tileID is positioned.
num_subpictures_in_attribute_frame [i][tileID][patchIdx]: Indicates, when the i-th attribute component is partially decodable and is encoded with VVC, the number of VVC subpictures including the area in the image where the attribute component of patch patchIdx in tile tileID is positioned.
attribute_subpicture_id[i][tileID][patchIdx][k]: Indicates, when the i-th attribute component is partially decodable and is encoded with VVC, the k-th subpicture index of the VVC subpictures including the area in the image where the attribute component of patch patchIdx in tile tileID is positioned.
FIG. 19 illustrates a V-DMC transmission device according to embodiments.
The transmission device in FIG. 19 corresponds to the transmission device and the dynamic mesh video encoder (V-DMC) 102 in FIG. 1, and the encoders in FIGS. 6, 7, and 13.
The transmission device (encoder) operates as follows. The transmission device may transmit signals related to the partial area decoding according to the embodiments in an auxiliary information bitstream that is transmitted by V-DMC.
Based on the submesh area information determined by the submesh generator, the displacement vector video generator may generate displacement vectors. In this case, the displacement vector information corresponding to each submesh may be generated such that they are present in some areas in an image. When the patches belonging to the same submesh are present in similar areas within the displacement vector image, the data that are transmitted using the proposed signal as illustrated in FIGS. 15 to 18 may be reduced, and independent partial area decoding by the decoder using a video codec may be performed more efficiently.
The mesh pre-processor may generate texture coordinates for a simplified version of the input original mesh, and the texture map video generator may transform the original texture map based on the generated texture coordinate information and regenerate a texture map to be encoded. According to embodiments, as shown in FIGS. 15 to 18, partial area decoding of the texture map may be performed using a signal. Moreover, for efficient partial area decoding using a video codec along with the minimized transmission signal, it may be advantageous to allow the texture map information for one submesh to be present in some areas within the regenerated texture map. To this end, when generating texture coordinates, the mesh pre-processor may generate texture coordinates for each submesh. Thus, the texture map video generator regenerate a texture map such that the texture map information related to each submesh may be distinguished.
Referring to FIG. 19, the submesh generator may be connected to the encoder of the transmission device, or may be included in the submesh generator of the encoder. The encoder may generate the atlas sequence parameter set, patch data unit, geometry MCTS information, geometry subpicture information, attribute MCTS information, and attribute subpicture information according to FIGS. 15 to 18, and transmit the same in an auxiliary information bitstream. The the atlas sequence parameter set, patch data unit, geometry MCTS information, geometry subpicture information, attribute MCTS information, and attribute subpicture information according to FIGS. 15 to 18 include information related to the submesh area. A displacement vector video generator may be connected to the encoder of the transmission device, or may be included in the displacement vector video generator of the encoder. The encoder may generate an image containing displacement vector information related to each submesh based on information related to the submesh areas. The mesh pre-processor may also be connected to the encoder of the transmission device or may be included in the mesh pre-processor of the encoder. The encoder generates texture coordinates (geometry) for the mesh. The texture map video generator may be connected to or included in the encoder. Based on the texture coordinates for the mesh, the encoder may transform and regenerate the texture map. The texture map may be processed based on the information related to the submesh areas.
FIG. 20 illustrates a V-DMC reception device according to embodiments.
The reception device in FIG. 20 corresponds to the reception device and the dynamic mesh video decoder (V-DMC) 113 in FIG. 1, and the decoders in FIGS. 11, 12, and 14.
The reception device (decoder) operates as follows. According to embodiments, the texture map represents an attribute component and may be one of multiple attribute components included in the mesh.
Depending on the use scenario, when a user desires to use either the entire mesh data or only a specific partial area thereof, user input may be received through a user-specified area receiver. Based on the received input, a target submesh to be reconstructed may be determined from the auxiliary information bitstream in the received bitstream. The target submesh index, tile index for the tile area of the corresponding atlas data, and patch indices for the patches belonging to the tile area may be determined through a target submesh determiner. Further, related information corresponding to the target submesh may be determined in the transmitted information by the receiver. Based on the determined target area information, the receiver reconstructs the base mesh, motion vectors, displacement vectors, and texture map components of the target submesh.
According to embodiments, it may be determined whether partial area decoding is enabled for the displacement vectors and the texture map, based on the received proposed signal. When partial area decoding is enabled for the displacement vectors or the texture map, signaling (which may be referred to as signaling information, metadata, or parameters) for partial area reconstruction may be received based on the codec information used for decoding of each component. According to embodiments, partial area decoding may be performed based on patch data having the submesh index, tile index, and patch index determined during encoding. The aforementioned signaling information may be utilized in this case.
The target submesh displacement vector decoder may perform partial area information decoding on the displacement vector component based on signaling information included in the geometry MCTS information (pdu_geometry_mcts_info) or geometry subpicture information (pdu_geometry_subpicture_info). Based on the signaling information, independent partial area decoding may be performed on the target area in the displacement vector video using a video codec. The decoding result is reconstructed as the displacement vector component to be used to reconstruct the target submesh mesh by the target submesh displacement vector reconstructor. The target submesh mesh reconstructor combines the reconstructed base mesh and displacement vector of the target submesh to reconstruct the final target mesh.
The target submesh texture map video decoder may perform partial area decoding on the texture map component based on signaling information included in the attribute MCTS information (pdu_attribute_mcts_info) or attribute subpicture information (pdu_attribute_subpicture_info). Based on the signaling information, independent partial area decoding may be performed on the target area in the texture map video using a video codec. The decoding result may be used as the texture map component of the target submesh.
The mesh and texture map of the target area reconstructed through the above process are processed by the mesh renderer and displayed to the user.
Referring to FIG. 20, the decoder may parse signaling information such as that shown in FIGS. 15 to 18 from the bitstream. Based on the signaling information, the decoder may identify submesh area-related information and may partially decode the target submesh through the target submesh determiner. The decoder may decode displacement vector information related to the target submesh through the target submesh displacement vector decoder. The decoder may decode the texture map related to the target submesh through the target submesh texture map video decoder.
While various use scenarios, devices, and applications using dynamic mesh may utilize the entire dynamic mesh data, there may also be cases where information about a partial area is needed. In such cases, it is more efficient in terms of processing time and resources for a device or software rendering the dynamic mesh to receive the mesh area information related to the needed area from the user and decode only the area to display the area or use the same for another area, than to process the entire mesh data. Currently, V-DMC, which is technology for decoding dynamic mesh, does not support technology for extracting and restoring only partial area information from the input bitstream. Therefore, to enhance its applicability, the partial area reconstruction technology described above needs to be applied. Although V-DMC currently defines the concept of submeshes for partial decoding, it does not define either a partial decoding method for components constituting a submesh or signaling for encoding/decoding of the components.
From this perspective, embodiments propose a method for supporting mesh partial access and reconstruction in V-DMC. In particular, when video compression techniques are applied to the displacement and attribute components in the V-DMC bitstream, independent video decoding units for partial decoding may be applied, allowing the displacement and attribute components of submeshes to be independently decoded. In this regard, a signal indicating whether partial decoding is enabled is provided. In V-DMC, patch data information is transmitted, and additional signals for partial decoding are provided. Through the embodiments, partial area decoding and data reconstruction may be performed for displacement and attribute components based on the submesh corresponding to a user-specified target area. Particularly, in decoding the attribute component, which accounts for the largest data portion of the V-DMC bitstream, efficiency may be improved in terms of the time and resource usage. The embodiments may be used in combination with base mesh reconstruction techniques based on submeshes. Thereby, high-quality dynamic mesh partial access and reconstruction may be provided.
FIG. 21 illustrates a method of transmitting mesh data according to embodiments.
In operation S2100, the mesh data transmission method according to the embodiments may include encoding mesh data.
The encoding operation according to the embodiments may include the operations of the transmission device 100 and dynamic mesh encoder 102 of FIG. 1, the pre-processor 200 and encoder 201 of FIG. 2, the pre-processors of FIGS. 3 to 5, the encoders of FIGS. 6, 7, 13, and 19, and the information generation of FIG. 18.
In operation S2101, the mesh data transmission method according to the embodiments may further include transmitting a bitstream containing the mesh data.
The transmission operation according to the embodiments may include operations such as transmission of a bitstream according to the transmission device 100, file/segment encapsulator 103, and transmitter 104 of FIG. 1, the pre-processor 200 and encoder 201 of FIG. 2, the pre-processors of FIGS. 3 to 5, the encoders of FIGS. 6, 7, 13, and 20, and transmission of bitstreams containing the information shown in FIGS. 15 to 18.
FIG. 22 illustrates a method of receiving mesh data according to embodiments.
In operation S2200, the mesh data reception method according to the embodiments may include receiving a bitstream containing mesh data.
The reception operation according to the embodiments may include the operations of the reception device 110, receiver 111, and file/segment decapsulator 112 of FIG. 1.
In operation S2201, the mesh data receiving method according to the embodiments may further include decoding the mesh data.
The decoding operation according to the embodiments may include the operations of the dynamic mesh video decoder 113 and renderer 114 of FIG. 2, the decoders of FIGS. 11, 12, 14, and 19, and the decoding of the information shown in FIGS. 15 to 18.
The mesh data transmission and reception methods according to the embodiments correspond to the point cloud data transmission and reception methods. They represent the case where the point cloud is of mesh type. Since mesh data is also composed of point clouds, the terms are interpreted as having the same meaning as the point cloud data.
Referring to FIG. 1, the mesh data transmission method according to embodiments may include encoding mesh data, and transmitting a bitstream containing the mesh data.
Referring to FIG. 19, regarding the submesh generator, the encoding the mesh data may include generating area information related to a submesh related to the mesh data.
Referring to FIG. 15, regarding the atlas sequence parameter set as auxiliary information, the area information related to the submesh may include information indicating whether partial decoding of a displacement related to the mesh data is enabled (asps_vmc_ext_displacement_independent_partial_decode_enable_flag), and information indicating whether partial decoding of attributes related to the mesh data is enabled (asps_vmc_ext_attribute_independent_partial_decode_enable_flag).
Referring to FIG. 15 and Tables 1 and 2, based on the information indicating whether the partial decoding of the displacement related to the mesh data is enabled, the area information related to the submesh may include information about a codec used to encode the displacement (asps_vmc_ext_displacement_codec_id). Based on the information indicating whether the partial decoding of the attributes related to the mesh data is enabled, the area information related to the submesh may include information about a codec used to encode the attributes (asps_vmc_ext_attribute_codec_id).
Referring to FIG. 16, regarding patch data units included in the bitstream, based on an encoding scheme for the displacement related to the mesh data, the area information related to the submesh may include at least one of tile set information for geometry related to a tile ID and a patch index (pdu_geometry_mcts_info(tileID, patchIdx)), or subpicture information for the geometry related to the tile ID and the patch index (pdu_geometry_subpicture_info(tileID, patchIdx)). Based on an encoding scheme for the attributes related to the mesh data, the area information may include at least one of tile set information for the attributes related to the tile ID and the patch index (pdu_attribute_mcts_info(i, tileID, patchIdx)), or subpicture information for the attributes related to the tile ID and the patch index (pdu_attribute_subpicture_info(i, tileID, patchIdx)).
Referring to FIG. 17, the tile set information for the geometry may include the number of tile sets for an area including the displacement (num_mcts_in_displacement_frame [tileID][patchIdx]), and indices of the tile sets for the area including the displacement (displacement_mcts_id [tileID][patchIdx][k]). The subpicture information for the geometry may include the number of subpictures for the area including the displacement (num_subpictures_in_displacement_frame [tileID][patchIdx]), and indices of the subpictures for the area including the displacement (displacement_subpicture_id [tileID][patchIdx][k]).
Referring to FIG. 18, the tile set information for the attributes may include the number of tile sets for an area including the attributes (num_mcts_in_attribute_frame [i][tileID][patchIdx]), and indices of the tile sets for the area including the attributes (attribute_mcts_id [i][tileID][patchIdx][k]). The subpicture information for the attributes may include the number of subpictures for the area including the attributes (num_subpictures_in_attribute_frame [i][tileID][patchIdx]), and indices of the subpictures for the area including the attributes (attribute_subpicture_id [i][tileID][patchIdx][k]).
The mesh data transmission method according to the embodiments is performed by a transmission device. The transmission device may include an encoder configured to encode mesh data, and a transmitter configured to transmit a bitstream containing the mesh data. The transmission device may include a memory storing instructions related to the encoding operation and a processor configured to execute the encoding operation.
In the reverse process of the mesh data transmission method according to the embodiments, a reception method may be performed, which may include receiving mesh data and decoding the mesh data. The mesh data reception method may include receiving a bitstream containing the mesh data, and decoding the mesh data. The reception method may include receiving the mesh data encoded by the transmission method, and area information for submeshes related to the encoding of the mesh data, and decoding a target submesh.
The mesh data reception method according to the embodiments is performed by a reception device. The reception device may include a receiver configured to receive a bitstream containing, and a decoder configured to decode the mesh data. The reception device may include a memory storing decoding instructions and a processor configured to perform the decoding operation.
Accordingly, instead of decoding the entire bitstream of the mesh content, a partial mesh area may be efficiently decoded. The receiving side may receive only the information about an area desired by the user, and extract and reconstruct only the bitstream related to the area based on the received information. Using specific area units such as submeshes, more specific areas than patches may be partially accessed and reconstructed.
The embodiments have been described in terms of a method and/or a device. The description of the method and the description of the device may complement each other.
Although embodiments have been described with reference to each of the accompanying drawings for simplicity, it is possible to design new embodiments by merging the embodiments illustrated in the accompanying drawings. If a recording medium readable by a computer, in which programs for executing the embodiments mentioned in the foregoing description are recorded, is designed by those skilled in the art, it may also fall within the scope of the appended claims and their equivalents. The devices and methods may not be limited by the configurations and methods of the embodiments described above. The embodiments described above may be configured by being selectively combined with one another entirely or in part to enable various modifications. Although preferred embodiments have been described with reference to the drawings, those skilled in the art will appreciate that various modifications and variations may be made in the embodiments without departing from the spirit or scope of the disclosure described in the appended claims. Such modifications are not to be understood individually from the technical idea or perspective of the embodiments.
Various elements of the devices of the embodiments may be implemented by hardware, software, firmware, or a combination thereof. Various elements in the embodiments may be implemented by a single chip, for example, a single hardware circuit. According to embodiments, the components according to the embodiments may be implemented as separate chips, respectively. According to embodiments, at least one or more of the components of the device according to the embodiments may include one or more processors capable of executing one or more programs. The one or more programs may perform any one or more of the operations/methods according to the embodiments or include instructions for performing the same. Executable instructions for performing the method/operations of the device according to the embodiments may be stored in a non-transitory CRM or other computer program products configured to be executed by one or more processors, or may be stored in a transitory CRM 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 covering not only volatile memories (e.g., RAM) but also nonvolatile memories, flash memories, and PROMs. In addition, it may also be implemented in the form of a carrier wave, such as transmission over the Internet. In addition, the processor-readable recording medium may be distributed to computer systems connected over a network such that the processor-readable code may be stored and executed in a distributed fashion.
In this document, the term “/” and “,” should be interpreted as indicating “and/or.” For instance, the expression “A/B” may mean “A and/or B.” Further, “A, B” may mean “A and/or B.” Further, “A/B/C” may mean “at least one of A, B, and/or C.” “A, B, C” may also mean “at least one of A, B, and/or C.” Further, in the document, the term “or” should be interpreted as “and/or.” For instance, the expression “A or B” may mean 1) only A, 2) only B, and/or 3) both A and B. In other words, the term “or” in this document should be interpreted as “additionally or alternatively.”
Terms such as first and second may be used to describe various elements of the embodiments. However, various components according to the embodiments should not be limited by the above terms. These terms are only used to distinguish one element from another. For example, a first user input signal may be referred to as a second user input signal. Similarly, the second user input signal may be referred to as a first user input signal. Use of these terms should be construed as not departing from the scope of the various embodiments. The first user input signal and the second user input signal are both user input signals, but do not mean the same user input signal unless context clearly dictates otherwise.
The terminology used to describe the embodiments is used for the purpose of describing particular embodiments only and is not intended to be limiting of the embodiments. As used in the description of the embodiments and in the claims, the singular forms “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise. The expression “and/or” is used to include all possible combinations of terms. The terms such as “includes” or “has” are intended to indicate existence of figures, numbers, steps, elements, and/or components and should be understood as not precluding possibility of existence of additional existence of figures, numbers, steps, elements, and/or components. As used herein, conditional expressions such as “if” and “when” are not limited to an optional case and are intended to be interpreted, when a specific condition is satisfied, to perform the related operation or interpret the related definition according to the specific condition.
Operations according to the embodiments described in this specification may be performed by a transmission/reception device including a memory and/or a processor according to embodiments. The memory may store programs for processing/controlling the operations according to the embodiments, and the processor may control various operations described in this specification. The processor may be referred to as a controller or the like. In embodiments, operations may be performed by firmware, software, and/or combinations thereof. The firmware, software, and/or combinations thereof may be stored in the processor or the memory.
The operations according to the above-described embodiments may be performed by the transmission device and/or the reception device according to the embodiments. The transmission/reception device may include a transmitter/receiver configured to transmit and receive media data, a memory configured to store instructions (program code, algorithms, flowcharts and/or data) for the processes according to the embodiments, and a processor configured to control the operations of the transmission/reception device.
The processor may be referred to as a controller or the like, and may correspond to, for example, hardware, software, and/or a combination thereof. The operations according to the above-described embodiments may be performed by the processor. In addition, the processor may be implemented as an encoder/decoder for the operations of the above-described embodiments.
Various embodiments have been described in the best mode for carrying out the disclosure.
As described above, the embodiments may be fully or partially applied to the point cloud data transmission/reception device and system.
It will be apparent to those skilled in the art that various changes or modifications may be made to the embodiments within the scope of the embodiments.
Thus, it is intended that the embodiments cover modifications/variations provided they come within the scope of the appended claims and their equivalents.
