WO2024232963A1

WO2024232963A1 - Positioning with user equipment (ue) controlled reconfigurable intelligent device (rid)

Info

Publication number: WO2024232963A1
Application number: PCT/US2024/016499
Authority: WO
Inventors: Sourjya Dutta; Alexandros MANOLAKOS; Navid Abedini; Kapil Gulati
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2023-05-05
Filing date: 2024-02-20
Publication date: 2024-11-14
Anticipated expiration: 2025-11-05
Also published as: CN121040112A

Abstract

An example method of positioning of a target UE in a presence of a distributed RID, the method performed by a server and may comprise receiving, from the target UE, information of the distributed RID indicating an availability of the distributed RID, wherein the positioning of the target UE may be performed using the distributed RID, and wherein the distributed RID is controlled by a distributed controller not being a network node. The method may also comprise determining a first RID configuration for positioning of the target UE based at least in part on the information of the distributed RID and sending to the target UE the first RID configuration for positioning the target UE.

Description

POSITIONING WITH USER EQUIPMENT (UE) CONTROLLED RECONFIGURABLE INTELLIGENT DEVICE (RID)

RELATED APPLICATIONS

[0001] This application claims the benefit of Greek Application No. 20230100365, filed May 5, 2023, entitled “POSITIONING WITH USER EQUIPMENT (UE) CONTROLLED RECONFIGURABLE INTELLIGENT DEVICE (RID)”, which is assigned to the assignee hereof, and incorporated herein in its entirety by reference.

BACKGROUND Field of Disclosure

[0002] The present disclosure relates generally to the field of wireless communications, and more specifically to positioning a target User Equipment (UE) using distributed reconfigurable intelligent device(s) RID(s). Description of Related Art

[0003] In a wireless communication network, positioning of a receiving device (e.g., a target UE) can involve measurements of a radio frequency (RF) signal (e.g., a wireless reference signal) received by the receiving device. In some instances, RID(s) may be used to enhance the positioning of the target UE.

BRIEF SUMMARY

[0004] An example method of positioning of a target UE in a presence of a distributed RID, the method performed by a server and may comprise receiving, from the target UE, information of the distributed RID indicating an availability of the distributed RID, wherein the positioning of the target UE may be performed using the distributed RID, and wherein the distributed RID is controlled by a distributed controller not being a network node. The method may also comprise determining a first RID configuration for positioning of the target UE based at least in part on the information of the distributed RID and sending to the target UE the first RID configuration for positioning the target UE.

[0005] An example method of positioning of a target UE in a presence of a RID, the method performed by the target UE and may comprise determining that a distributed RID may be used in positioning of the target UE, wherein the distributed RID is controlled by a distributed controller not being a network node. The method may also comprise sending, to a server, information of the distributed RID indicating availability of the distributed RID and receiving, from the server, a first RID configuration for the positioning of the target UE determined based at least in part on the information of the distributed RID.

[0006] An example server for positioning of a target UE in a presence of a distributed RID comprising a transceiver, a memory, and one or more processors communicatively coupled with the transceiver and the memory. The one or more processors may be configured to receive, from the target UE, information of the distributed RID indicating an availability of the distributed RID, wherein the positioning of the target UE may be performed using the distributed RID, and wherein the distributed RID is controlled by a distributed controller not being a network node. The one or more processors may also be configured to determine a first RID configuration for positioning of the target UE based at least in part on the information of the distributed RID. The one or more processors may further be configured to send to the target UE the first RID configuration for positioning the target UE.

[0007] An example target UE for positioning in a presence of a RID comprising a transceiver, a memory, and one or more processors communicatively coupled with the transceiver and the memory. The one or more processors may be configured to determine that a distributed RID may be used in positioning of the target UE, wherein the distributed RID is controlled by a distributed controller not being a network node. The one or more processors may also be configured to send, to a server, information of the distributed RID indicating availability of the distributed RID. The one or more processors may further be configured to receive, from the server, a first RID configuration for the positioning of the target UE determined based at least in part on the information of the distributed RID.

[0008] This summary is neither intended to identify key or essential features of the claimed subject matter, nor is it intended to be used in isolation to determine the scope of the claimed subject matter. The subject matter should be understood by reference to appropriate portions of the entire specification of this disclosure, any or all drawings, and each claim. The foregoing, together with other features and examples, will be described in more detail below in the following specification, claims, and accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] FIG. l is a simplified illustration of a positioning system for UE positioning in the presence of a distributed RID, according to an embodiment.

[0010] FIG. 2 is a diagram of a 5th Generation (5G) New Radio (NR) positioning system, illustrating an embodiment of a positioning system (e.g., the positioning system of FIG. 1) implemented within a 5G NR communication system.

[0011] FIG. 3 is a diagram illustrating beamforming in a 5G NR positioning system.

[0012] FIG. 4 is a simplified diagram illustrating how a distributed RID may facilitate the transmission of an RF signal in UE positioning according to an embodiment.

[0013] FIG. 5 is a call-flow diagram illustrating how positioning of a target UE may be performed in a presence of a distributed RID according to an embodiment.

[0014] FIG. 6 is a flow diagram of a method for positioning of a target UE in the presence of a distributed RID, which is performed by a server, according to some embodiments.

[0015] FIG. 7 is a flow diagram of a method for positioning of a target UE in the presence of a distributed RID, which is performed by the target UE, according to some embodiments.

[0016] FIG. 8 is a block diagram of an embodiment of a computer system, which can be utilized in embodiments as described herein.

[0017] FIG. 9 is a block diagram of an embodiment of a UE, which can be utilized in embodiments as described herein.

[0018] Like reference symbols in the various drawings indicate like elements, in accordance with certain example implementations. In addition, multiple instances of an element may be indicated by following a first number for the element with a letter or a hyphen and a second number. For example, multiple instances of an element 110 may be indicated as 110-1, 110-2, 110-3 etc. or as 110a, 110b, 110c, etc. When referring to such an element using only the first number, any instance of the element is to be understood (e.g., element 110 in the previous example would refer to elements 110-1, 110-2, and 110- 3 or to elements 110a, 110b, and 110c). DETAILED DESCRIPTION

[0019] The following description is directed to certain implementations for the purposes of describing innovative aspects of various embodiments. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways. The described implementations may be implemented in any device, system, or network that is capable of transmitting and receiving radio frequency (RF) signals according to any communication standard, such as any of the Institute of Electrical and Electronics Engineers (IEEE) 802.15.4 standards for ultra-wideband (UWB), IEEE 802.11 standards (including those identified as Wi-Fi® technologies), the Bluetooth® standard, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile communications (GSM), GSM/General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunked Radio (TETRA), Wideband-CDMA (W-CDMA), Evolution Data Optimized (EV-DO), IxEV- DO, EV-DO Rev A, EV-DO Rev B, High Rate Packet Data (HRPD), High Speed Packet Access (HSPA), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), Evolved High Speed Packet Access (HSPA+), Long Term Evolution (LTE), Advanced Mobile Phone System (AMPS), or other known signals that are used to communicate within a wireless, cellular or internet of things (loT) network, such as a system utilizing 3G, 4G, 5G, 6G, or further implementations thereof, technology.

[0020] As used herein, an “RF signal” comprises an electromagnetic wave that transports information through the space between a transmitter (or transmitting device) and a receiver (or receiving device). As used herein, a transmitter may transmit a single “RF signal” or multiple “RF signals” to a receiver. However, the receiver may receive multiple “RF signals” corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multiple channels or paths.

[0021] Additionally, unless otherwise specified, references to “reference signals,” “positioning reference signals,” “reference signals for positioning,” and the like may be used to refer to signals used for positioning of a user equipment (UE) in a 5G new radio (NR) network. As described in more detail herein, such signals may comprise any of a variety of signal types but may not necessarily be limited to a Positioning Reference Signal (PRS) as defined in relevant wireless standards. [0022] Further, unless otherwise specified, the term “positioning” as used herein may include absolute location determination, relative location determination, ranging, or a combination thereof. Such positioning may include and/or be based on timing, angular, phase, or power measurements, or a combination thereof (which may include RF sensing measurements) for the purpose of location or sensing services.

[0023] Various aspects generally relate to positioning of a target UE. Some aspects more specifically relate to the positioning of the target UE in the presence of a distributed reconfigurable intelligent device (RID). The term RID, as used herein may include any controllable devices in the medium between a transmitter and a receiver that can improve the link quality. For example, the RID may include passive RIDs that may not need power or control, such as a meta-surface installed on a window for getting rid of outdoor-to- indoor penetration loss and may include active RIDs such as repeaters, reconfigurable intelligent surfaces (IRSs), etc., controlled by a network controller (e.g., a network node, such as a location server and/or a base station) or a distributed controller (e.g., a roadside unit or another UE) for boosting signal strength and/or steering the signals. When the RID is controllable, the controller of the RID (RID-C) may communicate with other network nodes to determine the RID configuration for positioning the target UE.

[0024] As will be discussed in detail below, knowledge of the presence/availability of the RID in the positioning of the target UE is crucial because it may otherwise cause significant positioning errors (will be discussed in detail below). In some instances, if the RID(s) are network-controlled (e.g., controlled by a network node), a base station may notify the UEs connected to the base station of the presence of the RID. However, if the RID(s) are controlled by distributed controllers (e.g., controlled by a roadside unite (RSU) or another UE), the target UE may need to discover and notify the network node (e.g., the location server) the presence/availability of the RID(s).

[0025] In some examples, the target UE may determine that a distributed RID (e.g., a RID controlled by a distributed controller) is/may be used for positioning the target UE and may send to a server information of the distributed RID indicating the availability of the distributed RID. The server may determine a first RID configuration for poisoning the target UE based at least in part on the information of the distributed RID. The server may also determine a second RID configuration for reducing interference (e.g., to neighboring UEs not positioned using the distributed RID) associated with the positioning of the target UE caused by the distributed RID. The first RID configuration may be shared with the target UE. The second RID configuration may be shared with the neighboring UE by the server directly or by the target UE through sidelink communications.

[0026] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by considering the presence of the distributed RID, the described techniques can be used to enhance the positioning performance of the target UE (e.g., increase the positioning accuracy) and/or reduce the interference to the positioning of neighboring UEs that do not use the RID.

[0027] FIG. 1 is a simplified illustration of a positioning system 100 in which a UE 105, location server 160, and/or other components of the positioning system 100 can use the techniques provided herein for UE positioning in the presence of a distributed RID, according to an embodiment. The techniques described herein may be implemented by one or more components of the positioning system 100. The positioning system 100 can include: a UE 105; one or more satellites 110 (also referred to as space vehicles (SVs)) for a Global Navigation Satellite System (GNSS) such as the Global Positioning System (GPS), GLONASS, Galileo or Beidou; base stations 120; access points (APs) 130; location server 160; network 170; and external client 180. Generally put, the positioning system 100 can estimate a location of UE 105 based on RF signals received by and/or sent from the UE 105 and known locations of other components (e.g., GNSS satellites 110, base stations 120, APs 130) transmitting and/or receiving the RF signals. Additional details regarding particular location estimation techniques are discussed in more detail with regard to FIG. 2.

[0028] It should be noted that FIG. 1 provides only a generalized illustration of various components, any or all of which may be utilized as appropriate, and each of which may be duplicated as necessary. Specifically, although only one UE 105 is illustrated, it will be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the positioning system 100. Similarly, the positioning system 100 may include a larger or smaller number of base stations 120 and/or APs 130 than illustrated in FIG. 1. The illustrated connections that connect the various components in the positioning system 100 comprise data and signaling connections which may include additional (intermediary) components, direct or indirect physical and/or wireless connections, and/or additional networks. Furthermore, components may be rearranged, combined, separated, substituted, and/or omitted, depending on desired functionality. In some embodiments, for example, the external client 180 may be directly connected to location server 160. A person of ordinary skill in the art will recognize many modifications to the components illustrated.

[0029] Depending on desired functionality, network 170 may comprise any of a variety of wireless and/or wireline networks. Network 170 can, for example, comprise any combination of public and/or private networks, local and/or wide-area networks, and the like. Furthermore, network 170 may utilize one or more wired and/or wireless communication technologies. In some embodiments, network 170 may comprise a cellular or other mobile network, a wireless local area network (WLAN), a wireless wide- area network (WWAN), and/or the Internet, for example. Examples of network 170 include a Long-Term Evolution (LTE) wireless network, a Fifth Generation (5G) wireless network (also referred to as New Radio (NR) wireless network or 5G NR wireless network), a Wi-Fi WLAN, and the Internet. LTE, 5G and NR are wireless technologies defined, or being defined, by the 3rd Generation Partnership Project (3GPP). Network 170 may also include more than one network and/or more than one type of network.

[0030] Base stations 120 and access points (APs) 130 may be communicatively coupled to network 170. In some embodiments, base station 120s may be owned, maintained, and/or operated by a cellular network provider, and may employ any of a variety of wireless technologies, as described herein below. Depending on the technology of network 170, a base station 120 may comprise a node B, an Evolved Node B (eNodeB or eNB), a base transceiver station (BTS), a radio base station (RBS), an NR NodeB (gNB), a Next Generation eNB (ng-eNB), or the like. A base station 120 that is a gNB or ng-eNB may be part of a Next Generation Radio Access Network (NG-RAN) which may connect to a 5G Core Network (5GC) in the case that Network 170 is a 5G network. The functionality performed by a base station 120 in earlier-generation networks (e.g., 3G and 4G) may be separated into different functional components (e.g., radio units (RUs), distributed units (DUs), and central units (CUs)) and layers (e.g., L1/L2/L3) in view Open Radio Access Networks (O-RAN) and/or Virtualized Radio Access Network (V-RAN or vRAN) in 5G or later networks, which may be executed on different devices at different locations connected, for example, via fronthaul, midhaul, and backhaul connections. As referred to herein, a “base station” (or ng-eNB, gNB, etc.) may include any or all of these functional components. An AP 130 may comprise a Wi-Fi AP or a Bluetooth® AP or an AP having cellular capabilities (e.g., 4G LTE and/or 5G NR), for example. Thus, UE 105 can send and receive information with network-connected devices, such as location server 160, by accessing network 170 via a base station 120 using a first communication link 133. Additionally or alternatively, because APs 130 also may be communicatively coupled with network 170, UE 105 may communicate with network-connected and Internet-connected devices, including location server 160, using a second communication link 135, or via one or more other UEs 145.

[0031] As used herein, the term “base station” may generically refer to a single physical transmission point, or multiple co-located physical transmission points, which may be located at a base station 120. A Transmission Reception Point (TRP) (also known as transmit/receive point) corresponds to this type of transmission point, and the term “TRP” may be used interchangeably herein with the terms “gNB,” “ng-eNB,” and “base station.” In some cases, a base station 120 may comprise multiple TRPs - e.g., with each TRP associated with a different antenna or a different antenna array for the base station 120. Physical transmission points may comprise an array of antennas of a base station 120 (e.g., as in a Multiple Input-Multiple Output (MIMO) system and/or where the base station employs beamforming). The term “base station” may additionally refer to multiple non-co-located physical transmission points, the physical transmission points may be a Distributed Antenna System (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a Remote Radio Head (RRH) (a remote base station connected to a base station).

[0032] As used herein, the term “cell” may generically refer to a logical communication entity used for communication with a base station 120 and may be associated with an identifier for distinguishing neighboring cells (e.g., a Physical Cell Identifier (PCID), a Virtual Cell Identifier (VCID)) operating via the same or a different carrier. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., Machine-Type Communication (MTC), Narrowband Internet-of-Things (NB-IoT), Enhanced Mobile Broadband (eMBB), or others) that may provide access for different types of devices. In some cases, the term “cell” may refer to a portion of a geographic coverage area (e.g., a sector) over which the logical entity operates. [0033] Location server 160 may comprise a server and/or other computing device configured to determine an estimated location of UE 105 and/or provide data (e.g., “assistance data”) to UE 105 to facilitate location measurement and/or location determination by UE 105. According to some embodiments, location server 160 may comprise a Home Secure User Plane Location (SUPL) Location Platform (H-SLP), which may support the SUPL user plane (UP) location solution defined by the Open Mobile Alliance (OMA) and may support location services for UE 105 based on subscription information for UE 105 stored in location server 160. In some embodiments, location server 160 may comprise, a Discovered SLP (D-SLP) or an Emergency SLP (E-SLP). The location server 160 may also comprise an Enhanced Serving Mobile Location Center (E-SMLC) that supports location of UE 105 using a control plane (CP) location solution for LTE radio access by UE 105. The location server 160 may further comprise a Location Management Function (LMF) that supports location of UE 105 using a control plane (CP) location solution for NR or LTE radio access by UE 105.

[0034] In a CP location solution, signaling to control and manage the location of UE 105 may be exchanged between elements of network 170 and with UE 105 using existing network interfaces and protocols and as signaling from the perspective of network 170. In a UP location solution, signaling to control and manage the location of UE 105 may be exchanged between location server 160 and UE 105 as data (e.g. data transported using the Internet Protocol (IP) and/or Transmission Control Protocol (TCP)) from the perspective of network 170.

[0035] As previously noted (and discussed in more detail below), the estimated location of UE 105 may be based on measurements of RF signals sent from and/or received by UE 105. In particular, these measurements can provide information regarding the relative distance and/or angle of UE 105 from one or more components in positioning system 100 (e.g., GNSS satellites 110, APs 130, base stations 120). The estimated location of UE 105 can be estimated geometrically (e.g., using multi angulation and/or multilateration), based on the distance and/or angle measurements, along with known position of the one or more components.

[0036] Although terrestrial components such as APs 130 and base stations 120 may be fixed, embodiments are not so limited. Mobile components may be used. For example, in some embodiments, a location of UE 105 may be estimated at least in part based on measurements of RF signals 140 communicated between UE 105 and one or more other UEs 145, which may be mobile or fixed. When one or more other UEs 145 are used in the position determination of a particular UE 105, UE 105 for which the position is to be determined may be referred to as the “target UE,” and each of the one or more other UEs 145 used may be referred to as an “anchor UE.” For position determination of a target UE, the respective positions of the one or more anchor UEs may be known and/or jointly determined with the target UE. Direct communication between the one or more other UEs 145 and UE 105 may comprise sidelink and/or similar Device-to-Device (D2D) communication technologies. Sidelink, which is defined by 3GPP, is a form of D2D communication under the cellular-based LTE and NR standards.

[0037] An estimated location of UE 105 can be used in a variety of applications - e.g. to assist direction finding or navigation for a user of UE 105 or to assist another user (e.g. associated with external client 180) to locate UE 105. A “location” is also referred to herein as a “location estimate”, “estimated location”, “location”, “position”, “position estimate”, “position fix”, “estimated position”, “location fix” or “fix”. The process of determining a location may be referred to as “positioning,” “position determination,” “location determination,” or the like. A location of UE 105 may comprise an absolute location of UE 105 (e.g. a latitude and longitude and possibly altitude) or a relative location of UE 105 (e.g. a location expressed as distances north or south, east or west and possibly above or below some other known fixed location (including, e.g., the location of a base station 120 or AP 130) or some other location such as a location for UE 105 at some known previous time, or a location of another UE 145 at some known previous time). A location may be specified as a geodetic location comprising coordinates which may be absolute (e.g., latitude, longitude and optionally altitude), relative (e.g., relative to some known absolute location) or local (e.g., X, Y and optionally Z coordinates according to a coordinate system defined relative to a local area such a factory, warehouse, college campus, shopping mall, sports stadium or convention center). A location may instead be a civic location and may then comprise one or more of a street address (e.g. including names or labels for a country, state, county, city, road and/or street, and/or a road or street number), and/or a label or name for a place, building, portion of a building, floor of a building, and/or room inside a building etc. A location may further include an uncertainty or error indication, such as a horizontal and possibly vertical distance by which the location is expected to be in error or an indication of an area or volume (e.g. a circle or ellipse) within which UE 105 is expected to be located with some level of confidence (e.g. 95% confidence).

[0038] The external client 180 may be a web server or remote application that may have some association with UE 105 (e.g. may be accessed by a user of UE 105) or may be a server, application, or computer system providing a location service to some other user or users which may include obtaining and providing the location of UE 105 (e.g. to enable a service such as friend or relative finder, or child or pet location). Additionally or alternatively, the external client 180 may obtain and provide the location of UE 105 to an emergency services provider, government agency, etc.

[0039] As previously noted, the example positioning system 100 can be implemented using a wireless communication network, such as an LTE-based or 5G NR-based network. FIG. 2 shows a diagram of a 5G NR positioning system 200, illustrating an embodiment of a positioning system (e.g., positioning system 100) implementing 5GNR. The 5GNR positioning system 200 may be configured to determine the location of a UE 105 by using access nodes, which may include NR NodeB (gNB) 210-1 and 210-2 (collectively and generically referred to herein as gNBs 210), ng-eNB 214, and/or WLAN 216 to implement one or more positioning methods. gNBs 210 and/or the ng-eNB 214 may correspond with base stations 120 of FIG. 1, and the WLAN 216 may correspond with one or more access points 130 of FIG. 1. Optionally, the 5G NR positioning system 200 additionally may be configured to determine the location of a UE 105 by using an LMF 220 (which may correspond with location server 160) to implement the one or more positioning methods. Here, the 5G NR positioning system 200 comprises a UE 105, and components of a 5G NR network comprising a Next Generation (NG) Radio Access Network (RAN) (NG-RAN) 235 and a 5G Core Network (5G CN) 240. A 5G network may also be referred to as an NR network; NG-RAN 235 may be referred to as a 5G RAN or as an NR RAN; and 5G CN 240 may be referred to as an NG Core network. 5G NR positioning system 200 may further utilize information from GNSS satellites 110 from a GNSS system like Global Positioning System (GPS) or similar system (e.g., GLONASS, Galileo, Beidou, Indian Regional Navigational Satellite System (IRNSS)). Additional components of 5G NR positioning system 200 are described below. 5G NR positioning system 200 may include additional or alternative components. [0040] It should be noted that FIG. 2 provides only a generalized illustration of various components, any or all of which may be utilized as appropriate, and each of which may be duplicated or omitted as necessary. Specifically, although only one UE 105 is illustrated, it will be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the 5G NR positioning system 200. Similarly, 5G NR positioning system 200 may include a larger (or smaller) number of GNSS satellites 110, gNBs 210, ng-eNBs 214, Wireless Local Area Networks (WLANs) 216, Access and mobility Management Functions (AMF)s 215, external clients 230, and/or other components. The illustrated connections that connect the various components in 5G NR positioning system 200 include data and signaling connections which may include additional (intermediary) components, direct or indirect physical and/or wireless connections, and/or additional networks. Furthermore, components may be rearranged, combined, separated, substituted, and/or omitted, depending on desired functionality.

[0041] UE 105 may comprise and/or be referred to as a device, a mobile device, a wireless device, a mobile terminal, a terminal, a mobile station (MS), a Secure User Plane Location (SUPL)-Enabled Terminal (SET), or by some other name. Moreover, UE 105 may correspond to a cellphone, smartphone, laptop, tablet, personal data assistant (PDA), navigation device, Internet of Things (loT) device, or some other portable or moveable device. Typically, though not necessarily, UE 105 may support wireless communication using one or more Radio Access Technologies (RATs) such as using GSM, CDMA, W- CDMA, LTE, High Rate Packet Data (HRPD), IEEE 802.11 Wi-Fi®, Bluetooth, Worldwide Interoperability for Microwave Access (WiMAX™), 5G NR (e.g., using the NG-RAN 235 and 5G CN 240), etc. The UE 105 may also support wireless communication using a WLAN 216 which (like the one or more RATs, and as previously noted with respect to FIG. 1) may connect to other networks, such as the Internet. The use of one or more of these RATs may allow UE 105 to communicate with an external client 230 (e.g., via elements of 5G CN 240 not shown in FIG. 2, or possibly via a Gateway Mobile Location Center (GMLC) 225) and/or allow the external client 230 to receive location information regarding UE 105 (e.g., via the GMLC 225). The external client 230 of FIG. 2 may correspond to external client 180 of FIG. 1, as implemented in or communicatively coupled with a 5GNR network.

[0042] UE 105 may include a single entity or may include multiple entities, such as in a personal area network where a user may employ audio, video and/or data I/O devices, and/or body sensors and a separate wireline or wireless modem. An estimate of a location of UE 105 may be referred to as a location, location estimate, location fix, fix, position, position estimate, or position fix, and may be geodetic, thus providing location coordinates for UE 105 (e.g., latitude and longitude), which may or may not include an altitude component (e.g., height above sea level, height above or depth below ground level, floor level or basement level). Alternatively, a location of UE 105 may be expressed as a civic location (e.g., as a postal address or the designation of some point or small area in a building such as a particular room or floor). A location of UE 105 may also be expressed as an area or volume (defined either geodetically or in civic form) within which UE 105 is expected to be located with some probability or confidence level (e.g., 67%, 95%, etc.). A location of UE 105 may further be a relative location comprising, for example, a distance and direction or relative X, Y (and Z) coordinates defined relative to some origin at a known location which may be defined geodetically, in civic terms, or by reference to a point, area, or volume indicated on a map, floor plan or building plan. In the description contained herein, the use of the term location may comprise any of these variants unless indicated otherwise. When computing the location of a UE, it is common to solve for local X, Y, and possibly Z coordinates and then, if needed, convert the local coordinates into absolute ones (e.g., for latitude, longitude and altitude above or below mean sea level).

[0043] Base stations in NG-RAN 235 shown in FIG. 2 may correspond to base stations 120 in FIG. 1 and may include gNBs 210. Pairs of gNBs 210 in NG-RAN 235 may be connected to one another (e.g., directly as shown in FIG. 2 or indirectly via other gNBs 210). The communication interface between base stations (gNBs 210 and/or ng- eNB 214) may be referred to as an Xn interface 237. Access to the 5G network is provided to UE 105 via wireless communication between UE 105 and one or more of the gNBs 210, which may provide wireless communications access to the 5G CN 240 on behalf of the UE 105 using 5GNR. The wireless interface between base stations (gNBs 210 and/or ng-eNB 214) and UE 105 may be referred to as a Uu interface 239. 5G NR radio access may also be referred to as NR radio access or as 5G radio access. In FIG. 2, the serving gNB forUE 105 is assumed to be gNB 210-1, although other gNBs (e.g. gNB 210-2) may act as a serving gNB if UE 105 moves to another location or may act as a secondary gNB to provide additional throughput and bandwidth to UE 105. [0044] Base stations in the NG-RAN 235 shown in FIG. 2 may also or instead include a next generation evolved Node B, also referred to as an ng-eNB, 214. Ng-eNB 214 may be connected to one or more gNBs 210 in NG-RAN 235-e.g. directly or indirectly via other gNBs 210 and/or other ng-eNBs. An ng-eNB 214 may provide LTE wireless access and/or evolved LTE (eLTE) wireless access to UE 105. Some gNBs 210 (e.g. gNB 210- 2) and/or ng-eNB 214 in FIG. 2 may be configured to function as positioning-only beacons which may transmit signals (e.g., Positioning Reference Signal (PRS)) and/or may broadcast assistance data to assist positioning of UE 105 but may not receive signals from UE 105 or from other UEs. Some gNBs 210 (e.g., gNB 210-2 and/or another gNB not shown) and/or ng-eNB 214 may be configured to function as detecting-only nodes may scan for signals containing, e.g., PRS data, assistance data, or other location data. Such detecting-only nodes may not transmit signals or data to UEs but may transmit signals or data (relating to, e.g., PRS, assistance data, or other location data) to other network entities (e.g., one or more components of 5G CN 240, external client 230, or a controller) which may receive and store or use the data for positioning of at least UE 105. It is noted that while only one ng-eNB 214 is shown in FIG. 2, some embodiments may include multiple ng-eNBs 214. Base stations (e.g., gNBs 210 and/or ng-eNB 214) may communicate directly with one another via an Xn communication interface. Additionally or alternatively, base stations may communicate directly or indirectly with other components of the 5G NR positioning system 200, such as the LMF 220 and AMF 215.

[0045] 5G NR positioning system 200 may also include one or more WLANs 216 which may connect to a Non-3GPP InterWorking Function (N3IWF) 250 in the 5G CN 240 (e.g., in the case of an untrusted WLAN 216). For example, the WLAN 216 may support IEEE 802.11 Wi-Fi access for UE 105 and may comprise one or more Wi-Fi APs (e.g., APs 130 of FIG. 1). Here, the N3IWF 250 may connect to other elements in the 5G CN 240 such as AMF 215. In some embodiments, WLAN 216 may support another RAT such as Bluetooth. The N3IWF 250 may provide support for secure access by UE 105 to other elements in 5G CN 240 and/or may support interworking of one or more protocols used by WLAN 216 and UE 105 to one or more protocols used by other elements of 5G CN 240 such as AMF 215. For example, N3IWF 250 may support IPSec tunnel establishment with UE 105, termination of IKEv2/IPSec protocols with UE 105, termination of N2 and N3 interfaces to 5G CN 240 for control plane and user plane, respectively, relaying of uplink (UL) and downlink (DL) control plane Non-Access Stratum (NAS) signaling between UE 105 and AMF 215 across an N1 interface. In some other embodiments, WLAN 216 may connect directly to elements in 5G CN 240 (e.g. AMF 215 as shown by the dashed line in FIG. 2) and not via N3IWF 250. For example, direct connection of WLAN 216 to 5GCN 240 may occur if WLAN 216 is a trusted WLAN for 5GCN 240 and may be enabled using a Trusted WLAN Interworking Function (TWIF) (not shown in FIG. 2) which may be an element inside WLAN 216. It is noted that while only one WLAN 216 is shown in FIG. 2, some embodiments may include multiple WLANs 216.

[0046] Access nodes may comprise any of a variety of network entities enabling communication between the UE 105 and the AMF 215. As noted, this can include gNBs 210, ng-eNB 214, WLAN 216, and/or other types of cellular base stations. However, access nodes providing the functionality described herein may additionally or alternatively include entities enabling communications to any of a variety of RATs not illustrated in FIG. 2, which may include non-cellular technologies. Thus, the term “access node,” as used in the embodiments described herein below, may include but is not necessarily limited to a gNB 210, ng-eNB 214 or WLAN 216.

[0047] In some embodiments, an access node, such as a gNB 210, ng-eNB 214, and/or WLAN 216 (alone or in combination with other components of the 5G NR positioning system 200), may be configured to, in response to receiving a request for location information from the LMF 220, obtain location measurements of uplink (UL) signals received from the UE 105) and/or obtain downlink (DL) location measurements from the UE 105 that were obtained by UE 105 for DL signals received by UE 105 from one or more access nodes. As noted, while FIG. 2 depicts access nodes (gNB 210, ng-eNB 214, and WLAN 216) configured to communicate according to 5G NR, LTE, and Wi-Fi communication protocols, respectively, access nodes configured to communicate according to other communication protocols may be used, such as, for example, a Node B using a Wideband Code Division Multiple Access (WCDMA) protocol for a Universal Mobile Telecommunications Service (UMTS) Terrestrial Radio Access Network (UTRAN), an eNB using an LTE protocol for an Evolved UTRAN (E-UTRAN), or a Bluetooth® beacon using a Bluetooth protocol for a WLAN. For example, in a 4G Evolved Packet System (EPS) providing LTE wireless access to UE 105, a RAN may comprise an E-UTRAN, which may comprise base stations comprising eNBs supporting LTE wireless access. A core network for EPS may comprise an Evolved Packet Core (EPC). An EPS may then comprise an E-UTRAN plus an EPC, where the E-UTRAN corresponds to NG-RAN 235 and the EPC corresponds to 5GCN 240 in FIG. 2. The methods and techniques described herein for obtaining a civic location for UE 105 may be applicable to such other networks.

[0048] gNBs 210 and ng-eNB 214 can communicate with an AMF 215, which, for positioning functionality, communicates with an LMF 220. AMF 215 may support mobility of UE 105, including cell change and handover of UE 105 from an access node (e.g., gNB 210, ng-eNB 214, or WLAN 216)of a first RAT to an access node of a second RAT. AMF 215 may also participate in supporting a signaling connection to the UE 105 and possibly data and voice bearers for the UE 105. The LMF 220 may support positioning of UE 105 using a CP location solution when UE 105 accesses the NG-RAN 235 or WLAN 216 and may support position procedures and methods, including UE assisted/UE based and/or network based procedures/methods, such as Assisted GNSS (A- GNSS), Observed Time Difference Of Arrival (OTDOA) (which may be referred to in NR as Time Difference Of Arrival (TDOA)), Real Time Kinematic (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhance Cell ID (ECID), angle of arrival (AoA), angle of departure (AoD), WLAN positioning, round trip signal propagation delay (RTT), multi-cell RTT, and/or other positioning procedures and methods. LMF 220 may also process location service requests for the UE 105, e.g., received from AMF 215 or from GMLC 225. LMF 220 may be connected to AMF 215 and/or to GMLC 225. In some embodiments, a network such as 5GCN 240 may additionally or alternatively implement other types of location-support modules, such as an Evolved Serving Mobile Location Center (E-SMLC) or a SUPL Location Platform (SLP). It is noted that in some embodiments, at least part of the positioning functionality (including determination of a UE 105’s location) may be performed at UE 105 (e.g., by measuring downlink PRS (DL-PRS) signals transmitted by wireless nodes such as gNBs 210, ng-eNB 214 and/or WLAN 216, and/or using assistance data provided to UE 105, e.g., by LMF 220).

[0049] The Gateway Mobile Location Center (GMLC) 225 may support a location request for UE 105 received from an external client 230 and may forward such a location request to AMF 215 for forwarding by the AMF 215 to LMF 220. A location response from LMF 220 (e.g., containing a location estimate for UE 105) may be similarly returned to GMLC 225 either directly or via the AMF 215, and GMLC 225 may then return the location response (e.g., containing the location estimate) to external client 230.

[0050] A Network Exposure Function (NEF) 245 may be included in 5GCN 240. The NEF 245 may support secure exposure of capabilities and events concerning 5GCN 240 and UE 105 to the external client 230, which may then be referred to as an Access Function (AF) and may enable secure provision of information from external client 230 to 5GCN 240. NEF 245 may be connected to AMF 215 and/or to GMLC 225 for the purposes of obtaining a location (e.g. a civic location) of UE 105 and providing the location to external client 230.

[0051] As further illustrated in FIG. 2, the LMF 220 may communicate with the gNBs 210 and/or with the ng-eNB 214 using an NR Positioning Protocol annex (NRPPa) as defined in 3 GPP Technical Specification (TS) 38.455. NRPPa messages may be transferred between a gNB 210 and LMF 220, and/or between an ng-eNB 214 and LMF 220, via the AMF 215. As further illustrated in FIG. 2, LMF 220 and UE 105 may communicate using an LTE Positioning Protocol (LPP) as defined in 3GPP TS 37.355. Here, LPP messages may be transferred between the UE 105 and the LMF 220 via the AMF 215 and a serving gNB 210-1 or serving ng-eNB 214 for UE 105. For example, LPP messages may be transferred between LMF 220 and AMF 215 using messages for service-based operations (e.g., based on the Hypertext Transfer Protocol (HTTP)) and may be transferred between AMF 215 and UE 105 using a 5G NAS protocol. The LPP protocol may be used to support positioning of UE 105 using UE assisted and/or UE based position methods such as A-GNSS, RTK, TDOA, multi-cell RTT, AoD, and/or ECID. The NRPPa protocol may be used to support positioning of UE 105 using network based position methods such as ECID, AoA, uplink TDOA (UL-TDOA) and/or may be used by LMF 220 to obtain location related information from gNBs 210 and/or ng-eNB 214, such as parameters defining DL-PRS transmission from gNBs 210 and/or ng-eNB 214.

[0052] In the case of UE 105 access to WLAN 216, LMF 220 may use NRPPa and/or LPP to obtain a location of UE 105 in a similar manner to that just described for UE 105 access to a gNB 210 or ng-eNB 214. Thus, NRPPa messages may be transferred between a WLAN 216 and LMF 220, via AMF 215 and N3IWF 250 to support network-based positioning of UE 105 and/or transfer of other location information from WLAN 216 to LMF 220. Alternatively, NRPPa messages may be transferred between N3IWF 250 and LMF 220, via AMF 215, to support network-based positioning of UE 105 based on location related information and/or location measurements known to or accessible to N3IWF 250 and transferred from N3IWF 250 to LMF 220 using NRPPa. Similarly, LPP and/or LPP messages may be transferred between UE 105 and LMF 220 via the AMF 215, N3IWF 250, and serving WLAN 216 forUE 105 to support UE assisted or UE based positioning of UE 105 by LMF 220.

[0053] In a 5G NR positioning system 200, positioning methods can be categorized as being “UE assisted” or “UE based.” This may depend on where the request for determining the position of UE 105 originated. If, for example, the request originated at the UE (e.g., from an application, or “app,” executed by the UE), the positioning method may be categorized as being UE based. If, on the other hand, the request originates from an external client or AF 230, LMF 220, or other device or service within the 5G network, the positioning method may be categorized as being UE assisted (or “network-based”).

[0054] With a UE-assisted position method, UE 105 may obtain location measurements and send the measurements to a location server (e.g., LMF 220) for computation of a location estimate for UE 105. For RAT-dependent position methods location measurements may include one or more of a Received Signal Strength Indicator (RS SI), Round Trip signal propagation Time (RTT), Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Reference Signal Time Difference (RSTD), Time of Arrival (TOA), AoA, Receive Time-Transmission Time Difference (Rx-Tx), Differential AoA (DAoA), AoD, or Timing Advance (TA) for gNBs 210, ng- eNB 214, and/or one or more access points for WLAN 216. Additionally or alternatively, similar measurements may be made of sidelink signals transmitted by other UEs, which may serve as anchor points for positioning of the UE 105 if the positions of the other UEs are known. The location measurements may also or instead include measurements for RAT-independent positioning methods such as GNSS (e.g., GNSS pseudorange, GNSS code phase, and/or GNSS carrier phase for GNSS satellites 110), WLAN, etc.

[0055] With a UE-based position method, UE 105 may obtain location measurements (e.g., which may be the same as or similar to location measurements for a UE assisted position method) and may further compute a location of UE 105 (e.g., with the help of assistance data received from a location server such as LMF 220, an SLP, or broadcast by gNBs 210, ng-eNB 214, or WLAN 216). [0056] With a network based position method, one or more base stations (e.g., gNBs 210 and/or ng-eNB 214), one or more APs (e.g., in WLAN 216), or N3IWF 250 may obtain location measurements (e.g., measurements of RSSI, RTT, RSRP, RSRQ, AoA, or TOA) for signals transmitted by UE 105, and/or may receive measurements obtained by UE 105 or by an AP in WLAN 216 in the case of N3IWF 250, and may send the measurements to a location server (e.g., LMF 220) for computation of a location estimate for UE 105.

[0057] Positioning of UE 105 also may be categorized as UL, DL, or DL-UL based, depending on the types of signals used for positioning. If, for example, positioning is based solely on signals received at UE 105 (e.g., from a base station or other UE), the positioning may be categorized as DL based. On the other hand, if positioning is based solely on signals transmitted by UE 105 (which may be received by a base station or other UE, for example), the positioning may be categorized as UL based. Positioning that is DL-UL based includes positioning, such as RTT-based positioning, that is based on signals that are both transmitted and received by UE 105. Sidelink (SL)-assisted positioning comprises signals communicated between UE 105 and one or more other UEs. According to some embodiments, UL, DL, or DL-UL positioning as described herein may be capable of using SL signaling as a complement or replacement of SL, DL, or DL-UL signaling.

[0058] Depending on the type of positioning (e.g., UL, DL, or DL-UL based) the types of reference signals used can vary. For DL-based positioning, for example, these signals may comprise PRS (e.g., DL-PRS transmitted by base stations or SL-PRS transmitted by other UEs), which can be used for TDOA, AoD, and RTT measurements. Other reference signals that can be used for positioning (UL, DL, or DL-UL) may include Sounding Reference Signal (SRS), Channel State Information Reference Signal (CSL RS), synchronization signals (e.g., synchronization signal block (SSB) Synchronizations Signal (SS)), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Physical Sidelink Shared Channel (PSSCH), Demodulation Reference Signal (DMRS), etc. Moreover, reference signals may be transmitted in a Tx beam and/or received in an Rx beam (e.g., using beamforming techniques), which may impact angular measurements, such as AoD and/or AoA. [0059] FIG. 3 is a diagram illustrating a simplified environment 300 including two TRPs 320-1 and 320-2 (which may correspond to base stations 120 of FIG. 1 and/or gNBs 210 and/or ng-eNB 214 of FIG. 2) with antenna arrays that can perform beamforming to produce directional beams for transmitting and/or receiving reference signals. FIG. 3 also illustrates a UE 105, which may also use beamforming for transmitting and/or receiving reference signals. Such directional beams are used in 5G NR wireless communication networks. Each directional beam may have a beam width centered in a different direction, enabling different beams of a TRP 320 to correspond with different areas within a coverage area for TRP 320.

[0060] Different modes of operation may enable TRPs 320-1 and 320-2 to use a larger or smaller number of beams. For example, in a first mode of operation, a TRP 320 may use 16 beams, in which case each beam may have a relatively wide beam width. In a second mode of operation, a TRP 320 may use 64 beams, in which case each beam may have a relatively narrow beam width. Depending on the capabilities of a TRP 320, the TRP may use any number of beams TRP 320 may be capable of forming. The modes of operation and/or number of beams may be defined in relevant wireless standards and may correspond to different directions in either or both azimuth and elevation (e.g., horizontal and vertical directions). Different modes of operation may be used to transmit and/or receive different signal types. Additionally or alternatively, UE 105 may be capable of using different numbers of beams, which may also correspond to different modes of operation, signal types, etc.

[0061] In some situations, a TRP 320 may use beam sweeping. Beam sweeping is a process in which TRP 320 may send an RF signal in different directions using different respective beams, often in succession, effectively “sweeping” across a coverage area. For example, a TRP 320 may sweep across 120 or 360 degrees in an azimuth direction, for each beam sweep, which may be periodically repeated. Each direction beam can include an RF reference signal (e.g., a PRS resource), where base station 120-1 produces a set of RF reference signals that includes Tx beams 305-a, 305-b, 305-c, 305-d, 305-e, 305-f, 305-g, and 305-h, and the base station 120-2 produces a set of RF reference signals that includes Tx beams 309-a, 309-b, 309-c, 309-d, 309-e, 309-f, 309-g, and 309-h. As noted, because UE 105 may also include an antenna array, it can receive RF reference signals transmitted by base stations 120-1 and 120-2 using beamforming to form respective receive beams (Rx beams) 311-a and 311-b. Beamforming in this manner (by base stations 120 and optionally by UEs 105) can be used to make communications more efficient. They can also be used for other purposes, including taking measurements for position determination (e.g., AoD and AoA measurements).

[0062] FIG. 4 is a simplified diagram illustrating how a distributed RID may facilitate the transmission of an RF signal in UE positioning according to an embodiment. Specifically, in the given examples, an RF signal 460 is transmitted by base station 120 (which may comprise a base station for UE 105) and received by UE 105 (a target UE to be positioned) with the presence of a distributed RID 425. For example, RF signal 460 may be transmitted from base station 120, redirected and/or boosted by distributed RID 425, and received by UE 105, where the positioning of UE 105 may be performed based on RF signal 460 transmitted. As noted, in some embodiments, RF signal 460 may be a reference signal specialized in facilitating positioning (e.g., aPRS), which may be a signal that is not otherwise explicitly defined under 5G (or other 3GPP) standards.

[0063] In some embodiments, measurements (e.g., TDOA, AoA, AoD, RSTD, RTT, and/or multi-cell RTT) may be determined based on RF signal 460 received by UE 105. In some embodiments, the positioning processes may be facilitated with the use of a location server 160. Depending on the type of positioning (e.g., UE-based positioning or UE assisted positioning) and/or the desired functionality, UE 105 or location server 160 may be used to determine/calculate the location of UE 105 based on the measurements.

[0064] In some embodiments, distributed RID 425 may be meta-surfaces, reconfigurable intelligent surfaces, or reconfigurable reflect arrays/meta-surfaces controlled by a distributed controller 430 (e.g., a controller not being a network node) that is capable of communicating with other network nodes (e.g., base station 120 and/or location server 160) and is capable of communicating with other UEs through sidelink communication channels. As noted above, distributed RID 425, along with distributed controller 430, may be mounted on RSUs or large vehicles like buses, trucks, etc. As such, distributed RID 425 can enable wireless coverage of base station 120 (or, more broadly, the wireless network of base station 120) to extend to otherwise unreachable areas and/or increase the link quality of the communication established between base station 120 and the UEs.

[0065] In some embodiments, distributed RID 425 may include a software-controlled reflection/scattering profile configured to redirect wireless signals toward UE 105 in real- time. Additionally or alternatively, distributed RID 425 may act as a repeater by receiving signals transmitted by a base station 120 and directing them toward a UE 105. (As used herein, “directing,” “redirecting,” “reflecting,” and similar terms used when referring to the functionality of distributed RID 425 may refer to the reflecting and/or repeating functionality of a RID).

[0066] In some embodiments, when UE 105 determines that a distributed RID (e.g., distributed RID 425, not controlled by a network node) may be and/or are used for positioning (e.g., located within a vicinity of UE 105 and UE 105 may communicate with the controller of the distributed RID over sidelink communication channel(s) to dynamically configure the distributed RID), UE 105 may perform the positioning with the base station (e.g., base station 120) using the distributed RID for improving the accuracy of the positioning. Because the distributed RID is controlled by a distributed controller not being a network node, UE 105 may need to notify the network nodes (e.g., base station 120 and/or the server facilitating the positioning (e.g., location server 160)) to avoid measurements error when positioning UE 105. For example, when using TDOA measurements for positioning UE 105, without the knowledge of the presence of the distributed RID, incorrect positioning range (e.g., incorrect range 445) with regard to the base station may be caused by taking the redirected path (e.g., using the distributed RID) as a direct path between the base station to the target UE.

[0067] Accordingly, in some embodiments, as will be discussed in detail below, after receiving from UE 105, information of distributed RID 425 indicating e.g. availability of distributed RID 425, server 160 may determine a first RID configuration based at least in part on the information of distributed RID 425 for positioning UE 105. The first RID configuration may be communicated directly to the controller of distributed RID 425 or may be shared with UE 105, which may redirect the first RID configuration to the controller of distributed RID 425 over sidelink communication channel(s). Location server 160 may also determine a second RID configuration for reducing interference associated with the positioning of UE 105 caused by distributed RID 425 (e.g., based on an ON-OFF schedule of distributed RID 425). In some embodiments, location server 160 may determine a list of neighboring UEs that locates within a predetermined threshold distance from the distributed RID 425 and/or UE 105 and notify the neighboring UEs availability of distributed RID 425 (e.g., transmit the second RID configuration to the neighboring UEs directly or through UE 105). In some embodiments, the neighboring UEs may be positioned in accordance with the second RID configuration.

[0068] In some embodiments, as will be discussed in detail below, location server 160 may determine the first RID configuration or the second RID configuration based on usage information of distributed RID 425 indicating (1) time and frequency resources over which the RID is available for signal amplification or redirection, (2) a directional relationship between a primary beam pair link between UE 105 and base station 120 and a beam pair link through the distributed RID, or any combination thereof.

[0069] It can be noted that, although a single base station 120, a single distributed RID 425, and a single UE 105 are illustrated in FIG. 4, embodiments are not so limited. According to some embodiments, configurations may be used in which there are a plurality of base stations 120 (transmitters), a plurality of RIDs 425, and/or a different number of UEs 105 (receivers). Furthermore, in instances in which multiple receiving devices are used, a single RID may reflect signals to multiple receiving devices and/or multiple IRSs may be used to reflect or refract signals to multiple receiving devices.

[0070] FIG. 5 is a call-flow diagram illustrating how positioning of a target UE may be performed in a presence of a distributed RID according to an embodiment. In some embodiments, the process may be performed between a server 510, target UE 505, RID 515, and neighboring UEs 520. In some embodiments, server 510 may correspond to location server 160 in FIGS. 1 and 4. Target UE 505 may correspond to UE 105 in FIGS. 1 and 4. Distributed RID 515 may correspond to distributed RID 425 in FIG. 4. Neighboring UEs 520, as will be discussed in detail below, may correspond to any UE that is in the vicinity of RID 515, not positioned using RID 515 and capable of communicating with target UE 505 over sidelink communication channel(s).

[0071] As illustrated in FIG.5, starting at block 525, target UE 505 may determine that a distributed RID (e.g., RID 515) may be used and/or are used (e.g., modifying the communication link between the base station and target UE 505) in the positioning of target UE 505. For example, target UE 505 may determine that RID 515 is not controlled by a network node and may be dynamically configured by target UE, e.g. over a sidelink communication channel established with the distributed controller of RID 515.

[0072] At arrow 530, target UE 505 may transmit information of RID 515 to server 510, indicating the availability of RID 515 for positioning target UE 505. In some embodiments, the information of RID 515 may indicate (1) target UE 505 is capable of controlling RID 515, (2) a unique identification (ID) (e.g., international mobile subscriber identity (IMSI)) associated with the distributed controller of RID 515 or RID 515, (3) an additional processing delay associated with RID 515 (e.g., a delay due to the forwarding of the RF signal in a case where RID 515 is a repeater), (4) a position information of RID 515 (e.g., a zone-ID of the distributed controller of RID 515 shared over the sidelink control channel with target UE 505, and/or the GNSS coordinate of the distributed controller of RID 515 made available to target UE 505 over sidelink application(s), or any combination thereof.

[0073] In some embodiments, at arrow 532, target UE 505 may transmit additional information indicating measurement s) that are determined using RID 515. Additionally or alternatively, some or all of the information regarding the distributed controller of RID 515 may also be indicated in the additional information. In some embodiments, server 510 may configure target UE 505 to transmit the additional information. Additionally or alternatively, UE 505 may be configured to transmit the additional information according to a prior received configuration.

[0074] In some embodiments, at arrow 535, server 510 may request target UE 505 to share/transmit usage information of RID 515. In some embodiments, the usage information of RID 515 may indicate (1) time and/or frequency resources over which RID 515 is available for signal amplification or redirection, (2) a directional relationship between a primary beam pair link between target UE 505 and the base station and a beam pair link through RID 515, or any combination thereof.

[0075] At arrow 537, target UE 505 may transmit the usage information of RID 515 to server 510. For example, the usage information of the RID 515 may include the transmission configuration indicator (TCI) state IDs associated with the RID and the Quasi Co Location (QCL) relationship between the direct path and the path through the RID between the target UE 505 and the base station as determined at the target UE 505. In some embodiments, target UE 505 may obtain the usage information of RID 515 from RID 515, e.g. by communicating with the distributed controller of RID 515 through sidelink communication channels.

[0076] At block 540, server 510 may determine a first RID configuration for improving the quality of the positioning (e.g., increase the positioning accuracy) at least based on the information regarding RID 515 received at arrow 530, additional information received at arrow 532, and/or usage information of RID 515 received at arrow 537.

[0077] At block 545, server 510 may determine a second RID configuration for reducing potential interference associated with the positioning of target UE 505 caused by RID 515 based on an ON-OFF schedule of RID 515. For example, target UE 505 may request the ON-OFF schedule of RID 515 from the distributed controller of RID 515 (e.g., obtain the ON-OFF schedule through a sidelink communication channel) and may forward/transmit the ON-OFF schedule of RID 515 to server 510. In some embodiments, the second RID configuration may indicate a list of time divisional duplex (TDD) slots configuring RID 515 to (1) turn OFF on the listed TDD slots, (2) to use a polarization signature on the listed TDD slots, (3) to transmit signals on the listed TDD slots according to a predetermined transmit power or predetermined beamforming parameters, or any combination thereof.

[0078] At arrow 550, server 510 may transmit the second RID configuration to RID 515 directly through a NW node or indirectly through target UE 505 (e.g., target UE 505 may transmit a request to RID 515 indicating the second RID configuration). For example, server 510 may establish a communication channel with the distributed controller of RID 515 based on the information received from target UE 505. In some embodiments, the second RID configuration may configure RID 515 to turn ON or OFF on certain time intervals.

[0079] Additionally or alternatively, when directly connecting to the distributed controller of the RID 515, server 510 may also perform a positioning session with the distributed controller of RID 515 based on the communication channel established with the distributed controller of RID 515. For example, the position of the distributed controller of RID 515 may be determined through any suitable existing NR/LTE positioning mechanisms. The distributed controller of RID 515 may further share with server 510 the relative position of RID 515 with regard to the distributed controller of RID 515.

[0080] At block 555, server 510 may determine a list of neighboring UEs that locate within the vicinity of RID 515 (e.g., within a predetermined threshold distance from RID 515). In some embodiments, server 510 may determine the list of neighboring UEs based on the cell IDs of server 510 and the distributed controller of RID 515. In some other embodiments, server 510 may also determine the list of neighboring UEs based on GNSS- based location information of server 510 and the distributed controller of RID 515. In some further embodiments, the list of neighboring UEs may be determined by comparing the position estimates of the neighboring UEs with the position information of target UE 505 (e.g., a GNSS position) and/or the distributed controller of RID 515 (e.g., determined based on GNSS/zone ID of the distributed controller of RID 515).

[0081] At block 560, server 510 may transmit the second RID configuration to the neighboring UEs. In some embodiments, the second RID configuration may configure each of the neighboring UEs to (1) determine one or more first measurements during ON periods of RID 515, (2) transmit the one or more first measurements to server 510, and (3) determine one or more second measurements at a time different from the ON periods of RID 515. For example, server 510 may configure the neighboring UEs to stop determining measurements on the ON periods of RID 515 or shift the determination of the measurement away from the ON periods of RID 515 by a fixed offset time.

[0082] In some embodiments, the second RID configuration may be transmitted to the neighboring UEs by target UE 505 or RID 515. For example, target UE 505 and/or the distributed controller of RID 515 may broadcast or group cast the second configuration to the neighboring UEs. Additionally or alternatively, target UE 505 and/or the distributed controller of RID 515 may receive the list of the neighboring UEs from server 510 and may transmit the second RID configuration based on unicast links or a group session established with the neighboring UEs based on the list of the neighboring UEs. In some embodiments, the second RID configuration may include usage information of RID 515 that indicates (1) the time/slots/subframes over which RID 515 will be turned ON, (2) the location/position of RID 515 or the distributed controller of RID 515, (3) an indication of the direction of impact of RID 515 determined based on known TCI-states, beam indices, associated QCL relationships, etc.

[0083] In some embodiments, at block 565, the neighboring UEs may determine if their positioning procedures are impacted by the presence of RID 515. If so, the neighboring UEs may determine to use one or more updated PRS resources for positioning to reduce the impact caused by the presence of RID 515. In some embodiments, the neighboring UEs may notify the updates in the positioning procedure to server 510 and may indicate in the notification that the updates were caused by the operation of RID 515.

[0084] FIG. 6 is a flow diagram of a method 600 for positioning of a target UE (e.g., UE 105 in FIG. 1, and/or UE 505 in FIG. 5) in the presence of a distributed RID (e.g., distributed RID 425 in FIG. 4 and/or RID 515 in FIG. 5), which is performed by a server, according to some embodiments. In some embodiments, the server may correspond to server 160 in FIG. 1 and/or server 510 in FIG. 5. Means/structure for performing the functionality illustrated in one or more of the blocks shown in FIG. 8 may be performed by hardware and/or software components of a computer system, as described herein. Example components of a computer system are illustrated in FIG. 8, which are described in more detail below.

[0085] At block 610, the functionality comprises receiving, from the target UE, information of the distributed RID indicating an availability of the distributed RID, wherein the positioning of the target UE may be performed based on the distributed RID, and wherein the distributed RID is controlled by a distributed controller not being a network node.

[0086] As noted above, the information of the distributed RID may include (1) the target UE is capable of controlling the distributed RID, (2) a unique ID associated with the distributed controller or the distributed RID, (3) an additional processing delay associated with the distributed RID, (4) a position information of the distributed RID, or any combination thereof.

[0087] In some embodiments, method 600 may further include receiving, from the target UE, additional information indicating a position measurement performed based on the distributed RID, wherein the first RID configuration is determined at least based on the additional information.

[0088] Means for performing functionality at block 610 may comprise a bus 905, processor(s) 910, communications subsystem 930, memory 935, and/or other components of computer system 900, as illustrated in FIG. 9.

[0089] At block 620, the functionality comprises determining a first RID configuration for positioning of the target UE based at least in part on the information of the distributed RID. [0090] In some embodiments, method 600 may further include determining a second RID configuration based on an ON-OFF schedule of the distributed RID for reducing interference associated with the positioning of the target UE caused by the distributed RID. In some embodiments, the second RID configuration comprises a list of TDD slots configuring the distributed RID (1) to turn OFF on the listed TDD slots, (2) to use a polarization signature on the listed TDD slots, (3) to transmit signals on the listed TDD slots according to a predetermined transmit power or predetermined beamforming parameters, or any combination thereof.

[0091] In some embodiments, method 600 may further include receiving, from the target UE, usage information of the distributed RID indicating (1) time and frequency resources over which the RID is available for signal amplification or redirection (2) a directional relationship between a primary beam pair link between the target UE and a base station and a beam pair link through the distributed RID, or any combination thereof. In some embodiments, the first RID configuration or the second RID configuration is further determined based on the usage information of the distributed RID. As noted above, in some embodiments, the usage information of the RID may include the TCI-state IDs associated with the RID and the QCL relationship between the direct path and the path through the RID between the target UE and the base station as determined at the target UE.

[0092] Means for performing functionality at block 620 may comprise a bus 905, processor(s) 910, communications subsystem 930, memory 935, and/or other components of computer system 900, as illustrated in FIG. 9.

[0093] At block 630, the functionality comprises sending to the target UE the first RID configuration for positioning the target UE.

[0094] In some embodiments, method 600 may further include sending the second RID configuration to the distributed RID configuring the distributed RID to operate on predetermined time intervals.

[0095] In some embodiments, method 600 may further include (1) positioning the distributed controller, and (2) obtaining a relative position of the distributed RID and the distributed controller. In some embodiments, the first RID configuration or the second RID configuration is determined at least based on the position of the distributed controller and the relative position of the distributed RID and the distributed controller. [0096] In some embodiments, method 600 may further include determining a list of neighboring UEs, where each of the neighboring UEs locates within a predetermined threshold distance from the distributed RID.

[0097] In some embodiments, method 600 may further include sending the second RID configuration to the neighboring UEs indicating the presence of the distributed RID over a device-to-device link, where the neighboring UEs are positioned in accordance with the second RID configuration. In some embodiments, the list of neighboring UEs is determined based on (1) cell IDs of the neighboring UEs and the distributed controller, (2) GNSS-based location information of the neighboring UEs and the distributed controller, (3) comparing estimate positions of the neighboring UEs with a GNSS position of the target UE or a position of the distributed controller, or any combination thereof. In some embodiments, the second RID configuration configures each of the neighboring UEs to (1) determine one or more first measurements during ON periods of the distributed RID, (2) transmit the one or more first measurements to the server, (3) and determine one or more second measurements at a time different from the ON periods of the distributed RID.

[0098] Means for performing functionality at block 630 a bus 905, processor(s) 910, communications subsystem 930, memory 935, and/or other components of computer system 900, as illustrated in FIG. 9.

[0099] FIG. 7 is a flow diagram of a method for positioning of a target UE in the presence of a distributed RID (e.g., distributed RID 425 in FIG. 4 and/or RID 515 in FIG. 5), which is performed by the target UE, according to some embodiments. In some embodiments, the UE may correspond to UE 105 in FIG. 1, and/or UE 505 in FIG. 5. Means/structure for performing the functionality illustrated in one or more of the blocks shown in FIG. 7 may be performed by hardware and/or software components of a UE, as described herein. Example components of a UE are illustrated in FIG. 10, which are described in more detail below.

[0100] At block 710, the functionality comprises determining that a distributed RID may be used in positioning of the target UE, wherein the distributed RID is controlled by a distributed controller not being a network node. [0101] Means for performing functionality at block 710 may comprise a bus 805, processor(s) 810, wireless communication interface 830, memory 860, and/or other components of a UE 800, as illustrated in FIG. 8.

[0102] At block 720, the functionality comprises sending, to a server (e.g., server 160 in FIG. 1 and/or server 510 in FIG. 5), information of the distributed RID indicating the availability of the distributed RID.

[0103] As noted above, the information of the distributed RID may include (1) the target UE is capable of controlling the distributed RID, (2) a unique ID associated with the distributed controller or the distributed RID, (3) an additional processing delay associated with the distributed RID, (4) a position information of the distributed RID, or any combination thereof.

[0104] In some embodiments, method 700 may further include transmitting, to the server, additional information indicating a position measurement performed based on the distributed RID, wherein the first RID configuration is determined at least based on the additional information.

[0105] In some embodiments, method 700 may further include receiving from the distributed controller, usage information of the distributed RID indicating (1) time and frequency resources over which the RID is available for signal amplification or redirection (2) a directional relationship between a primary beam pair link between the target UE and a base station and a beam pair link through the distributed RID, or any combination thereof. In some embodiments, the first RID configuration and/or the second RID configuration is further determined based on the usage information of the distributed RID. In some embodiments, the usage information of the RID may include the TCI-state IDs associated with the RID and the QCL relationship between the direct path and the path through the RID between the target UE and the base station as determined at the target UE.

[0106] In some embodiments, method 700 may further include transmitting, to the server, the usage information of the distributed RID for determining the first RID configuration or the second RID configuration. [0107] Means for performing functionality at block 720 may comprise a bus 805, processor(s) 810, wireless communication interface 830, memory 860, and/or other components of a UE 800, as illustrated in FIG. 8.

[0108] At block 730, the functionality comprises receiving, from the server, the first RID configuration for the positioning of the target UE determined based at least in part on the information of the distributed RID.

[0109] In some embodiments, method 700 may further include receiving a second RID configuration based on an ON-OFF schedule of the distributed RID for reducing interference associated with the positioning of the target UE caused by the distributed RID. In some embodiments, the second RID configuration comprises a list of TDD slots configuring the distributed RID (1) to turn OFF on the listed TDD slots, (2) to use a polarization signature on the listed TDD slots, (3) to transmit signals on the listed TDD slots according to a predetermined transmit power or predetermined beamforming parameters, or any combination thereof.

[0110] In some embodiments, method 700 may further include obtaining a list of neighboring UEs, where each of the neighboring UEs locates within a predetermined threshold distance from the distributed RID, and notifying the neighboring UEs usage information of the distributed RID indicating (1) time and frequency resources over which the RID is turned ON, (2) a position of the distributed RID or the distributed controller, (3) an indication of a direction impact of the distributed RID, or any combination thereof.

[OHl] Means for performing functionality at block 730 may comprise a bus 805, processor(s) 810, wireless communication interface 830, memory 860, and/or other components of a UE 800, as illustrated in FIG. 8.

[0112] FIG. 8 is a block diagram of an embodiment of a UE 800, which can be utilized as described herein (e.g., in association with the previously described figures). In some embodiments, for example, the UE 800 may comprise, for example, a mobile (e.g., movable/portable) device (e.g., tablet, laptop, vehicle, etc.). It should be noted that FIG. 8 is meant only to provide a generalized illustration of various components, any or all of which may be utilized as appropriate.

[0113] The UE 800 is shown to comprise hardware elements that can be electrically coupled via a bus 805 (or may otherwise be in communication, as appropriate). The hardware elements may include a processor(s) 810 which can include without limitation one or more general -purpose processors (e.g., an application processor), one or more special-purpose processors (such as digital signal processor (DSP) chips, graphics acceleration processors, application specific integrated circuits (ASICs), and/or the like), and/or other processing structures or means. Processor(s) 810 may comprise one or more processing units, which may be housed in a single integrated circuit (IC) or multiple Ics. As shown in FIG. 8, some embodiments may have a separate DSP 820, depending on desired functionality. Location determination and/or other determinations based on wireless communication may be provided in the processor(s) 810 and/or wireless communication interface 830 (discussed below). The UE 800 also can include one or more input devices 870, which can include without limitation one or more keyboards, touch screens, touch pads, microphones, buttons, dials, switches, and/or the like; and one or more output devices 815, which can include without limitation one or more displays (e.g., touch screens), light emitting diodes (LEDs), speakers, and/or the like.

[0114] The UE 800 may also include a wireless communication interface 830, which may comprise without limitation a modem, a network card, an infrared communication device, a wireless communication device, and/or a chipset (such as a Bluetooth® device, an IEEE 802.11 device, an IEEE 802.15.4 device, a Wi-Fi device, a WiMAX device, a WAN device, and/or various cellular devices, etc.), and/or the like, which may enable the UE 800 to communicate with other devices as described in the embodiments above. The wireless communication interface 830 may permit data and signaling to be communicated (e.g., transmitted and received) with base stations of a network, for example, via eNBs, gNBs, ng-eNBs, access points, various base stations and/or other access node types, and/or other network components, computer systems, and/or any other electronic devices communicatively coupled with base stations, as described herein. The communication can be carried out via one or more wireless communication antenna(s) 832 that send and/or receive wireless signals 834. According to some embodiments, the wireless communication antenna(s) 832 may comprise a plurality of discrete antennas, antenna arrays, or any combination thereof. The antenna(s) 832 may be capable of transmitting and receiving wireless signals using beams (e.g., Tx beams and Rx beams). Beam formation may be performed using digital and/or analog beam formation techniques, with respective digital and/or analog circuitry. The wireless communication interface 830 may include such circuitry. [0115] Depending on desired functionality, the wireless communication interface 830 may comprise a separate receiver and transmitter, or any combination of transceivers, transmitters, and/or receivers to communicate with base stations (e.g., ng-eNBs and gNBs) and other terrestrial transceivers, such as wireless devices and access points. The UE 800 may communicate with different data networks that may comprise various network types. For example, one such network type may comprise a wireless wide area network (WWAN), which may be a code-division multiple access (CDMA) network, a time division multiple access (TDMA) network, a frequency division multiple access (FDMA) network, an orthogonal frequency division multiple access (OFDMA) network, a single-carrier frequency division multiple access (SC-FDMA) network, a WiMAX (IEEE 802.16) network, and so on. A CDMA network may implement one or more radio access technologies (RATs) such as CDMA2000®, wideband code division multiple access (WCDMA), and so on. CDMA2000® includes IS-95, IS-2000 and/or IS-856 standards. A TDMA network may implement global system for mobile communications (GSM), digital advanced mobile phone system (D-AMPS), or some other RAT. An OFDMA network may employ long-term evolution (LTE), LTE Advanced, fifthgeneration (5G) new radio (NR), and so on. 5G NR, LTE, LTE Advanced, GSM, and WCDMA are described in documents from 3^rd Generation Partnership Project (3GPP). CDMA2000® is described in documents from a consortium named “3^rd Generation Partnership Project 2” (3GPP2). 3 GPP and 3GPP2 documents are publicly available. A wireless local area network (WLAN) may also be an IEEE 802.1 lx network, and a wireless personal area network (WPAN) may be a Bluetooth network, an IEEE 802.15x, or some other type of network. The techniques described herein may also be used for any combination of WWAN, WLAN and/or WPAN.

[0116] The UE 800 can further include sensor(s) 840. Sensor(s) 840 may comprise, without limitation, one or more inertial sensors and/or other sensors (e.g., accelerometer(s), gyroscope(s), camera(s), magnetometer(s), altimeter(s), microphone(s), proximity sensor(s), light sensor(s), barometer(s), and the like), some of which may be used to obtain position-related measurements and/or other information.

[0117] Embodiments of the UE 800 may further comprise a sensing unit 850. The sensing unit 850 may comprise hardware and/or software components capable of transmitting and/or receiving RF signals (e.g., RS) to detect one or more targets in the manner described herein. The sensing unit 850 may comprise a standalone component connected with a bus 805, as illustrated, or may be incorporated into another component (e.g., the wireless indication interface 830). Further, the sensing unit 850 may be communicatively coupled with an antenna 832, which it may share with the wireless communication interface 830. Additionally or alternatively, the sensing unit 850 may have its own antenna (not shown). In some embodiments, the sensing unit 850 may be communicatively coupled with multiple antennas or an antenna array capable of sending and/or receiving RF signals via directional beams.

[0118] Embodiments of the UE 800 may also include a Global Navigation Satellite System (GNSS) receiver 880 capable of receiving signals 884 from one or more GNSS satellites using an antenna 882 (which could be the same as antenna 832). Positioning based on GNSS signal measurement can be utilized to complement and/or incorporate the techniques described herein. The GNSS receiver 880 can extract a position of the UE 800, using conventional techniques, from GNSS satellites of a GNSS system, such as Global Positioning System (GPS), Galileo, GLONASS, Quasi-Zenith Satellite System (QZSS) over Japan, IRNSS over India, BeiDou Navigation Satellite System (BDS) over China, and/or the like. Moreover, the GNSS receiver 880 can be used with various augmentation systems (e.g., a Satellite Based Augmentation System (SBAS)) that may be associated with or otherwise enabled for use with one or more global and/or regional navigation satellite systems, such as, e.g., Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multi-functional Satellite Augmentation System (MSAS), and Geo Augmented Navigation system (GAGAN), and/or the like.

[0119] It can be noted that, although GNSS receiver 880 is illustrated in FIG. 8 as a distinct component, embodiments are not so limited. As used herein, the term “GNSS receiver” may comprise hardware and/or software components configured to obtain GNSS measurements (measurements from GNSS satellites). In some embodiments, therefore, the GNSS receiver may comprise a measurement engine executed (as software) by one or more processors, such as processor(s) 810, DSP 820, and/or a processor within the wireless communication interface 830 (e.g., in a modem). A GNSS receiver may optionally also include a positioning engine, which can use GNSS measurements from the measurement engine to determine a position of the GNSS receiver using an Extended Kalman Filter (EKF), Weighted Least Squares (WLS), particle filter, or the like. The positioning engine may also be executed by one or more processors, such as processor(s) 810 or DSP 820.

[0120] The UE 800 may further include and/or be in communication with a memory 860. The memory 860 can include, without limitation, local and/or network accessible storage, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random-access memory (RAM), and/or a read-only memory (ROM), which can be programmable, flash-updateable, and/or the like. Such storage devices may be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and/or the like.

[0121] The memory 860 of the UE 800 also can comprise software elements (not shown in FIG. 8), including an operating system, device drivers, executable libraries, and/or other code, such as one or more application programs, which may comprise computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein. Merely by way of example, one or more procedures described with respect to the method(s) discussed above may be implemented as code and/or instructions in memory 860 that are executable by the UE 800 (and/or processor(s) 810 or DSP 820 within UE 800). In some embodiments, then, such code and/or instructions can be used to configure and/or adapt a general-purpose computer (or other devices) to perform one or more operations in accordance with the described methods.

[0122] FIG. 9 is a block diagram of an embodiment of a computer system 900, which may be used, in whole or in part, to provide the functions of one or more components and/or devices as described in the embodiments herein, including a server (e.g., sensing server/SMF, location server/LMF, etc.) in communication with one or more base stations and/or one or more sensing nodes to coordinate RF sensing as described in embodiments herein. This may include, for example, a computer server, personal computer, personal electronic device, or the like. It should be noted that FIG. 9 is meant only to provide a generalized illustration of various components, any or all of which may be utilized as appropriate. FIG. 9, therefore, broadly illustrates how individual system elements may be implemented in a relatively separated or relatively more integrated manner. In addition, it can be noted that components illustrated by FIG. 9 can be localized to a single device and/or distributed among various networked devices, which may be disposed at different geographical locations.

[0123] The computer system 900 is shown comprising hardware elements that can be electrically coupled via a bus 905 (or may otherwise be in communication, as appropriate). The hardware elements may include processor(s) 910, which may comprise without limitation one or more general-purpose processors, one or more special-purpose processors (such as digital signal processing chips, graphics acceleration processors, and/or the like), and/or other processing structure, which can be configured to perform one or more of the methods described herein. The computer system 900 also may comprise one or more input devices 915, which may comprise without limitation a mouse, a keyboard, a camera, a microphone, and/or the like; and one or more output devices 920, which may comprise without limitation a display device, a printer, and/or the like.

[0124] The computer system 900 may further include (and/or be in communication with) one or more non-transitory storage devices 925, which can comprise, without limitation, local and/or network accessible storage, and/or may comprise, without limitation, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random-access memory (RAM) and/or read-only memory (ROM), which can be programmable, flash-updateable, and/or the like. Such storage devices may be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and/or the like. Such data stores may include database(s) and/or other data structures used store and administer messages and/or other information to be sent to one or more devices via hubs, as described herein.

[0125] The computer system 900 may also include a communications subsystem 930, which may comprise wireless communication technologies managed and controlled by a wireless communication interface 933, as well as wired technologies (such as Ethernet, coaxial communications, universal serial bus (USB), and the like). The wireless communication interface 933 may comprise one or more wireless transceivers that may send and receive wireless signals 955 (e.g., signals according to 5G NR or LTE) via wireless antenna(s) 950. Thus the communications subsystem 930 may comprise a modem, a network card (wireless or wired), an infrared communication device, a wireless communication device, and/or a chipset, and/or the like, which may enable the computer system 900 to communicate on any or all of the communication networks described herein to any device on the respective network, including a User Equipment (UE), base stations and/or other transmission reception points (TRPs), and/or any other electronic devices described herein. Hence, the communications subsystem 930 may be used to receive and send data as described in the embodiments herein.

[0126] In many embodiments, the computer system 900 will further comprise a working memory 935, which may comprise a RAM or ROM device, as described above. Software elements, shown as being located within the working memory 935, may comprise an operating system 940, device drivers, executable libraries, and/or other code, such as one or more applications 945, which may comprise computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein. Merely by way of example, one or more procedures described with respect to the method(s) discussed above might be implemented as code and/or instructions executable by a computer (and/or a processor within a computer); in an aspect, then, such code and/or instructions can be used to configure and/or adapt a general purpose computer (or other device) to perform one or more operations in accordance with the described methods.

[0127] A set of these instructions and/or code might be stored on a non-transitory computer-readable storage medium, such as the storage device(s) 925 described above. In some cases, the storage medium might be incorporated within a computer system, such as computer system 900. In other embodiments, the storage medium might be separate from a computer system (e.g., a removable medium, such as an optical disc), and/or provided in an installation package, such that the storage medium can be used to program, configure, and/or adapt a general-purpose computer with the instructions/code stored thereon. These instructions might take the form of executable code, which is executable by the computer system 900 and/or might take the form of source and/or installable code, which, upon compilation and/or installation on the computer system 900 (e.g., using any of a variety of generally available compilers, installation programs, compression/decompression utilities, etc.), then takes the form of executable code.

[0128] It will be apparent to those skilled in the art that substantial variations may be made in accordance with specific requirements. For example, customized hardware might also be used and/or particular elements might be implemented in hardware, software (including portable software, such as applets, etc.), or both. Further, connection to other computing devices such as network input/output devices may be employed.

[0129] With reference to the appended figures, components that can include memory can include non-transitory machine-readable media. The term “machine-readable medium” and “computer-readable medium” as used herein, refer to any storage medium that participates in providing data that causes a machine to operate in a specific fashion. In embodiments provided hereinabove, various machine-readable media might be involved in providing instructions/code to processors and/or other device(s) for execution. Additionally or alternatively, the machine-readable media might be used to store and/or carry such instructions/code. In many implementations, a computer-readable medium is a physical and/or tangible storage medium. Such a medium may take many forms, including but not limited to, non-volatile media and volatile media. Common forms of computer-readable media include, for example, magnetic and/or optical media, any other physical medium with patterns of holes, a RAM, a programmable ROM (PROM), erasable PROM (EPROM), a FLASH-EPROM, any other memory chip or cartridge, or any other medium from which a computer can read instructions and/or code.

[0130] The methods, systems, and devices discussed herein are examples. Various embodiments may omit, substitute, or add various procedures or components as appropriate. For instance, features described with respect to certain embodiments may be combined in various other embodiments. Different aspects and elements of the embodiments may be combined in a similar manner. The various components of the figures provided herein can be embodied in hardware and/or software. Also, technology evolves and, thus many of the elements are examples that do not limit the scope of the disclosure to those specific examples.

[0131] It has proven convenient at times, principally for reasons of common usage, to refer to such signals as bits, information, values, elements, symbols, characters, variables, terms, numbers, numerals, or the like. It should be understood, however, that all of these or similar terms are to be associated with appropriate physical quantities and are merely convenient labels. Unless specifically stated otherwise, as is apparent from the discussion above, it is appreciated that throughout this Specification discussion utilizing terms such as “processing,” “computing,” “calculating,” “determining,” “ascertaining,” “identifying,” “associating,” “measuring,” “performing,” or the like refer to actions or processes of a specific apparatus, such as a special purpose computer or a similar special purpose electronic computing device. In the context of this Specification, therefore, a special purpose computer or a similar special purpose electronic computing device is capable of manipulating or transforming signals, typically represented as physical electronic, electrical, or magnetic quantities within memories, registers, or other information storage devices, transmission devices, or display devices of the special purpose computer or similar special purpose electronic computing device.

[0132] Terms, “and” and “or” as used herein, may include a variety of meanings that also is expected to depend, at least in part, upon the context in which such terms are used. Typically, “or” if used to associate a list, such as A, B, or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B, or C, here used in the exclusive sense. In addition, the term “one or more” as used herein may be used to describe any feature, structure, or characteristic in the singular or may be used to describe some combination of features, structures, or characteristics. However, it should be noted that this is merely an illustrative example and claimed subject matter is not limited to this example. Furthermore, the term “at least one of’ if used to associate a list, such as A, B, or C, can be interpreted to mean any combination of A, B, and/or C, such as A, AB, AA, AAB, AABBCCC, etc.

[0133] Having described several embodiments, various modifications, alternative constructions, and equivalents may be used without departing from the scope of the disclosure. For example, the above elements may merely be a component of a larger system, wherein other rules may take precedence over or otherwise modify the application of the various embodiments. Also, a number of steps may be undertaken before, during, or after the above elements are considered. Accordingly, the above description does not limit the scope of the disclosure.

[0134] In view of this description embodiments may include different combinations of features. Implementation examples are described in the following numbered clauses:

Clause 1. An example method of positioning of a target UE in a presence of a distributed RID, the method performed by a server and may comprise receiving, from the target UE, information of the distributed RID indicating an availability of the distributed RID, wherein the positioning of the target UE may be performed using the distributed RID, and wherein the distributed RID is controlled by a distributed controller not being a network node. The method may also comprise determining a first RID configuration for positioning of the target UE based at least in part on the information of the distributed RID and sending to the target UE the first RID configuration for positioning the target UE.

Clause 2. The method of the clause 1, wherein the information of the distributed RID indicates: the target UE is capable of controlling the distributed RID; a unique identification (ID) associated with the distributed controller or the distributed RID; an additional processing delay associated with the distributed RID; a position information of the distributed RID; or any combination thereof.

Clause 3. The method of any of clause 1 or 2, further comprising: receiving, from the target UE, additional information indicating a position measurement performed based on the distributed RID, wherein the first RID configuration is determined at least based on the additional information.

Clause 4. The method of any of clauses 1-3, further comprising: determining a second RID configuration based on an ON-OFF schedule of the distributed RID for reducing interference associated with the positioning of the target UE caused by the distributed RID.

Clause 5. The method of any of clauses 1-4 further comprising: receiving, from the target UE, usage information of the distributed RID indicating: time and frequency resources over which the RID is available for signal amplification or redirection; a directional relationship between a primary beam pair link between the target UE and a base station and a beam pair link through the distributed RID; or any combination thereof, wherein the first RID configuration or the second RID configuration is further determined based on the usage information of the distributed RID.

Clause 6. The method of any of clauses 1-5, wherein the usage information of the RID comprises the TCI-state IDs associated with the RID and the QCL relationship between the direct path and the path through the RID between the target UE and the base station as determined at the target UE. Clause 7. The method of any of clauses 1-6, wherein the second RID configuration comprises a list of time divisional duplex (TDD) slots configuring the distributed RID: to turn OFF on the listed TDD slots; to use a polarization signature on the listed TDD slots; to transmit signals on the listed TDD slots according to a predetermined transmit power or predetermined beamforming parameters; or any combination thereof.

Clause 8. The method of any of clauses 1-7, further comprising: sending the second RID configuration to the distributed RID configuring the distributed RID to operate on predetermined time intervals.

Clause 9. The method of any of clauses 1-8, further comprising: positioning the distributed controller; and obtaining a relative position of the distributed RID and the distributed controller, wherein the first RID configuration or the second RID configuration is determined at least based on the position of the distributed controller and the relative position of the distributed RID and the distributed controller.

Clause 10. The method of any of clauses 1-9, further comprising: determining a list of neighboring UEs, wherein each of the neighboring UEs locates within a predetermined threshold distance from the distributed RID; and sending the second RID configuration to the neighboring UEs indicating the presence of the distributed RID over a device-to-device link, wherein the neighboring UEs are positioned in accordance with the second RID configuration.

Clause 11. The method of any of clauses 1-10, wherein the list of neighboring UEs is determined based on: cell IDs of the neighboring UEs and the distributed controller; Global Navigation Satellite System (GNSS)-based location information of the neighboring UEs and the distributed controller; comparing estimate positions of the neighboring UEs with a GNSS position of the target UE or a position of the distributed controller; or any combination thereof.

Clause 12. The method of any of clauses 1-11, wherein the second RID configuration configures each of the neighboring UEs to: determine one or more first measurements during ON periods of the distributed RID; transmit the one or more first measurements to the server; and determine one or more first second measurements at a time different from the ON periods of the distributed RID.

Clause 13. An example method of positioning of a target UE in a presence of a RID, the method performed by the target UE and may comprise determining that a distributed RID may be used in positioning of the target UE, wherein the distributed RID is controlled by a distributed controller not being a network node. The method may also comprise sending, to a server, information of the distributed RID indicating availability of the distributed RID and receiving, from the server, a first RID configuration for the positioning of the target UE determined based at least in part on the information of the distributed RID.

Clause 14. The method of the clause 13, wherein the information of the distributed RID indicates: the target UE is capable of controlling the distributed RID; a unique ID associated with the distributed controller or the distributed RID; an additional processing delay associated with the distributed RID; a position information of the distributed RID; or any combination thereof.

Clause 15. The method of any of clause 13 or 14, further comprising: transmitting, to the server, additional information indicating a position measurement performed based on the distributed RID, wherein the first RID configuration is determined at least based on the additional information.

Clause 16. The method of any of clauses 13-15, further comprising: determining a second RID configuration based on an ON-OFF schedule of the distributed RID for reducing interference associated with the positioning of the target UE caused by the distributed RID.

Clause 17. The method of any of clauses 13-16 further comprising: receiving, from the target UE, usage information of the distributed RID indicating: time and frequency resources over which the RID is available for signal amplification or redirection; a directional relationship between a primary beam pair link between the target UE and a base station and a beam pair link through the distributed RID; or any combination thereof, wherein the first RID configuration or the second RID configuration is further determined based on the usage information of the distributed RID. Clause 18. The method of any of clauses 13-17, wherein the usage information of the RID comprises the TCI-state IDs associated with the RID and the QCL relationship between the direct path and the path through the RID between the target UE and the base station as determined at the target UE.

Clause 19. The method of any of clauses 13-18, wherein the second RID configuration comprises a list of time divisional duplex (TDD) slots configuring the distributed RID: to turn OFF on the listed TDD slots; to use a polarization signature on the listed TDD slots; to transmit signals on the listed TDD slots according to a predetermined transmit power or predetermined beamforming parameters; or any combination thereof.

Clause 20. The method of any of clauses 13-19, further comprising: obtaining a list of neighboring UEs, wherein each of the neighboring UEs locates within a predetermined threshold distance from the distributed RID; and notifying, the neighboring UEs, usage information of the distributed RID indicating: time and frequency resources over which the RID is turned ON; a position of the distributed RID or the distributed controller; an indication of a direction impact of the distributed RID; or any combination thereof.

Clause 21. An example server for positioning of a target UE in a presence of a distributed RID comprising a transceiver, a memory, and one or more processors communicatively coupled with the transceiver and the memory. The one or more processors may be configured to receive, from the target UE, information of the distributed RID indicating an availability of the distributed RID, wherein the positioning of the target UE may be performed using the distributed RID, and wherein the distributed RID is controlled by a distributed controller not being a network node. The one or more processors may also be configured to determine a first RID configuration for positioning of the target UE based at least in part on the information of the distributed RID. The one or more processors may further be configured to send to the target UE the first RID configuration for positioning the target UE.

Clause 22. The server of the clause 21, wherein the information of the distributed RID indicates: the target UE is capable of controlling the distributed RID; a unique ID associated with the distributed controller or the distributed RID; an additional processing delay associated with the distributed RID; a position information of the distributed RID; or any combination thereof.

Clause 23. The server of any of clause 21 or 22, wherein the one or more processors are further configured to: receive, from the target UE, additional information indicating a position measurement performed based on the distributed RID, wherein the first RID configuration is determined at least based on the additional information.

Clause 24. The server of any of clauses 21-23, wherein the one or more processors are further configured to: determine a second RID configuration based on an ON-OFF schedule of the distributed RID for reducing interference associated with the positioning of the target UE caused by the distributed RID.

Clause 25. The server of any of clauses 21-24, wherein the one or more processors are further configured to: receive, from the target UE, usage information of the distributed RID indicating: time and frequency resources over which the RID is available for signal amplification or redirection; a directional relationship between a primary beam pair link between the target UE and a base station and a beam pair link through the distributed RID; or any combination thereof, wherein the first RID configuration or the second RID configuration is further determined based on the usage information of the distributed RID.

Clause 26. The server of any of clauses 21-25, wherein the usage information of the RID comprises the TCI-state IDs associated with the RID and the QCL relationship between the direct path and the path through the RID between the target UE and the base station as determined at the target UE.

Clause 27. An example target UE for positioning in a presence of a RID comprising a transceiver, a memory, and one or more processors communicatively coupled with the transceiver and the memory. The one or more processors may be configured to determine that a distributed RID may be used in positioning of the target UE, wherein the distributed RID is controlled by a distributed controller not being a network node. The one or more processors may also be configured to send, to a server, information of the distributed RID indicating availability of the distributed RID. The one or more processors may further be configured to receive, from the server, a first RID configuration for the positioning of the target UE determined based at least in part on the information of the distributed RID.

Clause 28. The target UE of the clause 27, wherein the information of the distributed RID indicates: the target UE is capable of controlling the distributed RID; a unique ID associated with the distributed controller or the distributed RID; an additional processing delay associated with the distributed RID; a position information of the distributed RID; or any combination thereof.

Clause 29. The target UE of any of clause 27 or 28, wherein the one or more processors are further configured to: transmit, to the server, additional information indicating a position measurement performed based on the distributed RID, wherein the first RID configuration is determined at least based on the additional information.

Clause 30. The target UE of any of clauses 27-29, wherein the one or more processors are further configured to: receive a second RID configuration based on an ON-OFF schedule of the distributed RID for reducing interference associated with the positioning of the target UE caused by the distributed RID.

Claims

WHAT IS CLAIMED IS:

1. A method of positioning of a target User Equipment (UE) in a presence of a distributed reconfigurable intelligent device (RID), the method performed by a server and comprising: receiving, from the target UE, information of the distributed RID indicating an availability of the distributed RID, wherein the positioning of the target UE may be performed using the distributed RID, and wherein the distributed RID is controlled by a distributed controller not being a network node; determining a first RID configuration for positioning of the target UE based at least in part on the information of the distributed RID; and sending to the target UE the first RID configuration for positioning the target UE.

2. The method of claim 1, wherein the information of the distributed RID indicates: the target UE is capable of controlling the distributed RID; a unique identification (ID) associated with the distributed controller or the distributed RID; an additional processing delay associated with the distributed RID; a position information of the distributed RID; or any combination thereof.

3. The method of claim 1, further comprising: receiving, from the target UE, additional information indicating a position measurement performed based on the distributed RID, wherein the first RID configuration is determined at least based on the additional information.

4. The method of claim 1, further comprising: determining, based on an ON-OFF schedule of the distributed RID, a second RID configuration for reducing interference associated with the positioning of the target UE caused by the distributed RID.

5. The method of claim 4, further comprising: receiving, from the target UE, usage information of the distributed RID indicating: time and frequency resources over which the RID is available for signal amplification or redirection; a directional relationship between a primary beam pair link between the target UE and a base station and a beam pair link through the distributed RID; or any combination thereof, wherein the first RID configuration or the second RID configuration is further determined based on the usage information of the distributed RID.

6. The method of claim 5, wherein the usage information of the RID comprises TCI-state IDs associated with the RID and a QCL relationship between a direct path and a path through the RID between the target UE and the base station as determined at the target UE.

7. The method of claim 4, wherein the second RID configuration comprises a list of time divisional duplex (TDD) slots configuring the distributed RID: to turn OFF on the listed TDD slots; to use a polarization signature on the listed TDD slots; to transmit signals on the listed TDD slots according to a predetermined transmit power or predetermined beamforming parameters; or any combination thereof.

8. The method of claim 4, further comprising: sending the second RID configuration to the distributed RID configuring the distributed RID to operate on predetermined time intervals.

9. The method of claim 4, further comprising: positioning the distributed controller; and obtaining a relative position of the distributed RID with respect to the distributed controller, wherein the first RID configuration or the second RID configuration is determined at least based on the position of the distributed controller and the relative position of the distributed RID and the distributed controller.

10. The method of claim 4, further comprising: determining a list of neighboring UEs, wherein each of the neighboring UEs locates within a predetermined threshold distance from the distributed RID; and sending the second RID configuration to the neighboring UEs indicating the presence of the distributed RID over a device-to-device link, wherein the neighboring UEs are positioned in accordance with the second RID configuration.

11. The method of claim 10, wherein the list of neighboring UEs is determined based on: cell IDs of the neighboring UEs and the distributed controller;

Global Navigation Satellite System (GNSS)-based location information of the neighboring UEs and the distributed controller; comparing estimate positions of the neighboring UEs with a GNSS position of the target UE or a position of the distributed controller; or any combination thereof.

12. The method of claim 10, wherein the second RID configuration configures each of the neighboring UEs to: determine one or more first measurements during ON periods of the distributed RID; transmit the one or more first measurements to the server; and determine one or more second measurements at a time different from the ON periods of the distributed RID.

13. A method of positioning of a target User Equipment (UE) in a presence of a distributed reconfigurable intelligent device (RID), the method performed by the target UE and comprising: determining that a distributed RID may be used in positioning of the target UE, wherein the distributed RID is controlled by a distributed controller not being a network node; sending, to a server, information of the distributed RID indicating availability of the distributed RID; and receiving, from the server, a first RID configuration for the positioning of the target UE determined based at least in part on the information of the distributed RID.

14. The method of claim 13, wherein the information of the distributed RID indicates: the target UE is capable of controlling the distributed RID; a unique identification (ID) associated with the distributed controller or the distributed RID; an additional processing delay associated with the distributed RID; a position information of the distributed RID; or any combination thereof.

15. The method of claim 13, further comprising: transmitting, to the server, additional information indicating a position measurement performed based on the distributed RID, wherein the first RID configuration is determined at least based on the additional information.

16. The method of claim 13, further comprising: receiving a second RID configuration based on an ON-OFF schedule of the distributed RID for reducing interference associated with the positioning of the target UE caused by the distributed RID.

17. The method of claim 16, further comprising: receiving, from the distributed controller, usage information of the distributed RID indicating: time and frequency resources over which the RID is available for signal amplification or redirection; a directional relationship between a primary beam pair link between the target UE and a base station and a beam pair link through the distributed RID; or any combination thereof, transmitting, to the server, the usage information of the distributed RID for determining the first RID configuration or the second RID configuration.

18. The method of claim 17, the usage information of the RID comprises TCI-state IDs associated with the RID and a QCL relationship between a direct path and a path through the RID between the target UE and the base station as determined at the target UE.

19. The method of claim 16, wherein the second RID configuration comprises a list of time divisional duplex (TDD) slots configuring the distributed RID: to turn OFF on the listed TDD slots; to use a polarization signature on the listed TDD slots; to transmit signals on the listed TDD slots according to a predetermined transmit power or predetermined beamforming parameters; or any combination thereof.

20. The method of claim 16, further comprising: obtaining a list of neighboring UEs, wherein each of the neighboring UEs locates within a predetermined threshold distance from the distributed RID; and notifying, the neighboring UEs, usage information of the distributed RID indicating: time and frequency resources over which the RID is turned ON; a position of the distributed RID or the distributed controller; an indication of a direction impact of the distributed RID; or any combination thereof.

21. A server for positioning of a target User Equipment (UE) in a presence of a distributed reconfigurable intelligent device (RID), comprising: a transceiver; a memory; and one or more processors communicatively coupled with the transceiver and the memory, wherein the one or more processors are configured to: receive, from the target UE, information of the distributed RID indicating an availability of the distributed RID, wherein the positioning of the target UE may be performed using the distributed RID, and wherein the distributed RID is controlled by a distributed controller not being a network node; determine a first RID configuration for positioning of the target UE based at least in part on the information of the distributed RID; and send to the target UE the first RID configuration for positioning the target UE.

22. The server of claim 21, wherein the information of the distributed RID indicates: the target UE is capable of controlling the distributed RID; a unique identification (ID) associated with the distributed controller or the distributed RID; an additional processing delay associated with the distributed RID; a position information of the distributed RID; or any combination thereof.

23. The server of claim 21, wherein the one or more processors are further configured to: receive, from the target UE, additional information indicating a position measurement performed based on the distributed RID, wherein the first RID configuration is determined at least based on the additional information.

24. The server of claim 21, wherein the one or more processors are further configured to: determine a second RID configuration, based on an ON-OFF schedule of the distributed RID, for reducing interference associated with the positioning of the target UE caused by the distributed RID.

25. The server of claim 24, wherein the one or more processors are further configured to: receive, from the target UE, usage information of the distributed RID indicating: time and frequency resources over which the RID is available for signal amplification or redirection; a directional relationship between a primary beam pair link between the target UE and a base station and a beam pair link through the distributed RID; or any combination thereof, wherein the first RID configuration or the second RID configuration is further determined based on the usage information of the distributed RID.

26. The server of claim 25, wherein the usage information of the RID comprises TCI-state IDs associated with the RID and a QCL relationship between a direct path and a path through the RID between the target UE and the base station as determined at the target UE.

27. A target User Equipment (UE) for positioning in a presence of a distributed reconfigurable intelligent device (RID), comprising: a transceiver; a memory; and one or more processors communicatively coupled with the transceiver and the memory, wherein the one or more processors are configured to: determine that a distributed RID may be used in positioning of the target UE, wherein the distributed RID is controlled by a distributed controller not being a network node; send, to a server, information of the distributed RID indicating availability of the distributed RID; and receive, from the server, a first RID configuration for the positioning of the target UE determined based at least in part on the information of the distributed RID.

28. The target UE of claim 27, wherein the information of the distributed RID indicates: the target UE is capable of controlling the distributed RID; a unique identification (ID) associated with the distributed controller or the distributed RID; an additional processing delay associated with the distributed RID; a position information of the distributed RID; or any combination thereof.

29. The target UE of claim 27, wherein the one or more processors are further configured to: transmit, to the server, additional information indicating a position measurement performed based on the distributed RID, wherein the first RID configuration is determined at least based on the additional information.

30. The target UE of claim 27, wherein the one or more processors are further configured to: receive a second RID configuration based on an ON-OFF schedule of the distributed RID for reducing interference associated with the positioning of the target UE caused by the distributed RID.