Indication of quasi-co-location relationship for artificial intelligence - machine learning based positioning

Abstract

Techniques for utilizing QCL relationships of AI / ML models and reference signals are provided. An example method for providing positioning reference signal configuration information includes receiving, from a wireless node, an indication of a quasi-co-location (QCL) relationship between an AI / ML model and a reference signal, configuring one or more positioning reference signal resources based at least in part on the indication of the QCL relationship, and providing configuration information for the one or more positioning reference signal resources to the wireless node.

Description

Cross-references to related applications

[0001] This application claims the benefit of U.S. Patent Application No. 18 / 502,250, filed November 6, 2023, entitled “INDICATION OF QUASI CO-LOCATIONRELATION FOR ARTIFICIAL INTELLIGENCE - MACHINE LEARNING BASED POSITIONING”, which has been assigned to the assignee of this application and whose entire contents are hereby incorporated herein by reference for all purposes. Background Technology

[0002] Wireless communication systems have gone through several generations of development, including first-generation analog wireless telephone service (1G), second-generation (2G) digital wireless telephone service (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data wireless service with internet capabilities, and fourth-generation (4G) services (e.g., LTE or WiMax). ® ), and fifth-generation (5G) services (e.g., 5G New Radio (NR), etc.). Currently, there are many different types of wireless communication systems in use, including cellular and Personal Communication Services (PCS) systems. Known examples of cellular systems include cellular analog advanced mobile phone systems (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Time Division Multiple Access (TDMA), Global System for Mobile Access (GSM) TDMA variants, etc.

[0003] The fifth-generation (5G) mobile standard demands higher data transmission speeds, a greater number of connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance (NGC), the 5G standard is designed to provide tens of megabits per second (Mbps) of data to each of tens of thousands of users, or 1 gigabit per second (Gbps) to dozens of workers on an office floor. To support large-scale sensor deployments, it should support hundreds of thousands of simultaneous connections. Therefore, the spectral efficiency of 5G mobile communications should be significantly improved compared to the current 4G standard. Furthermore, signaling efficiency should be improved, and latency should be significantly reduced compared to the current standard.

[0004] It is typically desired to know the location of a user equipment (UE), such as a cellular phone, where the terms "location" and "positioning" are synonymous and used interchangeably herein. A Location Services (LCS) client may require knowledge of the UE's location and may communicate with a location center to request the UE's location. The location center and the UE may exchange messages appropriately to obtain a location estimate for the UE. The location center may then return this location estimate to the LCS client, for example, for use in one or more applications.

[0005] Obtaining the location of a mobile device accessing a wireless network can be useful for many applications, including emergency calls, personal navigation, asset tracking, and locating friends or family members. In industrial applications, the location of mobile devices can be essential for asset tracking, robot control, and other kinematic operations that may require precise positioning of end effectors. Existing positioning methods include those based on measuring radio signals transmitted from various devices, including satellite carriers and terrestrial radio sources (such as base stations and access points) within the wireless network. Stations in the wireless network can be configured to transmit reference signals that enable mobile devices to perform positioning measurements. Summary of the Invention

[0006] An example method for obtaining the output of an AI / ML model according to this disclosure includes: receiving an indication of a quasi-co-addressable (QCL) relationship between the AI / ML model and a reference signal; obtaining one or more measurements associated with the reference signal; and calculating the output of the AI / ML model based at least in part on the one or more measurements.

[0007] An example method for providing positioning reference signal configuration information according to this disclosure includes: receiving from a wireless node an indication of a quasi-co-location (QCL) relationship between an AI / ML model and a reference signal; configuring one or more positioning reference signal resources based at least in part on the indication of the QCL relationship; and providing the wireless node with configuration information for the one or more positioning reference signal resources.

[0008] The projects and / or technologies described herein can provide one or more of the following capabilities, as well as others not mentioned. Wireless nodes or network servers can be configured to indicate a quasi-co-location (QCL) relationship between an artificial intelligence / machine learning (AI / ML) localization model and a reference signal. The AI / ML model can be trained and / or provided by the wireless node or network server. The wireless node can be configured to prioritize and select reference signal resources for measurement and reporting, at least in part, based on the QCL relationship with the AI / ML model. The accuracy of localization estimation for mobile devices can be improved. Other capabilities can be provided, and not every specific embodiment according to this disclosure is required to provide any, let alone all, of the capabilities discussed. Attached Figure Description

[0009] Figure 1 This is a simplified diagram of an example wireless communication system.

[0010] Figure 2 yes Figure 1 The diagram shows a block diagram of the components of an example user device.

[0011] Figure 3 This is a block diagram of the components of an example send / receive point.

[0012] Figure 4 This is a block diagram of the server components, with various examples of the server in... Figure 1 As shown in the image.

[0013] Figure 5A and Figure 5B This is a block diagram of an example artificial intelligence / machine learning (AI / ML) model used for positioning applications.

[0014] Figure 6A This includes block diagrams of example UE-based and UE-assisted positioning technologies with AI / ML models.

[0015] Figure 6B A block diagram including example node-assisted localization techniques with AI / ML models.

[0016] Figure 7 This is an example of an old-style QCL relationship between reference signals.

[0017] Figure 8 This is an example of the QCL relationship between the reference signal and the AI / ML model.

[0018] Figure 9A and Figure 9B This is a sample message flow diagram used to instruct the QCL AI / ML positioning model.

[0019] Figure 10 This is a flowchart of an example method for obtaining the output of an AI / ML model.

[0020] Figure 11 This is a flowchart of an example method for providing positioning reference signal configuration information. Detailed Implementation

[0021] This paper discusses techniques for leveraging the QCL relationship between AI / ML models and reference signals. AI / ML positioning models can be configured to learn solutions for mapping specific reference signal characteristics and site-specific features. For example, AI / ML models can be specific to certain radio characteristics (e.g., delay spread, Doppler, spatial relationships, multiple spatial relationships, etc.). The techniques presented in this paper enable network nodes such as UEs and network servers (e.g., Location Management Functions (LMFs)) to indicate the applicable radio characteristics for AI / ML positioning models. These indications allow UEs and network servers (e.g., LMFs) to quickly and efficiently signal each other the suitability of AI / ML models for the selection and prioritization of reference signal measurements and reporting. The indications also allow for the application of control (e.g., model lifecycle control) to AI / ML models, including model selection, switching between models, monitoring models, or fallback to non-AI / ML positioning methods.

[0022] In operation, the UE or LMF can be configured to indicate the QCL relationship between the AI / ML positioning model and a reference signal. The AI / ML model can be trained and / or provided by the UE or LMF. The UE-side AI / ML positioning model can be trained and / or provided by the UE, and the UE can indicate the model's QCL relationship information to the LMF. In one example, the UE-side AI / ML positioning model can be trained and / or provided by the LMF, and the LMF can be configured to provide the model's QCL relationship information to the UE. In another example, the LMF-side AI / ML positioning model can be trained and / or provided by the LMF, and the LMF can be configured to provide the model's QCL relationship information to the UE, and the UE can be configured to prioritize and select reference signal resources for measurement and reporting. In one example, the indicated QCL relationship can be used to apply model control (including selection, handover, and monitoring) to the UE-side AI / ML positioning model. In yet another example, the indicated QCL relationship can be used to apply model control (including selection, handover, and monitoring) to the LMF-side AI / ML positioning model. Generally speaking, the AI / ML model described in this paper provides AI / ML localization functionality, including an AI / ML localization physical model and / or an AI / ML localization logical model.

[0023] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages: AI / ML positioning models can be utilized with multiple reference signals and / or antenna ports. Network messaging protocols can be used to provide QCL relationships between the Positioning Reference Signal (PRS) and other reference signals (e.g., synchronization signal blocks (SSBs) and / or other PRSs). AI / ML positioning model lifecycle management can be simplified. Prioritization and selection of PRS resource measurements and reporting can be improved. The accuracy of positioning estimates for mobile devices can be improved. Other advantages may also be achieved.

[0024] Obtaining the location of a mobile device accessing a wireless network can be used for many applications, including emergency calls, personal navigation, consumer asset tracking, locating friends or family members, etc. Existing positioning methods include those based on measuring radio signals transmitted from various devices or entities, including satellite vehicles (SVs) in wireless networks and terrestrial radio sources such as base stations and access points. Standardization for 5G wireless networks is expected to include support for various positioning methods that can utilize reference signals transmitted by base stations for location determination in a manner similar to how LTE wireless networks currently use Positioning Reference Signals (PRS) and / or Cell-Specific Reference Signals (CRS).

[0025] The description herein can refer to a sequence of actions to be performed, for example, by elements of a computing device. The various actions described herein can be performed by special-purpose circuitry (e.g., an application-specific integrated circuit (ASIC)), by program instructions being executed by one or more processors, or by a combination of both. The sequence of actions described herein can be embodied in a non-transitory computer-readable medium storing a corresponding set of computer instructions that, when executed, will cause the associated processor to perform the functionality described herein. Therefore, the various examples described herein can be embodied in several different forms, all of which fall within the scope of this disclosure, including the claimed subject matter.

[0026] As used herein, the terms “User Equipment” (UE) and “Base Station” are not specific to or otherwise limited to any particular Radio Access Technology (RAT) unless otherwise indicated. Generally, a UE can be any wireless communication device used to communicate over a wireless communication network (e.g., mobile phone, router, tablet computer, laptop computer, consumer asset tracking device, Internet of Things (IoT) device, automobile, etc.). A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term “UE” can be interchangeably referred to as “Access Terminal” or “AT,” “Client Equipment,” “Wireless Equipment,” “Wireless Node,” “Subscriber Equipment,” “Subscriber Terminal,” “Subscriber Station,” “User Terminal” or “UT,” “Mobile Terminal,” “Mobile Station,” “Mobile Equipment,” or variations thereof. In general, a UE can communicate with the core network via the RAN, and through the core network, the UE can connect to external networks such as the Internet and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as via wired access networks, WiFi, etc. ®Networks (e.g., based on IEEE (Institute of Electrical and Electronics Engineers) 802.11, etc.). In addition to transmitting information to each other via the network, or instead of transmitting information to each other via the network, two or more UEs can communicate directly.

[0027] Depending on the network in which the base station is deployed, the base station can operate according to one of several RATs when communicating with the UE. Examples of base stations include access points (APs), network nodes, NodeBs, evolved NodeBs (eNBs), or generic NodeBs (gNodeBs, gNBs). Furthermore, in some systems, the base station may only provide edge node signaling functions, while in others, it may provide additional control and / or network management functions.

[0028] The UE can be represented by any of several types of devices, including but not limited to printed circuit (PC) cards, compact flash memory devices, external or internal modems, wireless or wired phones, smartphones, tablet devices, consumer asset tracking devices, asset tags, etc. The communication link through which the UE can transmit signals to the RAN is called an uplink channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the RAN can transmit signals to the UE is called a downlink or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term "traffic channel (TCH)" can refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0029] As used herein, depending on the context, the term "cell" or "sector" may correspond to one of a plurality of cells of a base station or to the base station itself. The term "cell" may refer to a logical communication entity used to communicate with a base station (e.g., on a carrier) and may be associated with identifiers to distinguish adjacent cells operating via the same or different carriers (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)). In some examples, a carrier may support multiple cells and may be configured with different cell types based on different protocol types that can provide access to different types of devices (e.g., Machine-Type Communication (MTC), Narrowband Internet of Things (NB-IoT), Enhanced Mobile Broadband (eMBB), or other protocol types). In some examples, the term "cell" may refer to a portion of the geographic coverage area on which a logical entity operates (e.g., a sector).

[0030] refer to Figure 1Examples of communication system 100 include UE 105, UE 106, radio access network (RAN) (here, fifth-generation (5G) next-generation (NG) RAN (NG-RAN) 135), 5G core network (5GC) 140, and server 150. UE 105 and / or UE 106 can be, for example, an IoT device, a location tracker device, a cellular phone, a vehicle (e.g., a car, truck, bus, ship, etc.), or another device. 5G network can also be referred to as a new radio (NR) network; NG-RAN 135 can be referred to as 5G RAN or NR RAN; and 5GC 140 can be referred to as NG core network (NGC). Standardization of NG-RAN and 5GC is underway within the 3rd Generation Partnership Project (3GPP). Therefore, NG-RAN 135 and 5GC 140 can follow current or future standards from 3GPP for 5G support. NG-RAN 135 can be another type of RAN, such as 3G RAN, 4G Long Term Evolution (LTE) RAN, etc. UE 106 can be configured and coupled similarly to UE 105 to transmit signals to and / or receive signals from similar other entities in system 100, but for simplicity of the figures, in Figure 1 Such signaling is not indicated in this document. Similarly, for simplicity, the discussion focuses on UE 105. Communication system 100 may utilize information from a constellation 185 of satellite spacecraft (SVs) 190, 191, 192, 193 from a satellite positioning system (SPS) such as GPS, GLONASS, Galileo, or BeiDou, or some other local or regional SPS (such as the Indian Regional Navigation Satellite System (IRNSS), the European Geostationary Navigation Coverage Service (EGNOS), or the Wide Area Augmentation System (WAAS)). Additional components of communication system 100 are described below. Communication system 100 may include additional or optional components.

[0031] like Figure 1As shown, NG-RAN 135 includes NR nodeBs (gNBs) 110a and 110b and a next-generation eNodeB (ng-eNB) 114, and 5GC 140 includes Access and Mobility Management Functions (AMF) 115, Session Management Functions (SMF) 117, Location Management Functions (LMF) 120, and Gateway Mobile Location Center (GMLC) 125. gNBs 110a, 110b, and ng-eNB 114 are communicatively coupled to each other, each configured to conduct bidirectional wireless communication with UE 105, and each communicatively coupled to AMF 115 and configured to conduct bidirectional communication with AMF. gNBs 110a, 110b, and ng-eNB 114 may be referred to as base stations (BS). AMF 115, SMF 117, LMF 120, and GMLC 125 are communicatively coupled to each other, and the GMLC is communicatively coupled to an external client 130. The SMF117 can be used as the initial contact point for the Service Control Function (SCF) (not shown) to create, control, and delete media sessions. Base stations (such as gNB 110a, 110b, and / or ng-eNB 114) can be macrocells (e.g., high-power cellular base stations), small cells (e.g., low-power cellular base stations), or access points (e.g., short-range base stations configured to use short-range technologies such as WiFi). ® WiFi ® Direct connection (WiFi) ® -D), Bluetooth ® ,Bluetooth ® Low power (BLE), Zigbee ® (e.g., one or more of gNB 110a, 110b and / or ng-eNB 114) can be configured to communicate with UE 105 via multiple carriers. Each of gNB 110a, 110b and / or ng-eNB 114 can provide communication coverage for a corresponding geographic area (e.g., cell). Each cell can be divided into multiple sectors based on the base station antennas.

[0032] Figure 1Generalized examples of various components are provided, wherein any or all of the components may be appropriately utilized, and each component may be repeated or omitted as needed. Specifically, although a UE 105 is illustrated, many UEs (e.g., hundreds, thousands, millions, etc.) may be utilized in communication system 100. Similarly, communication system 100 may include a larger (or smaller) number of SVs (i.e., more or fewer than the four SVs 190-193 shown), gNBs 110a and 110b, ng-eNB 114, AMF 115, external client 130, and / or other components. The illustrated connections connecting the various components in communication system 100 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. Furthermore, the components may be rearranged, combined, separated, replaced, and / or omitted according to desired functionality.

[0033] Although Figure 1 A 5G-based network is illustrated, but similar network implementations and configurations can be used for other communication technologies such as 3G, Long Term Evolution (LTE), etc. The specific implementations described herein (for 5G technology and / or for one or more other communication technologies and / or protocols) can be used to transmit (or broadcast) directional synchronization signals, receive and measure directional signals at a UE (e.g., UE 105), and / or provide location assistance to UE 105 (via GMLC 125 or other location servers), and / or calculate the location of UE 105 at a location-capable device (such as UE 105, gNB 110a, 110b, or LMF 120) based on measurement parameters received at UE 105 for such directional transmissions. Gateway Mobile Location Center (GMLC) 125, Location Management Function (LMF) 120, Access and Mobility Management Function (AMF) 115, SMF 117, ng-eNB (eNodeB) 114, and gNB (gNodeB) 110a, 110b are examples and may be replaced by, or include, various other location server functions and / or base station functions, respectively.

[0034] System 100 is capable of wireless communication because its components can communicate directly or indirectly (at least sometimes using a wireless connection), for example, via gNB 110a, 110b, ng-eNB 114 and / or 5GC 140 (and / or one or more other devices not shown, such as one or more other transceiver base stations). For indirect communication, the communication can be modified during transmission from one entity to another, for example, by changing the header information of data packets, changing the format, etc. UE 105 may include multiple UEs and may be mobile wireless communication devices, but can communicate wirelessly as well as via wired connections. UE 105 can be any of a variety of devices, such as smartphones, tablets, vehicle-based devices, etc., but these are merely examples, as UE 105 does not need to be any of these configurations, and other configurations of UEs can be used. Other UEs may include wearable devices (e.g., smartwatches, smart jewelry, smart glasses, or head-mounted devices, etc.). Other UEs, whether currently existing or developed in the future, may also be used. In addition, other wireless devices (whether mobile or not) can be implemented within system 100 and can communicate with each other and / or with UE 105, gNB 110a, 110b, ng-eNB 114, 5GC 140, and / or external client 130. For example, such other devices may include Internet of Things (IoT) devices, medical devices, home entertainment and / or automation devices, etc. 5GC 140 can communicate with external client 130 (e.g., a computer system), for example, to allow external client 130 (e.g., via GMLC 125) to request and / or receive location information about UE 105.

[0035] UE 105 or other devices can be configured to communicate in various networks and / or for various purposes and / or using various technologies (e.g., 5G, Wi-Fi). ® Communication, multi-frequency Wi-Fi ® Communication, satellite positioning, and one or more types of communication (e.g., GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), LTE (Long Term Evolution), V2X (vehicle-to-everything communication, e.g., V2P (vehicle-to-pedestrian), V2I (vehicle-to-infrastructure), V2V (vehicle-to-vehicle), etc.), IEEE 802.11p, etc.). V2X communication can be cellular (Cellular-V2X (C-V2X)) and / or WiFi. ®(For example, DSRC (Dedicated Short Range Connection)). System 100 can support operation on multiple carriers (waveform signals of different frequencies). A multi-carrier transmitter can transmit modulated signals simultaneously on multiple carriers. Each modulated signal can be a Code Division Multiple Access (CDMA) signal, a Time Division Multiple Access (TDMA) signal, an Orthogonal Frequency Division Multiple Access (OFDMA) signal, a Single Carrier Frequency Division Multiple Access (SC-FDMA) signal, etc. Each modulated signal can be transmitted on different carriers and can carry pilot, overhead information, data, etc. UEs 105 and 106 can communicate with each other via UE-to-UE sidelink (SL) communication by transmitting on one or more sidelink (SL) channels (such as the Physical Sidelink Synchronization Channel (PSSCH), Physical Sidelink Broadcast Channel (PSBCH), or Physical Sidelink Control Channel (PSCCH)). Direct device-to-device communication (without a network) is generally referred to as sidelink communication, without limiting the communication to a specific protocol.

[0036] UE 105 may include and / or may be referred to as a device, mobile device, wireless device, mobile terminal, terminal, mobile station (MS), Secure User Plane Location Enabled (SUPL) terminal (SET), or some other name. Furthermore, UE 105 may correspond to a cellular phone, smartphone, laptop computer, tablet device, PDA, consumer asset tracking device, navigation device, Internet of Things (IoT) device, health monitor, security system, smart city sensor, smart meter, wearable tracker, or some other portable or mobile device. Typically, although not mandatory, UE 105 may use one or more Radio Access Technologies (RATs) to support wireless communication, such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), LTE, High Rate Packet Data (HRPD), IEEE 802.11 WiFi, etc. ® (Also known as Wi-Fi) ® ),Bluetooth ® (BT), WiMax (Global Microwave Access) ® 5G New Radio (NR) (e.g., using NG-RAN 135 and 5GC 140), etc. UE 105 can use a Wireless Local Area Network (WLAN) to support wireless communication, which can connect to other networks (e.g., the Internet) using, for example, digital subscriber line (DSL) or packet cable. Using one or more of these RATs allows UE 105 (e.g., via elements of 5GC 140) Figure 1(not shown in the image), or possibly via GMLC 125, to communicate with external client 130 and / or allow external client 130 (e.g., via GMLC 125) to receive location information about UE 105.

[0037] UE 105 may include a single entity or may include multiple entities, such as in a personal area network, where the user may employ audio, video, and / or data I / O (input / output) devices, and / or body sensors, as well as separate wired or wireless modems. An estimate of the location of UE 105 may be referred to as location, location estimate, location fixed, fixed, positioning, location estimation, or location fixed, and may be geographic, providing the location coordinates of UE 105 (e.g., latitude and longitude), which may or may not include an elevation component (e.g., height above sea level; height above ground level, floor level, or basement level, or depth below). Alternatively, the location of UE 105 may be expressed as a municipal location (e.g., a postal address or designation of a point or smaller area within a building, such as a specific room or floor). The location of UE 105 may be represented as an area or volume (geographically or municipally defined) within which UE 105 is expected to be located with a certain probability or confidence level (e.g., 67%, 95%, etc.). The location of UE 105 can be represented as a relative location, which includes, for example, distance and direction relative to a known location. This relative location can be represented as relative coordinates (e.g., X, Y (and Z) coordinates) defined relative to an origin at a known location, which can be, for example, geographically, municipally, or with reference to a point, area, or volume indicated, for example, on a map, floor plan, or building plan. In the description contained herein, the use of the term "location" can include any of these variations unless otherwise indicated. When calculating the location of the UE, local x, y, and (possibly also) z coordinates are typically solved, and then (if necessary) the local coordinates are converted to absolute coordinates (e.g., with respect to latitude, longitude, and altitude above or below mean sea level).

[0038] UE 105 can be configured to communicate with other entities using one or more of a variety of technologies. UE 105 can be configured to indirectly connect to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. D2D P2P links can use any suitable D2D radio access technology (RAT) such as LTE Direct (LTE-D), WiFi, etc. ® Direct connection (WiFi) ® -D), Bluetooth ®Support is provided. One or more UEs in a UE group utilizing D2D communication may be located within the geographic coverage area of ​​a Transmit / Receive Point (TRP) (such as one or more of gNB 110a, 110b and / or ng-eNB 114). Other UEs in such a group may be outside such geographic coverage area or may be unable to receive transmissions from the base station for other reasons. A UE group communicating via D2D communication may utilize a one-to-many (1:M) system, where each UE can transmit to other UEs in the group. The TRP can facilitate the scheduling of resources for D2D communication. In other cases, D2D communication may be performed between UEs without involving the TRP. One or more UEs in a UE group utilizing D2D communication may be located within the geographic coverage area of ​​a TRP. Other UEs in such a group may be outside such geographic coverage area or may be unable to receive transmissions from the base station for other reasons. A UE group communicating via D2D communication may utilize a one-to-many (1:M) system, where each UE can transmit to other UEs in the group. TRP can facilitate the scheduling of resources used for D2D communication. In other cases, D2D communication can be performed between UEs without involving TRP.

[0039] Figure 1 The base stations (BS) in NG-RAN 135 shown include NR Node Bs (referred to as gNB 110a and gNB 110b). Each pair of gNBs 110a and 110b in NG-RAN 135 can be interconnected via one or more other gNBs. Access to the 5G network is provided to UE 105 via wireless communication with one or more of the gNBs 110a and 110b. These gNBs can use 5G to provide wireless communication access to the 5GC 140 on behalf of UE 105. Figure 1 In this context, it is assumed that the serving gNB of UE 105 is gNB 110a, but another gNB (e.g., gNB 110b) may act as the serving gNB or as a secondary gNB to provide additional throughput and bandwidth to UE 105 if UE 105 moves to another location.

[0040] Figure 1The base station (BS) in NG-RAN 135 shown may include ng-eNB 114, also known as Next Generation Evolved Node B. ng-eNB 114 may be connected to one or more of gNBs 110a and 110b in NG-RAN 135 via one or more other gNBs and / or one or more other ng-eNBs. ng-eNB 114 may provide LTE radio access and / or evolved LTE (eLTE) radio access to UE 105. One or more of gNBs 110a, 110b and / or ng-eNB 114 may be configured to act as a location-only beacon, which may transmit signals to assist in determining the location of UE 105, but may not receive signals from UE 105 or other UEs.

[0041] gNB 110a, 110b, and / or ng-eNB 114 may each include one or more TRPs. For example, each sector within a cell of the BS may include a TRP, but multiple TRPs may share one or more components (e.g., a shared processor but with separate antennas). System 100 may include only macro TRPs, or system 100 may have different types of TRPs, such as macro TRPs, pico TRPs, and / or femto TRPs. Macro TRPs may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by terminals with service subscriptions. Pico TRPs may cover a relatively small geographic area (e.g., a pico cell) and may allow unrestricted access by terminals with service subscriptions. Femto or home TRPs may cover a relatively small geographic area (e.g., a femto cell) and may allow restricted access by terminals associated with that femto cell (e.g., terminals of users in a home).

[0042] Each of the gNBs 110a, 110b, and / or ng-eNB 114 may include a Radio Unit (RU), a Distributed Unit (DU), and a Central Unit (CU). For example, the gNB 110b includes RU 111, DU 112, and CU 113. RU 111, DU 112, and CU 113 define the functionality of the gNB 110b. Although the gNB 110b is shown as having a single RU, a single DU, and a single CU, a gNB may include one or more RUs, one or more DUs, and / or one or more CUs. The interface between CU 113 and DU 112 is referred to as the F1 interface. RU 111 is configured to perform digital front-end (DFE) functions (e.g., analog-to-digital conversion, filtering, power amplification, transmit / receive) and digital beamforming, and includes part of the physical (PHY) layer. RU 111 may perform DFE using massive MIMO and may be integrated with one or more antennas of the gNB 110b. DU 112 hosts the Radio Link Control (RLC), Media Access Control (MAC), and Physical Layer of gNB 110b. A DU can support one or more cells, and each cell is supported by a single DU. The operation of DU 112 is controlled by CU 113. CU 113 is configured to perform functions for delivering user data, mobility control, radio access network sharing, location, session management, etc., although some functions are only assigned to DU 112. CU 113 hosts the Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) of gNB 110b. UE 105 can communicate with CU 113 via the RRC, SDAP, and PDCP layers, with DU 112 via the RLC, MAC, and PHY layers, and with RU 111 via the PHY layer.

[0043] As pointed out, although Figure 1 The diagram depicts nodes configured to communicate according to 5G communication protocols, but nodes configured to communicate according to other communication protocols (such as, for example, LTE or IEEE 802.11x) can also be used. For instance, in an evolved packet system (EPS) providing LTE radio access to UE 105, the RAN may include an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN), which may include base stations containing evolved Node Bs (eNBs). The core network for the EPS may include an evolved packet core (EPC). The EPS may include the E-UTRAN plus the EPC, where the E-UTRAN corresponds to... Figure 1 NG-RAN 135 in the figure and EPC corresponds to 5GC 140 in the figure.

[0044] gNB 110a, 110b, and ng-eNB 114 can communicate with AMF 115; for location functionality, AMF communicates with LMF 120. AMF 115 can support UE 105 mobility (including cell changes and handover) and can participate in supporting signaling connections with UE 105 and (possibly) data and voice bearers for UE 105. LMF 120 can communicate directly with UE 105, for example, wirelessly, or directly with gNB 110a, 110b, and / or ng-eNB 114. LMF 120 can support UE 105 positioning when UE 105 accesses NG-RAN 135, and can support various positioning procedures / methods, such as Auxiliary GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA) (e.g., Downlink (DL) OTDOA or Uplink (UL) OTDOA), Round Trip Time (RTT), Multi-Cell RTT, Real-Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cell ID (E-CID), Angle of Arrival (AoA), Angle of Departure (AoD), and / or other positioning methods. LMF 120 can process, for example, location service requests for UE 105 received from AMF 115 or GMLC 125. LMF 120 can connect to AMF 115 and / or GMLC 125. LMF 120 can be referred to by other names, such as Location Manager (LM), Location Function (LF), Commercial LMF (CLMF), or Value-Added LMF (VLMF). The node / system implementing LMF 120 may additionally or alternatively implement other types of location support modules, such as an Enhanced Serving Mobility Location Center (E-SMLC) or a Secure User Plane Location (SUPL) Location Platform (SLP). At least a portion of the location functionality (including the derivation of the location of UE 105) can be performed at UE 105 (e.g., using signal measurements obtained by UE 105 against signals transmitted by radio nodes (such as gNB 110a, 110b and / or ng-eNB 114), and / or auxiliary data provided to UE 105, for example, by LMF 120). AMF 115 can be used as a control node to process signaling between UE 105 and 5GC 140 and can provide QoS (Quality of Service) streaming and session management. AMF 115 can support the mobility of UE 105 (including cell changes and handover) and can participate in supporting signaling connections with UE 105.

[0045] Server 150 (e.g., a cloud server) is configured to obtain the location estimate of UE 105 and provide it to external client 130. Server 150 may be configured, for example, to run a microservice / service for obtaining the location estimate of UE 105. Server 150 may, for example (e.g., by sending a location request to it), pull the location estimate from one or more of UE 105, gNB 110a, 110b (e.g., via RU 111, DU 112, and CU 113) and / or ng-eNB 114 and / or LMF 120. As another example, one or more of UE 105, gNB 110a, 110b (e.g., via RU 111, DU 112, and CU 113) and / or LMF 120 may push the location estimate of UE 105 to server 150.

[0046] GMLC 125 can support location requests for UE 105 received from external client 130 via server 150, and can forward such location requests to AMF 115 for forwarding to LMF 120, or can forward the location request directly to LMF 120. A location response from LMF 120 (e.g., containing a location estimate for UE 105) can be returned to GMLC 125 directly or via AMF 115, and GMLC 125 can then return the location response (e.g., containing the location estimate) to external client 130 via server 150. GMLC 125 is shown connected to both AMF 115 and LMF 120, but in some specific implementations it may not be connected to either AMF 115 or LMF 120.

[0047] like Figure 1 As a further example, the LMF 120 can use the new radio positioning protocol A (which may be referred to as NPPa or NRPPa) to communicate with gNB 110a, 110b and / or ng-eNB 114, which can be defined in 3GPP Technical Specification (TS) 38.455. NRPPa can be the same as, similar to or an extension of the LTE Positioning Protocol A (LPPa) defined in 3GPP TS 36.455, where NRPPa messages are transmitted via AMF 115 between gNB 110a (or gNB 110b) and LMF 120, and / or between ng-eNB 114 and LMF 120. Figure 1As a further example, LMF 120 and UE 105 can communicate using the LTE Location Protocol (LPP), which is defined in 3GPP TS 36.355. LMF 120 and UE 105 can also communicate using a new radio positioning protocol (which may be referred to as NPP or NRPP), which may be the same as, similar to, or an extension of LPP. Here, LPP and / or NPP messages can be transmitted between UE 105 and LMF 120 via AMF 115 and UE 105's serving gNB 110a, 110b, or serving ng-eNB 114. For example, LPP and / or NPP messages can be transmitted between LMF 120 and AMF 115 using the 5G Location Services Application Protocol (LCS AP), and between AMF 115 and UE 105 using the 5G Non-Access Stratum (NAS) protocol. The LPP and / or NPP protocols can be used to support the location of UE 105 using UE-assisted and / or UE-based positioning methods (such as A-GNSS, RTK, OTDOA, and / or E-CID). The NRPPa protocol can be used to support the location of UE 105 using network-based positioning methods (such as E-CID) (e.g., when used in conjunction with measurements obtained by gNB 110a, 110b, or ng-eNB 114) and / or can be used by LMF 120 to obtain location-related information from gNB 110a, 110b, and / or ng-eNB 114, such as defining parameters sent by directional SS or PRS from gNB 110a, 110b, and / or ng-eNB 114. LMF 120 can be co-located or integrated with gNB or TRP, or can be configured to be located away from gNB and / or TRP and communicate directly or indirectly with gNB and / or TRP.

[0048] Using a UE-assisted positioning method, UE 105 can obtain location measurements and transmit these measurements to a location server (e.g., LMF 120) for calculating a location estimate for UE 105. For example, location measurements may include one or more of the following: Received Signal Strength Indication (RSSI), Round-Trip Time (RTT), Reference Signal Time Difference (RSTD), Reference Signal Received Power (RSRP), and / or Reference Signal Received Quality (RSRQ) for gNB 110a, 110b, ng-eNB 114, and / or WLAN AP. Location measurements may additionally or alternatively include measurements of GNSS pseudorange, code phase, and / or carrier phase for SV 190-193.

[0049] Using a UE-based positioning method, UE 105 can obtain a location measurement (e.g., which may be the same as or similar to the location measurement of a UE-assisted positioning method) and can calculate the location of UE 105 (e.g., by means of auxiliary data received from a location server (such as LMF 120) or broadcast by gNB 110a, 110b, ng-eNB 114 or other base stations or APs).

[0050] Using a network-based positioning method, one or more base stations (e.g., gNB 110a, 110b and / or ng-eNB 114) or APs can obtain location measurements (e.g., measurements of RSSI, RTT, RSRP, RSRQ, or time information such as Time of Arrival (ToA) for signals transmitted by UE 105) and / or can receive measurements obtained by UE 105. One or more base stations or APs can transmit the measurements to a location server (e.g., LMF 120) for calculating a location estimate for UE 105.

[0051] The information provided to the LMF 120 by the gNB 110a, 110b and / or ng-eNB 114 using NRPPa may include timing and configuration information for directing SS or PRS transmissions, as well as location coordinates. The LMF 120 may provide some or all of this information as supplementary data to the UE 105 in LPP and / or NPP messages via NG-RAN 135 and 5GC140.

[0052] The LPP or NPP message transmitted from LMF 120 to UE 105 can command UE 105 to perform any of a variety of tasks depending on the desired functionality. For example, the LPP or NPP message may contain instructions for UE 105 to obtain measurements of GNSS (or A-GNSS), WLAN, E-CID, and / or OTDOA (or some other positioning method). In the case of E-CID, the LPP or NPP message may command UE 105 to obtain measurements supported by one or more of gNB 110a, 110b, and / or ng-eNB 114 (or by some other type of base station such as eNB or WiFi). ® One or more measurement parameters (e.g., beam ID, beamwidth, average angle, RSRP, RSRQ measurements) of directional signals transmitted within a specific cell supported by the AP. UE 105 can transmit these measurement parameters back to LMF 120 via serving gNB110a (or serving ng-eNB 114) and AMF 115 in an LPP or NPP message (e.g., within a 5G NAS message).

[0053] As noted, while a communication system 100 is described in relation to 5G technology, the communication system 100 can be implemented to support other communication technologies (such as GSM, WCDMA, LTE, etc.) for supporting and interacting with mobile devices (such as UE 105) (e.g., to provide voice, data, location, and other functionalities). In some such specific implementations, the 5GC 140 can be configured to control different air interfaces. For example, the 5GC 140 can use non-3GPP interoperability functions (N3IWF) within the 5GC 140. Figure 1 (Not shown) Connected to a WLAN. For example, the WLAN may support IEEE 802.11 WiFi for UE 105. ® Access, and may include one or more WiFi networks. ® AP. Here, the N3IWF can connect to the WLAN and other components in 5GC 140, such as AMF 115. In some examples, both NG-RAN 135 and 5GC 140 can be replaced by one or more other RANs and one or more other core networks. For example, in EPS, NG-RAN 135 can be replaced by E-UTRAN containing eNBs, and 5GC 140 can be replaced by EPC containing a Mobility Management Entity (MME) instead of AMF 115, an E-SMLC instead of LMF 120, and a GMLC that can be similar to GMLC 125. In such EPS, the E-SMLC can use LPPa instead of NRPPa to transmit location information to and receive location information from eNBs in the E-UTRAN, and can use LPP to support UE 105's positioning. In these other examples, the location of UE 105 using directional PRS can be supported in a manner similar to that described herein for 5G networks. The difference is that the functions and procedures described herein for gNB 110a, 110b, ng-eNB114, AMF 115, and LMF 120 can, in some cases, be alternatively applied to other network elements, such as eNBs and WiFi. ® AP, MME, and E-SMLC.

[0054] As noted, in some examples, positioning functionality can be achieved at least in part using directional SS or PRS beams transmitted by base stations (such as gNB 110a, 110b and / or ng-eNB 114) at the location of the UE (e.g., whose location is to be determined). Figure 1 Within the range of UE 105. In some instances, the UE can use directional SS or PRS beams from multiple base stations (such as gNB 110a, 110b, ng-eNB 114, etc.) to calculate the UE's location.

[0055] Also refer to Figure 2UE 200 may be an example of one of UEs 105 and 106, and may include a computing platform including processor 210, memory 211 including software (SW) 212, one or more sensors 213, transceiver interface 214 for transceiver 215 (which includes wireless transceiver 240 and wired transceiver 250), user interface 216, satellite positioning system (SPS) receiver 217, camera 218, and positioning device (PD) 219. Processor 210, memory 211, sensor 213, transceiver interface 214, user interface 216, SPS receiver 217, camera 218, and positioning device 219 may be communicatively coupled to each other via bus 220 (which may be configured for, for example, optical communication and / or electrical communication). One or more of the devices shown (e.g., camera 218, positioning device 219, and / or one or more sensors in sensor 213, etc.) may be omitted from UE 200. Processor 210 may include one or more hardware devices, such as a central processing unit (CPU), microcontroller, application-specific integrated circuit (ASIC), etc. Processor 210 may include multiple processors, including a general-purpose / application processor 230, a digital signal processor (DSP) 231, a modem processor 232, a video processor 233, and / or a sensor processor 234. One or more of processors 230 to 234 may include multiple devices (e.g., multiple processors). For example, sensor processor 234 may include processors for, for example, RF (radio frequency) sensing (where one or more transmitted (cellular) wireless signals and reflections are used to identify, map, and / or track objects) and / or ultrasound, etc. Modem processor 232 may support dual SIM / dual connectivity (or even more SIMs). For example, a SIM (subscriber identity module or subscriber identification module) may be used by an original equipment manufacturer (OEM), and another SIM may be used by the end user of UE 200 to obtain connectivity. Memory 211 may be a non-transitory storage medium that may include random access memory (RAM), flash memory, disk memory, and / or read-only memory (ROM), etc. Memory 211 may store software 212, which may be processor-readable, processor-executable software code containing instructions that, when executed, cause processor 210 to perform the various functions described herein. Alternatively, software 212 may not be directly executable by processor 210, but may be configured, for example, to cause processor 210 to perform these functions when compiled and executed. The description herein may refer to processor 210 performing functions, but this includes other specific implementations, such as specific implementations of processor 210 performing software and / or firmware. The description herein may refer to the execution of functions by processor 210 as a shortened form of processor-performed functions by one or more of processors 230-234.The description herein may refer to the performance of UE 200 as a shortened form of the performance of one or more appropriate components of UE 200. Processor 210 may include memory with stored instructions as a supplement to and / or replacement of memory 211. The functionality of processor 210 is discussed more fully below.

[0056] Figure 2 The configuration of UE 200 shown is exemplary and not intended to limit this disclosure (including the claims), and other configurations may be used. For example, an exemplary configuration of the UE may include one or more of processors 230 to 234 in processor 210, memory 211, and wireless transceiver 240. Other exemplary configurations may include one or more of processors 230 to 234 in processor 210, memory 211, wireless transceiver, and one or more of the following devices: sensor 213, user interface 216, SPS receiver 217, camera 218, PD 219, and / or wired transceiver.

[0057] UE 200 may include a modem processor 232 capable of performing baseband processing on signals received and downconverted by transceiver 215 and / or SPS receiver 217. Modem processor 232 may also perform baseband processing on signals to be upconverted for transmission by transceiver 215. Alternatively, baseband processing may be performed by general-purpose / application processor 230 and / or DSP 231. However, other configurations may be used to perform baseband processing.

[0058] UE 200 may include sensor 213, which may include, for example, an inertial measurement unit (IMU) 270, one or more magnetometers 271, and / or one or more environmental sensors 272. IMU 270 may include, for example, one or more accelerometers 273 (e.g., collectively responding to acceleration of UE 200 in three dimensions) and / or one or more gyroscopes 274 (e.g., three-dimensional gyroscopes). Sensor 213 may include one or more magnetometers 271 (e.g., three-dimensional magnetometers) to determine (e.g., relative to magnetic north and / or true north) an orientation that can be used for any of a variety of purposes, such as supporting one or more compass applications. Environmental sensors 272 may include, for example, one or more temperature sensors, one or more barometric pressure sensors, one or more ambient light sensors, one or more camera imagers, and / or one or more microphones, etc. Sensor 213 may generate analog and / or digital signals, indications of which may be stored in memory 211 and processed by DSP 231 and / or general-purpose / application processor 230 to support one or more applications, such as applications involving positioning and / or navigation operations. Sensor 213 may include one or more of other various types of sensors, such as one or more optical sensors, one or more weight sensors and / or one or more radio frequency (RF) sensors.

[0059] Sensor 213 can be used for relative position measurement, relative position determination, motion determination, etc. Information detected by sensor 213 can be used for motion detection, relative displacement, dead reckoning, sensor-based position determination, and / or sensor-assisted position determination. Sensor 213 can be used to determine whether UE 200 is stationary or moving and / or whether certain useful information related to the mobility of UE 200 needs to be reported to LMF 120. For example, based on information obtained / measured by sensor 213, UE 200 can notify / report to LMF 120 that UE 200 has detected movement or that UE 200 has moved, and report relative displacement / distance (e.g., via dead reckoning implemented by sensor 213, or sensor-based position determination, or sensor-assisted position determination). In another example, for relative positioning information, the sensor / IMU can be used to determine the angle and / or orientation of another device relative to UE 200, etc.

[0060] IMU 270 can be configured to provide measurements of the direction and / or velocity of motion of UE 200, which can be used for relative position determination. For example, one or more accelerometers 273 and / or one or more gyroscopes 274 of IMU 270 can detect the linear acceleration and rotational velocity of UE 200, respectively. The linear acceleration and rotational velocity measurements of UE 200 can be integrated over time to determine the instantaneous direction of motion and displacement of UE 200. The instantaneous direction of motion and displacement can be integrated to track the position of UE 200. For example, a reference position of UE 200 at a given moment can be determined, for example, using SPS receiver 217 (and / or by some other means), and measurements acquired from accelerometers 273 and gyroscopes 274 after that moment can be used for dead reckoning to determine the current position of UE 200 based on the movement (direction and distance) of UE 200 relative to that reference position.

[0061] Magnetometer 271 can determine the strength of magnetic fields in different directions, which can be used to determine the orientation of UE 200. For example, this orientation can be used to provide a digital compass for UE 200. The magnetometer may include a two-dimensional magnetometer configured to detect and provide an indication of magnetic field strength in two orthogonal dimensions. Magnetometer 271 may also include a three-dimensional magnetometer configured to detect and provide an indication of magnetic field strength in three orthogonal dimensions. Magnetometer 271 can provide components for sensing magnetic fields and, for example, providing an indication of the magnetic field to processor 210.

[0062] Transceiver 215 may include a wireless transceiver 240 and a wired transceiver 250 configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 240 may include a wireless transmitter 242 and a wireless receiver 244 coupled to antenna 246 for transmitting (e.g., on one or more uplink channels and / or one or more sidelink channels) and / or receiving (e.g., on one or more downlink channels and / or one or more sidelink channels) wireless signals 248 and converting signals from wireless signals 248 to wired (e.g., electrical and / or optical) signals and from wired (e.g., electrical and / or optical) signals to wireless signals 248. Wireless transmitter 242 includes suitable components (e.g., power amplifiers and digital-to-analog converters). Wireless receiver 244 includes suitable components (e.g., one or more amplifiers, one or more frequency filters, and analog-to-digital converters). Wireless transmitter 242 may include multiple transmitters that may be discrete components or combined / integrated components, and / or wireless receiver 244 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 240 can be configured to transmit signals according to various radio access technologies (RATs) (e.g., with TRP and / or one or more other devices), such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Telephone Systems), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), and WiFi. ® WiFi ® Direct connection (WiFi) ® -D), Bluetooth ® Zigbee ®The new radio can use millimeter wave frequencies and / or frequencies below 6 GHz. Wired transceiver 250 may include a wired transmitter 252 and a wired receiver 254 configured for wired communication, for example, a network interface used to communicate with and receive communications from NG-RAN 135. Wired transmitter 252 may include multiple transmitters that may be discrete components or combined / integrated components, and / or wired receiver 254 may include multiple receivers that may be discrete components or combined / integrated components. Wired transceiver 250 may be configured, for example, for optical and / or electrical communication. Transceiver 215 may be communicatively coupled to transceiver interface 214, for example, via optical and / or electrical connections. Transceiver interface 214 may be at least partially integrated with transceiver 215. The wireless transmitter 242, the wireless receiver 244, and / or the antenna 246 may each include multiple transmitters, multiple receivers, and / or multiple antennas for transmitting and / or receiving appropriate signals, respectively.

[0063] User interface 216 may include one or more of a number of devices, such as speakers, microphones, display devices, vibration devices, keyboards, touchscreens, etc. User interface 216 may include more than one of these devices. User interface 216 may be configured to enable a user to interact with one or more applications hosted by UE 200. For example, user interface 216 may store indications of analog and / or digital signals in memory 211 in response to actions from the user, for processing by DSP 231 and / or general-purpose / application processor 230. Similarly, applications hosted on UE 200 may store indications of analog and / or digital signals in memory 211 to present output signals to the user. User interface 216 may include audio input / output (I / O) devices, including, for example, speakers, microphones, digital-to-analog circuitry, analog-to-digital circuitry, amplifiers, and / or gain control circuitry (including more than one of these devices). Other configurations of the audio I / O devices may be used. Additionally or alternatively, the user interface 216 may include one or more touch sensors that respond to touch and / or pressure on, for example, the keyboard and / or touchscreen of the user interface 216.

[0064] SPS receiver 217 (e.g., a Global Positioning System (GPS) receiver) may be able to receive and acquire SPS signal 260 via SPS antenna 262. SPS antenna 262 is configured to convert SPS signal 260 from a wireless signal to a wired signal (e.g., an electrical or optical signal) and may be integrated with antenna 246. SPS receiver 217 may be configured to process the acquired SPS signal 260 fully or partially to estimate the location of UE 200. For example, SPS receiver 217 may be configured to determine the location of UE 200 by performing trilateration using SPS signal 260. The acquired SPS signal may be processed fully or partially using general-purpose / application processor 230, memory 211, DSP 231, and / or one or more dedicated processors (not shown), and / or the estimated location of UE 200 may be calculated. Memory 211 may store indications (e.g., measurements) of SPS signal 260 and / or other signals (e.g., signals acquired from wireless transceiver 240) for use in performing positioning operations. General-purpose / application processor 230, DSP 231, and / or one or more dedicated processors, and / or memory 211 may provide or support a location engine for processing measurements to estimate the location of UE 200.

[0065] UE 200 may include a camera 218 for capturing still or moving images. Camera 218 may include, for example, an imaging sensor (e.g., a charge-coupled device or CMOS (complementary metal-oxide-semiconductor) imager), lenses, analog-to-digital circuitry, frame buffers, etc. Additional processing, conditioning, encoding, and / or compression of signals representing the captured images may be performed by a general-purpose / application processor 230 and / or a DSP 231. Additionally or alternatively, a video processor 233 may perform conditioning, encoding, compression, and / or manipulation of signals representing the captured images. The video processor 233 may decode / decompress stored image data for presentation on a display device (not shown), for example, the user interface 216.

[0066] Location device (PD) 219 may be configured to determine the location of UE 200, the movement of UE 200, and / or the relative location of UE 200, and / or time. For example, PD 219 may communicate with SPS receiver 217 and / or include part or all of the SPS receiver. PD 219 may, where appropriate, work in conjunction with processor 210 and memory 211 to perform at least a portion of one or more location methods, although the description herein may refer to PD 219 being configured to perform according to a location method or the PD performing according to a location method. PD 219 may additionally or alternatively be configured to: perform trilateration using terrestrial signals (e.g., at least some radio signals 248), assist in acquisition, and use SPS signal 260, or both, to determine the location of UE 200. PD 219 may be configured to determine the location of UE 200 based on the cell of the serving base station (e.g., cell center) and / or another technology (such as E-CID). PD 219 can be configured to determine the location of UE 200 using one or more images from camera 218 and image recognition combined with the known location of landmarks (e.g., natural landmarks such as mountains and / or man-made landmarks such as buildings, bridges, streets, etc.). PD 219 can be configured to determine the location of UE 200 using one or more other technologies (e.g., relying on the UE's self-reported location (e.g., part of the UE's positioning beacon)), and can use a combination of these technologies (e.g., SPS and terrestrial positioning signals) to determine the location of UE 200. PD 219 may include one or more sensors 213 (e.g., gyroscopes, accelerometers, magnetometers, etc.) that can sense the orientation and / or motion of UE 200 and provide an indication of such orientation and / or motion. Processor 210 (e.g., general-purpose / application processor 230 and / or DSP 231) can be configured to use this indication to determine the motion of UE 200 (e.g., velocity vector and / or acceleration vector). PD 219 can be configured to provide an indication of uncertainty and / or error in the determined positioning and / or motion. The functionality of PD 219 can be provided in a variety of ways and / or configurations, such as by a general-purpose / application processor 230, transceiver 215, SPS receiver 217 and / or another component of UE 200, and can be provided by hardware, software, firmware or various combinations thereof.

[0067] Also refer to Figure 3Examples of TRP 300 for gNB 110a, 110b and / or ng-eNB 114 may include a computing platform containing processor 310, memory 311 containing software (SW) 312, and transceiver 315. Processor 310, memory 311 and transceiver 315 may be communicatively coupled to each other via bus 320 (which may be configured for, for example, optical communication and / or electrical communication). One or more of the devices shown may be omitted from the TRP 300. Processor 310 may include one or more hardware devices, such as a central processing unit (CPU), microcontroller, application-specific integrated circuit (ASIC), etc. Processor 310 may include multiple processors (e.g., including general-purpose / application processors, DSPs, modem processors, video processors and / or sensor processors, such as...). Figure 2 (As shown). Memory 311 may be a non-transitory storage medium including random access memory (RAM), flash memory, disk storage, and / or read-only memory (ROM). Memory 311 may store software 312, which may be processor-readable, processor-executable software code containing instructions configured to cause processor 310 to perform the various functions described herein when executed. Alternatively, software 312 may not be directly executable by processor 310, but may be configured to cause processor 310 to perform these functions, for example, when compiled and executed.

[0068] The description herein may refer to the functions performed by processor 310, but this includes other specific implementations, such as specific implementations of processor 310 performing software and / or firmware. The description herein may refer to the functions performed by processor 310 as a shorthand for the functions performed by one or more processors contained within processor 310. The description herein may refer to the functions performed by TRP 300 as a shorthand for the functions performed by one or more appropriate components of TRP 300 (and therefore one of gNB 110a, 110b and / or ng-eNB 114), such as processor 310 and memory 311. Processor 310 may include memory with stored instructions as a complement and / or replacement for memory 311. The functionality of processor 310 is discussed more fully below.

[0069] Transceiver 315 may include a wireless transceiver 340 and / or a wired transceiver 350 configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 340 may include a wireless transmitter 342 and a wireless receiver 344 coupled to one or more antennas 346 for transmitting (e.g., on one or more uplink channels and / or one or more downlink channels) and / or receiving (e.g., on one or more downlink channels and / or one or more uplink channels) wireless signals 348 and converting signals from wireless signals 348 to wired (e.g., electrical and / or optical) signals and from wired (e.g., electrical and / or optical) signals to wireless signals 348. Therefore, wireless transmitter 342 may include multiple transmitters that may be discrete components or combined / integrated components, and / or wireless receiver 344 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 340 can be configured to transmit signals according to various radio access technologies (RATs) (e.g., with UE 200, one or more other UEs, and / or one or more other devices), such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Telephone Systems), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), and WiFi. ® WiFi ® Direct connection (WiFi) ® -D), Bluetooth ® Zigbee ® The wired transceiver 350 may include a wired transmitter 352 and a wired receiver 354 configured for wired communication, for example, a network interface that can be used to communicate with NG-RAN 135 to transmit and receive communication to, for example, LMF 120 and / or one or more other network entities. The wired transmitter 352 may include multiple transmitters that may be discrete components or combined / integrated components, and / or the wired receiver 354 may include multiple receivers that may be discrete components or combined / integrated components. The wired transceiver 350 may be configured, for example, for optical communication and / or electrical communication.

[0070] Figure 3The configuration of TRP 300 shown is illustrative and not intended to limit this disclosure (including the claims), and other configurations may be used. For example, the description herein discusses that TRP 300 may be configured to perform several functions or that the TRP performs several functions, but one or more of these functions may be performed by LMF 120 and / or UE 200 (i.e., LMF 120 and / or UE 200 may be configured to perform one or more of these functions).

[0071] Also refer to Figure 4 Server 400 (LMF 120 may be an example thereof) may include: a computing platform including processor 410, a memory 411 including software (SW) 412, and a transceiver 415. Processor 410, memory 411, and transceiver 415 may be communicatively coupled to each other via bus 420 (which may be configured for, for example, optical communication and / or electrical communication). One or more devices in the illustrated apparatus (e.g., a wireless transceiver) may be omitted from server 400. Processor 410 may include one or more hardware devices, such as a central processing unit (CPU), microcontroller, application-specific integrated circuit (ASIC), etc. Processor 410 may include multiple processors (e.g., including general-purpose / application processors, DSPs, modem processors, video processors, and / or sensor processors, such as… Figure 2 (As shown). Memory 411 may be a non-transitory storage medium including random access memory (RAM), flash memory, disk storage, and / or read-only memory (ROM). Memory 411 may store software 412, which may be processor-readable, processor-executable software code containing instructions configured to cause processor 410 to perform the various functions described herein when executed. Alternatively, software 412 may not be directly executable by processor 410, but may be configured to cause processor 410 to perform these functions, for example, when compiled and executed. The description herein may refer to processor 410 performing functions, but this includes other specific implementations, such as specific implementations of processor 410 performing software and / or firmware. The description herein may refer to the function performed by processor 410 as an abbreviation for one or more processors included in processor 410 performing functions. The description herein may refer to the function performed by server 400 as an abbreviation for one or more suitable components of server 400 performing functions. In addition to and / or instead of memory 411, processor 410 may include memory with stored instructions. The functionality of the processor 410 will be discussed more comprehensively below.

[0072] Transceiver 415 may include a wireless transceiver 440 and / or a wired transceiver 450 configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 440 may include a wireless transmitter 442 and a wireless receiver 444 coupled to one or more antennas 446 for transmitting (e.g., on one or more downlink channels) and / or receiving (e.g., on one or more uplink channels) wireless signals 448 and converting signals from wireless signals 448 to wired (e.g., electrical and / or optical) signals and from wired (e.g., electrical and / or optical) signals to wireless signals 448. Therefore, wireless transmitter 442 may include multiple transmitters that may be discrete components or combined / integrated components, and / or wireless receiver 444 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 440 can be configured to transmit signals according to various radio access technologies (RATs) (e.g., with UE 200, one or more other UEs, and / or one or more other devices), such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Telephone Systems), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), and WiFi. ® WiFi ® Direct connection (WiFi) ® -D), Bluetooth ® Zigbee ® The wired transceiver 450 may include a wired transmitter 452 and a wired receiver 454 configured for wired communication, for example, a network interface that can be used to communicate with NG-RAN 135 to transmit and receive communication to, for example, TRP 300 and / or one or more other network entities. The wired transmitter 452 may include multiple transmitters that may be discrete components or combined / integrated components, and / or the wired receiver 454 may include multiple receivers that may be discrete components or combined / integrated components. The wired transceiver 450 may be configured, for example, for optical communication and / or electrical communication.

[0073] The description herein may refer to the processor 410 performing functions, but this includes other specific implementations, such as specific implementations of software and / or firmware (stored in memory 411) performed by the processor 410. The description herein may refer to the server 400 performing functions as an abbreviation for one or more appropriate components of the server 400 (e.g., processor 410 and memory 411) performing functions.

[0074] Figure 4The configuration of server 400 shown is exemplary and not intended to limit this disclosure (including the claims), and other configurations may be used. For example, wireless transceiver 440 may be omitted. Furthermore or alternatively, the description herein discusses server 400 being configured to perform certain functions or the server performing certain functions, but one or more of these functions may be performed by TRP 300 and / or UE 200 (i.e., TRP 300 and / or UE 200 may be configured to perform one or more of these functions).

[0075] For terrestrial positioning of UEs in cellular networks, techniques such as Advanced Forward Link Trilateral Measurement (AFLT) and Observed Time Difference of Arrival (OTDOA) typically operate in a “UE-assisted” mode, where measurements of reference signals (e.g., PRS, CRS, etc.) transmitted by the base station are acquired by the UE and subsequently provided to a location server. The location server calculates the UE’s location based on this measurement and the known location of the base station. Because these techniques use a location server (rather than the UE itself) to calculate the UE’s location, they are not frequently used in applications such as car or cellular phone navigation, which typically rely on satellite-based positioning instead.

[0076] UEs can use Satellite Positioning System (SPS) (Global Navigation Satellite System (GNSS)) to achieve high-accuracy positioning using Precise Point Positioning (PPP) or Real-Time Kinematics (RTK) techniques. These techniques use auxiliary data, such as measurements from ground-based stations. LTE Release 15 allows data to be encrypted so that only UEs subscribed to the service can read it. This auxiliary data changes over time. Therefore, a UE with a subscribed service may not be able to easily "crack" the encryption for other UEs by passing the data to them without paying for the subscription. This transmission needs to be repeated every time the auxiliary data changes.

[0077] In UE-assisted positioning, the UE transmits measurements (e.g., TDOA, Angle of Arrival (AoA), etc.) to a positioning server (e.g., LMF / eSMLC). The positioning server has a Base Station Almanac (BSA), which contains multiple "entries" or "records," one record per cell, where each record contains the geographic cell location, but may also include other data. Identifiers of the "records" among the multiple "records" in the BSA can be referenced. The BSA and measurements from the UE can be used to calculate the UE's positioning.

[0078] In conventional UE-based positioning, the UE calculates its own location, thus avoiding transmitting measurements to the network (e.g., a location server), which improves latency and scalability. The UE uses relevant BSA record information from the network (e.g., the location of the gNB (more broadly, the base station)). BSA information can be encrypted. However, since BSA information changes much less frequently than, for example, PPP or RTK auxiliary data described above, it may be easier to make BSA information available to UEs that have not subscribed and have not paid for decryption keys (compared to PPP or RTK information). The transmission of reference signals by the gNB makes BSA information potentially accessible to crowdsourcing or driving attacks, thus essentially enabling BSA information to be generated based on in-the-field and / or over-the-top observations.

[0079] Positioning technologies can be characterized and / or evaluated based on one or more criteria, such as positioning accuracy and / or latency. Latency is the time elapsed between the event that triggers the determination of positioning-related data and the availability of that data at the positioning system interface (e.g., the interface of an LMF 120). The latency for the availability of positioning-related data at the time of positioning system initialization is called the First Fix (TTFF), and is greater than the latency after the TTFF. The reciprocal of the time elapsed between two consecutive availability periods of positioning-related data is called the update rate, i.e., the rate at which positioning-related data is generated after the TTFF. Latency can depend on (e.g., the UE's) processing capacity. For example, assuming an allocation of 272 PRBs (Physical Resource Blocks), the UE can report its processing capacity as the duration (in time units, e.g., milliseconds) of DL PRS symbols that it can process per T time units (e.g., Tms). Other examples of capabilities that may affect latency include the number of TRPs from which the UE can process PRS, the number of PRSs the UE can process, and the UE's bandwidth.

[0080] One or more of many different positioning techniques (also known as positioning methods) can be used to determine the location of an entity (such as one of UE105, 106). Known positioning techniques include RTT, multiple RTT, OTDOA (also known as TDOA and including UL-TDOA and DL-TDOA), Enhanced Cell Identification (E-CID), DL-AoD, UL-AoA, etc. RTT uses the time it takes for a signal to travel from one entity to another and back to determine the range between the two entities. The range, plus the known location of the first entity and the angle between the two entities (e.g., azimuth), can be used to determine the location of the second entity. In multiple RTT (also known as multi-cell RTT), multiple ranges from one entity (e.g., UE) to other entities (e.g., TRP) and the known locations of other entities can be used to determine the location of that one entity. In TDOA, the time difference of travel between an entity and other entities can be used to determine the relative range with respect to other entities, and this relative range, combined with the known locations of other entities, can be used to determine the location of that one entity. Angle of arrival and / or angle of departure can be used to help determine the location of an entity. For example, the angle of arrival or departure of a signal, combined with the range between devices (distances determined using signals (e.g., signal travel time, signal received power, etc.)) and the known location of one of these devices, can be used to determine the location of another device. The angle of arrival or departure can be an azimuth angle relative to a reference direction (such as true north). The angle of arrival or departure can also be a zenith angle relative to directly upwards from the entity (i.e., radially outwards from the Earth's center). E-CID uses the identity of the serving cell, timing advance (i.e., the difference between the reception time and transmission time at the UE), estimated timing and power of detected neighboring cell signals, and possible angles of arrival (e.g., the angle of arrival of signals from the base station at the UE, or vice versa) to determine the location of the UE. In TDOA, the time difference of arrival of signals from different sources at the receiving device, along with the known locations of these sources and the known offsets of the transmission times from these sources, are used to determine the location of the receiving device.

[0081] In network-centric RTT estimation, the serving base station instructs the UE to scan / receive RTT measurement signals (e.g., PRS) on the serving cells of two or more neighboring base stations (and typically the serving base station, as at least three base stations are required). These one or more base stations transmit the RTT measurement signals on low-reuse resources (e.g., resources used by the base station to transmit system information) allocated by the network (e.g., a location server, such as an LMF 120). The UE records the arrival time (also referred to as time information, reception time, received time, or time of arrival (ToA)) of each RTT measurement signal relative to the UE's current downlink timing (e.g., as derived by the UE from DL signals received from its serving base station), and (e.g., when instructed by its serving base station) transmits a shared or individual RTT response message (e.g., an SRS (Sound Reference Signal) for positioning, i.e., UL-PRS) to these one or more base stations, and may transmit the time difference between the ToA of the RTT measurement signal and the transmission time of the RTT response message. (i.e., UE T) Rx-Tx or UE Rx-Tx The RTT response time is included in the payload of each RTT response message. The RTT response message will include a reference signal from which the base station can infer the ToA of the RTT response. This is achieved by comparing the transmission time of the RTT measurement signal from the base station with the ToA of the RTT response at the base station. Time difference with UE report Compare and subtract UE Rx-Tx The base station can infer the propagation time between the base station and the UE. Based on this propagation time, the base station can determine the distance between the UE and the base station by assuming the speed of light during this propagation time.

[0082] UE-centric RTT estimation is similar to network-based methods, except that the UE sends an uplink RTT measurement signal (e.g., when commanded by a serving base station), which is received by multiple base stations near the UE. Each base station involved responds with a downlink RTT response message, which may include in its payload the time difference between the ToA of the RTT measurement signal at the base station and the time of transmission of the RTT response message from the base station.

[0083] For both network-centric and UE-centric procedures, the side performing RTT calculation (network or UE) typically (but not always) sends a first message or signal (e.g., an RTT measurement signal), while the other side responds with one or more RTT response messages or signals, which may include the difference between the ToA of the first message or signal and the transmission time of the RTT response message or signal.

[0084] Multiple RTT (Multiple Real-Time Toll) technology can be used to determine location. For example, a first entity (e.g., a UE) may transmit one or more signals (e.g., unicast, multicast, or broadcast from a base station), and multiple second entities (e.g., other TSPs, such as a base station and / or the UE) may receive signals from the first entity and respond to those received signals. The first entity receives responses from the multiple second entities. The first entity (or another entity, such as an LMF) may use the responses from the second entities to determine the range to the second entities, and the location of the first entity may be determined by trilateration using the multiple ranges and the known locations of the second entities.

[0085] In some instances, additional information in the form of angle of arrival (AoA) or angle of departure (AoD) can be obtained, which defines a straight-line direction (e.g., this direction can be in a horizontal plane or in three dimensions) or a possible (e.g., the UE's direction as seen from the base station's location) range of directions. The intersection of the two directions can provide another estimate of the UE's location.

[0086] For positioning techniques that use PRS (Location Reference Signal) signals (e.g., TDOA and RTT), the PRS signals transmitted by multiple TRPs are measured, and the arrival time, known transmission time, and known location of the TRPs are used to determine the range from the UE to the TRPs. For example, RSTD (Reference Signal Time Difference) can be determined for PRS signals received from multiple TRPs, and this RSTD is used in TDOA techniques to determine the UE's location. The Location Reference Signal may be referred to as the PRS or PRS signal. PRS signals are typically transmitted using the same power, and PRS signals with the same signal characteristics (e.g., the same frequency shift) may interfere with each other, causing a PRS signal from a more distant TRP to be overwhelmed by a PRS signal from a closer TRP, making the signal from the more distant TRP undetectable. PRS silencing can be used to help reduce interference by silencing some PRS signals (reducing the power of the PRS signal, e.g., reducing it to zero and thus not transmitting the PRS signal). In this way, the UE can more easily detect the weaker PRS signal (at the UE) without the interference of the stronger PRS signal. The term RS and its variations (e.g., PRS, SRS, CSI-RS (Channel State Information - Reference Signal)) can refer to one or more reference signals.

[0087] The Positioning Reference Signal (PRS) comprises a downlink PRS (DL PRS, often simply referred to as PRS) and an uplink PRS (UL PRS) (the uplink PRS may be referred to as the SRS (Sound Reference Signal) used for positioning). The PRS may include PN codes (pseudo-random codes) or be generated using PN codes (e.g., by modulating a carrier signal with PN codes) to make the PRS source usable as a pseudo-satellite. The PN code may be unique for the PRS source (at least unique within a specified region, such that the same PRS from different PRS sources does not overlap). The PRS may include PRS resources and / or PRS resource sets of a frequency layer. The DL PRS positioning frequency layer (or simply frequency layer) is a collection of DL PRS resource sets from one or more TRPs, where the PRS resources have common parameters configured by the higher-layer parameters DL-PRS-PositioningFrequencyLayer, DL-PRS-ResourceSet, and DL-PRS-Resource. Each frequency layer has a DL PRS subcarrier spacing (SCS) for the DL PRS resource set and DL PRS resources within that frequency layer. Each frequency layer has a DL PRS resource set and a DL PRS cyclic prefix (CP) for the DL PRS resources within that frequency layer. In 5G, a resource block occupies 12 consecutive subcarriers and a specified number of symbols. A shared resource block is a set of resource blocks that occupy the channel bandwidth. A bandwidth portion (BWP) is a set of consecutive shared resource blocks and may include all shared resource blocks within the channel bandwidth or a subset of those shared resource blocks. Furthermore, the DL PRS point A parameter defines the frequency of a reference resource block (and its lowest subcarrier), where DL PRS resources belonging to the same DL PRS resource set have the same point A, and all DL PRS resource sets belonging to the same frequency layer have the same point A. The frequency layers also have the same DL PRS bandwidth, the same starting PRB (and center frequency), and the same comb size value (i.e., the frequency of the PRS resource element per symbol, such that for comb-N, every Nth resource element is a PRS resource element). A PRS resource set is identified by a PRS resource set ID and can be associated with a specific TRP (identified by the cell ID) transmitted by the base station's antenna panel. A PRS resource ID in a PRS resource set can be associated with an omnidirectional signal and / or with a single beam (and / or beam ID) transmitted from a single base station (where a base station can transmit one or more beams). Each PRS resource in a PRS resource set can be transmitted on a different beam, and thus, a PRS resource (or simply a resource) can also be referred to as a beam. There is no implication as to whether the base station and beam transmitting the PRS on it are known to the UE.

[0088] The TRP can be configured, for example, by instructions received from a server and / or by software within the TRP, to transmit DL PRS according to a schedule. Depending on this schedule, the TRP can transmit DL PRS intermittently (e.g., periodically at consistent intervals from the initial transmission). The TRP can be configured to transmit one or more PRS resource sets. A resource set is a collection of PRS resources spanning a TRP, wherein the resources have the same periodicity, a shared silent mode configuration (if any), and the same cross-slot repetition factor. Each PRS resource set comprises multiple PRS resources, wherein each PRS resource comprises multiple OFDM (Orthogonal Frequency Division Multiplexing) resource elements (REs), which may reside in multiple resource blocks (RBs) within N (or more) consecutive symbols in a time slot. PRS resources (or, in general, reference signal (RS) resources) may be referred to as OFDM PRS resources (or OFDMRS resources). An RB is a set of REs spanning a certain number of one or more consecutive symbols in the time domain and a certain number (12 for 5G RBs) of consecutive subcarriers in the frequency domain. Each PRS resource is configured using RE offset, slot offset, and symbol offset within a slot, as well as the number of consecutive symbols that a PRS resource can occupy within a slot. The RE offset defines the initial RE offset of the first symbol within a DL PRS resource in the frequency. The relative RE offsets of the remaining symbols within a DL PRS resource are defined based on the initial offset. The slot offset is the starting slot of the DL PRS resource relative to the corresponding resource set slot offset. The symbol offset determines the starting symbol of the DL PRS resource within the starting slot. Transmitted REs can be repeated across slots, with each transmission referred to as a repetition, allowing for multiple repetitions within a PRS resource. DL PRS resources in a DL PRS resource set are associated with the same TRP, and each DL PRS resource has a DL PRS resource ID. The DL PRS resource ID in a DL PRS resource set is associated with a single beam transmitted from a single TRP (although a TRP can transmit one or more beams).

[0089] PRS resources can also be defined by quasi-co-location parameters and starting PRB parameters. The quasi-co-location (QCL) parameter defines any quasi-co-location information of the DLPRS resource with other reference signals. The DL PRS can be configured to be of QCL type D with DL PRS or SS / PBCH (Synchronization Signal / Physical Broadcast Channel) blocks from the serving cell or non-serving cell. The DL PRS can be configured to be of QCL type C with SS / PBCH blocks from the serving cell or non-serving cell. The starting PRB parameter defines the starting PRB index of the DLPRS resource with respect to reference point A. This starting PRB index has a granularity of one PRB and can have a minimum value of 0 PRBs and a maximum value of 2176 PRBs.

[0090] A PRS resource set is a collection of PRS resources with the same periodicity, the same silent mode configuration (if any), and the same cross-slot repetition factor. Each time all repetitions of all PRS resources in a PRS resource set are configured to be transmitted is called an "instance". Therefore, an "instance" of a PRS resource set is a specified number of repetitions for each PRS resource and a specified number of PRS resources within the PRS resource set, such that the instance is complete once the specified number of repetitions has been transmitted for each of the specified number of PRS resources. An instance can also be referred to as an "opportunity". A DLPRS configuration, including DL PRS transmission scheduling, can be provided to the UE to facilitate (or even enable) the UE to measure DL PRS.

[0091] Multiple frequency layers of a PRS can be aggregated to provide an effective bandwidth greater than any bandwidth in the individual layers. Multiple frequency layers belonging to component carriers (which can be consecutive and / or separate) and satisfying criteria such as Quasi-Co-location (QCL) and having the same antenna port can be stitched together to provide a larger effective PRS bandwidth (for DL ​​PRS and UL PRS), thereby improving the accuracy of time information (e.g., time of arrival) measurements. Stitching involves combining PRS measurements on individual bandwidth segments into a unified fragment, such that the stitched PRS can be considered as taken from a single measurement. In the case of QCL, different frequency layers behave similarly, resulting in a larger effective bandwidth for PRS stitching. The larger effective bandwidth (which may be referred to as the bandwidth of the aggregated PRS or the frequency bandwidth of the aggregated PRS) provides better time-domain resolution (e.g., TDOA resolution). The aggregated PRS comprises a collection of PRS resources, and each PRS resource in the aggregated PRS may be referred to as a PRS component, and each PRS component may be transmitted on different component carriers, frequency bands, or frequency layers, or on different portions of the same frequency band.

[0092] RTT positioning is an active positioning technology because RTT uses positioning signals transmitted from the TRP to the UE and from the UE (participating in RTT positioning) to the TRP. The TRP can transmit DL-PRS signals received by the UE, and the UE can transmit SRS (Sound Reference Signal) signals received by multiple TRPs. The Sound Reference Signal may be referred to as SRS or SRS signal. In 5G multi-RTT, coordinated positioning can be used, where the UE transmits a single UL-SRS for positioning received by multiple TRPs, instead of transmitting a separate UL-SRS for positioning for each TRP. A participating TRP will typically search for UEs currently residing on that TRP (the served UE, where the TRP is the serving TRP) and also search for UEs residing on neighboring TRPs (neighbor UEs). A neighboring TRP can be a TRP of a single BTS (Broadband Transceiver Station) (e.g., gNB), or it can be a TRP of one BTS and a TRP of a single BTS. For RTT positioning (including multi-RTT positioning), the DL-PRS and UL-SRS positioning signals in the PRS / SRS positioning signal pair used to determine the RTT (and thus the range between the UE and TRP) may occur close to each other in time, so that the errors caused by UE movement and / or UE clock drift and / or TRP clock drift are within acceptable limits. For example, the signals in the PRS / SRS positioning signal pair may be transmitted from the TRP and the UE within approximately 10 ms of each other. In cases where the SRS for positioning is being transmitted by the UE and the PRS and the SRS for positioning are transmitted close to each other in time, it has been found that this may lead to radio frequency (RF) signal congestion (which may result in excessive noise, etc.) (especially if many UEs are concurrently attempting positioning), and / or may lead to computational congestion at the TRP where many UEs are concurrently attempting to measure.

[0093] RTT positioning can be UE-based or UE-assisted. In UE-based RTT, UE 200 determines the RTT and corresponding range to each TRP in TRP 300, and determines the location of UE 200 based on the range to TRP 300 and the known location of TRP 300. In UE-assisted RTT, UE 200 measures positioning signals and provides measurement information to TRP 300, and TRP 300 determines the RTT and range. TRP 300 provides the range to a location server (e.g., server 400), and the server determines the location of UE 200, for example, based on the range to different TRP 300s. RTT and / or range can be determined by TRP 300 receiving signals from UE 200, by TRP 300 in conjunction with one or more other devices (e.g., one or more other TRP 300s and / or server 400), or by one or more devices other than TRP 300 receiving signals from UE 200.

[0094] 5G NR supports various positioning technologies. NR-native positioning methods supported in 5G NR include DL-only positioning, UL-only positioning, and DL+UL positioning. Downlink-based positioning methods include DL-TDOA and DL-AoD. Uplink-based positioning methods include UL-TDOA and UL-AoA. Combined DL+UL positioning methods include RTT with one base station and RTT with multiple base stations (multi-RTT).

[0095] Location estimates (e.g., for a UE) may be referred to by other names, such as location estimation, location, positioning, fixed positioning, etc. Location estimates may be geodesic and include coordinates (e.g., latitude, longitude, and possible altitude), or they may be municipal and include street addresses, postal addresses, or some other textual description of the location. Location estimates may be further defined relative to another known location or (e.g., using latitude, longitude, and possible altitude) in absolute terms. Location estimates may include expected errors or uncertainties (e.g., by including areas or volumes that the location is expected to be included with a specified or default confidence level). Location information may include (e.g., one or more satellite signals, PRS, and / or one or more other signals) one or more location signal measurements, and / or one or more values ​​based on one or more location signal measurements (e.g., one or more distances (possibly including one or more pseudoranges), and / or one or more location estimates, etc.).

[0096] refer to Figure 5A and Figure 5BThe diagram shows a block diagram of an example AI / ML model for location applications. The AI / ML location model 502 can be trained to learn the relationship between reference signal measurements (e.g., channel impulse response (CIR), power delay distribution (PDP), delay distribution (DP), etc.) and location-based tags (such as location or other intermediate messages). Figure 5A A direct AI / ML localization use case with AI / ML localization model 502 is described, which is configured to receive reference signal measurements and output target location (e.g., direct tag). Figure 5B An AI / ML-assisted localization use case is described, featuring an AI / ML localization model 502 configured to receive reference signal measurements and output one or more intermediate labels, such as time information (e.g., time of arrival), LOS identifier, AoA, etc. Intermediate measurements can be provided to a second localization model 504 configured to output the target location. The second localization model 504 can be another AI / ML model or other non-AI model (e.g., Chan algorithm, Kalman filter, etc.). In one example, the AI / ML localization model 502 may be very large, and sharing the entire dataset with a mobile device such as UE200 or other network station (e.g., TRP 300) may be impractical. In some cases, a practical approach could be to train the AI / ML localization model 502 as a neural network (NN) and then share the neural network model and the parameters (e.g., weights, etc.) used for training the model with the mobile device or network station. In one example, the AI / ML localization model may be communicated via the Open Neural Network Exchange (ONNX) format. Other formats (e.g., flat files, binary files, etc.) may also be used. Mobile devices or web stations can then use the trained NN to predict target location and / or intermediate measurements based on reference signal measurements.

[0097] In one example, supervised learning techniques can be used to train an AI / ML localization model 502, where the input dataset includes reference signal measurements, location information, and other parameters. Other training techniques can also be used. For example, supervised learning algorithms, semi-supervised learning algorithms, unsupervised learning algorithms, reinforcement learning algorithms, deep learning algorithms, artificial neural network algorithms, or other types of machine learning algorithms can be used. For example, a deep convolutional network (DCN) can be used to perform machine learning. A DCN is a network of convolutional networks configured with additional pooling and normalization layers. DCNs have achieved state-of-the-art performance on many tasks. DCNs can be trained using supervised learning, where both the input and output targets are known for many examples and are used to modify the network weights using gradient descent. A DCN can be a feedforward network. Furthermore, as described above, the connections from neurons in the first layer of a DCN to a set of neurons in the next higher layer are shared across neurons in the first layer. The feedforward and shared connections of a DCN can be used for fast processing. For example, the computational cost of a DCN may be much smaller than that of a similarly sized neural network that includes recurrent or feedback connections.

[0098] refer to Figure 6A A block diagram example of a UE-based and UE-assisted positioning technology with an AI / ML model is shown. First use case 620 (case 1), second use case 622 (case 2a), and third use case 624 (case 2b) include an LMF 602, gNB 604, and UE 606 configured to communicate with each other via LPP, RRC, or other signaling technologies known in the art. First use case 620 includes an example UE-side model such that UE 606 is configured with a first AI / ML positioning model 608. The first AI / ML positioning model 608 can be configured as follows... Figure 5A The direct AI / ML model described in [the document] (i.e., D-AIML), or configured as such Figure 5B The auxiliary AI / ML model (i.e., A-AIML) described herein. UE 606 can measure reference signal transmissions from gNB 604 (and possibly other network nodes) and provide the corresponding measurements as input to AI / ML model 608. For example, UE 606 can measure PRS transmissions based on the input requirements of AI / ML model 608 to determine RSRP, ToA, AoA, or other measurements such as CIR, power delay distribution, delay distribution, or channel frequency response. In one example, UE 606 can be configured to determine a target location based on the output of AI / ML model 608 (and a second positioning model for A-AIML use cases) and provide the target location to LMF 602 (e.g., via LPP message reception).

[0099] In the second use case 622, UE 606 may be configured with a second AI / ML model 610 configured as an auxiliary AI / ML model. UE 606 may obtain reference signal measurements and utilize the second AI / ML model 610 to calculate intermediate tags. UE 606 may provide intermediate measurements (e.g., tags) to LMF 602, and LMF 602 may be configured with a positioning model to calculate the target location of UE 606 based on the intermediate measurements. In the third use case 624, LMF 602 may include a third AI / ML model 612 configured to receive reference signal measurements from UE 606 and calculate the target location of UE 606. For example, UE 606 may obtain measurements based on PRS transmitted by gNB 604 and provide PRS-based measurements to LMF 602.

[0100] refer to Figure 6B And further reference Figure 6A A block diagram of an example node-assisted localization technique with an AI / ML model is shown. Use cases 626 (case 3a) and 628 (case 3b) include an LMF 602, a gNB 604, and a UE 606. In these use cases, the UE 606 is configured to transmit uplink reference signals, such as SRS, received and measured by the gNB 604. In use case 626, the gNB 604 is configured with a fourth AI / ML model 614, and the gNB 604 can provide measurements based on the SRS transmitted from the UE 606. The fourth AI / ML model 614 can be configured as A-AIML, and the gNB 604 can provide intermediate measurements (i.e., the output of the fourth AI / ML model 614) to the LMF 602. The LMF 602 can calculate the target location based on the intermediate measurements provided by the gNB 604 (and potentially other gNBs or radio nodes in the network). In the fifth use case 628, the LMF 602 may be configured with a fifth AI / ML model 616, which is configured to receive SRS-based measurements obtained by the gNB 604 (and other nodes) and calculate the target location. Figure 6A and Figure 6B The use cases described are examples and not limitations, as other configurations and AI / ML models may also be used in the communication system 100. For example, other servers 150 and / or external clients 130 may be configured to receive PRS and / or SRS measurements and calculate the target location based on the output of one or more AI / ML models.

[0101] refer to Figure 7This illustrates an example of a legacy QCL relationship between reference signals. Generally, antenna ports are considered to have a QCL relationship, where transmissions using different antenna ports experience a radio channel that shares some common characteristics. Radio channel characteristics that can be shared across different antenna ports may include Doppler shift, Doppler spread, average delay, delay spread, and spatial receiver parameters (e.g., AoA at the UE). The concept of QCL relationships was introduced in 3GPP to assist the UE in channel estimation, frequency offset estimation, and synchronization processes. For example, if two antenna ports are classified as QCL based on delay spread, the UE can determine the delay spread of the first antenna port and then apply the result to both antenna ports. Therefore, the UE will not have to determine the delay spread of each antenna port individually. Listing 702 indicates four types of QCL relationships specified by 3GPP to indicate which large-scale channel characteristics are shared across the QCL antenna port set. The four types of QCL are: Type A (Doppler frequency shift, Doppler spread, average delay, delay spread), Type B (Doppler frequency shift, Doppler spread), Type C (Doppler frequency shift, average delay), and Type D (space receiver parameters).

[0102] In operation, referring to example associated Figure 704, a network station can be configured to provide indications of QCL relationships for different reference signals. For example, a UE can indicate to a network server (e.g., LMF) which QCL sources (e.g., SSB of the serving cell / neighboring cell, PRS of the serving cell / neighboring cell, etc.) it is configured to support. The network server can use the QCL information to determine how to indicate future QCL relationships as part of the reference signal configuration (e.g., PRS configuration). The UE can request PRS resources that include QCL relationship information from network resources (e.g., LMF). When network resources provide PRS configuration information, the QCL relationship information can indicate the QCL relationship between the PRS and the SSB signal and / or between the PRS and other PRS. For example, referring to associated Figure 704, the QCL relationship information indicates that the SSB signal (i.e., SSB-1) has a type C relationship with the first PRS (i.e., PRS1) and a type D relationship with the second PRS (i.e., PRS2). The QCL relationship information can also indicate that the first PRS has a type D relationship with the third PRS (i.e., PRS3). QCL information can be provided via existing signaling technologies such as LPP and RRC. The relationships depicted in Figure 704 are illustrative and not limiting, as other reference signals and other QCL relationships may be included in the QCL information provided to the mobile device.

[0103] refer to Figure 8 And further reference Figures 6A to 7Example association diagram 802 illustrates the QCL relationship between reference signals and AI / ML models. In one example, AI / ML models 608, 610 may be provided to UE 606 along with indications of the QCL relationship to inform UE 606 of recommended reference signals (e.g., PRS resources) to be considered for model inputs (e.g., first use case 620 and second use case 622). The UE may also be configured to automatically perform model lifecycle management (LCM) operations on the received AI / ML model. LCM operations may include model training, model deployment, model inference, model monitoring, and model updates. Other LCM operations may also be performed (e.g., see 3GPP TR 38.843 V0.1.0, May 2023). In a third use case 624 (e.g., when the AI / ML positioning model is running on LMF 602), QCL relationship information may assist UE 606 in determining the prioritization and / or selection of PRS resources to be measured and reported to the LMF. This use case can be implemented when the UE 606 has limited capabilities for measuring and reporting measurements to the LMF 602 (e.g., a UE with reduced capabilities (RedCap UE) or a UE with limited bandwidth).

[0104] In operation, UE 606 may receive one or more indicators from LMF indicating the relationship between an AI / ML positioning model and a reference signal (e.g., the SSB of the serving cell / neighboring cell, the PRS of the serving cell / neighboring cell). The indicators may indicate a QCL relationship, which shows the equivalence / similarity type between the AI / ML positioning model and one of the characteristics of the reference signal as described in Listing 702. For example, referring to Association Figure 802, the indicators may include a type D QCL relationship between SSB-1 and AI / ML positioning model 1, a type D QCL relationship between PRS1 and AI / ML positioning model 2, and a type C QCL relationship between PRS3 and AI / ML positioning model 3. Multiple positioning models may be associated with the reference signal. For example, the indicators may include a type C QCL relationship between PRS2 and AI / ML positioning model 1 and a type D QCL relationship between PRS2 and AI / ML positioning model 3. UE 606 can be configured to utilize such QCL relationship indications to apply model lifecycle management (e.g., activation, deactivation, selection, switching, rollback) to AI / ML positioning models (e.g., in use cases 620, 622 when the AI / ML model is stored locally). In other use cases, UE 606 can be configured to prioritize and / or select PRS resources to measure and report back to LMF 602 (e.g., when the AI / ML model is not stored locally). One or more indications of the QCL relationship between the reference signal and the AI / ML model can be signaled via existing network protocols. For example, the indications can be signaled as part of LPP location request message reception, LPP assisted data exchange message reception, and LPP broadcast positioning (e.g., posSIB). Other signaling may also be used.

[0105] In one example, UE 606 may be configured to provide one or more indications to LMF 602 to indicate the relationship between an AI / ML positioning model (e.g., model 608, 610) and one or more reference signals (e.g., SSB of the serving cell / neighboring cell, PRS of the serving cell / neighboring cell). LMF 602 may be configured to use the indication information received from UE 606 to configure PRS resources for the indicated AI / ML positioning model. LMF 602 may also be configured to apply model LCMs (e.g., activation, deactivation, selection, handover, fallback) to the AI / ML positioning model. In one example, UE 606 may be configured to signal the indication information as part of LPP capability exchange (e.g., a component / condition part of an AI / ML feature or feature group for AI / ML positioning). LMF 602 may be configured to transmit a request to UE 606 to provide the indication information. In one example, UE 606 may request additional PRS resources based on the QCL relationship indicated by the AI / ML positioning model, where UE 606 indicates a recommended QCL relationship for running the AI / ML positioning model (e.g., on-demand PRS for the AI / ML positioning model). The AI / ML positioning model may be trained and supported by the UE side, and multiple UEs may be configured to provide the AI / ML model and QCL indication to the LMF.

[0106] refer to Figure 9A and Figure 9BThis illustrates an example message flow diagram for indicating a QCL AI / ML model. The example message flow includes radio nodes and network resources such as UE 902 and LMF 904. Other radio nodes, such as gNBs, may also utilize the message flow. In the first example message flow 900, LMF 904 may be configured to provide an AI / ML indicator 906, which includes an indication of the relationship between the AI / LM positioning model and a reference signal (e.g., the SSB of the serving cell / neighboring cell, the PRS of the serving cell / neighboring cell). The AI / ML indicator 906 may be signaled as part of LPP location request message reception, LPP assisted data exchange message reception, LPP broadcast positioning (e.g., posSIB), or a combination of such message receptions. Other signaling may also be used. The AI / ML indicator 906 may include QCL relationship information indicating the equivalence / similarity type between one characteristic of the AI / ML positioning model and the reference signal. For example, QCL relationships may include QCL type A (average delay, delay spread, Doppler shift, Doppler spread), QCL type B (Doppler shift, Doppler spread), QCL type C (average delay, Doppler shift), and QCL type D (spatial RX relationship). UE 902 may be configured to optionally provide measurement report messages 908 to LMF 904. In one example, UE 902 may prioritize and measure PRS resources based at least in part on an AI / ML model and provide one or more measurement report messages 908 including the measurement results.

[0107] In the second example message flow 910, UE 902 may be configured to provide AI / ML indicator 912 to LMF 904. This AI / ML indicator includes an indication of the relationship between the AI / LM positioning model and reference signals (e.g., the SSB of the serving cell / neighboring cell, the PRS of the serving cell / neighboring cell). The AI / ML indication may be signaled in LPP capability exchange (e.g., a component / conditional portion of an AI / ML feature or feature group for AI / ML positioning). Other signaling may also be used. LMF 904 may be configured to transmit a request to UE 902 to provide AI / ML indicator 912. In one example, LMF 904 may configure PRS resources based on the AI / ML positioning model and associated QCL indication received from UE 902, and then provide UE 902 with one or more PRS configurations 914. UE 902 may obtain PRS measurements based at least in part on the received PRS configurations 914. LMF 904 can configure PRS resources based on AI / ML instructions and provide one or more PRS configurations 914 to UE 902, and UE 902 is configured to apply AI / ML model lifecycle management in response to receiving a PRS configuration 914.

[0108] refer to Figure 10 And further reference Figures 1 to 9B The method 1000 for obtaining the output of an AI / ML model includes the stages shown. However, method 1000 is merely an example and not a limitation. Method 1000 can be modified, for example, by adding, removing, rearranging, combining, performing one or more stages concurrently, and / or by splitting one or more individual stages into multiple stages. For example, sending the output of the AI / ML model to a location server at stage 1008 is optional.

[0109] At stage 1002, the method includes receiving an indication of a quasi-colocation (QCL) relationship between an AI / ML model and a reference signal. A UE 200, including processor 210 and transceiver 215, is a component for receiving the indication of the QCL relationship. In one example, UE 200 (such as UE 902) may receive an AI / ML indicator 906 from a network entity (such as LMF 904). The LPP protocol or other signaling technologies (e.g., RRC SIB) may also be used to provide the AI / ML indicator. The AI / ML indicator 906 may include QCL relationship information indicating the equivalence / similarity type between a characteristic of the AI / ML positioning model and the reference signal, such as... Figure 8 The reference signal may include SSB, PRS, or other signals used for channel measurements. For example, QCL relationships may include QCL type A (average delay, delay spread, Doppler shift, Doppler spread), QCL type B (Doppler shift, Doppler spread), QCL type C (average delay, Doppler shift), and QCL type D (spatial RX relationship). Other QCL relationships may also be defined.

[0110] At stage 1004, the method includes obtaining one or more measurements associated with a reference signal. The UE 200, including processor 210 and transceiver 215, is the component for obtaining the measurements. The selection of the reference signal to be measured may be based on the QCL relationship with the AI / ML model on the UE 200 and an indication received at stage 1002. In one example, the one or more measurements may be based on a UE-based or UE-assisted positioning method and may include RSSI, RTT, RSTD, RSRP, and / or RSRQ. Other measurements, such as AoA, TDOA, E-CID, CIR, power delay distribution, delay distribution, and CFR value, may be obtained and / or calculated based on the received reference signal. The obtained measurements may be based on AI / ML training and desired output labels.

[0111] At stage 1006, the method includes calculating the output of the AI / ML model based at least in part on the one or more measurements. The UE 200, including processor 210 and transceiver 215, is the component used to calculate the output of the AI / ML model. The AI / ML model can be configured as a direct AI / ML model (i.e., D-AIML) or as an auxiliary AI / ML model (i.e., A-AIML). The AI / ML model can be trained to learn reference signal measurements (e.g., channel impulse response (CIR), etc.) obtained at stage 1004 and location-based tags (such as location) or other intermediate messages (e.g., such as...). Figure 5A , Figure 5B The relationship between the parameters described in the document is as follows. Intermediate measurements can be provided to a second localization model configured to output the target location. In one example, the second localization model may be located on a network resource (e.g., LMF 120) and may be another AI / ML model or other non-AI model (e.g., Chan algorithm, Kalman filter, etc.).

[0112] At stage 1008, the method may optionally include sending the output of the AI / ML model to a location server. The UE 200, including processor 210 and transceiver 215, is the component for sending the output of the AI / ML model. The UE 200 may be configured to provide direct and / or intermediate tags to a location server (such as LMF 120) using communication system 100. For example, the UE 200 may provide the calculated target location and / or intermediate measurements via LPP messages or other signaling technologies.

[0113] While method 1000 can be executed on UE 200, other radio nodes (such as TRP 300) can be configured to execute method 1000. For example, refer to Figure 6B The gNB 604 can receive QCL indication and SRS signals associated with the AI / ML model 614 (and other such models). The gNB 604 can be configured to measure the SRS and calculate the output of the AI / ML model 614. The output can be provided to, for example... Figure 6B LMF 602 as described in [the document / reference].

[0114] refer to Figure 11 And further reference Figures 1 to 9B The method 1100 for providing positioning reference signal configuration information includes the stages shown. However, method 1100 is merely an example and not a limitation. Method 1100 can be modified, for example, by adding, removing, rearranging, combining, performing one or more stages concurrently, and / or by splitting one or more individual stages into multiple stages.

[0115] At stage 1102, the method includes receiving from a wireless node an indication of a quasi-co-location (QCL) relationship between an AI / ML model and a reference signal. Server 400 (such as LMF 120 including processor 410 and transceiver 415) is a component for receiving the indication of the QCL relationship. In one example, the reference... Figure 9B Radio nodes (such as UEs and gNBs) can be configured to provide AI / ML indicators to network resources (such as LMFs). These AI / ML indicators include indications of the relationship between the AI / ML positioning model and reference signals (e.g., the SSB of the serving cell / neighboring cell, the PRS of the serving cell / neighboring cell). The AI / ML indicators may include QCL relationship information, which indicates the equivalence / similarity type between one characteristic of the AI / ML positioning model and the reference signal. For example, QCL relationships may include QCL type A (average delay, delay spread, Doppler shift, Doppler spread), QCL type B (Doppler shift, Doppler spread), QCL type C (average delay, Doppler shift), and QCL type D (spatial RX relationship). The AI / ML indicators may be signaled in LPP capability exchanges (e.g., components / conditional parts of AI / ML features or feature groups used for AI / ML positioning). Other signaling may also be used.

[0116] At stage 1104, the method includes configuring one or more positioning reference signal resources, at least in part, based on indications of QCL relationships. Server 400, including processor 410 and transceiver 415, is a component for configuring one or more PRS. The LMF can utilize QCL relationship characteristics to configure PRS resources and then distribute the PRS resources to radio nodes (e.g., gNB, UE). These characteristics can be based on... Figure 7 The types of QCL relationships described in the document (e.g., average delay, delay spread, Doppler shift, Doppler spread, spatial relationship, etc.).

[0117] At stage 1106, the method includes providing configuration information to the radio node for one or more positioning reference signal resources. Server 400, including processor 410 and transceiver 415, is the component for providing the configuration information. In one example, PRS resource configuration may be provided in one or more LPP messages, such as NR-DL-PRS-Resource messages. Other signaling technologies, such as RRC and SIB, may be used to provide the configuration information.

[0118] Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software and computers, the functions described above can be implemented using software, hardware, firmware, hardwiring, or any combination thereof executed by a processor. Features implementing the functions can also be physically located in various locations, including portions distributed such that the functions are implemented in different physical locations.

[0119] As used herein, the singular forms “a,” “an,” and “the” also include the plural forms, unless the context clearly indicates otherwise. Thus, references to a device in the singular form included in the claims (e.g., “device,” “the / said device”) include at least one of such devices (i.e., one or more) (e.g., “processor” includes at least one processor (e.g., one processor, two processors, etc.), “the / said processor” includes at least one processor, “memory” includes at least one memory, “the / said memory” includes at least one memory, etc.). The phrases “at least one” and “one or more” are used interchangeably, and such that the object referred to by “at least one” and the object referred to by “one or more” include embodiments having one referred object and embodiments having multiple referred objects. For example, “at least one processor” and “one or more processors” each include embodiments having one processor and embodiments having multiple processors.

[0120] As used herein, the term "comprising" indicates the presence of the described features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0121] Furthermore, as used herein, the "or" (possibly followed by "at least one of" or "one or more of") used in the item enumeration indicates a disjunctive enumeration such that an enumeration of, for example, "at least one of A, B, or C," or an enumeration of "one or more of A, B, or C," or an enumeration of "A or B or C" represents A or B or C or AB (A and B) or AC (A and C) or BC (B and C) or ABC (i.e., A and B and C), or a combination having more than one feature (e.g., AA, AAB, ABBC, etc.). Therefore, a statement that an item (e.g., a processor) is configured to perform a function relating to at least one of A or B, or a statement that an item is configured to perform function A or function B, indicates that the item can be configured to perform a function relating to A, or can be configured to perform a function relating to B, or can be configured to perform a function relating to both A and B. For example, the phrase "a processor configured to measure at least one of A or B" or "a processor configured to measure A or measure B" means that the processor can be configured to measure A (and may or may not be configured to measure B), or can be configured to measure B (and may or may not be configured to measure A), or can be configured to measure both A and B (and can be configured to select which of A and B or measure both). Similarly, a description of a component for measuring at least one of A or B includes: a component for measuring A (which may or may not be able to measure B), or a component for measuring B (which may or may not be configured to measure A), or a component for measuring A and B (which may be able to select which of A and B or measure both). As another example, a description of an item (e.g., a processor) being configured to perform at least one of function X or function Y means that the item can be configured to perform function X, or can be configured to perform function Y, or can be configured to perform both functions X and Y. For example, the phrase "processor configured to measure at least one of X or Y" means that the processor can be configured to measure X (and may or may not be configured to measure Y), or can be configured to measure Y (and may or may not be configured to measure X), or can be configured to measure both X and Y (and can be configured to select which of X and Y or measure both).

[0122] As used herein, unless otherwise stated, a description of a function or operation as “based on” an item or condition means that the function or operation is based on the described item or condition and may be based on one or more items and / or conditions other than the described item or condition.

[0123] Substantial changes can be made depending on specific requirements. For example, custom hardware may be used, and / or specific elements may be implemented in the hardware, in software executed by the processor (including portable software such as applets), or both. Furthermore, connections to other computing devices, such as network input / output devices, may be employed. Unless otherwise specified, components shown in the figures and / or discussed herein that are connected or communicate with each other (functionally or otherwise) are communicatively coupled. That is, these components may be connected directly or indirectly to enable communication between them.

[0124] The systems and devices discussed above are examples. Various configurations may appropriately omit, substitute, or add various processes or components. For example, features described with respect to certain configurations may be combined in various other configurations. Different aspects and elements of configurations may be combined in a similar manner. Furthermore, technology is constantly evolving, and therefore many elements are examples and do not limit the scope of this disclosure or the claims.

[0125] A wireless communication system is a system in which communication is transmitted wirelessly between wireless communication devices, that is, through the propagation of electromagnetic waves and / or sound waves through the atmosphere rather than through wires or other physical connections. A wireless communication system (also called a wireless communication system or wireless communication network) may not transmit all communication wirelessly, but is configured to allow at least some communication to be transmitted wirelessly. Furthermore, the term "wireless communication device" or similar terms do not require the device to be functionally exclusive or even primarily used for communication, do not require that communication using the wireless communication device be exclusive or even primarily wireless, and do not require that the device be a mobile device, but rather indicate that the device includes wireless communication capabilities (one-way or two-way), for example, including at least one radio component (each radio component being part of a transmitter, receiver, or transceiver) for wireless communication.

[0126] Specific details are provided in this description to offer a thorough understanding of the example configurations, including specific implementations. However, the configurations can be practiced without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques have been shown without unnecessary detail to avoid obscuring these configurations. The description herein provides example configurations and does not limit the scope, applicability, or configuration of the claims. Rather, the preceding description of the configurations provides a description for implementing the described techniques. Various changes can be made to the function and arrangement of the elements.

[0127] As used herein, the terms “processor-readable medium,” “machine-readable medium,” and “computer-readable medium” refer to any medium that participates in providing data that enables a machine to operate in a particular manner. Using a computing platform, various processor-readable media may involve providing instructions / code to a processor for execution, and / or may be used to store and / or carry such instructions / code (e.g., as signals). In many specific implementations, processor-readable media are physical and / or tangible storage media. Such media can take many forms, including but not limited to non-volatile and volatile media. Non-volatile media include, for example, optical discs and / or magnetic disks. Volatile media include, but are not limited to, dynamic memory.

[0128] Having described several example configurations, various modifications, alternative constructions, and equivalents can be used. For example, the above elements can be components of a larger system, where other rules may take precedence over or otherwise modify the application of this disclosure. Furthermore, several operations may be performed before, during, or after considering the above elements. Accordingly, the above description does not limit the scope of the claims.

[0129] Unless otherwise indicated, the terms "about" and / or "approximately" as used herein when referring to measurable values ​​(such as quantities, durations of time, etc.) cover variations of ±20%, ±10%, ±5%, or ±0.1% from the specified value, as appropriate in the context of the systems, devices, circuits, methods, and other specific embodiments described herein. Similarly, unless otherwise indicated, the term "substantially" as used herein when referring to measurable values ​​(such as quantities, durations of time, physical properties (such as frequencies), etc.) also covers variations of ±20%, ±10%, ±5%, or ±0.1% from the specified value, as appropriate in the context of the systems, devices, circuits, methods, and other specific embodiments described herein.

[0130] A statement that a value exceeds (or is greater than or higher than) a first threshold is equivalent to a statement that a value meets or exceeds a second threshold slightly greater than the first threshold. For example, in the resolution of the computing system, the second threshold is one value higher than the first threshold. A statement that a value is less than the first threshold (or within or below the first threshold) is equivalent to a statement that a value is less than or equal to a second threshold slightly lower than the first threshold. For example, in the resolution of the computing system, the second threshold is one value lower than the first threshold.

[0131] Specific implementation examples are described in the following numbered clauses:

[0132] Clause 1. A method for obtaining the output of an AI / ML model, the method comprising: receiving an indication of a quasi-co-addressable (QCL) relationship between the AI / ML model and the reference signal; obtaining one or more measurements associated with the reference signal; and calculating the output of the AI / ML model based at least in part on the one or more measurements.

[0133] Clause 2. The method described in Clause 1, wherein the output of the AI / ML model is the target location.

[0134] Clause 3. The method according to Clause 2, the method further comprising: sending the target location to a location server.

[0135] Clause 4. The method according to Clause 1, wherein the output of the AI / ML model is an intermediate measurement, the intermediate measurement including at least one of time information, angle of arrival, and line-of-sight path information.

[0136] Clause 5. The method described in Clause 4 further includes: sending the intermediate measurement to a location server.

[0137] Clause 6. The method according to Clause 1, wherein the one or more measurements include channel impulse response, power delay distribution, delay distribution, or channel frequency response.

[0138] Clause 7. The method according to Clause 1, wherein the indication of the QCL relationship is received via an LPP message.

[0139] Clause 8. The method according to Clause 7, wherein the indication of the QCL relationship is received from the location management function.

[0140] Clause 9. The method described in Clause 1, wherein the reference signal is a positioning reference signal.

[0141] Clause 10. The method according to Clause 1, wherein the reference signal is a probe reference signal.

[0142] Clause 11. The method according to Clause 1, further comprising: in response to receiving the instruction on the QCL relationship, applying a model lifecycle management operation to the AI / ML model.

[0143] Clause 12. A method for providing positioning reference signal configuration information, the method comprising: receiving from a wireless node an indication of a quasi-co-location (QCL) relationship between an AI / ML model and a reference signal; configuring one or more positioning reference signal resources based at least in part on the indication of the QCL relationship; and providing the wireless node with configuration information for the one or more positioning reference signal resources.

[0144] Clause 13. The method according to Clause 12, wherein the indication of the QCL relation includes at least one of average delay, delay spread, Doppler shift, Doppler spread, and spatial relation.

[0145] Clause 14. The method according to Clause 12, wherein the indication of the QCL relationship is received via an LPP message or an NRPPa message.

[0146] Clause 15. The method described in Clause 12, wherein the wireless node is user equipment.

[0147] Clause 16. The method according to Clause 15, the method further comprising: requesting the instruction on the QCL relationship from the user equipment.

[0148] Clause 17. The method according to Clause 15, the method further comprising: receiving from the user equipment a request for additional positioning reference signal resources.

[0149] Clause 18. The method described in Clause 12, wherein the wireless node is gNode B.

[0150] Clause 19. The method according to Clause 12, further comprising: in response to receiving the instruction on the QCL relationship, applying a model lifecycle management operation to at least one AI / ML model.

[0151] Clause 20. An apparatus comprising: at least one memory; at least one transceiver; at least one processor communicatively coupled to the at least one memory and the at least one transceiver, and configured to: receive an indication of a quasi-co-addressable (QCL) relationship between an AI / ML model and a reference signal; obtain one or more measurements associated with the reference signal; and compute an output of the AI / ML model based at least in part on the one or more measurements.

[0152] Clause 21. The apparatus according to Clause 20, wherein the output of the AI / ML model is the target location.

[0153] Clause 22. The apparatus according to Clause 21, wherein the at least one processor is further configured to send the target location to a location server.

[0154] Clause 23. The apparatus of Clause 20, wherein the output of the AI / ML model is an intermediate measurement, the intermediate measurement including at least one of time information, angle of arrival, and line-of-sight path information.

[0155] Clause 24. The apparatus according to Clause 23, wherein the at least one processor is further configured to send the intermediate measurement to a location server.

[0156] Clause 25. The apparatus of Clause 20, wherein the one or more measurements include channel impulse response, power delay distribution, delay distribution, or channel frequency response.

[0157] Clause 26. The apparatus according to Clause 20, wherein the indication of the QCL relationship is received via an LPP message.

[0158] Clause 27. The apparatus according to Clause 26, wherein the indication of the QCL relationship is received from the location management function.

[0159] Clause 28. The apparatus according to Clause 20, wherein the reference signal is a positioning reference signal.

[0160] Clause 29. The apparatus according to Clause 20, wherein the reference signal is a detection reference signal.

[0161] Clause 30. The apparatus of Clause 20, wherein the at least one processor is further configured to apply a model lifecycle management operation to the AI / ML model in response to receiving the instruction on the QCL relationship.

[0162] Clause 31. An apparatus comprising: at least one memory; at least one transceiver; at least one processor communicatively coupled to the at least one memory and the at least one transceiver, and configured to: receive from a wireless node an indication of a quasi-colocation (QCL) relationship between an AI / ML model and a reference signal; configure one or more location reference signal resources based at least in part on the indication of the QCL relationship; and provide the wireless node with configuration information for the one or more location reference signal resources.

[0163] Clause 32. The apparatus according to Clause 31, wherein the indication of the QCL relation includes at least one of average delay, delay spread, Doppler frequency shift, Doppler spread, and spatial relation.

[0164] Clause 33. The apparatus according to Clause 31, wherein the indication of the QCL relationship is received via an LPP message or an NRPPa message.

[0165] Clause 34. The apparatus described in Clause 31, wherein the wireless node is user equipment.

[0166] Clause 35. The apparatus according to Clause 34, wherein the at least one processor is further configured to request the instruction on the QCL relationship from the user equipment.

[0167] Clause 36. The apparatus according to Clause 34, wherein the at least one processor is further configured to receive a request for additional positioning reference signal resources from the user equipment.

[0168] Clause 37. The apparatus described in Clause 31, wherein the wireless node is a gNode B.

[0169] Clause 38. The apparatus according to Clause 31, wherein the at least one processor is further configured to apply a model lifecycle management operation to at least one AI / ML model in response to receiving the instruction on the QCL relationship.

[0170] Clause 39. An apparatus for obtaining the output of an AI / ML model, the apparatus comprising: means for receiving an indication of a quasi-co-addressable (QCL) relationship between the AI / ML model and a reference signal; means for obtaining one or more measurements associated with the reference signal; and means for calculating the output of the AI / ML model based at least in part on the one or more measurements.

[0171] Clause 40. An apparatus for providing location reference signal configuration information, the apparatus comprising: means for receiving from a wireless node an indication of a quasi-co-location (QCL) relationship between an AI / ML model and a reference signal; means for configuring one or more location reference signal resources based at least in part on the indication of the QCL relationship; and means for providing the wireless node with configuration information for the one or more location reference signal resources.

[0172] Clause 41. A non-transitory processor-readable storage medium comprising processor-readable instructions configured to enable one or more processors to obtain the output of an AI / ML model, the processor-readable instructions comprising code for: receiving an indication of a quasi-co-address (QCL) relationship between the AI / ML model and a reference signal; obtaining one or more measurements associated with the reference signal; and calculating the output of the AI / ML model based at least in part on the one or more measurements.

[0173] Clause 42. A non-transitory processor-readable storage medium comprising processor-readable instructions configured to enable one or more processors to provide location reference signal configuration information, the processor-readable instructions comprising code for: receiving from a wireless node an indication of a quasi-co-address (QCL) relationship between an AI / ML model and a reference signal; configuring one or more location reference signal resources based at least in part on the indication of the QCL relationship; and providing the wireless node with configuration information for the one or more location reference signal resources.

Claims

1. A method for obtaining the output of an AI / ML model, the method comprising: Receive an indication of the quasi-co-address (QCL) relationship between the AI / ML model and the reference signal; Obtain one or more measurements associated with the reference signal; as well as The output of the AI / ML model is calculated at least in part based on the one or more of the measurements.

2. The method of claim 1, wherein the output of the AI / ML model is the target location.

3. The method according to claim 2, further comprising: Send the target location to the location server.

4. The method of claim 1, wherein the output of the AI / ML model is an intermediate measurement, the intermediate measurement including at least one of time information, angle of arrival, and line-of-sight path information.

5. The method according to claim 4, further comprising: The intermediate measurements are sent to the location server.

6. The method of claim 1, wherein the one or more measurements include channel impulse response, power delay distribution, delay distribution, or channel frequency response.

7. The method of claim 1, wherein the indication of the QCL relationship is received via an LPP message.

8. The method of claim 7, wherein the indication of the QCL relationship is received from the location management function.

9. The method according to claim 1, wherein the reference signal is a positioning reference signal.

10. The method of claim 1, wherein the reference signal is a detection reference signal.

11. The method according to claim 1, further comprising: In response to receiving the instruction regarding the QCL relationship, a model lifecycle management operation is applied to the AI / ML model.

12. A method for providing positioning reference signal configuration information, the method comprising: Receive an indication from the wireless node of the quasi-co-location (QCL) relationship between the AI / ML model and the reference signal; One or more positioning reference signal resources are configured, at least in part, based on the indication of the QCL relationship; as well as Provide the wireless node with configuration information for the one or more positioning reference signal resources.

13. The method of claim 12, wherein the indication of the QCL relationship comprises at least one of average delay, delay spread, Doppler frequency shift, Doppler spread, and spatial relationship.

14. The method of claim 12, wherein the indication of the QCL relationship is received via an LPP message or an NRPPa message.

15. The method of claim 12, wherein the wireless node is user equipment.

16. The method according to claim 15, further comprising: The user equipment requests the instruction regarding the QCL relationship.

17. The method according to claim 15, further comprising: Receive a request for additional positioning reference signal resources from the user equipment.

18. The method of claim 12, wherein the wireless node is a gNode B.

19. The method according to claim 12, further comprising: In response to receiving the instruction regarding the QCL relationship, a model lifecycle management operation is applied to at least one AI / ML model.

20. An apparatus comprising: At least one memory; At least one transceiver; At least one processor, communicatively coupled to the at least one memory and the at least one transceiver, and configured to: Receives an indication of the quasi-co-address (QCL) relationship between the AI / ML model and the reference signal; Obtain one or more measurements associated with the reference signal; and The output of the AI / ML model is calculated at least in part based on one or more of the measurements.

21. The apparatus of claim 20, wherein the output of the AI / ML model is a target location, and the at least one processor is further configured to send the target location to a location server.

22. The apparatus of claim 20, wherein the output of the AI / ML model is an intermediate measurement, the intermediate measurement including at least one of time information, angle of arrival, and line-of-sight path information, and the at least one processor is further configured to send the intermediate measurement to a location server.

23. The apparatus of claim 20, wherein the at least one processor is further configured to apply a model lifecycle management operation to the AI / ML model in response to receiving the instruction on the QCL relationship.

24. An apparatus comprising: At least one memory; At least one transceiver; At least one processor, communicatively coupled to the at least one memory and the at least one transceiver, and configured to: Receive an indication from the wireless node of the quasi-co-location (QCL) relationship between the AI / ML model and the reference signal; One or more positioning reference signal resources are configured, at least in part, based on the indication of the QCL relationship; as well as Provide the wireless node with configuration information for the one or more positioning reference signal resources.

25. The apparatus of claim 24, wherein the indication of the QCL relationship comprises at least one of average delay, delay spread, Doppler frequency shift, Doppler spread, and spatial relationship.

26. The apparatus of claim 24, wherein the wireless node is user equipment.

27. The apparatus of claim 26, wherein the at least one processor is further configured to request the indication of the QCL relationship from the user equipment.

28. The apparatus of claim 26, wherein the at least one processor is further configured to receive a request for additional positioning reference signal resources from the user equipment.

29. The apparatus of claim 24, wherein the wireless node is a gNode B.

30. The apparatus of claim 24, wherein the at least one processor is further configured to apply a model lifecycle management operation to at least one AI / ML model in response to receiving the instruction on the QCL relationship.

Images