Patent Description:
The disclosure generally relates to <NUM>th generation (<NUM>) augmented reality (AR)/mixed reality (MR), and, in particular, to a method and apparatus for providing AR/MR applications to <NUM> devices.

The 3rd Generation Partnership Project (3GPP) TS26. <NUM> defines the media streaming architecture for <NUM>th generation (<NUM>) networks. The 3GPP started a technical report on supporting augmented reality (AR)/mixed reality (MR) applications. 3GPP TR <NUM> defines the support for glass-type AR/MR devices in <NUM> networks. Two device classes are considered: devices that are fully capable of decoding and playing complex AR/MR content (i.e., stand-alone AR (STAR)), and devices that have smaller computational resources and/or smaller physical size (i.e., a smaller battery), and are only capable of running such applications if the larger portion of the computation is performed on <NUM> edge servers, networks, or clouds rather than on the device (edge dependent AR (EDGAR).

The selection of edge servers may be performed by a media session handler. However, the selection may occur prior to the AR/MR application deciding on the subset of media components of an immersive scene to be streamed. Thus, the required computational resources may be affected by the AR/MR application choices, which is not currently considered. Furthermore, the AR/MR application and media session handler should operate jointly or by the AR/MR application provider through a <NUM>th Generation media streaming downlink (5GMSd) application function (AF), which is not currently considered. Additionally, it is not clear how the AR/MR application selects the media components of the scene to be streamed to the device without receiving the full scene graph. Lastly, the scene updates are not addressed in the current workflow.

In accordance with an aspect of the disclosure, a method is presented in independent claim <NUM>.

In accordance with an aspect of the disclosure, a device is presented in independent claim <NUM>.

In accordance with an aspect of the disclosure, a non-transitory computer-readable medium is presented in claim <NUM>.

<FIG> is a diagram of an environment <NUM> in which methods, apparatuses, and systems described herein may be implemented, according to embodiments. As shown in <FIG>, the environment <NUM> may include a user device <NUM>, a platform <NUM>, and a network <NUM>. Devices of the environment <NUM> may interconnect via wired connections, wireless connections, or a combination of wired and wireless connections.

The user device <NUM> includes one or more devices capable of receiving, generating, storing, processing, and/or providing information associated with platform <NUM>. For example, the user device <NUM> may include a computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a handheld computer, a smart speaker, a server, etc.), a mobile phone (e.g., a smart phone, a radiotelephone, etc.), a wearable device (e.g., a pair of smart glasses or a smart watch), or a similar device. In some implementations, the user device <NUM> may receive information from and/or transmit information to the platform <NUM>.

The platform <NUM> includes one or more devices as described elsewhere herein. In some implementations, the platform <NUM> may include a cloud server or a group of cloud servers. In some implementations, the platform <NUM> may be designed to be modular such that software components may be swapped in or out depending on a particular need. As such, the platform <NUM> may be easily and/or quickly reconfigured for different uses.

In some implementations, as shown, the platform <NUM> may be hosted in a cloud computing environment <NUM>. Notably, while implementations described herein describe the platform <NUM> as being hosted in the cloud computing environment <NUM>, in some implementations, the platform <NUM> may not be cloud-based (i.e., may be implemented outside of a cloud computing environment) or may be partially cloud-based.

The cloud computing environment <NUM> includes an environment that hosts the platform <NUM>. The cloud computing environment <NUM> may provide computation, software, data access, storage, etc. services that do not require end-user (e.g. the user device <NUM>) knowledge of a physical location and configuration of system(s) and/or device(s) that hosts the platform <NUM>. As shown, the cloud computing environment <NUM> may include a group of computing resources <NUM> (referred to collectively as "computing resources <NUM>" and individually as "computing resource <NUM>").

The computing resource <NUM> includes one or more personal computers, workstation computers, server devices, or other types of computation and/or communication devices. In some implementations, the computing resource <NUM> may host the platform <NUM>. The cloud resources may include compute instances executing in the computing resource <NUM>, storage devices provided in the computing resource <NUM>, data transfer devices provided by the computing resource <NUM>, etc. In some implementations, the computing resource <NUM> may communicate with other computing resources <NUM> via wired connections, wireless connections, or a combination of wired and wireless connections.

As further shown in <FIG>, the computing resource <NUM> includes a group of cloud resources, such as one or more applications (APPs) <NUM>-<NUM>, one or more virtual machines (VMs) <NUM>-<NUM>, virtualized storage (VSs) <NUM>-<NUM>, one or more hypervisors (HYPs) <NUM>-<NUM>, or the like.

The application <NUM>-<NUM> includes one or more software applications that may be provided to or accessed by the user device <NUM> and/or the platform <NUM>. The application <NUM>-<NUM> may eliminate a need to install and execute the software applications on the user device <NUM>. For example, the application <NUM>-<NUM> may include software associated with the platform <NUM> and/or any other software capable of being provided via the cloud computing environment <NUM>. In some implementations, one application <NUM>-<NUM> may send/receive information to/from one or more other applications <NUM>-<NUM>, via the virtual machine <NUM>-<NUM>.

The virtual machine <NUM>-<NUM> includes a software implementation of a machine (e.g. a computer) that executes programs like a physical machine. The virtual machine <NUM>-<NUM> may be either a system virtual machine or a process virtual machine, depending upon use and degree of correspondence to any real machine by the virtual machine <NUM>-<NUM>. A system virtual machine may provide a complete system platform that supports execution of a complete operating system (OS). A process virtual machine may execute a single program, and may support a single process. In some implementations, the virtual machine <NUM>-<NUM> may execute on behalf of a user (e.g. the user device <NUM>), and may manage infrastructure of the cloud computing environment <NUM>, such as data management, synchronization, or long-duration data transfers.

The virtualized storage <NUM>-<NUM> includes one or more storage systems and/or one or more devices that use virtualization techniques within the storage systems or devices of the computing resource <NUM>. In some implementations, within the context of a storage system, types of virtualizations may include block virtualization and file virtualization. Block virtualization may refer to abstraction (or separation) of logical storage from physical storage so that the storage system may be accessed without regard to physical storage or heterogeneous structure. The separation may permit administrators of the storage system flexibility in how the administrators manage storage for end users. File virtualization may eliminate dependencies between data accessed at a file level and a location where files are physically stored. This may enable optimization of storage use, server consolidation, and/or performance of non-disruptive file migrations.

The hypervisor <NUM>-<NUM> may provide hardware virtualization techniques that allow multiple operating systems (e.g., "guest operating systems") to execute concurrently on a host computer, such as the computing resource <NUM>. The hypervisor <NUM>-<NUM> may present a virtual operating platform to the guest operating systems, and may manage the execution of the guest operating systems. Multiple instances of a variety of operating systems may share virtualized hardware resources.

The network <NUM> includes one or more wired and/or wireless networks. For example, the network <NUM> may include a cellular network (e.g. a fifth generation (<NUM>) network, a long-term evolution (LTE) network, a third generation (<NUM>) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g. the Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, or the like, and/or a combination of these or other types of networks.

Additionally, or alternatively, a set of devices (e.g. one or more devices) of the environment <NUM> may perform one or more functions described as being performed by another set of devices of the environment <NUM>.

<FIG> is a block diagram of example components of one or more devices of <FIG>. The device <NUM> may correspond to the user device <NUM> and/or the platform <NUM>. As shown in <FIG>, the device <NUM> may include a bus <NUM>, a processor <NUM>, a memory <NUM>, a storage component <NUM>, an input component <NUM>, an output component <NUM>, and a communication interface <NUM>.

The bus <NUM> includes a component that permits communication among the components of the device <NUM>. The processor <NUM> is implemented in hardware, firmware, or a combination of hardware and software. The processor <NUM> is a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or another type of processing component. In some implementations, the processor <NUM> includes one or more processors capable of being programmed to perform a function. The memory <NUM> includes a random access memory (RAM), a read only memory (ROM), and/or another type of dynamic or static storage device (e.g. a flash memory, a magnetic memory, and/or an optical memory) that stores information and/or instructions for use by the processor <NUM>.

The storage component <NUM> stores information and/or software related to the operation and use of the device <NUM>. For example, the storage component <NUM> may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and/or a solid state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and/or another type of non-transitory computer-readable medium, along with a corresponding drive.

The input component <NUM> includes a component that permits the device <NUM> to receive information, such as via user input (e.g. a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and/or a microphone). Additionally, or alternatively, the input component <NUM> may include a sensor for sensing information (e.g. a global positioning system (GPS) component, an accelerometer, a gyroscope, and/or an actuator). The output component <NUM> includes a component that provides output information from the device <NUM> (e.g. a display, a speaker, and/or one or more light-emitting diodes (LEDs)).

The communication interface <NUM> includes a transceiver-like component (e.g., a transceiver and/or a separate receiver and transmitter) that enables the device <NUM> to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. The communication interface <NUM> may permit the device <NUM> to receive information from another device and/or provide information to another device. For example, the communication interface <NUM> may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, or the like.

The device <NUM> may perform one or more processes described herein. The device <NUM> may perform these processes in response to the processor <NUM> executing software instructions stored by a non-transitory computer-readable medium, such as the memory <NUM> and/or the storage component <NUM>. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.

Software instructions may be read into the memory <NUM> and/or the storage component <NUM> from another computer-readable medium or from another device via the communication interface <NUM>. When executed, software instructions stored in the memory <NUM> and/or the storage component <NUM> may cause the processor <NUM> to perform one or more processes described herein.

In practice, the device <NUM> may include additional components, fewer components, different components, or differently arranged components than those shown in <FIG>. Additionally, or alternatively, a set of components (e.g., one or more components) of the device <NUM> may perform one or more functions described as being performed by another set of components of the device <NUM>.

A <NUM> media streaming (5GMS) system may be an assembly of application functions, application servers, and interfaces from the <NUM> media streaming architecture that support either downlink media streaming services or uplink media streaming services, or both. A 5GMS Application Provider may include a party that interacts with functions of the 5GMS system and supplies a 5GMS Aware Application that interacts with functions of the 5GMS system. The 5GMS Aware Application may refer to an application in the user equipment (UE), provided by the 5GMS Application Provider, that contains the service logic of the 5GMS application service, and interacts with other 5GMS Client and Network functions via the interfaces and application programming interfaces (APIs) defined in the 5GMS architecture. A 5GMS Client may refer to a UE function that is either a 5GMS downlink (SGMSd) Client or a 5GMS uplink (5GMSu) Client, or both.

The 5GMSd Client may refer to a UE function that includes at least a <NUM> media streaming player and a media session handler for downlink streaming and that may be accessed through well-defined interfaces/APIs. The 5GMSu Client may refer to an originator of a 5GMSu service that may be accessed through well-defined interfaces/APIs. A 5GMSu media streamer may refer to a UE function that enables uplink delivery of streaming media content to an Application Server (AS) function of the 5GMS Application Provider, and which interacts with both the 5GMSu Aware Application for media capture and subsequent streaming, and the Media Session Handler for media session control.

A dynamic policy may refer to a dynamic policy and charging control (PCC) rule for an uplink or downlink application flow during a media session. An egest session may refer to an uplink media streaming session from the 5GMS AS towards the 5GMSu Application Provider. An ingest session may refer to a session to upload the media content to a 5GMSd AS. A policy template may refer to a collection of (semi-static) Policy or Control Function (PCF)/Network Exposure Function (NEF) API parameters which are specific to the 5GMS Application Provider and also the resulting PCC rule. A policy template ID may identify the desired policy template, which is used by the 5GMSd Application Function (AF) to select the appropriate PCF/NEF API towards the <NUM> system so that the PCF can compile the desired PCC rule. The Media Player Entry may refer to a document or a pointer to a document that defines a media presentation (e.g., a media presentation description (MPD) for DASH or a uniform resource locator (URL) to a video clip file). A Media Streamer Entry may refer to a pointer (e.g., in the form of a URL) that defines an entry point of an uplink media streaming session. A presentation entry may refer to a document or a pointer to a document that defines an application presentation, such as an HTML5 document.

A Provisioning Session may refer to a data structure supplied at an interface (M1d) by a 5GMSd Application provider that configures the 5GMSd features relevant to a set of 5GMSd Aware Applications. A 5GMSd Media Player may refer to a UE function that enables playback and rendering of a media presentation based on a media play entry and exposing some basic controls such as play, pause, seek, and stop, to the 5GMSd Aware Application. Server Access Information may refer to a set of parameters and addresses (including 5GMSd AF and 5GMSd AS addresses) which are needed to activate the reception of a streaming session. A Service and Content Discovery may refer to functionality and procedures provided by a 5GMSd Application Provider to a 5GMS Aware Application that enables the end user to discover the available streaming service and content offerings and select a specific service or content item for access. A Service Announcement may refer to procedures conducted between the 5GMS Aware Application and the 5GMS Application Provider such that the 5GMS Aware Application is able to obtain 5GMS Service Access Information, either directly or in the form of a reference to that information.

A third party player may refer to a part of an application that uses APIs to exercise selected 5GMSd functions to play back media content. A third party uplink streamer may refer to a part of an application that uses APIs to exercise selected 5GMSu functions to capture and stream media content.

<FIG> is a diagram of a media architecture <NUM> for media uplink streaming according to embodiments. A 5GMSu Application Provider <NUM> may use 5GMSu for uplink streaming services. 5GMSu Application provider <NUM> may provide a 5GMSu Aware Application <NUM> on the UE <NUM> to make use of 5GMSu Client <NUM> and network functions using interfaces and APIs defined in 5GMSu. 5GMSu AS may be an AS dedicated to <NUM> Media Uplink Streaming. 5GMSu Client <NUM> may be a UE <NUM> internal function dedicated to <NUM> Media Uplink Streaming.

5GMSu AF <NUM> and 5GMSu AS <NUM> may be Data Network (DN) <NUM> functions. Functions in trusted DNs may be trusted by the operator's network. Therefore, AFs in trusted DNs may directly communicate with all <NUM> Core functions. Functions in external DNs may only communicate with <NUM> Core functions via the NEF <NUM> using link <NUM>.

The media architecture <NUM> may connect UE <NUM> internal functions and related network functions for <NUM> Media Uplink Streaming. Accordingly, media architecture <NUM> may include a number of functions. For example, 5GMSu Client <NUM> on UE <NUM> may be an originator of 5GMSu service that may be accessed through interfaces/APIs. 5GMSu Client <NUM> may include two sub-functions, media session handler <NUM> and media streamer <NUM>. Media session handler <NUM> may communicate with the 5GMSu AF <NUM> in order to establish, control and support the delivery of a media session. The Media Session Handler <NUM> may expose APIs that can be used by the 5GMSu Aware Application <NUM>. Media Streamer <NUM> may communicate with 5GMSu AS <NUM> in order to stream the media content and provide a service to the 5GMSu Aware Application <NUM> for media capturing and streaming, and the Media Session Handler <NUM> for media session control. 5GMSu Aware Application <NUM> may control 5GMSu Client <NUM> by implementing external application or content service provider specific logic and enabling the establishment of a media session. 5GMSu AS <NUM> may host <NUM> media functions and may be implemented as a content delivery network (CDN), for example. 5GMSu Application Provider <NUM> may be an external application or content specific media functionality, e.g., media storage, consumption, transcoding and redistribution that uses 5GMSu to stream media from 5GMSu Aware Application <NUM>. 5GMSu AF <NUM> may provide various control functions to the Media Session Handler <NUM> on the UE <NUM> and/or to 5GMSu Application Provider <NUM>. 5GMSu AF <NUM> may relay or initiate a request for different PCF <NUM> treatment or interact with other network functions.

Media architecture <NUM> may include a number of different interfaces. For example, link <NUM> may relate to M1u, which may be a 5GMSu Provisioning API exposed by 5GMSu AF <NUM> to provision usage of media architecture <NUM> and to obtain feedback. Link <NUM> may relate to M2u, which may be a 5GMSu Publish API exposed by 5GMSu AS <NUM> and used when 5GMSu AS <NUM> in trusted DN, such as DN <NUM>, is selected to receive content for streaming service. Link <NUM> may relate to M3u, which may be an internal API used to exchange information for content hosting on 5GMSu AS <NUM> within a trusted DN such as DN <NUM>. Link <NUM> may relate to M4u, which may be a Media Uplink Streaming API exposed by 5GMSu AS <NUM> to Media Streamer <NUM> to stream media content. Link <NUM> may relate to M5u, which may be a Media Session Handling API exposed by 5GMSu AF <NUM> to Media Session Handler for media session handling, control and assistance that also include appropriate security mechanisms e.g. authorization and authentication. Link <NUM> may relate to M6u, which may be a UE <NUM> Media Session Handling API exposed by Media Session Handler <NUM> to 5GMSu Aware Application <NUM> to make use of 5GMSu functions. Link <NUM> may relate to M7u, which may be a UE Media Streamer API exposed by Media Streamer <NUM> to 5GMSu Aware Application <NUM> and Media Session Handler <NUM> to make use of Media Streamer <NUM>. Link <NUM> may relate to M8u, which may be an Application API which is used for information exchange between 5GMSu Aware Application <NUM> and 5GMSu Application Provider <NUM>, for example to provide service access information to the 5GMSu Aware Application <NUM>. The UE <NUM> may also be implemented in a self-contained manner such that interfaces M6u <NUM> and M7u <NUM> are not exposed.

<FIG> is a diagram of a media architecture <NUM> for media downlink streaming, according to embodiments. A 5GMSd Application Provider <NUM> may use 5GMSd for downlink streaming services. 5GMSd Application provider <NUM> may provide a 5GMSd Aware Application <NUM> on the UE <NUM> to make use of 5GMSd Client <NUM> and network functions using interfaces and APIs defined in 5GMSd. 5GMSd AS may be an AS dedicated to <NUM> Media Downlink Streaming. 5GMSd Client <NUM> may be a UE <NUM> internal function dedicated to <NUM> Media Downlink Streaming.

5GMSd AF <NUM> and 5GMSd AS <NUM> may be DN <NUM> functions. Functions in trusted DNs may be trusted by the operator's network. Therefore, AFs in trusted DNs may directly communicate with all <NUM> Core functions. Functions in external DNs may only communicate with <NUM> Core functions via the NEF <NUM> using link <NUM>.

The media architecture <NUM> may connect UE <NUM> internal functions and related network functions for <NUM> Media Downlink Streaming. Accordingly, media architecture <NUM> may include a number of functions. For example, 5GMSd Client <NUM> on UE <NUM> may be a receiver of 5GMSd service that may be accessed through interfaces/APIs. 5GMSd Client <NUM> may include two sub-functions, media session handler <NUM> and media Player <NUM>. Media session handler <NUM> may communicate with the 5GMSd AF <NUM> in order to establish, control and support the delivery of a media session. The Media Session Handler <NUM> may expose APIs that can be used by the 5GMSd Aware Application <NUM>. Media Player <NUM> may communicate with 5GMSd AS <NUM> in order to stream the media content and provide a service to the 5GMSd Aware Application <NUM> for media playback, and the Media Session Handler <NUM> for media session control. 5GMSd Aware Application <NUM> may control 5GMSd Client <NUM> by implementing external application or content service provider specific logic and enabling the establishment of a media session. 5GMSd AS <NUM> may host <NUM> media functions. 5GMSd Application Provide <NUM> may be an external application or content specific media functionality, e.g., media creation, encoding, and formatting that uses 5GMSd to stream media to 5GMSd Aware Application <NUM>. 5GMSd AF <NUM> may provide various control functions to the Media Session Handler <NUM> on the UE <NUM> and/or to 5GMSd Application Provider <NUM>. 5GMSd AF <NUM> may relay or initiate a request for different PCF <NUM> treatment or interact with other network functions.

Media architecture <NUM> may include a number of different interfaces. For example, link <NUM> may relate to M1d, which may be a 5GMSd Provisioning API exposed by 5GMSd AF <NUM> to provision usage of media architecture <NUM> and to obtain feedback. Link <NUM> may relate to M2d, which may be a 5GMSd Ingest API exposed by 5GMSd AS <NUM> and used when 5GMSd AS <NUM> in trusted DN, such as DN <NUM>, is selected to receive content for streaming service. Link <NUM> may relate to M3d, which may be an internal API used to exchange information for content hosting on 5GMSd AS <NUM> within a trusted DN such as DN <NUM>. Link <NUM> may relate to M4d, which may be a Media Downlink Streaming API exposed by 5GMSd AS <NUM> to Media Player <NUM> to stream media content. Link <NUM> may relate to M5d, which may be a Media Session Handling API exposed by 5GMSd AF <NUM> to Media Session Handler for media session handling, control and assistance that also include appropriate security mechanisms e.g. authorization and authentication. Link <NUM> may relate to M6d, which may be a UE <NUM> Media Session Handling API exposed by Media Session Handler <NUM> to 5GMSd Aware Application <NUM> to make use of 5GMSd functions. Link <NUM> may relate to M7d, which may be a UE Media Player API exposed by Media Player <NUM> to 5GMSd Aware Application <NUM> and Media Session Handler <NUM> to make use of Media Player <NUM>. Link <NUM> may relate to M8d, , which may be an Application API which is used for information exchange between 5GMSd Aware Application <NUM> and 5GMSd Application Provider <NUM>, for example to provide service access information to the 5GMSd Aware Application <NUM>.

<FIG> and <FIG> are diagrams of an edge dependent augmented reality (AR) (EDGAR) 5GMSd download architecture <NUM>, according to embodiments. The AR EDGAR 5GMSd architecture <NUM> may be applied to mixed reality (MR) as well. The architecture <NUM> includes a <NUM> EDGAR UE <NUM>, a cloud/edge server <NUM> and an AR/MR application provider <NUM>. The <NUM> EDGAR UE <NUM> includes an AR runtime <NUM>, a lightweight scene manager <NUM>, a 5GMS client <NUM> and a basic AR/MR application <NUM>. The AR runtime <NUM> includes a vision engine/simultaneous localization and mapping (SLAM) <NUM>, a pose correction module <NUM>, and a soundfield mapping module <NUM>. The lightweight scene manager <NUM> includes a basic scene graph handler (SGH) <NUM> and a compositor <NUM>. The 5GMS client <NUM> includes a media session handler (including an edge session) <NUM> and a media client <NUM>. The media client <NUM> includes a scene description delivery module <NUM>, a content delivery module <NUM> and basic codecs <NUM>. The <NUM> EDGAR UE <NUM> includes a <NUM> lightweight system (Uu) <NUM> that is in communication with a <NUM> system (gNb) <NUM> of the cloud/edge server <NUM>.

The cloud/edge server <NUM> includes an AR/MR application <NUM> and media delivery functions <NUM>. The media delivery functions <NUM> include a media AF <NUM> and a media AS <NUM>. The media AS <NUM> includes a content delivery function <NUM>, a scene description function (SDF) <NUM>, decoders <NUM> and encoders <NUM>. The AR/MR application <NUM> includes an AR scene manager <NUM>, AR functions <NUM>, a semantical perception module <NUM>, a social integration module <NUM>, and a media assets database <NUM>. The AR scene manager <NUM> includes a scene graph generator <NUM>, an immersive visual renderer <NUM> and an immersive audio renderer <NUM>.

The AR/MR application provider <NUM> includes an immersive media server <NUM>. The immersive media server <NUM> includes a scene description module <NUM>, a manifest server <NUM>, and a segment server <NUM>.

The media client <NUM> transmits to the content delivery functions <NUM> by an M4 interface <NUM> (e.g., transmitting pose and interactions). The content delivery functions <NUM> transmits to the media client <NUM> by an M4 interface <NUM> (e.g., transmitting pre-rendered media). The media session handler <NUM> is in communication with the media AF <NUM> by an M5d interface <NUM>. The basic AR/MR application <NUM> is in communication with the AR/MR application <NUM> by an M8 interface <NUM>. The basic AR/MR application <NUM> may receive a user input <NUM> and AR data <NUM> from the AR runtime <NUM>. The AR runtime <NUM> may receive data from cameras <NUM> and sensors <NUM>, and may output data to a display <NUM> and to speakers <NUM>.

According to embodiments, the SCH <NUM> of the UE <NUM> may be capable of parsing a full scene graph (FSG) provided by the AR/MR application <NUM>. The SCH <NUM> may provide a scene description with a list of media components and their description to the AR/MR application <NUM>. The AR/MR application <NUM> selects a subset/list of media components from the FSG and provides the subset of media components to the SDF <NUM>. The SDF <NUM> is configured to generate a simplified scene graph (SSG) from the FSG by combining one or more media components and reducing the number of notes in the FSG. The SDF <NUM> is also configured to arrange the media decoders <NUM> and the media encoders <NUM> and the content delivery function <NUM> on the edge to prepare the corresponding media components used in the SSG. The SSG may be delivered to the UE <NUM>. The SCH <NUM> of the UE <NUM> is configured to parse and provide the SSG to the compositor <NUM> of the UE <NUM>. The compositor <NUM> is configured to compose simple scene graphs, such as the SSG. The UE <NUM> is configured to stream the necessary media components from the content delivery function <NUM>, and the UE <NUM> is configured to decode and compose the media components in the simplified scene.

Based on the FSG being updated during the media session, the system according to embodiments includes two capabilities. First, based on the SDF <NUM> being configured to convert the updated FSG to an updated SSG without losing any updates, the SDF <NUM> generates the updated SSG and delivers the updated SSG to the UE <NUM>. Based on the FSG updated being beyond the current features of the SSG, the AR/MR application <NUM> may be informed about the FSG update. Then, the AR/MR application <NUM> is configured to select a new subset of media components from the FSG. Based on the new subset being the same as the previous selection, no scene update is needed. Based on the new subset including new media components or a modification of existing media components, the AR/MR application <NUM> informs the SDF <NUM> of the new subset. Based on the received new media subset, the SDF <NUM> is configured to generate a new SSG from the updated FSG and provide the new SSG to the UE <NUM>. The SDF <NUM> is also configured to rearrange the media decoders <NUM>, the media encoders <NUM> and the content delivery functions <NUM> on the cloud/edge server <NUM> to prepare the corresponding media components used in the updated SSG. The SCH <NUM> of the UE <NUM> is configured to parse the updated SSG, and is configured to stream the corresponding media component, compose the media component and play the composition.

<FIG>, <FIG>, <FIG> and <FIG> are diagrams of an operation flow for EDGAR-based <NUM> downlink streaming, according to embodiments. The system performing the operation flow of <FIG> may include a basic AR/MR application <NUM>, an AR runtime <NUM>, a lightweight scene manager <NUM>, a media client <NUM>, and a media session handler <NUM>, which may be part of the EDGAR UE <NUM> (furthermore, the media client <NUM> and the media session handler <NUM> may be part of the media access functions). The system also includes a 5GMSd AF/EES <NUM>, a 5GMSd AS/ edge application server (EAS) <NUM>, and an AR/MR application <NUM>, which may be part of the cloud/edge server <NUM>. The system may also include an AR/MR application provider <NUM>.

In operation <NUM>, the system provides a service announcement and content discovery. The service announcement may be triggered by the AR/MR application <NUM>. The service access information may include a media player entry or a reference to the service access information and may be provided through the M8d interface. In operation <NUM>, the system selects the desired media content. In operation <NUM>, the system initiates media playback. The AR/MR application <NUM> may trigger the media session handler <NUM> to start the media playback, and the media player entry may be provided to the media client <NUM>. In operation <NUM>, the system performs service access information acquisition. When the AR/MR application <NUM> has received only a reference to the service access information, the media session handler <NUM> interacts with the 5GMSd AF <NUM> to acquire the whole service access information. In operation <NUM>, the AR/MR application <NUM> discovers the 5GMSd AS's with desired edge capabilities. In operation <NUM>, the system provides a list of available 5GMSd AS/EAS(s).

In operation <NUM>, the AR/MR application <NUM> and the media session handler <NUM> select the most suitable 5GMSd AS. In operation <NUM>, the AR/MR application <NUM>, through the lightweight scene manager <NUM> and the media client <NUM>, provides the initial scene parameters. In operation <NUM>, the 5GMSd AS <NUM> provides a new entry point for the SSG. Alternatively, the AR/MR application provider <NUM> may select or instantiate the 5GMSd for running the AR/MR edge application <NUM>, such that operations <NUM>, <NUM> and <NUM> may be omitted. In operation <NUM>, the AR/MR application <NUM> requests the scene manager <NUM> to play the SSG entry point.

In operation <NUM>, the system provides the simplified scene entry point to the media client <NUM>. In operation <NUM>, the system establishes a transport session for the entry point. In operation <NUM>, the system requests the entry point from the 5GMSd AS <NUM>. In operation <NUM>, the system confirms the request. In operation <NUM>, the system processes the entry point <NUM>. In operation <NUM>, the system provides an entry point receive notification to the media session handler <NUM>. In operation <NUM>, the system configures the quality of service (QoS) for the required streaming sessions. In operation <NUM>, the system establishes transport sessions for delivery manifest(s). In operation <NUM>, the system requests delivery manifest(s) from the 5GMSd AS <NUM>. In operation <NUM>, the system confirms the delivery manifest(s) request.

In operation <NUM>, the system processes the delivery manifest(s). In operation <NUM>, the system provides the delivery manifest(s) receive notification to the media session handler <NUM>. In operation <NUM>, the system captures media pipelines. In operation <NUM>, the system establishes transport sessions for content. In operation <NUM>, the system provides a notification of the transport sessions to the media session handler <NUM>. In operation <NUM>, the system requests from the 5GMSd AS <NUM> pre-rendered media and pose information. In operation <NUM>, the system renders a two-dimensional view. In operation <NUM>, the system provides the pre-rendered media to the media client <NUM>. In operation <NUM>, the system decodes and processes the media data.

In operation <NUM>, the media client <NUM> provides media data to the lightweight scene manager <NUM>. In operation <NUM>, the system performs composition, pose correction, and media rendering. In operation <NUM>, the AR/MR application provider <NUM> provides a full scene update to the 5GMSd AS <NUM>. In operation <NUM>, the system provides a simplified scene update.

<FIG> and <FIG> are diagrams of an operation flow for EDGAR-based <NUM> downlink streaming, according to embodiments. The system performing the operation flow of <FIG> may include a basic AR/MR application <NUM>, an AR runtime <NUM>, a lightweight scene manager <NUM>, a media client <NUM>, and a media session handler <NUM>, which may be part of the EDGAR UE <NUM> (furthermore, the media client <NUM> and the media session handler <NUM> may be part of the media access functions). The system also includes a 5GMSd AF/EES <NUM>, a 5GMSd AS/EAS <NUM>, and an AR/MR application <NUM>, which may be part of the cloud/edge server <NUM>. The system may also include an AR/MR application provider <NUM>.

In operation <NUM>, the system provides a service announcement and content discovery. The service announcement may be triggered by the AR/MR application <NUM>. The service access information may include a media player entry or a reference to the service access information and may be provided through the M8d interface. In operation <NUM>, the system selects the desired media content. In operation <NUM>, the system initiates media playback. The AR/MR application <NUM> may trigger the media session handler <NUM> to start the media playback, and the media player entry may be provided to the media client <NUM>. In operation <NUM>, the system performs service access information acquisition. When the AR/MR application <NUM> has received only a reference to the service access information, the media session handler <NUM> interacts with the 5GMSd AF <NUM> to acquire the whole service access information.

In operation <NUM>, the system requests the FSG. Given the media entry point, the AR/MR application <NUM> may request the full scene description through the scene manager <NUM>. In operation <NUM>, the system selects initial scene components. That is, the AR/MR application <NUM> selects the initial scene components and derives the required edge capabilities. In operation <NUM>, the AR/MR application <NUM> discovers the 5GMSd AS's with desired edge capabilities. In operation <NUM>, the system provides a list of available 5GMSd AS/EAS(s). In operation <NUM>, the system provides a list of available 5GMSd AS/EAS(s). In operation <NUM>, the AR/MR application <NUM> and the media session handler <NUM> select the most suitable 5GMSd AS. In operation <NUM>, the AR/MR application <NUM>, through the lightweight scene manager <NUM> and the media client <NUM>, provides the initial scene parameters. In operation <NUM>, the 5GMSd AS <NUM> provides a new entry point for the SSG. In operation <NUM>, the AR/MR application <NUM> requests the scene manager <NUM> to play the SSG entry point.

<FIG> is a diagram of an operation flow for an EDGAR-based procedure for scene updating, according to embodiments. In operation <NUM>, the AR/MR application provider <NUM> proves a full scene update during the streaming. In operation <NUM>, the 5GMSd AS <NUM> checks if a simplified scene update is possible. Based on the simplified scene update being possible, in operation <NUM>, the 5GMSd AS <NUM> updates the simplified scene and provides the simplified scene to the scene manager <NUM> of the UE <NUM>.

Based on the simplified scene update not being possible, the system performs operations <NUM>-<NUM>. In operation <NUM>, the 5GMDs AS <NUM> provides the full scene update to the AR/MR application <NUM>. In operation <NUM>, the AR/MR application <NUM> selects the initial scene components. In operation <NUM>, the AR/MR application <NUM> provides the selected components to the 5GMSd AS <NUM>. In operation <NUM>, the 5GMSd AS <NUM> generates the updated simplified scene and provides the updated simplified scene to the scene manager <NUM> of the UE <NUM>.

<FIG> is a flowchart of a process for EDGAR-based <NUM> downlink streaming, according to embodiments. In operation <NUM>, the system selects, with an AR/MR application, media content for playback. In operation <NUM>, the system discovers, with the AR/MR application, at least one 5GMSd AS with edge capabilities suitable for playback of the selected media content. In operation <NUM>, the system selects, with the AR/MR application, the at least one 5GMSd AS for playback of the selected media content. In operation <NUM>, the system requests, with the AR/MR application, playback of the selected media content by the selected at least one 5GMSd AS.

Thus, according to embodiments, the AR/MR application receives the FSGs and make a decision on which components of the scene graphs should be streamed (i.e., the AR/MR application is not just provided with a SSG). The edge resources are requested based on the processing needs of converting the FSG and its media components to the SSG and its media components. The updates on the FSGs may be handled depending on the extensiveness of the update. If the update can be implemented with an update to the SSG, the update occurs in the edge/cloud server. Otherwise, the FSG update is provided to the AR/MR application, and the AR/MR application may make a selection from the updated FSG. Thus, an updated SSG is generated according to the AR/MR application selection.

Further, the proposed methods 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 to perform one or more of the proposed methods.

The techniques described above can be implemented as computer software using computer-readable instructions and physically stored in one or more computer-readable media.

Embodiments of the present disclosure may be used separately or combined in any order. Further, each of the embodiments (and methods thereof) 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.

The scope of protection of the invention is defined by the appended claims.

Claim 1:
A method (<NUM>) for providing an augmented reality, AR/mixed reality, MR applications to <NUM> devices comprising:
selecting (<NUM>), with the AR/MR, application, media content for playback;
discovering (<NUM>), with the AR/MR application, at least one <NUM>th Generation media streaming downlink, 5GMSd, application server, AS, with edge capabilities suitable for playback of the selected media content;
selecting (<NUM>), with the AR/MR application, the at least one 5GMSd AS for playback of the selected media content;
requesting (<NUM>), with the AR/MR application, playback of the selected media content by the selected at least one 5GMSd AS; the method characterized by:
receiving, with the selected at least one 5GMSd AS, a full scene update from an AR/MR application provider;
determining, with the selected at least one 5GMSd AS, whether a simplified scene of the selected media content is updatable; and
based on determining that the simplified scene of the selected media content is updatable, providing, with the selected at least one 5GMSd AS, a simplified scene update based on the full scene update.