Positioning reference signal configuration and management

Abstract

A signal measurement assistance method includes obtaining reference signal angle information including a first indication, the first indication indicating a first reference signal and a first expected angle of arrival of the first reference signal, and at least one of requesting a transmission / reception point (TRP) to transmit the first indication to a user equipment or requesting the TRP to search for the first reference signal based on the first expected angle of arrival.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of Indian Patent Application No. 202011040980 entitled “RS CONFIGURATION AND MANAGEMENT”, filed on September 22, 2020, which has been assigned to the assignee of this application and whose entire contents are hereby incorporated by reference for all purposes.

[0003] background

[0004] Wireless communication systems have undergone several generations of development, including first-generation analog radiotelephone service (1G), second-generation (2G) digital radiotelephone service (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data radio service with Internet capabilities, fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax), and fifth-generation (5G) service. Currently, many different types of wireless communication systems are 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), and GSM TDMA variants.

[0005] 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 rate to each of tens of thousands of users, and 1 gigabits per second (Gbps) to dozens of employees on an office floor. It should support hundreds of thousands of simultaneous connections to support large-scale sensor deployments. 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 significantly reduced compared to the current standard.

[0006] Overview

[0007] An example network entity includes: an interface; a memory; and a processor communicatively coupled to the interface and the memory and configured to: obtain reference signal angle information including a first indication, the first indication indicating a first reference signal and a first expected angle of arrival of the first reference signal; and perform at least one of the following operations: requesting a transmit / receive point (TRP) to transmit the first indication to a user equipment; or requesting the TRP to search for the first reference signal based on the first expected angle of arrival.

[0008] An example signal measurement assistance method includes: obtaining reference signal angle information including a first indication, the first indication indicating a first reference signal and a first expected angle of arrival of the first reference signal; and performing at least one of the following operations: requesting a transmit / receive point (TRP) to transmit the first indication to user equipment; or requesting the TRP to search for the first reference signal based on the first expected angle of arrival.

[0009] An example user equipment includes: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory and configured to: transmit an angle usage capability message to a network entity via the transceiver, the angle usage capability message indicating the UE's ability to use signal angle information to measure a signal; receive a reference signal indication from the network entity via the transceiver, the reference signal indication indicating a reference signal and at least one reference signal angle search window corresponding to the reference signal; and search for the reference signal based on the at least one reference signal angle search window.

[0010] An example method for measuring a reference signal at a user equipment includes: transmitting an angle utilization capability message from the user equipment to a network entity, the angle utilization capability message indicating the user equipment's ability to measure a signal using signal angle information; receiving a reference signal indication from the network entity at the user equipment, the reference signal indication indicating a reference signal and at least one reference signal angle search window corresponding to the reference signal; searching for the reference signal at the user equipment based on the at least one reference signal angle search window; and measuring the reference signal at the user equipment. Brief description of the attached diagram

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

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

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

[0015] Figure 4 This is a block diagram of the components of the example server, and various embodiments of this example server are shown below. Figure 1 As shown in the image.

[0016] Figure 5 This is a block diagram of an example user equipment.

[0017] Figure 6 This is a block diagram of an example network entity.

[0018] Figure 7A This is a perspective view of the signal received from the base station at the angle of arrival.

[0019] Figure 7B This is a simplified diagram of the signal received from the base station at the line-of-sight angle and the signal received from the base station at the reflected angle of arrival.

[0020] Figure 8 yes Figure 5 A simplified diagram of an example of the signal receiving path for user equipment shown.

[0021] Figure 9 It is used to determine the processing and signal flow of positioning information.

[0022] Figure 10 yes Figure 9 The image shows a simplified example of an angle capability message.

[0023] Figure 11 This is a simplified diagram of the table containing the reference signal angle information set.

[0024] Figure 12 yes Figure 9 The example shown is a simplified example of a reference signal angle information message.

[0025] Figure 13 This is a flowchart of a signal measurement auxiliary method.

[0026] Figure 14 This is a flowchart of a method for measuring a reference signal.

[0027] Detailed description

[0028] This paper discusses techniques for facilitating the measurement of signals, such as reference signals. For example, user equipment (UE) can be instructed to use angle-aided information to search for, receive, and measure one or more (reference) signals. Capabilities can be indicated for a corresponding reference signal and / or one or more corresponding characteristics of the reference signal (e.g., frequency bands, combinations of frequency bands). Network entities can request transmit / receive points to send angle-aided information to the UE to help reduce the angle search window used by the UE to receive the (reference) signals. The UE can provide feedback to the network entity to help improve the angle-aided information. However, other examples can be implemented.

[0029] The projects and / or techniques described herein may provide one or more of the following capabilities, as well as others not mentioned: The latency for determining location information can be reduced, for example, by reducing the time required to locate the signal to be measured. The accuracy of location information determination can be improved. Computational complexity can be reduced, for example, by reducing the processing required to locate the received signal. Other capabilities may be provided, and not every implementation according to this disclosure is required to provide any, let alone all, of the capabilities discussed.

[0030] Obtaining the location of a mobile device accessing a wireless network can be useful for many applications, including, for example, emergency calls, personal navigation, consumer asset tracking, and locating friends or family members. Existing positioning methods include those based on measuring radio signals transmitted from various devices or entities, including satellite carriers (SVs) and terrestrial radio sources in the wireless network, 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 utilize Positioning Reference Signals (PRS) and / or Cell-specific Reference Signals (CRS).

[0031] This description may refer to a sequence of actions to be performed by elements such as 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 implemented in a non-transitory computer-readable medium storing a corresponding set of computer instructions that, upon execution, will cause the associated processor to perform the functionality described herein. Thus, the aspects described herein can be implemented in several different forms, all of which fall within the scope of this disclosure, including the claimed subject matter.

[0032] 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 stated. Generally, such a UE can be any wireless communication device (e.g., mobile phone, router, tablet computer, laptop computer, consumer asset tracking device, Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. The 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”, “Subscriber Equipment”, “Subscriber Terminal”, “Subscriber Station”, “User Terminal” or “UT”, “Mobile Terminal”, “Mobile Station”, “Mobile Equipment”, or variations thereof. Generally, 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 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 a wired access network, a WiFi network (e.g., based on IEEE 802.11, etc.), etc.

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

[0034] The UE can be implemented using any of several types of devices, including but not limited to printed circuit (PC) cards, dense flash memory devices, external or internal modems, wireless or wired telephones, smartphones, tablet devices, consumer asset tracking devices, asset tags, etc. The communication link through which the UE can send 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 send 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.

[0035] As used herein, depending on the context, the terms "cell" or "sector" may correspond to one of multiple 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 protocol types that 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).

[0036] Reference 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, IoT devices, location tracker devices, cellular phones, vehicles (e.g., cars, trucks, buses, ships, etc.) or other devices. 5G networks can also be referred to as new radio (NR) networks; 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 Third Generation Partnership Project (3GPP). Accordingly, NG-RAN 135 and 5GC 140 can comply with current or future standards for 5G support from 3GPP. NG-RAN 135 can be another type of RAN, such as 3G RAN, 4G Long Term Evolution (LTE) RAN, etc. UE106 can be similarly configured and coupled to UE 105 to send 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 can use information from constellation 185 of satellite carriers (SVs) 190, 191, 192, and 193 for a satellite positioning system (SPS) (e.g., a Global Navigation Satellite System (GNSS)), 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 replacement components.

[0037] like Figure 1As shown, NG-RAN 135 includes NR B-nodes (gNB) 110a, 110b and a next-generation evolved B-node (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 Mobility 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 and configured to conduct bidirectional communication with AMF 115. 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. SMF 117 can be used as the initial contact point for Service Control Functions (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 (WiFi-D)). (Communication via Low Energy (BLE), Zigbee, etc.). One or more BSs (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 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.

[0038] Figure 1A general explanation of each component is provided, wherein any or all of the components may be used appropriately, and each component may be repeated or omitted as needed. Specifically, although one UE 105 is explained, many UEs (e.g., hundreds, thousands, millions, etc.) may be used 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), gNB 110a, 110b, ng-eNB 114, AMF 115, external client 130, and / or other components. The explained 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, components may be rearranged, combined, separated, replaced, and / or omitted depending on the desired functionality.

[0039] Although Figure 1 While 5G-based networks have been described, similar network implementations and configurations can be used for other communication technologies, such as 3G, Long Term Evolution (LTE), etc. The implementations described herein (for 5G technologies 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 measurements of such directional transmissions received at UE 105. Gateway Mobile Location Center (GMLC) 125, Location Management Function (LMF) 120, Access and Mobility Management Function (AMF) 115, SMF 117, ng-eNB (evolved B-node) 114, and gNB (g B-node) 110a, 110b are examples and may be replaced by or include these functions in various embodiments by various other location server functions and / or base station functions, respectively.

[0040] 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 base transceiver stations). For indirect communication, the communication may be altered during transmission from one entity to another, for example, to change the header information of data packets, change the format, etc. UE 105 may include multiple UEs and may be mobile wireless communication devices, but can communicate wirelessly and 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.

[0041] 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, 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, e.g., V2P (vehicle to pedestrian), V2I (vehicle to infrastructure), V2V (vehicle to vehicle) etc.), IEEE (e.g., 802.11p). V2X communication can be cellular (Cellular-V2X (C-V2X)) and / or WiFi (e.g., DSRC (Dedicated Short Range Connectivity)). System 100 can support operation on multiple carriers (waveform signals of different frequencies). A multi-carrier transmitter can transmit modulated signals on multiple carriers simultaneously. 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 a different carrier 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 channels (such as the Physical Sidelink Synchronization Channel (PSSCH), Physical Sidelink Broadcast Channel (PSBCH), or Physical Sidelink Control Channel (PSCCH)).

[0042] 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 device, 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 required, UE 105 may support one or more Radio Access Technologies (RATs) 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 (also known as Wi-Fi). Wireless communication can be achieved using technologies such as Bit-Beat (BT), WiMAX (Microwave Access Global Interoperability), and 5G New Radio (NR) (e.g., using NG-RAN 135 and 5GC 140). UE 105 can support wireless communication using a Wireless Local Area Network (WLAN), 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) to... Figure 1 (not shown in the diagram) or possibly via GMLC 125, communicate with external client 130 and / or allow external client 130 (e.g., via GMLC 125) to receive location information about UE 105.

[0043] UE 105 may include a single entity or may include multiple entities, such as in a personal area network in which the user may employ audio, video, and / or data I / O (input / output) devices, and / or body sensors, and separate wired or wireless modems. An estimate of the location of UE 105 may be referred to as location, location estimate, location lock, lock, positioning, location estimation, or location lock, and may be geographic, providing location coordinates (e.g., latitude and longitude) about UE 105, 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., expressed as 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 expressed as an area or volume (geographically or municipally defined) in 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 expressed as a relative location, which includes, for example, distance and direction from a known location. A relative location can be expressed 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 term "location" may include any of these variations unless otherwise indicated. When calculating the location of the UE, local x, y, and possibly 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 elevation above or below mean sea level).

[0044] 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 Direct (WiFi-D), etc.). Supported by (etc.). One or more UEs in a group of UEs using D2D communication may be 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 the group may be outside such geographic coverage area or may be unable to receive transmissions from the base station for other reasons. A group of UEs communicating via D2D communication may utilize a one-to-many (1:M) system, where each UE may transmit to other UEs in the group. The TRP facilitates 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 group of UEs using D2D communication may be within the geographic coverage area of ​​a TRP. Other UEs in the group may be outside such geographic coverage area or may be unable to receive transmissions from the base station for other reasons. A group of UEs communicating via D2D communication may utilize a one-to-many (1:M) system, where each UE may transmit to other UEs in the group. TRP facilitates the scheduling of resources used for D2D communication. In other cases, D2D communication can be performed between UEs without involving TRP.

[0045] Figure 1 The base stations (BSs) in the NG-RAN 135 shown include NRB nodes (referred to as gNBs 110a and 110b). Each pair of gNBs 110a and 110b in the 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 between UE 105 and one or more of the gNBs 110a and 110b. gNBs 110a and 110b 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.

[0046] Figure 1The base station (BS) in NG-RAN 135 shown may include ng-eNB 114 (also referred to as a next-generation evolved B node). ng-eNB 114 may be connected to one or more of the 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 the gNBs 110a, 110b and / or ng-eNB 114 may be configured to act as a location-only beacon, transmitting signals to aid in determining the location of UE 105, but may not be able to receive signals from UE 105 or other UEs.

[0047] gNB 110a, 110b and / or ng-eNB 114 may each include one or more TRPs. For example, each sector within a BS cell may include a TRP, but multiple TRPs may share one or more components (e.g., share a processor but have separate antennas). System 100 may exclusively include macro TRPs, or system 100 may have different types of TRPs, such as macro, pico, and / or femto TRPs. Macro TRPs may cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by terminals with service subscriptions. Pico TRPs may cover a relatively small geographic area (e.g., a pico cell) and 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 allow restricted access by terminals associated with that femto cell (e.g., a user's terminal in a residence).

[0048] 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 110a includes RU 111, DU 112, and CU 113. RU 111, DU 112, and CU 113 define the functionality of the gNB 110a. Although the gNB 110a 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 a portion 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 110a. DU 112 stores the Radio Link Control (RLC), Media Access Control (MAC), and Physical Layer of gNB 110a. A DU can support one or more cells, and each cell is supported by one 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 exclusively assigned to DU 112. CU 113 stores the Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of gNB 110a. 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.

[0049] As mentioned, although Figure 1 The diagram depicts a node 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 protocols) can also be used. For example, 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 B-nodes (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 and EPC corresponds to Figure 1 5GC 140.

[0050] gNB 110a, 110b, and ng-eNB 114 can communicate with AMF 115; for positioning functionality, AMF 115 communicates with LMF 120. AMF 115 supports the mobility of UE 105 (including cell changes and handover) and can participate in supporting signaling connections to 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. The LMF120 enables UE 105 positioning when it accesses NG-RAN 135, and supports various positioning protocols / 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 Cellular ID (E-CID), Angle of Arrival (AOA), Angle of Departure (AOD), and / or other positioning methods. The LMF120 can process location service requests for UE 105 received, for example, from AMF 115 or GMLC 125. The LMF120 can connect to AMF 115 and / or GMLC 125. The LMF120 may 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 UE 105's location) can be performed at UE 105 (e.g., using signal measurements obtained by UE 105 for 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 serve as a control node for handling signaling between UE 105 and 5GC 140 and can provide QoS (Quality of Service) streaming and session management. AMF 115 can support UE 105 mobility (including cell changes and handovers) and can participate in supporting signaling connections to UE 105.

[0051] 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, pull the location estimate from (e.g., by sending a location request to) one or more of UE 105, gNB 110a, 110b (e.g., via RU 111, DU 112, CU 113), and / or ng-eNB 114, and / or LMF 120. As another example, UE 105, one or more of 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.

[0052] GMLC 125 can support location requests for UE 105 received from external client 130 via server 150, and can forward such requests to AMF 115 for forwarding to LMF 120, or can forward them 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 implementations it may not be connected to either AMF 115 or LMF 120.

[0053] like Figure 1 Further explanation is provided: 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. This new Radio Positioning Protocol A is 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 the LMF 120, and / or between ng-eNB 114 and the LMF 120. Figure 1As further explained, 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 location 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 location methods (such as E-CID) (e.g., in conjunction with measurements obtained by gNB110a, 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 for directional SS transmissions from gNB 110a, 110b, and / or ng-eNB 114. LMF 120 can be co-located or integrated with the gNB or TRP, or it can be configured to communicate directly or indirectly with the gNB and / or TRP, located away from the gNB and / or TRP.

[0054] Using a UE-assisted positioning method, UE 105 can obtain location measurements and send 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.

[0055] Using a UE-based positioning method, UE 105 can obtain a location measurement (e.g., which may be the same as or similar to a location measurement for 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).

[0056] Using a network-based positioning method, one or more base stations (e.g., gNB 110a, 110b and / or ng-eNB 114) or APs can acquire location measurements (e.g., measurements of RSSI, RTT, RSRP, RSRQ, or Time of Arrival (ToA) of signals transmitted by UE 105) and / or can receive measurements acquired by UE 105. These base stations or APs can then transmit these measurements to a location server (e.g., LMF 120) for calculating a location estimate for UE 105.

[0057] 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 directional SS 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 5GC 140.

[0058] The LPP or NPP message sent from LMF 120 to UE 105 may instruct 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 for 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 instruct UE 105 to obtain one or more measurements (e.g., beam ID, beamwidth, average angle, RSRP, RSRQ measurements) of directional signals transmitted within a specific cell supported by one or more of gNB 110a, 110b, and / or ng-eNB 114 (or supported by some other type of base station, such as eNB or WiFi AP). UE 105 can send these measurements back to LMF 120 via service gNB110a (or service ng-eNB 114) and AMF 115 in an LPP or NPP message (e.g., within a 5G NAS message).

[0059] As mentioned, 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.) used to support and interact with mobile devices (such as UE 105) (e.g., to enable voice, data, location, and other functionalities). In some such embodiments, the 5GC 140 can be configured to control different air interfaces. For example, non-3GPP interoperability functions (N3IWF) in the 5GC 140 can be used. Figure 1 (Not shown) Connects 5GC 140 to a WLAN. For example, the WLAN may support IEEE 802.11 WiFi access for UE 105 and may include one or more WiFi APs. Here, N3IWF may connect to the WLAN and other components in 5GC 140, such as AMF 115. In some embodiments, both NG-RAN 135 and 5GC 140 may be replaced by one or more other RANs and one or more other core networks. For example, in EPS, NG-RAN 135 may be replaced by E-UTRAN containing eNBs, and 5GC 140 may be replaced by EPC containing a Mobility Management Entity (MME) instead of AMF 115, an E-SMLC instead of LMF 120, and a GMLC similar to GMLC 125. In such EPS, the E-SMLC may use LPPa instead of NRPPa to send location information to and receive location information from eNBs in the E-UTRAN, and may use LPP to support UE 105's positioning. In these other embodiments, the location of UE 105 using directional PRS can be supported in a manner similar to that described herein for 5G networks, the difference being that the functions and procedures described herein for gNB 110a, 110b, ng-eNB 114, AMF 115 and LMF120 can be applied alternatively to other network elements, such as eNB, WiFi AP, MME and E-SMLC, in some cases.

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

[0061] Also refer to Figure 2UE 200 is an example of one of UEs 105 and 106, and includes a computing platform containing a processor 210, a memory 211 containing software (SW) 212, one or more sensors 213, a transceiver interface 214 for a transceiver 215 (which includes a wireless transceiver 240 and a wired transceiver 250), a user interface 216, a satellite positioning system (SPS) receiver 217, a camera 218, and a positioning device (PD) 219. The processor 210, memory 211, sensors 213, transceiver interface 214, user interface 216, SPS receiver 217, camera 218, and positioning device 219 can be communicatively coupled to each other via a bus 220 (which can be configured for, for example, optical and / or electrical communication). One or more of the illustrated devices (e.g., camera 218, positioning device 219, and / or one or more sensors 213, etc.) can be omitted from UE 200. Processor 210 may include one or more intelligent 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-234 may include multiple devices (e.g., multiple processors). For example, sensor processor 234 may include processors for 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, one SIM (subscriber identity module or subscriber identification module) may be used by an original equipment manufacturer (OEM), and another SIM may be used by an end user of UE 200 to obtain connectivity. Memory 211 is a non-transient storage medium, which may include random access memory (RAM), flash memory, disk storage, and / or read-only memory (ROM), etc. Memory 211 stores software 212, which may be processor-readable, processor-executable software code containing instructions configured to cause processor 210 to perform the various functions described herein when executed. Alternatively, software 212 may not be directly executable by processor 210, but may be configured (e.g., when compiled and executed) to cause processor 210 to perform various functions. This description may refer to processor 210 performing functions, but this includes other implementations, such as processor 210 performing software and / or firmware implementations. This description may refer to processor 210 performing functions as a shorthand for one or more of processors 230-234 performing that function.This description may refer to the UE 200 execution function as a shorthand for one or more appropriate components of the UE 200 performing that function. The processor 210 may include memory with stored instructions as a supplement to and / or replacement of memory 211. The functionality of the processor 210 is discussed more fully below.

[0062] 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 includes one or more of processors 230-234 in processor 210, memory 211, and wireless transceiver 240. Other exemplary configurations include one or more of processors 230-234 in processor 210, memory 211, wireless transceiver, and one or more of the following: (a) sensors 213, user interface 216, SPS receiver 217, camera 218, PD 219, and / or wired transceiver.

[0063] UE 200 may include a modem processor 232, which may be 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 or alternatively, baseband processing may be performed by processor 230 and / or DSP 231. However, other configurations may be used to perform baseband processing.

[0064] UE 200 may include sensors 213, which may include one or more of various types of sensors, such as one or more inertial sensors, one or more magnetometers, one or more environmental sensors, one or more optical sensors, one or more weight sensors, and / or one or more radio frequency (RF) sensors. An inertial measurement unit (IMU) may include, for example, one or more accelerometers (e.g., collectively responding to acceleration of UE 200 in three dimensions) and / or one or more gyroscopes (e.g., three-dimensional gyroscopes). Sensors 213 may include one or more magnetometers (e.g., three-dimensional magnetometers) to determine orientation (e.g., relative to magnetic north and / or true north), which may be used for any of a variety of purposes (e.g., supporting one or more compass applications). Environmental sensors 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. Sensors 213 can generate analog and / or digital signals, and indications of these signals can be stored in memory 211 and processed by DSP 231 and / or processor 230 to support one or more applications (such as, for example, applications involving positioning and / or navigation operations).

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

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

[0067] (A) Magnetometers 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. (A) Magnetometers may include two-dimensional magnetometers configured to detect and provide indications of magnetic field strength in two orthogonal dimensions. (A) Magnetometers may include three-dimensional magnetometers configured to detect and provide indications of magnetic field strength in three orthogonal dimensions. (A) Magnetometers may provide means for sensing magnetic fields and, for example, providing magnetic field indications to processor 210.

[0068] 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. Thus, 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), WiFi, and WiFi Direct (WiFi-D). Zigbee, etc. New radios can use millimeter-wave frequencies and / or sub-6 GHz frequencies. Wired transceiver 250 may include a wired transmitter 252 and a wired receiver 254 configured for wired communication, for example, a network interface for communicating with and receiving communications from NG-RAN 135. Wired transmitter 252 may include multiple transmitters, which may be discrete components or combined / integrated components, and / or wired receiver 254 may include multiple receivers, which 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 (e.g., 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.

[0069] User interface 216 may include one or more of a number of devices, such as, for example, speakers, microphones, display devices, vibration devices, keyboards, touchscreens, etc. User interface 216 may include any device that includes more than one of these devices. User interface 216 may be configured to enable a user to interact with one or more applications stored in the main memory of 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 processor 230. Similarly, applications in the main memory of 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 systems, analog-to-digital circuitry systems, amplifiers, and / or gain control circuitry systems (any device including more than one of these devices). Other configurations of the audio I / O devices may be used. Alternatively or concurrently, 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.

[0070] SPS receiver 217 (e.g., a Global Positioning System (GPS) receiver) can 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 can be integrated with antenna 246. SPS receiver 217 can be configured to process the acquired SPS signal 260 fully or partially to estimate the location of UE 200. For example, SPS receiver 217 can be configured to determine the location of UE 200 by performing trilateration using SPS signal 260. SPS receiver 217 can be combined with general-purpose processor 230, memory 211, DSP 231, and / or one or more dedicated processors (not shown) to process the acquired SPS signal fully or partially and / or calculate the estimated location of UE 200. 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 during positioning operations. General-purpose processor 230, DSP 231, and / or one or more dedicated processors, and / or memory 211 may provide or support a position engine for processing measurements to estimate the position of UE 200.

[0071] 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 a CMOS imager), lenses, analog-to-digital circuitry, frame buffers, etc. Additional processing, conditioning, encoding, and / or compression of the signals representing the captured images may be performed by a general-purpose processor 230 and / or a DSP 231. Alternatively or additionally, a video processor 233 may perform conditioning, encoding, compression, and / or manipulation of the 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, a user interface 216.

[0072] 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 some or all of SPS receiver 217. PD 219 may appropriately cooperate with processor 210 and memory 211 to perform at least a portion of one or more location methods, although the description herein may only refer to PD 219 being configured to perform or to be performed 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 acquiring and using 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., the 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 sense the orientation and / or motion of UE 200 and provide an indication of such orientation and / or motion, and processor 210 (e.g., 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.

[0073] Also refer to Figure 3Examples of TRP 300 for gNB 110a, 110b and / or ng-eNB 114 include a computing platform containing processor 310, memory 311 including software (SW) 312, and transceiver 315. Processor 310, memory 311 and transceiver 315 can be communicatively coupled to each other via bus 320 (which can be configured for, for example, optical communication and / or electrical communication). One or more of the illustrated devices (e.g., a wireless interface) may be omitted from the TRP 300. Processor 310 may include one or more intelligent 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 such...). Figure 2 (The general-purpose / application processor, DSP, modem processor, video processor, and / or sensor processor shown). Memory 311 is a non-transient storage medium, which may include random access memory (RAM), flash memory, disk storage, and / or read-only memory (ROM), etc. Memory 311 stores 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 (e.g., when compiled and executed) to cause processor 310 to perform the functions.

[0074] This description may refer to processor 310 performing functions, but this includes other implementations, such as processor 310 performing software and / or firmware implementations. This description may refer to processor 310 performing functions as a shorthand for one or more processors included in processor 310 performing that function. This description may refer to TRP 300 performing functions as a shorthand for one or more appropriate components (e.g., processor 310 and memory 311) of TRP 300 (and thus one of gNB 110a, 110b and / or ng-eNB 114) performing that function. Processor 310 may include memory with stored instructions as a complement and / or alternative to memory 311. The functionality of processor 310 is discussed more fully below.

[0075] 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 and / or receiving wireless signals 348 (e.g., on one or more uplink channels and / or one or more downlink channels) 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. Thus, 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 support various radio access technologies (RATs) such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Telephone System), 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), WiFi, and WiFi Direct (WiFi-D). 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 send communications to and receive communications from LMF 120 (e.g., 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, for example, optical communication and / or electrical communication.

[0076] Figure 3 The configuration of TRP 300 shown is exemplary and not intended to limit this disclosure (including the claims), and other configurations may be used. For example, the description herein discusses TRP 300 being configured to perform several functions or TRP 300 performing 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).

[0077] Also refer to Figure 4 Server 400 (where LMF 120 is an example) includes a computing platform containing processor 410, a memory 411 containing software (SW) 412, and a transceiver 415. Processor 410, memory 411, and transceiver 415 are communicatively coupled to each other via bus 420 (which may be configured for, for example, optical and / or electrical communication). One or more of the illustrated devices (e.g., a wireless interface) may be omitted from server 400. Processor 410 may include one or more intelligent 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 such...). Figure 2 (The general-purpose / application processor, DSP, modem processor, video processor, and / or sensor processor shown). Memory 411 is a non-transient storage medium, which may include random access memory (RAM), flash memory, disk storage, and / or read-only memory (ROM), etc. Memory 411 stores 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 (e.g., when compiled and executed) to cause processor 410 to perform various functions. This description may refer to processor 410 performing functions, but this includes other implementations, such as processor 410 performing software and / or firmware implementations. This description may refer to processor 410 performing functions as a shorthand for one or more processors included in processor 410 performing that function. This description may refer to server 400 performing functions as a shorthand for one or more appropriate components of server 400 performing that function. Processor 410 may include memory with stored instructions as a supplement to and / or replacement of memory 411. The functionality of processor 410 is discussed more fully below.

[0078] 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 and / or receiving wireless signals 448 (e.g., on one or more downlink channels) 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. Thus, 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 support various radio access technologies (RATs) such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Telephone System), 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), WiFi, and WiFi Direct (WiFi-D). 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 send communications to and receive communications from TRP 300 (e.g., and / or one or more other 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, for example, optical communication and / or electrical communication.

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

[0080] 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. Additionally or alternatively, the description herein discusses server 400 being configured to perform several functions or server 400 performing several 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).

[0081] Positioning technology

[0082] 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 transmitted by the base station (e.g., PRS, CRS, etc.) are acquired by the UE and subsequently provided to a location server. The location server then calculates the UE's location based on these measurements 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.

[0083] UEs can use Satellite Positioning System (SPS) (Global Navigation Satellite System (GNSS)) to achieve high-precision 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.

[0084] In UE-assisted positioning, the UE sends 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) containing 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 are used to calculate the UE's positioning.

[0085] In conventional UE-based positioning, the UE calculates its own location, thus avoiding sending 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 (compared to PPP or RTK information) to make BSA information available to UEs that have not subscribed and are paying for decryption keys. 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.

[0086] 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 the LMF120). The latency for the availability of positioning-related data during positioning system initialization is called the First Time Locked (TTFF) and is greater than the latency after the TTFF. The reciprocal of the time elapsed between two consecutive availability of positioning-related data is called the update rate, i.e., the rate at which positioning-related data is generated after the first lock. 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., T ms). Other examples of capabilities that may affect latency are the number of TRPs from which the UE can process PRS, the number of PRS the UE can process, and the UE's bandwidth.

[0087] 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 Cellular Identifier (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 distance between the two entities. This distance, plus the known location of the first entity and the angle (e.g., azimuth) between the two entities, can be used to determine the location of the second entity. In multiple RTT (also known as multi-cell RTT), multiple distances from one entity (e.g., UE) to other entities (e.g., TRP) and the known locations of these other entities can be used to determine the location of this one entity. In TDOA, the travel time difference between an entity and other entities can be used to determine the relative distance to these other entities, and those relative distances, combined with the known locations of these other entities, can be used to determine the location of this 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 angle of departure of a signal, combined with the distance between devices (a distance 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 angle of departure can be an azimuth angle relative to a reference direction (such as true north). The angle of arrival or angle of departure can be a zenith angle relative to directly upward from the entity (i.e., radially outward from the Earth's center). E-CID uses the identity of the serving cell, timing advance (i.e., the difference between the receive and transmit times 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.

[0088] In network-centric RTT estimation, the serving base station instructs the UE to scan / receive RTT measurement signals (e.g., PRS) on serving cells of two or more adjacent 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 reception time, time received, 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 (probe reference signal) for positioning, i.e., UL-PRS) to these one or more base stations, and may transmit the time difference T between the ToA of the RTT measurement signal and the transmission time of the RTT response message. Rx→Tx (i.e., UE T) Rx-Tx or UE Rx-Tx This 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 difference T between the ToA of the RTT response at the base station and the time taken. Tx→Rx Time difference T with UE report Tw，Tw The base station can infer the propagation time between the base station and the UE. From this propagation time, the base station can determine the distance between the UE and the base station by assuming that the propagation time is the speed of light.

[0089] UE-centric RTT estimation is similar to network-based methods, except that the UE transmits uplink RTT measurement signals (e.g., when instructed by a serving base station), which are received by multiple base stations near the UE. Each involved base station 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 transmission time of the RTT response message from the base station.

[0090] For both network-centric and UE-centric procedures, the side performing RTT calculation (network or UE) typically (but not always) transmits first messages or signals (e.g., RTT measurement signals), 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.

[0091] Multiple RTT (Round-Trip Toll) technology can be used to determine location. For example, a first entity (e.g., a UE) may emit one or more signals (e.g., unicast, multicast, or broadcast from a base station), and multiple second entities (e.g., other TSPs, such as base stations and / or UEs) 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 distance to the second entities, and may use the multiple distances and the known locations of the second entities to determine the location of the first entity via trilateration.

[0092] 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., it 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.

[0093] 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 distance from the UE to the TRP. For example, RSTD (Reference Signal Time Difference) can be determined for PRS signals received from multiple TRPs, and these RSTDs are 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, such that a PRS signal from a more distant TRP may be overwhelmed by a PRS signal from a closer TRP, thus the signal from the more distant TRP may not be detected. 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.

[0094] Positioning Reference Signals (PRS) include a downlink PRS (DL PRS, often simply referred to as PRS) and an uplink PRS (UL PRS) (which may be referred to as the SRS (Detection Reference Signal) used for positioning). PRS may include PN codes (pseudo-random codes) or be generated using PN codes (e.g., by modulating a carrier signal with PN codes) so that the PRS source can be used as a pseudo-satellite. PN codes can be unique for a PRS source (at least unique within a specified area, such that the same PRS from different PRS sources does not overlap). PRS may include PRS resources of a frequency layer or a set of PRS resources. The DL PRS positioning frequency layer (or simply frequency layer) is a collection of DL PRS resource sets from one or more TRPs, whose PRS resources have common parameters configured by the higher-level parameters DL-PRS-PositioningFrequencyLayer (DL-PRS-PositioningFrequencyLayer), DL-PRS-ResourceSet (DL-PRS-Resource Set), and DL-PRS-Resource (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 also has a DL PRS cyclic prefix (CP) for the DL PRS resource set and DL PRS resources within that frequency layer. In 5G, a resource block occupies 12 consecutive subcarriers and a specified number of symbols. Furthermore, the DL PRS point A parameter defines the frequency of the reference resource block (and the lowest subcarrier of the resource block), 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 for each symbol, such that for comb N, every Nth resource element is a PRS resource element). The PRS resource set is identified by the 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. This does not imply at all whether the UE is aware of the base station and beam transmitting the PRS.

[0095] 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. Based 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 across a TRP, wherein these 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 resource elements (REs), which may reside in multiple resource blocks (RBs) within N (or more) consecutive symbols in a time slot. An RB is a set of REs spanning one or more consecutive symbols in the time domain and a number of consecutive subcarriers in the frequency domain (12 for 5G). Each PRS resource is configured with an RE offset, a time slot offset, a symbol offset within a time slot, and the number of consecutive symbols that the PRS resource can occupy within a time slot. The RE offset defines the initial RE offset of the first symbol within a DL PRS resource in the frequency range. The relative RE offsets of the remaining symbols within a DL PRS resource are defined based on this initial offset. The slot offset is the starting slot of the DL PRS resource relative to the slot offset of the corresponding resource set. 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).

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

[0097] 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 for transmission 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 completed once the specified number of repetitions have 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 DL PRS measurement (or even enable the UE to measure DL PRS).

[0098] Multiple frequency layers of a PRS can be aggregated to provide an effective bandwidth greater than any bandwidth of any individual layer. Multiple frequency layers belonging to component carriers (which can be coherent and / or separate) and satisfying criteria such as Quasi-coexistence (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 of arrival measurements. Stitching involves combining PRS measurements on individual bandwidth segments into a unified fragment so 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. A 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., the resolution of TDOA). An 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.

[0099] RTT positioning is an active positioning technology because RTT uses positioning signals sent by the TRP to the UE and by the UE (participating in RTT positioning) to the TRP. The TRP can send a DL-PRS signal received by the UE, and the UE can send an SRS (Probe Reference Signal) signal received by multiple TRPs. The Probe Reference Signal may be referred to as SRS or SRS signal. In 5G multi-RTT, coordinated positioning can be used, where the UE sends a single UL-SRS for positioning received by multiple TRPs, instead of sending 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 (e.g., gNB), or it can be a TRP of a single 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 distance between the UE and the 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 positioning signal is being transmitted by the UE and the PRS and SRS positioning signals 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 computational congestion at the TRP where many UEs are concurrently attempting to measure.

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

[0101] 5G NR supports various positioning technologies. Native NR 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).

[0102] Location estimation (e.g., for a UE) may be referred to by other names, such as location estimate, location, positioning, location lock, lock, etc. Location estimation can be geodetic and include coordinates (e.g., latitude, longitude, and possible altitude), or it can be municipal and include street addresses, postal addresses, or some other verbal description of location. Location estimation can be further defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possible altitude). Location estimation may include expected errors or uncertainties (e.g., by including the area or volume that the expected location would be included with a specified or default confidence level).

[0103] Angle-assisted positioning

[0104] Information about the angle of arrival of a reference signal received by the UE can be useful for several reasons. For example, knowing (e.g., by determining) the angle of arrival of the reference signal can be useful in determining the UE's location. As another example, knowing the angle of arrival of one or more reflected signals can be used for RF sensing to determine information about the UE's environment (e.g., the number, size, and / or location of objects of interest). The location of the reflector can be mapped to the object of interest. Reflections can be used, additionally or alternatively, to determine the location of a virtual base station (e.g., gNB) and improve the accuracy of the UE's location. Therefore, the UE can attempt to determine the angle of arrival of the reference signal. Having auxiliary information to facilitate the determination of the angle of arrival can be beneficial (e.g., reducing latency and / or reducing power consumption). For example, the UE can use the range of expected angles of arrival of the reference signal to reduce the search window used to receive and measure the reference signal, which may improve computational costs (e.g., latency, processing power).

[0105] Angular information from one or more reference signals can aid in multipath mitigation. For example, knowing the range of the expected angle of arrival can help with multipath mitigation, such as ignoring unwanted multipath signals and / or using multipath signals (e.g., to characterize the environment, aid in localization, etc.). Further measurements supporting multipath mitigation include timing, power K-factor, and Doppler offset measurements for the line-of-sight (LOS) path and one or more non-line-of-sight (NLOS) paths. Auxiliary data can be provided to the UE for use in determining measurements that support multipath mitigation, localization, etc. For example, the expected timing of the reference signal (e.g., the expected reception time and the uncertainty of that reception time) can be provided, thereby providing a time window for receiving the reference signal. For example, the uncertainty might be + / -32 μs for DLPRS in FR1, while for DL ​​PRS in FR2, the uncertainty might be + / -8 μs. However, to date, angular auxiliary data has not been provided to the UE.

[0106] Reference Figure 5 And further refer to Figure 1-4 UE 500 includes a processor 510, an interface 520, and a memory 530, which are communicatively coupled to each other via a bus 540. UE 500 may include... Figure 5 Some or all of the components shown, and may include one or more other components, such as Figure 2Any of the components shown herein may be used to make UE 200 an example of UE 500. Processor 510 may include one or more components of processor 210. Memory 530 is a non-transient storage medium and may include RAM, flash memory, disk memory, and / or ROM, etc. Memory 530 may store software 532, which may be processor-readable, processor-executable software code containing instructions configured to cause processor 510 to perform the various functions described herein when executed. Alternatively, software 532 may be not directly executable by processor 510 but may be configured (e.g., when compiled and executed) to cause processor 510 to perform the functions. Interface 520 may include one or more components of transceiver 215, such as wireless transmitter 242 and antenna 246, or wireless receiver 244 and antenna 246, or wireless transmitter 242, wireless receiver 244, and antenna 246. Alternatively or alternatively, interface 520 may include a wired transmitter 252 and / or a wired receiver 254. Interface 520 may include an SPS receiver 217 and an SPS antenna 262.

[0107] The description herein may refer to processor 510 performing a function, but this includes other implementations, such as the implementation of software and / or firmware (stored in memory 530) performed by processor 510. The description herein may refer to UE 500 performing a function as a shorthand for one or more appropriate components of UE 500 (e.g., processor 510 and memory 530) performing that function. Processor 510 (possibly in conjunction with memory 530 and, where appropriate, with interface 520) includes an angle capability unit 550. Angle capability unit 550 may be configured to send one or more capability messages instructing UE 500 to use angle information about a reference signal to measure the reference signal. These capability messages may indicate: one or more parameters regarding UE 500's ability to use the angle information (e.g., the angle range over which UE 500 can direct a beam to measure the reference signal relative to the angle range of UE 500), one or more frequency bands and / or combinations of one or more frequency bands corresponding to one or more other parameters regarding UE 500's ability to use the angle information, etc. This document further discusses the configuration and functionality of the angle capability unit 550, and the UE 500 (e.g., processor 510 and one or more other appropriate components, such as memory 530) is configured to perform the functions of the angle capability unit 550 discussed herein.

[0108] Reference Figure 6 And further refer to Figure 2 and 3 Network Entity 600 (which can be) Figure 3 The example of TRP 300 shown, Figure 4 The example of server 400 shown, or a combination thereof (e.g., a TRP including LMF), includes a processor 610, an interface 620, and a memory 630 communicatively coupled to each other via bus 640. Network entity 600 may include... Figure 6 Some or all of the components shown, and may include one or more other components, such as Figure 3 and / or Figure 4 Any of the components shown herein. For example, interface 620 may include one or more components of transceiver 315, such as wireless transmitter 342 and antenna 346, or wireless receiver 344 and antenna 346, or wireless transmitter 342, wireless receiver 344 and antenna 346. Additionally or alternatively, interface 620 may include wired transmitter 352 and / or wired receiver 354. Memory 630 is a non-transient storage medium, which may include RAM, flash memory, disk memory, and / or ROM, etc. Memory 630 may store software 632, which may be processor-readable, processor-executable software code containing instructions configured to cause processor 610 to perform the various functions described herein when executed. Alternatively, software 632 may not be directly executable by processor 610, but may be configured (e.g., when compiled and executed) to cause processor 610 to perform the functions. Network entity 600 may additionally or alternatively include similar components of server 400. For example, network entity 600 may be TRP 300 or server 400 and is configured to communicate with TRP 300 (e.g., send requests to it), or it may include TRP 300 and be configured to communicate with the TRP portion of network entity 600 (e.g., send requests to it).

[0109] The description herein may refer to processor 610 performing functions, but this includes other implementations, such as implementations of software and / or firmware (stored in memory 630) performed by processor 610. The description herein may refer to network entity 600 performing functions as a shorthand for one or more appropriate components of network entity 600 (e.g., processor 610 and memory 630) performing the function. Processor 610 (possibly in conjunction with memory 630 and, where appropriate, with interface 620) includes angle information unit 650. Angle information unit 650 may be configured to request TRP 300 to send reference signal angle information to UE 500 for use by UE 500 when measuring one or more reference signals. For example, if network entity 600 is TRP 300, angle information unit 650 may request one or more other parts of network entity 600 to send reference signal angle information to UE 500. The reference signal angle information may, for example, identify one or more specific signals, identify one or more reference signal frequency bands, explicitly or implicitly indicate the arrival angle window of the corresponding reference signal, indicate the position corresponding to each reference signal and arrival angle window, and / or indicate the effective time associated with each reference signal and arrival angle window. The configuration and functionality of the angle information unit 650 are further discussed herein, and network entity 600 (e.g., processor 610 and one or more other appropriate components, such as memory 630) is configured to perform the functions of the angle information unit 650 discussed herein.

[0110] Reference Figure 7A and 7B and further reference Figure 5 and 6 Network entity 600 (here shown as a TRP that may include, for example, the LMF) may send a reference signal to UE 500. The reference signal may follow a LOS path 710, which is composed of an azimuth angle 720(θ) and a zenith angle... The angle of arrival is used to represent the position of the incident light on UE 500. UE 500 is... Figure 7A and 7B The orientation shown is an example, as the UE 500 can be rotated to a wide variety of possible orientations. Azimuth θ and zenith angle... The xy plane is determined relative to the Earth's surface. Assuming the Earth is a perfect sphere, the xy plane is tangent to this sphere at the location of UE 500, and the z-axis is the normal to the xy plane. In addition to LOS path 710, the reference signal may additionally (or alternatively) follow NLOS path 740, which is emitted from network entity 600 and reflected from object 750 before being received by UE 500. The AoA of the reference signal from NLOS path 740 (the reflection path) will generally be different from the AoA of LOS path 710 (although the AoA of LOS path 710 and the AoA of NLOS path 740 may be within the same AoA range). Although Figure 7B The diagram illustrates an NLOS path and a reflecting object, and a reference signal is discussed as being transmitted from network entity 600 to UE 500. However, multiple reference signals may be transmitted and / or a reference signal may take multiple NLOS paths to a destination location (e.g., to UE 500), such as being reflected from different objects, being reflected from multiple objects in one NLOS path, etc.

[0111] Also refer to Figure 8Multiple receive signal paths 801, 802 can be provided in UE 500. One or more transducers 810, 820 can be coupled to one or more corresponding tuners 811, 821 (the corresponding tuners 811, 821 can be coupled to one or more corresponding phase shifters 812, 822, the corresponding phase shifters 812, 822 can be coupled to one or more filters 813, 823 and one or more filters 814, 824) to receive one or more signals from one or more desired AoA and provide the signals(s) to processor 510, for example, for measurement. The tuners 811, 821, the phase shifters 812, 822 and the filters 813, 814, 823, 824 are optional and any one or more of these entries can be omitted. The tuners 811, the phase shifters 812 and the filters 813, 814 provide two receive signal paths 801. Transducers 810 may include one or more antenna panels. Tuners 811 may be adjusted under the control of processor 510 such that transducers 810 are tuned to receive different frequencies (e.g., signals in different frequency bands). Phase shifters 812 may be controlled by processor 510 to provide different phase shifts to transducers 810 to guide the beam of transducers 810. Filters 813, 814 may be configured to block or allow desired signal frequencies and may be controlled by processor 510 to change which frequencies are blocked / allowed. Transducers 820, tuners 821, phase shifters 822, and filters 823, 824 are configured to provide functionality similar to that of transducers 810, tuners 811, phase shifters 812, and filters 813, 814. One or more of the receiving signal paths 801 and 802 can be modified to receive signals of different frequencies and / or different angles of arrival at different times, for example, by changing the phase shift and / or frequency filter applied to the received signal. The receiving signal paths 801 and 802 shown are examples, and other configurations are possible.

[0112] Reference Figure 9 The processing and signal flow for determining location information 900 includes the stages shown. Process 900 is an example, and stages can be added, removed, and / or rearranged within process 900.

[0113] At stage 905, network entity 600 can obtain reference signal angle information. For example, network entity 600 can collect crowdsourced information by analyzing channel paths (e.g., delay, angle, path gain, etc.) across multiple signals (e.g., multiple PRS beams and / or multiple SRS beams (ports)), analyzing this information regarding the location where the information was collected, and so on. Network entity 600 can analyze this information to determine the angle of arrival (AoA) corresponding to different signals (e.g., different reference signal channels). The determined information may include the AoA of the LOS signal and the AoA of the NLOS signal reflected before reaching the corresponding location.

[0114] In phase 910, UE 500 (e.g., angle capability unit 550) sends an angle capability message 912 to network entity 600 via interface 520. The angle capability message 912 may indicate whether UE 500 is capable of using angle information to assist in measuring reference signals (e.g., to determine the AoA of a reference signal). The angle capability message 912 may include one or more parameters regarding UE 500's ability to use angle information, such as one or more parameters regarding UE 500's ability to measure the angle of one or more reference signals. The angle capability message 912 may provide information about UE 500's ability to use angle information for different frequencies (e.g., frequency bands, combinations of frequency bands), for example, because UE 500 may have different numbers and / or types of antennas with different performance characteristics for different frequencies. Different numbers and / or types may provide different beamguiding capabilities, such as a specific angle relative to the body of UE 500.

[0115] Also refer to Figure 10Example angle capability message 1000 includes an angle usage capability field 1010, a frequency band combination field 1020, a frequency band field 1030, an angle range field 1040, and a precision field 1050. The value in the angle usage field 1010 can indicate whether the UE 500 can use angle information (e.g., an angle search window) to measure a reference signal. The value of the angle usage capability field 1010 can be encoded, for example, with a single bit having a value of 1 and a value of 0, where a value of 1 indicates that the UE 500 can use the angle information, and a value of 0 indicates that the UE 500 will not use the angle information to measure the reference signal (e.g., in the corresponding frequency band combination and / or frequency band indicated by fields 1020 and 1030). The frequency band combination field 1020 indicates one or more frequency bands corresponding to the angle usage capability indication in the angle usage capability field 1010. The frequency band field 1030 indicates one or more frequency bands corresponding to the angle usage capability indication in the angle usage capability field 1010 and the frequency band combinations (if any) indicated in the frequency band combination field 1020. Therefore, for example, within the frequency band combination indicated in field 1020, a frequency band can be indicated in field 1030 for the UE 500's angular usage capability with respect to the indicated frequency band within the corresponding indicated frequency band combination. The UE 500's ability to use angular information (e.g., for different frequency band combinations and / or different frequency bands) can depend on the number of antennas and / or antenna panels (e.g., different positions of one or more antenna elements on the UE 500) and the performance of(e.g., (e.g.,) potential scan angles). The angle range field 1040 can indicate the angular range or field of view (FOV) at which the UE 500 can guide the antenna beam for the corresponding frequency band combination and / or corresponding frequency band. For example, the value of the angle range field 1040 can indicate the maximum sweep angle of the antenna beam corresponding to the frequency band combination indicated in field 1020 and / or the frequency band indicated in field 1030. A value of 360° in the angle range field 1040 can indicate that there is no angle sweep limitation for the corresponding frequency band combination and / or frequency band. The value of the accuracy field 1050 can provide one or more parameters regarding the accuracy of the positioning information (e.g., one or more measurements, one or more positioning estimates, etc.) to be provided (e.g., requested) by the UE 500. Fields 1020, 1030, 1040, and 1050 are optional, and one or more of fields 1020, 1030, 1040, and 1050 can be omitted. Furthermore, the indication that the UE 500 cannot use angle information can be defaulted, and the capability message 1000 can omit any value in the angle usage capability field 1010 indicating that the UE 500 cannot use angle information to measure the reference signal. The lack of angle usage capability can be indicated by a 0° angle range.The angle usage capability field 1010 can be omitted, for example, where the ability of UE 500 to use angle information to measure a reference signal is implied by providing a non-zero value for one or more of fields 1020, 1030, and 1040. Capability message 1000 is an example, and many other configurations of capability messages can be used.

[0116] Refer again Figure 9 In phase 920, network entity 600 obtains the location of UE 500. Network entity 600 may use one or more of a variety of techniques to determine a coarse location of UE 500. For example, network entity 600 may use the location of serving TRP 300, or the cell sector center of the serving cell, or may use E-CID or another technique to determine the UE's location. Network entity 600 may determine the location of UE 500 by combining locations determined using one or more techniques (e.g., using a weighted average). Network entity 600 may determine the future predicted location of UE 500, for example, based on the movement of UE 500 (especially relative to TRP 300). The speed of UE 500 may be used by network entity 600 to determine the predicted location of UE 500 and may be used (as discussed further below) to determine the effective time of auxiliary information provided to UE 500.

[0117] In phase 930, network entity 600 (e.g., angle information unit 650) may request TRP 300 to use or transmit reference signal angle information. For example, in sub-phase 932, angle information unit 650 may request TRP 300 (e.g., a TRP portion of network entity 600 or a separate TRP 300) to use the reference signal angle information for AoA measurement of UL PRS from UE 500. Alternatively or additionally, angle information unit 650 may request TRP 300 to send and TRP 300 to UE 500 a reference signal angle information message 934. For example, network entity 600 may send the request via interface 620 to TRP 300 that sends the message to UE 500, or, if network entity 600 includes TRP 300 or TRP 300, angle information unit 650 may request a TRP portion of network entity 600 to send the reference signal angle information message 934 to UE 500. The reference signal angle information used by network entity 600 in sub-phase 932 may be the same as or similar to the content of reference signal angle information message 934. Reference signal angle information message 934 may include auxiliary information for UE 500 to use when measuring reference signals, for example, to determine the angle of arrival of the measured signal. The description herein may refer to reference signals, but this includes one or more reference signals. Reference signal angle information message 934 may include one or more information elements (IEs) for conveying reference signal angle information (such as DL-PRS expected AoA and / or AoD). AoA may include azimuth (e.g., azimuth 720°) and / or zenith angle (e.g., ZoA (angle of arrival at zenith)) (e.g., zenith angle 730°), and AoD may include azimuth and / or zenith angle (e.g., ZoD (angle of departure at zenith)). IEs may include DL-PRS expected uncertainty, which may be combined with the expected angle to provide a search window. Alternatively or concurrently, endpoints of the search window (e.g., low-end and high-end angles) may be provided to enable the UE 500 to search for a reference signal between the low-end and high-end angles. (Etc.) IEs may include positions corresponding to each indication of the angle search window. An endpoint or expected angle plus uncertainty provides an explicit search window. However, the angle search window may be implicit (e.g., providing an expected angle and the uncertainty around the expected angle is implicit). Angle uncertainty may be implicit, for example, by statically and / or dynamically configuring uncertainty in the UE 500 and network entity 600. The UE 500 may be statically configured (e.g., hard-coded during the manufacture of the UE 500) and / or dynamically configured (e.g., by receiving instructions with configuration or instructions about which angle uncertainty from a set of statically configured configurations to use).

[0118] The RS angle information message 934 can be sent to one or more UEs 500. For example, UEs within an area can benefit from the same RS angle information message 934, such as being able to use at least some of the same angle assistance data to help narrow the search window. Network entity 600 can cause TRP 300 (e.g., the TRP portion of network entity 600) to broadcast the RS angle information message 934 and / or send the RS angle information message 934 in a multicast message. UEs 500 that are to receive the RS angle information message 934 can be grouped, for example, where each UE in a group is assigned a shared group ID and uses that group ID to broadcast the RS angle information message 934, or the RS angle information message 934 can be multicast to UEs 500 with the same group ID.

[0119] Also refer to Figure 11 The content of the reference signal angle information message 934 can be selected from the reference signal angle information table 1100, which includes the reference signal field 1110, the position field 1120, and the angle auxiliary data field 1130. Table 1100 includes various example values ​​for fields 1110, 1120, and 1130, some of which have different formats for the same field. Table 1100 is an example, and other configurations of the reference signal angle information message can be used, for example, where the same format for the values ​​of a given field is used for different (e.g., all) entries. The reference signal angle information table 1100 includes entries 1151, 1152, 1153, 1154, 1155, and 1156, where each of entries 1151-1156 includes a value for each of fields 1110, 1120, and 1130.

[0120] Network entity 600 may indicate reference signals to UE 500 in various ways based on values ​​obtained from Table 1100. For example, as shown in entry 1151, reference signal field 1110 may indicate a channel. Channel indication may include one or more parameters for the channel (e.g., frequency layer) to define the reference signal. As another example, as shown in entries 1152 and 1153, reference signal field 1110 may indicate a frequency band such that all reference signals within the indicated frequency band will have corresponding positions and auxiliary data (i.e., as indicated by other fields 1120 and 1130 of the same entry). As another example, as shown in entries 1154 and 1155, reference signal field 1110 may indicate a combination of frequency bands such that all reference signals within the indicated combination of frequency bands will have corresponding positions and auxiliary data (and possibly valid times). As another example, as shown in entry 1156, reference signal field 1110 may indicate a specific signal, here PRS1. Specific signal indicators may include one or more parameters used to define the signal (e.g., frequency layer, slot offset, symbol offset, number of comb teeth, etc.).

[0121] Each entry in entries 1151-1156 of the reference signal angle information table 1100 includes the location to which the entry applies, for example, the location to which angle auxiliary data applies. The location can be a specific point (e.g., x, y, and z coordinates, or latitude and longitude, etc.) or a region (e.g., a point with a radius, or a defined boundary (e.g., a rectangle, a circle, or other regular or irregular shape)).

[0122] The Angle Auxiliary Data Field 1130 of each of the entries 1151-1156 provides angle information that the UE 500 and / or TRP 300 can use to measure one or more signals (e.g., a reference signal). For example, the angle information can provide a specific angle (e.g., the average or expected angle of arrival of the (reference) signal), as shown in entry 1151. The angle may include azimuth (θ) and may also include zenith angle. As another example, angle information can include a search window in the form of an expected angle and uncertainty, for example, as shown in entry 1152. The uncertainty can be specified by a signal uncertainty value and thus symmetrical about the expected angle (e.g., + / -A°), or it can be specified by lower and higher uncertainties (e.g., +B°, -C) such that the uncertainty can be asymmetrical about the expected angle. As another example, angle information can provide a search window by specifying the boundaries of the search window. As shown in entry 1153, angle auxiliary data specifies a window having an azimuth range from M° to N° and a zenith range from P° to Q°. Generally, angle window values ​​are indicated as angle window 1, angle window 2, and angle window 3 in entries 1154-1156, respectively.

[0123] The angles in the angle assistance data 1130 may include the angle of arrival at the UE location and / or TRP location. The angle assistance data provides the expected angle of arrival of a reference signal at the intended UE location. Processor 610 or processor 310 may use these angles to determine the corresponding angle of arrival of a reference signal from a corresponding location at TRP 300 (e.g., separate from or part of network entity 600). Alternatively or additionally, the angle assistance data 1130 may include the expected angle of arrival of a reference signal transmitted by UE 500 from the intended location at one or more TRPs. For example, TRP 300 of network entity 600 may use the angle assistance data 1130 to narrow the angle search window from UE 500's UL PRS, for example, for AoA-based positioning.

[0124] Network entity 600 is configured to obtain values ​​from reference signal angle information table 1100. For example, network entity 600 can obtain reference signal angle information as discussed above with respect to stage 905. Network entity 600 can determine the angle of arrival corresponding to different signals (e.g., different reference signal channels) to generate table 1100, from which network entity 600 can select information for reference signal angle information message 934.

[0125] Network entity 600 can be configured to generate or request TRP 300 to generate the reference signal angle information message 934 only when network entity 600 receives an angle capability message 912 indicating that UE 500 can use angle information to measure at least one reference signal. For example, network entity 600 can generate message 934 and / or request TRP 300 to generate message 934 in response to receiving angle capability message 912 and in response to angle capability message 912 indicating that UE 500 can use angle information of at least one reference signal to receive and / or measure the reference signal. Network entity 600 can be configured to generate or request the generation of message 934 in response to UE 500 indicating that UE 500 can use angle information of at least one reference signal to be transmitted by TRP 300.

[0126] Also refer to Figure 12Network entity 600 can select reference signal angle information to be used by the network entity in sub-phase 932 and / or for use in reference signal angle information message 934. For example, network entity 600 can request TRP 300 to generate reference signal angle information message 934 (e.g., message 1200) by selecting information from table 1100 and potentially providing additional information for entries in message 1200 (here, entries 1251, 1252). Message 1200 is an example of message 934 (or reference signal angle information used at sub-phase 932) and includes a reference signal field 1210, a position field 1220, an auxiliary data field 1230, and an effective time field 1240. Fields 1210, 1220, and at least a portion of field 1230 can be populated with information selected from table 1100. For example, network entity 600 (e.g., angle information unit 650) can use the determined (e.g., predicted) location of UE 500 to identify one or more entries in table 1100, the location of which includes the determined location of UE 500. Alternatively, network entity 600 can provide auxiliary data related to one or more locations that are supplementary to and / or different from the predicted location of UE 500 (e.g., providing auxiliary data for the area around UE 500). Network entity 600 can determine which reference signals TRP 300 will transmit corresponding to the identified entries, and the angle information of which reference signals UE 500 can use (based on angle capability message 912), and generate one or more entries in message 1200, which include the reference signals to be transmitted and the corresponding locations for which UE 500 can use its angle information. Alternatively, message 1200 can include a location indication indicating the area where angle auxiliary data can (or should) be used. Angle information unit 650 can populate auxiliary data field 1230 with angle auxiliary data from entries identified in Table 1100. Angle information unit 650 may include AoD information in auxiliary data field 1230 as a supplement to or replacement of AoA. AoD information may indicate the origin angle of the corresponding reference signal, which UE 500 can use for RF sensing and / or multipath positioning. For example, UE 500 can use the AoD of the measured signal to help determine the position of a reflecting object and / or use the reflected signal to help determine the position of UE 500.

[0127] One or more values ​​of the auxiliary data field 1230 may depend on one or more parameters (e.g., quality, latency, and / or accuracy) of the location information to be provided by the UE 500. For example, a smaller latency requirement allows for a smaller angle window to be provided. As another example, auxiliary data may be provided in response to a threshold level requiring accuracy, and not in other ways, such as when only a rough location of the UE 500 is requested.

[0128] In addition to angle auxiliary data, auxiliary data field 1230 may also include delay auxiliary data. Network entity 600 may request timing information from TRP 300 so that, in addition to helping UE 500 narrow the AoA search window for the reference signal to be measured, UE 500 can also narrow the time search window for the reference signal to be measured. Similar to angle information, timing information may be provided as the start and end times of the window, as a reference time point and time uncertainty (symmetric or asymmetric) for determining the window, as a reference time with implicit uncertainty, etc. Timing information may be provided jointly with angle information, as shown in the figure, or it may be provided independently of angle information, and UE 500 (e.g., processor 510) may analyze corresponding information (e.g., position, reference signal) to obtain angle and timing information for joint use, for example, searching and measuring the reference signal. Although the discussion herein frequently refers to reference signals, it is applicable to signals other than reference signals.

[0129] The valid time field 1240 of each of entries 1251 and 1252 provides a valid time for the auxiliary data field 1230. Angle information can change rapidly, for example, due to movement of UE 500 relative to TRP 300. Moreover, angle information can be very base station specific, thus varying significantly from base station to base station (e.g., due to different relative movements of UE 500 to different base stations, such as relative to the LOS path from UE 500 to different base stations). For example, if UE 500 is moving approximately directly toward or approximately directly away from TRP 300, the angle information may change little even if it changes for the LOS signal; however, if UE 500 is moving partially or approximately laterally to the LOS of TRP 300, the angle information may change rapidly, especially as UE 500 gets closer to TRP 300. Therefore, network entity 600 can request TRP 300 to include a valid time value for message 1200 or for each entry of message 1200. Different entries in message 1200 may include different valid times because angle information can change at different rates for different reference signals (e.g., due to different paths, especially different NLOS paths). Valid time values ​​(e.g., time 1 in entry 1251 and time 2 in entry 1252) indicate the valid time of the corresponding auxiliary data in auxiliary data field 1230 (at least the angle information in auxiliary data field 1230). Valid times can be specified in various ways, such as a timer value for the time after message 1200 is received, or a specific future time (e.g., time of day). Valid times indicate the time after which UE 500 (or network entity 600 at sub-phase 932) should not use the corresponding auxiliary data, or at least after which the auxiliary data may not help narrow down the angle and / or time of the search reference signal. The values ​​of (various) valid times may depend on the expected rate of change of the (reference) signal's AoA. The values ​​of the effective time(s) can depend on a variety of factors, including the distance between UE500 and TRP 300, the speed of UE500, the direction of movement of UE500 relative to TRP 300 (e.g., relative to the LOS path between UE500 and TRP 300, and the rate of change of AoA of that LOS path), etc. For example, if UE500 is close to TRP 300 and / or is moving rapidly laterally along the LOS path, the effective time may be much shorter than if UE500 is stationary, moving slowly, and / or moving close to the LOS path.

[0130] Ancillary data can be repeatedly updated. For example, to accommodate rapid changes in angle auxiliary information, network entity 600 may request TRP 300 to repeatedly, frequently, and rapidly send RS angle information messages 934. RS angle information messages 934 may be sent to UE 500 periodically and / or non-periodically (e.g., on demand) along with updated information. RS angle information messages 934 may be sent to UE 500, for example, using lower-layer (low latency) communication, such as MAC-CE (Media Access Control-Control Element), especially where network entity 600 includes LMF (Local LMF in RAN). Updated RS angle information messages may be provided, for example, before the expiration of RS angle information message 934 (e.g., the most recently sent RS angle information message, or at least the most recently sent RS angle information message containing auxiliary information for a reference signal to the updated RS angle information message).

[0131] At stage 940, TRP 300 sends RS configuration message 942 to UE 500. RS configuration message 942 contains one or more parameters for RS configuration, such as time slot offset, comb tooth number, frequency offset, frequency layer DCI message, etc. UE 500 uses the RS configuration information to help measure the reference signal, for example, by properly tuning one or more antennas, and uses auxiliary data to reduce the search direction and / or search time for the reference signal.

[0132] At stage 950, TRP 300 sends one or more RS 952 to UE 500. TRP 300 sends RS based on RS configuration message 942, for example, with the indicated parameters, and possibly in the direction indicated by AoD information in auxiliary data.

[0133] At stage 960, UE 500 determines location information based on the received RS. For example, UE 500 may measure the PRS from TRP 300 to determine location information (e.g., RSRP, ToA, SINR, location estimate, etc.). UE 500 may send some or all of the determined location information to network entity 600 (e.g., to TRP 300 or via TRP 300 to server 400) in location information message 962. UE 500 may be configured (dynamically or statically) to report only (e.g., in response to receiving an indicated angle measurement window) reference signal measurements measured within the indicated angle window. For example, for RF sensing, narrowing the target list may be beneficial. Alternatively or alternatively, UE 500 may be configured (dynamically or statically) to report both reference signal measurements measured within the indicated angle window and reference signal measurements measured outside the indicated angle window. UE 500 may be configured to indicate that the reference signal for which the angle window was provided was received outside the indicated angle window. UE 500 may be configured to indicate that the provided auxiliary data is invalid and / or incorrect. Additionally or alternatively, UE 500 may be configured to provide feedback to network entity 600 to assist network entity 600 in determining auxiliary data. For example, UE 500 may be configured to provide suggested auxiliary data to network entity 600 based on the AoA of the received reference signal. The suggested auxiliary data may be, for example, the actual AoA of the received reference signal and / or an angle search window including the actual AoA of the received reference signal. For example, message 962 may indicate that the channel X reference signal was received at an azimuth angle AoA of Y° (and possibly indicate that the reference signal was received at a zenith angle AoA of Z°).

[0134] At stage 970, network entity 600 can determine location information. Network entity 600 (e.g., LMF) can determine the range and / or location estimate of UE500, for example, based on location information message 962 and possibly based on one or more other messages with other measurement information.

[0135] operate

[0136] Reference Figure 13 And further refer to Figure 1-12 The signal measurement assistance method 1300 includes the stages shown. However, method 1300 is merely an example and not a limitation. Method 1300 can be modified, for example, by having stages added, removed, rearranged, combined, executed concurrently, and / or by splitting a single stage into multiple stages.

[0137] At stage 1310, method 1300 includes obtaining reference signal angle information including a first indication indicating a first reference signal and a first expected angle of arrival for the first reference signal. For example, angle information unit 650 may retrieve reference signal angle information including one or more indications for one or more reference signals and corresponding angle auxiliary data from table 1100 stored in memory 630 (e.g., according to message 1200), or receive such information via interface 620 (e.g., collecting crowdsourced information). Processor 610 (possibly in conjunction with memory 630, possibly in conjunction with interface 620 (e.g., wireless receiver 344 and antenna 346, wired receiver 354, wireless receiver 444 and antenna 446, and / or wired receiver 454)) may include means for obtaining reference signal angle information.

[0138] At stage 1320, method 1300 includes at least one of the following operations: requesting a transmit / receive point (TRP) to transmit a first indication to the user equipment; or requesting the TRP to search for a first reference signal based on a first expected angle of arrival. For example, angle information unit 650 may request interface 620 to send a request to a separate TRP 300 (which is part of network entity 600) or via interface 620 (e.g., wired transmitter 452) to cause the TRP 300 to transmit the first indication (e.g., the value of at least portions of reference signal 1110 and auxiliary data 1130, or the value of at least portions of fields 1210, 1230 of message 1200). Processor 610 (possibly in conjunction with memory 630 and possibly with interface 620 (e.g., wireless transmitter 442 and antenna 446, and / or wired transmitter 452)) may include means for requesting the TRP to transmit the first indication. Alternatively or concurrently, the angle information unit 650 may request the TRP 300 (e.g., the TRP portion of network entity 600) to search for one or more reference signals based on one or more expected angles of arrival (EAAs) of one or more reference signals. For example, the angle information unit 650 may use the values ​​of at least portions of reference signal 1110 and auxiliary data 1130 (e.g., the values ​​of at least portions of fields 1210 and 1230 of message 1200, regardless of whether message 1200 is generated) to establish one or more search windows for one or more reference signals. The processor 610 (possibly in conjunction with memory 630) may include means for requesting the TRP to search for a first reference signal based on a first EA.

[0139] Implementations of method 1300 may include one or more of the following features. In an example implementation, method 1300 includes at least one of the following operations: requesting the TRP to transmit a valid time indication associated with the first indication to the user equipment; or providing the valid time indication to the TRP. For example, if network entity 600 is or includes TRP 300, angle information unit 650 may cause an interface (e.g., wireless transmitter 342 and antenna 346) to send a valid time field 1240 in message 1200. As another example, if the network entity is server 400, angle information unit 650 may send a request to TRP 300 via interface 620 (e.g., wired transmitter 452) to cause the TRP to send a valid time indication. As another example, if network entity 600 includes TRP 300, angle information unit 650 may provide a valid time indication to TRP 300. Processor 610 (possibly in conjunction with memory 630 and possibly with interface 620) may include means for requesting TRP to transmit a valid time indication and / or means for providing a valid time indication to TRP. In another example implementation, method 1300 includes determining a value for the valid time indication based on the motion of the user equipment relative to TRP. For example, processor 610 may calculate the valid time indication or select a valid time indication from a set of predefined valid time value options. Processor 610 may determine the value of the valid time, for example, based on the expected rate of change of the expected AoA of the LOS path between TRP 300 and UE 500 (e.g., based on the velocity and orientation of UE 500 (e.g., angular velocity relative to TRP 300)). As another example, processor 610 may determine the value of the valid time based on the velocity of UE 500, for example, without determining the rate of change of AoA at UE 500. Processor 610 (possibly in conjunction with memory 630 and possibly with interface 620) (e.g., to obtain UE motion information) may include means for determining the value of the valid time indication.

[0140] Additionally or alternatively, implementations of method 1300 may include one or more of the following features. In an example implementation, the first indication further indicates a first position, and the reference signal angle information further includes a second indication indicating a first reference signal, a second expected angle of arrival of the first reference signal, and a second position, and the method further includes: acquiring the user equipment position of the user equipment; and selecting the first indication from the reference signal angle information based on the user equipment position corresponding to the first position. For example, the first indication may also include an indication to position field 1120, whereby processor 610 can acquire (e.g., calculate or receive) the (current or future (e.g., predicted)) position of UE 500, and can select the first indication corresponding to the position of UE 500 (e.g., the position containing UE 500) from a plurality of possible sets (e.g., table entries) of such indications (e.g., stored in a table such as table 1100). Processor 610 (possibly in conjunction with memory 630, possibly in conjunction with interface 620 (e.g., radio receiver 344 and antenna 346, radio receiver 444 and antenna 446, and / or wired receiver 454)) may include means for obtaining the location of the user equipment. Processor 610 (possibly in conjunction with memory 630) may include means for selecting a first indication. In another example implementation, method 1300 includes requesting the TRP to transmit the first indication to the user equipment as either a MAC layer message or a physical layer message. For example, network entity 600 may repeatedly obtain the location of UE 500, determine RS angle information message 934 based on these locations, and transmit RS angle information message 934 to UE 500, for example, using low latency communication (such as MAC-CE or physical layer messaging).

[0141] Additionally or alternatively, implementations of method 1300 may include one or more of the following features. In one example implementation, the first indication indicates a first expected angle of arrival (AoA) of the first reference signal as a first angle search window including the first expected AoA of the first reference signal. For example, RS angle information message 934 may include an angle search window (e.g., expected AoA and uncertainty, or start and end angles across the expected AoA), as shown in entries 1151-1153, for example. AoA may include azimuth and possible zenith angle. In another example implementation, the reference signal angle information further includes a second indication indicating the first reference signal and a second expected AoA of the first reference signal, the first expected AoA being different from the second expected AoA, and at least one of the first and second expected AoA corresponding to a non-line-of-sight path between the TRP and the user equipment. For example, multiple indications for the reference signal with multiple corresponding expected AoA may be provided in the RS angle information (e.g., RS angle information message 934), wherein at least one NLOS expected AoA is included in the RS angle information. In another example implementation, acquiring reference signal angle information includes analyzing reference signal measurements and the position corresponding to those measurements. For example, processor 610 may compile the reference signal angle information for use as auxiliary data from crowdsourced measurements of the reference signal. Processor 610 (possibly in conjunction with memory 630) may include means for analyzing the reference signal measurements and position. In another example implementation, method 1300 includes requesting the TRP to transmit a first instruction to the user equipment in response to receiving a capability message from the user equipment indicating that the user equipment is configured to use angle of arrival information to measure the reference signal. For example, processor 610 may request interface 620 or a separate TRP 300 to transmit angle auxiliary information in response to a UE 500 report (possibly only if the UE 500 reports) of the capability to receive (and measure) the reference signal using angle auxiliary information. In another example implementation, the user equipment is a first user equipment, and the method includes requesting the TRP to transmit the first instruction to both the first and second user equipment in at least one of a multicast message or a broadcast message. For example, the angle information unit 650 may request separate TRPs 300 or TRPs 300 as part of network entity 600 to send multicast or broadcast messages with a first indication (e.g., for use when reducing the angle search window used to measure one or more reference signals) to multiple UEs 500. The processor 610 (possibly in conjunction with memory 630, possibly in conjunction with interface 620 (e.g., wireless transmitter 442 and antenna 446, or wired transmitter 452)) may include means for requesting TRPs to transmit multicast and / or broadcast messages.

[0142] Reference Figure 14 And further refer to Figure 1-12 The method 1400 for measuring a reference signal at the user equipment includes the phases shown. However, method 1400 is merely an example and not a limitation. Method 1400 can be modified, for example, by having phases added, removed, rearranged, combined, executed concurrently, and / or by splitting a single phase into multiple phases.

[0143] In phase 1410, method 1400 includes transmitting an angle usage capability message from a user equipment to a network entity, the angle usage capability message indicating the user equipment's ability to use signal angle information to measure a signal. For example, UE 500 (e.g., angle capability unit 550) may send angle capability message 912, such as message 1000 or one or more entries of a similar message, to network entity 600 via interface 520. Processor 510 (possibly in conjunction with memory 530 and interface 520 (e.g., wireless transmitter 242 and antenna 246)) may include means for transmitting the angle usage capability message.

[0144] At stage 1420, method 1400 includes receiving a reference signal indication from a network entity at the user equipment, the reference signal indication indicating a reference signal and at least one reference signal angle search window corresponding to the reference signal. For example, UE 500 may receive an RS angle information message 934 from network entity 600 (which may be the same entity to which UE 500 sends angle capability message 912 or may be a different entity). Message 934 may indicate one or more parameters (e.g., frequency and / or channel) of the reference signal. The reference signal angle search window may be implicit (e.g., based on the provided expected AoA and pre-coded uncertainty) or explicit. Processor 510 (possibly in conjunction with memory 530 and interface 520 (e.g., wireless receiver 244 and antenna 246)) may include means for receiving the reference signal indication.

[0145] At stage 1430, method 1400 includes searching for the reference signal at a user equipment based on the at least one reference signal angle search window. For example, processor 510 may control interface 520, such as one or more antenna panels or one or more antennas. For example, processor 510 may control one or more components of one or more of the receive signal paths 801, 802 (e.g., transducers 810, tuners 821, phase shifters 812, and / or filters 813, 814, 823, 824) to search for the reference signal based on the reference signal angle search window, such as searching across each AoA of the search window. Processor 510 (possibly in conjunction with memory 530, possibly in conjunction with interface 520 (e.g., wireless receiver 244 and antenna 246, including one or more of the receive signal paths 801, 802) may include means for searching for the reference signal.

[0146] At stage 1440, method 1400 includes measuring the reference signal at the user equipment. For example, processor 510 may measure one or more parameters (e.g., RSRP, RSSI, ToA, etc.) of the reference signal received by searching for the reference signal (e.g., as discussed herein). Processor 510 (possibly in conjunction with memory 530 and interface 520 (e.g., wireless receiver 244 and antenna 246)) may include means for searching for the reference signal.

[0147] Implementations of method 1400 may include one or more of the following features. In one example implementation, method 1400 includes reporting a measurement of the reference signal only if the reference signal is received within at least one reference signal angle search window. For example, processor 510 may be configured not to report (and may not measure) any reference signal received outside the indicated angle search window. Processor 510 (possibly in conjunction with memory 530 and interface 520 (e.g., wireless transmitter 242 and antenna 246)) may include means for reporting measurements of the reference signal. In another example implementation, method 1400 includes reporting measurements of the reference signal regardless of whether the reference signal is received outside at least one reference signal angle search window. For example, processor 510 may be configured to report measurements of any reference signal received within or outside the indicated angle search window. In another example implementation, method 1400 includes transmitting an error message from user equipment to a network entity indicating that the user equipment failed to receive the reference signal within the at least one reference signal angle search window. For example, processor 510 may be configured to send an indication via interface 520 that a reference signal has not arrived in a search window at an indicated angle. Processor 510 may send this error message to the same entity providing the search window and / or to another entity. The error message may include the actual angle of arrival of the reference signal received by UE 500. Processor 510 (possibly in conjunction with memory 530 and interface 520 (e.g., wireless transmitter 242 and antenna 246)) may include means for transmitting the error message.

[0148] Additionally or alternatively, implementations of method 1400 may include one or more of the following features. In one example implementation, the angle utilization capability message indicates at least one of the following: the frequency band to which the user equipment's capability to use signal angle information to measure a signal applies; or a combination of frequency bands to which the user equipment's capability to use signal angle information to measure a signal applies. For example, angle capability unit 550 may generate angle capability message 912 to instruct UE 500 to use angle information to search for a reference signal on a per-band and / or per-band combination basis. In another example implementation, method 1400 includes: determining at the user equipment whether the validity period indicated by the reference signal has expired, and searching for the reference signal according to at least one reference signal angle search window is performed based on the fact that the validity period indicated by the reference signal has not expired. For example, RS angle information message 934 may include one or more validity periods, and processor 510 may determine whether the validity period corresponding to the reference signal to be measured has expired, and use the angle auxiliary data of RS angle information message 934 for the reference signal only if the validity period of the reference signal has not expired. The processor 510 (possibly in conjunction with the memory 530) may include means for determining whether the validity period of the reference signal has expired.

[0149] Implementation Example

[0150] Examples of each implementation are provided in the following numbered clauses.

[0151] Clause 1. A network entity comprising:

[0152] interface;

[0153] Memory; and

[0154] The processor, communicatively coupled to the interface and the memory, is configured to:

[0155] Obtain reference signal angle information including a first indication, the first indication indicating a first reference signal and a first expected angle of arrival of the first reference signal; and

[0156] Perform at least one of the following operations:

[0157] Request the Transmit / Receive Point (TRP) to transmit the first instruction to the User Equipment; or

[0158] The TRP is requested to search for a first reference signal based on a first expected angle of arrival.

[0159] Clause 2. A network entity as described in Clause 1, wherein the processor is configured to perform at least one of the following operations: requesting the TRP to transmit a valid time indication associated with the first indication to the user equipment; or providing the valid time indication to the TRP.

[0160] Clause 3. The network entity as described in Clause 2, wherein the processor is configured to determine the value of the valid time indication based on the movement of the user equipment relative to the TRP.

[0161] Clause 4. As in Clause 1, the network entity wherein the first indication further indicates a first position, and wherein the reference signal angle information further includes a second indication indicating the first reference signal, a second expected angle of arrival of the first reference signal, and a second position, and wherein the processor is configured to:

[0162] Obtain the location of the user's equipment; and

[0163] The first indication is selected from the reference signal angle information based on the user equipment position corresponding to the first position.

[0164] Clause 5. A network entity as described in Clause 4, wherein the processor is configured to request the TRP to transmit a first indication to the user equipment as either a MAC layer message or a physical layer message.

[0165] Clause 6. As in Clause 1, the network entity wherein the first indication indicates the first expected angle of arrival of the first reference signal as a first angle search window including the first expected angle of arrival of the first reference signal.

[0166] Clause 7. As in Clause 6, the network entity wherein the reference signal angle information further includes a second indication indicating the first reference signal and a second expected angle of arrival of the first reference signal, wherein the first expected angle of arrival is different from the second expected angle of arrival, and wherein at least one of the first and second expected angles of arrival corresponds to a non-line-of-sight path between the TRP and the user equipment.

[0167] Clause 8. A network entity as described in Clause 1, wherein the processor is configured to: analyze a reference signal measurement and the position corresponding to the reference signal measurement to obtain reference signal angle information.

[0168] Clause 9. A network entity as described in Clause 1, wherein the processor is configured to: request the TRP to transmit a first indication to the user equipment, and wherein the processor is configured to: request the TRP to transmit a first indication to the user equipment in response to receiving a capability message from the user equipment indicating that the user equipment is configured to use angle of arrival information to measure reference signals.

[0169] Clause 10. A network entity as described in Clause 1, wherein the user equipment is a first user equipment, and wherein the processor is configured to request the TRP to transmit a first instruction to both the first user equipment and the second user equipment in at least one of a multicast message or a broadcast message.

[0170] Clause 11. A network entity comprising:

[0171] A means for obtaining reference signal angle information including a first indication, the first indication indicating a first reference signal and a first expected angle of arrival of the first reference signal; and

[0172] At least one of the following:

[0173] A means for requesting a transmit / receive point (TRP) to transmit a first instruction to user equipment; or

[0174] A means for requesting the TRP to search for a first reference signal based on a first expected angle of arrival.

[0175] Clause 12. A network entity as described in Clause 11 further includes at least one of the following: means for requesting the TRP to transmit a valid time indication associated with the first indication to the user equipment; or means for providing the valid time indication to the TRP.

[0176] Clause 13. The network entity as described in Clause 12 further includes means for determining the value of the valid time indication based on the movement of the user equipment relative to the TRP.

[0177] Clause 14. A network entity as described in Clause 11, wherein the first indication further indicates a first position, and wherein the reference signal angle information further includes a second indication indicating the first reference signal, a second expected angle of arrival of the first reference signal, and a second position, the network entity further includes:

[0178] A means for obtaining the location of the user equipment; and

[0179] A means for selecting a first indication from the reference signal angle information based on the user equipment position corresponding to the first position.

[0180] Clause 15. A network entity as described in Clause 14, wherein the network entity includes means for requesting the TRP to transmit a first indication to the user equipment, wherein the means for requesting the TRP to transmit the first indication includes means for requesting the TRP to transmit the first indication as either a MAC layer message or a physical layer message.

[0181] Clause 16. As in Clause 11, the network entity wherein the first indication indicates the first expected angle of arrival of the first reference signal as a first angle search window including the first expected angle of arrival of the first reference signal.

[0182] Clause 17. The network entity as described in Clause 16, wherein the reference signal angle information further includes a second indication indicating the first reference signal and a second expected angle of arrival of the first reference signal, wherein the first expected angle of arrival is different from the second expected angle of arrival, and wherein at least one of the first and second expected angles of arrival corresponds to a non-line-of-sight path between the TRP and the user equipment.

[0183] Clause 18. As in Clause 11, the means for obtaining the reference signal angle information includes means for analyzing the reference signal measurement and the position corresponding to the reference signal measurement to obtain the reference signal angle information.

[0184] Clause 19. A network entity as described in Clause 11, wherein the network entity includes means for requesting the TRP to transmit a first indication to the user equipment, and wherein the means for requesting the TRP to transmit the first indication to the user equipment includes means for requesting the TRP to transmit the first indication to the user equipment in response to receiving from the user equipment a capability message indicating that the user equipment is configured to use angle of arrival information to measure a reference signal.

[0185] Clause 20. A network entity as described in Clause 11, wherein the network entity includes means for requesting the TRP to transmit a first instruction to the user equipment, wherein the user equipment is a first user equipment, and wherein the means for requesting the TRP to transmit the first instruction to the user equipment includes means for requesting the TRP to transmit the first instruction to both the first user equipment and the second user equipment in at least one of a multicast message or a broadcast message.

[0186] Clause 21. A signal measurement auxiliary method, comprising:

[0187] Obtain reference signal angle information including a first indication, the first indication indicating a first reference signal and a first expected angle of arrival of the first reference signal; and

[0188] Perform at least one of the following operations:

[0189] Request the Transmit / Receive Point (TRP) to transmit the first instruction to the User Equipment; or

[0190] The TRP is requested to search for a first reference signal based on a first expected angle of arrival.

[0191] Clause 22. The signal measurement assistance method of Clause 21 further includes performing at least one of the following operations: requesting the TRP to transmit a valid time indication associated with the first indication to the user equipment; or providing the valid time indication to the TRP.

[0192] Clause 23. The signal measurement aid method as described in Clause 22 further includes determining the value of the effective time indication based on the motion of the user equipment relative to the TRP.

[0193] Clause 24. A signal measurement assistance method as described in Clause 21, wherein the first indication further indicates a first position, and wherein the reference signal angle information further includes a second indication indicating a first reference signal, a second expected angle of arrival of the first reference signal, and a second position, the signal measurement assistance method further comprising:

[0194] Obtain the location of the user's equipment; and

[0195] The first indication is selected from the reference signal angle information based on the user equipment position corresponding to the first position.

[0196] Clause 25. A signal measurement assistance method as described in Clause 24, wherein the signal measurement assistance method includes requesting the TRP to transmit a first indication to the user equipment as either a MAC layer message or a physical layer message.

[0197] Clause 26. A signal measurement aiding method as described in Clause 21, wherein the first indication indicates the first expected angle of arrival of the first reference signal as a first angle search window including the first expected angle of arrival of the first reference signal.

[0198] Clause 27. The signal measurement assistance method of Clause 26, wherein the reference signal angle information further includes a second indication indicating a first reference signal and a second expected angle of arrival of the first reference signal, wherein the first expected angle of arrival is different from the second expected angle of arrival, and wherein at least one of the first expected angle of arrival and the second expected angle of arrival corresponds to a non-line-of-sight path between the TRP and the user equipment.

[0199] Clause 28. A signal measurement aiding method as described in Clause 21, wherein obtaining the reference signal angle information includes analyzing the reference signal measurement and the position corresponding to the reference signal measurement.

[0200] Clause 29. A signal measurement assistance method as described in Clause 21, wherein the signal measurement assistance method includes: requesting the TRP to transmit a first instruction to the user equipment in response to receiving a capability message from the user equipment indicating that the user equipment is configured to use angle of arrival information to measure a reference signal.

[0201] Clause 30. A signal measurement assistance method as described in Clause 21, wherein the user equipment is a first user equipment, and wherein the signal measurement assistance method comprises: requesting the TRP to transmit a first instruction to both the first user equipment and the second user equipment in at least one of a multicast message or a broadcast message.

[0202] Clause 31. A non-transient processor-readable storage medium comprising processor-readable instructions configured to cause a processor of a network entity to perform the following operations for the purpose of assisting signal measurement:

[0203] Obtain reference signal angle information including a first indication, the first indication indicating a first reference signal and a first expected angle of arrival of the first reference signal; and

[0204] At least one of the following:

[0205] Request the Transmit / Receive Point (TRP) to transmit the first instruction to the User Equipment; or

[0206] The TRP is requested to search for a first reference signal based on a first expected angle of arrival.

[0207] Clause 32. The storage medium of Clause 31 further includes at least one of the following: a processor-readable instruction configured to cause the processor to request the TRP to transmit a valid time indication associated with the first indication to the user equipment; or a processor-readable instruction configured to cause the processor to provide the valid time indication to the TRP.

[0208] Clause 33. The storage medium, as described in Clause 32, further includes processor-readable instructions configured to cause the processor to determine the value of the valid time indication based on the movement of the user equipment relative to the TRP.

[0209] Clause 34. A storage medium as described in Clause 31, wherein the first indication further indicates a first position, and wherein the reference signal angle information further includes a second indication indicating the first reference signal, a second expected angle of arrival of the first reference signal, and a second position, the storage medium further including processor-readable instructions configured to cause the processor to perform the following operations:

[0210] Obtain the location of the user's equipment; and

[0211] The first indication is selected from the reference signal angle information based on the user equipment position corresponding to the first position.

[0212] Clause 35. The storage medium as described in Clause 34, wherein the storage medium includes processor-readable instructions configured to cause the processor to request the TRP to transmit a first indication to the user equipment as either a MAC layer message or a physical layer message.

[0213] Clause 36. The storage medium as described in Clause 31, wherein the first indication indicates the first expected angle of arrival of the first reference signal as a first angle search window including the first expected angle of arrival of the first reference signal.

[0214] Clause 37. The storage medium of Clause 36, wherein the reference signal angle information further includes a second indication indicating the first reference signal and a second expected angle of arrival of the first reference signal, wherein the first expected angle of arrival is different from the second expected angle of arrival, and wherein at least one of the first expected angle of arrival and the second expected angle of arrival corresponds to a non-line-of-sight path between the TRP and the user equipment.

[0215] Clause 38. The storage medium of Clause 31, wherein processor-readable instructions configured to cause the processor to obtain the reference signal angle information include processor-readable instructions configured to cause the processor to analyze the reference signal measurement and the position corresponding to the reference signal measurement.

[0216] Clause 39. The storage medium as described in Clause 31, wherein the storage medium includes a processor-readable instruction configured to request the TRP to transmit a first indication to the user equipment in response to receiving a capability message from the user equipment indicating that the user equipment is configured to use angle of arrival information to measure a reference signal.

[0217] Clause 40. A storage medium as described in Clause 31, wherein the user equipment is a first user equipment, and wherein the storage medium includes processor-readable instructions configured to cause the processor to request the TRP to transmit a first instruction to both the first user equipment and the second user equipment in at least one of a multicast message or a broadcast message.

[0218] Clause 41. A user equipment comprising:

[0219] transceiver;

[0220] Memory; and

[0221] The processor, communicatively coupled to the transceiver and the memory, is configured to:

[0222] The transceiver transmits an angle usage capability message to the network entity, which instructs the UE to use signal angle information to measure the signal's capability.

[0223] The transceiver receives a reference signal indication from the network entity, the reference signal indication indicating a reference signal and at least one reference signal angle search window corresponding to the reference signal; and

[0224] The reference signal is searched based on the at least one reference signal angle search window.

[0225] Clause 42. User equipment as described in Clause 41, wherein the processor is configured to report a measurement of the reference signal only if the reference signal is received within the at least one reference signal angle search window.

[0226] Clause 43. User equipment as described in Clause 41, wherein the processor is configured to report measurements of the reference signal regardless of whether the reference signal is received outside the at least one reference signal angle search window.

[0227] Clause 44. User equipment as described in Clause 41, wherein the processor is configured to transmit an error message to the network entity via the transceiver, the error message indicating that the user equipment failed to receive the reference signal within the at least one reference signal angle search window.

[0228] Clause 45. User equipment as described in Clause 44, wherein the processor is configured to include the actual angle of arrival of the reference signal in the error message.

[0229] Clause 46. User equipment as described in Clause 41, wherein the angle-use capability message indicates at least one of the following:

[0230] The frequency band applicable to the user equipment's ability to use this signal angle information to measure the signal; or

[0231] The combination of frequency bands applicable to the user equipment's ability to use the signal angle information to measure the signal.

[0232] Clause 47. User equipment as described in Clause 41, wherein the processor is configured to: determine whether the validity period indicated by the reference signal has expired, and search for the reference signal according to the at least one reference signal angle search window based on the fact that the validity period indicated by the reference signal has not expired.

[0233] Clause 48. A user equipment comprising:

[0234] A means for transmitting an angle usage capability message to a network entity, the angle usage capability message indicating the user equipment's ability to measure signals using signal angle information;

[0235] A means for receiving a reference signal indication from the network entity, the reference signal indication pointing to a reference signal and at least one reference signal angle search window corresponding to the reference signal;

[0236] A means for searching for the reference signal based on the at least one reference signal angle search window; and

[0237] A device used to measure the reference signal.

[0238] Clause 49. The user equipment as described in Clause 48 further includes: means for reporting a measurement of the reference signal only if the reference signal is received within the at least one reference signal angle search window.

[0239] Clause 50. User equipment as described in Clause 48 further includes means for reporting measurements of the reference signal, regardless of whether the reference signal is received outside the at least one reference signal angle search window.

[0240] Clause 51. The user equipment as described in Clause 48 further includes means for transmitting an error message to the network entity, the error message indicating that the user equipment failed to receive the reference signal within the at least one reference signal angle search window.

[0241] Clause 52. User equipment as described in Clause 51, wherein the error message includes the actual angle of arrival of the reference signal.

[0242] Clause 53. User equipment as described in Clause 48, wherein the angle-use capability message indicates at least one of the following:

[0243] The frequency band applicable to the user equipment's ability to use this signal angle information to measure the signal; or

[0244] The combination of frequency bands applicable to the user equipment's ability to use the signal angle information to measure the signal.

[0245] Clause 54. The user equipment as described in Clause 48 further includes means for determining whether the validity period indicated by the reference signal has expired, wherein the means for searching includes means for searching the reference signal according to the at least one reference signal angle search window based on the fact that the validity period indicated by the reference signal has not expired.

[0246] Clause 55. A method for measuring a reference signal at a user equipment location, the method comprising:

[0247] A means for transmitting an angle usage capability message from the user equipment to a network entity, the angle usage capability message indicating the user equipment's ability to use signal angle information to measure a signal;

[0248] The user equipment receives a reference signal indication from the network entity, the reference signal indication indicating the reference signal and at least one reference signal angle search window corresponding to the reference signal;

[0249] The user equipment searches for the reference signal based on the at least one reference signal angle search window; and

[0250] The reference signal was measured at the user equipment location.

[0251] Clause 56. The method of Clause 55 further includes reporting the measurement of the reference signal only if the reference signal is received within the at least one reference signal angle search window.

[0252] Clause 57. The method of Clause 55 further includes reporting the measurement of the reference signal, regardless of whether the reference signal is received outside the at least one reference signal angle search window.

[0253] Clause 58. The method of Clause 55 further includes transmitting an error message from the user equipment to the network entity, the error message indicating that the user equipment failed to receive the reference signal within the at least one reference signal angle search window.

[0254] Clause 59. As in Clause 58, wherein the error message includes the actual angle of arrival of the reference signal.

[0255] Clause 60. As in Clause 55, where the angle uses a capability message to indicate at least one of the following:

[0256] The frequency band applicable to the user equipment's ability to use this signal angle information to measure the signal; or

[0257] The combination of frequency bands applicable to the user equipment's ability to use the signal angle information to measure the signal.

[0258] Clause 61. The method of Clause 55 further includes determining at the user equipment whether the validity period indicated by the reference signal has expired, wherein searching for the reference signal according to the at least one reference signal angle search window is performed based on the fact that the validity period indicated by the reference signal has not expired.

[0259] Clause 62. A non-transient processor-readable storage medium comprising processor-readable instructions configured to cause a user-equipped processor to perform the following operations for measuring a reference signal:

[0260] Transmit an angle usage capability message to a network entity, which indicates the user equipment's ability to use signal angle information to measure signals;

[0261] Receive a reference signal indication from the network entity, the reference signal indication indicating the reference signal and at least one reference signal angle search window corresponding to the reference signal;

[0262] The user equipment searches for the reference signal based on the at least one reference signal angle search window; and

[0263] The reference signal was measured at the user equipment location.

[0264] Clause 63. The storage medium as described in Clause 62, wherein the storage medium further comprises: processor-readable instructions configured such that the processor reports a measurement of the reference signal only if the reference signal is received within the at least one reference signal angle search window.

[0265] Clause 64. The storage medium as described in Clause 62, wherein the storage medium further comprises: a processor-readable instruction configured to cause the processor to report a measurement of the reference signal, regardless of whether the reference signal is received outside the at least one reference signal angle search window.

[0266] Clause 65. The storage medium as described in Clause 62, wherein the storage medium further comprises: processor-readable instructions configured to cause the processor to transmit an error message to the network entity, the error message indicating that the user equipment failed to receive the reference signal within the at least one reference signal angle search window.

[0267] Clause 66. Storage media as described in Clause 65, wherein the error message includes the actual angle of arrival of the reference signal.

[0268] Clause 67. As with Clause 62, the storage medium wherein the angle-based capability message indicates at least one of the following:

[0269] The frequency band applicable to the user equipment's ability to use this signal angle information to measure the signal; or

[0270] The combination of frequency bands applicable to the user equipment's ability to use the signal angle information to measure the signal.

[0271] Clause 68. The storage medium as described in Clause 62, wherein the storage medium further comprises: processor-readable instructions configured to cause the processor to determine whether the validity period indicated by the reference signal has expired, wherein the processor-readable instructions configured to cause the processor to search for the reference signal include processor-readable instructions configured to cause the processor to search for the reference signal according to the at least one reference signal angle search window based on the fact that the validity period indicated by the reference signal has not expired.

[0272] Other considerations

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

[0274] As used herein, the singular forms of “a,” “some,” and “the” also include the plural forms, unless the context clearly indicates otherwise. As used herein, the terms “comprising,” “having,” “including,” and / or “containing” indicate the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0275] Similarly, as used herein, the "or" (which may be followed by "at least one of" or "one or more of") used in an 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 characteristic (e.g., AA, AAB, ABBC, etc.). Therefore, a statement that an item (e.g., a processor) is configured to perform a function with respect to at least one of A or B, or a statement that an item is configured to perform function A or function B, means that the item can be configured to perform a function with respect to A, or can be configured to perform a function with respect to B, or can be configured to perform a function with respect to both A and B. For example, a phrase processor being configured to measure "at least one of A or B" or "the processor is 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 may be configured to select which or both of A and B to measure). Similarly, a description of means for measuring at least one of A or B includes: means for measuring A (which may or may not measure B), or means for measuring B (which may or may not be configured to measure A), or means for measuring A and B (which may be able to select which or both of A and B to measure). 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 indicates 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 function X and function Y. For example, the phrase processor being 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 or both of X and Y to measure).

[0276] As used herein, unless otherwise stated, a description of a function or operation “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.

[0277] Substantial modifications can be made to suit specific requirements. For example, custom hardware can be used, and / or specific elements can be implemented in the hardware, in processor-executed software (including portable software such as applets), or both. Furthermore, connections to other computing devices (such as network input / output devices) can be employed. Unless otherwise stated, the interconnected or communicating components (functionally or otherwise) shown in the figures and / or discussed herein are communicatively coupled. That is, they can be directly or indirectly connected to enable communication between them.

[0278] The systems and devices discussed above are examples. Various configurations may appropriately omit, substitute, or add various procedures or components. For example, features described with reference to certain configurations may be combined in various other configurations. Different aspects and elements of a configuration may be combined in a similar manner. Furthermore, technology evolves, and thus many elements are examples and do not limit the scope of this disclosure or the claims.

[0279] A wireless communication system is a system in which communication is transmitted wirelessly, that is, through the atmospheric space via electromagnetic waves and / or sound waves rather than through wires or other physical connections. A wireless communication network may not necessarily transmit all communications wirelessly, but may be configured to transmit at least some communications wirelessly. Furthermore, the term "wireless communication device" or similar terms do not require that the device be functionally exclusively or uniformly primarily used for communication, or that the device is 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 (each radio being part of a transmitter, receiver, or transceiver) for wireless communication.

[0280] Specific details are provided in this description to offer a thorough understanding of the example configurations (including implementations). However, these 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. This description provides only 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 techniques. Various changes can be made to the function and arrangement of the elements.

[0281] 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 (such as) processors for execution, and / or being used to store and / or carry such instructions / code (e.g., as signals). In many 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.

[0282] After describing several example configurations, various modifications, substitutions, constructs, 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 the invention. 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.

[0283] A statement whose value exceeds (or is greater than or higher than) a first threshold is equivalent to a statement whose 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 whose value is less than the first threshold (or within or below the first threshold) is equivalent to a statement whose 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.

Claims

1. A user equipment comprising: transceiver; Memory; as well as The processor, communicatively coupled to the transceiver and the memory, is configured to: The transceiver transmits an angle usage capability message to the network entity, the angle usage capability message indicating the UE's ability to use signal angle information to measure a reference signal; The transceiver receives a reference signal indication from the network entity, the reference signal indication pointing to a reference signal and at least one reference signal angle search window corresponding to the reference signal, wherein the at least one reference signal angle search window indicates an expected angle of arrival; and The reference signal is searched based on the at least one reference signal angle search window.

2. The user equipment of claim 1, wherein the processor is configured to report a measurement of the reference signal only if the reference signal is received within the at least one reference signal angle search window.

3. The user equipment of claim 1, wherein the processor is configured to report measurements of the reference signal regardless of whether the reference signal is received outside the at least one reference signal angle search window.

4. The user equipment of claim 1, wherein the processor is configured to transmit an error message to the network entity via the transceiver, the error message indicating that the user equipment failed to receive the reference signal within the at least one reference signal angle search window.

5. The user equipment of claim 4, wherein the processor is configured to include the actual angle of arrival of the reference signal in the error message.

6. The user equipment of claim 1, wherein the angle usage capability message indicates at least one of the following: The frequency band to which the user equipment is applicable for its ability to measure signals using the signal angle information; or The frequency band combination to which the user equipment is applicable to the ability to use the signal angle information to measure the reference signal.

7. The user equipment of claim 1, wherein the processor is configured to: determine whether the validity period indicated by the reference signal has expired, and search for the reference signal according to the at least one reference signal angle search window based on the fact that the validity period indicated by the reference signal has not expired.

8. A method for measuring a reference signal at a user equipment location, the method comprising: The user equipment transmits an angle usage capability message to the network entity, the angle usage capability message indicating the user equipment's ability to use signal angle information to measure a reference signal; At the user equipment, a reference signal indication is received from the network entity, the reference signal indication pointing to the reference signal and at least one reference signal angle search window corresponding to the reference signal, wherein the at least one reference signal angle search window indicates the expected angle of arrival; The reference signal is searched at the user equipment based on the at least one reference signal angle search window; and The reference signal is measured at the user equipment.

9. The method of claim 8, further comprising: The measurement of the reference signal is reported only if the reference signal is received within the at least one reference signal angle search window.

10. The method of claim 8, further comprising: The report covers measurements of the reference signal, regardless of whether the reference signal is received outside the at least one reference signal angle search window.

11. The method of claim 8, further comprising transmitting an error message from the user equipment to the network entity, the error message indicating that the user equipment failed to receive the reference signal within the at least one reference signal angle search window.

12. The method of claim 11, wherein the error message includes the actual angle of arrival of the reference signal.

13. The method of claim 8, wherein the angle using the capability message indicates at least one of the following: The frequency band to which the user equipment is applicable for its ability to measure signals using the signal angle information; or The frequency band combination to which the user equipment is applicable to the ability to use the signal angle information to measure the reference signal.

14. The method of claim 8, further comprising determining at the user equipment whether the validity period indicated by the reference signal has expired, wherein the reference signal is searched according to the at least one reference signal angle search window based on the fact that the validity period indicated by the reference signal has not expired.

15. A user equipment, the user equipment comprising: A means for transmitting an angle usage capability message to a network entity, the angle usage capability message indicating the user equipment's ability to use signal angle information to measure a reference signal; A means for receiving a reference signal indication from the network entity, the reference signal indication pointing to the reference signal and at least one reference signal angle search window corresponding to the reference signal, wherein the at least one reference signal angle search window indicates an expected angle of arrival; A means for searching for the reference signal based on the at least one reference signal angle search window; as well as A device for measuring the reference signal.

16. The user equipment of claim 15, further comprising means for reporting a measurement of the reference signal only if the reference signal is received within the at least one reference signal angle search window.

17. The user equipment of claim 15, further comprising means for reporting measurements of the reference signal, regardless of whether the reference signal is received outside the at least one reference signal angle search window.

18. The user equipment of claim 15, further comprising means for transmitting an error message to the network entity, the error message indicating that the user equipment failed to receive the reference signal within the at least one reference signal angle search window.

19. The user equipment of claim 18, wherein the error message includes the actual angle of arrival of the reference signal.

20. The user equipment of claim 15, wherein the angle usage capability message indicates at least one of the following: The frequency band to which the user equipment is applicable for its ability to measure signals using the signal angle information; or The frequency band combination to which the user equipment is applicable to the ability to use the signal angle information to measure the reference signal.

21. The user equipment of claim 15, further comprising means for determining whether the validity period indicated by the reference signal has expired, wherein the means for searching the reference signal according to the at least one reference signal angle search window is based on the fact that the validity period indicated by the reference signal has not expired.

22. A non-transient processor-readable storage medium, the storage medium including processor-readable instructions configured to cause a user-equipped processor to perform the following operations for measuring a reference signal: Transmit an angle usage capability message to a network entity, the angle usage capability message indicating the user equipment's ability to use signal angle information to measure a reference signal; Receive a reference signal indication from the network entity, the reference signal indication pointing to the reference signal and at least one reference signal angle search window corresponding to the reference signal, wherein the at least one reference signal angle search window indicates the expected angle of arrival; The reference signal is searched based on the at least one reference signal angle search window; and Measure the reference signal.

23. The storage medium of claim 22, wherein the storage medium further comprises instructions configured to cause the processor to perform the following operation: report a measurement of the reference signal only if the reference signal is received within the at least one reference signal angle search window.

24. The storage medium of claim 22, wherein the storage medium further comprises instructions configured to cause the processor to perform the following operation: report a measurement of the reference signal, regardless of whether the reference signal is received outside the at least one reference signal angle search window.

25. The storage medium of claim 22, wherein the storage medium further comprises instructions configured to cause the processor to perform the following operation: transmit an error message to the network entity, the error message indicating that the user equipment failed to receive the reference signal within the at least one reference signal angle search window.

26. The storage medium of claim 25, wherein the error message includes the actual angle of arrival of the reference signal.

27. The storage medium of claim 22, wherein the angle usage capability message indicates at least one of the following: The frequency band to which the user equipment is applicable for its ability to measure signals using the signal angle information; or The frequency band combination to which the user equipment is applicable to the ability to use the signal angle information to measure the reference signal.

28. The storage medium of claim 22, wherein the storage medium further includes instructions configured to cause the processor to perform the following operation: determining whether the validity period indicated by the reference signal has expired, wherein processor-readable instructions configured to cause the processor to search for the reference signal according to the at least one reference signal angle search window are based on the fact that the validity period indicated by the reference signal has not expired.

Images