The present disclosure generally relates to point cloud compression and, in particular to methods and apparatus of encoding/decoding point cloud geometry data sensed by at least one sensor.
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 embodiments of the present disclosure 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 the present disclosure.
As a format for the representation of 3D data, point clouds have recently gained traction as they are versatile in their capability in representing all types of physical objects or scenes. 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.
Virtual Reality (VR), Augmented Reality (AR) and immersive worlds have recently become a hot topic and are foreseen by many as the future of 2D flat video. The basic idea is to immerse the viewer in a surrounding environment, in contrast to a standard TV that only allows the viewer to look at the virtual world in front of him/her. 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 VR/AR worlds.
The automotive industry, and more particularly autonomous cars, are also domains in which point clouds may be intensively used. Autonomous cars should be able to “probe” their environment to make good driving decisions based on the detected presence and nature of their immediate nearby objects and road configuration.
A point cloud is a set of points located in a tridimensional (3D) space, optionally with additional values attached to each of the points. These additional values are usually called attributes. Attributes may be, for example, three-component colors, material properties like reflectance and/or two-component normal vectors to a surface associated with a point.
A point cloud is thus a combination of geometry data (locations of the points in a 3D space usually represented by 3D cartesian coordinates x,y and z) and attributes.
Point clouds may be sensed by various types of devices like an array of cameras, depth sensors, lasers (light detection and ranging, also known as Lidars), radars, or may be computer-generated (for example in movie post-production). Depending on the use cases, points clouds may have from thousands to up to billions of points for cartography applications. Raw representations of point clouds require a very high number of bits per point, with at least a dozen of bits per cartesian coordinate x, y or z, and optionally more bits for the attribute(s), for instance three times 10 bits for the colors.
It is important in many applications to be able to either distribute point clouds to an end-user or store them in a server by consuming only a reasonable amount of bitrate or storage space, while maintaining an acceptable (or very good) quality of experience. Efficient compression of these point clouds is a key point in order to make the distribution chain of many immersive worlds practical.
Compression may be lossy (like in video compression) for the distribution to and visualization by an end-user, for example on AR/VR glasses or any other 3D-capable device. Other use cases do require lossless compression, like medical applications or autonomous driving, to avoid altering the results of a decision obtained from the subsequent analysis of the compressed and transmitted point cloud.
Until recently, point cloud compression (aka PCC) was not addressed by the mass market and no standardized point cloud codec was available. In 2017, the standardization working group ISO/JCT1/SC29/WG11, aka Moving Picture Experts Group or MPEG, initiated work items on point cloud compression. This has led to two standards, namely
The V-PCC coding method compresses a point cloud by performing multiple projections of a 3D object to obtain 2D patches that are packed into an image (or a video when dealing with dynamic point clouds). Obtained images or videos are then compressed using already existing image/video codecs, allowing for the leverage of already deployed image and video solutions. By its very nature, V-PCC is efficient only on dense and continuous point clouds because image/video codecs are unable to compress non-smooth patches as would be obtained from the projection of, for example, Lidar-sensed sparse geometry data.
The G-PCC coding method has two schemes for the compression of a sensed sparse geometry data.
The first scheme is based on an occupancy tree, being locally any type of tree among octree, quadtree or binary tree, representing the point cloud geometry. Occupied nodes are split down until a certain size is reached, and occupied leaf nodes provide the 3D locations of points, typically at the center of these nodes. The occupancy information is carried by occupancy flags signaling the occupancy status of each of the child nodes of nodes. By using neighbor-based prediction techniques, high level of compression of the occupancy flags can be obtained for dense point clouds. Sparse point clouds are also addressed by directly coding the position of point within a node with non-minimal size, by stopping the tree construction when only isolated points are present in a node; this technique is known as Direct Coding Mode (DCM).
The second scheme is based on a predictive tree in which each node represents the 3D location of one point and the parent/child relation between nodes represents spatial prediction from parent to children. This method can only address sparse point clouds and offers the advantage of lower latency and simpler decoding than the occupancy tree. However, compression performance is only marginally better, and the encoding is complex, relatively to the first occupancy-based method, because the encoder must intensively look for the best predictor (among a long list of potential predictors) when constructing the predictive tree.
In both schemes, attribute (de)coding is performed after complete geometry (de)coding, leading practically to a two-pass coding. Thus, the joint geometry/attribute low latency is obtained by using slices that decompose the 3D space into sub-volumes that are coded independently, without prediction between the sub-volumes. This may heavily impact the compression performance when many slices are used.
Combining together requirements on encoder and decoder simplicity, on low latency and on compression performance is still a problem that has not been satisfactory solved by existing point cloud codecs.
An important use case is the transmission of sparse geometry data sensed by at least one sensor mounted on a moving vehicle. This usually requires a simple and low latency embarked encoder. Simplicity is required because the encoder is likely to be deployed on computing units which perform other processing in parallel, such as (semi-) autonomous driving, thus limiting the processing power available to the point cloud encoder. Low latency is also required to allow for fast transmission from the car to a cloud in order to have a real-time view of the local traffic, based on multiple-vehicle acquisition, and take adequate fast decision based on the traffic information. While transmission latency can be low enough by using 5G, the encoder itself shall not introduce too much latency due to coding. Also, compression performance is extremely important since the flow of data from millions of cars to the cloud is expected to be extremely heavy.
Specific techniques related to spinning Lidar-sensed sparse geometry data have been already been exploited in G-PCC and have led to very significant gains of compression.
First, G-PCC exploits the elevation angle (relative to the horizontal ground) of sensing from a spinning Lidar head 10 as depicted on
A regular distribution along the azimuthal angle has been observed on Lidar-sensed data as depicted on
This quasi 1D property has been exploited in G-PCC in both the occupancy tree and the predictive tree by predicting, in the spherical coordinate space, the location of a current point based on an already coded point by using the discrete nature of angles.
More precisely, the occupancy tree uses DCM intensively and entropy codes the direct locations of points within a node by using a context-adaptive entropy coder. Contexts are then obtained from the local conversion of the point locations into angular coordinates (ϕ, θ) and from the location of these angular coordinates relative to discrete angular coordinates (ϕi, θj) obtained from precedingly coded points. The predictive tree directly codes a first version of a point location in the angular coordinates (r2D, ϕ, θ), where r2D is the projected radius on the horizontal xy plane as depicted on
G-PCC does use the angular priors to better compress spinning Lidar-sensed sparse geometry data but does not adapt the coding structure to the order of sensing. By its very nature, the occupancy tree must be coded down to its last depth before outputting a point. This occupancy is coded in the so-called breadth-first order: the occupancy of the root node is first coded, indicating its occupied child nodes; then the occupancy for each of the occupied child nodes is coded, indicating the occupied grand-child nodes; and so on iteratively over the tree depth until leaf nodes can be determined and the corresponding points are provided/output to an application or to the attribute(s) coding scheme. Regarding the predictive tree, the encoder is free to choose the order of point in the tree, but to obtain good compression performance, to optimize the prediction accuracy, G-PCC proposes to code one tree per sensor. This has mainly the same drawback as using one coding slice per sensor, i.e. non-optimal compression performance because prediction between sensors is not allowed and does not provide encoder low latency. Worse, one should have one coding processing per sensor and the number of core coding units should equal the number of sensors; this is not practical.
In brief, in a framework of a spinning sensors head used for sensing sparse geometry data of a point cloud, prior arts do not solve the problem of combining encoding and decoding simplicity, low latency and compression performance.
Moreover, sensing sparse geometry data of point cloud by using spinning sensors head has some drawbacks and other types of sensor head may be used.
The mechanical parts generating the spin (rotation) of a spinning sensors head are prone to breakage and are costly. Also, by construction, the angle of view is necessarily 2π. This does not allow to sense a particular region of interest with high frequency, for instance it may be more interesting to sense in front of a vehicle than behind. Practically in most cases, when a sensor is attached to a vehicle, most of the 2π angle of view is screened by the vehicle itself and the screened angle of view does not need to be sensed.
New types of sensors have emerged recently, allowing for a more flexible selection of the region to be sensed. In most recent designs, a sensor can be more freely and electronically (thus avoiding fragile mechanical parts) moved to obtain a large variety of sensing path in the 3D scene as depicted on
As is illustrated on
Combining together requirements on encoder and decoder simplicity, on low latency and on compression performance of point cloud sensed by any type of sensors is still a problem that has not been satisfactory solved by existing point cloud codecs.
At least one embodiment of the present disclosure has been devised with the foregoing in mind.
According to a first aspect of the present disclosure, there is provided a method of encoding points of a point cloud sensed by at least one sensor associated with a sensor index into a bitstream of encoded point cloud data, wherein the method comprises: encoding, into the bitstream, an information representing a sensing path, wherein the sensing path is defined in a two-dimensional angular coordinate space comprising an azimuthal coordinate representative of an azimuthal angle representing a sensing angle of a sensor relative to a referential and an elevation coordinate representative of an elevation angle of a sensor relative to a horizontal referential plane; the sensing path is used to sense the points of the point cloud according to ordered coarse points representing potential locations of sensed points of the point cloud, each coarse point being defined in the two-dimensional angular coordinate space from one sample index associated with a sensing time instant and one sensor index associated with a sensor; said sample index is defined along the sensing path according to a sensing scheme; for each point of the point cloud, obtaining one sensing point in the two-dimensional angular coordinate space from a sample index associated with a sensing time instant of the point of the point cloud along the sensing path, and the sensing scheme; obtaining one coarse point in the two-dimensional angular coordinate space by shifting the sensing point in the two-dimensional angular coordinate space with shifting values that depend on the sensor index associated with the sensor that sensed the point of the point cloud; and encoding, into the bitstream, the point of the point cloud relatively to the coarse point.
According to a second aspect of the present disclosure, there is provided a method of decoding points of a point cloud sensed by at least one sensor associated with a sensor index from a bitstream of encoded point cloud data, wherein the method comprises decoding, from the bitstream, an information representing a sensing path wherein the sensing path is defined in a two-dimensional angular coordinate space comprising an azimuthal coordinate representative of an azimuthal angle representing a sensing angle of a sensor relative to a referential and an elevation coordinate representative of an elevation angle of a sensor relative to a horizontal referential plane; the sensing path has been used to sense the points of the point cloud according to ordered coarse points representing potential locations of sensed points of the point cloud, each coarse point being defined in the two-dimensional angular coordinate space from one sample index associated with a sensing time instant and one sensor index associated with a sensor; said one sample index is defined along the sensing path according to a sensing scheme; for each point of the point cloud, obtaining one sensing point in the two-dimensional angular coordinate space from a sample index associated with a sensing time instant of the point of the point cloud along the sensing path, and the sensing scheme; obtaining a coarse point in the two-dimensional angular coordinate space by shifting the sensing point in the two-dimensional angular coordinate space with shifting values that depend on the sensor index associated with the sensor that sensed the point of the point cloud; and decoding a point of the point cloud relatively to the coarse point.
In some embodiments, angular coordinates of the coarse point are obtained by shifting angular coordinates of the sensing point in the two-dimensional angular coordinate space by an azimuthal angle shifting coefficient and an elevation angle shifting coefficient, both depending on the sensor index.
In some embodiments, the azimuthal angle shifting coefficient and/or elevation angle shifting coefficient may be encoded or decoded relatively to at least one previously encoded azimuthal angle shifting coefficient and at least one previously encoded elevation angle shifting coefficient corresponding to at least one other sensor index.
In some embodiments, the azimuthal angle shifting coefficients equal zero.
In one embodiment, the sum of the azimuthal angle shifting coefficients equals 0 and the sum of elevation angle shifting coefficients equals 0.
In some embodiments, the angular coordinates of the coarse point is obtained by further shifting the angular coordinates of the sensing point in the two-dimensional angular coordinate space by an offset depending on a sensing delay and a two-dimensional angular velocity of the sensing point.
In some embodiments, the sensing delay is encoded into the bitstream.
In some embodiments, the sensing path corresponds to a sensing trajectory of a particular sensor of reference.
According to a third aspect of the present disclosure, there is provided an apparatus of encoding points of a point cloud sensed by at least one sensor associated with a sensor index into a bitstream of encoded point cloud data. The apparatus comprising one or more processors configured to carry out a method according to the first aspect of the present disclosure.
According to a fourth aspect of the present disclosure, there is provided an apparatus of decoding points of a point cloud sensed by at least one sensor associated with a sensor index from a bitstream of encoded point cloud data. The apparatus comprising one or more processors configured to carry out a method according to the second aspect of the present disclosure.
According to a fifth aspect of the present disclosure, there is provided a non-transitory storage medium carrying instructions of program code for executing a method according to the first aspect of the present disclosure.
According to a sixth aspect of the present disclosure, there is provided a non-transitory storage medium carrying instructions of program code for executing a method according to the second aspect of the present disclosure.
Reference will now be made, by way of example, to the accompanying drawings which show embodiments of the present disclosure, and in which:
Similar reference numerals may have been used in different figures to denote similar components.
At least one of the embodiments is described more fully hereinafter with reference to the accompanying figures, in which examples of at least one of the embodiments are illustrated. 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 the present disclosure.
At least one of the aspects generally relates to point cloud encoding and decoding, one other aspect generally relates to transmitting a bitstream generated or encoded and one other aspects relates to receiving/accessing a decoded bitstream.
Moreover, the present aspects are not limited to MPEG standards such as MPEG-I part 5 or part 9 that relate 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 and part 9). Unless indicated otherwise, or technically precluded, the aspects described in the present disclosure may be used individually or in combination.
In brief, the present invention relates to encoding/decoding a point cloud sensed by any type of sensor head according to a sensing path. Some examples of such sensor head and sensing paths are shown on
For each point of the point cloud, one sample index associated with a sensing time instant of the point of the point cloud and a sensor index of a sensor that sensed the point of the point cloud are obtained.
A couple, formed by a sample index and a sensor index, identifies a coarse point (potential location) of a sensed point of the point cloud. However, some of these potential locations may not be occupied by sensed points for multiple reasons. For example, when a sensor uses a laser beam to sense an object, the beam may not be reflected (no object) or may be too weakly reflected (due to adverse surface conditions) or may not be reflected within a predetermined temporal window (object too far), and no object is detected. Thus, the occupancies of the coarse points (potential locations) shall be encoded into the bitstream to signal whether a coarse point (potential location) is occupied by a sensed point. One order index difference is encoded into the bitstream to encode the occupancy of a coarse point by a sensed point of the point cloud. The order index difference represents a difference between an order index of a coarse point identified by the sample index and the sensor index, and an order index of another coarse point associated with a previous sensed point of the point cloud in the list of ordered coarse points. One sensing point in the two-dimensional angular coordinate space is obtained from the sample index and the sensing scheme. One coarse point in the two-dimensional angular coordinate space is obtained by shifting a sensing point in the two-dimensional angular coordinate space with shifting values that depend on the sensor index associated with the sensor that sensed the point of the point cloud. The point of the point cloud is then encoded into the bitstream relatively to the coarse point.
The present invention introduces the use of coarse points. An occupied coarse point occupied by a sensed point of the point cloud is a coarse representation of said sensed point and the angular coordinates of said sensed point may be encoded relatively to the angular coordinates of said occupied coarse point. Encoding a point of a point cloud relatively to a coarse point is valid independently of the used sensor head and any type of sensors may be used including, but not limited to particular sensor head such as a spinning sensors head or sensor head able to sense points of a point cloud following a programmable sensing path.
Introducing the coarse representation for coding point cloud geometry data is advantageous compared to G-PCC as it provides better compression gains, lower complexity, and also very low latency because points are proceeded, by both encoder and decoder, in their sensing order. The present invention obtains a coarse point in the two-dimensional angular coordinate space by shifting a sensing point in the two-dimensional angular coordinate space with shifting values that depend on the sensor index associated with the sensor that sensed the point of the point cloud.
Shifting the coordinates of a sensing point in a two-dimensional space requires very low computing resources for obtaining a coarse representation of the sensed point of the point cloud.
In step 110, a sensing path SP is represented as a two-dimensional curve defined in a two-dimensional angular coordinate (ϕ, θ) space. The sensing path SP is obtained from sensing characteristics. The two-dimensional angular coordinate (ϕ, θ) space comprises an azimuthal coordinate ϕ representative of an azimuthal angle representing a sensing angle of a sensor relative to a referential and an elevation coordinate θ representative of an elevation angle of a sensor relative to a horizontal referential plane.
In one embodiment of step 110, illustrated on
Control points ok do not need to correspond to some sensing time instant. However, it may be advantageous to have the first control point
In one embodiment of step 110, one sensing characteristics imposes that the sensing path SP is closed by an extra interpolation between the last point and the first point of the sensing path SP.
In one embodiment of step 110, one other sensing characteristics imposes that the sensing path SP is a fixed path over which the sensing may loop continuously.
In one embodiment of step 110, one other sensing characteristics imposes that the sensing path SP is a zigzag path covering at least a part of the viewport of a sensor.
The sensing path SP is used to sense the points P of the point cloud according to ordered coarse points Pλ(s). A coarse point Pλ(s) represents a potential location in the two-dimensional coordinate (ϕ, θ) space of a sensed point P of the point cloud. Each coarse point Pλ(s) is defined in the two-dimensional angular coordinate (ϕ, θ) space from one sample index s associated with a sensing time instant along the sensing path SP, and one sensor index λ associated with a sensor. A coarse point Pλ(s) corresponds to a coarse representation of a potential sensed point of the cloud.
Each sample index s corresponds to a sensing point Pover(s) in the two-dimensional angular coordinate (ϕ, θ) space. A sensing point Pover(s) is representative of a reference direction that is used to determine the direction (coarse point Pλ(s)) to which a sensor λ of the sensor head is pointing to at a sensing time instant associated with a sample index s. The angular coordinates (ϕover, θover), as a function of the sample index s, of a sensing point Pover(s) on the sensing path SP are obtained from a given sensing scheme.
In one embodiment of step 110, illustrated on
In one embodiment of step 110, the sensing scheme may provide a repartition of the sensing point Pover(s) along the sensing path SP to get a uniform sampling of the azimuthal coordinates ϕ of said at least one sensing point Pover(s).
In one embodiment of step 110, the sensing scheme may provide a repartition of the sensing point Pover(s) along the sensing path SP to get a uniform sampling of the elevation coordinates θ of said at least one sensing point Pover(s).
On the illustrative example of
An order index o(P) is associated with each coarse point according to the rank of said coarse point among the ordered coarse points.
In one embodiment, the order index o(P) of a coarse point occupied by a sensed point P of the point cloud may be obtained by:
where K is the number of sensors of a set of sensors or the number of different positions of a single sensor for a same sample index, λ is the sensor index of the sensor that sensed the point P of the point cloud at the sensing time instant s.
In step 120, an information I(SP) representing the sensing path SP in the two-dimensional angular coordinate (ϕ, θ) space may be encoded into a bitstream B.
In one embodiment of step 120, the information I(SP) may comprise data representing the angular coordinates (ϕk, θk) of the control points
In one embodiment of step 120, the angular coordinates (ϕk, θk) of the control points
In one embodiment of step 120, the angular coordinates (ϕk, θk) of the control points
For example, the predicted angular coordinates may be obtained from the angular coordinates of the last encoded control point (m=1):
In another example, the predicted angular coordinates may be obtained by linearly combining multiple previously encoded control points (m=m1 to m2) where m1 and m2 are two integer values:
where wm are weighting coefficients.
In one variant, the coordinates (ϕk, θk) or the angular residual (ϕk,res, θk,res) may be quantized before encoding.
In one variant, the angular residual (ϕk,res, θk,res) may be further compressed by using an entropy coder like CABAC (Context Adaptive Binary Arithmetic Coding) after binarization of their values.
Any other entropy coder may be used.
In one embodiment of step 120, when the sensing path SP does not vary with time, the information I(SP) may be encoded as an element of a High-Level Syntax (HLS), for example in a Sequence Parameter Set (SPS) that gathers general coding parameters for the point cloud. Then, the coded sensing path may be used for several instances of the point cloud (point cloud frames).
In one embodiment of step 120, when the sensing path SP is frame dependent, the information I(SP) may be encoded as a High-Level Syntax example in a Geometry Parameter Set (GPS) of a current point cloud frame. This requires the determination of the sensing path before coding in the GPS and may lead to some latency up to one frame.
In another embodiment of step 120, the information I(SP) may be encoded into the bitstream B carrying encoded point cloud data.
By doing so, coding on-the-fly the sensing path SP preserves the low latency advantage of the coarse representation as it requires only a local determination of the sensing path before coding.
Referring to
A sensed point P of the point cloud may be represented by three-dimensional cartesian coordinates (xp, yp, zp) or three-dimensional spherical coordinates (rP, ϕP, θP). Well-known methods in prior art may be used to convert cartesian coordinates to spherical coordinates or inversely.
In step 130, one sample index s associated with a sensing time instant of a point P and one sensor index λ of a sensor that sensed the point P may be obtained.
The sample index s and the sensor index λ are obtained in a straightforward manner during sensing because the sensor index corresponds to the sensor used to sense the point P at a sensing time instant corresponding to the sample index s.
In step 140, one order index difference Δo may be encoded into the bitstream B. The order index difference Δo represents a difference between an order index o(P) of a coarse point identified by the sample index s and the sensor index λ, and an order index o(P−1) of another coarse point associated with a previous sensed point P−1 of the point cloud:
In one variant, the order index difference Δo may be compressed using an entropy coder like CABAC after binarization of their values.
Any other entropy coder may be used.
In one variant, the order index o(P1) of the first coarse point occupied by the first sensed point P1 of the point cloud may be directly encoded into the bitstream B. This is equivalent to arbitrary setting the order index of a virtual zero-th point to zero, i.e. o(P0)=0, and coding Δo1=o(P1)−o(P0)=o(P1).
Given the order index o(P1) of the first coarse point occupied by the first sensed point P1 of the point cloud, and order differences Δo, one can recursively reconstruct the order index o(P) of any coarse point occupied by a sensed point P of the point cloud by:
On
In step 150, one sensing point Pover(s) in the two-dimensional angular coordinate (ϕ, θ) space may be obtained from the sample index s according to the sensing scheme as above explained.
For example, the sensing scheme may inform that sensing is performed uniformly along the sensing path, such that the sensing Pover(s) is located at a distance (taking along the sensing path SP) proportional to the sample index s from some origin of the sensing path SP.
In step 160, a coarse point Pλ(s) in the two-dimensional angular coordinate space may be obtained by shifting the sensing point Pover(s) in the two-dimensional angular coordinate (ϕ, θ) space:
where δP is a shifting vector for the sensing point Pover(s) that depends on the sensor index λ associated with the sensor that sensed the point P of the point cloud.
The obtained coarse point Pλ(s) is associated with the point P of the point cloud sensed by a sensor having a sensor index λ at a sensing time instant associated with the sample index s.
In one embodiment of step 160, illustrated on
The angular coordinates (ϕλ, θλ) of the coarse point Pλ(s) depend on the angular coordinates (ϕover, θover) of the sensing point Pover(s), and depend on the intrinsic geometry of the sensor head.
In one variant, the azimuthal angle shifting coefficients δθλ and the elevation angle shifting coefficients δθλ are known by the decoder beforehand.
In one variant, an azimuthal angle shifting coefficient δθλ and an elevation angle shifting coefficient δθλ may be encoded into the bitstream B for the sensor index λ and do not depend on the sample index s.
In one embodiment of this variant, azimuthal angle shifting coefficients δθλ and elevation angle shifting coefficients δθλ may be encoded in High-Level Syntax (HLS) elements such as Sequence Parameter Set (SPS) and/or Geometry Parameter Set (GPS).
In one embodiment of this variant, the azimuthal angle shifting coefficient δθλ and elevation angle shifting coefficient δθλ may be encoded relatively to a previously encoded azimuthal angle shifting coefficient δϕλ′ and a previously encoded elevation angle shifting coefficient δθλ′ corresponding to another sensor index λ′. The following residual may then be encoded into the bitstream B:
(δϕλ,δθλ)−(δϕλ′,δθλ′)
In another embodiment of this variant, the azimuthal angle shifting coefficient δϕλ and elevation angle shifting coefficient δθλ may be encoded relatively to two previously encoded azimuthal angle shifting coefficients δϕλ′ and δϕλ″, and to two previously encoded elevation angle shifting coefficients δθλ′ and δθλ″ corresponding to two different sensor indices λ′ and λ″. The following residual may then be encoded into the bitstream B:
In yet another embodiment of this variant, the azimuthal angle shifting coefficient δθλ and elevation angle shifting coefficient δθλ may be encoded relatively to a weighted average of previously encoded azimuthal angle shifting coefficients and to a weighted average of previously encoded elevation angle shifting coefficients.
In another variant, an azimuthal angle shifting coefficient δϕλ and an elevation angle shifting coefficient Δθλ depend on the sample index s and may be encoded into the bitstream B for each coarse point Pλ(s).
In one embodiment of this variant, the azimuthal angle shifting coefficient δϕλ(s) and elevation angle shifting coefficient δθλ(s) corresponding to a coarse point Pa(s) may be encoded relatively to at least one previously encoded azimuthal angle shifting coefficient and at least one previously encoded elevation angle shifting coefficient corresponding to at least one coarse point.
In another embodiment of this variant, the azimuthal angle shifting coefficient δϕλ(s) and elevation angle shifting coefficient δθλ(s) corresponding to a coarse point Pλ(s) may be encoded relatively to the previously encoded azimuthal angle shifting coefficient δϕλ(s−n) and the previously encoded elevation angle shifting coefficient δθλ(s−n) corresponding to the latest coarse point Pλ(s−n) for which a point of the point cloud has been encoded with the sensor index λ. The following residual may then be encoded into the bitstream B:
In another embodiment of this variant, the azimuthal angle shifting coefficient δϕλ(s) and elevation angle shifting coefficient δθλ(s) corresponding to a coarse point Pλ(s) may be encoded relatively to a weighted linear combination of azimuthal angle shifting coefficients and/or a weighted linear combination of elevation angle shifting coefficients corresponding to multiple previously encoded coarse points for which multiple points of the point cloud have been encoded with the sensor index λ.
In yet another embodiment of this variant, the weighted linear combination may combine the azimuthal angle shifting coefficient δϕλ(s−n) and the elevation angle shifting coefficient δθλ(s−n) corresponding to the latest coarse point Pλ(s−n), and the azimuthal angle shifting coefficient δϕλ(s−m) and the elevation angle shifting coefficient δθλ(s−m) corresponding to the previous latest coarse point Pλ(s−m).
For example, the following residual may be encoded into the bitstream B:
where ‘s-n’ is the latest sample index for which a point has been coded with sensor index λ, and ‘s-m’ is the penultimate sample index for which a point has been coded with sensor index ‘λ’.
In one variant, illustrated on
In one variant, the sum of the azimuthal angle shifting coefficients δϕλ equals 0 and the sum of elevation angle shifting coefficients δθλ equals 0:
This variant is advantageous because coding of an azimuthal angle shifting coefficients δϕλ and an elevation angle shifting coefficients δθλ into the bitstream B may be avoided as they can be deduced from other coded coefficients. For example, the azimuthal angle shifting coefficient δϕλ and the elevation angle shifting coefficients δθλ associated with the first or the last sensor of a sensor head may be omitted into the bitstream B.
In one variant, the sensing path SP corresponds to the sensing trajectory of a particular sensor λref of reference such that one has Pλref(s)=Pover(s) and
(δϕλref,δθλref)=(0,0)
This variant is advantageous because it does not need coding of the azimuthal angle shifting coefficients δϕλref and the elevation angle shifting coefficients δθλref for the sensor λref of reference.
Typically, all sensors of a sensor head do not sense a real scene at the same sensing time instant. For example, a sensor having a sensor index λ may sense the scene at time ts+Δtλ where ts is a sensing time instant associated with a sample index s. Therefore, the 2D angular velocity v(s)=v(ts) of a sensing point Pover(s)=Pover(ts) may not be neglected in the determination of the coarse point Pλ(s) that is not sensed at time ts+Δtλ.
In one embodiment of step 160, with a first order temporal approximation, the angular coordinates (ϕλ, θλ) of the coarse point Pλ(s) may be obtained by further shifting the angular coordinates of the sensing point Pover(s) in the two-dimensional angular coordinate (ϕ, θ) space by an offset depending on a sensing delay Δtλ and a2D angular velocity v(s) of the sensing point Pover(s):
This variant improves the determination of the coarse point Pλ(s) by correcting the angular coordinates of the coarse point Pλ(s) according to the 2D angular velocity of the sensing point Pover(S).
This variant is particularly adapted to spinning sensor head such as Lidar sensor head using a vertically rotating mirror to adjust the sensing elevation angle.
In one variant, the velocity v(s) of a sensing point Pover(s) may be obtained from an angular distance of this sensing points and a previous sensing point Pover(ts-1) by.
In one variant, the velocity v(s) of a sensing point Pover(s) may be obtained from an angular distance between a first control point
where tk is a sensing time instant associated with the control point
In one variant, the sensing delays Δtλ may be fixed (depend on sensor characteristics).
In one variant, the sensing delays Δtλ may be encoded into the bitstream B.
With some spinning sensor head, such as a Lidar sensor head using a vertically rotating mirror to adjust the sensing elevation angle, elevation angle shifting coefficient δθλ may oscillate between a minimum elevation angle shifting coefficient δθmin, and a maximum elevation angle shifting coefficient δθmax, and so with a fixed oscillation amplitude δθmax−δθmin.
In some other systems the oscillation amplitude may also vary with time.
In one embodiment of step 160, in order to handle data coming from such spinning sensor head, the elevation angle shifting coefficient δθλ is multiplied by an amplitude coefficient factor α(s):
Combining different embodiments together, the angular coordinates (ϕλ, θλ) of the coarse point Pλ(s) may be obtained by:
In on variant, the amplitude coefficient factor α(s) is encoded in the bitstream B as an element of a High-Level Syntax (HLS), for example in a header of such element.
In on variant, the amplitude coefficient factor α(s) is directly encoded in the bitstream B if the oscillations amplitude is interactively/dynamically changing during the point cloud sensing.
In step 170, the point P may be encoded into the bitstream B relatively to the coarse point Pλ(s).
In one embodiment of step 170, encoding the point P relatively to the coarse point Pλ(s) may comprise encoding an angular residual (res(ϕ), res(θ)) based on angular coordinates (ϕP, θP) of the point P and angular coordinates (ϕλ, θλ) of the coarse point Pλ(s):
Optionally, the method 100 may further comprise in step 180, encoding, in the bitstream B, the radius value rp of spherical or cylindrical coordinates of the point P. A reconstructed radius value rp,rec may be obtained by decoding the encoded radius value rp.
In one embodiment of step 180, the radius value rp may be quantized and the reconstructed radius value rp,rec may be obtained by inverse quantizing the quantized radius value Q1(rp). For example, Q1 is a uniform quantizer using a quantization step Δ1:
The reconstructed radius value rp,rec is then obtained by inverse quantizing the quantized radius value Q1(rp) by an inverse quantizer IQ1:
Any other quantizer and inverse quantizer may be used.
In an embodiment of step 180, the radius value rp may be quantized and coded, and the reconstructed radius value rp,rec is obtained by decoding and inverse quantizing the coded radius value rp.
In one variant, the quantized radius value rp may be entropy encoded using an entropy coder like CABAC after binarization of their values.
Any other entropy coder may be used.
In one embodiment of step 180, the radius value rp may represent a three-dimensional radius r3D.
In one embodiment of step 180, the radius value rp may represent the projected radius r2D on the horizontal xy plane as depicted on
In one embodiment, the method 100 may further comprise, in step 190, encoding, into the bitstream B, a cartesian coordinate residual (xp,res, yp,res, zp,res) for the point P based on the cartesian coordinates of the point P and cartesian coordinates (xp,rec, yp,rec, zp,rec) of a reconstructed point Prec obtained from the coarse point Pλ(s), the angular residual (res(ϕ), res(θ)) and the reconstructed radius value rp,rec.
First, angular coordinates (ϕrec, θrec) of the reconstructed point Prec are obtained by adding the angular coordinates (ϕλ, θλ) of the coarse point Pλ(s) and the angular residual (res(ϕ),res(θ)):
Next, cartesian coordinates (xp,rec, yp,rec, zp,rec) of the reconstructed point Prec are obtained from the angular coordinates (ϕrec, θrec) of the reconstructed point Prec and the radius value rp,rec:
Finally, the cartesian coordinate residual (xp,res, yp,res, zp,res) is obtained based on the cartesian coordinates (xp, yp, zp) of the point P and the cartesian coordinates (xp,rec, yp,rec, zp,rec) of the reconstructed point Prec:
In one variant, a quantized cartesian coordinate residual Q2(xp,res, yp,res, zp,res) may be obtained by quantizing the cartesian coordinate residual (xp,res, yp,res, zp,res) and the quantized cartesian coordinate residual Q2(xp,res, yp,res, zp,res) is encoded.
For example, Q2 is a uniform quantizer using a quantization step Δ2:
The cartesian coordinate residual (xp,res, yp,res, zp,res) may be obtained by inverse quantizing the quantized cartesian coordinate residual Q2(xp,res, yp,res, zp,res) by:
Any other quantizer and inverse quantizer may be used.
In one variant, the quantized cartesian coordinate residual Q2(xp,res, yp,res, zp,res) may be entropy encoded using an entropy coder like CABAC after binarization of their values.
Any other entropy coder may be used.
In one variant, a quantized angular residual Q3(res(ϕ), res(θ)) may be obtained by quantizing the angular residual (res(ϕ), res(θ)) and the quantized angular residual Q3(res(ϕ),res(θ)) is encoded.
Angular coordinates of the reconstructed point Prec (equation 1) are then obtained by:
For example, Q3 is a uniform quantizer using a quantization step Δ3:
And IQ3 is the inverse quantizer:
Any other quantizer and inverse quantizer may be used.
In one variant, the quantized angular residual Q3(res(ϕ),res(θ)) may be entropy encoded using an entropy coder like CABAC after binarization of their values.
Any other entropy encoder may be used.
In step 210, the information I(SP) may be decoded from a bitstream.
In one embodiment of step 210, the angular coordinates (ϕk, θk) of the control points
In one embodiment of step 210, the angular coordinates (ϕk, θk) of the control points
In one variant, the coordinates (ϕk, θk) or the angular residual (ϕk,res, θk,res) may be decoded before inverse quantized.
In one variant, the angular residual (ϕk,res, θk,res) may be further decompressed by using an entropy decoder like CABAC after binarization of their values.
Any other entropy decoder may be used.
In one embodiment of step 210, a two-dimensional curve representing the sensing path SP may be obtained by interpolation between the control points
In one embodiment of step 210, when the sensing path SP does not vary with time, the information I(SP) may be decoded from an element of a High-Level Syntax (HLS), for example in a Sequence Parameter Set (SPS). Then, the decoded sensing path may be used for several instances of the point cloud (point cloud frames).
In one embodiment of step 210, when the sensing path SP is frame dependent, the information I(SP) may be decoded from a High-Level Syntax example in a Geometry Parameter Set (GPS) of a current point cloud frame. This requires the determination of the sensing path before decoding in the GPS and may lead to a latency up to one frame.
In another embodiment of step 210, the information I(SP) may be decoded from the bitstream B carrying encoded point cloud data.
By doing so, decoding on-the-fly the sensing path SP preserves the low latency advantage of the coarse representation as it requires only a local determination of the sensing path before coding.
Referring to
In step 220, one order index difference Δo may be decoded from the bitstream B for a point P of the point cloud to be decoded.
The order index difference Δo represents a difference between an order index o(P) of a coarse point associated with the point P, and an order index o(P−1) of another coarse point associated with a previous decoded point P−1 of the point cloud.
In one variant, the order index o(P1) of the first coarse point (occupied by the first point P1 of the point cloud to be decoded) may be directly decoded from the bitstream B.
In one variant, the order index differences Δon may be decompressed using an entropy decoder like CABAC after binarization of their values.
Any other entropy decoder may be used.
In step 230, one sensor index λ associated with a sensor that sensed the point P and one sample index s associated with the sensing time instant of the point P may be obtained from an order index o(P) obtained from the decoded order index difference Δo.
The sensor index λ and the sample index s may be obtained from the order index o(P) by:
where the division/K is the integer division (aka Euclidian division). Therefore, o(P1) and Δo are an alternative representation of λ and s.
In step 150, one sensing point Pover(s) in the two-dimensional angular coordinate (ϕ, θ) space may be obtained from the sample index s according to the sensing scheme as above discussed.
In step 160, a coarse point Pλ(s) in the two-dimensional angular coordinate space may be obtained by shifting the sensing point Pover(s) in the two-dimensional angular coordinate (ϕ, θ) space as above explained.
In step 240, a point P of the point cloud may be decoded relatively to the coarse point Pλ(s).
In one embodiment of step 240, decoding a point P of the point cloud from a coarse point Pλ(s) may comprise decoding an angular residual (res(ϕ), res(θ)) and obtaining angular coordinates (ϕrec, θrec) of a reconstructed point Prec by adding said decoded angular residual (res(ϕ), res(θ)) and angular coordinates (ϕλ, θλ) of the coarse point Pλ(s) (equation 1).
In step 270, the cartesian coordinates (xp, yp, zp) of the point P may then be the cartesian coordinates (xp,rec, yp,rec, zp,rec) obtained from the angular coordinates (ϕrec, θrec) of a reconstructed point Prec and a radius value rp,rec by equation (2).
Optionally, the method 200 may further comprise in step 250, decoding, from the bitstream B, the radius value rp,rec.
In one embodiment of step 250, the radius value rp,rec is entropy-decoded from the bitstream B.
In one embodiment of step 250, the radius value rp,dec may be inverse quantized by the inverse quantizer IQ1. Any other inverse quantizer may be used.
In an embodiment of step 250, the radius value rp,rec may be decoded and inverse quantized.
In one variant, the quantized radius value may be entropy decoded using an entropy coder like CABAC after binarization of their values.
Any other entropy coder may be used.
In one embodiment of step 250, the radius value rp,rec represents a three-dimensional radius r3D.
In one embodiment of step 250, the radius value rp,rec represents the projected radius r2D on the horizontal xy plane as depicted on
In one embodiment, the method 200 further comprises in step 260, decoding a cartesian coordinate residual (xp,res, yp,res, zp,res) from the bitstream B. The cartesian coordinate residual (xp,res, yp,res, zp,res) is given by equation (3).
In step 270, the cartesian coordinates (xp, yp, zp) of the point P may then be obtained by adding the decoded cartesian coordinate residual (xp,res, yp,res, zp,res) and the cartesian coordinates of the reconstructed point Prec:
In one variant, the cartesian coordinate residual (xp,res, yp,res, zp,res) may be obtained by decoding and inverse quantizing using the inverse quantizer IQ2.
Any other inverse quantizer may be used.
In one variant, the decoding may be an entropy decoder using an entropy decoder like CABAC after binarization of values.
Any other entropy decoder may be used.
In one variant, an angular residual (res(ϕ), res(θ)) may be obtained by decoding and inverse quantizing using the inverse quantizer Q3.
Any other quantizer and inverse quantizer may be used.
In one variant, the decoding may be an entropy decoder using an entropy decoder like CABAC after binarization of values.
Any other entropy decoder may be used.
Angular coordinates of the reconstructed point Prec (equation 1) are then obtained by:
System 300 may be embedded as one or more devices including the various components described below. In various embodiments, the system 300 may be configured to implement one or more of the aspects described in the present disclosure.
Examples of equipment that may form all or part of the system 300 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 300, singly or in combination, may be embodied in a single integrated circuit (IC), multiple ICs, and/or discrete components. For example, in at least one embodiment, the processing and encoder/decoder elements of system 300 may be distributed across multiple ICs and/or discrete components. In various embodiments, the system 300 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.
The system 300 may include at least one processor 310 configured to execute instructions loaded therein for implementing, for example, the various aspects described in the present disclosure. Processor 310 may include embedded memory, input output interface, and various other circuitries as known in the art. The system 300 may include at least one memory 320 (for example a volatile memory device and/or a non-volatile memory device). System 300 may include a storage device 340, 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 340 may include an internal storage device, an attached storage device, and/or a network accessible storage device, as non-limiting examples.
The system 300 may include an encoder/decoder module 330 configured, for example, to process data to provide encoded/decoded point cloud geometry data, and the encoder/decoder module 330 may include its own processor and memory. The encoder/decoder module 330 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 encoding and decoding modules. Additionally, encoder/decoder module 330 may be implemented as a separate element of system 300 or may be incorporated within processor 310 as a combination of hardware and software as known to those skilled in the art.
Program code to be loaded onto processor 310 or encoder/decoder module 330 to perform the various aspects described in the present disclosure may be stored in storage device 340 and subsequently loaded onto memory 320 for execution by processor 310. In accordance with various embodiments, one or more of processor 310, memory 320, storage device 340, and encoder/decoder module 330 may store one or more of various items during the performance of the processes described in the present disclosure. Such stored items may include, but are not limited to, a point cloud frame, encoded/decoded geometry/attributes videos/images or portions of the encoded/decoded geometry/attribute 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 310 and/or the encoder/decoder module 330 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 310 or the encoder/decoder module 330) may be used for one or more of these functions. The external memory may be the memory 320 and/or the storage device 340, 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), VVC (Versatile Video Coding), or MPEG-I part 5 or part 9.
The input to the elements of system 300 may be provided through various input devices as indicated in block 390. 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 390 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 300 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 IC or within processor 310 as necessary. Similarly, aspects of USB or HDMI interface processing may be implemented within separate interface ICs or within processor 310 as necessary. The demodulated, error corrected, and demultiplexed stream may be provided to various processing elements, including, for example, processor 310, and encoder/decoder module 330 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 300 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 of block 390, for example, an internal bus as known in the art, including the I2C bus, wiring, and printed circuit boards.
The system 300 may include communication interface 350 that enables communication with other devices via communication channel 700. The communication interface 350 may include, but is not limited to, a transceiver configured to transmit and to receive data over communication channel 700. The communication interface 350 may include, but is not limited to, a modem or network card and the communication channel 700 may be implemented, for example, within a wired and/or a wireless medium.
Data may be streamed to the system 300, in various embodiments, using a Wi-Fi network such as IEEE 802.11. The Wi-Fi signal of these embodiments may be received over the communications channel 700 and the communications interface 350 which are adapted for Wi-Fi communications. The communications channel 700 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 300 using a set-top box that delivers the data over the HDMI connection of the input block 390.
Still other embodiments may provide streamed data to the system 300 using the RF connection of the input block 390.
The streamed data may be used as a way for signaling information used by the system 300. The signaling information may comprise the bitstream B and/or information such a number of points of a point cloud, coordinates and/or sensor setup parameters.
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 300 may provide an output signal to various output devices, including a display 400, speakers 500, and other peripheral devices 600. The other peripheral devices 600 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 300.
In various embodiments, control signals may be communicated between the system 300 and the display 400, speakers 500, or other peripheral devices 600 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 300 via dedicated connections through respective interfaces 360, 370, and 380.
Alternatively, the output devices may be connected to system 300 using the communications channel 700 via the communications interface 350. The display 400 and speakers 500 may be integrated in a single unit with the other components of system 300 in an electronic device such as, for example, a television.
In various embodiments, the display interface 360 may include a display driver, such as, for example, a timing controller (T Con) chip.
The display 400 and speaker 500 may alternatively be separate from one or more of the other components, for example, if the RF portion of input of block 390 is part of a separate set-top box. In various embodiments in which the display 400 and speakers 500 may be external components, the output signal may be provided via dedicated output connections, including, for example, HDMI ports, USB ports, or COMP outputs.
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/or 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 (HMID, 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 310 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 320 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 310 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 “/”, “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 disclosure. 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 a decoder. In various embodiments, such processes also, or alternatively, include processes performed by a decoder of various implementations described in this application, for example,
As further examples, in one embodiment “decoding” may refer only to de-quantizing, in one embodiment “decoding” may refer to entropy decoding, in another embodiment “decoding” may refer only to differential decoding, and in another embodiment “decoding” may refer to combinations of de-quantizing, 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 encoder. In various embodiments, such processes also, or alternatively, include processes performed by an encoder of various implementations described in this application.
As further examples, in one embodiment “encoding” may refer only to quantizing, 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 combinations of quantizing, 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.
Additionally, this application may refer to “obtaining” various pieces of information. Obtaining 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 a particular information such a number of points of the point cloud or coordinates or sensor setup parameters. 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.
Number | Date | Country | Kind |
---|---|---|---|
21306181.5 | Aug 2021 | EP | regional |
This application is a National Stage of International Application No. PCT/CN2022/099613, filed on Jun. 17, 2022, which claims priority to European Patent Application No. 21306181.5 filed on Aug. 31, 2021, the entire content of which is hereby incorporated by reference for all purposes.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/CN2022/099613 | 6/17/2022 | WO |