Patent Application
20240426966
The present disclosure relates generally to communication systems, and more particularly, to a wireless communication involving positioning.
Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. 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.
These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (cMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.
The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus receives, from a network entity, at least one of: (1) a first indication of a first mapping and a first list of indices for first location information, where the first location information is associated with a first set of network nodes and a first set of positioning reference signal (PRS) resources and where the first mapping associates each index in the first list of indices with at least one PRS resource in the first set of PRS resources, or (2) a second indication of a previous implementation of the first mapping. The apparatus selects or configures at least one artificial intelligence (AI) or machine learning (ML)(AI/ML) positioning model based on at least one of the first indication or the second indication.
In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus configures at least one of: (1) a first mapping and a first list of indices for first location information, where the first location information is associated with a first set of network nodes and a first set of PRS resources and where the first mapping associates each index in the first list of indices with at least one PRS resource in the first set of PRS resources, or (2) a previous implementation of the first mapping. The apparatus transmits, to a user equipment (UE), at least one of (1) a first indication of the first mapping and the first list of indices for the first location information, or (2) a second indication of the previous implementation of the first mapping.
To the accomplishment of the foregoing and related ends, the one or more aspects may include the features hereinafter fully described and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.
Aspects presented herein may improve and maintain the accuracy and performance of artificial intelligence (AI)/machine learning (ML)(AI/ML) positioning by enabling a user equipment (UE) to be aware of changes in mapping between positioning reference signal (PRS) resource(s) and transmission reception point (TRP) location(s)/beam angle(s) without specifying mobile network operators to disclose the locations and beam angle information of their TRPs, thereby enabling the mobile network operators to maintain the privacy of their TRPs. For example, in one aspect of the present disclosure, a network (NW) may indicate, to or for a UE, a mapping (which may also be referred to as a “virtual map” or a “virtual mapping) between PRS resources and TRP locations/beam information that does not disclose the actual/exact TRP locations/beam information, and/or does not specify disclosure of cells physical and global identifications/identifiers (IDs), etc. This may enable a UE to decide how to map PRS measurements to its AI/M model and/or update and switch the AI/ML model (as applicable).
In one example, a network may be configured to maintain a “unique” indexing for cells/sites/TRPs and their beams, and the network may indicate how PRS resources (e.g., positioning frequency layer (PFL) ID(s), Set ID(s), PRS ID(s)) map to the cells/sites/TRPs and their beams based on this indexing. Thus, the network may be configured to just provide, to a UE, the mapping between its established indexing of TRPs/beams and PRS resources (e.g., PFL ID(s), Set ID(s), PRS ID(s)). When a network decides to change/modify the mapping of PRS resources to TRP locations/beams, the network may send, to or for a UE, an updated map/mapping on how PRS PFLs/Set IDs/PRS IDs map to the cells/sites/TRPs and their beams. In some scenarios, the network may also just indicate a flag that informs the UE that the mapping of PRS resources to TRP locations/beams has been changed. Then, the network may wait for the UE to request a detailed indication of the updated map. In other words, the network may be configured to provide the updated map just upon the request of the UE.
The detailed description set forth below in connection with the drawings describes various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.
Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus 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 such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. When multiple processors are implemented, the multiple processors may perform the functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.
Accordingly, in one or more example aspects, implementations, and/or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media can include a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the 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.
While aspects, implementations, and/or use cases are described in this application by illustration to some examples, additional or different aspects, implementations and/or use cases may come about in many different arrangements and scenarios. Aspects, implementations, and/or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations, and/or use cases may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described examples may occur. Aspects, implementations, and/or use cases may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques herein. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders/summers, etc.). Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.
Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. 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) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), a transmission reception point (TRP), or a cell, etc.) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.
An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among 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 throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
Base station operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.
Each of the units, i.e., the CUS 110, the DUs 130, the RUs 140, as well as the Near-RT RICs 125, the Non-RT RICs 115, and the SMO Framework 105, may include one or more interfaces or be coupled to one or more interfaces configured to receive or to transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or to transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), configured to receive or to transmit signals, or both, over a wireless transmission medium to one or more of the other units.
In some aspects, the CU 110 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 110. The CU 110 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 implementations, the CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface when implemented in an O-RAN configuration. The CU 110 can be implemented to communicate with the DU 130, as necessary, to network control and signaling.
The DU 130 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 140. In some aspects, the DU 130 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, demodulation, or the like) depending, at least in part, on a functional split, such as those defined by 3GPP. In some aspects, the DU 130 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 130, or with the control functions hosted by the CU 110.
Lower-layer functionality can be implemented by one or more RUs 140. In some deployments, an RU 140, controlled by a DU 130, 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, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 140 can be implemented to handle over the air (OTA) communication with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration can enable the DU(s) 130 and the CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
The SMO Framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operations and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO Framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, CUs 110, DUs 130, RUs 140 and Near-RT RICs 125. In some implementations, the SMO Framework 105 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 111, via an O1 interface. Additionally, in some implementations, the SMO Framework 105 can communicate directly with one or more RUs 140 via an O1 interface. The SMO Framework 105 also may include a Non-RT RIC 115 configured to support functionality of the SMO Framework 105.
The Non-RT RIC 115 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI)/machine learning (ML)(AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 125. The Non-RT RIC 115 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 125. The Near-RT RIC 125 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 110, one or more DUs 130, or both, as well as an O-eNB, with the Near-RT RIC 125.
In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC 125, the Non-RT RIC 115 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 125 and may be received at the SMO Framework 105 or the Non-RT RIC 115 from non-network data sources or from network functions. In some examples, the Non-RT RIC 115 or the Near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 115 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 105 (such as reconfiguration via 01) or via creation of RAN management policies (such as A1 policies).
At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Accordingly, a base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component indicated with dotted lines to signify that each component may or may not be included in the base station 102). The base station 102 provides an access point to the core network 120 for a UE 104. The base station 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station). The small cells include femtocells, picocells, and microcells. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication links between the RUs 140 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to an RU 140 and/or downlink (DL) (also referred to as forward link) transmissions from an RU 140 to a UE 104. The communication links may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base station 102/UEs 104 may use spectrum up to Y MHZ (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHZ (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell).
Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communications systems, such as for example, Bluetooth™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG)), Wi-Fi™ (Wi-Fi is a trademark of the Wi-Fi Alliance) based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.
The wireless communications system may further include a Wi-Fi AP 150 in communication with UEs 104 (also referred to as Wi-Fi stations (STAs)) via communication link 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the UEs 104/AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In 5G NR, 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 referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHZ-300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHZ-24.25 GHZ). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHZ. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHZ-71 GHZ), FR4 (71 GHz-114.25 GHZ), and FR5 (114.25 GHZ-300 GHz). Each of these higher frequency bands falls within the EHF band.
With the above aspects in mind, unless specifically stated otherwise, the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHZ, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and/or FR5, or may be within the EHF band.
The base station 102 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate beamforming. The base station 102 may transmit a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also transmit a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102/UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 102/UE 104. The transmit and receive directions for the base station 102 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.
The base station 102 may include and/or be referred to as a gNB, Node B, 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 TRP, network node, network entity, network equipment, or some other suitable terminology. The base station 102 can be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and an RU, or as a disaggregated base station including one or more of a CU, a DU, and/or an RU. The set of base stations, which may include disaggregated base stations and/or aggregated base stations, may be referred to as next generation (NG) RAN (NG-RAN).
The core network 120 may include an Access and Mobility Management Function (AMF) 161, a Session Management Function (SMF) 162, a User Plane Function (UPF) 163, a Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is the control node that processes the signaling between the UEs 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The one or more location servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, the one or more location servers 168 may include one or more location/positioning servers, which may include one or more of the GMLC 165, the LMF 166, a position determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), or the like. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients/applications (e.g., emergency services) for accessing UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to compute the position of the UE 104. The NG-RAN may utilize one or more positioning methods in order to determine the position of the UE 104. Positioning the UE 104 may involve signal measurements, a position estimate, and an optional velocity computation based on the measurements. The signal measurements may be made by the UE 104 and/or the base station 102 serving the UE 104. The signals measured may be based on one or more of a satellite positioning system (SPS) 170 (e.g., one or more of a Global Navigation Satellite System (GNSS), global position system (GPS), non-terrestrial network (NTN), or other satellite position/location system), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR enhanced cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time (Multi-RTT), DL angle-of-departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle-of-arrival (UL-AoA) positioning), and/or other systems/signals/sensors.
Examples of UEs 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., 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 similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and/or individually access the network.
Referring again to
In certain aspects, the one or more location servers 168 may include a mapping indication component 197 that may be configured to configure at least one of: (1) a first mapping and a first list of indices for first location information, where the first location information is associated with a first set of network nodes and a first set of PRS resources and where the first mapping associates each index in the first list of indices with at least one PRS resource in the first set of PRS resources, or (2) a previous implementation of the first mapping; and transmit, to a UE, at least one of (1) a first indication of the first mapping and the first list of indices for the first location information, or (2) a second indication of the previous implementation of the first mapping.
For normal CP (14 symbols/slot), different numerologies μ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology μ, there are 14 symbols/slot and 2 slots/subframe. The subcarrier spacing may be equal to 2μ*15 kHz, where u is the numerology 0 to 4. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing.
A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.
As illustrated in
As illustrated in
The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.
At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the receive (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 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. 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 symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.
The controller/processor 359 can be associated with at least one memory 360 that stores program codes and data. The at least one memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
Similar to the functionality described in connection with the DL transmission by the base station 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB. SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC 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 TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.
The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to a RX processor 370.
The controller/processor 375 can be associated with at least one memory 376 that stores program codes and data. The at least one memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with the mapping application component 198 of
At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 may be configured to perform aspects in connection with the RS transmission component 199 of
PRSs may be defined for network-based positioning (e.g., NR positioning) to enable UEs to detect and measure more neighbor transmission and reception points (TRPs), where multiple configurations are supported to enable a variety of deployments (e.g., indoor, outdoor, sub-6, mmW, etc.). To support PRS beam operation, beam sweeping may also be configured for PRS. The UL positioning reference signal may be based on sounding reference signals (SRSs) with enhancements/adjustments for positioning purposes. In some examples, UL-PRS may be referred to as “SRS for positioning,” and a new Information Element (IE) may be configured for SRS for positioning in RRC signaling.
DL PRS-RSRP may be defined as the linear average over the power contributions (in [W]) of the resource elements of the antenna port(s) that carry DL PRS reference signals configured for RSRP measurements within the considered measurement frequency bandwidth. In some examples, for FR1, the reference point for the DL PRS-RSRP may be the antenna connector of the UE. For FR2, DL PRS-RSRP may be measured based on the combined signal from antenna elements corresponding to a given receiver branch. For FR1 and FR2, if receiver diversity is in use by the UE, the reported DL PRS-RSRP value may not be lower than the corresponding DL PRS-RSRP of any of the individual receiver branches. Similarly, UL SRS-RSRP may be defined as linear average of the power contributions (in [W]) of the resource elements carrying sounding reference signals (SRS). UL SRS-RSRP may be measured over the configured resource elements within the considered measurement frequency bandwidth in the configured measurement time occasions. In some examples, for FR1, the reference point for the UL SRS-RSRP may be the antenna connector of the base station (e.g., gNB). For FR2, UL SRS-RSRP may be measured based on the combined signal from antenna elements corresponding to a given receiver branch. For FR1 and FR2, if receiver diversity is in use by the base station, the reported UL SRS-RSRP value may not be lower than the corresponding UL SRS-RSRP of any of the individual receiver branches.
PRS-path RSRP (PRS-RSRPP) may be defined as the power of the linear average of the channel response at the i-th path delay of the resource elements that carry DL PRS signal configured for the measurement, where DL PRS-RSRPP for the 1st path delay is the power contribution corresponding to the first detected path in time. In some examples, PRS path Phase measurement may refer to the phase associated with an i-th path of the channel derived using a PRS resource.
DL-AoD positioning may make use of the measured DL PRS-RSRP of downlink signals received from multiple TRPs 402, 406 at the UE 404. The UE 404 measures the DL PRS-RSRP of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with the azimuth angle of departure (A-AoD), the zenith angle of departure (Z-AoD), and other configuration information to locate the UE 404 in relation to the neighboring TRPs 402, 406.
DL-TDOA positioning may make use of the DL reference signal time difference (RSTD) (and/or DL PRS-RSRP) of downlink signals received from multiple TRPs 402, 406 at the UE 404. The UE 404 measures the DL RSTD (and/or DL PRS-RSRP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to locate the UE 404 in relation to the neighboring TRPs 402, 406.
UL-TDOA positioning may make use of the UL relative time of arrival (RTOA) (and/or UL SRS-RSRP) at multiple TRPs 402, 406 of uplink signals transmitted from UE 404. The TRPs 402, 406 measure the UL-RTOA (and/or UL SRS-RSRP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE 404.
UL-AoA positioning may make use of the measured azimuth angle of arrival (A-AoA) and zenith angle of arrival (Z-AoA) at multiple TRPs 402, 406 of uplink signals transmitted from the UE 404. The TRPs 402, 406 measure the A-AoA and the Z-AoA of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE 404. For purposes of the present disclosure, a positioning operation in which measurements are provided by a UE to a base station/positioning entity/server to be used in the computation of the UE's position may be described as “UE-assisted,” “UE-assisted positioning,” and/or “UE-assisted position calculation,” while a positioning operation in which a UE measures and computes its own position may be described as “UE-based,” “UE-based positioning,” and/or “UE-based position calculation.”
Additional positioning methods may be used for estimating the location of the UE 404, such as for example, UE-side UL-AoD and/or DL-AoA. Note that data/measurements from various technologies may be combined in various ways to increase accuracy, to determine and/or to enhance certainty, to supplement/complement measurements, and/or to substitute/provide for missing information.
Note that the terms “positioning reference signal” and “PRS” generally refer to specific reference signals that are used for positioning in NR and LTE systems. However, as used herein, the terms “positioning reference signal” and “PRS” may also refer to any type of reference signal that can be used for positioning, such as but not limited to, PRS as defined in LTE and NR, TRS, PTRS, CRS, CSI-RS, DMRS, PSS. SSS. SSB, SRS, UL-PRS, etc. In addition, the terms “positioning reference signal” and “PRS” may refer to downlink or uplink positioning reference signals, unless otherwise indicated by the context. To further distinguish the type of PRS, a downlink positioning reference signal may be referred to as a “DL PRS,” and an uplink positioning reference signal (e.g., an SRS-for-positioning, PTRS) may be referred to as an “UL-PRS.” In addition, for signals that may be transmitted in both the uplink and downlink (e.g., DMRS, PTRS), the signals may be prepended with “UL” or “DL” to distinguish the direction. For example, “UL-DMRS” may be differentiated from “DL-DMRS.” In addition, the term “location” and “position” may be used interchangeably throughout the specification, which may refer to a particular geographical or a relative place.
In some implementations, at least one artificial intelligence (AI)/machine learning (ML)(AI/ML) model may be configured/implemented at a UE or at a network entity/node (e.g., a base station, a location server, a location management function (LMF), etc.) for assisting the UE and/or the network entity/node with the positioning of the UE. For example, an AI/ML model may be trained to determine the position of a UE based on DL-AoA, DL-TDOA, channel impulse response (CIR), radio frequency (RF) fingerprinting, etc. In most scenarios, using an AI/ML model may significantly improve UE positioning latency, accuracy/reliability, and/or efficiency. For purposes of the present disclosure, an AI/ML model that is implemented at a UE side may be referred to as a “UE-side model” and/or “UE-side AI/ML model.” On the other hand, an AI/ML model that is implemented at a network side may be referred to as a “network-side model,” “network-side AI/ML model,” and/or (network name)-side AI/ML model (e.g., base station-side AI/ML model, LMF-side AI/ML model, etc.).
In addition, positioning that is associated with a UE or a network entity/node using an AI/ML model to determine the position of the UE may be referred to as “direct AI/ML positioning,” whereas positioning that is associated with a UE or a network entity/node performing positioning related measurements using an AI/ML model (and transmitting the positioning related measurements to another entity) to determine the position of the UE may be referred to as “AI/ML assisted positioning” and/or “assisted AI/ML positioning.” Also, UE-based positioning (e.g., UE determines its own position) using at least one UE-side AI/ML model may be referred to as “direct UE AI/ML positioning” and/or “UE direct AI/ML positioning,” whereas UE-assisted positioning (e.g., a UE provides positioning measurements and a network entity, such as an LMF, determines the position for the UE based on the positioning measurements provided by the UE) using at least one UE-side AI/ML model may be referred to as “UE AI/ML assisted positioning,” “UE assisted AI/ML positioning” “AI/ML assisted UE positioning,” and/or “AI/ML UE assisted positioning,” etc. Similarly, network-based positioning (e.g., a network entity, such as an LMF, determines the position for the UE) using at least one network/LMF-side AI/ML model may be referred to as “direct network/LMF AI/ML positioning” and/or “network/LMF direct AI/ML positioning.”
In addition to network based positioning methods, such as described in connection with
In some examples, the RF fingerprint database may be created and/or maintained based on AI/ML, and RFFP positioning with AI/ML may be referred to as AI/ML RFFP positioning. For AI/ML RFFP positioning, RF fingerprints and their associated positions may be used as features and labels, respectively, to train an AI/ML module in a supervised manner. After the AI/ML module is being trained, the AI/ML module may be used to estimate positions by passing it with newly captured RF fingerprints. In other words, an AI/ML module may be configured to collect RF fingerprints and their associated locations, and this process may be referred to as AI/ML position training or simply AI/ML training. After the AI/ML module is trained (e.g., RF fingerprints stored in the database are associated with known locations with certain level of certainties/accuracies), the AI/ML module may be used for estimating the location of a detected/captured RF fingerprint, and this process may be referred to as AI/ML position inference or simply AI/ML inference. In some examples, AI/ML position training/inference may be applied on UE side and/or on the network side. The RFFP AI/ML training and inference may also be based on millimeter wave (mmW or mm Wave), sub-THz, and/or THz frequencies.
At an online stage 904 (which may also be referred to as an operational stage or a training stage), the NN or the AI/ML module may receive RF fingerprint captured by a wireless device that has an unknown location. The NN may compare the RF fingerprint with unknown location to the mapping, select one or more RF fingerprints from the mapping that are similar to the RF fingerprint with unknown location, and computer an estimated position for the wireless device. Throughout the process, the NN or the AI/ML module may continue to update the mapping to increase the accuracy of the position estimation.
A positioning frequency layer (PFL) (or a “frequency layer” in some examples) may refer to a collection of one or more PRS resource sets across one or more TRPs that have the same values for certain parameters. A PFL may include one or more TRPs, and each TRP in the one or more TRPs may include one or more resource sets, and each resource set in the one or more resource sets may include one or more PRs resources, etc. In some examples, the collection of PRS resource sets may have the same subcarrier spacing and cyclic prefix (CP) type (e.g., meaning all numerologies supported for PDSCHs are also supported for PRS), the same value of the downlink PRS bandwidth, the same start physical resource block (PRB) (and center frequency), and/or the same comb-size, etc. In some examples, a downlink PRS bandwidth may have a granularity of four PRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs. In other examples, up to four frequency layers may be configured, and up to two PRS resource sets may be configured per TRP per frequency layer.
In some implementations, the concept of a PFL may be similar to a component carrier (CC) and a BWP, where CCs and BWPs may be used by one base station (or a macro cell base station and a small cell base station) to transmit data channels, while PFLs may be used by multiple (e.g., three or more) base stations to transmit PRS. A UE may indicate the number of PLFs it is capable of supporting when the UE sends the network its positioning capabilities, such as during a positioning protocol session. For example, a UE may indicate whether it is capable of supporting one, two, three, or four PFLs.
In some scenarios, a UE may receive a plurality of PRS resources from multiple TRPs via one or more PFLs, where the UE may not have capabilities to process all of the plurality of PRS resources. As such, the UE may apply a predefined prioritization rule to prioritize measurements of PRS resources. Based on the predefined prioritization rule, the UE may measure a subset of the plurality of PRS resources, and the UE may skip measuring another subset of the plurality of PRS resources.
For example, as shown by the diagram 1000, the UE may be configured to receive DL PRSs from a first frequency layer 1002 (PFL 1) and a second frequency layer 1004 (PFL 2). The first frequency layer 1002 may include DL PRSs transmitted from a first TRP 1006 and a second TRP 1008, where the first TRP 1006 may transmit PRSs using a first PRS resource 1016 and a second PRS resource 1018 in a first PRS resource set 1010, and using a first PRS resource 1020 and a second PRS resource 1022 in a second PRS resource set 1012, and the second TRP 1008 may transmit PRSs using a first PRS resource 1024 and a second PRS resource 1026 in a first PRS resource set 1014. Similarly, the UE may also receive DL PRSs from the second frequency layer 1004 via multiple TRPs, PRS resource sets, and/or PRS resources.
In one example, if the UE does not have the capability to process all the configured PRS resources, the UE may be configured to receive or measure the PRSs received from the first frequency layer 1002 first before processing PRSs in the second frequency layer 1004. Similarly, if there are also a third frequency layer (PFL 3) and a fourth frequency layer (PFL 4), the UE may be configured to receive or measure the PRSs received from the first frequency layer 1002 first, then the PRSs received from the second frequency layer 1004, then the PRSs received from the third frequency layer, and then the PRSs received from the fourth frequency layer (e.g., PRSs are processed/measured based on PFL 1>PFL 2>PFL 3>PFL 4). If the UE does not have the capability to process/measure PRSs in a frequency layer, the UE may skip measuring the PRSs in that frequency layer. For example, if the UE is configured to receive the PRSs via the first frequency layer 1002 and the second frequency layer 1004 but the UE is just able to process/measure PRSs in the first frequency layer 1002, the UE may skip PRS measurements for the second frequency layer 1004.
Similarly, within a frequency layer, if the UE does not have the capability to process all the PRSs in the frequency layer, the UE may prioritize its PRS measurements based on the priorities associated with the TRPs. For example, the UE may be configured to receive or measure the PRSs received from the first TRP 1006 before processing PRSs from the second TRP 1008. Similarly, if there are also a third TRP (TRP 3) and a fourth TRP (TRP 4), the UE may be configured to receive or measure the PRSs received from the first TRP 1006, then receive or measure the PRSs from the second TRP 1008, then receive or measure the PRSs from the third TRP, and then receive or measure the PRSs from the fourth TRP (e.g., PRSs are processed/measured based on TRP 1>TRP 2>TRP 3>TRP 4 with a frequency layer). If the UE does not have the capability to process/measure PRSs from a TRP, the UE may skip measuring the PRSs in that TRP. For example, if the UE is configured to receive the PRSs via the first TRP 1006 and the second TRP 1008 via the first frequency layer 1002 but the UE is just able to process/measure PRSs in the first TRP 1006, the UE may skip PRS measurements for the second TRP 1008.
Furthermore, within a TRP, if the UE does not have the capability to process all the PRSs in that TRP, the UE may prioritize its PRS measurements based on the priorities associated with the PRS resource sets. For example, the UE may be configured to receive or measure the PRSs received from the first PRS resource set 1010 first before processing PRSs from the second PRS resource set 1012. Similarly, if there are also a third PRS resource set (PRS resource set 3) and a fourth PRS resource set (PRS resource set 4), the UE may be configured to receive or measure the PRSs received from the first PRS resource set 1010 first, then the PRSs received from the second PRS resource set 1012, then the PRSs received from the third PRS resource set, and then the PRSs received from the fourth PRS resource set (e.g., PRSs are processed/measured based on PRS resource set 1>PRS resource set 2>PRS resource set 3>PRS resource set 4 with a TRP). If the UE does not have the capability to process/measure PRSs in a PRS resource set, the UE may skip measuring the PRSs in that PRS resource set. For example, if the UE is configured to receive the PRSs via the first PRS resource set 1010 and the second PRS resource set 1012 from the first TRP 1006 but the UE is just able to process/measure PRSs in the first PRS resource set 1010, the UE may skip PRS measurements for the second PRS resource set 1012.
Lastly, within a PRS resource set, if the UE does not have the capability to process all the PRSs in that PRS resource set, the UE may prioritize its PRS measurements based on the priorities associated with the PRS resources. For example, the UE may be configured to receive or measure the PRSs received from the first PRS resource 1016 first before processing PRSs from the second PRS resource 1018. Similarly, if there are also a third PRS resource (PRS resource 3) and a fourth PRS resource (PRS resource 4), the UE may be configured to receive or measure the PRSs received from the first PRS resource 1016 first, then the PRSs received from the second PRS resource 1018, then the PRSs received from the third PRS resource, and then the PRSs received from the fourth PRS resource (e.g., PRSs are processed/measured based on PRS resource 1>PRS resource 2>PRS resource 3>PRS resource 4 with a PRS resource set). If the UE does not have the capability to process/measure PRSs in a PRS resource, the UE may skip measuring the PRSs in that PRS resource. For example, if the UE is configured to receive the PRSs via the first PRS resource 1016 and the second PRS resource 1018 of the first PRS resource set 1010 but the UE is just able to process/measure PRSs in the first PRS resource 1016, the UE may skip PRS measurements for the second PRS resource 1018.
As such, if a UE is configured with multiple PRS resources via multiple frequency layers, multiple TRPs, multiple PRS resource sets, and/or multiple PRS resources, the UE may sort the frequency layers (e.g., may be up to four frequency layers) according to a priority, sort the TRPs per frequency layer (e.g., may be up to sixty four (64) TRPs per frequency layer) also according to a priority, sort the PRS resource sets per TRP (e.g., may be up to two resource sets per TRP) according to a priority, and/or sort the PRS resource per PRS resource set (e.g., may be up to sixty four (64) PRS resources per PRS resource set). In other words, within a positioning frequency layer, the DL PRS resources may be sorted in the decreasing order of priority for measurement to be performed by the UE, with the reference indicated by nr-DL-PRS-ReferenceInfo being the highest priority for measurement, and the following priority is assumed: (1) up to 64 dl-PRS-IDs of the frequency layer are sorted according to priority; and (2) up to 2 DL PRS resource sets per dl-PRS-ID of the frequency layer are sorted according to priority.
In some implementations, a UE may expect that it will be configured with dl-PRS-ID each of which is defined such that it is associated with multiple DL PRS resource sets. The UE may expect that one of these dl-PRS-ID along with a nr-DL-PRS-ResourceSetID and a nr-DL-PRS-ResourceID-r16 can be used to uniquely identify a DL PRS resource. For purposes of the present disclosure, a dl-PRS-ID may refer to an ID that corresponds to a PFL, an nr-DL-PRS-ResourceSetID may refer to an ID that corresponds to a PRS resource set in a PFL, and an nr-DL-PRS-ResourceID-r16 may refer to an ID that corresponds to a PRS resource in a PRS resource set. In some examples, a UE may be configured by a network with nr-PhysCellID, nr-CellGlobalID, and nr-ARFCN associated with a dl-PRS-ID. Table 2 below shows a list of example parameters that may be associated with a PRS resource set or a PRS resource.
In some examples, a UE may be provided by a network with an indication of locations of one or more TRPs and/or angles (e.g., DL-AoD). For example, a UE may be provided with beam/antenna information via higher layer parameter NR-TRP-BeamAntennaInfo, and the UE may request to be provided with either expected DL-AoD/ZoD and uncertainty range(s) of expected DL-AoD/ZoD, or expected DL-AoA/ZoA and uncertainty range(s) of the expected DL-AoA/ZoA. The UE may be provided with expected DL-AoD/ZoD and uncertainty range(s) of the expected DL-AoD/ZoD. The UE may be provided with expected DL-AoA/ZoA and uncertainty range(s) of the expected DL-AoA/ZoA. However, while a UE may request a network to provide TRP location and/or PRS beam/antenna angle information, the network response may not be configured to be mandatory (e.g., may be optional). Similarly, the network may also be configured to provide Cell IDs and global Cell IDs to the UE optionally.
In some scenarios, the mapping between PRS resources (e.g., PFL ID(s), PRS resource set(s), and/or PRS resource(s)/signals, etc.) and actual deployment (e.g., cells/sites, TRPs, and/or beams, etc.) may be left for implementation and usually decided by a mobile network operator (MNO) or based on predefined network vendor setting(s). As such, over the lifecycle of a network operation for a given network deployment, an MNO may decide to change how different PRS resources map to TRPs/beams to enhance/modify performance.
As shown at 1204, at another point in time (e.g., after a period of time), the mobile network operator may modify the mapping between the PRS resource sets/resources and TRPs, where now the first TRP (TRP 1) may be configured to transmit the fourth PRS resource set (PRS resource set 4), and transmit five PRS resources (PRSs 1 to 5) via five beams. Similarly, the fourth TRP (TRP 4) may now be configured to transmit the first PRS resource set (PRS resource set 1) instead, and transmit the first PRS resource (PRS 1) using a first beam and transmit the second PRS resource (PRS 2), etc.
In some scenarios, the mobile network operator may also modify the mapping between TRP beams and PRS resources. For example, as shown at 1202, a second TRP (TRP 2) that is configured to transmit the second PRS resource set (PRS resource set 2) may initially transmit a first PRS resource (PRS 1) using a first beam and a second PRS resource (PRS 2) using a second beam. However, as shown at 1204, after a period of time, the second TRP (TRP 2) may still be configured to transmit the second PRS resource set (PRS resource set 2), but the second TRP may now be configured to transmit the first PRS resource (PRS 1) using the second beam, and transmit the second PRS resource (PRS 2) using the first beam instead. In some scenarios, the aforementioned changes in mapping (e.g., by the mobile network operator) may be transparent to a UE (e.g., meaning the UE may not be aware of the changes). Thus, a UE may still receive the same PRS configurations but may not know whether mapping or PRS resources to physical anchors and/or beam angle has changed.
While changes in PRS and TRP mapping described in connection with
Thus, it may be quite important to let a UE aware/know when changes in mapping between PRS resource(s) and TRP location(s)/beam angle(s) occur. This may enable/helps the UE to better align input of the AI/ML model and/or to pick the suitable/right AI/ML model parameter(s) and configuration(s). However, due to proprietary, privacy, and/or implementation reasons, MNOs usually do not disclose TRP locations and/or beam angle information to UEs. In addition, such disclosure is also not mandatory (e.g., not being specified in a specification).
Aspects presented herein may improve and maintain the accuracy and performance of AI/ML positioning by enabling a UE to be aware of changes in mapping between PRS resource(s) and TRP location(s)/beam angle(s) without specifying mobile network operators to disclose the locations and beam angle information of their TRPs, thereby enabling the mobile network operators to maintain the privacy of their TRPs. For example, in one aspect of the present disclosure, a network (NW) may indicate, to or for a UE, a mapping (which may also be referred to as a “virtual map” or “virtual mapping) between PRS resources and TRP locations/beam information that does not disclose the actual/exact TRP locations/beam information, and/or does not specify disclosure of cells physical and global IDs, etc. This may enable a UE to decide how to map PRS measurements to its AI/M model and/or update and switch the AI/ML model (as applicable). For purposes of the present disclosure, when a first entity transmits a transmission (e.g., a mapping, an indication, a configuration, a request, a data, etc.) “for” a second entity, it may indicate that the first entity is transmitting the transmission directly to the second entity, and/or that that the first entity is transmitting the transmission to the second entity via at least one other entity or component (e.g., via a third entity, via a transmission component that may not be in proximity to the first entity). For example, when a network entity (e.g., an LMF) transmits a mapping for a UE, it may refer that the network entity is transmitting the mapping directly to the UE, or indirectly to the UE via another network node such as a base station or via a transmitter that is not co-located with the network entity.
In one example, a network may be configured to maintain a “unique” indexing for cells/sites/TRPs and their beams, and the network may indicate how PRS resources (e.g., PFL ID(s), Set ID(s), PRS ID(s)) map to the cells/sites/TRPs and their beams based on this indexing. Thus, the network may be configured to just provide, to a UE, the mapping between its established indexing of TRPs/beams and PRS resources (e.g., PFL ID(s), Set ID(s), PRS ID(s)). In some implementations, the network may consider an outer loop to update the UE for any change in the indexing (e.g., maintenance of indexing if specified. However, this may not be expected to occur too frequently, and the frequency is likely longer than the lifecycle of an AI/ML positioning model.
When a network decides to change/modify the mapping of PRS resources to TRP locations/beams, the network may send, to a UE, an updated map/mapping on how PRS PFLs/Set IDs/PRS IDs map to the cells/sites/TRPs and their beams. In some scenarios, the network may also just indicate a flag that informs the UE that the mapping of PRS resources to TRP locations/beams has been changed. Then, the network may wait for the UE to request a detailed indication of the updated map. In other words, the network may be configured to provide the updated map just upon the request of the UE.
Aspects presented herein may provide better configuration(s) for UE-sided AI/ML positioning models, such as described in connection with
At 1630, a network entity 1604 (e.g., a location, an LMF, etc.) may configure and transmit, to or for a UE 1602 (which may also be referred to as a “target” in some examples), a list of indices 1610 that corresponds to location(s) and/or beam(s) of a set of network nodes 1606 (e.g., a set of TRPs/cells/cites), such as described in connection with
At 1632, the network entity 1604 may configure and transmit, to or for a UE 1602, a list of PRS resources 1612 (e.g., a list of PRS resources configured for the UE 1602), such as their corresponding PFL ID(s), PRS resource set ID(s), and/or PRS resources ID(s), etc. For example, the PRS configuration may be specified to map a PRS resource to a PRS resource set and PFL. Therefore, a configured PRS resource may already be under a determined PRS resource set and PFL. Thus, for a list of PRS resources, this list may also cover PRS resource set(s) and PFL(s).
At 1634, the network entity 1604 may configure and transmit, to or for a UE 1602, a mapping 1614 that indicates how the list of indices 1610 maps to the list of PRS resources 1612, such as described in connection with
As shown at 1636, the network entity 1604 may be configured to transmit the list of indices 1610, the list of PRS resources 1612, and the mapping 1614 in one message, or the network entity 1604 may be configured to transmit one or more of the list of indices 1610, the list of PRS resources 1612, and the mapping 1614 in one message in multiple/different messages depending on the implementation. For example, if the UE 1602 already has the list of indices 1610 (e.g., pre-defined at the UE 1602 or obtained via a prior communication, etc.), the network entity 1604 may be specified to just transmit the list of PRS resources 1612 and the mapping 1614 to the UE 1602 (via the same message or two different messages, etc.).
At 1638, the UE 1602 may receive a measure a set of PRSs from the set of network nodes 1606 (or from a subset of network nodes in the set of network nodes 1606), which may be referred to as PRS measurements. Then, the UE 1602 may transmit/provide/input the PRS measurements to an AI/ML positioning model 1608 for model training and/or inferencing, such as described in connection with
At 1640, when there is a change or update to the mapping between the list of indices 1610 and the list of PRS resources 1612 (e.g., after a period of time, after a change in deployment of TRPs, etc.), the network entity 1604 may transmit, to and for the UE 1602, an updated mapping 1616 that indicates the updates/changes to the mapping 1614. In some examples, the network entity 1604 may be configured to indicate the entire updated mapping 1616 to the UE 1602, such as shown at
In some scenarios, as shown at 1642, when there is a change or update to the list of indices 1610, the network entity 1604 may transmit, to and for the UE 1602, an updated list of indices 1618 that indicates the updates/changes to the list of indices 1610. Similarly, the network entity 1604 may be configured to indicate the entire updated list of indices 1618, or just the difference(s) between the initial/previous indexing (e.g., the list of indices 1610) and the new/updated indexing (e.g., the updated list of indices 1618) to reduce signaling overhead.
In some implementations, as shown at 1644, the network entity 1604 may be configured to transmit/provide, to or for the UE 1602, the list of indices 1610, the mapping 1614, the updated mapping 1616, and/or the updated list of indices 1618 based on the request of the UE 1602. For example, the UE 1602 may transmit, to the network entity 1604, a request for at least one of the list of indices 1610, the mapping 1614, the updated mapping 1616, and/or the updated list of indices 1618. Then, the network entity 1604 may transmit the list of indices 1610, the mapping 1614, the updated mapping 1616, and/or the updated list of indices 1618 based on the request 1620.
In another example, as shown at 1646, the network entity 1604 may transmit, to or for the UE 1602, a configuration 1622 associated with the request 1620. For example, the configuration 1622 may configure the UE 1602 on how often and/or when to send the request. For example, the configuration 1622 may configure the UE 1602 with a periodicity to transmit the request 1620 (e.g., every 10 days, every month, etc.), a condition or a triggering event (e.g., event-based) for transmitting the request 1620 (e.g., when the UE 1602 moves to an area with new TRPs, the number of handover (HO) performed by the UE 1602 exceeds a number threshold, etc.), and/or time-expiration condition(s) for stop transmitting the request 1620 (e.g., the UE 1602 may transmit the request 1620 until a time period expires, or until a defined condition is met, such as the UE 1602 leaving the area covered by the set of network nodes 1606), etc.
In some examples, as shown at 1648, the UE 1602 may select, decide, and/or configure a UE-sided AI/ML positioning model (e.g., the AI/ML positioning model 1608) based on the mapping 1614 (e.g., the first/initial mapping) and/or the updated mapping 1616 (e.g., the second/updated mapping). In some examples, at least for training data collection purposes, the mapping 1614 may be incorporated as part of the training data used to train the UE-sided AI/ML positioning model.
In another aspect of the present disclosure, the network entity 1604 may be configured to provide a simple indication of change in the mapping or an indication of the presence of the mapping. For example, as shown at 1650, the network entity 1604 may configure and transmit an indication 1624, to or for the UE 1602, where the indication 1624 may indicate that a mapping (e.g., the mapping 1614, or a previous implementation (existence) of the mapping 1614) has been set for associating PRS resources to location and beams of the set of network nodes 1606. In other words, instead of transmitting the list of indices 1610, the list of PRS resources 1612, and/or the mapping 1614 (or the updated mapping 1616) to the UE 1602, the network entity 1604 may first indicate/inform the UE 1602 regarding the existence of the list of indices 1610, the list of PRS resources 1612, and/or the mapping 1614, etc. In some examples, the indication 1624 may be a simple one-bit flag (e.g., bit 1 indicates a mapping between PRS resources and TRPs/beams exists, and bit 0 indicates there is no mapping between PRS resources and TRPs/beams, etc.).
In response to the indication 1624, the UE 1602 may determine whether to utilize the mapping mechanism, such as for training its AI/ML positioning model. For example, based on the indication 1624, at 1644, the UE 1602 may transmit a request for the list of indices 1610, the mapping 1614, the updated mapping 1616, and/or the updated list of indices 1618, etc. Such configuration may conserve transmission resources as not all UEs may specify the mapping (e.g., UEs that do not need the mapping may skip sending the request 1620 and/or receiving mapping related information from the network entity 1604). Then, as described in connection with 1630, 1632, 1634, and/or 1640, the network entity 1604 may transmit, to or for the UE 1602, the list of indices 1610, the mapping 1614, the updated mapping 1616, and/or the updated list of indices 1618 based on the request 1620.
Aspects described above provide virtual mapping between anchor location/beams and positioning reference resources. A network (NW) can indicate, to the UE, a “virtual map” between PRS resources and TRP locations/beams that does not tell the exact TRP location/beam information and/or does not specify disclosing cells physical and global IDs. This enables the UE to decide how to map PRS measurements to its AI/M model and/or update and switch the model (as applicable); the NW can maintain a “unique” indexing for Cells/sites/TRPs and their beams and indicate how PRS resources (i.e., PFL ID, Set IDs, PRS IDs) map to this indexing. Aspects described above provide several proposals directed to signaling, configurations, and protocols directed to the NW, UE, and location server (LMF) for the “virtual” mapping of anchor locations/beams and PRS resources, maintenance/update of the mapping, as well as training data collection for AI/ML positioning model.
At 1706, the UE may receiving, from a network entity, at least one of: (1) a first indication of a first mapping and a first list of indices for first location information, where the first location information is associated with a first set of network nodes and a first set of PRS resources, and where the first mapping associates each index in the first list of indices with at least one PRS resource in the first set of PRS resources, or (2) a second indication of a previous implementation of the first mapping, such as described in connection with
At 1708, the UE may select or configure at least one AI/ML positioning model based on at least one of the first indication or the second indication, such as described in connection with
In one example, the UE may receive, from the network entity, a third indication of a second mapping that associates a second list of indices for second location information associated with a second set of network nodes and a second set of PRS resources, where the second set of network nodes is at least partially different from the first set of network nodes; and the UE may configure the at least one AI/ML positioning model based on the second mapping or selecting another AI/ML positioning model based on the second mapping, such as described in connection with
In another example, the first location information may include a first set of locations and beams associated with the first set of network nodes, and where the second location information may include a second set of locations and beams associated with the second set of network nodes.
In another example, the UE may train the at least one AI/ML positioning model based on the first mapping or the second mapping.
In another example, the at least one AI/ML positioning model may be at least one UE-side AI/ML positioning model.
In another example, the network entity is a location server or an LMF, and the first set of nodes includes one or more TRPs, one or more cells, one or more sites, or a combination thereof.
In another example, the UE may receive, from the network entity, an updated list of indices for the first location information, where the updated list of indices is at least partially different from the first list of indices, such as described in connection with
In another example, the UE may transmit, to the network entity, a request to provide at least one of: the first mapping, the first list of indices for the first location information, the second mapping, the second list of indices for the second location information, or an updated list of indices for the first location information, such as described in connection with
In another example, the UE may receive, from the network entity, a configuration indicating at least one of a periodicity or a condition for the transmission of the request, such as described in connection with
In another example, the UE may receive, from the network entity in response to the second indication, a notification regarding an update or a change for the first mapping. In some implementations, the UE may transmit, to the network entity, a request to provide the notification regarding the update or the change for the first mapping, where the notification is received based on the request. In some implementations, the UE may receive, from the network entity, a configuration indicating at least one of a periodicity or a condition for the transmission of the request. In some implementations, the UE may configure the at least one AI/ML positioning model based on the notification, or select another AI/ML positioning model based on the notification.
At 1806, the UE may receiving, from a network entity, at least one of: (1) a first indication of a first mapping and a first list of indices for first location information, where the first location information is associated with a first set of network nodes and a first set of PRS resources, and where the first mapping associates each index in the first list of indices with at least one PRS resource in the first set of PRS resources, or (2) a second indication of a previous implementation of the first mapping, such as described in connection with
At 1808, the UE may select or configure at least one AI/ML positioning model based on at least one of the first indication or the second indication, such as described in connection with
At 1810, the UE may receive, from the network entity, a third indication of a second mapping that associates a second list of indices for second location information associated with a second set of network nodes and a second set of PRS resources, where the second set of network nodes is at least partially different from the first set of network nodes; and the UE may configure the at least one AI/ML positioning model based on the second mapping or selecting another AI/ML positioning model based on the second mapping, such as described in connection with
In one example, the first location information may include a first set of locations and beams associated with the first set of network nodes, and where the second location information may include a second set of locations and beams associated with the second set of network nodes.
In another example, the UE may train the at least one AI/ML positioning model based on the first mapping or the second mapping.
In another example, the at least one AI/ML positioning model may be at least one UE-side AI/ML positioning model.
In another example, the network entity is a location server or an LMF, and the first set of nodes includes one or more TRPs, one or more cells, one or more sites, or a combination thereof.
At 1812, the UE may receive, from the network entity, an updated list of indices for the first location information, where the updated list of indices is at least partially different from the first list of indices, such as described in connection with
In one example, as shown at 1804, the UE may transmit, to the network entity, a request to provide at least one of: the first mapping, the first list of indices for the first location information, the second mapping, the second list of indices for the second location information, or an updated list of indices for the first location information, such as described in connection with
In another example, as shown at 1802, the UE may receive, from the network entity, a configuration indicating at least one of a periodicity or a condition for the transmission of the request, such as described in connection with
In another example, the UE may receive, from the network entity in response to the second indication, a notification regarding an update or a change for the first mapping. In some implementations, the UE may transmit, to the network entity, a request to provide the notification regarding the update or the change for the first mapping, where the notification is received based on the request. In some implementations, the UE may receive, from the network entity, a configuration indicating at least one of a periodicity or a condition for the transmission of the request. In some implementations, the UE may configure the at least one AI/ML positioning model based on the notification, or select another AI/ML positioning model based on the notification.
As discussed supra, the mapping application component 198 may be configured to receive, from a network entity, at least one of: (1) a first indication of a first mapping and a first list of indices for first location information, where the first location information is associated with a first set of network nodes and a first set of PRS resources and where the first mapping associates each index in the first list of indices with at least one PRS resource in the first set of PRS resources, or (2) a second indication of a previous implementation of the first mapping. The mapping application component 198 may also be configured to select or configure at least one AI/ML positioning model based on at least one of the first indication or the second indication. The mapping application component 198 may be within the cellular baseband processor(s) 1924, the application processor(s) 1906, or both the cellular baseband processor(s) 1924 and the application processor(s) 1906. The mapping application component 198 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes/algorithm individually or in combination. As shown, the apparatus 1904 may include a variety of components configured for various functions. In one configuration, the apparatus 1904, and in particular the cellular baseband processor(s) 1924 and/or the application processor(s) 1906, may include means for receiving, from a network entity, at least one of: (1) a first indication of a first mapping and a first list of indices for first location information, where the first location information is associated with a first set of network nodes and a first set of PRS resources and where the first mapping associates each index in the first list of indices with at least one PRS resource in the first set of PRS resources, or (2) a second indication of a previous implementation of the first mapping. The apparatus 1904 may further include means for selecting or means for configuring at least one AI/ML positioning model based on at least one of the first indication or the second indication.
In one configuration, the apparatus 1904 may further include means for receiving, from the network entity, a third indication of a second mapping that associates a second list of indices for second location information associated with a second set of network nodes and a second set of PRS resources, where the second set of network nodes is at least partially different from the first set of network nodes; and means for configuring the at least one AI/ML positioning model based on the second mapping or selecting another AI/ML positioning model based on the second mapping.
In another configuration, the first location information may include a first set of locations and beams associated with the first set of network nodes, and where the second location information may include a second set of locations and beams associated with the second set of network nodes.
In another configuration, the apparatus 1904 may further include means for training the at least one AI/ML positioning model based on the first mapping or the second mapping.
In another configuration, the at least one AI/ML positioning model may be at least one UE-side AI/ML positioning model.
In another configuration, the network entity is a location server or an LMF, and the first set of nodes includes one or more TRPs, one or more cells, one or more sites, or a combination thereof.
In another configuration, the apparatus 1904 may further include means for receiving, from the network entity, an updated list of indices for the first location information, where the updated list of indices is at least partially different from the first list of indices.
In another configuration, the apparatus 1904 may further include means for transmitting, to the network entity, a request to provide at least one of: the first mapping, the first list of indices for the first location information, the second mapping, the second list of indices for the second location information, or an updated list of indices for the first location information.
In another configuration, the apparatus 1904 may further include means for receiving, from the network entity, a configuration indicating at least one of a periodicity or a condition for the transmission of the request.
In another configuration, the apparatus 1904 may further include means for receiving, from the network entity in response to the second indication, a notification regarding an update or a change for the first mapping. In some implementations, the apparatus 1904 may further include means for transmitting, to the network entity, a request to provide the notification regarding the update or the change for the first mapping, where the notification is received based on the request. In some implementations, the apparatus 1904 may further include means for receiving, from the network entity, a configuration indicating at least one of a periodicity or a condition for the transmission of the request. In some implementations, the apparatus 1904 may further include means for configuring the at least one AI/ML positioning model based on the notification, or select another AI/ML positioning model based on the notification.
The means may be the mapping application component 198 of the apparatus 1904 configured to perform the functions recited by the means. As described supra, the apparatus 1904 may include the TX processor 368, the RX processor 356, and the controller/processor 359. As such, 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.
At 2006, the network entity may configure at least one of: (1) a first mapping and a first list of indices for first location information, where the first location information is associated with a first set of network nodes and a first set of PRS resources and where the first mapping associates each index in the first list of indices with at least one PRS resource in the first set of PRS resources, or (2) a previous implementation of the first mapping, such as described in connection with
In one example, the network entity is a location server or an LMF, and where the first set of nodes includes one or more TRPs, one or more cells, one or more sites, or a combination thereof.
At 2008, the network entity may transmit, to a UE, at least one of (1) a first indication of the first mapping and the first list of indices for the first location information, or (2) a second indication of the previous implementation of the first mapping, such as described in connection with
In another example, the network entity may transmit, to the UE, an updated list of indices for the first location information, where the updated list of indices is at least partially different from the first list of indices, such as described in connection with
In another example, the network entity may receive, from the UE, a request to provide at least one of: the first mapping, the first list of indices for the first location information, the second mapping, the second list of indices for the second location information, or an updated list of indices for the first location information, such as described in connection with
In another example, the network entity may transmit, to the UE, a configuration indicating at least one of a periodicity or a condition for a transmission of the request, such as described in connection with
In another example, the network entity may transmit, to the UE based on the second indication, a notification regarding an update or a change for the first mapping. In some implementations, the network entity may receive, from the UE, a request to provide the notification regarding the update or the change for the first mapping, where the notification is transmitted based on the request. In some implementations, the network entity may transmit, to the UE, a configuration indicating at least one of a periodicity or a condition for a transmission of the request.
At 2106, the network entity may configure at least one of: (1) a first mapping and a first list of indices for first location information, where the first location information is associated with a first set of network nodes and a first set of PRS resources and where the first mapping associates each index in the first list of indices with at least one PRS resource in the first set of PRS resources, or (2) a previous implementation of the first mapping, such as described in connection with
In one example, the network entity is a location server or an LMF, and where the first set of nodes includes one or more TRPs, one or more cells, one or more sites, or a combination thereof.
At 2108, the network entity may transmit, to a UE, at least one of (1) a first indication of the first mapping and the first list of indices for the first location information, or (2) a second indication of the previous implementation of the first mapping, such as described in connection with
At 2110, the network entity may transmit, to the UE, a third indication of a second mapping that associates a second list of indices for second location information associated with a second set of network nodes and a second set of PRS resources, where the second set of network nodes is at least partially different from the first set of network nodes, such as described in connection with
At 2112, the network entity may transmit, to the UE, an updated list of indices for the first location information, where the updated list of indices is at least partially different from the first list of indices, such as described in connection with
In one example, as shown at 2104, the network entity may receive, from the UE, a request to provide at least one of: the first mapping, the first list of indices for the first location information, the second mapping, the second list of indices for the second location information, or an updated list of indices for the first location information, such as described in connection with
In another example, as shown at 2102, the network entity may transmit, to the UE, a configuration indicating at least one of a periodicity or a condition for a transmission of the request, such as described in connection with
In one example, the network entity may transmit, to the UE based on the second indication, a notification regarding an update or a change for the first mapping. In some implementations, the network entity may receive, from the UE, a request to provide the notification regarding the update or the change for the first mapping, where the notification is transmitted based on the request. In some implementations, the network entity may transmit, to the UE, a configuration indicating at least one of a periodicity or a condition for a transmission of the request.
As discussed supra, the mapping indication component 197 may be configured to configure at least one of: (1) a first mapping and a first list of indices for first location information, where the first location information is associated with a first set of network nodes and a first set of PRS resources and where the first mapping associates each index in the first list of indices with at least one PRS resource in the first set of PRS resources, or (2) a previous implementation of the first mapping. The mapping indication component 197 may also be configured to transmit, to a UE, at least one of (1) a first indication of the first mapping and the first list of indices for the first location information, or (2) a second indication of the previous implementation of the first mapping. The mapping indication component 197 may be within the network processor(s) 2212. The mapping indication component 197 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes/algorithm individually or in combination. The network entity 2260 may include a variety of components configured for various functions. In one configuration, the network entity 2260 may include means for configuring at least one of: (1) a first mapping and a first list of indices for first location information, where the first location information is associated with a first set of network nodes and a first set of PRS resources and where the first mapping associates each index in the first list of indices with at least one PRS resource in the first set of PRS resources, or (2) a previous implementation of the first mapping. The network entity 2260 may further include means for transmitting, to a UE, at least one of (1) a first indication of the first mapping and the first list of indices for the first location information, or (2) a second indication of the previous implementation of the first mapping.
In one configuration, the network entity is a location server or an LMF, and where the first set of nodes includes one or more TRPs, one or more cells, one or more sites, or a combination thereof.
In another configuration, the network entity 2260 may further include means for transmitting, to the UE, a third indication of a second mapping that associates a second list of indices for second location information associated with a second set of network nodes and a second set of PRS resources, where the second set of network nodes is at least partially different from the first set of network nodes.
In another configuration, the network entity 2260 may further include means for transmitting, to the UE, an updated list of indices for the first location information, where the updated list of indices is at least partially different from the first list of indices.
In another configuration, the network entity 2260 may further include means for receiving, from the UE, a request to provide at least one of: the first mapping, the first list of indices for the first location information, the second mapping, the second list of indices for the second location information, or an updated list of indices for the first location information.
In another configuration, the network entity 2260 may further include means for transmitting, to the UE, a configuration indicating at least one of a periodicity or a condition for a transmission of the request.
In another configuration, the network entity 2260 may further include means for transmitting, to the UE based on the second indication, a notification regarding an update or a change for the first mapping. In some implementations, the network entity 2260 may further include means for receiving, from the UE, a request to provide the notification regarding the update or the change for the first mapping, where the notification is transmitted based on the request. In some implementations, the network entity 2260 may further include means for transmitting, to the UE, a configuration indicating at least one of a periodicity or a condition for a transmission of the request.
The means may be the mapping indication component 197 of the network entity 2260 configured to perform the functions recited by the means.
It is understood that the specific order or hierarchy of blocks in the processes/flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes/flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not limited to the specific order or hierarchy presented.
The previous 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 readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims. Reference to an element in the singular does not mean “one and only one” unless specifically so stated, but rather “one or more.” Terms such as “if,” “when,” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, 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 multiples of A, multiples of B, or multiples of 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 A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. Sets should be interpreted as a set of elements where the elements number one or more. Accordingly, for a set of X, X would include one or more elements. When at least one processor is configured to perform a set of functions, the at least one processor, individually or in any combination, is configured to perform the set of functions. Accordingly, each processor of the at least one processor may be configured to perform a particular subset of the set of functions, where the subset is the full set, a proper subset of the set, or an empty subset of the set. If a first apparatus receives data from or transmits data to a second apparatus, the data may be received/transmitted directly between the first and second apparatuses, or indirectly between the first and second apparatuses through a set of apparatuses. A device configured to “output” data, such as a transmission, signal, or message, may transmit the data, for example with a transceiver, or may send the data to a device that transmits the data. A device configured to “obtain” data, such as a transmission, signal, or message, may receive, for example with a transceiver, or may obtain the data from a device that receives the data. Information stored in a memory includes instructions and/or data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.”
As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently.
The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.
Aspect 1 is a method of wireless communication at a user equipment (UE), comprising: receiving, from a network entity, at least one of: (1) a first indication of a first mapping and a first list of indices for first location information, wherein the first location information is associated with a first set of network nodes and a first set of positioning reference signal (PRS) resources and wherein the first mapping associates each index in the first list of indices with at least one PRS resource in the first set of PRS resources, or (2) a second indication of a previous implementation of the first mapping; and selecting or configuring at least one artificial intelligence (AI) or machine learning (ML)(AI/ML) positioning model based on at least one of the first indication or the second indication.
Aspect 2 is the method of aspect 1, further comprising: receiving, from the network entity, a third indication of a second mapping that associates a second list of indices for second location information associated with a second set of network nodes and a second set of PRS resources, wherein the second set of network nodes is at least partially different from the first set of network nodes; and configuring the at least one AI/ML positioning model based on the second mapping or selecting another AI/ML positioning model based on the second mapping.
Aspect 3 is the method of aspect 1 or aspect 2, wherein the first location information includes a first set of locations and beams associated with the first set of network nodes, and wherein the second location information includes a second set of locations and beams associated with the second set of network nodes.
Aspect 4 is the method of any of aspects 1 to 3, further comprising: receiving, from the network entity, an updated list of indices for the first location information, wherein the updated list of indices is at least partially different from the first list of indices.
Aspect 5 is the method of any of aspects 1 to 4, further comprising: transmitting, to the network entity, a request to provide at least one of: the first mapping, the first list of indices for the first location information, the second mapping, the second list of indices for the second location information, or an updated list of indices for the first location information.
Aspect 6 is the method of any of aspects 1 to 5, further comprising: receiving, from the network entity, a configuration indicating at least one of a periodicity or a condition for the transmission of the request.
Aspect 7 is the method of any of aspects 1 to 6, further comprising: training the at least one AI/ML positioning model based on the first mapping or the second mapping.
Aspect 8 is the method of any of aspects 1 to 7, wherein the at least one AI/ML positioning model is at least one UE-side AI/ML positioning model.
Aspect 9 is the method of any of aspects 1 to 8, further comprising: receiving, from the network entity in response to the second indication, a notification regarding an update or a change for the first mapping.
Aspect 10 is the method of any of aspects 1 to 9, further comprising: transmitting, to the network entity, a request to provide the notification regarding the update or the change for the first mapping, wherein the notification is received based on the request.
Aspect 11 is the method of any of aspects 1 to 10, further comprising: receiving, from the network entity, a configuration indicating at least one of a periodicity or a condition for the transmission of the request.
Aspect 12 is the method of any of aspects 1 to 11, further comprising: configuring the at least one AI/ML positioning model based on the notification, or selecting another AI/ML positioning model based on the notification.
Aspect 13 is the method of any of aspects 1 to 12, wherein the network entity is a location server or a location management function (LMF), and wherein the first set of nodes includes one or more transmission reception points (TRPs), one or more cells, one or more sites, or a combination thereof.
Aspect 14 is an apparatus for wireless communication at a user equipment (UE), including: at least one memory; and at least one processor coupled to the at least one memory and, based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to implement any of aspects 1 to 13.
Aspect 15 is the apparatus of aspect 14, further including at least one of a transceiver or an antenna coupled to the at least one processor.
Aspect 16 is an apparatus for wireless communication including means for implementing any of aspects 1 to 13.
Aspect 17 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 1 to 13.
Aspect 18 is a method of wireless communication at a network entity, comprising: configuring at least one of: (1) a first mapping and a first list of indices for first location information, wherein the first location information is associated with a first set of network nodes and a first set of positioning reference signal (PRS) resources and wherein the first mapping associates each index in the first list of indices with at least one PRS resource in the first set of PRS resources, or (2) a previous implementation of the first mapping; and transmitting, to a user equipment (UE), at least one of (1) a first indication of the first mapping and the first list of indices for the first location information, or (2) a second indication of the previous implementation of the first mapping.
Aspect 19 is the method of aspect 18, further comprising: transmitting, to the UE, a third indication of a second mapping that associates a second list of indices for second location information associated with a second set of network nodes and a second set of PRS resources, wherein the second set of network nodes is at least partially different from the first set of network nodes.
Aspect 20 is the method of aspect 18 or aspect 19, wherein the first location information includes a first set of locations and beams associated with the first set of network nodes, and wherein the second location information includes a second set of locations and beams associated with the second set of network nodes.
Aspect 21 is the method of any of aspects 18 to 20, further comprising: transmitting, to the UE, an updated list of indices for the first location information, wherein the updated list of indices is at least partially different from the first list of indices.
Aspect 22 is the method of any of aspects 18 to 21, further comprising: receiving, from the UE, a request to provide at least one of: the first mapping, the first list of indices for the first location information, the second mapping, the second list of indices for the second location information, or an updated list of indices for the first location information.
Aspect 23 is the method of any of aspects 18 to 22, further comprising: transmitting, to the UE, a configuration indicating at least one of a periodicity or a condition for a transmission of the request.
Aspect 24 is the method of any of aspects 18 to 23, further comprising: transmitting, to the UE based on the second indication, a notification regarding an update or a change for the first mapping.
Aspect 25 is the method of any of aspects 18 to 24, further comprising: receiving, from the UE, a request to provide the notification regarding the update or the change for the first mapping, wherein the notification is transmitted based on the request.
Aspect 26 is the method of any of aspects 18 to 25, further comprising: transmitting, to the UE, a configuration indicating at least one of a periodicity or a condition for a transmission of the request.
Aspect 27 is the method of any of aspects 18 to 26, wherein the network entity is a location server or a location management function (LMF), and wherein the first set of nodes includes one or more transmission reception points (TRPs), one or more cells, one or more sites, or a combination thereof.
Aspect 28 is an apparatus for wireless communication at a network entity, including: at least one memory; and at least one processor coupled to the at least one memory and, based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to implement any of aspects 18 to 27.
Aspect 29 is the apparatus of aspect 28, further including at least one of a transceiver or an antenna coupled to the at least one processor.
Aspect 30 is an apparatus for wireless communication including means for implementing any of aspects 18 to 27.
Aspect 31 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 18 to 27.
