Group common downlink control information (DCI) for aperiodic positioning reference signal (PRS) triggering

Abstract

Group common downlink control information (DCI) for aperiodic positioning reference signal (AP-PRS) triggering is described herein. Embodiments for such AP-PRS can include an AP-PRS trigger command and / or a positioning measurement request command, and can be mapped to one or more bits of different blocks of the group common DCI to identify different aspects of the AP-PRS, such as one or more positioning frequency layers (PFLs), a PRS identifier (PRS-ID), a PRS resource set, and / or a PRS resource.

Description

[0001] Related applications

[0002] This application claims the benefit of Indian Patent Application No. 202021044991, filed on October 15, 2020, entitled "Group Common Downlink Control Information (DCI) for Aperiodic Positioning Reference Signal (PRS) Triggering", which has been assigned to the assignee of this application and is incorporated herein by reference in its entirety. background

[0003] Invention Field

[0004] This invention generally relates to the field of wireless communication, and more specifically to using radio frequency (RF) signals to determine the location of user equipment (UE).

[0005] Related technical descriptions

[0006] In fifth-generation (5G) new radio (NR) mobile communication networks, base stations can transmit a location reference signal (PRS) that can be measured at a UE to determine the UE's location using any of a variety of network-based positioning methods. For periodic PRS, the UE can know when the base station is transmitting the PRS based on its known periodicity. On the other hand, for aperiodic PRS (AP-PRS), the network may need to provide information about one or more base stations transmitting PRS to the UE, thereby "triggering" the base stations to monitor the PRS and / or report measurement information. The method by which this triggering information can be provided to multiple UEs has not yet been defined. Brief Overview

[0007] This document describes group-shared downlink control information (DCI) for triggering aperiodic positioning reference signals (AP-PRS). Implementations for such AP-PRS may include AP-PRS trigger commands and / or positioning measurement request commands, and may be mapped to one or more bits in different blocks of the group-shared DCI to identify different aspects of the AP-PRS, such as one or more positioning frequency layers (PFLs), PRS identifiers (PRS-IDs), PRS resource sets, and / or PRS resources.

[0008] According to this disclosure, an example method for providing aperiodic positioning reference signal (AP-PRS) information to at least one user equipment (UE) via group shared downlink control information (DCI) may include determining information regarding the transmission receiving point (TRP) transmission of the AP-PRS. The method may further include transmitting one or more information blocks in the group shared DCI for the at least one UE, wherein each of the one or more information blocks includes one or more bits mapped to: a trigger command associated with the AP-PRS, a positioning measurement request command associated with the AP-PRS, or a location report request command associated with the AP-PRS, or a combination thereof. The method may further include transmitting the group shared DCI.

[0009] According to this disclosure, an example method for using aperiodic positioning reference signal (AP-PRS) information in group-shared downlink control information (DCI) at a user equipment (UE) may include receiving one or more information blocks from a serving transport receiving point (TRP) in the group-shared DCI, wherein each of the one or more information blocks includes one or more bits mapped to: a trigger command associated with the AP-PRS, wherein the AP-PRS is transmitted from the serving TRP or a neighboring TRP; a positioning measurement request command associated with the AP-PRS; a location report request command associated with the AP-PRS; or a combination thereof. The method may also include measuring the AP-PRS based on the trigger command, positioning measurement request command, location report request command, or a combination thereof corresponding to one or more information blocks in the group-shared DCI.

[0010] According to this disclosure, an example Serving Transmitter Receiver (TRP) for providing aperiodic Positioning Reference Signal (AP-PRS) information to at least one User Equipment (UE) via Group Shared Downlink Control Information (DCI) may include a transceiver, a memory, and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to determine information regarding the transmission of AP-PRS to the Serving TRP or individual TRPs. The one or more processors may be further configured to transmit one or more information blocks in the Group Shared DCI for the at least one UE, wherein each of the one or more information blocks includes one or more bits mapped to: a trigger command associated with the AP-PRS, a location measurement request command associated with the AP-PRS, or a location report request command associated with the AP-PRS, or a combination thereof. The one or more processors may be further configured to transmit the Group Shared DCI via the transceiver.

[0011] According to this disclosure, an example user equipment (UE) for using aperiodic positioning reference signal (AP-PRS) information in group-shared downlink control information (DCI) may include a transceiver, a memory, and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to receive one or more information blocks from a serving transport receiving point (TRP) in the group-shared DCI via the transceiver, wherein each of the one or more information blocks includes one or more bits mapped to: a trigger command associated with the AP-PRS, wherein the AP-PRS is transmitted from the serving TRP or a neighboring TRP; a positioning measurement request command associated with the AP-PRS; a location report request command associated with the AP-PRS; or a combination thereof. The one or more processors may be further configured to measure the AP-PRS based on the trigger command, the positioning measurement request command, or the location report request command, or a combination thereof, corresponding to one or more information blocks in the group-shared DCI.

[0012] This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used alone to determine the scope of the claimed subject matter. The subject matter should be understood in reference to the appropriate portions of this disclosure, any or all drawings, and each claim. The foregoing, as well as other features and examples, will be described in more detail in the following description, claims, and drawings. Brief description of the attached diagram

[0013] Figure 1 This is a simplified explanation of a positioning system according to one embodiment.

[0014] Figure 2 This is a diagram illustrating a fifth-generation (5G) new radio (NR) positioning system, explaining how positioning systems are implemented within 5G NR communication systems (e.g., Figure 1 An example of a positioning system.

[0015] Figure 3 This is a diagram illustrating an example of the frame structure and associated terminology used for NR.

[0016] Figure 4 This is a diagram illustrating an example of a radio frame sequence with a Positioning Reference Signal (PRS) timing.

[0017] Figure 5 This is a diagram illustrating how different transmit / receive points (TRPs) of a given frequency layer (FL) as defined in some embodiments, such as in 5G NR, can use PRS resources and the hierarchical structure of PRS resource sets.

[0018] Figure 6This is an explanation of how positioning based on Observed Time Difference of Arrival (OTDOA) can be performed according to some embodiments.

[0019] Figure 7 This is an explanation of how positioning based on round-trip time (RTT) can be made according to some embodiments.

[0020] Figure 8 This is an explanation of how positioning based on the angle of origin (AOD) can be performed according to some embodiments.

[0021] Figure 9 This is a diagram illustrating the structure of a group shared downlink control information (DCI) according to one embodiment.

[0022] Figure 10 This is a diagram illustrating how a group-shared DCI block, according to some embodiments, can include non-periodic PRS (AP-PRS) trigger commands and location measurement report commands.

[0023] Figure 11 This is a flowchart of a method for providing AP-PRS information to at least one UE via a group-shared DCI according to an embodiment.

[0024] Figure 12 This is a block diagram of an embodiment of a UE that can be utilized in the embodiments described herein.

[0025] Figure 13 This is a block diagram of an embodiment of a TRP that can be utilized in the embodiments described herein.

[0026] Figure 14 This is a block diagram of an embodiment of a computer system that can be utilized in the embodiments described herein.

[0027] Figure 15 This is a flowchart of a method for using AP-PRS information in a group-shared DCI according to an embodiment.

[0028] Similar reference numerals in the various figures indicate similar elements according to certain examples. Additionally, multiple instances of an element can be indicated by appending a letter or hyphen followed by a second numeral after the first numeral. For example, multiple instances of element 110 may be indicated as 110-1, 110-2, 110-3, etc., or as 110a, 110b, 110c, etc. When only the first numeral is used to refer to such an element, it will be understood to refer to any instance of that element (e.g., element 110 in the previous examples would refer to elements 110-1, 110-2, and 110-3, or elements 110a, 110b, and 110c). Detailed description

[0029] The following description is directed to certain implementations in order to illustrate aspects of the innovation of the various embodiments. However, those skilled in the art will readily recognize that the teachings herein can be applied in many different ways. The described implementations can be implemented in any device, system, or network 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) IEEE 802.11 standards (including those identified as...). Those technical standards) 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 Trunking Radio (TETRA), Wideband CDMA (W-CDMA), Evolved Data Optimized (EV-DO), 1xEV-DO, EV-DO Revision A, EV-DO Revision 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 Systems (AMPS), or other known signals used for communication in wireless, cellular, or Internet of Things (IoT) networks (such as systems utilizing 3G, 4G, 5G, 6G, or further implementations thereof).

[0030] As used herein, an "RF signal" includes electromagnetic waves that transmit information through the space between a transmitter (or transmitter equipment) and a receiver (or receiver equipment). As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of each RF signal through multiple channels or paths, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal.

[0031] Additionally, unless otherwise indicated, references to “reference signal,” “location reference signal,” “reference signal for location,” etc., may be used to refer to signals used for locating user equipment (UE). As described in more detail herein, such signals may include any of a variety of signal types, but are not necessarily limited to the Location Reference Signal (PRS) as defined in the relevant radio standards.

[0032] Figure 1This is a simplified explanation of a positioning system 100 according to one embodiment, wherein the UE 105, location server 160, and / or other components of the positioning system 100 may use the techniques provided herein for determining and estimating the location of the UE 105. The techniques described herein may be implemented by one or more components of the positioning system 100. The positioning system 100 may include: the UE 105; one or more satellites 110 (also referred to as spacecraft (SV)) for a Global Navigation Satellite System (GNSS) (such as Global Positioning System (GPS), GLONASS, Galileo, or BeiDou); a base station 120; an access point (AP) 130; a location server 160; a network 170; and an external client 180. Generally, the positioning system 100 may estimate the location of the UE 105 based on RF signals received and / or transmitted by the UE 105 and the known locations of other components transmitting and / or receiving RF signals (e.g., GNSS satellite 110, base station 120, AP 130). Reference Figure 2 Further details regarding location-specific estimation techniques will be discussed.

[0033] It should be noted that Figure 1 This provides only a general explanation of the various components, where any or all of them can be appropriately utilized, and each component can be repeated as needed. Specifically, although only one UE 105 is described, it will be understood that many UEs (e.g., hundreds, thousands, millions, etc.) can utilize positioning system 100. Similarly, positioning system 100 may include more than Figure 1 The illustrated number of base stations 120 and / or access points 130 may be greater or less. The illustrated connections to the various components in the positioning system 100 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. Furthermore, components may be rearranged, combined, separated, replaced, and / or omitted depending on desired functionality. In some embodiments, for example, an external client 180 may be directly connected to the location server 160. Those skilled in the art will recognize numerous modifications to the illustrated components.

[0034] Depending on the desired functionality, network 170 may include any of a wide variety of wireless and / or wired networks. Network 170 may include, for example, combinations of public and / or private networks, local area networks (LANs) and / or wide area networks (WANs). Furthermore, network 170 may utilize one or more wired and / or wireless communication technologies. In some embodiments, network 170 may include, for example, cellular or other mobile networks, wireless local area networks (WLANs), wireless wide area networks (WWANs), and / or the Internet. Examples of network 170 include Long Term Evolution (LTE) wireless networks, fifth-generation (5G) wireless networks (also known as New Radio (NR) wireless networks or 5G NR wireless networks), Wi-Fi WLANs, and the Internet. LTE, 5G, and NR are wireless technologies defined or being defined by the Third Generation Partnership Project (3GPP). Network 170 may also include more than one network and / or more than one type of network.

[0035] Base station 120 and access point (AP) 130 can be communicatively coupled to network 170. In some embodiments, base station 120 may be owned, maintained, and / or operated by a cellular network provider and may employ any of a variety of wireless technologies as described below. Depending on the technology of network 170, base station 120 may include a B-node, evolved B-node (eNodeB or eNB), base transceiver station (BTS), radio base station (RBS), NR B-node (gNB), next-generation eNB (ng-eNB), etc. In the case where network 170 is a 5G network, base station 120, as a gNB or ng-eNB, may be part of a next-generation radio access network (NG-RAN) that can connect to a 5G core network (5GC). For example, AP 130 may include a Wi-Fi AP or An access point (AP) or an AP with cellular capabilities (e.g., 4G LTE and / or 5G NR). Thus, UE 105 can send and receive information with network-connected devices (such as location server 160) via base station 120 accessing network 170 using a first communication link 133. Additionally or alternatively, because AP 130 can also be communicatively coupled to network 170, UE 105 can 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.

[0036] As used herein, the term "base station" generally refers to a single physical transmission point or multiple physical transmission points located at base station 120. A transmit / receive point (TRP) (also referred to as a transmit / receive point) corresponds to this type of transmission point, and the term "TRP" is used interchangeably with the terms "gNB," "ng-eNB," and "base station." In some cases, base station 120 may include multiple TRPs—for example, where each TRP is associated with a different antenna or a different antenna array of base station 120. A physical transmission point may include the antenna array of base station 120 (e.g., as in a multiple-input multiple-output (MIMO) system and / or in the case of beamforming at the base station). The term "base station" may additionally refer to multiple non-co-located physical transmission points, which may be a distributed antenna system (DAS) (a network of spatially separated antennas connected via a transmission medium to a shared source) or a remote radio headend (RRH) (a remote base station connected to a serving base station). Alternatively, the physical transmission points that are not located in the same place can be the serving base station that receives the measurement report from UE 105 and the neighboring base station where UE 105 is measuring its reference RF signal.

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

[0038] Location server 160 may include servers and / or other computing devices configured to determine the estimated location of UE 105 and / or provide data (e.g., “auxiliary data”) to UE 105 to facilitate location measurement and / or location determination. According to some embodiments, location server 160 may include a Home Secure User Plane Positioning (SUPL) location platform (H-SLP) that supports SUPL user plane (UP) positioning solutions defined by the Open Mobility Alliance (OMA) and can support location services for UE 105 based on subscription information about UE 105 stored in location server 160. In some embodiments, location server 160 may include a Discovery SLP (D-SLP) or an Emergency SLP (E-SLP). Location server 160 may also include an Enhanced Serving Mobility Location Center (E-SMLC) that uses a control plane (CP) positioning solution to support the positioning of UE 105 for LTE radio access of UE 105. Location server 160 may further include location management function (LMF) that uses a control plane (CP) positioning solution to support the positioning of UE 105 for NR or LTE radio access of UE 105.

[0039] In the CP positioning solution, from the perspective of network 170, signaling for controlling and managing the positioning of UE 105 can use existing network interfaces and protocols and be exchanged as signaling between the various components of network 170 and with UE 105. In the UP positioning solution, from the perspective of network 170, signaling for controlling and managing the positioning of UE 105 can be exchanged as data (e.g., data transmitted using Internet Protocol (IP) and / or Transmission Control Protocol (TCP)) between location server 160 and UE 105.

[0040] As previously mentioned (and discussed in more detail below), the estimated location of UE 105 can be based on measurements of RF signals transmitted from and / or received by UE 105. Specifically, these measurements can provide information about the relative distance and / or angle between UE 105 and one or more components of positioning system 100 (e.g., GNSS satellite 110, AP 130, base station 120). The estimated location of UE 105 can be estimated geometrically (e.g., using polygonal measurements and / or polygonal positioning) based on the distance and / or angle measurements along with the known locations of these one or more components.

[0041] While ground components (such as AP 130 and base station 120) may be fixed, the embodiments are not limited thereto. Mobile components may be used. For example, in some embodiments, the location of UE 105 may be estimated at least in part based on measurements of RF signals 140 transmitted 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 determining the location of a particular UE 105, the UE 105 whose location is to be determined may be referred to as the “target UE,” and each of the one or more other UEs 145 may be referred to as the “anchor UE.” For the location determination of the target UE, the respective locations of the one or more anchor UEs may be known and / or determined jointly with the target UE. Direct communication between the one or more other UEs 145 and UE 105 may include sidelinks and / or similar device-to-device (D2D) communication technologies. Sidelinks, as defined by 3GPP, are forms of D2D communication under cellular-based LTE and NR standards.

[0042] The estimated location of UE 105 can be used in various applications—for example, to assist the user of UE 105 in direction finding or navigation, or to assist (e.g., in the location of another user associated with external client 180) in locating UE 105. "Location" is also referred to herein as "location estimation," "estimated location," "location," "positioning," "location estimation," "location lock," "estimated location," "location lock," or "lock." The process of determining location may be referred to as "location," "location determination," "location determination," etc. The location of UE 105 may include the absolute location of UE 105 (e.g., latitude and longitude and possible altitude) or the relative location of UE 105 (e.g., expressed as a distance north or south, east or west, and possibly above or below from another known fixed location (including, for example, the location of base station 120 or AP 130) or another location (such as the location of UE 105 at a known previous time, or the location of another UE 145 at a known previous time)). Location can be specified as a geodetic location including coordinates, which can be absolute (e.g., latitude, longitude, and optionally altitude), relative (e.g., relative to a 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 as a factory, warehouse, university campus, shopping mall, stadium, or conference center). Location can alternatively be a municipal location, and then may include one or more of the following: street address (e.g., including the name or label of country, state, county, city, road and / or street and / or road or street number) and / or location, building, part of a building, floor of a building and / or room within a building, etc. Location may further include indications of uncertainty or error, such as horizontal distances and possible vertical distances where errors are expected to exist in the location, or indications of the area or volume (e.g., a circle or ellipse) within which UE 105 is expected to be located at a certain confidence level (e.g., 95% confidence).

[0043] External client 180 may be a web server or remote application that can be associated with UE 105 in some way (e.g., accessible by a user of UE 105), or it may be a server, application, or computer system that provides location services to one or more other users, including obtaining and providing the location of UE 105 (e.g., to enable services such as friend or relative locator, asset tracking, or child or pet location). Additionally or alternatively, external client 180 may obtain the location of UE 105 and provide it to emergency service providers, government agencies, etc.

[0044] As previously mentioned, the example positioning system 100 can be implemented using a wireless communication network (such as an LTE-based or 5G NR-based network). Figure 2 A diagram of a 5G NR positioning system 200 is shown, illustrating an embodiment of a 5G NR positioning system (e.g., positioning system 100). The 5G NR positioning system 200 can be configured to determine the location of a UE 105 using access nodes to implement one or more positioning methods. The access nodes may include NRB nodes (gNBs) 210-1 and 210-2 (collectively referred to herein as gNB 210), an ng-eNB 214, and / or a WLAN 216. gNB 210 and / or ng-eNB 214 can be connected to… Figure 1 Corresponding to base station 120, and WLAN 216 can be connected to... Figure 2 One or more access points 130 correspond to this. Optionally, the 5G NR positioning system 200 can also be configured to determine the location of the UE 105 using an LMF 220 (which may correspond to a location server 160) to implement one or more positioning methods. Here, the 5G NR positioning system 200 includes the UE 105 and various components of the 5G NR network, including a next-generation (NG) radio access network (RAN) (NG-RAN) 235 and a 5G core network (5G CN) 240. The 5G network may also be referred to as an NR network; the NG-RAN 235 may be referred to as a 5G RAN or NR RAN; and the 5GCN 240 may be referred to as an NG core network. The 5G NR positioning system 200 may further utilize information from GNSS satellites 110 from GNSS systems such as the Global Positioning System (GPS) or similar systems such as GLONASS, Galileo, BeiDou, and the Indian Regional Navigation Satellite System (IRNSS). Additional components of the 5G NR positioning system 200 are described below. The 5G NR positioning system 200 may include additional or replacement components.

[0045] It should be noted that Figure 2This document provides only a general description of the various components, where any or all of them may be utilized appropriately, and each component may be repeated or omitted as needed. Specifically, although only one UE 105 is described, it will be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the 5G NR positioning system 200. Similarly, the 5G NR positioning system 200 may include a larger (or smaller) number of GNSS satellites 110, gNB 210, ng-eNB 214, wireless local area network (WLAN) 216, access and mobility management functions (AMF) 215, external clients 230, and / or other components. The described connections linking the various components in the 5G NR positioning system 200 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. Furthermore, components may be rearranged, combined, separated, replaced, and / or omitted depending on the desired functionality.

[0046] UE 105 may include and / or be referred to as a device, mobile device, wireless device, mobile terminal, terminal, mobile station (MS), Secure User Plane Positioning Enabled (SUPL) terminal (SET), or some other name. Furthermore, UE 105 may correspond to a cellular phone, smartphone, laptop computer, tablet device, personal data assistant (PDA), navigation device, Internet of Things (IoT) device, or some other portable or mobile device. Typically, although not required, UE 105 may use one or more Radio Access Technologies (RATs) (such as GSM, CDMA, W-CDMA, LTE, High Rate Packet Data (HRPD), IEEE 802.11). Bluetooth and microwave access are globally interoperable (WiMAX) TM 5G NR (e.g., using NG-RAN 235 and 5G CN240) etc.) can support wireless communication. UE 105 can also use WLAN 216 (similar to one or more RATs, and as previously referenced) that can connect to other networks (such as the Internet) to support wireless communication. Figure 1 (As mentioned) to support wireless communication. Using one or more of these RATs allows UE 105 (e.g., via...) Figure 2 The 5G CN 240 (not shown) may communicate with external client 230 via Gateway Mobile Location Center (GMLC) 225 and / or allow external client 230 (e.g., via GMLC 225) to receive location information about UE 105. When implemented in or coupled with a 5G NR network, Figure 2 The external client 230 can correspond to Figure 1 External client 180.

[0047] UE 105 may include a single entity or may include multiple entities, such as in a personal area network in which the user may employ audio, video, and / or data I / O devices, and / or body sensors, as well as separate wired or wireless modems. An estimate of the location of UE 105 may be referred to as location, location estimate, location lock, lock, positioning, location estimation, or location lock, and may be geodetic, providing location coordinates (e.g., latitude and longitude) of UE 105, which may or may not include an elevation component (e.g., altitude; height above or depth below ground level, floor level, or basement level). Alternatively, the location of UE 105 may be expressed as a municipal location (e.g., expressed as a postal address or designation of a point or smaller area within a building (such as a specific room or floor)). The location of UE 105 may also be expressed as an area or volume within which UE 105 is expected to be located with a certain probability or confidence level (e.g., 67%, 95%, etc.) (geodetically or municipally defined). The location of UE 105 may further be a relative location, which includes, for example, distance and direction defined relative to an origin at a known location, or relative to X, Y (and Z) coordinates, which may be defined geodetically, municipalally, or with 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 include any of these variations unless otherwise indicated. When calculating the location of the UE, local X, Y, and possibly Z coordinates are typically solved, and then, if necessary, the local coordinates are converted to absolute coordinates (e.g., with respect to latitude, longitude, and elevation above or below mean sea level).

[0048] Figure 2 The base station in the NG-RAN 235 shown can correspond to Figure 1 The base station 120 in the NG-RAN 235 may include gNB 210. Pairs of gNB 210 in the NG-RAN 235 may be interconnected (e.g., as shown in the image). Figure 2 (The connection shown is either a direct connection or an indirect connection via another gNB 210). The communication interface between the base stations (gNB 210 and / or ng-eNB 214) may be referred to as the Xn interface 237. Access to the 5G network is provided to UE 105 via wireless communication between UE 105 and one or more gNBs 210, which may use 5G NR to provide wireless communication access to the 5G CN 240 on behalf of UE 105. The radio interface between the base station (gNB 210 and / or ng-eNB 214) and UE 105 may be referred to as the Uu interface 239. 5G NR radio access may also be referred to as NR radio access or 5G radio access. Figure 2In this context, it is assumed that the serving gNB of UE 105 is gNB 210-1, but other gNBs (e.g., gNB 210-2) may act as serving gNBs or as secondary gNBs to provide additional throughput and bandwidth to UE 105 if UE 105 moves to another location.

[0049] Figure 2 The base stations in the NG-RAN 235 shown may additionally or alternatively include next-generation evolved B nodes (also referred to as ng-eNBs) 214. The ng-eNB 214 may connect to one or more gNBs 210 in the NG-RAN 235—for example, directly or indirectly via other gNBs 210 and / or other ng-eNBs. The ng-eNB 214 may provide LTE radio access and / or evolved LTE (eLTE) radio access to the UE 105. Figure 2 Some gNBs 210 (e.g., gNB 210-2) and / or ng-eNBs 214 may be configured to act as location-only beacons, which may transmit signals (e.g., location reference signal (PRS)) and / or broadcast auxiliary data to assist in the location 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-eNBs 214 may be configured to act as detection-only nodes, which may scan for signals containing, for example, PRS data, auxiliary data, or other location data. Such detection-only nodes may not transmit signals or data to the UE, but may transmit signals or data (involving, for example, PRS, auxiliary data, or other location data) to other network entities (e.g., one or more components of the 5G CN 240, external client 230, or controller), which may receive and store the data or use the data to locate at least UE 105. Note that although in Figure 2 The diagram shows only one ng-eNB 214, but some embodiments may include multiple ng-eNBs 214. Base stations (e.g., gNBs 210 and / or ng-eNBs 214) may communicate directly with each other via the 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.

[0050] The 5G NR positioning system 200 may also include one or more WLANs 216 that can connect to the non-3GPP interoperability 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 include one or more Wi-Fi APs (e.g., Figure 1 (AP 130). Here, N3IWF 250 can connect to other components in 5G CN 240, such as AMF 215. In some embodiments, WLAN 216 can support another RAT, such as Bluetooth. N3IWF 250 can provide support for secure access of UE 105 to other components in 5G CN 240 and / or can support interoperability between one or more protocols used by WLAN 216 and UE 105 and one or more protocols used by other components of 5G CN 240 (such as AMF 215). For example, N3IWF 250 can support: establishing an IPSec tunnel with UE 105, terminating IKEv2 / IPSec protocol with UE 105, terminating N2 and N3 interfaces to 5G CN 240 for control plane and user plane respectively, and relaying uplink (UL) and downlink (DL) control plane non-access layer (NAS) signaling across N1 interface between UE 105 and AMF 215. In some other embodiments, WLAN 216 may be directly connected to components in 5G CN 240 (e.g., such as...). Figure 2 The AMF 215 (shown by the dashed line) does not pass through N3IWF 250. For example, a direct connection between WLAN 216 and 5GCN 240 can occur if WLAN 216 is a trusted WLAN to 5GCN 240, and a Trusted WLAN Interoperability (TWIF) function that can be used as an internal component of WLAN 216 can be employed. Figure 2 (Not shown in the image) to achieve this. Note that although in Figure 2 Only one WLAN 216 is shown, but some embodiments may include multiple WLAN 216.

[0051] The access node may include any of a variety of network entities that enable communication between UE 105 and AMF 215. As described, this may include gNB 210, ng-eNB 214, WLAN 216, and / or other types of cellular base stations. However, the access node providing the functionality described herein may additionally or alternatively include entities that enable communication with... Figure 2The entity communicating with any of the various RATs (which may include non-cellular technologies) not described herein. Therefore, as used in the embodiments described below, the term "access node" may include, but is not limited to, gNB 210, ng-eNB 214, or WLAN 216.

[0052] In some embodiments, access nodes (such as 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 LMF 220, obtain location measurements of uplink (UL) signals received from UE 105 and / or obtain DL location measurements from UE 105 obtained by UE 105 for downlink (DL) signals received by UE 105 from one or more access nodes. As mentioned, although Figure 2 The description 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. However, access nodes configured to communicate according to other communication protocols can be used, such as, for example, a B node using the Wideband Code Division Multiple Access (WCDMA) protocol for Universal Mobile Telecommunications Service (UMTS) Terrestrial Radio Access Network (UTRAN), an eNB using the LTE protocol for Evolved UTRAN (E-UTRAN), or an access node using the WLAN protocol. The protocol's Bluetooth beacon station. For example, in a 4G Evolved Packet System (EPS) providing LTE radio access to UE 105, the RAN may include an E-UTRAN, which may include base stations containing eNBs supporting LTE radio access. The core network for the EPS may include an Evolved Packet Core (EPC). Thus, the EPS may include an E-UTRAN plus an EPC, where... Figure 2 In this context, E-UTRAN corresponds to NG-RAN 235 and EPC corresponds to 5GCN 240. The methods and techniques described herein for obtaining the municipal location of UE 105 are applicable to other networks of this type.

[0053] gNB 210 and ng-eNB 214 can communicate with AMF 215, and for positioning functionality, AMF 215 communicates with LMF 220. AMF 215 supports the mobility of UE 105, including cell changes and handovers from the access node of the first RAT (e.g., gNB 210, ng-eNB 214, or WLAN 216) to the access node of the second RAT. AMF 215 can also participate in supporting signaling connections to UE 105 and may support data and voice bearers for UE 105. The LMF 220 supports the use of the CP positioning solution to locate UE 105 when it accesses NG-RAN235 or WLAN 216, and supports various positioning procedures and methods, including UE-assisted / UE-based and / or network-based procedures / methods, such as A-GNSS, Observed Time Difference of Arrival (OTDOA) (which may be referred to as Time Difference of Arrival (TDOA) in NR), Real-Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cellular ID (ECID), Angle of Arrival (AOA), Angle of Departure (AOD), WLAN positioning, Round-Trip Propagation Delay (RTT), Multi-Cell RTT, and / or other positioning procedures and methods. The LMF 220 can also process location service requests for UE 105 received, for example, from AMF 215 or GMLC 225. The LMF 220 can be connected to AMF 215 and / or GMLC 225. In some embodiments, the network (such as 5GCN240) may additionally or alternatively implement other types of location support modules, such as an evolved Serving Mobility Location Center (E-SMLC) or a SUPL Location Platform (SLP). It should be noted that in some embodiments, at least a portion of the location functionality (including determining the location of UE 105) may be performed at UE 105 (e.g., by measuring downlink PRS (DL-PRS) signals transmitted by radio nodes (such as gNB 210, ng-eNB 214, and / or WLAN 216) and / or using auxiliary data, for example, provided to UE 105 by LMF 220).

[0054] Gateway Mobility Location Center (GMLC) 225 can support location requests for UE 105 received from external client 230 and can forward such location requests to AMF 215 for forwarding to LMF 220. A location response from LMF 220 (e.g., containing a location estimate for UE 105) can similarly be returned to GMLC 225 directly or via AMF 215, and GMLC 225 can then return the location response (e.g., containing the location estimate) to external client 230.

[0055] Network Open Function (NEF) 245 may be included in 5GCN 240. NEF 245 can support the secure opening of capabilities and events concerning 5GCN 240 and UE105 to external client 230. These capabilities and events can therefore be referred to as Access Functions (AF) and enable the secure provisioning of information from external client 230 to 5GCN 240. NEF 245 may be connected to AMF 215 and / or GMLC 225 for the purpose of obtaining the location of UE105 (e.g., municipal location) and providing that location to external client 230.

[0056] like Figure 2 As further explained, the LMF 220 can communicate with the gNB 210 and / or the ng-eNB 214 using NR Location Protocol Annex (NRPPa) as defined in 3GPP Technical Specification (TS) 38.455. NRPPa messages can be transmitted between the gNB 210 and the LMF 220 and / or between the ng-eNB 214 and the LMF 220 via the AMF 215. Figure 2 As further explained, LMF 220 and UE 105 can communicate using the LTE Positioning Protocol (LPP) as defined in 3GPP TS37.355. Here, LPP messages can be passed between UE 105 and LMF 220 via AMF 215 and UE 105's serving gNB 210-1 or serving ng-eNB 214. For example, LPP messages can be passed between LMF 220 and AMF 215 using messages for service-based operations (e.g., based on Hypertext Transfer Protocol (HTTP)), and can be passed between AMF 215 and UE 105 using the 5G NAS protocol. The LPP protocol can be used to support positioning of UE 105 using UE-assisted and / or UE-based positioning methods (such as A-GNSS, RTK, TDOA, multi-cell RTT, AoD, and / or ECID). The NRPPa protocol can be used to support the location of UE 105 using network-based location methods such as ECID, AOA, and uplink TDOA (UL-TDOA) and / or can be used by LMF220 to obtain location-related information from gNB 210 and / or ng-eNB 214, such as defining parameters of DL-PRS transmissions from gNB 210 and / or ng-eNB 214.

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

[0058] In the 5G NR positioning system 200, the positioning method can be classified as "UE-assisted" or "UE-based." This depends on where the request to determine the location of UE 105 originates. For example, if the request originates from the UE (e.g., from an application or "app" executed by the UE), the positioning method can be classified as UE-based. On the other hand, if the request originates from an external client or other devices or services within the AF 230, LMF 220, or 5G network, the positioning method can be classified as UE-assisted (or "network-based").

[0059] Using a UE-assisted positioning method, UE 105 can obtain location measurements and send these measurements to a location server (e.g., LMF 220) for calculating a location estimate for UE 105. For RAT-dependent positioning methods, location measurements may include one or more of the following for one or more access points: Received Signal Strength Indicator (RSSI), Round-Trip Time (RTT), Reference Received Power (RSRP), Reference Received Quality (RSRQ), Reference Time Difference (RSTD), Time of Arrival (TOA), AOA, Receive Time-Transmit Time Difference (Rx-Tx), Differential AOA (DAOA), AOD, or Timing Advance (TA). Additionally or alternatively, similar measurements may be performed on sidelink signals transmitted by other UEs, whose locations are known, and these other UEs may be used as anchor points for locating UE 105. Location measurements may additionally or alternatively include measurements for RAT-independent positioning methods, such as GNSS (e.g., GNSS pseudorange, GNSS code phase, and / or GNSS carrier phase with respect to GNSS satellite 110), WLAN, etc.

[0060] Using a UE-based positioning method, UE 105 can obtain a location measurement (e.g., which may be the same as or similar to the location measurement of a UE-assisted positioning method), and can further calculate the location of UE 105 (e.g., with the aid of auxiliary data received from a location server (such as LMF 220, SLP) or broadcast by gNB 210, ng-eNB214 or WLAN 216).

[0061] Using a network-based positioning method, one or more base stations (e.g., gNB 210 and / or ng-eNB 214), one or more APs (e.g., APs in WLAN 216), or N3IWF 250 may obtain location measurements (e.g., RSSI, RTT, RSRP, RSRQ, AOA, or TOA) of signals transmitted by UE 105, and / or may receive measurements obtained by UE 105 or, in the case of N3IWF 250, by APs in WLAN 216, and may send these measurements to a location server (e.g., LMF 220) for calculating a location estimate for UE 105.

[0062] The positioning of UE 105 can also be classified as UL-based, DL-based, or DL-UL-based depending on the type of signal used for positioning. For example, if positioning is based solely on signals received by UE 105 (e.g., from a base station or other UE), the positioning can be classified as DL-based. On the other hand, if positioning is based solely on signals transmitted by UE 105 (which may be received by, for example, a base station or other UE), the positioning can be classified as UL-based. DL-UL-based positioning includes positioning based on signals transmitted and received by UE 105, such as RTT-based positioning. Side-link (SL)-assisted positioning includes signals communicated between UE 105 and one or more other UEs. According to some embodiments, the UL, DL, or DL-UL positioning described herein can enable SL signaling to be used as a supplement to or replacement of SL, DL, or DL-UL signaling.

[0063] Depending on the positioning type (e.g., UL-based, DL-based, or DL-UL-based), the type of reference signal used may differ. For example, for DL-based positioning, these signals may include PRS (e.g., DL-PRS transmitted by the base station 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: Probe Reference Signal (SRS), Channel State Information Reference Signal (CSI-RS), Synchronization Signal (e.g., Synchronization Block (SSB) Synchronization Signal (SS)), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Physical Side Link Shared Channel (PSSCH), Demodulation Reference Signal (DMRS), etc. Furthermore, reference signals may be transmitted in Tx beams and / or received in Rx beams (e.g., using beamforming techniques), which can affect angle measurements such as AOD or AOA.

[0064] Figure 3 This is a diagram illustrating an example of a frame structure 300 for NR and associated terminology, which can serve as the basis for physical layer communication between UE105 and a base station / TRP (such as serving gNB 210-1). The transmission timeline for each of the downlink and uplink can be divided into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be divided into 10 subframes with indices 0 to 9, each subframe being 1 ms long. Each subframe may include a variable number of time slots, depending on the subcarrier spacing. Each time slot may include a variable number of symbol periods (e.g., 7 or 14 symbols), depending on the subcarrier spacing. An index may be assigned to the symbol periods in each time slot. Mini-time slots may include sub-time slot structures (e.g., 2, 3, or 4 symbols). Additionally, in Figure 3The diagram shows the complete orthogonal frequency division multiplexing (OFDM) of a subframe, illustrating how a subframe can be divided into multiple resource blocks (RBs) across both time and frequency. A single RB can comprise a grid of resource elements (REs) spanning 14 symbols and 12 subcarriers.

[0065] Each symbol in a time slot can indicate link direction (e.g., downlink (DL), uplink (UL), or flexible) or data transmission, and the link direction used for each subframe can be dynamically switched. Link direction can be based on the time slot format. Each time slot can include DL / UL data and DL / UL control information. In NR, synchronization signal (SS) blocks are transmitted. SS blocks include the primary SS (PSS), secondary SS (SSS), and a two-symbol physical broadcast channel (PBCH). SS blocks can be located at fixed time slot positions (e.g., Figure 3 The symbols 0-3 shown are transmitted. The PSS and SSS can be used by the UE for cell search and acquisition. The PSS provides half-frame timing, and the SS provides cyclic prefix (CP) length and frame timing. The PSS and SSS provide cell identity. The PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frames, SS burst set periodicity, system frame number, etc.

[0066] Figure 4 This is a diagram illustrating an example of a radio frame sequence 400 with a PRS positioning timing. A “PRS instance” or “PRS timing” is an instance of a periodically repeating time window (e.g., a group of one or more consecutive time slots) in which PRS is expected to be transmitted. A PRS timing may also be referred to as a “PRS positioning timing,” “PRS positioning instance,” “positioning timing,” “positioning instance,” or simply “timing” or “instance.” The subframe sequence 400 can be used for broadcasting PRS signals (DL-PRS signals) from base station 120 in positioning system 100. The radio frame sequence 400 can be used in 5G NR (e.g., 5G NR positioning system 200) and / or LTE. Similar to… Figure 3 ,exist Figure 4 Time is represented horizontally (e.g., on the X-axis) and increases from left to right. Frequency is represented vertically (e.g., on the Y-axis) and increases (or decreases) from bottom to top.

[0067] Figure 4 This illustrates how PRS positioning timings 410-1, 410-2, and 410-3 (collectively referred to herein as positioning timing 410) are determined by the system frame number (SFN) and the cell-specific subframe offset (Δ). PRS )415、L PRS Subframe length (or span) and PRS periodicity (T) PRSThe PRS subframe configuration, which varies from cell to cell, can be determined by the "PRS configuration index" included in the auxiliary data (e.g., TDOA auxiliary data). PRS This auxiliary data can be defined by the 3GPP control standards. Subframe offset (Δ) varies depending on the cell. PRS )415 can be defined according to the number of subframes transmitted from system frame number (SFN) 0 to the start of the first (subsequent) PRS positioning time.

[0068] PRS can be transmitted by a radio node (e.g., base station 120 or other UE) after appropriate configuration (e.g., by an operation and maintenance (O&M) server). PRS can be transmitted in specific positioning subframes or time slots grouped into positioning timing 410. For example, PRS positioning timing 410-1 may include N... PRS N consecutive positioning subframes, of which the number is N PRS The range can be between 1 and 160 (e.g., values ​​1, 2, 4, and 6, as well as other values). PRS timing 410 can be grouped into one or more PRS timing groups. As described, PRS positioning timing 410 can be periodically scheduled at intervals (consisting of a number of T). PRS The occurrence is indicated by a millisecond (or subframe) interval, where T PRS It can be equal to 5, 10, 20, 40, 80, 160, 320, 640, or 1280 (or any other suitable value). In some respects, T PRS It can be measured in terms of the number of subframes between the start of each consecutive positioning timing.

[0069] In some aspects, when UE 105 receives PRS configuration index I in auxiliary data for a specific cell (e.g., base station) PRS At that time, UE 105 can use the stored indexed data to determine the PRS periodicity (T). RPS )420 and subframe offset (Δ) that varies depending on the cell PRS 415. UE 105 can subsequently determine the radio frame, subframe, and time slot when the PRS is scheduled within the cell. Auxiliary data can be provided by, for example, a location server (e.g., Figure 1 Location server 160 and / or Figure 2 The LMF 220 in the reference cell is used to determine the reference cell and includes auxiliary data for several neighboring cells supported by each radio node.

[0070] Typically, PRS timings from all cells using the same frequency in the network are time-aligned and may have a fixed, known time offset relative to other cells using different frequencies in the network (e.g., subframe offsets (Δ) that vary from cell to cell). PRS(415). In an SFN synchronous network, all radio nodes (e.g., base station 120) can be aligned on both frame boundaries and system frame numbers. Therefore, in an SFN synchronous network, all cells supported by each radio node can use the same PRS configuration index for any specific frequency of PRS transmission. On the other hand, in an SFN asynchronous network, each radio node can be aligned on frame boundaries but not on system frame numbers. Thus, in an SFN asynchronous network, the PRS configuration index for each cell can be configured individually by the network to ensure that PRS timings are aligned in time. If UE 105 can obtain the cell timing (e.g., SFN or frame number) of at least one cell (e.g., a reference cell or serving cell), then UE 105 can determine the timing of the PRS timings 410 of the reference cell and neighboring cells for TDOA positioning. The timings of other cells can then be derived by UE 105, for example, based on assumptions about the overlap of PRS opportunities from different cells.

[0071] Reference Figure 3 The framework structure for transmitting PRS (Physical Relays) is defined as the set of REs used to transmit PRS. This set of resource elements can span multiple RBs in the frequency domain and one or more coherent symbols within a time slot in the time domain, transmitting pseudo-random quadrature phase shift keying (QPSK) sequences from the antenna ports of the TRP (Transmitter Relay). In a given OFDM symbol in the time domain, the PRS resource occupies a coherent RB in the frequency domain. The transmission of the PRS resource within a specific RB has a specific combination, or "comb" size. (The comb size can also be called "comb density"). The comb size "N" represents the subcarrier spacing (or frequency / frequency modulation spacing) within each symbol of the PRS resource configuration, where the configuration uses every Nth subcarrier of a specific symbol of the RB. For example, for comb-4, for each of the four symbols of the PRS resource configuration, the RE corresponding to every fourth subcarrier (e.g., subcarriers 0, 4, 8) is used to transmit the PRS of the PRS resource. In PRS, comb tooth sizes such as comb-2, comb-4, comb-6, and comb-12 can be used.

[0072] A “PRS resource set” comprises a group of PRS resources used for the transmission of PRS signals, where each PRS resource has a PRS resource ID. Furthermore, PRS resources in a PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and associated with a specific TRP (identified by a cell ID). “PRS resource repetition” is the repetition of PRS resources during a PRS event / instance. The number of PRS resource repetitions can be defined by a “repetition factor” for the PRS resource. Additionally, PRS resources in a PRS resource set have the same periodicity, share a silent mode configuration, and have the same cross-slot repetition factor. The periodicity can have a length selected from the following: 2 m • {4,5,8,10,16,20,32,40,64,80,160,320,640,1280,2560,5120,10240} time slots, where μ = 0,1,2,3. The repetition factor can have a length selected from {1,2,4,6,8,16,32} time slots.

[0073] A PRS resource ID in a PRS resource set can be associated with a single beam (and / or beam ID) transmitted from a single TRP (where a TRP can transmit one or more beams). That is, each PRS resource in a PRS resource set can be transmitted on a different beam, and thus, a "PRS resource" (or simply "resource") can also be referred to as a "beam". Note that this does not imply whether the UE is aware of the TRP and beam transmitting the PRS.

[0074] exist Figure 2 In the described 5G NR positioning system 200, the TRP (gNB 210, ng-eNB 214, and / or WLAN 216) can transmit frames or other physical layer signaling sequences supporting PRS signals (i.e., DL PRS) according to the frame configuration as described above. The PRS signals can be measured and used for the location determination of UE 105. As mentioned, other types of wireless network nodes (including other UEs) can also be configured to transmit PRS signals configured in a similar (or identical) manner as described above. Because the transmission of PRS by a wireless network node can be directed to all UEs within radio range, the wireless network node can be considered to transmit (or broadcast) PRS.

[0075] Figure 5This is a diagram illustrating the hierarchy of PRS resources and PRS resource sets that different TRPs can use for a given Positioning Frequency Layer (PFL) as defined in 5G NR. Relative to the network (Uu) interface, UE 105 can be configured with one or more DL-PRS resource sets from each of one or more TRPs. Each DL-PRS resource set includes K ≥ 1 DL-PRS resources, which, as described above, can correspond to the Tx beam of the TRP. A DL-PRS PFL is defined as a set of DL-PRS resource sets that have the same subcarrier spacing (SCS) and cyclic prefix (CP) type, the same DL-PRS bandwidth value, the same center frequency, and the same comb size value. In the current iteration of the NR standard, UE 105 can be configured with up to four DL-PRS PFLs.

[0076] The NR has multiple frequency bands spanning different frequency ranges (e.g., frequency range 1 (FR1) and frequency range 2 (FR2)). PFLs can be in the same or different frequency bands. In some embodiments, these PFLs can even be in different frequency ranges. Additionally, as in... Figure 5 As explained, multiple TRPs (e.g., TRP2 and TRP2) can be on the same PFL. Currently under NR, each TRP can have at most two PRS resource sets, and each PRS resource set has one or more PRS resources, as described above.

[0077] Different PRS resource sets can have different periodicity. For example, one PRS resource set can be used for tracking, while another can be used for acquisition. Additionally or alternatively, one PRS resource set may have more beams, while another may have fewer beams. Therefore, different resource sets can be used by a wireless network for different purposes.

[0078] Figure 6 This is an explanation of how OTDOA-based positioning (also known as downlink time difference of arrival (DL-TDOA)) can be made according to some embodiments. In short, OTDOA-based positioning is based on the following: the known location of the base stations (e.g., base stations 610, 610-2, and 610-3, generally referred to herein as base station 610, which may correspond to other base stations and / or TRPs described herein), the known time at which the base stations transmit the corresponding reference signals (e.g., PRS), and the time difference between the UE 605 (which may correspond to other UEs described herein) receiving the reference signals from each base station.

[0079] In OTDOA-based positioning, the location server can provide the UE 605 with OTDOA auxiliary data regarding a reference base station (which may be referred to as a "reference cell" or "reference resource") and one or more neighboring base stations relative to that reference base station (which may be referred to as "neighboring cells" or "adjacent cells," and may be individually referred to as a "target cell" or "target resource"). For example, the auxiliary data may provide the center channel frequency of each base station, various PRS configuration parameters (e.g., N...). PRS T PRS The data includes silent sequences, frequency hopping sequences, PRS IDs, PRS bandwidths, base station (cell) global IDs, PRS signal characteristics associated with directional PRS, and / or other base station-related parameters applicable to OTDOA or some other positioning method. OTDOA-based positioning by UE 605 can be facilitated by indicating the serving cell for UE 605 (e.g., where a reference cell base station is indicated as the serving base station) in the OTDOA auxiliary data. In some aspects, the OTDOA auxiliary data may also include "Expected Reference Signal Time Difference (RSTD)" parameters along with uncertainties in these expected RSTD parameters, which provide UE 605 with information about the RSTD values ​​that UE 605 is expected to measure between the reference base station and each neighboring base station at its current location. The expected RSTD, along with the associated uncertainties, can define a search window for UE 605 within which it is expected to measure RSTD values. OTDOA auxiliary information may also include PRS configuration information parameters, which allow UE 105 to determine when a PRS positioning opportunity occurs on signals received from neighboring base stations relative to a reference base station, and to determine the PRS sequence transmitted from each base station in order to measure the Time of Arrival (TOA) or RSTD. The TOA measurement may be an RSRP (Reference Signal Received Power) measurement of the average power of resource elements (REs) carrying the PRS (or other reference signals).

[0080] Using RSTD measurements, the known absolute or relative transmission timing of each base station, and the known locations of the physical transmit antennas(s) of the reference base station and neighboring base stations, the UE location can be calculated (e.g., by UE 605 or a location server). More specifically, the RSTD of the neighboring base station “k” relative to the reference base station “Ref” can be given as the difference in TOA measurements of the signals from each base station (i.e., TOA). k –TOA Ref The TOA value can be measured modulo a subframe duration (1 ms) to remove the influence of measuring different subframes at different times. Figure 6In this configuration, for example, a first base station 610-1 may be designated as a reference base station, and second and third base stations (610-2 and 610-3) are neighboring base stations. If UE 605 receives reference signals from the first base station 610-1, the second base station 610-2, and the third base station 610-3 at times T1, T2, and T2 respectively, then the RSTD measurement for the second base station 610-2 will be determined as T2-T1, and the RSTD measurement for the third base station 610-3 will be determined as T3-T1. The RSTD measurement may be used by UE 605 and / or sent to a location server to determine the location of UE 605 using (i) the RSTD measurement, (ii) the known absolute or relative transmission timing of each base station, (iii) the known locations of base stations 610(s) relative to the reference base station and neighboring base stations, and / or (iv) directional PRS characteristics (such as transmission direction). Geometrically, information (i)-(iv) allows for determining the possible locations of UE 605 for each RSTD (where each RSTD results in a hyperbola, as shown in the image). Figure 6 (as shown), and allows the location of UE 605 to be determined from the intersection of all possible locations for all RSTDs.

[0081] Figure 7 This describes how RTT-based positioning (or multi-RTT-based positioning) can be performed according to some embodiments. In short, RTT-based positioning includes a positioning method in which the location of UE 705 (which may correspond to other UEs described herein) is determined based on the known location of a base station (e.g., base station 710, which may also correspond to other base stations and / or TRPs described herein) and the known distance between UE 705 and the base station. RTT measurements between UE 705 and each base station are used to determine the distance between UE 705 and the corresponding base station, and multi-RTT positioning can be used to determine the location of UE 705.

[0082] In RTT-based positioning, the location server can coordinate RTT measurements between the UE 705 and each base station. Information provided to the UE 705 can be included in RTT auxiliary data. This auxiliary data may include, for example, reference signal (e.g., PRS) timing and other signal characteristics, base station (cell) ID, and / or other base station-related parameters applicable to multi-RTT or another positioning method. Depending on the desired functionality, RTT measurements can be made (and initiated) by either the UE 705 or the base station 710.

[0083] RTT measurement uses over-the-air (OTA) delay to measure distance. The initiating device (e.g., UE 705 or base station 710) transmits a first reference signal at a first time T1, which propagates to the responding device. At a second time T2, the first reference signal arrives at the responding device. The OTA delay (i.e., the propagation time taken for the first reference signal to travel from the initiating device to the responding device) is the difference between T1 and T2. The responding device then transmits a second reference signal at a third time T3, and the second reference signal is received and measured by the initiating device at a fourth time T4. RSRP measurement can be used to determine the TOA for times T2 and T4. Therefore, the distance d between the initiating device and the responding device can be determined using the following formula:

[0084]

[0085] (As will be understood, distance d divided by the RF propagation speed c equals the OTA delay). Therefore, a precise determination of the distance between the initiating and responding devices can be made.

[0086] The RTT measurements between UE 705 and base station 710 thus allow for the use of multilateral positioning to determine the location of UE 705. Specifically, the RTT measurements between UE 705 and the first base station 710-1, the second base station 710-2, and the third base station 710-3 (RTT1, RTT2, and RTT3, respectively) result in the determination of the distance between UE 705 and each of the base stations 710. These distances can be used to plot circles around the known locations of base stations 710 (where circle 1 corresponds to base station 701-1, circle 2 corresponds to base station 701-2, and circle 3 corresponds to base station 701-3). The location of UE 705 can be determined as the intersection of these circles.

[0087] Figure 8 This is an explanation of how AOD-based positioning (or DL-AOD) can be performed according to some embodiments. In short, AOD-based positioning is based on reference signals (e.g., PRS) received by UE 805 (which may also correspond to other UEs described herein) and transmitted through certain beams of base station 810 (which may also correspond to other base stations and / or TRPs described herein), and the corresponding coverage areas covered by these beams.

[0088] In AOD-based positioning, the location server can provide AOD auxiliary data to the UE 805. This auxiliary data (which can be based on the approximate location of the UE 805) can provide information about the reference signals of the nearby base station 810, including the center channel frequency of each base station, various PRS configuration parameters (e.g., N...). PRS T PRSThe silence sequence, frequency hopping sequence, PRS ID, PRS bandwidth, beam ID, base station (cell) global ID, PRS signal characteristics associated with directional PRS, and / or other base station-related parameters applicable to DOA or some other positioning method.

[0089] Using this information, UE 805 and / or the location server can determine the UE's location via beams(s) used by UE 805 to detect PRS(s) from each base station 810. More specifically, the PRS(s) from base station 810 are transmitted via beams centered along angular regions or slots 830. Thus, each slot 830 can correspond to a PRS(s) from a different corresponding beam. Slots 830 from different base stations 810 can form an angular grid that can be used to determine the location of UE 805. For example, as Figure 3 As explained, slot 830-1 of base station 810-1 intersects slot 830-2 of base station 810-2 to form an angular grid. UE 805 can measure (e.g., using RSRP measurements) the PRS of different beams of each base station 810. These measurements can be used by UE 805 or sent to a location server to determine the location of UE 805 from the corresponding slot intersection 850, where slot 830-1 corresponding to the PRS of the first base station 810-1 intersects slot 830-2 corresponding to the PRS of the second base station 810-2. Similar measurements can be made from additional base stations (not shown) to provide additional accuracy. Additionally or alternatively, measurements from multiple beams of a single base station 810 can enable interpolation for higher resolution positioning.

[0090] As previously indicated, periodic DL-PRS (e.g., to in...) Figure 4 The method of providing instructions allows the UE to know when the TRP transmits the PRS based on the known periodicity of the DL-PRS. On the other hand, for non-periodic DL-PRS or AP-PRS, the network may need to provide information about one or more network nodes transmitting AP-PRS to the UE, thereby "triggering" that network node to monitor the PRS (e.g., a "trigger command") and / or report measurement information (e.g., a "location measurement request command"). Such triggering can be invoked for UE-based and / or network-based positioning and can be prompted by external entities (e.g., in an emergency response center). In such instances, the LMF can provide DL-PRS configuration to the UE via Radio Resource Control (RRC) or LPP. Additionally, alternatively, the serving gNB (e.g., Figure 2The serving gNB (210-1) can trigger the UE via Media Access Control-Control Element (MAC-CE) configuration or Downlink Control Information (DCI) configuration, and its DL-PRS can be triggered by non-serving gNBs through communication with these non-serving gNBs via the Xn interface or LMF 220. Therefore, by triggering non-serving gNBs to transmit AP-PRS (and their own AP-PRS) and by pre-triggering the UE to monitor AP-PRS from each gNB, the serving gNB can orchestrate AP-PRS for the UE.

[0091] According to the embodiments described herein, a group-shared DCI can be used to trigger AP-PRS for multiple UEs. As those skilled in the art will understand, the DCI is carried from the gNB to the UE via the Physical Downlink Control Channel (PDCCH) provided in the Control Resource Set (CORESET). A group-shared DCI is a DCI provided in the search space for a group of one or more UEs. Therefore, a gNB can use a group-shared DCI to trigger multiple UEs to monitor AP-PRS from multiple gNBs (broadcast from multiple gNBs) at once, which can generally be a more efficient / more effective way to trigger AP-PRS for multiple UEs than using periodic DL-PRS.

[0092] Figure 9 This is a diagram illustrating the structure of a group-shared DCI according to one embodiment. Here, the group-shared DCI can be decomposed into n data blocks (hereinafter simply referred to as "blocks"), where each data block comprises a set of one or more bits that convey information to the UE group, thereby triggering one or more UEs in the group to monitor AP-PRS at least partially based on the group-shared DCI. It can be noted that, although... Figure 9 The data block described in the diagram comprises two bits (resulting in four different options), but alternative embodiments may include a larger or smaller number of bits. Furthermore, as detailed below, the number of data blocks may vary depending on the format used and the amount of information to be conveyed. Additionally, according to some embodiments, the bit mapping may be provided in the governance specification (e.g., established based on the type of group-shared DCI format used) or may be dynamically determined and provided to the UE group separately from the DCI.

[0093] Generally, the embodiments described herein may utilize a group-shared DCI to transmit a set of AP-PRS trigger commands and / or commands. An AP-PRS trigger command may instruct each UE to monitor one or more cells / TRPs to locate AP-PRS. In other words, the AP-PRS trigger command indicates to the UE which TRPs have been triggered to provide AP-PRS. A location measurement request command may instruct each UE to provide information back to the network (e.g., LMF 220) for locating the corresponding UE. In some embodiments, the group-shared DCI may further include a location report request command, which may include AP-PRS-related measurements already performed by the UE.

[0094] Each UE in a group of UEs targeted by a group-shared DCI can be configured to receive one or more blocks of that group-shared DCI. For example, the first UE in the group receives blocks 1 and 2, the second UE receives only block 2, the third UE may receive blocks 1, 4, and 5, and so on. Thus, each UE can be configured differently depending on the desired functionality. The indication of which blocks(s) in the DCI a UE will monitor can be provided using the “startingBitIndex” in the monitoring set provided to the UE. According to some embodiments, not only can each UE receive more than one block, but each block can be received by more than one UE, depending on the desired functionality. UEs can be configured via RRC, LPP, or MAC-CE.

[0095] The number of blocks, n, in a group-shared DCI can be limited by the size constraints imposed on the DCI. For example, for a DCI limited to 128 bits (where each block consists of two bits), the number of blocks would be limited to 64. Similarly, the number of blocks can be further limited based on the format type used and / or other factors.

[0096] Table 1 provides a list of example format types for providing AP-PRS trigger commands:

[0097]

[0098] Table 1

[0099] Format type 1 includes bit mappings to one or more PFLs. That is, each block includes bits indicating the set of one or more PFLs used by the TRP to transmit AP-PRS. Similarly, different UEs in the group can be configured to receive different blocks, and therefore can be configured to receive AP-PRS on different PFLs. When receiving DCI, the UE can assume that all PRS resources of the triggered PFL are triggered. An example mapping of 2-bit blocks to PFLs using format type 1 can be as follows: bit "00" means no AP-PRS is triggered, bit "01" maps to PFL1 and PFL2, bit "10" maps to PFL2 and PFL3, and bit "11" maps to PFL0. If the number of blocks n matches the number of UEs, each UE can then be configured with a separate set of PFLs (e.g., blocks can be mapped to UEs). That is, a UE can receive multiple blocks, thus providing additional configurability under format type 1.

[0100] Format type 2 includes bit mappings to one or more PRS identifiers (PRS-IDs). Using this format type, different blocks of a group-shared DCI can correspond to different PFLs, and bits can be used to identify which TRP will transmit the PRS based on the PRS-ID identified by the bit. Each PRS has its own timing (slot offset, etc.), so the receiving UE will know when to monitor the AP-PRS given a PRS-ID. An example of mapping two bit blocks to PRS-IDs using format type 2 could be as follows: block 0 is mapped to PFL0 and has a bit mapping where bit "01" maps to PRS-ID=5, bit "01" maps to PRS-ID=10, and bit "11" maps to PRS-ID=1 and PRS-ID=2; and block 1 is mapped to PFL1 and has the same bit mapping. In alternative embodiments, the bit mappings for different blocks can be different.

[0101] Format type 3 includes bit mappings to one or more PRS resource sets. Using this format type, different blocks of a group-shared DCI can be configured to be associated with one or more PRS-IDs (e.g., one or more TRPs), and bits can be used to identify which PRS resource set will be used by the TRP corresponding to that PRS-ID to transmit the triggered AP-PRS. For example, bits can be mapped to one or more different PRS resource set IDs.

[0102] Format type 4 includes bit mappings to one or more PRS resources. Using this format type, different blocks of a group-shared DCI can be configured to be associated with one or more PRS-IDs (e.g., one or more TRPs), and bits can be used to identify one or more specific PRS resources used by the TRP corresponding to that PRS-ID to transmit the triggered AP-PRS. For example, bits can be mapped to one or more different PRS resource IDs.

[0103] Finally, format type 5 includes bit mappings to specific combinations of different PRS aspects. That is, using this format type, each block and bit combination can be mapped to one or more unique combinations of PFL, PRS-ID, PRS resource set ID, and PRS resource ID. Thus, the group-shared DCI can include the number of unique combinations equal to the number of blocks multiplied by the number of combinations per block. For 64 blocks, each with two bits (four combinations), this would produce 256 different combinations. Example mappings for a given two-bit block could be as follows: bit "00" could be mapped to PFL0, PRS-ID1, PRS resource set ID2, and PRS resource ID5; bit "01" could be mapped to PFL1, PRS-ID6, PRS resource set ID3, and PRS resource ID8; bit "10" could be mapped to PFL3, PRS-ID2, PRS resource set ID3, and PRS resource ID8; and bit "11" could be mapped to PFL2, PRS-ID10, PRS resource set ID4, and PRS resource ID7. All other blocks in a group-shared DCI may include a set of similar bit maps that are unique to that group-shared DCI.

[0104] According to some embodiments, the governance specification can support multiple format types. Furthermore, different UEs can be configured for different format types. Some UEs can be configured for multiple format types. Some UEs may be able to receive different format types via different component carriers (CCs). For example, in one CC, a UE can use format type 1 to receive AP-PRS triggering via a group-shared DCI, and in another CC, a UE can use format type 2 to receive AP-PRS triggering via a group-shared DCI.

[0105] As described above, the group shared DCI can be used for location measurement report triggering as a supplement to or replacement of the AP-PRS triggering commands described in Table 1 above. According to some embodiments, location measurement report triggering can use bits of the group shared DCI block to identify the location method and quality of service (QOS) requirements to one or more UEs that receive the group shared DCI for location measurement reporting.

[0106] For example, depending on the first option, each block can be associated with a specific positioning method. Positioning methods may include, for example, OTDOA, RTT, or AOD positioning, as referenced... Figure 6-8 The bits can be associated with QoS requirements such as horizontal and / or vertical precision, response time, speed, etc.

[0107] According to the second option, different blocks of the group-shared DCI can be configured to correspond to different QoS requirements, and bits can indicate the positioning method. According to some embodiments, QoS requirements can be specific to different applications. For example, block 0 of the group-shared DCI can be associated with high-end QoS with 1m accuracy, and block 1 can be associated with low-end QoS with 50m accuracy.

[0108] Figure 10 This is a diagram illustrating how a group-shared DCI block can include AP-PRS trigger commands and location measurement report commands according to some embodiments. Figure 10 In the example explained in the text, a single block—block k (for example, representing...) Figure 9 The blocks 0 to n-1 may include two bits for the location measurement report command mapping (e.g., as described above with reference to the location measurement report command) and two bits for the AP-PRS trigger command mapping (e.g., as described above with reference to AP-PRS report command format types 1-5).

[0109] It should also be noted that because each UE has its own capabilities, reports provided by different UEs in a group of UEs receiving a shared DCI can differ in content and reporting time. For example, the first UE may include a mobile phone with relatively high processing power and bandwidth and capable of providing a relatively large number of measurements with a relatively short response time, while the second UE may include an IoT device capable of providing a relatively small number of measurements with a relatively long response time.

[0110] Figure 11 This is a flowchart of a method 1100 for providing AP-PRS information to at least one UE via a group-shared DCI according to an embodiment. It is used for execution... Figure 11 The functional means described in one or more of the boxes shown in the diagram can be performed by the hardware and / or software components of the base station or TRP. Figure 13 The example components of TRP have been explained, and will be described in more detail below.

[0111] In block 1110, functionality includes determining information about the transmission of AP-PRS by the TRP. As described, in some embodiments, this information may be determined by the serving TRP based on information received by the LMF. The AP-PRS may be transmitted by the TRP performing method 1100 (e.g., the serving TRP) or another TRP. In some embodiments, the LMF may be co-located with the serving TRP at the gNB. In other embodiments, this information may be obtained from the serving TRP, which can orchestrate AP-PRS from multiple nearby TRPs. Means for performing functionality in block 1110 may include a wireless communication interface 1330 of TRP 1300, a bus 1305, a DSP 1320, evaluation units 1310, a memory 1360, and / or other components, such as... Figure 13 As explained in the text.

[0112] In block 1120, functionality includes including one or more information blocks in a group-shared DCI for at least one UE. Each of these multiple information blocks includes one or more bits mapped to: an AP-PRS-related trigger command, an AP-PRS-related location measurement request command, or an AP-PRS-related location report request command, or a combination thereof. For example, as indicated in the above embodiments, the AP-PRS-related trigger command may be relayed using one or more different format types, which may include bit mappings in which different combinations of bits are mapped or indexed to two different pieces of information related to the triggered AP-PRS. According to some embodiments, one or more bits of each information block in the one or more information blocks are mapped to (i) one or more PFLs that will be used to obtain the corresponding AP-PRS, (ii) one or more PRS identifiers (PRS-IDs) that will be used to obtain the corresponding DL-PRS, (iii) one or more resource sets that will be used to obtain the corresponding AP-PRS, (iv) one or more resources that will be used to obtain the corresponding AP-PRS, or (v) a unique combination of two or more of the PFLs, PRS-IDs, resource sets, and resources of the DL-PRS.

[0113] Optionally, the group-shared DCI may include a location measurement report request command, as indicated in the above embodiments. Thus, according to some embodiments, one or more bits of each of the one or more information blocks are mapped to a QoS request that will be used for location measurement reports to AP-PRS from at least one UE. According to some embodiments, the QoS request includes accuracy, response time, speed request, or horizontal-to-vertical position request, or a combination thereof. Additionally or alternatively, one or more bits of each of the one or more information blocks are mapped to a positioning method that will be used for location measurement reports to AP-PRS from at least one UE.

[0114] like Figure 13 As explained herein, the means for performing the functionality at block 1120 may include the wireless communication interface 1305 of TRP 1300, DSP 1320, evaluation unit(s) 1310, memory 1360 and / or other components.

[0115] In block 1130, functionality includes a shared DCI for transport groups. According to some embodiments, the format of this shared DCI (including mappings of bits to various types of information) may be included in a governance standard. Where multiple formats / maps are available, one or more selected formats / maps may be provided to at least one UE by a TRP (e.g., serving gNB) or LMF. Alternatively, the TRP or LMF may provide the formats / maps themselves via MAC-CE or LPP configuration. Therefore, according to some embodiments, method 1100 may include providing at least one UE with an indication of how one or more bits are mapped to: an AP-PRS-related trigger command, a location measurement request command, a location report request command, or a combination thereof. Furthermore, according to some embodiments, providing at least one UE with an indication of how one or more bits are mapped may include providing a first mapping of the one or more bits to a first UE and a second mapping of the one or more bits to a second UE, wherein the second mapping differs from the first mapping. These mappings may be responsive to the capabilities of the at least one UE. Thus, according to some embodiments, method 1100 may further include obtaining capability information of the at least one UE and determining, at least in part, how the one or more bits are mapped to trigger commands based on that capability information. Additionally, according to some embodiments, method 1100 may further include configuring the at least one UE to use two or more information blocks of a group-shared DCI.

[0116] The means for performing functions in box 1130 may include a wireless communication interface 1330 of TRP 1300, bus 1305, DSP 1320, evaluation unit(s) 1310, memory 1360 and / or other components, such as Figure 13 As explained in the text.

[0117] According to some embodiments, additional operations may be performed, depending on the desired functionality. As described, different UEs may have different capabilities and therefore may report different information at different times. Accordingly, in some embodiments, at least one UE includes multiple UEs, and the method further includes receiving a first location measurement report from a first UE at a first time and receiving a second location measurement report from a second UE at a second time. The first time and the second time may be based on one or more capabilities of the first UE and the second UE, respectively. Furthermore, one or more capabilities of the first UE and the second UE may include the number of PRS resources that the respective UE can process per unit of time, the number of PRS symbols that the respective UE can process per unit of time, or the number of PFLs that the respective UE can process per unit of time, or a combination thereof.

[0118] In this regard, each UE can be configured to perform a method corresponding to method 1100 for using AP-PRS information in a group-shared DCI. Examples of such methods will be provided later. Figure 15 describe.

[0119] Figure 12 An embodiment of UE 105 has been explained, which can be implemented as described above (e.g., in conjunction with...). Figure 1-11 The description is used. It should be noted that... Figure 12 This is intended only to provide a general explanation of the various components, which may be appropriately utilized by any or all of them. Note that in some instances, [the components are...]. Figure 12 The components described can be localized to a single physical device and / or distributed among various networked devices that can be located in different physical locations. Furthermore, as previously mentioned, the functionality of the UE discussed in the previously described embodiments can be provided by… Figure 12 To perform the operation, one or more of the hardware and / or software components shown are used.

[0120] UE 105 is shown as including hardware elements electrically coupled (or otherwise communicable) via bus 1205. The hardware elements may include processing units 1210, which may include, but are not limited to, one or more general-purpose processors, one or more special-purpose processors (such as DSP chips, graphics accelerator processors, application-specific integrated circuits (ASICs), etc.), and / or other processing structures or devices. Figure 12As shown, some embodiments may have a separate DSP 1220 depending on the desired functionality. Wireless communication-based location determination and / or other determinations may be provided in the processing unit 1210 and / or the wireless communication interface 1230 (discussed below). The UE 105 may also include one or more input devices 1270 and one or more output devices 1215, the input devices 1270 including, but not limited to: one or more keyboards, touchscreens, touchpads, microphones, buttons, dial pads, switches, etc.; the output devices 1215 including, but not limited to: one or more displays (e.g., touchscreens), light-emitting diodes (LEDs), speakers, etc.

[0121] UE 105 may also include a wireless communication interface 1230, which may include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication device, and / or a chipset (such as...). Devices, such as IEEE 802.11 devices, IEEE 802.15.4 devices, Wi-Fi devices, WiMAX devices, WAN devices, and / or various cellular devices, etc., can enable the UE 105 to communicate with other devices as described in the above embodiments. Thus, the wireless communication interface 1230 may include an RF circuitry capable of receiving / acquiring group-shared DCI and AP-PRS from one or more TRPs as described herein. The wireless communication interface 1230 may permit the transmission of data and signaling with a network TRP (e.g., via an eNB, gNB, ng-eNB, access point, various base stations, and / or other access node types, and / or other network components), computer systems, and / or any other electronic devices communicatively coupled to a TRP as described herein. Communication may be performed via one or more wireless communication antennas 1232 that transmit and / or receive wireless signals 1234. According to some embodiments, the wireless communication antennas 1232 may include a plurality of discrete antennas, antenna arrays, or combinations thereof.

[0122] Depending on the desired functionality, the wireless communication interface 1230 may include separate receivers and transmitters, or combinations 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 105 can communicate with various data networks, which may include a variety of network types. For example, a wireless wide area network (WWAN) may be a 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 RATs, such as CDMA2000, WCDMA, etc. CDMA2000 includes IS-95, IS-2000, and / or IS-856 standards. A TDMA network may implement GSM, Digital Advanced Mobile Phone Systems (D-AMPS), or some other RAT. OFDMA networks can utilize LTE, Advanced LTE, 5G NR, and more. 5G NR, LTE, Advanced LTE, GSM, and WCDMA are described in 3GPP documents. Cdma2000 is described in documents from an organization called "3rd Generation Partnership Project 3" (3GPP2). 3GPP and 3GPP2 documents are publicly available. WLANs can also be IEEE 802.11x networks, while Wireless Personal Area Networks (WPANs) can be Bluetooth networks, IEEE 802.15x, or some other type of network. The technologies described herein can also be used in combinations of WWANs, WLANs, and / or WPANs.

[0123] UE 105 may further include sensors 1240. Sensors 1240 may include, but are not limited to, one or more inertial sensors and / or other sensors (e.g., accelerometers, gyroscopes, cameras, magnetometers, altimeters, microphones, proximity sensors, light sensors, barometers, etc.), some of which may be used to obtain measurements and / or other information related to positioning.

[0124] Embodiments of UE 105 may also include a Global Navigation Satellite System (GNSS) receiver 1280, which is capable of receiving signals 1284 from one or more GNSS satellites using an antenna 1282 (which may be the same as antenna 1232). Positioning based on GNSS signal measurements may be used to supplement and / or incorporate the techniques described herein. The GNSS receiver 1280 may use conventional techniques to extract the positioning of UE 105 from GNSS satellites 110 of GNSS systems such as Global Positioning System (GPS), Galileo, GLONASS, Quasi-Zenith Satellite System (QZSS) over Japan, Indian Regional Navigation Satellite System (IRNSS) over India, BeiDou Navigation Satellite System (BDS) over China, etc. In addition, the GNSS receiver 1280 can be used with various augmentation systems (e.g., satellite-based augmentation systems (SBAS)) that can be associated with or otherwise enabled to be used with one or more global and / or regional navigation satellite systems, such as, for example, the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Coverage Service (EGNOS), the Multifunctional Satellite Augmentation System (MSAS), and the Geographic Augmentation Navigation System (GAGAN).

[0125] It can be noted that, although in Figure 12 The GNSS receiver 1280 is described herein as a distinct component, but embodiments are not limited thereto. As used herein, the term "GNSS receiver" can include hardware and / or software components configured to acquire GNSS measurements (measurements from GNSS satellites). Thus, in some embodiments, the GNSS receiver may include a measurement engine executed by one or more processing units (such as processing unit 1210, DSP 1220, and / or processing units within wireless communication interface 1230 (e.g., in a modem)) (as software). The GNSS receiver may also optionally include a positioning engine that can use GNSS measurements from the measurement engine to determine the GNSS receiver's location using an extended Kalman filter (EKF), weighted least squares (WLS), a hatch filter, a particle filter, etc. The positioning engine may also be executed by one or more processing units (such as processing unit 1210 or DSP 1220).

[0126] UE 105 may further include memory 1260 and / or be in communication with memory 1260. Memory 1260 may include, but is not limited to, local and / or network-accessible storage, disk drives, drive arrays, optical storage devices, solid-state storage devices (such as random access memory (RAM) and / or read-only memory (ROM)), which may be programmable, flash-updatable, etc. Such storage devices may be configured to implement any suitable data storage, including but not limited to various file systems, database structures, etc.

[0127] The memory 1260 of UE 105 may also include software elements ( Figure 12 (Not shown in the text), these software elements include operating systems, device drivers, executable libraries, and / or other code (such as one or more applications). These software elements may include computer programs provided by various embodiments, and / or may be designed to implement methods provided by other embodiments, and / or configure systems provided by other embodiments, as described herein. By way of example only, one or more procedures described with respect to the methods discussed above may be implemented as code and / or instructions in memory 1260 executable by UE 105 (and / or processing units 1210 or DSP 1220 within UE 105). In one aspect, such code and / or instructions may then be used to configure and / or adapt a general-purpose computer (or other device) to perform one or more operations according to the described methods.

[0128] Figure 13 An embodiment of the TRP 1300 has been explained, which can be implemented as described above (e.g., in conjunction with...). Figure 1-12 The TRP 1300 is described and utilized in a specific way. Figure 11 The method shown herein has one or more functions. It should be noted that... Figure 13 This is intended only to provide a general explanation of the various components, which may be used appropriately for any or all of them.

[0129] TRP 1300 is shown as including hardware elements electrically coupled (or otherwise communicable) via bus 1305. The hardware elements may include processing units 1310, which may include, but are not limited to, one or more general-purpose processors, one or more special-purpose processors (such as DSP chips, graphics accelerator processors, ASICs, etc.), and / or other processing architectures or devices. Figure 13As shown, some embodiments may have a separate DSP 1320 depending on the desired functionality. According to some embodiments, location determination and / or other determination based on wireless communication may be provided in the processing unit 1310 and / or the wireless communication interface 1330 (discussed below). The TRP 1300 may also include one or more input devices and one or more output devices, the input devices including, but not limited to, a keyboard, display, mouse, microphone, buttons, dial pads, switches, etc.; the output devices including, but not limited to, a display, light-emitting diodes (LEDs), speakers, etc.

[0130] The TRP 1300 may also include a wireless communication interface 1330, which may include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication device, and / or a chipset (such as...). Devices such as IEEE 802.11 devices, IEEE 802.15.4 devices, Wi-Fi devices, WiMAX devices, cellular communication facilities, etc., enable the TRP 1300 to communicate as described herein. The wireless communication interface 1330 allows the transmission (e.g., delivery and reception) of data and signaling to the UE, other base stations / TRPs (e.g., eNB, gNB, and ng-eNB), and / or other network components, computer systems, and / or any other electronic devices described herein. Communication can be performed via one or more wireless communication antennas 1332 that transmit and / or receive wireless signals 1334.

[0131] The TRP 1300 may also include a network interface 1380, which may include support for wired communication technologies. The network interface 1380 may include a modem, network card, chipset, etc. The network interface 1380 may include one or more input and / or output communication interfaces to allow data exchange with networks, communication network servers, computer systems, and / or any other electronic devices described herein.

[0132] In many embodiments, TRP 1300 may further include memory 1360. Memory 1360 may include, but is not limited to, local and / or network-accessible storage, disk drives, drive arrays, optical storage devices, solid-state storage devices (such as RAM and / or ROM), which may be programmable, flash-updatable, etc. Such storage devices may be configured to implement any suitable data storage, including but not limited to various file systems, database structures, etc.

[0133] The memory 1360 of the TRP 1300 may also include software elements ( Figure 13(Not shown in the text), these software elements include operating systems, device drivers, executable libraries, and / or other code (such as one or more applications). These software elements may include computer programs provided by various embodiments, and / or may be designed to implement methods provided by other embodiments, and / or configure systems provided by other embodiments, as described herein. By way of example only, one or more procedures described with respect to the methods discussed above may be implemented as code and / or instructions in memory 1360 executable by TRP 1300 (and / or processing units 1310 or DSP 1320 within TRP 1300). In one aspect, such code and / or instructions may then be used to configure and / or adapt a general-purpose computer (or other device) to perform one or more operations according to the described methods.

[0134] Figure 14 This is a block diagram of an embodiment of computer system 1400, which can be used, in whole or in part, to provide one or more network components as described in the embodiments herein (e.g., Figure 1 Location server 160 Figure 2 The functionality of the LMF 220. It should be noted that... Figure 14 This is merely intended to provide a general explanation of the various components, which can be appropriately utilized by any or all of them. Therefore, Figure 14 It broadly explains how individual system components can be implemented in a relatively separate or relatively more integrated manner. Additionally, it can be noted that... Figure 14 The components of the explanation can be localized into a single device and / or distributed among various networked devices that can be deployed in different geographical locations.

[0135] Computer system 1400 is shown to include hardware elements electrically coupled (or otherwise communicatively connected) via bus 1405. The hardware elements may include processing units 1410, which may include, but are not limited to, one or more general-purpose processors, one or more special-purpose processors (such as digital signal processing chips, graphics accelerator processors, application-specific integrated circuits (ASICs), etc.), and / or other processing structures or means configured to perform one or more methods described herein. Computer system 1400 may also include: one or more input devices 1415, which may include, but are not limited to, a mouse, keyboard, camera, microphone, etc.; and one or more output devices 1420, which may include, but are not limited to, display devices, printers, etc.

[0136] Computer system 1400 may further include one or more non-transient storage devices 1425 (and / or in communication with said one or more non-transient storage devices 1425), which may include, but are not limited to, local and / or network-accessible storage, and / or may include, but are not limited to, disk drives, drive arrays, optical storage devices, solid-state storage devices (such as RAM and / or ROM), which may be programmable, flash-updatable, etc. Such storage devices may be configured to implement any suitable data storage, including but not limited to various file systems, database structures, etc. Such data storage may include databases and / or other data structures for storing and managing messages and / or other information to be transmitted via a central hub to one or more devices, as described herein.

[0137] Computer system 1400 may also include a communication subsystem 1430, which may include wireless communication technologies managed and controlled by wireless communication interface 1433, as well as wired technologies (such as Ethernet, coaxial communication, Universal Serial Bus (USB), etc.). Wireless communication interface 1433 may transmit and receive wireless signals 1455 (e.g., signals according to 5G NR or LTE) via wireless antennas 1450. Thus, communication subsystem 1430 may include modems, network interface cards (wireless or wired), infrared communication devices, wireless communication devices, and / or chipsets, etc., which enable computer system 1400 to communicate with any device (including user equipment (UE), base station and / or other TRP, and / or any other electronic device described herein) on any or all of the communication networks described herein. Therefore, communication subsystem 1430 can be used to receive and transmit data as described in the embodiments herein.

[0138] In many embodiments, computer system 1400 will further include working memory 1435, which may include RAM or ROM devices as described above. Software elements shown to be located within working memory 1435 may include operating system 1440, device drivers, executable libraries, and / or other code (such as one or more applications 1445), which may include computer programs provided by various embodiments and / or may be designed to implement methods provided by other embodiments and / or configure systems provided by other embodiments, as described herein. By way of example only, one or more procedures described with respect to the methods discussed above may be implemented as code and / or instructions executable by a computer (and / or processing units within a computer); in one respect, such code and / or instructions may then be used to configure and / or adapt a general-purpose computer (or other device) to perform one or more operations according to the described methods.

[0139] These sets of instructions and / or code may be stored on a non-transient computer-readable storage medium (such as storage device(s) 1425 described above). In some cases, the storage medium may be incorporated into a computer system (such as computer system 1400). In other embodiments, the storage medium may be separate from the computer system (e.g., a removable medium, such as an optical disc), and / or may be provided in an installation package so that the storage medium can be used to program, configure, and / or adapt a general-purpose computer storing the instructions / code. These instructions may take the form of executable code (which can be executed by computer system 1400) and / or may take the form of source code and / or installable code, which takes the form of executable code when compiled and / or installed on computer system 1400 (e.g., using various general-purpose compilers, installers, compression / decompression utilities, etc.).

[0140] Figure 15 This is a flowchart of a method 1500 for using AP-PRS information in a shared DCI according to an embodiment. It is used for execution... Figure 11 The functional means described in one or more of the boxes shown in the figure can be performed by the hardware and / or software components of the UE. Figure 12 The example components of TRP have been explained, and will be described in more detail below.

[0141] In block 1510, functionality includes receiving one or more information blocks from a Serving Delivery Receiving Point (TRP) in a group-shared DCI, wherein each of the one or more information blocks includes one or more bits mapped to: a trigger command associated with the AP-PRS, a location measurement request command associated with the AP-PRS, a location report request command associated with the AP-PRS, or a combination thereof. For example, as indicated in the above embodiments, the trigger command associated with the AP-PRS may be relayed using one or more different format types, which may include bit mappings, wherein different combinations of bits are mapped or indexed to two different messages associated with the triggered AP-PRS. According to some embodiments, one or more bits of each information block in the one or more information blocks are mapped to (i) one or more PFLs that will be used to obtain the corresponding AP-PRS, (ii) one or more PRS identifiers (PRS-IDs) that will be used to obtain the corresponding DL-PRS, (iii) one or more resource sets that will be used to obtain the corresponding AP-PRS, (iv) one or more resources that will be used to obtain the corresponding AP-PRS, or (v) a unique combination of two or more of the PFLs, PRS-IDs, resource sets, and resources of the DL-PRS, or a combination thereof.

[0142] Optionally, the group-shared DCI may include a location measurement report request command, as indicated in the above embodiments. Thus, according to some embodiments, one or more bits of each of the one or more information blocks are mapped to a QoS request that will be used for location measurement reports to AP-PRS from at least one UE. According to some embodiments, the QoS request includes accuracy, response time, speed request, or horizontal-to-vertical position request, or a combination thereof. Additionally or alternatively, one or more bits of each of the one or more information blocks are mapped to a positioning method that will be used for location measurement reports to AP-PRS from at least one UE.

[0143] like Figure 12 As explained herein, the means for performing the functionality at block 1510 may include the wireless communication interface 1205 of UE 105, DSP 1220, processing unit(s) 1210, memory 1260 and / or other components.

[0144] In block 1520, functionality includes measuring the AP-PRS based on a trigger command, a location measurement request command, a location report request command, or a combination thereof corresponding to one or more information blocks of the group-shared DCI. According to some embodiments, the format of the shared DCI (including bit-to-data mappings of various types of information) may be included in a governance standard. Where multiple formats / maps are available, one or more selected formats / maps may be provided to the UE by a TRP (e.g., serving gNB) or LMF. Alternatively, the TRP or LMF may provide the formats / maps themselves via MAC-CE or LPP configuration. Therefore, according to some embodiments, method 1500 may include receiving an indication of how one or more bits are mapped to: a trigger command, a location measurement request command, a location report request command, or a combination thereof associated with the AP-PRS. Additionally, according to some embodiments, the UE may be configured to use two or more information blocks of the group-shared DCI.

[0145] The means for performing functions in frame 1520 may include the wireless communication interface 1230 of UE 105, bus 1205, DSP 1220, evaluation unit(s) 1210, memory 1260 and / or other components, such as Figure 12 As explained in the text.

[0146] It will be apparent to those skilled in the art that substantial modifications can be made to suit specific requirements. For example, custom hardware may be used, and / or specific elements may be implemented in hardware, software (including portable software such as applets), or both. Furthermore, connectivity to other computing devices (such as network input / output devices) may be employed.

[0147] Referring to the accompanying drawings, components that may include memory may include non-transient machine-readable media. As used herein, the terms "machine-readable media" and "computer-readable media" refer to any storage medium that participates in providing data that enables a machine to operate in a particular manner. In the embodiments provided above, various machine-readable media may be involved in providing instructions / code to a processing unit and / or other devices for execution. Additionally or alternatively, machine-readable media may be used to store and / or carry such instructions / code. In many implementations, computer-readable media are physical and / or tangible storage media. Such media can take many forms, including, but not limited to, non-volatile media, volatile media, and transmission media. Common forms of computer-readable media include, for example, magnetic and / or optical media, any other physical media with a hole pattern, RAM, programmable ROM (PROM), erasable PROM (EPROM), FLASH-EPROM, any other memory chip or memory cartridge, the carrier wave described below, or any other medium from which a computer can read instructions and / or code.

[0148] The methods, systems, and devices discussed herein are examples. Various procedures or components may be appropriately omitted, substituted, or added to the various embodiments. For example, features described with reference to certain embodiments may be combined in various other embodiments. Different aspects and elements of embodiments may be combined in a similar manner. Various components of the accompanying drawings provided herein may be embodied in hardware and / or software. Moreover, technology evolves, and therefore many elements are examples that do not limit the scope of this disclosure to those particular examples.

[0149] Primarily for reasons of common use, referring to such signals as bits, information, values, elements, symbols, characters, variables, items, quantities, numbers, etc., has proven convenient in some cases. However, it should be understood that all such terms, or similar terms, are to be associated with the appropriate physical quantity and are merely convenient labels. Unless otherwise specifically stated, as is apparent from the foregoing discussion, it should be understood that throughout this specification, discussions using terms such as “processing,” “calculating,” “determining,” “identifying,” “ascertaining,” “identifying,” “associating,” “measuring,” “performing,” etc., refer to the actions or processes of a particular device (such as a dedicated computer or similar dedicated electronic computing device). Therefore, in the context of this specification, a dedicated computer or similar dedicated electronic computing device is capable of manipulating or transforming signals of physical, electronic, electrical, or magnetic quantities typically represented in the memory, registers, or other information storage, transmission, or display devices of that dedicated computer or similar dedicated electronic computing device.

[0150] As used herein, the terms “and” and “or” can include a variety of meanings, which are also contemplated to depend at least in part on the context in which such terms are used. Generally, “or,” when used in relation to a list such as A, B, or C, is intended to mean A, B, and C (in the inclusive sense) and A, B, or C (in the exclusive sense). Additionally, the term “one or more” as used herein can be used to describe any feature, structure, or property in the singular form, or can be used to describe some combination of features, structures, or properties. However, it should be noted that this is merely an illustrative example, and the claimed subject matter is not limited to this example. Furthermore, the term “at least one of” when used in relation to a list such as A, B, or C can be interpreted as meaning any combination of A, B, and / or C, such as A, AB, AA, AAB, AABBCCC, etc.

[0151] Several embodiments have been described, and various modifications, substitutions, constructions, and equivalents may be used without departing from the spirit of this disclosure. For example, the above elements may be components of a larger system, and other rules may take precedence over or otherwise modify the application of the various embodiments. Furthermore, several steps may be taken before, during, or after considering the above elements. Accordingly, the above description does not limit the scope of this disclosure.

[0152] In view of this specification, various embodiments may include different combinations of features. Examples of implementations are described in the following numbered clauses:

[0153] Clause 1. A method for providing aperiodic location reference signal (AP-PRS) information to at least one user equipment (UE) via group shared downlink control information (DCI), the method comprising: determining information regarding transmission of the AP-PRS by a transport receiving point (TRP); transmitting one or more information blocks in the group shared DCI for the at least one UE, each of the one or more information blocks comprising one or more bits mapped to: a trigger command associated with the AP-PRS, a location measurement request command associated with the AP-PRS, or a location report request command associated with the AP-PRS, or a combination thereof; and transmitting the group shared DCI.

[0154] Clause 2. The method as described in Clause 1, wherein the one or more bits of each of the one or more information blocks are mapped to: a corresponding one or more Positioning Frequency Layers (PFLs) for obtaining the AP-PRS; a corresponding one or more PRS Identifiers (PRS-IDs) for obtaining the AP-PRS; a corresponding one or more resource sets for obtaining the AP-PRS; a corresponding one or more resources for obtaining the AP-PRS; or a unique combination of two or more of the PFLs, PRS-IDs, resource sets, and resources of the AP-PRS; or a combination of the above five.

[0155] Clause 3. The method of any of Clauses 1-2 further comprises providing the at least one UE with an indication of how the one or more bits are mapped to: the trigger command associated with the AP-PRS, the location measurement request command, or the location report request command, or a combination thereof.

[0156] Clause 4. The method as described in Clause 3, wherein providing the at least one UE with an indication of how the one or more bits are mapped includes providing a first mapping of the one or more bits to a first UE and providing a second mapping of the one or more bits to a second UE, wherein the second mapping is different from the first mapping.

[0157] Clause 5. The method as described in Clause 3 further includes obtaining capability information of the at least one UE; and determining, at least in part, how the one or more bits are mapped to the trigger command based on the capability information.

[0158] Clause 6. The method of any of Clauses 1-5 further comprises: obtaining capability information of the at least one UE, wherein the one or more information blocks are transmitted in the group shared DCI for the at least one UE in response to determining, based on the capability information, that the at least one UE is capable of receiving AP-PRS information via the group shared DCI.

[0159] Clause 7. The method of any of Clauses 1-6 further comprises configuring the at least one UE to use two or more information blocks of the group shared DCI.

[0160] Clause 8. The method as described in any of Clauses 1-7, wherein the one or more bits of each of the one or more information blocks are mapped to a Quality of Service (QOS) requirement to be used in a location measurement report of the AP-PRS from the at least one UE.

[0161] Clause 9. The method as described in Clause 8, wherein the QoS requirement includes: accuracy, response time, speed request, or horizontal to vertical position request, or a combination thereof.

[0162] Clause 10. The method of any of Clauses 1-9, wherein the one or more bits of each of the one or more information blocks are mapped to a positioning method that will be used for positioning measurement reports of the AP-PRS from the at least one UE.

[0163] Clause 11. The method of any of Clauses 1-10, wherein the at least one UE comprises a plurality of UEs, and the method further comprises receiving a first positioning measurement report from a first UE at a first time and receiving a second positioning measurement report from a second UE at a second time.

[0164] Clause 12. The method of any of Clauses 1-11, wherein the first time and the second time are based on one or more capabilities of the first UE and one or more capabilities of the second UE, respectively.

[0165] Clause 13. The method as described in Clause 12, wherein one or more capabilities of the first UE and one or more capabilities of the second UE include: the number of PRS resources that the first UE, the second UE, or both can process per unit of time, the number of PRS symbols that the first UE, the second UE, or both can process per unit of time, or the number of PFLs that the first UE, the second UE, or both can process per unit of time, or a combination of the above three.

[0166] Clause 14. A method for using aperiodic Position Reference Signal (AP-PRS) information in a group-shared downlink control information (DCI) at a user equipment (UE), the method comprising: receiving one or more information blocks from a serving transport receiving point (TRP) in the group-shared DCI, wherein each of the one or more information blocks includes one or more bits mapped to: a trigger command associated with the AP-PRS, wherein the AP-PRS is transmitted from the serving TRP or a neighboring TRP; a location measurement request command associated with the AP-PRS; a location report request command associated with the AP-PRS; or a combination thereof; and measuring the AP-PRS based on the trigger command, the location measurement request command, the location report request command, or a combination thereof corresponding to the one or more information blocks in the group-shared DCI.

[0167] Clause 15. The method as described in Clause 14, wherein the one or more bits of each of the one or more information blocks are mapped to: a corresponding one or more Positioning Frequency Layers (PFLs) for measuring the AP-PRS; a corresponding one or more PRS Identifiers (PRS-IDs) for measuring the AP-PRS; a corresponding one or more resource sets for measuring the AP-PRS; a corresponding one or more resources for measuring the AP-PRS; or a unique combination of two or more of the PFLs, PRS-IDs, resource sets, and resources for measuring the AP-PRS; or a combination of the above five.

[0168] Clause 16. The method described by any of Clauses 14-15 further includes providing capability information to the Service TRP.

[0169] Clause 17. The method as described in any of Clauses 14-15 further comprises providing a positioning measurement report for the AP-PRS based on a mapping of the one or more bits of each of the one or more information blocks to a positioning method.

[0170] Clause 18. A Serving Transport Receiver (TRP) for providing aperiodic Positioning Reference Signal (AP-PRS) information to at least one User Equipment (UE) via a Group Shared Downlink Control Information (DCI), the Serving TRP comprising: a transceiver; a memory; and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: determine information regarding the transmission of AP-PRS to the Serving TRP or individual TRPs; transmit one or more information blocks in the Group Shared DCI for the at least one UE, wherein each of the one or more information blocks includes one or more bits mapped to: a trigger command associated with the AP-PRS, a location measurement request command associated with the AP-PRS, or a location report request command associated with the AP-PRS, or a combination thereof; and transmit the Group Shared DCI via the transceiver.

[0171] Clause 19. The Service TRP as described in Clause 18, wherein, in order to transmit the one or more information blocks in the group shared DCI for the at least one UE, the one or more processors are configured to map the one or more bits of each of the one or more information blocks to: a corresponding one or more Positioning Frequency Layers (PFLs) for obtaining the AP-PRS; a corresponding one or more PRS Identifiers (PRS-IDs) for obtaining the AP-PRS; a corresponding one or more resource sets for obtaining the AP-PRS; a corresponding one or more resources for obtaining the AP-PRS; or a unique combination of two or more of the PFLs, PRS-IDs, resource sets, and resources of the AP-PRS; or a combination of the above five.

[0172] Clause 20. The Service TRP as described in any of Clauses 18-19, wherein the one or more processors are further configured to provide the at least one UE with an indication of how the one or more bits are mapped to: the trigger command associated with the AP-PRS, the location measurement request command, or the location report request command, or a combination thereof.

[0173] Clause 21. The Service TRP as described in Clause 20, wherein, in order to provide the at least one UE with the indication of how the one or more bits are mapped, the one or more processors are configured to provide a first mapping of the one or more bits to the first UE and a second mapping of the one or more bits to a second UE, wherein the second mapping is different from the first mapping.

[0174] Clause 22. The Service TRP as described in Clause 20, wherein the one or more processors are further configured to: acquire capability information of the at least one UE; and determine, at least in part, how the one or more bits are mapped to the trigger command based on the capability information.

[0175] Clause 23. The Service TRP as described in any of Clauses 18-22, wherein the one or more processors are further configured to acquire capability information of the at least one UE, wherein the one or more processors are configured to transmit the one or more information blocks in the group-shared DCI for the at least one UE in response to determining, based on the capability information, that the at least one UE is capable of receiving AP-PRS information via the group-shared DCI.

[0176] Clause 24. The Service TRP as described in any of Clauses 18-23, wherein the one or more processors are further configured to configure the at least one UE to use two or more information blocks of the group shared DCI.

[0177] Clause 25. The Service TRP as described in any of Clauses 18-24, wherein the one or more processors are configured to map the one or more bits of each of the one or more information blocks to a Quality of Service (QOS) requirement to be used in a location measurement report of the AP-PRS from the at least one UE.

[0178] Clause 26. The Service TRP as described in Clause 25, wherein the QoS requirements include: accuracy, response time, speed request, or horizontal to vertical position request, or a combination thereof.

[0179] Clause 27. The Service TRP as described in any of Clauses 18-26, wherein the one or more processors are configured to map the one or more bits of each of the one or more information blocks to a positioning method to be used for positioning measurement reports of the AP-PRS from the at least one UE.

[0180] Clause 28. The Service TRP as described in any of Clauses 18-27, wherein the one or more processors are configured to receive a first location measurement report from a first UE of the at least one UE at a first time, and to receive a second location measurement report from a second UE of the at least one UE at a second time.

[0181] Clause 29. The Service TRP as described in Clause 28, wherein the one or more processors are configured to base the first time and the second time on one or more capabilities of the first UE and one or more capabilities of the second UE, respectively.

[0182] Clause 30. The Service TRP as described in Clause 29, wherein one or more capabilities of the first UE and one or more capabilities of the second UE include: the number of PRS resources that the first UE, the second UE, or both can process per time unit, the number of PRS symbols that the first UE, the second UE, or both can process per time unit, or the number of PFLs that the first UE, the second UE, or both can process per time unit, or a combination of the above three.

[0183] Clause 31. A user equipment (UE) for using aperiodic positioning reference signal (AP-PRS) information in a group-shared downlink control information (DCI), the UE comprising: a transceiver; a memory; and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: receive one or more information blocks from a serving transport receiving point (TRP) in the group-shared DCI via the transceiver, wherein each of the one or more information blocks includes one or more bits mapped to: a trigger command associated with the AP-PRS, wherein the AP-PRS is transmitted from the serving TRP or a neighboring TRP; a positioning measurement request command associated with the AP-PRS; a location report request command associated with the AP-PRS; or a combination thereof; and to measure the AP-PRS based on the trigger command, the positioning measurement request command, or the location report request command or a combination thereof corresponding to the one or more information blocks in the group-shared DCI.

[0184] Clause 32. The UE as described in Clause 31, wherein the one or more processors are configured to determine from a mapping of the one or more bits of each of the one or more information blocks: a corresponding one or more Positioning Frequency Layers (PFLs) for measuring the AP-PRS; a corresponding one or more PRS Identifiers (PRS-IDs) for measuring the AP-PRS; a corresponding one or more resource sets for measuring the AP-PRS; a corresponding one or more resources of the AP-PRS; or a unique combination of two or more of the PFLs, PRS-IDs, resource sets, and resources of the AP-PRS; or a combination of the above five.

[0185] Clause 33. The UE as described in any of Clauses 31-32, wherein one or more processors are further configured to provide capability information to the Serving TRP via the transceiver.

[0186] Clause 34. The UE as described in any of Clauses 31-33, wherein the one or more processors are further configured to provide a positioning measurement report for the AP-PRS based on the mapping of the one or more bits to the positioning method for each of the one or more information blocks.

[0187] Clause 35. An apparatus having means for performing the method as described in any of Clauses 1-17.

[0188] Clause 36. A non-transient computer-readable medium storing instructions, said instructions including code for performing methods as described in any of Clauses 1-17.

Claims

1. A method for providing aperiodic positioning reference signal (AP-PRS) information to at least one user equipment (UE) via group shared downlink control information (DCI) for at least one UE, the method comprising: Determine information regarding the transmission from the Transmitter Receiving Point (TRP) to the AP-PRS; One or more information blocks are transmitted in the group shared DCI for the at least one UE, each of the one or more information blocks including one or more bits mapped to a trigger command associated with the AP-PRS, wherein the trigger command is a command instructing the at least one UE to monitor the AP-PRS; Provide the at least one UE with an indication of how the one or more bits are mapped to the trigger command; as well as The group uses a shared DCI for transmission.

2. The method of claim 1, wherein the one or more bits of each of the one or more information blocks are mapped to: This will be used to obtain the corresponding one or more positioning frequency layers (PFLs) of the AP-PRS. One or more corresponding PRS identifiers (PRS-IDs) will be used to obtain the AP-PRS. This will be used to obtain one or more corresponding resource sets of the AP-PRS; This will be used to acquire one or more corresponding resources of the AP-PRS; or The unique combination of two or more of the PFL, PRS-ID, resource set, and resources used to obtain the AP-PRS; or The combination of the above five elements.

3. The method of claim 1, wherein providing the indication of how the one or more bits are mapped to the at least one UE comprises providing a first mapping of the one or more bits to a first UE and providing a second mapping of the one or more bits to a second UE, wherein the second mapping is different from the first mapping.

4. The method of claim 1, further comprising: Obtain the capability information of the at least one UE; as well as The determination of how the one or more bits are mapped to the trigger command is based at least in part on the capability information.

5. The method of claim 1, further comprising obtaining capability information of the at least one UE, wherein the one or more information blocks are transmitted in the group shared DCI for the at least one UE in response to determining, based on the capability information, that the at least one UE is capable of receiving AP-PRS information via the group shared DCI.

6. The method of claim 1, further comprising configuring the at least one UE to use two or more information blocks of the group shared DCI.

7. The method of claim 1, wherein the one or more bits of each of the one or more information blocks are mapped to a Quality of Service (QOS) requirement to be used in a location measurement report of the AP-PRS from the at least one UE.

8. The method of claim 7, wherein the QoS requirements include: Accuracy, Response time Speed ​​request, or Horizontal to vertical position request, or The combination of the above four.

9. The method of claim 1, wherein the one or more bits of each of the one or more information blocks are mapped to a positioning method to be used for positioning measurement reports of the AP-PRS from the at least one UE.

10. The method of claim 1, wherein the at least one UE comprises a plurality of UEs, and the method further comprises receiving a first positioning measurement report from a first UE at a first time and receiving a second positioning measurement report from a second UE at a second time.

11. The method of claim 10, wherein the first time and the second time are based on one or more capabilities of the first UE and one or more capabilities of the second UE, respectively.

12. The method of claim 11, wherein one or more capabilities of the first UE and one or more capabilities of the second UE include: The number of PRS resources that the first UE, the second UE, or both can process per unit of time. The number of PRS symbols that the first UE, the second UE, or both can process per unit of time, or The number of PFLs that the first UE, the second UE, or both can process per unit of time, or The combination of the above three.

13. A method for sharing aperiodic positioning reference signal (AP-PRS) information in downlink control information (DCI) at a user equipment (UE), the method comprising: In the group-shared DCI, one or more information blocks are received from the Serving Transport Receiver (TRP), each of the one or more information blocks including one or more bits mapped to a trigger command associated with AP-PRS, wherein the trigger command is a command instructing the UE to monitor AP-PRS; Receive an indication of how the one or more bits are mapped to the trigger command; as well as The AP-PRS is measured based on the trigger command corresponding to one or more information blocks that share the DCI with the group.

14. The method of claim 13, wherein the one or more bits of each of the one or more information blocks are mapped to: Used to measure the corresponding one or more positioning frequency layers (PFLs) of the AP-PRS. One or more corresponding PRS identifiers (PRS-IDs) are used to measure the AP-PRS. Used to measure one or more corresponding resource sets of the AP-PRS; Used to measure one or more corresponding resources of the AP-PRS; or Used to measure the unique combination of PFL, PRS-ID, resource set, and two or more of the resources in the AP-PRS; or The combination of the above five elements.

15. The method of claim 13, further comprising providing capability information to the service TRP.

16. The method of claim 13, further comprising providing a positioning measurement report for the AP-PRS based on a mapping of the one or more bits of each of the one or more information blocks to a positioning method.

17. A service delivery receiver (TRP) for providing aperiodic positioning reference signal (AP-PRS) information to at least one user equipment (UE) via group shared downlink control information (DCI) for at least one UE, the service TRP comprising: transceiver; Memory; as well as One or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: Determine information regarding the transmission of the service TRP or individual TRP to the AP-PRS; One or more information blocks are transmitted in the group shared DCI for the at least one UE, each of the one or more information blocks including one or more bits mapped to a trigger command associated with the AP-PRS, wherein the trigger command is a command instructing the at least one UE to monitor the AP-PRS; Provide the at least one UE with an indication of how the one or more bits are mapped to the trigger command; as well as The group-shared DCI is transmitted via the transceiver.

18. The Serving TRP of claim 17, wherein, in order to transmit the one or more information blocks in the group-shared DCI for the at least one UE, the one or more processors are configured to map the one or more bits of each of the one or more information blocks to: This will be used to obtain the corresponding one or more positioning frequency layers (PFLs) of the AP-PRS. One or more corresponding PRS identifiers (PRS-IDs) will be used to obtain the AP-PRS. This will be used to obtain one or more corresponding resource sets of the AP-PRS; This will be used to acquire one or more corresponding resources of the AP-PRS; or The unique combination of two or more of the PFL, PRS-ID, resource set, and resources used to obtain the AP-PRS; or The combination of the above five elements.

19. The Service TRP of claim 17, wherein, in order to provide the at least one UE with the indication of how the one or more bits are mapped, the one or more processors are configured to provide a first mapping of the one or more bits to a first UE and a second mapping of the one or more bits to a second UE, wherein the second mapping is different from the first mapping.

20. The service TRP of claim 17, wherein the one or more processors are further configured to: Obtain the capability information of the at least one UE; and The determination of how the one or more bits are mapped to the trigger command is based at least in part on the capability information.

21. The Service TRP of claim 17, wherein the one or more processors are further configured to acquire capability information of the at least one UE, wherein the one or more processors are configured to transmit the one or more information blocks in the group-shared DCI for the at least one UE in response to determining, based on the capability information, that the at least one UE is capable of receiving AP-PRS information via the group-shared DCI.

22. The Service TRP of claim 17, wherein the one or more processors are further configured to configure the at least one UE to use two or more information blocks of the group shared DCI.

23. The Service TRP of claim 17, wherein the one or more processors are configured to map the one or more bits of each of the one or more information blocks to a Quality of Service (QOS) requirement to be used in a location measurement report of the AP-PRS from the at least one UE.

24. The service TRP as described in claim 23, wherein the QoS requirements include: Accuracy, Response time Speed ​​request, or Horizontal to vertical position request, or The combination of the above four.

25. The Service TRP of claim 17, wherein the one or more processors are configured to map the one or more bits of each of the one or more information blocks to a positioning method to be used for positioning measurement reports of the AP-PRS from the at least one UE.

26. The service TRP of claim 17, wherein the one or more processors are configured to: Receive a first positioning measurement report from the first UE among the at least one UE at the first time, and A second positioning measurement report is received from a second UE among the at least one UE at a second time.

27. The Service TRP of claim 26, wherein the one or more processors are configured to base the first time and the second time on one or more capabilities of the first UE and one or more capabilities of the second UE, respectively.

28. The Service TRP of claim 27, wherein one or more capabilities of the first UE and one or more capabilities of the second UE include: The number of PRS resources that the first UE, the second UE, or both can process per unit of time. The number of PRS symbols that the first UE, the second UE, or both can process per unit of time, or The number of PFLs that the first UE, the second UE, or both can process per unit of time, or The combination of the above three.

29. A user equipment (UE) for using aperiodic positioning reference signal (AP-PRS) information in group-shared downlink control information (DCI), the UE comprising: transceiver; Memory; as well as One or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: The transceiver receives one or more information blocks from the Serving Transport Receive Point (TRP) in the group shared DCI via the transceiver, each of the one or more information blocks including one or more bits mapped to a trigger command associated with AP-PRS, wherein the trigger command is a command instructing the at least one UE to monitor AP-PRS; Receive an indication of how the one or more bits are mapped to the trigger command; as well as The AP-PRS is measured based on the trigger command corresponding to one or more information blocks that share the DCI with the group.

30. The UE of claim 29, wherein the one or more processors are configured to determine, based on the mapping of the one or more bits of each of the one or more information blocks: Used to measure the corresponding one or more positioning frequency layers (PFLs) of the AP-PRS. One or more corresponding PRS identifiers (PRS-IDs) are used to measure the AP-PRS. Used to measure one or more corresponding resource sets of the AP-PRS; Used to measure one or more corresponding resources of the AP-PRS; or Used to measure the unique combination of PFL, PRS-ID, resource set, and two or more of the resources in the AP-PRS; or The combination of the above five elements.

31. The UE of claim 29, wherein the one or more processors are further configured to provide capability information to the Serving TRP via the transceiver.

32. The UE of claim 29, wherein the one or more processors are further configured to provide a location measurement report for the AP-PRS based on the mapping of the one or more bits to the positioning method for each of the one or more information blocks.

Images