Patent Application
20250239032
This disclosure provides a method for providing device capabilities for the negotiation between the device and network to set up a split-rendering session.
3GPP has a work item on split rendering of media delivery services, in which the client media functions are split between the device and the network edge. Therefore the client runs lighter less demanding processes and can receive more complicated applications and services. In turn, the edge network would receive the media, decode and partially render it to a simpler form, so that the client can run a lighter process.
The 5G augmented reality devices need to have intensive processing, including multiple parallel media decoding and possibility media encoding, scene composition, and augmented reality rendering.
When the Application and/or Application Service Provider decides to run the client media functions in the split-rendering fashion, they have to replace this functionality with two new modules: 1. The edge-dependent light media service client, and 2. The media processing application running on 5GMS AS.
The current specification defines split rendering configuration parameters, including the desired view information. The device is expected to send back the view position information for those views to the network. However, the configuration parameters do not define any specification of how often and with what increments those position information needs to be captured and sent to the network.
To address one or more different technical problems, this disclosure provides technical solutions to reduce network overhead and server computational overheads while delivering an option to apply various operations to the resolved element such that in using these operations some of practicality and technical signaling features thereof may be improved.
And for any of those reasons there is therefore a desire for technical solutions to such problems that arose in video coding technology.
There is included a method and apparatus comprising memory configured to store computer program code and a processor or processors configured to access the computer program code and operate as instructed by the computer program code. The computer program is configured to cause the processor implement obtaining code configured to cause the at least one processor to perform a conversion between a visual media file and a bitstream of a visual media data according to a format rule, the format rule indicating to: determine capabilities of an augmented reality (AR) device, the capabilities indicating, as part of the AR device serving as a split rendering client (SRC), any of an audio encoder or decoder of the AR device and a video encoder or decoder of the AR device; obtain AR data of a media component of at least one of audio and video based on a request signaling the capabilities of the AR device to a server, acting as a split rendering server (SRS) for split rendering of the media component between the SRS and the SRC, providing the AR data; and process the AR data based on the capabilities of the AR device signaled to the SRC.
The request signaling the capabilities of the AR device may include a profile identifier in a form of a uniform resource indicator (URI) and comprising a syntax of “deviceType”.
The profile identifier may indicate an extended reality (XR) runtime and scene manager capabilities.
The request signaling the capabilities of the AR device may include a list of at least some of the capabilities of the AR device, and the at least some of the capabilities of the AR device indicating optional codecs of the AR device.
The at least some of the capabilities of the AR device may further indicate a number of instances of and interfaces of the optional codecs of the AR device, extended reality (XR) runtime profiles, optional extensions, a scene description format, and a profile supported by the scene description format.
The request signaling the capabilities of the AR device may further include a profile identifier in a form of a uniform resource indicator (URI) and comprising a syntax of “deviceType”, and a syntax indicating the list of the at least some of the capabilities is “deviceDetailedCapabilities”, and the profile identifier may indicate an extended reality (XR) runtime and scene manager capabilities other than of the at least some of the capabilities of the AR device.
Further features, nature, and various advantages of the disclosed subject matter will be more apparent from the following detailed description and the accompanying drawings in which:
with embodiments.
The proposed features discussed below may be used separately or combined in any order. Further, the embodiments may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits). In one example, the one or more processors execute a program that is stored in a non-transitory computer-readable medium.
In
A streaming system may include a capture subsystem 203, that can include a video source 201, for example a digital camera, creating, for example, an uncompressed video sample stream 213. That sample stream 213 may be emphasized as a high data volume when compared to encoded video bitstreams and can be processed by an encoder 202 coupled to the camera 201. The encoder 202 can include hardware, software, or a combination thereof to enable or implement aspects of the disclosed subject matter as described in more detail below. The encoded video bitstream 204, which may be emphasized as a lower data volume when compared to the sample stream, can be stored on a streaming server 205 for future use. One or more streaming clients 212 and 207 can access the streaming server 205 to retrieve copies 208 and 206 of the encoded video bitstream 204. A client 212 can include a video decoder 211 which decodes the incoming copy of the encoded video bitstream 208 and creates an outgoing video sample stream 210 that can be rendered on a display 209 or other rendering device (not depicted). In some streaming systems, the video bitstreams 204, 206 and 208 can be encoded according to certain video coding/compression standards. Examples of those standards are noted above and described further herein.
A receiver 302 may receive one or more codec video sequences to be decoded by the decoder 300; in the same or another embodiment, one coded video sequence at a time, where the decoding of each coded video sequence is independent from other coded video sequences. The coded video sequence may be received from a channel 301, which may be a hardware/software link to a storage device which stores the encoded video data. The receiver 302 may receive the encoded video data with other data, for example, coded audio data and/or ancillary data streams, that may be forwarded to their respective using entities (not depicted). The receiver 302 may separate the coded video sequence from the other data. To combat network jitter, a buffer memory 303 may be coupled in between receiver 302 and entropy decoder/parser 304 (“parser” henceforth). When receiver 302 is receiving data from a store/forward device of sufficient bandwidth and controllability, or from an isosychronous network, the buffer 303 may not be needed, or can be small. For use on best effort packet networks such as the Internet, the buffer 303 may be required, can be comparatively large and can advantageously of adaptive size.
The video decoder 300 may include a parser 304 to reconstruct symbols 313 from the entropy coded video sequence. Categories of those symbols include information used to manage operation of the decoder 300, and potentially information to control a rendering device such as a display 312 that is not an integral part of the decoder but can be coupled to it. The control information for the rendering device(s) may be in the form of Supplementary Enhancement Information (SEI messages) or Video Usability Information parameter set fragments (not depicted). The parser 304 may parse/entropy-decode the coded video sequence received. The coding of the coded video sequence can be in accordance with a video coding technology or standard, and can follow principles well known to a person skilled in the art, including variable length coding, Huffman coding, arithmetic coding with or without context sensitivity, and so forth. The parser 304 may extract from the coded video sequence, a set of subgroup parameters for at least one of the subgroups of pixels in the video decoder, based upon at least one parameters corresponding to the group. Subgroups can include Groups of Pictures (GOPs), pictures, tiles, slices, macroblocks, Coding Units (CUs), blocks, Transform Units (TUs), Prediction Units (PUs) and so forth. The entropy decoder/parser may also extract from the coded video sequence information such as transform coefficients, quantizer parameter values, motion vectors, and so forth.
The parser 304 may perform entropy decoding/parsing operation on the video sequence received from the buffer 303, so to create symbols 313. The parser 304 may receive encoded data, and selectively decode particular symbols 313. Further, the parser 304 may determine whether the particular symbols 313 are to be provided to a Motion Compensation Prediction unit 306, a scaler/inverse transform unit 305, an Intra Prediction Unit 307, or a loop filter 311.
Reconstruction of the symbols 313 can involve multiple different units depending on the type of the coded video picture or parts thereof (such as: inter and intra picture, inter and intra block), and other factors. Which units are involved, and how, can be controlled by the subgroup control information that was parsed from the coded video sequence by the parser 304. The flow of such subgroup control information between the parser 304 and the multiple units below is not depicted for clarity.
Beyond the functional blocks already mentioned, decoder 300 can be conceptually subdivided into a number of functional units as described below. In a practical implementation operating under commercial constraints, many of these units interact closely with each other and can, at least partly, be integrated into each other. However, for the purpose of describing the disclosed subject matter, the conceptual subdivision into the functional units below is appropriate.
A first unit is the scaler/inverse transform unit 305. The scaler/inverse transform unit 305 receives quantized transform coefficient as well as control information, including which transform to use, block size, quantization factor, quantization scaling matrices, etc. as symbol(s) 313 from the parser 304. It can output blocks comprising sample values, that can be input into aggregator 310.
In some cases, the output samples of the scaler/inverse transform 305 can pertain to an intra coded block; that is: a block that is not using predictive information from previously reconstructed pictures, but can use predictive information from previously reconstructed parts of the current picture. Such predictive information can be provided by an intra picture prediction unit 307. In some cases, the intra picture prediction unit 307 generates a block of the same size and shape of the block under reconstruction, using surrounding already reconstructed information fetched from the current (partly reconstructed) picture 309. The aggregator 310, in some cases, adds, on a per sample basis, the prediction information the intra prediction unit 307 has generated to the output sample information as provided by the scaler/inverse transform unit 305.
In other cases, the output samples of the scaler/inverse transform unit 305 can pertain to an inter coded, and potentially motion compensated block. In such a case, a Motion Compensation Prediction unit 306 can access reference picture memory 308 to fetch samples used for prediction. After motion compensating the fetched samples in accordance with the symbols 313 pertaining to the block, these samples can be added by the aggregator 310 to the output of the scaler/inverse transform unit (in this case called the residual samples or residual signal) so to generate output sample information. The addresses within the reference picture memory form where the motion compensation unit fetches prediction samples can be controlled by motion vectors, available to the motion compensation unit in the form of symbols 313 that can have, for example X, Y, and reference picture components. Motion compensation also can include interpolation of sample values as fetched from the reference picture memory when sub-sample exact motion vectors are in use, motion vector prediction mechanisms, and so forth.
The output samples of the aggregator 310 can be subject to various loop filtering techniques in the loop filter unit 311. Video compression technologies can include in-loop filter technologies that are controlled by parameters included in the coded video bitstream and made available to the loop filter unit 311 as symbols 313 from the parser 304, but can also be responsive to meta-information obtained during the decoding of previous (in decoding order) parts of the coded picture or coded video sequence, as well as responsive to previously reconstructed and loop-filtered sample values.
The output of the loop filter unit 311 can be a sample stream that can be output to the display 312, which may be a render device, as well as stored in the reference picture memory 557 for use in future inter-picture prediction.
Certain coded pictures, once fully reconstructed, can be used as reference pictures for future prediction. Once a coded picture is fully reconstructed and the coded picture has been identified as a reference picture (by, for example, parser 304), the current reference picture 309 can become part of the reference picture buffer 308, and a fresh current picture memory can be reallocated before commencing the reconstruction of the following coded picture.
The video decoder 300 may perform decoding operations according to a predetermined video compression technology that may be documented in a standard, such as ITU-T Rec. H.265. The coded video sequence may conform to a syntax specified by the video compression technology or standard being used, in the sense that it adheres to the syntax of the video compression technology or standard, as specified in the video compression technology document or standard and specifically in the profiles document therein. Also necessary for compliance can be that the complexity of the coded video sequence is within bounds as defined by the level of the video compression technology or standard. In some cases, levels restrict the maximum picture size, maximum frame rate, maximum reconstruction sample rate (measured in, for example megasamples per second), maximum reference picture size, and so on. Limits set by levels can, in some cases, be further restricted through Hypothetical Reference Decoder (HRD) specifications and metadata for HRD buffer management signaled in the coded video sequence.
In an embodiment, the receiver 302 may receive additional (redundant) data with the encoded video. The additional data may be included as part of the coded video sequence(s). The additional data may be used by the video decoder 300 to properly decode the data and/or to more accurately reconstruct the original video data. Additional data can be in the form of, for example, temporal, spatial, or signal-to-noise ratio (SNR) enhancement layers, redundant slices, redundant pictures, forward error correction codes, and so on.
The encoder 400 may receive video samples from a video source 401 (that is not part of the encoder) that may capture video image(s) to be coded by the encoder 400.
The video source 401 may provide the source video sequence to be coded by the encoder (303) in the form of a digital video sample stream that can be of any suitable bit depth (for example: 8 bit, 10 bit, 12 bit, . . . ), any colorspace (for example, BT.601 Y CrCB, RGB, . . . ) and any suitable sampling structure (for example Y CrCb 4:2:0, Y CrCb 4:4:4). In a media serving system, the video source 401 may be a storage device storing previously prepared video. In a videoconferencing system, the video source 401 may be a camera that captures local image information as a video sequence. Video data may be provided as a plurality of individual pictures that impart motion when viewed in sequence. The pictures themselves may be organized as a spatial array of pixels, wherein each pixel can comprise one or more samples depending on the sampling structure, color space, etc. in use. A person skilled in the art can readily understand the relationship between pixels and samples. The description below focuses on samples.
According to an embodiment, the encoder 400 may code and compress the pictures of the source video sequence into a coded video sequence 410 in real time or under any other time constraints as required by the application. Enforcing appropriate coding speed is one function of Controller 402. Controller controls other functional units as described below and is functionally coupled to these units. The coupling is not depicted for clarity. Parameters set by controller can include rate control related parameters (picture skip, quantizer, lambda value of rate-distortion optimization techniques, . . . ), picture size, group of pictures (GOP) layout, maximum motion vector search range, and so forth. A person skilled in the art can readily identify other functions of controller 402 as they may pertain to video encoder 400 optimized for a certain system design.
Some video encoders operate in what a person skilled in the art readily recognizes as a “coding loop.” As an oversimplified description, a coding loop can consist of the encoding part of an encoder (for example a source coder 403) (responsible for creating symbols based on an input picture to be coded, and a reference picture(s)), and a (local) decoder 406 embedded in the encoder 400 that reconstructs the symbols to create the sample data that a (remote) decoder also would create (as any compression between symbols and coded video bitstream is lossless in the video compression technologies considered in the disclosed subject matter). That reconstructed sample stream is input to the reference picture memory 405. As the decoding of a symbol stream leads to bit-exact results independent of decoder location (local or remote), the reference picture buffer content is also bit exact between local encoder and remote encoder. In other words, the prediction part of an encoder “sees” as reference picture samples exactly the same sample values as a decoder would “see” when using prediction during decoding. This fundamental principle of reference picture synchronicity (and resulting drift, if synchronicity cannot be maintained, for example because of channel errors) is well known to a person skilled in the art.
The operation of the “local” decoder 406 can be the same as of a “remote” decoder 300, which has already been described in detail above in conjunction with
An observation that can be made at this point is that any decoder technology except the parsing/entropy decoding that is present in a decoder also necessarily needs to be present, in substantially identical functional form, in a corresponding encoder. The description of encoder technologies can be abbreviated as they are the inverse of the comprehensively described decoder technologies. Only in certain areas a more detail description is required and provided below.
As part of its operation, the source coder 403 may perform motion compensated predictive coding, which codes an input frame predictively with reference to one or more previously-coded frames from the video sequence that were designated as “reference frames.” In this manner, the coding engine 407 codes differences between pixel blocks of an input frame and pixel blocks of reference frame(s) that may be selected as prediction reference(s) to the input frame.
The local video decoder 406 may decode coded video data of frames that may be designated as reference frames, based on symbols created by the source coder 403. Operations of the coding engine 407 may advantageously be lossy processes. When the coded video data may be decoded at a video decoder (not shown in
The predictor 404 may perform prediction searches for the coding engine 407. That is, for a new frame to be coded, the predictor 404 may search the reference picture memory 405 for sample data (as candidate reference pixel blocks) or certain metadata such as reference picture motion vectors, block shapes, and so on, that may serve as an appropriate prediction reference for the new pictures. The predictor 404 may operate on a sample block-by-pixel block basis to find appropriate prediction references. In some cases, as determined by search results obtained by the predictor 404, an input picture may have prediction references drawn from multiple reference pictures stored in the reference picture memory 405.
The controller 402 may manage coding operations of the video coder 403, including, for example, setting of parameters and subgroup parameters used for encoding the video data.
Output of all aforementioned functional units may be subjected to entropy coding in the entropy coder 408. The entropy coder translates the symbols as generated by the various functional units into a coded video sequence, by loss-less compressing the symbols according to technologies known to a person skilled in the art as, for example Huffman coding, variable length coding, arithmetic coding, and so forth.
The transmitter 409 may buffer the coded video sequence(s) as created by the entropy coder 408 to prepare it for transmission via a communication channel 411, which may be a hardware/software link to a storage device which would store the encoded video data. The transmitter 409 may merge coded video data from the video coder 403 with other data to be transmitted, for example, coded audio data and/or ancillary data streams (sources not shown).
The controller 402 may manage operation of the encoder 400. During coding, the controller 405 may assign to each coded picture a certain coded picture type, which may affect the coding techniques that may be applied to the respective picture. For example, pictures often may be assigned as one of the following frame types:
An Intra Picture (I picture) may be one that may be coded and decoded without using any other frame in the sequence as a source of prediction. Some video codecs allow for different types of Intra pictures, including, for example Independent Decoder Refresh Pictures. A person skilled in the art is aware of those variants of I pictures and their respective applications and features.
A Predictive picture (P picture) may be one that may be coded and decoded using intra prediction or inter prediction using at most one motion vector and reference index to predict the sample values of each block.
A Bi-directionally Predictive Picture (B Picture) may be one that may be coded and decoded using intra prediction or inter prediction using at most two motion vectors and reference indices to predict the sample values of each block. Similarly, multiple-predictive pictures can use more than two reference pictures and associated metadata for the reconstruction of a single block.
Source pictures commonly may be subdivided spatially into a plurality of sample blocks (for example, blocks of 4×4, 8×8, 4×8, or 16×16 samples each) and coded on a block-by-block basis. Blocks may be coded predictively with reference to other (already coded) blocks as determined by the coding assignment applied to the blocks' respective pictures. For example, blocks of I pictures may be coded non-predictively or they may be coded predictively with reference to already coded blocks of the same picture (spatial prediction or intra prediction). Pixel blocks of P pictures may be coded non-predictively, via spatial prediction or via temporal prediction with reference to one previously coded reference pictures. Blocks of B pictures may be coded non-predictively, via spatial prediction or via temporal prediction with reference to one or two previously coded reference pictures.
The video coder 400 may perform coding operations according to a predetermined video coding technology or standard, such as ITU-T Rec. H.265. In its operation, the video coder 400 may perform various compression operations, including predictive coding operations that exploit temporal and spatial redundancies in the input video sequence. The coded video data, therefore, may conform to a syntax specified by the video coding technology or standard being used.
In an embodiment, the transmitter 409 may transmit additional data with the encoded video. The source coder 403 may include such data as part of the coded video sequence. Additional data may comprise temporal/spatial/SNR enhancement layers, other forms of redundant data such as redundant pictures and slices, Supplementary Enhancement Information (SEI) messages, Visual Usability Information (VUI) parameter set fragments, and so on.
And according to exemplary embodiments, as described below, there may be experienced a shared conversational use case in which all participants of a shared AR conversational experience have AR devices, each participant sees other participants in an AR scene, where the participants are overlays in the local physical scene, the arrangement of the participants in the scene is consistent in all receiving devices, e.g., the people in each local space have the same position/seating arrangement relative to each other, and such virtual space creates the sense of being in the same space but the room varies from participant to participant since the room is the actual room or space each person is physically located.
For example according to the exemplary embodiments shown with respect to
According to exemplary embodiments, see also
And see in the AR environment where in the office 1001, the AR of user A 10 shows to that user A 10 a virtual user B 11v1, corresponding to user B 11, and a virtual user T 12v1, corresponding to user T 12, and such that the virtual user B 11v1 and virtual user T 12v1 are shown to user A 10 as sitting on the furniture, office chairs, in the office 1001 as is the user A 10. And see in the living room 1202 in the example 1200 in which the AR for user B 11 shows the virtual user T 12v2, corresponding to the user T 12 but sitting on a couch in the living room 1202, and a virtual user A 10v1 corresponding to the user A 10 also sitting on furniture in the living room 1202 rather than the office chair in office 1201. See also in the airport lounge 1203 where the AR for the user T12 shows a virtual user A 10v2, corresponding to the user A 10 but sitting at a table at the airport lounge 1203, and a virtual user B 11v2 also sitting at the table across from virtual user A 10v2. And in each of those office 1201, living room 1202, and airport lounge 1203, the updated scene description of each room is consistent with other rooms in terms of position/seating arrangements. For example, user A 10 is shown as relatively counter-clockwise to user 11 or virtual representations thereof who is also relatively clockwise to user T 12 or virtual representations thereof per room.
But AR technology has been limited in any attempts to incorporate creation and use of virtual spaces for devices that do not support AR but can parse VR or 2D video, and embodiments herein provide for improved technological procedure for creating a virtual scene consistent with the AR scene when such devices participated in the shared AR conversational services.
As is shown
As such, there may be multiview capabilities such as where AR processing on edge/cloud 1102 may generate multiple videos of the same virtual room: from different angles and with different viewports. And the device 1101 can receive one or more of these videos, switching between them when desired, or sends commands to the edge/cloud processing to only stream the desired viewport/angle.
Also, there may be changing the background capability, where the user on the device 1101 can select the desired room background from the provided library, e.g one of different conference rooms, or even living rooms and layouts. And the cloud/edge 1102 uses the selected background and creates the virtual room accordingly.
There is shown an AR application module 21, a media play module 22, and a media access function module 23 which may be considered to be modules of the receiving non-AR UE 1101. There is also shown a cloud/edge split rendering module 24. There is also shown a media delivery module 25 and a scene graph composer module 26 each of the network cloud 1102. There is also shown a 5G sender UE module 700.
S1-S6 may be considered a session establishment phase. The AR application module 21 may request to start a session to the media access function module 23 at S1, and the media access function module 23 may request to start a session to the cloud/edge split rendering module 24 at S2.
The cloud/edge split rendering module 24 may implement session negotiation at S3 with the scene graph composer module 26 which may accordingly negotiate with the 5G sender UE 700. If successful, then at S5, the cloud/edge split-rendering module may send an acknowledgement to the media access function module 23, and the media access function module 23 may send an acknowledgement to the AR application module 21.
Afterwards, the S7 may be considered to be a media pipeline configuration stage in which the media access function module 23 and the cloud/edge split-rendering module 24 each configure respective pipelines. And then, after that pipeline configuration, a session may be started by a signal at S8 from the AR application module to the media player module 22, and from the media player module 22 to the media access function module 23 at S9, and from the media access function module 23 to the cloud/edge split-rendering module 24 at S10.
Then there may be a pose loop stage from S11 to S13 in which at S11, pose data may be provided from the media player module 22 to the AR application module 21, and at S12, the AR application module may provide pose data 12 to the media access function module 23 after which the media access function module 23 may provide pose data to the cloud/edge split-rendering module 24.
S14 to S16 may be considered to be a shared experience stream stage in which at S14 the 5G sender UE 700 may provide media streams at S14 to the media delivery module 25 and AR data to the scene graph compositor module 26 at S15. Then the scene graph compositor module 25 may compose one or more scenes based on the received AR data and at S16 provide scene and scene updates to the could/edge split-rendering module 24, and also the media delivery module 25 may provide media streams to the cloud/edge split-rendering module at S17. This may include obtaining an AR scene descriptor from the non-AR device that does not render an AR scene and generating a virtual scene by a cloud device by parsing and rendering the scene description obtained from the non-AR device according to exemplary embodiments.
S18 to S19 may be considered to be a media uplink stage in which the media player module 22 captures and processes media data from its local user and provides, at S18, that media data to the media access function module 23. Then the media access module 23 may encode the media and provide, at S19, media streams to the cloud/edge split-rendering module 24.
Between S19 and S20 may be considered a media downlink stage in which the cloud/edge split-rendering module 24 may implement scene parsing and complete AR rendering after which, S20 and S21 may be considered to make up a media stream loop stage. At S20, the cloud/edge split-rendering module 24 may provide media streams to the media access function module 23 which may then decode the media and provide, at S21, media rendering to the media player 22.
By such features according to exemplary embodiments, the non-AR UE 1101, even though not having a see-through display and therefore not able to create an AR scene, nonetheless, can take advantage of its display that can render VR or 2-D video. As such, its immersive media processing function only generates a common scene description, describing the relative position of each participant to others and the scene. The scene itself needs to be adjusted with pose information at each device before being rendered as an AR scene as described above. And AR rendering process on edge or cloud can parse an AR scene and create the simplified VR-2D scene.
According to exemplary embodiments, this disclosure uses similar split-rendering processing of an EDGAR device for a non-AR device, such as a VR or 2-d video device, with characteristics such as the edge/cloud AR rendering process in this case does not produce any AR scene. Instead, it generated a virtual scene, by parsing and rendering the scene description received from the immersive media processing function for a given background (such as a conference room) and then renders each participant in the location described by the scene description in the conference room.
Also, the resulting video can be a 360 Video or a 2-D video depending on the capabilities of the receiving non-AR device, and the resulted video is generated considering the pos-information received from the non-AR device according to exemplary embodiments.
Also, each other participant with a non-AR device is added as a 2-D video overlay on the 360/2D video of the conference room, such as shown in
Also, the audio signals from all participants may be mixed if necessary to create single-channel audio that carries the voice in the room, the video may be encoded as a single 360 video or 2-D video and delivered to the device, and optionally, multiple video (multi-view) sources can be created, each of which captures the same virtual conference room from a different view and provide those views to the device according to exemplary embodiments.
Further, the non-AR UE device 1101 can receive the 360 video and/or one or more multi-view videos of choice along with audio and renders on the device display, and the user may switch between different views, or by moving or rotating the view device, change the viewport of the 360-video and therefore be able to navigate in the virtual room while viewing the video.
Although embodiments described above are provided with such 5G media stream architecture (5GMS) extensions to use the edge servers in their architectures, and while a specification thereof may have many features, such features have been technically unable to be deployed as a set of software development kits (SDKs) on a device or as a set of microservices on the cloud, and such technical deficiency is addressed by embodiments described further below.
For example, the current media service enabler technical report does not define a framework that relates the specification to SDKs and does not include any notion of microservices.
See the example 1400 of
According to exemplary embodiments,
According to exemplary embodiments, the MSE specification 1501 defines (a) media aspects and (b) MSE configuration, which provides for such technical advantages. The (a) media aspects may indicate any of (i) functional description of the MSE including mandatory and optional features, (ii) control interfaces such as provisioning, authentication that is used by the application, and other functions to interact with this MSE, (iii), media interfaces that includes all inputs and outputs format and protocols, (iv) network interface including system and radio network, (v) event, notifications, reporting, and monitoring, and (vi) error handling. The (b) MSE configuration may indicate (i) an MSE description document (MDD) (that describes (1) functions supported by an MSE implementation and their configuration parameters, and (2) optionally the performance/cost metrics for the different features/options), (ii) an MSE Configuration API (MCA) abstraction (indicating information for (1) retrieving the description document, (2) configuring the MSE instantiation, and (3) retrieving the state and status of the MSE instantiation), and (iii) a service API for that MSE Configuration API (MCA) abstraction. The MSE implementation 1502 may include any of (a) the MSE SDK abstraction 1510 (which indicates (i) media aspects, conforming to the media aspects of the MSE specification 1501, and (ii) the MSE description document (MDD) and the MSE Configuration API (MCA) abstraction of the above-described MSE configuration of the MSE Specification 1501), (b) the MSE SDK (platform dependent) instantiation 1520 (which indicates an SDK implementation in a specific environment and conforms to the following: (i) media aspects, conforming to the media aspects of the MSE specification 1501, and (ii) the MSE description document (MDD) and, unlike the MSE SDK abstraction 1530, only a specific the MSE Configuration API (MCA) abstraction of the above-described MSE configuration of the MSE Specification 1501), and (c) the MSE microservice 1510 which is the MSE implementation as a microservice and indicates (i) media aspects, conforming to the media aspects of the MSE specification 1501, and a service API for the MSE Configuration API (MCA) abstraction for the MSE description document (MDD) and the MSE Configuration API (MCA) abstraction of the above-described MSE configuration of the MSE Specification 1501. Determining conformance may be by matching formats or syntax for example or by a flag indicating such format or syntax.
For example, according to such advantageous MSE specification, which is absent from the 3GPP SA4 specifications, for any SDK or microservice that is conforming to the MSE specification, a description of the features and their configuration parameters can be retrieved by an external function or service according to exemplary embodiments, the external function or service can set a specific configuration for running that SDK, and the state and status of the running SDK can be retrieved at any time. The state and status may indicate available, running, busy, idle, offline, etc.
In that light,
According to exemplary embodiments, see the flowchart 1700 of
An example of MDD can be found in ISO/IEC 23090-8. The function description document is a JSON document that describes the functionalities and features a function provides and its configuration parameters.
As such, exemplary embodiments provide a method for defining media service enabler SDK and services wherein the functionalities and features of a media service enabler are described in a document that can be retrieved by an external function, application, or service, as well as the configuration parameters for each feature, wherein the external entity can set up a specific configuration of the media service enabler using the same interface used for retrieving the information, wherein the complexity or other metric of various functions of the media service enabler, is also described in the document, wherein the media service enabler specification defines a format for the description document as well as a unique identifier to that specific media service enabler.
According to embodiments, the example 1800 of
According to an embodiment, the detailed device capabilities indicate the capabilities at two levels: the high-level device type and the low level device detailed capabilities as in Table 2:
According to embodiments, during the negotiation of split rendering client (SRC) and split rendering server (SRS). SRC provides the device capabilities as part of the split-rendering configuration to SRS. SRS with analysis of the device capabilities, whether it provides high-level device type or additional detailed capabilities, along with the splitRenderingProfile, defines how to split the session between the network and the device. Since the device capabilities define more information than the splitRenderingProfile, the SRS can optimize the split session per the device's capabilities and does not limit the split-rendering to the defined split-rendering profile.
And therefore, there is provided a method for signaling the augmented reality device capabilities as a part of split-rendering configuration by the device to the network during the device-network negotiation for setting up the split-rendering session, wherein the split-rendering client provides the device type/profiles that the device supports with optionally detailed information about the number of codecs it supports and maximum number of instances, as well as the XR runtime and scene manager capabilities, by which the split-rendering server can decide what would be the best optional for split-rendering session.
The XR Runtime comprises functions and hardware components present on the XR Device. However, those functions and hardware components are not directly exposed to the XR Application. Instead, the XR Runtime offers its functions and hardware components via an XR System. A single XR Runtime may expose more than one XR Systems for targeting different purposes, e.g., a handheld device may have two XR Systems, one when the user holds the device and one when the device is inserted into an HMD. At the start of the XR Application, the XR Application is expected to query what XR Systems are available on the XR Device and select one of them to create the XR Session.
The Split Rendering client establishes an XR session locally based on the device configuration and user selection. The SR client defines the view configuration (e.g. mono or stereo views), the projection format (such as projection, equirectangular, quad, or cubemap), the swap chain image configuration, etc. In addition, XR space and action configurations are negotiated between the SR client and server. This includes defining common XR spaces and defining and selecting actions and action sets. The format is extensible to support the exchange of additional/future configuration information.
The techniques described above, can be implemented as computer software using computer-readable instructions and physically stored in one or more computer-readable media or by a specifically configured one or more hardware processors. For example,
The computer software can be coded using any suitable machine code or computer language, that may be subject to assembly, compilation, linking, or like mechanisms to create code comprising instructions that can be executed directly, or through interpretation, micro-code execution, and the like, by computer central processing units (CPUs), Graphics Processing Units (GPUs), and the like.
The instructions can be executed on various types of computers or components thereof, including, for example, personal computers, tablet computers, servers, smartphones, gaming devices, internet of things devices, and the like.
The components shown in
Computer system 1900 may include certain human interface input devices. Such a human interface input device may be responsive to input by one or more human users through, for example, tactile input (such as: keystrokes, swipes, data glove movements), audio input (such as: voice, clapping), visual input (such as: gestures), olfactory input (not depicted). The human interface devices can also be used to capture certain media not necessarily directly related to conscious input by a human, such as audio (such as: speech, music, ambient sound), images (such as: scanned images, photographic images obtain from a still image camera), video (such as two-dimensional video, three-dimensional video including stereoscopic video).
Input human interface devices may include one or more of (only one of each depicted): keyboard 1901, mouse 1902, trackpad 1903, touch screen 1910, joystick 1905, microphone 1906, scanner 1908, camera 1907.
Computer system 1900 may also include certain human interface output devices. Such human interface output devices may be stimulating the senses of one or more human users through, for example, tactile output, sound, light, and smell/taste. Such human interface output devices may include tactile output devices (for example tactile feedback by the touch-screen 1910, or joystick 1905, but there can also be tactile feedback devices that do not serve as input devices), audio output devices (such as: speakers 1909, headphones (not depicted)), visual output devices (such as screens 1910 to include CRT screens, LCD screens, plasma screens, OLED screens, each with or without touch-screen input capability, each with or without tactile feedback capability-some of which may be capable to output two dimensional visual output or more than three dimensional output through means such as stereographic output; virtual-reality glasses (not depicted), holographic displays and smoke tanks (not depicted)), and printers (not depicted).
Computer system 1900 can also include human accessible storage devices and their associated media such as optical media including CD/DVD ROM/RW 1920 with CD/DVD 1911 or the like media, thumb-drive 1922, removable hard drive or solid state drive 1923, legacy magnetic media such as tape and floppy disc (not depicted), specialized ROM/ASIC/PLD based devices such as security dongles (not depicted), and the like.
Those skilled in the art should also understand that term “computer readable media” as used in connection with the presently disclosed subject matter does not encompass transmission media, carrier waves, or other transitory signals.
Computer system 1900 can also include interface 1999 to one or more communication networks 1998. Networks 1998 can for example be wireless, wireline, optical.
Networks 1998 can further be local, wide-area, metropolitan, vehicular and industrial, real-time, delay-tolerant, and so on. Examples of networks 1998 include local area networks such as Ethernet, wireless LANs, cellular networks to include GSM, 3G, 4G, 5G, LTE and the like, TV wireline or wireless wide area digital networks to include cable TV, satellite TV, and terrestrial broadcast TV, vehicular and industrial to include CANBus, and so forth. Certain networks 1998 commonly require external network interface adapters that attached to certain general-purpose data ports or peripheral buses (1950 and 1951) (such as, for example USB ports of the computer system 1900; others are commonly integrated into the core of the computer system 1900 by attachment to a system bus as described below (for example Ethernet interface into a PC computer system or cellular network interface into a smartphone computer system). Using any of these networks 1998, computer system 1900 can communicate with other entities. Such communication can be uni-directional, receive only (for example, broadcast TV), uni-directional send-only (for example CANbusto certain CANbus devices), or bi-directional, for example to other computer systems using local or wide area digital networks. Certain protocols and protocol stacks can be used on each of those networks and network interfaces as described above.
Aforementioned human interface devices, human-accessible storage devices, and network interfaces can be attached to a core 1940 of the computer system 1900.
The core 1940 can include one or more Central Processing Units (CPU) 1941, Graphics Processing Units (GPU) 1942, a graphics adapter 1917, specialized programmable processing units in the form of Field Programmable Gate Areas (FPGA) 1943, hardware accelerators for certain tasks 1944, and so forth. These devices, along with Read-only memory (ROM) 1945, Random-access memory 1946, internal mass storage such as internal non-user accessible hard drives, SSDs, and the like 1947, may be connected through a system bus 1948. In some computer systems, the system bus 1948 can be accessible in the form of one or more physical plugs to enable extensions by additional CPUs, GPU, and the like. The peripheral devices can be attached either directly to the core's system bus 1948, or through a peripheral bus 1951. Architectures for a peripheral bus include PCI, USB, and the like.
CPUs 1941, GPUs 1942, FPGAs 1943, and accelerators 1944 can execute certain instructions that, in combination, can make up the aforementioned computer code. That computer code can be stored in ROM 1945 or RAM 1946. Transitional data can be also be stored in RAM 1946, whereas permanent data can be stored for example, in the internal mass storage 1947. Fast storage and retrieval to any of the memory devices can be enabled through the use of cache memory, that can be closely associated with one or more CPU 1941, GPU 1942, mass storage 1947, ROM 1945, RAM 1946, and the like.
The computer readable media can have computer code thereon for performing various computer-implemented operations. The media and computer code can be those specially designed and constructed for the purposes of the present disclosure, or they can be of the kind well known and available to those having skill in the computer software arts.
As an example and not by way of limitation, an architecture corresponding to computer system 1900, and specifically the core 1940 can provide functionality as a result of processor(s) (including CPUs, GPUs, FPGA, accelerators, and the like) executing software embodied in one or more tangible, computer-readable media. Such computer-readable media can be media associated with user-accessible mass storage as introduced above, as well as certain storage of the core 1940 that are of non-transitory nature, such as core-internal mass storage 1947 or ROM 1945. The software implementing various embodiments of the present disclosure can be stored in such devices and executed by core 1940. A computer-readable medium can include one or more memory devices or chips, according to particular needs. The software can cause the core 1940 and specifically the processors therein (including CPU, GPU, FPGA, and the like) to execute particular processes or particular parts of particular processes described herein, including defining data structures stored in RAM 1946 and modifying such data structures according to the processes defined by the software. In addition or as an alternative, the computer system can provide functionality as a result of logic hardwired or otherwise embodied in a circuit (for example: accelerator 1944), which can operate in place of or together with software to execute particular processes or particular parts of particular processes described herein. Reference to software can encompass logic, and vice versa, where appropriate. Reference to a computer-readable media can encompass a circuit (such as an integrated circuit (IC)) storing software for execution, a circuit embodying logic for execution, or both, where appropriate. The present disclosure encompasses any suitable combination of hardware and software.
While this disclosure has described several exemplary embodiments, there are alterations, permutations, and various substitute equivalents, which fall within the scope of the disclosure. It will thus be appreciated that those skilled in the art will be able to devise numerous systems and methods which, although not explicitly shown or described herein, embody the principles of the disclosure and are thus within the spirit and scope thereof.
The present application claims priority to provisional application U.S. 63/623,763 filed on Jan. 22, 2024, the contents of which are hereby expressly incorporated by reference, in its entirety, into the present application.
| Number | Date | Country | |
|---|---|---|---|
| 63623763 | Jan 2024 | US |
