Processing a point cloud

Technical Field

At least one of the present embodiments relates generally to a processing of a point cloud. In particular, the present embodiments relate to the use of the V-PCC syntax to signal MIV metadata relative to 3DoF+ (volumetric) video.

Background

The present section is intended to introduce the reader to various aspects of art, which may be related to various aspects of at least one of the present embodiments that is described and/or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of at least one embodiment.

Point clouds may be used for various purposes such as culture heritage/buildings in which objects like statues or buildings are scanned in 3D in order to share the spatial configuration of the object without sending or visiting it. Also, it is a way to ensure preserving the knowledge of the object in case it may be destroyed; for instance, a temple by an earthquake. Such point clouds are typically static, colored and huge.

Another use case is in topography and cartography in which using 3D representations allows for maps that are not limited to the plane and may include the relief. Google Maps is now a good example of 3D maps but uses meshes instead of point clouds. Nevertheless, point clouds may be a suitable data format for 3D maps and such point clouds are typically static, colored and huge.

The automotive industry and the autonomous car are also domains in which point clouds may be used. Autonomous cars should be able to“probe” their environment to make good driving decisions based on the reality of their immediate neighbors. Typical sensors like LIDARs (Light Detection And Ranging) produce dynamic point clouds that are used by a decision engine. These point clouds are not intended to be viewed by a human being and they are typically small, not necessarily colored, and dynamic with a high frequency of capture. These point clouds may have other attributes like the reflectance provided by the LIDAR as this attribute provides good information on the material of the sensed object and may help in making decisions.

Virtual Reality and immersive worlds have become hot topics recently and are foreseen by many as the future of 2D flat video. The basic idea is to immerse the viewer in an environment that surrounds the viewer, in contrast to a standard TV in which the viewer can only look at the virtual world in front of the viewer. There are several gradations in the immersivity depending on the freedom of the viewer in the environment. A point cloud is a good format candidate for distributing Virtual Reality (VR) worlds.

It is important in many applications to be able to distribute dynamic point clouds to an end-user (or store them in a server) by consuming only a reasonable amount of bit-rate (or storage space for storage applications) while maintaining an acceptable (or preferably very good) quality of experience. Efficient compression of these dynamic point clouds is a key point in order to make the distribution chain of many immersive worlds practical.

At least one embodiment has been devised with the foregoing in mind.

Summary

The following presents a simplified summary of at least one of the present embodiments in order to provide a basic understanding of some aspects of the present disclosure. This summary is not an extensive overview of an embodiment. It is not intended to identify key or critical elements of an embodiment. The following summary merely presents some aspects of at least one of the present embodiments in a simplified form as a prelude to the more detailed description provided elsewhere in the document.

According to a general aspect of at least one embodiment, there is provided a method for signaling metadata relative to volumetric video by using at least one syntax element of a bitstream representative of a point cloud video.

According to an embodiment, the method comprises:

- embedding the metadata into said at least one syntax element;

- transmitting and receiving said at least one syntax element;

- obtaining the metadata from said at least one syntax element.

According to an embodiment, the metadata are relative to real or virtual cameras.

According to an embodiment, the metadata are relative to patch atlas used for encoding the volumetric data.

According to an embodiment, all the patches of a patch atlas are signalled in all intra- or predictive-coded frames inside a syntax element containing only intra-coded patches.

According to an embodiment, a specific frame rate for the metadata may be used to fix a transmission rate of metadata.

According to another general aspect of the present embodiments, a method for encoding or decoding volumetric data comprising an above method for signalling metadata relative to said volumetric data.

One or more embodiment also provide apparatus, a computer program product, a non-transitory computer readable medium and a bitstream.

The specific nature of at least one of the present embodiments as well as other objects, advantages, features and uses of said at least one of the present embodiments will become evident from the following description of examples taken in conjunction with the accompanying drawings.

Brief Description of Drawings

In the drawings, examples of several embodiments are illustrated. The drawings show: - Fig. 1 illustrates a schematic block diagram of an example of a two- layer-based point cloud encoding structure in accordance with at least one of the present embodiments;

- Fig. 2 illustrates a schematic block diagram of an example of a two- layer-based point cloud decoding structure in accordance with at least one of the present embodiments;

- Fig. 3 illustrates a schematic block diagram of an example of an image-based point cloud encoder in accordance with at least one of the present embodiments;

- Fig. 3a illustrates an example of a canvas comprising 2 patches and their 2D bounding boxes;

- Fig. 3b illustrates an example of two in-between 3D samples located between two 3D samples along a projection line;

- Fig. 4 illustrates a schematic block diagram of an example of an image-based point cloud decoder in accordance with at least one of the present embodiments;

- Fig. 5 illustrates schematically an example of syntax of a bitstream representative of a base layer BL in accordance with at least one of the present embodiments;

- Fig. 6 illustrates a schematic block diagram of an example of a system in which various aspects and embodiments are implemented;

- Fig. 7 illustrates a schematic block diagram of an example of a TMIV encoding and decoding structure in accordance with prior art;

- Fig. 8 illustrates a schematic bloc diagram of an example of an atlas constructor in accordance with prior art;

- Figs. 9-11 illustrates examples of syntax elements relative to cameras;

- Fig. 12-13 illustrate examples of syntax elements relative to patch atlas;

- Fig. 14 illustrates a simplified architecture of a V-PCC codec in accordance with prior art;

- Fig. 15 represents the simplified architecture of a volumetric video codec in accordance with prior art; - Fig. 16 illustrates a simplified architecture of a V-PCC codec in accordance with at least one embodiment;

- Fig. 17 illustrates a simplified architecture of a V-PCC decoder in accordance with at least one embodiment;

- Fig. 18 illustrates a flowchart of a method 1800 for signalling MIV metadata in a V-PCC bitstream in accordance with at least one embodiment;

- Figs. 19- 19b illustrate examples of syntax elements related to camera parameters in accordance with at least one embodiment;

- Fig. 20-20f illustrate examples of syntax elements related to patch data in accordance with at least one embodiment; and

- Fig. 21-21a illustrate examples of syntax elements related to patch metadata coding modes in accordance with at least one embodiment;

Detailed Description

At least one of the present embodiments is described more fully hereinafter with reference to the accompanying figures, in which examples of at least one of the present embodiments are shown. An embodiment may, however, be embodied in many alternate forms and should not be construed as limited to the examples set forth herein. Accordingly, it should be understood that there is no intent to limit embodiments to the particular forms disclosed. On the contrary, the disclosure is intended to cover all modifications, equivalents, and alternatives falling within the spirit and scope of this application.

When a figure is presented as a flow diagram, it should be understood that it also provides a block diagram of a corresponding apparatus. Similarly, when a figure is presented as a block diagram, it should be understood that it also provides a flow diagram of a corresponding method/process.

Similar or same elements of figures are referenced with the same reference numbers.

Some figures represent syntax tables widely used in V-PCC for defining the structure of a bitstream that conforms with V-PCC. In those syntax tables, the term denotes unchanged portions of the syntax with respect to the original definition given in V-PCC and removed in the figures to facilitate reading. Bold terms in figures indicate that a value for this term is obtained by parsing a bitstream. The right column of the syntax tables indicates the number of bits for encoding a data of a syntax element. For example, u(4) indicates that 4 bits are used for encoding a data, u(8) indicates 8 bits, ae(v) indicates a context adaptive arithmetic entropy coded syntax element.

The aspects described and contemplated below may be implemented in many different forms. Figs. 1-21 a below provide some embodiments, but other embodiments are contemplated and the discussion of Figs. 1-21a does not limit the breadth of the implementations.

At least one of the aspects generally relates to point cloud encoding and decoding, and at least one other aspect generally relates to transmitting a bitstream generated or encoded.

More precisely, various methods and other aspects described herein may be used to modify modules, for example, the image-based encoder 3000 and decoder 4000 as shown in Figs. 1-2.

Moreover, the present aspects are not limited to MPEG standards such as MPEG-I part 5 that relates to the Point Cloud Compression, and may be applied, for example, to other standards and recommendations, whether pre existing or future-developed, and extensions of any such standards and recommendations (including MPEG-I part 5). Unless indicated otherwise, or technically precluded, the aspects described in this application may be used individually or in combination.

In the following, image data refer to data, for example, one or several arrays of 2D samples in a specific image/video format. A specific image/video format may specify information pertaining to pixel values of an image (or a video). A specific image/video format may also specify information which may be used by a display and/or any other apparatus to visualize and/or decode an image (or video) for example. An image typically includes a first component, in the shape of a first 2D array of samples, usually representative of luminance (or luma) of the image. An image may also include a second component and a third component, in the shape of other 2D arrays of samples, usually representative of the chrominance (or chroma) of the image. Some embodiments represent the same information using a set of 2D arrays of color samples, such as the traditional tri-chromatic RGB representation.

A pixel value is represented in one or more embodiments by a vector of C values, where C is the number of components. Each value of a vector is typically represented with a number of bits which may define a dynamic range of the pixel values.

An image block means a set of pixels which belong to an image. The pixel values of an image block (or image block data) refer to the values of the pixels which belong to this image block. An image block may have an arbitrary shape, although rectangles are common.

A point cloud may be represented by a dataset of 3D samples within a 3D volumetric space that have unique coordinates and that may also have one or more attributes.

A 3D sample of this data set may be defined by its spatial location (X, Y, and Z coordinates in a 3D space) and possibly by one or more associated attributes such as a color, represented in the RGB or YUV color space for example, a transparency, a reflectance, a two-component normal vector or any feature representing a feature of this sample. For example, a 3D sample may be defined by 6 components (X, Y, Z, R, G, B) or equivalently (X, Y, Z, y, U, V) where (C,U,Z) defines the coordinates of a point in a 3D space and (R,G,B) or (y,U,V) defines a color of this 3D sample. The same type of attribute may be present multiple times. For example, multiple color attributes may provide color information from different points of view.

A point cloud may be static or dynamic depending on whether or not the cloud changes with respect to time. A static point cloud or an instance of a dynamic point cloud is usually denoted as a point cloud frame. It should be noticed that in the case of a dynamic point cloud, the number of points is generally not constant but, on the contrary, generally changes with time. More generally, a point cloud may be considered as dynamic if anything changes with time, such as, for example, the number of points, the position of one or more points, or any attribute of any point.

As an example, a 2D sample may be defined by 6 components (u, v, Z, R, G, B) or equivalently (u, v, Z, y, U, V). (u,v) defines the coordinates of a 2D sample in a 2D space of the projection plane. Z is the depth value of a projected 3D sample onto this projection plane. (R,G,B) or (y,U,V) defines a color of this 3D sample.

Fig. 1 illustrates a schematic block diagram of an example of a two- layer-based point cloud encoding structure 1000 in accordance with at least one of the present embodiments.

The two-layer-based point cloud encoding structure 1000 may provide a bitstream B representative of an input point cloud frame IPCF. Possibly, said input point cloud frame IPCF represents a frame of a dynamic point cloud. Then, a frame of said dynamic point cloud may be encoded by the two-layer- based point cloud encoding structure 1000 independently from another frame.

Basically, the two-layer-based point cloud encoding structure 1000 may provide ability to structure the bitstream B as a Base Layer BL and an Enhancement Layer EL. The base layer BL may provide a lossy representation of an input point cloud frame IPCF and the enhancement layer EL may provide a higher quality (possibly lossless) representation by encoding isolated points not represented by the base layer BL.

The base layer BL may be provided by an image-based encoder 3000 as illustrated in Fig. 3. Said image-based encoder 3000 may provide geometry/texture images representing the geometry/attributes of 3D samples of the input point cloud frame IPCF. It may allow isolated 3D samples to be discarded. The base layer BL may be decoded by an image-based decoder 4000 as illustrated in Fig. 4 that may provide an intermediate reconstructed point cloud frame IRPCF.

Then, back to the two-layer-based point cloud encoding 1000 in Fig. 1 , a comparator COMP may compare the 3D samples of the input point cloud frame IPCF to the 3D samples of the intermediate reconstructed point cloud frame IRPCF in order to detect/locate missed/isolated 3D samples. Next, an encoder ENC may encode the missed 3D samples and may provide the enhancement layer EL. Finally, the base layer BL and the enhancement layer EL may be multiplexed together by a multiplexer MUX so as to generate the bitstream B.

According to an embodiment, the encoder ENC may comprise a detector that may detect and associate a 3D reference sample R of the intermediate reconstructed point cloud frame IRPCF to a missed 3D samples M.

For example, a 3D reference sample R associated with a missed 3D sample M may be its nearest neighbor of M according to a given metric.

According to an embodiment, the encoder ENC may then encode the spatial locations of the missed 3D samples M and their attributes as differences determined according to spatial locations and attributes of said 3D reference samples R.

In a variant, those differences may be encoded separately.

For example, for a missed 3D sample M, with spatial coordinates x(M), y(M) and z(M), a x-coordinate position difference Dx(M), a y-coordinate position difference Dy(M), a z-coordinate position difference Dz(M), a R- attribute component difference Dr(M), a G-attribute component difference Dg(M) and the B-attribute component difference Db(M) may be calculated as follows:

Dx(M)=x(M)-x(R),

where x(M) is the x-coordinate of the 3D sample M, respectively R in a geometry image provided by Fig. 3,

Dy(M)=y(M)-y(R)

where y(M) is the y-coordinate of the 3D sample M, respectively R in a geometry image provided by Fig. 3,

Dz(M)=z(M)-z(R)

where z(M) is the z-coordinate of the 3D sample M, respectively R in a geometry image provided by Fig. 3,

Dr(M)=R(M)-R(R). where R(M), respectively R(R) is the r-color component of a color attribute of the 3D sample M, respectively R,

Dg(M)=G(M)-G(R).

where G(M), respectively G(R) is the g-color component of a color attribute of the 3D sample M, respectively R,

Db(M)=B(M)-B(R).

where B(M), respectively B(R) is the b-color component of a color attribute of the 3D sample M, respectively R.

Fig. 2 illustrates a schematic block diagram of an example of a two- layer-based point cloud decoding structure 2000 in accordance with at least one of the present embodiments.

The behavior of the two-layer-based point cloud decoding structure 2000 depends on its capabilities.

A two-layer-based point cloud decoding structure 2000 with limited capabilities may access only the base layer BL from the bitstream B by using a de-multiplexer DMUX, and then may provide a faithful (but lossy) version IRPCF of the input point cloud frame IPCF by decoding the base layer BL by a point cloud decoder 4000 as illustrated in Fig. 4.

A two-layer-based point cloud decoding structure 2000 with full capabilities may access both the base layer BL and the enhancement layer EL from the bitstream B by using the de-multiplexer DMUX. The point cloud decoder 4000, as illustrated in Fig. 4, may determine the intermediate reconstructed point cloud frame IRPCF from the base layer BL. The decoder DEC may determine a complementary point cloud frame CPCF from the enhancement layer EL. A combiner COM then may combine together the intermediate reconstructed point cloud frame IRPCF and the complementary point cloud frame CPCF to therefore provide a higher quality (possibly lossless) representation (reconstruction) CRPCF of the input point cloud frame IPCF.

Fig. 3 illustrates a schematic block diagram of an example of an image- based point cloud encoder 3000 in accordance with at least one of the present embodiments. The image-based point cloud encoder 3000 leverages existing video codecs to compress the geometry and texture (attribute) information of a dynamic point cloud. This is accomplished by essentially converting the point cloud data into a set of different video sequences.

In particular embodiments, two videos, one for capturing the geometry information of the point cloud data and another for capturing the texture information, may be generated and compressed using existing video codecs. An example of an existing video codec is the HEVC Main profile encoder/decoder (ITU-T H.265 Telecommunication standardization sector of ITU (02/2018), series H: audiovisual and multimedia systems, infrastructure of audiovisual services - coding of moving video, High efficiency video coding, Recommendation ITU-T H.265).

Additional metadata that are used to interpret the two videos are typically also generated and compressed separately. Such additional metadata includes, for example, an occupancy map OM and/or auxiliary patch information PI.

The generated video bitstreams and the metadata may be then multiplexed together so as to generate a combined bitstream.

It should be noted that the metadata typically represents a small amount of the overall information. The bulk of the information is in the video bitstreams.

An example of such a point cloud coding/decoding process is given by the Test model Category 2 algorithm (also denoted V-PCC) that implements the MPEG draft standard as defined in ISO/IEC JTC1/SC29/WG1 1 MPEG2019/W18479 (March 25 ^th -29 ^th , Geneva).

In step 3100, a module PGM may generate at least one patch by decomposing 3D samples of a data set representative of the input point cloud frame IPCF to 2D samples on a projection plane using a strategy that provides best compression.

A patch may be defined as a set of 2D samples. A patch frame is a frame comprising at least one patch. A patch frame may be divided into one or more tile rows and one or more tile columns. A tile is a rectangular region of a patch frame. For example, in V-PCC, a normal at every 3D sample is first estimated as described, for example, in Hoppe et al. (Hugues Hoppe, T ony DeRose, T om Duchamp, John McDonald, Werner Stuetzle. Surface reconstruction from unorganized points. ACM SIGGRAPH 1992 Proceedings , 71 -78). Next, an initial clustering of the input point cloud frame IPCF is obtained by associating each 3D sample with one of the six oriented planes of a 3D bounding box encompassing the 3D samples of the input point cloud frame IPCF. More precisely, each 3D sample is clustered and associated with an oriented plane that has the closest normal (that is maximizes the dot product of the point normal and the plane normal). Then the 3D samples are projected to their associated planes. A set of 3D samples that forms a connected area in their plane is referred as a connected component. A connected component is a set of at least one 3D sample having similar normal and a same associated oriented plane. The initial clustering is then refined by iteratively updating the cluster associated with each 3D sample based on its normal and the clusters of its nearest neighboring samples. The final step consists of generating one patch from each connected component, that is done by projecting the 3D samples of each connected component onto the oriented plane associated with said connected component. A patch is associated with auxiliary patch information PI that represents auxiliary patch information defined for each patch to interpret the projected 2D samples that correspond to the geometry and/or attribute information.

In V-PCC, for example, the auxiliary patch information PI includes 1 ) information indicating one of the six oriented planes of a 3D bounding box encompassing the 3D samples of a connected component; 2) information relative to the plane normal; 3) information determining the 3D location of a connected component relative to a patch represented in terms of depth, tangential shift and bi-tangential shift; and 4) information such as coordinates (uO, vO, u1 , v1 ) in a projection plane defining a 2D bounding box encompassing a patch.

In step 3200, a patch packing module PPM may map (place) at least one generated patch onto a 2D grid (also called canvas) without any overlapping in a manner that typically minimizes the unused space, and may guarantee that every TxT (for example, 16x16) block of the 2D grid is associated with a unique patch. A given minimum block size TxT of the 2D grid may specify the minimum distance between distinct patches as placed on this 2D grid. The 2D grid resolution may depend on the input point cloud size and its width W and height H and the block size T may be transmitted as metadata to the decoder.

The auxiliary patch information PI may further include information relative to an association between a block of the 2D grid and a patch.

In V-PCC, the auxiliary information PI may include a block to patch index information ( BlockToPatch ) that determines an association between a block of the 2D grid and a patch index.

Fig. 3a illustrates an example of a canvas C comprising 2 patches P1 and P2 and their associated 2D bounding boxes B1 and B2. Note that two bounding boxes may overlap in the canvas C as illustrated on Fig. 3a. The 2D grid (the splitting of the canvas) is only represented inside the bounding box but the splitting of the canvas also occurs outside those bounding boxes. A bounding box associated with a patch can be split into TxT blocks, typically T=16.

TxT blocks containing 2D samples belonging to a patch may be considered as occupied blocks. Each occupied block of the canvas is represented by a particular pixel value (for example 1 ) in the occupancy map OM and each unoccupied block of the canvas is represented by another particular value, for example 0. Then, a pixel value of the occupancy map OM may indicate whether a TxT block of the canvas is occupied, that is contains 2D samples that belong to a patch.

In Fig. 3a, an occupied block is represented by a white block and light grey blocks represent unoccupied blocks. The image generation processes (steps 3300 and 3400) exploit the mapping of the at least one generated patch onto the 2D grid computed during step 3200, to store the geometry and texture of the input point cloud frame IPCF as images. In step 3300, a geometry image generator GIG may generate at least one geometry image Gl from the input point cloud frame IPCF, the occupancy map OM and the auxiliary patch information PI. The geometry image generator GIG may exploit the occupancy map information in order to detect (locate) the occupied blocks and thus the non-empty pixels in the geometry image Gl.

A geometry image Gl may represent the geometry of the input point cloud frame IPCF and may be a monochromatic image of WxH pixels represented, for example, in YUV420-8bit format.

In order to better handle the case of multiple 3D samples being projected (mapped) to a same 2D sample of the projection plane (along a same projection direction (line)), multiple images, referred to as layers, may be generated. Thus, different depth values D1 , ... , Dn may be associated with a 2D sample of a patch and multiple geometry images may then be generated.

In V-PCC, 2D samples of a patch are projected onto two layers. A first layer, also called the near layer, may store, for example, the depth values DO associated with the 2D samples with smaller depths. A second layer, referred to as the far layer, may store, for example, the depth values D1 associated with the 2D samples with larger depths. Alternatively, the second layer may store difference values between depth values D1 and DO. For example, the information stored by the second depth image may be within an interval [0, D] corresponding to depth values in the range [DO, DO+D], where D is a user- defined parameter that describes the surface thickness.

By this way, the second layer may contain significant contour-like high frequency features. Thus, it clearly appears that the second depth image may be difficult to code by using a legacy video coder and, therefore, the depth values may be poorly reconstructed from said decoded second depth image, which results on a poor quality of the geometry of the reconstructed point cloud frame.

According to an embodiment, the geometry image generating module GIG may code (derive) depth values associated with 2D samples of the first and second layers by using the auxiliary patch information PI. In V-PCC, the location of a 3D sample in a patch with a corresponding connected component may be expressed in terms of depth 5(u, v), tangential shift s(u, v) and bi-tangential shift r(u, v) as follows:

5(u, v) = 50 + g(u, v)

s(u, v) = so - uO + u

r(u, v) = rO - vO + v

where g(u, v) is the luma component of the geometry image, (u,v) is a pixel associated with the 3D sample on a projection plane, (50, sO, rO) is the 3D location of the corresponding patch of a connected component to which the 3D sample belongs and (uO, vO, u1 , v1 ) are the coordinates in said projection plane defining a 2D bounding box encompassing the projection of the patch associated with said connected component.

Thus, a geometry image generating module GIG may code (derive) depth values associated with 2D samples of a layer (first or second or both) as a luma component g(u,v) given by: g(u,v)=5(u, v) - 50. It is noted that this relationship may be employed to reconstruct 3D sample locations (50, sO, rO) from a reconstructed geometry image g(u, v) with the accompanying auxiliary patch information PI.

According to an embodiment, a projection mode may be used to indicate if a first geometry image GI0 may store the depth values of the 2D samples of either the first or second layer and a second geometry image GI1 may store the depth values associated with the 2D samples of either the second or first layer.

For example, when a projection mode equals 0, then the first geometry image GI0 may store the depth values of 2D samples of the first layer and the second geometry image GI1 may store the depth values associated with 2D samples of the second layer. Reciprocally, when a projection mode equals 1 , then the first geometry image GI0 may store the depth values of 2D samples of the second layer and the second geometry image GI1 may store the depth values associated with 2D samples of the first layer.

According to an embodiment, a frame projection mode may be used to indicate if a fixed projection mode is used for all the patches or if a variable projection mode is used in which each patch may use a different projection mode.

The projection mode and/or the frame projection mode may be transmitted as metadata.

A frame projection mode decision algorithm may be provided, for example, in section 2.2.1.3.1 of V-PCC.

According to an embodiment, when the frame projection indicates that a variable projection mode may be used, a patch projection mode may be used to indicate the appropriate mode to use to (de-)project a patch.

A patch projection mode may be transmitted as metadata and may be, possibly, an information included in the auxiliary patch information PI.

A patch projection mode decision algorithm is provided, for example in section 2.2.1.3.2 of V-PCC.

According to an embodiment of step 3300, the pixel value in a first geometry image, for example GI0, corresponding to a 2D sample (u,v) of a patch, may represent the depth value of least one in-between 3D sample defined along a projection line corresponding to said 2D sample (u,v). More precisely, said in-between 3D samples reside along a projection line and share the same coordinates of the 2D sample (u,v) whose depth value D1 is coded in a second geometry image, for example GI1. Further, the said in-between 3D samples may have depth values between the depth value DO and a depth value D1. A designated bit may be associated with each said in-between 3D samples which is set to 1 if the in-between 3D sample exists and 0 otherwise.

Fig. 3b illustrates an example of two in-between 3D samples PM and P located between two 3D samples P0 and P1 along a projection line PL. The 3D samples P0 and P1 have respectively depth values equal to DO and D1. The depth values DM and Di2 0f respectively the two in-between 3D samples PM and Pi2 are greater than DO and lower than D1.

Then, all said designated bits along said projection line may be concatenated to form a codeword, denoted Enhanced-Occupancy map (EOM) codeword hereafter. As illustrated in Fig. 3b, assuming an EOM codeword of 8 bits of length, 2 bits equal 1 to indicate the location of the two 3D samples Pn and Pi2. Finally, all the EOM codewords may be packed in an image, for example, the occupancy map OM. In that case, at least one patch of the canvas may contain at least one EOM codeword. Such a patch is denoted reference patch and a block of a reference patch is denoted a EOM reference block. Thus, a pixel value of the occupancy map OM may equal to a first value, for example 0, to indicate an unoccupied block of the canvas, or another value, for example greater than 0, to indicate either a occupied block of the canvas, for example when D1 -D0 <=1 , or to indicate a EOM reference block of the canvas when, for example D1-D0>1.

The locations of pixels in the occupancy map OM that indicates EOM reference blocks and the values of the bits of a EOM codeword that are obtained from the values of those pixels, indicate the 3D coordinates of the in- between 3D samples.

In step 3400, a texture image generator TIG may generate at least one texture image Tl from the input point cloud frame IPCF, the occupancy map OM, the auxiliary patch information PI and a geometry of a reconstructed point cloud frame derived from at least one decoded geometry image DGI, output of a video decoder VDEC (step 4200 in Fig. 4).

A texture image Tl may represent the texture of the input point cloud frame IPCF and may be an image of WxH pixels represented, for example, in YUV420-8bit format.

The texture image generator TG may exploit the occupancy map information in order to detect (locate) the occupied blocks and thus the non empty pixels in the texture image.

The texture image generator TIG may be adapted to generate and associate a texture image Tl with each geometry image/layer DGI.

According to an embodiment, the texture image generator TIG may code (store) the texture (attribute) values TO associated with 2D samples of the first layer as pixel values of a first texture image TI0 and the texture values T1 associated with the 2D samples of the second layer as pixel values of a second texture image TI1. Alternatively, the texture image generating module TIG may code (store) the texture values T 1 associated with 2D samples of the second layer as pixel values of the first texture image TIO and the texture values DO associated with the 2D samples of the first layer as pixel values of the second geometry image GI1 .

For example, colors of 3D samples may be obtained as described in section 2.2.3, 2.2.4, 2.2.5, 2.2.8 or 2.5 of V-PCC.

The texture values of two 3D samples are stored in either the first or second texture images. But, the texture values of in-between 3D samples cannot be stored neither in this first texture image TIO nor the second texture image TI1 because the locations of the projected in-between 3D samples correspond to occupied blocs that are already used for storing a texture value of another 3D sample (P0 or P1 ) as illustrated in Fig. 3b. The texture values of in-between 3D samples are thus stored in EOM texture blocks located elsewhere in either the first or second texture image in locations procedurally defined (section 9.4.5 of V-PCC). In brief, this process determines locations of unoccupied blocks in a texture image and stored the texture values associated with in-between 3D samples as pixel values of said unoccupied blocks of the texture image, denoted EOM texture blocks.

According to an embodiment, a padding process may be applied on the geometry and/or texture image. The padding process may be used to fill empty space between patches to generate a piecewise smooth image suited for video compression.

An image padding example is provided in sections 2.2.6 and 2.2.7 of V-

PCC.

In step 3500, a video encoder VENC may encode the generated images /layers Tl and Gl.

In step 3600, an encoder OMENC may encode the occupancy map as an image as detailed, for example, in section 2.2.2 of V-PCC. Lossy or lossless encoding may be used.

According to an embodiment, the video encoder ENC and/or OMENC may be a HEVC-based encoder. In step 3700, an encoder PIENC may encode the auxiliary patch information PI and possibly additional metadata such as the block size T, the width W and height H of the geometry /texture images.

According to an embodiment, the auxiliary patch information may be differentially encoded (as defined, for example in section 2.4.1 of V-PCC).

In step 3800, a multiplexer may be applied to the generated outputs of steps 3500, 3600 and 3700, and as a result these outputs may be multiplexed together so as to generate a bitstream representative of the base layer BL. It should be noted that the metadata information represents a small fraction of the overall bitstream. The bulk of the information is compressed using the video codecs.

Fig. 4 illustrates a schematic block diagram of an example of an image- based point cloud decoder 4000 in accordance with at least one of the present embodiments.

In step 4100, a de-multiplexer DMUX may applied to demutiplex the encoded information of the bitstream representative of the base layer BL.

In step 4200, a video decoder VDEC may decode encoded information to derive at least one decoded geometry image DGI and at least one decoded texture image DTI.

In step 4300, a decoder OMDEC may decode encoded information to derive a decoded occupancy map DOM.

According to an embodiment, the video decoder VDEC and/or OMDEC may be a HEVC-based decoder.

In step 4400, a decoder PIDEC may decode encoded information to derive auxiliary patch information DPI.

Possibly, metadata may also be derived from the bitstream BL.

In step 4500, a geometry generating module GGM may derive the geometry RG of a reconstructed point cloud frame IRPCF from the at least one decoded geometry image DGI, the decoded occupancy map DOM, the decoded auxiliary patch information DPI and possible additional metadata. The geometry generating module GGM may exploit the decoded occupancy map information DOM in order to locate the non-empty pixels in the at least one decoded geometry image DGI.

Said non-empty pixels belong to either occupied blocks or EOM reference blocks depending on pixels values of the decoded occupancy information DOM and value of D1-D0 as explained above.

According to an embodiment of step 4500, the geometry generating module GGM may derive two of the 3D coordinates of in-between 3D samples from coordinates of non-empty pixels.

According to an embodiment of step 4500, when said non-empty pixels belong to said EOM reference block, the geometry generating module GGM may derive the third of the 3D coordinates of in-between 3D samples from the bit values of the EOM codewords.

For example, according to the example of Fig. 3b, the EOM codeword EOMC is used for determining the 3D coordinates of in-between 3D samples Pn and Pi2. The third coordinate of the in-between 3D sample Pn may be derived, for example, from DO by Dn=D0+3 and the third coordinate of the reconstructed 3D sample P,2 may be derived, for example, from DO by Di2=D0+5. The offset value (3 or 5) is the number of intervals between DO and D1 along the projection line.

According to an embodiment, when said non-empty pixels belong to an occupied block, the geometry generating module GGM may derive the 3D coordinates of reconstructed 3D samples from coordinates of non-empty pixels, values of said non-empty pixels of one of the at least one decoded geometry image DGI, the decoded auxiliary patch information, and possibly, from additional metadata.

The use of non-empty pixels is based on 2D pixel relationship with 3D samples. For example, with the said projection in V-PCC, the 3D coordinates of reconstructed 3D samples may be expressed in terms of depth 5(u, v), tangential shift s(u, v) and bi-tangential shift r(u, v) as follows:

5(u, v) = 50 + g(u, v)

s(u, v) = so - uO + u r(u, v) = r0 - vO + v

where g(u, v) is the luma component of a decoded geometry image DGI, (u,v) is a pixel associated with a reconstructed 3D sample, (50, sO, rO) is the 3D location of a connected component to which the reconstructed 3D sample belongs and (uO, vO, u1 , v1 ) are the coordinates in a projection plane defining a 2D bounding box encompassing the projection of a patch associate with said connected component.

In step 4600, a texture generating module TGM may derive the texture of the reconstructed point cloud frame IRPCF from the geometry RG and the at least one decoded texture image DTI.

According to an embodiment of step 4600, the texture generating module TGM may derive the texture of non-empty pixels that belong to a EOM reference block from a corresponding EOM texture block. The locations of a EOM texture blocks in a texture image are procedurally defined (section 9.4.5 of V-PCC)

According to an embodiment of step 4600, the texture generating module TGM may derive the texture of non-empty pixels that belong to an occupied block directly as pixel values of either the first or second texture image.

Fig. 5 illustrates schematically an example syntax of a bitstream representative of a base layer BL in accordance with at least one of the present embodiments.

The bitstream comprises a Bitstream Header SH and at least one Group Of Frame Stream GOFS.

A group of frame stream GOFS comprises a header HS, at least one syntax element OMS representative of an occupancy map OM, at least one syntax element GVS representative of at least one geometry image (or video), at least one syntax element TVS representative of at least one texture image (or video) and at least one syntax element PIS representative of auxiliary patch information and other additional metadata.

In a variant, a group of frame stream GOFS comprises at least one frame stream. Fig. 6 shows a schematic block diagram illustrating an example of a system in which various aspects and embodiments are implemented.

System 6000 may be embodied as one or more devices including the various components described below and is configured to perform one or more of the aspects described in this document. Examples of equipment that may form all or part of the system 6000 include personal computers, laptops, smartphones, tablet computers, digital multimedia set top boxes, digital television receivers, personal video recording systems, connected home appliances, connected vehicles and their associated processing systems, head mounted display devices (HMD, see-through glasses), projectors (beamers), “caves” (system including multiple displays), servers, video encoders, video decoders, post-processors processing output from a video decoder, pre-processors providing input to a video encoder, web servers, set top boxes, and any other device for processing a point cloud, a video or an image or other communication devices. Elements of system 6000, singly or in combination, may be embodied in a single integrated circuit, multiple ICs, and/or discrete components. For example, in at least one embodiment, the processing and encoder/decoder elements of system 6000 may be distributed across multiple ICs and/or discrete components. In various embodiments, the system 6000 may be communicatively coupled to other similar systems, or to other electronic devices, via, for example, a communications bus or through dedicated input and/or output ports. In various embodiments, the system 6000 may be configured to implement one or more of the aspects described in this document.

The system 6000 may include at least one processor 6010 configured to execute instructions loaded therein for implementing, for example, the various aspects described in this document. Processor 6010 may include embedded memory, input output interface, and various other circuitries as known in the art. The system 6000 may include at least one memory 6020 (for example a volatile memory device and/or a non-volatile memory device). System 6000 may include a storage device 6040, which may include non volatile memory and/or volatile memory, including, but not limited to, Electrically Erasable Programmable Read-Only Memory (EEPROM), Read- Only Memory (ROM), Programmable Read-Only Memory (PROM), Random Access Memory (RAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), flash, magnetic disk drive, and/or optical disk drive. The storage device 6040 may include an internal storage device, an attached storage device, and/or a network accessible storage device, as non-limiting examples.

The system 6000 may include an encoder/decoder module 6030 configured, for example, to process data to provide encoded data or decoded data, and the encoder/decoder module 6030 may include its own processor and memory. The encoder/decoder module 6030 may represent module(s) that may be included in a device to perform the encoding and/or decoding functions. As is known, a device may include one or both of the encoding and decoding modules. Additionally, encoder/decoder module 6030 may be implemented as a separate element of system 6000 or may be incorporated within processor 6010 as a combination of hardware and software as known to those skilled in the art.

Program code to be loaded onto processor 6010 or encoder/decoder 6030 to perform the various aspects described in this document may be stored in storage device 6040 and subsequently loaded onto memory 6020 for execution by processor 6010. In accordance with various embodiments, one or more of processor 6010, memory 6020, storage device 6040, and encoder/decoder module 6030 may store one or more of various items during the performance of the processes described in this document. Such stored items may include, but are not limited to, a point cloud frame, encoded/decoded geometry/texture videos/images or portions of the encoded/decoded geometry /texture video/images, a bitstream, matrices, variables, and intermediate or final results from the processing of equations, formulas, operations, and operational logic.

In several embodiments, memory inside of the processor 6010 and/or the encoder/decoder module 6030 may be used to store instructions and to provide working memory for processing that may be performed during encoding or decoding.

In other embodiments, however, a memory external to the processing device (for example, the processing device may be either the processor 6010 or the encoder/decoder module 6030) may be used for one or more of these functions. The external memory may be the memory 6020 and/or the storage device 6040, for example, a dynamic volatile memory and/or a non-volatile flash memory. In several embodiments, an external non-volatile flash memory may be used to store the operating system of a television. In at least one embodiment, a fast external dynamic volatile memory such as a RAM may be used as working memory for video coding and decoding operations, such as for MPEG-2 part 2 (also known as ITU-T Recommendation H.262 and ISO/IEC 13818-2, also known as MPEG-2 Video), HEVC (High Efficiency Video coding), or VVC (Versatile Video Coding).

The input to the elements of system 6000 may be provided through various input devices as indicated in block 6130. Such input devices include, but are not limited to, (i) an RF portion that may receive an RF signal transmitted, for example, over the air by a broadcaster, (ii) a Composite input terminal, (iii) a USB input terminal, and/or (iv) an HDMI input terminal.

In various embodiments, the input devices of block 6130 may have associated respective input processing elements as known in the art. For example, the RF portion may be associated with elements necessary for (i) selecting a desired frequency (also referred to as selecting a signal, or band- limiting a signal to a band of frequencies), (ii) down-converting the selected signal, (iii) band-limiting again to a narrower band of frequencies to select (for example) a signal frequency band which may be referred to as a channel in certain embodiments, (iv) demodulating the down-converted and band-limited signal, (v) performing error correction, and (vi) demultiplexing to select the desired stream of data packets. The RF portion of various embodiments may include one or more elements to perform these functions, for example, frequency selectors, signal selectors, band-limiters, channel selectors, filters, downconverters, demodulators, error correctors, and de-multiplexers. The RF portion may include a tuner that performs various of these functions, including, for example, down-converting the received signal to a lower frequency (for example, an intermediate frequency or a near-baseband frequency) or to baseband.

In one set-top box embodiment, the RF portion and its associated input processing element may receive an RF signal transmitted over a wired (for example, cable) medium. Then, the RF portion may perform frequency selection by filtering, down-converting, and filtering again to a desired frequency band.

Various embodiments rearrange the order of the above-described (and other) elements, remove some of these elements, and/or add other elements performing similar or different functions.

Adding elements may include inserting elements in between existing elements, such as, for example, inserting amplifiers and an analog-to-digital converter. In various embodiments, the RF portion may include an antenna.

Additionally, the USB and/or HDMI terminals may include respective interface processors for connecting system 6000 to other electronic devices across USB and/or HDMI connections. It is to be understood that various aspects of input processing, for example, Reed-Solomon error correction, may be implemented, for example, within a separate input processing 1C or within processor 6010 as necessary. Similarly, aspects of USB or HDMI interface processing may be implemented within separate interface ICs or within processor 6010 as necessary. The demodulated, error corrected, and demultiplexed stream may be provided to various processing elements, including, for example, processor 6010, and encoder/decoder 6030 operating in combination with the memory and storage elements to process the data stream as necessary for presentation on an output device.

Various elements of system 6000 may be provided within an integrated housing. Within the integrated housing, the various elements may be interconnected and transmit data therebetween using suitable connection arrangement 6140, for example, an internal bus as known in the art, including the I2C bus, wiring, and printed circuit boards.

The system 6000 may include communication interface 6050 that enables communication with other devices via communication channel 6060. The communication interface 6050 may include, but is not limited to, a transceiver configured to transmit and to receive data over communication channel 6060. The communication interface 6050 may include, but is not limited to, a modem or network card and the communication channel 6060 may be implemented, for example, within a wired and/or a wireless medium.

Data may be streamed to the system 6000, in various embodiments, using a Wi-Fi network such as IEEE 802.1 1. The Wi-Fi signal of these embodiments may be received over the communications channel 6060 and the communications interface 6050 which are adapted for Wi-Fi communications. The communications channel 6060 of these embodiments may be typically connected to an access point or router that provides access to outside networks including the Internet for allowing streaming applications and other over-the-top communications.

Other embodiments may provide streamed data to the system 6000 using a set-top box that delivers the data over the HDMI connection of the input block 6130.

Still other embodiments may provide streamed data to the system 6000 using the RF connection of the input block 6130.

It is to be appreciated that signaling may be accomplished in a variety of ways. For example, one or more syntax elements, flags, and so forth may be used to signal information to a corresponding decoder in various embodiments.

The system 6000 may provide an output signal to various output devices, including a display 6100, speakers 61 10, and other peripheral devices 6120. The other peripheral devices 6120 may include, in various examples of embodiments, one or more of a stand-alone DVR, a disk player, a stereo system, a lighting system, and other devices that provide a function based on the output of the system 3000.

In various embodiments, control signals may be communicated between the system 6000 and the display 6100, speakers 61 10, or other peripheral devices 6120 using signaling such as AV.Link (Audio/Video Link), CEC (Consumer Electronics Control), or other communications protocols that enable device-to-device control with or without user intervention.

The output devices may be communicatively coupled to system 6000 via dedicated connections through respective interfaces 6070, 6080, and 6090.

Alternatively, the output devices may be connected to system 6000 using the communications channel 6060 via the communications interface 6050. The display 6100 and speakers 61 10 may be integrated in a single unit with the other components of system 6000 in an electronic device such as, for example, a television.

In various embodiments, the display interface 6070 may include a display driver, such as, for example, a timing controller (T Con) chip.

The display 6100 and speaker 61 10 may alternatively be separate from one or more of the other components, for example, if the RF portion of input 6130 is part of a separate set-top box. In various embodiments in which the display 6100 and speakers 61 10 may be external components, the output signal may be provided via dedicated output connections, including, for example, HDMI ports, USB ports, or COMP outputs.

The 3DoF+ metadata (also denoted MIV metadata) and syntax used in the following is based on the WD Metadata for Immersive Media (Video) (MIV) and the Test Model for Immersive Video (TMIV), noted as [miv] and [tmiv] in this document, respectively, and corresponding to MPEG output documents w18464 and w18470, respectively, from the Geneva meeting (MPEG #126). [miv] specifies the normative decoding process for metadata for immersive (volumetric, 3DoF+) video while [tmiv] demonstrates a reference implementation of non-normative encoding and rendering techniques and the normative decoding process. The delivery of MIV metadata is based on existing MPEG tools, both at elementary HEVC stream level (MIV metadata are embedded into SEIs) and at system level (ISOBMFF container to be specified by OMAF to synchronize the different components).

The present embodiments relate to an extension of V-PCC to carry MIV metadata in order to design a versatile immersive video decoder being able to decode point clouds corresponding to either point cloud data inputs or 3DoF+ volumetric data inputs (volumetric video) carried by a bitstream conforms to the V-PCC syntax.

By carrying the MIV metadata as metadata conformed to V-PCC (V- PCC metadata) and the corresponding video in a single elementary stream, there’s no need to resort to system-level tools to synchronize the different components, resulting in a natural simplification of the delivery and storage mechanism.

Although the representation format of uncompressed 3DoF+ video is multi-view plus depth, an alternative point cloud representation can be easily obtained from it. It then appears obvious that the technical approaches chosen by MPEG to compress point clouds and 3DoF+ videos share common principles, mainly the projection of 3D data onto 2D planes, the clustering of projected color and depth pixels into a multiplicity of 2D patches, and their packing into patch atlases. The V-PCC syntax, defined for encoding point clouds, could therefore be easily adapted (extended) to also transport compressed 3DoF+ volumetric video.

Fig. 7 illustrates a schematic block diagram of an example of a TMIV encoding and decoding structure in accordance with prior art;

In essence, the TMIV encoder consists in a view optimizer, an atlas constructor, a video encoder and a metadata composer. Similarly, the decoder consists in a video decoder, a metadata parser, an atlas patch occupancy map generator, and a Tenderer.

A detailed scheme of the Atlas Constructor is depicted in Fig. 8. The atlas constructor takes as input basic and additional views along with the associated basic and additional camera parameters list and outputs atlases, with the camera parameters list and with the atlas parameters list. In a 3DOF+ stream, a patch atlas contains an aggregation of one or more patches from one or more view representations of a single component type, texture or depth. A patch atlas is an aggregation of patches from one or more view representations after a packing process. Each basic view is carried in the patch atlas as a single, fully occupied patch (assuming the patch atlas size is equal or larger than the basic view size otherwise the basic view may be split into multiple patch atlases). The additional views are pruned into multiple patches which may be carried along with a basic view’s patch in the same patch atlas if the patch atlas is of larger size or in separate patch atlas(es).

The 3DoF+ TMIV bitstream therefore consists of a set HEVC bitstreams encoding one or more pairs of (texture, depth) patch atlases accompanied by MIV metadata describing the (real or virtual) cameras used for 3D-to-2D projections:“Camera Parameters List”, and the packing of 2D patches within the patch atlases:“Atlas Parameters List”.

The MIV metadata frame rate is not specified but is typically slower than the video frame rate. In the first version of the TMIV test model, camera parameters are fixed per sequence and patch atlas parameters are defined per fixed groups of successive video frames, corresponding to an HEVC intra period of 32 frames.

Fig. 9-11 illustrate examples of syntax elements relative to cameras. FIG. 9 illustrates an example of a syntax element“camera parameters list” conveying MIV metadata describing real or virtual cameras used for 3D-to-2D projections (on the encoder side) and 2D-to-3D projections (on the decoder side). Fig. 10 illustrates an example of a syntax element“camera intrinsics” conveying MIV metadata describing intrinsic camera parameters. Fig. 11 illustrates an example of a syntax element“depth quantization” conveying MIV metadata describing depth quantization parameters.

Fig. 12-13 illustrate examples of syntax elements relative to patch atlas.

Fig. 12 illustrates an example of a syntax element“atlas params list” conveying MIV metadata describing the number and parameters of the patch atlas(es) used to represent a 3DoF+ content. Fig. 13 illustrates an example of a syntax element“atlas params” conveying MIV metadata describing the parameters of a patch atlas.

Fig. 14 illustrates a simplified architecture of a V-PCC codec in accordance with prior art.

The PCC processing block takes a point cloud as input and maps (projects) it to a 2D plane, generating depth information (coded as a“geometry video”), color information (coded as an“attribute video”), and an occupancy map video. Additionally, metadata allowing to re-map from the 2D plane back to 3D space is also generated by the PCC processing block. Once each video component and the metadata have been encoded, the resulting streams are muxed together, forming the V-PCC elementary stream. The muxing process and the high-level syntax (HLS) of the V-PCC stream is also specified in the V-PCC standard.

Fig. 15 represents the simplified architecture of a volumetric video codec in accordance with prior art.

Similar to the PCC codec, the MIV processing block takes multi-view plus depth (also denoted MVD) as input and maps (projects) it to a 2D plane, generating geometry and texture videos and the corresponding MIV metadata. Note that there is no need for an explicit occupancy map video because in the MIV codec, the occupancy map information can be derived by the decoder from the MIV metadata. The encoding process ends after the encoding of the MIV metadata and corresponding videos. A unified MIV elementary stream is not defined by the MIV specifications. System-level tools should be used to deliver the individual MIV streams.

Fig. 16 illustrates a simplified architecture of a V-PCC codec in accordance with at least one embodiment.

Inputs of V-PCC codec are MIV metadata, MIV geometry and attribute (texture) videos obtained by MIV processing a source video (volumetric video in MVD format).

The V-PCC codec may comprise a MIV to V-PCC metadata syntax converter to embed the MIV metadata into at least one V-PCC syntax element.

In a variant, the V-PCC codec further comprises an occupancy map video generator to create an occupancy map video from the MIV metadata. Possibly, the occupancy map video is also transmitted.

In another variant, the V-PCC codec does not comprise the occupancy map video generator. Although it may be possible to generate the occupancy map video from the MIV metadata, there’s no need to send it - hence, it’s shown using a doted line in Fig. 16. V-PCC supports not sending the occupancy map video.

The encoding of the MIV geometry and attribute videos, the V-PCC syntax element conveying the MIV metadata and the muxing process conform to the V-PCC standard.

The syntax of the V-PCC bitstream is then generated. The part of the syntax relative to the V-PCC metadata obtained from the MIV metadata conforms to an extension of the V-PCC syntax as detailed below.

Fig. 17 illustrates a simplified architecture of a V-PCC decoder in accordance with at least one embodiment.

The V-PCC decoder may comprise a V-PCC to MIV metadata syntax converter to extract MIV metadata from at least one V-PCC syntax element.

In a variant, the V-PCC decoder further comprises an occupancy map to MIV metadata generator to extract MIV metadata from an occupancy map video, possibly received from the bitstream.

In another variant, the V-PCC decoder does not comprise the occupancy map to MIV metadata generator.

Outputs of V-PCC decoder may be MIV metadata, MIV geometry and attribute (texture) videos. The MIV processing and Tenderer are identical to that used by the existing MIV test model [tmiv].

Fig. 18 illustrates a flowchart of a method 1800 for signalling MIV metadata in a V-PCC bitstream in accordance with at least one embodiment.

In step 1810, MIV metadata is embedded into at least one V-PCC syntax element.

In a variant of step 1810, an occupancy map video is created from the MIV metadata and, possibly transmitted.

In step 1820, at least one V-PCC syntax element embedding MIV metadata is added in a bitstream carrying data representative of a point cloud video.

In step 1830, the bitstream is transmitted. In step 1840, at least one V-PCC syntax element is obtained from the bitstream.

In step 1850, MIV metadata is obtained (extracted) from said at least one V-PCC syntax element.

The syntax of said at least one V-PCC syntax element of the bitstream carrying MIV metadata may be based on an extended V-PCC syntax as explained below.

In one embodiment, the MIV metadata are relative to real or virtual cameras used for 3D-to-2D and 2D-to-3D projections. The MIV metadata are those which are usually embedded in the syntax element “camera_params_list” in Fig. 9. At least one V-PCC syntax element may be added in the bitstream to signal said MIV metadata. The V-PCC standard may be modified to include such new syntax element.

According to this embodiment, for example, a syntax element “camerajnformation” may be added in the bitstream (Fig. 19) and signaled in the syntax element“sequence_parameter_set” as illustrated in Fig. 19a. In this example, the syntax element“camerajnformation” is signaled only if the flag “sps_miv_patch_enabled_flag” is set to 1. The V-PCC standard may be modified to include such new flag.

In a variant, the syntax element“camerajnformation” may conform to the syntax as defined in sections 7.3 and 7.4 of the WD of the MIV specification.

According to this variant, the syntax element“camerajnformation” comprises a syntax element“ci_camera_params_list” as illustrated in Fig. 19. The syntax element “ci_camera_params_list” (Fig. 19b) comprises the elements of the syntax element“camera_params_list” in Fig. 9 including, for example the syntax element“camerajntrinsics” (Fig. 10) and the syntax element“camera_depth_quantization” (Fig. 11).

In one embodiment, the MIV metadata are relative to the patch atlas(es) used for encoding volumetric data. The MIV metadata are those which are usually embedded in the syntax elements“atlas_params_list” in Fig. 12 and the syntax element“atlas_params” in Fig. 13. At least one V-PCC syntax element may be added in the bitstream to signal said MIV metadata.

According to this embodiment, a syntax element “patch_tile_group_data_unit” may be added in the bitstream (Fig. 20) to signal said a patch atlas.

In a variant, the syntax element “patch_tile_group_data_unit” may conform to the V-PCC syntax.

According to this variant, the syntax element “patch_tile_group_data_unit” may comprise a syntax element “ptgdu_patch_mode” conform to the V-PCC syntax as illustrated in Fig. 20.

The syntax element“ptgdu_patch_mode” indicates a patch mode for a patch in a patch tile group (patch atlas). The possible values for syntax element “ptgdu_patch_mode” may be specified in Fig. 20a for patch tile groups with ptgh_type = I and in Fig. 20b for patch tile groups with ptgh_type = P.

Fig. 20a-b illustrate an extension of tables as defined in section 7.4.6.1 of w18479 in which the following modes have been added:

• l_MIV: this mode corresponds to MIV patch metadata for intra frames.

• P_MIV: this mode corresponds to MIV patch metadata for inter

(predicted) frames.

The V-PCC standard may be modified to include those two patch coding modes.

The existing P_SKIP mode indicates that patch metadata shall be copied from previous frame. It’s especially useful for MIV metadata since such MIV metadata may remain constant for several frames (typically an HEVC intra period).

According to this variant, the syntax element “patch_tile_group_data_unit” may also comprise a syntax element “patch_information_data” as illustrated in Fig. 20c.

The syntax element“patch_information_data” indicates multiple patch coding modes. For example, the syntax element“patch_information_data” as defined in V-PCC may be modified to support the l_M IV and P_MIV modes as illustrated in Fig. 20c.

If the“patch_mode” equals P_SKIP, then the skip mode is considered.

If the “patch_mode” equals l_MIV, then a syntax element “miv_patch_data_unit” is signaled in the bitstream. The V-PCC standard may be modified to include such new syntax element.

The syntax element “miv_patch_data_unit” (Fig. 20d) comprises elements obtained from the MIV metadata of the syntax element in Fig. 13 to describe a patch of an atlas.

For example, the elements of the syntax element “miv_patch_data_unit(p)” of Fig. 20d are defined as:

-“mpdu_view_id_x [ p ]” indicates the view representation pair index associated with patch with index p of the current patch tile group;

-“mpdu_2d_size_x [ p ]” and“mpdu_2d_size_y [ p ]” specify the width and height in luma samples, respectively, of patch with index p of the current patch tile group;

- “mpdu_2d_shift_x [ p ]” and “mpdu_2d_shift_y [ p ]” specify the horizontal and vertical coordinates in luma samples, respectively, of the top- left corner of patch with index p of the current patch tile group;

These two parameters correspond to patch_pos_in_atlas_x and patch_pos_in_atlas_y from the MIV WD specifications.

-“mpdu_patch_shift_in_view_x [ p ]” and“mpdu_patch_shift_in_view_y [ p ]” specify the horizontal and vertical coordinates in luma samples, respectively, of the top-left corner of the patch with index p of the current patch tile group in the mpdu_view_id [ p ]-th view;

-“mpdu_orientation_index [ p ]” indicates the rotation of the p-th patch relative to the orientation of the patch in the mpdu_view_id [ p ]-th view. “patch_rotation [ p ]” equal to 0 specifies no rotation. “patch_rotation [ p ]” equal to 1 specifies a clockwise 90 degrees rotation from the atlas to the view. Values greater than 1 are reserved for future use. This parameter corresponds to the“patch_orientation” parameter from the MIV WD specifications.

The number of bits for encoding the parameters of the syntax element “miv_patch_data_unit” are specified in the syntax element “patch_tile_group_header( )” (Fig. 20e).

If the“patch_mode” equals P_MIV (Fig. 20c), then a syntax element “miv_delta_patch_data_unit” is signaled in the bitstream. The syntax element “miv_delta_patch_data_unit” indicates a parsing of differences (delta values) between the parameters of a patch and the parameters of the corresponding patch (patch with the same patch index of a previous frame) as illustrated in Fig. 20f. The V-PCC standard may be modified to include such new syntax element.

The same parameters as for the l_MIV mode are transmitted, only the index of the reference (mdpdu_patch_index) patch has been added for the P_MIV mode. The naming change to denote these are delta values (prefix is mdpdu instead of mpdu). Absolute values are computed from delta values and values of the reference patch as follows (as done for other existing patch modes in the V-PCC specifications already using delta coding): mpdu _view_id x [ patchlndex ] = mdpdu_view_id x [ patchlndex ]

+ mpdu_view_id x [ mdpdu_patch_index[ patchlndex ]]

The patch atlas layout is refreshed every n video frames, n typically corresponding to an HEVC intra-period (for example 32 frames). The patch atlas parameters metadata are thus transmitted at a lower frame rate than the video frame frequency. In V-PCC, the patches are typically transmitted in a syntax element“general patch tile group data” for each frame, that is at the video frame frequency. Thus, transmitting MIV metadata in a bitstream having a syntax that conforms to a V-PCC raises an issue to signal the frequency at which the MIV metadata, that is for fixing the transmission rate of MIV metadata, shall be signaled. In a first embodiment, all the patches of one patch atlas may be signalled in all intra- or predictive-coded frames inside a syntax element “General patch tile group data” per frame. A syntax element“General patch tile group data” may contain only intra-coded patches (mode l_MIV).

This first embodiment leads to an increase of bit-rate due to the transmission of a lot of redundant data.

The P_MIV mode and the syntax element“miv_delta_patch_data_unit” are not required for this embodiment.

In a second embodiment, all patches of a patch atlas may be transmitted in a first intra-coded frame inside a syntax element“General patch tile group data” that contains only intra-coded patches, and all patches of a patch atlas are transmitted in the following predictive-coded frames inside a syntax element“General patch tile group data” that contains only patches with SKIP mode.

This second embodiment assumes that patch metadata only changes once per intra-period, which allows greatly reducing the bit rate required for the MIV metadata.

As for the first embodiment, the P_MIV mode and the miv_delta_patch_data_unit syntax structure are not required.

In a third embodiment, all the patches of a patch atlas may be transmitted in the first intra-coded frame inside a syntax element“General patch tile group data”. A syntax element“General patch tile group data” may contain only intra-coded patches (mode l_MIV). For the following predictive- coded pictures, a SKIP coding type of the current syntax element“patch tile group” (ptgh_type) is created. When this mode is used, all the patches of the current frame are“skipped”, meaning they reuse the values from the previous frame.

The advantage compared to the first embodiment is that a single SKIP flag is required (instead of one per patch), reducing the bitrate. On the other hand, this third embodiment may only be used when none of the patches change. In the third embodiment, the V-PCC syntax is modified by adding a new syntax element“ptgh_type” that specifies the coding type of a patch tile goup according to Fig. 21. The syntax element“patch_tile_group_layer_unit” is also modified to take into account the new SKIP mode. A simple way of doing it is by skipping the parsing of the patch tile group data when the SKIP mode is active.

In a fourth embodiment, a specific frame rate for the metadata may be used to fix the transmission rate of MIV metadata.

For example, the metadata that contains the MIV patches data may be transmitted at 1 fps while the depth and texture video may be transmitted at 30 fps.

In a variant, the metadata may be persistent during the 1 second period without need to send any explicit signalling, therefore reducing the bitrate. However, this variant adds some complexity on the decoder side since the decoder should take care of properly synchronizing the metadata with the video.

There are no changes required in the syntax to support this feature.

In a fifth embodiment, the Delta Patch data unit mechanism defined in V-PCC may be used. In this case, only the differences between the parameters of the current MIV patch and the parameters of the corresponding patch (patch with the same patchlndex of the previous frame) are transmitted. In this fifth embodiment, all difference values (delta) of the all the MIV patches of a frame coder in Inter mode will be equal to zero.

In the case of MIV metadata that do not change at all every frame, the SKIP modes described in the first and second embodiments would be more efficient. However, this embodiment is more efficient when the MIV metadata slightly changes.

Embodiments 1 to 4 may be combined together. It’s the more flexible approach as it allows changing the MIV metadata at any transmission rate and provides the most efficient way of coding (intra, delta, skip) for each situation.

In Fig. 1-21 a, various methods are described herein, and each of the methods includes one or more steps or actions for achieving the described method. Unless a specific order of steps or actions is required for proper operation of the method, the order and/or use of specific steps and/or actions may be modified or combined.

Some examples are described with regard to block diagrams and operational flowcharts. Each block represents a circuit element, module, or portion of code which includes one or more executable instructions for implementing the specified logical function(s). It should also be noted that in other implementations, the function(s) noted in the blocks may occur out of the indicated order. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending on the functionality involved.

The implementations and aspects described herein may be implemented in, for example, a method or a process, an apparatus, a computer program, a data stream, a bitstream, or a signal. Even if only discussed in the context of a single form of implementation (for example, discussed only as a method), the implementation of features discussed may also be implemented in other forms (for example, an apparatus or computer program).

The methods may be implemented in, for example, a processor, which refers to processing devices in general, including, for example, a computer, a microprocessor, an integrated circuit, or a programmable logic device. Processors also include communication devices.

Additionally, the methods may be implemented by instructions being performed by a processor, and such instructions (and/or data values produced by an implementation) may be stored on a computer readable storage medium. A computer readable storage medium may take the form of a computer readable program product embodied in one or more computer readable medium(s) and having computer readable program code embodied thereon that is executable by a computer. A computer readable storage medium as used herein may be considered a non-transitory storage medium given the inherent capability to store the information therein as well as the inherent capability to provide retrieval of the information therefrom. A computer readable storage medium may be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. It is to be appreciated that the following, while providing more specific examples of computer readable storage mediums to which the present embodiments may be applied, is merely an illustrative and not an exhaustive listing as is readily appreciated by one of ordinary skill in the art: a portable computer diskette; a hard disk; a read-only memory (ROM); an erasable programmable read-only memory (EPROM or Flash memory); a portable compact disc read only memory (CD-ROM); an optical storage device; a magnetic storage device; or any suitable combination of the foregoing.

The instructions may form an application program tangibly embodied on a processor-readable medium.

Instructions may be, for example, in hardware, firmware, software, or a combination. Instructions may be found in, for example, an operating system, a separate application, or a combination of the two. A processor may be characterized, therefore, as, for example, both a device configured to carry out a process and a device that includes a processor-readable medium (such as a storage device) having instructions for carrying out a process. Further, a processor-readable medium may store, in addition to or in lieu of instructions, data values produced by an implementation.

An apparatus may be implemented in, for example, appropriate hardware, software, and firmware. Examples of such apparatus include personal computers, laptops, smartphones, tablet computers, digital multimedia set top boxes, digital television receivers, personal video recording systems, connected home appliances, head mounted display devices (HMD, see-through glasses), projectors (beamers),“caves” (system including multiple displays), servers, video encoders, video decoders, post-processors processing output from a video decoder, pre-processors providing input to a video encoder, web servers, set-top boxes, and any other device for processing a point cloud, a video or an image or other communication devices. As should be clear, the equipment may be mobile and even installed in a mobile vehicle. Computer software may be implemented by the processor 6010 or by hardware, or by a combination of hardware and software. As a non-limiting example, the embodiments may be also implemented by one or more integrated circuits. The memory 6020 may be of any type appropriate to the technical environment and may be implemented using any appropriate data storage technology, such as optical memory devices, magnetic memory devices, semiconductor-based memory devices, fixed memory, and removable memory, as non-limiting examples. The processor 6010 may be of any type appropriate to the technical environment, and may encompass one or more of microprocessors, general purpose computers, special purpose computers, and processors based on a multi-core architecture, as non-limiting examples.

As will be evident to one of ordinary skill in the art, implementations may produce a variety of signals formatted to carry information that may be, for example, stored or transmitted. The information may include, for example, instructions for performing a method, or data produced by one of the described implementations. For example, a signal may be formatted to carry the bitstream of a described embodiment. Such a signal may be formatted, for example, as an electromagnetic wave (for example, using a radio frequency portion of spectrum) or as a baseband signal. The formatting may include, for example, encoding a data stream and modulating a carrier with the encoded data stream. The information that the signal carries may be, for example, analog or digital information. The signal may be transmitted over a variety of different wired or wireless links, as is known. The signal may be stored on a processor-readable medium.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the singular forms "a", "an", and "the" may be intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "includes/comprises" and/or "including/comprising" when used in this specification, may specify the presence of stated, for example, features, integers, steps, operations, elements, and/or components but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. Moreover, when an element is referred to as being "responsive" or "connected" to another element, it may be directly responsive or connected to the other element, or intervening elements may be present. In contrast, when an element is referred to as being "directly responsive" or "directly connected" to other element, there are no intervening elements present.

It is to be appreciated that the use of any of the symbol/term 7”,“and/or”, and“at least one of”, for example, in the cases of“A/B”,“A and/or B” and“at least one of A and B”, may be intended to encompass the selection of the first listed option (A) only, or the selection of the second listed option (B) only, or the selection of both options (A and B). As a further example, in the cases of “A, B, and/or C” and“at least one of A, B, and C”, such phrasing is intended to encompass the selection of the first listed option (A) only, or the selection of the second listed option (B) only, or the selection of the third listed option (C) only, or the selection of the first and the second listed options (A and B) only, or the selection of the first and third listed options (A and C) only, or the selection of the second and third listed options (B and C) only, or the selection of all three options (A and B and C). This may be extended, as is clear to one of ordinary skill in this and related arts, for as many items as are listed.

Various numeric values may be used in the present application. The specific values may be for example purposes and the aspects described are not limited to these specific values.

It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements are not limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element without departing from the teachings of this application. No ordering is implied between a first element and a second element.

Reference to “one embodiment” or “an embodiment” or “one implementation” or“an implementation”, as well as other variations thereof, is frequently used to convey that a particular feature, structure, characteristic, and so forth (described in connection with the embodiment/implementation) is included in at least one embodiment/implementation. Thus, the appearances of the phrase “in one embodiment” or “in an embodiment” or “in one implementation” or “in an implementation”, as well any other variations, appearing in various places throughout this application are not necessarily all referring to the same embodiment.

Similarly, reference herein to “in accordance with an embodiment/example/implementation” or “in an embodiment/example/implementation”, as well as other variations thereof, is frequently used to convey that a particular feature, structure, or characteristic (described in connection with the embodiment/example/implementation) may be included in at least one embodiment/example/implementation. Thus, the appearances of the expression “in accordance with an embodiment/example/implementation” or “in an embodiment/example/implementation” in various places in the specification are not necessarily all referring to the same embodiment/example/implementation, nor are separate or alternative embodiment/examples/implementation necessarily mutually exclusive of other embodiments/examples/implementation.

Reference numerals appearing in the claims are by way of illustration only and shall have no limiting effect on the scope of the claims. Although not explicitly described, the present embodiments/examples and variants may be employed in any combination or sub-combination.

When a figure is presented as a flow diagram, it should be understood that it also provides a block diagram of a corresponding apparatus. Similarly, when a figure is presented as a block diagram, it should be understood that it also provides a flow diagram of a corresponding method/process.

Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

Various implementations involve decoding. “Decoding”, as used in this application, may encompass all or part of the processes performed, for example, on a received point cloud frame (including possibly a received bitstream which encodes one or more point cloud frames) in order to produce a final output suitable for display or for further processing in the reconstructed point cloud domain. In various embodiments, such processes include one or more of the processes typically performed by an image-based decoder.

As further examples, in one embodiment“decoding” may refer only to entropy decoding, in another embodiment “decoding” may refer only to differential decoding, and in another embodiment“decoding” may refer to a combination of entropy decoding and differential decoding. Whether the phrase“decoding process” may be intended to refer specifically to a subset of operations or generally to the broader decoding process will be clear based on the context of the specific descriptions and is believed to be well understood by those skilled in the art.

Various implementations involve encoding. In an analogous way to the above discussion about“decoding”,“encoding” as used in this application may encompass all or part of the processes performed, for example, on an input point cloud frame in order to produce an encoded bitstream. In various embodiments, such processes include one or more of the processes typically performed by an image-based decoder.

As further examples, in one embodiment“encoding” may refer only to entropy encoding, in another embodiment “encoding” may refer only to differential encoding, and in another embodiment“encoding” may refer to a combination of differential encoding and entropy encoding. Whether the phrase“encoding process” may be intended to refer specifically to a subset of operations or generally to the broader encoding process will be clear based on the context of the specific descriptions and is believed to be well understood by those skilled in the art.

Note that the syntax elements as used herein are descriptive terms. As such, they do not preclude the use of other syntax element names.

Various embodiments refer to rate distortion optimization. In particular, during the encoding process, the balance or trade-off between the rate and distortion is usually considered, often given the constraints of computational complexity. The rate distortion optimization may be usually formulated as minimizing a rate distortion function, which is a weighted sum of the rate and of the distortion. There are different approaches to solve the rate distortion optimization problem. For example, the approaches may be based on an extensive testing of all encoding options, including all considered modes or coding parameters values, with a complete evaluation of their coding cost and related distortion of the reconstructed signal after coding and decoding. Faster approaches may also be used, to save encoding complexity, in particular with computation of an approximated distortion based on the prediction or the prediction residual signal, not the reconstructed one. A mix of these two approaches may also be used, such as by using an approximated distortion for only some of the possible encoding options, and a complete distortion for other encoding options. Other approaches only evaluate a subset of the possible encoding options. More generally, many approaches employ any of a variety of techniques to perform the optimization, but the optimization is not necessarily a complete evaluation of both the coding cost and related distortion.

Additionally, this application may refer to“determining” various pieces of information. Determining the information may include one or more of, for example, estimating the information, calculating the information, predicting the information, or retrieving the information from memory.

Further, this application may refer to“accessing” various pieces of information. Accessing the information may include one or more of, for example, receiving the information, retrieving the information (for example, from memory), storing the information, moving the information, copying the information, calculating the information, determining the information, predicting the information, or estimating the information.

Additionally, this application may refer to“receiving” various pieces of information. Receiving is, as with“accessing”, intended to be a broad term. Receiving the information may include one or more of, for example, accessing the information, or retrieving the information (for example, from memory). Further, “receiving” is typically involved, in one way or another, during operations such as, for example, storing the information, processing the information, transmitting the information, moving the information, copying the information, erasing the information, calculating the information, determining the information, predicting the information, or estimating the information.

Also, as used herein, the word“signal” refers to, among other things, indicating something to a corresponding decoder. For example, in certain embodiments the encoder signals MIV metadata in a bitstream conforms to V- PCC. In this way, in an embodiment the same parameter may be used at both the encoder side and the decoder side. Thus, for example, an encoder may transmit (explicit signaling) a particular parameter to the decoder so that the decoder may use the same particular parameter. Conversely, if the decoder already has the particular parameter as well as others, then signaling may be used without transmitting (implicit signaling) to simply allow the decoder to know and select the particular parameter. By avoiding transmission of any actual functions, a bit savings is realized in various embodiments. It is to be appreciated that signaling may be accomplished in a variety of ways. For example, one or more syntax elements, flags, and so forth are used to signal information to a corresponding decoder in various embodiments. While the preceding relates to the verb form of the word“signal”, the word“signal” may also be used herein as a noun.

A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made. For example, elements of different implementations may be combined, supplemented, modified, or removed to produce other implementations. Additionally, one of ordinary skill will understand that other structures and processes may be substituted for those disclosed and the resulting implementations will perform at least substantially the same function(s), in at least substantially the same way(s), to achieve at least substantially the same result(s) as the implementations disclosed. Accordingly, these and other implementations are contemplated by this application.