Techniques for facilitating cloud-based vehicle XR experience

Abstract

Apparatuses, methods, and computer-readable media for facilitating a cloud-based vehicle XR user experience are disclosed herein. An example method for wireless communication at a user equipment (UE) includes sending a request for a vehicle augmented reality (XR) session. The vehicle XR session may be based on a first user XR stream that includes a vehicle XR component associated with the vehicle and a first user XR component associated with the first user. The first user may have an association with the vehicle. The example method also includes transmitting uplink information associated with the first user XR flow. The example method also includes receiving rendering information associated with the first user XR stream. The rendering information may be based on the uplink information.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 17 / 811,578, filed on July 8, 2022, and entitled “TECHNIQUES TO FACILITATE ACLOUD-BASED VEHICLE XR EXPERIENCE,” which is expressly incorporated herein by reference in its entirety. Background Art

[0003] The present disclosure relates generally to communication systems, and more particularly to wireless communications associated with extended reality (XR) services.

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] The following presents a summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive review of all envisioned aspects. This summary is neither intended to identify the key or important elements of all aspects, nor to describe the scope of any or all aspects. Its only purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method of wireless communication at a user equipment (UE) is provided. The method may include sending a request for a vehicle extended reality (XR) session based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle. The example method may also include sending uplink information associated with the first user XR stream. The example method may also include receiving rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

[0008] In another aspect of the present disclosure, a device for wireless communication is provided. The device may be a UE including a memory and at least one processor coupled to the memory, the at least one processor being configured to send a request for a vehicle XR session based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle. The at least one processor may also be configured to send uplink information associated with the first user XR stream. The at least one processor may also be configured to receive rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

[0009] In another aspect of the present disclosure, an apparatus for wireless communication at a UE is provided. The apparatus may include a component for sending a request for a vehicle XR session based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle. The example apparatus may also include a component for sending uplink information associated with the first user XR stream. The example apparatus may also include a component for receiving rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

[0010] In another aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer-executable code for wireless communication at a UE is provided. The code, when executed, may cause a processor to send a request for a vehicle XR session based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle. The example code, when executed, may also cause the processor to send uplink information associated with the first user XR stream. The example code, when executed, may also cause the processor to receive rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

[0011] In one aspect of the present disclosure, a method for wireless communication at a network entity is provided. The method may include: obtaining a request for a vehicle XR session. The method may also include: authorizing the vehicle XR session, the vehicle XR session based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle. The example method may also include: obtaining uplink information associated with the first user XR stream. Additionally, the example method may include: outputting rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

[0012] In another aspect of the present disclosure, a device for wireless communication is provided. The device may be a base station including a memory and at least one processor coupled to the memory, the at least one processor being configured to obtain a request for a vehicle XR session. The at least one processor may also be configured to authorize the vehicle XR session, the vehicle XR session being based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle. The at least one processor may also be configured to obtain uplink information associated with the first user XR stream. Additionally, the at least one processor may be configured to output rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

[0013] In another aspect of the present disclosure, an apparatus for wireless communication at a base station is provided. The apparatus may include a component for obtaining a request for an associated vehicle XR session. The apparatus may also include a component for authorizing the vehicle XR session, the vehicle XR session being based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle. The example apparatus may also include a component for obtaining uplink information associated with the first user XR stream. Additionally, the example apparatus may include a component for outputting rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

[0014] In another aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer executable code for wireless communication at a base station is provided. The code, when executed, may cause a processor to obtain a request for a vehicle XR session. The example code, when executed, may also cause the processor to authorize the vehicle XR session, the vehicle XR session being based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle. The example code, when executed, may also cause the processor to obtain uplink information associated with the first user XR stream. Additionally, the example code, when executed, may cause the processor to output rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

[0015] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0017] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0018] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

[0019] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0020] Figure 2Dis a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0021] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0022] Figure 4 is a diagram illustrating an example decomposed base station architecture according to the teachings disclosed herein.

[0023] Figure 5 is a diagram illustrating an example vehicle configured with a vehicle XR system in accordance with the teachings disclosed herein.

[0024] Fig. 6A is a diagram illustrating an example XR scene according to the teachings disclosed herein.

[0025] Figure 6B is a diagram illustrating an example scene including real-world objects according to the teachings disclosed herein.

[0026] Figure 6C is a diagram illustrating an example XR scene including virtual objects superimposed on real-world objects in accordance with the teachings disclosed herein.

[0027] Figure 7 is an example communication flow between a network entity, a UE, and a cloud XR entity according to the teachings disclosed herein.

[0028] Figure 8 is an example communication flow between a network entity and a UE according to the teachings disclosed herein.

[0029] Fig. 9 is an example communication flow between a network entity and a UE according to the teachings disclosed herein.

[0030] Fig.10 is a diagram illustrating example collected information exchanged with network entities according to the teachings disclosed herein.

[0031] Fig.11 is an example communication flow between a network entity and a UE according to the teachings disclosed herein.

[0032] Fig.12 is an example communication flow between a network entity and a UE according to the teachings disclosed herein.

[0033] Fig.13 is an example communication flow between a network entity and a UE according to the teachings disclosed herein.

[0034] Fig.14is an example communication flow between a network entity and a UE according to the teachings disclosed herein.

[0035] Fig.15 is an example communication flow between a network entity, a UE, and a service entity according to the teachings disclosed herein.

[0036] Fig.16 is a flow chart of a method of wireless communication at a UE according to the teachings disclosed herein.

[0037] Fig.17 is a flow chart of a method of wireless communication at a UE according to the teachings disclosed herein.

[0038] Fig.18 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0039] Fig.19 is a flow chart of a method of wireless communication at a network entity according to the teachings disclosed herein.

[0040] Fig. 20 is a flow chart of a method of wireless communication at a network entity according to the teachings disclosed herein.

[0041] Fig.21 is a diagram illustrating an example of a hardware implementation for an example network entity.

[0042] Fig. 22 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0043] Extended reality (XR) refers to the reality-virtual continuum between the real environment and the virtual environment. Extended reality technology can provide virtual content to users and / or combine the real or physical environment with the virtual environment (which can be composed of virtual content or virtual objects) to provide users with XR experiences. XR experiences can include virtual reality (VR), augmented reality (AR), mixed reality (MR), and / or other immersive content.

[0044] A user may experience XR via an XR device (e.g., may be provided with an XR experience). Extended reality devices may have different form factors and may differ in processing power, power consumption, and / or communication type. An example of an XR device is a head mounted display (HMD). The HMD may include a display positioned in front of one or both eyes. The display may stream data, images, and / or other information in front of the user's eyes.

[0045] The HMD may include an optical system such as a display and / or lens, one or more tracking sensors, one or more cameras, communication functionality, and an XR engine. The XR engine may perform XR-related processing and may include one or more graphics processing units (GPUs), central processing units (CPUs), etc. The display of the HMD may be transparent or opaque. For example, for AR applications, the display may be transparent (or mostly transparent) and AR information may be superimposed on real-life objects. In another example, for VR applications, the display may not be transparent, and virtual information and images may be displayed in front of the user's eyes.

[0046] An example application of XR is associated with a vehicle. For example, a vehicle may be configured with an XR system that provides a vehicle-based XR experience to the user of the vehicle. The vehicle may include land vehicles such as cars, buses, trains, etc., or air / non-land vehicles such as drones, balloons, airplanes, helicopters, etc. The user of the vehicle may be a person, a device with artificial intelligence, a communication equipment that supports remote access, or a connected controller. The XR system of the vehicle may have a different form factor from the HMD, but may include one or more similar components. For example, the vehicle XR system may include one or more displays for rendering information, one or more sensors for collecting information at the vehicle, and a UE that facilitates communication functions and XR-based processing. As used herein, a UE associated with a vehicle and configured to provide a vehicle-based XR experience may be referred to herein as a "vehicle UE", "vehicle XR system UE", or may be generally referred to as a "UE".

[0047] As an example of a vehicle XR application, a navigation system of a vehicle may enable a user (e.g., a driver, a first passenger, etc.) to input a desired destination and generate a path plan (e.g., a route) to reach the desired destination. One or more sensors may capture vehicle surrounding information of an area around the vehicle. The vehicle UE may then process the vehicle surrounding information and generate rendering information accordingly. One or more displays of the vehicle XR system may then display the rendering information. For example, the rendering information may include enhanced information superimposed on real-world objects around the vehicle. Non-limiting examples of real-world objects around the vehicle may include traffic lights, hazard signs, road signs, roadblocks, landmarks, buildings, billboards, etc. The enhanced information may include driver assistance information such as the current speed of the vehicle, speed limit, gasoline-related or battery-related information, upcoming direction, traffic light phase information, information about potential manipulations of surrounding vehicles and vulnerable road users (VRUs), road conditions, etc.

[0048] In some examples, the augmented information presented to the user may be based on content that the vehicle UE is able to identify and then present via one or more displays. That is, the augmented information may be based on a static or locally processed mechanism. Examples of static or locally processed mechanisms may be based on preconfigured information stored at the vehicle UE. For example, the vehicle UE may be configured with augmented information corresponding to navigation, such as an indicator of a speed limit associated with a street or highway. In some such examples, the vehicle UE may identify real-world objects, such as street signs, based on information provided by one or more sensors of the vehicle XR system. According to one or more examples, the vehicle UE may then display augmented information indicating a speed limit associated with the street based on the identified street sign.

[0049] In some examples, augmented information may be generated and displayed via one or more displays of the vehicle XR system regardless of where the driver or user is looking. For example, a display associated with the front windshield of a vehicle may display augmented information indicating a speed limit when the driver is looking out of a side window of the vehicle. In such examples, the UE may be using resources (e.g., processing resources, memory, etc.) to generate and present augmented information with certain default configurations. Additionally, in some examples, the augmented information presented in the XR scene may be limited to what objects the UE is able to identify and / or may be limited to information provided by another system of the vehicle, such as a navigation system.

[0050] However, it is understandable that as more complex vehicle XR operation scenarios emerge, static or local processing-based mechanisms (or systems) may be less suitable and / or less effective for providing a satisfactory user experience. For example, a static or local processing-based mechanism of a vehicle XR system may not have the ability to identify landmarks in real time (or near real time). In some examples, static or local processing-based mechanisms may provide inaccurate augmented information. For example, a vehicle UE may be configured with augmented information associated with a first landmark that has been replaced by a second landmark since the vehicle UE was configured. For example, when the vehicle UE is configured with augmented information associated with an intersection, the augmented information may include additional information about a clothing store. However, after the vehicle UE is configured with the augmented information, the clothing store may have been replaced by a coffee shop.

[0051] The various aspects disclosed herein facilitate vehicle XR applications including cloud-based processing. For example, the various aspects disclosed herein enable offloading of some processing associated with presenting enhanced information to a cloud XR entity. The cloud XR entity may communicate with a vehicle UE of a vehicle XR system. The cloud XR entity may receive information collected from the vehicle UE via one or more sensors of the vehicle XR system. The cloud XR entity may then help determine what rendering information is needed to support the vehicle XR application at the vehicle and provide a satisfactory user experience (e.g., an XR experience that the user may appreciate). The rendering information may include associated with the XR information, and may facilitate the presentation of the XR information via one or more displays of the vehicle XR system. Non-limiting examples of rendering information may include enhanced information that may be superimposed on real-world objects and / or representations of real-world objects, identifiers of landmarks, interactive objects, additional information associated with real-world objects, and the like. For example, a cloud XR entity may have the ability to identify real-world objects in real time (or near real time) based on information received from a vehicle UE. For example, based on information received from a vehicular UE, a cloud XR entity may have the ability to identify that an intersection has a clothing store and provide augmented information associated with the clothing store.

[0052] In some aspects, the vehicle UE and the cloud XR entity may establish a vehicle XR session. The vehicle XR session may enable communications associated with a user flow between the vehicle UE and the cloud XR entity. For example, the user flow may include uplink information provided by the vehicle UE to the cloud XR entity. The user flow may also include downlink information provided by the cloud XR entity to the vehicle UE.

[0053] The uplink information may include information collected by one or more sensors of the vehicle XR system. The uplink information may include information about the vehicle and information about the user. For example, the collected information may include a vehicle XR component, which includes one or more of vehicle posture information, vehicle information, and vehicle surrounding information. The uplink information may also include a user XR component, which includes one or more of user posture information and input information. The user posture information may include information related to the position and / or orientation of the user in space relative to the XR space. The XR space may represent a virtual coordinate system with an origin corresponding to a physical position. The user posture information may be relative to the ground (e.g., absolute posture information) and / or relative to the vehicle (e.g., relative posture information). The input information may include information related to user eye tracking and / or user gestures.

[0054] Downlink information from the cloud XR entity to the vehicle UE may include rendering information for presentation at the vehicle. For example, the rendering information may include XR information that the vehicle UE is configured to overlay on a real-world object, such as augmented information. The vehicle UE may also display the XR information via one or more displays of the vehicle XR system. As used herein, the term "XR information" refers to information rendered in association with a vehicle XR session. For example, the XR information may include augmented information generated by the cloud XR entity for overlay on a real-world object.

[0055] The cloud XR entity may obtain uplink information and perform virtual-physical fusion of information to generate rendering information. In one or more aspects, the virtual-physical fusion of information may include identifying real-world objects and XR information. For example, the cloud XR entity may identify real-world objects based on the vehicle surrounding information of the vehicle XR component of the uplink information. The cloud XR entity may also generate XR information based on the identified real-world objects. In some examples, the cloud XR entity may generate XR information based on information received from additional network entities. For example, the cloud XR entity may identify a stadium and obtain XR information associated with the stadium from a network entity that provides sports-based information. The cloud XR entity may then provide the rendering information to the vehicle UE for presentation. For example, the vehicle UE may facilitate the display of the rendering information via one or more displays of the vehicle.

[0056] Additionally, as XR systems and communication systems develop and mature, more XR experiences may emerge. For example, instead of a vehicle XR application that displays information without considering driver information, the cloud XR entity may adjust the rendering information provided to the vehicle UE based on the user's posture. In such an example, when a user (e.g., a driver) moves his head and the content that the user is seeing changes, the XR application may present information related to the user. The rendering information provided to the vehicle UE may be adjusted according to the state of the user or the condition of the vehicle. For example, when the vehicle is parked, certain traffic-related information may not be presented to the user. In another example, when the vehicle is moving at a higher speed, only driving-related XR information may be presented to the driver.

[0057] Additionally, the cloud XR entity may allow for XR experiences to be provided to passengers. For example, one or more sensors of a vehicle XR system may collect information associated with different users (e.g., a driver and one or more passengers). In some such examples, the cloud XR entity may have the ability to generate XR information for different users. For example, the same or different XR information as the driver may be presented to a passenger. For example, first XR information related to navigation (e.g., direction, speed, etc.) may be presented to the driver, while second XR information related to a landmark may be presented to the passenger. According to one or more examples, the XR information presented to the passenger may be out of the driver's field of view, for example to avoid distracting the driver.

[0058] In some examples, the rendering information provided to the vehicle UE may include an interactive object with which the user can interact. In some examples, interacting with the interactive object may provide additional information about the real-world object. For example, the interactive object may be superimposed on a landmark. In some examples, the user may interact with (e.g., select) the interactive object to receive information about the landmark. In some examples, the user may interact with the interactive object to perform a transaction. For example, the rendering information may include an interactive object superimposed on a coffee shop. In some examples, the user may select the interactive object to initiate a coffee purchase at the coffee shop. In some examples, the input information of the user XR component may include information indicating interaction with the interactive object.

[0059] In some examples, the vehicle UE may provide relatively frequent communication of uplink information, for example, to enable the reception of accurate rendering information for presentation. For example, frequent updates (e.g., transmission of uplink information) may be required to provide the cloud XR entity with accurate information about the location of the vehicle and information about the surroundings of the vehicle. According to one or more aspects, the cloud XR entity may have the ability to perform pre-fetching and / or compression of information as appropriate. For example, based on a path plan, the cloud XR entity may pre-fetch XR information related to landmarks that a user can see while traveling a route. In some examples, the cloud XR entity may also encode and / or compress the rendering information to reduce the amount of information sent over the air (OTA). Additionally, by enabling the cloud XR entity to generate XR information, one or more aspects disclosed herein facilitate reducing the computational load of the vehicle UE for displaying XR information. For example, the cloud XR entity may generate XR information, rather than the vehicle UE using a static or local processing-based mechanism to generate XR information.

[0060] In some examples, a vehicle XR session may be associated with one or more XR services such as a navigation service, a landmark service, an interaction service, a service that enables transactions, and the like. A navigation service may enable display of XR information related to navigation. A landmark service may enable display of XR information related to landmark identification. An interaction service may enable display of XR information including one or more interactive objects. A service that enables transactions may enable display of XR information related to performing transactions based on interactive objects.

[0061] In some examples, when the cloud XR entity receives the uplink information, the cloud XR entity may generate XR information based on one or more XR services. For example, based on the uplink information, the cloud XR entity may identify a landmark, an opportunity for user interaction, and / or an opportunity to perform a transaction. In such examples, the cloud XR entity may generate rendering information to include XR information associated with the corresponding service.

[0062] In some examples, the cloud XR entity may provide granular control over the XR services supported by the vehicle XR session. For example, the vehicle XR session may be subscription-based and associated with a subscription level. The subscription level may be associated with the number of user flows that may be associated with the vehicle XR session. For example, the first subscription level may only allow driver flows, the second subscription level may only allow passenger flows, the third subscription level may allow driver flows and passenger flows, and the fourth subscription level may allow any number of flows and combinations of these flows. In some examples, the subscription level may be associated with the level of XR interaction. For example, based on the subscription level, the cloud XR entity may generate XR information including different types of interactive objects. In some examples, the subscription level may be associated with which services are enabled and / or disabled. For example, one subscription level may include navigation services and landmark services, while another subscription level may include navigation services, landmark services, interactive services, and services that enable transactions, etc. Therefore, according to one or more examples, different subscription levels may result in different XR information being presented to the user. In some examples, the subscription level may additionally or alternatively determine what type of services may be presented to the user. For example, at some subscription levels, high priority service users (e.g., police, government officials, etc.) may be presented with landmark services or interactive services from all surrounding buildings / locations, while users who are not high priority service users (e.g., "ordinary" users) may be presented with services only from commercial buildings / locations.

[0063] When establishing a vehicle XR session with a vehicle UE, the cloud XR entity may authorize a supported session level based on the subscription level. The supported session level may indicate which XR services are enabled and / or disabled for each vehicle XR session, and provide XR information accordingly. In some examples, the supported session level may be based on quality of service (QoS) information and / or quality of experience (QoE) information. For example, the cloud XR entity may perform rendering adaptation to provide a satisfactory user experience. Rendering adaptation may be based on QoE metrics and / or QoS support information provided by the vehicle UE. For example, when communication between the vehicle UE and the cloud XR entity is delayed, packet retransmissions are being observed, and / or the data rate is lower than the allowed data rate, the cloud XR entity may perform rendering adaptation to adjust the XR information being generated and provided to the vehicle UE. For example, when the QoE metric and / or QoS support information indicates reduced communication capabilities, the cloud XR entity may increase the priority of the XR information associated with the driver flow, and may reduce the priority of the XR information associated with the passenger flow. In this way, the cloud XR entity may provide a satisfying user experience to the driver, which may, for example, have a higher priority than providing a satisfying user experience to the passengers.

[0064] In some examples, a vehicle XR session may be associated with multiple users. For example, a vehicle XR session may include a first user stream associated with a first user (e.g., a driver) and a second user stream associated with a second user (e.g., a passenger). In such examples, the user streams may be associated with the same vehicle. For example, the uplink information may include a first user XR component associated with the first user, a second user XR component associated with the second user, and a vehicle XR component shared between the first user stream and the second user stream. The cloud XR entity may receive the uplink information and the corresponding components and merge the uplink information so that the rendering information facilitates a unified projection to one or more displays of the vehicle XR system.

[0065] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations that can practice the concepts described herein. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid blurring these concepts.

[0066] Several aspects of the telecommunication system are also presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0067] As an example, an element or any part of an element or any combination of elements can be implemented as a "processing system", which includes one or more processors. The example of a processor includes a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gate logic piece, a discrete hardware circuit and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other terms, software should be broadly interpreted as meaning an instruction, an instruction set, a code, a code segment, a program code, a program, a subroutine, a software component, an application, a software application, a software package, a routine, a subroutine, an object, an executable, a thread of execution, a process, a function or any combination thereof.

[0068] Therefore, in one or more example aspects, specific implementations and / or use cases, the described functions may be implemented with hardware, software, or any combination thereof. If implemented with software, the functions may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0069] Although various aspects, specific implementations and / or use cases are described in this application by illustrating some examples, additional or different aspects, specific implementations and / or use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, aspects, specific implementations and / or use cases may be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user equipment, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may be specifically for use cases or applications, or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Aspects, specific implementations and / or use cases may be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some practical environments, the equipment in conjunction with the various aspects and features described may also include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / accumulators, etc.). The various techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0070] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0071] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0072] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access and backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0073] Figure 1 1 is a diagram illustrating an example of a wireless communication system and an access network 100. The wireless communication system (which is also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) (e.g., EPC 160), and another core network 190 (e.g., 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0074] The base station 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG-RAN)) can interface with the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can perform one or more of the following functions: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 can communicate with each other directly or indirectly (e.g., through the EPC 160 or the core network 190) through the third backhaul link 134 (e.g., X2 interface). The first backhaul link 132, the second backhaul link 184 (e.g., Xn interface) and the third backhaul link 134 can be wired or wireless.

[0075] In some aspects, a base station (e.g., one of base stations 102 or one of base stations 180) may be referred to as a RAN and may include aggregated components or disaggregated components. As an example of a disaggregated RAN, a base station may include a central unit (CU) (e.g., CU 106), one or more distributed units (DUs) (e.g., DU 105), and / or one or more remote units (RUs) (e.g., RU 109), such as Figure 1 As illustrated. The RAN may be decomposed using a split between the RU 109 and the aggregated CU / DU. The RAN may be decomposed using a split between the CU 106, DU 105, and RU 109. The RAN may be decomposed using a split between the CU 106 and the aggregated DU / RU. The CU 106 and one or more DUs may be connected via an F1 interface. The DU 105 and the RU 109 may be connected via a fronthaul interface. The connection between the CU 106 and the DU 105 may be referred to as midhaul, and the connection between the DU 105 and the RU 109 may be referred to as fronthaul. The connection between the CU 106 and the core network 190 may be referred to as backhaul.

[0076] The RAN may be based on a functional split between various components of the RAN (e.g., between the CU 106, DU 105, or RU 109). The CU 106 may be configured to perform one or more aspects of a wireless communication protocol, for example, one or more layers of a protocol stack, and one or more DUs may be configured to handle other aspects of the wireless communication protocol, for example, other layers of the protocol stack. In different implementations, the split between the layers handled by the CU and the layers handled by the DU may occur at different layers of the protocol stack. As a non-limiting example, the DU 105 may provide a logical node for hosting at least a portion of a radio link control (RLC) layer, a medium access control (MAC) layer, and a physical (PHY) layer based on the functional split. The RU may provide a logical node configured to host at least a portion of the PHY layer and radio frequency (RF) processing. The CU 106 may host, for example, higher layer functions above the RLC layer, such as a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, and / or an upper layer. In other implementations, the split between the layer functions provided by the CU, DU, or RU may be different.

[0077] The access network may include one or more integrated access and backhaul (IAB) nodes (e.g., IAB node 111) that exchange wireless communications with a UE (e.g., one of UEs 104) or another IAB node to provide access and backhaul to the core network. In an IAB network of multiple IAB nodes, an anchor node may be referred to as an IAB donor. An IAB donor may be a base station (e.g., one of base stations 102 or one of base stations 180) that provides access to a core network 190 or EPC 160 and / or control of one or more IAB nodes in the IAB node 111. The IAB donor may include a CU 106 and a DU 105. The IAB node 111 may include a DU 105 and a mobile terminal (MT). The DU 105 of the IAB node may operate as a parent node, and the MT may operate as a child node.

[0078] As described above, the deployment of a communication system (such as a 5G New Radio (NR) system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0079] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0080] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access and backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0081] As an example, Figure 4 A diagram illustrating the architecture of an example disaggregated base station 400 is shown. The disaggregated base station 400 architecture may include one or more CUs (e.g., CU 410) that may communicate directly with a core network 420 via a backhaul link, or indirectly with a core network 420 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) (e.g., near-RT RIC 425) via an E2 link, or a non-real-time (non-RT) RIC (e.g., non-RT RIC 415) associated with a service management and orchestration (SMO) framework (e.g., SMO framework 405), or both. CU 410 (e.g., near-RT RIC 425) may communicate with a core network 420 via a backhaul link. Figure 1 CU 106) can communicate with one or more DUs (e.g., DU 430) via corresponding mid-haul links such as F1 interfaces. DU 430 (e.g., Figure 1 The DU 105 of the embodiment may communicate with one or more RUs (e.g., RU 440) via corresponding fronthaul links. Figure 1The RU 109) may communicate with a corresponding UE (e.g., Figure 1 In some implementations, a UE may be served by multiple RUs at the same time.

[0082] Each of the units (i.e., CU 410, DU 430, RU 440, and near-RT RIC 425, non-RT RIC 415, and SMO framework 405) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or send signals, or both, to one or more of the other units via a wireless transmission medium.

[0083] In some aspects, CU 410 may host one or more high-level control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 410. CU 410 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 410 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 410 may be implemented to communicate with DU 430 for network control and signaling.

[0084] DU 430 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs. In some aspects, DU 430 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to functional splits (such as those defined by the 3rd Generation Partnership Project (3GPP)). In some aspects, DU 430 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 430 or with control functions hosted by CU410.

[0085] The lower layer functionality may be implemented by one or more RUs. In some deployments, the RU 440 controlled by the DU 430 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU may be implemented to handle over-the-air (OTA) communications with one or more UEs in UE104. In some specific implementations, the real-time and non-real-time aspects of the control plane and user plane communications with the RU may be controlled by the corresponding DU. In some scenarios, this configuration may enable the DU and CU 410 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0086] The SMO framework 405 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 405 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 405 may be configured to interact with a cloud computing platform (such as an open cloud 490 (O-Cloud)) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 410, DU 430, RU 440, and near-RT RIC 425. In some specific implementations, the SMO framework 405 may communicate with hardware aspects of the 4G RAN such as an open eNB (O-eNB) (e.g., O-eNB 411) via the O1 interface. Additionally, in some specific implementations, the SMO framework 405 may communicate directly with one or more RUs via the O1 interface. The SMO framework 405 may also include a non-RT RIC 415 configured to support the functionality of the SMO framework 405 .

[0087] The non-RT RIC 415 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 425. The non-RT RIC 415 may be coupled to or communicate with the near-RT RIC 425 (such as via an A1 interface). The near-RT RIC 425 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs, one or more DUs, or both, and the O-eNB with the near-RT RIC 425.

[0088] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 425, the non-RT RIC 415 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 425 and may be received from a non-network data source or from a network function at the SMO framework 405 or the non-RT RIC 415. In some examples, the non-RT RIC 415 or the near-RT RIC 425 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 415 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 405 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0089] Reference again Figure 1 , the base station 102 can communicate wirelessly with the UE 104. Each base station in the base station 102 can provide communication coverage for a corresponding geographic coverage area (e.g., coverage area 110). There may be overlapping geographic coverage areas. For example, the small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more base stations (e.g., one or more macro base stations) in the base station 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group called a closed subscriber group (CSG). The communication link 120 between the base station 102 and the UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from the UE to the base station and / or a downlink (DL) (also referred to as a forward link) transmission from the base station to the UE. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in the carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 can use a spectrum of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) bandwidth. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0090] Some of the UEs 104 may communicate with each other using a device-to-device (D2D) communication link (e.g., D2D communication link 158). The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more side link channels, such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and a physical side link control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0091] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) (e.g., STA 152) via a communication link 154, e.g., in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0092] The small cell 102' may operate in licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may improve the coverage of the access network and / or increase the capacity of the access network.

[0093] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0094] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0095] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used in this document, it can broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used in this document, it can broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2 and / or FR5, or may be within the EHF band.

[0096] A base station, whether a small cell 102' or a large cell (e.g., a macro base station), may include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations, such as gNBs (e.g., one of the base stations in base station 180), may operate in traditional sub-6 GHz spectrum, in millimeter wave frequencies, and / or near millimeter wave frequencies to communicate with UE 104. When a gNB operates at millimeter wave frequencies or near millimeter wave frequencies, the gNB may be referred to as a millimeter wave base station. The millimeter wave base station may utilize beamforming 182 with one or more of the UEs 104 to compensate for path loss and short range. The base station 180 and the UE 104 may each include multiple antennas (e.g., antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Similarly, beamforming may be applied to sidelink communications, for example, between UEs.

[0097] The base station 180 may transmit beamformed signals in one or more transmit directions 182' to one or more UEs in the UE 104. The UE may receive the beamformed signals from the base station in one or more receive directions 182". The UE may also transmit beamformed signals to the base station in one or more transmit directions. The base station 180 may receive the beamformed signals from the UE in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station / UE. The transmit direction and receive direction of the base station may or may not be the same. The transmit direction and receive direction of the UE may or may not be the same.

[0098] The EPC 160 may include a mobility management entity (MME) (e.g., MME 162), other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway (e.g., MBMS gateway 168), a broadcast multicast service center (BM-SC) (e.g., BM-SC 170), and a packet data network (PDN) gateway (e.g., PDN gateway 172). The MME 162 may communicate with a home subscriber server (HSS) (e.g., HSS 174). The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are passed through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to the IP service 176. The IP services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services in a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to allocate MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area of ​​a broadcast specific service, and may be responsible for session management (start / stop) and for collecting eMBMS-related billing information.

[0099] The core network 190 may include an access and mobility management function (AMF) (e.g., AMF 192), other AMFs 193, a session management function (SMF) (e.g., SMF 194), and a user plane function (UPF) (e.g., UPF 195). AMF 192 may communicate with a unified data management (UDM) (e.g., UDM 196). AMF 192 is a control node that handles signaling between UE 104 and the core network 190. Generally speaking, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are passed through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, intranet, IP multimedia subsystem (IMS), packet switching (PS) streaming services, and / or other IP services.

[0100] A base station may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other suitable term. Base station 102 provides an access point to EPC 160 or core network 190 for UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of UE 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart monitor, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access a network together and / or individually.

[0101] Reference again Figure 1 In certain aspects, a device communicating with a network entity, such as one of the UEs 104 communicating with one of the base stations 102 or a component of the base station (e.g., CU 106, DU 105, and / or RU 109)), may be configured to manage one or more aspects of wireless communication. For example, one or more of the UEs 104 (e.g., a vehicle UE) may include a vehicle XR component 198 configured to facilitate an XR user experience associated with a vehicle. In certain aspects, the vehicle XR component 198 may be configured to send a request for a vehicle XR session based on a first user XR stream including a vehicle XR component associated with the vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle. The example vehicle XR component 198 may also be configured to send uplink information associated with the first user XR stream. Additionally, the example vehicle XR component 198 may be configured to receive rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

[0102] In another configuration, a network entity such as one of the base stations 102 or a component of the base station (e.g., CU 106, DU 105, and / or RU 109) or the air device 103 may be configured to manage one or more aspects of wireless communication. For example, one or more of the base stations 102 may include a vehicle-to-cloud XR network component 199 configured to facilitate an XR user experience associated with a vehicle. In certain aspects, the vehicle-to-cloud XR network component 199 may be configured to obtain a request for a vehicle XR session. The vehicle-to-cloud XR network component 199 may also be configured to authorize a vehicle XR session based on a first user XR stream including a vehicle XR component associated with the vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle. The example vehicle-to-cloud XR network component 199 may also be configured to obtain uplink information associated with the first user XR stream. Additionally, the example vehicle-to-cloud XR network component 199 may be configured to output rendering information associated with the first user XR stream, the rendering information being based on the uplink information. In some examples, the vehicle-to-cloud XR network component 199 may be configured to additionally or alternatively provide additional information related to a vehicle XR session associated with a vehicle, such as location information of the vehicle, sensory information about the surrounding environment of the vehicle environment, and the like.

[0103] In another configuration, a network entity such as EPC 160 and / or core network 190, or a component of a network entity, may be configured to manage one or more aspects of wireless communication. For example, EPC 160 and / or core network 190 may include a vehicle-to-cloud XR component 191 configured to facilitate an XR user experience associated with a vehicle. The vehicle-to-cloud XR component 191 may be a new logical entity in EPC 160 or core network 190, or a new function distributed in an existing entity within EPC 160 or core network 190, such as AMF 192, SMF 194, UPF 195, or MME 162, Serving Gateway 166, PDN Gateway 172, MBMS GW 168, and / or BM-SC 170. In some aspects, the vehicle-to-cloud XR component 191 may be configured to obtain a request for a vehicle XR session. The vehicle-to-cloud XR component 191 may also be configured to authorize a vehicle XR session based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle. The example vehicle-to-cloud XR component 191 may also be configured to obtain uplink information associated with the first user XR stream. Additionally, the example vehicle-to-cloud XR component 191 may be configured to output rendering information associated with the first user XR stream, the rendering information being based on the uplink information. The vehicle-to-cloud XR component 191 may be configured to provide necessary handling of a connection request for a vehicle XR session, for example, establishing a required protocol data unit (PDU) session, selecting an appropriate UPF, authorizing a session based on subscription information, setting an appropriate QoS level and billing record, etc. In another example, the vehicle-to-cloud XR component 191 may be implemented outside the EPC 160 or the core network 190, for example, outside the PDN gateway 172 or the UPF 195.

[0104] Various aspects presented herein may enable a UE to provide an XR user experience in a vehicle. For example, various aspects presented herein may enable network-based operational support to determine information that supports an XR user experience in a vehicle, which may facilitate improved communication performance, for example, by reducing the computational load at the vehicle.

[0105] Although the following description provides examples involving 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, enhanced 5G, 6G, and / or other wireless technologies.

[0106] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2BFIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The slot format is configured for the UE via a received slot format indicator (SFI) (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0107] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of the same size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4 or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is conventional or extended. For a conventional CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0108]

[0109] Table 1

[0110] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Accordingly, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ As shown in Table 1, the subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0111] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0112] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0113] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. The PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on the CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of a frame. The PSS is used by the UE to determine subframe / symbol timing and physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information such as system information blocks (SIBs) that are not sent via the PBCH, and paging messages.

[0114] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the comb teeth. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0115] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0116] Figure 3 is a block diagram illustrating an example of a first wireless device configured to exchange wireless communications with a second wireless device. Figure 3 In the illustrated example of , the first wireless device may include a base station 310, the second wireless device may include a UE 350, and the base station 310 may communicate with the UE 350 in an access network. Figure 3 As shown, base station 310 includes a transmit processor (TX processor 316), a transmitter 318Tx, a receiver 318Rx, an antenna 320, a receive processor (RX processor 370), a channel estimator 374, a controller / processor 375, and a memory 376. Example UE 350 includes antenna 352, a transmitter 354Tx, a receiver 354Rx, an RX processor 356, a channel estimator 358, a controller / processor 359, a memory 360, and a TX processor 368. In other examples, base station 310 and / or UE 350 may include additional or alternative components.

[0117] In the DL, Internet Protocol (IP) packets may be provided to the controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer protocol data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0118] The TX processor 316 and the RX processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from channel estimator 374 may be used to determine coding and modulation schemes and for spatial processing. Channel estimates may be derived from reference signals and / or channel state feedback sent by UE 350. Each spatial stream may then be provided to a different antenna in antenna 320 via a separate transmitter (e.g., transmitter 318Tx). Each transmitter 318Tx may modulate a radio frequency (RF) carrier for transmission using a corresponding spatial stream.

[0119] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna in the antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream to the UE 350. In the case where multiple spatial streams are to the UE 350, two or more of the multiple spatial streams can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbol on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on the channel estimate calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0120] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0121] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0122] Channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different ones of the antennas 352 via separate transmitters (e.g., transmitter 354Tx). Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0123] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding one of the antennas 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0124] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0125] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The Vehicle XR component 198 combines various aspects.

[0126] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The transportation to cloud XR network component 199 combines various aspects.

[0127] As mentioned above, XR refers to the reality-virtual continuum between the real environment and the virtual environment. Extended reality technology can provide virtual content to users and / or combine the real or physical environment with the virtual environment (which can be composed of virtual content or virtual objects) to provide users with XR experiences. XR experiences can include VR, AR, MR and / or other immersive content.

[0128] Augmented reality (AR) can merge the real world with virtual objects to support realistic, intelligent, and personalized experiences. Virtual reality (VR) provides a level of immersion, for example, by creating a sense of physical presence in a real or imagined world. Augmented virtuality (AV) merges the virtual world with real-world objects. Mixed reality (MR) merges the real world with the virtual world to produce new environments and visualizations in which physical and virtual objects can coexist and interact with each other. Extended reality (XR) includes AR, AV, VR, and MR, and refers to a complete reality-virtual continuum between real and virtual environments.

[0129] A user may experience XR via an XR device (e.g., may be provided with an XR experience). Extended reality devices may have different form factors and may differ in processing power, power consumption, and / or communication type. An example of an XR device is an HMD. The HMD may include a display positioned in front of one or both eyes. The display may stream data, images, and / or other information in front of the user's eyes.

[0130] The HMD may include an optical system such as a display and / or lens, one or more tracking sensors, one or more cameras, communication functionality, and an XR engine. The XR engine may perform XR-related processing and may include one or more GPUs, CPUs, etc. The display of the HMD may be transparent or opaque. For example, for AR applications, the display may be transparent (or mostly transparent) and AR information may be superimposed on real-life objects. In another example, for VR applications, the display may not be transparent, and virtual information and images may be displayed in front of the user's eyes.

[0131] An example application of XR is associated with a vehicle. For example, a vehicle may be configured with an XR system that provides a vehicle-based XR experience to a user of the vehicle. The vehicle may include a land vehicle such as a car, bus, train, etc., or an air / non-land vehicle such as a drone, balloon, airplane, helicopter, etc. The user of the vehicle may be a person, a device with artificial intelligence, a communication equipment that supports remote access, or a connected controller. The XR system of the vehicle may have a different form factor than an HMD, but may include one or more similar components.

[0132] Figure 5 is a diagram illustrating an example vehicle 500 configured with a vehicle XR system as presented herein. Figure 5 The vehicle 500 includes a seat 502 for a driver, a seat 504 for a first passenger, and a seat 506 for a second passenger. Figure 5 In the example of , the driver 502 and the first passenger 504 are located in the same row (e.g., the front row), and the second passenger 506 is located in a different row (e.g., the back row). However, other examples may include additional or alternative configurations for the driver and one or more passengers.

[0133] exist Figure 5 In the example of , vehicle 500 is configured with a vehicle XR system, which may also be referred to as a “vehicle XR platform” or another name. The vehicle XR system facilitates providing vehicle XR to users of vehicle 500. Figure 5 The vehicle XR system includes a first display 510, one or more sensors 512, and a vehicle UE 514. The first display 510 may include a head-up display that adds enhanced information. The enhanced information may include information superimposed on a real-world object via the first display 510. For example, the enhanced information may include an identifier of a landmark, an interactive object, additional information associated with a real-world object, and the like. The one or more sensors 512 may include a camera, a GPS sensor, a radar sensor, a light detection and ranging (LiDAR) sensor, and the like. The one or more sensors 512 may be associated with an advanced driver assistance system (ADAS) of the vehicle 500 and / or may be an in-cabin sensor. For example, the in-cabin sensor may be able to provide posture information of a user of the vehicle (such as the driver 502, the first passenger 504, and / or the second passenger 506). The vehicle UE 514 may provide communication functions and XR-based processing.

[0134] As an example of a vehicle XR application, the navigation system of the vehicle 500 may enable a user (e.g., driver 502, first passenger 504, and / or second passenger 506) to input a desired destination and generate a path plan (e.g., route) to reach the desired destination. One or more sensors 512 may capture vehicle surrounding information of an area around the vehicle 500. The vehicle UE 514 may then process the vehicle surrounding information and generate rendering information accordingly. The first display 510 may then display the rendering information. For example, the rendering information may include augmented information superimposed on real-world objects around the vehicle 500. Examples of real-world objects around the vehicle may include traffic lights, hazard signs, road signs, roadblocks, landmarks, buildings, billboards, and the like. The augmented information may include driver assistance information such as the current speed of the vehicle 500, speed limits, gasoline-related or battery-related information, upcoming directions, traffic light phase information, information about potential manipulations of surrounding vehicles and vulnerable road users (VRUs), road conditions, and the like.

[0135] Fig. 6A A scenario 600 as presented herein is depicted in which a heads-up display of a vehicle overlays augmented information on real-world objects and / or representations of real-world objects. Fig. 6A In the example of FIG. 6 , scene 600 includes real-world objects such as traffic lights 602, hazard signs 604, directional signs 606, roadblocks 608, and median strips 610. Scene 600 also includes augmented information 620 that can be superimposed on the real-world objects, which is displayed via a display such as Figure 5 The first display 510. Fig. 6A In the example of FIG. 6 , the enhanced information 620 includes information related to the speed of the vehicle, speed limit, navigation information, etc.

[0136] exist Figure 5 and Fig. 6A In the example of , the augmented information 620 is based on content that the vehicle UE 514 is able to identify and then present via the first display 510. For example, the augmented information 620 may be identified and presented based on a static or local processing-based mechanism. Examples of static or local processing-based mechanisms may be based on preconfigured information stored at the vehicle UE. For example, the vehicle UE may be configured with augmented information corresponding to navigation, such as an indicator of a speed limit associated with a street or highway. In some such examples, the vehicle UE may identify real-world objects, such as street signs, based on information provided by one or more sensors of the vehicle XR system. According to one or more examples, the vehicle UE may then display augmented information indicating a speed limit associated with the street based on the identified street sign.

[0137] In some examples, augmented information 620 may be generated and displayed via first display 510 regardless of where driver 502 is looking. For example, driver 502 may be looking out of window 516 of vehicle 500 and may not be able to see augmented information displayed via first display 510. In such examples, vehicle UE 514 may be using resources (e.g., processing resources, memory, etc.) to generate and present augmented information 620 with a default configuration. Additionally, in some examples, augmented information 620 presented in scene 600 may be limited to what objects vehicle UE 514 is able to identify and / or may be limited to information provided by another system of the vehicle, such as a navigation system.

[0138] Figure 6B A scene 650 including real-world objects as presented herein is depicted. Figure 6B In the example of , scene 650 includes real-world objects such as a traffic light 652 , a median 654 , an electronic billboard 656 , a bus 658 , and a train station 660 .

[0139] Figure 6C A scene 670 including virtual objects superimposed on real-world objects as presented herein is depicted. For example, the scene 670 includes a virtual object that may be superimposed on a real-world object. Figure 6B The augmented information on the real-world objects can be displayed via a display associated with the vehicle XR system such as Figure 5 The first display 510 is used to present the Figure 6C In the example of FIG. 6 , the enhanced information includes landmark information 671 , navigation information 672 , and an interactive object 674 superimposed on the train station 660 .

[0140] In some examples, a user (e.g., a driver and / or a passenger) may be presented with an interactive object that the user may interact with. In some examples, interacting with the interactive object may provide additional information about the real-world object. Figure 6C In the example of FIG. 6 , selecting interactive object 674 may provide additional information for a related landmark, such as train station 660. For example, if a user selects interactive object 674, augmented information 676 may be presented to the user that provides information related to train station 660, such as the name of the train station, the distance to the train station, the arrival of the next train, etc.

[0141] The various aspects disclosed herein facilitate vehicle XR applications that include cloud-based processing. For example, the various aspects disclosed herein enable offloading of some processing associated with presenting augmented information to a cloud XR entity. The cloud XR entity may be connected to a vehicle UE of a vehicle XR system such as Figure 5The cloud XR entity may receive information collected from the vehicle UE 514 via one or more sensors of the vehicle XR system, such as one or more sensors 512. The cloud XR entity may then help determine what rendering information is needed to support the vehicle XR application at the vehicle UE 514 and provide a satisfactory user experience (e.g., an XR experience that the user may appreciate). For example, the cloud XR entity may have the ability to identify real-world objects in real time (or near real time) based on information received from the vehicle UE. For example, based on information received from the vehicle UE, the cloud XR entity may have the ability to identify that an intersection has a coffee shop and provide enhanced information associated with the coffee shop.

[0142] In some aspects, the vehicle UE and the cloud XR entity may establish a vehicle XR session. The vehicle XR session may enable communications associated with a user flow between the vehicle UE and the cloud XR entity. For example, the user flow may include uplink information provided by the vehicle UE to the cloud XR entity. The user flow may also include downlink information provided by the cloud XR entity to the vehicle UE.

[0143] The uplink information may include information collected by one or more sensors of the vehicle XR system. The uplink information may include information about the vehicle and information about the user. For example, the collected information may include a vehicle XR component, which includes one or more of vehicle posture information, vehicle information, and vehicle surrounding information. The uplink information may also include a user XR component, which includes one or more of user posture information and input information. The user posture information may include information related to the position and / or orientation of the user in space relative to the XR space. The XR space may represent a virtual coordinate system with an origin corresponding to a physical position. The user posture information may be relative to the ground (e.g., absolute posture information) and / or relative to the vehicle (e.g., relative posture information). The input information may include information related to user eye tracking and / or user gestures.

[0144] Downlink information from the cloud XR entity to the vehicle UE may include rendering information for presentation at the vehicle. For example, the rendering information may include XR information that the vehicle UE is configured to overlay on real-world objects, such as augmented information. The vehicle UE may also display the XR information via one or more displays of the vehicle XR system.

[0145] The cloud XR entity may obtain uplink information and perform virtual-physical fusion of information to generate rendering information. In one or more aspects, the virtual-physical fusion of information may include identifying real-world objects and XR information. For example, the cloud XR entity may identify real-world objects based on the vehicle surrounding information of the vehicle XR component of the uplink information. The cloud XR entity may also generate XR information based on the identified real-world objects. In some examples, the cloud XR entity may generate XR information based on information received from additional network entities. For example, the cloud XR entity may identify a stadium and obtain XR information associated with the stadium from a network entity that provides sports-based information. The cloud XR entity may then provide the rendering information to the vehicle UE for presentation. For example, the vehicle UE may facilitate the display of the rendering information via one or more displays of the vehicle.

[0146] Additionally, as XR systems and communication systems develop and mature, more XR experiences may emerge. For example, instead of a vehicle XR application that displays information without considering driver information, the cloud XR entity may adjust the rendering information provided to the vehicle UE based on the user's posture. In such an example, when a user (e.g., a driver) moves his head and the content that the user is seeing changes, the XR application may present information related to the user. The rendering information provided to the vehicle UE may be adjusted according to the state of the user or the condition of the vehicle. For example, when the vehicle is parked, certain traffic-related information may not be presented to the user. In another example, when the vehicle is moving at a higher speed, only driving-related XR information may be presented to the driver.

[0147] Additionally, the cloud XR entity may allow for XR experiences to be provided to passengers. For example, one or more sensors of a vehicle XR system may collect information associated with different users (e.g., a driver and one or more passengers). In some such examples, the cloud XR entity may have the ability to generate XR information for different users. For example, the same or different XR information as the driver may be presented to a passenger. For example, first XR information related to navigation (e.g., direction, speed, etc.) may be presented to the driver, while second XR information related to a landmark may be presented to the passenger. According to one or more examples, the XR information presented to the passenger may be out of the driver's field of view, for example to avoid distracting the driver.

[0148] In some examples, the rendering information provided to the vehicle UE may include an interactive object with which the user can interact. In some examples, interacting with the interactive object may provide additional information about the real-world object. For example, the interactive object may be superimposed on a landmark. In some examples, the user may interact with (e.g., select) the interactive object to receive information about the landmark. In some examples, the user may interact with the interactive object to perform a transaction. For example, the rendering information may include an interactive object superimposed on a coffee shop. In some examples, the user may select the interactive object to initiate a coffee purchase at the coffee shop. In some examples, the input information of the user XR component may include information indicating interaction with the interactive object.

[0149] In some examples, the vehicle UE may provide relatively frequent communication of uplink information, for example, to enable the reception of accurate rendering information for presentation. For example, frequent updates (e.g., transmission of uplink information) may be required to provide the cloud XR entity with accurate information about the location of the vehicle and information about the surroundings of the vehicle. According to one or more aspects, the cloud XR entity may have the ability to perform pre-fetching and / or compression of information as appropriate. For example, based on a path plan, the cloud XR entity may pre-fetch XR information related to landmarks that a user can see while traveling a route. In some examples, the cloud XR entity may also encode and / or compress the rendering information to reduce the amount of information sent over the air (OTA). Additionally, by enabling the cloud XR entity to generate XR information, one or more aspects disclosed herein facilitate reducing the computational load of the vehicle UE for displaying XR information. For example, the cloud XR entity may generate XR information, rather than the vehicle UE using a static or local processing-based mechanism to generate XR information.

[0150] In some examples, a vehicle XR session may be associated with one or more XR services such as a navigation service, a landmark service, an interaction service, a service that enables transactions, and the like. A navigation service may enable display of XR information related to navigation. A landmark service may enable display of XR information related to landmark identification. An interaction service may enable display of XR information including one or more interactive objects. A service that enables transactions may enable display of XR information related to performing transactions based on interactive objects.

[0151] In some examples, when the cloud XR entity receives the uplink information, the cloud XR entity may generate XR information based on one or more XR services. For example, based on the uplink information, the cloud XR entity may identify a landmark, an opportunity for user interaction, and / or an opportunity to perform a transaction. In such examples, the cloud XR entity may generate rendering information to include XR information associated with the corresponding service.

[0152] In some examples, the cloud XR entity may provide granular control over the XR services supported by the vehicle XR session. For example, the vehicle XR session may be subscription-based and associated with a subscription level. The subscription level may be associated with the number of user flows that may be associated with the vehicle XR session. For example, the first subscription level may only allow driver flows, the second subscription level may only allow passenger flows, the third subscription level may allow driver flows and passenger flows, and the fourth subscription level may allow any number of flows and combinations of these flows. In some examples, the subscription level may be associated with the level of XR interaction. For example, based on the subscription level, the cloud XR entity may generate XR information including different types of interactive objects. In some examples, the subscription level may be associated with which services are enabled and / or disabled. For example, one subscription level may include navigation services and landmark services, while another subscription level may include navigation services, landmark services, interactive services, and implementation services for implementing transactions, etc. Therefore, according to one or more examples, different subscription levels may result in different XR information being presented to the user. In some examples, the subscription level may additionally or alternatively determine what type of services may be presented to the user. For example, at some subscription levels, high priority service users (e.g., police, government officials, etc.) may be presented with landmark services or interactive services from all surrounding buildings / locations, while users who are not high priority service users (e.g., "ordinary" users) may be presented with services only from commercial buildings / locations.

[0153] When establishing a vehicle XR session with a vehicle UE, the cloud XR entity may authorize the supported session level based on the subscription level. The supported session level may indicate which XR services are enabled and / or disabled, and provide XR information accordingly. In some examples, the supported session level may be based on QoS information and / or QoE information. For example, the cloud XR entity may perform rendering adaptation to provide a satisfactory user experience. Rendering adaptation may be based on QoE metrics and / or QoS support information provided by the vehicle UE. For example, when communication between the vehicle UE and the cloud XR entity is delayed, packet retransmissions are being observed, and / or the data rate is lower than the allowed data rate, the cloud XR entity may perform rendering adaptation to adjust the XR information being generated and provided to the vehicle UE. For example, when the QoE metric and / or QoS support information indicates reduced communication capabilities, the cloud XR entity may increase the priority of the XR information associated with the driver flow, and may reduce the priority of the XR information associated with the passenger flow. In this way, the cloud XR entity may provide a satisfying user experience to the driver, which may, for example, have a higher priority than providing a satisfying user experience to the passengers.

[0154] In some examples, a vehicle XR session may be associated with multiple users. For example, a vehicle XR session may include a first user stream associated with a first user (e.g., a driver) and a second user stream associated with a second user (e.g., a passenger). In such examples, the user streams may be associated with multiple users of the same vehicle (e.g., Figure 5 The uplink information may be associated with a vehicle 500 of the vehicle. For example, the uplink information may include a first user XR component associated with a first user, a second user XR component associated with a second user, and a vehicle XR component shared between the first stream and the second stream. The cloud XR entity may receive the uplink information and the corresponding components and merge the uplink information so that the rendering information facilitates unified projection to one or more displays of the vehicle.

[0155] Reference again Figure 5 In the example vehicle 500, the vehicle XR system of the vehicle 500 may be associated with one or more displays. The displays may be glasses-based or glasses-free. In a glasses-based display, the users may each be wearing separate XR glasses and the XR information may be displayed separately on different XR glasses. In a glasses-free display, the XR information may be presented via a heads-up display (HUD). In some examples, in order to enable different XR information to be presented to different users, the HUD may be a specially processed window that is polarized to enable dual views of different content.

[0156] exist Figure 5 In the example of , the vehicle 500 includes a first display 510, which can be a HUD and is configured to display XR information for the driver 502 and the first passenger 504. The vehicle 500 also includes a second display 520 positioned on the driver's side of the vehicle 500 and a third display 522 positioned on the other side of the vehicle 500. The second display 520 and the third display 522 can be HUDs configured to display XR information to users on the respective sides of the vehicle. In some examples, the third display 522 can be configured to display different XR information to the first passenger 504 and the second passenger 506. The vehicle 500 also includes a fourth display 530. The fourth display 530 can be a glasses-based display worn by the second passenger 506 to view the XR information associated with the vehicle XR session. Therefore, it can be understood that when Figure 5 When the vehicle UE 514 receives rendering information (e.g., from a cloud XR entity), the rendering information may be presented via one or more displays of the vehicle 500 (e.g., a first display 510, a second display 520, a third display 522, and / or a fourth display 530).

[0157] It is understood that in other examples, the positioning of the display and / or the type of display may vary. For example, a vehicle may include only glasses-based displays or may include only non-glasses-based displays.

[0158] As used herein, the term "XR information" refers to information rendered in association with an XR session. For example, XR information may include augmented information superimposed on real-world objects, such as Fig. 6A Enhanced information 620 and / or Figure 6C Enhanced information.

[0159] Figure 7 An example communication flow 700 between a network entity 702, a vehicle UE 704, and a cloud XR entity 708 as presented herein is illustrated. One or more aspects described with respect to the network entity 702 may be performed by a component of a base station or a component of a base station such as a CU, DU, and / or RU. Aspects of the cloud XR entity 708 may facilitate implementation Figure 1 The vehicle-to-cloud XR component 191 and / or the vehicle-to-cloud XR network component 199. Figure 7 Not shown in the illustrated example, it will be appreciated that in additional or alternative examples, the network entity 702, the vehicle UE 704, and / or the cloud XR entity 708 may communicate with one or more other network entities or UEs.

[0160] exist Figure 7 In the illustrated example of , the communication flow 700 facilitates the establishment of a vehicle XR session between a vehicle UE 704 and a cloud XR entity 708 and the management of the vehicle XR session. The vehicle UE 704 can be a UE that enables a vehicle 706 to communicate via an access network. The vehicle 706 can be a land vehicle such as a car, a bus, a train, etc., or can be an air / non-land vehicle such as a drone, a balloon, etc. The cloud XR entity 708 can be a network entity that provides vehicle-to-cloud based XR services to the vehicle 706. In some examples, the cloud XR entity 708 can be operated by a network operator such as an operator of the network entity 702. In other examples, the cloud XR entity 708 can be operated by an operator different from the operator of the network entity 702. In some implementations, the network entity 702 and the cloud XR entity 708 can be collocated in a physical entity.

[0161] like Figure 7As shown, the vehicle UE 704 and the cloud XR entity 708 perform corresponding connection establishment procedures to facilitate communication between the vehicle UE 704 and the cloud XR entity 708. For example, the vehicle UE 704 and the network entity 702 perform a first connection establishment procedure 710 to enable the vehicle UE 704 to communicate via the access network. The cloud XR entity 708 and the network entity 702 may also perform a second connection establishment procedure 712 to enable the cloud XR entity 708 to communicate via the access network.

[0162] exist Figure 7 In the example of , after the vehicle UE 704 and the cloud XR entity 708 establish their respective connections, the vehicle UE 704 and the cloud XR entity 708 may communicate via the network entity 702. For example, when the vehicle UE 704 sends a message to the cloud XR entity 708, the message may first be communicated from the vehicle UE 704 to the network entity 702, and then from the network entity 702 to the cloud XR entity 708. In a similar manner, when the cloud XR entity 708 sends a message to the vehicle UE 704, the message may first be communicated from the cloud XR entity 708 to the network entity 702, and then from the network entity 702 to the vehicle UE 704.

[0163] like Figure 7 As shown, the vehicle UE 704 and the cloud XR entity 708 may perform a session establishment process 720 to establish a vehicle XR session. The session establishment process 720 may enable the vehicle UE 704 to initiate a vehicle XR session with the cloud XR entity 708. The session establishment process 720 may also enable the cloud XR entity 708 to authorize the vehicle XR session and configure one or more aspects of the vehicle XR session.

[0164] For example, the vehicle UE 704 may output (e.g., send) a session request 722 that is obtained (e.g., received) by the cloud XR entity 708. The session request 722 may include a request to establish a vehicle XR session. The cloud XR entity 708 may perform an authorization process 724 to authorize the vehicle XR session 726. The cloud XR entity 708 may perform the authorization process 724 based on the information included in the session request 722. The cloud XR entity 708 may then output a session response 728 that is received by the vehicle UE 704. The session response 728 may confirm that the vehicle XR session 726 is established between the vehicle UE 704 and the cloud XR entity 708.

[0165] The vehicle XR session 726 may be associated with a session level and a corresponding session configuration. The session level may be based on one or more of a subscription, supported quality of service (QoS), a user identifier (ID), and / or privacy control. In some examples, the cloud XR entity 708 may determine the session configuration based on the session level. The session configuration may be associated with one or more operating parameters. For example, the session configuration may indicate a Uu connection to be established, a frequency of updating of state information, etc. The cloud XR entity 708 may configure one or more operating parameters to the vehicle UE 704 via a session response 728. An additional aspect of the session establishment process 720 is in conjunction with Figure 8 To describe.

[0166] After establishing the vehicle XR session 726 (e.g., via the session establishment process 720), the vehicle UE 704 and the cloud XR entity 708 may perform a session management process 730 to manage the user experience associated with the vehicle XR session 726. For example, the vehicle UE 704 may perform a collection process 732 to collect information at the vehicle 706. For example, one or more sensors of the vehicle 706 may be configured to collect information related to the user and / or the vehicle 706. Various aspects of the one or more sensors of the vehicle 706 may be provided by Figure 5 The one or more sensors 512 of the vehicle 706 may be implemented. For example, the one or more sensors of the vehicle 706 may include sensors associated with an ADAS system of the vehicle 706 and / or in-cabin sensors.

[0167] like Figure 7 As shown, the vehicle UE 704 can output uplink information 734 obtained by the cloud XR entity 708. The uplink information 734 can be based on the information collected via the collection process 732. Figure 7 In the example of , the uplink information 734 includes a vehicle XR component 736 and a user XR component 738. The vehicle XR component 736 may include information related to the vehicle 706, such as vehicle posture information, vehicle information, and / or vehicle surrounding information. The user XR component 738 may include information related to the user, such as user gesture information and / or user input information.

[0168] In some examples, the vehicle UE 704 may collect information associated with the vehicle XR component 736 and / or the user XR component 738 based on the respective periodicities configured via the session response 728. Because different sensors may be associated with the collection of information for the vehicle and the user, the information collection may occur at different points in time and / or with different periodicities. In some examples, the vehicle UE 704 may include timing information (e.g., timestamps) associated with different attributes of the uplink information.

[0169] like Figure 7 As shown, the cloud XR entity 708 may perform a combination process 740 based on the uplink information 734. For example, the cloud XR entity 708 may perform virtual-physical fusion based on the vehicle XR component 736 and the user XR component 738 of the uplink information 734. In some examples, the combination process 740 may include associating an enhanced component with the vehicle surrounding information based on the environmental component. For example, the cloud XR entity 708 may identify the environmental component (e.g., a real-world object) based on the vehicle XR component 736 of the uplink information 734. The cloud XR entity 708 may then associate the enhanced component with the environmental component. For example, the cloud XR entity 708 may identify a stadium and associate the enhanced component with the stadium. The enhanced component may include one or more of an identifier of a landmark (e.g., the name of the stadium) and an interactive object. The interactive object may be selected by the user to access additional information related to the real-world object.

[0170] In some examples, the combining process 740 may include combining information from the vehicle UE 704 (eg, uplink information 734) with information from a service entity providing the service. Combining information based on information from the service entity is a combination of Fig.14 and Fig.15 is described by example.

[0171] In some examples, the combining process 740 may include associating multiple attributes of the uplink information based on at least the first timestamp and the second timestamp. For example, the vehicle XR component 736 may include at least the first timestamp and the user XR component 738 may include at least the second timestamp. The cloud XR entity 708 may use the first timestamp and the second timestamp to associate the attributes of the uplink information 734 and / or compensate for differences in different attributes of the uplink information 734.

[0172] The cloud XR entity 708 may perform a determination process 742 to determine what information to provide to the vehicle UE 704. For example, the cloud XR entity 708 may determine different XR information to provide to the vehicle UE 704 based on, for example, a subscription level, a QoS profile, a user identifier, privacy controls, etc. For example, based on the subscription level and the corresponding supported session level associated with the vehicle XR session 726, the cloud XR entity 708 may determine to include different levels of interaction via the XR information provided to the vehicle UE 704.

[0173] The cloud XR entity 708 may perform a generation process 744 to generate rendering information 746. The rendering information 746 may be based on the outputs of the combination process 740 and the determination process 742. In some examples, the rendering information 746 may be configured based on the display capabilities of the vehicle 706. For example, the cloud XR entity 708 may adjust the rendering information 746 based on whether the rendering information 746 is for presentation via a glasses-based display or a glasses-free display. The cloud XR entity 708 may then output the rendering information 746 that is obtained by the vehicle UE 704.

[0174] like Figure 7 As shown, the vehicle UE 704 may perform a rendering process 748 to present the rendering information 746. For example, the vehicle UE 704 may present the rendering information 746 via one or more displays of the vehicle 706. Various aspects of the display of the vehicle 706 may be displayed by Figure 5 The first display 510, the second display 520, the third display 522 and / or the fourth display 530 are implemented.

[0175] Figure 8 An example communication flow 800 between a network entity 802 and a vehicle UE 804 as presented herein is illustrated. Aspects of the network entity 802 may be implemented by the cloud XR entity 708. Figure 8 In the illustrated example of FIG. 8 , communication flow 800 facilitates establishing a vehicle XR session between a network entity 802 and a vehicle UE 804. For example, communication flow 800 may facilitate executing Figure 7 In another example, the signaling between the vehicle UE 804 and the network entity 802 may be performed by Figure 7 The network entity 702 forwards the message.

[0176] like Figure 8 As shown, vehicle UE 804 may send a session request 810 that is obtained (eg, received) by network entity 802. Figure 7 As described in connection with the session request 722 of FIG. 8 , the session request 810 may indicate a request to establish a vehicle XR session with the network entity 802. The session request 810 may also indicate information that the network entity 802 may use to establish and maintain the vehicle XR session. In some examples, the session request 810 may include vehicle information 812, QoS information 814, subscription credential information 816, and / or subscription request information 818. Figure 8In the example of , the transportation information 812, QoS information 814, subscription credential information 816, and subscription request information 818 are illustrated as separate communications, but in other examples, one or more of the transportation information 812, QoS information 814, subscription credential information 816 and / or subscription request information 818 may be included with the session request 810.

[0177] In some examples, the vehicle UE 804 may send vehicle information 812 obtained by the network entity 802. The vehicle information 812 may include information about a vehicle associated with the vehicle UE 804, such as Figure 7 The vehicle information 812 may include vehicle manufacturing information, vehicle model information, vehicle modem information, vehicle mobile equipment (ME) information, path planning information, traffic condition information, etc. In some examples, the path planning information may be provided via the navigation system of the vehicle. For example, the path planning information may indicate the destination and the route to the destination. In some examples, the traffic condition information may be associated with traffic light information obtained from other devices, for example, via side link communication. Some examples of side link communication may include communication from vehicle to vehicle (V2V), vehicle to infrastructure (V2I) (e.g., from a vehicle-based communication device to a road infrastructure node such as a roadside unit (RSU)), vehicle to network (V2N) (e.g., from a vehicle-based communication device to one or more network nodes such as a base station), vehicle to pedestrian (V2P), cellular vehicle-to-vehicle (C-V2X), and / or combinations thereof, and / or a vehicle-based communication device communicating with other devices, which may be collectively referred to as vehicle-to-vehicle (V2X) communication. In some examples, the network entity 802 may obtain the vehicle information via a third party other than the vehicle UE 804. For example, the network entity 802 may obtain the vehicle information directly from the RSU, from another UE, or using other connected sensors including cameras or radars.

[0178] In some examples, the transport UE 804 may send QoS information 814 obtained by the network entity 802. The QoS information 814 may indicate data rates supported by the transport UE 804 and / or a mobile device of a user associated with the transport XR session. The QoS information 814 may also or alternatively indicate whether a data rate has been received by the transport UE 804 (e.g., via Figure 7The QoS information 814 may also indicate whether an associated protocol data unit (PDU) session is established and whether any guaranteed bit rate (GBR) bearers are established. In some examples, the QoS information 814 may include an identifier of the UE, such as a general public subscription identifier (GPSI). The identifier of the UE may enable the network entity 802 to obtain a UE identifier from another network entity such as Figure 1 The AMF 192 obtains QoS monitoring / prediction information.

[0179] In some examples, a vehicle XR session may be associated with a subscription. A subscription may facilitate receiving one or more services associated with a vehicle XR session. A subscription may provide one or more services to only one user associated with the vehicle XR session (e.g., a driver or a passenger) or to more than one user (e.g., a driver and one or more passengers, or two or more passengers). In some examples, a subscription may be associated with different sets of services for different users. For example, a subscription may provide a first set of services (e.g., one or more services) to a driver, and may provide a second set of services (e.g., one or more services) to a passenger. In some examples, a subscription may be associated with different sets of services for passengers. For example, the set of services provided to a passenger may be based on the age of the passenger (e.g., different sets of services associated with children, teenagers, adults, etc.) and / or the position of the passenger in the vehicle (e.g., different sets of services associated with passengers in the front row compared to passengers in the back row).

[0180] In some examples, the subscription may be a vehicle-based subscription. A vehicle-based subscription may be associated with a vehicle (e.g., Figure 7 The vehicle 706 of the vehicle is associated, and one or more services can be registered with the vehicle. For example, one or more services can be provided to the user of the vehicle based on the subscription of the vehicle.

[0181] In some aspects, the subscription may be a user-based subscription. The user-based subscription may be associated with a user (e.g., via a user identifier), and one or more services may be registered with the user. For example, a user-based subscription may enable a user to access one or more services associated with their subscription from different vehicles, such as a rental vehicle. In some examples, a user-based subscription may allow a user to transfer a vehicle XR session from one vehicle to another, for example, in the case of carpooling. The user-based subscription information may be shared locally with the vehicle UE 804 so that it can be used for corresponding vehicle XR session control. The local sharing mechanism for subscription information may depend on the connectivity available in the vehicle, such as via Bluetooth, Wi-Fi, or other device-to-device communication technology.

[0182] The subscription may be an existing subscription or may be requested. In some examples, the vehicle UE 804 may send subscription credential information 816 obtained by the network entity 802. The subscription credential information 816 may include credentials associated with an existing subscription to the vehicle XR service. The credentials may be stored in and / or associated with a subscriber identity module (SIM), a vehicle mobile equipment (ME), and / or an IP multimedia subsystem (IMS) like credentials. For example, a ME identifier (e.g., an international mobile equipment identity (IMEI) or a UE ID) may be used for authorization and / or authentication. In some examples, the credentials may be stored in a virtual SIM, a secure environment of a ME, or a physical security token. In some examples, the credentials may additionally or alternatively use different formats that may be supported by the network entity 802, such as 3GPP-defined credentials, or other credentials including certificates issued or authorized by other authorities, etc.

[0183] In some examples, the vehicle UE 804 may send subscription request information 818 obtained by the network entity 802. The subscription request information 818 may include information associated with creating a subscription to the vehicle XR service. Aspects of the subscription request information 818 may be collected via an online registration process, an application store, and / or payment information (e.g., credit card, mobile payment, etc.).

[0184] like Figure 8 As shown, the network entity 802 may perform an authorization process 820 to establish a vehicle XR session 826. In some examples, the authorization process 820 may include a subscription management process 822. For example, the network entity 802 may perform subscription registration and subscription control. For example, the network entity 802 may create a subscription based on the subscription request information 818. In some examples, the network entity 802 may verify the subscription credential information 816 to confirm that the vehicle UE 804 is authorized to access the vehicle XR session.

[0185] The network entity 802 may also determine a supported session level 824. The network entity 802 may determine the supported session level 824 based on information obtained and / or associated with the session request 810, such as vehicle information 812, QoS information 814, and / or subscription credential information 816. For example, the supported session level 824 may be associated with a subscription level, supported QoS, a user identifier, and / or privacy controls. The supported session level 824 may enable the network entity 802 to perform granular support for services supported by the vehicle XR session 826. For example, based on the supported session level 824, the network entity 802 may determine to enable and / or disable one or more services and / or may determine a level of XR interaction.

[0186] In some examples, the supported session level 824 may be based in part on the location and / or the path plan of the vehicle. For example, the vehicle information 812 may indicate the location of the vehicle and / or the path plan of the vehicle. The network entity 802 may obtain the supported QoS along the path plan of the vehicle based on the vehicle information 812 (e.g., via a predicted QoS process), and determine the supported session level 824 of the vehicle XR session 826 based on the supported QoS. For example, the network entity 802 may determine that portions of the path plan may have different levels of network support capabilities based on the vehicle information 812, and adjust the supported session level 824 of the vehicle XR session 826 accordingly.

[0187] Determining supported session levels 824 based on supported QoS may enable network entity 802 to ensure that the user experience of a user (e.g., a driver) is not impaired. Supported session levels 824 may be used by network entity 802 to schedule transmission plans, encoding of information, or even feedback to Figure 7 The network entity 702 may adjust the rendering information structure. For example, in an example where the vehicle XR session 826 is associated with multiple users (e.g., a driver and one or more passengers), the network entity 802 may determine a supported session level 824 so that the passenger XR session does not interfere with the driver's experience. For example, different session levels may provide different levels of XR interactivity, and the supported session level 824 may be associated with the level of XR interactivity based on the supported QoS.

[0188] In some examples, the network entity 802 can determine the supported session level 824 based on the location of the vehicle UE 804. For example, the vehicle information 812 can include vehicle surrounding information indicating that the vehicle is traveling next to a roadblock on one side of the vehicle. In such examples, the supported session level 824 can adjust the information provided to the vehicle UE 804 so that the information for presentation on the roadblock side is reduced, thereby reducing the amount of information communicated to the vehicle UE 804.

[0189] In some examples, the network entity 802 may determine the supported session level 824 based on the user and / or privacy control. For example, different services may be associated with different users. In such examples, the XR information presented to the user may be based on the user's associated services. For example, certain public locations / services may provide XR information. In such examples, XR information may be presented to certain users, but not to other users. For example, XR information may be presented to a user who is a police officer that is not presented to a user who is not a police officer. As another example, house-based XR information associated with a house may be presented to a real estate agent, while house-based XR information may not be presented to the general public and / or limited house-based XR information may be presented to the general public. For example, a real estate agent may see information indicating that the house is on the market, while the general public may not see information about the house or may see the address of the house.

[0190] As another example, if a user has a subscription to a sports channel, the user may be presented with additional XR information and / or more in-depth information than a user who does not have a subscription to the sports channel. For example, when a stadium is visible, one supported session level may provide information such as the name of the stadium, and another supported session level may provide additional information related to the stadium, such as the home team of the stadium, whether there is an ongoing game (or a recently played game), the score of the game, the schedule of the game, etc.

[0191] Thus, the supported session level 824 may facilitate the network entity 802 determining what information to provide to the vehicle UE 804 for presentation associated with the vehicle XR session 826. For example, based on the supported session level 824 and in association with the vehicle XR session 826, the network entity 802 may determine what XR information to provide to the vehicle UE 804 and / or may determine how much XR information to provide to the vehicle UE 804.

[0192] like Figure 8 As shown, the network entity 802 may output a session response 830 obtained (eg, received) by the vehicle UE 804. Figure 7 As described by session response 728 , session response 830 may confirm that a vehicle XR session 826 is established between the vehicle UE 804 and the network entity 802 .

[0193] In some examples, the session response 830 may include a session configuration 832. The session configuration 832 may configure one or more operating parameters associated with the vehicle XR session 826 at the vehicle UE 804. For example, the session configuration 832 may include an indication of a supported session level 824 associated with the vehicle XR session 826. The session configuration 832 may be based on the supported session level 824. In some examples, the session configuration 832 may configure a network connection type at the vehicle UE 804. In some examples, the session configuration 832 may configure an update frequency (e.g., periodicity) associated with uplink information associated with the vehicle XR session 826. For example, the session configuration 832 may configure a vehicle XR component of the uplink information (e.g., Figure 7 The first periodicity associated with the vehicle XR component 736 of the uplink information and the user XR component (eg, Figure 7 A second periodicity associated with the user XR component 738).

[0194] In some examples, the network entity 802 may provide a configuration associated with a quality of experience (QoE) parameter for a vehicle XR session 826. For example, the network entity 802 may output a QoE measurement configuration 834 received by the vehicle UE 804. The QoE measurement configuration 834 may be based on the supported session level 824 and / or the QoS information 814. The QoE measurement configuration 834 may facilitate providing fast and accurate rendering information to the vehicle UE 804. For example, the QoE measurement configuration 834 may facilitate accurate placement of enhancement components for presentation at the vehicle. In some examples, the QoE measurement configuration 834 may be associated with latency and / or capacity. For example, the QoE measurement configuration 834 may configure a latency threshold, a retransmission threshold, and / or a data rate threshold.

[0195] In some examples, the transport UE 804 can collect QoE metrics based on the QoE measurement configuration 834. Examples of QoE metrics can include delays associated with transmissions, observed packet retransmissions, and / or data rates. In some examples, the transport UE 804 can send a session request 810 when events associated with the QoE metrics are met. For example, the transport UE 804 can send a session request 810 when the delay exceeds a delay threshold, the observed packet retransmissions exceed a retransmission threshold, and / or the capacity does not meet a data rate threshold (e.g., the data rate is lower than the data rate allowed by the network).

[0196] Although in Figure 8 In the example of , the session configuration 832 and the QoE measurement configuration 834 are illustrated as separate communications, but in other examples, one or both of the session configuration 832 and the QoE measurement configuration 834 may be included with the session response 830.

[0197] Fig. 9 An example communication flow 900 between a network entity 902 and a vehicle UE 904 as presented herein is illustrated. Aspects of the network entity 902 may be Figure 7 The cloud XR entity 708 and / or Figure 8 Various aspects of the vehicle UE 904 may be implemented by the network entity 802. Figure 7 UE 704 and / or Figure 8 The UE 804 is implemented.

[0198] exist Fig. 9 In the illustrated example of FIG. 1 , the communication flow 900 facilitates providing a vehicle-to-cloud XR service associated with a vehicle XR session. For example, a vehicle UE 904 and a network entity 902 may establish a vehicle XR session 910, such as in conjunction with Figure 7 Session establishment process 720 and / or Figure 8 The vehicle XR session 910 may include one or more information flows that facilitate the exchange of information associated with respective users between the network entity 902 and the vehicle UE 904. Fig. 9 As shown, the vehicle XR session 910 includes a first user XR stream 930 and a second user XR stream 950. The first user XR stream 930 can facilitate the exchange of information with the first user such as Figure 5 The second user XR stream 950 may facilitate exchanging information with a second user such as Figure 5 The information associated with the first passenger 504. Fig. 9 Examples include two information streams (e.g., first user XR stream 930 and second user XR stream 950 ) (which may also be referred to as “sub-sessions” or “layers” of the vehicle XR session), but other examples may include any suitable number of information streams, for example based on the number of users accessing the vehicle XR session 910 .

[0199] The vehicle UE 904 may send uplink information obtained by the network entity 902, such as in conjunction with Figure 7 The uplink information may include one or more components. Fig. 9In the example of , the vehicle UE 904 sends a vehicle XR component 920 obtained by the network entity 902. The vehicle XR component 920 may include vehicle posture information 922 (e.g., position information, orientation information, direction information, heading information, speed information, yaw information, etc.), vehicle information 924 (e.g., vehicle manufacturing information, vehicle model information, vehicle modem information, vehicle mobile equipment (ME) information, path planning information, navigation information, traffic status information, etc.) and / or vehicle surrounding information 926 (e.g., environment information, building information, scenery information, etc.).

[0200] like Fig. 9 As shown, the vehicle XR session 910 includes a first user XR stream 930, which can facilitate communication between the network entity 902 and the vehicle UE 904 with a first user (eg, Figure 5 The first user XR stream 930 may include information associated with the driver 502 of the first user. For example, the first user XR stream 930 may include a component of the uplink information, such as a first user XR component 932. The first user XR component 932 may include user posture information 934 (e.g., the position and / or orientation of the first user). The user posture information 934 may be relative posture information and / or absolute posture information. For example, the user posture information 934 relative to the ground may be referred to as absolute user posture information. The user posture information 934 relative to the vehicle coordinate system may be referred to as relative user posture information. The first user XR component 932 may also or alternatively include user input information 936. The user input information 936 may include information related to eye tracking, such as the length of eye focus, and / or user gesture information associated with the first user. The user input information 936 may facilitate identification of when the first user is providing user input, such as selecting an enhanced component (e.g., an interactive object) presented via rendering information.

[0201] The first user XR stream 930 also includes first user rendering information 940. For example, the network entity 902 may output the first user rendering information 940 received by the vehicle UE 904. The first user rendering information 940 may include rendering information configured for presentation via one or more displays associated with the first user. For example, and with reference to Figure 5 In the example of , the first user rendered information 940 may be presented to the driver 502 via the first display 510 when the driver is looking forward, and may be presented to the driver 502 via the second display 520 when the driver 502 is looking in the direction of the window 516.

[0202] The first user rendering information 940 may include XR information configured to provide a satisfactory user experience to the first user. For example, the first user rendering information 940 may include an enhancement component associated with a path plan (e.g., direction), a landmark, and / or an interactive object. The enhancement component may be associated with the vehicle surrounding information. For example, the network entity 902 may identify an environmental component (e.g., a landmark such as a stadium) via the vehicle XR component 920. The network entity 902 may then associate the enhancement component with the vehicle surrounding information based on the environmental component. For example, the network entity 902 may associate an identifier of a landmark (e.g., a stadium name) with the environmental component. Therefore, the first user rendering information 940 may include an enhancement component associated with a real-world object and related to the user experience of the first user.

[0203] like Fig. 9 As shown, the vehicle XR session 910 may also include a second user XR stream 950, which may facilitate communication between the network entity 902 and the vehicle UE 904 with respect to a second user (eg, Figure 5 The second user XR stream 950 may include information associated with the first passenger 504 or the second passenger 506 of the user. For example, the second user XR stream 950 may include a component of the uplink information, such as a second user XR component 952. The second user XR component 952 may be similar to the first user XR component 932, but relative to the second user. For example, the second user XR component 952 may include user posture information 954 (e.g., the position and / or orientation of the second user). The user posture information 954 may be relative posture information and / or absolute posture information. The second user XR component 952 may also or alternatively include user input information 956. The user input information 956 may include information related to eye tracking, such as the length of eye focus, and / or user gesture information associated with the second user. The user input information 956 may facilitate identifying when the second user is providing user input, such as selecting an enhanced component (e.g., an interactive object) presented via rendering information.

[0204] The second user XR stream 950 also includes second user rendering information 960. For example, the network entity 902 may output the second user rendering information 960 received by the vehicle UE 904. Similar to the first user rendering information 940 associated with the first user XR stream 930, the second user rendering information 960 may include rendering information configured for presentation via one or more displays associated with the second user. For example, and with reference to Figure 5 For example, the second user rendered information 960 may be presented to the first passenger 504 via the first display 510 when the first passenger 504 is looking forward, and may be presented to the first passenger 504 via the third display 522 when the first passenger is looking in the direction of the third display 522.

[0205] Similar to the first user rendering information 940, the second user rendering information 940 may include XR information configured to provide a satisfactory user experience to the second user. For example, the second user rendering information 960 may include an enhancement component associated with a real-world object. The enhancement component may include an identifier of a real-world object and / or an interactive object.

[0206] exist Fig. 9 In the example of , the rendering information may be based on the user XR component and the vehicle XR component. Therefore, in some examples, the vehicle XR component 920 may be shared between the first user XR stream 930 and the second user XR stream 950. Communications associated with different user sessions may be communicated separately or together. For example, the vehicle UE 904 may send uplink information including the vehicle XR component 920, the first user XR component 932, and / or the second user XR component 952. Additionally, the network entity 902 may output rendering information including the first user rendering information 940 and / or the second user rendering information 960. For example, the rendering information may include a first rendering information component corresponding to the first user rendering information 940 and a second rendering information component corresponding to the second user rendering information 960.

[0207] like Fig. 9 As shown, one or more aspects of the uplink information (e.g., the vehicle XR component 920, the first user XR component 932, and / or the second user XR component 952) may include timing information. For example, the vehicle XR component 920 may be associated with a first timestamp 928, the first user XR component 932 may be associated with a second timestamp 938, and the second user XR component 952 may be associated with a third timestamp 958. The respective timestamps may include a date and / or time at which the corresponding information was collected. The timing information may facilitate correlating attributes of the uplink information and / or compensating for attributes of the uplink information. Aspects of correlating attributes of the uplink information and / or compensating for attributes of the uplink information are combined Fig.14 The communication flow 1400 is described.

[0208] Fig.10 1 is a diagram illustrating information 1000 that may be exchanged with a network entity as presented herein. Information 1000 may be collected by a UE for communication to a network entity. Aspects of collecting information 1000 are in conjunction with Figure 7 For example, the information may be collected via one or more sensors of the vehicle such as Figure 5 The information is collected by one or more sensors 512 of the vehicle 500.

[0209] exist Fig.10In the example of , information 1000 includes aspects of a vehicle XR component 1010, such as vehicle posture information. The vehicle XR component 1010 may include information related to the position and / or orientation of the vehicle 1002. For example, Fig.10 The vehicle XR component 1010 may include vehicle orientation, speed, heading, yaw, pitch, and / or roll. The vehicle XR component 1010 may be based on relative positioning or absolute positioning. An example of absolute positioning is Fig.10 Marked by X E , Y E and Z E An example of relative positioning is shown in Fig.10 Marked by X V , Y V and Z V The vehicle XR component 1010 may also include the surrounding environment of the vehicle 1002, such as Fig. 9 The vehicle surrounding information 926. The vehicle XR component 1010 may also or alternatively include a path plan (eg, from a navigation system) that provides directions to a desired destination.

[0210] exist Fig.10 In the example of , information 1000 may also include aspects of user XR component 1020, such as user pose information. User pose information may refer to the position and / or orientation of the user in space relative to the XR space. For example, user XR component 1020 may include the orientation of the user. User XR component 1020 may also include video and / or camera input, such as the surrounding environment, user eye tracking, and / or user gestures (e.g., based on a hand device).

[0211] In some examples, the information 1000 associated with the user XR component 1020 may correspond to an absolute pose, for example, relative to the ground. In some examples, the user XR component 1020 may correspond to a relative pose, for example, relative to a vehicle coordinate system. For example, the user's orientation may be relative to the ground (e.g., an absolute pose) or may be relative to a vehicle coordinate system (e.g., a relative pose). In a similar manner, a user gesture may be described relative to the ground (e.g., an absolute gesture) or may be described relative to a vehicle coordinate system (e.g., a relative gesture). In some examples, information related to relative gestures and / or relative poses may be collected via sensors in the cabin of the vehicle 1002.

[0212] Fig.11 1100 between a network entity 1102 and a vehicle UE 1104 as presented herein. Aspects of the network entity 1102 may be communicated by a vehicle to a cloud platform such as Figure 7 The cloud XR entity 708 and / or Figure 8Aspects of the vehicle UE 1104 may be implemented by an XR-enabled vehicle such as Figure 5 500 and / or Figure 7 This is achieved by using the vehicle UE 704 and the vehicle 706.

[0213] exist Fig.11 In the illustrated example of FIG. 1 , the network entity 1102 and the vehicle UE 1104 communicate via a communication system 1106. Aspects of the communication system 1106 are combined with Figure 7 The network entity 1102 is described with reference to the network entity 702. For example, the network entity 1102 and the vehicle UE 1104 can communicate via the 5G NR system.

[0214] like Fig.11 As shown, the vehicle UE 1104 can send an XR session request 1110 that is obtained (e.g., received) by the network entity 1102. Various aspects of the XR session request 1110 can be obtained by Figure 7 Session request 722 and / or Figure 8 The session request 810 is implemented. Fig.11 In the illustrated example of , the vehicle UE 1104 may send QoS support information 1112 associated with the XR session request 1110. The QoS support information 1112 may facilitate XR rendering adaptation by the network entity 1102.

[0215] QoS support information 1112 may include data rates supported by a vehicle and / or a user's mobile device associated with the vehicle XR session. In some examples, QoS support information 1112 may indicate whether a network connection has been established (e.g., via the communication system 1106). For example, QoS support information 1112 may indicate that the vehicle UE 1104 has established a network connection with the communication system 1106 and whether there are one or more XR-based PDU sessions associated with the network connection. For example, an XR-based PDU session may be associated with a QoS flow (e.g., a GBR QoS flow) that requires a guaranteed stream bit rate, and therefore, QoS support information 1112 may indicate whether one or more GBR bearers have been established to facilitate communications associated with the vehicle XR session.

[0216] In some examples, the XR session request 1110 may include a vehicle identifier 1114. For example, the vehicle identifier 1114 may include a vehicle ME identifier, a UE ID, a GPSI, etc. The network entity 1102 may use the vehicle identifier 1114 to obtain QoS monitoring information and / or QoS prediction information from the communication system 1106. For example, the network entity 1102 may output a request 1120 obtained by the communication system 1106. The request 1120 may include the vehicle identifier 1114. The communication system 1106 may use the vehicle identifier 1114 to obtain QoS monitoring information and / or QoS prediction information associated with the vehicle UE 1104. The communication system 1106 may then send a response 1122 based on the request 1120 and include the QoS monitoring information and / or QoS prediction information.

[0217] In some examples, the network entity 1102 may configure the vehicle UE 1104 to collect and provide QoE metrics. For example, to facilitate XR rendering adaptation, the network entity 1102 may output a QoE measurement configuration 1130 received by the vehicle UE 1104. In some examples, the network entity 1102 may respond to a request via a session such as Figure 7 The QoE measurement configuration 1130 may be provided based on the session response 728 and / or the session response 830 of the vehicle UE 1104. The QoE measurement configuration 1130 may be based on the supported session level and / or QoS support information 1112. The QoE measurement configuration 1130 may facilitate providing fast and accurate rendering information to the vehicle UE 1104. For example, the QoE measurement configuration 1130 may facilitate accurate placement of enhancement components for presentation at the vehicle. In some examples, the QoE measurement configuration 1130 may be associated with delay and / or capacity. For example, the QoE measurement configuration 1130 may configure a delay threshold, a retransmission threshold, and / or a data rate threshold.

[0218] In some examples, the transport UE 1104 may collect QoE metrics based on the QoE measurement configuration 1130. Examples of QoE metrics may include latency associated with transmission, observed packet retransmissions, and / or data rates. In some examples, the transport UE 1104 may send an XR session request 1110 when an event associated with the QoE metric is met. For example, the transport UE 1104 may send an XR session request 1110 when latency exceeds a latency threshold, observed packet retransmissions exceed a retransmission threshold, and / or capacity does not meet a data rate threshold (e.g., the data rate is lower than the data rate allowed by the network).

[0219] Fig.12 1200 is illustrated as a communication flow between a network entity 1202 and a vehicle UE 1204 as presented herein. Aspects of the network entity 1202 may be similar to Fig.11 Aspects of the transport UE 1204 may be similar to Fig.11 The means of transport UE 1104. Fig.12 In the illustrated example of FIG. 1 , the network entity 1202 and the vehicle UE 1204 communicate with each other via a communication system 1206. Aspects of the communication system 1206 may be similar to Fig.11 Communication system 1106.

[0220] like Fig.12 As shown, the vehicle UE 1204 can output an XR session request 1210 obtained by the network entity 1202. Various aspects of the XR session request 1210 can be obtained by Figure 7 Session request 722 and / or Figure 8 For example, the XR session request 1210 may include transportation information, QoS information, subscription credential information, and / or subscription request information, such as in combination with Figure 8 As described.

[0221] The network entity 1202 may determine supported session levels based on the XR session request 1210, such as in conjunction with Figure 8 The supported session level 824 may be as described in the example of FIG. 12. For example, the XR session request 1210 may include subscription credential information, and the network entity 1202 may determine the subscription level based on the subscription credential information. The network entity 1202 may also determine the supported session level based on the subscription level.

[0222] In some examples, the network entity 1202 may determine which XR services to provide based on the subscription level. Fig.12 In an example of , example XR services include navigation service 1220, landmark service 1222, sports service 1224, and real estate agent service 1226. Navigation service 1220 may facilitate providing XR information related to navigation (e.g., path planning, etc.). Landmark service 1222 may facilitate providing XR information related to identifying landmarks. Sports service 1224 may facilitate providing XR information related to additional and / or in-depth information related to sports-based landmarks. Real estate agent service 1226 may facilitate providing XR information related to real estate (e.g., information about houses on the market, sellers' agents, etc.).

[0223] Other examples may include additional or alternative XR services that provide immersive XR experiences to users, such as passengers. For example, a shopping service may enable a passenger to initiate and participate in a shopping experience. A video conferencing service may enable a passenger to initiate and participate in a video conference. A gaming service may enable a passenger to initiate and participate in a gaming session with other passengers in the area (e.g., via vehicle-to-vehicle (V2V) communications).

[0224] exist Fig.12 In the example of , the network entity 1202 may determine that the user has access to certain XR services and does not have access to other XR services based on the XR session request 1210. For example, the network entity 1202 may determine to provide access to the navigation service 1220, the landmark service 1222, and the sports service 1224, and not provide access to the real estate agent service 1226. As described above, access to different XR services may be based on a subscription level, a user identifier, and / or based on privacy controls.

[0225] Different XR services may provide different XR information for presentation via rendering information. For example, based on the landmark service 1222, the network entity 1202 may provide XR information identifying a government building 1230 and a stadium 1232. If the user has a subscription to a sports channel, the network entity 1202 may determine to provide access to the sports service 1224 and provide additional information related to the stadium 1232. For example, the XR information associated with the stadium 1232 may indicate a game being played at the stadium 1232, may indicate the current score of the game, etc. In some examples, the XR information associated with the stadium 1232 may provide a transaction opportunity. For example, the XR information associated with the stadium 1232 may include an interactive object that facilitates the purchase of tickets for an upcoming game at the stadium 1232.

[0226] Fig.13 1300 between a network entity 1302 and a vehicle UE 1304 as presented herein. Aspects of the network entity 1302 may be similar to Fig.11 The network entity 1102 and / or Fig.12 Aspects of the transport UE 1304 may be similar to Fig.11 UE 1104 and / or Fig.12 The means of transport UE 1204. Similar to Fig.11 and Fig.12 For example, Fig.13 In the illustrated example of FIG. 1 , the network entity 1302 and the vehicle UE 1304 communicate with each other via a communication system 1306. Aspects of the communication system 1306 may be similar to Fig.11 The communication system 1106 and / or Fig.12 Communication system 1206.

[0227] Fig.13 The communication flow 1300 of facilitating vehicle XR session and service management. In some examples, the communication flow 1300 may facilitate a vehicle XR session including interactive objects. Fig.13In the example of FIG. 1 , the network entity 1302 outputs an XR session setup message 1310 obtained by the vehicle UE 1304. Aspects of the XR session setup message 1310 may be obtained by Figure 7 Session response 728 and / or Figure 8 830. For example, the XR session establishment message 1310 may indicate the supported session level and / or session configuration. In some examples, the XR session establishment message 1310 may configure one or more operating parameters at the vehicle UE 1304. For example, the XR session establishment message 1310 may indicate the type of network connection to be established (e.g., via the communication system 1306), the update frequency associated with the uplink information, etc. In some examples, the update frequency (e.g., periodicity) may be associated with different components of the uplink information. For example, the XR session establishment message 1310 may configure a first periodicity associated with the vehicle XR component and a second periodicity associated with the user XR component. The vehicle UE 1304 may collect information associated with different XR components based on the corresponding periodicity. For example, the vehicle UE 1304 may collect information associated with the vehicle XR component based on the first periodicity, and collect information associated with the user XR component based on the second periodicity.

[0228] As above combined Figure 7 As described in the collection process 732, the vehicle UE 1304 can use one or more sensors of the vehicle such as Figure 5 The vehicle UE 1304 may output uplink information 1320 obtained by the network entity 1302. Various aspects of the uplink information 1320 may be obtained by the vehicle UE 1304. Figure 7 This is achieved by transmitting the uplink information 734.

[0229] The network entity 1302 may obtain the uplink information 1320 and fuse the attributes of the uplink information 1320 to generate rendering information, such as Figure 7 The network entity 1302 may provide the rendering information to the vehicle UE 1304 for display via one or more displays of the vehicle (such as Figure 5 The display may be presented on a first display 510, a second display 520, a third display 522 and / or a fourth display 530).

[0230] In some examples, network entity 1302 may have the capability to provide XR services. For example, network entity 1302 may have the capability to provide navigation services and landmark services (such as Fig.12In some examples, network entity 1302 may have the ability to communicate with another network entity that provides XR services. For example, network entity 1302 may establish a first connection 1330 to communicate with a real estate agent service (such as Fig.12 The network entity 1302 may establish a second connection 1334 to communicate with a first network entity 1332 that provides a sports service (such as a real estate agent service 1226). Fig.12 The first network entity 1332 and the second network entity 1336 may communicate with each other through the sports service 1224. It may be understood that the first network entity 1332 and the second network entity 1336 may be the same network entity or may be different network entities.

[0231] exist Fig.13 In the example of FIG. 13 , the rendered information provided to the vehicle UE 1304 may include an interactive object. For example, the rendered information may include an interactive object 1340 superimposed on a real-world object (e.g., a stadium). The interactive object 1340 may enable a user (e.g., a passenger) to select the interactive object 1340 and obtain additional or in-depth information related to the stadium. For example, selecting the interactive object 1340 may provide additional information about the stadium, such as the current score of a game being played at the stadium.

[0232] exist Fig.13 In the example of FIG. 13 , when a user interacts with an interactive object such as interactive object 1340, vehicle UE 1304 may generate user interaction information 1322 based on the interaction. User interaction information 1322 may provide information about what interactive object was selected. Fig.13 As shown, the vehicle UE 1304 may provide user interaction information 1322 to the network entity 1302 via uplink information (e.g., uplink information 1320). The network entity 1302 may then generate and output subsequent rendering information based in part on the user interaction information 1322. For example, in Fig.13 In the illustrated example of , the subsequent rendering information may include score information 1342 indicating the score of the current game being played at the stadium.

[0233] In some examples, network entity 1302 may communicate with second network entity 1336 via second connection 1334 to provide score information 1342. For example, network entity 1302 may receive user interaction information 1322 and determine a user interaction with interactive object 1340. Network entity 1302 may also determine that interactive object 1340 is associated with a sports service provided by second network entity 1336. In such examples, network entity 1302 may communicate with second network entity 1336 to obtain additional information associated with the stadium, if any. Fig.13In the example of , second network entity 1336 may identify score information 1342 and provide score information 1342 to network entity 1302, for example, via second connection 1334. Network entity 1302 may then generate subsequent rendering information including score information 1342 for presentation at the vehicle.

[0234] Fig.14 1400 is illustrated as a communication flow between a network entity 1402 and a vehicle UE 1404 as presented herein. Aspects of the network entity 1402 may be similar to Fig.11 Network entity 1102, Fig.12 The network entity 1202 and / or Fig.13 Aspects of the transport UE 1404 may be similar to Fig.11 UE 1104, Fig.12 UE 1204 and / or Fig.13 The vehicle UE 1304. Fig.14 1404, but the network entity 1402 and the vehicle UE 1404 may communicate via a communication system such as Fig.11 Communication system 1106, Fig.12 The communication system 1206 and / or Fig.13 communication system 1306) to communicate with each other.

[0235] exist Fig.14 In the illustrated example of FIG. 1 , communication flow 1400 facilitates access to an XR service provided by another network entity, such as a non-automotive XR platform 1406. The non-automotive XR platform 1406 may provide services that may not be associated with a vehicle-based service. For example, the non-automotive XR platform 1406 may provide services, such as purchasing tickets to a game or buying coffee.

[0236] exist Fig.14 In the illustrated example of FIG. 1 , the network entity 1402 may be configured to receive information from the vehicle UE 1404 and / or the non-vehicle XR platform 1406 and process the received information for use by the vehicle UE 1404 and / or the non-vehicle XR platform 1406. For example, the vehicle UE 1404 may output uplink information 1410 obtained by the network entity 1402. The uplink information 1410 may include a vehicle XR component and a user XR component, such as a combination of Fig. 9 The uplink information 1410 may include information related to the vehicle XR component 920 and the first user XR component 932. For example, the uplink information 1410 may include information related to speed, heading, user location, XR device capabilities (e.g., glasses-based display, glasses-free display, etc.), user profiles (e.g., subscription credentials, etc.).

[0237] The network entity 1402 may then condition the uplink information 1410 to generate the service request information 1420. The network entity 1402 may condition the uplink information 1410 so that the non-automotive XR platform 1406 may use the service request information 1420 without knowing the automotive use of the service. For example, the network entity 1402 may aggregate and translate the uplink information 1410 (such as location, directional gestures, targets, etc.) to generate the service request information 1420. The service request information 1420 may include a service request and a user profile. The network entity 1402 may condition the uplink information 1410 to generate the service request information 1420 that the non-automotive XR platform 1406 may expect to receive when receiving the service request. The network entity 1402 may perform the translation of the uplink information 1410 based on knowledge of the vehicle (such as brand, model, and / or additional vehicle-specific information such as original equipment manufacturer (OEM) information).

[0238] The network entity 1402 may then output service request information 1420 obtained by the non-automotive XR platform 1406. The non-automotive XR platform 1406 may then operate as usual based on the service request information 1420. For example, the non-automotive XR platform 1406 may use the service request information 1420 to generate service output information 1430. The service output information 1430 may be based on the service request information 1420 and be unaware that the service request information 1420 is generated based on information obtained from the vehicle and associated with the vehicle XR session. In some examples, the service output information 1430 may include data for rendering based on the service performed by the non-automotive XR platform 1406.

[0239] The non-automotive XR platform 1406 may output service output information 1430 obtained by the network entity 1402. The network entity 1402 may then transcode the service output information 1430 for rendering at the vehicle. For example, the network entity 1402 may transcode data obtained from the non-automotive XR platform 1406 via the service output information 1430 based on one or more attributes of the uplink information 1410. For example, based on the speed, direction, rendering capabilities, etc. of the vehicle UE 1404, the network entity 1402 may generate transcoded data 1440. The network entity 1402 may output the transcoded data 1440 to the vehicle UE 1404 for presentation via one or more displays of the vehicle associated with the vehicle XR session. Aspects of the one or more displays of the vehicle may be displayed by Figure 5 The system may be implemented by one or more displays (eg, a first display 510 , a second display 520 , a third display 522 , and / or a fourth display 530 ) of the vehicle 500 .

[0240] In some examples, generating service request information 1420 and / or transcoded data 1440 by network entity 1402 may include correlating and / or compensating for differences associated with uplink information 1410. For example, one or more attributes of uplink information 1410 may include timing information, enabling network entity 1402 to compensate for differences between, for example, the time when network entity 1402 received uplink information 1410 and the time when transcoded data 1440 was generated. In some such examples, uplink information 1410 may include one or more timestamps, such as Fig. 9 A first timestamp 928 associated with the vehicle XR component 920 and a second timestamp 938 associated with the first user XR component 932 .

[0241] As based on Fig.14 As one example of the operation of communication flow 1400, non-automotive XR platform 1406 may be associated with a coffee business and may provide services associated with purchasing goods at the coffee business, for example, via a mobile application. In such an example, uplink information 1410 may include user interaction information such as Fig.13 The uplink information 1410 may also include information about the route plan of the vehicle. The network entity 1402 may use the route plan and navigation services of the vehicle to identify the location of the coffee business on the route plan. The network entity 1402 may adjust the uplink information 1410 (including the user interaction information) to generate service request information 1420 to initiate the purchase of the selected coffee. The service request information 1420 may be configured with information that facilitates the purchase of coffee (e.g., coffee type, specifications, etc.), and there may be no information related to the vehicle. The non-automotive XR platform 1406 may use the service request information 1420 to execute the mobile order of the selected coffee and generate service output information 1430 obtained by the network entity 1402. The service output information 1430 may include verification of the successful purchase of the coffee and the expected time when the coffee is ready. The network entity 1402 may then generate transcoded data 1440 based on the service output information 1430 and one or more attributes of the uplink information 1410. For example, the transcoded data 1440 may include rendering information configured for presentation via one or more devices of a vehicle associated with the vehicle XR session.

[0242] Despite Fig.14Not shown in the example, but understandable, the communication flow 1400 between the vehicle UE 1404, the network entity 1402, and the non-automotive XR platform 1406 may be implemented via one or more application programming interfaces (APIs) or cloud-native services. The API or cloud-native service may provide exposure to one or more configuration and operating parameters. For example, the network entity 1402 may be configured with a first API or cloud-native service that enables the vehicle UE 1404 to communicate with the network entity 1402. The network entity 1402 may also be configured with a second API or cloud-native service that enables the network entity 1402 and the non-automotive XR platform 1406 to communicate. Therefore, the API or cloud-native service at the network entity 1402 and the non-automotive XR platform 1406 may enable certain interfaces to be exposed so that a service operator can provide non-automotive services for use via a vehicle XR session.

[0243] Fig.15 An example communication flow 1500 between a network entity 1502, a UE 1504, and a service entity 1506 as presented herein is illustrated. Aspects of the network entity 1502 may be provided by Figure 7 Cloud XR entity 708, Figure 8 The network entity 802 and / or Fig. 9 The network entity 902 is implanted. Fig.15 Although not shown in the illustrated example, it can be understood that the network entity 1502, the UE 1504 and the service entity 1506 can communicate via a communication system such as a 5G NR system.

[0244] exist Fig.15 In the illustrated example of , the communication flow 1500 may facilitate the execution of a transaction associated with a service provided by the service entity 1506. For example, the service entity 1506 may provide a service for ordering coffee from a coffee business via a mobile application. Aspects of the communication flow 1500 may be similar to Fig.14 Communication flow 1400.

[0245] exist Fig.15 In the example of , UE 1504 may output user interaction information 1510 obtained by network entity 1502. User interaction information 1510 may be included with uplink information output to network entity 1502. Network entity 1502 may perform identification 1512 of transaction interactions associated with the service. For example, network entity 1502 may determine that user interaction information 1510 includes a selection of an interactive object that facilitates the transaction. Fig.15 In the example of FIG. 15 , network entity 1502 may determine that the transaction is associated with a service provided by service entity 1506. Fig.15As shown, the network entity 1502 and the service entity 1506 may perform a connection establishment process 1514 to facilitate communication with each other. The network entity 1502 may output a service request 1516 obtained by the service entity 1506. Aspects of the service request 1516 may be similar to Fig.14 The service request 1516 may include service information 1420 of the network entity 1502. For example, the service request 1516 may include information to facilitate a transaction with the service entity 1506. The service entity 1506 may process the service request 1516 and may output service information 1518 obtained by the network entity 1502.

[0246] The network entity 1502 may generate 1520 transaction information using the service information 1518. In some examples, the network entity 1502 may generate transaction information 1522 based on the service information 1518 and the uplink information. The network entity 1502 outputs the transaction information 1522, which is received by the UE 1504. The UE 1504 may process the transaction information 1522 for presentation via one or more displays of a vehicle associated with the vehicle XR session.

[0247] For example, user interaction information 1510 may indicate a selection of an interactive object associated with a coffee business. Network entity 1502 may establish a connection with service entity 1506 that facilitates performing a transaction related to the coffee business, such as ordering coffee. Service information 1518 may include a menu of products provided by the coffee business and available for purchase. Transaction information 1522 may include rendering information that facilitates presenting the menu based on one or more displays of the vehicle. For example, network entity 1502 may adjust transaction information 1522 based on whether the rendering information will be presented via a HUD or a glasses-based display.

[0248] In some examples, the user may further interact with the rendering information based on the transaction information 1522. For example, the rendering information may include interactive objects corresponding to corresponding beverages that can be purchased via a menu. UE 1504 may output uplink information including a transaction message 1524 indicating the selection of the interactive object corresponding to the beverage. Network entity 1502 and service entity 1506 may then exchange transaction communications 1526 to place an order for the beverage. Network entity 1502 may also perform a generation process 1528 of subsequent rendering information 1530 based on the transaction communications 1526. Network entity 1502 may then output the subsequent rendering information 1530 for presentation via one or more displays associated with the vehicle XR session.

[0249] Fig.16 1600 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104 and / or Fig.18The method may facilitate improving a user experience associated with a vehicle XR session by using a cloud-based entity to reduce information sent OTA and / or reduce a computational load associated with a vehicle XR session at the UE.

[0250] At 1602, the UE sends a request for a vehicle XR session. Aspects of the request for a vehicle XR session are at least in conjunction with Figure 7 The vehicle XR session may be based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle, such as in conjunction with Figure 7 The request for a vehicle XR session sent at 1602 may be performed by Fig.18 The cellular RF transceiver 1822 of the device 1804 and / or the vehicle XR component 198 may be implemented.

[0251] In some examples, the vehicle XR component may include at least one of vehicle posture information, vehicle information, and vehicle surrounding information, such as at least one of the vehicle posture information, the vehicle information, and the vehicle surrounding information. Fig. 9 In some examples, the first user XR component may include relative user posture information about the vehicle and user input, such as at least in combination with Fig. 9 The first user XR component 932 is described.

[0252] At 1604, the UE sends uplink information associated with the first user XR stream. Aspects of the uplink information are combined with at least Figure 7 The uplink information 734 of FIG. 1604 may be sent by Fig.18 The cellular RF transceiver 1822 of the device 1804 and / or the vehicle XR component 198 may be implemented.

[0253] At 1606, the UE receives rendering information associated with the first user XR stream. Aspects of the rendering information are at least combined with Figure 7 The rendering information 746 is described. The rendering information received at 1606 may be Fig.18 The cellular RF transceiver 1822 of the device 1804 and / or the vehicle XR component 198 may be implemented.

[0254] Fig.17 1700 is a flowchart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104 and / or Fig.18The method may facilitate improving a user experience associated with a vehicle XR session by using a cloud-based entity to reduce information sent OTA and / or reduce a computational load associated with a vehicle XR session at the UE.

[0255] At 1702, the UE sends a request for a vehicle XR session. Aspects of the request for a vehicle XR session are at least in conjunction with Figure 7 The vehicle XR session may be based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle, such as in conjunction with Figure 7 The request for a vehicle XR session at 1702 may be sent by Fig.18 The cellular RF transceiver 1822 of the device 1804 and / or the vehicle XR component 198 may be implemented.

[0256] In some examples, the vehicle XR component may include at least one of vehicle posture information, vehicle information, and vehicle surrounding information, such as at least one of the vehicle posture information, the vehicle information, and the vehicle surrounding information. Fig. 9 In some examples, the first user XR component may include relative user posture information about the vehicle and user input, such as at least in combination with Fig. 9 The first user XR component 932 is described.

[0257] In some examples, the request for a vehicle XR session at 1702 may include subscription credentials, such as in conjunction with Figure 8 The subscription credentials information 816 described in the example. In some examples, the subscription credentials may be associated with a subscription level.

[0258] At 1704, the UE may collect a first user XR component associated with the first user XR stream via one or more of an advanced driver assistance system (ADAS) or an onboard sensor, such as in conjunction with Figure 7 The collection process 732 of FIG. 1704 may be described by collecting the first user XR component. Fig.18 The vehicle XR component 198 of the device 1804 is executed.

[0259] At 1706, the UE sends uplink information associated with the first user XR stream. Aspects of the uplink information are combined with at least Figure 7 The uplink information 734 of FIG. 1706 may be sent by Fig.18The cellular RF transceiver 1822 of the device 1804 and / or the vehicle XR component 198 may be implemented.

[0260] In some examples, the uplink information may include at least a first timestamp associated with the vehicle XR component and at least a second timestamp associated with the first user XR component, such as in combination with at least Fig. 9 The first timestamp 928 and the second timestamp 938 are described.

[0261] At 1708, the UE receives rendering information associated with the first user XR stream. Aspects of the rendering information are at least combined with Figure 7 The rendering information 746 is described. The rendering information received at 1708 may be Fig.18 The cellular RF transceiver 1822 of the device 1804 and / or the vehicle XR component 198 may be implemented.

[0262] In some examples, the rendered information may include an enhanced component associated with the vehicle surrounding information, such as at least in combination with Fig.13 The interactive object 1340 and / or score information 1342 are described.

[0263] At 1710, the UE may present rendering information via one or more displays associated with the vehicle XR session. Aspects of presenting the rendering information may include at least Figure 7 The rendering process 748 of FIG. 1710 is described. The rendering information can be presented by Fig.18 The vehicle XR component 198 of the device 1804 is executed.

[0264] At 1712, the UE may detect a user interaction with the interactive object associated with the rendering information. In some examples, the first user XR component may include user interaction information associated with the user interaction. In some examples, the interactive object may be associated with a vehicle XR component of the vehicle XR session. Aspects of the user interaction and user interaction information may be combined Fig.13 The user interaction information 1322 is described.

[0265] In some examples, the vehicle XR session may be further based on a second user XR stream including the vehicle XR component and a second user XR component associated with the second user. Aspects of the second user XR stream may be combined with at least Fig. 9 The second user XR stream 950 is described.

[0266] In some examples where the vehicle XR session is based on a first user XR stream and a second user XR stream, the rendering information at 1708 may include a first rendering component associated with the first user XR stream and a second rendering component associated with the second user XR stream, such as in combination with at least Fig. 9 The first user rendering information 940 and the second user rendering information 960 are described.

[0267] In some examples where the vehicle XR session is based on a first user XR stream and a second user XR stream, the vehicle XR component may be shared between the first user XR stream and the second user XR stream, such as in conjunction with Fig. 9 At least the vehicle XR component 920, the first user XR stream 930 and the second user XR stream 950 are described.

[0268] Fig.181800 is a diagram illustrating an example of a hardware implementation for an apparatus 1804. The apparatus 1804 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1804 may include a cellular baseband processor 1824 (also referred to as a modem) coupled to one or more transceivers (e.g., a cellular RF transceiver 1822). The cellular baseband processor 1824 may include on-chip memory 1824'. In some aspects, the apparatus 1804 may also include one or more subscriber identity module (SIM) cards 1820 and an application processor 1806 coupled to a secure digital (SD) card 1808 and a screen 1810. The application processor 1806 may include on-chip memory 1806'. In some aspects, the device 1804 may also include a Bluetooth module 1812, a WLAN module 1814, an SPS module 1816 (e.g., a GNSS module), one or more sensor modules 1818 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1826, a power source 1830, and / or a camera 1832. The Bluetooth module 1812, the WLAN module 1814, and the SPS module 1816 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1812, the WLAN module 1814, and the SPS module 1816 may include their own dedicated antennas and / or communicate using one or more antennas 1880. The cellular baseband processor 1824 communicates with one or more UEs in the UE 104 and / or with the RU associated with the network entity 1802 via one or more antennas 1880 through a transceiver (e.g., a cellular RF transceiver 1822). The cellular baseband processor 1824 and the application processor 1806 may each include a computer-readable medium / memory, such as an on-chip memory 1824' and an on-chip memory 1806', respectively. The additional memory module 1826 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory (e.g., on-chip memory 1824', on-chip memory 1806', and / or additional memory module 1826) may be non-transitory. The cellular baseband processor 1824 and the application processor 1806 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 1824 / application processor 1806, enables the cellular baseband processor 1824 / application processor 1806 to perform the various functions described above. The computer-readable medium / memory may also be used to store data that is manipulated by the cellular baseband processor 1824 / application processor 1806 when executing software.The cellular baseband processor 1824 / application processor 1806 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1804 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1824 and / or the application processor 1806, while in another configuration, the device 1804 may be the entire UE (e.g., see. Figure 3 UE 350) and includes additional modules of device 1804.

[0269] As discussed above, the vehicle XR component 198 is configured to send a request for a vehicle extended reality (XR) session based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle. The vehicle XR component 198 is also configured to send uplink information associated with the first user XR stream. The vehicle XR component 198 is also configured to receive rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

[0270] The vehicle XR component 198 may be within the cellular baseband processor 1824, the application processor 1806, or both the cellular baseband processor 1824 and the application processor 1806. The vehicle XR component 198 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof.

[0271] As shown, the device 1804 may include various components configured for various functions. For example, the vehicle XR component 198 may include a processor that executes Fig.16 and / or Fig.17 Each block of the algorithm in the flowchart is one or more hardware components.

[0272] In one configuration, the apparatus 1804 (and in particular the cellular baseband processor 1824 and / or the application processor 1806) includes means for sending a request for a vehicle extended reality (XR) session based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle. The example apparatus 1804 also includes means for sending uplink information associated with the first user XR stream. The example apparatus 1804 also includes means for receiving rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

[0273] In another configuration, the example apparatus 1804 also includes components for presenting the rendering information via one or more displays associated with the vehicle XR session.

[0274] In another configuration, the example apparatus 1804 further includes means for collecting a first user XR component associated with the first user XR stream via one or more of an advanced driver assistance system (ADAS) or an onboard sensor, wherein the uplink information includes the first user XR component.

[0275] In another configuration, the example apparatus 1804 further includes means for detecting a user interaction with an interactive object associated with the rendered information, and wherein the first user XR component includes user interaction information associated with the user interaction.

[0276] In another configuration, the example apparatus 1804 further includes means for receiving subsequent rendering information based on the user interaction information.

[0277] In another configuration, the example apparatus 1804 further includes means for receiving a message in response to the request, the message including a configuration associated with the vehicle XR session.

[0278] In another configuration, the example apparatus 1804 further includes means for collecting a second user XR component associated with the second user XR stream, wherein the uplink information includes the second user XR component.

[0279] In another configuration, the example apparatus 1804 further includes means for presenting the first rendered component via a first display of one or more displays associated with the vehicle XR session. The example apparatus 1804 further includes means for presenting the second rendered component via a second display of the one or more displays.

[0280] The means may be the vehicle XR component 198 of the device 1804 configured to perform the functions recited by the means. As described above, the device 1804 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0281] Fig.19 1900 is a flowchart of a method of wireless communication. The method may be performed by a network entity (e.g., one of the base stations 102 or a component of the base station, the cloud XR entity 708, Fig.21 network entity 2102, and / or Fig. 22 The method may facilitate improving a user experience associated with a vehicle XR session by using a cloud-based entity to reduce information sent OTA and / or reduce a computational load associated with a vehicle XR session at the UE.

[0282] At 1902, a network entity obtains a request for a vehicle XR session. Aspects of the request for a vehicle XR session may be combined with at least Figure 7 The request for a vehicle XR session at 1902 may be obtained by Fig.21 The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0283] At 1904, the network entity authorizes the vehicle XR session. Aspects of authorizing the vehicle XR session may be combined with at least Figure 7 The vehicle XR session may be based on a first user XR stream including a vehicle XR component associated with the vehicle and a first user XR component associated with the first user, the first user having an association with the vehicle, such as in conjunction with Figure 7 The vehicle XR component 736 and the user XR component 738 are described. At 1904, the authorization of the vehicle XR session can be performed by Fig.21 The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0284] At 1906, the network entity obtains uplink information associated with the first user XR stream. Aspects of the uplink information are at least combined with Figure 7 The uplink information 734 is described. The uplink information obtained at 1906 can be obtained by Fig.21The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0285] The uplink information may include a vehicle XR component and a first user XR component, such as a combination of Figure 7 The vehicle XR component 736 and the user XR component 738 are described. In some examples, the vehicle XR component may include at least one of vehicle posture information, vehicle information, and vehicle surrounding information, such as at least in combination with Fig. 9 In some examples, the first user XR component may include relative user posture information about the vehicle and user input, such as at least in combination with Fig. 9 The first user XR component 932 is described.

[0286] At 1908, the network entity outputs rendering information associated with the first user XR stream, the rendering information being based on the uplink information. Aspects of the rendering information are at least combined with Figure 7 The rendering information 746 is described. Outputting the rendering information at 1908 may be performed by Fig.21 The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0287] Fig. 20 2000 is a flowchart of a method of wireless communication. The method may be performed by a network entity (e.g., one of the base stations 102 or a component of the base station, the cloud XR entity 708, Fig.21 network entity 2102, and / or Fig. 22 The method may facilitate improving a user experience associated with a vehicle XR session by using a cloud-based entity to reduce information sent OTA and / or reduce a computational load associated with a vehicle XR session at the UE.

[0288] At 2002, a network entity obtains a request for a vehicle XR session. Aspects of the request for a vehicle XR session may be combined with at least Figure 7 The request for a vehicle XR session at 2002 may be obtained by Fig.21 The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0289] At 2003, the network entity authorizes the vehicle XR session. Aspects of authorizing the vehicle XR session may be combined with at least Figure 7 The vehicle XR session may be based on a first user XR stream including a vehicle XR component associated with the vehicle and a first user XR component associated with the first user, the first user having an association with the vehicle, such as in conjunction with Figure 7 The vehicle XR component 736 and the user XR component 738 are described. At 2003, the vehicle XR session can be authorized by Fig.21 The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0290] In some examples, the request for a vehicle XR session at 2002 may include subscription credentials, such as in conjunction with Figure 8 The subscription credentials information 816 described in the example. In some examples, the subscription credentials may be associated with a subscription level.

[0291] At 2004, the network entity obtains uplink information associated with the first user XR stream. Aspects of the uplink information are at least combined with Figure 7 The uplink information 734 is described. The uplink information obtained at 2004 can be obtained by Fig.21 The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0292] The uplink information may include a vehicle XR component and a first user XR component, such as a combination of Figure 7 The vehicle XR component 736 and the user XR component 738 are described. In some examples, the vehicle XR component may include at least one of vehicle posture information, vehicle information, and vehicle surrounding information, such as at least in combination with Fig. 9 In some examples, the first user XR component may include relative user posture information about the vehicle and user input, such as at least in combination with Fig. 9 The first user XR component 932 is described.

[0293] At 2014, the network entity outputs rendering information associated with the first user XR stream, the rendering information being based on the uplink information. Aspects of the rendering information are at least combined with Figure 7 Outputting the rendering information at 2014 may be performed by Fig.21The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0294] At 2006, the network entity may combine the uplink information based on the vehicle XR component and the first user XR component to generate rendering information. Aspects of combining the uplink information may include at least Figure 7 The combined uplink information at 2006 may be provided by Fig.21 The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0295] In some examples, the uplink information (eg, at 2004) may include at least a first timestamp associated with the vehicle XR component and at least a second timestamp associated with the first user XR component, such as in combination with at least Fig. 9 In some such examples, the network entity may, at 2008, correlate multiple attributes of the uplink information based at least on the first timestamp and the second timestamp, such as at least in conjunction with Figure 7 The combination process 740 is described. Correlating multiple attributes of the uplink information at 2008 can be performed by Fig.21 The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0296] In some examples, combining the uplink information to generate the rendering information (e.g., at 2006) can be based on the enhancement component. For example, at 2010, the network entity can identify the environmental component via the vehicle XR component of the first user XR stream. Aspects of identifying the environmental component at least in combination Fig.12 The stadium 1232 is described. The environmental component can be identified at 2010 by Fig.21 The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0297] At 2012, the network entity may associate the enhancement component with the vehicle surrounding information based on the environmental component to combine the uplink information. Fig.13 The interactive object 1340 and score information 1342 are described. Associating the enhancement component at 2012 can be performed by Fig.21The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0298] In some examples, the uplink information (e.g., at 2004) may include user interaction information associated with the user interaction. At 2030, the network entity may output subsequent rendering information based on the user interaction information. The aspects of outputting the subsequent rendering information are at least combined with Fig.13 The score information 1342 is described. The subsequent rendering information output at 2030 can be Fig.21 The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0299] In some examples, the user interaction information may be associated with the transaction. For example, at 2016, the network entity may identify the transaction interaction based on the user interaction information. The transaction interaction may be associated with a service provided by the second network entity. Aspects of the transaction interaction may be associated with at least Fig.15 The transaction interaction can be described by the identification 1512 of . Fig.21 The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0300] At 2024, the network entity may output transaction information to facilitate transactions associated with the service. Aspects of the transaction information may include at least Fig.15 The transaction information 1522 is described. The output transaction information at 2024 can be Fig.21 The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0301] In some examples, the network entity may communicate with a second network entity to facilitate a transaction associated with the service. For example, at 2018, the network entity may establish a connection with the second network entity based on the transaction interaction. The aspects of establishing the connection with the second network entity may at least include: Fig.15 The connection establishment process 1514 is described. Establishing a connection with the second network entity at 2018 may be performed by Fig.21 The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0302] At 2020, the network entity may obtain service information via a connection with the second network entity. Aspects of obtaining service information are at least combined with Fig.15 The service information 1518 is described. The service information can be obtained at 2020 by Fig.21 The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0303] At 2022, the network entity may generate transaction information based on the uplink information and the service information. Aspects of generating the transaction information may include at least Fig.15 The generation of transaction information at 2022 may be described by Fig.21 The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0304] The network entity may then output transaction information to facilitate the transaction associated with the service (eg, at 2024).

[0305] In some examples, the network entity may obtain a response based on the transaction information. For example, at 2026, the network entity may obtain a transaction message in response to the transaction information. The aspects of obtaining the transaction message may be at least combined with Fig.15 The transaction message 1524 is described. The transaction message can be obtained at 2026 by Fig.21 The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0306] At 2028, the network entity may generate subsequent rendering information based on the transaction message. Aspects of the subsequent rendering information are at least combined with Fig.15 The subsequent rendering information 1530 is described. The subsequent rendering information generated at 2028 can be Fig.21 The transportation of the network entity 2102 to the cloud XR network component 199 and / or Fig. 22 The transportation of the network entity 2260 to the cloud XR component 191 is executed.

[0307] In some examples, the vehicle XR session may be further based on a second user XR stream including the vehicle XR component and a second user XR component associated with the second user. Aspects of the second user XR stream may be combined with at least Fig. 9 The second user XR stream 950 is described.

[0308] In some examples where the vehicle XR session is based on a first user XR stream and a second user XR stream, the rendering information at 2014 may include a first rendering component associated with the first user XR stream and a second rendering component associated with the second user XR stream, such as in combination with at least Fig. 9 The first user rendering information 940 and the second user rendering information 960 are described.

[0309] In some examples where the vehicle XR session is based on a first user XR stream and a second user XR stream, the uplink information (e.g., at 2004) may include a second user XR component associated with the second user, and the second rendering component may be based on the vehicle XR component and the second user XR component, such as in combination with at least Fig. 9 The second user rendering information 960 is described.

[0310] In some examples where the vehicle XR session is based on a first user XR stream and a second user XR stream, the vehicle XR component may be shared between the first user XR stream and the second user XR stream, such as in conjunction with Fig. 9 At least the vehicle XR component 920, the first user XR stream 930 and the second user XR stream 950 are described.

[0311] Fig.2121 is a diagram illustrating an example of a hardware implementation for a network entity 2102. The network entity 2102 may be a BS, a component of a BS, or may implement BS functionality. The network entity 2102 may include at least one of a CU 2110, a DU 2130, or a RU 2140. For example, depending on the layer functionality handled by the vehicle-to-cloud XR network component 199, the network entity 2102 may include a CU 2110; both a CU 2110 and a DU 2130; each of the CU 2110, the DU 2130, and the RU 2140; the DU 2130; both a DU 2130 and a RU 2140; or a RU 2140. The CU 2110 may include a CU processor 2112. The CU processor 2112 may include an on-chip memory 2112'. In some aspects, an additional memory module 2114 and a communication interface 2118 may also be included. CU 2110 communicates with DU 2130 via a midhaul link, such as an F1 interface. DU 2130 may include a DU processor 2132. DU processor 2132 may include on-chip memory 2132'. In some aspects, DU 2130 may also include an additional memory module 2134 and a communication interface 2138. DU 2130 communicates with RU 2140 via a fronthaul link. RU 2140 may include a RU processor 2142. RU processor 2142 may include on-chip memory 2142'. In some aspects, RU 2140 may also include an additional memory module 2144, one or more transceivers 2146, an antenna 2180, and a communication interface 2148. RU 2140 communicates with one or more UEs in UE 104. On-chip memory (e.g., on-chip memory 2112', on-chip memory 2132', and / or on-chip memory 2142') and / or additional memory modules (e.g., additional memory module 2114, additional memory module 2134, and / or additional memory module 2144) may each be considered as a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of the CU processor 2112, the DU processor 2132, and the RU processor 2142 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor, enables the processor to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0312] As discussed above, the vehicle-to-cloud XR network component 199 is configured to obtain a request for a vehicle XR session. The vehicle-to-cloud XR network component 199 is also configured to authorize a vehicle XR session based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle. The vehicle-to-cloud XR network component 199 is also configured to obtain uplink information associated with the first user XR stream. The vehicle-to-cloud XR network component 199 is also configured to output rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

[0313] The vehicle-to-cloud XR network component 199 may be within one or more processors of one or more of the CU 2110, DU 2130, and RU 2140. The vehicle-to-cloud XR network component 199 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above.

[0314] The network entity 2102 may include various components configured for various functions. For example, the vehicle-to-cloud XR network component 199 may include executing Fig.19 and / or Fig. 20 Each block of the algorithm in the flowchart is one or more hardware components.

[0315] In one configuration, the network entity 2102 includes components for obtaining a request for a vehicle extended reality (XR) session. The example network entity 2102 also includes components for authorizing a vehicle XR session based on a first-user XR stream including a vehicle XR component associated with a vehicle and a first-user XR component associated with a first user, the first user having an association with the vehicle. The example network entity 2102 also includes components for obtaining uplink information associated with the first-user XR stream. The example network entity 2102 also includes components for outputting rendering information associated with the first-user XR stream, the rendering information being based on the uplink information.

[0316] In another configuration, the example network entity 2102 also includes means for combining the uplink information based on the vehicle XR component and the first user XR component to generate rendering information.

[0317] In another configuration, the example network entity 2102 further includes means for identifying an ambient component via a vehicle XR component of the first user XR stream. The example network entity 2102 further includes means for associating an enhancement component with the vehicle surrounding information based on the ambient component.

[0318] In another configuration, the example network entity 2102 further includes means for outputting subsequent rendering information based on the user interaction information.

[0319] In another configuration, the example network entity 2102 further includes means for identifying a transaction interaction based on the user interaction information, the transaction interaction associated with a service provided by the second network entity. The example network entity 2102 further includes means for outputting the transaction information to facilitate a transaction associated with the service.

[0320] In another configuration, the example network entity 2102 further includes means for establishing a connection with a second network entity based on the transaction interaction. The example network entity 2102 further includes means for obtaining service information via the connection with the second network entity. The example network entity 2102 further includes means for generating transaction information based on the uplink information and the service information.

[0321] In another configuration, the example network entity 2102 further includes means for obtaining a transaction message in response to the transaction information. The example network entity 2102 further includes means for generating subsequent rendering information based on the transaction message.

[0322] In another configuration, the example network entity 2102 further includes means for correlating a plurality of attributes of the uplink information based on at least the first timestamp and the second timestamp.

[0323] In another configuration, the example network entity 2102 further includes means for outputting a message in response to the request, the message including a configuration associated with the vehicle XR session.

[0324] In another configuration, the example network entity 2102 further includes a component for outputting a quality of experience (QoE) measurement configuration associated with the vehicle XR session. The example network entity 2102 further includes a component for obtaining QoE metric information based on the QoE measurement configuration. The example network entity 2102 further includes a component for adjusting a rendering setting associated with the vehicle XR session based on the QoE metric information. The example network entity 2102 further includes a component for outputting subsequent rendering information generated based on the rendering setting.

[0325] The means may be a vehicle-to-cloud XR network component 199 of the network entity 2102 configured to perform the functions recited by the means. As described above, the network entity 2102 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the means may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recited by the means.

[0326] Fig. 22 2200 is an example of a hardware implementation for a network entity 2260. In one example, the network entity 2260 may be within the core network 190. The network entity 2260 may include a network processor 2212. The network processor 2212 may include an on-chip memory 2212'. In some aspects, the network entity 2260 may also include an additional memory module 2214. The network entity 2260 communicates with the CU 2202 directly (e.g., backhaul link) or indirectly (e.g., through the RIC) via a network interface 2280. The on-chip memory 2212' and the additional memory module 2214 may each be considered as a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. The network processor 2212 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software causes the processor to perform the various functions described above when executed by the corresponding processor. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0327] As discussed above, the vehicle-to-cloud XR component 191 is configured to obtain a request for a vehicle XR session. The vehicle-to-cloud XR component 191 is also configured to authorize a vehicle XR session based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle. The vehicle-to-cloud XR component 191 is also configured to obtain uplink information associated with the first user XR stream. The vehicle-to-cloud XR component 191 is also configured to output rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

[0328] The vehicle-to-cloud XR component 191 may be within the network processor 2212. The vehicle-to-cloud XR component 191 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 2260 may include a variety of components configured for various functions.

[0329] In one configuration, the network entity 2260 includes components for obtaining a request for a vehicle extended reality (XR) session. The example network entity 2260 also includes components for authorizing a vehicle XR session based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle. The example network entity 2260 also includes components for obtaining uplink information associated with the first user XR stream. The example network entity 2260 also includes components for outputting rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

[0330] In another configuration, the example network entity 2260 also includes means for combining the uplink information based on the vehicle XR component and the first user XR component to generate rendering information.

[0331] In another configuration, the example network entity 2260 further includes means for identifying an ambient component via a vehicle XR component of the first user XR stream. The example network entity 2260 further includes means for associating an enhancement component with the vehicle surrounding information based on the ambient component.

[0332] In another configuration, the example network entity 2260 further includes means for outputting subsequent rendering information based on the user interaction information.

[0333] In another configuration, the example network entity 2260 further includes means for identifying a transaction interaction based on the user interaction information, the transaction interaction associated with a service provided by the second network entity. The example network entity 2260 further includes means for outputting the transaction information to facilitate a transaction associated with the service.

[0334] In another configuration, the example network entity 2260 further includes means for establishing a connection with a second network entity based on the transaction interaction. The example network entity 2260 further includes means for obtaining service information via the connection with the second network entity. The example network entity 2260 further includes means for generating transaction information based on the uplink information and the service information.

[0335] In another configuration, the example network entity 2260 further includes means for obtaining a transaction message in response to the transaction information. The example network entity 2260 further includes means for generating subsequent rendering information based on the transaction message.

[0336] In another configuration, the example network entity 2260 further includes means for correlating a plurality of attributes of the uplink information based on at least the first timestamp and the second timestamp.

[0337] In another configuration, the example network entity 2260 further includes means for outputting a message in response to the request, the message including a configuration associated with the vehicle XR session.

[0338] In another configuration, the example network entity 2260 also includes a component for outputting a quality of experience (QoE) measurement configuration associated with the vehicle XR session. The example network entity 2260 also includes a component for obtaining QoE metric information based on the QoE measurement configuration. The example network entity 2260 also includes a component for adjusting a rendering setting associated with the vehicle XR session based on the QoE metric information. The example network entity 2260 also includes a component for outputting subsequent rendering information generated based on the rendering setting.

[0339] The component may be a vehicle-to-cloud XR component 191 of the network entity 2260 configured to perform the functions recited by the component.

[0340] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is only an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not limited to the specific order or hierarchy provided.

[0341] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when ..." and "at ..." do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ...", do not mean an instant action in response to the occurrence of an action or during the occurrence of an action, but only mean that if the condition is met, the action will occur without a specific or instantaneous time constraint to make the action occur. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having an advantage over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data may be directly received / sent between the first device and the second device, or indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will be known later to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device" cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0342] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0343] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0344] Aspect 1 is a method for wireless communication at a UE, the method comprising: sending a request for a vehicle extended reality (XR) session, the vehicle XR session being based on a first user XR stream comprising a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user being associated with the vehicle; sending uplink information associated with the first user XR stream; and receiving rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

[0345] Aspect 2 is a method according to aspect 1, the method further comprising: presenting the rendering information via one or more displays associated with the vehicle XR session.

[0346] Aspect 3 is a method according to any one of aspects 1 and 2, the method further comprising: the vehicle XR component includes at least one of vehicle posture information, vehicle information, and vehicle surrounding information.

[0347] Aspect 4 is a method according to any one of aspects 1 to 3, the method further comprising: the first user XR component comprises relative user posture information about the vehicle and user input.

[0348] Aspect 5 is a method according to any one of aspects 1 to 4, the method further comprising: the request for the vehicle XR session includes subscription credentials, wherein the subscription credentials are associated with a subscription level.

[0349] Aspect 6 is a method according to any one of Aspects 1 to 5, the method further comprising: collecting the first user XR component associated with the first user XR stream via one or more of an advanced driver assistance system (ADAS) or an on-board sensor, wherein the uplink information includes the first user XR component.

[0350] Aspect 7 is a method according to any one of Aspects 1 to 6, the method further comprising: detecting a user interaction with an interactive object associated with the rendered information, and wherein the first user XR component comprises user interaction information associated with the user interaction.

[0351] Aspect 8 is a method according to any one of aspects 1 to 7, the method further comprising: associating the interactive object with the vehicle XR component of the vehicle XR session.

[0352] Aspect 9 is a method according to any one of aspects 1 to 8, the method further comprising: the uplink information comprises at least a first timestamp associated with the vehicle XR component and at least a second timestamp associated with the first user XR component.

[0353] Aspect 10 is a method according to any one of aspects 1 to 9, the method further comprising: the rendering information includes an enhancement component associated with vehicle surrounding information.

[0354] Aspect 11 is a method according to any one of aspects 1 to 10, the method further comprising: the vehicle XR session is further based on a second user XR stream including the vehicle XR component and a second user XR component associated with a second user.

[0355] Aspect 12 is a method according to any one of aspects 1 to 11, the method further comprising: the rendering information includes a first rendering component associated with the first user XR stream and a second rendering component associated with the second user XR stream.

[0356] Aspect 13 is a method according to any one of aspects 1 to 12, the method further comprising: sharing the vehicle XR component between the first user XR stream and the second user XR stream.

[0357] Aspect 14 is an apparatus for wireless communication at a UE, the apparatus comprising: at least one processor coupled to a memory and configured to implement any one of aspects 1 to 13.

[0358] In aspect 15, the apparatus according to aspect 14 further comprises at least one antenna coupled to the at least one processor.

[0359] In aspect 16, the apparatus according to aspect 14 or 15 further comprises a transceiver coupled to the at least one processor.

[0360] Aspect 17 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 13.

[0361] In aspect 18, the apparatus according to aspect 17 further comprises at least one antenna coupled to the means for performing the method according to any one of aspects 1 to 13.

[0362] In aspect 19, the apparatus according to aspect 17 or 18 further comprises a transceiver coupled to the means for performing the method according to any one of aspects 1 to 13.

[0363] Aspect 20 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 1 to 13.

[0364] Aspect 21 is a method for wireless communication at a network entity, the method comprising: obtaining a request for a vehicle extended reality (XR) session; authorizing the vehicle XR session, the vehicle XR session being based on a first user XR stream comprising a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user being associated with the vehicle; obtaining uplink information associated with the first user XR stream; and outputting rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

[0365] Aspect 22 is a method according to aspect 21, the method further comprising: the vehicle XR component includes at least one of vehicle posture information, vehicle information, and vehicle surrounding information.

[0366] Aspect 23 is a method according to any one of Aspects 21 and 22, the method further comprising: the first user XR component comprises relative user posture information about the vehicle and user input.

[0367] Aspect 24 is a method according to any one of aspects 21 to 23, the method further comprising: the request for the vehicle XR session includes subscription credentials, and wherein the subscription credentials are associated with a subscription level.

[0368] Aspect 25 is a method according to any one of aspects 21 to 24, the method further comprising: combining the uplink information based on the vehicle XR component and the first user XR component to generate the rendering information.

[0369] Aspect 26 is a method according to any one of aspects 21 to 25, the method further comprising: identifying an environmental component via the vehicle XR component of the first user XR stream; and associating an enhancement component with vehicle surrounding information based on the environmental component to combine the uplink information.

[0370] Aspect 27 is a method according to any one of Aspects 21 to 26, the method further comprising: the uplink information comprises user interaction information associated with user interaction, and further comprising: outputting subsequent rendering information based on the user interaction information.

[0371] Aspect 28 is a method according to any one of Aspects 21 to 27, the method further comprising: the network entity is a first network entity, and the method further comprises: identifying a transaction interaction based on the user interaction information, the transaction interaction being associated with a service provided by a second network entity; and outputting transaction information to facilitate transactions associated with the service.

[0372] Aspect 29 is a method according to any one of Aspects 21 to 28, the method further comprising: establishing a connection with the second network entity based on the transaction interaction; obtaining service information via the connection with the second network entity; and generating the transaction information based on the uplink information and the service information.

[0373] Aspect 30 is a method according to any one of aspects 21 to 29, the method further comprising: obtaining a transaction message in response to the transaction information; and generating the subsequent rendering information based on the transaction message.

[0374] Aspect 31 is a method according to any one of Aspects 21 to 30, the method further comprising: the uplink information comprises at least a first timestamp associated with the vehicle XR component and at least a second timestamp associated with the first user XR component, and the method further comprises: correlating multiple attributes of the uplink information based on at least the first timestamp and the second timestamp.

[0375] Aspect 32 is a method according to any one of aspects 21 to 31, the method further comprising: the vehicle XR session is further based on a second user XR stream including the vehicle XR component and a second user XR component associated with a second user.

[0376] Aspect 33 is a method according to any one of aspects 21 to 32, the method further comprising: the rendering information includes a first rendering component associated with the first user XR stream and a second rendering component associated with the second user XR stream.

[0377] Aspect 34 is a method according to any one of aspects 21 to 33, the method further comprising: the uplink information includes the second user XR component associated with the second user, and the second rendering component is based on the vehicle XR component and the second user XR component.

[0378] Aspect 35 is a method according to any one of aspects 21 to 34, the method further comprising: sharing the vehicle XR component between the first user XR stream and the second user XR stream.

[0379] Aspect 36 is an apparatus for wireless communication at a network entity, the apparatus comprising: at least one processor coupled to a memory and configured to implement any one of aspects 21 to 35.

[0380] In aspect 37, the apparatus according to aspect 36 further comprises at least one antenna coupled to the at least one processor.

[0381] In aspect 38, the apparatus according to aspect 36 or 37 further comprises a transceiver coupled to the at least one processor.

[0382] Aspect 39 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 21 to 35.

[0383] In aspect 40, the apparatus according to aspect 39 further comprises at least one antenna coupled to the means for performing the method according to any one of aspects 21 to 35.

[0384] In aspect 41, the apparatus according to aspect 39 or 40 further comprises a transceiver coupled to the means for performing the method according to any one of aspects 21 to 35.

[0385] Aspect 42 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 21 to 35.

[0386] Aspect 43 is a method for wireless communication at a UE, the method comprising: sending a request for a vehicle XR session associated with a vehicle, the vehicle XR session being based on a first user XR stream including a vehicle XR component associated with the vehicle and a first user XR component associated with a first user; sending uplink information associated with the first user XR stream; and receiving rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

[0387] Aspect 44 is a method according to aspect 43, the method further comprising: presenting the rendering information via one or more displays associated with the vehicle XR session.

[0388] Aspect 45 is a method according to any one of aspects 43 and 44, the method further comprising: the one or more displays comprising at least one of a glasses-based display or a glasses-free display.

[0389] Aspect 46 is a method according to any one of Aspects 43 to 45, the method further comprising: the vehicle XR component includes at least one of vehicle posture information, vehicle information and vehicle surrounding information.

[0390] Aspect 47 is a method according to any one of aspects 43 to 46, the method further comprising: the first user XR component comprises relative user posture information and user input about the vehicle.

[0391] Aspect 48 is a method according to any one of aspects 43 to 47, the method further comprising: the request for the vehicle XR session includes subscription credentials, wherein the subscription credentials are associated with a subscription level.

[0392] Aspect 49 is a method according to any one of aspects 43 to 48, the method further comprising: the rendering information is based on the subscription level associated with the subscription credential.

[0393] Aspect 50 is a method according to any one of aspects 43 to 49, the method further comprising: the request for the vehicle XR session comprises a subscription request to create subscription credentials associated with a subscription level.

[0394] Aspect 51 is a method according to any one of aspects 43 to 50, the method further comprising: the request for the transport XR session includes QoS support information for communications associated with the transport XR session.

[0395] Aspect 52 is a method according to any one of aspects 43 to 51, the method further comprising: the rendering information is based on the QoS support information.

[0396] Aspect 53 is a method according to any one of Aspects 43 to 52, the method further comprising: collecting the first user XR component associated with the first user XR stream via one or more of an advanced driver assistance system (ADAS) or an on-board sensor, wherein the uplink information includes the first user XR component.

[0397] Aspect 54 is a method according to any one of aspects 43 to 53, the method further comprising: collecting the first user XR component via one or more of an advanced driver assistance system (ADAS) or an on-board sensor.

[0398] Aspect 55 is a method according to any one of aspects 43 to 54, the method further comprising: detecting a user interaction with an interactive object associated with the rendered information, and wherein the first user XR component comprises user interaction information associated with the user interaction.

[0399] Aspect 56 is a method according to any one of aspects 43 to 55, the method further comprising: receiving subsequent rendering information based on the user interaction information.

[0400] Aspect 57 is a method according to any one of aspects 43 to 56, the method further comprising: associating the interactive object with the vehicle XR component of the vehicle XR session.

[0401] Aspect 58 is a method according to any one of aspects 43 to 47, the method further comprising: the uplink information comprising at least a first timestamp associated with the vehicle XR component and at least a second timestamp associated with the first user XR component.

[0402] Aspect 59 is a method according to any one of aspects 43 to 58, the method further comprising: sending the uplink information to a network entity based on a periodicity associated with the first user XR stream.

[0403] Aspect 60 is a method according to any one of aspects 43 to 59, the method further comprising: receiving a message in response to the request, the message comprising a configuration associated with the vehicle XR session.

[0404] Aspect 61 is a method according to any one of aspects 43 to 60, the method further comprising: the configuration includes one or more of the following: a network connection type, an update frequency associated with the first user XR stream, an XR session level, and a QoE measurement configuration.

[0405] Aspect 62 is a method according to any one of aspects 43 to 61, the method further comprising: the rendering information is based on one or more of the following: subscription level, QoS profile, user identifier and privacy control.

[0406] Aspect 63 is a method according to any one of aspects 43 to 62, the method further comprising: the rendering information comprises an enhancement component associated with vehicle surrounding information.

[0407] Aspect 64 is a method according to any one of aspects 43 to 63, the method further comprising: the enhancement component comprises one or more of: landmark identifiers and interactive objects planned along the path of the vehicle.

[0408] Aspect 65 is a method according to any one of aspects 43 to 64, the method further comprising: the vehicle XR session is further based on a second user XR stream including the vehicle XR component and a second user XR component associated with a second user.

[0409] Aspect 66 is a method according to any one of aspects 43 to 65, the method further comprising: collecting the second user XR component associated with the second user, wherein the uplink information includes the second user XR component.

[0410] Aspect 67 is a method according to any one of aspects 43 to 66, the method further comprising: the rendering information includes a first rendering component associated with the first user XR stream and a second rendering component associated with the second user XR stream.

[0411] Aspect 68 is a method according to any one of Aspects 43 to 67, the method further comprising: presenting the first rendering component via a first display among one or more displays associated with the vehicle XR session; and presenting the second rendering component via a second display among the one or more displays.

[0412] Aspect 69 is a method according to any one of aspects 43 to 68, the method further comprising: sharing the vehicle XR component between the first user XR stream and the second user XR stream.

[0413] Aspect 70 is an apparatus for wireless communication at a UE, the apparatus comprising: at least one processor coupled to a memory and configured to implement any one of aspects 43 to 69.

[0414] In aspect 71, the apparatus according to aspect 70 further comprises at least one antenna coupled to the at least one processor.

[0415] In aspect 72, the apparatus according to aspect 70 or 71 further comprises a transceiver coupled to the at least one processor.

[0416] Aspect 73 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 43 to 69.

[0417] In aspect 74, the apparatus according to aspect 73 further comprises at least one antenna coupled to the means for performing the method according to any one of aspects 43 to 69.

[0418] In aspect 75, the apparatus according to aspect 73 or 74 further comprises a transceiver coupled to the means for performing the method according to any one of aspects 43 to 69.

[0419] Aspect 76 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 43 to 69.

[0420] Aspect 77 is a method for wireless communication at a network entity, the method comprising: obtaining a request for a vehicle XR session associated with a vehicle, the vehicle XR session being based on a first user XR stream including a vehicle XR component associated with the vehicle and a first user XR component associated with a first user; obtaining uplink information associated with the first user XR stream; and outputting rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

[0421] Aspect 78 is a method according to aspect 77, the method further comprising: the vehicle XR component includes at least one of vehicle posture information, vehicle information, and vehicle surrounding information.

[0422] Aspect 79 is a method according to any one of aspects 77 and 78, the method further comprising: the first user XR component comprises relative user posture information and user input about the vehicle.

[0423] Aspect 80 is a method according to any one of aspects 77 to 79, the method further comprising: the request for the vehicle XR session includes subscription credentials, and wherein the subscription credentials are associated with a subscription level.

[0424] Aspect 81 is a method according to any one of aspects 77 to 80, the method further comprising: the rendering information is based on the subscription level associated with the subscription credential.

[0425] Aspect 82 is a method according to any one of aspects 77 to 81, the method further comprising: the request for the vehicle XR session includes a subscription request to create subscription credentials associated with a subscription level.

[0426] Aspect 83 is a method according to any one of aspects 77 to 82, the method further comprising: the request for the transport XR session includes QoS support information for communications associated with the transport XR session.

[0427] Aspect 84 is a method according to any one of aspects 77 to 83, the method further comprising: the rendering information is based on the QoS support information.

[0428] Aspect 85 is a method according to any one of aspects 77 to 84, the method further comprising: combining the uplink information based on the vehicle XR component and the first user XR component to generate the rendering information.

[0429] Aspect 86 is a method according to any one of aspects 77 to 85, the method also including: combining the uplink information includes: identifying an environmental component via the vehicle XR component of the first user XR stream; and associating an enhanced component with vehicle surrounding information based on the environmental component.

[0430] Aspect 87 is a method according to any one of aspects 77 to 86, the method further comprising: the enhancement component includes one or more of the following: landmark identifiers and interactive objects planned along the path of the vehicle.

[0431] Aspect 88 is a method according to any one of aspects 77 to 87, the method further comprising: the uplink information comprises user interaction information associated with user interaction, and further comprising: outputting subsequent rendering information based on the user interaction information.

[0432] Aspect 89 is a method according to any one of Aspects 77 to 88, the method further comprising: the network entity is a first network entity, and the method further comprises: identifying a transaction interaction based on the user interaction information, the transaction interaction being associated with a service provided by a second network entity; and outputting transaction information to facilitate transactions associated with the service.

[0433] Aspect 90 is a method according to any one of Aspects 77 to 89, the method further comprising: establishing a connection with the second network entity based on the transaction interaction; obtaining service information via the connection with the second network entity; and generating the transaction information based on the uplink information and the service information.

[0434] Aspect 91 is a method according to any one of aspects 77 to 90, the method further comprising: obtaining a transaction message in response to the transaction information; and generating the subsequent rendering information based on the transaction message.

[0435] Aspect 92 is a method according to any one of Aspects 77 to 91, the method also including: the uplink information includes at least a first timestamp associated with the vehicle XR component and at least a second timestamp associated with the first user XR component, and the method also includes: correlating multiple attributes of the uplink information based on at least the first timestamp and the second timestamp.

[0436] Aspect 93 is a method according to any one of aspects 77 to 92, the method also including: obtaining the uplink information based on a periodicity associated with the first user XR stream.

[0437] Aspect 94 is a method according to any one of aspects 77 to 93, the method further comprising: outputting a message in response to the request, the message including a configuration associated with the vehicle XR session.

[0438] Aspect 95 is a method according to any one of Aspects 77 to 94, the method further comprising: the configuration includes one or more of the following: a network connection type, an update frequency associated with the first user XR stream, an XR session level, and a QoE measurement configuration.

[0439] Aspect 96 is a method according to any one of aspects 77 to 95, the method further comprising: the rendering information is based on one or more of the following: subscription level, QoS profile, user identifier and privacy control.

[0440] Aspect 97 is a method according to any one of Aspects 77 to 96, the method further comprising: outputting a QoE measurement configuration associated with the transport XR session; obtaining QoE metric information based on the QoE measurement configuration; adjusting rendering settings associated with the transport XR session based on the QoE metric information; and outputting subsequent rendering information generated based on the rendering settings.

[0441] Aspect 98 is a method according to any one of aspects 77 to 97, the method further comprising: the vehicle XR session is further based on a second user XR stream including the vehicle XR component and a second user XR component associated with a second user.

[0442] Aspect 99 is a method according to any one of aspects 77 to 98, the method further comprising: the rendering information includes a first rendering component associated with the first user XR stream and a second rendering component associated with the second user XR stream.

[0443] Aspect 100 is a method according to any one of aspects 77 to 99, the method further comprising: the uplink information includes the second user XR component associated with the second user, and the second rendering component is based on the vehicle XR component and the second user XR component.

[0444] Aspect 101 is a method according to any one of Aspects 77 to 100, the method further comprising: presenting the first rendering component via a first display among one or more displays associated with the vehicle XR session; and presenting the second rendering component via a second display among the one or more displays.

[0445] Aspect 102 is a method according to any one of aspects 77 to 101, the method further comprising: sharing the vehicle XR component between the first user XR stream and the second user XR stream.

[0446] Aspect 103 is a method according to any one of aspects 77 to 102, the method further comprising: the first rendering component includes a first enhancement component associated with the first user XR stream and the second rendering component includes a second enhancement component associated with the second user XR stream.

[0447] Aspect 104 is an apparatus for wireless communications at a network entity, the apparatus comprising: at least one processor coupled to a memory and configured to implement any one of aspects 77 to 103.

[0448] In aspect 105, the apparatus according to aspect 104 further comprises at least one antenna coupled to the at least one processor.

[0449] In aspect 106, the apparatus according to aspect 104 or 105 further comprises a transceiver coupled to the at least one processor.

[0450] Aspect 107 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 77 to 103.

[0451] In aspect 108, the apparatus according to aspect 107 further comprises at least one antenna coupled to the means for performing the method according to any one of aspects 77 to 103.

[0452] In aspect 109, the apparatus according to aspect 107 or 108 further comprises a transceiver coupled to the means for performing the method according to any one of aspects 77 to 103.

[0453] Aspect 110 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 77 to 103 .

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory and configured to: sending a request for a vehicle extended reality (XR) session based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle; Sending uplink information associated with the first user XR stream; as well as Rendering information associated with the first user XR stream is received, the rendering information being based on the uplink information.

2. The device according to claim 1, further comprising: at least one antenna, the at least one antenna coupled to the at least one processor, wherein the at least one processor is further configured to: The rendering information is presented via one or more displays associated with the vehicle XR session. 3 . The apparatus of claim 1 , wherein the vehicle XR component comprises at least one of vehicle posture information, vehicle information, and vehicle surrounding information. The apparatus of claim 1 , wherein the first user XR component comprises relative user posture information and user input about the vehicle. 5 . The apparatus of claim 1 , wherein the request for the vehicle XR session includes subscription credentials, wherein the subscription credentials are associated with a subscription level.

6. The apparatus of claim 1, wherein the at least one processor is further configured to: The first user XR component associated with the first user XR stream is collected via one or more of an advanced driver assistance system (ADAS) or an onboard sensor, wherein the uplink information includes the first user XR component.

7. The apparatus of claim 1, wherein the at least one processor is further configured to: A user interaction with an interactive object associated with the rendered information is detected, and wherein the first user XR component includes user interaction information associated with the user interaction. 8 . The apparatus of claim 7 , wherein the interactive object is associated with the vehicle XR component of the vehicle XR session. 9 . The apparatus of claim 1 , wherein the uplink information comprises at least a first timestamp associated with the vehicle XR component and at least a second timestamp associated with the first user XR component.

10. The apparatus of claim 1, wherein the rendering information includes an enhancement component associated with vehicle surrounding information. 11 . The apparatus of claim 1 , wherein the vehicle XR session is further based on a second user XR stream comprising the vehicle XR component and a second user XR component associated with a second user. 12 . The apparatus of claim 11 , wherein the rendering information comprises a first rendering component associated with the first user XR stream and a second rendering component associated with the second user XR stream. 13 . The apparatus of claim 11 , wherein the vehicle XR component is shared between the first user XR stream and the second user XR stream.

14. A method of wireless communication at a user equipment (UE), the method comprising: sending a request for a vehicle extended reality (XR) session based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle; Sending uplink information associated with the first user XR stream; as well as Rendering information associated with the first user XR stream is received, the rendering information being based on the uplink information.

15. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and at least one processor coupled to the memory and configured to: Get a request for a vehicle extended reality (XR) session; authorizing the vehicle XR session, the vehicle XR session being based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle; Obtaining uplink information associated with the first user XR stream; as well as Outputting rendering information associated with the first user XR stream, the rendering information being based on the uplink information. 16 . The apparatus of claim 15 , wherein the vehicle XR component comprises at least one of vehicle posture information, vehicle information, and vehicle surrounding information. 17 . The apparatus of claim 15 , wherein the first user XR component comprises relative user posture information and user input about the vehicle.

18. The apparatus of claim 15, wherein the request for the vehicle XR session includes subscription credentials, and wherein the subscription credentials are associated with a subscription level.

19. The apparatus according to claim 15, further comprising: at least one antenna, the at least one antenna coupled to the at least one processor, wherein the at least one processor is further configured to: The uplink information is combined based on the vehicle XR component and the first user XR component to generate the rendering information.

20. The apparatus of claim 19, wherein to combine the uplink information, the at least one processor is further configured to: identifying an ambient component via the vehicle XR component of the first user XR stream; and An enhancement component is associated with the vehicle surrounding information based on the environmental component.

21. The apparatus of claim 19, wherein the uplink information comprises user interaction information associated with a user interaction, and the at least one processor is further configured to: Subsequent rendering information is output based on the user interaction information.

22. The apparatus of claim 21 , wherein the network entity is a first network entity, and the at least one processor is further configured to: identifying a transaction interaction based on the user interaction information, the transaction interaction being associated with a service provided by a second network entity; and Transaction information is output to facilitate a transaction associated with the service.

23. The apparatus of claim 22, wherein the at least one processor is further configured to: establishing a connection with the second network entity based on the transaction interaction; obtaining service information via the connection with the second network entity; and The transaction information is generated based on the uplink information and the service information.

24. The apparatus of claim 22, wherein the at least one processor is further configured to: obtaining a transaction message in response to the transaction information; and The subsequent rendering information is generated based on the transaction message.

25. The apparatus of claim 15, wherein the uplink information comprises at least a first timestamp associated with the vehicle XR component and at least a second timestamp associated with the first user XR component, and the at least one processor is further configured to: A plurality of attributes of the uplink information are correlated based on at least the first timestamp and the second timestamp. 26 . The apparatus of claim 15 , wherein the vehicle XR session is further based on a second user XR stream comprising the vehicle XR component and a second user XR component associated with a second user. 27 . The apparatus of claim 26 , wherein the rendering information comprises a first rendering component associated with the first user XR stream and a second rendering component associated with the second user XR stream.

28. The apparatus of claim 27, wherein the uplink information includes the second-user XR component associated with the second user, and the second rendering component is based on the vehicle XR component and the second user XR component.

29. The device of claim 26, wherein the vehicle XR component is shared between the first user XR stream and the second user XR stream.

30. A method for wireless communication at a network entity, the method comprising: Get a request for a vehicle extended reality (XR) session; authorizing the vehicle XR session, the vehicle XR session being based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user, the first user having an association with the vehicle; Obtaining uplink information associated with the first user XR stream; as well as Outputting rendering information associated with the first user XR stream, the rendering information being based on the uplink information.

Images