Patent Grant
11825116
Virtual reality (VR) started to go into our daily lives. For example, VR has many applications in areas including, but not limited to, healthcare, education, social networking, industry design/training, game, movie, shopping, and/or entertainment VR may bring an immersive viewing experience by creating a virtual environment surrounding a viewer. VR may generate a true sense of “being there” for the viewer. User's experience may rely on, for example, providing a full real feeling in the VR environment. For example, the VR system may support interactions through posture, gesture, eye gaze, and/or voice. The VR system may provide haptic feedback to the user to allow the user to interact with objects in the VR world in a natural way. VR systems may use 360-degree video to provide the users, for example, the capability to view the scene from 360-degree angles in the horizontal direction and/or 180-degree angles in the vertical direction. The VR system and/or 360-degree video may be mega consumption beyond, for example, Ultra High Definition (UHD) service.
A video coding system may perform face-based sub-block motion compensation for 360-degree video to predict one or more samples of a sub-block. The video coding system may include an encoder and/or a decoder. The video coding system may receive a 360-degree video content. The 360-degree video content may Include multiple faces. For example, the 360-degree video content may include multiple faces arranged in a frame-packed picture. The 360-degree video content may include a current block. The current block may include one or more sub-blocks. For examples, the current block may be divided into one or more sub-blocks. Sub-block level face association may be performed to the 360-degree video content. For example, when a sub-block mode is used for the current block, sub-block level face association may be performed based on the location(s) of the sub-block(s) in the frame-packed picture associated with the 360-degree video content.
In examples, the sub-block mode may include at least one of an advanced temporal motion vector prediction (ATMVP) mode, a spatial-temporal motion vector prediction (STMVP) mode, frame-rate up conversion (FRUC) mode, or an affine mode.
The video coding system may determine whether the current block includes samples located on multiple faces associated with the 360-degree video content. The system may predict one or more samples in the current block. For example, the system may predict one or more samples in the current block based on sub-block level face association. The system may perform geometry padding on the multiple faces. The faces may include a padded region associated with the face. For example, the first face may include a padded region associated with the first face.
In examples, for a first sub-block in the current block, the system may identify a first location of the first sub-block. The system may associate the first sub-block with a first face. For example, the system may associate the first sub-block with the first face based on the identified first location of the first sub-block. The system may predict a first sample in the first sub-block. For example, the system may predict the first sample in the first sub-block based on the first face that is associated with the first sub-block.
The system may predict the first sample associated with the first sub-block by identifying a reference sample associated with the first face. For example, the system may identify a reference sample associated with the first face using a motion vector. The system may predict the first sample in the first sub-block based on the identified reference sample. For example, the system may predict the first sample in the first sub-block using the identified reference sample. The identified reference samples may be associated with the first face or a padded region of the first face. For example, the identified reference samples may be located within the first face or a padded region of the first face.
In examples, for a second sub-block in the current block, the system may identify a second location of the second sub-block. The system may associate the second sub-block with a second face. For example, the system may associate the second sub-block with the second face based on the identified second location of the second sub-block. The system may predict a second sample in the second sub-block. For example, the system may predict the second sample in the second sub-block based on the second face that is associated with the second sub-block. The second face described herein may differ from the first face.
If the first sub-block is associated with the first face and a second sub-block is associated with a second face and the first face differs from the second face, the system may predict the first sample using a first reference sample that is/modeled with the first face and may predict the second sample using a second reference sample that is associated with the second face.
A detailed description of illustrative embodiments will now be described with reference to the various figures. Although this description provides a detailed example of possible implementations, it should be noted that the details are intended to be exemplary and in no way omit the scope of the application.
Improving the quality of 360-degree video in VR and/or standardizing the processing chain for chairs interoperability may have been focused by one or more groups. For example, an ad hoc group, belonging to MPEG-A (multimedia application format) Part-19, was set up in ISO/IEC/MPEG to work on the requirements and/or technologies for omnidirectional media application format. For example, an ad hoc group, free view TV (FTV), performed exploration experiments for 360-degree 313 video application. FTV tested for 360-degree video (e.g., omnidirectional video) based system and/or multi-view based system. For example, the joint video exploration team (JVET) from MPEG and ITU-T tested sequences including VR for video coding standard. The Joint Exploration Model (JEM), which is designed to enhance the coding efficiency of 2D video beyond the High Efficiency Video Coding (HEVC), may be used for the exploration work of 360-degree video coding. A preliminary Cali for Evidence (CE) is planned to be issued on video compression technologies, where VR and/or 360-degree video may be included as a category of a video source content.
Quality and/or users experience of one or more aspects in the VR processing chain, including capturing, processing, display, and/or applications may be improved. For example, on the capturing side, VR system may use one or more cameras to capture a scene from one or more different views (e.g., 6-12 views). The different views may be stitched together to form 360-degree video in high resolution (e.g., 4K or 8K), For example, on the client or user side, the VR system may include a computation platform, a head mounted display (HMD), and/or a head tracking sensor. The computation platform may receive and/or decode the 360-degree video and may generate a viewport for display. Two pictures, one for each eye, may be rendered for the viewport. The two pictures may be displayed in the HMD for stereo viewing. Lens may be used to magnify the image displayed in the HMD, e.g., for better viewing. The head tracking sensor may keep (e.g., constantly keep) track of the viewers head orientation. The head tracking sensor may feed the orientation information to the system to display the viewport picture for that orientation. A VR system may provide a touch device (e.g., specialized touch device) for the viewer, e.g., to interact with objects in the virtual world. In examples, a VR system may be driven by a workstation with GPU support. In examples, a VR system may use a smartphone as a computation platform, a HMD display, and/or a head tracking sensor. The spatial HMD resolution may be 2160×1200. Refresh rate may be 90 Hz, and the field of view (FOV) may be 110 degree. The sampling rate for head tracking sensor may be 1000 Hz, which may capture fast (e.g., very fast) movement. An example of VR system may use a smartphone as a computation platform and may include of lens and/or cardboard. 360-degree video streaming service may exist.
360-degree video delivery may represent the 360-degree information using a sphere geometry structure. For example, the synchronized one or more views captured by the one or more cameras may be stitched on a sphere as an integral structure. The sphere information may be projected to 2D planar surface with a geometry conversion process. For example, an equirectangular projection (ERP) and/or a cubemap projection (CMP) may be used to illustrate the projection format.
ERP may map the latitude and/or longitude coordinates of a spherical globe onto (e.g., directly onto) horizontal and/or vertical coordinates of a grid.
ue=(φ/2*π)+0.5)*W (1)
ve=(0.5−θ/π)*H (2)
where W and H may be the width and height of the 2D planar picture. As shown in
As shown in
The CMP may be compression friendly format.
Video codec(s) may be designed considering 2D video captured on a plane. When motion compensated prediction uses samples outside of a reference picture's boundaries, padding may be performed by copying the sample values from the picture boundaries. For example, repetitive padding may be performed by copying the sample values from the picture boundaries.
Geometry padding for ERP may be defined on the sphere with longitude and/or latitude. For example, given a point (u, v) to be padded (e.g., outside of the ERP picture), the point (u′, v′) used to derive the padding sample may be calculated using one or more Equations 3-5.
If (u<0 or u≥W) and (0≤v<H),u′=u%W,v′=v (3)
if (v<0),v′=−v−1,u′=(u+W/2)%W; (4)
if (v≥H),v′=2*H−1−v,u′=(u+W/2)%W (5)
where W and H may be the width and height of the ERP picture.
When the projection format is CMP, faces of CMP may be extended by the geometry padding through projecting the samples of the neighboring faces onto the extended area of the current face.
After spatial and/or temporal prediction, a mode decision 680 in the encoder may select a prediction mode, for example based on a rate-distortion optimization. The prediction block may be subtracted from the current video block at 616. Prediction residuals may be de-correlated using a transform module 604 and a quantization module 606 to achieve a target bit-rate. The quantized residual coefficients may be inverse quantized at 610 and inverse transformed at 612 to form reconstructed residuals. The reconstructed residuals may be added back to the prediction block at 626 to form a reconstructed video block. An in-loop filter such as a de-blocking filter and/or an adaptive loop filter may be applied to the reconstructed video block at 666 before it is put in the reference picture store 664. Reference pictures in the reference picture store 664 may be used to code future video blocks. An output video bit-stream 620 may be formed. Coding mode (e.g., inter or infra coding mode), prediction mode information, motion information, and/or quantized residual coefficients may be sent to an entropy coding unit 608 to be compressed and packed to form the bit-stream 620.
A video block may have a motion vector (e.g., at most a motion vector) for a prediction direction. Sub-block level motion vector predictions may be applied, A block (e.g., large block) may be split into multiple sub-blocks (e.g., multiple small sub-blocks). Motion information for one or more (e.g., all) the sub-blocks may be derived. Advanced Moral motion vector prediction (ATMVP) may build upon the temporal motion vector prediction (TMVP). ATMVP may allow a coding block to fetch the motion information of its sub-blocks from multiple small blocks from its temporal neighboring picture (e.g., collocated reference picture). Spatial-temporal motion vector prediction (STMVP) may derive (e.g., recursively derive) the motion information of the sub-blocks, e.g., by averaging the motion vectors of temporal neighbors with that of the spatial neighbors.
In ATMVP, the TMVP may allow a block to derive multiple motion information (e.g., inducting motion vector and/or reference indices) for the sub-blocks in the block from one or more (e.g., multiple) smaller blocks of the temporal neighboring pictures of the current picture. The ATMVP may derive the motion information of sub-blocks of a block as described herein. The ATMVP may identify the corresponding block of the current block (e.g., which may be called collocated block) in a temporal reference picture. The selected temporal reference picture may be called the collocated picture. The ATMVP may split the current block into one or more sub-blocks and may derive the motion information of the sub-blocks (e.g., each of the sub-blocks) from the corresponding small blocks in the collocated picture, as shown in
The collocated block and/or the collocated picture may be identified by the motion information of the spatial neighboring blocks of the current block. In ATMVP design, the available (e.g., first available) candidate in the merge candidate list may be considered.
For sub-blocks in the current blocs, the motion information of the corresponding small block (e.g., as indicated by arrows in
In STMVP, the motion information of the sub-blocks in a coding block may be derived in, for example a recursive manner.
The overlapped block motion compensation (OBMC) may be used to remove the blocking artifact at motion compensation stage. The OBMC may be performed for one or more (e.g., all) inter block boundaries except for example, the right and/or bottom boundaries of a block. When a video block is coded in a sub-block mode (e.g., ATMVP and/or STMVP), the OBMC may be performed for sub-block's boundaries.
Weighted average may be used in OBMC to generate the prediction signal of a block. The prediction signal using the motion vector of a neighboring sub-block may be denoted as PN. The prediction signal using the motion vector of the current sub-block may be denoted as PC. When the OBMC is applied, the samples in the first and/or last four rows and/or columns of PN may be weighted averaged with the samples at the same positions in PC. The samples to which the weighted averaging is applied may be determined according to, for example, the location of the corresponding neighboring sub-block. For example, when the neighboring sub-block is above neighbor (e.g., sub-block ‘b’ in
In HEVC, one or more (e.g., all) inter prediction parameters (e.g., motion vectors, reference index, and/or weighted prediction parameters) may be determined at an encoder by rate-distortion (R-D) optimization and may be signaled to a decoder. Coding inter prediction parameters may account for an overhead (e.g., significant overhead). Signaling overhead may be avoided, for example, by using template-based costing in JEM. The template-based coding may derive the inter prediction parameters at decoder using the templates that may be already reconstructed neighboring samples of the current block. Local illumination compensation (IC) may derive local weighting parameters based on, for example, a linear model using the template and/or may apply weighted motion compensated prediction using, for example, the derived weighting parameters. Frame-rate up conversion (FRUC) may derive motion information at decoder using template matching or bilateral matching.
IC may be based on a linear motet for illumination changes, using a scaling factor ‘a’ and/or an offset. The tool may be enabled and/or disabled adaptively for one or more inter coded blocks.
P(x,y)=a·Pr(x+vx,y+vy)+b
where P(x, y) may be the prediction signal of the current block at the coordinate (x, y), and Pr(x+vx, y+vy) may be the reference block pointed by the motion vector (vx, vy).
FRUC mode may be supported for inter coded blocks (e.g., to save the overhead of signaling motion information). When FRUC mode is enabled, motion information (e.g., including motion vectors and/or reference indices) of the block may not be signaled. The motion information may be derived at a decoder side by, for example, template-matching or bilateral-matching. During the motion derivation process at the decoder, the merge candidate list of the block and/or a set of preliminary motion vectors generated using ATMVP-like prediction for the block may be checked (e.g., firstly checked). The candidate which may lead to the minimum sum of absolute difference (SAD) may be selected as a starting point A local search based on template-matching or bilateral-matching around the starting point may be performed and/or the motion vector (MV) that results in the minimum SAD may be taken as the MV for the whole block. The motion information may be refined (e.g., further refined), e.g., at sub-block level.
Quad-tree plus binary-tree (QTBT) bock partitioning structure may be applied. In the QTBT structure, a coding tree unit (CTU), which is a root node of quad-tree, may be partitioned (e.g., firstly partitioned) in the quad-tree manner, where the quad-tree splitting of a node may be iterated until the node reaches the minimum of the allowed quad-tree size (MinQTSize). If the quad-tree node size is no larger than the maximum of the allowed binary tree size (MaxBTSize), the quad-tree node may be partitioned (e.g., further partitioned) using binary tree in horizontal or vertical direction. The splitting of the binary tree may be iterated until the binary tree node reaches the minimum of the allowed binary tree node size (MinBTSize) or the maximum of the allowed binary tree depth. The binary tree node may be used as the basic unit of prediction and/or transform without further partitioning (e.g., the concepts of prediction unit (PU) and/or transform unit (TU) in HEVC test model (HM) may not exist). An example of QTBT partitioning structure may be described herein. The CTU size may be 128×128, MinQTSize may be 16×16, MaxBTSize may be 64×64, and MinBTSize may be 4. The quad-tree partitioning may be applied (e.g., firstly applied) to the CTU to generate quad-tree leaf nodes. The quad-tree leaf node size may range from, for example 128×128 to 16×16. If the quad-tree node is 128×128, the quad-tree node may not be split by the binary tree as quad-tree node exceeds the maximum binary tree size (e.g., MaxBTSize may be 64×64). If the quad-tree node is not 128×128, the quad-tree node may be partitioned (e.g., further partitioned) by the binary tree. The quad-tree node may be the root node of the binary tree. The binary tree depth may be equal to 0. The binary tree partitioning may be iterated until the binary tree depth reaches MaxBTDepth or the binary tree node has width or height equal to MinBTSize.
Video codec(s) may consider (e.g., only consider) 2D video signals that may be captured on the same plane. When considering 360-degree video (e.g., which may include of one or more projection faces), continuity between faces may be broken because one or more faces are generated based on, for example a different projection plane. The discontinuity between faces may be increased for various frame-packing. For motion compensated prediction of 360-degree video coding, geometry padding may be applied. Geometry padding may provide a temporal reference for picture areas that may be outside face boundaries, Motion compensated prediction for 360-degree video using geometry padding may be performed.
Template-based coding (e.g., IC and/or FRUC) may be used to derive inter prediction parameters (e.g., weight and/or offset for IC, and/or motion information for FRUC) using the reconstructed samples from the neighboring region. When geometry padding Is applied (e.g., applied jointly) with template-based coding, complication may arise. In geometry padding, the faces in the reference pictures may be padded, and the faces in the current picture that is being coded may not be padded. When template-based coding is used, if the current block is located at face boundary, the template used by IC and/or FRUC may be outside of the current face. If geometry padding is used as an example, the template of the current block may be from a neighboring face or from outside of the current picture. The reference of the template in the reference picture may be in the padded region of the current face in the reference picture. The template and the reference of the template may be mismatched (e.g., poorly matched) with each other.
The motion information of spatial and/or temporal neighboring blocks may use one or more inter coding tools to predict the motion information of the current block (e.g., advanced motion vector prediction (AMVP), TMVP, merge mode, ATMVP and/or STMVP) or to generate the prediction signal of the current block (e.g., OBMC). If the current block is located on face boundaries, the current block's spatial and/or temporal neighbors may be fetched from the other faces. A motion vector defined within a face may be used to predict the motion vector or generate the prediction signal of a block that is defined in another face. One or more faces of a 360-degree video may be rotated, flipped, and/or disordered during frame-packing process. The motion vectors from different faces may not have strong correlation.
When the geometry padding is enabled, the reference samples of the current block may be from (e.g., always from) the padded region of the current face. The geometry padding may ensure that a reference block, which may be correlated (e.g., highly correlated) with the current block, may be identified in the padded region to predict the current block because of the intrinsic symmetry characteristic of 360-degree video. When the QTBT partitioning structure is applied (e.g., directly applied) to 360-degree video coding, a quad-hiss/binary-tree (QT/BT) leaf node in the current picture may span one or more faces and may include the samples from one or more faces (e.g., the face boundaries may lie inside the QT/BT leaf node). Neighboring faces (e.g., two neighboring faces) in a frame-packed picture may no longer be contiguous in the 3D space. The samples around the neighboring faces (e.g., two neighboring faces) boundaries may show different characteristics (e.g., belonging to different objects). The padded region of the current face in the reference pictures may not be able to provide a reference block having a strong correlation with the current block.
Motion compensated prediction for 360-degree video based on geometry padding may be performed. The reference sample derivation process for template-based coding may fetch the template samples. For example, the reference sample derivation process for template-based coding may fetch the template serrates from the above and/or the left neighbors. The template samples (e.g., from the above and/or left neighbors) may be from different faces and/or may include discontinuous information. An example of different process for template-based coding may consider the 3D geometry when deriving the template samples that may be beyond the region of the current face.
Geometry-based reference block derivation and/or geometry-based motion vector projection may be used for motion prediction for 360-degree video coding. The geometric characteristics of 360-degree video may be considered.
QTBT block partitioning may partition the blocks at the face boundaries of a frame-packed 360-degree video with the consideration of the impact of the geometry padding (e.g., disabling crossing-face QT/BT leaf node).
If a video block is located on face boundaries and is coded using template-based coding (e.g., IC and/or FRUC), one or more template samples of the video block may be obtained from above and/or left neighbors that are from another face, while the reference samples of the template may be obtained from the padded region of the current face in temporal picture (e.g.,
The template samples may be fetched based on the 3D geometry of 360-degree video. For example, if the current block of the current picture is on the face boundary, the template samples may be located outside the boundaries of the current face. If the current block of the current picture is on the face boundary, 3D geometry information may be applied when deriving the template samples of the current block. Using the 3D geometry information to derive the template samples of the current block may provide template samples that may be correlated (e.g., more correlated) with the current block. Using the CMP as example,
The template reference samples of the current block may be derived, e.g., from the geometric neighbors based on 3D geometry information. Using geometry information (e.g., 3D geometry information) may maximize the correlation between the samples of the template and the current block. When using geometry information, the decoder may maintain (e.g., temporarily maintain) the samples of previously reconstructed faces. To reduce the line buffer size, template samples may be disabled (e.g., may be regarded as unavailable) if the template samples are outside the boundaries of the current face. For example, when the current block is on a face boundary, template-based coding tools may be disabled. Disabling template-based coding tools may reduce line buffer size with limited performance impact, as the number of blocks on face boundaries may be small. As shown in
An encoder and/or a decoder may determine the location and/or orientation of template pixels for a template-based coding.
For a current block located in a first face of a multi-face projection format, whether a template of the current block resides in the first face may be determined. If the template of the current block does not reside in the first face, the location and/or orientation of the template of the current block may be determined. For example, a geometric relationship between the faces of the multi-face projection format may be used to identify a second face. The second face may differ from the first face and the template of the current block may reside in the second face. A face-packing relationship may be used to identify the location and/or orientation of the template of the current block in the second face within the multi-face projection format. The template for prediction of the current block may be used according to the template-based coding.
The template based coding may be IC, FRUC, or other prediction which may be associated with one or more templates of coded (e.g., already encoded and/or decoded) pixels which may adjoin the location of a current block in the current frame or in a coded (e.g., already encoded and/or decoded) reference frame. The template may be a “top” template located above the current block, a ‘left’ template located to the left of the current block, a “bottom” template located below the current block, a “right” template located to the right of the current block, or other template defined to adjoin the current block at a relative location. The multi-face projection format may be a cubemap format, an octahedral format, an icosahedral format, or other multi-face projection format where the faces may be packed into a 2D frame for compression. The geometric relationship may define the relationship between faces in a 3D geometry, as illustrated in
When geometry padding is used for coding 360-degree video, if a block refers to a sample that is outside the region of the current face, the reference sample value may be generated. For example, the reference sample value may be generated by projecting the corresponding sample of the neighboring face into the current face using, for example 3D geometry. The motion vector of one or more blocks in a face may not refer to a reference sample that may exceed the padded region of the face in the reference picture. Motion information of spatial and/or temporal neighboring blocks may be used to predict the motion information or to generate the motion compensated signal of the current block. If the position of the current block is located on one or more face boundaries, the current block's spatial and/or temporal neighbor may be from a neighboring face. If the current face and its neighboring face are not contiguous in 3D space, the motion of the current block and its spatial and/or temporal neighbors may not have correlation (e.g., obvious correlation). Motion vector may be predicted based on 3D geometry.
3D geometry may be applied to derive the motion vector of a reference block. For example, the motion vector of a reference block may be derived base on 3D geometry when its position is outside of the face to which the current block belongs. Motion vector prediction based on 3D geometry may provide an efficient motion vector predictor for the blocks that may be located on face boundaries.
For example, in
An encoder and/or a decoder may determine the location and/or the orientation of a motion vector candidate for use in a motion vector prediction. For a current block, whether the block providing the motion vector candidate resides in the same face as the current block may be determined. If the block providing the motion vector candidate does not reside in the same face as the current block, the location and/or the orientation of the block providing the motion vector candidate may be determined, e.g., based on a geometric relationship. The geometric relationship between the faces of a multi-face projection format may be used to identify a face (e.g., different than the face that includes the current block) in which the block providing the motion vector candidate resides. A face-packing relationship may be used to identify the location and/or the orientation of the block providing the motion vector candidate in the identified face in the multi-face projection format. The motion vector candidate may be retrieved based on the identified location and/or the orientation of the block. The retrieved motion vector candidate may predict the motion of the current block according to the motion vector prediction.
Whether a block providing the motion vector candidate resides in the sane face as the current block may be determined. For example, determining whether the block providing the motion vector candidate resides in the same f7ace as the current face may be determined using a position of the block providing the motion vector candidate relative to the position of the current block. Examples of such relative positions (e.g., AL, A, AR, L, and/or BL) may be illustrated in
An encoder and/or a decoder may determine whether a motion vector candidate is available for use in a motion vector prediction. For a current block, whether the block providing the motion vector candidate resides in the same face as the current block may be determined. If the block providing the motion vector candidate does not reside in the same face as the current block, a geometric relationship between the faces of the multi-face projection format may be used to identify a face (e.g., different than the face that includes the current face) in which the block providing the motion vector candidate resides. A face-packing relationship may be used to determine whether the block providing the motion vector candidate is in its proper neighboring position relative to the current block within the multi-face projection format Whether the block providing the motion vector candidate is not in its proper neighboring position relative to the current block, due to a discontinuity at the border between the same face as the current block and the identified face, may be determined. If the block proving the motion vector candidate is determined to be in its proper neighboring position relative to the current block, the motion vector candidate may be marked as available for prediction. If the motion vector candidate is available for prediction, the motion vector candidate may predict the motion of the current block, e.g., according to the motion vector prediction. If the block providing the motion vector candidate is not in its proper neighboring position relative to the current block, the motion vector candidate may be marked as unavailable for prediction.
An encoder and/or a decoder may determine whether a motion vector candidate is available for use in a motion vector prediction. For a current block, whether the block providing the motion vector candidate resides in the same face as the current block may be determined. If the block providing the motion vector candidate resides in the same face as the current block, the motion vector candidate may be marked as available for prediction. If the motion vector candidate is available for prediction, the motion vector candidate may predict the motion of the current block based on the motion vector prediction described herein. If the block providing the motion vector candidate does not reside in the same face as the current block, the motion vector candidate may be marked as unavailable for prediction.
When 360-degree video is projected onto multiple faces (e.g., using CMP), one or more face pictures may look similar to a 2D picture. Rectilinear projection may cause shape distortions (e.g., for objects close to face boundaries). A continuous structure in the 3D space may not be continuous when the continuous structure crosses face boundaries on the frame-packed 2D picture. For example, a straight line crossing two neighboring faces may become two line segments in different directions at the boundary of the two neighboring faces. The motion across the face boundary may become discontinuous. For example, a moving object may change its motion direction after crossing the face boundary. In the geometry-based motion vector prediction described herein, the motion vector of a reference block derived based on, for example, 3D geometry (e.g., the reference block may be rotated if necessary) may be used as the motion vector predictor to predict the motion vector of the current block. When crossing face boundary, motion direction may change. Predicting the motion vectors of the blocks on face boundaries using the motion vectors from neighboring faces may be difficult. An example of a motion vector projection may be applied for motion vector prediction of 360-degree video. If the current block and its reference block are from different faces, using geometry information in the motion vector domain may project the motion vector of the reference block onto the face where the current block belongs before motion vector prediction may be applied. The motion vector projection described herein may be similar to geometry padding and may be based on the rectilinear projection between a 3D point and the corresponding point on a 2D projection plane.
Based on the CMP format
The geometry-based reference block derivation described herein and/or the geometry-based motion vector projection described herein may be operated (e.g., operated together or independently) from each other. The geometry-based reference block derivation may be combined with, for example, the geometry-based motion vector projection for motion vector prediction of 360-degree video. One or more motion vector candidates of the current block may be derived. For example, the motion vector of the corresponding geometric neighboring block may be fetched according to geometry-based reference block derivation described herein. The motion vector may be projected using the geometry-based motion vector projection described herein. The projected motion vector may be used as the motion vector predictor of the current block. The geometry-based reference block derivation may be used for motion vector prediction of 360-degree video. For example, the geometry-based reference block derivation may be used for motion vector prediction of 360-degree video disabling geometry-based motion vector projection. The motion vector of the geometrical neighboring block may be used as candidate for motion vector prediction. The reference block derivation (e.g., relying on the spatial and/or temporal neighbors) may be combined with the geometry-based motion vector projection for predicting motion vectors of 360-degree video. Motion candidates may be fetched from the spatial and/or temporal neighboring blocks of the current block and may be adjusted according to the motion vector projection scheme (e.g., if the reference block is from a different face) before being used for predicting the motion vector of the current block.
CMP format and/or merge mode may be used to discuss the geometry-based reference block derivation and/or geometry-based motion vector projection described herein. The geometry-based reference block derivation and/or geometry-based motion vector projection may be applicable to other 360-degree video projection formats and/or inter coding tools. Without loss of generality,
A video encoder and/or a video decoder may determine a motion vector prediction candidate for a current block in a same face as the current block. The location of the block, which provides the motion vector candidate (e.g., relative to the location of the current block), may be determined. The location of the block, which provides the motion vector candidate, may be determined based on whether the location of the block is within the same face as the current block. If the location of the block is not in the sane face as the current block, the motion vector candidate may be determined as described herein. A geometric relationship may be used between the faces of the multi-face projection format to identify a face (e.g., different from the face that includes the current block) in which the block which provides the motion vector candidate resides. The block that provides the motion vector candidate in the identified face may be identified. A representation of the motion vector in the identified face may be determined. The representation of the motion vector may be projected from the identified face to the plane of the same face as the current block. The projected motion vector may be used as a motion vector prediction candidate for the current block.
The multi-face projection format may be a cubemap format, an octahedral format, an icosahedral format, or other multi-face projection format where the faces may be packed into a 2D frame for compression. The geometric relationship may define the relationship between faces in a 3D geometry, as illustrated in
When a QT/BT node is across the boundary between two faces, the corresponding QT/BT splitting indication (e.g., flag) may be skipped. The value (e.g., 1) may be inferred (e.g., to be further split). When a QT/BT node is inside a face, the QT/BT signaling may be applied. For example, the QT/BT signaling may signal an indication (e.g., flag) to indicate whether the current node may be further split or not. The indication (e.g., splitting flag) set to a value (e.g., 1) for the QT/BT nodes across face boundaries may infer that face boundaries may aligned with the boundaries of QT/BT leaf nodes. QT/BT leaf node may include samples from a face after, for example, the QTBT partitioning described herein may be applied.
A parameter, MaxBTDepth (e.g., in the QTBT design), may specify the maximum depth of allowed binary-tree partitioning. A QT/BT node may be split (e.g., split horizontal), or vertically) when the depth of the current binary-tree does not reach MaxBTDepth. A QT/BT node that is across multiple faces may not be able to provide enough partition granularities to support the separation of the face boundaries using ST partitions. Quad-tree (QT) partitions (e.g., only QT partitions and not both QT and binary-tree (BT) partitions) may be used to align with face boundaries. For example, CTU may be partitioned (e.g., firstly partitioned) in the QT manner, and QT node may be enforced to be split if the QT node covers one or more face boundaries. The QT splitting may be iterated until one or more of the corresponding descendent QT nodes may be contained (e.g., completely contained) in a face. QT node may be partitioned (e.g., further partitioned) by the BT. One or more (e.g., all) enforced BT splitting that are used to align with face boundaries may be counted towards the total depth of the corresponding BT structure. When a QT/BT node spans into one or more faces, the corresponding BT indication (e.g., splitting flag) may be inferred to further split (e.g., flag set to 1) without being signaled. If the indication (e.g., flag) is not signaled, the corresponding BT splitting (e.g., which may be used to align with face boundaries) may not be considered when calculating the total depth of the current BT structure. BTs may be split (e.g., further split) to align with face boundaries without being subject to the constraint of MaxBTDepth.
In the constrained QTBT partition described herein, a QT/BT leaf node may be used as the basic unit to align with face boundaries. The size of one or more faces may be one or more of the size of the basic unit to ensure enough block-partitioning granularity. For example, for approach of skipping signaling QT/BT splitting indication (e.g., flag) when a QT/BT node is across the boundary between two faces as described herein, the face size may be multiple of minimum BT size (e.g., MinBTSize). For approach of using QT partitions to align with face boundaries described herein, the face size may be multiple of minimum QT size (e.g., MinQTSize). The constrained QTBT partitioning described herein may be applied to inter coded pictures where geometry padding is applied. The constrained QTBT partitioning described herein may be applied to inter coded pictures (e.g., B and/or P pictures) and may be disabled for infra coded pictures (e.g., I pictures). The constrained QTBT partitioning may be applied to the video blocks of the 360-degree (e.g., entire 360-degree) video sequence. Within the 360-degree (e.g., entire 360-degree) video block, homogeneous area may exist across faces boundaries (e.g., sky, ground, and/or water). Homogeneous area (e.g., which may be across face boundaries) may be put into a coding block (e.g., large coding block) aid may save signaling overhead of coding mode, motion related information, and/or residual. An indication (e.g., a flag) may be used to be signaled at a high-level (e.g., video parameter set (VPS), sequence parameter set (SPS), picture parameter set (PPS), and/or the slice header) for enabling and/or disabling the QTBT partitioning. Region-based enabling and/or disabling may be applicable to the constrained QTBT partitioning described herein. The constrained QTBT partitioning may be applied to face boundary areas that show heterogeneous characteristics while disabled for homogeneous face boundaries. For example, if the frame packed picture includes 6 faces in total, a bit may be signaled for one or more faces to indicate whether the constrained QTBT partitioning approach is applied to that face or not. The constrained QTBT partitioning structure described herein may be applicable to other block partitioning frameworks including, but not limited to, the quad-tree based partitioning in HM, asymmetric block partitioning, and/or multi-type-tree partitioning.
The QTBT partition constants may be used to ensure that the current block includes sample(s) in a face (e.g., a single face). For example, mismatched reference block due to geometry padding may be avoided. One or more sub-block level motion compensation techniques (e.g., ATMVP and/or STMVP) may be supported. The one or more sub-block level motion compensation techniques may allow a large block to split into one or more small sub-blocks and/or may derive own motion information for one or more sub-blocks. The large block may be a current block that is associated with 360-degree video. The face-based sub-block motion compensation described herein may increase the usage of large coding blocks (e.g., QT/BT leaf node) in a QTBT block partition structure. When a video block is across the boundaries of one or more faces (e.g., which may not be contiguous in 3D space), the approach of using coding blocks (e.g., large axing blocks) in a QTBT block partition structure may be used for 360-degree video coding since the sub-blocks (e.g., which may represent different objects from various faces) inside the current block may be predicted using different motion information. When geometry padding is applied (e.g., jointly applied) with sub-block level motion compensation techniques, different approaches) may be applied to derive the reference samples for one or more sub-blocks at the motion compensation stage. For execrate, the reference samples of one or more (e.g., all) the sub-blocks in the current block may be derived from the padded region of a face (e.g., a single face). For example, as shown in
A face-based sub-block motion compensation may be used when geometry padding is applied for oozing 360-degree video. Fine-granularity motion of sub-block mode on coding video blocks on face boundaries may be utilized, and the QTBT block partition may be applied without a constraint in using QT partitions to align with face boundaries as described herein. A QTBT leaf node may be allowed to occupy the regions of one or more faces. The face-based sub-block motion compensation may predict the samples of one or more sub-blocks using the motion compensated prediction signal from the padded region of the corresponding face that sub-block belongs to.
The sub-block motion compensation described herein may be applied to one or more sub-block level motion compensation mode. The sub-block level motion compensation mode may include, but not limited to, ATMVP mode, STMVP mode, FRUC mode, and/or affine mode. When the sub-block motion compensation is enabled, video blocks at face boundaries may be coded by the sub-block level motion compensation mode(s). If A video block is found to be across one or more face boundaries, the video block may be coded by the coding mode(s). The coding mode(s) may be used to derive motion information at a sub-block level.
For example, if a sub-block mode is used for the current block and if the current block includes samples located on multiple faces associated with 360-degree video content one or more samples in the current block may be predicted based on sub-block level face association. For a sub-block in the current block (e.g., a first sub-block and/or a second sub-block), a location of the sub-block may be identified. Tire sub-block may be associated with a face based on the identified location of the sub-block. A sample in the sub-block may be predicted based on the face that is associated with the sub-block.
Signaling of an indication (e.g., flag) to indicate coding mode may be skipped. For example, the coding modes (e.g. which may associate a single motion vector for a direction for the whole block) may not be examined during the rate distortion process at the encoder. One or more (e.g., all) allowed coding modes (e.g., with sub-block level motion or without sub-block level motion) may be allowed to code video blocks at face boundaries. Signaling a syntax (e.g., additional signaling syntax) may be applied to indicate which coding mode is selected.
As shown in
The communications systems 100 may also include a base station 114a and/or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106/115, the Internet 110, and/or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
The base station 114a may be part of the RAN 104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred b as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fared or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions.
The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible tight etc.). The air interface 116 may be established using any suitable radio access technology (RAT).
More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104/113 and the WTRUs 102a, 102b, 102c may Implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115/116/117 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as ugh-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed UL Packet Access (HSUPA).
In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).
In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).
In an embodiment the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., a eNB and a gNB).
In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (MAX)), CDMA2000, CDMA2000 1×, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
The base station 114b in
The RAN 104/113 may be in communication with the CN 106/115, which may be any type of network configured to provide voice, data, applications, and/or voice over Internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the tike. The CN 106/115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in
The CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the Internet protocol (IP) in the TCP/IP internet protocol suite. The networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/113 or a different RAT.
Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may Include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in
The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller. Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While
The transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In an embodiment, the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
Although the transmit/receive element 122 is depicted in
The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.
The processor 118 of the WTRU 102 may be coupled to, and may receive user Input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
The processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.
The processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Realty and/or Augmented Reality (VR/AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor, a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choice) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, and the like. As shown in
The CN 106 shown in
The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.
The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface. The SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102c, 102c. The SGW 164 may perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
Although the WTRU is described in
In representative embodiments, the other network 112 may be a WLAN.
A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11z tunneled PIS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., alt of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an ‘ad-hoc’ mode of communication.
When using the 802.11ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AR In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in ln 802.11 systems. For CSMA/CA, the STAs (e.g., every STA), Including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.
High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
Very High Throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).
Sub 1 GHz modes of operation are supported by 802.11af and 802.11ah. The channel operating bandwidths, and carriers, are reduced in 802.11d and 802.11ah relative to those used in 802.11n, and 802.11 ac. 802.11af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the iv White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz. and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support Meter Type Control/Machine-Type Communications, such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
MAN systems, which may support multiple channels, and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the as support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes. Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.
In the United States, the available frequency bands, which may be used by 802.11ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11ah is 6 MHz to 26 MHz depending on the country code.
The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs white remelting consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to, and or receive wireless signals from, the WTRU 102a In an embodiment, the gNBs 180a, 180b, 180c may implement cater aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component earners may be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and/or lasting varying lengths of absolute time).
The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a. 102b, 102c in a standalone configuration and/or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160z). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.
Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in
The CN 115 shown in
The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handing of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mottle broadband (eMBB) access, services for machine type communication (MTC) access, and/or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.
The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.
The CN 115 may facilitate communications with other networks. For example, the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
In view of
The emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or an, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications.
The one or more emulation devices may perform the one or more, including al, functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.
This application is a Continuation Application of U.S. patent application Ser. No. 16/494,835, filed Sep. 17, 2019, which is the National Stage Entry under 35 U.S.C. § 371 of Patent Cooperation Treaty Application No. PCT/US2018/022658, filed Mar. 15, 2018, which claims the benefit of U.S. Provisional Application Ser. No. 62/473,105 filed Mar. 17, 2017, the contents of which are incorporated by reference herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6389074 | Andrew | May 2002 | B1 |
| 10477238 | Jin et al. | Nov 2019 | B2 |
| 20070217508 | Shimada et al. | Sep 2007 | A1 |
| 20140153645 | Zhang et al. | Jun 2014 | A1 |
| 20150201212 | Zhang et al. | Jul 2015 | A1 |
| 20160255369 | Nam et al. | Sep 2016 | A1 |
| 20170374385 | Huang et al. | Dec 2017 | A1 |
| 20180103199 | Hendry | Apr 2018 | A1 |
| 20180160123 | Van Der Auwera et al. | Jun 2018 | A1 |
| 20220210465 | Kondow | Jun 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 2003-179938 | Jun 2003 | JP |
| 2012-191512 | Oct 2012 | JP |
| Entry |
|---|
| Abbas, Adeel, “GoPro Test Sequences for Virtual Reality Video Coding”, JVET-C0021, GoPro, Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 3rd Meeting: Geneva, CH, May 26-31, 2016, 10 pages. |
| Bang et al., “Description of 360 3D Video Application Exploration Experiments on Divergent Multi-View Video”, ISO/IEC JTC1/SC29/WG11 MPEG2015/ M16129, Requirements, San Diego, US, Feb. 2016, 5 pages. |
| Boyce et al., “JVET Common Test Conditions and Evaluation Procedures for 360° Video”, JVET-D1030_V1, Editors, Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC1/SC 29/WG 11, 4th Meeting: Chengdu, CN, Oct. 15-21, 2016, pp. 1-6. |
| Chen et al., “Algorithm Description of Joint Exploration Test Model 5”, JVET-E1001-V1, Editors, Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 5th Meeting: Geneva, CH, Jan. 12-20, 2017, 45 pages. |
| Choi, Byeongdoo, “Technologies Under Consideration for Omnidirectional Media Application Format”, Systems Subgroup, ISO/IEC JTC1/SC29/WG11 N15946, San Diego, CA, US, Feb. 2016, 16 pages. |
| Facebook360, “Facebook 360 Video”, Available at <https://facebook360.fb.com/>, pp. 1-5. |
| Github, “Facebook's Equirectangular to Cube Map Tool on GitHub”, Transform 360, Available at <https://github.com/facebook/transform?files=1>, pp. 1-3. |
| Google VR, “Google Cardboard”, Available at <https://www.google.com/get/cardboard/>, pp. 1-4. |
| Hanhart et al., “AHG8: Reference Samples Derivation Using Geometry Padding for Intra Coding”, JVET-D0092, InterDigital Communications Inc., Joint Video Exploration Team (JVET) of ITU-T SF 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 4th Meeting: Chengdu, CN, Oct. 15-21, 2016, pp. 1-6. |
| He et al., “AHG8: Geometry Padding for 360 Video Coding”, JVET-D0075, InterDigital Communications Inc., Joint Video Exploration Team (JVET) of ITU-T Sg 16 WP 3 and ISO/IEC JTC1/SC 29/WG 11, 4th Meeting: Chengdu, CN, Oct. 15-21, 2016, pp. 1-10. |
| HTC, “HTC Vive”, Available at <https://www.htcvive.com/us/>, pp. 1-3. |
| ISO/IEC, “Requirements for OMAF”, Requirements, ISO/IEC JTC1/SC29/WG11 N16143, San Diego, CA, US, Feb. 2016, 2 pages. |
| Kuzyakov et al., “Next-Generation Video Encoding Techniques for 360 Video and VR”, Facebook Code, Available at <https://code.facebook.com/posts/1126354007399553/next-generation-video-encoding-techniques-for-360-video-and-vr/>, Jan. 21, 2016, pp. 1-6. |
| Leannec et al., “Asymmetric Coding Units in QTBT”, JVET-D0064, Technicolor, Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 4th Meeting: Chengdu, CN, Oct. 15- 21, 2016, pp. 1-8. |
| Li et al., “Multi-Type-Tree”, JVET-D0117, Qualcomm Inc., Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 4th Meeting: Chengdu, CN, Oct. 15-21, 2016, pp. 1-3. |
| Norkin et al., “Call for Test Materials for Future Video Coding Standardization”, JVET-B1002, ITU-T Q6/16 Visual Coding (VCEG) and ISO/IEC JTC1/SC29/WG11 Coding of Moving Pictures and Audio (MPEG), Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 2nd Meeting: San Diego, USA, Feb. 20-26, 2016, pp. 1-4. |
| Oculus, “Oculus Rift”, Available at <https://www.oculus.com/en-us/rift/>, pp. 1-19. |
| Shih et al., “AHG8: Face-Based Padding Scheme for Cube Projection”, JVET-E0057, MediaTek Inc., Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC1/SC 29/WG 11, 5th Meeting: Geneva, CH, Jan. 12-20, 2017, pp. 1-5. |
| Thomas et al., “5G and Future Media Consumption”, TNO, ISO/IEC JTC1/SC29/WG11 MPEG2016/m37604, San Diego, CA, US, Feb. 2016, 10 pages. |
| Wien et al., “Preliminary Joint Call for Evidence on Video Compression with Capability Beyond HEVC”, JVET-E1002, JVET, Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 5th Meeting: Geneva, CH, Jan. 12-20, 2017, pp. 1-9. |
| Number | Date | Country | |
|---|---|---|---|
| 20220201327 A1 | Jun 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62473105 | Mar 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16494835 | US | |
| Child | 17690996 | US |
